1、 TIA-102.BACA-B-1 (Addendum to TIA-102.BACA-B) July 2013Project 25 Inter-RF Subsystem Interface Messages and Procedures for Voice Services, Mobility Management, and RFSS Capability Polling Services- Addendum 1- Group Emergency Behaviors NOTICE TIA Engineering Standards and Publications are designed
2、to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for their particular need. The existence
3、of such Standards and Publications shall not in any respect preclude any member or non-member of TIA from manufacturing or selling products not conforming to such Standards and Publications. Neither shall the existence of such Standards and Publications preclude their voluntary use by Non-TIA member
4、s, either domestically or internationally. Standards and Publications are adopted by TIA in accordance with the American National 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 ado
5、pting the Standard or Publication. This Standard does not purport to address all safety problems associated with its use or all applicable regulatory requirements. It is the responsibility of the user of this Standard to establish appropriate safety and health practices and to determine the applicab
6、ility of regulatory limitations before its use. (From Project No. TIA-PN-102.BACA-B-1, 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 INDUSTRY ASSOCIATION Technology (b) there is n
7、o 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 contents of this Document may involve the use of
8、 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 and called to TIAs attention, a statement from t
9、he 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 discussions of any licensing terms or conditions, which
10、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 have been complied with as respects the Docume
11、nt 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, specification, recommendation or otherwise), whether such
12、 reference consists 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) T
13、IAs policy of encouragement 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 TI
14、A 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 investigate products, designs or services or any claims of compliance with the contents of the
15、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 OR USE, ITS MERCHANTABILITY AND ITS NONINFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL PRO
16、PERTY 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 REGULATION, OR THE SAFETY OR HEALTH EFFECTS OF THE CONTENTS OR ANY PRODUCT OR SERVICE
17、REFERRED TO IN THE DOCUMENT OR PRODUCED OR RENDERED TO COMPLY WITH THE CONTNTS. 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 CONSEQU
18、ENTIAL 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 OTHERWISE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGATION OF DAM
19、AGES 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.BACA-B-1 i Foreword (This foreword is not part of this standard.) This document has been created to further the objectives outlined in a Memorandum of U
20、nderstanding (MOU) dated December, 1993 between APCO/NASTD/FED and the Telecommunications Industry Association (TIA). The MOU provides that APCO/NASTD/FED will devise a Common System Standard for digital public safety communications (the Standard), and that TIA shall, to the extent TIA members are w
21、illing, provide technical assistance in the development of documentation for the Standard. This document has been developed by TR8.19 (Wire-line Interfaces) with inputs from the APCO Project 25 Interface Committee (APIC), the APIC ISSI Task Group, and TIA Industry members. The appearance of the abbr
22、eviation “P25” or the phrase “Project 25” on the cover sheet of this document when published or in the title of any TIA-102 document or Telecommunications Service Bulletin (TSB) referenced herein, indicates the APCO/NASTD/FED Project 25 Steering Committee has adopted the document as part of the Stan
23、dard. The appearance of the abbreviation “P25” or the phrase “Project 25” on the cover sheet of this document or in the title of any document referenced herein does not limit the applicability of the information contained in the document to “P25” or “Project 25” implementations exclusively. This doc
24、ument is an Addendum to 102BACA. The ISSI is the interface between Radio Frequency Subsystems (RFSSs) satisfying relevant user requirements as described in 102BACC.TIA-102.BACA-B-1 ii Patent Identification The readers attention is called to the possibility that compliance with this document may requ
25、ire the use of one or more inventions covered by patent rights. By publication of this document no position is taken with respect to the validity of those claims or any patent rights in connection therewith. The patent holders so far identified have, we believe, filed statements of willingness to gr
26、ant licenses under those rights on reasonable and nondiscriminatory terms and conditions to applicants desiring to obtain such licenses. The following patent holders and patents have been identified in accordance with the TIA intellectual property rights policy: No patents have been identified. TIA
27、shall not be responsible for identifying patents for which licenses may be required by this document or for conducting inquiries into the legal validity or scope of those patents that are brought to its attention. Trademark Identification The following trademarks are referenced in this specification
28、: IMBE is a trademark of Digital Voice Systems, Inc.11Use of the trademark identified in this standard is not an endorsement by TIA. TIA-102.BACA-B-1 iii TABLE OF CONTENTS A. ADDENDUM INTRODUCTION . 1 B. ADDENDUM SCOPE . 1 C. ADDENDUM REFERENCES 2 1. NORMATIVE REFERENCES 2 1. INTRODUCTION . 3 1.1 SC
29、OPE . 3 1.2 TERMINOLOGY 3 1.3 DOCUMENT STRUCTURE 3 1.4 DEFINITIONS 3 1.5 ABBREVIATIONS . 3 1.6 REFERENCES 3 2. OVERVIEW OF ARCHITECTURE AND PROTOCOL SUITE 4 2.1 ARCHITECTURE OVERVIEW . 4 2.1.1 Call Models . 4 2.1.2 Subsystem Topologies 4 2.1.3 Functional Model 4 2.1.3.1 Mobility Management 6 2.1.3.2
30、 Call Control 6 2.1.3.2.1 Unit Call Control 6 2.1.3.2.2 Group Call Control . 6 2.1.3.2.2.1 Group Call Topology 8 2.1.3.2.2.2 Group Call RTP Resource Management . 8 2.1.3.2.2.3 Group Call RF Resource Management . 8 2.1.3.2.2.4 Group Call Vocoder Mode Selection 9 2.1.3.2.2.5 Group Emergency Signaling
31、. 9 2.1.3.3 Media processing . 9 2.1.3.4 RFSS Service Capability Polling . 9 2.1.4 Service Access Point Model . 9 2.1.4.1 Mobility Management SAP 9 2.1.4.2 Call Control SAP . 9 2.1.4.2.1 CC Call Segment Setup Transaction . 11 2.1.4.2.2 CC Call Segment Teardown Transaction 11 2.1.4.2.3 CC Call Segmen
32、t Modification Transaction . 11 2.1.4.2.4 CC Group Emergency Cancel Transaction . 11 2.1.4.3 Transmission Control SAP . 12 2.2 ISSI INTERNET PROTOCOL SUITE 12 2.3 ISSI DATA TRANSMISSION ORDER . 12 3. SIP MESSAGES AND PARAMETERS DEFINITION FOR ISSI . 13 3.1 PREAMBLE: GRAMMAR 13 3.2 SIP TRANSPORT . 13
33、 3.3 REQUEST LINE CONSTRUCTION 13 3.4 SIP URI AND RELATED ADDRESSING LOGIC . 13 3.5 SIP HEADER ENCODING . 13 3.6 STATUS-CODE AND REASON-PHRASE 13 3.7 SDP ANNOUNCEMENTS 13 3.8 X-TIA-P25-ISSI BODY PARAMETERS 13 3.8.1 Group Service Profile attributes . 13 TIA-102.BACA-B-1 iv 3.8.2 User Service Profile
34、attributes . 13 3.8.3 RFSS Service Capability Profile attributes . 13 3.8.4 ISSI specific register parameter attributes . 13 3.8.5 ISSI specific call parameter attributes 13 3.8.5.1 Initial transmitter . 13 3.8.5.2 RF Resource Availability . 13 3.8.5.3 Preference 14 3.8.5.4 Duplex Mode . 14 3.8.5.5
35、In-call roaming . 14 3.8.5.6 Group Call Type 14 3.8.5.7 Protected 15 3.8.5.8 Console Transmit Request Priority 15 3.9 X-TIA-P25-SNDCP BODY PARAMETERS . 15 3.10 EXAMPLES 15 4. RTP MESSAGE VOCABULARY FOR ISSI . 15 5. MOBILITY MANAGEMENT . 15 6. CALL CONTROL 16 6.1 CC-SAP 16 6.2 SIP TRANSACTIONS 16 6.3
36、 STATE MODELS FOR ISSI VOICE SERVICES 16 6.4 BASIC ISSI SIP CONTROL PROCEDURES 16 6.5 CALL CONTROL PROCEDURES FOR ISSI SU-TO-SU VOICE SERVICES . 16 6.6 CALL CONTROL PROCEDURES FOR ISSI GROUP VOICE SERVICES 16 6.6.1 ISSI Group Voice Call Setup 17 6.6.1.1 General . 17 6.6.1.2 Group Voice Call Setup In
37、itiated by Serving RFSS 18 6.6.1.2.1 Actions Required at Serving RFSS . 18 6.6.1.2.2 Actions Required at Home RFSS . 19 6.6.1.3 Call Segment Setup Initiated by Home RFSS 21 6.6.1.3.1 Actions Required at Home RFSS . 22 6.6.1.3.2 Actions Required at Serving RFSS . 24 6.6.2 Subsequent Modification of I
38、SSI SIP Session Characteristics . 26 6.6.3 Handling (re-)INVITE Request Collisions 26 6.6.4 ISSI SIP Heartbeat 26 6.6.5 ISSI SIP Session Termination by Home RFSS 26 6.6.6 ISSI SIP Session Termination by Serving RFSS . 26 6.6.7 ISSI Group Voice Call Release . 26 6.6.8 ISSI Group Emergency Cancellatio
39、n 26 6.6.8.1 Group Emergency Cancellation Initiated by Serving RFSS 26 6.6.8.2 Group Emergency Cancellation Initiated by Home RFSS . 26 7. PUSH-TO-TALK (PTT) MANAGEMENT 28 8. RFSS SERVICE CAPABILITY POLLING . 28 ANNEX A (NORMATIVE) GENERIC SIP RESPONSES OVER THE ISSI . 29 ANNEX B (NORMATIVE) TABLE O
40、F TIMERS AND CONSTANTS 29 ANNEX C (NORMATIVE) TIA-102 VOCODER ERROR MITIGATION DATA . 29 ANNEX D (NORMATIVE) SU-TO-SU CALL FLOWS . 29 ANNEX E (NORMATIVE) GROUP CALL FLOWS . 29 TIA-102.BACA-B-1 v ANNEX F (INFORMATIVE) SU-TO-SU CALL FLOWS INVOLVING MULTIPLE VOCODER MODES 29 ANNEX G (INFORMATIVE) GROUP
41、 CALL FLOWS INVOLVING MULTIPLE VOCODER MODES 29 ANNEX H (INFORMATIVE) FUTURE CONSIDERATIONS 29 ANNEX I (INFORMATIVE) CONSOLE FUNCTIONALITY . 29 TIA-102.BACA-B-1 vi DOCUMENT REVISION HISTORY Version Date Description Rev 0 June, 2013 Approved for TIA publication. TIA-102.BACA-B-1 1 A. Addendum Introdu
42、ction The purpose of this addendum is to update information contained in 102BACA, to include procedural changes to support consistent group emergency behaviors between RFSSs that may implement different group emergency tracking behaviors per 102AABD. B. Addendum Scope This addendum provides the foll
43、owing changes to the ISSI: (1) Enhanced Group Emergency procedures This document will only include information relevant to the aforesaid scope. The reader is referred to 102BACA for all other pertinent information. The next complete revision of 102BACA will incorporate the changes contained in this
44、addendum. Care must be taken when incorporating changes in this addendum to avoid conflicts with the changes made by other addendum(s) that are incorporated at the same time. Changes to 102BACA are described in this document starting at Section 1.0. Italic text between square brackets provides instr
45、uctions on how to incorporate changes in a section. If a section contains subsections, and neither the section nor subsections thereof change, only the section will be identified in this document. Note that section numbers identified in this addendum correspond to the same section numbers in 102BACA
46、. Also note that new or modified text is tracked in blue in order to assist the reader. TIA-102.BACA-B-1 2 C. Addendum References This addendum references the following TIA documents. 1. Normative References 102BACA Project 25 Inter-RF Subsystem Interface Messages and Procedures for Voice Services,
47、Mobility Management, and RFSS Capability Polling Services, TIA-102.BACA-B, TIA, November 2012 102BACC Project 25 Inter-RF Subsystem Interface Overview, TIA-102.BACC-B, TIA, November 2011 102BACD Project 25 Inter-RF Subsystem Interface - Messages and Procedures for Supplementary Data, TIA-102.BACD-B,
48、 TIA, July 2011 102AABD Trunking Procedures, TIA-102.AABD-A, TIA, December 2008 102AABC Project 25 Trunking Control Channel Messages, TIA-102.AABC-C, TIA, October 2009 TIA-102.BACA-B-1 3 1. Introduction No change from existing text in this section of 102BACA, except for subsection 1.4 below. 1.1 Sco
49、pe No change from existing text in this section of 102BACA. 1.2 Terminology No change from existing text in this section of 102BACA. 1.3 Document Structure No change from existing text in this section of 102BACA. 1.4 Definitions Add the following new definitions in this section of 102BACA. Non-Tracking RFSS: This term is used to denote an RF Subsystem that does not track the emergency state of groups per 102AABD. A non-tracking RFSS can consider some or all SUs “sufficiently privileged” with regards to the Emergency
