1、 TIA-102.BAEF November 2013Project 25 Packet Data Host Network Interface ANSI/TIA-102.BAEF-2013 APPROVED: NOVEMBER 26, 2013 NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilita
2、ting 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 of such Standards and Publications shall not in any respect preclude any member or non-member of TIA from manufac
3、turing 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 members, either domestically or internationally. Standards and Publications are adopted by TIA in accordance with the A
4、merican 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 adopting the Standard or Publication. This Standard does not purport to address all safety problems associated with
5、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 applicability of regulatory limitations before its use. (From Project No. ANSI/TIA-PN-102.BAEF, formulated under the cogn
6、izance of the TIA TR-8 Mobile and Personal Private Radio Standards, TR-8.5 Subcommittee on Signaling and Data Transmission). 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 p
7、resent 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 property rights (“IPR”), including pending or issued patents, or copyrights, owned
8、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 is requested, all in accordance with the Manual. TIA takes no position with ref
9、erence 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 the parties involved, nor will TIA opine or judge whether proposed licensing
10、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. If the Document contains one or more Normative References to a document publi
11、shed 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 of mandatory, alternate or optional elements (as defined in the TIA Engineeri
12、ng 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 encouragement of voluntary disclosure (see Engineering Manual Section 6.5.1) of Ess
13、ential 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 applications. TIA does not enforc
14、e 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, INCLUDING WITHOUT LIMITATION, ANY A
15、ND 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 THE ACCURACY OF THE CONTEN
16、TS 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 CONTENTS. TIA SHALL NOT BE
17、 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 PROFITS, LITIGATION, OR THE LIKE
18、), 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 THESE CONTENTS WOULD NOT BE
19、 PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. TIA-102.BAEF i Foreword (This foreword is not part of this document.) This document has been created in response to a request by the APCO/NASTD/FED1Project 25 Steering Committee as provided for in a Memorandum of Understanding (MOU) dated April 1992 and am
20、ended December 1993. The MOU states APCO/NASTD/FED shall devise a Common System Standard for digital public safety 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 technica
21、l assistance in the development of documentation for the Standard. If the abbreviation “P25” or the wording “Project 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 a
22、ppearance 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 should not be interpreted as limiting the applicability of the information contained in any document to “P25” or “Project 25” implementations exclusiv
23、ely. This document provides a specification of the Packet Data Host Network Interface for TIA-102 Packet Data. This document was developed by the TIA TR-8.5 Signaling and Data Transmission Subcommittee based on materials originated by the APCO Project 25 Interface Committee (APIC) Data Task Group (D
24、TG). The 1stedition (Original) of this document provides a standalone document for the Packet Data Host Network Interface based on material originally published in TIA-102.BAEB-A. This document cancels and replaces the material specific to the Packet Data Host Network Interface in TIA-102.BAEB-A. Th
25、e TIA makes no claims as to the applicability of the information contained in this document for any purpose although it is believed that the information will prove to be invaluable to manufacturers and operators of equipment based on the TIA-102 series of documents. Some aspects of the specification
26、s contained in this document may not have been fully operationally tested; however, a great deal of time and good faith effort has been invested in the preparation of this document to ensure the accuracy of the information it contains. 1APCO/NASTD/FED is an abbreviation for the Association of Public
27、-Safety Communications Officials (APCO), the National Association of State Telecommunications Directors (NASTD), and the various agencies of the Federal government (FED). TIA-102.BAEF ii Patent Identification The readers attention is called to the possibility that compliance with this document may r
28、equire 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 t
29、o grant 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 T
30、IA 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. TIA-102.BAEF iii Table of Contents 1. Introduction . 1 1.1 Scope . 1 1.2 References
31、 . 1 1.2.1 Normative References 1 1.2.2 Informative References 2 1.3 Acronyms and Abbreviations 2 1.4 Definitions . 2 2. Architecture 3 2.1 Ethernet Protocol 3 2.2 IEEE 802.3 Protocol . 4 2.3 Network Layer Procedures . 4 2.4 Network Layer Payload 4 2.4.1 Data Application Information 4 2.4.2 Control
32、Signaling 5 TIA-102.BAEF iv List of Figures Figure 1 Ethernet EdInterface Stack Diagram 3 Figure 2 IEEE 802 EdInterface Stack Diagram 4 List of Tables Table 1 EdInterface Protocol Combinations 3 TIA-102.BAEF v Revision History Version Date Description Original 11/11/2013 Packet Data Host Network Int
33、erface specification based on material originally published in TIA-102.BAEB-A; adopted by the Project 25 Steering Committee November 1st2013 as part of the Project 25 Standard TIA-102.BAEF vi This page intentionally left blank TIA-102.BAEF 1 1. Introduction The objective of this document is to provi
34、de a specification of the Packet Data Host Network Interface which is designated as the EdInterface in 6. The term “EdInterface” is used throughout the remainder of this document as a short form of “Packet Data Network Interface” and has equivalent meaning. 1.1 Scope This document specifies the prot
35、ocols utilized on the EdInterface. The information necessary to enable interoperable services and functionality on this interface is provided in this document or referenced in other documents as appropriate. This document assumes the reader has a good working knowledge of the Data Overview and Speci
36、fication 6. 1.2 References The 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.” 1.2.1 Normative References The following documents contain provisions
37、 that, through reference in this text, constitute provisions of this document. At the time of publication, the editions indicated were valid. All documents are subject to revision, and parties to agreements based on this document are encouraged to investigate the possibility of applying the most rec
38、ent editions of the documents indicated below. ANSI and TIA maintain registers of currently valid national standards published by them. 1 IEEE 802.2-1998, IEEE Standard for Information technology-Telecommunications and information exchange between systems-Local and metropolitan area networks-Specifi
39、c requirements-Part 2: Logical Link Control, IEEE (http:/standards.ieee.org/), 1998 2 IEEE 802.3-2000, IEEE Standard for Information technology-Telecommunications and information exchange between systems-Local and metropolitan area networks-Specific requirements-Part 3: Carrier Sense Multiple Access
40、 with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications, IEEE (http:/standards.ieee.org/), 2000 3 RFC 791, Internet Protocol, IETF (http:/www.rfc-editor.org/), September 1981 4 RFC 894, Standard for the Transmission of IP Datagrams Over Ethernet Networks, IETF (http:/www.
41、rfc-editor.org/), April 1984 5 RFC 1042, Standard for the Transmission of IP Datagrams Over IEEE 802 Networks, IETF (http:/www.rfc-editor.org/), February 1988 6 TIA-102.BAEA-B, Project 25 Data Overview and Specification, ANSI/TIA, June 2012 TIA-102.BAEF 2 1.2.2 Informative References 7 RFC 792, Inte
42、rnet Control Message Protocol, IETF (http:/www.rfc-editor.org/), September 1981 8 RFC 826, Ethernet Address Resolution Protocol: Or converting network protocol addresses to 48 bit Ethernet address for transmission on Ethernet hardware, IETF (http:/www.rfc-editor.org/), November 1982 1.3 Acronyms and
43、 Abbreviations ANSI American National Standards Institute APCO Association of Public-Safety Communications Officials DHN Data Host Network FED Various Agencies of the Federal Government FNE Fixed Network Equipment ICMP Internet Control Message Protocol IEEE Institute of Electrical and Electronics En
44、gineers IETF Internet Engineering Task Force IP Internet Protocol IPv4 IP version 4 NASTD National Association of State Telecommunications Directors P25 Project 25 RFC Request For Comments TIA Telecommunications Industry Association 1.4 Definitions DHN See definition in 6 EdInterface See definition
45、in 6 FNE See definition in 6 Local Policy See definition in 6 RFC # Request For Comments where # refers to a document number maintained by the IETF TIA-102.BAEF 3 2. Architecture This section specifies the architecture for the EdInterface with respect to the protocol combinations supported. The EdIn
46、terface supports the two (2) protocol combinations listed in Table 1 below. Table 1 EdInterface Protocol Combinations IPv4 over Ethernet IPv4 over IEEE 802.3 2.1 Ethernet Protocol This clause specifies the architecture for the Ethernet EdInterface. The stack diagram in Figure 1 below illustrates the
47、 protocol elements involved in the Edinterface endpoint entities. Figure 1 Ethernet EdInterface Stack Diagram The Ethernet Edinterface shall support IPv4 over Ethernet in accordance with the provisions of 4 and 3. EdFNE DHNPayloadIPv4Ethernet withRFC 894 encapsulationPayloadIPv4Ethernet withRFC 894
48、encapsulationTIA-102.BAEF 4 2.2 IEEE 802.3 Protocol This clause specifies the architecture for the IEEE 802.3 EdInterface. The stack diagram in Figure 2 below illustrates the protocol elements involved in the Edinterface endpoint entities. Figure 2 IEEE 802 EdInterface Stack Diagram The IEEE 802.3 E
49、dinterface shall support IPv4 over IEEE 802.3/802.2 in accordance with the provisions of 1, 2, 5, and 3. 2.3 Network Layer Procedures The EdInterface network layer shall convey IPv4 datagrams per the provisions of 3 and as specified in clauses 2.1 and 2.2 above. The method of Ethernet/IEEE 802.3 IP address binding is beyond the scope of this document. IP addressing binding on the Edinterface is the subject of local policy and the policy of the organization that provides the DHN. A common method of Ethernet/IEEE
