Fill and Sign the Commercial Lease Contract Triple Net This Lease is Form

S tandard ECMA-253 2nd Edition - September 2000 Standardizing Information and Communication Systems Private Integrated Services Network (PISN) Mapping Functions for the Employment of 64 kbit/s Circuit Mode Connections with 16 kbit/s Sub-Multiplexing Phone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http://www.ecma.ch - Internet: helpdesk@ecma.ch . S tandard ECMA-253 2nd Edition - September 2000 Standardizing Information and Communication Systems Private Integrated Services Network (PISN) Mapping Functions for the Employment of 64 kbit/s Circuit Mode Connections with 16 kbit/s Sub-Multiplexing (Mapping/16) Phone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http://www.ecma.ch - Internet: helpdesk@ecma.ch IW ECMA-253.DOC 06-09-00 09,22 . Brief History This Standard is one of a series of standards defining mapping functions in exchanges of Private Integrated Services Networks. The series uses the ISDN concepts as developed by ITU-T (formerly CCITT) and is also within the framework of standards for open systems interconnection as defined by ISO/IEC. This Standard specifies mapping functions for the type of scenario where two PINXs are interconnected via a 64 kbit/s circuit mode connection with 16 kbit/s sub-multiplexing. This Standard is based upon the practical experience of ECMA member companies and the results of their active and continuous participation in the work of ISO/IEC JTC1, ITU-T, ETSI and other international and national standardization bodies. It represents a pragmatic and widely based consensus. Compared to the 1st Edition of Standard ECMA-253 (published by ECMA in December 1996), this 2nd Edition incorporates changes to achieve complete alignment with International Standard ISO/IEC 17310:2000(E) published by ISO/IEC in September 2000. Adopted as 2nd Edition of Standard ECMA-253 by the General Assembly in September 2000. - i - Table of contents 1 Scope 1 2 Conformance 1 3 References (normative) 1 4 Definitions 4 . 1 E x te r n a l d e f in itio n s 4.2 Special definitions 4.2.1 Ch a n n e l 4.2.2 End PINX 4.2.3 I n te r - P I N X Co n n e c tio n 4.2.4 I n te r - P I N X L in k 4.2.5 T r a n s it P I N X 2 2 2 2 2 2 2 2 5 Abbreviations 2 6 Introduction 2 7 Capabilities at the Q reference point 3 8 Mapping functions 8 . 1 P h ys ic a l a d a p ta tio n 8.1.1 6 4 k b i t / s U n r e s t r i c t e d D ig i t a l L e a s e d L i n e ( D 6 4 U ) 8 . 2 Ma p p in g Ma tr ix 8.2.1 Ch a n n e l a llo c a tio n 8.2.2 Be a r e r Co n d itio n in g f o r th e D Q - c h a n n e l 8.2.3 Be a r e r Co n d itio n in g f o r th e U Q - c h a n n e ls Annex A - Implementation Conformance Statement (ICS) Proforma 3 3 4 4 4 4 4 7 Annex B - Bibliography 11 Annex C - QSIG Protocol Codepoints 13 Annex D - Example figure for Bearer Conditioning of UQ-channels 15 1 Scope This Standard defines the mapping functions in exchanges of Private Integrated Services Networks (PISNs) required for the utilization of scenarios in which 64 kbit/s circuit mode connections are sub-multiplexed into 4 x 16 kbit/s channels for carrying inter-PINX signalling and user information. NOTE 1 This Standard has been prepared to meet the specific needs of an application for a particular user organisation. However, it may also be applicable elsewhere. The requirements contained in this Standard will be incorporated in any future standard specifying a more generic approach to bearer conditioning. In order to connect a Private Integrated Services Network Exchange (PINX) to another PINX, mapping functions are required to adapt the specific interfaces at the C reference point to the application at the Q reference point. As such, mapping functions provide for physical adaptation to the interface at the C reference point. Mapping functions also provide for the mapping of user channels and signalling information at the Q reference point to the appropriate channels or timeslots at the C reference point. The C and Q reference points are defined in ECMA-133. The type of interface at the C reference point covered by this Standard is the 64 kbit/s Unrestricted Digital Leased Line (D64U) Terminal Equipment Interface, in accordance with ITU-T Rec. G.703. At the Q reference point the mapping provides a 16 kbit/s service for user channels to support the transfer of unrestricted digital information and to support the transfer of speech, and a packet mode service for the signalling channel. The applied mapping is a static mapping, i.e. there is a fixed relationship between user and signalling channels at the Q reference point and the interface at the C reference point. Management functions relating to failure management are outside the scope of this Standard. This Standard is applicable to PINXs that can be interconnected to form a Private Integrated Services Network (PISN) and that support signalling protocols at the Q reference point. 2 Conformance In order to conform to this Standard, a PINX shall satisfy the requirements identified in the Implementation Conformance Statement (ICS) proforma in annex A. 3 References (normative) The following standards contain provisions which, through reference in this text, constitute provision of this Standard. All standards are subject to revision, and parties to agreements based on this Standard are encouraged to investigate the possibility of applying the most recent editions of the standards indicated below. In the case of references to ECMA Standards that are aligned with ISO/IEC International Standards, the number of the appropriate ISO/IEC International Standard is given in brackets after the ECMA reference. ECMA-133 Private Integrated Services Network (PISN) - Reference Configuration for PISN Exchanges (PINX) (International Standard ISO/IEC 11579-1) ITU-T Rec. G.703 Physical/electrical characteristics of hierarchical digital interfaces (1998) ITU-T Rec. I.112 Vocabulary of terms for ISDNs (1993) ITU-T Rec. I.460 Multiplexing, rate adaption and support of existing interfaces (1999) ITU-T Rec. Q.920 Digital Subscriber Signalling System No. 1 (DSS1) - ISDN user-network interface data link layer - General aspects (1993) ITU-T Rec. Q.920 Am. 1 Amendment 1 to ITU-T Recommendation Q.920 (2000) ITU-T Rec. Q.921 ISDN user-network interface - Data link layer specification (1997) ITU-T Rec. Q.921 Am. 1 Amendment 1 to ITU-T Recommendation Q.921 (2000) - 2 - NOTE 2 This Standard also contains informative references. Details of these publications are given in annex B. 4 Definitions 4.1 External definitions For the purpose of this Standard the following external definitions shall apply. 4.2 – Integrated Services Digital Network (ITU-T Rec. I.112) – Private Integrated Services Network (ECMA-133) – Private Integrated Services Network Exchange (ECMA-133) Special definitions 4.2.1 5 Channel A means of bi-directional transmission of user or signalling information between two points. 4.2.1.1 DQ-Channel A channel used to convey call control information between the Q reference points of two peer PINXs. 4.2.1.2 UQ-Channel A channel used to convey user information between the Q reference points of two PINXs. 4.2.2 En d P I N X In the context of a particular call, a PINX to which one of the users is attached (Originating PINX or Terminating PINX) or a PINX at which signalling interworking occurs (Gateway PINX). 4.2.3 Inter-PINX Connection A connection provided by an IVN between two C reference points used to transport inter-PINX information from the PISN control plane and/or the PISN user plane. 4.2.4 I n t e r - P I N X Lin k A link between the Q reference points of two PINXs, comprising the totality of signalling transfer and user information transfer means. 4.2.5 Tr a n s it P I N X In the context of a particular call, any PINX, excluding the End PINXs, through which the call passes. Abbreviations ICS Implementation Conformance Statement IPC Inter-PINX Connection IPL Inter-PINX Link ISDN Integrated Services Digital Network LD-CELP Low-Delay Code Excited Linear Prediction 6 MP MaPping functional grouping PINX Private Integrated Services Network Exchange PISN Private Integrated Services Network Introduction This Standard specifies mapping functions for the following scenario: − Dedicated 64 kbit/s circuit mode connection with 16 kbit/s sub-multiplexing. - 3 - This scenario consists of a dedicated 64 kbit/s circuit mode connection in a point-to-point configuration, and offering at the C reference point an interface with a single 64 kbit/s channel. This 64 kbit/s channel is sub-multiplexed by the Mapping (MP) functional grouping into 4 x 16 kbit/s channels. Where such a channel is used for carrying speech, a speech compression function is also provided. The applied mapping is a static mapping. There is a fixed relationship between user and signalling channels at the Q reference point and the interface at the C reference point. Administrative actions to apply the mapping are necessary at both sides of an IPL. At the C reference point more than one instance of the interface type may exist. NOTE 3 For more information refer to ECMA TR/76 clause 7. 7 Capabilities at the Q reference point For each instance of the Q reference point: − 3 user channels (U Q); and − 1 signalling channel (D Q) for carrying the inter-PINX layer 3 signalling protocol are provided. The user channels are numbered 1..3. For a U Q-channel the following bearer capabilities shall be provided: − information transfer rate: 16 kbit/s − information transfer capability: speech, or unrestricted digital information − user information layer 1 protocol: ITU-T Rec. G.728 16 kbit/s LD-CELP − Other attributes shall be the same as at the C reference point. NOTE 4 The user information layer 1 protocol is only specified as "LD-CELP" for the case where the information transfer capability is "speech". In the case where the information transfer capability is "unrestricted digital information", no user information layer 1 protocol is specified; it is an end-to-end matter between terminal equipments attached to a PISN. NOTE 5 Annex C (informative) specifies the codepoints to be used by the QSIG protocol when implementing the mapping arrangements specified in this Standard. For a D Q-channel the following bearer capability shall be provided: − Transfer mode: packet mode − Information transfer capability: unrestricted digital information − Information transfer rate: 16 kbit/s − Other attributes shall be the same as at the C reference point. The functions to map D Q and U Q channels to an inter-PINX connection (IPC) at the C reference point are described in clause 8. 8 Mapping functions The PINX mapping functions shall meet the following requirements. 8.1 Physical adaptation A PINX shall support the following physical adaptation: - 4 - 8.1.1 6 4 k b it /s U n r e s t r ic t e d D ig it a l Le a s e d Lin e ( D 6 4 U ) Layer 1 termination shall be in accordance with the requirements of co-directional interfaces at 64 kbit/s, specified in ITU-T Rec. G.703. NOTE 6 ETS 300 290 provides additional information about this interface type. At the C reference point, the interface described in this clause provides for one IPC with the following bearer capability: – Information transfer mode: circuit mode – Information transfer capability: unrestricted digital information – Information transfer rate: 64 kbit/s. The physical adaptation part of the mapping function shall maintain a fixed relationship between a 64 kbit/s IPC and the 16 kbit/s channels perceived at the Q reference point, according to the requirements for fixed format multiplexing specified in ITU-T Rec. I.460 (§ 2.1.1). NOTE 7 ITU-T Rec. I.460 assumes bit positions in the 64 kbit/s octet are numbered from 1 to 8 with bit position 1 being the first transmitted. According to CCITT Rec. G.711, bit position 1 corresponds to the most significant bit of the octet in an A-law PCM bitstream. By extrapolation, this convention is also true for an LD-CELP bitstream encoded according to ITU-T Rec. G.728. For signalling information (e.g., HDLC at layer 2, QSIG at layer 3) bit 1 corresponds to the least significant bit in the octet. These conventions are maintained by this Standard. Each 64 kbit/s IPC shall be sub-multiplexed into 4 16 kbit/s channels. Each 16 kbit/s channel shall be mapped to a pair of bit positions in the 64 kbit/s IPC as follows: – The first 16 kbit/s channel shall be mapped to bit positions 1 and 2; – The second 16 kbit/s channel shall be mapped to bit positions 3 and 4; – The third 16 kbit/s channel shall be mapped to bit positions 5 and 6; and, – The fourth 16 kbit/s channel shall be mapped to bit positions 7 and 8. 8.2 Mapping Matrix The mapping matrix provides for the bearer conditioning and mapping of channels at the Q reference point to the channels provided by the physical adaptation function. 8.2.1 C h a n n e l a llo c a t io n A PINX shall support the mapping of a single instance of the Q reference point on to a single interface at the C reference point. Each channel at the Q reference point shall be mapped to a 16 kbit/s channel in the 64 kbit/s interface at the C reference point as follows: – The D Q-channel shall be mapped to the first 16 kbit/s channel; – U Q-channel number 1 shall be mapped to the second 16 kbit/s channel; – U Q-channel number 2 shall be mapped to the third 16 kbit/s channel; and, – U Q-channel number 3 shall be mapped to the fourth 16 kbit/s channel. 8.2.2 Be a r e r C o n d i t i o n i n g f o r t h e D Q - c h a n n e l The signalling carriage mechanism connection (layer 2) on a DQ-channel shall be according to the symmetrical application in annex A of ITU-T Rec. Q.920 and annex J of ITU-T Rec. Q.921. The SM / SREJ option, defined in annex E of ITU-T Rec. Q.921, shall not apply. At installation time one of the sides of the D Q-channel shall be designated as 'master' and the other side of the D Q -channel as 'slave'. 8.2.3 Be a r e r C o n d i t i o n i n g f o r t h e U Q - c h a n n e l s No bearer conditioning of the U Q-channels is necessary. - 5 - NOTE 8 Annex D gives an example for the arrangement of functional groupings. NOTE 9 A PINX may need to rate-adapt incoming user information to its internal channel rate to permit internal switching and processing. For those calls in which it is acting as a Transit PINX, a PINX shall: – map U Q-channels at the Outgoing side into the outgoing 64 kbit/s IPC as specified in 8.2.1 above; – neither decompress received user information nor re-compress transmitted user information. - 6 - - 7 - Annex A ( n o r ma tiv e ) Implementation Conformance Statement (ICS) Proforma A.1 Introduction The supplier of a protocol implementation which is claimed to conform to this Standard shall complete the Implementation Conformance Statement (ICS) proforma in A.3. A completed ICS proforma is the ICS for the implementation in question. The ICS is a statement of which capabilities and options have been implemented. The ICS can have a number of uses, including use: A.2 - by the equipment implementer, as a check list to reduce the risk of failure to conform to the Standard through oversight; - by the supplier and acquirer, or potential acquirer, of the implementation, as a detailed indication of the capabilities of the implementation, stated relative to the common basis for understanding provided by the Standard's ICS proforma; - by the user or potential user of an implementation, as a basis for initially checking the possibility of interworking with another implementation. While interworking can never be guaranteed, failure to interwork can often be predicted from incompatible ICSs. Instructions for completing the ICS proforma A.2.1 General structure of the ICS proforma The ICS proforma is a fixed-format questionnaire divided into subclauses each containing a group of individual items. Each item is identified by an item number, the name of the item (question to be answered), and the reference(s) to the clause(s) that specifies (specify) the item in the main body of this Standard. The "Status" column indicates whether an item is applicable and if so whether support is mandatory or optional. The following terms are used: m mandatory (the capability is required for conformance); o optional (the capability is not required for conformance, but if the capability is implemented it is required to conform to the specifications); o. optional, but support of at least one of the group of options labelled by the same numeral is required; x prohibited; c. conditional requirement, depending on support for the item or items listed in condition ; :m simple conditional requirement, the capability being mandatory if item number is supported, otherwise not applicable; :o simple conditional requirement, the capability being optional if item number is supported, otherwise not applicable; Answers to the questionnaire items are to be provided either in the "Support" column, by simply marking an answer to indicate restricted choice (Yes) or (No), or in the "Not Applicable" column (N/A). - 8 - A.2.2 Additional information Items of Additional Information allow a supplier to provide further information intended to assist the interpretation of the ICS. It is not intended that a large quantity will be supplied, and an ICS can be considered complete without such information. Examples might be an outline of the ways in which a (single) implementation can be set up to operate in a variety of environments and configurations. References to items of Additional Information may be entered next to any answer in the questionnaire, and may be included in items of Exception Information. A.2.3 Exception information It may occasionally happen that a supplier will wish to answer an item with mandatory or prohibited status (after any conditions have been applied) in a way that conflicts with the indicated requirement. No preprinted answer will be found in the Support column for this. Instead, the supplier is required to write into the Support column an x. reference to an item of Exception Information, and to provide the appropriate rationale in the Exception item itself. An implementation for which an Exception item is required in this way does not conform to this Standard. A possible reason for the situation described above is that a defect in the Standard has been reported, a correction for which is expected to change the requirement not met by the implementation. - 9 - A.3 ICS proforma for PINX implementation A.3.1 Implementation identification Supplier Contact point for queries about the ICS Implementation name(s) and version(s) Other information necessary for full identification, e.g. name(s) and version(s) for machines and/or operating systems; system name(s) Only the first three items are required for all implementations; other information may be completed as appropriate in meeting requirements for full identification. The terms name and version should be interpreted appropriately to correspond with a supplier’s terminology (e.g. type, series, model). A.3.2 Implementation summary Implementation version 1.0 Addenda implemented (if applicable) Amendments implemented Have any exception items been required (see A.2.3)? Date of statement No [ ] Yes [ ] (The answer Yes means that the implementation does not conform to this Standard) - 10 - A.3.3 General Item Name of Item Reference Status N/A Support A1 Support of 64 kbit/s unrestricted digital leased line (D64U) interface with 16 kbit/s sub-multiplexing 8.1.1 m Yes [ ] A2 Support of prescribed channel allocation 8.2.1 m Yes [ ] A3 Support of bearer conditioning for the D Q-channel 8.2.2 m Yes [ ] A4 Support of bearer conditioning for the U Q-channel 8.2.3 m Yes [ ] - 11 - Annex B ( in f o r ma tiv e ) Bibliography ECMA TR/76 (1999) Private Integrated Services Network (PISN) - Architecture and Scenarios for Private Integrated Services Networking ETS 300 290 (1994) Business TeleCommunications (BTC); 64 kbit/s digital unrestricted leased line with octet integrity (D64U); Terminal equipment interface CCITT Rec. G.711 (1988) Pulse code modulation (PCM) of voice frequencies ITU-T Rec. G.728 (1992) Coding of speech at 16 kbit/s using low-delay code excited linear prediction - 12 - - 13 - Annex C ( in f o r ma tiv e ) QSIG Protocol Codepoints This Standard defines the mapping functions for the following bearer capabilities at the Q reference point: 1) 2) Speech: − information transfer rate: 16 kbit/s − information transfer capability: speech − user information layer 1 protocol: ITU-T Rec. G.728 16 kbit/s LD-CELP Unrestricted digital: − information transfer rate: 16 kbit/s − information transfer capability: unrestricted digital information. Support of these bearer capabilities by a PINX requires the use of additional, ISO / IEC defined, codepoints in the Bearer capability information element of the QSIG protocol, as follows: Octet & field Codepoint Meaning Octet 3 - Coding standard: 01 ISO / IEC Standard Octet 4 - Information transfer rate: 10010 16 kbit/s Octet 5 - User information layer 1 protocol: 01010 G.728 LD-CELP - 14 - - 15 - Annex D ( in f o r ma tiv e ) Example figure for Bearer Conditioning of U Q -channels SW MP Q Q C 16 kbit/s, LD-CELP MP Transit traffic BC 16 kbit/s, LD-CELP CELP codec S End traffic Speech Terminal 64 kbit/s, LD-CELP 64 kbit/s, A-law PCM BC = Bearer Conditioning CC = Call Control functional group MP = MaPping functional group SW = SWitching functional group TE = Terminal Equipment CC Figure D.1 - Example for the arrangement of bearer conditioning and speech compression / decompression In this example the functionalities "analogue / digital convertor", "compression / decompression" and "multiplexing" are realized in the box entitled "codec" and are controlled by the Call Control (CC). There are other possibilities to implement them in which the Call Control is not involved. Free printed copies can be ordered from: ECMA 114 Rue du Rhône CH-1204 Geneva Switzerland Fax: Email: +41 22 849.60.01 documents@ecma.ch Files of this Standard can be freely downloaded from the ECMA web site (www.ecma.ch). This site gives full information on ECMA, ECMA activities, ECMA Standards and Technical Reports. ECMA 114 Rue du Rhône CH-1204 Geneva Switzerland See inside cover page for obtaining further soft or hard copies.