Abstract: In one embodiment, a method for supporting backward compatibility in a mobile network can include: receiving a packet in a first device that can support a first protocol; forming a modified packet by adding a field to the packet, where the field is related to a context for a second protocol; and providing the modified packet to a second device, where the second device can support the first and second protocols. The context can include a Packet Data Protocol (PDP) context and the field can include a PDP identifier. The mobility layer can include Mobile IP, for example. The first and second protocols can be Mobile IP and PDP, respectively.

Abstract: In one embodiment, a method for supporting backward compatibility in a mobile network can include: receiving a packet in a first device that can support a first protocol; forming a modified packet by adding a field to the packet, where the field is related to a context for a second protocol; and providing the modified packet to a second device, where the second device can support the first and second protocols. The context can include a Packet Data Protocol (PDP) context and the field can include a PDP identifier. The mobility layer can include Mobile IP, for example. The first and second protocols can be Mobile IP and PDP, respectively.

Abstract: Supporting communication sessions at a mobile node includes determining at a mobile node an address for one or more interior network elements of a network system. A interior network element is distinct from an edge network element of the network system, and is operable to establish a communication session. An address for an interior network element is inserted into packets. The packets are sent from the mobile node to the interior network element to communicate directly with the interior network element. The communication session is established using the interior network element.

Abstract: Requesting a network resource includes facilitating a communication session between a mobile node and an endpoint. A trigger event is received at a first anchor point associated with the mobile node. The trigger event indicates that reservation of a network resource is being requested for the communication session. A second anchor point associated with the endpoint is identified. Reservation of the network resources for the communication sessions is initiated over a tunnel between the first anchor point and the second anchor point.

Abstract: Forwarding a packet includes facilitating a communication session for a mobile node. A packet is identified as received from the mobile node. One or more labels are added to the packet. A subscriber label of the one or more labels uniquely identifies the mobile node for the communication session. The packet is forwarded to a gateway. The gateway is operable to uniquely identify the mobile node from the subscriber label.

Abstract: Facilitating node mobility includes facilitating a communication session for a mobile node communicated along a first communication path. A first anchor point manages context information for the communication session, where the context information comprises information for supporting the communication session. A command to transfer the context information to a second anchor point is received from a home agent. The second anchor point is operable to facilitate communication of the communication session along a second communication path. The context information is transferred in response to the command.

Abstract: A method for distributing information in a network environment is provided that includes receiving one or more packets from a communication flow and recognizing a universal generic identification (UGI) associated with the communication flow. The UGI corresponds to an end user that is associated with the communication flow. The UGI is operable to enable a service for the end user in a first network and a second network, the first and second networks being different, whereby either the first network or the second network operates as a home network for the end user.

Abstract: Providing a multicast service includes maintaining multicast service information at an application server. The multicast service information describes a multicast service having an associated subscriber, and the multicast service is operable to deliver multicast content from a multicast source. A cell supporting a user device associated with the subscriber is determined, and creation of a bearer path for the multicast service is initiated. Delivery of the multicast content to the user device is enabled using the bearer path.