TS 29.279
Mobile IPv4 (MIPv4) based
Mobility Protocols

3GPP‑Page ETSI‑search CONTENT_↓

V17.0.0 (PDF) 2022/03 11 p.

V16.0.0 2020/06 11 p.

V15.0.0 2018/06 10 p.

V14.0.0 2017/03 11 p.

V13.0.0 2015/12 11 p.

V12.0.0 2014/09 11 p.

V11.0.0 2012/09 11 p.

V10.0.0 2011/04 11 p.

V9.0.0 2009/12 11 p.

V8.0.0 2008/12 10 p.

Rapporteur:: Mr. Landais, Bruno
Nokia France

Content for TS 29.279 Word version: 17.0.0

1 Scope p. 4

The present document specifies the stage 3 of the MIPv4 Based Mobility Protocol used over the S2a reference point defined in TS 23.402, and is thus applicable to the PDN Gateway and Trusted Non-3GPP Access. Protocol specification is compliant with relevant IETF RFCs.

2 References p. 4

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 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 present document.

[1]

TR 21.905: "Vocabulary for 3GPP Specifications".

[2]

TS 23.401: "GPRS enhancements for E-UTRAN access".

[3]

TS 23.402: "Architecture Enhancements for non-3GPP accesses".

[4]

TS 33.402: "3GPP System Architecture Evolution (SAE); Security aspects of non-3GPP accesses".

[5]

draft-ietf-mip4-rfc3344bis-06.txt (March 2008) "IP Mobility Support for IPv4, revised".

[6]

IANA Assigned Numbers Online Database, "Private Enterprise Numbers": <http://www.iana.org/assignments/enterprise-numbers>.

[7]

TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols".

[8]

TS 24.304: "Mobility management based on Mobile IPv4; User Equipment (UE) - Foreign Agent interface".

[9]

RFC 3543 (August 2003): "Registration Revocation in Mobile IPv4".

3 Definitions and abbreviations p. 5

3.1 Definitions p. 5

For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.

Evolved Packet Core:

the successor to the 3GPP Release 7 packet-switched core 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].

Foreign agent care-of address:

an address of a foreign agent with which the UE is registered as described in draft-ietf-mipv4-rfc3344bis [5]. According to TS 23.402, the home agent functionality is implemented in the PDN Gateway.

3.2 Abbreviations p. 5

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.

EPC

Evolved Packet Core

Foreign Agent

FACoA

Foreign Agent Care-of Address

PDN GW

Packet Data Network Gateway

Home Agent

MIPv4

Mobile IPv4

RRP

Registration Reply

RRQ

Registration Request

4 MIPv4 Mobility Management Registration Procedures p. 5

4.1 General p. 5

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 Connectivity 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) p. 6

After receiving an RRQ from the UE, the FA shall process it and relay the RRQ message to the HA as described in draft-ietf-mip4-rfc3344bis-06.txt [5], and TS 24.304 .

The RRQ message shall be protected between the FA and the HA according to TS 33.402.

4.1.2 MIPv4 Registration Reply (RRP) p. 6

After receiving an RRQ from the FA, the HA shall process 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 TS 24.304

The RRP message shall be protected between the FA and the HA according to TS 33.402.

5 MIPv4 Mobility Management Revocation Procedures p. 6

5.1 General p. 6

The MIPv4 Registration Revocation and Registration Revocation Ack messages are used during the following registration revocation procedures with MIPv4 FACoA on s2a.

Network Initiated Detach: Trusted Non-3G Access follows the FA procedure as described in RFC 3543 and PDN-GW follows the HA procedure as described in RFC 3543, for 'FA initiated revocation' procedure.
HSS/AAA Initiated Detach: Trusted Non-3G Access follows the FA procedure as described in RFC 3543 and PDN-GW follows the HA procedure as described in RFC 3543, for 'FA initiated revocation' procedure.
PDN-GW Initiated Resource Allocation Deactivation: Trusted Non-3G Access follows the FA procedure as described in RFC 3543 and PDN-GW follows the HA procedure as described in RFC 3543, 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 p. 6

The following extension has to be present in the RRQ message sent 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 RFC 3543.

Table 5.1.1-1

Information element	IE Description	Reference
Revocation support extension	To indicate the node supports registration revocation and can receive revocation messages.	RFC 3543

5.2 MIPv4 Registration Revocation p. 6

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 procedure.

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 RFC 3543. The HA must process the received Revocation Request as described in RFC 3543.

In case of HA Initiated Revocation procedure, the FA must process received Revocation Request as described in RFC 3543.

In both cases the FA may notify UE by as described in RFC 3543, however this is outside the scope of this document.

5.3 MIPv4 Registration Revocation Ack p. 7

The MIPv4 Registration 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 Acknowledge message and follow the "Home Agent responsibilities" in "Foreign Domain Revoking" as described in RFC 3543.

In case of HA Initiated Revocation Procedure, the FA shall reply with a Registration Revocation Acknowledge message and follow "Foreign Agent responsibilities" in "Home Domain Revoking" as described in RFC 3543.