ETSI TS 126 230-2018 Digital cellular telecommunications system (Phase 2+) (GSM) Universal Mobile Telecommunications System (UMTS) Cellular text telephone modem Transmitter bit exa.pdf

《ETSI TS 126 230-2018 Digital cellular telecommunications system (Phase 2+) (GSM) Universal Mobile Telecommunications System (UMTS) Cellular text telephone modem Transmitter bit exa.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 126 230-2018 Digital cellular telecommunications system (Phase 2+) (GSM) Universal Mobile Telecommunications System (UMTS) Cellular text telephone modem Transmitter bit exa.pdf（29页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 126 230 V15.0.0 (2018-07) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Cellular text telephone modem; Transmitter bit exact C-code (3GPP TS 26.230 version 15.0.0 Release 15) TECHNICAL SPECIFICATION GLOBAL SYSTEM FOR MOBILE C

2、OMMUNICATIONSRETSI ETSI TS 126 230 V15.0.0 (2018-07)13GPP TS 26.230 version 15.0.0 Release 15Reference RTS/TSGS-0426230vf00 Keywords GSM,UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Assoc

3、iation but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or prin

4、t versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on

5、 a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx I

6、f you find errors in the present document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and

7、 microfilm except as authorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. ETSI 2018. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMa

8、nd the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTETMare trademarks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the benefit of its Members. GSMand the GSM logo are trademarks reg

9、istered and owned by the GSM Association. ETSI ETSI TS 126 230 V15.0.0 (2018-07)23GPP TS 26.230 version 15.0.0 Release 15Intellectual Property Rights Essential patents IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information pertaining to thes

10、e essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest

11、updates are available on the ETSI Web server (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web

12、server) which are, or may be, or may become, essential to the present document. Trademarks The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims no ownership of these except for any which are indicated as being the property of

13、 ETSI, and conveys no right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks. Foreword This Technical Specification (TS) has been

14、produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables. The cross referenc

15、e between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clau

16、se 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 126 230 V15.0.0 (2018-07)33GPP TS 26.230 version 15.0.0 Release 15Contents Intellectual Property Rights 2g3F

17、oreword . 2g3Modal verbs terminology 2g3Foreword . 4g30 Scope 5g31 Normative references . 5g32 Definitions and Abbreviations 5g33 C code structure 5g33.1 Contents of the C source code 5g33.2 Program execution 6g33.3 Code hierarchy . 10g33.3.1 Initialization routines 10g33.3.2 Signal Processing Funct

18、ions . 10g33.4 Description of global constants used in the C-code 12g33.5 Type Definitions . 13g33.6 Functions of the C Code . 13g3Annex A (informative): Change history . 27g3History 28g3ETSI ETSI TS 126 230 V15.0.0 (2018-07)43GPP TS 26.230 version 15.0.0 Release 15Foreword This Technical Specificat

19、ion has been produced by T1P1. The contents of the present document are subject to continuing work within the 3GPP TSG and may change following formal 3GPP approval. Should the 3GPP TSG modify the contents of this TS, it will be re-released by the 3GPP TSG with an identifying change of release date

20、and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to 3GPP for information; 2 presented to 3GPP for approval; 3 Indicates 3GPP approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhance

21、ments, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the specification; ETSI ETSI TS 126 230 V15.0.0 (2018-07)53GPP TS 26.230 version 15.0.0 Release 150 Scope This Technical Standard (TS) contains an electronic copy of the ANSI-C co

22、de for the Cellular Text Telephone Modem (CTM) for reliable transmission of text telephone text via the speech channel of cellular networks. While CTM is generally usable with text in UCS coding, the example application linked to CTM in this document is limited to use the signals and character set o

23、f the Baudot type. 1 Normative references This TS incorporates by dated and undated reference, provisions from other publications. These normative references are cited at the appropriate places in the text and the publications are listed hereafter. For dated references, subsequent amendments to or r

