ECMA TR 76-1999 Private Integrated Services Network (PISN) - Architecture and Scenarios for Private Integrated Services Networking《专用综合业务网络(PISN) 专用综合业务网络用架构和情境》.pdf

《ECMA TR 76-1999 Private Integrated Services Network (PISN) - Architecture and Scenarios for Private Integrated Services Networking《专用综合业务网络(PISN) 专用综合业务网络用架构和情境》.pdf》由会员分享，可在线阅读，更多相关《ECMA TR 76-1999 Private Integrated Services Network (PISN) - Architecture and Scenarios for Private Integrated Services Networking《专用综合业务网络(PISN) 专用综合业务网络用架构和情境》.pdf（44页珍藏版）》请在麦多课文档分享上搜索。

1、ECMA Technical Report TR/76December 1999Standardizing Information and Communication SystemsPhone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http:/www.ecma.ch - Internet: helpdeskecma.chPrivate Integrated Services Network(PISN) - Architecture and Scenarios forPrivate Integrated Services Network

2、ing.ECMA Technical Report TR/76December 1999Standardizing Information and Communication SystemsPhone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http:/www.ecma.ch - Internet: helpdeskecma.chIW TR-076.DOC 12-04-01 14,18Private Integrated Services Network(PISN) - Architecture and Scenarios forPri

3、vate Integrated Services Networking.Brief HistoryThis Technical Report is fully aligned with ISO/IEC TR 14475 2nd edition to be published by ISO in 2001.This Technical Report has been adopted by the ECMA General Assembly of December 1999.List of corrected errata for ECMA TR/7621 March 2001SummaryFol

4、lowing is a summary of errors detected and corrected in Technical Report TR/76, Private Integrated ServicesNetwork (PISN) - Architecture and Scenarios for Private Integrated Services Networking.Clause 2 ReferencesThe following recommendations are mentioned in the Technical Report but are missing in

5、the References clause:ITU-T Rec. I.430 Basic user-network interface - Layer 1 specification (1995)ITU-T Rec. X.31 Support of packet mode terminal equipment by an ISDN (1995)Clause 3.2.5 Interconnecting Network (ICN)The word “PTNX“ should be replaced by “PINX“.Corrected:3.2.5 Interconnecting Network

6、(ICN)The emulation of transit-PINX functionality by equipment that is physically part of the public network infrastructure.In addition, it includes one or more IVNs and may include the emulation of gateway-PINX functionality.Original:3.2.5 Interconnecting Network (ICN)The emulation of transit-PTNX f

7、unctionality by equipment that is physically part of the public network infrastructure.In addition, it includes one or more IVNs and may include the emulation of gateway-PTNX functionality.- i -Table of contents1Scope 12 References 13 Definitions 23.1 External Definitions 23.2 Special Definitions 23

8、.2.1 Attached PINX 23.2.2 Centrex 23.2.3 Channel 23.2.4 Corporate Telecommunication Network (CN) 33.2.5 Interconnecting Network (ICN) 33.2.6 Inter-PINX Connection (IPC) 33.2.7 Inter-PINX Link (IPL) 33.2.8 Relay Node (functionality) 33.2.9 Signalling Functions 33.2.10 ScenSIG 33.2.11 Scenario 43.2.12

9、 Semi-permanent connection 43.2.13 Virtual Private Network (VPN) 44 Symbols and Abbreviations 45 Introduction 55.1 PINX Reference Configuration 55.2 Additional Descriptions 65.2.1 Inter-PINX Connection (IPC) 65.2.2 Inter-PINX Link (IPL) 65.2.3 Relationship between IPLs and IPCs 76 Details of the Fun

10、ctional Groupings as Relevant for Scenario Handling 76.1 Mapping Unit (MP) 76.1.1 Physical Adaptation 86.1.2 Mapping Matrix 86.2 Inter-PINX Connection Control (ICC) 96.2.1 IPC Control 96.2.2 IPL Control 96.3 Scenario Management 96.3.1 Link Resource Management 106.3.2 Mapping Management 106.3.3 IPC M

