Abstract: A first aspect of the invention relates to a method for verifying an attachment of a mobile node to a network element in a network. A second aspect of the invention relates to a method to be implemented in a mobility anchor node, which detects whether a race condition between registration messages occurs and resolves the most recent location of a mobile node. A third aspect of the invention relates to a method for detecting whether a binding cache entry for a mobile at a correspondent node has been spoofed and to a method for registering a care-of address of a mobile node at a correspondent node. A fourth aspect of the invention relates to a method for providing from a mobile node to a local mobility anchor information on an attachment of a mobile node to a network element.

Abstract: A first aspect of the invention relates to a method for improving security at a local mobility anchor implementing both a network-based and a host-based mobility management scheme for managing the mobility of a mobile node. It suggests a method for verifying an attachment of a mobile node (MN) to a network element in a network. A second aspect of the invention relates to a method to be implemented in a mobility anchor node, which detects whether a race condition between registration messages occurs and resolves the most recent location of a mobile node. A third aspect of the invention relates to a method for detecting whether a binding cache entry for a mobile at a correspondent node has been spoofed and to a method for registering a care-of address of a mobile node at a correspondent node.

Abstract: The invention relates to a method for reducing the header size of data packets by removing inner headers from the data packets, wherein at least an outer header remains for routing purposes. When removing the inner headers from a data packet, a newly configured address of the receiving and/or the transmitting entity is inserted in the remaining outer header of the data packet. Context information is provided in the receiving entities for reconstructing the removed inner headers, wherein the context information is referred to by the newly configured address that is in the source and/or destination address of the outer header. The reduced data packet is transmitted with only one header, thereby significantly reducing the size of each data packet. The original packet is completely reconstructed at the receiving entity thereby allowing to proceed with the usual processing of each data packet.

Abstract: The invention relates to a method for reducing the header size of data packets exchanged between a Mobile Node (MN) and a gateway that is located between the MN and a Corresponding Node (CN). Different sort of headers are utilized between the MN and the gateway, and between the gateway and the CN. The sort of header, obtained by an optimizing procedure, allows to reduce the header size of exchanged packets on said data path section. To achieve this, a modified route optimization (RO) process is performed between the MN and the gateway, wherein the gateway acts on behalf of the CN. After completing the first RO process, the MN initiates and performs a second RO process with the gateway acting as CN. After completing both route optimization processes, data packet transmission is performed between the CN and the gateway after switching from IPsec tunnel mode to IPsec transport mode.

Abstract: The present invention describes a method for signalling to a mobility anchor point a position of a mobile node in a network using a network-based mobility management scheme for managing the mobility of the mobile node, said method comprising receiving, by a network element, from the mobile node, during or after network authentication of the mobile node, a sequence number used by a process implementing a mobile node-based mobility management scheme for managing the mobility of the mobile node, and transmitting, by the network element, to the mobility anchor point a message on a position of the mobile node in the network, wherein said message comprises the received sequence number. A common sequence number variable for BU and PBU messages is used, so that the HA is able to determine a correct transmission order of PBU/BU messages based on the sequence number in the message.