1、 TIA-102.BACA-B-2 (Addendum to TIA-102.BACA-B) November 2016Project 25 Inter-RF Subsystem Interface Messages and Procedures for Voice Services, Mobility Management, and RFSS Capability Polling Services- Addendum 2- Erratum 1 to Fix Errors and Omissions NOTICE TIA Engineering Standards and Publicatio
2、ns are designed 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
3、. The existence 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 b
4、y Non-TIA members, 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 whateve
5、r to parties adopting 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 determ
6、ine the applicability of regulatory limitations before its use. Any use of trademarks in this document are for information purposes and do not constitute an endorsement by TIA or this committee of the products or services of the company. (From Project No. TIA-PN-102.BACA-B-2, formulated under the co
7、gnizance 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 no assurance that the Document will be approved by any Committee of TIA or any other body in its present or any
8、 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 property rights (“IPR”), including pending or issued patents, or copyrights, owned by one or mor
9、e 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 is requested, all in accordance with the Manual. TIA takes no position with reference to, an
10、d 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 the parties involved, nor will TIA opine or judge whether proposed licensing terms or cond
11、itions 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. If the Document contains one or more Normative References to a document published by anoth
12、er 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 of mandatory, alternate or optional elements (as defined in the TIA Procedures for America
13、n 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 assurance relating to any such Normative Reference; (ii) TIAs policy of encouragement of voluntary disclosure (see TIA Procedures for American National Stan
14、dards 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 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 applic
15、ations. 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 WARRANTIES, EXPRESS OR IMPLIED, ARE DISCLAIMED, INCLUDIN
16、G 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 EXPRESSLY DISCLAIMS ANY AND ALL RESPONSIBILITIES FOR
17、 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 DOCUMENT OR PRODUCED OR RENDERED TO COMPLY WITH THE
18、 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 (INCLUDING DAMAGES FOR LOSS OF BUSINESS, LOSS OF PROFI
19、TS, 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 FUNDAMENTAL ELEMENT OF THE USE OF THE CONTENTS HEREOF, AND
20、THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. TIA-102.BACA-B-2 iForeword (This foreword is not part of this standard.) This document has been submitted to APCO/NASTD/FED by the Telecommunications Industry Association (TIA), as provided for in a Memorandum of Understanding (M
21、OU) dated December, 1993. That MOU provides that APCO/NASTD/FED will devise a Common System Standard for digital public safety communications (the Standard), and that TIA shall provide technical assistance in the development of documentation for the Standard. This document has been developed by TR8.
22、19 (Wireline Interfaces) with inputs from the APCO Project 25 Interface Committee (APIC), the APIC ISSI 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. The symbol “P25” or the wo
23、rding “Project 25” appearing 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, that indicates the APCO/NASTD/FED Project 25 Steering Committee has adopted the document as part of the Standard. Th
24、e appearance of the abbreviation “P25” or the wording “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 this document to “P25” or “Project 25” implementations exclusively. This document
25、is an Erratum to TIA-102.BACA-B, November 2012, Project 25 Inter-RF Subsystem Interface (ISSI) Messages and Procedures for Voice and Mobility Management Services. The ISSI is the interface between Radio Frequency Subsystems (RFSSs) enabling relevant Project 25 user requirements to be satisfied (e.g.
26、, as described in the Inter-RF Subsystem Interface Overview (TSB-102.BACC-B). Standardization efforts are planned to continue developing TIA standards defining compliance tests (e.g., measurement methods, performance recommendations, and interoperability tests) applicable to equipment implementing t
27、he TIA-102 ISSI protocols defined in this and other related TIA standards. TIA-102.BACA-B-2 iiPatent Identification The readers attention is called to the possibility that compliance with this document may require the use of one or more inventions covered by patent rights. By publication of this doc
28、ument 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 grant licenses under those rights on reasonable and nondiscriminatory terms and conditions t
29、o 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 shall not be responsible for identifying patents for which licenses may be required by thi
30、s 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: IMBE is a trademark of Digital Voice Systems, Inc.1 1 Use of the trademark identified in
31、 this standard is not an endorsement by TIA. TIA-102.BACA-B-2 iii TABLE OF CONTENTS A. ADDENDUM INTRODUCTIO N 1 B. ADDENDUM SCOPE . 1 C. ADDENDUM REFERENCES. 1 C.1 NORMATIVE REFERENCES . 1 C.2 INFORMATIVE REFERENC ES . 1 0.1 MINOR TECHNIC AL AND EDITORIAL CHANGES TH ROUGHOUT TIA -102.BACA-B 2 1. INT
32、RODUCTION . 3 1.1 SCOPE . 3 1.2 TERMINOLOGY 3 1.3 DOCUMENT STRUCTURE 3 1.4 DEFINITIONS 3 1.5 ABBREVIATIONS 4 1.6 REFERENCES . 5 1.6.1 Normative References 5 1.6.2 Informative References. 6 2. O VERVIEW OF ARCHITECT URE AND PROTOCOL SUI TE 9 2.1 ARCHITECTURE OVERVIEW 9 2.1.1 Call Models . 9 2.1.2 Sub
33、system Topologies 9 2.1.3 Functional Model. 9 2.1.4 Service Access Point Model 9 2.1.4.1 Mobility Management SAP . 9 2.1.4.1.1 MM Registration Transaction. 9 2.1.4.1.2 MM Serving Deregistration Transaction . 9 2.1.4.1.3 MM Home Deregistration Transaction . 9 2.1.4.1.4 MM Query Transaction 10 2.1.4.2
34、 Call Control SAP 10 2.1.4.3 Transmission Control SAP 10 2.1.4.4 RFSS Service Capability Polling SAP . 10 2.2 ISSI INTERNET PROTOCOL SUITE . 11 2.2.1 Lower Layers . 11 2.2.2 Network Layer . 11 2.2.2.1 Internet Protocol Version 4 (IPv4) 11 2.2.2.1.1 IPv4 Header Format . 11 2.2.2.1.2 Header Field Defi
35、nitions 12 2.2.2.2 Internet Protocol Version 6 (IPv6) 13 2.2.3 Transport Layer . 14 2.2.4 Application Layer 14 2.3 ISSI DATA TRANSMISSION ORDER . 14 3. SIP MESSAGES AND PAR AMETERS DEFINITION F OR ISSI 15 3.1 PREAMBLE: GRAMMAR 15 3.2 SIP TRANSPORT. 17 3.3 REQUEST LINE CONSTRUCTION 18 3.4 SIP URI AND
36、 RELATED ADDRESSING LOGIC 18 3.4.1 General Characteristics of SIP URIs 18 3.4.1.1 ISSI Domain Names . 18 3.4.1.2 ISSI Radical Names 18 TIA-102.BACA-B-2 iv3.4.1.3 ISSI Parameters 19 3.4.2 Request URI formatting Summary 23 3.5 SIP HEADER ENCODING . 24 3.5.1 Accept 26 3.5.2 Allow . 28 3.5.3 Call-ID 29
37、3.5.4 Contact 30 3.5.5 Content-Disposition . 30 3.5.6 Content-Length 30 3.5.7 Content-Type . 30 3.5.8 Cseq 36 3.5.9 Expires 36 3.5.10 From . 36 3.5.11 Max-Forwards 36 3.5.12 MIME-Version 36 3.5.13 Priority . 37 3.5.14 Record-Route 37 3.5.15 Route 37 3.5.16 To . 37 3.5.16.1 To Header Field for REGIST
38、ER . 37 3.5.16.1.1 To field for SUID (a(ii) and SGID registration 37 3.5.16.1.2 To field for Group Supplementary Data Interest (a(i) . 38 3.5.16.1.3 To field for FNE Group Supplementary Data Interest (c(i) . 38 3.5.16.1.4 To field for FNE Unit Supplementary Data Interest (c(ii),c(iii). 38 3.5.16.1.5
39、 To field for Group SD Monitoring Interest (b(i.1) 38 3.5.16.1.6 To field for FNE Group SD Monitoring Interest (b(i.2) 38 3.5.16.1.7 To field for Unit SD Monitoring Interest (b(ii), b(iii) . 38 3.5.16.1.8 To field for PD SN Context Registration 38 3.5.16.2 To Header Field for INVITE, CANCEL, ACK, an
40、d BYE 38 3.5.16.3 To Header Field for OPTIONS 38 3.5.16.4 To Header Field for MESSAGE 38 3.5.17 Via 38 3.5.18 Warning 39 3.6 STATUS-CODE AND REASON-PHRASE . 45 3.7 SDP ANNOUNCEMENTS . 45 3.7.1 SDP offer/answer usage . 45 3.7.2 SDP parameters encoding 46 3.7.2.1 Session-level part . 46 3.7.2.1.1 The
41、protocol version field 46 3.7.2.1.2 The origin field 46 3.7.2.1.3 The session name field . 47 3.7.2.1.4 The time field 47 3.7.2.1.5 The connection field 47 3.7.2.2 Media description part 47 3.7.2.2.1 The media announcement field . 47 3.7.2.2.2 Attributes fields . 47 3.7.3 SDP examples 48 3.7.3.1 SDP
42、 Offer with MutipleMultiple Vocoder Modes Being Offered . 48 3.7.3.2 SDP Offer in Older RFSS Implementations . 49 3.8 X-TIA-P25-ISSI BODY PARAMETERS 49 3.8.1 Group Service Profile attributes . 50 3.8.1.1 Access Permission (g -access) 52 3.8.1.2 Announcement Group (g -agroup) 52 3.8.1.3 Priority (g-p
43、ri) 52 3.8.1.4 Emergency Capable (g -ecap) 53 3.8.1.5 Emergency Preemption (g -eprempt) 53 3.8.1.6 RF Hang Time (g -rfhangt) 54 3.8.1.7 Confirmed Call Setup Time (g -ccsetupT) 54 3.8.1.8 Interrupt Mode (g-intmode) . 55 TIA-102.BACA-B-2 v3.8.1.9 Group Security Level (g-sec) 55 3.8.1.10 Interconnect F
44、lag (g-ic). 56 3.8.1.11 Interconnect Security (g-icsecstart) . 56 3.8.1.12 Group Alias (g-alias) 56 3.8.1.13 Manufacturer Specific (g-man) 57 3.8.1.14 Example Group Service Profiles 58 3.8.1.14.1 Fully Specified Example 58 3.8.1.14.2 Minimum Group Service Profile 58 3.8.2 User Service Profile attrib
45、utes . 58 3.8.2.1 System Access Permission (u -access) 61 3.8.2.2 Duplexity (u-dup) . 61 3.8.2.3 Secure Capable (u-sec) . 62 3.8.2.4 Group Call Permissions (u -gcall) 62 3.8.2.5 Unit-to-unit Call Permissions (u -ucall) 62 3.8.2.6 Unit-to-unit Call Priority (u-upri) 63 3.8.2.7 Interconnect Permission
46、s (u -iccall) 63 3.8.2.8 Interconnect Security (u-icsec) 64 3.8.2.9 Interconnect Call Priority (u-icpri) 64 3.8.2.10 Authentication Type/Capability (u-authtype) . 65 3.8.2.11 Authentication Policy (u-authpol) 65 3.8.2.12 Authentication Parameters (u -authparm) 66 3.8.2.13 Availability Check Attribut
47、e (u-availcheck) . 67 3.8.2.14 Call Set-Up Preference Attribute (u-prefsetup) 68 3.8.2.15 Radio Inhibit (u-radinhib) . 68 3.8.2.16 Packet Data Capable (u-packetdata) 69 3.8.2.17 SU Alias (u-alias) . 69 3.8.2.18 Manufacturer Specific Attributes (u-man) 70 3.8.2.19 Example User Service Profiles 70 3.8
48、.2.19.1 Fully Specified Profile . 70 3.8.2.19.2 Minimal User Service Profile (With Authentication) . 72 3.8.3 RFSS Service CapabiltyCapability Profile attributes. 72 3.8.3.1 Encrypted SU-to-SU Call Capability (r-ucall-sec) 72 3.8.3.2 Clear SU-to-SU Call Capability (r-ucall-clear) . 72 3.8.3.3 Encryp
49、ted Group Call Capability (r-gcall-sec) . 73 3.8.3.4 Clear Group Call Capability (r-gcall-clear) 73 3.8.3.5 Encrypted Confirmed Group Call Capability (r -gcall-econf). 73 3.8.3.6 Clear Confirmed Group Call Capability (r -gcall-cconf) 74 3.8.3.7 SD Emergency Alarm Capability (r -sd-ealarm) 74 3.8.3.8 SD Emergency Alarm Cancel Capability (r-sd-ealarmc) . 74 3.8.3.9 SD Group Emergency Cancel Capability (r -sd-egroupc) 75 3.8.3.10 SD Call Alert Capability (r-sd-calert) 75 3.8.3.11 SD Short Message Capability (r-sd-smsg) . 75 3.8.3.12 SD Status Query Capability (r-sd-sq
