.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' .LP \fBMONTAGE: FIN de la Recommandation G.762 en\(hyt\* | te de cette page\fR .sp 2P .LP \v'22P' \fBRecommendation\ G.763\fR .RT .sp 2P .ce 1000 \fBDIGITAL\ CIRCUIT\ MULTIPLICATION\ EQUIPMENT\fR .EF '% Fascicle\ III.4\ \(em\ Rec.\ G.763'' .OF '''Fascicle\ III.4\ \(em\ Rec.\ G.763 %' .ce 0 .sp 1P .ce 1000 \fBUSING\ 32\ KBIT/S\ ADPCM\ AND\ DIGITAL\ SPEECH\ INTERPOLATION\fR .ce 0 .sp 1P .ce 1000 \fI(Melbourne, 1988)\fR .sp 9p .RT .ce 0 .sp 1P .LP \fB1\fR \fBGeneral\fR .sp 1P .RT .sp 1P .LP 1.1 \fIScope\fR .sp 9p .RT .PP This Recommendation is intended as an introduction to digital circuit multiplication equipment and systems, and as a base document for the specification of Digital Circuit Multiplication Equipment (DCME) and Digital Circuit Multiplication Systems (DCMS). .PP Essential facilities, interface conditions and overall performance requirements are given. Requirements for full compatibility and interoperability are under study (see Supplemnent\ N\uo\d\ 31 at the end of this fascicle). .RT .sp 1P .LP 1.2 \fIAttributes\fR .sp 9p .RT .PP Digital circuit multiplication equipment is utilized as a means of augmenting the capacity of digital transmission systems operating between several International Switching Centers (ISCs). DCME has all of the following attributes: .RT .LP \(em digital speech interpolation (DSI); .LP \(em low rate encoding (LRE); .LP \(em dynamic load control (DLC) arrangement in association with interfacing; .LP \(em capability to accommodate the following types of bearer service requirements: .LP i) speech, .LP ii) 3.1 kHz audio (data and speech), .LP iii) 64 kbit/s unrestricted (transparent), .LP iv) alternate speech/64 kbit/s unrestricted. .PP The link between two DCMEs is generally one where a highly efficient traffic carrying capability is required, e.g., a long\(hydistance link. .bp .sp 1P .LP 1.3 \fIApplication\fR .sp 9p .RT .PP This Recommendation is applicable to the design of digital circuit multiplication equipment intended for, but not limited to, use in an international digital circuit. Freedom is permitted in design details which are not covered in this Recommendation (see Note). .PP \fINote\fR \ \(em\ Several additional items yet to be fully considered include the evaluation of: .RT .LP \(em instantaneous 2\(hybit speech encoding on overloads (to avoid clipping), and voice\(hyband data rate discrimination (to permit rates less than or equal to 4800\ bit/s to be coded at 32\ kbit/s only and to increase bearer channel efficiency). .LP \(em silence elimination techniques (to permit saving of bearer channel capacity during the inactive periods of half\(hyduplex voice\(hyband data calls). .sp 2P .LP \fB2\fR \fBDefinitions relating to digital circuit multiplication equipment\fR .sp 1P .RT .sp 1P .LP 2.1 \fBdigital circuit multiplication equipment (DCME)\fR .sp 9p .RT .PP A general class of equipment which permits concentration of a number of 64\ kbit/s PCM encoded input trunk channels on a reduced number of transmission channels (see \(sc\ 2.7). .RT .sp 1P .LP 2.2 \fBdigital circuit multiplication system (DCMS)\fR .sp 9p .RT .PP A telecommunications network comprised of two or more DCME terminals where each DCME terminal contains a transmit unit and a receive unit. .RT .sp 1P .LP 2.3 \fBlow rate encoding (LRE)\fR .sp 9p .RT .PP A voice\(hyband signal encoding method, e.g. adaptive differential pulse code modulation (ADPCM), which results in a bit rate less than 64\ kbit/s, e.g. 40\ kbit/s, 32\ kbit/s, or 24\ kbit/s. .PP \fINote\fR \ \(em\ Conversion between speech signals encoded in PCM at 64 kbit/s and those encoded in ADPCM must be carried out by means of transcoding processes given in Recommendations\ G.721 and\ G.723. .RT .sp 1P .LP 2.4 \fBvariable bit rate (VBR)\fR .sp 9p .RT .PP The capability of the encoding algorithm to dynamically switch between 32\ and 24\ kbit/s for speech traffic under control of the DCME. .RT .sp 1P .LP 2.5 \fBdigital speech interpolation (DSI)\fR .sp 9p .RT .PP A process which, when used in the transmit unit of a DCME, causes a trunk channel (see \(sc\ 2.9) to be connected to a bearer channel (see \(sc\ 2.8) only when activity is actually present on the trunk channel. Thus, by exploiting the probability of the speech activity factor (see \(sc\ 2.14) of trunk channels being less than\ 1.0, enables the traffic from a number of trunk channels to be concentrated and carried by a lesser number of time\(hyshared bearer channels. The signals carried by a bearer channel, therefore, represent interleaved bursts of speech signals derived from a number of different trunk channels. .PP \fINote\fR \ \(em\ A process complementary to DSI is required in the receive unit of a DCME, i.e, assignment of the interleaved bursts to their appropriate trunk channels. .RT .sp 1P .LP 2.6 \fBDCME frame\fR .sp 9p .RT .PP A time interval, the beginning of which is identified by a <> in the control channel. The DCME frame need not coincide with the multiframes defined in Recommendation\ G.704. The format specification of the DCME frame includes channel boundaries and bit position significance. .RT .sp 1P .LP 2.7 \fBtransmission channel\fR .sp 9p .RT .PP A 64 kbit/s time slot within a DCME frame. .bp .RT .sp 1P .LP 2.8 \fBbearer channel (BC)\fR .sp 9p .RT .PP A bearer channel is a unidirectional, digital, transmission path from the transmit unit of one DCME to the receive unit of a second associated DCME and which is used to carry concentrated traffic between the two DCMEs. .PP \fINote\ 1\fR \ \(em\ A number of bearer channels in each direction of transmission form the both\(hyway link required between two DCMEs. This link may be, for example, a 2048\ kbit/s system. .PP \fINote\ 2\fR \ \(em\ A bearer channel may have any of the following instantaneous bit rates: 24, 32, 40 and 64\ kbit/s. .RT .sp 1P .LP 2.9 \fBtrunk channel (TC)\fR .sp 9p .RT .PP A unidirectional, digital transmission path (generally short distance) used for carrying traffic and which connects a DCME to other equipment, e.g. an International Switching Centre (ISC). Two such trunk channels (transmit and receive) are needed by 4\(hywire telephone circuits and constitute a trunk circuit. .PP \fINote\ 1\fR \ \(em\ Signals carried by a trunk channel will be transmitted at a bit rate of 64\ kbit/s. .PP \fINote\ 2\fR \ \(em\ A number of trunk channels in each direction of transmission are required between a DCME and, for instance, an\ ISC. These trunk channels may be carried by a number of\ 1544 of 2048\ kbit/s systems. .RT .sp 1P .LP 2.10 \fBassignment message\fR .sp 9p .RT .PP The message specifying the interconnections required between trunk channels and bearer channels. .RT .sp 1P .LP 2.11 \fBassignment map\fR .sp 9p .RT .PP A record, held in a memory of a DCME, of the interconnections required between trunk channels and bearer channels. This record is dynamically uptated in real time in accordance with the traffic demands made on the DCME. .RT .sp 1P .LP 2.12 \fBcontrol channel\fR .sp 9p .RT .PP A unidirectional transmission path from the transmit unit of one DCME to the receive unit of one or more associated DCMEs and which is dedicated primarily to carrying channel assignment messages. In addition, the control channel transmits other messages such as idle noise levels, dynamic load control, and alarm messages. .PP \fINote\fR \ \(em\ An alternative name for <> is <>. .RT .sp 1P .LP 2.13 \fBensemble activity\fR .sp 9p .RT .PP The ratio of the time active signals and their corresponding hangover time and front\(hyend delay occupy the trunk channels, to the total measuring time, averaged over the total number of trunk channels included in the measurement. .RT .sp 1P .LP 2.14 \fBspeech activity factor\fR .sp 9p .RT .PP The radio of the time speech signals with their corresponding hangover time and front\(hyend delay occupy a trunk channel, to the total measuring time, averaged over the total number of trunk channels carrying speach. .RT .sp 1P .LP 2.15 \fBvoice band data ratio\fR .sp 9p .RT .PP The radio of the number of trunk channels carrying voice\(hyband data signals to the total number of trunk channels averaged over a fixed interval of time. .RT .sp 1P .LP 2.16 \fB64 kbit/s unrestricted digital data ratio\fR .sp 9p .RT .PP The radio of the number of trunk channels carrying 64 kbit/s unrestricted digital data signals, to the total number of trunk channels averaged over a fixed interval of time. .bp .RT .sp 1P .LP 2.17 \fBDCME overload (mode)\fR .sp 9p .RT .PP The condition when the number of input trunk channels instantaneously active carrying speech exceeds the number of 32\ kbit/s channels available for interpolation. .RT .sp 1P .LP 2.18 \fBoverload channels\fR .sp 9p .RT .PP The additional bearer channel capacity which is generated using variable bit rate (VBR) encoding to minimize or eliminate\ DSI competitive clipping. .RT .sp 1P .LP 2.19 \fBaverage bits per sample\fR .sp 9p .RT .PP The average number of encoding bits per sample computed over a given time window for the ensemble of active interpolated bearer channels within a given interpolated pool. Only bearer channels carrying speech are included in this calculation. .RT .sp 1P .LP 2.20 \fBtransmission overload\fR .sp 9p .RT .PP The condition when the average bits per sample goes beyond the value set in accordance with speech quality requirements. .RT .sp 1P .LP 2.21 \fBfreeze\(hyout\fR .sp 9p .RT .PP The condition when a trunk channel becomes active and cannot immediately be assigned to a bearer channel, due to lack of available transmission capacity. .RT .sp 1P .LP 2.22 \fBfreeze\(hyout fraction (FOF)\fR .sp 9p .RT .PP The ratio of the total time that the individual channels experience the freeze\(hyout condition to the total time of the active intervals and their corresponding hangover times and front\(hyend delays, for all trunks over a fixed interval of time, e.g. one minute. .RT .sp 1P .LP 2.23 \fBinterpolation gain (IG)\fR .sp 9p .RT .PP The trunk channel multiplication ratio which is achieved through DSI. The\ IG is the ratio of the number of trunk channels to the number of DCME bearer channels where the same signal encoding rate is used for trunk and bearer channels. The achievable gain depends on the ensemble activity and the system size. .RT .sp 1P .LP 2.24 \fBtranscoding gain (TG)\fR .sp 9p .RT .PP The transmission channel multiplication ratio which is achieved through LRE, which effectively creates a number of low rate encoded bearer channels which is greater than the number of available transmission channels. When only a transcoding process conforming to Recommendation\ G.721 (i.e 32\ kbit/s ADPCM) is used, the\ TG will equal\ 2. When no transcoding is used the\ TG will equal\ 1. When overload channels are created the\ TG will be greater than\ 2. .RT .sp 1P .LP 2.25 \fBDCME gain (DCMG)\fR .sp 9p .RT .PP The trunk channel transmission multiplication ratio, which is achieved through application of DCME, including\ LRE and\ DSI. Hence DCMG\ =\ TG | (mu | G. .RT .sp 1P .LP 2.26 \fBclique\fR .sp 9p .RT .PP A set of bearer channels which are associated with a set of trunk channels and which are independent in operation and control from other bearer channels. The set of trunk channels is directed to a single destination. .PP \fINote\fR \ \(em\ An alternate term for clique is <>. .RT .sp 1P .LP 2.27 \fBmulti\(hyclique mode\fR .sp 9p .RT .PP A DCME operational mode in which more than one clique is used when each clique is associated with a different destination. .bp .RT .sp 1P .LP 2.28 \fBmulti\(hydestination mode\fR .sp 9p .RT .PP A DCME operational mode where traffic is exchanged between more than two\ (2) corresponding DCMEs simultaneously and trunk channel traffic is interpolated over a pool of available bearer channels for all destinations having traffic in the pool. The transmit trunk channels are designated to receive trunk channels at corresponding locations. .RT .sp 2P .LP \fB3\fR \fBTutorial\fR .sp 1P .RT .sp 1P .LP 3.1 \fIUse of digital circuit multiplication system (DCMS)\fR .sp 9p .RT .PP DCMS provides the means to reduce the cost of long distance transmission by making use of the combination of Digital Speech Interpolation (DSI) and Low Rate Encoding (LRE) techniques. .PP DSI is used to concentrate a number of input channels (generally referred to as trunk channels ) onto a smaller number of output channels (generally referred to as bearer channels ). It does this by connecting a trunk channel to a bearer channel only for the period that the trunk channel is active, i.e. is carrying a burst of speech or voice\(hyband data. Since in average conversations one direction of transmission is active for only 30\ to 40\ per cent of the time, if the number of trunks is large the statistics of the speech and silence distributions will permit a significantly smaller number of bearer channels ( bearer channel pool ) to be used. Control information must also be passed between the terminals to ensure that bearer and trunk channel assignments at each end remain synchronized. .PP LRE uses digital filtering techniques to construct an estimate of the waveform at both the encoder and the decoder. Since the actual information rate of speech is much lower than the channel Nyquist rate, the link used between the\ LRE encoder and the decoder can operate at a rate which is dependent mainly on the quality of the models and the permissible amount of transmission degradation. The CCITT has standardized in Recommendations\ G.721 and\ G.723 a type of\ LRE known as ADPCM, the performance of which has been extensively characterized. .PP The simplest way to use DCMS is in the single destination mode as shown in Figure\ 1/G.763. This mode of operation, is most economic for the largest routes. For smaller routes there are two options: .RT .LP \(em operation in multi\(hyclique mode; .LP \(em operation in multi\(hydestination mode. .PP Operation in multi\(hyclique mode , see Figure 2/G.763, divides the bearer channels into a number of blocks or <>, each associated with a different route. There is a fixed boundary between cliques, and trunk/bearer channel assignments are generally carried in a control channel within the clique that they refer to. This limits the dynamic processing of .PP received channels to those which are contained in the wanted clique; selection of the wanted clique channels can be done using a simple static digital switch without reference to the assignment information. With a 2048\ kbit/s bearer system in multi\(hyclique DCMS, the statistics of the\ DSI are unpromising with more than three routes. .PP Operation in multi\(hydestination mode\fR , see Figure 3/G.763, permits any bearer channel to be associated with any trunk channel of any of a number of different routes. There is no segregation of routes on the bearer, and therefore at the receive terminal it is impossible to select the wanted channels without reference to the assignment information. Multi\(hydestination mode is economic for very small routes via satellite, but practical difficulties limit the number of routes which is desirable to have on a single DCMS. .RT .LP .rs .sp 11P .ad r \fBFigure 1/G.763, p. 1\fR .sp 1P .RT .ad b .RT .LP .bp .LP .rs .sp 21P .ad r \fBFigure 2/G.763, p. 2\fR .sp 1P .RT .ad b .RT .LP .rs .sp 21P .ad r \fBFigure 3/G.763, p. 3\fR .sp 1P .RT .ad b .RT .LP .bp .sp 1P .LP 3.2 \fILocation\fR .sp 9p .RT .PP Location of DCME depends on its use. Equipment used in single destination mode or in multi\(hyclique mode can in general be located at the: .RT .LP \(em ISC, .LP \(em earth station, .LP \(em cable head, .LP without significant restrictions. .PP Equipment used in the multi\(hyclique mode will typically be located at the\ ISC so that the advantages of DCMG can be extended over the national section. .PP Equipment used in the multi\(hydestination mode will typically be located at the earth station or cable head. The reason for this is that whereas in multi\(hyclique mode the number of receive bearer channels at the DCME terminal is approximately equal to the number of transmit bearer channels, in multi\(hydestination mode the number of receive bearer channels at the DCME .PP terminal is the number of transmit bearer channels multiplied by the number of destinations. It therefore may be uneconomic to provide sufficient transmission capacity between the earth station and the\ ISC to permit location of multi\(hydestination DCME at an\ ISC. .RT .sp 1P .LP 3.3 \fITransmission requirements\fR .sp 9p .RT .PP DCMS is usually required to carry any traffic which can be carried on ordinary General Switched Telephone Network (GSTN) connections. That includes voice\(hyband data using V\(hyseries GSTN modems and facsimile calls following Recommendations\ T.4 and\ T.30 and using\ V.29 modems. In addition, in the\ ISDN, 64\ kbit/s unrestricted on\(hydemand digital data and alternate speech/64\ kbit/s unrestricted bearer services must be carried. .PP DCMS are primarily designed to maximize the efficiency of speech transmission. Use with voice\(hyband data especially at high rates, presents problems. These problems are mainly due to the difficulty for 32\ kbit/s ADPCM to encode voice\(hyband data waveforms. .RT .sp 1P .LP 3.4 \fIDCME gain (DCMG)\fR .sp 9p .RT .PP The gain of DCME is the input trunk channel transmission multiplication ratio, which is achieved through application of DCME, including\ LRE and\ DSI (for a specified speech quality at a certain level of bearer channel activity). The maximum available gain depends on: .RT .LP \(em number of trunk channels; .LP \(em number of bearer channels; .LP \(em trunk channel occupancy; .LP \(em speech activity; .LP \(em voice\(hyband data traffic; .LP \(em ratio of half duplex to full duplex voice\(hyband data; .LP \(em type of signalling; .LP \(em 64 kbit/s traffic; .LP \(em minimum acceptable speech quality; .LP \(em dynamic load control threshold. .PP Of these, the factor which has the greatest significance is the percentage of 64\ kbit/s digital data traffic. This is because a trunk channel carrying 64\ kbit/s traffic requires two 32 kbit/s bearer channels to be removed from the pool of channels available to the DSI process. .PP The percentage of voice\(hyband data typically varies between 5 and 30\ per cent, depending on the route. It is not unusual for a route to show more than a\ 2:1 variation, depending on time of day, with peaks which may or may not coincide for speech and voice\(hyband data. .PP The type of signalling system used on the route can significantly affect the gain. Continuously compelled signalling systems hold channels active for undesirably long periods. In the case of Signalling System\ R2 digital signalling via a DCMS used on a satellite, the channel might be active for\ 5 to 14\ seconds (Signalling System\ R2 also requires capacity for line signalling). .bp .PP The measured speech activity depends on the characteristics of the activity detector . It is usual to assume an activity of\ 35 to 40\ per cent. Outside of the route busy hour the occupancy of the trunk channels by traffic will be lower than during the route busy hour. The effect of this is .PP to reduce the activity measured by the activity detector to about 27\ per\ cent outside the route busy hour, whereas it will be close to the speech activity factor, i.e. about 40\ per\ cent, during the route busy hour. .PP The speech quality is governed by two main factors: the LRE rate, and the amount of speech lost while a newly active trunk channel is awaiting connection to a bearer channel. If there are a great many newly active trunk channels in competition, the beginning of a burst of speech is more likely to be <> of <> than if relatively few trunk channels are active. .PP The speech quality of a DCME in a network with external echo control devices may be affected by clipping introduced by echo control devices and by a possible noise contrast effect . In particular when echo suppressors or echo cancellers are used on low noise circuits, suppression of the far end noise may be objectionable due to noise contrast. Possible means of eliminating this problem are use of echo control devices which insert idle line noise at the appropriate level during suppression periods, or insertion of idle line noise at the DCME during the relevant period when the echo control device is integrated in the DCME. .PP When commissioning a new DCMS, observations should be made of the type and characteristics of the traffic which will use it. It is unwise to rely solely on customer complaints to indicate when a system is poorly dimensioned since interactions between the DCMS and echo control .FS The highest speech quality is obtained when echo cancellers conforming to Recommendation\ G.165 are used for echo control. However echo suppressors conforming to Recommendation\ G.164 and\ G.161 may be used. .FE may obscure the true problem. Furthermore the consquence of trying to concentrate too may trunk channels onto too few bearers may be simply to increase the calling rate and to reduce the call holding time. This may result in greatly reduced quality, especially where continuously compelled signalling systems are used, and in levels of trunk channel activity far above what was envisaged in the original system dimensioning. .PP Two possible criteria for acceptable speech performance are: an average of 3.7\ bits per sample and les than two\ per\ cent probability of clipping exceeding 50\ ms, or alternatively less than 0.5\ per\ cent of speech lost due to clipping. .PP Using the above criteria, approximations have been derived that relate the percentage of voice\(hyband data and the number of trunk channels to the gain of a DCME using 30\ bearer channels. These approximations are intended for use in initial system dimensioning and are as follows: .RT .LP \fIG\fR = 0.42 + 0.73 (log\fI\fI ) for less than 7% voice\(hyband data, .EF '% \fIe\ T'' .OF '''\fIe\ T %' .LP \fIG\fR = \(em1.15 + log\fI\fI for less than 15% voice\(hyband data, .EF '% \fIe\ T'' .OF '''\fIe\ T %' .LP where .LP \fIG\fR Gain .LP \fIT\fR Number of trunk channels. .PP These simple approximations are only valid for between 30 and 150\ trunk channels with a channel activity of 37\ per\ cent. If operation with fewer bearer channels is envisaged, then the approximations given above will tend to overestimate the achievable gain and this must be taken into account. If a more accurate representation is required, it will be necessary to carry out a first order Markov chain analysis referred to in the literature on\ DSI\ [1], [2], [3]. .sp 1P .LP 3.5 \fIISDN bearer services\fR .sp 9p .RT .PP DCMS are generally required to carry the full range of ISDN bearer services which can be provided on a 64\ kbit/s channel as specified in Recommendation\ I.231. These are: .RT .LP \(em circuit mode 64 kbit/s unrestricted, 8 kHz structured bearer service category. .LP This category may be used among other things for speech, multiple sub\(hyrate information streams multiplexed by the user, or for transparent access to an\ X.25 public network. .bp .LP \(em circuit mode 64 kbit/s, 8 kHz structured bearer service category, usable for speech information transfer. .LP This is broadly similar to the preceding category, but with different access protocols. .LP \(em circuit mode 64 kbit/s, 8 kHz structured bearer service category, usable for 3.1\ kHz audio information transfer. .LP This bearer service provides the transfer of 3.1 kHz bandwith audio information, for example voice\(hyband data via modems, Group\ I, II and\ III facsimile information, and speech. .LP \(em circuit mode alternate speech/64\ kbit/s unrestricted 8 kHz structured bearer service category. .LP This service is similar to both the unrestricted and speech 64\ kbit/s circuit\(hymode bearer services, but provides for the alternate transfer of either voice or unrestricted digital information at 64\ kbit/s within the same call. .sp 1P .LP 3.6 \fIRestoration of services\fR .sp 9p .RT .PP For most applications, the loss of traffic under failure conditions would be such that the installation of a single pair of terminals on a route would be insufficient without a means of rapid changeover to spare equipment in the event of failure. This means that DCME is often used in a cluster of\ \fIn\fR active terminals and one standby terminal to be loaded with the configuration information of the failed terminal. Other automatic fallback modes may be considered. .PP Failure of the transmission system between DCME terminals can be handled by normal transmission system restoration procedures. Failure of the transmission systems entering the DCME terminals from the exchanges may result in a wide range of different alarm conditions being experienced, particularly where a multi\(hydestination DCME terminal serves more than one exchange and more .PP than one route. It is desirable to limit the generation of alarm conditions to the channels which have actually failed. .RT .sp 1P .LP 3.7 \fIControl of transmission overload\fR .sp 9p .RT .PP A reduction in the number of bearer channels available to the interpolation process can occur due to high activity of voice\(hyband and 64\ kbit/s data services or statistical variations in the ensemble input speech activity. This can lead to overload, where the number of instantaneously active trunk channels exceeds the number of available bearer channels. Action is then required to safeguard speech quality. There are four possible solutions: .RT .LP \(em The system can be dimensioned so that with the maximum anticipated short\(hyterm trunk channel activities there is negligible probability of violating the speech quality criteria. This employs the DCMS very inefficiently outside the busy hour. .LP \(em A multi\(hydestination system can be made to carry routes with widely different busy hours, so that although the trunk channels might have relatively low non\(hybusy hour occupancy, the bearer channels would always be well loaded. .LP \(em Signals can be sent from the DCME to the exchange to busy\(hyout part of the route when the quality criteria are violated. This is known as Dynamic Load Control (DLC), and can be an effective control method. However, it cannot be retroactive and it is slow to take effect. Furthermore, care must be taken to ensure that when circuits are returned to service the increase in bearer channel activity is not sufficient to result in the immediate reapplication of\ DLC. .LP \(em The signal\(hyto\(hyquantization performance can be traded against the clipping of speech burst. By using variable rate ADPCM algorithms, it is possible to quantize to three, rather than four, bits on individual speech channels on a pseudo\(hycyclic basis for a given number of samples. In this way the system can be given a gradual degradation characteristic, rather than a sudden overloading. .PP Practical DCMS are likely to require some or all of these techniques to be used. .bp .sp 1P .LP 3.8 \fIControl channel\fR .sp 9p .RT .PP Because the assignment of trunk channels to bearer channels is continually changing , it is necessary to provide a control information channel between the transmit and the receive units to ensure that their assignment maps correspond. This channel carries information for assignments, changes of coding rates, message refreshments, 64\ kbit/s channel allocations and other system and management messages. It should be carried in a permanently allocated time slot which includes forward error correction, so that transmission errors do not cause the transmit and receive assignment maps to go out of step. .RT .sp 2P .LP \fB4\fR \fBDCME functions\fR .sp 1P .RT .PP This Recommendation is applicable to DCME designs in both directions of transmission. .PP The purpose of DCME is to provide maximum effective use of transmission facilities in the digital operating environment, using\ DSI and\ LRE techniques. At a minimum, the DCME functions shall include: .RT .LP \(em interpolation of speech signals (DSI); .LP \(em transcoding of 64 kbit/s PCM to ADPCM (LRE) when applicable; .LP \(em the means to carry the ISDN bearer services given in \(sc 4.4; .LP \(em one or more of the following operating modes: .LP i) point\(hyto\(hypoint, .LP ii) multi\(hyclique, .LP iii) multi\(hydestination; .LP \(em speech detection; .LP \(em voice\(hyband data detection; .LP \(em a means for transmit detection and receive injection of background noise; .LP \(em the means to accommodate non\(hyinterpolated preassigned traffic; .LP \(em a means for interterminal communication (control channel); .LP \(em a means for exchanging signals with an ISC for purposes of ISDN bearer services involving 64\ kbit/s unrestricted taffic, DLC, and alarms; .LP \(em time slot interchange; .LP \(em the ability to support the signalling systems identified in \(sc\ 4.12. .sp 1P .LP 4.1 \fIDigital speech interpolation\fR .sp 9p .RT .PP The DCME shall incorporate digital speech interpolation (DSI) techniques to achieve a reduction in the composite transmission rate of the 64\ kbit/s trunk channels. .RT .sp 1P .LP 4.2 \fIDCME low rate encoding algorithm\fR .sp 9p .RT .PP The DCME shall operate with a nominal low rate encoding gain of 2:1 through the use of adaptive differential pulse code modulation (ADPCM) techniques. The DCME shall incorporate the algorithms defined in Recommendation\ G.721 and\ G.723. These algorithms include provisions for transcoding the 64\ kbit/s\ PCM input signal to 24\ kbit/s ADPCM during overload conditions, to 32\ kbit/s ADPCM during normal operation, and to 40\ kbit/s for voice\(hyband data. .RT .sp 1P .LP 4.3 \fIDCME gain\fR .sp 9p .RT .PP The DCME shall combine digital speech interpolation and low rate encoding techniques to achieve a reduction in the composite transmission rate of the 64\ kbit/s trunk channels. .RT .sp 1P .LP 4.4 \fIDCME bearer services\fR .sp 9p .RT .PP The DCME shall respond to the following ISDN bearer service requests from its associated ISCs: .RT .LP a) speech; .LP b) 3.1 kHz audio (data and speech); .LP c) 64 kbit/s unrestricted. .bp .sp 1P .LP 4.5 \fIOperational modes\fR .sp 9p .RT .PP The following three modes of operation are described: .RT .LP a) point\(hyto\(hypoint; .LP b) multi\(hyclique; and .LP c) multi\(hydestination. .sp 1P .LP 4.5.1 \fIPoint\(hyto\(hypoint mode\fR | (see Figure 1/G.763) .sp 9p .RT .PP The transmit side DCME concentrates \fIN\fR trunk channels at 64\ kbit/s into \fIN\fR /\fIG\fR \ transmission channels. The transmission channels represent a number of time shared variable bit rate (bearer) channels which are grouped into a primary rate multiplex format. .PP At the receive side, the receiving DCME simply demultiplexes the primary\(hyrate format and reconstitutes the \fIN\fR \ trunk channels from the \fIN\fR /\fIG\fR \ transmission channels. .RT .sp 1P .LP 4.5.2 \fIMulti\(hyclique mode\fR | (see Figure 2/G.763) .sp 9p .RT .PP In this mode the pool of bearer channels is subdivided into two or three independant pools (cliques) of fixed capacity, each pool corresponding to an individual destination While the aggregate bearer bit rates for both the transmit side and the receive side are equal, the DCMG of each clique may be different, since this gain is a function of the number of input channels, routed within each clique. .PP It is desirable to limit the number of cliques within a primary\(hyrate bearer to two or three. Figure\ 2/G.763 indicates one from of this approach in which the primary\(hyrate bearer circuit is assumed to be available to each of the\ DCM nodes, but each node has the capability of preselecting the traffic that is intended for it. .RT .sp 1P .LP 4.5.3 \fIMulti\(hydestination mode\fR | (see Figure 3/G.763) .sp 9p .RT .PP In this mode, the input trunk channels are interpolated over a common pool of bearer channels, regardless of their destination. The input trunk channels are destination preassigned so that they may be routed to the appropriate destination in accordance with the assignment channel messages. This operational mode permits higher\ DCM gains that the multi\(hyclique mode, but its usefulness is limited if the\ DCME is located at the\ ISC. .RT .sp 2P .LP 4.6 \fIActivity detector\fR .sp 1P .RT .sp 1P .LP 4.6.1 \fIPurpose\fR .sp 9p .RT .PP The purpose of the activity detector is to recognize when a valid signal is applied to the input of the\ DCME, which results in a request for an available bearer channel for transmission of the valid signal. The activity detector must: .RT .LP a) detect low\(hylevel activity on a quiet input trunk channel; .LP b) reject high\(hylevel noise on an input trunk channel; .LP c) avoid introducing front end clipping on signals; .LP d) minimize false operation on impulse noise; .LP e) avoid clipping during a signalling sequence; .LP f ) avoid clipping on facsimile messages during page changes. .sp 1P .LP 4.6.2. \fIActivity detector characteristics\fR | (under study) .sp 9p .RT .PP The activity detector characteristics are based upon the assumption that the frequency response of the transmission channel up to the input of the activity detector is \(+- | .5\ dB with respect to 1020\ Hz over the frequency band from\ 300 to 3400\ Hz, and that the level of any single audio frequency, measured selectively on an idle channel, should not exceed \(em50\ dBm0. .RT .sp 1P .LP 4.6.2.1 \fIOperating threshold and operation time for variable threshold\fR .sp 9p .RT .PP The transmit activity detector threshold shall automatically adjust relative to the average power of Gaussian noise band limited between 300\ to 3400\ Hz. .PP The threshold and operate time of the transmit activity detector may operate in a manner which is equivalent to an activity detector with the characteristics given below (see note). .bp .PP \fINote\fR \ \(em\ All parameter values are provisional and under study. .RT .LP \fIAverage signal power\fR \fIOperate time\fR .LP < \(em40 dBm0 OFF .LP \(>=" \(em40 dBm0, \(= \(em30 dBm0 Figure 4/G.763 .LP > \(em30dBm0 2 ms < \fIt\fR < 4 ms .PP The operate time requirements will be satisfied while permitting tolerances on the average signal power of any stimulus signal in the frequency band at boundary conditions as follows: .LP \(em40 dBm0 \(+- | .5 dB .LP \(em30 dBm0 \(+- | .0 dB .PP The rate of change of the transmit activity detector adaptive threshold will be between 2.5\ dB/s and 20.0\ dB/s. .LP .rs .sp 32P .ad r \fBFigure 4/G.763, p.\fR .sp 1P .RT .ad b .RT .sp 1P .LP 4.6.2.2 \fIInteraction of the transmit activity detector with echo control\fR \fIdevices\fR .sp 9p .RT .PP The threshold of the transmit activity detector shall not adapt to Gaussian noise level variations which are due to the actions of echo suppressors or echo cancellers. This may be accomplished by any means which is functionally equivalent to providing an inhibit signal from a receive activity detector when activity is present in the receive channel. .bp .RT .sp 1P .LP 4.6.2.3 \fIHangover time\fR .sp 9p .RT .PP The permissible hangover time as a function of stimulus signal duration shall be within the mask shown in Figure\ 5/G.763 for Signalling System\ No.\ 5 and within the mask shown in Figure\ 6/G.763 for Signalling Systems\ No.\ 6, 7 and\ R2D. .PP It shall be possible to select the required type of hangover time mask. For voice\(hyband data, the hangover time should be extended so that it is sufficiently long to bridge FAX page changes. This time may be as long as 14\ s. .RT .LP .rs .sp 25P .ad r \fBFigure 5/G.763, p.\fR .sp 1P .RT .ad b .RT .LP .rs .sp 15P .ad r \fBFigure 6/G.763, p.\fR .sp 1P .RT .ad b .RT .LP .bp .sp 2P .LP 4.7 \fIData/speech discrimination\fR .sp 1P .RT .sp 1P .LP 4.7.1 \fIPurpose\fR .sp 9p .RT .PP The DCME data detector shall be capable of discriminating between voice\(hyband data and speech. This discrimination is necessary in order to assign the voice\(hyband data signal to a non\(hyoverloaded bearer channel and to eliminate or minimize front end clipping of the data signal. .RT .sp 1P .LP 4.7.2 \fIData/speech discrimination characteristics\fR .sp 9p .RT .PP Most of the V\(hySeries modems use the 2100 Hz disabling tone for the purpose of disabling echo control devices. The 2100\ Hz echo control disabling signal shall be used to identify those input trunk channels where the active signal is in\(hyband data originating from 2\(hywire\ PSTN data modems. Upon detecting the 2100\ Hz disabling tone with or without phase reversal (see Recommendation\ V.25), a particular call shall be designated as data through the\ DCME. .RT .sp 1P .LP 4.8 \fIControl channel\fR .sp 9p .RT .PP The control channel shall include provisions for accommodating the following categories of inter DCME\(hyterminal messages: .RT .LP \(em trunk\(hyto\(hybearer assignment; .LP \(em idle noise level; .LP \(em dynamic load control; .LP \(em alarm information; .LP \(em self diagnostic information; .LP \(em signal classification. .PP In addition, the control channel shall include DCME frame synchronization and the messages shall be protected against bit errors occurring on the bearer channel. .PP A dedicated 32 kbit/s channel shall be used; however, the precise format and operation is under study. .RT .sp 1P .LP 4.9 \fICommunication to the ISC\fR .sp 9p .RT .PP The DCME shall communicate with the ISC in accordance with Recommendation\ Q.50. .RT .sp 1P .LP 4.9.1 \fIDynamic load control\fR \fI(DLC)\fR .sp 9p .RT .PP The DCME shall generate dynamic load control messages for the following two categories of traffic: .RT .LP a) speech and 3.1 kHz audio, and .LP b) 64 kbit/s unrestricted. .PP The DCME shall provide a dynamic load control signal which may be sent to the local and distant telephone switching centres to limit the traffic load presented to the\ DCME during overload conditions. The dynamic load control signal is activated by monitoring load parameters for the interpolated speech and the 64\ kbit/s unrestricted channels. .PP Overload conditions should be indicated by the average number of bits per sample calculated for each clique. When the value falls below a particular, previously set threshold level, the\ DLC message should be generated at the\ DCME. DLC\ messages shall be sent back to the local ISC(s), and the distant\ DCME shall be informed through the control channel. The distant\ DCME shall interpret and appropriately convey the\ DLC information to its associated ISC(s). .PP The DLC condition shall be reset automatically when the average number of bits per sample exceeds a second, previously set threshold. .RT .sp 1P .LP 4.9.2 \fIDynamic load control activation/deactivation criteria\fR .sp 9p .RT .PP Speech and 3.1 kHz audio dynamic load control activation messages shall be generated when the average number of bits per sample drops below a preset threshold. .bp .PP The 64 kbit/s unrestricted dynamic load control activation messages shall be generated when: .RT .LP a) the measured number of assigned 64 kbit/s unrestricted channels exceeds a preset threshold, or .LP b) the speech and 3.1 kHz audio dynamic load control has been activated, or .LP c) the speech and 3.1 kHz audio dynamic load control is expected to be activated due to an increase of one additional channel in the 64\ kbit/s unrestricted traffic loading. .PP Dynamic load control activation shall occur immediately upon satisfying the threshold criteria. Dynamic load control deactivation messages shall be generated when the average number of bits per sample exceeds a preset threshold or the number of 64\ kbit/s unrestricted channels falls below a preset threshold. If the 64\ kbit/s dynamic load control is not active, 64\ kbit/s unrestricted channel requests shall not be refused. Dynamic load control deactivation shall not occur earlier than a programmable interval which has a minimum of 10\ s. .sp 1P .LP 4.9.3 \fIEstablishment and release of 64 kbit/s unrestricted class\fR \fIconnections\fR .sp 9p .RT .PP The DCME shall establish/release 64 kbit/s unrestricted duplex connections under control of the seizing/releasing\ ISC as part of the call set\(hyup/clearing process between exchanges. Dedicated seizure/select and release messages and the associated acknowledgement messages are exchanged between the\ DCME and the\ ISC as defined in Recommendation\ Q.50. .PP Subject to the capability of the ISC, this process is usable for performing the in\(hycall modifications between the DCMEs during alternate speech/64\ kbit/s unrestricted type calls. .PP Upon reception of a seizure/select message from the ISC for a trunk, the\ DCME shall perform the necessary internal checks, including the 64\ kbit/s unrestricted dynamic load control status, for the accommodation of this call and an acknowledgement (positive or negative) message shall be returned as soon as possible to the calling\ ISC. The calling end\ DCME shall initiate the establishment of the unrestricted 64\ kbit/s forward connection to the called end\ DCME using a special identifier in the assignment message. The called end DCME, upon receipt of this message, shall automatically initiate the .PP establishment of the unrestricted 64\ kbit/s return connection. Failure to complete the establishment of a 64\ kbit/s circuit between DCMEs shall be reported to the\ ISC as soon as this has been detected internally. This reporting shall be in the form of an out\(hyof\(hyservice message. .PP Upon receipt of a release message from the calling ISC, the releasing end\ DCME shall initiate the release of the unrestricted 64\ kbit/s forward connection, and the opposite end\ DCME shall automatically initiate the release of the unrestricted 64\ kbit/s return connection. Upon completion of this process, a positive release acknowledgement message shall be returned to the releasing\ ISC. Failure to complete the release shall be reported to the releasing\ ISC using the out\(hyof\(hyservice message and the\ DCME shall put the trunk in a blocked condition. .PP After manual or automatic removal of any failure condition, the DCME shall put the trunk in an idle condition and send a back\(hyin\(hyservice message to the\ ISC. .PP A calling end DCME shall detect a release initiated by the opposite end (non\(hycontrolling)\ ISC by the reception of a disconnect message in the control channel. This abnormal release shall be recognized as a dual seizure situation being resolved between the\ ISCs. The detecting\ DCME shall first complete the release normally and immediately attempt to re\(hyestablish the released 64\ kbit/s unrestricted duplex connection between the DCMEs. .RT .sp 1P .LP 4.10 \fITrunk channel idle noise level detection and injection\fR .sp 9p .RT .PP The DCME transmit unit shall measure the trunk channel idle noise level and forward this information to the corresponding\ DCME receive unit, which shall insert the appropriate idle level noise within the receive output speech channel during silent intervals following disconection of the bearer channel. The idle level noise shall not be inserted on 64\ kbit/s unrestricted channels. .RT .sp 1P .LP 4.11 \fITime slot interchange (TSI)\fR .sp 9p .RT .PP The DCME shall include a time slot interchange capability on the trunk side interface so that a given time slot at the transmit unit can be assigned to any time slot on the receive unit. .bp .RT .sp 1P .LP 4.12 \fISignalling transmission\fR .sp 9p .RT .PP The DCME shall support the following signalling systems: .RT .LP \(em Signalling System No. 5 .LP \(em Signalling System No. 6 (both analogue and digital versions) .LP \(em Signalling System No. 7 .LP \(em Signalling System R1 under study (Note 1) .LP \(em Signalling System R2 (Note 2) .PP Signalling detection is under study. .PP \fINote\ 1\fR \ \(em\ Signalling System R1 may be supported, but a special signalling interface will be required. .PP \fINote\ 2\fR \ \(em\ Transmission of R2D line signalling in the control channel is recommended. .RT .sp 1P .LP 4.13 \fIVoice\(hyband data transmission\fR .sp 9p .RT .PP Once a voice\(hyband data call is recognized by the DCME, the DCME system shall not introduce any degradation to the voice\(hyband data block error rate performance beyond that normally encountered by a single encoding of the ADPCM codec used inthe\ DCME for voice\(hyband data tansmission. .RT .sp 1P .LP 4.14 \fIEcho protection\fR .sp 9p .RT .PP The DCME shall not activate transmission in the transmit direction as the result of receive signals. Such activation increases the apparent speech activity factor and reduces the\ DCME gain. Therefore, echo in the transmit signal resulting from the receive signal must be removed, but this echo control function is not required to be a part of the\ DCME. .PP A network echo control device meeting or exceeding the requirements of Recommendations\ G.165, G.164 or\ G.161 is required on all trunk channels carrying speech serviced by a\ DCME .FS The French Administration has indicated that improved echo suppressor performance, superior to Recommendations\ G.164 and\ G.161, can be achieved by incorporating an echo suppressor within the\ DCME, because advantage can be taken of the more sophisticated speech detection incorporating a delay line to reduce break\(hyin and double\(hytalk clipping. .FE .RT .sp 1P .LP 4.15 \fIBearer channel preassignment\fR .sp 9p .RT .PP The DCME shall permit trunk channels to be preassigned to bearer channels. The 64\ kbit/s trunk channels may be preassigned to any of the following: .RT .LP \(em channels subject to 32 kbit/s ADPCM, .LP \(em channels subject to 40 kbit/s ADPCM, .LP \(em channels transmitted using 64 kbit/s. .sp 2P .LP \fB5\fR \fBInterfaces\fR .sp 1P .RT .PP The transmission interface to the international switching centre (ISC) or national transmission medium (trunk side) shall be at the primary hierarchical rates of either 2048\ kbit/s or 1544\ kbit/s. The transmission interface to the national or international transmission medium (bearer side) shall be at either 2048\ kbit/s or 1544\ kbit/s. The data rates on the trunk and bearer sides are normally the same. .PP In the case of interworking between the 1544 kbit/s and 2048 kbit/s hierarchies on the same\ DCMS, it is recommended in Recommendation\ G.802 that the bearer system should be 2048\ kbit/s. Nevertheless, there may be operational difficulties with such interworking depending on whether the\ DCME is Type\ 1, where the\ DCME cannot communicate with the\ ISC, or Type\ 2, where it can, as defined in Recommendation\ Q.50. .RT .sp 2P .LP 5.1 \fITransmission interface; trunk side\fR .sp 1P .RT .sp 1P .LP 5.1.1 \fITrunk side interface at 2048 kbit/s\fR \v'3p' .sp 9p .RT .LP a) The electrical characteristics shall comply with Recommendation\ G.703. The test load impedance shall be either 75\ ?73 unbalanced or 120\ ?73 balanced depending on the user requirement. .bp .LP b) The frame structure shall comply with Recommendation G.704. .LP c) The encoding law for voice frequency signals shall conform to the A\(hylaw system described in Recommendation\ G.711. .sp 1P .LP 5.1.2 \fITrunk side interface at 1544 kbit/s\fR \v'3p' .sp 9p .RT .LP a) The electrical characteristic shall comply with Recommendation\ G.703. The line code adopted shall be either\ AMI or B8ZS depending on the user requirement. .LP b) The frame stucture shall comply with Recommendation G.704. The multiframe size shall be either 24\ frames or 12\ frames depending on the user requirement. .LP c) The encoding law for voice frequency signals shall conform to the \(*m\(hylaw system described in Recommendation\ G.711. .LP 5.2 \fITransmission interface: bearer side\fR .sp 1P .RT .sp 2P .LP 5.2.1 \fIBearer side interface at 2048 kbit/s\fR .sp 1P .RT .sp 1P .LP 5.2.1.1 \fIElectrical characteristics\fR .sp 9p .RT .PP The electrical characteristics shall comply with Recommendation\ G.703. The test load impedance shall be either 75\ ?73 unbalanced or 120\ ?73 balanced depending on the user requirement. .RT .sp 1P .LP 5.2.1.2 \fIBearer frame structure\fR .sp 9p .RT .PP The bearer frame structure shall comply with Recommendation\ G.704. Time slot\ 0 shall be used as recommended in Recommendation\ G.704 and time slots\ 1 to 31\ shall carry control channels and traffic according to the\ DCME frame structure. .RT .sp 2P .LP 5.2.2 \fIBearer side interface at 1544 kbit/s\fR .sp 1P .RT .sp 1P .LP 5.2.2.1 \fIElectrical characteristics\fR .sp 9p .RT .PP The electrical characteristics shall comply with Recommendation\ G.703. The test load impedance shall be 100\ ?73 resistive. .RT .sp 1P .LP 5.2.2.2 \fIBearer frame structure\fR .sp 9p .RT .PP The bearer frame structure shall comply with Recommendation\ G.704. .PP Provisions shall be included in the bearer frame structure to accomodate control channels and traffic according to the\ DCME frame structure. .PP The 193\ur\d\ud\d bit shall be used for frame synchronization as recommended in Recommendation\ G.704. .RT .sp 1P .LP 5.3 \fIControl interfaces to switching equipment (at the ISC)\fR .sp 9p .RT .PP The choice of interface is considered to be a national matter and left for each Administration to define within the constraints of their transmission facilities and\ ICSs. .PP The control interface to the switching equipment is dependent on the capability of the\ ISC and the facilities between the\ ISC and the\ DCME (see Recommendation\ Q.50). .RT .sp 1P .LP 5.4 \fIMan\(hymachine interface\fR .sp 9p .RT .PP The DCME shall contain a system command structure which serves as a menu\(hydriven interface between internal functions and the system operator. Typically two RS\ 232C/V24 ports are necessary to provide operator access to the equipment: one for a display terminal and one for a printer. .RT .sp 2P .LP 5.5 \fIOperations function interface(s)\fR .sp 1P .RT .sp 1P .LP 5.5.1 \fITrunk side operation at 2048 kbit/s or 1544 kbit/s\fR .sp 9p .RT .PP The utilization of spare bits for monitoring and error protection shall be in accordance with Recommendations\ G.704 and\ G.706. .PP Details covering the use of the above in an equipment specification are under study. .bp .RT .sp 2P .LP 5.5.2 \fIBearer side\fR .sp 1P .RT .sp 1P .LP 5.5.2.1 \fISingle destination mode\fR .sp 9p .RT .PP The utilization of spare bits for monitoring and error protection is under study. .RT .sp 1P .LP 5.5.2.2 \fIMulti\(hyclique or multi\(hydestination mode\fR .sp 9p .RT .PP The utilization of spare bits for monitoring and error protection is under study. .RT .sp 1P .LP 5.6 \fILocal alarms interface (provisional)\fR .sp 9p .RT .PP The DCME must present alarms to the local entity according to the user's requirement. The choice of the physical/electrical interface is to be decided by the individual Administration. In the case of individual voltage\(hyfree loop alarms, the categories of alarm in Recommendation\ G.803 should be included. In the case of a serial alarm interface, it is recommended to provide as a minimum the following signals: .RT .LP a) initial occurrence of an alarm in the monitored DCME; .LP b) initial ocurrence of a clear in the monitored DCME; .LP c) receipt of a data request from the local entity; .LP d) initial system power\(hyon. .PP \fINote\fR \ \(em\ The inclusion of Telecommunications Management Network (TMN) protocols and interface requirements in future\ DCME Recommendations is planned. .sp 2P .LP 5.7 \fIExternal clock interface\fR .sp 1P .RT .sp 1P .LP 5.7.1 \fIDCME working with 2048 kbit/s transmission interfaces\fR .sp 9p .RT .PP The external clock interface shall comply with Recommendation\ G.703, \(sc\ 10.3. The test load impedance shall be either 75\ ?73 unbalanced or 120\ ?73 balanced depending on the user requirement. .RT .sp 1P .LP 5.7.2 \fIDCME working with 1544 kbit/s transmission interfaces\fR .sp 9p .RT .PP The timing normally derived from an incoming digital link at 1544\ kbit/s complying with Recommendation\ G.703, \(sc\ 2. Where required an external clock interface may be provided. .RT .sp 2P .LP \fB6\fR \fBTiming synchronization\fR .sp 1P .RT .sp 1P .LP 6.1 \fIGeneral\fR .sp 9p .RT .PP Timing synchronization of DCME can be achieved in many ways and care should therefore be taken in any implementation to ensure that the configuration adopted is correct. .RT .sp 1P .LP 6.1.1 \fIReference clock\fR .sp 9p .RT .PP The DCME reference clock shall be derived from a source which meets the requirement of Recommendation\ G.811. For networks that entail one international destination, loop timing can be used as an alternative at one end of the link. The need for an internal reference clock for use under failure conditions is for further study. .RT .sp 1P .LP 6.1.2 \fIPlesiochronous slips\fR .sp 9p .RT .PP The slip rate shall not exceed the requirements of Recommendation\ G.822. Controlled slips at 2048\ kbit/s on the trunk side shall be 2\ frames, controlled slips at 1544\ kbit/s and on the bearer side require further study. .RT .sp 1P .LP 6.1.3 \fIBuffer sizes and locations\fR .sp 9p .RT .PP Table 1/G.763 indicates suitable buffer sizes and locations for the 2048\ kbit/s hierarchy for the various synchronization options which are detailed in Appendix\ I. A table for the 1544\ kbit/s hierarchy is under study. .bp .RT .ce \fBH.T. [T1.763]\fR .ce TABLE\ 1/G.763 .ps 9 .vs 11 .nr VS 11 .nr PS 9 .TS center box; cw(60p) | cw(48p) | cw(36p) | cw(48p) | cw(36p) . Synchronization type (Note 1) Buffer size (Note 2) Slip size (Note 3) Location (Note 4) Figure No. of Appendix I _ .T& lw(60p) | lw(48p) | lw(36p) | lw(48p) | lw(36p) . \fINo buffering\fR .T& lw(60p) | cw(48p) | cw(36p) | cw(48p) | lw(36p) . Asynchronous No buffer \(em \(em I\(hy1/G.763 .T& lw(60p) | cw(48p) | cw(36p) | cw(48p) | lw(36p) . Synchronous No buffer \(em \(em { I\(hy2/G.763, I\(hy12/G.763, I\(hy15/G.763 } .T& lw(60p) | cw(48p) | cw(36p) | cw(48p) | lw(36p) . { Synchronous analogue\(hyto\(hydigital } No buffer \(em \(em I\(hy5/G.763 _ .T& lw(60p) | cw(48p) | cw(36p) | cw(48p) | lw(36p) . { \fIPlesiochronous buffering\fR } .T& lw(60p) | cw(48p) | cw(36p) | cw(48p) | lw(36p) . Asynchronous 0.5 ms 2 frames Trunk side I\(hy3/G.763 .T& lw(60p) | cw(48p) | cw(36p) | cw(48p) | lw(36p) . Synchronous 0.5 ms 2 frames Bearer side { I\(hy4/G.763, I\(hy13/G.763, I\(hy16/G.763 } _ .T& lw(60p) | cw(48p) | cw(36p) | cw(48p) | lw(36p) . { \fIPlesiochronous/doppler buffering\fR } .T& lw(60p) | cw(48p) | cw(36p) | cw(48p) | lw(36p) . Synchronous 1.7 ms 2 frames Bearer side { I\(hy6/G.763, I\(hy11/G.763, I\(hy14/G.763, I\(hy17/G.763, I\(hy19/G.763 } .T& lw(60p) | cw(48p) | cw(36p) | cw(48p) | lw(36p) . Synchronous 2.4 and 1.7 ms Bearer side and trunk side I\(hy7/G.763 .T& lw(60p) | cw(48p) | cw(36p) | cw(48p) | lw(36p) . Asynchronous 1.7 ms 2 frames Trunk side I\(hy9/G.763 .T& lw(60p) | cw(48p) | cw(36p) | cw(48p) | lw(36p) . Synchronous 2.4 and 1.7 ms Trunk side and bearer side I\(hy8/G.763 .T& lw(60p) | cw(48p) | cw(36p) | cw(48p) | lw(36p) . Synchronous 1.7 ms 2 frames Trunk side { I\(hy10/G.763, I\(hy18/G.763 } .TE .LP \fINote\ 1\fR \ \(em\ Asynchronous refers to the case where the transmit unit and receive unit of the same DCME terminal are deriving their timing from different clock sources. .LP \fINote\ 2\fR \ \(em\ Buffer sizes are derived from the following: .LP \(em\ single doppler with plesiochronous buffer: (0.6\ ms \(mu 2) + 0.5\ =\ 1.7\ ms; .LP \(em\ double doppler buffer: 1.2\ ms \(mu 2\ =\ 2.4 ms; .LP \(em\ plesiochronous buffer for 2\ PCM (2048\ kbit/s) frames: 0.5\ ms. .LP The doppler buffer size used is an example for a specific satellite. These buffer sizes may need to be adjusted taking into account the orbital parameters of the satellite in use. .LP \fINote\ 3\fR \ \(em\ The slip size of 2 PCM frames is based upon the requirement in the 2048 kbit/s frame to maintain frame alignment. .LP \fINote\ 4\fR \ \(em\ In general it is preferable to avoid placing the plesiochronous slip buffers on the bearer side of the DCME to minimize disruptions caused by slips. This may not be possible under all circumstances. .LP } _ .TE .nr PS 9 .RT .ad r \fBTable 1/G.763 [T1.763], p.\fR .sp 1P .RT .ad b .RT .sp 1P .LP 6.1.4 \fITerminal synchronization\fR .sp 9p .RT .PP The DCME terminal shall be capable of deriving its timings from any of the incoming digital links or from an external clock. When the synchronization is derived from the trunk receive side, it is recommended that a fallback trunk receive synchronization source is allocated in the event of the primary channel receiving an alarm condition indicating a received line signal failure, loss of frame alignment, AIS or receive BER\ \(>="\ 10\uD\dlF261\u3\d. Switching between primary and fallback sources shall be automatic. .bp .RT .sp 2P .LP \fB7\fR \fBPerformance\fR .sp 1P .RT .sp 1P .LP 7.1 \fISpeech performance\fR .sp 9p .RT .PP Recommendation P.84 .FS The specifications in Rec. P.84 are subject to future enhancement and therefore should be regarded as provisional. .FE describes a subjective test method for comparing the performance of\ DCME systems against suitable reference conditions for carefully defined input signals. Recommendation\ P.84 consists of listening tests and is the recommended source of information about subjective testing of\ DCME. These tests are a first step and do not preclude the need for conversational tests. .PP It is recommended that a fixed delay be inserted in the transmit speech path to reduce the probability of front end clipping. This delay compensates for activity detection time and\ DCME assignment message connection delay. The delay should be such as to assure that the main speech spurt clipping is less than 5\ ms. .RT .sp 1P .LP 7.2 \fIVoice\(hyband data performance\fR .sp 9p .RT .PP Paragraph 2.3 refers to Recommendation G.721 (32 kbit/s ADPCM algorithms) and to Recommendation\ G.723 (24\ kbit/s and 40\ kbit/s algorithms derived from Recommendation\ G.721), which have been selected for use in\ DCME. Extensive testing has demonstrated satisfactory voice\(hyband data performance for the 40\ kbit/s algorithm specified in Recommendation\ G.723 for a voice\(hyband data rate of 9600\ bit/s. .PP Voice\(hyband data at rates greater than 9600 bit/s may be satisfactorily transmitted, but in any event a 64\ kbit/s unrestricted channel can be selected through the\ DCME which will accommodate voice\(hyband data rates at 14400\ bit/s. .RT .sp 2P .LP \fB8\fR \fBSystem management functions\fR .sp 1P .RT .sp 1P .LP 8.1 \fITransmission facilities\fR .sp 9p .RT .PP Each terminal should monitor each incoming digital link for the following conditions or parameters and store separate cumulative counts of each type of event as required by users: .RT .LP \(em AIS, remote alarm indication; .LP \(em loss of incoming signal, loss of frame alignment, reframe rate; .LP \(em severely errored seconds; .LP \(em degraded minutes; .LP \(em slips, slip rate. .sp 1P .LP 8.2 \fITerminal traffic handling performance\fR .sp 9p .RT .PP The DCMS terminals shall monitor and store records of the various parameters needed to evaluate the traffic handling performance being provided. .RT .sp 1P .LP 8.2.1 \fIMeasurement of statistics\fR (see Table 2/G.763) .sp 9p .RT .PP Measurements and calculations, other than for BER, shall be done only on non\(hypreassigned trunk channels which are defined in the configuration data. The DLC\(hyon ratio for voice/voice\(hyband data and the DLC\(hyon ratio for 64 kbit/s unrestricted traffic shall be obtained separately for each destination. All other parameters shall be obtained separately for each transmit pool. .PP The measurements of each parameter shall be made over Statistics Time Interval (STI) determined by the operator. Each statistic shall be calculated once every update interval (e.g.\ 30s), with the accumulated data from every sampled\ DCME frame (e.g. each 10th\ frame) over the previous averaging period (e.g. 1\ min). The average over the\ STI shall be the average of the values calculated each update interval during the\ STI within the range from 10\ min to 60\ min (in 10\ min steps). .PP The definitions of the Quality of Service and offered traffic statistics are given in Appendix\ II. .PP During the STI, the average BER shall be calculated at the end of each 1\ minute interval, the voice freezeout excess shall be calculated from the 1\ min values of voice queue freezeout fraction and the\ BER excess shall be calculated from the 1\ min values of average\ BER. .bp .PP The summary statistics calculated at the end of the STI shall be output to a statistics data file on a secure storage medium (e.g. non\(hyvolatile\ RAM, hard disk.\ etc.). .RT .ce \fBH.T. [T2.763]\fR .ce TABLE\ 2/G.763 .ce \fBDCME management statistics\fR .ps 9 .vs 11 .nr VS 11 .nr PS 9 .TS center box; cw(60p) | cw(84p) | cw(84p) . Service to be measured Quality of service statistics Offered traffic statistics _ .T& lw(60p) | lw(84p) | lw(84p) . Voice { \ (1) Bits per sample \ (2) Voice queue freezeout fraction \ (3) Voice freezeout excess } { \ (4) Voice activity ratio \ (5) DLC voice\(hyon ratio } _ .T& lw(60p) | lw(84p) | lw(84p) . Data { \ (6) Data queue freezeout fraction } \ (7) Data activity ratio _ .T& lw(60p) | lw(84p) | lw(84p) . 64 kbit/s on demand { \ (8) 64 kbit/s failed seizures ratio } { \ (9) 64 kbit/s connected ratio (10) 64 kbit/s DLC\(hyon ratio } _ .T& lw(60p) | lw(84p) | lw(84p) . All services { (11) Average BER (12) BER excess (13) Severely errored seconds (14) Degraded minutes } .TE .LP \fINote\fR \ \(em\ Statistics (1) to (4) and (6) to (9) shall be calculated separately for each transmit pool. .LP Statistics (5) and (10) shall be calculated separately for each destination. .LP Statistics (11) and (12) shall be calculated separately for each receive control channel. .LP Statistics (13) and (14) shall be calculated separately for each incoming digital link according to Recommendation\ G.821. .nr PS 9 .RT .ad r \fBTableau 2/G.763 [T2.763], p.\fR .sp 1P .RT .ad b .RT .sp 1P .LP .sp 1 8.3 \fISynchronizer\fR .sp 9p .RT .PP The state of synchronization of each primary group interface, the selected clock source, and the times of any failures or changes of clock source should be monitored. .RT .sp 1P .LP 8.4 \fICommunication links\fR .sp 9p .RT .PP The condition of all communication links should be monitored to detect failures as far as practicable, including: .RT .LP \(em control channels; .LP \(em ISC\(hyDCME interface; .LP \(em man\(hymachine interface. .sp 1P .LP 8.5 \fIReports\fR .sp 9p .RT .PP The terminal should: .RT .LP a) at operator defined intervals, or when set parameters have been exceeded, or as a worst 15\(hyminutes report for any 24\ hours period, file operator selected parameters from those monitored and stored, including header information such as terminal identification, date, and measurement period covered by the file; .bp .LP b) compare selected parameters, status or measurements with predetermined conditions; .LP c) upon detection that predetermined conditions have been met or exceeded for a given period of time, take the necessary action(s) which may include: .LP 1) filing of an anomaly report; .LP 2) transmission of alarm signals; .LP 3) block all new calls due to failure; .LP 4) switch to standby, if available; .LP 5) total shut down of the terminal. .sp 1P .LP 8.6 \fISystem configuration\fR .sp 9p .RT .PP The terminal shall include a non\(hyvolatile back\(hyup memory containing a copy of the latest configuration of the\ DCME, for use in failure situations. A non\(hyworking spare copy should also be provided to allow changes in configuration to be made without impact upon service security. In cases where cluster operation of terminals is used to provide additional service security, means must be provided for the standby terminal to adopt the configuration of the working terminal which it is intended to replace. .PP The configuration information shall include details of trunk side interface channel connections, modes of operation of any preassigned channels, any restrictions in force to any destination or on any block of circuits (e.g. limit on the number of 64\ kbit/s calls). .RT .sp 1P .LP 8.7 \fIFailure strategy\fR .sp 9p .RT .PP Upon detection of conditions affecting the service, the DCME shall take the appropriate actions to protect existing traffic, such as switching to fallback timing sources or fallback units where redundancy is provided, transmission of\ DLC signals, disconnection of failed circuits, transmission of any appropriate alarm conditions. .RT .sp 2P .LP \fB9\fR \fBMaintenance functions and alarms\fR .sp 1P .RT .sp 1P .LP 9.1 \fIMaintenance functions\fR .sp 9p .RT .PP The DCME should provide the following maintenance functions: .RT .LP a) facilities for disabling (terminal out\(hyof\(hyservice test): .LP \(em digital speech interpolation; .LP \(em low rate encoding (ADPCM); .LP \(em variable bit rate coding; .LP b) facilities for providing fixed connections of specific trunk channels to specific bearer channels, at 32\ kbit/s without interpolation, 40\ kbit/s without interpolation and 64\ kbit/s interpolation; .LP c) facilities for protected monitoring points (under study). .sp 1P .LP 9.2 \fIDCME alarm conditions\fR .sp 9p .RT .PP Alarm conditions and the appropriate consequent actions are defined as follows: .RT .sp 1P .LP 9.2.1 \fINormal traffic carrying operating conditions\fR .sp 9p .RT .PP The following shall apply when the DCME is carrying traffic, when no digital links are exhibiting fault conditions and when the\ DCME is also not exhibiting a fault condition: .RT .LP a) the absence of alarm indications on the DCME terminal shall indicate a normal condition; .LP b) the means used on the DCME terminal to indicate operating modes or to provide routine information shall be of such form, colour or type that they cannot be confused with alarm conditions. .sp 1P .LP 9.2.2 \fITime delay\fR .sp 9p .RT .PP Optionally, a time delay, selectable up to three seconds maximum, shall be provided before alarms are initiated or indications are transmitted in fault conditions categories\ A, B, C and/or\ D of Table\ 3/G.763, as appropriate. .RT .sp 1P .LP 9.2.3 \fIFault conditions and consequent actions\fR .sp 9p .RT .PP Table 3/G.763 shows various fault conditions and consequent actions which are externally observable. .bp .RT .ce \fBH.T. [1T3.763]\fR .ce TABLE\ 3/G.763 .ce \fBConsequent actions\fR .ps 9 .vs 11 .nr VS 11 .nr PS 9 .TS center box; cw(58p) | cw(44p) | cw(44p) | cw(44p) | cw(38p) . Fault condition Alarm (Note 4) { Apply to bearer side, towards distant terminal (Note 5) } { Apply to trunk side of own network (Note 5) } Other action _ .T& cw(12p) | lw(46p) | lw(44p) | lw(44p) | lw(44p) | lw(38p) . A { Failure of incoming 1.5\(hy or 2\(hyMbit/s trunk from own network (Note 1) (See conditions G, E) } Prompt { Message in control channel to indicate which 64\ kbit/s trunks are affected } AIRE in affected trunk Management report | ua\d\u)\d _ .T& cw(12p) | lw(46p) | lw(44p) | lw(44p) | lw(44p) | lw(38p) . B { Failure of bearer from distant end (Note 1) (See condition F) } Prompt { Remote alarm messge in control channel and AIRE } AIS in all affected trunks Management report | ua\d\u)\d _ .T& cw(12p) | lw(46p) | lw(44p) | lw(44p) | lw(44p) | lw(38p) . C { AIS in incoming 1.5\(hy or 2\(hyMbit/s trunk from own network (See conditions G, E) } { Message in control channel to indicate which 64\ kbit/s trunks are affected } AIRE in affected trunk { Managements report | ua\d\u)\d } _ .T& cw(12p) | lw(46p) | lw(44p) | lw(44p) | lw(44p) | lw(38p) . D { AIS in bearer from distant end (See condition F) } { Remote alarm in control channel and AIRE } AIS in all affected trunks _ .T& cw(12p) | lw(46p) | lw(44p) | lw(44p) | lw(44p) | lw(38p) . E { Remote alarm indication in incoming 1.5\(hy or 2\(hyMbit/s trunk from own network (See conditions A, C) } { Message in control channel to indicate which 64\ kbit/s trunks are affected } Management report | ua\d\u)\d _ .T& cw(12p) | lw(46p) | lw(44p) | lw(44p) | lw(44p) | lw(38p) . F { Remote alarm message in control channel and AIRE (Note\ 2) (See conditions B, D) } { Extend remote alarm indication in all appropriate trunks (optional) } _ .T& cw(12p) | lw(46p) | lw(44p) | lw(44p) | lw(44p) | lw(38p) . G { Message in control channel of bearer to indicate failure or AIS in a 1.5\(hy or 2\(hyMbit/s trunk incoming from distant end (See conditions A, C) } { All \*Q1s\*U in affected 64\ kbit/s trunks and \*Qout of service\*U code via an ISC to DCME link } _ .T& cw(12p) | lw(46p) | lw(44p) | lw(44p) | lw(44p) | lw(38p) . H Timing source failure { Prompt if unprotected deferred if protected } { Management report | ua\d\u)\d and switch to fall back source when available } _ .TE .nr PS 9 .RT .ad r \fBTable 3/G.763 [1T3.763], p.\fR .sp 1P .RT .ad b .RT .LP .bp .ce \fBH.T. [2T3.763]\fR .ce TABLE\ 3/G.763\ \fI(continued)\fR .ps 9 .vs 11 .nr VS 11 .nr PS 9 .TS center box; cw(58p) | cw(44p) | cw(44p) | cw(44p) | cw(38p) . Fault condition Alarm (Note 4) { Apply to bearer side, towards distant terminal (Note 5) } { Apply to trunk side of own network (Note 5) } Other action _ .T& cw(12p) | lw(46p) | lw(44p) | lw(44p) | lw(44p) | lw(38p) . J { DCME failure (not power failure, but self\(hytest routine) } { Prompt is deferred depending upon nature of failure } { AIS, if necessary, dependent upon nature of failure (for prompt alarms only) } { AIS, if necessary, upon nature of failure (for prompt alarms only) } Management report | ua\d\u)\d _ .T& cw(12p) | lw(46p) | lw(44p) | lw(44p) | lw(44p) | lw(38p) . K DCME power failure { Prompt when service affecting, deferred otherwise } { AIS if possible when service affecting } { AIS if possible when service affecting } { Management report | ua\d\u)\d if possible } _ .T& cw(12p) | lw(46p) | lw(44p) | lw(44p) | lw(44p) | lw(38p) . L { Speech performance degraded (Note 3) } { Prompt or deferred, depending upon level of degradation } { \(em Management report | ua\d\u)\d \(em Apply DLC or STM as appropriate via the ISC DCME link } _ .T& cw(12p) | lw(46p) | lw(44p) | lw(44p) | lw(44p) | lw(38p) . M { 1.5\(hy or 2\(hyMbit/s trunk BER between 10\uD\dlF261\u6\d and 10\uD\dlF261\u3\d } Deferred Management report | ua\d\u)\d _ .T& cw(12p) | lw(46p) | lw(44p) | lw(44p) | lw(44p) | lw(38p) . N { Bearer BER between 10\uD\dlF261\u6\d and 10\uD\dlF261\u3\d } Deferred { Message in control channel to distant end } Management report | ua\d\u)\d _ .T& cw(12p) | lw(46p) | lw(44p) | lw(44p) | lw(44p) | lw(38p) . O { Receive message in control channel for BER between 10\uD\dlF261\u6\d and 10\uD\dlF261\u3\d } Deferred Management report | ua\d\u)\d _ .T& cw(12p) | lw(46p) | lw(44p) | lw(44p) | lw(44p) | lw(38p) . P { Control channel error rate exceeds threshold (under study) } Prompt { Remote alarm message in control channel and AIRE } AIS in all affected trunks { Management report | ua\d\u)\d } .TE .LP \ua\d\u)\d Denotes management report, printout or information storage for maintenance. .IP STM Synchronous transfer module .IP AIS Alarm indication signal .IP AIRE Alarm indication to remote end .LP \fINote\ 1\fR \ \(em\ The fault conditions are loss of incoming signal, loss of frame alignment or a bit error ratio greater than 10\uD\dlF261\u3\d as defined in Recommendations\ G.737, \(sc\ 4.1, and G.734, \(sc\ 3.1 for 2048 and 1544\ kbit/s digital links, respectively. .LP \fINote\ 2\fR \ \(em\ \*QFault condition\*U is a network condition. DCME should optionally pass on the condition transparently for recognition and action by own network. .LP \fINote\ 3\fR \ \(em\ The following conditions must exist before the alarm for speech performance degradation operates: .LP a) Deferred alarm: the average number of encoding bits per sample, as defined in Appendix II, is less than a present threshold determined by subjective criteria (for further study) for a period \*Qx\*U seconds (to be determined); .LP b) Prompt alarm: the \*Qvoice queue freezeout fraction\*U exceeds a selectable threshold (value under study). The possibility of additionnaly using \*Qvoice freezeout excess\*U and/or measuring the length of freezeout instances is also under study. .LP \fINote\ 4\fR \ \(em\ Recommendation G.803 defines the alarm categories. .LP \fINote\ 5\fR \ \(em\ The DCME shall not cause any indeterminate or unknown conditions when AIS is injected into its network, either on the trunk or the bearer side of the DCME. .nr PS 9 .RT .ad r \fBTable 3/G.763 [2T3.763], p.\fR .sp 1P .RT .ad b .RT .LP .bp .ce 1000 APPENDIX\ I .ce 0 .ce 1000 (to Recommendation G.763) .sp 9p .RT .ce 0 .ce 1000 \fBTiming synchronization\fR .sp 1P .RT .ce 0 .PP The following figures provide a number of examples of Doppler and plesiochronous slip buffer placements for a variety of network synchronization schemes. In the figures it is assumed that all buffers will derive their write clocks from the input bit stream. .sp 1P .RT .PP The following drawing convention is used: .LP . | | | | | Timing path .LP . | | | | | Traffic path. .sp 2P .LP I.1 \fIPoint\(hyto\(hypoint operation\fR .sp 1P .RT .sp 1P .LP I.1.1 \fITerrestrial operation within a national network\fR .sp 9p .RT .PP Figures I\(hy1/G.763 and I\(hy2/G.763 show methods of DCME terminal synchronization for operation within a national network. .RT .LP .rs .sp 15P .ad r \fBFigure I\(hy1/G.763, p. \fR .sp 1P .RT .ad b .RT .LP .rs .sp 14P .ad r \fBFigure I\(hy2/G.763, p. \fR .sp 1P .RT .ad b .RT .LP .bp .sp 1P .LP I.1.2 \fITerrestrial operation between national networks\fR .sp 9p .RT .PP Figures I\(hy3/G.763, I.4/G.763 and I.5/G.763 show methods of terminal synchronization for operation between national networks via terrestrial networks. Plesiochronous buffers are required for networks as shown in Figures\ I\(hy3/G.763 and\ I\(hy4/G.763. Figure\ I\(hy5/G.763 utilizes loop timing and therefore does not require plesiochronous buffering. .RT .LP .rs .sp 15P .ad r \fBFigure I\(hy3/G.763, p. \fR .sp 1P .RT .ad b .RT .LP .rs .sp 13P .ad r \fBFigure I\(hy4/G.763, p. \fR .sp 1P .RT .ad b .RT .LP .rs .sp 15P .ad r \fBFigure I\(hy5/G.763, p. \fR .sp 1P .RT .ad b .RT .LP .bp .sp 1P .LP I.1.3 \fISatellite operation between national networks based upon\fR \fIcontinuous digital carrier type services\fR .sp 9p .RT .PP Figures I\(hy6/G.763 to I\(hy9/G.763 show methods of terminal synchronization for operation between national networks over a satellite link based upon anynchronous continuous digital carrier type services. Figure\ I\(hy6/G.763 introduces controlled slips between the DCMEs which are limited to\ in 70\ days if\ G.811 clocks are available in both networks. Figures\ I\(hy7/G.763, I\(hy8/G.763 and\ I\(hy9/G.763 permit slip free operation between the DCMEs. .RT .LP .rs .sp 13P .ad r \fBFigure I\(hy6/G.763, p. \fR .sp 1P .RT .ad b .RT .LP .rs .sp 14P .ad r \fBFigure I\(hy7/G.763, p. \fR .sp 1P .RT .ad b .RT .LP .rs .sp 13P .ad r \fBFigure I\(hy8/G.763, p. \fR .sp 1P .RT .ad b .RT .LP .bp .LP .rs .sp 14P .ad r \fBFigure I\(hy9/G.763, p. \fR .sp 1P .RT .ad b .RT .sp 1P .LP I.1.4 \fISatellite operation between national networks based upon\fR \fITDMA\(hyType services\fR .sp 9p .RT .PP Figures I\(hy10/G.763 and I\(hy11/G.763 show a method of CDME terminal synchronization for operation between national networks over a satellite link based on TDMA\(hytype services. An appropriate interface is provided in the TDMA terminal to permit interfacing the DCME with and without multi\(hyclique operation over a primary multiplex port. Figure I\(hy10/G.763 permits slip free operation between the DCMEs. .RT .LP .rs .sp 14P .ad r \fBFigure I\(hy10/G.763, p. \fR .sp 1P .RT .ad b .RT .LP .rs .sp 13P .ad r \fBFigure I\(hy11/G.763, p. \fR .sp 1P .RT .ad b .RT .LP .bp .sp 2P .LP I.2 \fIMulti\(hyclique operation\fR .sp 1P .RT .sp 1P .LP I.2.1 \fITerrestrial operation within a national network\fR .sp 9p .RT .PP Figure I\(hy12/G.763 shows a method of DCME terminal syncrhonization for operation within a national network. The cross\(hyconnect function provides a means of assembling the received multi\(hyclique pools onto a single primary multiplex. .RT .LP .rs .sp 14P .ad r \fBFigure I\(hy12/G.763, p. \fR .sp 1P .RT .ad b .RT .sp 1P .LP I.2.2 \fITerrestrial operation between national networks\fR .sp 9p .RT .PP Figure I\(hy13/G.763 shows a method of DCME terminal synchronization for operation between national networks via terrestrial facilities. Plesiochronous buffers are required to resolve timing differences between the various plesiochronous networks. Due to the multiple source nature of the multi\(hyclique configuration, the plesiochronous buffers must be placed before the cross\(hyconnect function. .RT .LP .rs .sp 14P .ad r \fBFigure I\(hy13/G.763, p. \fR .sp 1P .RT .ad b .RT .sp 1P .LP I.2.3 \fISatellite operation between national networks based upon\fR \fIcontinuous carrier type services\fR .sp 9p .RT .PP Figure I\(hy14/G.763 shows a method of DCME terminal synchronization for operation between national networks based on continuous digital satellite carriers. Plesiochronous/Doppler buffers are required to resolve timing differences between the various plesiochronous networks and to remove satellite induced Doppler shifts on the received data streams. Due to the multiple source nature of the multi\(hyclique configuration, the plesiochronous/Doppler buffers must be placed before the cross\(hyconnect function. .bp .RT .LP .rs .sp 18P .ad r \fBFigure I\(hy1/G.763, p. \fR .sp 1P .RT .ad b .RT .sp 2P .LP I.3 \fIMulti\(hydestination operation\fR .sp 1P .RT .sp 1P .LP I.3.1 \fITerrestrial operation within a national network\fR .sp 9p .RT .PP Figure I\(hy15/G.763 shows a method of DCME terminal synchronization for operation within a national network. The received data streams are assumed to originate from mutually synchronized sources. .RT .LP .rs .sp 23P .ad r \fBFigure I\(hy15/G.763, p. \fR .sp 1P .RT .ad b .RT .LP .bp .sp 1P .LP I.3.2 \fITerrestrial operation between national networks\fR .sp 9p .RT .PP Figure I\(hy16/G.763 shows a method of DCME terminal synchronization for operation between national networks via terrestrial facilities. Plesiochronous buffers are required to resolve timing differences between the various plesiochronous networks. Due to the multiple source nature of the multi\(hydestination configuration, the plesiochronous buffers must be placed before the DCME receive function. .RT .LP .rs .sp 28P .ad r \fBFigure I\(hy16/G.763, p. \fR .sp 1P .RT .ad b .RT .sp 1P .LP I.3.3 \fISatellite operation between national networks based upon\fR \fIcontiuous carrier type services\fR .sp 9p .RT .PP Figure I\(hy17/G.763 shows a method of DCME terminal synchronization for operation between national networks based on continuous digital satellite carriers. Plesiochronous/Doppler buffers are required to resolve timing differences between the plesiochronous networks and to remove satellite induced Doppler shifts on the received data streams. Due to the multiple source nature of the receive signals in the multi\(hydestination configuration, the plesiochronous/Doppler buffers must be placed before the DCME receiver. .RT .sp 1P .LP I.3.4 \fISatellite operation between national networks based upon\fR \fITDMA\(hytype services\fR .sp 9p .RT .PP Figures I\(hy18/G.763 and I\(hy19/G.763 show a method of DCME terminal synchronization for operation between national networks over a satellite link based on TDMA\(hytype services. An appropriate interface is provided in the TDMA terminal to permit interfacing the DCME over a primary multiplex port. Figure\ I\(hy18/G.763 permits slip free operation between the DCMEs. .bp .RT .LP .rs .sp 22P .ad r \fBFigure I\(hy17/G.763, p. 27\fR .sp 1P .RT .ad b .RT .LP .rs .sp 12P .ad r \fBFigure I\(hy18/G.763, p. 28\fR .sp 1P .RT .ad b .RT .LP .rs .sp 13P .ad r \fBFigure I\(hy19/G.763, p. 29\fR .sp 1P .RT .ad b .RT .LP .bp .ce 1000 APPENDIX\ II .ce 0 .ce 1000 (to Recommendation G.763) .sp 9p .RT .ce 0 .ce 1000 \fBChannel state classification and system management statistics\fR .sp 1P .RT .ce 0 .PP The purpose of this Appendix is to provide sufficient information to clearly define the system management statistics identified in Table\ 2/G.763. .sp 1P .RT .PP \fINote\fR \ \(em\ It is important that the voice and data performance are measured separately for the following reasons: .LP \(em The effect of freezeout and clipping is different on voice calls and data calls. .LP \(em The DCME process gives priority to assigning activity classed as data and hence the freezeout figures for the data queue should always be less that the corresponding freezeout figure for the voice queue. .sp 1P .LP II.1 \fIChannel state classifications\fR .sp 9p .RT .PP The following channel states are defined in order to clarify their specific meaning in the definitions of the system management statistics. .RT .sp 1P .LP II.1.1 \fITrunk channel (TC) classification\fR .sp 9p .RT .PP The following trunk channel states are defined: .RT .LP a) \fITransparent\fR \ \(em\ The channel is engaged in the transmission of an unrestricted 64\ kbit/s call; .LP b) \fIVoice\(hyactive\fR \ \(em\ The channel is classified as voice by the data/speech discriminator and it is declared active by the activity detector; .LP c) \fIVoice\(hyinactive\fR \ \(em\ The channel is classified as voice by the data speech discriminator and the channel is declared inactive by the activity detector; .LP d) \fIData\(hyactive\fR \ \(em\ The channel is classified as data by the data/speech discriminator and it is declared active by the activity detector; .LP e) \fIData\(hyinactive\fR \ \(em\ The channel is classified as data by the data/speech discriminator and it is declared inactive by the activity detector; .LP f ) \fISignalling\(hyactive\fR \ \(em\ Signalling is detected in this channel by the signalling detector (under study) and the channel is declared active by the activity detector. .sp 1P .LP II.1.2 \fIBearer channel (BC) classification\fR .sp 9p .RT .PP The following bearer channel states are defined: .RT .LP a) \fIVoice\fR \ \(em\ The connected trunk channel carries a voice signal or in\(hyband signalling; .LP b) \fIData\fR \ \(em\ The connected trunk channel carries a data signal; .LP c) \fITransparent\fR \ \(em\ The connected trunk channel carries a transparent call; .LP d) \fIDisconnected\fR \ \(em\ No trunk channel is connected to this bearer channel; .LP e) \fIVoice\(hyavailable\fR \ \(em\ The bearer channel is connected to a voice trunk channel, but could be used for a different assignement; .LP f ) \fIData\(hyavailable\fR \ \(em\ The bearer channel is connected to a data trunk channel, but could be used for a different assignment; .LP g) \fIPre\(hyassigned\fR \ \(em\ The bearer channel is permanently assigned to a trunk channel; .LP h) \fIBank\fR (provisional)\ \(em\ This 4\(hybit bearer channel can be used to obtain the LSBs of up to four data channels. .bp .sp 1P .LP II.2 \fISystem management statistics\fR .sp 9p .RT .PP In the following definitions, \fIN\fR is the number of sampled DCME frames in the averaging period. .RT .sp 1P .LP II.2.1 \fBbits/sample for voice\fR .sp 9p .RT .PP The average number of encoding bits per sample for all TCs used for voice. The average should be calculated to two decimal places. \v'6p' .RT .LP \fR Bits/sample for voice = @ pile { sum above \fIN\fR } @ \v'6p' No. of bits within the BC used for voice @ pile { sum above \fIN\fR } @ \v'6p' No. of non\(hypreassigned TCs classified other than transparent, data or inactive .sp 1P .LP II.2.2 \fBvoice queue freezeout fraction (Voice FOF)\fR .sp 9p .RT .PP The ratio of competitive clip duration to voice spurt duration. The fraction may be determined as the ratio of the number of non\(hypreassigned TCs classified as voice\(hyactive but not connected, to the total number of non\(hypreassigned TCs classified as voice\(hyactive connected plus not connected. The ratio should be expressed as a percentage to three decimal places. \v'6p' .RT .PP \fR Voice FOF = @ pile { sum above \fIN\fR } @ \v'6p' No. of non\(hypreassigned TCs classified as voice\(hyactive but not connected @ pile { sum above \fIN\fR } @ \v'6p' Total No. of non\(hypreassigned TCs classified as voice\(hyactive (i.e. not connected + connected) \ \(mu 100 The number of TCs classified as voice\(hyactive and connected includes those within the hangover time. The voice spurt duration is taken to include hangover. .sp 1P .LP II.2.3 \fBvoice freezeout excess\fR .sp 9p .RT .PP Percentage of time voice FOF exceeds 0.5% when averaged over\ 1 minute. The percentage should be calculated to two decimal places. [For statistic time interval (STI) see \(sc\ 8.2.1.] \v'6p' .RT .sp 1P .ce 1000 Voice FOF excess \ =\ $$1oNo. of 1 min. periods in STI in which voice FOF > 0.5% $$1uNo. of 1 min. periods in STI $$3e \(mu 100 .ce 0 .sp 1P .LP .sp 1 II.2.4 \fBvoice activity ratio\fR .sp 9p .RT .PP The ratio of the number of non\(hypreassigned TCs which are classified as voice\(hyactive to the total number of non\(hypreassigned TCs. The ratio is expressed as a percentage, to the nearest integer. \v'6p' .RT .PP \fR Voice activity ratio = @ pile { sum above \fIN\fR } @ \v'6p' No. of non\(hypreassigned voice\(hyactive TCs No. of non\(hypreassigned TCs \(mu \fIN\fR \ \(mu 100 The voice activity ratio includes hangover time. .bp .sp 1P .LP II.2.5 \fBDLC voice\(hyon ratio\fR .sp 9p .RT .PP The ratio of the number of frame during which DLC for voice/voiceband data (V/VBD) is ON, to the total number of frames. The ratio is expressed as a percentage, to the nearest integer. \v'6p' .RT .sp 1P .LP \fR DLC voice\(hyon ratio = \v'6p' No. of sampled DCME frames with DLC ON for V/VBD \fIN\fR \ \(mu 100 II.2.6 \fBdata queue freezeout fraction (Data FOF)\fR .sp 9p .RT .PP The ratio of the number of non\(hypreassigned TCs classified as data\(hyactive but not connected, to the total number of non\(hypreassigned TCs classified as data\(hyactive (i.e. connected + not connected). The ratio should be expressed as a percentage to three decimal places. \v'6p' .RT .PP \fR Data FOF = @ pile { sum above \fIN\fR } @ \v'6p' No. of non\(hypreassigned TCs classified as data\(hyactive but not connected @ pile { sum above \fIN\fR } @ \v'6p' Total No. of non\(hypreassigned TCs classified as data\(hyactive (i.e. not connected + connected) \ \(mu 100 The number of TCs classified as data\(hyactive connected includes those within the hangover time. .sp 1P .LP II.2.7 \fBdata activity ratio\fR .sp 9p .RT .PP The ratio of the number of non\(hypreassigned TCs which are classified as data\(hyactive, to the total number of non\(hypreassigned TCs. The ratio is expressed as a percentage to the nearest interger. \v'6p' .RT .PP \fR Data activity ratio = @ pile { sum above \fIN\fR } @ \v'6p' No. of non\(hypreassigned data\(hyactive TCs No. of non\(hypreassigned TCs \(mu \fIN\fR \ \(mu 100 The data activity ratio includes hangover time. .sp 1P .LP II.2.8 \fB64 kbit/s failed seizures ratio\fR .sp 9p .RT .PP The percentage of 64 kbit/s on demand seizure (S64) attempts that receive a 64\ kbit/s negative acknowledgment (S64 NACK) from the DCME, given as an integer. \v'6p' .RT .LP \fR 64 kbit/s FSR = \v'6p' Count of S64 signals received in STI Count of S64 NACK signals sent in STI \ \(mu 100 .bp .sp 1P .LP II.2.9 \fB64 kbit/s connected ratio\fR .sp 9p .RT .PP The ratio of the number of non\(hypreassigned TCs which are classified as 64\ kbit/s connect\(hycalled plus 64\ kbit/s connect\(hycalling, to the total number of non\(hypreassigned TCs. The ratio is expressed as a percentage to the nearest integer. \v'6p' .RT .PP \fR 64 kbit/s connected ratio = @ pile { sum above \fIN\fR } @ \v'6p' No. of non\(hypreassigned 64 kbit/s TCs connect\(hycalled and\(hycalling No. of non\(hypreassigned TCs \(mu \fIN\fR \ \(mu 100 The data activity ratio includes hangover time. .sp 1P .LP II.2.10 \fB64 kbit/s DLC \(em on ratio\fR .sp 9p .RT .PP The ratio of the number of frames during which DLC for 64\ kbit/s unrestricted is ON, to the total number of frames. The ratio is expressed as a percentage to the nearest integer. \v'6p' .RT .sp 1P .LP \fR 64 kbit/s DLC\(hyon ratio = \v'6p' No. of sampled DCME frames with DLC for 64\ kbit/s ON \fIN\fR \ \(mu 100 II.2.11 \fBaverage BER\fR .sp 9p .RT .PP The average BER, as measured on the receive control channel. \v'6p' .RT .sp 1P .ce 1000 Average BER \ =\ $$1oCount of No. of bit errors identified in the control channel $$1uCount of total No. of bits received in the control channel $$1e \(mu 100 .ce 0 .sp 1P .LP .sp 1 .sp 1P .LP II.2.12 \fBBER excess\fR .sp 9p .RT .PP The percentage of time that the average BER exceeds 1\(mu10\uD\dlF261\u3\d when averaged over 1\ minute. The value is given as an integer. \v'6p' .RT .sp 1P .ce 1000 BER excess \ =\ $$1oNo. of 1 min periods in STI in which BER > 1\(mu10\uD\dlF261\u3\d $$1uNo. of 1 min periods in STI $$1e \(mu 100 .ce 0 .sp 1P .LP .sp 1 II.2.13 \fBseverely errored seconds ratio\fR .sp 9p .RT .PP See Recommendation G.821. .RT .sp 1P .LP II.2.14 \fBdegraded minutes ratio\fR .sp 9p .RT .PP See Recommendation G.821. .RT .sp 2P .LP \fBReferences\fR .sp 1P .RT .LP [1] KOU (K.Y.), O'NEAL (J.B.), NILSON (A.A.): Computations of DSI (TASI) overload as a function of the traffic offered, \fIIEEE Trans. on Communications\fR , Vol. COM\(em33, No.\ 2, Feb. 1985. .LP [2] BRADY (P.T.): A model for generating on\(hyoff speech patterns in 2\(hyway conversation, \fIBell System Technical Journal\fR , page\ 2445 \fIet\ seq.\fR , Sep.\ 1969. .LP [3] Special Issue on bit rate reduction and speech interpolation, Guest Editors M.R. Aaron and N.S. Jayant, \fIIEEE trans. on Communications\fR Vol. COM\ 30 No.\ 4, April\ 1982. .LP .bp