TIA-889-B-2012 TTY TDD Minimum Performance Specification (Includes Access to Additional Content)《TTY TDD最低性能规范》.pdf

1、 Access to Additional Content for TIA-889-B, Dated: March 2012 (Click here to view the publication) This Page is not part of the original publication This page has been added by IHS as a convenience to the user in order to provide access to additional content as authorized by the Copyright holder of

2、 this document Click the link(s) below to access the content and use normal procedures for downloading or opening the files. TIA-889-B SF TIA-889-B Software Files Information contained in the above is the property of the Copyright holder and all Notice of Disclaimer (b) there is no assurance that th

3、e Document will be approved by any Committee of TIA or any other body in its present or any other form; (c) the Document may be amended, modified or changed in the standards development or any editing process. The use or practice of contents of this Document may involve the use of intellectual prope

4、rty rights (“IPR”), including pending or issued patents, or copyrights, owned by one or more parties. TIA makes no search or investigation for IPR. When IPR consisting of patents and published pending patent applications are claimed and called to TIAs attention, a statement from the holder thereof i

5、s requested, all in accordance with the Manual. TIA takes no position with reference to, and disclaims any obligation to investigate or inquire into, the scope or validity of any claims of IPR. TIA will neither be a party to discussions of any licensing terms or conditions, which are instead left to

6、 the parties involved, nor will TIA opine or judge whether proposed licensing terms or conditions are reasonable or non-discriminatory. TIA does not warrant or represent that procedures or practices suggested or provided in the Manual have been complied with as respects the Document or its contents.

7、 If the Document contains one or more Normative References to a document published by another organization (“other SSO”) engaged in the formulation, development or publication of standards (whether designated as a standard, specification, recommendation or otherwise), whether such reference consists

8、 of mandatory, alternate or optional elements (as defined in the TIA Engineering Manual, 4thedition) then (i) TIA disclaims any duty or obligation to search or investigate the records of any other SSO for IPR or letters of assurance relating to any such Normative Reference; (ii) TIAs policy of encou

9、ragement of voluntary disclosure (see Engineering Manual Section 6.5.1) of Essential Patent(s) and published pending patent applications shall apply; and (iii) Information as to claims of IPR in the records or publications of the other SSO shall not constitute identification to TIA of a claim of Ess

10、ential Patent(s) or published pending patent applications. TIA does not enforce or monitor compliance with the contents of the Document. TIA does not certify, inspect, test or otherwise investigate products, designs or services or any claims of compliance with the contents of the Document. ALL WARRA

11、NTIES, EXPRESS OR IMPLIED, ARE DISCLAIMED, INCLUDING WITHOUT LIMITATION, ANY AND ALL WARRANTIES CONCERNING THE ACCURACY OF THE CONTENTS, ITS FITNESS OR APPROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, ITS MERCHANTABILITY AND ITS NONINFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL PROPERTY RIGHTS. TIA E

12、XPRESSLY DISCLAIMS ANY AND ALL RESPONSIBILITIES FOR THE ACCURACY OF THE CONTENTS AND MAKES NO REPRESENTATIONS OR WARRANTIES REGARDING THE CONTENTS COMPLIANCE WITH ANY APPLICABLE STATUTE, RULE OR REGULATION, OR THE SAFETY OR HEALTH EFFECTS OF THE CONTENTS OR ANY PRODUCT OR SERVICE REFERRED TO IN THE

13、DOCUMENT OR PRODUCED OR RENDERED TO COMPLY WITH THE CONTENTS. TIA SHALL NOT BE LIABLE FOR ANY AND ALL DAMAGES, DIRECT OR INDIRECT, ARISING FROM OR RELATING TO ANY USE OF THE CONTENTS CONTAINED HEREIN, INCLUDING WITHOUT LIMITATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES (IN

14、CLUDING DAMAGES FOR LOSS OF BUSINESS, LOSS OF PROFITS, LITIGATION, OR THE LIKE), WHETHER BASED UPON BREACH OF CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGATION OF DAMAGES IS A FUNDAMEN

15、TAL ELEMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. 3GPP2 C.S0028-B v1.0 Revision History Revision Date C.S0028-0 v1.0 CDMA TTY/TDD Minimum Performance Specification May 2001 C.S0028-0 v2.0 CDMA TTY/TDD Minimum Performance Specifi

16、cation Dec. 2001 C.S0028-A v1.0 TTY/TDD Minimum Performance Specification Jan. 2004 C.S0028-B v1.0 TTY/TDD Minimum Performance Specification May 2011 3GPP2 C.S0028-B v1.0 i Table of Contents 1 1 Introduction 1 2 1.1 Scope.1 3 1.2 Requirements Language1 4 1.3 References.1 5 1.3.1 Normative References

17、1 6 1.3.2 Informative References 2 7 2 The Baudot Code3 8 3 Character Error Rate.4 9 4 TTY/TDD Test Cases.5 10 4.1 Interoperability with Reference TTY Vocoder .5 11 4.2 Interoperability with Reference Non-TTY Capable Vocoder .5 12 4.3 Input Level 5 13 4.4 Bit Duration.5 14 4.5 Stop Bit5 15 4.6 Phase