11、anagement 106.4 Complete PINX Model 107 Configuration Variants 117.1 PINX with Multiple IPLs 11- ii -7.2 More than One Type of IVN 127.3 Different Spread of IPCs among the Interfaces at the Two PINXs 128 IPL Establishment and administration procedures 128.1 IPL Establishment using ScenSIG 138.1.1 St

12、atic Pre-Conditions 138.1.2 Establishment of a First IPC 138.1.3 IPL Initialisation Process 148.1.4 Establishment of the DQ-Channel 148.1.5 Establishment of UQ-Channels 158.1.6 Channel Mapping 158.2 IPL Establishment Procedures without using ScenSIG 158.3 IPL Administration Procedures 159 Items for

13、Future Standardisation 159.1 Mapping Function 169.1.1 Physical Adoption 169.1.2 Mapping Matrix 169.1.3 Static Pre-Conditions 169.2 ScenSIG 169.2.1 IPL Establishment and Administration Procedures 169.2.2 Bearer Modification Procedures 169.3 Bearer Conditioning 1610 Scenarios 1710.1 Scenarios: Dedicat

14、ed Transmission Systems 1710.1.1 Scenario 1.1 - Unstructured Transmission Link 1710.1.2 Scenario 1.2 - Structured Transmission Link 1710.2 Scenarios: Semi-Permanent IVN Connections 1810.2.1 Scenario 2.1 - Semi-permanent Circuit Switched 1810.2.2 Scenario 2.2 - Permanent Virtual Call 1810.3 Scenarios

15、: On-Demand Public Network Connections 1910.3.1 Scenario 3.1 - On-demand Circuit Switched 1910.3.2 Scenario 3.2 - ISDN Call with User-to-User Signalling 2010.3.3 Scenario 3.3 - On Demand Virtual Call 2010.4 Scenarios: Virtual Private Network 2110.4.1 Introduction 2110.4.2 Access Arrangements 2210.4.

16、3 Scenario 4.1 - Transit PINX 2510.4.4 Scenario 4.2 - Centrex 2510.4.5 Scenario 4.3 - Gateway to another network 25Annex A - Attribute Values 27Annex B - Scenario 4.4 - Relay Node 291ScopeA Private Integrated Service Network (PISN) is a network comprising either one PINX or more than one PINXinterco

17、nnected by Inter-PINX connections. This Technical Report is concerned with inter-PINX connections (IPC)that are provided by Intervening Networks (IVN), and the way in which these are handled by PINXs to provide aplatform for inter-PINX communication. Different types of IVNs can be used to provide IP

18、Cs, in accordance with thescenarios indicated in ISO/IEC 11579-1. These are Overlay Scenarios in that they enable the services of the PISN tooperate transparently across an IVN.Connected PINXs need to co-ordinate their use of IVNs, and appropriate standardisation is needed to allow networksto be cre

19、ated employing PINXs and IVNs from multiple vendors. The following points need to be considered:- In general but depending on the type of IVN, procedures and signalling protocols between the PINXs are neededfor the establishment, maintenance and release of IPCs. Appropriate standardisation of these

20、procedures andsignalling protocols is necessary.- At the Q-reference point (a conceptual point within a PINX) channels and PISN call control signalling (QSIG)are defined independently of the type of IVN. However, at the C-reference point (where the PINX is connected tothe IVN), the representation of

21、 the channels and of signalling is dependent on the type of IVN, and on how thePINXs use the IPCs. Appropriate standardisation of these aspects at the C reference point is necessary.- In general the relationship between a channel at the Q-reference point and its representation at the C-referencepoin

22、t is not static, and procedures and signalling between the PINXs are needed for the co-ordination of theserelationships. Appropriate standardisation of these procedures and signalling is necessary.- Appropriate mechanisms need to be standardised for conveying inter-PINX signalling through the IVN. T

23、hesewill depend on the characteristics of the IPC used.The aim of this Technical Report is to identify:1. In addition to PISN call control signalling (QSIG), what needs to be standardised, in order to be able to inter-connect PINXs;2. General techniques, procedures, protocols etc., that apply to of

