1、 TIA-1137.000-A-2009 APPROVED: JUNE 1, 2009 REAFFIRMED: DECEMBER 6, 2013 TIA-1137.000-A June 2009CAN Wireless IP Network Overview and List of Parts NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers
2、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 respect preclude any member or non-me
3、mber 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 Publications are adopted by TIA
4、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 not purport to address all safety p
5、roblems 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 Project No. 3-0291.000-RV1-RF1, for
6、mulated 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 any editing process. The
7、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 published pending patent applic
8、ations 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 IPR. TIA will neither be
9、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 practices suggested or pr
10、ovided 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 (whether designated as a
11、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 any other SSO for IPR or le
12、tters 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 IPR in the records or publ
13、ications 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 investigate products, design
14、s 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 PURPOSE OR USE, ITS MERCHANTA
15、BILITY 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, RULE OR REGULATION, OR THE
16、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 CONTAINED HEREIN, INCLUDING WIT
17、HOUT 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 OTHERWISE, EVEN IF ADVIS
18、ED 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. X.S0054-000-A 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 2
19、8 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 i ContentsCAN Wireless IP Network Overview and List of Parts CONTENTS CAN Wireless IP Network Overview and List of Parts i 1 Introduction1 1.1 Scope1 2 References2 2.1 Normative References2 2.2 Informat
20、ive References3 3 Definitions, Symbols and Abbreviations4 3.1 Definitions .4 3.1.1 Symbols and Abbreviations.5 4 List of Parts 7 5 Network Reference Model .8 5.1 Network Architecture.8 5.1.1 Non-Roaming Architecture .9 5.1.2 Roaming Architecture11 5.2 Network Entities 13 5.3 Reference Points 15 X.S0
21、054-000-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 Figures ii LIST OF FIGURES Figure 1 Non-Roaming Architecture 1 (Split AGW) 9 Figure 2 Non-Roaming Architec
22、ture 2 (Single AGW) .10 Figure 3 Roaming Architecture 1 (Split AGW) 11 Figure 4 Roaming Architecture 2 (Single AGW)12 X.S0054-000-A 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 5
23、8 59 60 iii List of TablesLIST OF TABLES Table 1 List of Parts.7 X.S0054-000-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 Revision History iv REVISION HISTORY Revision
24、 Date Remarks 0v1.0 December 2007 Initial Release 0 v2.0 August 2008 Bug fix release for the initial release A v1.0 August 2008 Revision A This document is subject to change.X.S0054-000-A 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
25、 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 part of a multi-part document consisting of multiple parts that together describes specifications for Converged
26、 Access Network (CAN) IP 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 change in version number as follows: X.S0054-000-X-n where: X an uppercase numerical or alphabeti
27、c character A, B, C, that represents the revision level. n a numeric string 1, 2, 3, that indicates a point release level. This document uses the following conventions: “Shall” and “shall not” identify requirements to be followed strictly to conform to this document and from which no deviation is pe
28、rmitted. “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 is preferred but not necessarily required, or that (in the negative form) a certain possibility or course of
29、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 possibility and capability, whether material, physical or causal. This page is left blank intentionally. X.S0054-000
30、-A 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 document provides an overview of the series of documents used to specify th
31、e Converged Access Network (CAN). The CAN enables optimization and upgrade for packet data access network to support services to the customers. This document also describes the CAN Network Reference Model. 1.1 Scope This series of documents defines an architecture model and set of specifications for
32、 a Converged Access Network (CAN) that can support real time services such as VoIP, Video Telephony, voice and video streaming, etc. The proposed architecture supports multiple access technologies including the Ultra Mobile Braodband (UMB)1air interface 12. This revision of the CAN series of documen
33、ts provides the following capability: Support for UMB air interface only. Support for simple IPv4, simple IPv6 13, Client Mobile IPv4 (CMIP4), and Proxy Mobile IPv4 (PMIP4). RADIUS authentication and authorization support for these protocols is specified. Diameter authentication and authorization su
34、pport for simple IPv4 and simple IPv6 is specified. Support for QoS without SBBC is specified. RADIUS-based accounting is specified. Support for handoff between HRPD/1X and UMB. 1Ultra Mobile Broadband and (UMB) are trade and service marks owned by the CDMA Development Group (CDG). X.S0054-000-0 v1.
35、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 other specific
36、ations and standards that are necessary to implement this document. 1 3GPP2: X.S0054-100-0 v2.0, “Basic IP Services for Converged Access Network Specifications”, August 2008. 2 3GPP2: X.S0054-102-0 v2.0, “Multiple-Authentication and Legacy Authentication Support for Converged Access Network”, August
37、 2008. 3 3GPP2: X.S0054-110-0 v2.0, “MIPv4 Specification in Converged Access Network”, August 2008. 4 3GPP2: X.S0054-210-0 v1.0, “CMIP Based Inter-AGW Handoff”, December 2007. 5 3GPP2: X.S0054-220-A v1.0, “Network PMIP Support”, August 2008. 6 3GPP2: X.S0054-300-0 v1.0, “QoS Support for Converged Ac
38、cess Network Specification”, December 2007. 7 3GPP2: X.S0054-400-0 v1.0, “Converged Access Network Accounting Specification”, December 2007. 8 3GPP2: X.S0054-910-A v1.0, “CAN Data Dictionary”, August 2008. 9 IETF: draft-leung-mip4-proxy-mode-08. Editors Note: The above document is a work in progress
39、 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. 10 IETF: draft-ietf-netlmm-proxymip6-18 Editors Note: The above document is a work in progress and sho
40、uld 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. 11 3GPP2: X.S0011-(all parts)-D v1.0, “cdma2000 wireless IP Network Standard”, March 2006. 12 3GPP2: C.S0084-(
41、all parts)-0 v2.0, “Ultra Mobile Broadband (UMB) Air Interface Specification”, September 2007. 13 IETF: RFC 3775, “Mobility Support in IPv6”, June 2004. 14 3GPP2: A.S0020-0 v1.0, “Interoperability Specification (IOS) for Ultra Mobile Broadband (UMB) Radio Access Network Interfaces”, November 2007. 1
42、5 3GPP2: A.S0008-C v1.0, “Interoperability Specification (IOS) for High Rate Packet Data (HRPD) Radio Access Network Interfaces with Session Control in the Access Network,” July 2007. X.S0054-000-A 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 3
43、6 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 2 References16 3GPP2: A.S0009-C v1.0, “Interoperability Specification (IOS) for High Rate Packet Data (HRPD) Radio Access Network Interfaces with Session Control in the Packet Control Function,” Ju
44、ly 2007. 17 3GPP2: X.S0054-610-0 v1.0, “Handoff between HRPD/1X and UMB”, August 2008. 2.2 Informative References This section provides references to other documents that may be useful for the reader of this document. 3GPP2: X.S0013-013-0 v1.0, “All-IP Core Network Multimedia Domain - Service Based
45、Bearer Control - Tx Interface Stage 3”, December 2007. X.S0054-000-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 3 Definitions, Symbols and Abbreviations 4 3.1 Definiti
46、ons3 Definitions, Symbols and Abbreviations This section contains definitions, symbols and abbreviations that are used throughout the document. 3.1 Definitions Access Network Route Instance An Access Network Route Instance (ANRI) is a logical function that has an open route with an AT. An eBS and an
47、 SRNC may support an ANRI function. An ANRI is referred to as an Access Network (AN) in 12. Client Mobile IP Client Mobile IP refers to use of Mobile IPv4/IPv6 for mobility from the AT. Specifically, the term is used if it is the AT to perform MIP registration with the network. This term is introduc
48、ed to distinguish from the Proxy MIP where the network entity performs MIP registration on behalf of the AT. Data Attachment Point The Data Attachment Point (DAP) is the eBS that receives forward-link user traffic for the AT from the Access Gateway (AGW). The term of DAP in this document is same as
49、DAP eBS in 14. IP-Session An IP-Session is a session that is defined by a users NAI, AAA-Session-ID, and an ATs IP-Address (e.g., IPv4 address, MIPv4 HoA in FA CoA mode, or IPv6 address). Proxy Mobile IP Proxy Mobile IP refers to a protocol based on having the Mobile IP client function in a network element to provide mobility support for an unaltered and mobility-unaware device. Route Set The set of all ANRIs that have a route with the AT. The Session Anchor ANRI is in the SRNC and is alw