18、 Changes.5 16 4.7 Frequency Deviations5 17 4.8 Typing Mode.5 18 4.9 Preamble6 19 4.10 Mark Hold Tone 6 20 4.11 Voice Carryover/ Hearing Carryover (VCO/HCO).6 21 4.12 Tandem 6 22 4.13 Variable Rates6 23 4.14 Reduced Rate Modes .6 24 4.15 False Alarms 7 25 4.16 Slew .7 26 4.17 Impaired Channels.7 27 4

19、.18 Worst Case Deviations 7 28 5 Test Tools.8 29 5.1 ttygen.8 30 5.2 ttyrcv .8 31 3GPP2 C.S0028-B v1.0 ii 6 TTY/TDD Test Procedure9 1 6.1 Description of Test Vectors.9 2 6.1.1 File Naming Convention9 3 6.2 Baudot Parameter Variation Test 10 4 6.3 Interoperability Test 14 5 6.4 Frame Error Handling T

20、est .14 6 6.5 Hard Handoff Test.14 7 6.6 False Alarm Test .15 8 6.7 Tandem Test15 9 6.8 Half-Rate Max Test.15 10 7 Requirements For Minimum Performance Compliance.17 11 7.1 Baudot Parameter Variation Test Requirements .17 12 7.2 Interoperability Test Requirements .17 13 7.3 Frame Error Handling Test

21、 Requirements 17 14 7.4 Hard Handoff Test Requirements .17 15 7.5 False Alarm Test Requirements 17 16 7.6 Tandem Test Requirements.17 17 7.7 Half-Rate Max Test and Additional Requirements for EVRC-B, EVRC-WB, and EVRC-NW 18 18 19 3GPP2 C.S0028-B v1.0 iii List of Tables Table 6-1: Description of TTY

22、PCM Test Vectors .11 1 2 3GPP2 C.S0028-B v1.0 iv FOREWORD 1 (This foreword is not part of this specification.) 2 This document specifies the minimum performance requirements and a test procedure for verifying solutions 3 for transporting the Baudot code over cdma2000 wireless networks using 3GPP2 13

23、K Vocoder, EVRC, SMV, 4 EVRC-B, EVRC-WB, and EVRC-NW, corresponding to Service Options 17, 3, 56, 68, 70, and 73, 5 respectively6 3GPP2 C.S0028-B v1.0 1 1 INTRODUCTION 1 1.1 Scope 2 Persons with hearing impairments or speech impediments are able to communicate over the telephone using 3 TTY/TDD (tel

24、etype/text telephone devices for the deaf), hereafter referred to as TTY devices. These devices 4 typically have a keyboard and a 2-line display, allowing a TTY user to type messages over the phone lines to 5 another TTY user. TTY devices transmit the characters at either 45.45 bps or 50 bps using t

25、he Baudot code, a 6 binary frequency shift keyed scheme that is carrierless, half duplex, and without error protection. 7 In June 1996, the FCC adopted Section 20.18(c) of the Commissions Rules. It requires that, as of October 1, 8 1997, all covered wireless carriers must be capable of transmitting

26、911 calls from individuals with speech or 9 hearing disabilities through means other than mobile radio handsets, e.g., through the use of TTY devices. The 10 pre-existing digital wireless networks have rendered TTY conversations unintelligible. The frame and bit 11 errors that occur over the air, as

27、 well as the variable rate speech coding, conspired to create unacceptably high 12 character error rates. 13 The purpose of this standard is to establish minimum performance requirements and a test procedure for 14 verifying solutions for transporting the Baudot code over cdma2000 7 wireless network

28、s using 3GPP2 13K 15 Vocoder 2, EVRC 1, SMV 8, EVRC-B, EVRC-WB, and EVRC-NW 1, corresponding to Service 16 Options 17, 3, 56, 68, 70, and 73, respectively. An electronic package containing tools and test vectors for the 17 purpose of performing these minimum performance tests accompanies this standa

29、rd. 18 For the remainder of this document, the term test vocoder refers to the speech coder with TTY extension for 19 which compliance with this document is being verified. The term reference vocoder refers to the C simulation 20 of the vocoder with the most recent TTY extension, which is provided i

30、n the accompanying electronic package. 21 1.2 Requirements Language 22 This specification uses the following verbal forms: “Shall” and “shall not” identify requirements to be 23 followed strictly to conform to the standard and from which no deviation is permitted. “Should” and “should 24 not” indica

31、te that one of several possibilities is recommended as particularly suitable, without mentioning or 25 excluding others; that a certain course of action is preferred but not necessarily required; or that (in the negative 26 form) a certain possibility or course of action is discouraged but not prohi

32、bited. “May” and “need not” indicate 27 a course of action permissible within the limits of the standard. “Can” and “cannot” are used for statements of 28 possibility and capability, whether material, physical, or causal. 29 1.3 References 30 1.3.1 Normative References 31 1 C.S0014, Enhanced Variabl

