Abstract: A mobile communication network includes a plurality of access nodes that can serve different roles in support of a communication session with a mobile station. An access node can serve as a connecting node that receives access requests the mobile station, as an anchor node to anchor a radio packet connection with a core network for the communication session; or as a primary node to store session information for the communication session. When the communication session is established, the anchor node for the communication session may select another access node to serve as the primary node. Session information can be stored at both the anchor node and primary node so that data can be delivered to the mobile station if either one of the anchor node and primary node are available.

Abstract: A mobile communication network includes a plurality of access nodes that can serve different roles in support of a communication session with a mobile station. An access node can serve as a connecting node that receives access requests the mobile station, as an anchor node to anchor a radio packet connection with a core network for the communication session; or as a primary node to store session information for the communication session. When the communication session is established, the anchor node for the communication session may select another access node to serve as the primary node. Session information can be stored at both the anchor node and primary node so that data can be delivered to the mobile station if either one of the anchor node and primary node are available.

Abstract: A mobile communication network comprises a plurality of access nodes, wherein each access node allocates mobile station identifiers to mobile stations from an assigned group of mobile station identifiers. The mobile station identifiers in each group have a common property that identifies the corresponding access node. The mobile station identifier may be used, for example, to locate session information for a mobile station when a mobile station moves between access nodes.

Abstract: In a mobile communication network comprising a plurality of access nodes, session information for a communication session is stored in one access node and may be requested by a peer access node. A requesting access node determines the location of session information based on the mobile station identifier associated with the communication session. If the session information is transferred to the requesting node, the requesting node may allocate a new mobile station identifier to the mobile station for the communication session.

Abstract: A mobile communication network includes a plurality of access nodes that can serve different roles in support of a communication session with a mobile station. An access node can serve as a connecting node that receives access requests the mobile station, as an anchor node to anchor a radio packet connection with a core network for the communication session; or as a primary node to store session information for the communication session. When the communication session is established, the anchor node for the communication session may select another access node to serve as the primary node. Session information can be stored at both the anchor node and primary node so that data can be delivered to the mobile station if either one of the anchor node and primary node are available. During a communication session, a connecting node receiving a connection request from a dormant mobile station may request session information from the primary node. The radio packet connection may also be moved to the connecting node.

Abstract: A method, system and cluster of Management Objects (MOs) for creating and maintaining a relationship between one or more MOs and one or more attribute values that are common to the MOs. These attribute values may be contained in one or more configuration templates, and the MOs are grouped in a cluster of MOs sharing the same attribute values, i.e. the same configuration templates. The relationship provided by the cluster between the templates and the MOs allows for a one-time definition of the persistent relationship, which reduces the subsequent edition tasks. The relation between the management objects and templates is first defined by creating the cluster with MOs and templates. Subsequent updates to the templates are propagated to the MOs of the cluster. Likewise, subsequent addition of MOs to the cluster engenders a transfer of attribute values of the cluster's templates to the added MOs.