ETSI EN 301 060-1 V1.2.2 (1998-04)
Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Basic call control; Enhancement at the b service entry point for Virtual Private Network (VPN) applications; Part 1: Protocol specification
Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Basic call control; Enhancement at the b service entry point for Virtual Private Network (VPN) applications; Part 1: Protocol specification
DEN/SPS-05109-1
Digitalno omrežje z integriranimi storitvami (ISDN) - Protokol digitalne naročniške signalizacije št. 1 (DSS1) - Krmiljenje osnovnega klica - Izboljšanje uporabe osnovnega klica v vstopni točki "b" storitve za aplikacije navideznega zasebnega omrežja (VPN) - 1. del: Specifikacija protokola
General Information
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Basic call control; Enhancement at the b service entry point for Virtual Private Network (VPN) applications; Part 1: Protocol specification33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:EN 301 060-1 V1.2.23SIST EN 301 060-1:en01-december-3SIST EN 301 060-1:SLOVENSKI
STANDARD
EN 301 060-1 V1.2.2 (1998-04)European Standard (Telecommunications series)Integrated Services Digital Network (ISDN);Digital Subscriber Signalling System No. one (DSS1) protocol;Basic call control;Enhancement at the "b" service entry point forVirtual Private Network (VPN) applications;Part 1: Protocol specificationSIST EN 301 060-1:2000
ETSIEN 301 060-1 V1.2.2 (1998-04)2ReferenceDEN/SPS-05109-1 (9tc90ipc.PDF)KeywordsBasic, DSS1, ISDN, VPN, ProtocolETSIPostal addressF-06921 Sophia Antipolis Cedex - FRANCEOffice address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00
Fax: +33 4 93 65 47 16Siret N° 348 623 562 00017 - NAF 742 CAssociation à but non lucratif enregistrée à laSous-Préfecture de Grasse (06) N° 7803/88Internetsecretariat@etsi.frhttp://www.etsi.frhttp://www.etsi.orgCopyright NotificationNo 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.SIST EN 301 060-1:2000
ETSIEN 301 060-1 V1.2.2 (1998-04)3ContentsIntellectual Property Rights.5Foreword.51Scope.62References.62.1Normative references.72.2Informative references.73Definitions.74Abbreviations.95Description.95.1VPN services in the context of CN.95.2Networking aspects - requirements.115.2.1Emulation of Transit PINX functionality and Gateway PINX functionality in the public network.115.2.1.1Support of multiple CNs.125.2.2Emulation of Originating and/or Terminating PINX functionality in the public network.125.2.3Provision of Relay Node functionality in the public network.125.2.4Connection requirements.126Operational requirements.137Coding requirements.137.1Additional messages and content.137.1.1SETUP message.137.1.2CONNECT message.147.2Additional information elements coding.147.2.1Called party number.147.2.2Calling party number.167.2.3Connected number.177.2.4Connected subaddress.177.2.5Progress indicator.177.2.6Transit counter.187.2.7VPN indicator.188Basic call states.199Circuit-switched call control procedures.199.1Distinction between public network and VPN context.199.2Procedures applicable for signalling in a public network context.199.3Procedures applicable for signalling in a VPN context.209.3.1Establishment of calls from a physical PINX.209.3.1.1Call request.209.3.1.2Call confirmation.219.3.2Establishment of calls towards a physical PINX.219.3.2.1Incoming call.219.3.2.2Call confirmation.229.3.3Notification of interworking and provision of in-band information.229.3.3.1Actions at a preceding PINX.229.3.3.2Actions at a subsequent PINX.2310System parameters.24Annex A (informative):Networking aspects - CN models.25A.1Representation of a CN in terms of functional groupings.25A.1.1Connections between PINXs.25A.1.2Structured overview of the functional groupings which may be involved in a call.26A.1.3Transit networking service provided by the public network.27SIST EN 301 060-1:2000
ETSIEN 301 060-1 V1.2.2 (1998-04)4A.1.4Transit and terminating functions provided by the public network.27History.29SIST EN 301 060-1:2000
ETSIEN 301 060-1 V1.2.2 (1998-04)5Intellectual Property RightsIPRs essential or potentially essential to the present document may have been declared to ETSI. The informationpertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be foundin ETR 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect ofETSI standards", which is available free of charge from the ETSI Secretariat. Latest updates are available on the ETSIWeb 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 ETSI. Noguarantee can be given as to the existence of other IPRs not referenced in ETR 314 (or the updates on the ETSI Webserver) which are, or may be, or may become, essential to the present document.ForewordThis European Standard (Telecommunications series) has been produced by ETSI Technical Committee SignallingProtocols and Switching (SPS).The present document defines the Digital Subscriber Signalling System No. one (DSS1) extensions to the basic call tosupport the Private Signalling System No. one (PSS1) information flow (see ISO/IEC 11572 [7]) in Virtual PrivateNetwork (VPN) applications. The relevant requirements and other information that affect DSS1 are defined in thepresent document.The present document is part 1 of a multi-part European Standard (Telecommunications series) covering the IntegratedServices Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Basic callapplications: enhancement at the "b" service entry point for Virtual Private Network (VPN) applications, as identifiedbelow:Part 1:"Protocol specification";Part 2:"PICS proforma specification";Part 3:"Test Suite Structure and Test Purposes (TSS&TP), user";Part 4:"Abstract Test Suite (ATS), user";Part 5:"Test Suite Structure and Test Purposes (TSS&TP), network";Part 6:"Abstract Test Suite (ATS), network".National transposition datesDate of adoption of this EN:3 April 1998Date of latest announcement of this EN (doa):31 July 1998Date of latest publication of new National Standardor endorsement of this EN (dop/e):31 January 1999Date of withdrawal of any conflicting National Standard (dow):31 January 1999SIST EN 301 060-1:2000
ETSIEN 301 060-1 V1.2.2 (1998-04)61ScopeThe present document specifies the extensions of the protocol for basic call control for the pan-European IntegratedServices Digital Network (ISDN). These extensions are applicable at the "b" service entry point (as defined in clause 5of the present document). It is part of the Digital Subscriber Signalling System No. One (DSS1) protocol. The presentdocument contains only additional requirements to those in the main body of ETS 300 403-1 [2].The present document is applicable only to point-to-point access configurations.The present document specifies additional protocol elements and call control procedures for the handling of callsbetween users in a Corporate telecommunication Network (CN) at the "b" service entry point. The functionalityprovided by the public network may be:-the emulation of an Originating Private Integrates services Network Exchange (PINX);-the emulation of a Terminating PINX;-the emulation of a Transit PINX;-the emulation of a Relay Node;-the emulation of an Incoming Gateway PINX;-the emulation of an Outgoing Gateway PINX;-the emulation of a combination of two or more of the above.The support of these capabilities is a network option.The present document does not cover the requirements for support of the "a" service entry point.The specification included in the present document does not imply any specific implementation technology or platform.NOTE:Calls/connections relating to the "b" service entry point are distinguished from calls that are accessing thepublic network at the T reference point. Calls relating to the T reference point are supported in accordancewith the requirements of EN 300 403-1 [2]. Calls relating to the "b" service entry point are supported inaccordance with the requirements of the present document. The requirements have been defined such thatboth contexts can coexist on the same access, and this is expected to be a typical implementation. There isno requirement that when the provisions of the present document are implemented, calls at the T referencepoint also need to be implemented on the same access. Where both contexts are implemented, the accessresources are common to both contexts.2ReferencesReferences may be made to:a)specific versions of publications (identified by date of publication, edition number, version number, etc.), inwhich case, subsequent revisions to the referenced document do not apply; orb)all versions up to and including the identified version (identified by "up to and including" before the versionidentity); orc)all versions subsequent to and including the identified version (identified by "onwards" following the versionidentity); ord)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 samenumber.SIST EN 301 060-1:2000
ETSIEN 301 060-1 V1.2.2 (1998-04)72.1 Normative references[1] ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces - reference configurations".[2] EN 300 403-1: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling SystemNo. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control; Part 1:Protocol specification".[3] ETS 300 097-1: "Integrated Services Digital Network (ISDN); Connected Line IdentificationPresentation (COLP) supplementary service; Digital Subscriber Signalling System No. one (DSS1)protocol; Part 1: Protocol specification".[4] ITU-T Recommendation I.210 (1993): "Principles of telecommunication services supported by anISDN and the means to describe them".[5] ITU-T Recommendation I.112 (1993): "Vocabulary of terms for ISDNs".[6] ISO/IEC 11571 (1994): "Information technology -- Telecommunications and information exchangebetween systems -- Numbering and sub-addressing in private integrated services networks".[7] ISO/IEC 11572 (1996), plus Amendment 1 (1996) and Amendment 2 (1996): "Informationtechnology - Telecommunications and information exchange between systems - Private IntegratedServices Network - Circuit mode bearer services - Inter-exchange signalling procedures andprotocol".[8] ISO/IEC 11579-1 (1994): "Information technology -- Telecommunications and informationexchange between systems -- Private integrated services network -- Part 1: Reference configurationfor PISN Exchanges (PINX)".[9] ISO/IEC 15056 (1997): "Information technology - Telecommunications and information exchangebetween systems - Private Integrated Services Network - Inter-exchange signalling protocol -Transit counter additional network feature".2.2 Informative references[10] ITU-T Recommendation I.330: "ISDN numbering and addressing principles".[11] ETR 172 (1995): "Business TeleCommunications (BTC); Virtual PrivateNetworking (VPN); Services and networking aspects; Standardization requirements and workitems".3 DefinitionsFor the purposes of the present document, the following definitions apply:Corporate telecommunication Network (CN): Consists of sets of equipment (Customer Premises Equipment (CPE)and/or Customer Premises Network (CPN)) which are located at geographically dispersed locations and areinterconnected to provide networking services 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.g. a single PINX orCentrex-provided services to users at a single location) may form a CN.end PINX functionality: Within the context of a call the functionality of a PINX required to provide attachment andservicing of terminals.gateway PINX functionality: Within the context of a call the functionality of a PINX required to interconnect EndPINXs or Transit PINXs with nodes of other public or private networks.incoming Gateway PINX functionality: Gateway PINX functionality providing support of calls incoming to the CN.SIST EN 301 060-1:2000
ETSIEN 301 060-1 V1.2.2 (1998-04)8integrated Services Digital Network (ISDN): See ITU-T Recommendation I.112 [5], definition 308.originating PINX functionality: End PINX functionality providing support of the calling user.outgoing Gateway PINX functionality: Gateway PINX functionality providing support of calls from the CN to othernetworks.preceding PINX: In the context of a call, an entity with PINX functionality located in the direction towards theoriginating interface. A preceding PINX may be functionality provided by a physical PINX or may be an emulation ofPINX functionality by the public network.Private Integrated services Network eXchange (PINX): A PISN nodal entity that provides automatic switching andcall handling functions used for the provision of telecommunication services. The nodal entity can be implemented byone or more pieces of equipment located on the premises of the private network administrator or by equipment co-located with, or physically part of, a public network.NOTE 3:If applicable, a PINX provides to users of the same and/or other private integrated services networkexchanges:-telecommunication services within its own area; and/or-telecommunication services from the public ISDN; and/or-telecommunication services from other public or private networks; and/or-within the context of a PISN, telecommunication services from other PINXs.Relay Node functionality: Within the context of a call the functionality that identifies calls between users in the CN,and relays such calls to designated PINX functionality emulated by the public network, or to a designated terminating"b" service entry point. This may be via other Relay Nodes. Relay Node functionality includes transparent handling ofprivate networking information (e.g. transit counter).service; telecommunications service: See ITU-T Recommendation I.112 [5], definition 201.subsequent PINX: In the context of a call, an entity with PINX functionality located in the direction towards thedestination interface. A subsequent PINX may be functionality provided by a physical PINX or may be an emulation ofPINX functionality by the public network.supplementary service: See ITU-T Recommendation I.210 [4], subclause 2.4.terminating PINX functionality: End PINX functionality providing support of the called user.transit PINX functionality: Within the context of a call the functionality of a PINX required to interconnect EndPINXs and/or other Transit PINXs and/or Gateway PINXs.Virtual Private Network (VPN): That part of a CN that provides corporate networking using shared switched networkinfrastructures. This is split into VPN architecture and VPN services.The VPN architecture is that part of a CN that provides corporate networking between customer equipment where:-the shared switch network infrastructure takes the place of the traditional analogue or digital leased lines and thefunction of the transit node, irrespective of the network type, whether it be the Public Switched TelephoneNetwork (PSTN), ISDN, mobile communication network, or a separate network;-the customer premises may be served in terms of end node functionality with any combination of PBX, Centrex,Local Area Network (LAN) router, or multiplexer;-the CN user may also be served by terminal equipment connected to end node functionality residing on customerpremises, or provided by public network equipment; and-the VPN architecture in one network, or multiple networks, comprises a part of the total national or internationalCN.VPN services offered by the switched network infrastructure provide:-VPN end-user services to CN users;-VPN networking services to support the interconnection of PINXs;SIST EN 301 060-1:2000
ETSIEN 301 060-1 V1.2.2 (1998-04)9-service interworking functionality;-inter-VPN services to provide co-operation between the VPN services of two networks; and-VPN management services to enable service subscribers to control and manage their VPN resources andcapabilities.4AbbreviationsFor the purposes of the present document, the following abbreviations apply:ANF-TCAdditional Network Feature - Transit CounterBCDBinary Coded DigitCLIPCalling Line Identification Presentation supplementary serviceCLIRCalling Line Identification Restriction supplementary serviceCNCorporate telecommunication NetworkCOLPCOnnected Line identification Presentation supplementary serviceCOLRCOnnected Line identification Restriction supplementary serviceCPECustomer Premises EquipmentCPNCustomer Premises NetworkDSS1Digital Subscriber Signalling System No. oneIA5International Alphabet No. fiveIVNInterVening NetworkISDNIntegrated Services Digital NetworkLANLocal Area NetworkPBXPrivate Branch eXchangePINXPrivate Integrated services Network eXchangePISNPrivate Integrated Services NetworkPSS1Private Signalling System No. onePSTNPublic Switched Telephone NetworkSUBSUBaddressing supplementary serviceTETerminal EquipmentVPNVirtual Private Network5DescriptionThe present document specifies the extensions required to the basic call control signalling protocol defined inEN 300 403-1 [2] to support calls within a Corporate telecommunication Network (CN) and to support calls which enteror exit the CN via Gateway Private Integrated services Network eXchange (PINX) functionality performed by the publicnetwork. The protocol is applicable at the T reference points to which VPN services are provided. The support of theseadditional signalling capabilities is a network option. These Digital Subscriber Signalling System No. one (DSS1)extensions shall be made available to PINXs, on the basis of bilateral agreements at subscription time.The additional basic call signalling capabilities identified in the present document are to provide information flows thatare functionally identical to the information flows provided by the Private Signalling System No. 1 (PSS1) basic callcontrol protocol (as defined by ISO/IEC 11572 [7]). In the context of the present document, the public network(providing VPN services) can be seen, from the private network perspective, as providing an interconnection between aPINX supporting the present document and another PINX supporting PSS1 information flows. This second PINX maybe a physical PINX connected to the public network or may be an emulation of an End PINX functionality provided bythe public network.5.1VPN services in the context of CNThe support of virtual private networking has been developed using the concept of "service entry points". This enablesVPN services to be described without the need to identify impacts on particular protocols. Whilst the present documentonly relates to the "b" service entry point and to PINX type 2, the other service entry points are included forcompleteness. Items that are covered by the present document are specifically identified in the text.SIST EN 301 060-1:2000
ETSIEN 301 060-1 V1.2.2 (1998-04)10Annex A provides more information on CN models.In order to identify VPN services and the points where these services are offered (service entry points) the CN overviewgiven in figure 1 has been produced. It reflects a CN overview in terms of services and service relations between:-CPE/CPN;-public networks;-VPN service providers; and-VPN service subscribers.The following PINX types are defined:PINX type 1:An implementation of a PINX outside the public network that supports services provided by thepublic ISDN and/or PSTN.PINX type 2:An implementation of a PINX outside the public network that supports services based on PISNstandards in addition to the services provided by the public ISDN and/or PSTN. The scope of thepresent document covers the support of PINX type 2.Referring to figure 1, VPN services can be subdivided into four classes depending on the service entry point at whichthey are offered:-VPN end-user services: services offered at the "a1", "a2" and "a3" service entry points;-VPN networking services: services offered at the "b" service entry point;-Inter-VPN services: services offered at the "c" service entry point; and-VPN management services: services offered at the "d" service entry point.PINXtype1or2PINXtype1or2PINXtype1or2CustomerPremises EquipmentPINXtype1CustomerPremises NetworkVPN Servicesby Network ANon-registeredVPN AccessPhysical/PublicNetwork AVPN Servicesby Network BNon-registeredVPN AccessPhysical/PublicNetwork BVPN ServiceProviderdVPN Management ServicesVPN Servicesubscribera3a3cbPINXtype2CustomerPremises EquipmentDedicatedVPN AccessesPINXtype1PINXtype2a1bbVPNend userservicesVPNend userservicesbba2RegisteredVPN AccessNOTE:a2 is a registered VPN access operating in the CN mode.Figure 1: VPN services in context of a CNThe following types of service entry points are identified:a1:The "a1" service entry point for an access (within a specific CN) which is dedicated to the utilization of VPNservices. This is referred to as "dedicated VPN access". At this service entry point, a pre-defined set of VPNend-user services is permanently available.SIST EN 301 060-1:2000
ETSIEN 301 060-1 V1.2.2 (1998-04)11a2:The "a2" service entry point for a public network access which is registered as able to utilize VPN serviceswithin a predetermined CN. This is referred to as "registered VPN access". At this service entry point, the usercan use either its pre-defined set of VPN end-user services, or the public network services.a3:The "a3" service entry point for a public network access which is not registered for the utilization of VPNservices. This is referred to as "non-registered VPN access". By means of an appropriate authenticationprocedure a pre-defined set of VPN end-user services becomes available to the CN user.b:The "b" service entry point for PINX type 2 and PINX type 1. At this service entry point VPN networkingservices are provided to PINX type 2 and PINX type 1 for the provision/support of services to its end-users. Thescope of the present document covers the "b" service entry point and the support of PINX type 2.c:The "c" service entry point for the provision of inter-VPN services between different VPN service providers. Atthis service entry point co-operation between VPN service providers enables VPN services to span multiplepublic networks.d:The "d" service entry point between the VPN service provider and the VPN service subscriber for the offering ofVPN management services. They allow the VPN service subscriber to manage resources and capabilities relatedto its CN.The "a1", "a2", and "a3" service entry points are subcategories of the "a" service entry point that provides VPN end-userservices.5.2Networking aspects - requirementsThe public network may provide one or more of the following capabilities:-the emulation of an Originating PINX;-the emulation of a Terminating PINX;-the emulation of a Transit PINX;-the emulation of a Relay Node;-the emulation of an Incoming Gateway PINX;-the emulation of an Outgoing Gateway PINX.5.2.1Emulation of Transit PINX functionality and Gateway PINXfunctionality in the public networkThis subclause addresses some requirements for the emulation of Transit PINX functionality, and for the emulation ofGateway PINX functionality, in the public network.For the emulation of Transit PINX functionality, the functions provided by the public network shall meet therequirements of Transit PINX Call Control as defined in ISO/IEC 11572 [7] for the circuit-switched call control and theISO supplementary services associated to the basic call (the Calling Line Identification Presentation supplementaryservice (CLIP), the Calling Line Identification Restriction supplementary service (CLIR), the COnnected Lineidentification Presentation supplementary service (COLP), the COnnected Line identification Restriction supplementaryservice (COLR), the SUBaddressing supplementary service (SUB)). In addition the transit counter additional networkfeature (ANF-TC) defined in ISO/IEC 15056 [9] may be supported by those extensions to the DSS1 protocol.For the emulation of Incoming Gateway PINX functionality, the functions provided by the public network shall meet therequirements of Incoming Gateway PINX call control as defined in ISO/IEC 11572 [7] for the circuit-switched callcontrol and the ISO supplementary services associated to the basic call (CLIP, CLIR, COLP, COLR, SUB). In additionANF-TC defined in ISO/IEC 15056 [9] may be supported by those extensions to the DSS1 protocol.For the emulation of Outgoing Gateway PINX functionality, the functions provided by the public network shall meet therequirements of Outgoing Gateway PINX call control as defined in ISO/IEC 11572 [7] for the circuit-switched callcontrol and the ISO supplementary services associated to the basic call (CLIP, CLIR, COLP, COLR, SUB). In additionANF-TC defined in ISO/IEC 15056 [9] may be supported by those extensions to the DSS1 protocol.SIST EN 301 060-1:2000
ETSIEN 301 060-1 V1.2.2 (1998-04)12In general, the requirements are common to both and any requirements applying specifically to one type of functionalityare indicated explicitly. Annex A contains a number of call examples to illustrate how the different functionality caninteract.NOTE:The requirements identified here need not be fulfilled in every switching element in the public network;these requirements need only be implemented at those switching elements in which CN functionality isneeded.The requirements for basic call functionality are identified in the following subclauses.5.2.1.1Support of multiple CNsThe public network can support the co-existence of multiple CNs in parallel, i.e. the resources of the public network areshared by multiple CNs. Each CN should be considered as a separate network.The facilities of the virtual transit PINX or virtual gateway PINX are shared between the different CNs. Thus, the virtualtransit PINX or virtual gateway PINX need to be able to provide differentiation between the calls belonging to thedifferent CNs.The minimum requirement of the virtual transit PINX and the virtual gateway PINX is to be able to uniquely identify theCN to which a particular attached PINX belongs in order to ensure correct routeing of a particular call. In addition, toensure that calls do not terminate on incorrect CNs, a mechanism may be required at the point where the call leaves thepublic network.In addition, a PINX may support multiple CNs. Thus the mechanism for identifying a CN needs to be conveyed betweena PINX and the public network.The capability of supporting multiple CNs is fulfilled by the VPN indicator information element defined in subclause7.2.7.5.2.2Emulation of Originating and/or Terminating PINX functionality in thepublic networkThis subclause identifies the requirements for the emulation of originating and/or Terminating PINX functionality in thepublic network. This is commonly known as Centrex.For the emulation of Originating PINX functionality, the functions provided by the public network shall meet therequirements of Originating PINX Call Control as defined in ISO/IEC 11572 [7] for the circuit-switched call control andthe ISO supplementary services associated with the basic call (CLIP, CLIR, COLP, COLR, SUB). In addition ANF-TCdefined in ISO/IEC 15056 [9] may be supported by those extensions to the DSS1 protocol.For the emulation of Terminating PINX functionality, the functions provided by the public network shall meet therequirements of Terminating PINX Call Control as defined in ISO/IEC 11572 [7] for the circuit-switched call controland the ISO supplementary services associated to the basic call (CLIP, CLIR, COLP, COLR, SUB). In addition ANF-TC defined in ISO/IEC 15056 [9] may be supported by those extensions to the DSS1 protocol.The requirements identified here are not required in every switching element in the public network.5.2.3Provision of Relay Node functionality in the public networkFor Relay Node functionality, the public network shall provide:-minimal routeing capability; and-transparent handling of private networking information (e.g. transit counter).5.2.4Connection requirementsFour types of network connections can be identified:-connection to a PINX;SIST EN 301 060-1:2000
ETSIEN 301 060-1 V1.2.2 (1998-04)13-connection through the CN (e.g. supported by the Relay Node functionality);-access from a digital terminal (outside the scope of the present document); and-access from an analogue terminal (outside the scope of the present document).For connection to a PINX, the interface here is the same as that between two PINXs.6Operational requirementsThe provision of the capabilities described in the present document may require a prior arrangement between theoperator of the physical PINX and the public network infrastructure.The public network infrastructure shall be able to associate one CN with the access, and may as an option be able toassociate multiple CNs with the access.As an option, the operator of the public network infrastructure may offer the VPN service with the subscription optionshown in table 1. This option shall apply per access.Table 1OptionValuesDefault CNNominated CN, or none designated7Coding requirementsThe coding requirements in this clause apply to the VPN context. The coding requirements applicable to the publicnetwork context are outside the scope of the present document.NOTE 1:The coding of messages and information elements relating to the restart procedures in EN 300 403-1 [2]apply regardless of the context, i.e. they are common to both the public network context and the VPNcontext.NOTE 2:The
coding of messages and information elements relating to the segmentation and reassemblyprocedures in EN 300 403-1 [2] apply regardless of the context, i.e. they are common to both the publicnetwork context and the VPN context.7.1Additional messages and contentThe coding requirements contained in subclause 3.1 of EN 300 403-1 [2] relating to the ALERTING,CALL PROCEEDING, CONNECT ACKNOWLEDGE, PROGRESS, SETUP ACKNOWLEDGE, DISCONNECT,RELEASE, RELEASE COMPLETE, INFORMATION, STATUS and STATUS ENQUIRY messages shall applyunchanged in a VPN context.The coding requirements contained in subclause 3.1 of EN 300 403-1 [2] relating to the CONNECT and SETUPmessages shall apply in a VPN context with the additions specified in the following subclauses.NOTE:The NOTIFY message forms part of the basic call in a public network context. However, in a VPNcontext it forms part of the Generic Functional Protocol for the support of supplementary services.7.1.1SETUP messageThe VPN indicator information element may be included in the SETUP message in both the user-network and thenetwork-user directions.Inclusion of this information element is mandatory to indicate a VPN context.SIST EN 301 060-1:2000
ETSIEN 301 060-1 V1.2.2 (1998-04)14The Called party number information element is mandatory in both the user-network and the network-user directions.The Transit counter information element may be included in the SETUP message, for use in both user-to-network andnetwork-to-user directions.7.1.2CONNECT messageThe Connected number information element and the Connected subaddress information element may be included in theCONNECT message for use in both the user-network and the network-user directions.7.2Additional information elements codingThe coding requirements contained in subclause 3.1 of EN 300 403-1 [2] relating to the following information elementsshall apply unchanged in a VPN context:-Locking shift;-Non-locking shift;-Sending complete;-Bearer capability;-Cause;-Call state;-Channel identification;-Calling party subaddress;-Called party subaddress;-Low layer compatibility; and-High layer compatibility.The coding requirements contained in subclause 3.1 of EN 300 403-1 [2] relating to the following information elementsshall apply in a VPN context with the additions specified in the following subclauses:-Progress indicator;-Calling party number; and-Called party number.The following information elements are additional to those contained in subclause 3.1 of EN 300 403-1 [2]:-Connected number;-Connected subaddress;-Transit counter; and-VPN indicator.NOTE:The Notification indicator information element forms part of the basic call in a public network context.However, in a VPN context it forms part of the Generic Functional Protocol for the support ofsupplementary services.7.2.1Called party numberSubclause 4.5.8 of EN 300 403-1 [2] shall apply with the exception that table 4.9 of EN 300 403-1 [2] shall be replacedby the following table:SIST EN 301 060-1:2000
ETSIEN 301 060-1 V1.2.2 (1998-04)15Table 2: Called party numberNumbering plan identification (octet 3)Bits4
0Unknown (note 1)0
1ISDN/telephony numbering plan (Recommendation E.164)1
1Private numbering plan (ISO/IEC 11571)All other values are reserved.NOTE 1:The numbering plan "unknown" is used when the user or network has no knowledge of the numbering plan. Inthis case the number digits field is organized according to the network dialling plan, e.g. prefix or escapedigits might be present.Type of number (octet 3) when Numbering Plan identification is ISDN/telephony numbering plan (RecommendationE.164) (note 2).Bits7
0Unknown (note 3)0
1International number (note 4)0
0National number (note 4)1
0Subscriber number (note 4)All others values are reserved.NOTE 2:For the definition of international, national and subscriber number, see ITU-T Recommendation I.330 [10].NOTE 3:The type of number "unknown" is used when the user or the network has no knowledge of the type ofnumber, e.g. international number, national number, etc. In this case the number digits field is organizedaccording to the network dialling plan; e.g. prefix or escape digits might be present.NOTE 4:Prefix or escape digits shall not be included.Type of number (octet 3) when Numbering Plan identification is UnknownBits7
0Unknown (note 5)All others values are reserved.NOTE 5:The type of number "unknown" is used when the user or the network has no knowledge of the type ofnumber, e.g. international number, national number, etc. In this case the number digits field shall beorganized according to the network dialling plan; e.g. prefix or escape digits might be present.Type of number (octet 3) when Numbering Plan identification is Private numbering plan (note 6).Bits7
0Unknown (note 7)0
1Level 2 Regional Number0
0Level 1 Regional Number0
1PISN specific number1
0Level 0 Regional NumberAll others values are reserved.NOTE 6:For the definition of Level 2 Regional Number, Level 1 Regional Number, Level 0 Regional Number and PISNspecific number, see ISO/IEC 11571.NOTE 7:The type of number "unknown" is used when the user or the network has no knowledge of the type ofnumber, e.g. Level 1, Level 2, etc. In this case the number digits field is organized according to the networkdialling plan; e.g. prefix or escape digits might be present.Number digits (octets 4, etc.)This field is coded with IA5 characters, according to the formats specified in the appropriate numbering/dialling plan.SIST EN 301 060-1:2000
ETSIEN 301 060-1 V1.2.2 (1998-04)167.2.2Calling party numberSubclause 4.5.10 of EN 300 403-1 [2] shall apply with the exception that table 4.11 of EN 300 403-1 [2] is replaced bythe following table:Table 3: Calling party numberNumbering plan identification (octet 3)Bits4
0Unknown (note 1)0
1ISDN/telephony numbering plan (Recommendation E.164)1
1Private numbering plan (ISO/IEC 11571)All other values are reserved.NOTE 1:The numbering plan "unknown" is used when the user or network has no knowledge of the numbering plan. Inthis case the number digits field is organized according to the network dialling plan; e.g. prefix or escapedigits might be present.Type of number (octet 3) when Numbering Plan identification is ISDN/telephony numbering plan(Recommendation E.164) (note 2)Bits7
0Unknown (note 3)0
1International number (note 4)0
0National number (note 4)1
0Subscriber number (note 4)All others values are reserved.NOTE 2:For the definition of international, national and subscriber number, see Recommendation I.330 [10].NOTE 3:The type of number "unknown" shall be used when the user or the network has no knowledge of the type ofnumber, e.g. international number, national number, etc. In this case the number digits field is organizedaccording to the network dialling plan; e.g. prefix or escape digits might be present.NOTE 4:Prefix or escape digits shall not be included.Type of number (octet 3) when Numbering Plan identification is UnknownBits7
0Unknown (note 5)All others values are reserved.NOTE 5:The type of number "unknown" is used when the user or the network has no knowledge of the type ofnumber, e.g. international number, national number, etc. In this case the number digits field is organizedaccording to the network dialling plan; e.g. prefix or escape digits might be present.Type of number (octet 3) when Numbering Plan identification is Private numbering plan (note 6).Bits7
0Unknown (note 7)0
1Level 2 Regional Number0
0Level 1 Regional Number0
1PISN specific number1
0Level 0 Regional NumberAll others values are reserved.NOTE 6:For the definition of Level 2 Regional Number, Level 1 Regional Number, Level 0 Regional Number and PISNspecific number, see ISO/IEC 11571.NOTE 7:The type of number "unknown" is used when the user or the network has no knowledge of the type ofnumber, e.g. Level 1, Level 2, etc. In this case the number digits field is organized according to the networkdialling plan; e.g. prefix or escape digits might be present.(continued)SIST EN 301 060-1:2000
ETSIEN 301 060-1 V1.2.2 (1998-04)17Table 3 (concluded): Calling party numberPresentation indicator (octet 3a)Bits7
Meaning0
0 Presentation allowed0
1Presentation restricted1
0Number not available due to interworking1
1ReservedScreening indicator (octet 3a)Bits2
Meaning0
0 User-provided, not screened0
1User-provided, verified and passed1
0Reserved1
1Network providedNumber digits (octets 4, etc.)This field is coded with IA5 characters, according to the formats specified in the appropriate numbering/dialling plan.7.2.3Connected numberThe coding of the Connected number information element shall be as defined in ETS 300 097-1 [3] subclause 7.1 withthe exception that the content of this information element shall be coded as defined in subclause 7.2.2.7.2.4Connected subaddressThe coding of the Connected subaddress information element shall be as defined in ETS 300 097-1 [3] subclause 7.2.7.2.5Progress indicatorThe following additional progress description values shall be as defined in the ISO/IEC coding standardISO/IEC 11572 [7]:Bits765 4321
N°001 000016Interworking with a public network001 000117Interworking with a network unable to supply a release signal001 001018Interworking with a network unable to supply a release signal before answer001 001119Interworking with a network unable to supply a release signal after answerSIST EN 301 060-1:2000
ETSIEN 301 060-1 V1.2.2 (1998-04)187.2.6Transit counterThe Transit counter information element may be included in the SETUP message to indicate the number of privatenetwork transit exchanges which intervene in the requested connection. The coding of the Transit counter informationelement is defined in IS
...
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Basic call control; Enhancement at the b service entry point for Virtual Private Network (VPN) applications; Part 1: Protocol specification33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:EN 301 060-1 Version 1.2.2SIST EN 301 060-1:2000en01-december-2000SIST EN 301 060-1:2000SLOVENSKI
STANDARD
EN 301 060-1 V1.2.2 (1998-04)European Standard (Telecommunications series)Integrated Services Digital Network (ISDN);Digital Subscriber Signalling System No. one (DSS1) protocol;Basic call control;Enhancement at the "b" service entry point forVirtual Private Network (VPN) applications;Part 1: Protocol specificationSIST EN 301 060-1:2000
ETSIEN 301 060-1 V1.2.2 (1998-04)2ReferenceDEN/SPS-05109-1 (9tc90ipc.PDF)KeywordsBasic, DSS1, ISDN, VPN, ProtocolETSIPostal addressF-06921 Sophia Antipolis Cedex - FRANCEOffice address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00
Fax: +33 4 93 65 47 16Siret N° 348 623 562 00017 - NAF 742 CAssociation à but non lucratif enregistrée à laSous-Préfecture de Grasse (06) N° 7803/88Internetsecretariat@etsi.frhttp://www.etsi.frhttp://www.etsi.orgCopyright NotificationNo 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.SIST EN 301 060-1:2000
ETSIEN 301 060-1 V1.2.2 (1998-04)3ContentsIntellectual Property Rights.5Foreword.51Scope.62References.62.1Normative references.72.2Informative references.73Definitions.74Abbreviations.95Description.95.1VPN services in the context of CN.95.2Networking aspects - requirements.115.2.1Emulation of Transit PINX functionality and Gateway PINX functionality in the public network.115.2.1.1Support of multiple CNs.125.2.2Emulation of Originating and/or Terminating PINX functionality in the public network.125.2.3Provision of Relay Node functionality in the public network.125.2.4Connection requirements.126Operational requirements.137Coding requirements.137.1Additional messages and content.137.1.1SETUP message.137.1.2CONNECT message.147.2Additional information elements coding.147.2.1Called party number.147.2.2Calling party number.167.2.3Connected number.177.2.4Connected subaddress.177.2.5Progress indicator.177.2.6Transit counter.187.2.7VPN indicator.188Basic call states.199Circuit-switched call control procedures.199.1Distinction between public network and VPN context.199.2Procedures applicable for signalling in a public network context.199.3Procedures applicable for signalling in a VPN context.209.3.1Establishment of calls from a physical PINX.209.3.1.1Call request.209.3.1.2Call confirmation.219.3.2Establishment of calls towards a physical PINX.219.3.2.1Incoming call.219.3.2.2Call confirmation.229.3.3Notification of interworking and provision of in-band information.229.3.3.1Actions at a preceding PINX.229.3.3.2Actions at a subsequent PINX.2310System parameters.24Annex A (informative):Networking aspects - CN models.25A.1Representation of a CN in terms of functional groupings.25A.1.1Connections between PINXs.25A.1.2Structured overview of the functional groupings which may be involved in a call.26A.1.3Transit networking service provided by the public network.27SIST EN 301 060-1:2000
ETSIEN 301 060-1 V1.2.2 (1998-04)4A.1.4Transit and terminating functions provided by the public network.27History.29SIST EN 301 060-1:2000
ETSIEN 301 060-1 V1.2.2 (1998-04)5Intellectual Property RightsIPRs essential or potentially essential to the present document may have been declared to ETSI. The informationpertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be foundin ETR 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect ofETSI standards", which is available free of charge from the ETSI Secretariat. Latest updates are available on the ETSIWeb 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 ETSI. Noguarantee can be given as to the existence of other IPRs not referenced in ETR 314 (or the updates on the ETSI Webserver) which are, or may be, or may become, essential to the present document.ForewordThis European Standard (Telecommunications series) has been produced by ETSI Technical Committee SignallingProtocols and Switching (SPS).The present document defines the Digital Subscriber Signalling System No. one (DSS1) extensions to the basic call tosupport the Private Signalling System No. one (PSS1) information flow (see ISO/IEC 11572 [7]) in Virtual PrivateNetwork (VPN) applications. The relevant requirements and other information that affect DSS1 are defined in thepresent document.The present document is part 1 of a multi-part European Standard (Telecommunications series) covering the IntegratedServices Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Basic callapplications: enhancement at the "b" service entry point for Virtual Private Network (VPN) applications, as identifiedbelow:Part 1:"Protocol specification";Part 2:"PICS proforma specification";Part 3:"Test Suite Structure and Test Purposes (TSS&TP), user";Part 4:"Abstract Test Suite (ATS), user";Part 5:"Test Suite Structure and Test Purposes (TSS&TP), network";Part 6:"Abstract Test Suite (ATS), network".National transposition datesDate of adoption of this EN:3 April 1998Date of latest announcement of this EN (doa):31 July 1998Date of latest publication of new National Standardor endorsement of this EN (dop/e):31 January 1999Date of withdrawal of any conflicting National Standard (dow):31 January 1999SIST EN 301 060-1:2000
ETSIEN 301 060-1 V1.2.2 (1998-04)61ScopeThe present document specifies the extensions of the protocol for basic call control for the pan-European IntegratedServices Digital Network (ISDN). These extensions are applicable at the "b" service entry point (as defined in clause 5of the present document). It is part of the Digital Subscriber Signalling System No. One (DSS1) protocol. The presentdocument contains only additional requirements to those in the main body of ETS 300 403-1 [2].The present document is applicable only to point-to-point access configurations.The present document specifies additional protocol elements and call control procedures for the handling of callsbetween users in a Corporate telecommunication Network (CN) at the "b" service entry point. The functionalityprovided by the public network may be:-the emulation of an Originating Private Integrates services Network Exchange (PINX);-the emulation of a Terminating PINX;-the emulation of a Transit PINX;-the emulation of a Relay Node;-the emulation of an Incoming Gateway PINX;-the emulation of an Outgoing Gateway PINX;-the emulation of a combination of two or more of the above.The support of these capabilities is a network option.The present document does not cover the requirements for support of the "a" service entry point.The specification included in the present document does not imply any specific implementation technology or platform.NOTE:Calls/connections relating to the "b" service entry point are distinguished from calls that are accessing thepublic network at the T reference point. Calls relating to the T reference point are supported in accordancewith the requirements of EN 300 403-1 [2]. Calls relating to the "b" service entry point are supported inaccordance with the requirements of the present document. The requirements have been defined such thatboth contexts can coexist on the same access, and this is expected to be a typical implementation. There isno requirement that when the provisions of the present document are implemented, calls at the T referencepoint also need to be implemented on the same access. Where both contexts are implemented, the accessresources are common to both contexts.2ReferencesReferences may be made to:a)specific versions of publications (identified by date of publication, edition number, version number, etc.), inwhich case, subsequent revisions to the referenced document do not apply; orb)all versions up to and including the identified version (identified by "up to and including" before the versionidentity); orc)all versions subsequent to and including the identified version (identified by "onwards" following the versionidentity); ord)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 samenumber.SIST EN 301 060-1:2000
ETSIEN 301 060-1 V1.2.2 (1998-04)72.1 Normative references[1] ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces - reference configurations".[2] EN 300 403-1: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling SystemNo. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control; Part 1:Protocol specification".[3] ETS 300 097-1: "Integrated Services Digital Network (ISDN); Connected Line IdentificationPresentation (COLP) supplementary service; Digital Subscriber Signalling System No. one (DSS1)protocol; Part 1: Protocol specification".[4] ITU-T Recommendation I.210 (1993): "Principles of telecommunication services supported by anISDN and the means to describe them".[5] ITU-T Recommendation I.112 (1993): "Vocabulary of terms for ISDNs".[6] ISO/IEC 11571 (1994): "Information technology -- Telecommunications and information exchangebetween systems -- Numbering and sub-addressing in private integrated services networks".[7] ISO/IEC 11572 (1996), plus Amendment 1 (1996) and Amendment 2 (1996): "Informationtechnology - Telecommunications and information exchange between systems - Private IntegratedServices Network - Circuit mode bearer services - Inter-exchange signalling procedures andprotocol".[8] ISO/IEC 11579-1 (1994): "Information technology -- Telecommunications and informationexchange between systems -- Private integrated services network -- Part 1: Reference configurationfor PISN Exchanges (PINX)".[9] ISO/IEC 15056 (1997): "Information technology - Telecommunications and information exchangebetween systems - Private Integrated Services Network - Inter-exchange signalling protocol -Transit counter additional network feature".2.2 Informative references[10] ITU-T Recommendation I.330: "ISDN numbering and addressing principles".[11] ETR 172 (1995): "Business TeleCommunications (BTC); Virtual PrivateNetworking (VPN); Services and networking aspects; Standardization requirements and workitems".3 DefinitionsFor the purposes of the present document, the following definitions apply:Corporate telecommunication Network (CN): Consists of sets of equipment (Customer Premises Equipment (CPE)and/or Customer Premises Network (CPN)) which are located at geographically dispersed locations and areinterconnected to provide networking services 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.g. a single PINX orCentrex-provided services to users at a single location) may form a CN.end PINX functionality: Within the context of a call the functionality of a PINX required to provide attachment andservicing of terminals.gateway PINX functionality: Within the context of a call the functionality of a PINX required to interconnect EndPINXs or Transit PINXs with nodes of other public or private networks.incoming Gateway PINX functionality: Gateway PINX functionality providing support of calls incoming to the CN.SIST EN 301 060-1:2000
ETSIEN 301 060-1 V1.2.2 (1998-04)8integrated Services Digital Network (ISDN): See ITU-T Recommendation I.112 [5], definition 308.originating PINX functionality: End PINX functionality providing support of the calling user.outgoing Gateway PINX functionality: Gateway PINX functionality providing support of calls from the CN to othernetworks.preceding PINX: In the context of a call, an entity with PINX functionality located in the direction towards theoriginating interface. A preceding PINX may be functionality provided by a physical PINX or may be an emulation ofPINX functionality by the public network.Private Integrated services Network eXchange (PINX): A PISN nodal entity that provides automatic switching andcall handling functions used for the provision of telecommunication services. The nodal entity can be implemented byone or more pieces of equipment located on the premises of the private network administrator or by equipment co-located with, or physically part of, a public network.NOTE 3:If applicable, a PINX provides to users of the same and/or other private integrated services networkexchanges:-telecommunication services within its own area; and/or-telecommunication services from the public ISDN; and/or-telecommunication services from other public or private networks; and/or-within the context of a PISN, telecommunication services from other PINXs.Relay Node functionality: Within the context of a call the functionality that identifies calls between users in the CN,and relays such calls to designated PINX functionality emulated by the public network, or to a designated terminating"b" service entry point. This may be via other Relay Nodes. Relay Node functionality includes transparent handling ofprivate networking information (e.g. transit counter).service; telecommunications service: See ITU-T Recommendation I.112 [5], definition 201.subsequent PINX: In the context of a call, an entity with PINX functionality located in the direction towards thedestination interface. A subsequent PINX may be functionality provided by a physical PINX or may be an emulation ofPINX functionality by the public network.supplementary service: See ITU-T Recommendation I.210 [4], subclause 2.4.terminating PINX functionality: End PINX functionality providing support of the called user.transit PINX functionality: Within the context of a call the functionality of a PINX required to interconnect EndPINXs and/or other Transit PINXs and/or Gateway PINXs.Virtual Private Network (VPN): That part of a CN that provides corporate networking using shared switched networkinfrastructures. This is split into VPN architecture and VPN services.The VPN architecture is that part of a CN that provides corporate networking between customer equipment where:-the shared switch network infrastructure takes the place of the traditional analogue or digital leased lines and thefunction of the transit node, irrespective of the network type, whether it be the Public Switched TelephoneNetwork (PSTN), ISDN, mobile communication network, or a separate network;-the customer premises may be served in terms of end node functionality with any combination of PBX, Centrex,Local Area Network (LAN) router, or multiplexer;-the CN user may also be served by terminal equipment connected to end node functionality residing on customerpremises, or provided by public network equipment; and-the VPN architecture in one network, or multiple networks, comprises a part of the total national or internationalCN.VPN services offered by the switched network infrastructure provide:-VPN end-user services to CN users;-VPN networking services to support the interconnection of PINXs;SIST EN 301 060-1:2000
ETSIEN 301 060-1 V1.2.2 (1998-04)9-service interworking functionality;-inter-VPN services to provide co-operation between the VPN services of two networks; and-VPN management services to enable service subscribers to control and manage their VPN resources andcapabilities.4AbbreviationsFor the purposes of the present document, the following abbreviations apply:ANF-TCAdditional Network Feature - Transit CounterBCDBinary Coded DigitCLIPCalling Line Identification Presentation supplementary serviceCLIRCalling Line Identification Restriction supplementary serviceCNCorporate telecommunication NetworkCOLPCOnnected Line identification Presentation supplementary serviceCOLRCOnnected Line identification Restriction supplementary serviceCPECustomer Premises EquipmentCPNCustomer Premises NetworkDSS1Digital Subscriber Signalling System No. oneIA5International Alphabet No. fiveIVNInterVening NetworkISDNIntegrated Services Digital NetworkLANLocal Area NetworkPBXPrivate Branch eXchangePINXPrivate Integrated services Network eXchangePISNPrivate Integrated Services NetworkPSS1Private Signalling System No. onePSTNPublic Switched Telephone NetworkSUBSUBaddressing supplementary serviceTETerminal EquipmentVPNVirtual Private Network5DescriptionThe present document specifies the extensions required to the basic call control signalling protocol defined inEN 300 403-1 [2] to support calls within a Corporate telecommunication Network (CN) and to support calls which enteror exit the CN via Gateway Private Integrated services Network eXchange (PINX) functionality performed by the publicnetwork. The protocol is applicable at the T reference points to which VPN services are provided. The support of theseadditional signalling capabilities is a network option. These Digital Subscriber Signalling System No. one (DSS1)extensions shall be made available to PINXs, on the basis of bilateral agreements at subscription time.The additional basic call signalling capabilities identified in the present document are to provide information flows thatare functionally identical to the information flows provided by the Private Signalling System No. 1 (PSS1) basic callcontrol protocol (as defined by ISO/IEC 11572 [7]). In the context of the present document, the public network(providing VPN services) can be seen, from the private network perspective, as providing an interconnection between aPINX supporting the present document and another PINX supporting PSS1 information flows. This second PINX maybe a physical PINX connected to the public network or may be an emulation of an End PINX functionality provided bythe public network.5.1VPN services in the context of CNThe support of virtual private networking has been developed using the concept of "service entry points". This enablesVPN services to be described without the need to identify impacts on particular protocols. Whilst the present documentonly relates to the "b" service entry point and to PINX type 2, the other service entry points are included forcompleteness. Items that are covered by the present document are specifically identified in the text.SIST EN 301 060-1:2000
ETSIEN 301 060-1 V1.2.2 (1998-04)10Annex A provides more information on CN models.In order to identify VPN services and the points where these services are offered (service entry points) the CN overviewgiven in figure 1 has been produced. It reflects a CN overview in terms of services and service relations between:-CPE/CPN;-public networks;-VPN service providers; and-VPN service subscribers.The following PINX types are defined:PINX type 1:An implementation of a PINX outside the public network that supports services provided by thepublic ISDN and/or PSTN.PINX type 2:An implementation of a PINX outside the public network that supports services based on PISNstandards in addition to the services provided by the public ISDN and/or PSTN. The scope of thepresent document covers the support of PINX type 2.Referring to figure 1, VPN services can be subdivided into four classes depending on the service entry point at whichthey are offered:-VPN end-user services: services offered at the "a1", "a2" and "a3" service entry points;-VPN networking services: services offered at the "b" service entry point;-Inter-VPN services: services offered at the "c" service entry point; and-VPN management services: services offered at the "d" service entry point.PINXtype1or2PINXtype1or2PINXtype1or2CustomerPremises EquipmentPINXtype1CustomerPremises NetworkVPN Servicesby Network ANon-registeredVPN AccessPhysical/PublicNetwork AVPN Servicesby Network BNon-registeredVPN AccessPhysical/PublicNetwork BVPN ServiceProviderdVPN Management ServicesVPN Servicesubscribera3a3cbPINXtype2CustomerPremises EquipmentDedicatedVPN AccessesPINXtype1PINXtype2a1bbVPNend userservicesVPNend userservicesbba2RegisteredVPN AccessNOTE:a2 is a registered VPN access operating in the CN mode.Figure 1: VPN services in context of a CNThe following types of service entry points are identified:a1:The "a1" service entry point for an access (within a specific CN) which is dedicated to the utilization of VPNservices. This is referred to as "dedicated VPN access". At this service entry point, a pre-defined set of VPNend-user services is permanently available.SIST EN 301 060-1:2000
ETSIEN 301 060-1 V1.2.2 (1998-04)11a2:The "a2" service entry point for a public network access which is registered as able to utilize VPN serviceswithin a predetermined CN. This is referred to as "registered VPN access". At this service entry point, the usercan use either its pre-defined set of VPN end-user services, or the public network services.a3:The "a3" service entry point for a public network access which is not registered for the utilization of VPNservices. This is referred to as "non-registered VPN access". By means of an appropriate authenticationprocedure a pre-defined set of VPN end-user services becomes available to the CN user.b:The "b" service entry point for PINX type 2 and PINX type 1. At this service entry point VPN networkingservices are provided to PINX type 2 and PINX type 1 for the provision/support of services to its end-users. Thescope of the present document covers the "b" service entry point and the support of PINX type 2.c:The "c" service entry point for the provision of inter-VPN services between different VPN service providers. Atthis service entry point co-operation between VPN service providers enables VPN services to span multiplepublic networks.d:The "d" service entry point between the VPN service provider and the VPN service subscriber for the offering ofVPN management services. They allow the VPN service subscriber to manage resources and capabilities relatedto its CN.The "a1", "a2", and "a3" service entry points are subcategories of the "a" service entry point that provides VPN end-userservices.5.2Networking aspects - requirementsThe public network may provide one or more of the following capabilities:-the emulation of an Originating PINX;-the emulation of a Terminating PINX;-the emulation of a Transit PINX;-the emulation of a Relay Node;-the emulation of an Incoming Gateway PINX;-the emulation of an Outgoing Gateway PINX.5.2.1Emulation of Transit PINX functionality and Gateway PINXfunctionality in the public networkThis subclause addresses some requirements for the emulation of Transit PINX functionality, and for the emulation ofGateway PINX functionality, in the public network.For the emulation of Transit PINX functionality, the functions provided by the public network shall meet therequirements of Transit PINX Call Control as defined in ISO/IEC 11572 [7] for the circuit-switched call control and theISO supplementary services associated to the basic call (the Calling Line Identification Presentation supplementaryservice (CLIP), the Calling Line Identification Restriction supplementary service (CLIR), the COnnected Lineidentification Presentation supplementary service (COLP), the COnnected Line identification Restriction supplementaryservice (COLR), the SUBaddressing supplementary service (SUB)). In addition the transit counter additional networkfeature (ANF-TC) defined in ISO/IEC 15056 [9] may be supported by those extensions to the DSS1 protocol.For the emulation of Incoming Gateway PINX functionality, the functions provided by the public network shall meet therequirements of Incoming Gateway PINX call control as defined in ISO/IEC 11572 [7] for the circuit-switched callcontrol and the ISO supplementary services associated to the basic call (CLIP, CLIR, COLP, COLR, SUB). In additionANF-TC defined in ISO/IEC 15056 [9] may be supported by those extensions to the DSS1 protocol.For the emulation of Outgoing Gateway PINX functionality, the functions provided by the public network shall meet therequirements of Outgoing Gateway PINX call control as defined in ISO/IEC 11572 [7] for the circuit-switched callcontrol and the ISO supplementary services associated to the basic call (CLIP, CLIR, COLP, COLR, SUB). In additionANF-TC defined in ISO/IEC 15056 [9] may be supported by those extensions to the DSS1 protocol.SIST EN 301 060-1:2000
ETSIEN 301 060-1 V1.2.2 (1998-04)12In general, the requirements are common to both and any requirements applying specifically to one type of functionalityare indicated explicitly. Annex A contains a number of call examples to illustrate how the different functionality caninteract.NOTE:The requirements identified here need not be fulfilled in every switching element in the public network;these requirements need only be implemented at those switching elements in which CN functionality isneeded.The requirements for basic call functionality are identified in the following subclauses.5.2.1.1Support of multiple CNsThe public network can support the co-existence of multiple CNs in parallel, i.e. the resources of the public network areshared by multiple CNs. Each CN should be considered as a separate network.The facilities of the virtual transit PINX or virtual gateway PINX are shared between the different CNs. Thus, the virtualtransit PINX or virtual gateway PINX need to be able to provide differentiation between the calls belonging to thedifferent CNs.The minimum requirement of the virtual transit PINX and the virtual gateway PINX is to be able to uniquely identify theCN to which a particular attached PINX belongs in order to ensure correct routeing of a particular call. In addition, toensure that calls do not terminate on incorrect CNs, a mechanism may be required at the point where the call leaves thepublic network.In addition, a PINX may support multiple CNs. Thus the mechanism for identifying a CN needs to be conveyed betweena PINX and the public network.The capability of supporting multiple CNs is fulfilled by the VPN indicator information element defined in subclause7.2.7.5.2.2Emulation of Originating and/or Terminating PINX functionality in thepublic networkThis subclause identifies the requirements for the emulation of originating and/or Terminating PINX functionality in thepublic network. This is commonly known as Centrex.For the emulation of Originating PINX functionality, the functions provided by the public network shall meet therequirements of Originating PINX Call Control as defined in ISO/IEC 11572 [7] for the circuit-switched call control andthe ISO supplementary services associated with the basic call (CLIP, CLIR, COLP, COLR, SUB). In addition ANF-TCdefined in ISO/IEC 15056 [9] may be supported by those extensions to the DSS1 protocol.For the emulation of Terminating PINX functionality, the functions provided by the public network shall meet therequirements of Terminating PINX Call Control as defined in ISO/IEC 11572 [7] for the circuit-switched call controland the ISO supplementary services associated to the basic call (CLIP, CLIR, COLP, COLR, SUB). In addition ANF-TC defined in ISO/IEC 15056 [9] may be supported by those extensions to the DSS1 protocol.The requirements identified here are not required in every switching element in the public network.5.2.3Provision of Relay Node functionality in the public networkFor Relay Node functionality, the public network shall provide:-minimal routeing capability; and-transparent handling of private networking information (e.g. transit counter).5.2.4Connection requirementsFour types of network connections can be identified:-connection to a PINX;SIST EN 301 060-1:2000
ETSIEN 301 060-1 V1.2.2 (1998-04)13-connection through the CN (e.g. supported by the Relay Node functionality);-access from a digital terminal (outside the scope of the present document); and-access from an analogue terminal (outside the scope of the present document).For connection to a PINX, the interface here is the same as that between two PINXs.6Operational requirementsThe provision of the capabilities described in the present document may require a prior arrangement between theoperator of the physical PINX and the public network infrastructure.The public network infrastructure shall be able to associate one CN with the access, and may as an option be able toassociate multiple CNs with the access.As an option, the operator of the public network infrastructure may offer the VPN service with the subscription optionshown in table 1. This option shall apply per access.Table 1OptionValuesDefault CNNominated CN, or none designated7Coding requirementsThe coding requirements in this clause apply to the VPN context. The coding requirements applicable to the publicnetwork context are outside the scope of the present document.NOTE 1:The coding of messages and information elements relating to the restart procedures in EN 300 403-1 [2]apply regardless of the context, i.e. they are common to both the public network context and the VPNcontext.NOTE 2:The
coding of messages and information elements relating to the segmentation and reassemblyprocedures in EN 300 403-1 [2] apply regardless of the context, i.e. they are common to both the publicnetwork context and the VPN context.7.1Additional messages and contentThe coding requirements contained in subclause 3.1 of EN 300 403-1 [2] relating to the ALERTING,CALL PROCEEDING, CONNECT ACKNOWLEDGE, PROGRESS, SETUP ACKNOWLEDGE, DISCONNECT,RELEASE, RELEASE COMPLETE, INFORMATION, STATUS and STATUS ENQUIRY messages shall applyunchanged in a VPN context.The coding requirements contained in subclause 3.1 of EN 300 403-1 [2] relating to the CONNECT and SETUPmessages shall apply in a VPN context with the additions specified in the following subclauses.NOTE:The NOTIFY message forms part of the basic call in a public network context. However, in a VPNcontext it forms part of the Generic Functional Protocol for the support of supplementary services.7.1.1SETUP messageThe VPN indicator information element may be included in the SETUP message in both the user-network and thenetwork-user directions.Inclusion of this information element is mandatory to indicate a VPN context.SIST EN 301 060-1:2000
ETSIEN 301 060-1 V1.2.2 (1998-04)14The Called party number information element is mandatory in both the user-network and the network-user directions.The Transit counter information element may be included in the SETUP message, for use in both user-to-network andnetwork-to-user directions.7.1.2CONNECT messageThe Connected number information element and the Connected subaddress information element may be included in theCONNECT message for use in both the user-network and the network-user directions.7.2Additional information elements codingThe coding requirements contained in subclause 3.1 of EN 300 403-1 [2] relating to the following information elementsshall apply unchanged in a VPN context:-Locking shift;-Non-locking shift;-Sending complete;-Bearer capability;-Cause;-Call state;-Channel identification;-Calling party subaddress;-Called party subaddress;-Low layer compatibility; and-High layer compatibility.The coding requirements contained in subclause 3.1 of EN 300 403-1 [2] relating to the following information elementsshall apply in a VPN context with the additions specified in the following subclauses:-Progress indicator;-Calling party number; and-Called party number.The following information elements are additional to those contained in subclause 3.1 of EN 300 403-1 [2]:-Connected number;-Connected subaddress;-Transit counter; and-VPN indicator.NOTE:The Notification indicator information element forms part of the basic call in a public network context.However, in a VPN context it forms part of the Generic Functional Protocol for the support ofsupplementary services.7.2.1Called party numberSubclause 4.5.8 of EN 300 403-1 [2] shall apply with the exception that table 4.9 of EN 300 403-1 [2] shall be replacedby the following table:SIST EN 301 060-1:2000
ETSIEN 301 060-1 V1.2.2 (1998-04)15Table 2: Called party numberNumbering plan identification (octet 3)Bits4
0Unknown (note 1)0
1ISDN/telephony numbering plan (Recommendation E.164)1
1Private numbering plan (ISO/IEC 11571)All other values are reserved.NOTE 1:The numbering plan "unknown" is used when the user or network has no knowledge of the numbering plan. Inthis case the number digits field is organized according to the network dialling plan, e.g. prefix or escapedigits might be present.Type of number (octet 3) when Numbering Plan identification is ISDN/telephony numbering plan (RecommendationE.164) (note 2).Bits7
0Unknown (note 3)0
1International number (note 4)0
0National number (note 4)1
0Subscriber number (note 4)All others values are reserved.NOTE 2:For the definition of international, national and subscriber number, see ITU-T Recommendation I.330 [10].NOTE 3:The type of number "unknown" is used when the user or the network has no knowledge of the type ofnumber, e.g. international number, national number, etc. In this case the number digits field is organizedaccording to the network dialling plan; e.g. prefix or escape digits might be present.NOTE 4:Prefix or escape digits shall not be included.Type of number (octet 3) when Numbering Plan identification is UnknownBits7
0Unknown (note 5)All others values are reserved.NOTE 5:The type of number "unknown" is used when the user or the network has no knowledge of the type ofnumber, e.g. international number, national number, etc. In this case the number digits field shall beorganized according to the network dialling plan; e.g. prefix or escape digits might be present.Type of number (octet 3) when Numbering Plan identification is Private numbering plan (note 6).Bits7
0Unknown (note 7)0
1Level 2 Regional Number0
0Level 1 Regional Number0
1PISN specific number1
0Level 0 Regional NumberAll others values are reserved.NOTE 6:For the definition of Level 2 Regional Number, Level 1 Regional Number, Level 0 Regional Number and PISNspecific number, see ISO/IEC 11571.NOTE 7:The type of number "unknown" is used when the user or the network has no knowledge of the type ofnumber, e.g. Level 1, Level 2, etc. In this case the number digits field is organized according to the networkdialling plan; e.g. prefix or escape digits might be present.Number digits (octets 4, etc.)This field is coded with IA5 characters, according to the formats specified in the appropriate numbering/dialling plan.SIST EN 301 060-1:2000
ETSIEN 301 060-1 V1.2.2 (1998-04)167.2.2Calling party numberSubclause 4.5.10 of EN 300 403-1 [2] shall apply with the exception that table 4.11 of EN 300 403-1 [2] is replaced bythe following table:Table 3: Calling party numberNumbering plan identification (octet 3)Bits4
0Unknown (note 1)0
1ISDN/telephony numbering plan (Recommendation E.164)1
1Private numbering plan (ISO/IEC 11571)All other values are reserved.NOTE 1:The numbering plan "unknown" is used when the user or network has no knowledge of the numbering plan. Inthis case the number digits field is organized according to the network dialling plan; e.g. prefix or escapedigits might be present.Type of number (octet 3) when Numbering Plan identification is ISDN/telephony numbering plan(Recommendation E.164) (note 2)Bits7
0Unknown (note 3)0
1International number (note 4)0
0National number (note 4)1
0Subscriber number (note 4)All others values are reserved.NOTE 2:For the definition of international, national and subscriber number, see Recommendation I.330 [10].NOTE 3:The type of number "unknown" shall be used when the user or the network has no knowledge of the type ofnumber, e.g. international number, national number, etc. In this case the number digits field is organizedaccording to the network dialling plan; e.g. prefix or escape digits might be present.NOTE 4:Prefix or escape digits shall not be included.Type of number (octet 3) when Numbering Plan identification is UnknownBits7
0Unknown (note 5)All others values are reserved.NOTE 5:The type of number "unknown" is used when the user or the network has no knowledge of the type ofnumber, e.g. international number, national number, etc. In this case the number digits field is organizedaccording to the network dialling plan; e.g. prefix or escape digits might be present.Type of number (octet 3) when Numbering Plan identification is Private numbering plan (note 6).Bits7
0Unknown (note 7)0
1Level 2 Regional Number0
0Level 1 Regional Number0
1PISN specific number1
0Level 0 Regional NumberAll others values are reserved.NOTE 6:For the definition of Level 2 Regional Number, Level 1 Regional Number, Level 0 Regional Number and PISNspecific number, see ISO/IEC 11571.NOTE 7:The type of number "unknown" is used when the user or the network has no knowledge of the type ofnumber, e.g. Level 1, Level 2, etc. In this case the number digits field is organized according to the networkdialling plan; e.g. prefix or escape digits might be present.(continued)SIST EN 301 060-1:2000
ETSIEN 301 060-1 V1.2.2 (1998-04)17Table 3 (concluded): Calling party numberPresentation indicator (octet 3a)Bits7
Meaning0
0 Presentation allowed0
1Presentation restricted1
0Number not available due to interworking1
1ReservedScreening indicator (octet 3a)Bits2
Meaning0
0 User-provided, not screened0
1User-provided, verified and passed1
0Reserved1
1Network providedNumber digits (octets 4, etc.)This field is coded with IA5 characters, according to the formats specified in the appropriate numbering/dialling plan.7.2.3Connected numberThe coding of the Connected number information element shall be as defined in ETS 300 097-1 [3] subclause 7.1 withthe exception that the content of this information element shall be coded as defined in subclause 7.2.2.7.2.4Connected subaddressThe coding of the Connected subaddress information element shall be as defined in ETS 300 097-1 [3] subclause 7.2.7.2.5Progress indicatorThe following additional progress description values shall be as defined in the ISO/IEC coding standardISO/IEC 11572 [7]:Bits765 4321
N°001 000016Interworking with a public network001 000117Interworking with a network unable to supply a release signal001 001018Interworking with a network unable to supply a release signal before answer001 001119Interworking with a network unable to supply a release signal after answerSIST EN 301 060-1:2000
ETSIEN 301 060-1 V1.2.2 (1998-04)187.2.6Transit counterThe Transit counter information element may be included in the SETUP message to indicate the number of privatenetwork transit exchanges which intervene in the requested connection. The coding of the Transit counter informationelement
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...