Update Notifications for Proxy Mobile IPv6

Krishnan, Suresh; Gundavelli, Sri; Liebsch, Marco; Yokota, Hidetoshi; Korhonen, Jouni

doi:10.17487/rfc7077

Cited by 6 publications

(16 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Since the LMA cannot send a PBA message that has not been triggered in response to a received PBU message, the solution defined in this specification makes use of two mobility messages: FMI and FMA, which actually use the format of the Update Notifications for PMIPv6 defined in [RFC7077]. The trigger for the flow movement can be on the MN (e.g., by using layer-2 signaling with the MAG), or on the network (e.g., based on congestion and measurements), which then notifies the MN for the final IP flow mobility decision (as stated in Section 3.1).…”

Section: Mn With Different Sets Of Prefixes On Each Magmentioning

confidence: 99%

“…This specification requires implementation of Update Notification (UPN) [RFC7077] and Update Notification Ack (UPA) [RFC7077] messages with the specific Notification Reason and Status Code values as defined by this document. This document does not require implementation of any other aspects of [RFC7077].…”

Section: Message Formatsmentioning

confidence: 99%

“…The FMA message used in this specification is the UPA message specified in Section 4.2 of [RFC7077]. The message format, transport, and security considerations are as specified in [RFC7077].…”

Section: Flow Mobility Acknowledgement (Fma)mentioning

confidence: 99%

“…The message format, transport, and security considerations are as specified in [RFC7077]. The format of the message is specified in Section 4.2 of [RFC7077].…”

Section: Flow Mobility Acknowledgement (Fma)mentioning

confidence: 99%

“…The message format, transport, and security considerations are as specified in [RFC7077]. The format of the message is specified in Section 4.2 of [RFC7077]. This specification does not modify the UPA message, however, it defines the following new status code values for use in this specification: …”

Section: Flow Mobility Acknowledgement (Fma)mentioning

confidence: 99%

See 4 more Smart Citations

Proxy Mobile IPv6 Extensions to Support Flow Mobility

Bernardos¹

2016

View full text Add to dashboard Cite

Section: Mn With Different Sets Of Prefixes On Each Magmentioning

confidence: 99%

Section: Message Formatsmentioning

confidence: 99%

Section: Flow Mobility Acknowledgement (Fma)mentioning

confidence: 99%

“…The message format, transport, and security considerations are as specified in [RFC7077]. The format of the message is specified in Section 4.2 of [RFC7077].…”

Section: Flow Mobility Acknowledgement (Fma)mentioning

confidence: 99%

Section: Flow Mobility Acknowledgement (Fma)mentioning

confidence: 99%

See 3 more Smart Citations

Proxy Mobile IPv6 Extensions to Support Flow Mobility

Bernardos¹

2016

View full text Add to dashboard Cite

PMIPv6 Integrated with MIH for Flow Mobility Management: A Real Testbed with Simultaneous Multi-Access in Heterogeneous Mobile Networks

Alves

Silva

Marinheiro

et al. 2017

Wireless Pers Commun

View full text Add to dashboard Cite

The exponential growth of the number of multihomed mobile devices is changing the way how we can connect to the Internet. Our mobile devices are demanding for more network resources, in terms of traffic volume and QoS requirements. Unfortunately, it is very hard to a multihomed device to be simultaneously connected to the network through multiple links. The current work enhances the network access of multihomed devices agnostically to the deployed access technologies. This enhancement is achieved by using simultaneously all of the mobile devices interfaces, and by routing each individual data flow through the most convenient access technology. The proposed solution is only deployed at the network side and it extends Proxy Mobile IPv6 with flow mobility in a completely transparent way to mobile nodes. In fact, it gives particular attention to the handover mechanisms, by improving the detection and attachment of nodes in the network, with the inclusion of the IEEE 802.21 standard in the solution. This provides the necessary implementation and integration details to extend a network topology with femtocell devices. Each femtocell is equipped with various network interfaces supporting a diverse set of access technologies. There is also a decision entity that manages individually each data flow according to its QoS / QoE requisites. The proposed solution has been developed and extensively tested with a real prototype. Evaluation results evidence that the overhead for using the solution is negligible as compared to the offered advantages such as: the support of flow mobility, the fulfil of VoIP functional requisites, the session continuity in spite of flows mobility, its low overhead, its high scalability, and the complete transparency of the proposed solution to the user terminals.

show abstract

Considerations of IP multicast for load balancing in Proxy Mobile IPv6 networks

Nguyen

Bonnet

2014

Computer Networks

View full text Add to dashboard Cite

Update Notifications for Proxy Mobile IPv6

Cited by 6 publications

References 6 publications

Proxy Mobile IPv6 Extensions to Support Flow Mobility

Proxy Mobile IPv6 Extensions to Support Flow Mobility

PMIPv6 Integrated with MIH for Flow Mobility Management: A Real Testbed with Simultaneous Multi-Access in Heterogeneous Mobile Networks

Considerations of IP multicast for load balancing in Proxy Mobile IPv6 networks

Contact Info

Product

Resources

About