1、 TIA-1137.210-2009 APPROVED: JUNE 1, 2009 REAFFIRMED: DECEMBER 6, 2013 TIA-1137.210 June 2009CMIP based Inter-AGW Handoff 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.210-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.S0054-210-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 3
19、8 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 i ContentsCMIP based Inter-AGW Handoff CONTENTS 1 Introduction1 1.1 Scope1 2 References2 2.1 Normative References2 2.2 Informative References2 3 Inter-AGW Active Handoff .3 3.1 Reverse Link Operation .4 3.2 Forward Link Operation 5
20、3.3 AGW Requirements.5 3.4 eBS Behavior .5 3.5 SRNC Requirements5 3.6 AT Requirements.5 3.7 HAAA Requirements.6 4 Inter-AGW AT Idle Handoff7 4.1 AGW Requirements.7 4.2 SRNC Requirements7 4.3 AT Requirements.7 4.4 HAAA Requirements.7 5 Call Flows 8 5.1 Inter-AGW Handoff.8 X.S0054-210-0 v1.0 1 2 3 4 5
21、 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 Figures ii LIST OF FIGURES Figure 1 An Example of Inter-AGW HO based on CMIP 4 Figure 2 An example call flow for client CMIP4 base
22、d inter-AGW Handoff.8 X.S0054-210-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 iii List of TablesLIST OF TABLES No table is described in this document. X.S0054-210-0 v
23、1.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 Revision History iv REVISION HISTORY Revision Date Remarks 0 December, 2007 Initial release X.S0054-210-0 v1.0 1 2 3 4 5 6 7
24、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 ForewordFOREWORD (This foreword is not part of this Standard.) This document was prepared by 3GPP2 TSG-X. This document is a new specificatio
25、n. 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 and an identifying cha
26、nge in version number as follows: X.S0054-210-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: “Shall” and “shall not”
27、 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 certain course of action i
28、s 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 statements of possibil
29、ity and capability, whether material, physical or causal. X.S0054-210-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 Introduction This docume
30、nt describes inter-AGW handoff operation using Mobile IP (e.g., the AT implements MIP client functionality, called CMIP) for layer 3 mobility, for both active and idle handoffs. The seamless inter-AGW handoff is achieved using CMIP4 7 and L2 tunneling between the eBSs that are connected to the Sourc
31、e AGW and Target AGW as specified in 2. 1.1 Scope This document is part of a multi-part document consisting of multiple parts that together describes Ultra Mobile BroadbandTM1Wireless IP Network operation. The scope of this document covers support for CMIP4 based Inter-AGW handoff. 1Ultra Mobile Bra
32、oadbandTMand (UMBTM) are trade and service marks owned by the CDMA Development Group (CDG). X.S0054-210-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
33、 Normative References2 References 2.1 Normative References 1 3GPP2: C.S0084-0 v2.0, “Ultra Mobile Broadband (UMB) Air Interface”, September 2007. 2 3GPP2: A.S0020-0 v1.0, “Interoperability Specification (IOS) for Ultra Mobile Broadband (UMB) Radio Access Network Interfaces”, November 2007. 3 3GPP2:
34、X.S0054-100-0 v1.0, “Basic IP Service for Converged Access Network Specification”, December 2007. 4 3GPP2: X.S0054-110 v1.0, “MIP4 Specification in Converged Access Network Specification”, December 2007. 5 IETF: IETF: draft-leung-mip4-proxy-mode Editor Note: The above document is a work in progress
35、and should not be referenced unless and until it is approved and published. Until such time as this Editors Note is removed, the inclusion of the above document is for informational purposes only. 6 IETF: draft-yegani-gre-key-extension Editor Note: The above document is a work in progress and should
36、 not be referenced unless and until it is approved and published. Until such time as this Editors Note is removed, the inclusion of the above document is for informational purposes only. 7 IETF: RFC3344, Parkins, “IP Mobility Support for IPv4”, August 2002. 8 3GPP2: X.S0054-400-0, v1.0, “Converged A
37、ccess Network Accounting Specification”, December 2007. 2.2 Informative References This section provides references to other documents that may be useful for the reader of this document. 3GPP2: X.S0054-000-0 v1.0, “CAN Wireless IP Network Overview and List of Parts”, December 2007. 3GPP2: X.S0054-10
38、2-0 v1.0, “Multiple-Authentication and Legacy Authentication Support for CAN”, December 2007. 3GPP2: X.S0054-220-0 v1.0, “Network PMIP Support”, December 2007. 3GPP2: X.S0054-300-0 v1.0, “QoS Support for Converged Access Network Specification”, December 2007. 3GPP2: X.S0054-910-0 v1.0, “CAN Data Dic
39、tionary”, December 2007. X.S0054-210-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.2 Informative References 3 3 Inter-AGW Active Handoff3 Inter-AGW Active Handoff Mob
40、ility in the CAN network architecture is achieved via handoffs. A handoff between eBSs with connectivity to the same AGW such that the Source AGW remains the same before, during, and after handoff, is called Intra-AGW handoff. When the AT has an active session, a newly added eBS in the Route Set sho
41、uld be able to connect to the existing AGW. Therefore Intra-AGW handoff normally occurs. The intra-AGW handoff is specified in 2. In some cases, inter-AGW Handoff occurs when the AT has an active session and a newly added eBS needs to connect with a different AGW from the Source AGW. This section ad
42、dresses this scenario. In this scenario, a different LinkID (which represents the new AGW that assigns the new CMIP4 care of address (e.g., CMIP4 FA CoA) is presented to the AT after the new eBS which is connected to a new AGW is added in the Route Set and after EAP Access Authentication is performe
43、d successfully. Once the new primary RAN PMIP4 tunnel is established between the new eBS and new AGW (Target AGW) the AT presents the new IP interface to upper layer which triggers CMIP4 binding update. See 2 for the details. A new CMIP4 FA CoA is assigned to the AT and is associated with the newly
44、established primary PMIP4 tunnel with the new AGW. A Client initiated CMIP4 binding is then performed. The primary PMIP4 tunnel from the previous DAP to the previous AGW is kept alive until that PMIP4 tunnel life-time expires or the AGW receives PMIP4 deregistration for the primary PMIP4 tunnel. The
45、 reverse link bindings to the previous AGW (if any) are also kept alive until the reverse link PMIP4 bindings life-times expire or the AGW receives PMIP4 deregistration for the reverse link PMIP4 tunnel. During inter-AGW handoff, the AT keeps each IP interface (e.g., both CMIP4 FA CoAs under Source
46、AGW and Target AGW) until all eBSs associated with that particular IP interface are dropped from the Route Set. This is so that the AT can receive/send the data from/to both IP interfaces during inter-AGW handoff period. Inter-AGW handoff is a Make-Before-Break process. Figure 1 shows an example of
47、inter-AGW handoff. In the figure, eBS0 and eBS1 are under AGW1 (associated with LinkID1) and eBS2 and eBS3 are under AGW2 (associated with LinkID2) and Mobile IP (e.g., CMIP4 as specified in 7) is used for inter-AGW handoff. The AT has been in communication with eBS1 (DAP/FLSE/RLSE) connected with A
48、GW1. The AT has just added eBS2 and eBS2 sent LinkID2 representing AGW2 to the AT. Due to radio conditions, the FLSE/RLSE is switched to eBS2. X.S0054-210-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
49、50 51 52 53 54 55 56 57 58 59 60 3 Inter-AGW Active Handoff 4 3.1 Reverse Link OperationFigure 1 An Example of Inter-AGW HO based on CMIP 3.1 Reverse Link Operation In Figure 1 , before handoff CMIP4 binding uses IP interface 1. When the application in the AT generates data, the MN in the AT sends the data to IP interface 1 associated with the LinkID 1 (which is associated with AGW1, called the Source AGW). The AT can use any stack associated with LinkID1 (e.g., Route 0 or Route 1 in Figure 1 ). Since current RLSE (eBS2 in the f
