TIA-1165 100-A-2012 cdma2000 Femtocell Network Packet Data Network Aspects《Cdma2000 Femtocell网络 分组数据网络方面》.pdf

《TIA-1165 100-A-2012 cdma2000 Femtocell Network Packet Data Network Aspects《Cdma2000 Femtocell网络 分组数据网络方面》.pdf》由会员分享，可在线阅读，更多相关《TIA-1165 100-A-2012 cdma2000 Femtocell Network Packet Data Network Aspects《Cdma2000 Femtocell网络 分组数据网络方面》.pdf（80页珍藏版）》请在麦多课文档分享上搜索。

1、 TIA-1165.100-A February 2012cdma2000 Femtocell Network: Packet Data Network Aspects NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement

2、 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 manufacturing or selling products not conformi

3、ng 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 American National Standards Institute (A

4、NSI) 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 its use or all applicable regulatory re

5、quirements. 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-0055.100-RV1, formulated under the cognizance of the TIA TR-45 Mobile (b) there is n

6、o 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 this Document may involve the use of

7、 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 to TIAs attention, a statement from t

8、he 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 licensing terms or conditions, which

9、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 complied with as respects the Docume

10、nt 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, recommendation or otherwise), whether such

11、 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 any such Normative Reference; (ii) T

12、IAs 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 shall not constitute identification to TI

13、A 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 compliance with the contents of the

14、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 OF ANY THIRD PARTYS INTELLECTUAL PRO

15、PERTY 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 THE CONTENTS OR ANY PRODUCT OR SERVICE

16、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 INDIRECT, SPECIAL, INCIDENTAL OR CONSEQ

17、UENTIAL 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 DAMAGES. THE FOREGOING NEGATION OF DA

18、MAGES IS A FUNDAMENTAL ELEMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. 3GPP2 X.S0059-100-A v1.0 Revision History Revision Description of Changes Date Rev. 0 v1.0 Initial Publication January 2010 Rev. A v1.0 Updated Publication Dec

19、ember 2011 3GPP2 X.S0059-100-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 100-i Contentscdma2000 Femtocell Network: Packet Data Network Aspects CONTENTS List of Figures .

20、iv List of Tablesv Foreword .vi 1 Introduction1 1.1 Scope1 2 References2 2.1 Normative References2 2.2 Informative References5 3 FAP Network Connectivity Procedures .6 3.1 General.6 3.2 Tunnel Management Procedures6 3.2.1 Discovery and Selection of SeGW from FAP .6 3.2.2 Tunnel Establishment 7 3.2.3

21、 Tunnel Disconnection8 3.3 Authentication and Authorization9 3.3.1 Authentication Procedures.9 3.4 FAP Auto-configuration 10 3.4.1 FMS Discovery10 3.4.2 FAP Auto-configuration Procedures .11 3.4.3 Location Determination of the FAP.11 3.5 Quality of Service (QoS) Considerations.12 3.5.1 CHILD_SA12 3.

22、5.2 Reverse Link Packet Classifier in FAP13 4 Mobility Management14 5 Local IP Access for HRPD.15 5.1 LIPA Requirements and Procedures16 5.1.1 LIPA Protocol Reference Model .16 5.1.2 AN-PPP Session 17 5.1.3 Addressing with IPCP .18 5.1.4 PPP Framing21 5.1.5 Ingress Address Filtering at the FAP.21 5.

23、1.6 Egress Address Filtering/Routing at the MS .21 6 Remote IP Access 23 6.1 General.23 6.2 Discovery and Selection of SeGW by MS.24 3GPP2 X.S0059-100-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 5

24、1 52 53 54 55 56 57 58 59 Contents 100-ii 6.2.1 MS Requirements 24 6.2.2 SeGW Requirements .25 6.2.3 Femtocell AAA Requirement 25 6.2.4 Home AAA Requirements.25 6.3 Remote IP Access Tunnel Establishment.25 6.3.1 IKEv2 PSK Key Generation26 6.3.2 MS Requirements 26 6.3.3 SeGW Requirements .28 6.3.4 Ho

25、me AAA Requirements.30 6.3.5 FAP Requirements.31 6.4 IP Traffic Processing for Remote IP Access31 6.4.1 MS Requirements 31 6.4.2 FAP Requirements.32 6.4.3 SeGW Requirements .32 6.5 Tunnel Disconnection 33 6.5.1 MS Procedures.33 6.5.2 SeGW Requirements .33 6.5.3 Home AAA Requirements.33 6.5.4 FAP Req

26、uirements.34 7 Accounting .35 8 RADIUS Considerations 36 8.1 RADIUS Attributes between SeGW and Femtocell AAA for FAP Authorization36 8.2 RADIUS Attributes between SeGW and HAAA for RIPA .36 8.3 RADIUS Attributes between FAP and AN- AAA for LIPA .38 8.4 RADIUS Vendor Specific Attributes.38 8.4.1 Ses

27、sion-Key-Method .38 8.4.2 RIPA-Info 39 8.4.3 Local-IP-Access-Authorized .39 9 Diameter Considerations 41 9.1 Diameter Applications and Commands41 9.1.1 FAP Authorization.41 9.1.2 RIPA Authentication .41 9.2 Diameter AVPs 45 9.2.1 Master-Security-Association .46 9.2.2 SFF-KEY-Nonces46 9.2.3 RIPA-Info

28、 47 9.3 Experimental Result-Code AVP Values 47 9.3.1 Permanent Failures 47 10 eHRPD Packet Data Femtocell Operation48 A Annex Call Flow Examples (Informative) 49 A.1 Femtocell Network Connectivity Call Flow 49 A.1.1 Femtocell Network Connectivity Call Flow without Redirection .49 3GPP2 X.S0059-100-A

