1、 ETSI TS 1Universal Mobile TelMobile IPv4 (MIP(3GPP TS 29.2TECHNICAL SPECIFICATION129 279 V13.0.0 (2016elecommunications System (LTE; I v4) based mobility protocoStage 3 .279 version 13.0.0 Release 1316-01) (UMTS); cols; 13) ETSI ETSI TS 129 279 V13.0.0 (2016-01)13GPP TS 29.279 version 13.0.0 Releas
2、e 13Reference RTS/TSGC-0429279vd00 Keywords LTE,UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important n
3、otice The present document can be downloaded from: http:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written author
4、ization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the present document should b
5、e aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following service
6、s: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. The content of the PDF version shall
7、 not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2016. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for
8、the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 129 279 V13.0.0 (2016-01)23GPP TS 29.279 version 13.0.0
9、 Release 13Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectu
10、al Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, including
11、IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has bee
12、n produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables. The cross refere
13、nce between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in cl
14、ause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 129 279 V13.0.0 (2016-01)33GPP TS 29.279 version 13.0.0 Release 13Contents Intellectual Property Rights 2g
15、3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 6g34 MIPv4 Mobility Management Registration Procedures . 6 g34.1 General . 6g34.1.1 MIPV4 Registration Request (RRQ) 6g34.1.2 MIPv4 Registrat
16、ion Reply (RRP) . 6g35 MIPv4 Mobility Management Revocation Procedures 7g35.1 General . 7g35.1.1 Extensions to RRQ and RRP 7g35.2 MIPv4 Registration Revocation . 7g35.3 MIPv4 Registration Revocation Ack 7g3Annex A (informative): Change history: 9g3History 10g3ETSI ETSI TS 129 279 V13.0.0 (2016-01)43
17、GPP TS 29.279 version 13.0.0 Release 13Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the c
18、ontents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved
19、 document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 129 279 V13.0.0 (2016-01)53GPP TS
20、29.279 version 13.0.0 Release 131 Scope The present document specifies the stage 3 of the MIPv4 Based Mobility Protocol used over the S2a reference point defined in 3GPP TS 23.402 3, and is thus applicable to the PDN Gateway and Trusted Non-3GPP Access. Protocol specification is compliant with relev
21、ant IETF RFCs. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. For a specific refere
22、nce, subsequent revisions do not apply. For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. 1
23、 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 23.401: “GPRS enhancements for E-UTRAN access“. 3 3GPP TS 23.402: “Architecture Enhancements for non-3GPP accesses“. 4 3GPP TS 33.402: “3GPP System Architecture Evolution (SAE); Security aspects of non-3GPP accesses“. 5 IETF Internet-D
24、raft, draft-ietf-mip4-rfc3344bis-06.txt (March 2008): “IP Mobility Support for IPv4, revised“. Editors note: The above document cannot be formally referenced until it is published as an RFC. 6 IANA Assigned Numbers Online Database, “Private Enterprise Numbers“, . 7 3GPP TS 24.008: “Mobile radio inte
25、rface Layer 3 specification; Core network protocols“. 8 3GPP TS 24.304: “Mobility management based on Mobile IPv4; User Equipment (UE) - Foreign Agent interface“. 9 IETF RFC 3543 (August 2003): “Registration Revocation in Mobile IPv4“. 3 Definitions and abbreviations 3.1 Definitions For the purposes
26、 of the present document, the terms and definitions given in 3GPP TR 21.905 1 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 1. Evolved Packet Core: the successor to the 3GPP Release 7 packet-switched c
27、ore network, developed by 3GPP within the framework of the 3GPP System Architecture Evolution (SAE). Foreign agent: a router on a visited network which provide mobile IPv4 routing services to the UE while registered as described in draft-ietf-mipv4-rfc3344bis 5. ETSI ETSI TS 129 279 V13.0.0 (2016-01
28、)63GPP TS 29.279 version 13.0.0 Release 13Foreign agent care-of address: an address of a foreign agent with which the UE is registered as described in draft-ietf-mipv4-rfc3344bis 5 Home agent: a mobile IPv4 router on a UE“s home network which tunnels datagrams for delivery to the UE while it is regi
29、stered on a visited network as described in draft-ietf-mipv4-rfc3344bis 5. According to 3GPP TS 23.402 3, the home agent functionality is implemented in the PDN Gateway. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 1 and the following apply. A
30、n abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 1. EPC Evolved Packet Core FA Foreign Agent FACoA Foreign Agent Care-of Address PDN GW Packet Data Network Gateway HA Home Agent MIPv4 Mobile IPv4RRP Registration R
31、eply RRQ Registration Request 4 MIPv4 Mobility Management Registration Procedures 4.1 General The MIPv4 Registration Request (RRQ) and Registration Reply (RRP) messages are used during the following registration procedures with MIPv4 FACoA on s2a: Initial attach UE-initiated detach. UE initiated Con
32、nectivity to Additional PDN Trusted Non-3G Access shall follow the FA procedure as described in draft-ietf-mip4-rfc3344bis 5 and PDN-GW shall follow the HA procedure as described in draft-ietf-mip4-rfc3344bis 5. 4.1.1 MIPV4 Registration Request (RRQ) After receiving an RRQ from the UE, the FA shall
33、process it and relay the RRQ message to the HA as described in draft-ietf-mip4-rfc3344bis-06.txt 5, and 3GPP TS 24.304 8 . The RRQ message shall be protected between the FA and the HA according to TS 33.402 4. 4.1.2 MIPv4 Registration Reply (RRP) After receiving an RRQ from the FA, the HA shall proc
34、ess the message, and shall assign an IPv4 address for the UE, if requested by the UE, and send an RRP message to the FA, as described in draft-ietf-mip4-rfc3344bis-06.txt 5, and 3GPP TS 24.304 8 The RRP message shall be protected between the FA and the HA according to 3GPP TS 33.402 4. ETSI ETSI TS
35、129 279 V13.0.0 (2016-01)73GPP TS 29.279 version 13.0.0 Release 135 MIPv4 Mobility Management Revocation Procedures 5.1 General The MIPv4 Registration Revocation and Registration Revocation Ack messages are used during the following registration revocation procedures with MIPv4 FACoA on s2a. Network
36、 Initiated Detach: Trusted Non-3G Access follows the FA procedure as described in IETF RFC 3543 9 and PDN-GW follows the HA procedure as described in IETF RFC 3543 9, for “FA initiated revocation“ procedure. HSS/AAA Initiated Detach: Trusted Non-3G Access follows the FA procedure as described in IET
37、F RFC 3543 9 and PDN-GW follows the HA procedure as described in IETF RFC 3543 9, for “FA initiated revocation“ procedure. PDN-GW Initiated Resource Allocation Deactivation: Trusted Non-3G Access follows the FA procedure as described in IETF RFC 3543 9 and PDN-GW follows the HA procedure as describe
38、d in IETF RFC 3543 9, for “HA initiated revocation“ procedure. The MIPv4 registration revocation procedure can be initiated by a node acting as FA or HA to revoke the binding of a mobile node with an HA. 5.1.1 Extensions to RRQ and RRP The following extension has to be present in the RRQ message sen
39、t from the FA and the RRP message sent from HA to support Revocation Procedure. They must follow the Negotiation of Revocation Support as explained in IETF RFC 3543 9. Table 5.1.1-1: Information element IE Description Reference Revocation support extension To indicate the node supports registration
40、revocation and can receive revocation messages. IETF RFC 3543 9 5.2 MIPv4 Registration Revocation The MIPv4 Registration Revocation message is sent from the FA to the HA as part of the FA initiated revocation procedure, or from the PDN GW (HA) to the FA as part of the HA Initiated revocation procedu
41、re. In case of FA Initiated Revocation procedure, the FA must send a Registration Revocation message and follow the “Foreign Agent Responsibilities“ in “Foreign Domain Revoking“ as described in IETF RFC 3543 9. The HA must process the received Revocation Request as described in IETF RFC 3543 9. In c
42、ase of HA Initiated Revocation procedure, the FA must process received Revocation Request as described in IETF RFC 3543 9. In both cases the FA may notify UE by as described in IETF RFC 3543 9, however this is outside the scope of this document. 5.3 MIPv4 Registration Revocation Ack The MIPv4 Regist
43、ration Revocation Ack message is sent from the HA to the FA as part of the FA initiated revocation procedure, or from the FA to the HA as part of the HA initiated revocation procedure procedure. In case of FA Initiated Revocation Procedure, the HA shall reply with a Registration Revocation Acknowled
44、ge message and follow the “Home Agent responsibilities“ in “Foreign Domain Revoking“ as described in IETF RFC 3543 9. ETSI ETSI TS 129 279 V13.0.0 (2016-01)83GPP TS 29.279 version 13.0.0 Release 13In case of HA Initiated Revocation Procedure, the FA shall reply with a Registration Revocation Acknowl
45、edge message and follow “Foreign Agent responsibilities“ in “Home Domain Revoking“ as described in IETF RFC 3543 9. ETSI ETSI TS 129 279 V13.0.0 (2016-01)93GPP TS 29.279 version 13.0.0 Release 13Annex A (informative): Change history: Date TSG # TSG Doc CT4 Doc CR Rev Cat Subject/Comment Old New 2008
46、-12 CT#42 CP-080713 V2.0.0approved in CT#42 2.0.0 8.0.0 2009-12 - - - - - - Update to Rel-9 version (MCC) 8.0.0 9.0.0 2011-03 - - - - - - Update to Rel-10 version (MCC) 9.0.0 10.0.0 2012-09 - - - - - - Update to Rel-11 version (MCC) 10.0.0 11.0.0 2014-09 - - - - - - Update to Rel-12 version (MCC) 11.0.0 12.0.0 2015-12 - - - - - - Update to Rel-13 version (MCC) 12.0.0 13.0.0 ETSI ETSI TS 129 279 V13.0.0 (2016-01)103GPP TS 29.279 version 13.0.0 Release 13History Document history V13.0.0 January 2016 Publication