24、evisions of any of these publications apply to this TS only when incorporated in it by amendment or revision. For undated references, the latest edition of the publication referred to applies. 1 3GPP TS 26.226: “Cellular text telephone modem; General description“. 2 ISO/IEC 10646-1: “Information tec

25、hnology Universal Multiple-Octet Coded Character Set (UCS) Part 1: Architecture and Basic Multilingual Plane“. 2 Definitions and Abbreviations For the purposes of this TS, the following abbreviations apply: CTM Cellular Text Telephone Modem FEC Forward Error Correction FSK Frequency Shift Key HCO He

26、aring Carry Over, (individual may be able to hear, but cannot speak) Alternating transmission of speech and text. PCM Pulse Code Modulation RX Receive TX TransmitTTY Text Telephone UCS Universal Multiple-Octet Coded Character Set UTF UCS transformation format VAD Voice Activity Detection VCO Voice C

27、arry Over, Alternating transmission of speech and text 3 C code structure This clause gives an overview of the structure of the bit-exact C code and provides an overview of the contents and organization of the C code attached to this document. The C code has been verified on the following system. -

28、Sun Microsystems workstations with SUN SolarisTMoperating system and the the Gnu C Compiler (gcc version 2.7.2.3) and GNU Make 3.77; The C code has also been successfully compiled and used in the following environment, with the exception that it cannot be guaranteed that the upper part of the UCS co

29、de table in file ucs_functions.c will be compiled correctly since it depends on the codepage setting of the environment. - IBM PC/AT compatible computers with WindowsTMNT 4.0 operating system and Microsoft Visual C+ 6.0TMcompiler. 3.1 Contents of the C source code The distributed files with suffix “

30、c“ contain the source code and the files with suffix “h“ are the header files. All these files are in the root level of the ZIP-archive. ETSI ETSI TS 126 230 V15.0.0 (2018-07)63GPP TS 26.230 version 15.0.0 Release 15Makefiles are provided for the platforms in which the C code has been verified (list

31、ed above). They are called “Makefile“ for GNU Make and “Makefile.vc“ for Microsoft Visual C+TM. For the Sun Microsystems platform, an example shell script for a transmission via two signal adaptation modules is given in “test_negotiation“. For the Microsoft WindowsTMplatform, no shell script or batc

32、h program is provided. The software can be compiled using the commands make all or gmake all in case of Gnu Make nmake /f Makefile.vc in case of Microsoft Visual C+. The executables are compiled into the directory ./solaris (in case of Gnu Make) or into the actual directory in case of Microsoft Visu

33、al C+TM. The directory ./patterns provides the file baudot.pcm that serves as input signal for the test script test_negotiation. All output data of test_negotiation will be stored into the directory ./output. If required, this directory will be created by test_negotiation automatically. 3.2 Program

34、execution The CTM signal adaptation module is implemented in the execuable adaptation_switch (in case of Sun SolarisTMplatform) or adaptation_switch.exe (in case of the Micorsoft WindowsTMplatform). The program should be called like: adaptation_switch -ctmin -ctmout -baudotin -baudotout using the fo

35、llowing parameters: -ctmin input file with CTM signal -ctmout output file for CTM signal -baudotin input file with Baudot Tones -baudotout output file for Baudot Tones -textout output text file from CTM receiver (optional) -numsamples number of samples to process (optional) -nonegotiation disables t

36、he negotiation (optional) All files contain 16-bit linear encoded PCM audio samples, which are swapped according to the platforms endian type (Sun Microsystems platforms use big endian, Intel platforms use little endian). An example file baudot.pcm containing a Baudot Code modem signal (big endian)

37、is provided in the subdirectory ./patterns. Due to the fact that the signal adaptation module expects a successful negotiation before Baudot Code signals can be converted to CTM signals, the signal adaptation module has to be executed several times in two instances in order to execute a successful n

