1、 ETSI TS 1Digital cellular telecoUniversal Mobile TelMobility managUser Equipment(3GPP TS 24.3TECHNICAL SPECIFICATION124 304 V13.0.0 (2016communications system (Phaelecommunications System (LTE; agement based on Mobile IPvnt (UE) - foreign agent interfaStage 3 .304 version 13.0.0 Release 1316-01) ha
2、se 2+); (UMTS); Pv4; face; 13) ETSI ETSI TS 124 304 V13.0.0 (2016-01)13GPP TS 24.304 version 13.0.0 Release 13Reference RTS/TSGC-0124304vd00 Keywords GSM,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 00
3、017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice 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 e
4、lectronic and/or print versions of the present document shall not be modified without the prior written authorization 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
5、(PDF) version kept on a specific network drive within ETSI Secretariat. Users of the present document should be 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/s
6、tatus.asp If you find errors in the present document, please send your comment to one of the following services: 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 photo
7、copying and microfilm except as authorized by written permission of ETSI. The content of the PDF version shall 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 2
8、016. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for 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 reg
9、istered and owned by the GSM Association. ETSI ETSI TS 124 304 V13.0.0 (2016-01)23GPP TS 24.304 version 13.0.0 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
10、 any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual 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 availabl
11、e on the ETSI Web server (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, including 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, o
12、r may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been 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 identi
13、ties. These should be interpreted as being references to the corresponding ETSI deliverables. The cross reference 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“, “s
14、hould not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 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
15、 TS 124 304 V13.0.0 (2016-01)33GPP TS 24.304 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 6g34 General . 6g34.1 Mobility
16、management based on FACoA 6g34.2 Identities . 6g34.3 Multiple PDN connectivity. 6g34.4 MIPv4 security aspects . 7g35 FACoA procedures for mobile IPv4 7g35.1 FACoA initial attach and registration . 7g35.1.1 General 7g35.1.2 UE procedures 7g35.1.2.1 Agent discovery 7g35.1.2.2 FACoA registration . 7g35
17、.1.3 FA procedures . 8g35.1.3.1 Agent advertisement 8g35.1.3.2 UE registration 8g35.2 FACoA handover . 8g35.2.1 General 8g35.2.2 UE procedures 8g35.2.3 FA procedures. 9g35.3 FACoA deregistration 9g35.3.1 General 9g35.3.2 UE procedures 9g35.3.2.1 Network-initiated deregistration . 9g35.3.2.2 UE-initi
18、ated deregistration 10g35.3.3 FA procedures . 10g35.3.3.1 Network-initiated deregistration . 10g35.3.3.2 UE-initiated deregistration 11g3Annex A (informative): Change history . 12g3History 13g3ETSI ETSI TS 124 304 V13.0.0 (2016-01)43GPP TS 24.304 version 13.0.0 Release 13Foreword This Technical Spec
19、ification 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 contents of the present document, it will be re-released by the TSG
20、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 document under change control. y the second digit is incremented f
21、or 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 124 304 V13.0.0 (2016-01)53GPP TS 24.304 version 13.0.0 Release 131 Scope The present document descri
22、bes the stage 3 aspects of mobility management for User Equipment (UE) using IETF Mobile IPv4 foreign agent mode to access the Evolved Packet Core Network (EPC) through trusted non-3GPP access networks and for mobility management of UE between the 3GPP access network and trusted non-3GPP access netw
23、orks. In particular, the present document describes the UE Mobile IPv4 Foreign Agent (FA) interface stage 3 aspects, where the FA functionality is located within the access network in the non-3GPP access domain. The present document is applicable to the User Equipment (UE) and the network node imple
24、menting the FA functionality. 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
25、specific reference, 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 pres
26、ent document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 IETF RFC 5944 (November 2010): “IP Mobility Support for IPv4, revised“. 3 3GPP TS 23.402: “Architecture enhancements for non-3GPP accesses“. 4 3GPP TS 23.003: “Numbering, addressing and identification“. 5 IETF RFC 5446 (February
27、 2009): “Service Selection for Mobile IPv4“. 6 3GPP TS 33.402: “3GPP System Architecture Evolution; Security aspects for non-3GPP accesses“. 7 IETF RFC 2794 (January 2000): “Mobile IP Network Access Identifier Extension for IPv4“. 8 3GPP TS 29.279: “Mobile IPv4 (MIPv4) based Mobility protocols; (Sta
28、ge 3)“. 9 IETF RFC 3543 (August 2003): “Registration Revocation in Mobile IPv4“. 3 Definitions and abbreviations 3.1 Definitions For the purposes 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 precede
29、nce over the definition of the same term, if any, in 3GPP TR 21.905 1. Foreign Agent (FA): a router on a visited network which provides mobile IPv4 routing services to the UE while registered as described in IETF RFC 5944 2. ETSI ETSI TS 124 304 V13.0.0 (2016-01)63GPP TS 24.304 version 13.0.0 Releas
30、e 13Foreign agent care-of address: an address of a foreign agent with which the UE is registered as described in IETF RFC 5944 2. Home Agent (HA): a mobile IPv4 router on a UE“s home network which tunnels datagrams for delivery to the UE while it is registered on a visited network as described in IE
31、TF RFC 5944 2. According to 3GPP TS 23.402 3, the HA 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. An abbreviation defined in the present document takes precedence over
32、 the definition of the same abbreviation, if any, in 3GPP TR 21.905 1. EPC Evolved Packet Core Network FA Foreign Agent FACoA Foreign Agent Care-of Address HA Home Agent RRP Registration Reply RRQ Registration Request 4 General 4.1 Mobility management based on FACoA MIPv4 is specified in IETF RFC 59
33、44 2 which provides two alternative modes of enabling a mobile node (UE) to acquire a care-of address for routing of datagrams: - a “foreign agent care-of address“ (FACoA) mode wherein a care-of address is provided by a FA through agent advertisement messages, or - a “co-located care-of address“ mod
34、e wherein a care-of address is acquired by the UE as a local IP address. For the purpose of IP mobility management while accessing the EPC through a trusted non-3GPP access network, the FACoA mode enables the UE to register the IP address of the FA (FACoA) located within the non-3GPP access network
35、with the UEs HA for the routing of datagrams to the UE. 4.2 Identities In order to support MIPv4 FA mode mobility management with the EPC, the network and mobile client shall use an NAI as described in 3GPP TS 23.003 4 for user identification. The network and mobile client shall base the username pa
36、rt of the NAI on IMSI. The network and UE shall use the Root NAI when the UE attempts a MIPv4 registration while attached to the HPLMN. The Root NAI format is specified in 3GPP TS 23.003 4. The network and UE shall use the Decorated NAI when the UE attempts a MIPv4 registration while attached to a V
37、PLMN. The Decorated NAI format is specified in 3GPP TS 23.003 4. 4.3 Multiple PDN connectivity Following the establishment of a mobility binding to an initial PDN, the UE can request the establishment of a mobility binding with an additional PDN by including the APN of the desired PDN within a Servi
38、ce Selection extension defined in IETF RFC 5446 5. The Service Selection extension is included within the Registration Request (RRQ) message defined in IETF RFC 5944 2. The UE can repeat the process of sending an (RRQ) with a Service Selection extension to establish connectivity with additional PDNs
39、. ETSI ETSI TS 124 304 V13.0.0 (2016-01)73GPP TS 24.304 version 13.0.0 Release 134.4 MIPv4 security aspects The procedures for bootstrapping of MIPv4 foreign agent care-of address (FACoA) security parameters are described in 3GPP TS 33.402 6. The MIPv4 security is based on the use of the authenticat
40、ion extensions defined in IETF RFC 5944 2. The MIPv4 signalling messages are protected between the UE and the HA using the Mobile-Home Authentication extension and optionally between the UE and the FA using the Mobile-Foreign Authentication extension. 5 FACoA procedures for mobile IPv4 5.1 FACoA ini
41、tial attach and registration 5.1.1 General The MIPv4 initial attach is performed by the UE to establish a MIPv4 connection with the node acting as the HA. The initial attach involves the following procedures: - Discovery of the HA address. The UE needs to discover the IPv4 address of the node acting
42、 as the HA. - Discovery of FACoA. The UE needs to discover the IPv4 care-of address provided by the FA. - IPv4 home address assignment. The UE needs to be assigned an IPv4 address to be used as the home address in Mobile IPv4 FACoA mode. The HA is responsible of assigning the home address to the UE.
43、 - Security association establishment. The UE needs to establish a security association with the node acting as the HA in order to secure the MIPv4 signalling. This procedure usually consists in a shared key verification and is performed via MIPv4 signalling. 5.1.2 UE procedures 5.1.2.1 Agent discov
44、ery When the UE has attached to the non-3GPP access network, the UE may send a MIPv4 Agent Solicitation as specified in IETF RFC 5944 2. 5.1.2.2 FACoA registration Upon first receiving a MIPv4 Agent Advertisement message from a FA or detecting a reboot of the FA through inspection of the Agent Adver
45、tisement message sequence number, the UE shall select one care-of address included in the Mobility Agent Advertisement Extension and shall send an RRQ to the FA as specified in IETF RFC 5944 2 with the care-of address included in the Care-of Address field of the RRQ message. The UE shall set the sou
46、rce address and Home Address field to the unspecified address (i.e. 0.0.0.0). The UE shall clear bits S (simultaneous binding) and D (decapsulation by mobile node), and set bit T (reverse tunnelling) to request reverse tunnelling. The UE shall also include the NAI extension as specified in IETF RFC
47、2794 7. As part of MIPv4 security, the UE shall include the Mobile-Home Authentication extension within the RRQ as specified in IETF RFC 5944 2. The UE shall set the authenticator and SPI fields of the of the Mobile-Home authentication extension to the MN-HA key and associated MN-HA-SPI generated as
48、 described in 3GPP TS 33.402 6. If the non-3GPP access specific procedures require a security association between the UE and FA, the UE shall also include the Mobile-Foreign Authentication extension within the RRQ as specified in IETF RFC 5944 2. The UE shall set the authenticator and SPI fields of
49、the of the Mobile-Foreign authentication extension to the MN-FA key and associated MN-FA-SPI generated as described in 3GPP TS 33.402 6. If the UE already knows the IP address of the HA (e.g. when the HA address is pre-configured) the UE shall include that IP address in the Home Agent field. ETSI ETSI TS 124 304 V13.0.0 (2016-01)83GPP TS 24.304 version 13.0.0 Release 13If the UE does not know the IP address of the HA, the UE shall include the unspecified address (i.e. 0.0.0.0) in the Home Agent field. If
