1、 TIA-102.BACF October 2009 Project 25 Inter-RF Subsystem Interface (ISSI) Messages and Procedures for Packet Data Services NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitat
2、ing 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 manufact
3、uring 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 Am
4、erican 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 i
5、ts 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 Standards Proposal No. 3-0372, formulated under the cognizan
6、ce of the TIA, TR-8 Mobile and Personal Private Radio Standards. TR-8.19 Subcommittee on Wireline System Interfaces). Published by TELECOMMUNICATIONS INDUSTRY ASSOCIATION Standards and Technology Department 2500 Wilson Boulevard Arlington, VA 22201 U.S.A. PRICE: Please refer to current Catalog of TI
7、A TELECOMMUNICATIONS INDUSTRY ASSOCIATION STANDARDS AND ENGINEERING PUBLICATIONS or call IHS USA and Canada (1-800-525-7052 ) International (303-790-0600) or search online at http:/www.tiaonline.org/standards/catalog/ All rights reserved Printed in U.S.A. NOTICE OF COPYRIGHT This document is copyrig
8、hted by the TIA. Reproduction of these documents either in hard copy or soft copy (including posting on the web) is prohibited without copyright permission. For copyright permission to reproduce portions of this document, please contact TIA Standards Department or go to the TIA website (www.tiaonlin
9、e.org) for details on how to request permission. Details are located at: http:/www.tiaonline.org/standards/catalog/info.cfm#copyright OR Telecommunications Industry Association Standards (b) there is no assurance that the Document will be approved by any Committee of TIA or any other body in its pre
10、sent 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 by
11、 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 refer
12、ence 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 te
13、rms 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 publish
14、ed 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 Engineering
15、 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 Essen
16、tial 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 enforce
17、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 AND
18、 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 CONTENTS
19、 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 L
20、IABLE 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),
21、 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 P
22、UBLISHED BY TIA WITHOUT SUCH LIMITATIONS. TIA-102.BACF i Foreword (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 (MOU) dated December, 1993. This M
23、OU 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.19 (Wireline Interfaces) with in
24、puts from the APCO Project 25 Interface Committee (APIC), the APIC Data Task Group, 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. This document defines an Inter-RF Su
25、bsystem Interface (ISSI) for Project 25 supporting Project 25-defined trunked Packet Data Services. The ISSI is the interface between Radio Frequency Subsystems (RFSSs) enabling relevant Project 25 user requirements to be satisfied (e.g., as described in the Inter-RF Subsystem Interface Overview (TS
26、B-102.BACC-A). Future related standardization efforts are planned to develop new TIA standards defining protocols for an ISSI supporting Project 25-defined conventional Packet Data Services. In addition, future associated standardization efforts are planned to develop new TIA standards defining comp
27、liance tests (e.g., conformance tests, measurement methods, performance recommendations, and interoperability tests) applicable to equipment implementing the Project 25 ISSI protocols defined in this and future related TIA standards. TIA-102.BACF ii Patent Identification The readers attention is cal
28、led 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 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
29、identified have, we believe, filed statements of willingness to 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 intellec
30、tual property rights policy: No patents have been identified. TIA 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 Identifica
31、tion The following trademarks are referenced in this specification: (None) TIA-102.BACF iii TABLE OF CONTENTS 1. INTRODUCTION .1 1.1 SCOPE 1 1.2 TERMINOLOGY .2 1.3 DOCUMENT STRUCTURE .2 1.4 DEFINITIONS .2 1.5 ABBREVIATIONS.5 1.6 REFERENCES.7 1.6.1 Normative References7 1.6.2 Informative References7
32、2. OVERVIEW OF ARCHITECTURE AND PROTOCOL SUITE 9 2.1 ARCHITECTURE OVERVIEW9 2.1.1 P25 Packet Data Service Model10 2.1.2 ISSI Packet Data Services Model13 2.1.2.1 Context Activation . 13 2.1.2.2 IP Address Assignment for Roaming SU and Associated MDPs. 15 2.1.2.3 Packet Data ISSI Link Maintenance 15
33、2.1.2.4 Transport of Packet Data between RFSSs 16 2.1.2.5 Mobility Management of Packet Data Capable SUs 17 2.1.3 Subsystem Topologies20 2.1.4 Functional Model 22 2.1.4.1 Mobility Management 23 2.1.4.2 Packet Data Service . 23 2.1.5 Service Access Point Model.24 2.1.5.1 Mobility Management SAP 26 2.
34、1.5.2 Packet Data SAP 27 2.1.5.2.1 PD Registration Transaction. 28 2.1.5.2.2 PD IP Packet Transaction . 29 2.2 ISSI INTERNET PROTOCOL SUITE.30 2.2.1 Lower Layers.30 2.2.2 Network Layer .30 2.2.3 Transport Layer.31 2.2.4 Application Layer31 2.3 ISSI DATA TRANSMISSION ORDER.31 3. MESSAGES AND PARAMETE
35、RS DEFINITION FOR ISSI32 3.1 SIP MESSAGES AND PARAMETERS DEFINITION .32 3.2 MIPV4 MESSAGES AND PARAMETERS DEFINITION .32 3.2.1 MIPv4 Registration Request33 3.2.1.1 Simultaneous Bindings (S bit) 33 3.2.1.2 Decapsulation by Mobile Node (D bit) 34 3.2.1.3 Minimal Encapsulation (M bit) 34 3.2.1.4 GRE En
36、capsulation (G bit) 34 3.2.1.5 Reverse Tunneling (T bit) 34 3.2.1.6 Lifetime 34 3.2.1.7 Home Address 34 3.2.1.8 Home Agent. 34 3.2.1.9 Care-of Address . 34 3.2.1.10 Identification 35 3.2.1.11 Extensions 35 3.2.2 MIPv4 Registration Reply .35 3.2.2.1 Lifetime 35 3.2.2.2 Home Address 35 TIA-102.BACF iv
37、 3.2.2.3 Home Agent. 35 3.2.2.4 Identification 36 3.2.2.5 Extensions 36 3.2.2.6 Codes . 36 4. PACKET DATA MOBILITY MANAGEMENT PROCEDURES 37 5. PACKET DATA SERVICES ACCESS POINT MODELS 38 5.1 REGISTRATION PRIMITIVES . 38 5.2 IP DATAGRAM PRIMITIVES 41 5.3 PD-SAP STATE MODEL: SERVING RFSS . 43 5.3.1 St
38、ate Model Description . 44 5.3.1.1 Initial State. 44 5.3.1.2 Registering State 44 5.3.1.2.1 Successful Registration Reply 44 5.3.1.2.2 Unsuccessful Registration Reply 44 5.3.1.2.3 IP Datagram 44 5.3.1.3 Registered State . 44 5.3.1.3.1 Registration Renewal Request 44 5.3.1.3.2 Successful Registration
39、 Renewal Response 45 5.3.1.3.3 Unsuccessful Registration Renewal Response . 45 5.3.1.3.4 Inbound IP Datagram 45 5.3.1.3.5 Outbound IP Datagram. 45 5.3.1.3.6 Deregistration Request . 45 5.3.1.4 DeRegistering State . 45 5.3.1.4.1 Deregistration Response . 45 5.3.1.4.2 IP Datagrams 45 5.3.2 State Model
40、 Summary. 46 5.4 PD-SAP STATE MODEL: HOME RFSS 48 5.4.1 State Model Description . 48 5.4.1.1 Initial State. 48 5.4.1.2 Registering State 49 5.4.1.2.1 Successful Registration Response 49 5.4.1.2.2 Unsuccessful Registration Response 49 5.4.1.2.3 IP Datagrams 49 5.4.1.3 Registered State . 49 5.4.1.3.1
41、Registration Renewal Request 49 5.4.1.3.2 Successful Registration Renewal Response 50 5.4.1.3.3 Unsuccessful Registration Renewal Response . 50 5.4.1.3.4 Inbound IP Datagram 50 5.4.1.3.5 Outbound IP Datagram. 50 5.4.1.3.6 Deregistration Request . 50 5.4.1.4 Deregistering State. 50 5.4.1.4.1 Deregist
42、ration Response . 50 5.4.1.4.2 IP Datagrams 51 5.4.2 State Model Summary. 51 6. PROCEDURES FOR ISSI PACKET DATA SERVICES 53 6.1 OVERVIEW53 6.2 BASIC PROCEDURES FOR MIPV4 TUNNEL MANAGEMENT AND DATAGRAM TRANSFER53 6.2.1 Setting Up MIPv4 Tunnels 53 6.2.1.1 MIPv4 Registration Request 53 6.2.1.2 MIPv4 Re
43、gistration Reply . 54 6.2.2 Removing MIPv4 Tunnels 55 6.2.3 Datagram Transfer.56 6.2.3.1 Datagram Transfer at the Serving RFSS 56 6.2.3.2 Datagram Transfer at the Home RFSS. 56 6.3 PACKET DATA ISSI PROCEDURES . 57 6.3.1 SU Initiated SNDCP Context Activation 57 6.3.1.1 Actions Required at Serving RFS
44、S 57 TIA-102.BACF v 6.3.1.2 Actions Required at Home RFSS. 58 6.3.2 Home RFSS Initiated SNDCP Context Activation.58 6.3.2.1 Actions Required at Home RFSS. 58 6.3.2.2 Actions Required at Serving RFSS 58 6.3.3 SU Initiated SNDCP Context Deactivation.59 6.3.3.1 Actions Required at Serving RFSS 59 6.3.3
45、.2 Actions Required at Home RFSS. 59 6.3.4 Serving RFSS Initiated SNDCP Context Deactivation59 6.3.5 Home RFSS Initiated SNDCP Context Deactivation 60 6.3.5.1 Actions Required at Home RFSS. 60 6.3.5.2 Actions Required at Serving RFSS 60 6.3.6 Home RFSS Initiated SNDCP Context Query .60 6.3.6.1 Actio
46、ns Required at Home RFSS. 60 6.3.6.2 Actions Required at Serving RFSS 60 6.3.7 Serving RFSS Initiated SNDCP Context Query 61 6.3.7.1 Actions Required at Serving RFSS 61 6.3.7.2 Actions Required at Home RFSS. 61 6.3.8 SNDCP Context Transfer 61 6.3.8.1 Actions Required at New Serving RFSS 61 6.3.8.2 A
47、ctions Required at Home RFSS. 62 6.3.8.3 Actions Required at Previous Serving RFSS . 63 6.3.9 Registration Renewal 63 ANNEX A (INFORMATIVE) MESSAGE SEQUENCE DIAGRAMS 64 A.1 SU INITIATED SNDCP CONTEXT ACTIVATION.65 A.2 HOME RFSS INITIATED SNDCP CONTEXT ACTIVATION.67 A.3 SU INITIATED SNDCP CONTEXT DEA
48、CTIVATION 68 A.4 HOME RFSS INITIATED SNDCP CONTEXT DEACTIVATION 70 A.5 SNDCP CONTEXT QUERY .71 A.6 SNDCP CONTEXT TRANSFER72 A.7 MIPV4 REGISTRATION RENEWAL 75 A.8 MIPV4 REGISTRATION RENEWAL DURING AN SNDCP CONTEXT TRANSFER 76 TIA-102.BACF vi Table of Figures FIGURE 1 SIMPLE ISSI P25 PACKET DATA SERVI
49、CE MODEL: ES TO MDP. 10 FIGURE 2 - SIMPLE ISSI P25 PACKET DATA SERVICE MODEL: ES TO SU. 11 FIGURE 3 PACKET DATA ISSI ARCHITECTURE TERMINOLOGY . 13 FIGURE 4 REGISTRATION AND CONTEXT ACTIVATION 14 FIGURE 5 ISSI IP ADDRESS REALM EXAMPLE 16 FIGURE 6 MOBILITY MANAGEMENT OF PACKET DATA 18 FIGURE 7 MOBILITY MANAGEMENT OF PACKET DATA WHILE TRANSFERRING IP DATAGRAMS.19 FIGURE 8 MULTIPLE SOURCE / MULTIPLE DESTINATION / MULTIPLE APN EXAMPLE . 20 FIGURE 9 MULTIPLE SOURCE / MULTIPLE DESTINATION / SINGLE APN EXAMPLE 21 FIGURE 10 SU TO SU PACKET DATA SERVICE ON THE ISSI 22
