The following reports of recent standards meetings represent the view of the reporterand are not official, authorized minutes of the meetings.
Q15/16, Video Coding Experts, February 15 - 19, 1999, Monterey, CA ....................................................... 2Support of Existing Video Coding Standards ......................................................................................... 2Coordination of Video Coding Needs for Systems .................................................................................. 2Technical Content Proposals for H.263++ and H.26L ........................................................................... 3Test Model, Software, and Encoding........................................................................................................ 8Sign Language and Lip Reading Applications........................................................................................ 11Workplan for H.263++............................................................................................................................... 11Workplan for H.26L ................................................................................................................................... 12Plans for Future Work, and Ad Hoc Committee Designations.............................................................. 14
Addendum to the Report of Q11/16, February 17 - 19, 1999, Monterey CA................................................ 18ETSI TIPHON Meeting #12 March 1 -5, 1999, Philadelphia, PA, USA..................................................... 20
Working Group 1, Requirements .............................................................................................................. 24Working Group 2, Architecture................................................................................................................. 26Working Group 3, Call Control ................................................................................................................ 29Working Group 4, Naming, Addressing.................................................................................................. 31Working Group 5, Quality of Service........................................................................................................ 33Working Group 6, Verification .................................................................................................................. 35Working Group 7, Wireless ....................................................................................................................... 36Security ....................................................................................................................................................... 38BOF on Back End Services, and STF 114 Meeting ................................................................................ 39
ETSI ATA (Analog Terminals and Access), March 8 - 12, 1999, Sophia Antipolis, France ...................... 43Joint Session with DTA............................................................................................................................ 45ATAc (Conventional) Session.................................................................................................................... 47ATAe (Enhanced) Session........................................................................................................................ 47
ETSI DTA (Digital Terminal and Access) Meeting #5, March 9 - 11, 1999, Sophia Antipolis, France .... 50Q4/15 Rapporteurs Meeting on xDSL, March 29 - April 2, 1999, Melbourne, Australia............................ 54
TR-30, Data Transmission Systems and Equipment, April 12 - 14, 1999, San Jose, CA .......................... 63TR-30.1, Modems ....................................................................................................................................... 63TR-30.2, Data Transmission..................................................................................................................... 64TR-30.3, Data Communications Equipment Evaluation and Network Interfaces ............................. 65
TR-41.3.4 Interim Meeting, April 1939 - 20, 1999, Vancouver, BC .............................................................. 70PN-4462 Performance and Interoperability Requirements for VoIP Telephone Terminals............... 70
Acronym Definitions ......................................................................................................................................... 76Year 2000 Standards Committee Meeting Schedules, as of April 27, 1999................................................. 781999 Standards Committee Meeting Schedules, as of April 27, 1999......................................................... 79Document Order Form .................................................................................................................................... 80
REPORT OF Q15/16, VIDEO CODING EXPERTSFEBRUARY 16 - 19, 1999, MONTEREY, CA
Editor’s note: Q11-14/16 met concurrently with Q15/16 in Monterey. The Q11-14/16 reportswere published in CSR Vol. 10 #3.
The meeting was chaired by Q15/16 Rapporteur G. Sullivan (PictureTel). Information pertinentto the Video Coding Experts Group can be found on the Q15/16 ftp siteftp://standard.pictel.com/video-siteDocuments for this meeting are in the 9902_Mon subdirectory of the ftp site.
E-mail conversations about Q15/16 activities are routinely conducted using a reflector which waschanged recently. To send messages, address them to “itu-adv-video@standard .pictel.com.” Tosubscribe or unsubscribe, send email to “[email protected].” Note: Only peoplewhose exact email address is subscribed to the list can post. Subscriptions: “subscribe itu-adv-video YOUR-EMAIL-ADDRESS” in message body. Unsubscriptions: “unsubscribe itu-adv-videoYOUR-EMAIL-ADDRESS” in message body.
Attendees were reminded about disclosing patents and filing intellectual property claims with theITU.
The next meeting of Study Group 16 will be May 17-28, 1999, in Santiago, Chile(http://www.ict.uchile.cl/itu-t.sg16). The deadline for delayed documents is May 5, 1999. Thefollowing Q15/16 experts meeting will be August 10-13, 1999 in Berlin.
SUPPORT OF EXISTING VIDEO CODING STANDARDS
Q15-G-04 (S. Gupta, VTEL) reports the progress of work on the adoption of H.263+ in H.320.The relevant drafts for H.320, H.221, H.242 and H.230 were modified at the November Q11/16meeting in Turino (see CSR Vol. 10.2). The draft modifications included clarification of themacroblock and GOB (Group of Blocks [H.261, H.263]) numbering used in H.230, and a review toensure appropriate usage of shall and should. The documents have now been submitted to theTSB in preparation for Approval at the Santiago SG16 meeting in May.
COORDINATION OF VIDEO CODING NEEDS FOR SYSTEMS
JOINT SESSION WITH Q11/16 THROUGH Q15/16
The following topics were discussed (see report of joint meeting in CSR Vol. 10.3, page 18, formore details):
1. Status of H.263+ in H.320.2. Video codec projects and status: a review of the H.263++ and H.26L projects, including an
overview of their key technical areas and scheduled workplans.3. The status of work on video coding for sign language and lip-reading communication.4. Mobile multiplex model for error resilience testing.5. Third-generation mobile systems development.
THIRD-GENERATION MOBILE SYSTEMS DEVELOPMENT
Q15-G-14 (D.-S. Park, Samsung, and J. Villasenor, UCLA) gives the status of work on thedevelopment of third-generation mobile telephony networks, i.e., IMT-2000. It was reported thatT1 and TIA TR-45.5 (CDMA-2000) in the US., ETSI in Europe (the third-generation partnershipproject: 3GPP), ARIV in Japan, and ITU-T TG 8/1 are some of the organizations working towarddefinition of these networks. The initial goals of the design have been to work out issues for thephysical layer transmission methods, and to design voice and packet communicationmechanisms. The IMT-2000 network is expected to support bit rates suitable for multimediacommunication service terminals (e.g., 144 kbit/s, 384 kbit/s, and 2 Mbit/s). It was reported thatthere may be incompatibility between the methods chosen for standardization in different nations.The definition of multimedia system operation has not yet been a primary focus of attention insome of these efforts, but it was verbally reported that ETSI has chosen H.324/M as the
multimedia terminal for 3GPP; multimedia systems are of increasing interest in the otherorganizations and are expected to be addressed further when the initial goals are closer to beingreached. The members of Q11/16 through Q15/16 expressed great interest in the evolution ofthese networks, and the need to define multimedia terminal systems for operation on them.
Satellite systems for wireless mobile communication were also discussed (APC-1539a / Q11-I-15).Geostationary satellites with approximately 64 kbps channels having 240 ms one-way delay(user terminal to user terminal) are expected, with 10-6 BER near the center of the beam andNx10-4 BER near the edge. The next IMT-2000 Satellite Group meeting is in March 1999.
TECHNICAL CONTENT PROPOSALS FOR H.263++ AND H.26L
RESPONSES TO H.26L CALL FOR PROPOSALS
Four basic algorithm designs with test results were presented which appeared strictly directedtoward the H.26L project. These designs are described below. Other technical proposals,considered to possibly apply either to the H.263++ or H.26L, are also discussed below.
Balanced Multiple Description Coding
Q15-G-09 (V. Vaishampayan, A. Reibman, and S. John, AT&T) is a tutorial paper describing theprinciples of interframe balanced multiple description coding and its potential application to videocodecs. As opposed to a priority-coding scheme such as the methods used in temporal, spatialand SNR scalability coding, this method can generate separate streams of equally-importantinformation for the generation of each video picture. Receipt of any one of these streams canprovide a basic level of quality, and receipt of more than one can provide an enhanced level ofquality.
Q14-G-09 describes a method of performing balanced multiple description coding. It consists ofencoding each picture with two coarse scalar quantizers that have their origins shifted by a halfstep-size relative to each other. Receipt of either bitstream would provide a coarserepresentation of a picture, and receipt of both would provide a finer representation by decodingthe information in the two bitstreams together to effectively yield quantization with half the stepsize. The interframe feedback loop is handled by also quantizing DCT coefficients for theprediction picture (using the same offset coarse quantizers) as well as quantizing and sending theresidual difference information (no index information is sent to the decoder for the quantization ofthe prediction, since the decoder can infer these indices).
A demonstration of the technique was shown in a simple DCT frame-difference video coder (nomotion compensation) under 20% packet loss conditions with approximately 20% extrainformation sent relative to a single-description encoding. The demonstration showed that thetechnique did produce a very visible improvement relative to using the DCT frame differencecoding without multiple descriptions.
This technique, although still at a preliminary stage of development for video coding, may developinto a scheme for robust video transmission. Some issues, such as how to combine the techniquewith motion compensation and switched prediction modes, still need to be addressed. We lookforward to further contributions as this method matures.
Enhanced Telenor Proposal
Q15-G-25 (G. Bjøntegaard, Telenor) describes enhancements to the Telenor H.26L proposalpresented in Seoul. (See Q15-F-11 in CSR Vol. 10.2, 2/99, for additional details.) The enhancedproposal added several key features, including:• 1/3-pixel motion compensation (with a coupling between filter strength and 1/3-pixel position,
and four-tap vertical and horizontal interpolation filters designed to avoid the need for“rounding control”)
• A 2x2 transform for DC coefficients of 4x4 chroma blocks• Redefined coded-block-pattern coding for chroma• The use of a de-blocking loop filter on I-pictures• Prediction using multiple (e.g., five) reference pictures
Q15-G-25 also illustrates the importance of the first INTRA-picture on R-D performance withfixed step size. Technical editor’s note: An INTRA picture is a picture that is coded without usingany reference picture(s) for predicting its values. An INTER picture is a picture that is codedusing temporal prediction, i.e., using a temporally-previous picture as a reference.
The enhanced proposal provided improved R-D (rate-distortion) performance (approximately 0.5dB or more, or approximately 10% in bit rate, not including the gain from enhancing the fidelityof the I-picture) relative to the prior proposal as shown in plots illustrated per Q15/16’s commonconditions comparison method. Relative to the reference anchor, it showed approximately a 1 to2 dB improvement (approximately 20-40% bit rate savings).
The group asked about the choice of 1/3 pixel motion resolution rather than 1/4. The proponentresponded that the R-D and visual performance of the two were approximately comparable. Theimportance of subjective versus objective coding efficiency enhancement was also discussed as ageneral issue.
Enhanced Strathclyde Proposal
Q15-G-27 (R. Fryer and R. Lambert, Univ. of Strathclyde) reports on an enhancement of theprior Strathclyde H.26L proposal to include residual difference coding. The prior proposal Q15-F-19 had not included a residual difference coding mechanism, and the addition of this featureimproved the Peak Signal to Noise Ratio (PSNR performance significantly. The resultingperformance now appears to be approximately 0.5 dB better than the reference anchor for allQUANT values greater than about 5. The proposed codec showed the best improvement forscenes with a fixed camera and high-contrast, bright content. Technical editor’s note: QUANT isessentially the same as QP in MPEG coding. The DCT coefficients in H.263 are represented byscalar quantization reconstruction. QUANT is an integer parameter having a value from 1 to 31that controls the coarseness of the reconstruction. QUANT is half of the value of the quantizerreconstruction step size for non-zero coefficients. Precise detail on exactly what QUANT normallydoes is defined in Section 6.2.1 of H.263.
The proposed codec is also described as having very low complexity; a real-time demonstration ofits ability to operate on an ordinary computer was provided.
The codec performance could probably have been improved by predictive coding of motion vectorinformation, which was not performed in the tested configuration. The motion representation ofthe demonstrated codec used four reference pictures to improve coding efficiency relative tosingle-reference video coding.
Low latency is another emphasized feature of the proposed design. The demonstrated qualitywas obtained using an essentially constant number of bits per picture. The need for methods tocompare quality under low latency conditions was expressed, and action was taken on this issueas noted below (under Common Conditions for Simulation Testing).
Wavelet coding with OBMC and Warping
Q15-G-36 (G. Heising, D. Marpe, Heinrich-Hertz Institute; H. L. Cycon, F. H. T. W.-Berlin; A.Petukhov, State University of St. Petersburg) describes a method of video coding using eitheroverlapped-block motion compensation (OBMC) or control-grid warping for motion compensationof each picture region, followed by residual three-level dyadic wavelet decomposition and codingwith the PACC wavelet coding method (Partitioning, Aggregation, and Conditional Coding) basedon scalar quantization with an enlarged dead-zone and arithmetic coding. The interpolationmethod used for motion compensation could be switched between bilinear and higher-orderinterpolation.
The reported R-D performance of this codec was illustrated as providing a range ofapproximately 0.5 to 1.5 dB gain (10-30% bit rate savings) relative to the reference anchor, withmore gain on intra picture coding.
Several contributions were presented relating to the proposal of a Data Partitioned Slice modeannex for addition to H.263. This subject is a Key Technical Area of H.263++ as reported at theSeoul meeting.
Q15-G-13 (M. Luttrell and J. Villasenor, UCLA; D. S. Park, Samsung) is proposed text for thisnew annex, which essentially uses the existing syntax of the slice structured mode of H.263Annex K, except for separation of the motion vector data from the coefficient data for each slice(with addition of a start marker), use of the coding table of Annex D for motion vectors(regardless of whether or not the Annex D extension of the motion vector range is active), andsimplification of the motion vector prediction mechanism.
Test Results
Q15-G-12 (M. Luttrell and J. Villasenor, UCLA; D. S. Park and J.-H. Park, Samsung) is a set oftest results presented for evaluation of the proposed Data Partitioned Slice mode. Theperformance of the proposed syntax was measured relative to previously agreed-upon commonconditions and anchors (with a forced intra refresh counter of 5 rather than 132). The testshowed a performance gain of an average of approximately 1 dB or more along with a verysubstantial reduction in the number of lost pictures. Included in the test was an evaluation ofperformance relative to the original Annex K slice structured mode, showing an additionalperformance gain over that of Annex K. (Simulation experiments using the Annex K SliceStructured mode are further reported below.)
Q15-G-23 (J. Kim, K. Wuttipong, and C. C. Jay Kuo, USC) gives a cross-verification of the testresults for the Data Partitioned Slice mode. This cross-verification test also showed a significantperformance gain, essentially corroborating the results presented by the proponents in Q15-G-12. Q15-G-23 also discusses a number of issues surrounding the design of this mode, includingthe treatment of the first slice in each picture, byte-alignment of motion markers, and theusefulness of a packet number for each slice. Issues marked for further investigation in thisdocument include the validity of received values of packet number and macroblock address, andthe possibility of the use of unequal error protection methods. The opinion in the contribution wasthat the Data Partitioned Slice mode was worthwhile for addition, but may need further draftingwork and testing.
Q15-G-24 (S. Kittitornkun, A. Li, Y.-H. Hu University of Wisconsin-Madison) presents a third setof test results for cross-verification of this proposed feature. This work used a decoder providedby UCLA, but used a separate implementation of the encoder so that results would beindependent to the extent deemed practical. The tests concluded that the Data Partitioned Slicemode provided a significant performance gain when compared to agreed anchor conditions underforced intra refresh rates of both 5 and 132. The reported PSNR improvements were consistentand substantial (apparently a greater degree of gain than that reported by Samsung and UCLA).A somewhat older version of the syntax may have been used in these tests, and the proponentswere asked to examine whether the most recent proposed syntax has affected performance.
Adoption of Draft Annex V
As a result of the three sets of favorable test results and expressions of support for the feature,Q15/16 decided to adopt the current draft of this feature, Q15-G-12, for refinement and laterapproval as an optional mode embodied as a new annex to H.263. D.-S. Park (Samsung) and J.Villasenor (UCLA) were appointed jointly as editors of the draft for this new annex (which iscurrently planned to become Annex V).
Several contributions were presented relating to the proposal of an enhanced reference pictureselection / long-term memory mode annex for addition to H.263. This subject is a Key TechnicalArea of both H.263++ and H.26L as reported at the Seoul meeting.
Q15-G-18, the proposed text for this new annex (T. Wiegand, N. Färber, and B. Girod, Universityof Erlangen-Nuremberg; and B. Andrews, 8x8), provides a buffer management method for use ofa number of prior reference pictures and alters motion vector coding to provide both a spatial anda temporal offset for each motion compensated region. Q15-G-19 (T. Wiegand, N. Färber, and B.Girod, University of Erlangen-Nuremberg; and B. Andrews, 8x8) provides a description of a coreexperiment for evaluation of the merits of this feature. The core experiment tested this feature forcoding efficiency improvement in configurations of 10 or 50 reference pictures of Quarter CIF(QCIF) resolution, and of 5 or 10 reference pictures of Common Intermediate Format (CIF)resolution.
Test Results
Q15-G-20 (T. Wiegand, N. Färber, and B. Girod, University of Erlangen-Nuremberg; and B.Andrews, 8x8) presents test results for the evaluation of this method. In this test, average bitrate savings of about 10% with 10 reference pictures and 15% with 50 reference pictures werereported to be typical, with the highest gains being at higher bit rates and with more motion, andbit rate savings of up to 60% were reported to have been achieved in special situations.
Q15-G-33 (M. Galland and F. Kossentini, University of British Columbia) provides cross-verification of the results of this feature. Q15-G-33 tested the use of 10 reference pictures, andreported similar gains. The University of BC expressed support for the adoption of this newproposed mode.
Interaction with Error Resilience
Q15-G-26 (R. Fryer and R. Lambert, Univ. of Strathclyde) expresses concern that the proposednew mode might degrade error resilience performance, based on the idea that the larger numberof reference pictures provides an increased probability that some corrupted reference picturesmay be used in the coding of new pictures.
In response it was noted that this technique had been recently studied (Budagavi and Gibson, Int.Conf. Image Proc. ’97) for its potential to enhance error resilience performance. It was based onthe idea that the larger number of reference pictures provides an increase in error resilience,since in some cases a picture that is corrupted may not be used as the reference (as opposed toconventional coding, in which any corrupted picture will almost certainly be used as a reference).A probability model for corruption of pictures was discussed; Q15-G-43 describes the errorresilience enhancement analysis. This led to a withdrawal of the expressions of concern in light ofthe new information. However, Q15/16 agreed that error resilience is a highly pertinent issuethat should receive further study.
Adoption of Draft Annex U
As a result of the two sets of favorable test results and expressions of support for the feature,Q15/16 decided to adopt the current draft of this feature, Q15-G-18, for refinement and laterapproval as an optional mode embodied as a new annex to H.263. T. Wiegand (University ofErlangen-Nuremberg) was appointed editor of the draft of this annex (planned to become AnnexU).
AFFINE WARPING
Affine warping was designated as a Key Technical Area of both H.263++ and H.26L as reportedat the Seoul meeting.
Affine Warping with 32 Picture Warp Selections
Q15-G-21 (T. Wiegand, E. Steinbach, and B. Girod, University of Erlangen-Nuremberg; and B.Andrews, 8x8) describes a combination of enhanced reference-picture selection / long-termmemory and affine warping. In this method, 32 affine warpings of a reference picture were sentat the picture level. These affine parameters were used (with cubic interpolation) to create 32additional reference pictures for use (with a plus or minus two additional motion vector offset) in a
manner similar to that used in the draft Annex U described above. This method (with andwithout additional reference pictures as described above) was tested in coding efficiencyperformance relative to an H.263+ anchor (with and without additional reference pictures asdescribed above). A significant performance gain was seen on some sequences relative to ananchor using approximately the same number of reference pictures.
Affine Warping on Macroblock Basis
Q15-G-29 (M. Karczewicz and J. Lainema, Nokia) describes sending affine warping parameterson a macroblock basis (as distinct from the picture-level method used in Q15-G-21). This methodwas against an H.263+ anchor. This experiment appeared to show a significant gain for themacroblock-structured method, exceeding that of the picture warp method. Coupling thistechnique with long-term memory prediction may provide further gain, but this method aloneappeared to provide approximately an average 30% bit rate savings relative to the anchor.
Request for Proposed Draft
The experts found the performance results of the affine motion proposals to be very encouraging,and asked the interested parties to confer, conduct further investigations, and to propose a goodexperiment design and draft text for potential adoption at the next Q15/16 experts group meetingas a new Annex to H.263. T. Wiegand, M. Karczewicz, and J. Lainema were designated to leadthe creation of this draft. A core experiment design was drafted for this experiment (Q15-G-44).
IDCT MISMATCH REDUCTION
Today’s DCT-based video coding standards (e.g., H.263 Annex A) provide an imprecisespecification of the inverse transform to be used in decoding - specifying only statistical accuracybounds. In some situations, especially when Annex J of H.263+ is active (the Deblocking Filtermode), mismatch error can create visible artifacts. Reducing this mismatch is a designated KeyTechnical Area of H.263++ as reported at the Seoul meeting. Q15-G-34 (B. Andrews and S.Bryant, 8x8) proposes providing an exact integer-based Inverted Discrete Cosine Transform(IDCT) definition which could eliminate mismatch when both the encoder and decoder implementthe same method. A discussion of several issues which surround this concept was provided,including:
• The ability to eliminate the forced intra update requirement when using a specified IDCT• Whether a single IDCT should be chosen or several alternative definitions• Whether the chosen IDCT needs to be compliant with H.263 Annex A
An IDCT program was provided (in Q15-G-34) which is reported to have compliant performanceand which may potentially be chosen for this purpose.
Q15/16 asked its experts to review this proposal and provide feedback on its content and its openissues at the next experts’ group meeting. Three remarks from Q15/16 regarding this proposalwere that:
• Perhaps the accuracy spec. could simply be tightened rather than specified exactly.• Perhaps the IDCT method could be indicated using Supplemental Enhancement Information
for backward compatibility.• Perhaps the IDCT method could simply be announced rather than negotiated.
DEBLOCKING AND DE-RINGING FILTERS
Two methods for deblocking and de-ringing filtering were presented; this topic has beendesignated as an H.263++ Key Technical Area as reported at the Seoul meeting. In one case thedesign considered was a loop filter method, and in the other case a post-processing filter. Theassessment of these methods and the comments regarding them should be considered somewhatrelated.
Loop Filtering for Deblocking, De-Ringing, and Corner-Outlier Artifacts
Q15-G-10 (Y.-L. Lee, H.-W. Park, D.-S. Park, and Y.-S. Kim, KAIST and Samsung) presents atechnique which had been presented at the Whistler Q15/16 meeting (as Q15-E-22, July, 1998)
and at the Seoul meeting (as Q15-F-20) which adaptively filtered the areas of the picture usingclassifications on the values of coding parameters.
For deblocking, the technique used a set of directional flags to indicate whether blocking artifactswere likely to occur horizontally, vertically, or both, and to filter with varying strength accordingto these flag classifications. For de-ringing, similar adaptive means were used as controlled bytwo flag values. Special treatment of the classification flags was provided for determining newflags after motion compensation. In INTRA pictures, a method is provided to detect and correct“corner outlier” pixel values in which the extreme corner of an INTRA-coded block may have avalue that unusually deviates from the values of its neighbor pixels in other blocks.
The filter provides a gain in Peak Signal to Noise Ratio (PSNR) fidelity performance typicallybetween 0.3 and 0.5 dB, with roughly the same complexity as that of Annex J (approximately93% of the complexity measured for a non-optimized version of H.263 Annex J). A demonstrationwas provided. It was agreed that the demonstration appears to show a reduction in artifactsrelative to Annex J (without the de-ringing filter defined in the test model) in some areas (parts ofthe Hall Monitor sequence, diagonal edges in the Foreman sequence, ringing reduction in theContainer Ship sequence, and some artifact reduction in the Paris sequence).
This filter design is used as a post-filter in the MPEG-4 standard’s informative section; furtherinformation about it is available in an article in the February ’99 issue of the IEEE Transactionson Circuits and Systems for Video Technology (pages 161-171).
Regularized Post-Filtering for Deblocking and De-Ringing
Q15-G-35 (M.-C. Hong, C.-W. Kim, and C. M. You, LG Electronics) gives a post-filtering methodusing a regularization method with a smoothing constraint applied with four directionalsmoothness functions. The method provides an iterative filtering approach. A single filteringmethod applies to obtain both a deblocking and a de-ringing benefit. A consistent PSNR gain wasshown as a result of using this filtering method (which is often not seen from post-filteringmethods), relative to H.263+ Annex J with and without the de-ringing post-filter of Section 10 ofTMN10.
A demonstration of the filtering method’s performance was provided. There appeared to be somebenefit shown (although not a dramatic one), and the filter was reported to have much lowercomplexity than the combination of Annex J with the TMN10 de-ringing filter.
Test Model Adoption of Post Filter
Q15/16 discussed the performance and complexity associated with these two filter designs, alongwith the IDCT mismatch issue and the relative benefits of using a loop filter as opposed to a postfilter.
Q15/16 decided that it was unlikely to want to add another annex to H.263 for an improved loopfilter design, at least for the demonstrated complexity and performance for these two filters. Ittherefore decided to cease listing loop filtering as a Key Technical Area of H.263++. However, itwas agreed that the test model does not require the same degree of stability as that of the videocoding standard itself. The proponents of Q15-G-10 did not wish to pursue it as a test model postfilter, and thus Q15-G-10 was withdrawn from such consideration. The design described in Q15-G-35 was then adopted into the test model for use when Annex J is not in use, due to its benefitsin perceptual performance and its low complexity.
EZW-STRUCTURED DCT CODING FOR H.26L
Q15-G-30 (Y.-A. Jeong, Y.-S. Soh, and Y.-M. Park, LG Electronics) describes the restructuredDiscrete Cosine Transform (DCT) coefficient filtering structure along the lines of embedded zero-tree wavelet (EZW) coding. The resulting design was presented as offering enhancements incoding efficiency, rate control precision, scalability, and error robustness. Significant gains incoding performance were reported in both intra and inter coding performance (particularly intra).Test results and a demonstration of performance were provided. The test results showed asignificant performance gain for some scenes, although the anchor results against which thetechnique was compared did not appear to be from a current test model design and the results
reported were not obtained from decoded bitstreams. The perceptual performance appeared tohave a somewhat less blocky appearance, although it was difficult to see in these demonstrationconditions. Q15/16 thought that this method may show promise (as much for its other propertiesas for its coding efficiency), and thought it to be potentially relevant to H.26L, where morefreedom is available for significant restructuring of the codec design.
TEST MODEL, SOFTWARE, AND ENCODING
ERROR RESILIENCE QUALITY EXPERIMENTS
The ad-hoc report on error resilience, Q15-G-05 (S. Wegner, TU Berlin), notes several issues,including:
• Mobile anchors would be provided by the University of British Columbia (UBC)• Mobile anchors require more than just encoded bitstreams (e.g., packetizer, error patterns,
decoding error concealment, depacketizer, multiplex simulator, etc.)• The set of bit rates and error patterns chosen for this work may need to be reviewed• Some error patterns were not available• More work in regard to Internet packet loss scenarios is needed• High latency conditions may warrant attention
Slice Structured Coding Experiments
Q15-G-15 (M. Tisserand and J. Villasenor, UCLA) reports simulation results for the SliceStructured mode of H.263+ with an intra forced refresh rate of 5 with Annexes D, F, I, J, and Talso active. These tests prompt some observations such as:
• The Slice Structured mode and the proposed Data Partitioned Slice mode have approximatelythe same performance in the absence of errors (i.e., they have essentially similar amounts ofoverhead although slightly more overhead for the Data Partitioned Slice mode).
• The Slice Structured mode appears to provide some gain relative to the anchor without theSlice Structured mode.
• The proposed Data Partitioned Slice mode as proposed appears to provide further gainrelative to the Slice Structured mode.
• The amount of gain provided by the Slice Structure mode and the proposed Data PartitionedSlice mode diminishes as the channel behavior improves (which should be obvious, but may beworth stating).
• It appears difficult to clearly separate the gains from the error handling mechanism (e.g., therules for discarding pictures, discarding packets, concealing errors, and making encoderdecisions) from the syntactical format.
Packet Multiplex Simulator For Error Resilience Testing
Q15-G-38 (G. Sullivan, PictureTel) gives software for the simulation of the effects of an error-prone channel on video data. It simulates the Level 2 mobile multiplex of H.223 Annex Bprocessing video data using Adaptation Layer 3 transmission. It allows an error pattern fileobtained from channel measurements or simulation conditions to be applied to the pseudo-multiplexed bitstream and for the effects of this corruption to be simulated on the multiplexeddata. This new version of the program differs from that presented in Seoul in its handling oflarge packets. The previous version was slightly unrealistic in its handling of packets of size 253and 254 bytes, and it could not handle packets larger than 254 bytes. The new versionsubmitted will handle packets as large as 65535 bytes (by splitting AL3 packets across multiplemux packets if needed).
Q15/16 consulted the Q11/16 mobile experts at this meeting regarding the validity of the modelpresented in Q15-G-38. They provided a response, Q15-G-42, which can be summarized asfollows:
• The mux simulation is basically reasonably realistic.• The mux payload length field can reduce the probability of a lost mux packet due to sync
corruption (modifications to the program for this purpose were suggested)
• Duplicate headers can be optionally attached to subsequent mux packets, further reducing thelikelihood of lost mux packets.
The group was glad to have this expert feedback on the usefulness of this mux simulationprogram, and will incorporate the suggested improvements in the near future.
Internet / H.323 Video
Q15-G-17 (S. Wegner, TU Berlin and G. Côté, UBC) describes example methods for videotransmission over Internet Protocol networks (to appear in Packet Video ’99). Such networksrequire a large amount of overhead (e.g., 40 bytes) per packet and have effective upper bounds(e.g., 1500 bytes) on packet sizes. This contribution examines the interplay between packet sizesand structures, error concealment, and encoder decisions. In particular it:
• Proposes a method of compensating a rate-distortion optimized mode decision rule toincorporate packet loss probability and the degree to which a given region will be distorted ifdata is lost. This method was judged meritorious by the group and is to be included in the nextissued test model document.
• Proposes use of the Telenor Research’s error concealment decoder (TCON) error concealmentmethod for lost information (as already described in the test model document).
• Notes that the packetization overhead alone could fill an entire video channel of 28.8 kbps forQCIF pictures at 10 frames pre second if separate packets are used for each GOB.
• Proposes a packetization format in which alternating GOBs are placed into two packets (onefor even-numbered GOBs and one for odd-numbered ones). However, there was some issuetaken with whether this packetization scheme (although perhaps a good idea in itself) wascompliant with the RTP packetization format specified for H.263 in RFC 2429. It appearedthat the method would only be fully compliant if the Slice Structured mode was active withArbitrary Slice Ordering submode in effect - not in the GOB-structured scheme as described.
After discussing the issues involved in video transmission over Internet Protocol networks,Q15/16 agreed on a set of common conditions for testing performance in this environment; thesecommon conditions are described below. The rate-distortion optimization technique for errorprone environments was adopted into the test model document, and the packetization scheme wasalso adopted subject to alteration to specify use of the Slice Structured mode (Annex K) withArbitrary Slice Ordering.
WCDMA Error Patterns
Contributions Q15-G-28 (G. Bang, Ericsson) and Q15-G-41 (also from Ericsson, it includes theerror patterns) made available Wideband Code Division Multiple Access (WCDMA) errorpatterns for error resilience testing use. These error patterns should be useful in conductingerror resilience experiments.
Mobile Anchor Sequences
Q15-G-31 (G. Côté and F. Kossentini, UBC, and S. Wegner TU Berlin) indicates that anchorsequences are available for error resilience testing according to the previously-agreed commonconditions. It provides various tools for generating the anchor results, and reports the results.The contributors indicated that they are also likely to be able to generate anchor sequences forsuch new common conditions as agreed upon at this meeting.
Using GFID in Error Prone Environments
Q15-G-37 (G. Côté and F. Kossentini, UBC, and S. Wegner TU Berlin) describes a potential useof the GFID (GOB frame identification) bits for error resilience tests. The proposal was to useGFID to detect picture header changes in lost headers, and to guess that the picture headerchange was most likely due to a change in picture type (e.g., intra changing to inter). However,after discussion, the group decided that since GFID can change for other reasons (e.g., changes inoptional mode configurations) it might be risky to assume that picture type changes wereresponsible for GFID changes. It was therefore decided not to adopt this method into the testmodel at this time.
Q15-G-22 (H. Song, J. Kim, and C.-C. Kuo, USC) describes methods for adaptively controllingframe rate during changes in scene motion activity and channel bit rate. The selection of anappropriate frame rate for use in encoding a video sequence is a fundamental part of the design ofa video coding system, yet previously it has not received any significant attention in our testmodel design efforts (more typically we simply pick a frame rate we think is appropriate forexperiments using a video sequence, without regard for the fact that a real-time encoder wouldneed to decide on its own what frame rate is appropriate, and would need to do so without priorknowledge of the difficulty of the content of the video sequence). The design provided attempts tomaintain both perceptual visual motion smoothness and adequate picture fidelity while adaptingthe frame rate for encoding based on the bit rate available for use and the amount of motion in thescene.
Q15/16 agreed to adopt a description of this method in the “information capture” section of thetest model document, but not to immediately adopt its use into common conditions forexperiments.
USING CHROMA DISTORTION IN TEST MODEL ENCODING
Q15-G-32 (M. Gallant, UBC) proposes including chrominance distortion measurement in thehigh-complexity test model reference encoder design. A demonstration was shown to illustratethe usefulness of this technique. Q15/16 agreed to adopt this method into the test model assuggested. Further investigation is encouraged to determine whether inclusion of chrominancedistortion in motion estimation is also useful.
TEST MODEL DRAFTING
Q15-G-16 (S. Wegner, TU Berlin; G. Côté, M. Gallant, and F. Kossentini, UBC) is a draft of anew version of the test model. Q15/16 agreed to give the editors authorization to alter thedocument as needed to clarify it and to capture prior group decisions for enhancing it. A revisedversion of the document is to be produced by its editors as the TMN11 output of the meeting.
DEBLOCKING AND DE-RINGING DECODER POST-PROCESSING
Q15-G-35 (M. C. Hong, C.-W. Kim, and C, M. You, LG Electronics) provides for enhancing thetest model reference design for post-processing filtering. The results are described above (underDeblocking and De-ringing Filters).
COMMON CONDITIONS FOR SIMULATION TESTING
Four sets of such common conditions were agreed:
1. Common conditions for coding efficiency tests: These are to be performed as previouslyspecified in Q15-D-62r1 except that the current version of the test model should be used(including use of chroma distortion). A motion vector range of plus or minus 32 pixels shouldbe used. Results with de-ringing post-filtering turned off are mandatory; those with the post-filtering turned on are encouraged as additional information, but are optional.
2. Common conditions for error resilience tests: The common conditions for such tests aredescribed in Q15-G-46. Modifications include new error patterns, a new multiplex model, anda reduced set of test sequences.
3. Common conditions for Internet / packet-loss tests: The new common conditions for such testsare described in Q15-G-39.
4. Common conditions for latency comparisons: The new common conditions for such tests aredescribed in Q15-G-45.
It was agreed that proposals for H.26L must show that each issue in the goal set of H.26L hasbeen considered and addressed in their proposal document, and that a good-faith effort has beenmade at estimating performance on each of these criteria and the additional criteria listed in thegoals list for the H.26L project. However, strict adherence to the common conditions for all fourtested criteria are not absolutely required.
This was the first experts group meeting held without a D-1 VTR. Q15/16 discussed the issuessurrounding how to conduct the best video performance demonstrations at meetings withoutnecessarily always having a D-1 on hand. Having a D-1 at each meeting has often been aproblem, and Q15/16 decided that it is not absolutely necessary. Members indicated that a D-1will be available at the Berlin meeting, but that we should not count on one in the future; demosusing methods other than D-1 are acceptable.
Members were asked to bring demonstration data to the next meeting in the following format: aPC-based CD-ROM, containing a single file for each video sequence in the format of Y, then CB,then CR (unsigned byte) for the first picture, then Y, then CB, then CR for the next picture, and soon. Appropriate software and computer hardware will be available at the next meeting to playsuch sequences on a large CRT.
SIGN LANGUAGE AND LIP READING APPLICATIONS
SIGN LANGUAGE AND LIP READING APPLICATION PROFILE
Q15-G-40 (same as Q15-F-12 from G. Hellström Omnitor as editor) is a draft on the use of videocoding in sign language and lip reading applications. Q15/16 decided that it would like to havethe drafted content adopted in some form by the ITU-T. The plan envisioned for this is as follows:
1. The document should become a supplement to the H series rather than an appendix to H.263,since its content is relevant when using essentially any particular video codec design, not justH.263. The further work on standardization of this draft should proceed by Question 9/16(Accessibility to Multimedia for People with Disabilities - Rapporteur G. Hellström) and shouldbe coordinated with Question 15/16.
2. An appendix to H.263 should be added to refer to this new supplement when it is approved. Adraft of such an appendix was submitted at the meeting (Q15-G-47).
3. The document makes a reference to a particular video sequence data set which is available onthe PictureTel informal ftp site (ftp://standard.pictel.com/video-site/sequences/irene). However,if this data set is to be referenced in a formally-approved document such as an appendix to aRecommendation, then it should probably be made available in a more official manner from theITU-T itself. The current informal outside archiving of the data set may be inappropriate for adata set referenced in a published Appendix to a Recommendation. The ITU-T TSB will beconsulted regarding the potential difficulty of having the ITU itself make this electronic dataset available. The issue of the existence of a copyright on this data set also needs to beaddressed in the ITU archiving and publishing process evaluation.
WORKPLAN FOR H.263++As reported in Q15-G-07 (G. Sullivan, PictureTel), the ad hoc report on H.263++ enhancementefforts, five of the seven prior Key Technical Areas (KTAs) of H.263++ development wereaddressed in contributions to this meeting.
SCHEDULE AND KTAS
Two of the KTAs were adopted as draft annexes for H.263 version 3 at this meeting:
Two additional KTAs had contributions at this meeting which appear to show interest andincreasing maturity for the proposed features. Further refinement and consideration of theseproposals is requested:
• Affine Motion Compensation, coordination with T. Wiegand, J. Lainema, and M. Karczewicz• IDCT Mismatch Reduction, coordination with B. Andrews
One additional KTA remains of interest to the group despite a lack of contributions at thismeeting:
• Error Concealment (Normative or Informative), coordination with S. Wenger
The current list of Key Technical Areas for the H.263++ project was thus refined. The currentworkplan is shown below in Table 1; the new KTA list is provided in Table 2.
Meeting Date Type MilestoneSG16-4 May 1999 Study GroupQ15-H Aug 1999 Experts Last Formal Draft AdoptionsQ15-I Nov 1999 Experts Final Draft for DeterminationSG16-5 Feb 2000 Study Group DeterminationQ15-J Apr 2000 Experts Bug-checkingQ15-K Jul 2000 Experts Final Draft for DecisionSG16-6 Nov 2000 Study Group Decision
Table 1. H.263++ Workplan from March 1999.
Key Technical Area ExampleRelevantDocument(s)
Status Editors /Coordinators /Proponents
Error Resilient DataPartitioning
Q15-G-12Q15-G-13Q15-G-23Q15-G-24
Draft AdoptedAnnex V
Dong-Seek ParkJohn Villasenor(Annex editors)
Enhanced ReferencePicture Selection
Q15-G-18Q15-G-19Q15-G-20Q15-G-33
Draft AdoptedAnnex U
Thomas Wiegand(Annex editor)
Affine MotionCompensation
Q15-G-21Q15-G-29Q15-G-44
In collaborativeproposaldevelopment
Thomas WiegandJani LainemaMarta Karczewicz(KTA coordinators)
IDCT MismatchReduction
Q15-G-34 One proposalreceived
Barry Andrews(proponent)
Error Concealment(normative orinformative)
None No proposalsreceived
Stephan Wenger(proponent)
Table 2. H.263++ Key Technical Areas.
Q15/16 discussed whether all proposed H.263++ modifications must proceed on the sameschedule, and decided that this was not necessary, although it was desirable. The group alsodiscussed the issue of whether H.263 would continue to be incrementally enhanced indefinitely;Q15/16 decided to turn its primary focus toward H.26L. The plan adopted was to not adoptfurther new proposals of optional incremental enhancements to H.263 after Determination of thecurrent round of draft annexes (Determination target date: February 2000). However, proposalsthat have already begun collaborative KTA development by that time may continue to be refinedand evaluated for later Determination.
WORKPLAN FOR H.26L
Q15-G-08 (K. Hibi, Sharp) reports that the H.26L project continues to progress, with severaltechnical proposals at this meeting (described above) including:
• Q15-G-09 on balanced multiple description coding• Q15-G-25 on the Telenor H.26L coding design using variable block size motion compensation
and 4x4 difference coding• Q15-G-27 on the Strathclyde Coding Transform coding method• Q15-G-36 on the PACC wavelet coding method with overlapped block motion compensation
and control grid interpolation• Q15-G-30 on EZW-structured DCT coding
In addition to these proposals which were specifically targeted for H.26L, many of the othertechnical contributions also may apply to H.26L as well.
Table 3 shows the H.26L Workplan.
Mtg. Date Type MilestoneSG16-4 May ‘99 SGQ15-H Aug ‘99 Experts First Draft Text and Test ModelQ15-I Nov ‘99 ExpertsSG16-5 Feb ‘00 SGQ15-J Apr ‘00 ExpertsQ15-K Jul ‘00 Experts Final Major Feature AdoptionsSG16-6 Nov ‘00 SGQ15-L Apr ‘01 ExpertsQ15-M Jul ‘01 ExpertsSG16-7 Aug ‘01 SG DeterminationQ15-N Oct ‘01 Experts Bug-CheckingQ15-O Jan ‘02 Experts White Doc. GenerationSG16-8 May ‘02 SG Decision
Table 3. H.26L Workplan from March 1999.
REQUIREMENTS FOR VIDEO STREAMING
Q15-G-11 (G. Greenbaum, RealNetworks) provides guidance for the H.26L project in regard tocodec requirements for video streaming. Streaming is defined as real-time play (as opposed todownload and play) of video content, but perhaps with relatively high delay.
Media streaming has become very popular on the Internet, with thousands of radio stationsbroadcasting, hundreds of thousands of server sites, and ten of millions of registered players. Anumber of codec features can be supported in such environments, including asymmetricprocessing, inhomogeneous bit allocation, long temporal-axis analysis windows, retransmission oflost packets, error correction coding, dejittering of decoding time, dynamic switching of streamrates, CPU power scalability, bandwidth scalability, random access, etc. The properties desiredfor a video streaming codec are primarily to have high compression / low complexity decodingand packet-oriented (large packet, e.g., 0.5 to 1.5 kbytes per packet) operation over a widevariety of bit rate and channel characteristics (including mobile channels).
SCHEDULE, KTAS, AND FUNCTIONALITY DEVELOPMENT AREAS
The H.26L effort has continued to move forward, although no particular proposal fully meets allthe requirements for H.26L at this time.
According to the discussion on the similarities in technical natures of H.26L proposals realizedduring the evaluation of proposals, six Key Technical Areas of interest for the H.26L project havebeen identified as described below:
Inter frame prediction coding:
(1) Variable-size block-based segmentation-Quad-tree like decomposition of frame-Small block size to 8x8, 4x4
(2) Long-term memory-Increase candidates of reference materials for prediction-Combination with other prediction scheme (e.g., affine warping)
(3) Affine motion model-Adoption of six parameter affine motion model-Coding method and syntax of affine motion parameters-Searching of affine motion parameters
Inter frame residual coding (also applicable to Intra texture coding):
(4) 16-sampled waveform coding (4x4)-Coding with smaller block size than 8x8 DCT
(5) VQ, EZW with DCT, multiple waveform coding-Adoption of (variable-dimension) VQ scheme-Embedded EZW structured coding-Selection from multiple coding modes
Intra frame coding:
(6) Directional (pixel-prediction) Intra coding-Improvement of prediction in Intra coding-Consideration of activity direction of picture
Note: Coordination with JPEG-2000 to obtain an information on the state of the art of Intracoding technology would be helpful.
Functionality development areas to be covered by H.26L were also discussed. All functionalitieslisted in the H.26L requirement document should be finally supported by the H.26L standard.The following list shows the functionality area to be worked on in the H.26L development process:
• High compression performance-Capable of 50% or greater bit rate savings with respect to ’98 H.263v2 (DFIJT) at all bit
rates• Simplification “back to basics” approach
-Adoption of a generally simple, straightforward design using well-known building-blocks-For example, use of one VLC for all parameters to be coded
• Flexible application to delay constraints appropriate to a variety of services-Low delay (e.g., no B pictures) for real-time conversational services-Moderate delay usage appropriate for sever-based streaming application
• Error resilience-Packet loss resilience-Mobile channel corruption resilience
• Complexity scalability in encoder and decoder-Asymmetry of encoder and decoder processing complexity-Scalability between amount of encoder processing and achievable quality
• Full specification of decoding (no mismatch)-Resolve mismatch problem (e.g., integer transform, VQ,…)
• High quality application-Performance improvement in higher bitrate-Applicability to entertainment-quality applications
• Network friendliness-Ease of packetization-Information priority control
The current project status can be summarized as follows:
1. Significant progress on compression performance:-Approximate potential of 50% bit rate savings (relative to H.263+DFIJT)-Performance improvement maintained at high bit rates
2. Can be achieved with “clean back-to-basics” approach3. Full specification of decoding expected4. Progress needed on other aspects:
-Study and progress on delay characteristics-Error resilience-Network friendliness-Complexity scalability
PLANS FOR FUTURE WORK, AND AD HOC COMMITTEE DESIGNATIONS
The workplans for the H.263++ and H.26L projects and for deployment of prior video codecstandards were reviewed. The following four ad hoc committees were established to progress thework between now and the next meeting:
Error Resilient Simulation Conditions and Evaluations S. WengerTest Model and Software Development K. HibiH.263++ Development G. SullivanH.26L Development K. Hibi
COMMUNICATIONS STANDARDS REVIEW ALSO PUBLISHES:
Communications Standards Summary (ISSN 1075-5721), a quarterly publicationreporting on all active projects and recently completed standards of the TIA’s(Telecommunications Industry Association’s) TR-committees. Authorized by TIA.
For more details visit http://www.csrstds.com. To receive a complimentary issue ofeither of CSR’s technical journals, please contact Elaine Baskin, tel +1 650 856-9018,fax +1 650 856-6591, e-mail: [email protected]
ADDENDUM TO THE REPORT OF Q11/16, FEBRUARY 17 - 19, 1999,MONTEREY CA
The following is a list of companies who have submitted patent statements regarding MPEG4,from ISO/IEC JTC1/SC29/WG11 N2599, December 1998. It was also published as Annex A indraft 3 of the Q11/16 meeting report, Q11-I-22d3. An "x" indicates that the patent statementapplies to that specific part of the standard.
Systems Visual Audio ReferenceSoftware
DMIF
Alcatel x x x x xAT&TBBC x x x x xBosch x x xBritish Telecommunications x x x x xCanon x x x x xCCETT x x x x xColumbia University x x x x xCreative x x xCSELT xDEmoGraFX x xDirecTV x x xDolby x x x x xEPFL x x xETRI x x x x xFhG x x x x xFrance Telecom x x x x xFujitsu Limited x x x x xGC Technology Corporation x x xGeneral Instrument x xHitachi x x x x xHyundai x x x x xIBMInstitut für Rundfunktechnik x x x xInterTrustJVC x x x x xKDD Corporation x xKPN x x x x xLG SemiconLucentMatsushita x x x x xMicrosoft x x x x xMITMitsubishi x x x xMotorola x xNEC Corporation x x x x xNHK x x x x xNokia x x xNTT x x x x xOKI x x x x xPhilips x x x x xPictureTel Corporation x xRockwell x x x x xSamsung x x xSarnoff x x x x xScientific Atlanta x x x x xSharp x x x x xSiemens x x x
REPORT OF ETSI TIPHON MEETING #12MARCH 1 - 5, 1999, PHILADELPHIA, PA, USA
To receive information on how to become a member of the any of the TIPHON mailing lists, pleasesend a message to “[email protected]” with the single word “HELP” in the body of themessage.
ETSI has set a mail archive for the TIPHON list, which can be browsed at:http://list.etsi.fr/tiphon.html. Mails and attachments are published in MIME format; feedback iswelcome ([email protected]).
This meeting was paperless: only the agenda and the document list were printed. Intelsat hadset up 256 kbit/s internet connectivity, which worked very reliably. The local networkingcapabilities as set up by the support officer and the STF enhanced the efficiency of the meetingand allowed delegates to update files during the week. Intelsat also provided a demonstration ofthe IP Telephony application showing the feasibility of satellite-based communication using IP-based networks in conjunction with TIPHON-Net. 12TD-90 provides a diagram of the systemand equipment used.
H. Schink (Siemens), TIPHON Chair, reminded participants of ETSI’s IPR policy and invitedattendees to announce IPR of relevance to TIPHON. No announcements were received.
The goals for this meeting (12TD-01) and the achievements include:1. DTR/TIPHON-01003 (TR 101308, Requirements for service interoperability; Scenario 3) is at
first draft2. DTR/TIPHON-02005 (TS 101316 Requirements N [MGC to MG] reference point) was
approved by TIPHON3. Stable text was provided for DTS/TIPHON-03005 (TS 101322 Signaling for basic calls and
inter domain calls, between an H.323 terminal and a terminal in a SCN, Phase II; Scenario 1+ Scenario 2)
4. DTS/TIPHON-03006 (TS 101323, Interoperable security profiles) was approved by WG3(special group on security)
5. DTS/TIPHON-04002 (TS 101325, Naming and addressing: Scenario 2) was approved by WG46. DTR/TIPHON-05002 (TR 101330, Minimum levels of QoS for the establishment of TIPHON-
compliant systems) is at first draft7. DTR/TIPHON-05006 (TR 101329 v1.3.0, General aspects of QoS) was approved by TIPHON8. Stable text was provided for DTR/TIPHON-06002 (TR 101335, Phase 2 verification and
demonstration implementation, implementors handbook and test reports); to be approved bothby WG6 and TIPHON in Bangkok (May 3-7)
9. DTS/TIPHON-06004 (TS 101337, PICS for TIPHON end-to-end systems, Phase 1) wasapproved by TIPHON
10. Stable text was provided for DTS/TIPHON-06005 TS 101338, PICS for TIPHON end-to-endsystems, Phase 2)
11. Stable text was provided for DTS/TIPHON-06006 TS 101339, PICS for TIPHON end-to-endsystems, Phase 3)
12. Stable text was provided for DTS/TIPHON-06007 (TS 101340, test specifications forTIPHON systems)
13. DTR/TIPHON-07001 (Analysis of existing roaming techniques applicable to TIPHON mobilityservices) was approved by WG7 as stable text
14. The work program (12TD-18) and project plan (12TD-19) were both updated.15. The liaison plan was updated16. Marketing plan was not updated
Scenario 1 is interworking from IP terminals to SCN terminals. Scenario 2 is interworking fromSCN terminals to IP terminals. Scenario 3 is interworking from SCN terminals to IP networks toSCN terminals.
TIPHON had to appoint new Chairs for WGs 3, 5 and 7. For WG5, one candidate (M. Buckley)was nominated and approved unanimously by the opening plenary.
The Chair first outlined the voting procedure. The Chair then stated that Dr. M. Ramalho(Bellcore), a candidate for WG3 Chair, desired to make a point of clarification statement beforethe vote.
M. Ramalho noted that many companies, including the company he represents (Bellcore), weredeveloping Voice over Packet (VOP) products that use a non-TIPHON Call ConnectionManagement (CCM) architecture. He noted that discussions in previous TIPHON WG3 meetingswere prematurely cut off by the mere mention that a protocol being presented was derived from anon-TIPHON CCM, even if such protocols could find utility in a TIPHON architecture. Hementioned that this, in his view, was silly. The primary reason that he considered the WG3Chair was to help facilitate such discussions, hopefully to the benefit of all VOP architectures,including TIPHON’s.
M. Ramalho did note, however, that the WG3 meeting of the previous day was different. Henoted that G. Kimchi (who was interim Chair) did not cut off protocol discussions involving a non-H.323 interface. His point of clarification was to ask the other candidate (G. Kimchi), theTIPHON Chair, and the audience if discussion of non-TIPHON CCM derived protocols would beallowed in the future. If so, M. Ramalho’s primary reason to run for WG3 Chair would be moot.
G. Kimchi responded that if he were voted WG3 Chair, he would allow such protocol discussion tooccur to the extent that there were contributions on them. The Chair responded that he did notsee why such discussion would be disallowed in the future. The Chair then solicited commentsfrom the audience. L. Spergel (Lucent), Chair of WG4, offered a statement that perhaps theprevious WG3 function did not naturally allow for discussion of non-TIPHON CCM derivedprotocols. However, she saw no reason why such protocol discussion, if at all related to theTIPHON architecture, should be excluded in the future. The Chair asked for further commentsfrom the audience. There were none. The Chair then noted that discussion of protocols that couldfind utility in the TIPHON architecture could be discussed freely in TIPHON, even if they werederived or could be used in non-TIPHON CCM architectures. This fact will be reflected in theTIPHON#12 meeting minutes.
M. Ramalho then stated that his primary reason for desiring the WG3 Chair was moot, noted theextensive VoIP protocol expertise of the other WG3 candidate (G. Kimchi), and formally requestedthat his name be withdrawn from consideration for WG3 Chair. The Chair, noting that therewere no other candidates for WG3 Chair, asked for the proclamation of G. Kimchi to be the newTIPHON WG3 Chair. This was unanimously approved.
Discussions among the three candidates for WG7 on an optimal distribution of tasks and theindividual goals and objectives yielded the idea, that for WG7 it would be most appropriate tocreate an additional vice-Chair position. Its specific tasks are the liaison activities which areexpected to be rather extensive and time-consuming as compared to the other WGs. The Chairshould focus on the technical work progress.
Further, candidate M. Shore (Nokia IP Telephony Unit) indicated that she and her companywould support the other two candidates in their commitment to WG7, providing her moreflexibility to concentrate, for example, on security issues. Further the other candidates agreed toaccept the work split as proposed by the Chair.
The Chair, noting that the organization was supported by the candidates, proposed R. Zwart asChair and T. Hatala as vice-Chair to the meeting. This was unanimously approved.
The newly elected officials are:
WG3 Chair: G. Kimchi (VocalTec)WG5 Chair: M. Buckley (Lucent Technologies)WG7 Chair: R. Zwart (AT&T Communications UK Ltd.)
The Chair reminded the meeting that all officials have terms limited to two years. Thus thefollowing positions have to be elected or re-appointed:
TIPHON ChairTIPHON Vice-Chair for external liaisonsTIPHON Vice-Chair for marketingWG2 ChairWG4 ChairWG6 Chair
This will be done during the upcoming TIPHON 13 meeting. Candidatures for the TIPHONChair and WG Chairs are to be submitted to the ETSI secretariat ([email protected]) by April 1,1999.
The TIPHON 11 meeting report from Sophia Antipolis (Jan. 1999), 12TD-05, was presented by L.Vreck (TIPHON project support officer) and reviewed by the meeting. An updated version willbe provided as a permanent document.
H. Schink, Chair, presented the results of the last meeting survey. The ratings indicate that theoverall satisfaction of the participants is unchanged and quite positive. The trend shows anincreasing satisfaction with the use of EDH at the meeting but also shows that the meetingfrequency is at the upper limit.
UPDATE ON TIPIA
In a separate session chaired by H. Schink, TIPHON Chair, A. Dilber (AT&T and vice-Chair ofTIPIA) introduced the current situation of TIPIA (TIPHON IP Telephony ImplementationAssociation). R. Stastny (OEFEG) provided more in depth information on the goals and workingstructure of TIPIA. 12TD-118 provides an overview of TIPIA; its mission is to provide aharmonized framework among members (service providers, IP telephony manufacturers, andothers) to deploy seamless and interoperable IP telephony applications utilizing ETSI TIPHONspecifications.
TIPIA held its first meeting in Vienna and produced drafts of Statutes, working structures andthe Implementation agreement. The following messages are of relevance for TIPHON; the TIPIAofficials clearly stated the draft character of the documents and invited comments for their nextmeeting:
• TIPIA fully supports TIPHON and will use its specifications and provide input to TIPHON onrequirements
• TIPIA is open for operators (full members), manufacturers (associated members), andorganizations (observers)
• The Chair of TIPHON will be an ex officio member of the TIPIA board• The focus of TIPIA is the area of service deployment
TIPHON appreciates the support from TIPIA and a number of participants will investigatemembership in TIPIA.
SPECIALIST TASK FORCE (STF) ACHIEVEMENTS
12TD-30 (R. Scholl, ETSI-TIPHON STF leader) provides details about the recent STF activities.The STF report was approved. S. Cadzow (Cadzow Communications Consulting) was welcomedby the meeting as a new member of the STF team.
MARKETING
H. Schink, Chair, reported about recent and coming events with participation by TIPHONofficials as speakers. Major events are the PBX2000 conference, INET99 and severalconferences organized by IBC and IIR. In particular, a press release was drafted during thismeeting by L. Vreck (TIPHON support officer) with the support of several companies clarifying
the finalization of Phase 1 and indicating the future work plan. It was to be sent out one weekafter the meeting to give the companies time to cross check with their press departments. Also,participating companies were invited to use the press release as a basis for separate pressreleases.
ITU-T SG16
ITU-T SG16 Q13-14 held an interim (Rapporteurs) meeting in Monterey, Feb. 15-19, 1999 (seereport in CSR Vol. 10.3). The main focus areas were:
Gateway DecompositionTwo competing contributions presented protocols as candidates for the ITU-T media gatewaycontrol protocol: MGCP and MDCP. After controversial discussion, including indicative polling,MDCP was accepted as a basis for further work.
Inter-Domain CommunicationThe scope of H.225.0 Annex G was extended to include not only address resolution but alsopricing information exchange, access authorization, and usage reporting.
SS7 InterworkingIt was determined that the interworking between ISUP and H.323 signaling needs to bestandardized. This will become part of a new annex of H.246. No consensus could be reached on“SCN Tunneling mechanisms.”
Supplementary ServicesA further set of H.450-based Supplementary Services will be Decided in May, 1999. That is,besides H.450.1 (Generic), H.450.2 (Transfer) and H.450.3 (Diversion), the following H.450features will be approved as ITU standards by in May, 1999: H.450.4 (Hold), H.450.5 (Park,Pickup), H.450.6 (Call Waiting), and H.450.7 (Message Waiting Indication). Further H.450-based features are on the work program list.
MSAF
A. Dilber, AT&T, reported about MSAF (Multimedia Services Affiliate Forum) activities,emphasizing the coming meeting March 22-24, 1999, in Santa Barbara, CA (seehttp://www.msaf.org).
VOICE-OVER-PACKET INITIATIVE
M. Ramalho (Bellcore) spoke briefly concerning a new Bellcore initiative for Voice over Packet(VOP) Generic Requirements (GRs).
The intent of the VOP GR process was not to define new protocols (the primary question that hehad received from several TIPHON delegates), but rather to specify existing or newly createdprotocols for use in VOP systems. M. Ramalho also stated, as a side comment, that it was likelythat the legal wording in the Bellcore documents probably reserved Bellcore’s right to define theprotocols if they were inappropriate in some dimension. A recent US telecom act referencedBellcore by name as the company responsible for the US Generic Requirements; there are someconstraints in the GR creation process that are mandated by US law.
The primary intent of the GRs would be to add specificity as to how the protocols should be usedin a larger system context. This is similar to the manner in which existing Bellcore GRs (or othertelecom industry specification) are used today.
Seven proposed GR areas cover VOP requirement areas, such as “Operations and Management,”“Call Connection Management,” “Services,” “Performance,” “Billing,” and a few others. Thenumber of GRs actually produced would be determined by industry interest to fund them(individual GRs would be funded individually by one or more companies). The work on the GRs isscheduled to begin in April with the “Phase one requirements” for the funded GRs scheduled fromSeptember 1999 through January 2000.
M. Ramalho offered to be the TIPHON/Bellcore liaison for the Bellcore VOP initiative; this wasaccepted by the meeting.
J. Vandenameele (Alcatel) reported that the ITU-T created an Internet Protocol (IP) project forcoordinating all IP-relevant work in all ITU-T study groups. Looking beyond the ITU-T activities,it is desired that ETSI TIPHON and the IETFalign their work as much as possible.
ITU-T SG15
M. Shore (Nokia) reported about the new question Q21/15 dealing with transport equipment.Other questions in SG15 might be of interest for TIPHON as well. A liaison will be draftedduring this meeting and directed to SG15 WP2.
OCG AND ETSI BOARD
H. Schink (Siemens) reported on the results of the last OCG (ETSI Operational CoordinationGroup) meeting and the ETSI Board meeting. While the OCG supported TIPHON’s request foradditional funding within their possibilities, the ETSI board invited the TIPHON Chair to give anupdate on the situation of TIPHON and the rational for the amendment of its Terms of Reference(ToR). As a consequence, TIPHON’s funding request was deferred to the next board meetingMarch 24.
MSF LIAISON
L. Spergel (Lucent Technologies) reported on a liaison received from MSF (MultiserviceSwitching Forum), 12TD-22 (D. McDysan, MCI). The MSF thanked TIPHON for their liaisonand offered to provide MSF documents (which are not publicly available) as appropriate. 12TD-129 is the response from TIPHON which includes DTS/TIPHON 02005, Requirements for aProtocol at Reference Point N; Media Gateway Controller to Media Gateway.
ANSI T1 LIAISON
G. Peterson (Chair of ANSI T1) gave a presentation, expressing the desire of T1 for efficient workwhich would include full cooperation with ETSI TIPHON, giving benefit for both organizations.With regard to TIPIA he proposed to set up a cooperative contact to investigate futureopportunities for collaboration. The liaison in response to Committee T1 and TIA is in 12TD-132(L. Spergel, Lucent Technologies) which notes the approval of TIPHON scenario 1 specificationsand the desire for cooperation on lawful interception issues.
NEW WORK ITEMS
Four new work items were approved (proposed through the cited contribution):
12TD-108: Lawful Interception in TIPHON and TIPHON access networks (S. Cadzow, ETSISTF114)
12TD-114: Revision of TS 101 321 (open settlement protocol) (R. Brennan, GRICCommunications; S. Thomas, TransNexus; K. Sambor, Datacom; M. Lucchina, Cisco; and R.Stastny, PTA/OEFEG)
12TD-120: Interworking specification for H.450 and QSIG/DSS1 (J. Korpi, E. Hovarth, and K.Klaghofer, Siemens)
12TD-128: Packetization and code-points for the TIA/EIA IS-641 Enhanced Full-Rate SpeechCodec in H.323 systems (G. Kimchi, VocalTec)
TIPHON members were invited to review the new work items until April 5, 1999. Commentswere to be directed to the TIPHON Chair, the WG Chair, and the editor.
WORKING GROUP 1, REQUIREMENTS
The WG1 chair is L. Klostermann (Ericsson). 12TD-12 is the report of this meeting. 12TD-06 isthe WG1 agenda.
DTR-01003, REQUIREMENTS FOR SERVICE INTEROPERABILITY, SCENARIO 3
The first draft of DTR-01003, Requirements for Service Interoperability, Scenario 3, wasproduced, with the WG1 chair as editor.
There was a discussion on H.450 Supplementary Services. 12TD-39 (J. Korpi, K. Klaghofer, E.Horvath, Siemens) proposes to include H.450 supplementary services in the scope of TIPHON.12TD-89 (L. Klostermann, Ericsson) analyzes two H.450 supplementary services, Call Transferand Call Forwarding, mainly with regards to service flexibility; it concludes that the CallForwarding service, especially, as a supplementary service would unnecessarily limit flexibilityand service differentiation. It was agreed that it requires more study, and that it is too early forTIPHON to adopt the H.450 supplementary services.
TIPHON COMPLIANCE
12TD-55 (S. Moore, Siemens) addresses the issue of TIPHON compliance, noting that the term isused everywhere in the documentation, but not defined. The paper proposes a definition. Therewas a short discussion on whether one should speak about a TIPHON compliant system or aTIPHON compliant network. It was agreed that “system” is better, partly because TIPHON canbe viewed as an application system on top of a transport network, and because TIPHONcompliance also applies for equipment which is not part of a network.
Discussion of 12TD-55 then led to the issue of consistency of deliverables. Requirementsidentified in the WG1 document for phase 2 are to be covered in phase 2 output of WG2 and WG3.It was decided to take up the work of requirements tracing already anticipated in Annex B of therequirements document, and to distinguish between “specified” and “tested” (among others). Thiswork will be performed in a slightly larger context of progress assessment by the STF incollaboration with the WG chairs.
BUSINESS ROLE MODELS
12TD-47 (P. Sibjen, Lucent) describes the TINA (Telecommunication Information NetworkingArchitecture) business model. http://www.tinac.com/97/sa50-main.pdf provides the servicearchitecture version 5; http://www.tinac.com/97/bm-rp.pdf provides the business model andreference points. 12TD-29 (L. Strahs, AT&T) contains material on clearing house models. 12TD-49 (H. Wermescher, Infonova, K. Sambor, Telekom Austria) discusses different kind of servicesrequired to enable interoperability between IP telephony providers. It was concluded that most ofthe roles mentioned in 12TD-29 and 12TD-49 are broker roles; it was decided that the authorswould (virtually) get together with the editor to incorporate material to describe these differentbroker roles. The section on certificates and trust models will not be incorporated at the moment;more clarification will be provided for the next meeting. It was decided to include the retailer roleas well in the role model, while the exact boundary between service provider and retailer needssome more discussion.
USER ORIENTED BACK-END SERVICES
12TD-50 (H. Wermescher, Infonova, L. Strahs, AT&T, and K. Sambor, Telekom Austria)proposes different global back-end services (BES). It was clarified that the intention is not tostandardize these services, but to provide these services as a benchmark of the kind of servicesthat TIPHON should enable in their architecture and protocols. It was also clarified that theseservices might also be offered within a domain.
It was decided that a new section on “user oriented back-end services” will be created; it willinclude a description of text on the targeted services, in combination with the above clarification.It was also agreed that the contributor and editor will look at the more detailed requirements ofthe contribution.
This text, as well as the text on business models, will be send out on the E-mail exploder forcomments, in preparation for input at the next meeting.
12TD-63 (M Potter, S. Condie, BT Labs) discusses the need for IVR (Interactive Voice Response)interaction. It was decided to make sure that the new back-end services include the need forannouncements, etc. There will be a more detailed contribution at the next meeting.
NA8 LIAISON
12TD-101, a liaison from ETSI NA8 (Network Architectures), states that they are in the processof finalizing TR/NA-080301 (12TD-102) on parameters and mechanisms for charging in IPnetworks. After a short review, it was concluded that NA8 mainly deals with charging at IPlevel, while TIPHON focuses on charging and accounting at the telephony application level.
There were some remarks on whether accounting, charging, and billing were assumed to bewithin one business domain, as one of the figures in TR/NA-080301 suggests.
There is no hurry to draft a return liaison for the moment, since the next NA8 meeting is inSeptember. It was thus decided that WG1 will look at the report before the next meeting toprovide a more detailed liaison. Apart from comments on their work, the liaison to NA8 will alsocontain an overview of the WG1 work at the application level.
LAWFUL INTERCEPTION
12TD-98 (J. Horrocks, DTI) contains supporting text for the Lawful Interception requirementssubsection 8.7 of DTR-01002 (Requirements for Service Interoperability, Scenario 2), which wasagreed. (See Security report below.)
WORKING GROUP 2, ARCHITECTURE
The WG2 chair is J. Vandenameele (Alcatel). 12TD-13r2 is the report of the WG2 meeting. Theagenda is 12TD-07.
The major objectives of the WG2 meeting were:
• To finalize DTS/TIPHON-02005 (Requirements for a Protocol at Reference Point N: MediaGateway Controller to Media Gateway) and approve it at the WG2 level.
• To start work on DTS/TIPHON-02003 (Network Architecture and Reference Configurations,Scenario 3) covering the architecture for Scenarios 1 to 4, and to agree on an architecturalmodel covering Scenario 3.
INITIAL WORK ON DTS/TIPHON-02003
J. Holm (Ericsson) volunteered to be the editor for DTS/TIPHON-02003. His candidature wassupported by the full meeting.
DTS/TIPHON-02003 ARCHITECTURE FOR SCENARIO 3
12TD-052 (B. van Doorselaer, J. Vandenameele, Alcatel) proposes that TIPHON study andanalyze different reference architectures, call models and protocols for scenario 3, prior todecision. It introduces the concept of an M reference point between peer Media GatewayControllers.
12TD-062, Architecture for TIPHON Scenario 3 (S. Condie, BT), provides a conceptual modelconsisting of four planes: Intelligence plane, Call control plane, Device Control plane, and Deviceplane. It maps this model on an extended TIPHON architectural model including both an ingressand egress decomposed gateway and proposes that the latter be adopted for Scenario 3.
12TD-048 (P. Sijben, Lucent) proposes a finer grained definition of the existing TIPHONarchitecture reference points. It further states that the current TIPHON architecture covers allneeds for Scenario 1, 2 and 3 and suggests text to be incorporated in DTS-02003 to note thisadditional insight.
12TD-078 L. Kristiansen, J. Holm, Ericsson) proposes to split the Gatekeeper into anetwork/resource part (n-GK) and a User/service part (u-GK). It also shows how the TIPHONscenarios fit into this architecture. The architecture allows for the deployment of only n-GK forthe bypass market and still provides the full features for users at PCs.
It was agreed that these four contributions will be used as an input to the first draft of thearchitectural model for Scenario 3 to be used for DTS/TIPHON-02003. A long discussion tookplace. The meeting agreed to create a strawman proposal for an Architectural model that coversScenarios 1 to 4. The draft should reflect the basic agreements reached in order to solicit furthercontributions to be discussed at the TIPHON13 meeting. The major agreements of this meetingwere: to describe a possible decomposition of the Gatekeeper, to create a model with peer MGCshaving a new reference point, and to start describing the nature of that new reference point.
DTS/TIPHON-02003 - FUNCTIONAL ELEMENTS AND REFERENCE POINTS
12TD-028 (I. Rytina, C. Groves, Ericsson) outlines SS7 functional requirements for the J-reference point in the TIPHON Gateway decomposition. It proposes to use these requirements asa base for discussion for, and inclusion in, the Network architecture and reference configurationsdocument DTS/TIPHON-02003. WG2 agreed to take 12TD-28 as the basis for requirements forthe reference point J. The meeting agreed that the requirements should be extended to coverother protocols than SS7, and suggested other editorial changes. The meeting asked J. Holm(edtior) to implement the changes. T. Taylor (Nortel Networks) proposed to send this part to theIETF SIGTRAN mailing list as an input to the requirements work.
12TD-035 (J. Talbot, Nortel Networks) indicates that the Media Gateway Controllers (MGCs) asused by IETF groups MEGACO and SIGTRAN at one side and TIPHON at the other side do notexactly match. It proposes that TIPHON raise the potential confusion with the IETF and proposealignment on a common terminology for this combination. It offers a diagram in which an entitycalled “call and gateway manager” includes the GK and the MGC in the same box. In discussion,it was pointed out that IETF MEGACO addresses a number of functions at the MGC side of theinterface, but does not define the split between the GK and MGC. Hence this could give thewrong impression that some of the functions belonging to the GK as defined by TIPHON belong tothe MGC. Hence it was concluded that there is no explicit contradiction and that no action isrequired from WG2.
12TD-057 (E. Martinez, Motorola) proposes a new reference point I in order to support NumberTranslations and IN services using TCAP (Transaction Capabilities Application Part)Interactions with an H.323 Gatekeeper. The meeting agreed that the contribution mixes physicaland functional considerations. The proposed link between the Gatekeeper and the IN STP(Signaling Transfer Point) is already covered by reference point G since the service described ispart of the Back End Service. WG2 agreed that more thought should be given to how such a linkworks and solicits proposals for the next meeting. WG2 also agreed that there is no need tocreate a new reference point I.
In the discussion, the need and the nature of reference point F was also questioned. As thisreference point has not yet been discussed, contributions are requested for the next meeting.
12TD-046 (P. Guram, Motorola) discusses the requirement and mechanism for carrying TC-userinformation over IP; it suggests, if agreed, to send a liaison statement to ETSI SPS1/SPS3/NA6requesting their input and help for completing this work. WG2 agreed to discuss thiscontribution together with the liaison from SPS3 (see liaison activities below).
FIREWALLS
12TD-033 (K. Sambor, A. Steiner, Telekom Austria) considers the inclusion of a solution for the“H.323 Proxy / Firewall” (Borderwall) problematic in DTR-02003. It provides text for inclusionin the next version of this deliverable.
WG2 discussed 12TD-033. The meeting agreed that the architectural issues related toBorderwalls/Firewalls have to be addressed in the DTS/TIPHON-02003. However the
considerations required in this case are of a different nature than those leading to an architecturemodel. Hence the way in which it will be handled in the Architecture deliverable needs furtherconsideration. WG2 agreed to copy the major part of 12TD-033 into an Annex to the first draft ofthe deliverable and solicit further contributions.
FIRST DRAFT OF DTS-02003
WG2 chartered a drafting group chaired by J. Holm (editor) to create the first draft. The resultis DTS/TIPHON-02003 V.0.0.1. The new model comprises three layers, i.e., Service, Callsignaling, and Media. The new draft also contains the new text related to the reference point Jand the Annex related to Borderwall/firewall.
Contributions are solicited on:
• Which sections of ETSI TS 101 313 (the former DTS/TIPHON-02002) can be kept for the newdeliverable and which ones have to be reviewed; New text for the latter;
• Refinement of the new proposal for the Reference architecture for Scenarios 1 to 4: descriptionof information flows, definition of the reference points;
• Comments to “Requirements for the information flow CB” (at the reference point J);• Need for the former reference point F;• Back-end services (BES): further definition (based on possible back-end services as defined by
WG1), reference points, information flows, interfaces, existing protocols;• Identification of the architectural issues related to Firewalls and proposal for a model
consisting with the Architecture model.
FINALIZATION OF DELIVERABLE DTS/TIPHON-02005
12TD-040 (S. Moore, Siemens) provides a number of comments on DTS/TIPHON-02005 V0.1.1.Not all of the comments were discussed by the full WG2 meeting. WG2 chartered a draftinggroup chaired by B. Van Doorselaer (Alcatel Bell) to further discuss the comments in 12TD-040and implement the agreed changes.
The result is DTS/TIPHON-02005 V.0.1.2. The full WG2 meeting discussed some additionalimprovements proposed by S. Moore (Siemens), resulting in version V.0.1.3. WG2 approvedDTS/TIPHON-02005 version 0.1.3.
LIAISON ACTIVITIES
Related IETF WGs
ETSI STF114 has submitted DTS/TIPHON-02005 V.0.1.1, the output of TIPHON11, as anupdated draft to IETF MEGACO, where it has been taken as an input to the MEGACOrequirements draft.
T. Taylor (Nortel Networks) proposed to bring the newly created text on the requirements for theformer TIPHON reference point J to SIGTRAN.
Interim Meeting of SG16 Q13-14
T. Taylor presented the outcome of the Interim meeting at Monterey (12TD-119, Reconciliation ofETSI TIPHON and ITU-T SG16 Architectures). It reflects TD-24 from the Q14/16 Montereymeeting (see report in CSR Vol. 10.3) and forms the basis of the current draft of H.gcp (APC-1500). He pointed out that the architecture model of H.gcp is based on physical considerations,while TIPHON’s model is more a functional one.
WG2 proposed sending the approved DTS/TIPHON-02005 to the next SG16 meeting in Santiago,Chile (May, 1999). WG2 considers that the new model in DTS/TIPHON-02003 is not matureenough to be sent to SG16. This will be reconsidered after the next TIPHON meeting.
Liaison Statements
WG2 discussed the liaison statement received from the MSF (Multiservice Switching Forum) in12TD-022. No response was requested. A proposal to send them our Deliverable DTS/TIPHON-
02005 was accepted. The draft of DTS/TIPHON-02003 was considered to be mature enough,although it might be sent to the MS Forum after the TIPHON13 meeting. The return liaisonsending DTS-02005 is in 12TD-129.
WG2 also discussed the liaison statement received from ETSI SPS3 provided in 12TD-027. Theliaison contains five questions related to the use of Intelligent Networks in an H.323 environment.Most of them cannot be answered by WG2 as TIPHON did not address the SCN Call models.WG2 does see a role for IN in the area of Back End services, although a lot of work is still to bedone in this area. A liaison statement will be sent back to SPS3 along these line. TIPHON willalso propose a joint meeting.
12TD-046, SS7 TC Messaging over IP (P. Guram, Motorola), was not received as a liaisonstatement, although it proposes a close liaison with SPS, in particular SPS3. As it relates to theformer reference point J, it was proposed to send them our requirements for this reference point.WG2 agreed to combine this into one liaison together with the one on IN.
WORKING GROUP 3, CALL CONTROL
The WG3 chair is G. Kimchi (VocalTec). The meeting report is 12TD-14r1. 12TD-08 is the WG3agenda. The goal of the meeting was to achieve stable text on DTS-03005.
DTS-03004, INTER-DOMAIN PRICING, AUTHORIZATION, AND USAGE EXCHANGE
12TD-25, Alternative User Authentication Format for TS 101 321, and 12TD-26, Additions to TS101 321 Usage Indication Message (both from E. Leckner, M. Hayden, R. Brennan, GRICCommunications), suggest that a new version of DTS-03004 be created with editorial andprocedural changes. Both documents were accepted as basic text for version 2 of DTS-03004.DTS-03004 version 2 will be available at the next TIPHON meeting.
DTS-03005, SIGNALING FOR BASIC CALLS AND INTER-DOMAIN CALLS BETWEEN AN H.323 TERMINALAND A TERMINAL IN AN SCN, PHASE II: SCENARIO 1 + SCENARIO 2
12TD-53, Protocol Selection for Reference Point D (VocalTec, Ascend, Siemens, Lucent, ITXC andOzEmail Interline), recommends that the Direct-Routed-Call (DRC) model, ITU-T H.225.0 AnnexG (Inter-Gatekeeper Communications) be assigned as the singular protocol for TIPHON referencepoint D, and that in the case of a Gatekeeper-Routed-Call model, H.225.0 signaling with tunneledH.245 signaling shall be used in addition to H.225.0 Annex G as the only protocols for TIPHONreference point D. The contribution was accepted; the editor will incorporate the new mandatoryrequirements into DTS-03005.
It was noted that the latest WG2 deliverable removed references to the DRC model. Afterconsulting with the WG2 chair, this was identified as an editorial mistake, and will be correctedin next version of DTS-02002 and in the first text of DTS-02003.
To clarify, TIPHON systems shall support GRC, and should support DRC: as the GRC model is asuperset of the DRC model (being a case of co-location of the call-signaling function within theGatekeeper), the DRC model is supported by all TIPHON systems.
12TD-56 (S. Moore, Siemens) provides detailed comments (editorial and technical) onDTS/TIPHON-03005 V0.1.1. Most of the technical points were accepted and will be incorporatedinto the draft.
12TD-59, Call signaling for scenario 2 (G. Kimchi, VocalTec), identifies the call flows andprotocols that must be used to enable Phone to PC services. It was accepted; the editor willincorporate new text and flow diagrams into DTS-03005.
12TD-72 (E. Sion, VocalTec) proposes text to clarify the use of information returned by theGatekeeper in the ACF message in subsequent SETUP messages. It was accepted; the editorwill add clarification that the EP shall hide the translated (returned) number, and if the networkwishes to protect information from a hacked terminal, it should use the GRC model withpreGrantedAdmission.
12TD-73 (E. Sion and G. Kimchi, VocalTec) proposes clarification on the use of RTP within aTIPHON endpoint, specifically with regard to the number of audio frames that are sent andreceived in a single RTP packet. The contribution was accepted. The editor will incorporateclarification on the H.245/RTP mandatory requirements into DTS-03005. The draft of DTS-03005 from this meeting is 12TD-100, DTS-03005 version 0.2.1.
12TD-76, In-band before connect (J. Holm, Ericsson), notes that the introduction of ISUP in anH.323 network causes some problem regarding the interworking with PSTN, and addressesanother interworking issue. 12TD-116, Generation of Ringing Tone (J. Holm, Ericsson, andSiemens), presents a solution, which was adopted by the meeting.
12TD-79 (P. Cordell, BT Labs) proposes amendments to Figures B1 and B2 in DTS/TIPHON-03005 V.0.10.1. Pre-Opened channels (through connection before charging) were not accepted inSG16 Q13, so cannot be accepted here. An alternative method (being considered by Q13/16) is toallow fastStart in the middle of a call. It was agreed to add SetupAck, with clarification that it isan optional message. A “Media open both ways” arrow will be added after Connect as aclarification.
CODER ISSUES
12TD-036 (same as APC-1494 presented at the Q12-14/16 meeting Feb. 1999, R. Roy, K.Patnam and R. Cox, AT&T) is a description of the TIA/EIA IS-641 Enhanced Full-Rate SpeechCodec for H.323. The original contribution proposes to include this codec as part of H.323,H.225.0, H.245 and their associated annexes. (Editor’s note: this item will be addressed at theSG16 meeting in May.) 12TD-036 requests support of the TIA IS-641 codec in a TIPHONcontext. The question was raised whether there was a need for TIPHON to include a wider rangeof codecs. It was agreed to create a new work-item (possibly DTS-03007) specifying“packetization and code-points for the TIA/EIA IS-641 Enhanced Full-Rate Speech Codec.” Thenew work item request is 12TD-128. Concerns regarding TIPHON’s ability to reference TIAinterim standards were raised; the technical officer will verify what constitutes a legal ANSI/TIAreference for ETSI.
LIAISONS
12TD-64, Proposal for a liaison statement concerning H.341 (K. Sambor, Telekom Austria),requests that a liaison be sent to SG16 with editorial corrections to ITU-T H.341. The meetingdecided that it is more appropriate for the contributor to send his comments as a contribution tothe SG16 meeting rather than for TIPHON to generate an official liaison.
12TD-101 is a liaison from ETSI WG NA8 requesting comments on “Parameters andMechanisms for Charging in IP networks” (provided as 12TD-102). This liaison will be discussedagain in the next TIPHON meeting.
FUTURE WORK
12TD-52 (B. Van Doorselaer, J. Vandenameele, Alcatel) proposes that TIPHON study differentreference architectures, call models, and protocols for scenario 3. No action was deemednecessary at this time.
12TD-48 (P. Sijben, Lucent) proposes a finer grained definition of the TIPHON architecturereference points. No action was deemed necessary at this time.
12TD-39 (J. Korpi, K. Klaghofer, E. Horvath, Siemens) proposes support for H.450 seriessupplementary services in TIPHON systems.
12TD-89 (L. Klostermann, LM Ericsson AB) notes that in some cases the approach taken in theH.450 Recommendations leads to unnecessary restrictions in service offering; it proposes aService Agent approach instead which suits the Gatekeeper routed concept adopted by TIPHON.
A small group headed by J. Korpi (Siemens) will discuss the issue to decide how to proceed. (SeeWG6 report, below.)
DELIVERABLES / STUDY TOPICS
Figure 1 presents the status of WG3 deliverables.
Study topics include:
• Identification of scenarios (0...4) calls at call-setup, implications when no identification ispossible.
• Scenario 3 issues, addressing both GRC and DRC, must demonstrate seamless interworkingwith Scenario 1 & 2.
• Analysis of interworking cases where the TIPHON acts as a public network (scenarios 1 & 2) -this relates to 12TD-27.
• Analysis of interworking of scenario 3 between foreign networks (e.g., SS7 to TIPHON toQSIG/GSM and others, and vice-versa) where the TIPHON public transit network has tomediate the call.
• Applicability of ITU-T H.341 (or other management solutions) for the management functionsTIPHON systems.
WorkingName
ETSITitle
Status Description
DTS/03001 TS 101 318 Published (18/08/1998) Using GSM speech codecs within ITU-TRecommendation H.323
DTS/03002 TS 101 319 Published (29/12/1998) Signaling for basic calls from an H.323terminal to a terminal in an SCN (Scenario 1)
DTS/03003 TS 101 320 Deliverable integrated intoDTS/03005 - will not bepublished separately.
Call control flows for basic calls from a H.323terminal to PSTN/ISDN/GSM terminalinvolving multiple domains
DTS/03004 TS 101 321 Published (31/12/1998) Protocol for Inter-domain pricing,authorization and usage exchange.
DTS/03005 TS 101 322 Stable Text achieved(TIPHON 12), scheduled to beapproved at the WG level atTIPHON 13.
Signaling for basic calls and inter domaincalls, between an H.323 Terminal and aTerminal in the SCN Phase II (Scenario 1 +Scenario 2)
DTS/03006 101 323 Approved at the WG level(Special session on Security) atthe TIPHON 12 meeting.
Interoperable Security Profiles
DTS/03007 Work-Item to be approved bythe TIPHON 12 closingplenary, WG3 approval inTIPHON 13.
Packetization and code-points for theTIA/EIA IS-641 Enhanced Full-Rate SpeechCodec
Figure 1. Status of WG3 Deliverables.
WORKING GROUP 4, NAMING, ADDRESSING
The WG4 chair is L. Spergel (Lucent). The meeting report is 12TD-15. 12TD-09 is the WG4agenda. The goals of the WG4 meeting were:• WG approval of DTS-04002, Naming and Addressing, Scenario 2• Progress on DTR-04004, E.164/IP Address Resolution
DTS-04002, NAMING AND ADDRESSING, SCENARIO 2
R. Scholl (STF) presented the DTS-04002 revised draft, Naming and Addressing, Scenario 2. Itwas noted that there was some updating of references and abbreviations, definitions werematched to E.164, and a definition was added to define E.164 number.
12TD-86 contains comments (ETO, Spanish Regulatory Body, Telenor) on DTS-04001/2 collectedfrom the ETSI NAR mailing list. These comments were accommodated; it was decided to send a
liaison back with the approved document and a marked up version of these comments reflectingWG4’s specific response to each comment. The text for the liaison is 12TD-130. DTS-04001Numbering; Scenario 1+2 (TS 101 324) version 1.2.3 was the clean draft from this meeting.
12TD-41 (S. Moore, Siemens) contains editorial and minor technical comments on DTS-04002v1.2.1. They were accommodated.
12TD-55 (S. Moore, Siemens) proposes a definition for TIPHON compliant networks: “A systemcomprising H.323 terminals Gatekeepers and Gateways using Internet Protocols that complieswith all of the mandatory requirements identified in the deliverables produced by ETSI ProjectTIPHON.” This was accepted.
The group approved DTS/TIPHON-04002 at the working group level.
DTR-04004, E.164/IP ADDRESS RESOLUTION
12TD-70 (R. Scholl, STF) proposes an outline for DTR/TIPHON-04004. This White paper makesnote of all the open issues: scope of work, types of addresses (names versus numbers), existingglobal resolution services (e.g., X.500), mapping of E.164 different approaches (e.g., IETFTENUM and RESCAP), and flat name space issues. Suggestions were made on how to proceedwith this document.
GLOBAL CODE
12TD-71 (R. Stastny, Telekom Austria) contains a report of the SG2 Q1 experts meeting in Feb.1999 in Hawaii, regarding the Request for Numbering Resources, Project 11. It was explainedthat during the meeting the previously raised questions were answered but nine new questions (in12TD-71) were raised. The Q1/SG2 discussion is now focused on the conditional reservation of thecode. The following three documents were also presented at Q1/2.
12TD-42, Technology independence and possible use of UPT code (J. Horrocks, DTI), proposesarchitectures for routing calls within a global code. Architectures are presented showing bothtechnology dependent and technology independent solutions. There is also a proposal for how toshare the UPT code.
12TD-43, Clarifications concerning the proposal for a global code (J. Horrocks, DTI), attempts toclarify some of the differences between the new service and existing services (voice and UPT).This paper explains that E.105 (public fixed telephony with geographic numbering) is notsufficient for VoIP but may, depending on requirements, be satisfactory.
12TD-44, Country identification after a global service code (J. Horrocks, DTI), discusses some ofthe advantages and disadvantages of using a national structure within the global code.
These documents led to a discussion of whether a global administration is possible. If not, thenthe approaches presented might be a good possibility.
12TD-81, Views on the way forward for a global code (DTI), describes a meeting in the UK thatfocused on the issues related to the global code. The main conclusion is that the need for a globalcode is based primarily on the need for portability between operators in different countries.Other reasons have to do with other service features, quality, and tariffs. They also investigatedusing the UPT code and concluded that there is no reason why the UPT code could not be used forthis service; it should be investigated further. It was mentioned that some modifications to theUPT Recommendations might be needed, but the details of these have not yet been determined.
E.164 TO IP RESOLUTION
12TD-67 (R. Scholl, STF) reports on the EURESCOM meeting on Project P817 on DatabaseTechnologies for Large Scale Databases in Telecommunications. 12TD-69 (T. Sater, S-O.Hvasshovd, ClustRa) reports on the ClustRa product hardware architecture which allows for avery large database (VLDB). This architecture has a very high reliability against failures;response time is 5-15 msec on four record updates; architecture is scalable. 12TD-109 provides
an overview of the ClustRa DBMS; 12TD-110 is a ClustRa presentation. ClustRa is a companybased in Norway, a spin-off of TelNor. ClustRa indicates it holds IPR on this technology.
12TD-80 (S. Sun, L. Lannom, CNRI) is an introduction to and tutorial on the Handle system, ageneral-purpose global name service.
12TD-87 (R. Scholl, STF) describes some activities of the voice messaging industry. VPIM (Voiceprofile for Internet Mail) is voice messaging for Internet transport. VPIM is documented in RFC2421 (September, 1998) with the current status as a proposed standard. VPIM takes encodedvoice or fax messages, raps them in MIME message parts and uses SMTP to send them over IPnetworks. VPIM uses “local-part@domain-part” addressing where the local-part is a telephonenumber (E.164 is only recommended currently) or mailbox number, and the domain-part is anInternet domain. The idea is to use a standardized directory service (X.500, LDAP) to performthe mapping of the telephone number into a fully qualified VPIM address. It was agreed to getmore information on this at a future meeting.
NEXT WG4 MEETING
The next TIPHON meeting conflicts with ITU-T SG2 which affects a large number of WG4participants. If the schedule of SG2 does not allow the WG4 participants to attend TIPHON inBangkok May 3-7, the next meeting of WG4 will be held in Vienna, Austria on April 30-May 1 atthe generous invitation of Telekom Austria. There will still be one session of WG4 during theBangkok meeting to report on what happened and to accommodate TIPHON participants whocannot attend in Vienna. Final decision concerning the WG4 sessions in Vienna and Bangkok willbe made within the next week or so and will be communicated to participants via the mailinglists.
WORKING GROUP 5, QUALITY OF SERVICE
The WG5 acting chair is J. Magill (Lucent UK). The meeting report is 12TD-16. 12TD-010 is theagenda. Approval of Deliverable TR 101 329 v 1.3.0 (Work Item DTR-05006) was the major itemof business.
TR 101 329, QUALITY OF SERVICE
New work item DTR/TIPHON-05007 covers further revisions to TR 101 329; the current draft isV 1.4.0.
12TD-034, Performance of TIPHON end-to-end QoS Classes (P. Coverdale, Nortel Networks),identifies an inconsistency between the parameters in Table 2 of TR 101 329 and the associateduser satisfaction values derived from the E-model. The options were reviewed and it was agreedto add a new Table to TR 101 329 showing examples of the combinations of codec and end-to-enddelay for the various QoS categories. New text is proposed in 12TD-115 (M. Perkins, AT&T, fora drafting group). After review, it was agreed to incorporate this new material into the nextworking draft of TR 101 329.
12TD-058 (E. Diedrich, H.W. Gierlich, Deutsche Telekom Berkom) is a proposed new Annex toTR 101 329 on terminal testing procedures for TIPHON systems. It was confirmed that thisAnnex could be withdrawn once the material is covered by a future TR from ETSI STQ,currently expected in 2001. It was agreed to request the editor to incorporate this annex in thenext working draft of TR 101 329.
With the above changes, the updated draft of TR 101 329 will be reviewed at the next meeting.Contributions proposing further changes are expected.
DTR/TIPHON-5002, MINIMUM LEVELS OF QOS FOR THE ESTABLISHMENT OF TIPHON-COMPLIANTSYSTEMS
12TD-061 (G. Koerbler, STF) provides information on the IETF work on DiffServ and how thisrelates to the objectives of TIPHON QoS. The resulting discussion extended to address widerissues of how the defined QoS categories can be negotiated and signaled. A drafting group wasestablished to list the issues for study. The result of this work is 12TD-113, which proposes an
initial QoS framework. The purpose of this framework is to facilitate development of TIPHON-compliant systems which will enable QoS requirements to be determined, guaranteed, andmonitored between two end-points for each call. The following components of this framework havebeen identified, but this may not be an exhaustive list. 12TD-113 contains a supporting diagramand other information.
1. Each end-point shall be able to indicate its QoS capabilities and characteristics (e.g., asdefined by the terminal type) to the Gatekeeper. This is required because the terminalconsumes a portion of end-to-end resources, which vary depending upon its type.
2. Each end-point shall be able to indicate its bi-directional QoS preferences (e.g., default QoSClass to be used for all calls, or per-call QoS) for the call to the Gatekeeper at which it isregistered. The default QoS Class can be indicated upon registration, and optionallyoverridden on a per-call basis.
3. The Gatekeeper(s) shall have the mechanisms to determine if the preferences of the two end-points are achievable.
4. The Gatekeeper(s) shall establish or reject connectivity between end-points, and across themanaged packet network, that meets the mutual requirements previously indicated by end-users, taking all components into account.
5. Network traffic engineering or other specific packet QoS measures/mechanisms shall beutilized to “guarantee” the required QoS in terms of packet loss, delay control, etc. Delayengineering guidelines or mechanisms such as DiffServ could be examples of possible solutions.
6. A monitoring function is required to indicate whether or not the qualities of servicecommitments of the system were met for the call.
Contributions are invited on the development of the framework in general, and on each componentin detail.
It is anticipated that this study will ultimately result in a detailed technical framework thatshould be integrated into the TIPHON WG2 architecture. In the case where specific protocolsolutions are required, WG3 should identify and develop an appropriate solution. WG5 willdevelop an issues list and coordinate appropriate work items as required.
12TD-045 (J. Horrocks, DTI) discusses the future work on VoIP transmission quality, of WG5,the potential use of DiffServ, etc. It was agreed that the issues raised in this contribution shouldbe addressed further by WG5; contributions are invited to address questions such as:
• What DiffServ behaviors should be specified for VoIP? (we need to understand their effect onquality and this may require some experimental or simulation work)
• How should any behavior limits, e.g., queue delay, be set?• Should the behaviors be related to the codec type? (There will certainly be some interaction,
but with many different codecs this could be impracticable and hopefully can be avoided.)• Should the behaviors and the corresponding code points for the headers be standardized for
common use between interconnected networks? (It would make sense.)• Should adherence to a standard set of code points and behaviors become part of standard
interconnection agreements?• What should be the failure mode when the cell loss exceeds a certain level (does the call
continue or is it dropped by the network or terminal)?• What other protocols should be given equal attention?
Contributions are also invited on practical experiences on QoS issues.
RELATED WORK
It was noted that the work TIA TR-41.3, TIA TR-41.2.2, and USA T1A1.5 committees may be ofinterest to WG5:
12TD-103 provides a copy of TIA TR-41.3’s PN-4462, Performance and InteroperabilityRequirements for VoIP Telephone Terminals. 12TD-104 provides a copy of Section 5 (TechnicalRequirements) from TIA TR-41.3 PN-4352, Transmission Requirements for Voice over IP andVoice over PCM Digital Wireline Telephones. PN-4352 is based on TIA-579-A, TransmissionRequirements for Digital Wireline Telephones.
12TD-082 provides a diagrammatic view of the standards work relating to the E-model in bothETSI and the ITU-T; it was provided for information.
ETSI STQ is aiming to hold a workshop on VoIP Quality on June 8-9, 1999, in Sophia Antipolis.Further information will be made available on the e-mail reflector.
WORKING GROUP 6, VERIFICATION
The WG6 chair is M. Blaschitz (Infonova). The meeting report is 12TD-17. 12TD-11 is the WG6agenda. The following were the objectives for this meeting were:
• Approval of DTS-06004, Test Specifications (TS 101 335, V1.1.1)• Stable text for DTR-06002, Verification, Demonstration and Interoperability Activities (TR
101 335)• Stable text for DTS-06005, TIPHON Test Specification (TS 101 335, V2.1.1)• Stable PICS specification for DTR-06007, DTR-06008, and DTR-06009, PICS Pro Forma for
H.450.1, .2 and .3 Supplementary Services, respectively (TR 101 340, 341, and 342respectively)
• Planning of the next Interop event• Implementers Net
12TD-74 is the Revised Work Program of WG6. It was reviewed and approved.
PACKET CABLE PROJECT
12TD-125 (M. Stachelek, Cable Labs) presents an overview of the Packet Cable project. ThePacket Cable Project is a cable industry initiative being managed by CableLabs. Its goal is todevelop a set of specifications that will allow vendors to develop interoperable products aimed atdelivering real-time, packet-based multimedia services over cable systems, including interactivegaming and general voice and video applications. It was noted that the approach taken byCableLabs was very similar to the one taken by WG6, also with respect to interoperability eventsand demonstration. Unfortunately the technology selected by CableLabs is not compatible withTIPHON (MGCP is supported rather than H.323). It was also noted that end-to-endcompatibility between the CableLabs solution must be achieved. It was decided to exchangeinformation and to consider cross-participation at the respective Interop-events in order to ensureinteroperability.
VIRTUAL INTEROP MEETING PLACE
12TD-94, Implementers Net 1, Creating the Virtual Interop Meeting Place (G. Koerbler, R.Scholl, S. Cadzow, STF114), proposes, with the cooperation of IMTC, to create a website tofunction as a virtual interop meeting place for long distance tests.
From the presented technical options in 12TD-85, Implementers Net 2, Technical Solutions (G.Koerbler, R. Scholl, S. Cadzow, STF114), WG6 selected the following as the basis for theimplementers net:
• A centralized hub solution as defined in 12TD-85,• A WWW server as defined in 12TD-94 serving as an administration center for the virtual
interops.
The centralized hub could be configured to accept calls only or work using a callbackfunctionality. Implementers Net participants should be able to use the public internet for theirtests as well as the centralized hub.
A detailed description of the implementers net based on 12TD-95, 12TD-84 and complemented bythis report will be put in the deliverable DTR-06002 and should be discussed within the ETSIsecretariat and ETSI board.
12TD-127, TTT-Network Infrastructure (H. Wermescher, Infonova), describes a networkinfrastructure for “Service Interoperability Trials” between Telekom Austria and Omnitel. Itinvites Service Providers to the TTT-Net trials. Other service providers are invited to join. Onceapproved by TIPIA, this infrastructure will form the basis for the TIPIA large scale user trials.It was presented for information.
PROPOSED EXTENSIONS OF DTR-06005
12TD-131 (M. Bien, Bosch), gives guidance on how to implement the proposed extensions (from11TD-031) of DTR-06005, TIPHON test specification, for the consideration of the SCN side withinDTR-06005. The idea is to have some minor SCN aspects covered in the first chapters, and themain definitions in an annex. The STF will create a draft.
PLANNING OF INTEROPERABILITY EVENTS
The next interop event will take place April 19-23 in the Boston area (USA). WG6 requests anSTF member to be responsible for the detailed planning with IMTC. Details like invitation, test-plans, and audio-conferences for preparation will be announced on the WG6 and implementersmailing lists.
The following interop event is scheduled for June 21-26 at ETSI headquarters. If more than 150people register, a fallback solution should be considered. In this case, TIPHON members will beinvited to volunteer.
TEST SPECIFICATIONS FOR TIPHON SYSTEMS DTS/TIPHON-06005
DTS-06005 was reviewed and frozen. The following responsibilities for test cases was assigned:
• J. P. Albinet (Alcatel) will provide a draft for clause 14.• E. Mannie (ULB and Telscom) will provide a draft contribution to clause 15.• K. Sambor (TA) will provide a draft contribution to clause 16 “Scenarios for security profiles.”• J. Holm (Ericsson) should provide a test description for “Audio before connect.”
DTR-06002 was reviewed. It was agreed to keep the description of TIPHON-Net but to state thatthe focus of WG6 lies in the Implementers Net and in the interop events. A stable draft version ofthe document was approved. After the ETSI board meeting, a clean version of the deliverablewill be distributed on the WG6 reflector. To accelerate the procedure, it was then agreed toapprove the document on the WG-level as well as on the project level.
PICS PRO FORMA FOR H.450 SUPPLEMENTARY SERVICES: DTS-06007, DTS-06008, DTS-06009
PICS pro forma 12TD-121 (H.450.1, Generic functional protocol), 12TD-122 (H.450.2, Calltransfer supplementary services), and 12TD-123 (H.450.3 Call diversion supplementaryservices) for H.450 Supplementary services, DTS-06007 DTS-06008 DTS-06009 respectively,were reviewed. Stable draft versions of the documents were approved. A two week period forcomments was agreed before the drafts will be sent to SG16 Q13. A liaison to SG16 Q13 wasprepared informing them about the work on DTS-06007, DTS-06008, and DTS-06009.
WORKING GROUP 7, WIRELESS
This was the first meeting of WG7, Wireless. The WG7 chair is R. Zwart (AT&T). The meetingreport is 12TD-134. The objectives of this meeting were to detail and approve the Table ofContents and Scope of the two deliverables DTR-07001, Analysis of Existing RoamingTechniques Applicable to TIPHON Mobility Services, and DTR-07002, Investigation of Synergiesand Common Requirements between TIPHON Networks and Wireless Systems as they arecurrently being developed by other bodies. An additional goal was to start the required liaisonwork with other bodies in and outside of ETSI.
12TD-051, Discussion for Number Portability (S. Cadzow, STF114), is a starting point for thediscussion on the impact of number portability on mobility. It describes the TETRA and GSMnumber portability structures and suggests that TIPHON networks with address portabilitymay require that TIPHON is considered a special class of mobile system. It was understood theWG7 will work with WG4 to ensure a common view of this impact on both groups.
12TD-088, Mobility and Roaming Technologies (L. Klostermann, S. Sultana, L. Madour,Ericsson), is a tutorial document offering an overview of mobility and roaming in GSM, ANSI-41,UPT, CDPD, GPRS (General Packet Radio Service used within GSM), GPRS-136, UMTS,IMT2000, MobileIPv4, MobileIPv6 (in progress), Network Access Identifier (used during PPPauthentication) and IETF Session Initiation Protocol (SIP). This paper provides valuableadditional text for DTR-07001. A question was raised whether the definitions provided in thedocument were taken from an existing TIPHON common definition document.
12TD-084, Voice Over Wireless IP in a UMTS/TIPHON Network (E. Martinez, Motorola),presents a potential network model in a shared UMTS TIPHON environment. There werequestions for clarification suggesting that the intended target deliverable (DTR-07001 or DTR-07002) for this contribution was not quite clear. After some discussion it was agreed that themajority of the text was relevant to DTR-07002 and that the mobility related pieces of thiscontribution would be considered for DTR-07001.
After the presentation of contributions, a discussion was held on DTR-07001. The discussion firstfocused on 12TD-84. It was pointed out that this proposed architecture is not addressing severalpotentially important networks. It was also expressed that the proposed model is suggesting aconclusion for the work item, while the required analysis has not yet taken place.
In the drafting session, an attempt was made to integrate 12TD-84 into DTR-07001. Extensivediscussion took place. It was agreed to include a diagram reflecting the view of some of theparticipants in DTR-07001 as a placeholder. It was also agreed that the editor would workjointly with the author of 12TD-88 to also include 12TD-88 in the new DTR-07001.
After some modifications, there was agreement in the drafting session on the table of contents ofDTR-07001. The work on this document will be progressed further over the email exploder. Thenew version of DTR-07001 will available on the ETSI server within a week. Comments arerequested to the text of sections 1 through 5, however, in view of the timelines associated with theDTR-07001 deliverable, it is noted that these comments have to be in the form of clearly markedreplacement text for these sections. Contributions are requested on sections 6 and 7 on theanalysis of and subsequent recommendations on roaming techniques in the TIPHON context.
DTR-07002, WIRELESS
12TD-038, Scope and Outline for DTR-07002 (R. Zwart, AT&T), was used as a basis fordiscussion of the scope and table of contents of DTR-07002.
There was little comment to the proposed outline of the deliverable. In the context of thisdiscussion, it was proposed to identify an additional work item for WG7 that will enable WG7,based on the results of DTR-07002 and DTR-07001, to send more detailed questions orrequirements to other working groups. This additional work item is expected to also help indelivering the existing documents on time. There was no major objection in the working group toinstalling this new work item, however, the chairman suggested to wait with the actual definitionof this work item until the existing work items are closer to completion.
The outline of DTR-07002 was further discussed. The result of this discussion is available on theETSI server as 12TD-38-R1.doc. For one of the sections of DTR-07002, i.e., section 5, “Overviewand description of identified wireless access networks,” several participants acceptedresponsibility for contributions on the different subsections, but further contributions are stillrequested.
12TD-031, is the meeting report of ITU-R WP8A’s new Question, “Internet over Mobile systems.”
12TD-083, Report from UMTS Kick-off Meeting, 25/26 Feb. 1999, was not yet available, but waspresented verbally. It was reported that EP UMTS had, in their recent kick-off meeting, decidedto send a liaison to TIPHON WG7. The liaison welcomed input from WG7. One of the remarksfrom the meeting noted that there is an unclear status of EP UMTS, in view of the work on UMTSbeing done in 3GPP.
12TD-060, Liaison Statement from EP DECT to EP TIPHON : TIPHON Services over DECT (J.Navarro, EP DECT), was received and presented to WG7, however in absence of any DECTrepresentative some questions could not be answered. It was decided that WG7 will send aresponse to the liaison to welcome contributions from EP DECT and to explain the goals of WG7.
12TD-037 (R. Zwart, AT&T, T. Hatala, Motorola) proposes a set of liaisons to be established byWG7.
A discussion of the identified candidate parties for liaison was held. The working group vice chairpresented the text to be used as a basis for the liaison statements. This text was accepted withsome minor changes. Liaisons will be sent out to the following groups: ETSI Project BRAN, ETSIProject SMG 12, ETSI Project NA6, ETSI Project SES, ECMA TC32, ETSI Partner Project3GPP SA WG1, ITU-R WP8A, ITU-T WP3/11, T1P1, TIA TR-45.6, IMTC, UWCC, 3GPP2.12TD-135 details the text to be used for these liaison statements. Responses to the liaisonstatements already received from EP DECT and EP UMTS will be drafted and discussed overthe email exploder in the coming two weeks.
SECURITY
The special rapporteur for security is S. Thomas (TransNexus). The meeting report is 12TD-106.(See also WG1, Lawful Interception, above.)
APPROVAL OF SECURITY PROFILES DOCUMENT
One additional change was proposed for DTS-03006, Interoperable Security Profiles: It wassuggested that actual definitions of security terms be removed from the document and that theETSI Technical Report Glossary of Security Terms be added as a normative reference. Thissuggestion was agreed; the document was updated accordingly (subject to a check on the exactreference), and the attendees unanimously approved the resulting version of DTS-03006.TIPHON was requested to approve DTS-03006 at the project level during the TIPHON 13meeting.
12TD-024 (S. Cadzow, Cadzow Communications) presents additional information on lawfulinterception requirements.
12TD-054, The H.323 Firewall Control Interface, HFCI (H. Hurry, Siemens, A. Molitor, StorageTechnology, and T. Ngo, Sun), introduces work being undertaken within the IETF (see IETFInternet draft draft-rfced-inf-mercer-00.txt). It was presented for information.
12TD-095 (B. Adams, DTAG) notes that ETSI TC SEC is the focal point for LI (LawfulInterception) within ETSI. However TIPHON is a global initiative of ETSI and shouldadditionally meet the regulatory requirements of other non-European countries participating inthe TIPHON project. With this understood the following documents were presented:
• 12TD-091, ETR 331, Security Techniques Advisory Group (STAG) Definition of userRequirements for Lawful Interception of Telecommunications; Requirements of the LawEnforcement Agencies
• 12TD-092, ES 201 158 v1.1.2 (May, 1998), Telecommunications Security; Lawful Interception(LI); Requirements for Network Functions
• 12TD-093, DES/SEC-003003 v1.7.2 (Feb. 15, 1999), Telecommunications Security; HandoverInterface for the Lawful Interception of Telecommunications Traffic, Edition 1
12TD-099 (S. Cadzow, STF) is a proposal for work to be undertaken by the STF to coordinatelawful interception activities relating to TIPHON within ETSI. 12TD-108 is the new work item.
TC SEC provided an update of its plans to assist TIPHON with a security threat analysis ofTIPHON systems. TC SEC expects to begin their effort March 8-12; the presentation will beprovided as a temporary document.
BOF ON BACK END SERVICES
The BOF session was chaired by H. Schink (Siemens). The agenda is 12TD-32.
K. Sambor (Telekom Austria) gave some background from the TIPHON11 meeting concerningthe topic of Back End Services (BES); the presentation is 12TD-65. The first BOF on this subjectwas held at TIPHON 11. The following were discussed:
• TS 101 321 Inter-domain pricing, authorization and usage exchange.• H.225 Annex G Inter-domain communications• Back-End Services Transport (BEST) protocol• IETF IPTEL gateway location protocol
A new work item was proposed for WG2, but no decision has yet been made. 12TD-65 alsoproposes a phased approach.
12TD-49, BES requirements for global services (H. Wermescher, Infonova and K. Sambor,Telekom Austria), and 12TD-50, Global value added services within the super domain BES cloud(H. Wermescher, Infonova, L. Strahs, AT&T, and K. Sambor, Telekom Austria), both propose toadd a Super Domain BES cloud to the architectural model, to address the global servicesnecessary for deployment of IP telephony worldwide.
12TD-29, Clearing house model (L. Strahs, AT&T), summarizes the clearinghouse modelsrequired for the TIPHON architectural model and for validating the TIPHON specifications. Thispaper will also be submitted to TIPIA, March 28, 1999.
After discussion, the following were agreed:• The presented contributions should be further considered; BES is in principle a future work
area for TIPHON.• The phased approach presented in 12TD-65 was approved in principle. The phasing and
harmonization with other involved bodies like SG16 and TIPIA were supported.• As a first step, WG1 was asked to consider detailed requirements for back end services and to
provide a prioritization.• New work items for WG1 and for WG2 (e.g., on a service creation architecture) should be
considered depending on the outcome of WG1 discussions.• TIPHON should not work on all possible services but concentrate on some few key services
which are considered highest priority by WG1 and TIPIA.
STF 114 MEETING
R. Scholl (ETSI) is the TIPHON STF representative. The STF 114 meeting report is 12TD-112.
STF 114 ACTION ITEMS FROM TIPHON #12
1. Consistency Check and Quality Assessment of TIPHON documents Phase II. After almost twoyears of activity, the TIPHON community and the number of deliverables keeps growing. Toassess the progress that has been achieved, to assure the consistency of the TIPHONdeliverables, and to make sure that TIPHON is specifying adequately what is needed for theimplementation of interconnected networks, the STF will provide a “living document” overview ofthe work and main problem areas (as a Technical Document, and on the Web). This item wasrequested by PMC and members of TIPHON community; it will start immediately; the ongoingwork will be assigned to R. Scholl and S. Cadzow.
2. Draft IETF/ETSI Cooperation Agreement. Currently there are discrepancies between thedrafts as envisioned by TIPHON and the ETSI secretariat. Discussion with the TIPHON chair
and ETSI will be continued by email. This item was requested by the TIPHON Chair; itsdeadline is the end of March; it has been assigned to R. Scholl.
3. Coordinate PICS for TIPHON Protocols, with specific emphasis on H.450.x series. Thisadministrative item was requested by the WG6 chair; R. Scholl will complete it by TIPHON 13.
4. Prepare second joint IMTC/ETSI-TIPHON Interop event on April 19-23. This event will be inthe Boston area, organized by PictureTel.
5. Implement “Virtual Interop Meeting Place.” WG6 requested the creation of a Web-site withforms where test engineers enter information necessary to organize, run, and evaluate both face-to-face interops and remote tests. It will be done in collaboration with IMTC, by March 31, 1999;it was assigned to G. Koerbler (ETSI).
6. Installation and running of an ISDN-router on ETSI premises for remote testing (tentative).Pending on the result of the ETSI board meeting (March 24), a centralized ISDN router might beinstalled on ETSI premises to facilitate remote testing. This facility will be run by the STF.
7. Plan the third joint IMTC/ETSI TIPHON Interop event for June 21-25 in Sophia Antipolis,France (tentative). R. Scholl will take this proposal to the IMTC.
8. Overview of TETRA’s work on mobility for WG7. Requested by WG7, it was assigned to S.Cadzow.
9. Liaison between TIPHON, ETSI TC SEC, and others on (1) lawful interception; (2) threatanalysis of TIPHON architecture. This item was assigned to S. Cadzow.
10. Produce draft for DTR/TIPHON-04004 on Numbering Issues (“E.164 / IP Resolution”). Thiswork will be accomplished by e-mail for TIPHON 13.
WORK PLAN FOR STF 114
Current funding for STF 114 is for the entire year of 1999, and includes 16.5 working months.The budget situation will be discussed at the next ETSI Board meeting on March 24, 1999.
G. Koerbler will leave STF 114 at the end of March 1999; he may continue maintaining the“Virtual Interop Meeting Place” (effort: a couple of days/months); various financing schemes arebeing discussed.
TIPHON MEETING #12 ROSTER, MARCH 1 - 5, 1999, PHILADELPHIA, PA, USA
REPORT OF ETSI ATA (ANALOG TERMINALS AND ACCESS)MEETING #6, MARCH 8 - 12, 1999, SOPHIA ANTIPOLIS, FRANCE
This was the first ATA meeting held at Sophia Antipolis since installation of full network accessfacilities at each seat in all conference rooms. Access to the ETSI network is intended to makemeetings paperless. Thus, copies were not provided of any documents put on the server beforethe meeting. Some 20% of the delegates had the necessary network cards in their portables.Forty-two members attended (TD-07). Two representatives from TC TM6 (one of whom was J.Besseyre) attended part time.
After agreement of the agenda (TD-01), the Chair (N. Encarnação, OFCOM, Switzerland)proposed a number of amendments to the report of the last meeting (TD-02). They were acceptedwith minor changes. One action point carried out involved setting up an e-mail exploder todiscuss Asymmetric Digital Subscriber Loop (Line) (ADSL) splitter requirements. J. Long (DTI)protested that discussions could be inhibited by the fact that non-ETSI members had access tothe exploder, and he asked that their access be prevented.
The Chair announced that, as ATA was now over two years old, all officials needed to be elected.All officials were formally re-elected except that G. Engstrom (Ericsson) replaced U. Jansson(Ericsson) as Vice Chair and Rapporteur for ATAe (Enhanced Signaling Systems). J. Long (DTI)strongly objected to the lack of notice of the election. After the meeting, M. Harris (Oftel) saidthat he would be unable to continue as technical secretary and the Chair asked for volunteers toreplace him.
TD-03 notes that the Board had approved the creation of TC Telecommunications EquipmentSafety (TES) and the related Terms of Reference. Health and safety aspects of the Radio andTelecommunications Terminal Equipment (R&TTE) Directive will be included within the purviewof this committee.
The Chair reported that the Board had approved in principle the Terms of Reference for aSpecialist Task Force (STF) for the production of harmonized standards under the R&TTEDirective, and the ETSI Operational Coordination Group (OCG) had approved the draft workprogram for the R&TTE Directive. The steering group for the STF planned to meet on Friday,March 12. The Chair indicated that he would attend on behalf of ATA.
Knowing that the Chair had suppressed some details of the invitation, J. Long (DTI) askedwhether other members would be able to take part. He received no reply. It was remarked thatit would be a waste of time for an STF to write new standards without consulting ATA during theprocess as otherwise the documents may not be approved at voting.
The Chair drew delegates’ attention to the fact that prior to termination, any technical bodyshould prepare recommendations concerning the maintenance of its ETSI deliverables. He alsostated that he currently understood that TCAM, the advisory committee set up by the R&TTEDirective, would start work on April 20, 1999, and that the Directive itself would become effectivefrom April 1, 2000.
The Chair stated that the activity of ATAc (Conventional technologies) should be centered on TR101 389-1-5, a set of technical reports giving guidance to the implications of the R&TTE Directivefor terminal standards. He did not want the approval of this set of Technical Reports (TRs) to bedelayed as it would prevent early working on Harmonized Standards for the new R&TTE. ATAewill work on TR 101 292.
The OCG had endorsed the creation of an Ad-Hoc working group (Subscriber’s Lines, SL) tohandle the inclusion of all the different Digital Subscriber Lines (xDSL) requirements intoHarmonized Standards. It is under the convenorship of ATA member F. Howett (Nortel) but willalso involve TM6 / ERM-EMC / JTC-Safety. The document, currently TR 102 139, is likely tobecome an ETSI Guide (EG). Discussion of the document will take place largely through an e-mail exploder.
A liaison from STQ, TD-12, includes a chart of the parameters of six acoustic safety specificationincluding P.360 (Efficiency of devices for preventing the occurrence of excessive acoustic pressureby telephone receivers), and Annex A of P.360 (Basis for the determination of the limits for theacoustic pressure). P.360 (1998) is a revision of P.36 using the artificial ears specified in P.57. Itwas noted that the document contained no reference to the information in ES 200 677 (PSTN,Requirements for handset telephony) and I-ETS 300 480 (PSTN, Testing specification for analoghandset telephony). TD-31, a reply liaison noting the missing standards, was approved at thefinal plenary.
A liaison received from the Digital Terminal and Access project (DTA) on the R&TTE directiveand scopes of the various projects is to be dealt with in the joint plenary with DTA. The liaisonfrom TM (TD-10) indicates the need for an Amendment to CTR21/TBR21 (they currentlypreclude pan-European approval of G.lite technology) and a new HS addressing high frequencycross-talk caused by xDSL equipment. This will be dealt with by the new group SL (SubscriberLines), and by the ATAc meeting.
TD-11, a liaison from the ETSI User Group, describes the open areas being set up on the ETSIserver to inform and solicit comment on the work of the group.
TD-15 is a liaison from the chair to ATAAB suggesting disposal of some of the general commentsthat were not appropriate for the resolution meeting. For consistency with CTR21, TD-15suggests that EN 301 437 (PSTN attachment requirements for voice TE in which networkaddressing, if provided, is by DTMF), when published, should be applied under the conditions ofCTR 21 (international arrangements promoted by ACTE and TRAC). The chair’s proposedliaison to ADLNB on testing in EN 301 437 (TD-16) was rejected as unnecessary.
WORK PROGRAM
The ATA work program is in TD-05; the ATA membership list is in TD-06.
The Chair proposed a new work item to replace ETR 201, a Conference of European PTTs(CEPT) document on register recall, with an ETSI standard.
The Chair intended that EN 301 437 should be approved at the opening plenary but there was atechnical objection from C. Harley (BT) in TD-24 to the decision at the resolution meeting(recorded in TD-13) that affected clause 4.7.3.2. This decision had the effect of removing the testthat ensured that the output of a speech terminal was limited correctly. His objection receivedsupport from Telefonica, Deutsche Telekom, the Norwegian PT, Telekom Austria and theAustrian regulator. There was not the necessary 71% support to approve the document to go forvote; the Chair said that he would try again at the final plenary. (See ATAc, below.)
It was pointed out at the Cape Town meeting (Dec. 1998) that many recommendations in ETR075 (Study and investigation into the feasibility of further harmonization of the requirements andtests of ETS 300 001) are out of date. R. Trevland (NPT) proposed in TD-18 that it should bewithdrawn. This was opposed by two of the authors present (J. Montenot, France Telecom, andW. Mellors, WM Services). They argued that it was a useful historical record and all that wasnecessary was to decide to ignore its recommendations to revise ETS 300 001 (General technicalrequirements for equipment connected to an analog subscriber interface in the PSTN, revised10/1998) as they were now superseded by the latest revision. J. Long (DTI) suggested that ETSIinvestigate the possibility of declaring the status of the document as obsolete. It was decided tosend a liaison to OCG (TD-30) asking that such a classification be created within ETSI.
C. Harley (BT) reported that there will be a need to produce a new version of EG 201 121 (Aguide to the application of TBR 21) as a result of EN 301 437 and other activities in ATAAB.New advisory notes, which should be produced within the next two months, deal with the issue ofterminals not intended to operate at currents less than 18 mA and with connection methods formulti-line equipment.
ATAAB will also need to consider a revision of AN03 which says that networks are notnecessarily compatible with TBR 21; AN03 is causing a problem for manufacturers. It was notedthat all countries have been asked to reconsider the need for their existing advisory notes andwhether those produced for TBR 21 need to be applied to TBR 37.
JOINT SESSION WITH DTA
A joint session was held with DTA, chaired by B. Martensen (Ericsson) and D. Maxey (BT). DTAhad strong opinions on the steering group meeting for the STF which was to be held on the Fridayand also on the manner in which the ATA guides on the R&TTE directive were being dealt with.They also had views on xDSL which they wished to put to ATA.
R. Trevland (Norwegian PT) introduced TD-17 (TR 101 389-2, R&TTED; the impact of theR&TTED essential requirements on present and future standards in the TE area; Part 2:Prevention of harm to the network or its functioning). He suggested that there might be problemsarising from different operators using the same cable pair or using different pairs in the samecable. Dealing with the aspects of harm that might arise from this would need experts from morethan ATA. It was pointed out that OCG is setting up a group on spectrum management in newtechnologies.
P. O’Keefe (Telecom Eireann) spoke on part 3 (TR 101 389-3) which dealt with interfaces andtheir publication. The document was not available as a TD as it had not changed since the CapeTown meeting. He indicated that the parts dealing with who should publish information andwhat they should publish had been agreed in ad hoc C of the Commission Steering Group.
P. Döfnäs (Ericsson) introduced part 4 on service aspects. He noted that speech quality isnormally not the deciding factor for a user when choosing a speech telephony service and thatthere may not be a pressing need to apply regulatory requirements for speech quality. W.Mellors (WM Services) on behalf of the users insisted that users will continue to expect that thespeech quality level currently offered will continue to be available irrespective of any regulatorychanges.
M. Harris (Oftel) spoke on part 5 of the document dealing with new technologies. This had notchanged since December and he was beginning to wonder whether it was needed at all. He wasreluctant to pursue it as an ATA work item as much of its content seemed to be within the termsof reference of DTA.
D. Maxey (BT) thanked the rapporteurs for their presentations and invited DTA members tosend any comments directly to the rapporteurs. He reported the discussion in DTA on the ETSIsteering group being set up to control the work of the STF on harmonized standards. Heprovided a copy of the invitation to attend the kick-off meeting of the Group (DTA(99)14).Because the work was so important, DTA had felt that they needed strong representation and soidentified four members to attend on their behalf in spite of the fact that the invitation suggestedonly two.
DTA thought that the briefing should deal with new technologies that have no standards. TheSTF members should understand terminals, understand the technology, and be capable ofworking together. They asked that they should be allowed to approve the letter asking forexperts.
DTA was insistent that the output of the STF should be approved by the technical body in thearea concerned. Whether the final Harmonized Standard(s) should be a single document orseparate small ones is probably up to the STF, but it is important not to have one large,incomprehensible document.
DTA intended that the liaison document should be written so that the DTA delegation couldpresent it; it would have more impact if it was a joint document on behalf of ATA and DTAtogether. A. Mullan (Motorola) was worried about the main guidance document, saying that itwould apply to the 80% of the market that was not radio-based; he was not happy if it was bothwritten and approved by the EMC and Radio Matters (ERM) committee. He thought that ATAand DTA should be involved in the approval process.
J. Long (DTI) advised that it was too late as the document would be approved in a few days. IfATA/DTA were now to take part, it might be seen as endorsement of the document. I. Marshall(Nortel) reported that all DTA comments had been discussed at the last ERM TG6 meeting. R.Ceruti (CSELT) was worried about the future of harmonized standards and invited comments onthe ETSI exploder.
A second joint session, with members of TM present, discussed TR 102 139, a draft of a report onxDSL compatibility. The document is mainly concerned with compatibility between analogTerminal Equipment (TE) and xDSL apparatus operating on the same line, but also considerscompatibility with xDSL systems operating in the same cable pair.
It was noted that TM6 had proposed extending the out-of-band noise limits on TE from 200 kHzto 30 MHz. There is significant concern from certain manufacturers that the cost of meetingthese increased limits may be disproportionate. The rapporteur stated that he had measuredsome (UK) TE: while some met the limits, others failed during DTMF signaling, and a UK CT1(cordless) telephone had significant signals at 1.6 MHz and harmonics. He invited otherdelegates to submit additional test results.
P. Döfnäs (Ericsson) pointed out a current EMC requirement for TE to withstand a 3Vlongitudinal voltage over a wide frequency range. Assuming a balance to earth of 40 dB, thiswould give a resulting signal level of approximately -40 dBV, significantly above the suggestedout of band noise limits. It was also noted that analog TE might well have an out of bandimpedance incompatible with the operation of DSL-lite.
The rapporteur asked members to provide information on issues of remote line testing anddemodulation of SDL signals. He agreed to give delegates time to submit further comments andto update the document in the light of both those comments and those received at the meeting. Anew version of the document was targeted for 6-8 weeks.
It was noted that two UK documents dealing with xDSL are available on the web athttp://www.oftel.gov.uk/NICC/Public/DOCLIST.TXT.
J. Salemans (KPN) presented TD-29 calling for the spectral management of access networks. P.Döfnäs (Ericsson) stressed that ATA should only deal with the technical issues and they shouldnot attempt to impose regulation through standardization. D. Maxey (BT) agreed and urgeddelegates to identify those technical issues which could be brought to the attention of theregulators to ensure that they had the best technical advice on which to base their decisions. It isimportant to note that many member states were already looking at local loop unbundling butthat different solutions may be applicable to different countries.
In further discussion on the R&TTE Directive, the Chair reported that the work of ERM TG6would be presented to TCAM (European Commission Telecommunication Conformity Assessmentand Market surveillance committee) at their first meeting on April 20, 1999. Other EuropeanCommission ad hoc Groups deal with Market Surveillance (A), Equipment Classes (B), Interfacepublication (C) and Essential requirements (D). He said that the work of the ad hoc groups wasnot yet complete and that their future was uncertain.
ETSI was expected to attend TCAM as an observer. It was not clear what would happen toother advisory committees such as TRAC and the TAABs. In further discussion on the ATAreports TR 101 389-1 to 5, J. Long (DTI) stated that his part 1 did not yet exist. He consideredthat the reports were an educational exercise setting out facts and background to the future. J.Montenot (France Telecom) asked whether DTA supported the work or would it write similardocuments of its own? DTA declined to state a formal position.
France Telecom asked what would be the impact of the report and what would be its purpose ifATA had no control of the work arising from it. D. Maxey queried whether the ATA reportswould be updated when the Commission ad hoc groups produced their reports. N. Encarnaçãoreplied that the output of the ad hoc groups might not be published as their work was an input tothe Commission which could do what it liked with it.
France Telecom (TD-34) also wished ATA to input to the Guide for the preparation of candidateHarmonized Standards being produced by TG6 (EG 201 399). They were told that it was nowtoo late and were advised to submit their comments either directly to TG6 or during the membersapproval process.
ATAC (CONVENTIONAL) SESSION
TD-20 (France Telecom) provides comments on the draft of TR 101 188 (Harmonized analogpresented network termination point [NTP]), specifically about the unresolved comments arisingat the voting stage which specified a 2-wire analog NTP. TD-23 (CSELT) provides additionalcomments. Some of the comments were accepted and others amended or rejected. The resultswere incorporated into a version 0.0.4 which was accepted at the final plenary.
The discussion continued on EN 301 437, and TD-24 (BT, see Work Program, above) whichcontains comments on clause 4.7.3.2 (instantaneous voltage). There was much haggling andATAc finally proposed the inclusion of a note recommending that speech equipment pass a testwith higher level stimulation into subclause 4.7.3.2, with the recommendation that ATA holdanother vote at the plenary on the document (see below).
C. Harley (BT), the rapporteur, introduced the Dual Tone Multi Frequency (DTMF) standard ES201 235 parts 1,2 and 3. He apologized that part 4 was not yet available due to pressures on histime. These standards replace CEPT Recommendations T/CS 46-02 and T/ST146-04 (now ETR206 and ETR 207) for DTMF senders and receivers. TD-21 (R. Ceruti, CSELT) provides anumber of comments.
It was agreed to remove all reference to CEPT standards since the original intent of the ETSIdocuments was to replace CEPT standards that were no longer readily accessible. It wasrecognized that the majority of DTMF receivers are now fully integrated with exchangeequipment and that certain requirements previously contained in the CEPT recommendationswere outside the scope of any standard for DTMF receivers as they related to the wholeequipment.
C. Harley pointed to TD-35, a copy of a CEPT document that describes the production of a testtape to determine speech immunity. R. Ceruti stated that the documents only indicate how togenerate a speech tape and questioned whether a standard tape was available. He wasconcerned that tapes generated by different organizations would result in different test resultsand proposed that ATA and ETSI consider the need of generating a definitive sample for suchtesting.
It was questioned whether STQ should be involved, however it was clarified that STQ isconcerned with speech quality and that SPS is responsible for signaling (although they have nocurrent expertise in DTMF signaling). C. Harley said that he would work further on thedocuments and put them on the server under “DTMF.”
ATAE (ENHANCED) SESSION
ATAe undertook further work on TR 101 292, the proposals for enhancements to Server Displayand Script Services (SDSS) standards working from TD-22, TD-26, TD-33, and TD-37. Theseproposed enhancements cover message ID, Last caller identification and short message servicesdealing with general information, advertisement, network provider ID, Carrier identity andaddress. The report was not completed but ATAe requested authority from ATA to approve thisreport at a meeting in May. Following the approval of TR 101 292, ATAe intends to raise newwork items to update ETS 300 659 parts 1 and 2 (PSTN, Subscriber line protocol over the localloop for display [and related] services [part 1 on-hook data transmission and part 2 off-hook datatransmission]), and ETS 300 778 parts 1 and 2 (PSTN, Protocol over the local loop for displayand related services [part 1 off-line data transmission and part 2 on-line data transmission]).
P. O’Keefe (Telecom Eireann) had written to the Payphone Terminals and Systems (PTS) projectproposing an ETSI standard for Euro coin validation tones in payphones which accept Europeancoin. Unfortunately PTS only deals with IC cards, so the responsibility was passed back to ATA.Their Chair misunderstood that network tones were referred to and involved SPS, DTA and TC
HF. This history is recorded in TD-19. Early in the meeting, P. O’Keefe was privately warned ofthe fraud potential in his original proposal, so he drafted a new work item (TD-36) to study thecurrent practice of payphone control. The work was considered by ATAe on the basis that SDSSsignals could be used, but it only received support from two members, BT (TD-25) and TelecomEireann. Delegates were urged to give this issue further consideration.
Two documents from W. Schellhas (Deutsche Telekom), TD-27 (corrections) and TD-28 (proposedchanges for call accounting display), propose amendments to TR 102 088 V1.1.1 (on Advice ofCharge display services). DT intends to provide AOC-E service for analog TE in the year 2001.
FINAL PLENARY
TR 101 188 was approved for voting as an EG in addition to being published as a TR.
At a vote on EN 301 437 with the addition of the note, five of those who originally voted “no”abstained; with only two votes against it, the standard received enough support to be approved togo for national vote.
Authority was delegated to ATAe to approve TD 101 292 at their meeting in May. Authoritywas also delegated to ATAc to approve TR/ES x01 235 at their meeting in June.
ATA members felt unable to fully support the DTA input to the STF steering group meeting, butapproved TD-38 (ATA liaison to OCG), which was similar in intent but milder in tone. Itnominates ATA’s official representatives to the steering group as N. Encarnação (OFCOM), P.Lottin (France Telecom), and R. Trevland (Norwegian PT).
Walter J. G. Mellors, WM Services
ETSI ATA MEETING ROSTER, MARCH 8-12, 1999, SOPHIA ANTIPOLIS, FRANCE
Nuno Encarnação, OFCOM/BAKOM ATA Chair
Austria Austrian Fed. Ministry Walter MarxtTelekom Austria AG Gustav MagdoinTelekom Austria AG Josef Halbertschlager
Czech Republic Testcom Prague Zdenek GutterDenmark Teledanmark A/S Finn RavensholtFinland Finnet Group Kaj Andersson
Finnish Telecom. Antero SaarinenFrance Alcatel Jean-Marie Notter
ETSI Secretariat Claire d’EsclercsFrance Telecom Jerome DescosFrance Telecom Philippe LottinFrance Telecom Jean MontenotIBM France Jean MartinTRT Lucent Technologies Thierry Salaun
Germany Deutsche Telekom Othmer KlausDeutsche Telekom Werner SchellhaasDeutsche Telekom Stefan WüstGlobespan Semiconductor Jacques BesseyreREG TP Christina GandyraSiemens AG Josef-Peter ZuckTDK Electronics Europe Peter de Wit
Ireland Telecom Eireann Pat O’KeeffeItaly CSELT Rodolfo Ceruti
CSELT Fabrizio ProvenzaleEricsson Telecom. Pasquale PlaitanoTelecom Italia Sonia LalliTelecom Italia Paolo Vitiello
Norway Norwegian Post & Tel. Eskil ElnessNorwegian Post & Tel. Mikael KarlssonNorwegian Post & Tel. Jan NergardNorwegian Post & Tel. Eskil ElnessNorwegian Post & Tel. Gunn Anny RoymTelenor R&D Finn Stafsnes
S. Africa Telkom SA Ltd Kimon AposporisTelkom SA Ltd Pieter ErasmusSiemens Telecommunications Paul Alberts
Spain Alcatel Espana SA Jose Maria GarciaAlcatel Espana SA Juan-Antonio SaezMinisterio de Fomento Enrique BerrojalvizTelefonica de España S.A. Enrique Carrasco
Sweden Ericsson Bus. Networks Per DöfnäsEricsson Bus.Networks Berndt MartensonEricsson LM Urban JanssonTelia AB Göran EngströmTelia AB Christer Karlsson
Switzerland OFCOM/BAKOM Nuno EncarnaçãoUK British Telecom. Chris Harley
DTI John LongETSI User Group Walter MellorsMotorola Trevor HizzardMotorola Simon KangMotorola Andy MullenNortel Fred HowettOFTEL Martin Harris
REPORT OF ETSI DTA (DIGITAL TERMINAL AND ACCESS PROJECT)MEETING #5, MARCH 9 - 11, 1999, SOPHIA ANTIPOLIS, FRANCE
Two joint sessions were held with EP ATA; see the ATA meeting report in this issue. Note: Alldocuments referred to in this meeting report are available electronically to ETSI members fromthe EP DTA Permanent (99) area of the ETSI Server.
D. Maxey (British Telecom) is the EP (ETSI Project) DTA Chair. The Agenda is DTA(99)003r01(EP ATA Chair). The report of the previous meeting (DTA #4) is DTA(99)049B. It was approvedwithout change. DTA(99)004 is the Chair’s report.
DTA(99)006 (J. Pritchard, OGC Secretary) provides an overview of decisions of the OCG(Operational Coordination Group). The OCG supports giving TIPHON an eight man-monthextension to the STF, a 10 man-month extension for DECT work (STF GZ), and creating an STF(under EP ATA) to support the production of Harmonized Standards (HSs) under the R&TTEDirective.
DTA IMPLEMENTATION OF THE RTTE DIRECTIVE
Consideration of the effects of the Radio and Telecommunications Terminals Equipment Directive(R&TTED) on EP DTA constituted a major part of the meeting. The agreed text of the Directivewas made available to members for their information, as was the text for EG 201 399, which isthe draft ETSI Guide on the production of Harmonized Standards (HSs) under the R&TTED.
DTA(99)008 (TM6 Chair) contains the draft ETSI work plan for the R&TTED. A philosophy isemerging to develop requirements relating to R&TTED separately from standards containingrequirements related to the operation of the equipment. The proposed standardization programconsists of two separate activities. The first activity is aimed at developing HSs for equipmentfor which there exists an HS under 98/13/EC; it consists of reviewing the technical requirementsand seeing where existing standards can be grouped to be covered by a single HS. The secondactivity is aimed at developing HSs for other equipment where it is necessary to establish apresumption of conformity as well as grouping existing standards together. The draft work planlists standards and technical areas where such a review is needed.
The formation of an ETSI R&TTED Steering Group (SG) under the aegis of OCG was noted withgreat interest.
DTA members considered it very important to ensure that this Steering Group has adequaterepresentation from Technical Bodies (TBs) representing non-radio interests. Moreover,members emphasized the need for expert TBs to be actively involved in the approval of HSswithin their field of expertise and likewise to have a say in the appointment of the STF. Inaddition, for non-radio applications, it was considered that priority should be given by theSteering Group to the production of HSs for services that currently do not have a Technical Basisfor Regulation (TBR, ETSI standard).
In response to the invitation from the Steering Group Chair it was agreed to nominate thefollowing delegates to represent DTA at the Steering Group :
A. Kamcke, Siemens AG, DES. Kang, Motorola, UKI. Marshall, Nortel Networks, UKG. Sebek, France Telecom, FR
In the light of the importance of the work of the Steering Group, it was agreed to send a LiaisonStatement to the initial Steering Group meeting stating DTA’s opinions on the issues raised. Thisliaison is DTA(99)015R02.
It was decided to defer consideration of a DTA R&TTED work plan until results of the SteeringGroup meeting become available.
A Miscellaneous Work Item was approved for DTA to take part in all aspects of the R&TTEDwork. I. Marshall (Nortel Networks UK) will be the Rapporteur. This Work Item was supportedby all members present.
Note: DTA has since been informed that the Directive was adopted on March 9, 1999 and isknown as 99/5/EC. It is still to be published in the OJEC (approximately 4 to 6 weeks at themost). It is expected to be fully in force on March 10, 2000.
B CHANNEL AGGREGATION AND COMPRESSION
B. Hass (Orsenna, standing in for J. P. Senkheisen) gave a presentation on the status of ESRES/DTA-005069, B Channel Aggregation and Compression. It was noted that the aggregationand compression methods specified are independent of hardware platforms and are based uponRFC 9051 and RFC 9052. It was agreed that members be given until April 30, 1999 forcomment to the Rapporteur, after which, if no objections are received, it will be submitted to theETSI membership approval process.
ISDN (NARROWBAND)
J. Dietz (KPN), who was standing in for P. Nooren, introduced the topic of ISDN (narrowband).The previous DTA meeting had generated a liaison to CENELEC suggesting adding a starconfiguration to the ISDN basic access wiring standard; this Liaison is in DTA(99)001.DTA(99)005 is the reply which had been received from CENELEC (Commission Europeenne deNormalisation Electrotechnique). The reply supported the concept of start wired ISDN, posedsome questions about operation in specific cable configurations and invited DTA to send arepresentative to future CENELEC meetings. J. Dietz agreed to investigate whether or not aKPN delegate could be made available; he will inform DTA accordingly. If it is agreed to send aDTA delegate, the arrangements will be made via the ETSI Liaison Officer, G. Ochel.
The proposed withdrawal of ETS 300 153 (Attachment requirements for terminal equipment toconnect to an ISDN using ISDN basic access - NET 3 Part 1) and ETS 300 156 (Attachmentrequirements for terminal equipment to connect to an ISDN using ISDN primary rate access -Net 5) was noted.
B-ISDN
The Chair agreed to write to the Chair of the Technical Recommendation Application Committee(TRAC) requesting information on the fate of the Liaison generated at the last DTA meetingwhich proposed an approval method for broadband terminals.
DATACOMM APPROVAL
It was noted that EN 301 401 is now in Public Enquiry (PE). A date was agreed for a resolutionmeeting (see below). EN 301 401 provides attachment requirements for DTE to connect to publicnetworks that have physical and electrical network presentations based upon the ITU V-seriesRecommendations. This EN is a proposed replacement for TBR 1 and 2 (PSTN and PSPDNattachment requirements).
XDSL TECHNOLOGY
OCG #7 has agreed to set up a joint group comprising TM6, ATA, ERM and DTA to consider theeffects of xDSL. It was agreed that DTA should participate in this work and a MiscellaneousWork Item was approved to cover this; the DTA Chair will act as Rapporteur. This Work Itemwas supported by BT, Deutsche Telekom, Siemens, NTP, FT, OFCOM and Swisscom.
REVIEW OF ONP DIGITAL LEASED LINE STANDARDS
G. Sebek (FT) presented three documents which propose amendments to the Open NetworkProvision (ONP) digital Leased Line (LL) standards: DTA(99)011 (ONP LL: revision ofspecifications, resistibility ), DTA(99)012 (ONP LL: revision of specifications, jitter performance)and DTA(99)013 (ONP LL: revision of specifications, jitter performance measurement).
DTA(99)011 discusses resistibility requirements and questions the reasons for having differentrequirements for different data rates. It was noted that ITU-T Recommendation G.703 had beenupdated and therefore the ONP standards are not in accordance with the latest version of thisRecommendation.
The ISDN Primary Rate is also affected in the same way. DTA was reminded that the previousmeeting had drafted a liaison to ERM requesting their cooperation in removing references to ETS300 046 (Primary rate access - safety and protection, General) and ETS 300 047 (Basic access -safety and protection, General) from the ISDN TBRs; as yet no reply had been received to thisliaison.
During this discussion, A. Mullan (Motorola) reported on the work of the ETSI/CENELECresistibility committee; he stated that they had produced a report that needs to be approved byboth organizations. The report is known as ETR 238; ERM/EMC is the ETSI TB concerned. A.Mullan strongly recommended that the advice of this TB be taken into account when updatingresistibility requirements.
As a result of these discussions, it was decided that the ONP digital leased line standards andISDN Primary Rate standards should be updated to:
a) Be consistent between the various standards; and,b) To comply with the advice of ERM/EMC.
It was agreed to draft a further liaison to ERM/EMC requesting explicit instructions on what todo with resistibility requirements in both the TBRs and the other standards. This liaison isDTA(99)016. The procedural difficulties of updating TBRs were acknowledged; C. d’Esclercs(ETSI) agreed to seek advice from G. Craik (ETSI Secretariat).
It was pointed out that to comply with the ETSI Rules of Procedure, separate Work Items wouldneed to be generated for each standard to be updated. It was agreed in the first instance togenerate a Miscellaneous Work Item to identify those standards concerned and to propose asuitable Amendment. G. Sebek (FT) agreed to be Rapporteur. The Work Item was supported byFT, Motorola, Nortel, and OFCOM. This Work Item will not become operative until a reply isreceived from ERM/EMC.
DTA(99)012 contains proposals to update the ONP digital leased line standards to take intoaccount revised ITU-T Recommendation G.823 (The control of jitter and wander within digitalnetworks which are based on the 2048 kbit/s hierarchy) which specifies the jitter performance forthe PDH (primary digital hierarchy) hierarchical bit rates. It was explained that the existingversions of the ONP leased line standards were based upon an old version of G.823 which waswritten for PDH-based networks. G.823 has been revised to take SDH-based networks intoaccount; it was proposed that the ONP standards follow suit.
As this is a complex issue and little advance notice had been given, the Chair decided thatmembers be given until April 30, 1999 before they decide so that they have an opportunity toconsult their experts. On April 30, the Chair will e-mail DTA members asking for their decision.If members agree to the work, appropriate Work Items will be created and supporters sought.Members were asked to give reasons if they did not want the work to proceed. It was noted thatthe TBR procedural problems also exist with this proposal. If the Work Items are agreed, ETSITC TM and ECMA TC32 should be consulted.
SAFETY, PROTECTION, AND EMC
A. Mullan (Motorola) informed the meeting that the proposed joint ETSI/CENELEC safetycommittee had not been approved in its proposed form and therefore ETSI had formed its ownsafety Technical Body to mirror CLC/TC74. This TB will be known as ETSI TC Safety and willbe chaired by R. Hughes (Nortel).
The first meeting of this new TC Safety will take place on April 23, 1999 (see ETSI CollectiveLetter 1939).
The Chair explained that the ETSI Rules of Procedure state that officials of TBs are appointedfor a two-year term, after which they should offer themselves for re-appointment or stand downand an election for a replacement conducted. He further explained that this two-year term hadexpired for both himself and the Vice Chair, F. Jürgens (Deutsche Telekom), and that they wereboth willing to stand for a further period, but that due to changes within their organizationsneither was in a position to give a full two-year commitment. There being no other candidates,both the Chair and Vice Chair were re-appointed.
DTA #5 MEETING ROSTER, MARCH 8 - 12, 1999, SOPHIA ANTIPOLIS, FRANCE
David Maxey, BT DTA ChairFrank Jürgens, Deutsche Telekom AG DTA Vice-ChairClaire d’Esclercs, ETSI Secretariat ETSI Support Officer
Czech Republic Ministry Of Transport & Com. Zdenek GutterFinland Telecom. Admin. Centre Antero SaarinenFrance France Telecom Georges SebekFrance IBM La Gaude Jean-Marc CazaentreFrance Orsenna Béatrice HassGermany Siemens AG Andreas KamckeNetherlands KPN Jan B DietzNorway PT Gunn Anny RoymSwitzerland OFCOM Claude-André PolierSwitzerland Swisscom Christof KaeserUK Motorola Ltd Trevor HizzardUK Motorola Ltd Simon KangUK Motorola Ltd Andy MullanUK Nortel Networks (Europe) Ian Marshall
REPORT OF Q4/15 RAPPORTEURS MEETING ON XDSLMARCH 29 - APRIL 2, MELBOURNE, AUSTRALIA
Note: Some documents at this meeting include as “Source” companies or organizations which arenot ITU members. These organizations were removed from the source list of those papers at themeeting. This report includes the original source list for all papers, including those organizationswhich are not ITU members. Companies which were deleted from papers are shown instrikethrough text.
IPR
Lucent has submitted the general licensing agreement. See MA-002R1 (R. Stuart, Rapporteur,3Com), the report of the last meeting, for the Intellectual Property Rights (IPR) list (32organizations are listed). The new process for submission of IPR statements was also reviewed.Nortel indicated that it was not in a position to make a statement either way.
The Rapporteur then asked if anyone wished to make a statement relating to any new proposalsbeing made at this meeting. Stanford University announced that it had filed for IPR.
LIAISONS
MA-032 (Q5/5 Rapporteur J. Erreygers, Raychem N.V.) is a liaison on K.sov (Safe limits foroperating voltages and currents for telecommunications equipment that is powered over thenetwork) and K.sc (Safety criteria for telecommunications equipment). Both K.sov and K.sc havebeen Determined. K.sc applies to all telecommunications network infrastructure. K.sovspecifically applies to equipment that is using remote power feeding. MA-032 was deferred to theeditor’s sessions but was not reviewed further during this meeting.
MA-018 (C. Hansen, Intel) comprises the G.lite and G.lite bis Issues Lists. MA-081 (C. Hansen,Intel) is the list of contributions and work plan for this meeting.
MA-022r3, Proposed Appendix B to G.992.2 (T. Cole, Editor, AMD), is an Implementers Guidefor using G.992.2 together with G.994.1 (G.hs). This proposed Appendix was reviewed in detail.The goal is to have it approved with G.992.2.
MA-039 (T. Cole, AMD; Intel, Aware, Alcatel, Compaq) requests that a statement be added toG.lite indicating that if errors occur during SHOWTIME, a Fast Retrain procedure may beinvoked. This proposal was accepted.
MA-040 (T. Cole, AMD; Compaq) proposes that the text of G.lite be modified prior to finaldecision to allow the value of the Fast Retrain Politeness Cutback to be vendor-discretionary atthe ADSL Transceiver Unit-Central Office End (ATU-C). This proposal was placed in the bisIssues list.
MA-059 (I. Sharfer, Orckit) proposes to expand the ADSL Transceiver Unit - Remote TerminalEnd (ATU-R) capabilities by allowing it to specify a negative relative downstream Fast Retrainpower cutback value, so that the ATU-C transmit power can be boosted if necessary. Thisproposal was also placed in the bis Issues list.
MA-060 (I. Sharfer, Orckit) proposes to dedicate two bits in R_MSGS and R_MSG_FR1 for on/offhook indication.
MA-061 (D. Van Bruyssel, Alcatel) discusses some problems in the definitions of the handoverfrom G.994.1 termination to G.992.1 Initialization and G.992.2 Initialization. A similar problemoccurs in the G.992.2 Escape to Fast Retrain. This contribution contains proposals to resolvethese problems.
MA-062 (D. Van Bruyssel, Alcatel) proposes a number of corrections to the text of G.lite.
MA-084 (C. Hansen, Intel) is the report of the ad hoc group, which had reviewed MA-061 andMA-062. The ad hoc group agreed with all of points raised and the majority of the proposedsolutions given in MA-062. The solution to Point 2.9, abort of an ATU-R initiated Fast RetrainRequest, was not accepted. Work will be necessary between now and the Boston meeting in Mayto resolve this issue.
G.LITE BIS
MA-023r3 (T. Cole, AMD; also PairGain, Intel, Aware, 3COM, TI, Motorola, NationalSemiconductor, ADI, Lucent, and Compaq) proposes that field experience and application-basedrequirements of the physical layer be the basis of the priority items for the work on G.lite bis.These two items were added to the open issues list.
MA-034r1 (J. Cioffi, Stanford and P. Chow, TI) introduces an express swapping AOC (ADSLOverhead Channel) command that dramatically increases the speed of swapping (indicating afactor of 100-8,000 speed increase). It also introduces a second bit-swap confirmation command.The proposals made in MA-034r1 received considerable discussion. It was eventually decided toadd the express bit swapping to the open issues list.
MA-035 (J. Cioffi, Stanford) provides as analysis of ways of implementing the express swapping(ES) proposed in MA-034.
MA-076r1 (N. King and B. Jenness, Siemens) provides an estimate of the additional bandwidththat could be made available if G.lite were to use the Plain Old Telephone Service (POTS)spectrum (when POTS wasn’t required). Based on this, it proposes that G.lite bis should includea Power Spectral Density (PSD) mask at -34.5 dBm/Hz down to the lowest carrier. MA-069 (F.Van der Putten, Alcatel) is essentially in-line with the proposal in MA-076r1. The proposals forusing the lower (voice) end of the band were added to the G.lite-bis agreements list.
It was agreed that interference from AM broadcasts will be added to the list of interferers in thepresence of which G.lite-bis must operate. (See MA-070 and MA-082, agreement 2 below.)
MA-028 (S. Abbas, Centillium Technology; L. Humphrey, Nortel; J. Mueller, 3COM) proposesthat the item describing the requirement for a minimum 4 kbit/s clear eoc (error control channel)capacity in Section 6.1 be replaced with a sentence that states that “a minimum clear eoccapacity requirement is for further study.” It was decided to delay any action until the Maymeeting in Boston.
There were no new contributions on G.ploam bis at this meeting.
MA-046 (F. Van der Putten, Alcatel; T. Cole, AMD; C. Paganelli, PairGain; J. Cioffi, Stanford)proposes that the PSD level of synchronization symbols be reduced to the average PSD level ofthe used sub-carriers.
MA-061 (D. Van Bruyssel, Alcatel) proposes text changes to resolve problems in the definitions ofthe handover from G.994.1 termination to G.992.1 Initialization and G.992.2 Initialization and in
the G.922.2 Escape to Fast Retrain. The proposals made in MA-061 were accepted with minormodifications.
MA-069 (F. Van der Putten, Alcatel) identifies the advantages of defining the use of ADSL in anall-digital environment (i.e., no underlying service). It specifically proposes that a splitterlessservice be defined with the PSD masks for G.dmt bis and G.lite bis and that that service beextended to allow for the optional allocation of the POTS band to ADSL.
MA-074, Framing structure for ATM transport (J. Beany, R Chen, and J. Stiscia, Virata; andIteX), proposes replacement text to eliminate an inconsistency between Section 6.2 and Section7.2.4 in the present draft Recommendation G.992.1. The result is that framing structure 3should be listed as one of the mandatory framing modes supported by the ATU-C when configuredfor ATM transport.
MA-085 (D. Shaver, TI; Compaq) proposes the addition of notes to Annex E (POTS and ISDN-BAsplitters) of G.992.1 recommending an impedance 100 ohms above 4 MHz. The reason for this isto ease compatibility with HomePNA. (See also MA-055 in G.gen bis, below.) The proposal wasessentially approved using one generic note to replace the different, section-specific notesproposed.
G.GEN BIS
MA-027 (M. Tzannes, R. Gross, H. Padir, S. Sandberg, and D. Krinsky, Aware) describes aprotocol for Seamless Rate Adaptation (SRA) that is characterized as enabling fast, robust andefficient on-line rate adaptation in Discrete Multi-tone Carrier (DMT) systems. The SRA protocolalso enables new methods for transitioning in and out of low power or quiescent modes. Theconcept of seamless rate changing was added to the open issues list.
MA-043 (J. Carlo and B. Wiseman, TI) proposes an improved “suspend” type quiescent mode ofoperations for reduced steady state power consumption building on previous contributions. Thetechniques proposed are equally applicable to T1.413-1998, G.992.1, and G.992.2implementations.
MA-055 (HomePNA represented by: H. Johnson, 3COM; T. Cole, AMD; R. Hamdi, Compaq; M.Rushing, Conexant; S. Khorhar, IBM; B. O’Mahony, Intel; K. Hayden, Level One; S. Strauss,Lucent; W. Chen, Motorola; G. Zimmerman, PairGain; D. Shaver, TI) provides information onrelevant portions of the HomePNA 1.0 (1.0 Mbit/s) specification, with emphases on HomePNA 1.0spectral compatibility with voice-band devices, G.lite, and G.dmt. Based on a theoreticalanalysis, it draws the conclusion that HomePNA 1.0 and G.lite/G.992.1 can be compatible (i.e.,aliasing of HomePNA signals into the G.lite receiver should be less than -140 dBm/Hz). Indiscussion it was noted that this paper does not consider the effects of loading on DSL systems.
MA-070 (M. Drew, Nortel) provides results of an assessment of ingress present on residentialloops due to AM radio transmitters. It suggests that significant AM ingress occurs on manysubscribers loops and proposes that Q4/15 develop North American system performancerequirements in the presence of AM and HAM ingress noise for G.lite bis and G.dmt.bis. Nortelplans additional contributions on this topic. This topic was added to the G.lite bis issues list (seeabove).
MA-071 (M. Wingrave, Nortel and J. Carlo, TI), with MA-072 and MA-073, proposes thedevelopment of an upstream power control mechanism in G.992.1 and G.992.2 bis.
MA-072 (M. Wingrave, Nortel) proposes what is referred to as a realistic FEXT model for theassessment of ADSL upstream performance.
MA-073 (M. Wingrave, Nortel) proposes the use of upstream power control on non-overlappedspectra to limit FEXT into ATU-R receivers on adjacent loops.
MA-047 (F. Van den Putten, Alcatel) requests the addition of the Belgian Vendor IDAdministrator to Appendix 2 of G.994.1.
G.SHDSL
MA-005 (S. Blackwell, Adtran) provides the updated Issues List and draft Recommendation forG.shdsl, reflecting contributions to the January 1999 meeting of the Q4/15 Rapporteurs Group inPortland, OR. MA-015 (S. Blackwell, Adtran provides the updated Issues List for G.shdsl,reflecting contributions to the January 1999 meeting of the Q4/15 Rapporteurs Group inPortland, OR. MA-015r1 (S. Blackwell, Adtran) updates the list to reflect the input at thismeeting.
MA-026 (K. Foster, BT) is a liaison from ETSI TM6 which reports the status of their workdefining a reference model which they will send via liaison to Q4/15 as soon as it is available.MA-026 also provides a number of requirements (spectral compatibility with: other DSL systems,ISDN-BA and ISDN-PA; multirate operation, regional annexes for loop plant), that TM6 hasidentified to assist Q4/15.
MA-030 (T1E1.4 represented by: M. Rude, ADC; R. Goodson, Adtran, T. Starr, Ameritech; S.McCaslin, Cicada Semiconductor; M. Sorbara, GlobeSpan; J. Quilici, Level One) providesinformation on applications and service characteristics for G.shdsl. It also proposes bit rates,latency, bit error rate, loop reach, span powered repeaters, network timing reference, andspectral compatibility requirements needed to support these applications and services.
MA-036 (R. Goodson and K. Schneider, Adtran; T. Starr, Ameritech; M. Sorbara, GlobeSpan; J.Quilici, Level One; M. Tu, PairGain) provides the consensus view of T1E1.4 on the open items ofthe G.shdsl living list.
MA-037 (T1E1.4 represented by: M. Rude, ADC; R. Goodson, Adtran; S. McCaslin, CicadaSemiconductor; M, Sushing, Conexant; M. Sorbara, GlobeSpan; J. Garza, Level One; P.Versavel, Raychem; G. Zimmerman, PairGain) proposes a schedule for G.shdsl with approval byOctober 2000. The timetable of Determination 04/2000 and Approval 10/2000 proposed in MA-037 was accepted as a goal.
MA-038R1 (S. Blackwell, Adtran) provides a comparison of the proposals from T1E1.4, ETSITM6 and Japanese company contributions to previous Q4/15 meetings. There is a high level ofagreement between the different proposals at this early stage.
MA-044 (C. Baumert, Raychem; Transcend) provides an overview of Digital Subscriber Linetechnologies that are specifically designed to provide symmetric data rates on the local loop. Itwas presented for information.
MA-052 (J. Hausner, Siemens AG; M. Kimpe, Adtran; J. Benndorf, Alcatel-Ke; G. Eisler,Conexant Systems; H. Takatori, Level One Communications; M. Simkins, Lucent Technologies;E. Shusterman, Orckit/MOC Israel, J. Lindholm, Nokia) makes three proposals:
1. Analog splitters for the purpose of supporting narrow band services shall not be required,2. The selected line code should make as much use as possible of the lower frequency range where
high signal-to-noise ratio are most evident3. The line code to be used shall be based upon Ungerboeck coded pulse amplitude modulation.
MA-054 (J. Garza, Level One) proposes a system reference model for G.shdsl.
MA-075 (K. Matsumoto, Sumitomo Electric; Matsushita, NEC) provides simulation results thatshow that there is interference between PAM-based SHDSL and TCM-ISDN. Two approaches tominimize this interference are examined: TCM-PAM-SHDSL and TCM-DMT. No conclusion isdrawn and further study is proposed.
MA-080 (S. Blackwell, Adtran) is the proposed work plan for G.shdsl. The following points wereagreed during discussion:
• Minimizing equipment cost should be a consideration
• G.994.1 shall be used as the initialization sequence• Multi-rate operation will be specified• Support the range of rates from 192 kbit/s to 2.304 Mbit/s• Provisionally it shall support the following end-user payload symmetric bit rates:
192 kbit/s, 256 kbit/s, 384 kbit/s, 768 kbit/s, 1.544 Mbit/s, 2.048 Mbit/s, 2.32 Mbit/s• Meet a latency requirement of 5 ms for rates > 1.5 Mbit/s and 1.25 ms for < 1.5 Mbit/s• Provide a means of error control, which can be adjusted, to trade off performance for latency.• An error rate of 10-7 , with some tolerance, shall be used for performance evaluation• Optionally support powering of the HTU-R on a single span• Optionally support powering of regenerators• Power usage shall be consistent with the span powering requirements• Capable of supporting a clear EOC channel• The HTU-R shall be referenced to network timing• Capable of supporting the Service Requirements (to be determined)• Provide for automatic power cutback• Analog splitters shall not be supported• Regional performance requirements will be separate annexes• The following loop reach goals were accepted for North America:
- 256 kbit/s: 17.5 kft of 26 AWG, ANSI T1.601 loops 1, 2, 3, 4- 384 kbit/s: All Revised Resistance Designed loops, 15 kft of 26 AWG, e.g. ANSI T1.601
loops 4-15- 768 kbit/s: (to be determined)- 1.544 Mbit/s: All Carrier Serving Area loops, 9 kft of 26 AWG, e.g., all loops in ITU Rec.
G.991.1- 2.048 Mbit/s: 6 kft of 26 AWG
• The following services (at a minimum) will be considered for spectrum compatibility for NorthAmerica:
- Voiceband services- G.991.1 (HDSL)- G.992.1 (G.dmt)- G.992.2 (G.lite)- RADSL per T1E1.4/98-294R2- ANSI T1.601 (BRI)- ANSI T1.410 (DDS)- ANSI T1.403 (T1 carrier with repeaters)- ANSI HDSL2 per T1E1.4/99-006
• It shall operate in the presence of AM Radio interference.
G.VDSL
MA-078 (S. Palm, Matsushita) outlines the work program for G.vdsl.
MA-025 (K. Foster, BT, on behalf of ETSI TM6) provides the ETSI TM6 views on the Issues Listfor G.vdsl. It further encourages Q4/15 to take note of these comments, and where appropriate tomodify their work accordingly.
MA-029 (FSAN represented by: R. Heron, Bell Canada; R. Clarke and J. Cooke, BT; L. Magnoneand R. Persico, CSELT [Telecom Italia Group]; M. Friese and T. Kessler, Deutsche Telekom; M.Vautier, FT; A. Forcucci, GTE; Gye Tae Kihl, Korea Telecom; R. van den Brink, KPN; K.McCammon, SBC Technology Resources; M. Isaksson, Telia) proposes that Frequency DivisionDuplexing (FDD) is the preferred duplexing scheme for Very high speed ADSL (VDSL) from theoperator perspective.
MA-031 (M. Rude, ADC; T. Starr, Ameritech; G. Sherrill, Bell Atlantic; S. Abbas, Centillium; J.Joyce, Cisco; G. McAnich, GTE; C. Hansen, Intel; K. McCammon, SBC; P. Youngberg, Sprint; J.Cioffi, Stanford University) expresses a T1E1.4 consensus view proposing that the G.vdsl workprogram be organized to develop the draft G.vdsl Recommendation in a timely manner. Itproposes that each component of the VDSL system be addressed independently, to the extentpossible, and it should have the goal of specifying only one method for each component. WhenMA-031 was reviewed, there was agreement to the goal of developing solutions for each
component independently. The goal of reaching a single solution for each component receivedconsiderable discussion, however it was finally agreed (although Nortel seemed to still havestrong reservations). On the question of establishing criteria for evaluation of the variouscomponents, there was also considerable controversy. It was finally decided to focus initially ondeveloping a set of requirements.
MA-033 (J. Cioffi, Stanford University) provides an analysis of the problems arising fromCoexistence of 1 Mbit/s HPNA (Home Phoneline Network Alliance) and DMT VDSL via Multi-user Detection and Code Division Multiplexing. It proposes the use of a multi-user detection andcoding system that is characterized as allowing VDSL to operate in the presence of HPNAcrosstalk with little or no degradation. It further concludes that while this system works forDMT signals, it does not appear to work as well for QAM/CAP signals.
MA-041 (VDSL Coalition represented by: V. Oksman, Lucent; also Analog Devices, BoschTelecom, Broadband Technologies, Broadcom, Brooktree/Rockwell, Comcore, ECI Telecom,GlobeSpan, GTE Government Systems, Harris Semiconductor, Libit, Metalink, Next LevelCommunications, Newbridge Networks, Nokia Telecommunications, Siemens AG, US West,ViaGate Technologies, VDSL Systems) proposes a Physical Media Dependent (PMD) sublayer asa part of the VDSL specification, which defines the transmission method over the link includingline coding, modulation and duplexing. It proposes that this PMD sublayer use DifferentialConstellation coding, Single-Carrier Modulation (SCM) and an FDD.
MA-042 (VDSL Coalition represented by: V. Oksman, Lucent; also Analog Devices, BoschTelecom, Broadband Technologies, Broadcom, Brooktree/Rockwell, Comcore, ECI Telecom,GlobeSpan, GTE Government Systems, Harris Semiconductor, Libit, Metalink, Next LevelCommunications, Newbridge Networks, Nokia Telecommunications, Orckit Communications,Savan Communications, Schmid Telecom, Siemens AG, Tellabs Oy, US West, ViaGateTechnologies, VDSL Systems) proposes a specification of the Physical Media SpecificTransmission Convergence sublayer (PMS-TC) for a VDSL transceiver based on single-carriertechnology.
MA-045 (Y. Okamura, NEC) examines the home network proposal of HomePNA and the impactbetween HomePNA and VDSL signals in adjacent lines. It suggests that the noise injection fromnon-DSL, especially HomePNA, has to be considered in the System Requirements of G.vdsl andG.test.
MA-050r2 (VDSL Alliance represented by: T. Pollet, Alcatel; also Aware, Cadence, DataPathSystems, Ericsson, IBM Research, Italtel, Marvell Semiconductor, NEC America, NEC Japan,Newbridge Networks, Nortel, Rockwell, Samsung AIT, Spectrum Signal Processing,STMicroelectronics, Stanford University, Telia, Texas Instruments, Transcend Access Systems,Tripath, US West) proposes a PMS proposal based on multi carrier transmission.
MA-051 (T. Pollet, Alcatel; also Aware Inc., Ericsson Telecom, IBM, NEC, Stanford University,STMicroelectronics, Telia Research AB, Texas Instruments) proposes that some deploymentstrategies of ADSL and VDSL will impose their coexistence in the network at both the CentralOffice and the Cabinet. Therefore, operators will be concerned with the possible interoperabilityof VDSL with ADSL in order to allow for a smooth transition from low to high throughputsystems.
MA-053 (VDSL Alliance represented by: J. Cioffi, Stanford University and K. Jacobsen, TI; alsoAlcatel, Aware, Cadence, DataPath Systems, Ericsson, IBM Research, Italtel, MarvellSemiconductor, NEC America, NEC Japan, Newbridge Networks, Nortel, Rockwell, SamsungAIT, Spectrum Signal Processing, STMicroelectronics, Telia, Transcend Access Systems,Tripath, US West) recommends that proposed VDSL transmission techniques be evaluated interms of Spectrum Management/compatibility with other services and range/rate compliance beadded to the VDSL terms of reference. This contribution also proposes that a correspondingwork item on VDSL spectrum-compatibility and performance related system requirementsverification be added to the VDSL issues list. It notes that the group should collaborate withT1E1.4 in their spectrum management work.
MA-056 (D.J.G. Mestdagh, ST Microelectronics; also Stanford University, Ericsson) providesinformation to support the premise that digital complexity is not an issue for DMT-based FDD-VDSL. The paper provides information on power consumption and die size for a given IC designimplementing 2K-(I)Fast Fourier Transform (FFT) processor for DMT-based FDD-VDSL.
MA-057 (VDSL Alliance represented by: D.J.G. Mestdagh, ST Microelectronics; also Alcatel,Aware, Cadence, DataPath Systems, Ericsson, IBM Research, Italtel, Marvell Semiconductor,NEC America, NEC Japan, Newbridge Networks, Nortel, Rockwell, Samsung AIT, SpectrumSignal Processing, Stanford University, Telia AB, TI, Transcend Access Systems, Tripath, USWest) proposes that G.vdsl specify a family of optional scalable implementations of DMT modems.
MA-058 (M. Isaksson, Telia; also Ericsson, Stanford University, ST Microelectronics) proposesthat the PSD mask be programmable in order to be in a position to react to possible regulatorychanges.
MA-063 (J. Chow, TI, and J. Cioffi, Stanford University) proposes that when comparingcomplexity for VDSL, only systems that meet the requirements should be considered. It furtherstates that a DMT system that meets the minimum system requirements will be simpler than aCAP/QAM system that also meets the minimum requirements.
MA-064 (Y. Okamura, NEC ) proposes that the frequency band of HomePNA be shifted from 5.5MHz - 9.5 MHz to 15 MHz - 30 MHz, which is higher than the VDSL band.
MA-065 (H. Furuno, NEC; also Oki Electric Industry, Matsushita) presents an initialrequirements list related to the environment in Japan.
MA-068 (H. Furuno, NEC; also Oki Electric Industry, Matsushita) presents an optional 400 HzTDD mode.
MA-067 (VDSL Coalition represented by: D. Schmücking, Siemens AG; also Analog Devices,Bosch Telecom, Broadband Technologies, Broadcom, Brooktree/Rockwell, Comcore, ECITelecom, GlobeSpan, GTE Government Systems, Harris Semiconductor, Libit, LucentTechnologies, Metalink, Next Level Communications, Newbridge Networks, NokiaTelecommunications, Orckit, Savan Communications, Schmid Telecom, Tellabs Oy, US West,ViaGate Technologies, VDSL Systems) proposes that G.vdsl utilize handshaking based onG.994.1. It also proposes that it use the 4000 Hz G.994.1 signaling family, define two carriersfor handshaking - one for the downstream and one for the upstream - and determine the exactcarrier frequency after the G.vdsl frequency band allocations have been agreed upon. It furtherproposes that the G.994.1 full duplex transmission mode be used for G.vdsl startup. Robustnessand complexity should also be considered in determining the optimum symbol rate for G.vdslhandshaking.
MA-077 (VDSL Alliance represented by: J. Cioffi, Stanford and T. Pollet, Alcatel; also Aware,Cadence, DataPath Systems, Ericsson, IBM Research, Italtel, Marvell Semiconductor, NECAmerica, NEC Japan, Newbridge Networks, Nortel, Rockwell, Samsung AIT, Spectrum SignalProcessing, ST Microelectronic, Telia, Texas Instruments, Transcend Access Systems, Tripath,US West) proposes that G.vdsl should also study the 4.3125 kHz of a tone spacing facility of G.hs.A G.hs (G.994.1) facility in G.vdsl should also study the time-division-duplexing necessary forinteroperability with the Annex Cs of both the G.992.1 and G.992.2 ADSL standards. MA-067and MA-077 propose that G.vdsl use G.994.1 as its initialization method. Nortel expressed theopinion that the group should not take this decision, as ETSI had not yet expressed its supportfor this concept. It was finally decided to accept the proposals in MA-067 and MA-077, as theywere in line with the early decision to use G.994.1 in all new xDSL Recommendations.
There was considerable discussion over the duplexing scheme to be used. Japan requires TDDand Europe strongly prefers FDD. In the end no decision was reached. After a very protracteddiscussion, an agreement to have a programmable PSD mask, as a goal, was reached. It wasagreed to have a goal to address compatibility with home networks (e.g. HomePNA). In responseto several papers, it was decided to defer any discussion of line code until the next meeting.However, the line code was discussed indirectly through discussions on many of the papers. Acase in point was challenges raised to the complexity issues addressed in MA-056 and MA-063.
There was no resolution to these discussions. In response to Nortel’s MA-070, AM Radio ingresswas added to the list of interferers. The requirement for upstream power control was accepted.Open issues were added to the list relating to studying the possibility of developing a family ofspectrally compatible modems raised in MA-057.
G.995.1 (G.REF)
MA-004 is G.995.1 (S. Abbas, Centillium, Editor) as submitted to the ITU. See also MA-054,presented under G.shdsl.
G.966.1 (G.TEST)
MA-010 (M. Tzannes) is the text of draft Recommendation G.966.1 that was sent to the TSB.
MA-082 (L. Humphrey, Nortel) proposes adding the issue of AM ingress noise described underG.gen.bis MA-070 to the G.lite.bis issues list This was agreed. The G.996.1 issues list wasclosed at the ending meeting.
Dick Brandt, dB Consulting
Q4/15 RAPPORTEURS GROUP ROSTER, MARCH 29 - APRIL 2,1999, MELBOURNE, AUSTRALIA
Dick Stuart, 3Com Q4/15 RapporteurHost: Ericsson Australia
REPORT OF TR-30, DATA TRANSMISSION SYSTEMS AND EQUIPMENT,APRIL 12 - 14, 1999, SAN JOSE, CA
TR-30.1, MODEMS
SG16 LIAISONS
TR-30.1/99-04-008, a liaison from SG8 to SG16 (SG8 TD-0125rev1, A. Pugh, Panasonic),addresses an issue with half-duplex fax operation when using V.34. V.34 (section 11.1.2.1)indicates that the transmission of ANSam with phase reversals as specified in V.8 is optional ifhalf duplex mode is intended. Field trials/tests have shown that on connections with network echocancellers, if the no-phase reversal option is used for V.34 half-duplex communications, then thereis a high incidence of connection failures during the V.8 negotiation phase. The perceived causefor these failures is the network echo-cancellers training upon the double-talk of the CM portion ofV.8. The effect is to suppress the 1650 Hz and hence corrupt the communications. It is therecommendation of Q1/8 that V.34 be amended to be like duplex mode and mandate the use ofphase reversals.
TR-30.1/99-04-009 (SG8 TD-0164rev2, A. Pugh, Panasonic) is a liaison from SG8 to SG16addressing revisions of T.35 to include the expansion of the country code and terminal providercode (manufacturer code). It also offers clarification on related T.35 issues. It was brieflyreviewed.
FCC REQUEST
TR-30.1/99-04-010 (F. Lucas, 3Com) is the request from the FCC (Docket 98-163) to TIA fortesting to aid the FCC in their decision about relaxing the level of the encoded digital signalcontent for PCM modems. The FCC is encouraging TIA members to complete this testing in onemonth. F. Lucas (3Com) highlighted the possibility of an assessment to cover the cost of thetesting. Technical editor’s note: ATIS reported that it will be funding the PCM testing completely.They are presently negotiating with Telcordia (Bellcore) to actually conduct the tests. Equipmentfor testing is still required.
WITHDRAWAL OF IS-63
TR-30.1 approved the withdrawal of IS-63, “Automatic Interworking Between Automode Modemsand Modems Conforming to Recommendations V.32, V.22bis and V.22.”
TR-30.1/99-006 (L. Brown, Motorola, TR-30.1 chair) proposes a USA position paper to SG16supporting the continuation of work on V.90 Issue 2. Conexant noted that this didn’t seemappropriate when there did not appear to be any US companies contributing to this work. IBMand AMD expressed support for Conexant’s position; consequently there was no consensus forthis proposal. 3Com and Motorola indicated that they would submit this contribution as a multi-company paper.
F. Lucas (3Com) verbally presented a 3Com proposal for a change to the V.91 start up sequence.3Com proposes to turn on the scrambler before the PHIL and J sequences to prevent them frombeing incorrectly detected as tones. It was decided to discuss this by email prior to the US SG Dmeeting with the goal of arriving at a proposed USA position by then.
DATA COMPRESSION
TR-30.1/99-02-004R1 (J. Heath, Hughes Network Systems) proposes the initiation of work for anew Recommendation for data compression. A description of the LZH (Lempel-Ziv-Welch)algorithm and simulation results were provided. An earlier version of this paper had been
presented at the Dana Point TR-30.1 meeting in February (as TR-30.1/99-02-004). This will besubmitted as a company contribution to the May SG16 meeting in Santiago.
Dick Brandt, dB Consulting
TR-30.2, DATA TRANSMISSION
TR-30.2/99-04-008 is a copy of a letter which TIA had received from the Federal CommunicationsCommission (FCC) regarding testing of crosstalk in local loops for V.90 modems. This waspresented in TR-30.2 for information. (See TR-30.1 report for additional information.)
REAFFIRMATION OF TIA/EIA-612 AND TIA/EIA-613
F. Lucas (TR-30.2 Chair) announced that the ballots for the reaffirmation of TIA/EIA-612 (SP-4394), “Electrical Characteristics for an Interface at Data Signaling Rates Up to 52 Mbit/s” andTIA/EIA-612 (SP-4395), “High Speed Serial Interface for Data Terminal Equipment and DataCircuit Terminating Equipment”, had closed February 22. There were no negative ballots norballots with comments. As a result, both standards have been reaffirmed.
ITU-T STUDY GROUP 16
The next ITU-T Study Group 16 meeting is scheduled for May 18-28 in Santiago, Chile. The USDepartment of State will be holding a Study Group D meeting on Wednesday, April 21 toreview/approve contributions to the SG16 meeting. Study Group 16 will again be looking at amajor revision of Recommendation V.24. F. Lucas (TR-30.2 Chair) indicated that he did notknow what will become of the draft Recommendation V.25I which addresses an AT command setfor ISDN Terminal Adapters. The editor of this work, J. Moughton, is no longer able to continuein that position and the work may terminate. The exact status of that work will not be knownuntil after the Study Group 16 meeting.
REVISION OF TIA/EIA-334-B
TR-30.2 has undertaken a new project to revise TIA/EIA-334-B, “Signal Quality at Interfacebetween Data Terminal Equipment and Synchronous Data Circuit-Terminating Equipment forSerial Data Transmission.” Although Project Number PN-4540 has been assigned to this work,F. Lucas indicated that, acting as editor for this project, he was not yet ready to provide TR-30.2with suggested changes to the standard. Approximately five years ago, the standard wasrevised to “simplify” the timing diagrams. This appears to have left the users of this standardwith a good deal of confusion as to how to interpret these diagrams. The task at this revision willbe to return to diagrams similar to those in the -A revision of the standard. In addition,references to three additional TIA standards, which have been approved since the last revision ofTIA/EIA-334, will be included:
• TIA/EIA-687, Medium Speed Interface for Data Terminal Equipment and Data Circuit-Terminating Equipment
• TIA/EIA-723, High Speed 232 Type DTE/DCE Interface• TIA/EIA-694, Electrical Characteristics for an Unbalanced Digital Interface for Data
Signaling Rates Up to 512 kbit/s
REVISION OF ITU-T RECOMMENDATION V.250
At the February 1999 meeting, TR-30.2 approved the concept of a contribution to Study Group16 regarding inclusion of a general V.250 command in support of the emerging V.mmo ModemManaged Object Recommendation. At this meeting, TR-30.2 approved a contribution (TR-30.2/99-04-006) to Study Group 16 which asks that a command similar to the +UD command,which is used in the Microsoft Unimodem Specification, be included in the V.250 command set.This work will take place under Question 7/16, however it will not get fully underway untilQuestion 4/16 has progressed further with Recommendation V.mmo.
TR-30.2/99-04-007, Proposed Amendments to the +WS46= command of TIA-678 and its inclusionin ITU-T Recommendation V.250 (F. Farazmandnia, Conexant), points out the need to include
additional code points in TIA/EIA-678 in support of the Infrared Data Association Specificationfor Ir Mobile Communications (+WS46 codes 18-22). The WS46 extended syntax command isused to select and indicate the Wireless Data Service (WDS) side stack, which comprises both aWDS type and DCE WDS communications protocol. TR-30.2 agreed to open a new project torevise TIA/EIA-678. It also was agreed that this would be the first revision suggestion to beconsidered. The Chair indicated that in reviewing the V.250 Supplement, he finds that the+WS46 command seems to have been omitted. He indicated that, as Rapporteur for Question7/16, he would discuss this at the Q7/16 sessions in May.
UNIVERSAL SERIAL BUS
TR-30.2 had expected to receive a contribution from TIA TR-29 regarding the need for mappingof TIA/EIA-232 interchange circuits into the Universal Serial Bus (USB). Unfortunately, thiscontribution did not appear. Once again, TR-30.2 discussed the advantages of a standard whichlooks like the USB and which would give USB legitimacy in the standards world. There is a gooddeal of support for work on such a standard which does not infringe on the IPR rights of thecompanies which own the USB specification.
TIA/EIA-644 FUTURE REVISION
At the February meeting, TR-30.2 had agreed to open a new project to revise TIA/EIA-644,Electrical Characteristics of Low Voltage Differential Signaling (LVDS) Interface Circuits, toaddress Multidrop operation. The Chair indicated that he had not yet opened that project,although work could continue on it; he needs anticipated completion dates from the TR-30.2.1 adhoc group. Unfortunately, no members of the ad hoc group were in attendance; the Chair willcontact J. Goldie (National Semiconductor), the ad hoc chair, to obtain the required information.
Fred Lucas, 3Com
TR-30.3, DATA COMMUNICATIONS EQUIPMENT EVALUATION AND NETWORK INTERFACES
TR-30.3/99-02-02R1 is the Revised Assignment list from November 1998 TR-30.3 meeting. TR-30.3/99-04-39 is the Assignment list from February TR-30.3 meeting.
TR-30.3/99-04-49A (J. Cookman, ESS Technology) is e-mail concerning ESS’s TR-30.3membership. ESS would like to be added to the Member List.
TR-30.3/99-04-49B (S. Satchell, Satchell Evaluations) is e-mail requesting that SatchellEvaluations be reinstated as a TR-30.3 member.
S. Satchell will bring a CD of meeting documents for distribution at each meeting. J. Douglass(Oak Technology) will post the document list in each folder on the ftp site.
FCC LIAISON
TR-30.3/99-04-060 is a letter from the FCC to TIA concerning Modifications to Signal PowerLimitations Contained in Part 68 of the Commission’s Rules. F. Lucas (3Com) reviewed the FCCV.90 Testing status. TIA is still trying to determine a method to pay for the costs of running thetests. The T1A1.7 tests will be used. In TR-30.3/99-04-060, the FCC requested that everythingbe complete within 30 days. (See the TR-30.1 report for additional information.)
P. Kyees (Paradyne) and F. Lucas (3Com) reported on the FCC meeting where they discussedacceptable technology for xDSL. The criteria for FCC acceptable technology are the T1 mask ortechnology that has been deployed by at least one carrier or recommended by a standards body.T1E1.4 will develop the T1 Mask. The process should be neutral. The FCC will complete thework on spectrum management within one year.
SP-3459, REVISING TSB-37A (TELEPHONE NETWORK TRANSMISSION MODEL FOR EVALUATING MODEMPERFORMANCE)
TR-30.3/99-04-018H-J are ballot comments on SP-3459-1, Revising TSB-37A (TelephoneNetwork Transmission Model for Evaluating Modem Performance). All votes were “yes” or no
comment. SP-3459-1 was approved for release as ANSI/TIA/EIA-3700. This project is nowclosed.
TR-30.3 will forward this document to TR-30 for submission to SG D as a proposed UScontribution to SG16 Q10. It is being submitted as a proposed revision to V.56.
PN-3509, REVISION OF TSB-38 (TEST PROCEDURES FOR EVALUATING MODEM PERFORMANCE), ANDPN-3856, TEST PROCEDURES FOR EVALUATING PCM-MODEM PERFORMANCE
TR-30.3/99-04-036 (S. Satchell, Satchell evaluations, Editor) is Draft 8 of PN-3509, Revision ofTSB-38 (Test Procedures for Evaluating Modem Performance).
TR-30.3/99-04-046 (C. Mellon, Conexant) provides technical and editorial comments on PN-3509Draft 8.
It was agreed that a method needs to be developed to better relate which test procedures areassociated with each network model. A table that identifies test procedures and the associatedapplication also needs to be developed.
It was agreed to forward Draft 8 of PN-3509 with the agreed changes to the ITU SG16 Q10 forinformation.
PN-3857, NORTH AMERICAN TELEPHONE NETWORK TRANSMISSION MODEL FOR EVALUATING ANALOGCLIENT AND DIGITALLY CONNECTED SERVER MODEMS
TR-30.3/99-04-056, PN-3857 Draft 11 was submitted by editor G. Hillman. It was agreed tochange the title of PN-3857 to North American Telephone Network Transmission Model forEvaluating Analog Client and Digitally Connected Server Modems. It was agreed that Draft 11be forwarded to SG16 Q10 for information.
TR-30.3/99-04-045 (R. Perez, Telcordia) is a Proposed Annex F: Impairments Understudy in theTelephone Network, for PN-3857 Draft 11. This proposed annex provides RBS (Robbed bitsignaling) impairments that are known to be in the IDLC (Integrated Digital Loop Carrier)section of the PSTN as well as in the digital PBX but are in such limited deployment that they arenot considered for inclusion in the main document. It was accepted as an annex for Draft 12.
TR-30.3/99-04-048 (N. King, Siemens) provides typographical ballot comments on PN-3857(Draft 10).
TR-30.3/99-04-052 is e-mail from E. Schulz (Lucent) to R. Perez (Telcordia) and J. Douglass (OakTechnology) concerning types and percentages of End Office Switches, and LOO numbers in thenetwork model. This is derived from SP-OPT-001839 NPA/NXX Active code list which provides alisting of the number/percentage of exchanges in North America using each type of switch(described by a three character code which is not defined-some are self evident). TR-30.3 felt thatit wasn’t worth the effort to recalculate the LOOs to the resolution given in TR-30.3/99-04-052. Itwas felt that the LOOs would not significantly change. J. Douglass (Oak Technology) will contactE. Schultz (Lucent) to find out if he is willing to submit a contribution based on TR-30.3/99-04-052 that would recommend new LOOs.
JOINT MEETING WITH T1E1.4 XDSL MODEM PERFORMANCE EVALUATION AD HOC
A block of document numbers starting at 600 was set aside for PN-4254 and PN-4255. T1E1.4will use the same numbers as TR-30.3 for documents addressing these projects. The documentswill be posted on both FTP sites. The T1E1 site is at www.T1.org.
TR-30.3/99-04-602R2, Project definition for T1E1.4 xDSL Modem Performance Evaluation AdHoc, was submitted by L. Brown (Motorola). TR-30.3/99-04-610 (L. Brown, Motorola) is theReport of the T1E1.4 xDSL Modem Performance Evaluation Ad Hoc Meeting on March 8-9,1999.
TR-30.3/99-04-612 is e-mail to K. Moreland (Chair ADSL Forum) from D. Brandt (Motorola)requesting formal liaison between TR-30.3 and the ADSL Forum.
TR-30.3/99-04-616 is a Liaison Letter to TR-30 from the ADSL Forum (G. Young, Chair ADSLforum Technical Committee) Testing & Interoperability Working Group (TIWG). TR-30.3/99-04-613 (R. Hamdi, Compaq Computers) is a proposed liaison response. It provides descriptions andcurrent status of TR-30.3 xDSL performance evaluation testing projects. R. Hamdi (CompaqComputers) noted separately that he will not be able to continue as the ADSL forum liaison. J.Douglass will contact Paradyne to determine if they will be the TR-30.3 liaison to the ADSLforum.
L. Brown (Motorola) will generate a T1E1.4 joint meeting report using the sections on PN-4254and PN-4255 from J. Douglass’ (Oak Technology) meeting report (see below). The next jointmeeting (hosted by T1E1) will be on June 7-8 in Ottawa, Ontario, Canada.
PN-4254, TELEPHONE NETWORK TRANSMISSION MODEL FOR EVALUATION XDSL SYSTEMS ANDPN-4255, TEST PROCEDURES FOR EVALUATING XDSL SYSTEM PERFORMANCE
TR-30.3/99-04-601R3 (P. Kyees, Paradyne, editor) is PN-4254 Draft 3, Network AccessTransmission Model for Evaluating xDSL Modem Performance.
TR-30.3/99-04-611, ETSI STC TM6 - Performance tests for SDSL and other long range xDSLsystems, was submitted for information. It is ETSI STC TM6 Permanent Document TM6(98)10;its goal is to keep tract of the various proposals in ETSI TM6 on performance tests for SDSL.
TR-30.3/99-04-614 (J. P. Houdard, Texas Instruments) provides Impairment Combinationstables, test loops, and Network Model Coverage scores for most of the types of xDSLcommunication systems that are deployed on today’s telephone network.
TR-30.3/99-04-615, Crosstalk Model for binder of 25 wire pairs (J. P. Houdard, TexasInstruments), defines the way to generate crosstalk signals that must be considered forevaluating any xDSL communications system. Spectrum characteristics of crosstalk noise aredirectly related to other xDSL systems which are present in the same cable. Two signalgenerators inject crosstalk noise at both ends of the test loop to simulate realistic disturbers thataffect xDSL signals in both directions (upstream and downstream).
TR-30.3/99-04-617 (G. Bremer, Paradyne) is a proposal to include all guarded services in testingdocuments. Guarded service refers to loop technologies expected to exist in the installed base, asidentified by T1E1.4 in their spectrum management standard under development. PowerSpectral Density of guarded services should be included in the network model. It was agreed toadd the services listed to the list of services in Annex E of draft 3 of PN-4254 as potential noisesources.
TR-30.3/99-04-618, DDS PSDs and Proposal for Generating DDS NEXT (G. Bremer, Paradyne),identifies DDS transmit PSDs via both measurements of DDS signals and via authoritativereference (Subscriber Loop Signaling and Transmission, Whitham D. Reeve Editor, 1995, IEEEPress, provides a theoretical definition of DDS PSD). Examples from TR-30.3/99-04-618 will beplaced in Annex E of PN-4254. Text will also be placed in Annex E. Validation of PSD examplesgiven in the Appendix of TR-30.3/99-04-618 are requested from Telcordia and othermanufacturers. R. Perez (Telcordia) agreed to research the information about secondary channelDDS and do a sanity check on the information presented.
It was agreed that the crosstalk generator cannot be a simple white noise generator. It needs tobe a flexible, complex signal generator that is able to simulate single or multiple disturbingsignals.
TR-30.3/99-04-619, Data-Dependent T1 PSDs and Proposal for Correctly Generating T1 NEXT(G. Bremer, Paradyne), provides figures showing actual Y1 transmit PSD measurements madeduring transmission of practical user data sequences. It was agreed to place text and examplesfrom this contribution in Annex E of PN-4254. Validation of PSD examples given in the Appendixof TR-30.3/99-04-619 are requested from Telcordia and other manufacturers.
TR-30.3/99-04-620, Non-Continuous Events in the Telephone Outside Plant (R. Brown, AGCommunication Systems/Lucent), characterizes three ubiquitous, non-continuous POTS events
(ringing, supervision and dial pulse) that have not been shown to be detrimental to servicesshared within the binder. This is in response to recent submissions to T1E1.4 which suggest thatnon-continuous events, such as power variances, can be detrimental to services shared within thebinder.
P. Kyees (Paradyne), R. Perez (Telcordia), J.P. Houdard (TI), and J. Roquet (ILEC) will draft aninitial set of ranges for impairment combinations and consider additional impairments that needto be added to the list. They will also generate a loop model. Information from TR-30.3/99-04-620 will be considered in the impairments that are generated.
Paradyne will provide a contribution on the types of drop wire, their distribution, andcharacteristics. A rationale for selecting a single pair will be derived from this information.
TR-30.3/99-04-600R1 (L. Brown, Motorola) is the Issues List for the xDSL Transmission ModelProject. L. Brown (Motorola) and J. Douglass (Oak Technology) will generate a document list andassignment list.
PN-4256 REVISION OF TIA/EIA-496-A, INTERFACE BETWEEN DCE AND THE PSTN
R. Perez (Telcordia) will post PN-4256 before the next meeting so that TR-30.3 can review itbefore it is sent out for ballot. It must be released for ballot before the next meeting, so that theballot cycle will be completed before September. If TIA/EIA-496-A is not revised or re-affirmedby September, it will be discontinued.
PN-4514, NORTH AMERICAN TELEPHONE NETWORK TRANSMISSION MODEL FOR EVALUATING V.91MODEMS
M. Pellegrini (TAS) will be editor for PN-4514, North American Telephone Network TransmissionModel for Evaluating V.91 Modems. He will provide the first draft at the next meeting.
Jack Douglass, Oak Technology
The next issue of Communications Standards Review - Telecommunications (Vol. 10 #5) isscheduled for June-July 1999.
TR-30 MEETING ROSTER, APRIL 12 - 14, 1999, SAN JOSE, CA
Dick Brandt, Motorola TR-30 ChairLes Brown, Motorola TR-30.1 ChairFred Lucas, 3Com TR-30.2 ChairJack Douglass, Oak Technology TR-30.3 ChairHost: PC Tel
3Com Fred LucasACTION Consulting Ken KrechmerAG Comm. Systems Scott BaerAMD Terry ColeAnalog Devices Josh KablotskyAscend Comm. Ken JonesAscend Comm. Brendan NeutraComm. Stds Review Elaine BaskinCompaq Computer Rabah HamdiCompaq Computer Larry LyleConexant Systems Stan BaconConexant Systems Keith ChuConexant Systems Farshid FarazmandniaConexant Systems Joe HoangConexant Systems Craig MellonCSI Telecom Bill BuckleyEicon Claude TremblyESS Technology Wai Ying (Peter) KanFloreat Earl GibsonGAO Research Alan MarionHenderson Labs Warren HendersonHughes Networks Jeff HeathIBM Ali SadriInfineon (Seimens) Arndt PauschardtLucent Technologies Jingdong LinMediagate Mendal AiznerMotorola Dick BrandtMotorola Les BrownMotorola Bruce GieseMulti-Tech Systems Sam GopalanNortel Networks Slabodon JovanovicOak Technology Jack DouglassParadyne Gordon BremerParadyne Philip KyeesPC Tel Gary AnwylPC Tel Enrico CadorinPC Tel Di ZhouRaychem Al MartinSatchell Evaluations Stephen SatchellSBC TRI Afshin ShaybaniSignals & Software Bruce AdamsTAS Mike PellegriniTelcordia (Bellcore) Ricardo PerezTI Jean-Pierre HoudardTrisignal Comm. Jean BelleauW. E. Martin Cons. Wayne MartinXircom Phil HoppeZD Labs David Bardes
REPORT OF TR-41.3.4 INTERIM MEETING, APRIL 19 - 20, 1999,VANCOUVER, BC
Members were asked if they were aware of any intellectual property the use of which might beessential to the work being considered by TR-41.3.4. No members responded.
PN-4462 PERFORMANCE AND INTEROPERABILITY REQUIREMENTS FOR VOIP TELEPHONETERMINALS
The primary goal of this working group is to produce a set of performance and interoperabilityrequirements for VoIP telephones that allow for adequate product innovation. To satisfy thisgoal, TR-41.3.4 will specify certain capabilities that telephones must have. By specifyingcapability requirements, the onus is on the telephone manufacturer to determine how thecapabilities are implemented, thus allowing the freedom to innovate.
PRESENTATIONS ON MEGACO
N. Greene (Nortel Networks) gave a presentation of the current activities of the IETF Megacoworking group. It was agreed that a formal liaison should be established between TR-41.3.4 andMegaco.
Note: Anyone can subscribe to the Megaco mailing list by sending a message [email protected] with “subscribe megaco” in the message body.
P. Blatherwick (Nortel Networks) presented an excellent overview of the new Megaco proposedstandard and showed how VoIP telephones could be represented in the Megaco telephony model.The proposed Megaco protocol defines two elements: terminations and contexts. A context is acontainer of one or more terminations while a termination identifies a media flow or resource.Contexts may support only a single media type and serve to “mix” that media, at least in the caseof audio. Terminations have certain properties, such as class, state, and capabilities.Termination classes provide a way to refer to a reusable set of capabilities that give atermination default parameters. Termination capabilities are defined by packages which groupevents and commands. Finally, termination state allows terminations to keep state informationsuch as directionality, handling of accumulated events, and other information beyond mediadescriptors.
P. Blatherwick’s proposed IP telephone model defines a Megaco telephone as a set ofterminations. The audio terminations specify resources such as the handset and speakerphoneand are grouped into a context. Other terminations model resources such as display, soft keys,and indicators and are not part of a context. To implement this proposed model, TR-41.3.4 mustdefine new termination classes for each resource in the model. A set of packages defining eventsand signals for each resource combined with the class definitions would be submitted to theMegaco WG for inclusion into the Megaco standard.
The group agreed to go ahead with the definition of the Megaco IP telephone model, recognizingthat Megaco still faces many uncertainties before standardization.
POWERING
P. Holland (Circa Communications) gave a presentation of a proposed method for powering VoIPtelephones over existing Ethernet cables. The method is based on existing standards that usepins 7 & 8 to carry power to the terminal.
Many older wiring installations run two-pair wiring; thus, it is impossible to use the proposedpowering method on those older networks. It was suggested that a method of powering that putspower directly on the Ethernet data lines (phantom powering) be used instead. The trade off withphantom powering is that it requires relatively costly transformers to be in place in networkequipment. Consensus was that the group should investigate phantom powering further.
R. Shaaf (Pingtel Corp.) reported that IEEE 802.3 working is developing a powering standardfor Ethernet wiring. IEEE 802.3’s powering work, however, is proceeding slowly and may not beready in time for PN-4462.
The group discussed powering methods and came to consensus that while network powering isadvantageous when available, it should not be made a mandatory requirement.
CONTRIBUTIONS TO MEGACO
The group decided to begin work on P. Blatherwick’s IP telephone model.
Audio Terminations
Audio terminations in the Megaco IP telephone model are grouped into a context, the purpose ofwhich is to mix the audio signals. For example, a handset is modeled in Figure 1.
Speaker
Micr ophone
T1
T2
T3
RTP
Figure 1. Audio termination context.
In Figure 1, T1 is the termination that communicates an audio stream with the network.Termination T3 receives audio from the microphone while T2 sends it to the speaker.
In a business telephone, additional terminations would need to be specified to accommodate thespeakerphone and headset. Some members were concerned that the context model allows mixingto occur when it is inappropriate. For example, if the speakerphone speaker is muted, whatguarantee is there that the microphone is not also muted, as would be expected by the telephoneuser? A possible solution is to have an indicator light show when the microphone is enabled.
Display
The provisioning of a display was deemed by the group as essential for many business telephoneapplications, such as access to special network services. Therefore, the display termination wasidentified as something the group must specify, regardless of whether displays are mademandatory in the final standard.
The group focused on several areas of concern relating to the display, including:
• Resolution,• Character sets• Graphics capability
The specification of display requirements is difficult because displays typically vary greatly incapability. For example, two telephones conforming to the same network standards may containvastly different displays - one may be a high resolution color graphics display while the other is atwo line by sixteen character black and white text display. Because of the variability in possibledisplay configurations, the group decided to keep the initial display requirements as simple aspossible. Requirements for complex graphic displays may be formulated later if necessary.
The first consensus reached by the group was that there may be zero or more displays. Eachdisplay must be able to present at least two lines of sixteen characters each - the two lines maybe in any physical configuration and must understand how to process carriage return and linefeed characters. Auditing methods will be defined so that the media gateway controller can
determine how many displays exist in the telephone and what characteristics each of the displayshave. Commands will be defined so that the media gateway controller can write to any part ofthe display.
An important factor in the setting of display requirements is the specification of what characterscan be presented on the display. The group decided that, in the interests of internationalization,telephones shall indicate which Unicode code pages they support on each display. Consensus wasnot reached on a minimum code page requirement, although GSM ASCII and US ASCII werepresented as possibilities.
Soft Keys
Soft keys present a special challenge compared with normal keys because their function must bedynamically indicated to the user. Commonly, soft keys are arranged along the edges of thedisplay. When a soft key is active, its function is indicated on the display in a location adjacent tothe soft key (Figure 2).
H arold Sm ith:1:15
H old Xfer Park
Soft key
Figure 2. Example of soft keys.
Because soft keys often have a close relationship with the display, the group decided that softkeys should be considered when the display termination is defined. The group also decided thatsoft keys should be in a different class than regular keys because their function is dynamic.
Keys
While basic “black telephones” require only a small set of keys with fixed functions, businesstelephones often provide a rich set of keys, the functions of which may be variable. Sometelephones do not have keys, such as taxi telephones.
The group identified a number of issues that must be resolved before key terminations can bedefined. Among other things,
• Are keys named?- “Hold,” “Release,” etc.- Can keys be renamed?
• Are all keys “created equal,” i.e., are some keys fixed in function while others are variable?• Is the hook switch a key?• How are key press events generated, and what is reported?
Dial Pad
The dial pad (keys labeled 0-9, #, and *) must be considered specially in the Megaco modelbecause dialed telephone digit strings may be sent “en bloc” to the media gateway controller, as
opposed to digit-by-digit. Furthermore, pressing a dial pad key must immediately produce atone, light a lamp, or produce some other indication to provide adequate feedback to the user.
One of the problems with generating tones or other indications when dialing is that there aresituations in which producing dial pad feedback is not desirable. For example, when thetelephone is on-hook, dial pad feedback must not occur. Also, the type of feedback to be suppliedmay differ depending on the call state in the media gateway controller. For instance, whengenerating tones during a call to a country in which different dialing tones are used (i.e., otherthan DTMF), the dial pad feedback may have to be adjusted to correctly indicate the kind of tonesbeing generated on behalf of the telephone at the other end of the RTP media stream.
When a call is in progress, the usual tones (i.e., DTMF) sent by the telephone to the remote end ofthe conversation are sent out-of-band of the media stream as many audio codecs are not capableof carrying such tones. The out-of-band tone data is sent in special RTP packets alongside theaudio information. However, a problem arises in the Megaco model. Because the telephone doesnot have any concept of call state, it has no way of knowing whether it should transmit dial padkey press indications to the media gateway controller. In effect, when a call is in progress, thedial pad events are sent unnecessarily to the media gateway controller, where they arediscarded. Without the telephone storing extra state, this wasteful procedure is unfortunatelyunavoidable. Because there is no easy solution to the problem, the group agreed that dial padevents should still be generated and sent to the media gateway controller, even when a call isunderway.
Protocol issues aside, the group did agree that a dial pad should be an optional component as it isnot strictly necessary in all telephones.
Hook Switch
Telephones that have a handset must have a hook switch to indicate when the user is using thehandset. A hook switch is similar to a regular key because it is always in one of two states;however, a hook switch, unlike a key, is frequently engaged in one state or the other for a longperiod of time. The timing logic that generates the length of a key press may not be capable ofdetermining how long the hook switch has been engaged (i.e., the timer may overflow).
Some members indicated that hook switch timing was only necessary to determine whether theuser has performed a hook flash. Since hook flash is unnecessary in IP telephones, they viewedthe timer overflow issue as fairly moot. Therefore, the group agreed that the hook switch shouldbe represented as an ordinary key, unless it can be demonstrated that making a separate hookswitch class does not cause any additional complexity in the standard.
Indicators
Many feature telephones on the market provide indicator lights or icons to show when the userhas a voice mail message waiting or when a certain line is selected. Because indicators mayconsist of almost anything, from lights to display elements to audible alarms, it was agreed thattheir specification should mandate function rather than form.
Indications are produced in response to a wide variety of events. One important indication occurswhen the telephone “rings.” Because many systems provide distinctive ringing to differentiate thesource of a call, it was agreed that indications should be customizable. What form thecustomization takes was left for further study; however, examples such as cadence patterns andtone specifications were considered. In order that indication customization be flexible enoughover the range of possible indicator types, it was agreed that indicators should be classed asaudible, visual, or some other type.
Making the Contribution to Megaco
There was discussion as to how this group’s contribution should be given to the Megaco workinggroup. It was agreed that TR-41.3.4 should use its mailing list initially to craft the contribution.When the contribution is ready, it will be forwarded to the Megaco mailing list and identified asrepresentative of the opinions of TR-41.3.4.
P. Blatherwick (Nortel Networks) and B. Bell (Cisco) reviewed the Handset Emulation Packageas described in the Megaco proposed standard. The handset emulation package provides anexample of the sort of package TR-41.3.4 will be specifying for business IP telephones.
SECURITY
Security is extremely important in IP networks as traffic may be inspected en route from sourceto destination by a variety of devices, not all of which may be trusted. Protocols that do not allowfor adequate encryption and authentication of sensitive information have shown time and againthe need for such mechanisms by placing their users in unfortunate legal, moral, or othersituations. Telephone network traffic is especially sensitive as users presently have theassumption of privacy when using the telephone.
However, the provision of security is not without significant challenges. Encryption can beprocessor-intensive and there are a universe of possible encryption algorithms to consider.Furthermore, encryption algorithms are frequently patented. In some countries, encryption iseven outlawed.
The group agreed that security is essential in many networks where IP telephones will beinstalled. What needs to be examined is the level of security that is reasonable and the areas inwhich security must be applied.
SIP
R. Shaaf (Pingtel Corp.) gave an excellent presentation on the status and directions of IETFSession Initiation Protocol (SIP). His presentation used slides from Henning Schulzrinne’s speechat this year’s VON conference. Dr. Schulzrinne’s web site ishttp://www.cs.columbia.edu/~hgs/sip.
The consensus was that SIP should be included in the proposed standard and that the requiredsections would be developed via the mailing list in preparation for the May TR-41.3.4 meeting inPortland.
DISCOVERY MECHANISM
Because PN-4462 telephones may run either SIP or Megaco as their call control or device controlprotocols, the group recognized that a method of determining which protocol should be used in aparticular network must be formulated as telephones may contain both protocols. The discoverymechanism allows a telephone to determine which services are available on the network andwhether a sufficient level of service is provided for the telephone to function correctly.
Table 1 shows the stages of network initiation that occur when a telephone is “powered up.” Therightmost columns indicate whether the technician or end-user must see indication of the events.Technician UI may be in the form of a change in the telephone’s memory readable only by adebugging port or a more easily accessible element such as a light-emitting diode.
Event Technician UI User UI1 Bring up the physical link (i.e. LED tells you the
network is present).Yes No
2 Bring up the network layer. DHCP has assigned an IPaddress. Indicate whether the network layer issuccessfully initialized.
Yes No
3 Application level registration. Indicate availability oftelephone service via a dial tone etc.
Megaco and SIP Choose Megaco Choose SIP Chooseeither
Choose SIP
Megaco Only Choose Megaco Don’t Care ChooseMegaco
Indicate Error -Controller not Found
SIP Only Don’t Care Choose SIP Choose SIP Choose SIP
Table 2. Determining What Service is Available.
Once the telephone has determined what sort of application level service is available, it mustdecide which to use. Table 2 describes which protocol telephones will use under variouscircumstances.
Ken Simpson, Simon Fraser Univ., Engineering Undergraduate Student Society
Phil Holland, Circa Communications TR-41.3.4 Chair
Circa Comm. Ltd. Scott DeeCirca Comm. Ltd. Phil HollandCirca Comm. Ltd. Chih-Jen (Ted) LuCirca Comm. Ltd. Sang Eel NamCisco Systems, Inc. Robert T. (Bob) BellCisco Systems, Inc. John CombsCisco Systems, Inc. Kirit D. PatelDialogic Corporation William E. JacobsGTE Network Svcs Harry Van ZandtHotHaus Tech. Inc. Craig HemsingHotHaus Tech. Inc. Wing YuHotHaus Tech. Inc. Michael AndersonNEC America, Inc. John StaffordNortel Networks Peter Blatherwick, MAScNortel Networks Nancy M. GreenePingtel Corporation Richard ShaafReltec Corporation David K. BrownSimon Fraser Univ., Ken Simpson
Eng. Undergraduate Student SocietyTelogy Networks Ed Morgan
3GPP Third Generation Partnership ProjectACF Authentication Control FunctionACTE Approvals Committee for Terminal EquipmentADLNB Association of Designated Laboratories and Notified Bodies (European)ADSL Asymmetric Digital Subscriber LineAM Amplitude ModulationAOC-E Advice Of Charge at the End of a callATA Analog Terminal and Access ProjectATAAB Analog Technical Ad hoc Advisory BoardATAc ATA’s Conventional Technology WGATM Asynchronous Transfer ModeATU-C ADSL Transceiver Unit - Central Office EndATU-R ADSL Transceiver Unit - Remote Terminal EndAWG American Wire GaugeBER Bit Error RateBES Back-End ServicesBEST Back-End Service TransactionBOF Birds of a FeatherBRI Basic Rate InterfaceCAP Carrier-less Amplitude Modulation Phase ModulationCDMA Code Division Multiple AccessCDPD Cellular Digital Packet DataCENELEC European Electrotechnical Stds Comm.CM Call MenuDBMS Data Base Management Systemdc Direct CurrentDCE Data Circuit Terminating EquipmentDCT Discrete Cosine TransformDDS Digital Data ServiceDECT Digital Enhanced Cordless Telecommunications (ETS 300 175)DMT Discrete Multi-tone CarrierDRC Direct-Routed-CallDSL Digital Subscriber LineDTA Digital Terminal and Access ProjectDTE Data Terminal EquipmentDTMF Dual Tone Multi FrequencyEDH Electronic Document HandlingEMC ElectroMagnetic CompatibilityEN European NormEOC Embedded Operations ChannelEP ETSI ProjectERM ETSI committee on EMC and Radio spectrum MattersES ETSI StandardETS European Telecommunications StandardETSI European Telecommunications Standards InstituteEURESCOM European Institute for Research and Strategic Studies in TelecommunicationsFCC Federal Communications Commission (U.S.)FEXT Far End Cross TalkFSAN Full Service Access NetworksGK GateKeeperGOB Group of Blocks (H.261, H.263)GR Generic RequirementsGRC Gatekeeper-Routed-CallGSM Global System for Mobile Communications (formerly Groupe Speciale Mobile)HDSL High-rate Digital Subscriber LoopHS Harmonized StandardsHTU-R Handshake Transceiver Unit - Remote Terminal EndIC Interexchange CarrierIDCT Inverted Discrete Cosine TransformIETF Internet Engineering Task ForceIMT International Mobile Telecommunications (IMT-2000)IMTC International Multimedia Teleconferencing Consortium
IN Intelligent NetworkingIP Internet ProtocolIPR Intellectual Property RightsISDN Integrated Services Digital NetworkISDN-BA ISDN basic accessISDN-PA ISDN primary accessISUP ISDN User PartITU-T ITU Telecommunications SectorJPEG Joint Photographics Expert GroupJTC Joint Technical CommitteeKTA Key Technical AreasLDAP Lightweight Directory Access ProtocolLOO Likelihood of OccurrenceLVDS Low Voltage Differential SignalingMDCP Media Device Control ProtocolMEGACO MEdia GAteway COntrolMGC Media Gateway ControllerMGCP Media Gateway Control ProtocolMIME Multipurpose Internet Mail ExtensionMPEG Motion Picture Experts GroupNEXT Near End Cross TalkOCG Operational Coordination Group (ETSI)OJEC Official Journal of the European CommunitiesONP Open Network ProvisionPAM Pulse Amplitude ModulationPBX Private Branch ExchangePCM Pulse Code ModulationPMC Packet Mode ChannelPMS Physical Media SpecificPOTS Plain Old Telephone ServicePPP Point-to-Point ProtocolPSD Power Spectral DensityPSNR Peak Signal to Noise RatioPSPDN Packet Switched Public Data NetworkPSTN Public Switched Telephone NetworkQAM Quadrature Amplitude ModulationQCIF Quarter CIFQoS Quality of ServiceQP Quantization Parameter (H.262)QSIG The signaling protocol used at the Q-interface between two switches in a private network.
ECMA/ISO have defined a set of QSIG standards.R&TTED Radio and TTE (Telecommunications Terminal Equipment) DirectiveRADSL Rate-Adapting ADSLRESCAP Resource Capabilities discoveryRFC Designation for an Internet StandardRTP Real Time Transport ProtocolSDH Synchronous Digital HierarchySDL Specification and Description LanguageSDSL Symmetrical high bit rate Digital Subscriber LineSDSS Server Display And Script ServicesSHDSL Single-line High Speed DSLSIGTRAN Signaling transportSMTP Simple Mail Transfer ProtocolSNR Signal to Noise RatioSS7 Signaling System 7STF Specialist Task ForceSTQ Speech Transmission QualityTAAB Technical Ad hoc Advisory BoardTB Technical BodyTBR Technical Basis for Regulation (ETSI standard)TC Technical CommitteeTCAM Telecommunication Conformity Assessment and Market Surveillance Committee (ETSI)TCM Time Compression MultiplexTDD Time Division Duplexing
TE Terminal Equipment (ETSI Committee)TETRA Trans European Trunked RAdioTG Task GroupTIA Telecommunications Industry AssociationTIPHON Telecommunications and Internet Protocol Harmonization Over Networks (ETSI Project)TIPIA TIPHON IP telephony Implementation AgreementTM Transmission and Multiplexing (ETSI Committee)TMN Test Model NumberTR Technical ReportTSB Telecommunications Standardization Board (ITU)TSB Telecommunications Systems Bulletin (TIA)TTT Trans European Network Telecom (TIPHON)UI User InterfaceUMTS Universal Mobile Telecommunications SystemUPT Universal Personal Telecommunications (CCITT)VDSL Very high speed ADSLVLC Variable Length CodewordVoIP Voice Over Internet ProtocolVON Voice on Network CoalitionVOP Video Object PlanesVQ Vector QuantizationVTR Video Tape RecorderWG Working GroupWWW World Wide Web (Internet)xDSL all the different Digital Subscriber Lines
YEAR 2000 STANDARDS COMMITTEE MEETING SCHEDULESAS OF APRIL 27, 1999
Subject to Change without Notice
Committee Date(s) LocationQ4/15 Rapp.* Jan 31-Feb 4 ---Study Group 16 Feb 7 - 18 Geneva, CHTR-41 February Maui, HIETSI TM6 Feb28-Mar 3 ---Q15/16 Rapp. April ---Study Group 15 Apr 3 - 14 Geneva, CHTR-41 May Washington, DCETSI TM6 May 22 - 26 ---Q15/16 Rapp. JulyTR-41 August Niagara Falls, OnETSI TM6 Sep 18 - 22 ---TR-41 November New Orleans LAStudy Group 16 November Geneva, CHETSI TM6 Nov27-Dec 1 ---
1999 STANDARDS COMMITTEE MEETING SCHEDULESAS OF APRIL 27, 1999
Subject to Change without Notice
Committee Date(s) LocationETSI ATAe WG May 3 - 6 Sophia Antip, FRETSI TIPHON13 May 3 - 7 Bangkok, THETSI TM6 May 3 - 7 Grenoble, FRTR-29 May 10 -12 East Coast USQ4/15 Rapp. May 10 - 14 Boston, MAT1E1.4 Interim May 17 - 18 Boston, MATR-41 and TR-42 May 17 - 21 Portland, ORITU-T SG16 May 18 - 28 Santiago, ChileT1E1 Jun 7 - 11 Ottawa, Ont.TR-30 Jun 14 - 17 Lake Tahoe, NVITU-T SG15 Jun 21-Jul 2 Geneva, CHTIPHON InterOp (with IMTC) Jun 21 - 25 Sophia Antip, FRETSI ATAc WG Jun 29 - 30 Sophia Antip, FRETSI TIPHON14 Jul 19 -23 Amsterdam, NLETSI DTA** Jul 20 - 21 Sophia Antip, FRQ4/15 Rapp.* Aug 2 - 6 Nuremberg, DE.Q11-15/16 Rapp. Aug 2 - 6 Berlin, DETR-29* Aug 9 - 11 West CoastTR-30 Aug 9 - 11 Quebec City, PQTR-41 and TR-42 Aug 16 - 20 Ottawa, OntT1E1 Aug 23 - 27 Baltimore, MDETSI TM6 Sep 20 - 24 Edinburgh, Scot.ETSI TIPHON15 Oct 4 - 8 Berlin, DETR-30 Oct 11 - 14 Baltimore, MDETSI ATA #7 Oct 11 - 15 Vienna, AustriaETSI DTA#6 Oct 26 - 28 Sophia Antip, FRQ11/16 Rapp. November ---Q15/16 Rapp. Nov-Dec ---Q4/15 Rapp.* Nov 1 - 5 New Orleans, LATR-41 and TR-42 Nov 8 - 12 Reno, NVTR-30 Nov29-Dec 2 Clearwater, FLETSI TM6 Nov29-Dec 3 Amsterdam, NLETSI TIPHON16 Dec 6 - 10 San Diego, CAT1E1 Dec 6 - 10 Clearwater, FL
* Proposed ** Resolution meeting
Visit the CSR Web Pages: http://www.csrstds.comThe Web Pages include an updated Telecom Acronym Definitions list, updated meeting schedules,a list of web sites and ftp sites as listed in all issues of CSR journals, background material ontelecom standards and CSR (the company), data sheets on both CSR technical journals, andmore.
BILL TO: SHIP TO: (Include Telephone)_________________________ _____________________________________________________ _____________________________________________________ _____________________________________________________ ____________________________
CSR provides to CSR subscribers copies of communications standardswork in process. Once standards are completed and available,
they should be acquired from the appropriate, authorized source.
Documents in addition to those listed in boldface in this issue of CSR mayalso be ordered. Please ask if we have what you are looking for.
Subscribers, Per Order North America Outside North America1st Document $50.00 $50.002nd Document $40.00 $40.003rd + Documents $25.00 $25.00Shipping 2nd day air included Invoiced at cost