24、all (or at least very many) types of IVNs.2 ReferencesECMA-142 Private Integrated Services Network (PISN) Circuit Mode 64kbit/s Bearer Services ServiceDescription, Functional Capabilities and Information Flows (International StandardISO/IEC 11574)ECMA-143 Private Integrated Services Network (PISN) -

25、 Circuit Mode Bearer Services - Inter-ExchangeSignalling Procedures and Protocol (International Standard ISO/IEC 11572)ECMA-165 Private Integrated Services Network (PISN) - Generic Functional Protocol for the Support ofSupplementary Services - Inter-Exchange Signalling Procedures and Protocol (Inter

26、nationalStandard ISO/IEC 11582)ISO/IEC 7776 Information technology - Telecommunications and information exchange between systems -High-level data link control procedures - Description of the X.25 LAPB - compatible DTE datalink procedures (1986)ISO/IEC 11579-1 Information technology - Telecommunicati

27、on and information exchange between systems -Private integrated service network - Part 1: Reference configuration for PISN Exchanges (PINX)(1994)ITU-T Rec. I.112 Vocabulary of terms for ISDN (Blue Book) (1993)CCITT Rec. I.I30 Method for the characterisation of telecommunication services supported by

28、 an ISDN, andnetwork capabilities of an ISDN (Blue Book) (1989)ITU-T Rec. I.140 Attribute technique for the characterisation of telecommunication services supported by an ISDN,and network capabilities of an ISDN (Blue Book) (1994)- 2 -ITU-T Rec. I.210 Principles of telecommunication services support

29、ed by an ISDN and means to describe them (BlueBook) (1993)ITU-T Rec. I.411 ISDN user-network interfaces - Reference configurations (Blue Book) (1993)ITU-T Rec. I.430 Basic user-network interface - Layer 1 specification (1995)ITU-T Rec. X.31 Support of packet mode terminal equipment by an ISDN (1995)

30、3 DefinitionsFor the purposes of this Technical Report the following definitions apply.3.1 External DefinitionsThis Technical Report uses the following terms defined in other documents:- Basic Service (ITU-T Rec. I.210)- Private Integrated Services Network (PISN) (ISO/IEC 11579-1)- Private Integrate

31、d Services Network Exchange (PINX) (ISO/IEC 11579-1)- Service (ITU-T Rec. I.112)- Signalling (ITU-T Rec. I.112)- Supplementary Service (ITU-T Rec. I.210)- Supplementary Service Control Entity (ECMA-165)- Terminating PINX (ECMA-143)- Transit PINX (ECMA-143)- User (ECMA-142)3.2 Special Definitions3.2.

32、1 Attached PINXA PINX that is attached to a VPN and capable of using VPN services.NOTEIn the context of a call, the attached PINX can be an end-PINX (i.e. serving the originating or destination useror acting as a gateway with another network) or it can be a transit-PINX.3.2.2 CentrexThat part of a V

33、PN that emulates an End-PINX.3.2.3 ChannelA means of bi-directional transmission of user or signalling information between two points.DC-ChannelA channel used to convey IPC control information, at the C reference point, between a PINX and an IVN.NOTEThis does not preclude the conveyance of other typ

34、es of information.DQ-ChannelA channel used to convey call control information between the Q reference points of two peer PINXs.NOTECall control information can include information for the control of basic services, supplementary services,additional network features, etc.- 3 -IPL-Service-Channel (IS-

35、Channel)A channel used to convey information related to the management of scenarios between the two peer PINXs.NOTEThis channel conveys ScenSIG. The use for other applications is outside the scope of this Technical Report.UQ-ChannelA channel used to convey user information between the Q reference po

36、ints of two PINXs.3.2.4 Corporate Telecommunication Network (CN)A CN consists of a set of equipment (Customer Premises Equipment and/or Customer Premises Network) thatare located at geographically dispersed locations and are interconnected to provide networking services to adefined group of users.NO