38、egotiation. For the Sun Microsystems platform, a shell script test_negotiation is provided for executing the following structure: - ctm_forward - baudot.pcm -| | -| |- baudot_out.pcm | adapt#1 | | adapt#2 | ETSI ETSI TS 126 230 V15.0.0 (2018-07)73GPP TS 26.230 version 15.0.0 Release 15/dev/null Enqu

39、iry Burst generated! Enquiry Burst generated! Enquiry Burst generated! CTM from far-end detected! Enquiry From Far End Detected! Enquiry From Far End Detected! Enquiry From Far End Detected! Enquiry Burst generated! CTM from far-end detected! CTM from far-end detected! Enquiry From Far End Detected!

40、 in case that inChar is not valid (e.g. inChar=0) ETSI ETSI TS 126 230 V15.0.0 (2018-07)153GPP TS 26.230 version 15.0.0 Release 15char convertTTYcode2char(Shortint ttyCode); Purpose: Conversion from TTY code into Character Defined in: baudot_functions.c Input Variables: ttyCode Baudot code (must be

41、within the range 0.63) or -1 if there is nothing to convert Return Value: character (or 0 if ttyCode is not valid) char convertUCScode2char(UShortint ucsCode); Purpose: Conversion from UCS code into character (Universal Multiple-Octet Coded Character Set, Row 00 of the Multilingual plane according t

42、o ISO/IEC 10646-1). This routine only handles characters in the range 0255 since that is all that is required for demonstration of Baudot support. Defined in: ucs_functions.c Input Variables: ucsCode UCS code index, must be within the range 0.255 Return Value: character (or 0 if ucsCode is not valid

43、) void conv_encoder_exec(conv_encoder_t* ptr_state, Shortint* in, Shortint inbits, Shortint* out); Purpose: Execution of the convolutional encoder for error protection Defined in: conv_encoder.c Input Variables: in Vector with net bits inbits Number of valid net bits in vector in Output variables: o

44、ut Vector with the encoded gross bits. The gross bits are either 0 or 1. The vector out must have at least CHC_RATE*inbits elements. Input/output variables: *ptr_state state variable of the encoder void conv_encoder_init(conv_encoder_t* ptr_state); Purpose: Initialization of the convolutional encode

45、r Defined in: conv_encoder.c Output Variables: *ptr_state Initialized state variable of the encoder ETSI ETSI TS 126 230 V15.0.0 (2018-07)163GPP TS 26.230 version 15.0.0 Release 15void ctm_receiver(fifo_state_t* ptr_signal_fifo_state, fifo_state_t* ptr_output_char_fifo_state, Bool* ptr_early_muting_

46、required, rx_state_t* rx_state); Purpose: Runs the CTM Receiver for a block of (nominally) 160 samples. Due to the internal synchronization, the number of processed samples might vary between 156 and 164 samples. The input of the samples and the output of the decoded characters is handled via fifo b

47、uffers, which have to be initialized externally before using this function (see fifo.h for details). Defined in: ctm_receiver.c input/output variables *ptr_signal_fifo_state fifo state for the input samples *ptr_output_char_fifo_state fifo state for the output characters *ptr_early_muting_required r

48、eturns whether the original audio signal must not be forwarded. This is to guarantee that the preamble or resync sequence is detected only by the first CTM device, if several CTM devices are cascaded subsequently. rx_state pointer to the variable containing the receiver states void ctm_transmitter(U

49、Shortint ucsCode, Shortint* txToneVec, tx_state_t* tx_state, Shortint *ptrNumBitsStillToModulate, Bool sineOutput); Purpose: Runs the CTM Transmitter for a block of 160 output samples, representing 8 gross bits. The bits, which are modulated into tones, are taken from an internal fifo buffer. If the fifo buffer is empty, zero-valued samples are generated. The fifo buffer is filled with channel-encoded and interleaved bits, which are generated internally