1、TIA-102.BAHA-A (Revision of TIA-102.BAHA)June 2017Project 25 Fixed Station Interface Messages and Procedures NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchang
2、eability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for their particular need. The existence of such Standards and Publications shall not in any respect preclude any member or non-member of TIA from manufacturing or selli
3、ng products not conforming to such Standards and Publications. Neither shall the existence of such Standards and Publications preclude their voluntary use by Non-TIA members, either domestically or internationally. Standards and Publications are adopted by TIA in accordance with the American Nationa
4、l Standards Institute (ANSI) patent policy. By such action, TIA does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Standard or Publication. This Standard does not purport to address all safety problems associated with its use or all
5、applicable regulatory requirements. It is the responsibility of the user of this Standard to establish appropriate safety and health practices and to determine the applicability of regulatory limitations before its use. Any use of trademarks in this document are for information purposes and do not c
6、onstitute an endorsement by TIA or this committee of the products or services of the company. (From Project No. TIA-PN-102.BAHA-A-R1, formulated under the cognizance of the TIA TR-8 Mobile and Personal Private Radio TR-8.19 Subcommittee on Wireline System Interfaces). Published by TELECOMMUNICATIONS
7、 INDUSTRY ASSOCIATION Technology (b) there is no assurance that the 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 c
8、ontents of this Document may involve the use of intellectual property 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 a
9、nd called to TIAs attention, a statement from the holder thereof is 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 discussio
10、ns of any licensing terms or conditions, which are instead left to 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
11、 have been complied with as respects the Document or its contents. 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, specificat
12、ion, recommendation or otherwise), whether such reference consists of mandatory, alternate or optional elements (as defined in the TIA Procedures for American National Standards) then (i) TIA disclaims any duty or obligation to search or investigate the records of any other SSO for IPR or letters of
13、 assurance relating to any such Normative Reference; (ii) TIAs policy of encouragement of voluntary disclosure (see TIA Procedures for American National Standards Annex C.1.2.3) of Essential Patent(s) and published pending patent applications shall apply; and (iii) Information as to claims of IPR in
14、 the records or publications of the other SSO shall not constitute identification to TIA of a claim of Essential 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 investig
15、ate products, designs or services or any claims of compliance with the contents of the Document. ALL WARRANTIES, 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 O
16、R USE, ITS MERCHANTABILITY AND ITS NONINFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL PROPERTY RIGHTS. TIA EXPRESSLY 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
17、 REGULATION, OR THE SAFETY OR HEALTH EFFECTS OF THE CONTENTS OR ANY PRODUCT OR SERVICE REFERRED TO IN THE 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 H
18、EREIN, INCLUDING WITHOUT LIMITATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING 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 OTHE
19、RWISE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGATION OF DAMAGES IS A FUNDAMENTAL ELEMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. TIA-102.BAHA-A i FOREWORD (This foreword is not part of this document.)
20、This document has been created in response to a request by the APCO/NASTD/FED Project 25 Steering Committee as provided for in a Memorandum of Understanding (MOU) dated April 1992 and amended December 1993. The MOU states APCO/NASTD/FED shall devise a Common System Standard for digital public safety
21、 communications (the Standard) commonly referred to as Project 25 or P25, and that TIA, as agreed to by the membership of the appropriate TIA Engineering Committee, will provide technical assistance in the development of documentation for the Standard. If the abbreviation “P25” or the wording “Proje
22、ct 25” appears on the cover sheet of this document when published that indicates the APCO/NASTD/FED Project 25 Steering Committee has adopted this document as part of the Standard. The appearance of the abbreviation “P25” or the wording “Project 25” on the cover sheet of this document or in the titl
23、e of any document referenced herein should not be interpreted as limiting the applicability of the information contained in any document to “P25” or “Project 25” implementations exclusively. This document has been developed by TR8.19 (Wireline Interfaces) with inputs from the APCO Project 25 Interfa
24、ce Committee (APIC), the APIC Fixed Station Interface Task Group, and TIA Industry members. This document is being published to provide technical information on the emerging digital techniques for Land Mobile Radio Service. This document is the first revision to the published Fixed Station Interface
25、 Messages Clause 2 identifies the document organization and structure; Clause 3 identifies the normative and informative references; Clause 4 defines key terms; Clause 5 provides a list of acronyms and abbreviations; Clause 6 defines the CFSI architecture; Clause 7 defines the CFSI analog interface;
26、 Clause 8 defines the CFSI digital interface. Clause 9 defines the CFSI packet data interface TIA-102.BAHA-A 4 3 References The following documents contain provisions which, through reference herein, constitute provisions of this document. At the time of publication, the editions indicated were vali
27、d. All documents are subject to revision, and parties to agreements based on this document are encouraged to investigate the possibility of applying the most recent editions of the documents indicated below. ANSI and TIA maintain registers of currently valid national standards maintained by them. Th
28、e appearance of “Project 25” in references below indicates the TIA document has been adopted by the APCO/NASTD/FED Project 25 Steering Committee as part of its Project 25 standard, i.e. “the Standard.” 3.1 Normative References The following referenced documents are valid as of the date of this docum
29、ent. Please also refer to relevant updates or replacements to these documents offered by their publishing bodies. 1 RFC 791, Internet Protocol, IETF, September 1981. 2 TIA-603-D, Land Mobile FM or PM Communications Equipment Measurement and Performance Standards, TIA, August 2010. 3 GR-506-CORE Issu
30、e 2, Signaling for Analog Interfaces, Telcordia, December 2006. 4 ANSI/TIA-968-B, Technical Requirements for Connection of Terminal Equipment To the Telephone Network, Global Engineering Documents, Englewood CO, August 2009. (This is the privatization of FCC Title 47 CFR Part 68.) 5 TIA-102.BACA-B,
31、Project 25 Inter-RF Subsystem Interface Messages and Procedures for Voice Services, Mobility Management, and RFSS Capability Polling Services, TIA, November 2011 6 RFC 768, User Datagram Protocol, IETF, August 1980. 7 RFC 3550, RTP: A Transport Protocol for Real-Time Applications, IETF, July 2003. 8
32、 TIA-102.BAAA-A, Project 25 FDMA Common Air Interface, TIA, September 2003. 9 ANSI/TIA-102.AABC-D, Project 25 Trunking Control Channel Messages, TIA, April 2015. 10 TIA-102.AABF-D, Project 25 Link Control Word Formats and Messages, TIA, April 2015. 11 TIA-102.BABA-A, Project 25 Vocoder Description,
33、TIA, February 2014. 12 ITU-T Recommendation G.711, Pulse Code Modulation (PCM) Of Voice Frequencies, International Telecommunication Union, November 1988. TIA-102.BAHA-A 5 13 RFC 3246, An Expedited Forwarding PHB (Per-Hop Behavior), IETF, March 2002. 21 TIA-102.BAAC-C, Project 25 Common Air Interfac
34、e Reserved Values, TIA, April 2011. 22 TIA-102.BAAD-B Project 25 Conventional Procedures, TIA, August 2015. 3.2 Informative References 14 TIA-102.AABG, Project 25 Conventional Control Messages, TIA, April 2009. 15 RFC 793, Transmission Control Protocol, IETF, September 1981. 16 RFC 2475, An Architec
35、ture for Differentiated Services, IETF, December 1998. 17 TSB-102.BACC-B, APCO Project 25 Inter-RF Subsystem Interface Overview, TIA, November 2011. 18 RFC 3551, RTP Profile for Audio and Video Conferences with Minimal Control, IETF, July 2003. 19 TSB-102-C, Project 25 TIA-102 Documentation Suite Ov
36、erview, TIA, March 2016. 20 TIA-102.AABD-B, Project 25 Trunking Procedures, TIA, November 2014. 23 TSSC-20150707_008_TIA Style Guide 2015_Final Revision TIA Style Manual, TIA, July, 2015 24 TIA-102.BACE, Project 25 Inter RF Subsystem Interface (ISSI) Messages and Procedures for Conventional Operatio
37、n, TIA, June 2008 25 TIA-102.BAEA-C, Project 25 Data Overview and Specification, TIA, December 2015 TIA-102.BAHA-A 6 4 Definitions $This prefix is used to indicate a hex value parameter. %.This prefix is used to indicate a binary value parameter. Base Station .Equipment within a fixed station subsys
38、tem that performs at least the Base Radio functions of power amplifier (PA), RF front-end, modulation and demodulation. It may perform other fixed station subsystem functions also. It is normally connected to a console or RFSS through a Fixed Station Interface. Block Payload The actual data containe
39、d in the block. The block data may be voice, CAI data blocks, control words, low speed data, etc. Block Payload Type, Block PT .A number which describes the basic payload type as defined by the IETF (when E bit is set to 0) or, it may be a profile specific type (when E bit is set to 1). In this spec
40、ification, E = 1 and the Block Payload Type is carried in either a Voice Conveyance or Data Conveyance message payload. Block Type .A block identifier used to indicate what type of data is contained in the block, such as CAI voice, IMBE only, link control word, encryption sync word, CAI data, etc. B
41、usy Bits. A set of two binary bits used by the Fixed Station Subsystem to indicate inbound channel status on the CAI. CAI (Common Air Interface) A radio to radio signal path defined in terms of access method, modulation scheme, vocoding method, channel data rate, and channel data format. CAI Data Bl
42、ock. A CAI Data Block is a single formatted block of information protected by a trellis code that may be part of a related sequence of blocks (a data packet) transmitted over the Common Air Interface. Types of CAI Data Blocks include Confirmed Header, Confirmed Data block, TIA-102.BAHA-A 7 Confirmed
43、 Last block, Unconfirmed Header, Unconfirmed Data block, Unconfirmed Last block, or Confirmed Response. CDCSS Continuous Digital Controlled Squelch System which allows a receiver to block out all signals except those encoded with the selected sub-audible digital pattern. CFSH. Conventional Fixed Sta
44、tion Host: Functional component of either an RF Subsystem (RFSS) or a Console Subsystem. CFSS. See Fixed Station Subsystem. Console A device used by a dispatcher to communicate with radios in the field. These range from simple devices that resemble telephones to advanced touch screen computer based
45、subsystems that control multiple transmitters and can patch multiple call groups together. Conventional Fixed Station. See Fixed Station CTCSS . Continuous Tone-Coded Squelch System which allows a receiver to block out all signals except those encoded with the selected sub-audible tone. Fixed Data N
46、etwork . A network of fixed computer equipment for wide-area data communications. Fixed Station.Short -cut for Fixed Station Subsystem” Fixed Station Subsystem Set of equipment that is bounded by a Conventional Air Interface and the Fixed Station Interface. Equipment within the Fixed Station Subsyst
47、em boundary may include, but is not limited to; Conventional Base Station(s), Repeater(s), Voter(s), Distribution Function(s), and other RF fixed equipment. The RF equipment contained in a Fixed Station Subsystem may also transmit or receive conventional FM. Fixed Station Host The control equipment
48、which is situated at the opposite end of the Fixed Station Interface from the Fixed Station. Examples of Fixed Station Hosts include Consoles and RFSSs. TIA-102.BAHA-A 8 IMBE Improved Multi-Band Excitation. A low data rate Voice codec developed by Digital Voice Systems, Inc. (DVSI) Mobile .A Subscri
49、ber Unit intended for vehicular operation. Portable A Subscriber Unit intended for hand-held operation. Repeater Equipment within a fixed station subsystem that performs at least the radio functions of power amplifier (PA), RF front-end, modulation and demodulation. It may include a limited number of functions such as NAC detection, CTCSS/DCS detection to enable repeater functions etc. It need not include a connection to a console or RFSS through a Fixed Station Int