37、TEThe ownership of the equipment is not relevant to this definition.NOTEIn this Report, even equipment that is not geographically dispersed (e.g., a single PBX or a Centrex providingservice to users at a single location) may form a CN.3.2.5 Interconnecting Network (ICN)The emulation of transit-PINX

38、functionality by equipment that is physically part of the public networkinfrastructure. In addition, it includes one or more IVNs and may include the emulation of gateway-PINXfunctionality.3.2.6 Inter-PINX Connection (IPC)A connection provided by an IVN between two C reference points used to transpo

39、rt inter-PINX informationfrom the PISN control plane and/or the PISN user plane.3.2.7 Inter-PINX Link (IPL)A link between the Q reference points of two PINXs, comprising the totality of signalling transfer and userinformation transfer means.3.2.8 Relay Node (functionality)Within the context of a cal

40、l the functionality that distinguishes calls between users in the Corporate Network,and relays such calls to designated PINX functionality emulated by public network equipment, or to an attachedPINX. This may be via other relay nodes.NOTERelay Node functionality includes transparent handling of priv

41、ate networking information (e.g. transit counter).3.2.9 Signalling FunctionsCSIGThe generic term describing access signalling information flows (i.e. not a specific signalling protocol) betweena PINX and an IVN, at the C reference point.QSIGThe generic term describing the signalling information flow

42、s (i.e. not a specific signalling protocol), within aDQ-channel.TSIGThe generic term describing signalling information flows (i.e. not a specific signalling protocol) forinterworking between a PINX and the public ISDN (which occurs at the T reference point).3.2.10 ScenSIGThe generic term describing

43、the signalling information flows (i.e. not a specific signalling protocol) that supportthe handling of the specific scenario employed between the two interconnected PINXs.- 4 -3.2.11 ScenarioA particular type of IPC provided by a particular type of IVN.3.2.12 Semi-permanent connectionA connection in

44、 a switched network established by the network operator.3.2.13 Virtual Private Network (VPN)Is that part of a CN that provides corporate networking using shared switched resources from a third partyprovider (e.g. a public network).4 Symbols and AbbreviationsACP Availability Check ProcedureC C refere

45、nce pointCiInstance i of a C reference pointCh ChannelCC Call Control functional groupingCLIP Calling Line Identification PresentationCM Circuit ModeCOLP Connected Line Identification PresentationCSIG SIGnalling information flows at the C reference pointCUG Closed User GroupDDI Direct Dial InHLC Hig

46、h Layer CompatibilityICC Inter-PINX Connection (IPC) Control functional groupingId IdentityIFC InterFaCeIPC Inter-PINX ConnectionIPL Inter-PINX LinkIS IPL ServiceIVN InterVening NetworkLLC Low Layer CompatibilityMC Mapping ControlMP MaPping functional groupingNP Numbering PlanPSPDN Packet Switched P

47、ublic Data NetworkPISN Private Integrated Service NetworkPINX Private Integrated Network EXchangePM Packet ModeQ Q reference pointQiInstance i of a Q reference pointQSIG SIGnalling information flows at the Q reference point- 5 -ScenSIG Scenario SIGnalling information flowsSS #7 Signalling System No.

48、 7SW SWitching functional groupingT T reference pointTSIG SIGnalling information flows at the T reference point5 IntroductionSome general mapping functions are listed in the reference configuration for PINXs, defined in ISO/IEC 11579-1.Further definitions are required to understand the co-operation

49、of functions in a PINX, to derive from them a subsetwhich needs to be standardised.Subclause 5.1 provides an excerpt from those functions mentioned in ISO/IEC 11579-1, which are relevant to thisdocument. Subclause 5.2 and its subclauses describe refinements of these functions and some additions necessary forunderstanding the overall context.5.1 PINX Reference ConfigurationFigure 1 shows an excerpt from the PINX reference configuration as described in ISO/IEC 11579-1.99-0070-AIVNMappingpeer PINXICCScenario ManagementCCPINXQC CSwitchingFigure 1 - PINX Reference Configuration (Excerpt