1、 TIA-1135-2009 APPROVED: JANUARY 1, 2009 REAFFIRMED: DECEMBER 2, 2013 TIA-1135 January 2009Inter-Technology Handoff for Ultra Mobile Broadband (UMB) Radio Access Network Interfaces NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunde
2、rstandings 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 of such Standards and Publications shall not in any resp
3、ect 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 members, either domestically or internationally. Standards and
4、 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 adopting the Standard or Publication. This Standard does no
5、t 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 applicability of regulatory limitations before its use. (From Pr
6、oject No. 3-0286-RF1, formulated under the cognizance of the TIA TR-45 Mobile (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
7、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 more parties. TIA makes no search or investigation for IPR. When IPR consisting of patents and publis
8、hed 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, and disclaims any obligation to investigate or inquire into, the scope or validity of any claims of
9、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 conditions are reasonable or non-discriminatory. TIA does not warrant or represent that procedures or
10、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 another organization (“other SSO”) engaged in the formulation, development or publication of standards
11、(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 Manual, 4thedition) then (i) TIA disclaims any duty or obligation to search or investigate the records of an
12、y 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 Essential Patent(s) and published pending patent applications shall apply; and (iii) Information as to claims of I
13、PR 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 or monitor compliance with the contents of the Document. TIA does not certify, inspect, test or otherwise inv
14、estigate 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 PURP
15、OSE 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 AND MAKES NO REPRESENTATIONS OR WARRANTIES REGARDING THE CONTENTS COMPLIANCE WITH ANY APPLICABLE STATUTE, RU
16、LE 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 LIABLE FOR ANY AND ALL DAMAGES, DIRECT OR INDIRECT, ARISING FROM OR RELATING TO ANY USE OF THE CONTENTS CONTAI
17、NED 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), WHETHER BASED UPON BREACH OF CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR
18、 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 PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. TIA-1135 i Table of Contents 1 Foreword iv 2 1 Introduction.1-1 3 1
19、.1 Overview.1-1 4 1.1.1 Purpose1-1 5 1.1.2 Scope.1-1 6 1.1.3 Document Convention 1-1 7 1.2 References.1-1 8 1.2.1 Normative References.1-1 9 1.3 Terminology1-2 10 1.3.1 Acronyms1-2 11 1.4 UMB IOS Inter-Technology Architecture Reference Model1-4 12 1.4.1 Architecture Reference Model (UMB to HRPD) .1-
20、4 13 1.4.1.1 Network Element Functional Descriptions.1-5 14 1.4.1.1.1 HRPD AN/PCF-lite 1-5 15 1.4.1.1.2 Interworking Security Function1-6 16 1.4.2 Architecture Reference Model (HRPD to UMB Handoff) .1-6 17 1.4.2.1 Network Element Functional Descriptions.1-6 18 1.4.2.1.1 UMB eBS-lite.1-6 19 1.4.2.1.2
21、 Interworking Security Function1-6 20 1.4.3 Architecture Reference Model (UMB VoIP to 1x Circuit Voice Handoff)1-6 21 1.4.3.1 Network Element Functional Descriptions.1-7 22 1.4.3.1.1 1x BS-lite1-7 23 1.4.3.1.2 IWS Function1-7 24 1.4.4 Protocol Interface Descriptions.1-7 25 1.4.4.1 HRPD Packet Tunnel
22、ing over IP Interface .1-7 26 1.4.4.2 UMB Packet Tunneling over IP Interface.1-8 27 1.4.4.3 1x Signaling Message Tunneling over IP Interface 1-8 28 1.5 Feature Descriptions .1-8 29 1.5.1 Explicitly Supported Features.1-8 30 1.5.1.1 Pre-setup and Handoff from UMB to HRPD1-8 31 1.5.1.2 Pre-setup and H
23、andoff from HRPD to UMB1-8 32 1.5.1.3 Hard Handoff of a VoIP Call from UMB to 1x circuit Voice Call.1-8 33 2 UMB IOS Interfaces .2-1 34 2.1 UMB to HRPD Handoff Procedures.2-1 35 2.1.1 Subnet Provisioning of HRPD AN/PCF-lite and Advertisement by UMB eBS.2-1 36 TIA-1135 ii 2.1.1.1 Advertisement by UMB
24、 eBS 2-1 1 2.1.1.2 Subnet Provisioning of HRPD AN/PCF-lite.2-1 2 2.1.2 HPRD Packet Tunneling over IP Interface.2-1 3 2.1.2.1 HRPD Packet Tunneling over IP Interface Network/Transport Protocol.2-1 4 2.1.2.1.1 Requirements for Access Terminal 2-1 5 2.1.2.1.2 Requirements for Access Network .2-2 6 2.1.
25、3 HRPD A9 and A11 Messaging.2-2 7 2.1.3.1 A9 Message Changes2-2 8 2.1.3.1.1 A9 Indicators 2-2 9 2.1.3.2 A11 Message Changes2-3 10 2.1.3.2.1 NVSE2-3 11 2.2 HRPD to UMB Handoff Procedures.2-3 12 2.2.1 Usage of LLT Interface for UMB Packet Tunneling over IP .2-3 13 2.2.2 LLT Procedure2-4 14 2.3 Handoff
26、 of UMB VoIP to 1x Circuit Voice Procedure 2-5 15 2.3.1 CSNA over IP .2-5 16 2.3.2 A1/A1p and A21 Interfaces 2-5 17 3 Inter-Technology Handoff Call Flows3-1 18 3.1 UMB to HRPD Handoff .3-1 19 3.1.1 UMB to HRPD Handoff to Regular HRPD AN .3-1 20 3.1.1.1 Handoff to Regular HRPD AN with Session Control
27、 in AN3-1 21 3.1.1.2 Handoff to Regular HRPD AN with Session Control in PCF 3-4 22 3.1.2 UMB to HRPD Handoff to AN/PCF-lite3-7 23 3.1.2.1 UMB to HRPD Handoff to AN/PCF-lite with Session Control in AN.3-7 24 3.1.2.2 UMB to HRPD Handoff to AN/PCF-lite with Session Control in PCF .3-11 25 3.1.3 UMB to
28、HRPD Handoff with AN/PCF-lite and A16 Interface 3-15 26 3.1.4 UMB to HRPD Handoff with AN/PCF-lite and A16 Interface in PMIP Case.3-19 27 3.2 HRPD to UMB Handoff .3-24 28 3.2.1 HRPD to UMB Handoff Call Flow 3-24 29 3.3 UMB VoIP to 1x Voice Handoff3-27 30 3.3.1 UMB VoIP to 1x Voice Handoff in Case of
29、 Collocated IWS and 1xBS3-28 31 3.3.2 UMB VoIP to 1x Voice Handoff in Case of Collocated IWS and BS-lite .3-30 32 33 TIA-1135 iii Table of Figures 1 2 Figure 1.4.1-1 UMB to HRPD IOS Handoff Architecture Based on A.S0008 .1-4 3 Figure 1.4.1-2 UMB to HRPD IOS Handoff Architecture (with HRPD AN/PCF-lit
30、e) Based on A.S0008 4 .1-4 5 Figure 1.4.1-3 UMB to HRPD IOS Handoff Architecture Based on A.S0009 .1-5 6 Figure 1.4.1-4 UMB to HRPD IOS Handoff Architecture (with HRPD AN/PCF-lite) Based on A.S0009 7 .1-5 8 Figure 1.4.2-1 HRPD to UMB IOS Handoff Architecture Reference Model .1-6 9 Figure 1.4.3-1 UMB
31、 VoIP to 1x Circuit Voice IOS Handoff Architecture Reference Model 1-7 10 Figure 2.2.1-1 Transport Protocol for HPRD to UMB Handoff2-4 11 Figure 3.1.1.1-1 UMB to HRPD Handoff to Regular HRPD AN - SC in AN .3-2 12 Figure 3.1.1.2-1 UMB to HRPD Handoff to Regular HRPD AN - SC in PCF3-5 13 Figure 3.1.2.
32、1-1 UMB to HRPD Handoff to HRPD AN/PCF-lite - SC in AN 3-9 14 Figure 3.1.2.2-1 UMB to HRPD Handoff to HRPD AN/PCF-lite - SC in PCF.3-12 15 Figure 3.1.3-1 UMB to HRPD Handoff with HRPD AN/PCF-lite and A16 Interface .3-17 16 Figure 3.1.4-1 UMB to HRPD Handoff with HRPD AN/PCF-lite and A16 Interface in
33、 PMIP Case (Part 17 A Pre-handoff Setup) .3-20 18 Figure 3.1.4-2 UMB to HRPD Handoff with HRPD AN/PCF-lite and A16 Interface in PMIP Case (Part 19 B Post-handoff Steps) 3-21 20 Figure 3.2.1-1 HRPD to UMB Handoff 3-26 21 Figure 3.3.1-1 UMB VoIP to 1x Voice Call Handoff for Collocated IWS and 1xBS.3-2
34、8 22 Figure 3.3.2-1 UMB VoIP to 1x Voice Call Handoff for Collocated IWS and BS-lite 3-30 23 24 25 TIA-1135 iv Foreword 1 (This foreword is not part of this Standard.) 2 This document describes the protocols and procedures to support inter-technology handoff between Ultra 3 Mobile BroadbandTM(UMBTM)
35、1and other technologies. 4 5 Revision History Date Publication Description July 2008 A.S0021-0 v1.0 For features supported, refer to section 1.1. 6 7 1Ultra Mobile BroadbandTMand (UMBTM) are trade and service marks owned by the CDMA Development Group (CDG). TIA-1135 1-1 1 Introduction 1 2 1.1 Overvi
36、ew 3 This document includes a description of the interface protocols and procedures to support the following 4 features and functions. 5 Features and functions explicitly supported in this standard: 6 Pre-setup and handoff from UMB to HRPD 7 Pre-setup and handoff from HRPD to UMB 8 Hard handoff of a
37、 VoIP Call from UMB to 1x circuit voice call 9 10 1.1.1 Purpose 11 The purpose of this document is to provide a standard and call flows for inter-technology handoff 12 between UMB and other access technologies. The protocols and procedures in this specification assume 13 that the access terminal (AT
38、) is capable of being logically associated with multiple access technologies 14 simultaneously but may not be able to transmit simultaneous in different access technologies. The 15 specification allows for initial setup of the target radio access network prior to over-the-air handoff thus 16 reducin
39、g the interruption in real-time services. Handoff of ATs with only delay-tolerant applications may 17 not require the protocols and procedures in this specification. 18 1.1.2 Scope 19 This document provides an interoperability specification between a RAN that supports UMB, the AT and 20 other access
40、 technologies. This document contains message procedures and formats necessary to obtain 21 this interoperability. 22 1.1.3 Document Convention 23 “Shall” and “shall not” identify requirements to be followed strictly to conform to the standard and from 24 which no deviation is permitted. “Should” an
41、d “should not” indicate that one of several possibilities is 25 recommended as particularly suitable, without mentioning or excluding others; that a certain course of 26 action is preferred but not necessarily required; or (in the negative form) that a certain possibility or 27 course of action is d
42、iscouraged but not prohibited. “May” and “need not” indicate a course of action 28 permissible within the limits of the standard. “Can” and “cannot” are used for statements of possibility 29 and capability, whether material, physical, or causal. 30 1.2 References 31 References are either normative o
43、r informative. A normative reference is used to include another doc-32 ument as a mandatory part of a 3GPP2 specification. Documents that provide additional non-essential in-33 formation are included in the informative references section. 34 1.2.1 Normative References 35 The following standards cont
44、ain provisions which, through reference in this text, constitute provisions of 36 this Standard. At the time of publication, the editions indicated were valid. All standards are subject to 37 revision, and parties to agreements based on this Standard are encouraged to investigate the possibility of
45、38 TIA-1135 1-2 applying the most recent editions of the standards indicated below. ANSI and TIA maintain registers of 1 currently valid national standards published by them. 2 1 3GPP2 A.S0008-C v1.0, Interoperability Specification (IOS) for High Rate Packet Data 3 (HRPD) Radio Access Network Interf
46、aces with Session Control in the Access Network, July 4 2007. 5 2 3GPP2 A.S0009-C v1.0, Interoperability Specification (IOS) for High Rate Packet Data 6 (HRPD) Radio Access Network Interfaces with Session Control in the Packet Control Function, 7 July 2007. 8 3 3GPP2 A.S0020-0 v2.0, Interoperability
47、 Specification (IOS) for Ultra Mobile Broadband 9 (UMB) Radio Access Network Interfaces, July 2008. 10 4 3GPP2 C.S0024-B v2.0, CDMA2000 High Rate Packet Data Air Interface Specification, 11 March 2007. 12 5 3GPP2 C.S0084-0 v2.0, Ultra Mobile Broadband (UMB) Air Interface Specification, August 13 200
48、7. 14 6 3GPP2 X.S0011-D v1.0, Wireless IP Network Standard, February 2006. 15 7 3GPP2 X.S0042-0 v1.0, Voice Call Continuity between IMS and Circuit Switched Systems, 16 October 2007. 17 8 3GPP2 X.S0054-0 v1.0, CAN Wireless IP Network Specification, December 2007. 18 9 IETF RFC 1661, Point to Point P
49、rotocol, July 1994. 19 10 IETF RFC 1865, Remote Authentication Dial In User Service (RADIUS), June 2000. 20 11 IETF RFC 1994, PPP Challenge Handshake Authentication Protocol (CHAP), August 1996. 21 12 IETF RFC 3344, IP mobility Support for IPv4, August 2002. 22 1.3 Terminology 23 24 1.3.1 Acronyms 25 3GPP2 3rdGeneration Partnership Project 2 AAA Authentication, Authorization and Accounting AGW Access Gateway AN Access Network ANRI Access Network Route Instance AT Access Terminal ATI Access Terminal Identifier BS Base Station CANID Current Access Network Identi