33、e Rate Codec, Speech Service Options 3, 68, 70, and 73 for Wideband Spread 32 Spectrum Digital Systems. 33 2 C.S0020, High Rate Speech Service Option 17 for Wide Band Spread Spectrum Communication Systems. 34 3 ITU-T Recommendation V.18, Operational and Interworking Requirements for DCEs Operating i

34、n the Text 35 Telephone Mode, November 2000. 36 4 Reserved 37 3GPP2 C.S0028-B v1.0 2 5 TTY Over Cellular Laboratory and Field Test Procedure, Lober Printable Character Error Rate (PCER) and Total Character Error Rate (TCER) 5. PCER compares the 4 actual text sent and received without any considerati

35、on to the underlying method of transfer, which involved 5 conversion to and from Baudot with the insertion of shift state characters. TCER recognizes the Baudot 6 character set and the insertion of shift characters by comparing the 5-bit Baudot code directly. 7 For both PCER and TCER, the character

36、error rate is computed by counting the number of missed and changed 8 characters. The number of characters in the reference file is considered the total number of characters. PCER 9 = (missed + changed)/total for the printable characters and TCER = (missed + changed)/total for the 5-bit 10 Baudot co

37、de character set. The number of added characters is not considered in the character error rate. 11 The TTY Forum has set a goal for the character error rate to be less than 1%, however, there was no agreement 12 as to whether that would be TCER or PCER. The TTY solution adopted for CDMA is capable o

38、f far exceeding 13 this goal. For the purposes of this minimum performance requirement, only the TCER shall be used because it 14 does not depend on the content of the TTY sequences. Furthermore, the TCER shall be calculated using the 15 tools provided with this specification in conjunction with the

39、 UNIX diff command. See Section 5 for a 16 description of the tools. 17 3GPP2 C.S0028-B v1.0 5 4 TTY/TDD TEST CASES 1 This section describes the test cases that are exercised in this minimum performance specification. Compliance 2 with these requirements shall be verified by processing the accompany

40、ing test vectors and using the 3 accompanying tools, as described in Section 6. 4 4.1 Interoperability with Reference TTY Vocoder 5 The test vocoder shall interoperate with the simulation of its corresponding reference vocoder. Packets from 6 the test encoder shall interoperate with the reference de

41、coder, and vice versa. 7 4.2 Interoperability with Reference Non-TTY Capable Vocoder 8 The test vocoder shall interoperate with legacy, non-TTY capable vocoders. Packets from the test encoder shall 9 interoperate with the reference decoder, and vice versa, for TTY and non-TTY inputs. Performance wit

42、h the 10 test vocoder and non-TTY vocoders shall be comparable to the performance between two non-TTY capable 11 phones. 12 4.3 Input Level 13 The test vocoder shall meet the performance requirements for detection and regeneration when the input signal 14 level ranges from 45 dBm to 5 dBm. 15 4.4 Bi

43、t Duration 16 The test vocoder shall meet the performance requirements for detection and regeneration when the input bit 17 durations are in the range 22 ms 0.4 ms for 45.45 bps and 20 ms 0.4 ms for 50 bps. 18 4.5 Stop Bit 19 The test vocoder shall meet the performance requirements for detection and

44、 regeneration with stop bits ranging 20 in duration from 1 to 2 bits, where the bits may be in the range 22 ms 0.4 ms for 45.45 bps and 20 ms 0.4 21 ms for 50 bps. 22 4.6 Phase Changes 23 The performance of the test vocoder shall be independent of the inputs phase changes between TTY bits. 24 These

45、phase changes include: 25 Zero phase 26 Random phase 27 4.7 Frequency Deviations 28 The test vocoder shall meet the performance requirements for detection and regeneration when the mark tone 29 (1400 Hz) and the space tone (1800 Hz) deviate from their nominal values by 4.0%. 30 4.8 Typing Mode 31 Fo

46、r most applications, text telephone conversations are conducted live, with manual typists. The TTY call is 32 characterized by bursts of typing followed by pauses. This is referred to as manual mode. Some TTY devices 33 3GPP2 C.S0028-B v1.0 6 are capable of transmitting stored conversations, or file

47、s. In this case, a long, uninterrupted stream of TTY 1 characters characterizes the TTY call. This is referred to as streaming mode. The test vocoder shall be capable 2 of supporting both typing modes. 3 4.9 Preamble 4 In TTY devices, the first tone of a character may be the space tone of the start

48、bit, or a mark tone preceding the 5 start bit, which is referred to as the preamble. The test vocoder shall meet the performance requirements for 6 detection and regeneration whether or not the preamble is present. 7 4.10 Mark Hold Tone 8 The mark hold time defines an additional period of time durin

49、g which the TTY transmits a mark hold tone 9 (1400 Hz) following the last character transmitted. The mark hold tone is not transmitted between each 10 character if the character is followed immediately by another character. The test vocoder shall regenerate a 11 mark hold tone for 300 ms or until the next character is regenerated, whichever is less. The test vocoder shall 12 meet the performance requirements for detection and regeneration: 13 When characters are followed by the mark hold tone. 14 When characters are followed by silence. 15 4.11