29、 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 100-iii ContentsA.1.2 Femtocell Network Connectivity Call Flow with Redirection to Serving System .50 A.2 SeGW Discovery .52 A

30、.3 FAP-SeGW IPsec Tunnel Establishment.52 A.4 Local IP Access Call Flows .54 A.4.1 Successful LIPA Session Establishment55 A.4.2 LIPA not Supported at MS 56 A.4.3 LIPA Terminated after Handoff 58 A.5 Remote IP Access Call Flows59 A.5.1 Redirection Based SeGW Discovery with EAP Authentication59 A.5.2

31、 Redirection Based SeGW Discovery with IKEv2 PSK Authentication 60 A.5.3 Tunnel Establishment for Remote IP Address with EAP Authentication62 A.5.4 Tunnel Establishment for Remote IP Access with IKEv2 PSK Authentication 63 3GPP2 X.S0059-100-A v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 2

32、1 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 List of Figures 100-iv LIST OF FIGURES Figure 1 Example of Security Associations and associated QoS classes of traffic with two SAs12 Figure 2 IP Access Bearer and Interfaces15 Figure

33、3 HRPD LIPA Protocol Reference Model.16 Figure 4 Femtocell Remote IP Access Architecture .23 Figure 5 Femtocell Network Connectivity Call Flow without Redirection.49 Figure 6 Femtocell Network Connectivity with Redirection 51 Figure 7 SeGW Discovery 52 Figure 8 IPsec Tunnel Establishment53 Figure 9

34、Successful LIPA Session Establishment.55 Figure 10 LIPA not Supported by MS: Session Establishment Failure 57 Figure 11 LIPA Terminated After Handoff.58 Figure 12 Redirection Based SeGW Discovery with EAP Authentication .59 Figure 13 Redirection Based SeGW Discovery with IKEv2 PSK Authentication61 F

35、igure 14 Tunnel Establishment for Remote IP Access with EAP Authentication.62 Figure 15 Tunnel Establishment for Remote IP Access with IKEv2 PSK Authentication .64 3GPP2 X.S0059-100-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

36、41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 100-v List of TablesLIST OF TABLES Table 1 IPCP Vendor Specific Option.21 Table 2 Value(s) Field for the IPv4 Packet Filter Criteria .22 Table 3 Value(s) Field for the IPv6 Packet Filter Criteria .22 Table 4 Additional Parameters in A10 Connec

37、tion Setup Airlink Fields 35 Table 5 Additional Parameters in PDSN UDR35 Table 6 Additional Accounting Parameter Attribute RADIUS Definitions.35 Table 7 Meaning of the Request, Accept, Reject, Challenge columns of Table 8 and Table 9 .36 Table 8 RADIUS Attributes exchanged between the SeGW and the F

38、emtocell AAA for FAP Authorization36 Table 9 RADIUS Attributes exchanged between the SeGW and the HAAA37 Table 10 Additional RADIUS Attributes exchanged between the FAP and AN- AAA for LIPA .38 Table 11 Session-Key-Method VSA .38 Table 12 RIPA-Info VSA 39 Table 13 Local-IP-Access-Authorized VSA39 Ta

39、ble 14 Diameter Command Codes for FAP Authorization41 Table 15 Diameter Command Codes for EAP based IKEv2 .42 Table 16 Diameter Command Codes for PSK based IKEv2 .43 Table 17 Meaning of the Request, Answer columns .45 Table 18 Diameter AVP exchanged between the SeGW and the HAAA45 3GPP2 X.S0059-100-

40、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 Foreword 100-vi FOREWORD (This foreword is not part of this specification.) This document was prepared by the Third Generatio

41、n Partnership Project 2 (3GPP2). This document is Revision A of X.S0059-100. eHRPD Femtocells are newly supported. This document is part of a multi-part document consisting of multiple parts that together describes specifications for cdma2000 Femtocell Network. This document is subject to change fol

42、lowing 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.S0059-100-X-n where: X an uppercase numerical or alphabetic character A, B, C, that represents the revision level. n a numeric stri

43、ng 1, 2, 3, that indicates a point release level. Note that there is one annex section in this document. Annex A is informative and not considered part of this document. 3GPP2 X.S0059-100-A v1.0 3 4 5 6 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 32 33 34 35 36 37 38 39 40 41 42 43 4

44、4 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 100-1 1 Introduction1 2 1 Introduction 7 8 9 30 31 This document provides a packet date specifications for the HRPD, eHRPD and 1x packet data Femtocell network. 1.1 Scope This series of documents defines packet data specifications for an HRPD, eHRPD and

45、 1x packet data Femtocell network that can support existing services provided by HRPD, eHRPD and 1x. This revision of the Femtocell network specification includes the following capabilities: FAP-SeGW Tunnel Management FAP Authentication and Authorization FAP Auto-Configuration Quality of Service (Qo

46、S) Support between FAP and SeGW FAP Remote IP Access Mobility Management between macro cell and Femtocell Accounting Enhancements FAP Local IP Access 1.2 Document Conventions “Shall” and “shall not” identify requirements to be followed strictly to conform to this document and from which no deviation

47、 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 is preferred but not necessarily required, or that (in the negative form) a certain possibility or cour

48、se 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 possibility and capability, whether material, physical or causal. 3GPP2 X.S0059-100-A v1.0 1 2 3 4 5 6 7 8 9 1

49、0 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 2 References 100-2 2 References 2.1 Normative References This section provides references to other specifications and standards that are necessary to implement this document. References are either specific (identified by date of publication, revision identifier, and version number) or non-specific. For a specific reference, subsequent revisions may not apply. For a non-specific reference, the latest revisi