1、 TIA-1137.610-2009 APPROVED: JUNE 1, 2009 REAFFIRMED: DECEMBER 6, 2013 TIA-1137.610 June 2009UMB and HRPD/1x Interworking NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitati
2、ng 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 manufactu
3、ring 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 Ame
4、rican 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 it
5、s 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. 3-0291.610-RF1, formulated under the cognizance o
6、f 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 any editing process. The use or practice of contents of
7、 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 published pending patent applications are claimed and called
8、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 IPR. TIA will neither be a party to discussions of any
9、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 practices suggested or provided in the Manual have been
10、 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 (whether designated as a standard, specification, recom
11、mendation 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 any other SSO for IPR or letters of assurance relating to
12、 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 IPR in the records or publications of the other SSO shal
13、l 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 investigate products, designs or services or any claims of
14、 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 PURPOSE OR USE, ITS MERCHANTABILITY AND ITS NONINFRINGEMENT
15、 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, RULE OR REGULATION, OR THE SAFETY OR HEALTH EFFECTS OF TH
16、E 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 CONTAINED HEREIN, INCLUDING WITHOUT LIMITATION ANY AND ALL IN
17、DIRECT, 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 OTHERWISE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
18、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. X.S054-610-0 v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38
19、 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 i ContentsUMB and HRPD/1x Interworking CONTENTS 1 Introduction1 1.1 Scope1 2 References2 2.1 Normative References2 2.2 Informative References4 3 Interworking Architecture5 3.1 UMB and HRPD/1x Interworking Architecture without Tunneli
20、ng5 3.2 UMB and HRPD Interworking Architecture through IP Tunneling 5 3.3 UMB and 1x Circuit Interworking Architecture through IP Tunneling.7 4 Target System Discovery .8 4.1 Local Domain Name Discovery.8 4.1.1 DHCPv4 Option 8 4.1.2 DHCPv6 Option 9 4.2 HRPD RAN/RAN-lite IP Address Resolution.9 4.3 U
21、MB RAN/RAN-lite IP Address Resolution 9 4.4 1x RAN/RAN-lite IP Address Resolution .10 4.5 UMB to HRPD Handoff ISF IP Address Resolution.10 4.6 HRPD to UMB Handoff ISF IP Address Resolution.11 4.7 UMB to 1x Handoff ISF IP Address Resolution11 5 IPsec Tunnel Operation12 5.1 Tunnel Establishment.12 5.1
22、.1 AT Requirements.12 5.1.2 ISF Requirements 12 5.1.3 HAAA Requirements 13 6 CMIPv4 Based Approach.14 6.1 Common Requirements .14 6.1.1 AGW Requirements 14 6.1.2 HA Requirements 14 6.1.3 AAA Requirements .14 6.2 Requirements for handoff from UMB to HRPD14 6.2.1 AT Requirements.14 6.2.2 PDSN Requirem
23、ents15 6.3 Requirements for handoff from HRPD to UMB15 6.3.1 AT Requirements.15 6.3.2 PDSN Requirements15 7 CMIPv4/PMIPv4 Based Approach 16 X.S0054-610-0 v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
24、51 52 53 54 55 56 57 58 59 60 Contents ii 7.1 Common Requirements16 7.1.1 AGW Requirements.16 7.1.2 HA Requirements 16 7.1.3 AAA Requirements .16 7.2 Requirements for handoff from UMB to HRPD16 7.2.1 AT Requirements.16 7.2.2 PDSN Requirements17 7.3 Requirements for handoff from HRPD to UMB17 7.3.1 A
25、T Requirements.17 7.3.2 PDSN Requirements17 8 PMIP Based Approach .18 8.1 Requirements for Handoff from UMB to HRPD .18 8.1.1 AT Requirements.18 8.1.2 AGW Requirements.18 8.1.3 PDSN Requirements19 8.1.4 HA Requirements 21 8.1.5 LMA Requirements .21 8.1.6 AAA Requirements .21 8.2 Requirements for Han
26、doff from HRPD to UMB .21 8.2.1 AT Requirements.21 9 Call Flows 22 9.1 ISF Discovery 22 9.2 Handoff Session Pre-setup overview call flow through L3 tunneling23 9.2.1 UMB to HRPD Handoff 23 9.2.2 HRPD to UMB Handoff 24 9.3 IPsec Tunnel Establishment .25 9.4 CMIP Based Approach Call Flow28 9.4.1 CMIP
27、Based Approach Active Handoff from UMB to the HRPD AN 28 9.4.2 CMIP Based Approach Active Handoff from UMB to HRPD through HRPD AN-Lite31 9.4.3 CMIP Based Approach Active Handoff from HRPD to UMB through UMB AN-Lite/eBS34 9.5 CMIP/PMIP Based Approach Call flow 37 9.5.1 CMIP/PMIP Based Approach Activ
28、e Handoff through HRPD AN-Lite.37 9.5.2 CMIP/PMIP Based Approach Active Handoff to HRPD AN40 9.5.3 PMIP/CMIP Based Approach Active Handoff from HRPD to UMB through UMB RAN-Lite/eBS .43 9.6 PMIP Based Approach Call flow.45 9.6.1 PMIP Based Call Flow for Active Handoff through HRPD RAN-Lite using AGW-
29、PDSN Interface.45 9.6.2 PMIP Based Call Flow for Active Handoff through HRPD RAN-Lite.52 9.6.3 PMIP Based Approach Active Handoff from HRPD to UMB through UMB RAN-Lite/eBS .58 X.S054-610-0 v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 3
30、9 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 iii List of FiguresLIST OF FIGURES Figure 1 Architecture for Interworking between UMB and HRPD/1x packet without Tunneling5 Figure 2 UMB-HRPD Interworking Architecture (From UMB to HRPD).6 Figure 3 HRPD-UMB Interworking Architecture (F
31、rom HRPD to UMB).6 Figure 4 UMB-1x Circuit Interworking Architecture (From UMB to 1x Circuit)7 Figure 5 ISF Discovery .22 Figure 6 UMB-HRPD handoff Session Pre-setup overview call flow23 Figure 7 HRPD-UMB handoff Session Pre-setup overview call flow24 Figure 8 Tunnel establishment flow26 Figure 9 CM
32、IP Based Approach UMB-HRPD Handoff.29 Figure 10 CMIP Based Approach UMB-HRPD Handoff.32 Figure 11 CMIP Based Approach HRPD-UMB Handoff.35 Figure 12 CMIP/PMIP Based Approach UMB to HRPD Handoff (with HRPD AN-Lite) 38 Figure 13 CMIP/PMIP Based Approach UMB to HRPD Handoff to HRPD AN 41 Figure 14 PMIP/
33、CMIP Based Approach HRPD to UMB Handoff.43 Figure 15 PMIP based UMB to HRPD Interworking using AGW-PDSN Interface (PDSN buffering)46 Figure 16 PMIP based UMB to HRPD Interworking using AGW-PDSN Interface (AGW buffering)50 Figure 17 PMIP based UMB to HRPD Interworking .53 Figure 18 IPv4 Addressing56
34、Figure 19 IPv6 Addressing57 Figure 20 PMIP Based Approach HRPD-UMB Handoff .58 X.S0054-610-0 v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 List of Tables iv LIST OF TABLE
35、S NoneX.S054-610-0 v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 v Revision HistoryREVISION HISTORY Revision Date Remarks 0 v1.0 August, 2008 Initial release X.S0054-610-
36、0 v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 Foreword vi FOREWORD (This foreword is not part of this Standard.) This document was prepared by 3GPP2 TSG-X. This documen
37、t is a new specification. This document is part of a multi-part document consisting of multiple parts that together describes Converged Access Network. This document is subject to change following formal approval. Should this document be modified, it will be re-released with a change of release date
38、 and an identifying change in version number as follows: X.S0054-610-X version n.0 where: X an uppercase numerical or alphabetic character 0, A, B, C, that represents the revision level. n a numeric string 1, 2, 3, that indicates an point release level. This document uses the following conventions:
39、“Shall” and “shall not” identify requirements to be followed strictly to conform to this document and from which no deviation is permitted. “Should” and “should not” indicate that one of several possibilities is recommended as particularly suitable, without mentioning or excluding others, that a cer
40、tain course of action is preferred but not necessarily required, or that (in the negative form) a certain possibility or course of action is discouraged but not prohibited. “May” and “need not” indicate a course of action permissible within the limits of the document. “Can” and “cannot” are used for
41、 statements of possibility and capability, whether material, physical or causal. X.S054-610-0 v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 1.1 Scope 1 1 Introduction1 In
42、troduction This document defines the stage-2 and stage-3 requirements for interworking between Ultra Mobile BroadbandTM(UMBTM)1Wireless access and HRPD/1x Wireless access in the Converged Access Network 1.1 Scope This document is part of a multi-part document. The multi-part document together descri
43、bes IP Network operation for the Converged Access Network. The scope of this document covers support for handoff from UMB to HRPD/1x (Packet and Circuit) and handoff from HRPD/1x to UMB. 1Ultra Mobile BroadbandTMand (UMBTM) are trade and service marks owned by the CDMA Development Group (CDG). X.S00
44、54-610-0 v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 2 References 2 2.1 Normative References2 References 2.1 Normative References This section provides references to ot
45、her specifications and standards that are necessary to implement this document. 1 IETF: RFC 2131, R. Droms, et al. Dynamic Host Configuration Protocol, March 1997. 2 IETF: RFC 2132, S. Alexander, et al. DHCP Options and BOOTP Vendor Extensions, March 1997. 3 IETF: RFC 3315, R. Droms, Ed. et al. Dyna
46、mic Host Configuration Protocol for IPv6 (DHCPv6), July 2003 4 IETF: RFC 3646, R. Droms, Ed. DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6), December 2003. 5 3GPP2: C.S0024-B v2.0, “cdma2000 High Rate Packet Data Air Interface Specification”, April 2007. 6 3GPP2:
47、 X.0054-100-0 v2.0, “Basic IP Services for Converged Access Network Specification”, December 2007 7 IETF: draft-yokota-mipshop-pfmipv6 8 3GPP2: X.S0011-002-D, “cdma2000 Wireless IP Network Standard: Simple IP and Mobile IP Access Service”, March 2006. 9 3GPP2: X.S0054-102-0 v2.0, “Multiple-Authentic
48、ation and Legacy Authentication Support for CAN”, December 2007. 10 IETF: RFC 2406, Kent. S, Atkinson R., “IP Encapsulating Security Payload (ESP)”, November 1998. 11 IETF: RFC 4306, Kaufman, C., “Internet Key Exchange (IKEv2) Protocol”, December 2005. 12 IETF: RFC 3948, Huttunen A., et.al., “UDP En
49、capsulation of IPsec ESP Packets”, January 2005. 13 IETF: RFC 3579, Aboba, B. and P. Calhoun, “RADIUS (Remote Authentication Dial In User Service) Support For Extensible Authentication Protocol (EAP)”, September 2003. 14 3GPP2: S.S0078-B, “Common Security Algorithms”, TBD 15 3GPP2: X.S0054-110-0 v1.0, “MIP4 Specification in Converged Access Network Specification”, December 2007. 16 3GPP2: X.S0044-0 v1.0, “MIPv4 Enhancements, TBD 17 3GPP2: A.S0008-C v1.0, “Interoperability Specification (IOS) for High Rate Packet Data (HRPD)
