.rs .\" Troff code generated by TPS Convert from ITU Original Files .\" Not Copyright ( c) 1991 .\" .\" Assumes tbl, eqn, MS macros, and lots of luck. .TA 1c 2c 3c 4c 5c 6c 7c 8c .ds CH .ds CF .EQ delim @@ .EN .nr LL 40.5P .nr ll 40.5P .nr HM 3P .nr FM 6P .nr PO 4P .nr PD 9p .po 4P .rs \v | 5i' .sp 1P .ce 1000 \v'12P' \s12PART\ I \v'4P' .RT .ce 0 .sp 1P .ce 1000 \fBRecommendations Q.500 to Q.554\fR \v'2P' .EF '% \ \ \ ^'' .OF ''' \ \ \ ^ %' .ce 0 .sp 1P .ce 1000 \fBDIGITAL\ LOCAL, COMBINED, TRANSIT\fR .ce 0 .ce 1000 \fBAND\ INTERNATIONAL\ EXCHANGES\ IN\ INTEGRATED\fR .ce 0 .sp 1P .ce 1000 \fBDIGITAL\ NETWORKS\ AND\ MIXED\ ANALOGUE\(hyDIGITAL\ NETWORKS\fR .ce 0 .sp 1P .LP .rs .sp 25P .ad r Blanc .ad b .RT .LP .bp .LP \fBMONTAGE PAGE 2 = PAGE BLANCHE\fR .sp 1P .RT .LP .bp .sp 1P .ce 1000 \v'3P' SECTION\ 1 .ce 0 .sp 1P .ce 1000 \fBINTRODUCTION\ AND\ FIELD\ OF\ APPLICATION\fR \v'1P' .ce 0 .sp 1P .sp 2P .LP \fBRecommendation\ Q.500\fR .RT .sp 2P .ce 1000 \fBDIGITAL\ LOCAL,\ COMBINED,\ TRANSIT\ AND\ INTERNATIONAL\ EXCHANGES\fR .EF '% Fascicle\ VI.5\ \(em\ Rec.\ Q.500'' .OF '''Fascicle\ VI.5\ \(em\ Rec.\ Q.500 %' .ce 0 .sp 1P .ce 1000 \fBINTRODUCTION\ AND\ FIELD\ OF\ APPLICATION\fR .ce 0 .sp 1P .sp 2P .LP \fB1\fR \fBIntroduction\fR .sp 1P .RT .PP This series of Recommendations Q.500\(hy554 applies to digital local, combined .FS A \*Qcombined\*U digital exchange is one which includes both local exchange and transit exchange functions (see definition\ 1005 in Recommendation\ Q.9). .FE , transit and international exchanges for telephony in Integrated Digital Networks (IDNs) and mixed analogue/digital networks, and also to local, combined, transit and international exchanges in an Integrated Services Digital Network (ISDN). .PP The series of Recommendations comprises: .RT .LP Q.500 Introduction and field of application .LP Q.511 Exchange interfaces towards other exchanges .LP Q.512 Exchange interfaces for subscriber access .LP Q.513 Exchange interfaces for operations, administration and maintenance .LP Q.521 Exchange functions .LP Q.522 Digital exchange connections, signalling and ancillary functions .LP Q.541 Design objectives \(em General .LP Q.542 Design objectives \(em Operations and Maintenance .LP Q.543 Performance design objectives .LP Q.544 Exchange measurements .LP Q.551 Transmission characteristics of digital exchanges .LP Q.552 Transmission characteristics at 2\(hywire analogue interfaces .LP Q.553 Transmission characteristics at 4\(hywire analogue interfaces .LP Q.554 Transmission characteristics at digital interfaces. .PP Considerations have been primarily on exchanges utilizing, at least in part, time division switching techniques. However, these Recommendations are implementation independent, and other system implementations using alternative techniques (e.g.,\ space division switching) may be possible, which would meet the requirements of these Recommendations. .LP .sp 1 .bp .sp 2P .LP \fB2\fR \fBField of application\fR .sp 1P .RT .PP These Recommendations are intended to be applied as indicated below. .RT .sp 1P .LP 2.1 \fIApplication and evolution to the ISDN\fR .sp 9p .RT .PP The selection of features, functions and interfaces to be provided in a digital local, combined, transit or international exchange in a particular network application will be determined by the administration concerned. Reference to a function in these Recommendations, including their diagrams, does not imply that it will necessarily be provided in every exchange type or configuration. Similarly, it is possible that some functions may be provided which are not mentioned. .RT .sp 1P .LP 2.2 \fIRelationship of design performance requirements to operational\fR \fIperformance requirements\fR .sp 9p .RT .PP Performance requirements as defined in this series of Recommendations should be considered as design objectives for systems under the conditions stated in the Recommendations. These conditions are defined by such parameters as average circuit occupancy, busy hour call attempts,\ etc. They should be distinguished from the operational performance requirements which administrations establish for exchanges operating in their particular environment. .PP Further clarification of this point can be obtained in Recommendation\ G.102. .RT .sp 2P .LP \fB3\fR \fBThe Q.500\(hySeries of Recommendations\fR .sp 1P .RT .sp 1P .LP 3.1 \fIExchange interfaces (Recommendations Q.511, Q.512 and Q.513)\fR .sp 9p .RT .PP The interface functions defined are those necessary for interworking with digital and analogue transmission systems on both circuits to other exchanges and on subscriber lines, and with telecommunications management networks. .RT .sp 1P .LP 3.1.1 \fICharacteristics of exchange interfaces towards other exchanges\fR \fI(Recommendation Q.511)\fR .sp 9p .RT .PP This Recommendation describes the exchange interfaces used to provide transmission facilities towards other exchanges. It applies to digital local, combined, transit and international exchanges for telephony in integrated digital networks (IDN) and mixed (analogue/digital) networks, and also to local, combined, transit and international exchanges in an integrated services digital network (ISDN). .RT .sp 1P .LP 3.1.2 \fICharacteristics of exchange interfaces for subscriber access\fR \fI(Recommendation\ Q.512)\fR .sp 9p .RT .PP The Recommendation describes the subscriber side interface characteristics. It applies to digital local and combined exchanges for telephony in Integrated Digital Networks (IDN) and mixed (analogue/digital) networks, and also to local and combined exchanges in an integrated digital network (ISDN). .RT .sp 1P .LP 3.1.3 \fIExchange interfaces for operations, administration and\fR \fImaintenance (Recommendation\ Q.513)\fR .sp 9p .RT .PP The interfaces defined are those necessary for transmission of messages associated with operations, administration and maintenance of the exchange. .PP These interfaces include OAM interfaces between the exchange and the following: OAM systems, mediation devices, user workstations, and other network elements. .RT .sp 1P .LP 3.1.4 \fIInterfaces to non\(hyvoice handling facilities\fR .sp 9p .RT .PP The need for the Recommendation of interfaces between digital transit, local and combined exchanges and non\(hyvoice handling facilities remains for further study. (An example of such a non\(hyvoice facility is a packet switched data node.) Attention is drawn to Recommendation\ X.300 which describes the general principles for interworking between public data networks and also to the I.400/I.500\(hySeries Recommendations for interworking between ISDN and other dedicated networks. .bp .RT .sp 1P .LP 3.2 \fIExchange functions (Recommendation Q.521)\fR .sp 9p .RT .PP This Recommendation covers the definition of the principal exchange functions to support services and includes a description of an exchange functional model. .RT .sp 1P .LP 3.3 \fIExchange connections, signalling and ancillary functions\fR \fI(Recommendation\ Q.522)\fR .sp 9p .RT .PP This Recommendation covers the following functions: .RT .LP a) \fIConnections through an exchange\fR .LP This section includes the switch block(s), the characteristics associated with connections through exchanges and a set of diagrams showing typical types of connection. .LP A connection through an exchange may include one or more stages of time and/or space division switching, providing a path for transmission through the exchange. .LP b) \fISignalling\fR .LP Signalling includes reception of call\(hyrelated and other information, interaction with the call control function and transfer of information to subscribers and network(s) as required. .LP Signalling may involve common channel and/or channel associated signalling. .LP c) \fIControl and call handling\fR .LP Control and call handling includes initiation, supervision and termination of most actions in the exchange. .LP Commands are initiated and information passed/received to/from the other functions within the exchange. .LP Control functions may be contained in one block or distributed throughout the exchange. .LP d) \fIAncillaries\fR .LP Examples of such functions are: .LP \(em recorded announcements; .LP \(em tone generation; .LP \(em conferencing facilities. .LP Their location is dependent on the function itself and the exchange configuration. .sp 2P .LP 3.4 \fIExchange design objectives (Recommendations Q.541, Q.542, Q.543\fR \fIand Q.544)\fR .sp 1P .RT .sp 1P .LP 3.4.1 \fIGeneral design objectives (Recommendation Q.541)\fR .sp 9p .RT .PP This includes the general design objective principles, availability and hardware design objectives as well as the design objectives associated with the operation of an exchange in an Integrated Digital Network. The latter encompasses timing and synchronization design objectives. .PP Timing comprises the generation and distribution of timing signals and includes timing of outgoing signals. It enables those parts of the exchange which form the switched path of a connection to operate synchronously. Synchronization will depend on the national synchronization plan and exchange timing arrangements. .PP Exchanges will usually extract synchronizing information from one or more incoming bit streams or a separate synchronization network and use this to adjust the timing signals generated in the distribution within the exchange. .RT .sp 1P .LP 3.4.2 \fIOperations and maintenance design objectives\fR \fI(Recommendation Q.542)\fR .sp 9p .RT .PP This covers the operations and maintenance design objectives including network management controls, alarm handling and subscriber line maintenance and testing. .bp .RT .sp 1P .LP 3.4.3 \fIPerformance design objectives (Recommendation Q.543)\fR .sp 9p .RT .PP Exchange performance design objectives are defined for guiding system design and for comparing the capabilities of different systems. (Recommendations relating to provisioning and operational performance of exchanges in the network are covered in the E.500\(hyE.543 Series.) .RT .sp 1P .LP 3.4.4 \fIExchange measurements (Recommendation Q.544)\fR .sp 9p .RT .PP Measurements that may be used for planning, operation, maintenance and network management of exchanges and their associated networks are described. The measurement data consists primarily of event counts and traffic intensity levels experienced by the various traffic handling elements of the exchange. .RT .sp 2P .LP 3.5 \fITransmission characteristics (Recommendations Q.551 to Q.554)\fR .sp 1P .RT .sp 1P .LP 3.5.1 \fITransmission characteristics of digital exchanges\fR \fI(Recommendation Q.551)\fR .sp 9p .RT .PP This includes the general definitions associated with Recommendations\ Q.551 to\ Q.554, and transmission parameters from a total exchange perspective such as absolute group delay and the transfer function for jitter and wander. These Recommendations define, for any connection which may be set up by a local, combined, transit or international exchange, the necessary levels of transmission performance to conform with overall objectives for the complete user\(hyto\(hyuser connections in which the exchange may be involved. .RT .sp 1P .LP 3.5.2 \fITransmission characteristics at 2\(hywire interfaces\fR \fI(Recommendation\ Q.552), 4\(hywire interfaces (Recommenda\fR \fItion\ Q.553)\fR \fIand digital interfaces (Recommendation Q.554)\fR .sp 9p .RT .PP These cover the detailed transmission characteristics of the various types of interface that may be provided on a digital exchange. .RT .LP .rs .sp 27P .ad r Blanc .ad b .RT .LP .bp .sp 1P .ce 1000 \v'3P' SECTION\ 2 .ce 0 .sp 1P .ce 1000 \fBEXCHANGE\ INTERFACES,\ FUNCTIONS\ AND\ CONNECTIONS\fR .ce 0 .sp 1P .LP \fR .sp 2P .LP \fBRecommendation\ Q.511\fR .RT .sp 2P .sp 1P .ce 1000 \fR \fBEXCHANGE\ INTERFACES\ TOWARDS\ OTHER\ EXCHANGES\fR .EF '% Fascicle\ VI.5\ \(em\ Rec.\ Q.511'' .OF '''Fascicle\ VI.5\ \(em\ Rec.\ Q.511 %' .ce 0 .sp 1P .sp 2P .LP \fB1\fR \fBGeneral\fR .sp 1P .RT .PP This Recommendation applies to digital local, combined, transit and international exchanges for telephony in Integrated Digital Networks (IDN) and mixed (analogue/digital) networks, and also to local, combined, transit and international exchanges in an Integrated Services Digital Network (ISDN). .PP The field of application of this Recommendation is more fully defined in Recommendation\ Q.500. .RT .sp 2P .LP \fB2\fR \fBScope of Recommendation\fR .sp 1P .RT .PP This Recommendation is not intended to define any systems or equipment in or connected to, a digital exchange via these interfaces. Therefore only the characteristics of the interfaces are described. .PP The exchange interfaces described in this Recommendation are used to connect these exchanges to transmission facilities towards other exchanges. .PP All interfaces that have been studied in detail are described, and illustrated in Figure\ 1/Q.511 but it is not intended to specify every interface. Other interfaces are for further study (e.g.,\ those for broadband facilities). .RT .LP \fB3\fR \fBCharacteristics of digital interfaces towards other exchanges\fR .sp 1P .RT .sp 2P .LP 3.1 \fIInterface A\fR .sp 1P .RT .sp 1P .LP 3.1.1 \fIGeneral\fR .sp 9p .RT .PP Interface A is a digital interface to allow interconnection at the first level of a digital transmission hierarchy towards other exchanges. .RT .sp 1P .LP 3.1.2 \fIElectrical characteristics\fR .sp 9p .RT .PP The electrical characteristics of interface A are described in Recommendation\ G.703. .PP The frame structure at interface A should be identical to that of the first order multiplexes described in Recommendations\ G.704 and\ G.705. .PP Timing in the transmitting direction will be derived within the digital exchange. .bp .RT .LP .rs .sp 47P .ad r \fBFigure 1/Q.511, p.1\fR .sp 1P .RT .ad b .RT .LP .bp .sp 1P .LP 3.1.3 \fIChannel types, channel allocation and signalling\fR : \v'3p' .sp 9p .RT .LP \(em number of channel timeslots per frame: 32B/F24, numbered 0\(hy31B/F1\(hy24; .LP \(em additional channel timeslots may be utilized for common channel signalling when more signalling capacity is required between exchanges. For 2048\ kbitB/Fs systems, they should be selected from the channel timeslots allocated in PCM multiplexes for data purposes according to Recommendation\ G.735. When no such channel timeslots are allocated or available, additional channel timeslots may be selected from channel timeslots allocated for voice channels. .PP For 2048 kbit/s systems: .LP \(em channel timeslot 16 is primarily intended for signalling but should be switchable. On systems between exchanges (not involving PCM primary muldex) when channel 16 is not assigned to carry signalling it may be allocated to speech or other srvices; .LP \(em channel timeslot 0 is used for frame alignment, alarm indication, network synchronization and other purposes; .LP \(em although no specific application is at present foreseen for switching timeslot\ 0, it is recommended that the possibility of read and write access to this timeslot should be retained as a safeguard for future requirements. Such access would allow processing of some or all of the information contained in this timeslot, in particular those bits reserved for national and international use. The need to switch channel timeslot\ 0 as a normal channel, without special access, requires further study. In any case the incoming frame alignment signal will not be passed through the exchange to an outgoing system. .sp 1P .LP 3.1.4 \fIFunctional characteristics\fR .sp 9p .RT .PP The use of the Cyclic Redundancy Check (CRC) procedures described in Recommendation\ G.704 is recommended for interfaces which carry ISDN traffic and optional for other applications. The frame alignment, CRC multiframe alignment and CRC monitoring functions are in accordance with Recommendation\ G.706. .RT .sp 2P .LP 3.2 \fIInterface B\fR .sp 1P .RT .sp 1P .LP 3.2.1 \fIGeneral\fR .sp 9p .RT .PP Interface B is a digital interface to allow interconnection at the second level of a digital transmission hierarchy towards other exchanges. .RT .sp 1P .LP 3.2.2 \fIElectrical characteristics\fR .sp 9p .RT .PP The electrical characteristics of interface B are described in Recommendation\ G.703. .PP The frame structure at interface B should be identical to that of the second order multiplexes described in Recommendations\ G.704 and G.705. .PP Timing in the transmitting direction will be derived within the digital exchange. .RT .sp 1P .LP 3.2.3 \fIChannel types, channel allocation and signalling\fR : \v'3p' .sp 9p .RT .LP \(em number of channels: 132/98 numbered 0\(hy131/1\(hy98. .PP For 8448 kbit/s systems: .LP \(em where signalling capacity is required between exchanges, timeslots\ 67, 68, 69 and 70 can be utilized for signalling in this order of descending priority. Those channels not used for signalling can be used for speech or other purposes. If a channel timeslot is reserved for service purposes within the switch, it shall be channel timeslot\ 1; .LP \(em it is left for mutual agreement whether or not channel timeslot\ 1 will carry traffic; .bp .LP \(em 128 of the channel timeslots may carry traffic through the exchange. .PP For 6312 kbit/s systems: .LP \(em the multiplex structure contains 5 bits and 98 channel timeslots, numbered\ 1\(hy98, each of 64\ kbit/s, of which 96 may carry traffic through the exchange; .LP \(em five bits per frame are assigned for a frame alignment signal and for other signals. Timeslots\ 97 and\ 98 are assigned to signalling between exchanges. .sp 1P .LP 3.2.4 \fIFunctional characteristics\fR .sp 9p .RT .PP The use of the Cyclic Redundancy Check (CRC) procedures described in Recommendation\ G.704, is recommended for interfaces which carry ISDN traffic and optional for other applications. The frame alignment, CRC multiframe alignment and CRC monitoring functions are in accordance with Recommendation\ G.706. .RT .LP \fB4\fR \fBCharacteristics of\fR \fBanalogue interfaces towards other\fR \fBexchanges\fR .sp 1P .RT .sp 2P .LP 4.1 \fIInterface C\fR .sp 1P .RT .sp 1P .LP 4.1.1 \fIGeneral\fR .sp 9p .RT .PP Interface C is a 2\(hywire or a 4\(hywire analogue interface, used where direct interconnection analogue facilities is required. This implies that a PCM codec, associated with this interface, is incorporated in the digital exchange. The equipment on the exchange side of interface\ C may include a muldex within the exchange termination functions. Differences in circuit configurations with respect to transmission parameters are likely to result in the need to specify a number of different C\ interfaces, depending on the application environment. This is likely to reduce the flexibility in interconnection possibilities. These C\ interfaces are specified in Recommendation\ Q.551. The transmission characteristics of 2\(hywire interface\ C2 are described in Recommendation\ Q.552 and of 4\(hywire interface\ C1 in Recommendation\ Q.553. .RT .sp 1P .LP 4.1.2 \fIChannel types, channel allocation and signalling\fR .sp 9p .RT .PP The signalling characteristics of interface C vary considerably from country to country, and therefore it is not intended that this interface should be the subject of CCITT Recommendations beyond those aspects covered in Recommendations\ Q.552 and\ Q.553. \v'1P' .RT .sp 2P .LP \fBRecommendation\ Q.512\fR .RT .sp 2P .sp 1P .ce 1000 \fBEXCHANGE\ INTERFACES\ FOR\ SUBSCRIBER\ ACCESS\fR .EF '% Fascicle\ VI.5\ \(em\ Rec.\ Q.512'' .OF '''Fascicle\ VI.5\ \(em\ Rec.\ Q.512 %' .ce 0 .sp 1P .sp 2P .LP \fR \fB1\fR \fBGeneral\fR .sp 1P .RT .PP This Recommendation applies to digital local and combined exchanges for telephony in Integrated Digital Networks (IDN) and mixed (analogue/digital) networks, and also to local and combined exchanges in Integrated Services Digital Networks (ISDN). The field of application of this Recommendation is more fully defined in Recommendation\ Q.500. .RT .sp 2P .LP \fB2\fR \fBScope of Recommendation\fR .sp 1P .RT .PP Exchange interfaces for subscriber access that have been considered are described, and illustrated in Figure\ 1/Q.512 and Table\ 1/Q.512, but it is not intended to specify every interface. Other interfaces are for further study (e.g.,\ those for dynamic multiplexed basic rate access, broadband access,\ etc.). .bp .RT .LP .rs .sp 47P .ad r \fBFigure 1/Q.512, p.2\fR .sp 1P .RT .ad b .RT .LP .bp .ce \fBH.T. [T1.512]\fR .ce TABLE\ 1/Q.512 .ce \fBInterface references\fR .ps 9 .vs 11 .nr VS 11 .nr PS 9 .TS center box; cw(48p) | cw(30p) | cw(24p) | cw(42p) | cw(36p) | cw(48p) . Access type Interface/reference points Paragraph Related physical Recs. Related OAM Recs. Application to connect _ .T& lw(48p) | cw(30p) | cw(24p) | cw(42p) | cw(36p) | lw(48p) . Basic access digital section V 1 3.2 (Note 1) G.960 (Note 1) I.603 ISDN basic access (2B\ +\ D) _ .T& lw(48p) | cw(30p) | cw(24p) | cw(42p) | lw(36p) | lw(48p) . Generic digital section V 2 3.3 None { Digital network equipment, supporting any combination of access types } _ .T& lw(48p) | cw(30p) | cw(24p) | cw(42p) | cw(36p) | lw(48p) . { Generic subscriber access (Note 2) digital section } V 3 3.4 G.703 G.704 G.705 G.706 I.604 (Note 3) Digital subscriber equipment _ .T& lw(48p) | cw(30p) | cw(24p) | cw(42p) | lw(36p) | lw(48p) . { Digital access link (Static multiplex) } V 4 3.5 G.706 I.605 { A multiple of ISDN basic accesses } _ .T& lw(48p) | cw(30p) | cw(24p) | cw(42p) | cw(36p) | lw(48p) . { Generic analogue subscriber access } Z 4.1 None (Note 4) None Analogue subscriber lines .TE .LP \fINote\ 1\fR \ \(em\ Recommendation G.961 specifies the characteristics of a digital transmission system on metallic local lines which may form part of the basic access digital selection. .LP \fINote\ 2\fR \ \(em\ In the case of ISDN access this is the primary rate access digital section. .LP \fINote\ 3\fR \ \(em\ Only in the case of ISDN application, G.706 and I.604 are recommended. .LP \fINote\ 4\fR \ \(em\ Characteristics other than those defined in Recommendations Q.551 to Q.554 are not subject of CCITT Recommendation. .nr PS 9 .RT .ad r \fBTable 1/Q.512 [T1.512], p.3\fR .sp 1P .RT .ad b .RT .PP .sp 5 This Recommendation is not intended to define any transmission system, network or subscriber equipment in or connected to, a digital exchange via these interfaces. Therefore only the characteristics of the interfaces are described. .PP Digital exchange interfaces for subscriber access are defined at the V\ reference point which is the boundary between the ET and the digital access section or link. These interfaces are designated interface\ V and are defined to allow flexibility of implementation for different exchange and transmission equipment realizations. However, a physical interface will not be specified for all subscriber access types identified (see Figure\ 1/Q.512). .PP In this Recommendation, a digital section is defined as the whole of the means of digital transmission of a digital signal of specified rate between two consecutive reference points. A digital link comprises one or more digital sections and may include either a multiplexer or concentrator, but not switching. .bp .RT .sp 2P .LP \fB3\fR \fBCharacteristics\fR \fBof digital exchange interfaces for\fR \fBsubscriber access\fR .sp 1P .RT .sp 1P .LP 3.1 \fIGeneral\fR .sp 9p .RT .PP As an objective, the characteristics of digital interfaces on the subscriber side of the exchange should be aligned with the characteristics of ISDN user/network access structures (Recommendation\ I.411). .PP However in many countries, digital access arrangements not structured according to ISDN principles are used, e.g.,\ to ensure compatibility with existing networks and services and it is expected that these arrangements will continue to be used for several years. Only certain characteristics of these arrangements are the subject of CCITT Recommendations. .RT .sp 2P .LP 3.2 \fIInterface V\fR\d\fI1\fR\u .sp 1P .RT .sp 1P .LP 3.2.1 \fIGeneral\fR .sp 9p .RT .PP Interface V\d1\umay be used at the V\d1\ureference point to connect to an ISDN basic access digital section for the provision of a single basic .PP access. The characteristics of the basic access digital section are defined in Recommendation\ G.960 and the characteristics and parameters of a digital transmission system which may form part of the digital section for the ISDN basic rate access are given in Recommendation\ G.961. .RT .sp 1P .LP 3.2.2 \fIFunctional characteristics\fR .sp 9p .RT .PP The functional description is illustrated in Figure\ 2/Q.512 and the following functional requirements are defined: \v'3p' .RT .LP 1) \fI(2B + D) channels\fR .LP To provide the bidirectional transmission capability for two B\ channels and one 16\ kbit/s D\ channel as described in Recommendation\ I.412. .LP 2) \fIBit timing\fR .LP To provide bit (signal element) timing to enable the digital section to recover information from the aggregate bit stream. .LP 3) \fIFrame timing\fR .LP To provide frame timing to enable digital section and ET to recover the time division multiplexed channels. .LP 4) \fICV\fI .EF '% \fI1\ channel'' .OF '''\fI1\ channel %' .LP The CV\d1\uchannel provides, for each direction of transmission, the capability to transfer management functions required for the digital section as specified in Recommendations\ G.960 and I.603. The CV\d1\uchannel may carry one or more functional links. These functions include activation from network side, activation from network side, activation request from a digital section, deactivation from ET side, operation and maintenance signals. .LP 5) \fIPower feed\fR .LP This function provides for remote power feeding for the digital section and possibly terminal equipment. This function is optional. .sp 1P .LP 3.2.3 \fIElectrical characteristics\fR .sp 9p .RT .PP The electrical characteristics of interface V\d1\uare not subject to CCITT Recommendations. .RT .sp 1P .LP 3.2.4 \fIChannel types, channel allocation and signalling\fR .sp 9p .RT .PP The channel types associated with interface V\d1\uinclude two B\ channels and one D\ channel as defined at the user network interface in Recommendation\ I.412. In addition, the CV\d1\u\ channel is required to support the operational and maintenance functions. .PP The channel allocation is not subject to CCITT Recommendations. .PP The D channel signalling procedures are defined in the Q.920 and Q.930\(hySeries Recommendations. .bp .RT .LP .rs .sp 31P .ad r \fBFigure 2/Q.512, p.\fR .sp 1P .RT .ad b .RT .sp 2P .LP 3.3 \fIInterface V\fR\d\fI2\fR\u .sp 1P .RT .sp 1P .LP 3.3.1 \fIGeneral\fR .sp 9p .RT .PP Interface V\d2\uis a generic digital interface used to connect remote or local digital network equipment via a first or second order digital section. This network equipment may support any combination of analogue, digital and ISDN subscriber access. The characteristics of this interface may not be structured according to the ISDN principles. .RT .sp 1P .LP 3.3.2 \fIFunctional characteristics\fR .sp 9p .RT .PP The functional characteristics depend on the specific application of the V\d2\u\ interface. These are not generally subject to CCITT Recommendations. .RT .sp 1P .LP 3.3.3 \fIElectrical characteristics\fR .sp 9p .RT .PP The electrical characteristics of interface V\d2\uare described in Recommendation\ G.703. .PP The basic frame structure at interface V\d2\ushould be identical to that of the first or second order rate multiplexes described in Recommendations\ G.704 and G.705. .RT .sp 1P .LP 3.3.4 \fIChannel types, channel allocation and signalling\fR .sp 9p .RT .PP The channel types, channel allocation and signalling depends on the specific application of the V\d2\u\ interface. These are not generally subject to CCITT Recommendations. .bp .RT .sp 2P .LP 3.4 \fIInterface V\fR\d\fI3\fR\u .sp 1P .RT .sp 1P .LP 3.4.1 \fIGeneral\fR .sp 9p .RT .PP Interface V\d3\uis a digital interface used to connect digital subscriber equipment (e.g.,\ PABX) via a generic digital subscriber section. The characteristics of this interface may not be structured according to the ISDN principles. In this case, only the electrical characteristics defined in \(sc\ 3.4.2 are recommended. However, in the case of ISDN where interface\ V\d3\uis used to connect a primary rate access digital section for the provision of a single primary rate access, all of the following characteristics apply. .RT .sp 1P .LP 3.4.2 \fIFunctional characteristics\fR .sp 9p .RT .PP The use of the Cyclic Redundancy Check (CRC) procedures described in Recommendations\ G.704 and G.706 is recommended. The information on the status of the CRC processing shall be passed across the V\d3\u\ interface. The maintenance procedures are defined in Recommendation\ I.604. .RT .sp 1P .LP 3.4.3 \fIElectrical characteristics\fR .sp 9p .RT .PP The electrical characteristics of interface V\d3\uare described in Recommendation\ G.703. .PP The frame structure at interface V\d3\ushould be identical to that described in Recommendations\ G.704 and\ G.705. .RT .sp 1P .LP 3.4.4 \fIChannel types, channel allocation and signalling\fR .sp 9p .RT .PP The channel types and allocation associated with interface V\d3\uare 30\ B\ +\ 1\ D at 2048\ kbit/s or 23\ B\ +\ 1 D at 1544\ kbit/s as described in Recommendation\ I.431. .PP The channel allocation should also consider that: .RT .LP a) when the signalling for the B channels in one primary rate structure is carried by the D\ channel in another primary rate structure, the channel timeslot normally used for signalling may be used to provide an additional B\ channel; .LP b) at interface V\d3\uthe designated number of B channels is always present within the multiplexed channel structure, but one or more of the B\ channels may not be used in any given application. .PP The D channel signalling procedures are defined in the Q.920 and Q.930\(hySeries Recommendations. .sp 2P .LP 3.5 \fIInterface V\fR\d\fI4\fR\u .sp 1P .RT .sp 1P .LP 3.5.1 \fIGeneral\fR .sp 9p .RT .PP Interface V\d4\uis a digital interface used to connect a digital access link which includes a static multiplexer supporting several basic access digital sections. The local digital multiplexer application is considered to be a subset of the remote digital multiplexer application. .RT .sp 1P .LP 3.5.2 \fIFunctional characteristics\fR .sp 9p .RT .PP The functional description is illustrated in Figure 3/Q.512 and the following functional requirements are defined: .RT .LP \(em m \(mu (2 B\ +\ D + CV\d1\u): to provide the bidirectional transmission capability for the B, and D, CV\d1\u\ channels from each basic rate access section. .LP \(em Timing: to provide the necessary timing information for bit transmission, frame synchronization and subscriber line synchronization. .LP \(em Operations and maintenance: to provide the transmission capability to carry the operation and maintenance signals of the digital link and the basic access muldex as defined in I.605. .bp .LP .rs .sp 18P .ad r \fBFigure 3/Q.512, p.\fR .sp 1P .RT .ad b .RT .PP The use of the Cyclic Redundancy Check (CRC) procedures described in Recommendations\ G.704 and G.706 are recommended. The information on the status of the CRC processing shall be passed across the V\d4\u\ interface. .sp 1P .LP 3.5.3 \fIElectrical characteristics\fR .sp 9p .RT .PP The electrical characteristics of interface V\d4\uare described in Recommendation\ G.703. .PP The basic frame structure at interface V\d4\ushould be identical to that of the first order multiplexes described in Recommendations\ G.704 and G.705. .RT .sp 2P .LP 3.5.4 \fIChannel types, channel allocation and signalling\fR .sp 1P .RT .sp 1P .LP 3.5.4.1 \fIGeneral\fR .sp 9p .RT .PP The V\d4\uinterface is composed of a number of individual ISDN basic rate access digital sections, as described in \(sc\ 3.2. .PP The channel allocation at interface V\d4\uis defined within a first order structure using a static multiplexing principle as follows: .RT .sp 2P .LP 3.5.4.2 \fIStatic multiplexed at 2048 kbit/s\fR .sp 1P .RT .sp 1P .LP 3.5.4.2.1 \fIChannel allocation\fR .sp 9p .RT .PP In this case 12 basic access channels are multiplexed in a static manner using fixed allocation of the channels. Figure\ 4/Q.512 illustrates the channel allocation for 2048\ kbit/s, where 24\ channel timeslots are used by B1 and B2\ channels and 6\ channel timeslots are used by the D and CV\d1\u\ channels of the 12\ basic accesses. .PP The CV\d1\uand D channels of two basic accesses are multiplexed into one channel timeslot. Five contiguous channel timeslots are occupied by two basic accesses each consisting of B1\ +\ B2\ +\ D\ +\ CV\d1\u\ channels. .PP Channel timeslot 0 is used for frame alignment including the application of CRC4 according to Recommendation\ G.704. Additionally, the alarm handling facilities of channel timeslot\ 0 are used for maintenance of the primary link as described in Recommendation\ I.605. .bp .PP According to the channel allocation shown in Figure 4/Q.512, the CV\d1\uchannels are located in timeslots\ 5, 10, 15, 21, 26 and 31. These represent 8\ bits, namely two bits for each of the D and CV\d1\u\ channels of two basic accesses. .RT .LP .sp 2 .rs .sp 44P .ad r \fBFigure 4/Q.512 [T2.512], p.\fR .sp 1P .RT .ad b .RT .LP .bp .sp 1P .LP 3.5.4.2.2 \fICV\fI .sp 9p .RT .EF '% \fI1\ channel\ structure'' .OF '''\fI1\ channel\ structure %' .PP To facilitate separate treatment of bundles of two basic accesses, represented by five 64\ kbit/s\ channels, multi\(hyframe alignment should be performed individually for each bundle. The relevant overhead information should be contained in the CV\d1\u\ channels. CV\d1\u\ channel structure is for further study. .PP The D channel signalling procedures are defined in the Q.920 and Q.930\(hySeries Recommendations. .RT .sp 1P .LP 3.5.4.3 \fIStatic multiplexed 1544 kbit/s\fR .sp 9p .RT .PP For further study. .RT .sp 2P .LP \fB4\fR \fBCharacteristics of\fR \fBanalogue exchange interface for\fR \fBsubscriber access\fR .sp 1P .RT .sp 1P .LP 4.1 \fIInterface Z\fR .sp 9p .RT .PP Interface Z is a generic analogue interface defined at the exchange side of an analogue subscriber line used to connect subscriber equipment (e.g.,\ single telephone set or PABX). .PP It is recognized that the characteristics of analogue interfaces (generally designated Z\ interface) vary considerably from country to country and therefore it is not intended that those interfaces be the subject of CCITT Recommendations beyond those aspects covered in Recommendations\ Q.551/552. .RT .sp 2P .LP \fB5\fR \fBCombined digital and analogue interface for subscriber access\fR .sp 1P .RT .PP In the evolution towards an ISDN, user network accesses may exist which have a combination of both analogue and digital interfaces. .PP This type of interface is not presently considered to be a matter for CCITT Recommendations. \v'1P' .RT .sp 2P .LP \fBRecommendation\ Q.513\fR .RT .sp 2P .ce 1000 \fBEXCHANGE\ INTERFACES\ FOR\ OPERATIONS,\fR .EF '% Fascicle\ VI.5\ \(em\ Rec.\ Q.513'' .OF '''Fascicle\ VI.5\ \(em\ Rec.\ Q.513 %' .ce 0 .sp 1P .ce 1000 \fBADMINISTRATION\ AND\ MAINTENANCE\fR .ce 0 .sp 1P .sp 2P .LP \fB1\fR \fBGeneral\fR .sp 1P .RT .PP This Recommendation applies to digital local, combined, transit and international exchanges for telephony in Integrated Digital Networks (IDN) and mixed (analogue/digital) networks, and also to local, combined, transit and international exchanges in an Integrated Services Digital Network (ISDN). .PP The field of application of this Recommendation is more fully defined in Recommendation\ Q.500. .PP This Recommendation is not intended to define any systems or equipment in or connected to, a digital exchange via these interfaces. Therefore only the interfaces characteristics are described. .PP In the text of this Recommendation, references are made to operation, administration and maintenance (OAM) equipment which comprises either or both of the following: .RT .LP a) operations systems (OS) which support personnel responsible for exchange OAM. Note that the word exchange includes both signalling and switching equipment; .LP b) human\(hymachine terminals which provide access to exchanges or operations systems. .bp .sp 2P .LP \fB2\fR \fBGeneral characteristics of the\fR \fBinterfaces to\fR \fBOAM equipment\fR .sp 1P .RT .PP \fR 2.1 Interfaces are provided for the transfer of information between exchanges and locations where OAM functions are performed. Items\ a) and\ b) below illustrate examples of information that may cross the interface and which may need to be catered for. (The choice of information that crosses the interface is a matter for each Administration/RPOA.) .sp 9p .RT .LP a) The information transferred from the exchange to OAM equipment may include customer usage and charging data, exchange system status indication, system resource utilization data, system performance measurements, alarms and messages alerting operating personnel to the current state of the exchange and other data. .LP b) The information transferred to the exchange from the OAM equipment may include commands for system initializations and configuration control, data to effect changes in system operation, commands to initiate, terminate, or otherwise modify the services provided to customers, requests for status information and other commands. .PP 2.2 An exchange may have access to one or more OAM equipment. .PP 2.3 Access may be provided using separate data links, multiplexed data links, or one or more data networks to each OAM equipment. .PP 2.4 The exchange shall not become unavailable due to the failure or malfunction of OAM equipment, or the failure of links between the exchange and OAM equipment. .PP 2.5 The choice between single and multiple physical links at the exchange, and the configuration of the OAM equipment is a national matter, not subject to CCITT Recommendations. .sp 2P .LP \fB3\fR \fBFunctional characteristics of the interface to OAM equipment\fR .sp 1P .RT .PP 3.1 The exchange should not depend for its basic operation on the correct functioning of the OAM equipment. .sp 9p .RT .PP 3.2 The interface should provide basic initialization, error detection and automatic recovery procedures for the data link. .PP 3.3 The interface should support data transport mechanisms that may be employed by the exchange and the OAM equipment to assure the reliable transfer of particular information (e.g.,\ charging data). .PP 3.4 The interface should support the setting of priorities by the exchange or OAM equipment for the use of the transmission medium (data links). .PP 3.5 The interface should support priority transfer of urgent messages. .sp 2P .LP \fB4\fR \fBExchange OAM interfaces\fR .sp 1P .RT .PP Exchange OAM interfaces are shown in Figure 1/Q.513. .PP There are two general classes of OAM interfaces: .RT .LP a) human\(hymachine interfaces; .LP b) interfaces to OAM OSs and workstations. .PP The interfaces for local and remote human\(hymachine functions should conform to the MML Z.300\(hySeries of Recommendations. .PP It is planned to provide Recommendations which specify interfaces between exchanges and operations systems and between exchanges and workstations. Such specifications will be based on the concept of the Telecommunications Management Network (TMN). The principles and architecture of the TMN are defined in Recommendation\ M.30. .RT .sp 2P .LP 4.1 \fITMN interfaces\fR .sp 1P .RT .sp 1P .LP 4.1.1 \fIQ\fR .sp 9p .RT .EF '% \fI3\ interface'' .OF '''\fI3\ interface %' .PP Interface Q\d3\uconnects exchanges to OSs via the Data Communication Network (DCN). .bp .RT .LP .rs .sp 27P .ad r \fBFigure 1/Q.513, p.\fR .sp 1P .RT .ad b .RT .PP The interface shall be capable of supporting the following two broad categories of information to be communicated: .RT .LP a) transactions: low data volumes to be transported, e.g.,\ exchange alarm messages; .LP b) bulk data transfers: large data volumes to be transported, e.g.,\ billing data. .PP The characterization of these information types is for further study. .PP The protocols used across the Q\d3\uinterface will be based on the OSI model and will use OSI protocols specified by CCITT where possible. To allow for alternative DCNs, alternative lower layer protocol sets may be used, depending on the specific situation. Several protocol sets for layers\ 1, 2 and 3 have been used for similar data communications networks. Examples include: .RT .LP a) X.25 .LP b) Signalling System No. 7 MTPB/FSCCP .LP c) Q.921/Q.931. .PP Their use in TMN applications is for further study. .PP It is recommended that each set of TMN application functions with similar protocol needs be supported with unique protocol selections for layers\ 4 through\ 7 as defined by the OSI Reference Model (Recommendation\ X.200). The nulling of service options of individual layers above layer\ 3 and even entire layers above layer\ 3 may be necessary where justifiable. .RT .sp 1P .LP 4.1.2 \fIQ\fR .sp 9p .RT .EF '% \fI2\ interface'' .OF '''\fI2\ interface %' .PP Interface Q\d2\umay be used to connect exchanges to Mediation Devices (MDs) or to Network Elements (NEs) which contain a mediation function. .PP The need for the Q\d2\uinterface on an exchange is for further study. .bp .RT .sp 1P .LP 4.1.3 \fIQ\fR .sp 9p .RT .EF '% \fI1\ interface'' .OF '''\fI1\ interface %' .PP Interface Q\d1\umay be used to connect exchanges to NEs which support only the Network Element Function and no mediation function. .PP The need for the Q\d1\uinterface on an exchange is for further study. .RT .sp 1P .LP 4.1.4 \fIF interface\fR .sp 9p .RT .PP Interface F connects exchanges to workstations. The definition of functions and protocols is for further study. .RT .sp 1P .LP 4.1.5 \fIG interface\fR .sp 9p .RT .PP Interface G is the human\(hymachine interface for OAM functions, providing output displays and text (e.g.,\ CRT, printer, light panel) and input capabilities (e.g.,\ keyboard). .PP This interface is specified in the Z.300\(hySeries of Recommendations which may be enhanced in the future. .RT .sp 1P .LP 4.2 \fIOther OAM interfaces\fR .sp 9p .RT .PP These interfaces are intended to represent existing OAM interfaces during the period of transition to TMN. They are not subject to CCITT Recommendations. .RT .sp 1P .LP 4.2.1 \fIQ\fR .sp 9p .RT .EF '% \fI0\ interface'' .OF '''\fI0\ interface %' .PP Interface Q\d0\uconnects exchanges to OSs, MDs and NEs using protocols and functions other than those defined in TMN Recommendations. .RT .sp 1P .LP 4.2.2 \fIF\fR .sp 9p .RT .EF '% \fI0\ interface'' .OF '''\fI0\ interface %' .PP Interface F\d0\uconnects exchanges to workstations, using function and protocols not specified in TMN Recommendations. .RT .sp 1P .LP 4.2.3 \fIG\fR .sp 9p .RT .EF '% \fI0\ interface'' .OF '''\fI0\ interface %' .PP Interface G\d0\uis a human\(hymachine interface not subject to CCITT Recommendations. .RT .sp 1P .LP 4.3 \fIISDN access interfaces\fR .sp 9p .RT .PP The exchange requirements for interworking between the exchange ISDN access sub\(hysystem including the V\ interfaces and the exchange TMN sub\(hysystem are for futher study. .RT .sp 1P .LP 4.4 \fISignalling System No. 7 network interface\fR .sp 9p .RT .PP The exchange requirements for interworking between the exchange Signalling System\ No.\ 7 sub\(hysystems and the exchange TMN sub\(hysystem are for further study. \v'1P' .RT .sp 2P .LP \fBRecommendation\ Q.521\fR .RT .sp 2P .sp 1P .ce 1000 \fBEXCHANGE\ FUNCTIONS\fR .EF '% Fascicle\ VI.5\ \(em\ Rec.\ Q.521'' .OF '''Fascicle\ VI.5\ \(em\ Rec.\ Q.521 %' .ce 0 .sp 1P .sp 2P .LP \fB1\fR \fBGeneral\fR .sp 1P .RT .PP This Recommendation applies to digital local, combined, transit and international exchanges for telephony in Integrated Digital Networks (IDN) and mixed (analogue/digital) networks and also to local, combined, transit and international exchanges in an Integrated Services Digital Network (ISDN). .PP The field of application of this Recommendation is more fully defined in Recommendation\ Q.500. .PP Some text may only apply to a certain type (types) of exchange, e.g.\ digital transit, local or combined. Where this occurs, the application is defined in the text. Not all the recommended functions will necessarily be provided in every exchange. .bp .RT .sp 2P .LP \fB2\fR \fBExchange functions \(em Introduction and framework\fR .sp 1P .RT .sp 1P .LP 2.1 \fIGeneral\fR .sp 9p .RT .PP The purpose of this Recommendation is to specifically address those functions required to support basic and supplementary services in performing this test, this Recommendation takes account of the principles set down in Recommendation\ I.310 and draws a clear distinction between services and the exchange capabilities required to support them. .PP It should be noted that the list of functions identified in this Recommendation is not necessarily extensive. .RT .sp 1P .LP 2.2 \fIExchange model\fR .sp 9p .RT .PP The functions described in this and associated Recommendations can be considered within the framework of an exchange functional model. Such a model is shown in Figure\ 1/Q.521. This divides the exchange into three functional areas as follows: .RT .LP a) control functions \(em Those functions required to control services and connections, e.g.\ signalling, routing and connectionB/Fresources handling functions; .LP b) connection functions \(em Those functions directly related to the connection path through an exchange, i.e.\ switching and transmission mechanism (including ET); .LP c) operation and maintenance functions \(em Those functions of an operational, management and maintenance nature which are not employed for call establishment and supervisory purposes, e.g.\ test functions. .PP The exchange functional model shown in Figure\ 1/Q.521 is appropriate to exchanges operating in an IDN and also those operating in an IDN which is evolving towards an ISDN. In terms of this Recommendation, most of the functions fall within the control functions area. .LP .rs .sp 20P .ad r \fBFigure 1/Q.521, p.\fR .sp 1P .RT .ad b .RT .PP Connection functions are primarily covered in Recommendation\ Q.522. These address the basic switch characteristics of different connection types. OAM functions are primarily covered in Recommendation\ Q.542. .bp .sp 2P .LP \fB3\fR \fBUtilization of exchange functions for services\fR .sp 1P .RT .sp 1P .LP 3.1 \fIGeneral\fR .sp 9p .RT .PP Exchange functions are used and reused in various stages of call processing. Some may be combined with others to create features used in providing supplementary services. The specific functions used in a given context will be determined by the requested service. .PP Within the framework of the model shown in Figure 1/Q.521 the utilization of functions arising from a service request, can be considered in the following way: .RT .LP a) on receipt of a service request (via the Signalling Functions) the Service Processing Functions are used to identify the appropriate connection type(s); .LP b) the appropriate type of connection is established by use of the Connection/Resources Handling Functions; .LP c) Supplementary Services which involve additional functions and information flows beyond those required for bearer services, are provided under the control of logic residing in the Service Processing Function. This logic is designed to provide specific services. Corresponding service/feature capabilities must also reside in the Signalling and Connection/Resources Handling Functions. .PP In addition to services provided by use of logic/data residing in the exchange, some services may be provided under the control of logic located at separate specialized nodes (Service Control Points). Also, data required or process certain service requests may be kept in a remote data base accessed by use of the Signalling Function. .sp 2P .LP \fB4\fR \fBGeneral functions required for operation of an exchange in the\fR \fBIDN, ISDN or mixed analogue/digital environment\fR .sp 1P .RT .sp 1P .LP \fR 4.1 \fITiming and synchronization\fR \v'3p' .sp 9p .RT .PP 4.1.1 Exchange timing \(em Ability to distribute timing within the exchange so that it will maintain synchronism on 64\ kbit/s channel timeslots in a connection through the exchange. .PP 4.1.2 Synchronization \(em Ability to operate in the IDN or ISDN in synchronism with other digital entities and provide timing signals to other network entities as required. .PP 4.1.3 Interval timing \(em Ability to measure time between events as required in call processing and/or in signalling. .PP 4.1.4 Time\(hyof\(hyday clock \(em Ability to determine time of day. .PP \fINote\fR \ \(em\ The level of accuracy is for further study. .sp 2P .LP 4.2. \fISignalling\fR .sp 1P .RT .sp 1P .LP 4.2.1 \fIUser\(hyaccess signalling functions\fR \v'3p' .sp 9p .RT .PP 4.2.1.1 Ability to receive and interpret decadic or Dual Tone Multi\(hyFrequency (DTMF) signalling from user terminals. .PP 4.2.1.2 Ability to support user\(hyaccess signalling layers\ 1 and\ 2 in accordance with Recommendations\ I.430, Q.921 (I.441). .PP 4.2.1.3 Ability to communicate with user terminals using layer\ 3 signalling in accordance with Recommendation\ Q.931 (I.451). .sp 1P .LP 4.2.2 \fINetwork signalling functions\fR \v'3p' .sp 9p .RT .PP 4.2.2.1 Ability to use and support CCITT signalling systems included in Recommendation Q.7, particularly CCITT Signalling System\ No.\ 7. .PP 4.2.2.2 Ability to communicate with other network entities using the CCITT Signalling System\ No.\ 7, Q.700\(hySeries of Recommendations User Parts. .bp .sp 2P .LP \fBRecommendation\ Q.522\fR .RT .sp 2P .ce 1000 \fBDIGITAL\ EXCHANGE\ CONNECTIONS,\fR .EF '% Fascicle\ VI.5\ \(em\ Rec.\ Q.522'' .OF '''Fascicle\ VI.5\ \(em\ Rec.\ Q.522 %' .ce 0 .sp 1P .ce 1000 \fBSIGNALLING\ AND\ ANCILLARY\ FUNCTIONS\fR .ce 0 .sp 1P .sp 2P .LP \fR \fB1\fR \fBGeneral\fR .sp 1P .RT .PP This Recommendation applies to digital local, combined, transit and international exchanges for telephony in Integrated Digital Networks (IDN) and also to local, combined, transit, and international exchanges in an Integrated Services Digital Network (ISDN). The field of application of this Recommendation is more fully defined in Recommendation\ Q.500. .RT .sp 2P .LP \fB2\fR \fBConnections through an exchange\fR .sp 1P .RT .sp 1P .LP 2.1 \fIGeneral\fR .sp 9p .RT .PP The characteristics of the connections detailed in this section refer to an established connection when it is made available to the users. .PP An exchange must be able to provide originating, terminating and internal exchange connections between input and output interfaces for telephony and other services as required. It may also provide transit connections: .RT .LP \(em A connection (if any) between an incoming and an outgoing circuit at interfaces to other exchangesB/Fnetworks is called a transit connection. .LP \(em A connection between channel(s) of a calling subscriber line at an interface for subscriber access and an outgoing circuit at an interface to other exchange/networks is called an originating connection. .LP \(em A connection between an incoming circuit at an interface to other exchange/networks and channel(s) of a called subscriber line at an interface for subscriber access is called a terminating connection. .LP \(em A connection between channels of two subscriber lines at interfaces for subscriber access is called an internal connection. .PP An exchange must be able to provide bidirectional connections between input and output interfaces for telephony and other services as required. .PP Also unidirectional connections may be required. .RT .sp 2P .LP 2.2 \fIBasic exchange connections\fR .sp 1P .RT .sp 1P .LP 2.2.1 \fIGeneral\fR .sp 9p .RT .PP The requirements in this section primarily apply to digital local or combined exchanges. Applicability to digital transit or international exchanges requires further study. .PP Four types of exchange connection have been identified to show the basic forms of connection and their associated information flows that a digital local or combined exchange may be required to handle in an ISDN. They have been based on originatingB/Fterminating connections established via interfaces for subscriber access as described in Recommendation\ Q.512 to/from locations external to the exchange. Calls may be set up in either direction, i.e.,\ subscriber to network or network to subscriber. .PP These diagrams are functional and not intended to represent any particular implementation. They illustrate the options which may be available for handling a given information type or service within a digital local or combined exchange. Although this approach leads to some duplication between the individual diagrams when considered from the connection point of view, the approach is a logical basis for the further consideration of the more detailed issues arising from the impact of the ISDN on a digital local or combined exchange. .PP It is not intended to imply that every digital local or combined exchange should necessarily have the capability to handle all these types of connection. .bp .PP Other types of connection and variants of these basic exchange connections may be feasible in an ISDN and are the subject of further study. .PP The signalling and control aspects of these connections are covered in \(sc\(sc\ 3 and\ 5 of this Recommendation. .RT .sp 1P .LP 2.2.2 \fIExplanatory information on the exchange connection diagrams\fR .sp 9p .RT .PP The functions associated with the groupings shown on the types I\(hyIV exchanges connection diagrams are covered in \(sc\ 3. .RT .sp 1P .LP \fIKey\fR .sp 9p .RT .LP \ information other than separate signalling \ \(em\(em\(em\(em\(em\(em\(em separate signalling(s) .sp 1P .LP \fIInformation flows\fR .sp 9p .RT .LP \(em p\d1\u: packet data information different from customer\(hyoriginated packetized data; .LP \(em s\d1\u, s\d2\u, s\d4\u, s\d5\u: signalling information different from the signalling associated with customer terminals; .LP \(em packet switching interworking functions may be provided at other exchanges in an ISDN or at the point of access to a separate packet switched network. .sp 1P .LP 2.2.3 \fIType 1 exchange connection\fR (Figure 1/Q.522) .sp 9p .RT .PP This connection is sued to transport telephony and associated voice services. .PP This connection is characterized by (see Table 2/I.340, A | , A | , A | and A | ): .RT .sp 1P .LP \(em \fIInformation transfer attributes\fR .sp 9p .RT .LP mode: circuit .LP rate: 64 kbit/s .LP capability: speech \(em 3.1 kHz audio .LP establishment: switched \(em semi\(hypermanent .LP symmetry: bidirectional \(em symmetric .LP configuration: point\(hyto\(hypoint uniform .LP structure: 8 kHz integrity .sp 1P .LP \(em \fIAccess attributes\fR (Table 1/Q.522) .sp 9p .RT .ce \fBH.T. [T1.522]\fR .ce TABLE\ 1/Q.522 .ps 9 .vs 11 .nr VS 11 .nr PS 9 .TS center box; cw(60p) | cw(60p) | cw(90p) . Access attributes User access Network access _ .T& lw(60p) | cw(60p) | cw(90p) . Access channel and rate .T& lw(60p) | lw(60p) | lw(90p) . Information B/64 { Digital circuit with access to analogue/digital switched network } .T& lw(60p) | lw(60p) | lw(90p) . Signalling D/16\(hy64 Digital circuit (s 1) .T& lw(60p) | lw(60p) | lw(90p) . Access protocol | ua\d\u)\d .T& lw(60p) | lw(60p) | lw(90p) . \ Layer 1 For further study Q.702, others .T& lw(60p) | lw(60p) | lw(90p) . \ Layer 2 I.441 Q.703, others .T& lw(60p) | lw(60p) | lw(90p) . \ Layer 3 I.451 Q.704, Q.714, Q.764, others .TE .LP \ua\d\u)\d Only for switched services. .nr PS 9 .RT .ad r \fBTable 1/Q.522 [T1.522], p.\fR .sp 1P .RT .ad b .RT .LP .bp .sp 1P .LP \(em \fIOther attributes\fR .sp 9p .RT .LP For further study. .LP .rs .sp 13P .ad r \fBFigure 1/Q.522, p.\fR .sp 1P .RT .ad b .RT .sp 1P .LP 2.2.4 \fIType II exchange connection\fR | Figure 2/Q.522) .sp 9p .RT .PP This connection is used to transport circuit switched services such as data, telephony, multiple subrate information streams multiplexed into 64\ kbit/s by the user, transparent access to a PSPDN (see \(sc\ 5.2.2). .PP This connection is characterized by: .RT .sp 1P .LP \(em \fIInformation transfer attributes\fR (see Table 2/I.340, A | and A | ) .sp 9p .RT .LP mode: circuit .LP rate: 64 kbit/s .LP capability: unrestricted digital information .LP establishment: switched \(em semi\(hypermanent .LP symmetry: bidirectional \(em symmetric .LP configuration: point\(hyto\(hypoint uniform .LP structure: 8 kHz integrity .sp 1P .LP \(em \fIAccess attributes\fR (Table 2/Q.522) .sp 9p .RT .ce \fBH.T. [T2.522]\fR .ce TABLE\ 2/Q.522 .ps 9 .vs 11 .nr VS 11 .nr PS 9 .TS center box; cw(60p) | cw(60p) | cw(90p) . Access attributes User access Network access _ .T& lw(60p) | cw(60p) | cw(90p) . Access channel and rate .T& lw(60p) | lw(60p) | lw(90p) . Information B/64 { Digital circuit with access to analogue/digital switched network \fR } .T& lw(60p) | lw(60p) | lw(90p) . Signalling D/16\(hy64 Digital circuit (s 1) .T& lw(60p) | lw(60p) | lw(90p) . Access protocol { See type I (For signalling only) | ua\d\u)\d } { See type I (For signalling access to digital switched network) | ua\d\u)\d } .TE .LP \ua\d\u)\d Further study is required for information transfer protocol or access to PSPDN. .nr PS 9 .RT .ad r \fBTable 2/Q.522 [T2.522], p.\fR .sp 1P .RT .ad b .RT .LP .bp .sp 1P .LP \(em \fIOther attributes\fR .sp 9p .RT .LP For further study. .LP .rs .sp 16P .ad r \fBFigure 2/Q.522, p.\fR .sp 1P .RT .ad b .RT .sp 1P .LP 2.2.5 \fIType III exchange connection\fR (Figure 3/Q.522) .sp 9p .RT .PP This is a connection used to transport packetized data information between an information channel on a digital subscriber access and a 64\ kbit/s digital circuit which has an access to: .RT .LP a) a remote ISDN Packet Handling Functional Grouping; .LP b) a remote ISDN Packet Switching Interworking Functional Grouping; .LP c) a public packet network (see \(sc\ 5.2.3). .PP This connection is characterized by: .sp 1P .LP \(em \fIInformation transfer attributes\fR | see Table 3/Q.522) .sp 9p .RT .LP (see Table\ 2/I.340, A | 0 and A | 1) .LP .sp 1 .ce \fBH.T. [T3.522]\fR .ce TABLE\ 3/Q.522 .ps 9 .vs 11 .nr VS 11 .nr PS 9 .TS center box; cw(60p) | cw(84p) | cw(84p) . Access attributes Option a) Options b) and c) _ .T& lw(60p) | lw(84p) | lw(84p) . Mode Circuit Packet .T& lw(60p) | lw(84p) | lw(84p) . Rate 64 kbit/s (further study) 64 kbit/s (further study) .T& lw(60p) | lw(84p) | lw(84p) . Capability { Unrestricted digital information } { Unrestricted digital information } .T& lw(60p) | lw(84p) | lw(84p) . Establishment { Switched \(em semi\(hypermanent } { Switched \(em semi\(hypermanent } .T& lw(60p) | lw(84p) | lw(84p) . Symmetry Bidirectional symmetric Bidirectional symmetric .T& lw(60p) | lw(84p) | lw(84p) . Configuration Point\(hyto\(hypoint Point\(hyto\(hypoint .T& lw(60p) | lw(84p) | lw(84p) . Structure 8 kHz Service data unit integrity _ .TE .nr PS 9 .RT .ad r \fBTableau 3/Q.522 [T3.522], p.\fR .sp 1P .RT .ad b .RT .LP .bp .sp 1P .LP \(em \fIAccess attributes\fR | Table 4/Q.522) .sp 9p .RT .LP .sp 1 .ce \fBH.T. [T4.522]\fR .ce TABLE\ 4/Q.522 .ps 9 .vs 11 .nr VS 11 .nr PS 9 .TS center box; cw(60p) | cw(72p) | cw(72p) . Access attributes User access Network access _ .T& lw(60p) | cw(72p) | cw(72p) . Access channel and rate .T& lw(60p) | cw(72p) | cw(72p) . Information .T& lw(60p) | lw(72p) | lw(72p) . Options a), b), c) B/Further study { 64 kbit/s digital circuit | ua\d\u)\d } .T& lw(60p) | lw(72p) | lw(72p) . Signalling a), b), c) D/16\(hy64 { 64 kbit/s digital circuit | ua\d\u)\d } .T& lw(60p) | lw(72p) | lw(72p) . Access protocol .T& lw(60p) | lw(72p) | lw(72p) . \ Options a), b) For further study For further study .T& lw(60p) | lw(72p) | lw(72p) . \ Option c) For further study X.75 | (hy | .25 .TE .LP \ua\d\u)\d Information and signalling may be carried by the same circuit (in\(hyband signalling). .nr PS 9 .RT .ad r \fBTable 4/Q.522 [T4.522], p.\fR .sp 1P .RT .ad b .RT .LP .sp 5 .sp 1P .LP \(em \fIOther attributes\fR .sp 9p .RT .LP For further study. .LP .rs .sp 20P .ad r \fBFigure 3a/Q.522, p.\fR .sp 1P .RT .ad b .RT .LP .bp .LP .rs .sp 22P .ad r \fBFigure 3b/Q.522, p.\fR .sp 1P .RT .ad b .RT .LP .rs .sp 27P .ad r \fBFigure 3c/Q.522, p.\fR .sp 1P .RT .ad b .RT .LP .bp .sp 1P .LP 2.2.6 \fIType IV exchange connection\fR | Figure 4/Q.522) .sp 9p .RT .PP This connection is used to transport message type data, for example packetized data messages or teleaction information messages (see \(sc\ 5.2.4). .PP It consists of a message/packet type connection via a D channel on a digital subscriber access to an access port to either: .RT .LP a) a remote ISDN Interworking Functional Grouping; or .LP b) a public packet network. .PP This connection is characterized by: .sp 1P .LP \(em \fIInformation transfer attributes\fR .sp 9p .RT .LP (see Table\ 2/I.340). .LP See type III, options b) and c). .sp 1P .LP \(em \fIAccess attributes\fR | Table 5/Q.522). .sp 9p .RT .ce \fBH.T. [T5.522]\fR .ce TABLE\ 5/Q.522 .ps 9 .vs 11 .nr VS 11 .nr PS 9 .TS center box; cw(60p) | cw(72p) | cw(72p) . Access attributes User access Network access _ .T& lw(60p) | cw(72p) | cw(72p) . Access channel and rate .T& lw(60p) | cw(72p) | cw(72p) . Information and signalling .T& lw(60p) | lw(72p) | lw(72p) . \ Options a) and b) { D/For further study | ua\d\u)\d } { 64 kbit/s digital circuit \ub\d\u)\d } .T& lw(60p) | lw(72p) | lw(72p) . Access protocol .T& lw(60p) | lw(72p) | lw(72p) . \ Option a) For further study For further study .T& lw(60p) | lw(72p) | lw(72p) . \ Option a) For further study X.75 | (hy | .25 .TE .LP \ua\d\u)\d Signalling in\(hyband or out\(hyband. .LP \ub\d\u)\d Signalling in\(hyband or out\(hyband for option a), or in\(hyband for option b). .nr PS 9 .RT .ad r \fBTable 5/Q.522 [T5.522], p.\fR .sp 1P .RT .ad b .RT .LP .rs .sp 18P .ad r Blanc .ad b .RT .LP .bp .sp 1P .LP \(em \fIOther attributes\fR .sp 9p .RT .LP For further study. .LP .rs .sp 30P .ad r \fBFigure 4/Q.522, p.\fR .sp 1P .RT .ad b .RT .sp 1P .LP 2.3 \fIFunctions associated with attributes shown in \(sc\ 2.2\fR .sp 9p .RT .PP The following information is to clarify which functions may be associated with the attributes shown on the types\ I\(hyIV exchange connection diagrams described in \(sc\ 2.2. .RT .sp 1P .LP 2.3.1 \fILayer 1 functions\fR (see Note in \(sc\ 2.3.4) .sp 9p .RT .PP This functional grouping includes: .RT .LP \(em digital line/exchange termination interface functions. .sp 1P .LP 2.3.2 \fILayer 2 functions\fR (see Note in \(sc\ 2.3.4) .sp 9p .RT .PP This functional grouping includes: .RT .LP \(em layer 2 D\(hychannel protocol handling (LAP D) .sp 1P .LP 2.3.3 \fI64 kbit/s circuit switching functions\fR .sp 9p .RT .PP This functional grouping includes: .RT .LP \(em 64 kbit/s switching stage(s). .bp .sp 1P .LP 2.3.4 \fISignalling handling and exchange control functions\fR .sp 9p .RT .PP This functional grouping may include: .RT .LP \(em layer 3 D\(hychannel protocol for signalling (see Note); .LP \(em functions related to circuit switched connection control; .LP \(em signalling functions for common channel signalling; .LP \(em signalling interfaces with \*Qpacket handling function\*U; .LP \(em functions related to packet switched connections; .LP \(em signalling interface with \*Qpacket switching interworking function\*U. .PP \fINote\fR \ \(em\ The term \*Qlayer\*U refers to Open Systems Interconnection as applied to CCITT signalling systems as defined by Recommendations\ X.200 and\ I.112. .sp 1P .LP 2.3.5 \fIPacket switching interworking functions\fR .sp 9p .RT .PP This functional grouping may include: .RT .LP \(em signalling interface with \*Qpacket handling function\*U and \*Qsignalling handling and exchange control function\*U allowing call packets to be routed to/from the appropriate subscriber terminals; .LP \(em routing functions; .LP \(em functions such as compatibility checking; .LP \(em protocol conversion; .LP \(em numbering interworking; .LP \(em control function (see Note in \(sc\ 2.3.6). .sp 1P .LP 2.3.6 \fIPackets handling function\fR .sp 9p .RT .PP This functional grouping may include: .RT .LP \(em layer 3 D\(hychannel protocol for packet calls; .LP \(em packet level multiplexing for outgoing calls; .LP \(em packet level demultiplexing for incoming calls; .LP \(em signalling interface with the \*Qsignalling handling function\*U and subscriber terminals via layer 1 and 2 functional block; .LP \(em control functions for packet switched connections (see Note); .LP \(em some or all the functions associated with packet switching (e.g., internal packet calls). .PP \fINote\fR \ \(em\ Clarification of control function would need further study. .PP In the case where the packet switching interworking function is not present in the local exchange, the local exchange contains the minimum functions necessary to enable it to communicate with the packet switching interworking function. The protocols to carry out this minimum function require further study. .RT .sp 2P .LP 2.4 \fIBit rate of a connection through an exchange\fR .sp 1P .RT .sp 1P .LP 2.4.1 \fIBasic bit rate for circuit switched connections\fR .sp 9p .RT .PP The exchange should be able to make circuit switched connections between channel timeslots with the basic bit rate of 64\ kbit/s. The channel timeslots to be connected are contained in primary or higher order frame structures appearing at the digital interfaces of the exchange or derived from analogue channels appearing at the analogue interfaces, or from individual digital interfaces for subscriber access. .PP Switching at rates other than 64\ kbit/s is for further study. .RT .sp 1P .LP 2.4.2 \fIBasic bit rate for message/packet switched connections Type IV\fR .sp 9p .RT .PP The bit rate of a messageB/Fpacket connection Type IV will depend on a number of factors including the bit rate of the subscriber terminal equipment, the bit rate of the D\ channel and the bit rate capacity of the connection to the appropriate network. .bp .RT .sp 1P .LP 2.5 \fIServices offered at bit rates less than 64 kbit/s\fR .sp 9p .RT .PP Services requiring less than 64 kbit/s for a connection should be switched as 64\ kbit/s connections. .RT .sp 2P .LP 2.6 \fIServices offered at bit rates greater than 64 kbit/s\fR .sp 1P .RT .sp 1P .LP 2.6.1 \fIGeneral\fR .sp 9p .RT .PP Services requiring more than 64 kbit/s for a connection are through\(hyconnected as a multiple of 64\ kbit/s connections. They are called multi\(hyslot connections . .PP The exchange may be required to establish the following types of multi\(hyslot connections (see Recommendation\ I.340): .RT .LP \(em 2 \(mu 64 kbit/s connections; .LP \(em 6 \(mu 64 kbitB/Fs connections to provide a H\d0\uchannel; .LP \(em 24 \(mu 64 kbitB/Fs connections to provide a H\d1\\d1\uchannel; .LP \(em 30 \(mu 64 kbitB/Fs connections to provide a H\d1\\d2\uchannel. .PP It should be noted that an n \(mu 64 kbit/s connection can seriously affect the blocking probability of an exchange and the network, particularly if all n\ timeslots are routed in a defined order in the same multiplex. The ability to handle multi\(hyslot traffic will be influenced by the traffic loading of the exchange at any instant and the number of circuits available on the required route. .sp 1P .LP 2.6.2 \fI2 \(mu 64 kbit/s connections\fR .sp 9p .RT .PP This connection type is characterized by the following attributes (see Recommendation\ I.340). .PP The attributes are for further study. .PP A 2 \(mu 64 kbitB/Fs connection is established in response to signalling information received on the subscriber line or on an inter\(hyexchange link. .PP The exchange should maintain restricted differential time delay between the two timeslots involved in the connection. The precise definition of \*Urestricted differential time delay\*U is still to be formulated, but the intention is to ensure that the time delay between the individual slots forming a 2\ \(mu\ 64\ kbit/s connection is not excessive, for example as could occur if the two channels were routed out of the exchange on diverse physical routings. .PP The exchange aspects of meeting this requirement require further study, but will include the need for the exchange to be capable of recognizing the signalling information on incoming inter\(hyexchange circuits/subscriber accesses which indicates that there is an association between two incoming 64\ kbit/s channels and to ensure that the two channels are handled by the exchange in a uniform manner. .RT .sp 1P .LP 2.6.3 \fISwitching of 6 \(mu 64 kbit/s connections (H\fR\d0\u\fIchannel)\fR .sp 9p .RT .PP The 64 kbit/s timeslots which form an H\d0\uchannel are transmitted over the same primary multiplex system within the same frame. This is valid for both the subscriber line and the inter\(hyexchange links. .PP The requirement for 6 \(mu 64 kbit/s connections can be satisfied by establishing 6\ separate 64\ kbit/s semi\(hypermanent connections, each of which would be set up to preserve the sequence with the other slots forming the 6\ \(mu\ 64\ kbit/s connection. .RT .sp 1P .LP 2.6.4 \fISwitching of 24 or 30 \(mu 64 kbit/s connection (H\fR\d1\u\fIchannels)\fR .sp 9p .RT .PP This is for further study. .RT .sp 2P .LP 2.7 \fIMode of establishment\fR .sp 1P .RT .sp 1P .LP 2.7.1 \fICircuit switched connections, Type I, Type II and Type III\fR \fIoption a)\fR .sp 9p .RT .PP Circuit switched connections are set up at any time on demand in response to signalling information received from subscribers, other exchanges or other networks. .bp .RT .sp 1P .LP 2.7.2 \fIPacket switched connections, Type III options b) and c)\fR .sp 9p .RT .PP For further study. .RT .sp 1P .LP 2.7.3 \fIMessageB/Fpacket switched connections, Type IV\fR .sp 9p .RT .PP These connections are set up on demand subject to any D channel priority/flow control restrictions that may be applicable. .RT .sp 1P .LP 2.7.4 \fISemi\(hypermanent connections\fR .sp 9p .RT .PP The exchange should have the capability of establishing semi\(hypermanent connections which pass through the exchange switching network. .PP Other features of semi\(hypermanent connections, e.g. grade of service, the need for an out\(hyslot signalling channel associated with the connection,\ etc. are for further study. .RT .sp 1P .LP 2.8 \fIBit sequence independence\fR .sp 9p .RT .PP See Recommendation Q.554. .RT .sp 1P .LP 2.9 \fIBit integrity\fR .sp 9p .RT .PP See Recommendation Q.554. .RT .sp 1P .LP 2.10 \fIOctet sequence integrity\fR .sp 9p .RT .PP See Recommendation Q.9. .RT .sp 1P .LP 2.11 \fI8 kHz (structure) integrity\fR .sp 9p .RT .PP See Recommendation I.140. .RT .sp 1P .LP 2.12 \fIBit patterns generated by the exchange in idle channel timeslots\fR .sp 9p .RT .PP At interfaces A and B, the following patterns are recommended for the idle condition, where the left\(hymost digit is the polarity digit. .PP 01111111 for 1544 kbit/s systems .PP 01010100 for 2048 and 8448 kbit/s systems. .PP At other interfaces the bit pattern generated in idle channel timeslots is for further study. .PP The patterns should not be used as an indication of the idle or barred conditions of a channel since this information should be derived from the control or signalling functions. .PP \fINote\fR \ \(em\ These patterns are slightly different from the quiet code produced by external test equipment and used as an auxiliary signal for noise and crosstalk measurements on digital exchanges (see Recommendations\ Q.551, \(sc\ 1.2.3.1, Q.552, \(sc\(sc\ 2, 2.2.3, 3.1.4 and Q.553, \(sc\(sc\ 2.1.1.2, 3.1.4). .RT .sp 1P .LP 2.13 \fIError performance\fR .sp 9p .RT .PP See Recommendation Q.554. .RT .sp 1P .LP 2.14 \fIIn\(hycall rearrangement\fR .sp 9p .RT .PP In\(hycall rearrangement is the rearrangement by the exchange of the established connections across the switchblock in a more efficient manner. .PP When it is provided, it is essential that the requirements for error performance, Quality of Service, etc. be met (see Recommendation\ Q.543). .RT .sp 1P .LP 2.15 \fITransmission performance characteristics\fR .sp 9p .RT .PP See Recommendations Q.551 to Q.554. .bp .RT .sp 2P .LP \fB3\fR \fBSignalling and D\(hychannel handling\fR .sp 1P .RT .sp 1P .LP 3.1 \fIGeneral\fR .sp 9p .RT .PP The exchange should be capable of interworking with other exchanges using signalling systems indicated in Recommendation\ Q.7, and for local or combined exchanges with user equipment on digital access lines (e.g.,\ terminals and PABXs) using the signalling procedures in Recommendations\ I.430, I.431, and Q.920 (I.440), Q.930 (I.450)\(hySeries of Recommendations. .PP For a local or combined exchange interworking with user terminals or analogue subscriber access lines should be accomplished using nationally recommended signalling procedures. .PP 64 kbit/s signalling channels entering the exchange via a multiplex structure may be connected through the exchange as semi\(hypermanent channels. .RT .sp 1P .LP 3.2 \fISignalling associated with exchange connections Types I\(hyIV\fR .sp 9p .RT .PP This section applies to local or combined exchanges only. .RT .sp 1P .LP 3.2.1 \fIGeneral\fR .sp 9p .RT .PP Details of the exchange connections Types I\(hyIV are given in \(sc\ 5. .PP For internal and originating connections, the call set up signalling information will be received from the subscriber. .PP For terminating and transit connections, the call set up signalling information will be received from the appropriate network or separate signalling network. .PP \fINote\fR \ \(em\ Receipt of call set up signalling information may be affected by the involvement of supplementary services. .RT .sp 1P .LP 3.2.2 \fIBasic connections including Type I exchange connection\fR .sp 9p .RT .PP The exchange should carry out the functions defined in the following signalling systems. .RT .sp 1P .LP 3.2.2.1 \fIOn the subscribers side\fR : \v'3p' .sp 9p .RT .LP a) analogue line signalling systems as defined nationally; and .LP b) the defined digital subscriber access signalling system(s) if digital subscriber accesses are provided (see Recommendations\ I.430 and Q.920, Q.930\(hySeries of Recommendations). .sp 1P .LP 3.2.2.2 \fIOn the network side\fR .sp 9p .RT .PP One or more of the signalling systems are defined in Recommendation\ Q.7. .RT .sp 1P .LP 3.2.3 \fIType II exchange connection\fR .sp 9p .RT .PP The exchange should carry out the functions defined in the following signalling systems. .RT .sp 1P .LP 3.2.3.1 \fIOn the subscriber side\fR .sp 9p .RT .PP The defined digital subscriber access signalling system(s) (see Recommendations\ I.430 and Q.920, Q.930\(hySeries of Recommendations). .RT .sp 1P .LP 3.2.3.2 \fIOn the network side\fR .sp 9p .RT .PP One or more of the signalling systems defined in Recommendation\ Q.7. .PP \fINote\fR \ \(em\ Further study is required for information transfer protocol or access to PSPDN. .bp .RT .sp 2P .LP 3.2.4 \fIType III exchange connection\fR .sp 1P .RT .sp 1P .LP 3.2.4.1 \fIOn the subscriber side\fR .sp 9p .RT .PP For further study. .RT .sp 1P .LP 3.2.4.2 \fIOn the network side\fR .sp 9p .RT .PP The signalling associated with the messages/packets may be: .RT .LP a) contained in the individual message/packets; or .LP b) transported separately, in accordance with one or more of the signalling systems defined in Recommendation\ Q.7. .PP A local exchange which supports such services must contain a function that is capable of either interpreting them and routing them appropriately, or of sending them directly to an appropriate interworking function. .sp 1P .LP 3.2.5 \fIType IV exchange connection\fR .sp 9p .RT .PP On the subscriber side: .PP The signalling associated with the messagesB/Fpackets may be: .RT .LP a) contained in the individual message/packet, or .LP b) transported separately as s\(hyinformation (see Recommendations\ I.430 and Q.920, and Q.930\(hySeries of Recommendations). .PP On the trunk side: .PP The signalling associated with the messages/packets may be: .RT .LP a) contained in the individual message/packet (p\d1\u); or .LP b) transported separately (s\d1\uinformation), in accordance with one or more of the signalling systems defined in Recommendation\ Q.7. .PP A local exchange which supports such services must contain a function that is capable of either interpreting them and routing appropriately, or of sending them directly to an appropriate interworking function. .sp 1P .LP 3.3 \fIDigital subscriber access \(em D channel and protocol handling\fR \fIlayers 1, 2 and 3\fR .sp 9p .RT .PP The following text refers to handling the D\(hychannel protocol on the exchange side of the interfaces\ U and\ V\d1\u. .PP The functions associated with handling the D\(hychannel protocol are defined in the parts of Recommendations\ I.430, Q.920 and Q.930\(hySeries of Recommendations relating to call establishment for subscribers connected to the U or V\d1\u\ interfaces. Exchange functions for D\(hychannel signalling procedures for users connected via a primary rate multiple access are also given in I.431, Q.920 and Q.930\(hySeries of Recommendations. .RT .sp 1P .LP 3.4 \fIUser\(hyto\(hyuser signalling\fR .sp 9p .RT .PP The exchange may receive signals from the user (e.g., from a PABX) for transport across the network. It must be capable of receiving this information, verifying its acceptability, and if the service is permitted to the requesting user, send it via the inter\(hyexchange signalling or other network to the distant exchange. Similarly the exchange may receive information from the signalling network for transmission to the subscriber. This capability may not be provided on all types of connection. .PP Where user\(hyto\(hyuser signalling involves network inter\(hyexchange facilities, it may be necessary for the originating local exchange to process this signalling information before sending it to the network, to ensure that it is compatible with signalling, charging and flow control requirements of the originating exchange and network. .bp .RT .sp 2P .LP \fB4\fR \fBAncillary functions\fR .sp 1P .RT .sp 1P .LP 4.1 \fIConnection of ancillary equipment\fR .sp 9p .RT .PP Ancillary equipment may be connected in the following way: .RT .LP i) Serially. This may require more than one connection through the exchange. Examples of serially connected equipment include: .LP \(em echo control devices, .LP \(em encoding law converters, .LP \(em manual board access equipment (for operator controlled traffic). .LP ii) As terminal connected equipment usually requiring one connection through the exchange. Examples of such equipment include: .LP \(em recorded announcements, .LP \(em manual board terminations, .LP \(em speech codecs, .LP \(em data terminal facilities, .LP \(em test equipment (such as a test call sender), .LP \(em tone generators, .LP \(em signalling receivers. .PP The interface between the exchange and the items of equipment listed above may be left to the national designers. However, the use of internationally standardized interfaces is preferred. .PP \fINote\fR \ \(em\ In some cases it may be necessary to establish more than one connection to one timeslot at the same time. .RT .sp 1P .LP 4.2 \fIDigitally generated tones and frequencies\fR .sp 9p .RT .PP When tones and frequencies are digitally generated the following minimum requirements apply on a provisional basis. .RT .sp 1P .LP 4.2.1 \fIService tones\fR .sp 9p .RT .PP Digitally generated tones should meet the recommended limits specified in Recommendation\ Q.35 when decoded. .RT .sp 1P .LP 4.2.2 \fISignalling frequencies\fR .sp 9p .RT .PP Digitally generated signalling frequencies should be such that they can be detected after decoding by any analogue receivers designed to CCITT Recommendations. .RT .sp 1P .LP 4.3 \fIEcho control devices\fR .sp 9p .RT .PP The exchange should be able to be equipped with echo control devices (echo suppressors/echo cancellers conforming to Recommendations\ G.164 and\ G.165 respectively). When required the exchange should be able to control such devices to meet the requirements of Recommendation\ Q.115. The means of control by the exchange is for further study. .PP (\fINote\fR \ \(em\ It is recognized that there is a need for an internationally agreed method of disabling and enabling echo control devices for the purposes of making end\(hyto\(hyend circuit transmission maintenance measurements, e.g.\ as recommended in Recommendation\ V.25.) .RT .sp 2P .LP \fB5\fR \fBControl functions associated with call handling\fR .sp 1P .RT .sp 1P .LP 5.1 \fIBasic control functions\fR .sp 9p .RT .PP The requirements for the basic control functions are implicit in the requirements recommended for the other functions of the exchange. However recommendation of a number of new requirements for the control functions associated with the handling of digital subscriber lines and the use of a digital local exchange within an ISDN, may be necessary. .bp .PP The exchange should provide the capability to avoid fraudulent use of the connection. Such capabilities may be based on the use of digital pads or an asymmetrical through\(hyconnect procedure. .PP An originating local exchange should be capable of supporting either symmetric or asymmetric through\(hyconnect procedures. The choice of procedure may be determined on the basis of service. .PP Terminating and transit exchange need only support symmetric through\(hyconnect procedure. .PP This subject is for further study. .RT .sp 2P .LP 5.2 \fIExchange connections Types I\(hyIV, general control aspects\fR .sp 1P .RT .sp 1P .LP 5.2.1 \fIType I\fR .sp 9p .RT .PP These connections will be set up between the accesses associated with network addresses specified in response to the signalling information received. Voice\(hyassociated facilities, e.g.\ tones, should be provided where appropriate and telephony supplementary services may be invoked if provided. .RT .sp 1P .LP 5.2.2 \fIType II\fR .sp 9p .RT .PP Such connections will be set up between the accesses associated with network addresses specified in response to the signalling messages received. Compatibility checking may be provided before the connection is completely established (see \(sc\ 2.3.1). Voice associated facilities (e.g.\ tones, pads) will be disabled in order to provide a transparent digital path, (the means of doing this is for further study). Data supplementary services may be invoked if provided. .RT .sp 1P .LP 5.2.3 \fIType III\fR .sp 9p .RT .PP Such connections will be set up between the accesses associated with network addresses specified in response to the signalling messages received. Compatibility checking may be provided before the connection is completely established (see \(sc\ 2.3.1). Voice associated facilities (e.g.\ tones, pads) will be disabled in order to provide a transparent digital path (the means of doing this is for further study). Data supplementary services may be invoked if provided. .PP For option a) in the switched access case, originating calls will be set up over the B\ channel towards the 64\ kbit/s digital circuit using the ISDN signalling procedures prior to starting X.25 layer\ 2 and layer\ 3 functions. The corresponding service requested in the Q.931 SET\(hyUP message is ISDN packet mode bearer service. For calls originated by the network, the same consideration applies (see Recommendations\ X.31 and\ I.462). .PP The distant packet handling must be selected by the called address in the D\(hychannel protocol when the terminal sets up the circuit switched connection. .PP Packet data communications, when using a switched B channel, will be established by separating the establishment phase of the B\ channel (carried out by the exchange) and the control phase of the virtual circuit using the X.25 link layer and packet layer protocol (carried out in the distant packet handling function). .PP For options b) and c) the same considerations as above apply except that the control phase of the virtual circuit is performed within the exchange. .RT .sp 1P .LP 5.2.4 \fIType IV\fR .sp 9p .RT .PP These connections will be of the messageB/Fpacket type (e.g., virtual circuit). The \*Qp\(hyinformation handling function\*U and \*Qpacket switching interworking function\*U shown in Figure\ 4/Q.521 will implement procedures for control of the logical links on the D\ channel (e.g.,\ flow control, error control) (see also \(sc\ 3.2.5). Voice associated facilities (e.g.,\ tones, pads) will be disabled in order to provide a transparent digital path. .PP The D channel provides a semi\(hypermanent physical connection which enables the user terminal to access a packet handling function by establishing a link layer connection (with a specific SAPI) to that function which can then be used to support packet communications according to X.25 layer\ 3 procedures. The X.25 packet layer will use the acknowledged information service provided by LAP\ D\ (see Recommendation\ Q.920). X.25 layer\ 3 procedures are transferred transparently over the D\ Channel link. .PP A single or multiple LAP D link must support the multiplexing of logical channels at layer\ 3. .bp .RT .sp 2P .LP 5.3 \fIControl functions associated with calls over a digital subscriber\fR \fIaccess via Interfaces U and V\fI\d\fI1\fR\u .sp 1P .RT .sp 1P .LP 5.3.1 \fIControl of circuit switched calls Types I, II and III\fR .sp 9p .RT .PP In response to s\(hyinformation carried on the D channel and network signalling messages, the exchange must have the following capabilities. .RT .LP a) \fISetting up a call\fR .LP The exchange must receive address information (overlap sending or en bloc), establish the desired path (digital only or mixed) and send further (e.g.,\ Signalling System\ No.\ 7) signalling, if necessary (e.g.,\ address, calling line identity, service indicator) into the network. .LP The call set up procedure may include steps to verify compatibility based on the record in the exchange of the services permitted for the subscriber. The degree of compatibility checking provided by the exchange requires further study. .LP b) \fIDuring a call\fR .LP In addition to the basic functions of maintaining a call record, supervising the call, charging for the call,\ etc., the exchange must be able to handle in\(hycall serviceB/Ffacility requests. These include for example transfer of a call to another terminal or conferencing. .LP If it is required that a terminal be moved from one location to another on the same access during a call, the exchange must be able to hold the call while the transfer is made and to re\(hyestablish communication on request by the user (including carrying out any compatibility checks). The exchange may limit the time allowed for moving a terminal. In addition, the user must send a signal to the exchange indicating that terminal movement is about to take place. Signalling procedures for terminal movement are given in Recommendation\ Q.931. .LP c) \fIClearing a call\fR .LP The exchange will need to initiate call clearing on receipt of a clear request signal from the terminal or network. .LP d) \fIWithout a call path\fR .LP The exchange may be required to handle signalling information without establishment of a call path (subscriber\(hynetwork transactions). .sp 1P .LP 5.3.2 \fIControl of message/packet calls over the D channel, Type IV\fR .sp 9p .RT .PP Any messages carrying p\(hyinformation on the D channel must be handled by the exchange in accordance with the applicable Recommendation for services (e.g.,\ Recommendation\ X.25) requested by the user. It is not necessary that every digital local or combined exchange in an ISDN should be able to .PP to carry out all the possible functions associated with handling this information. It is possible for example that the exchange may route such traffic to another node which has the appropriate handling facilities. .RT .sp 2P .LP \fB6\fR \fBControl functions associated with maintenance and automatic\fR \fBsupervision\fR .sp 1P .RT .PP See Recommendation Q.542. .RT .LP .rs .sp 10P .ad r Blanc .ad b .RT .LP .bp .LP \fBMONTAGE: PAGE 40 = PAGE BLANCHE\fR .sp 1P .RT .LP .bp