Abstract:
Systems and methods for providing a converged gateway (CGW) may be disclosed. A policy may be by the CGW to make routing decisions (e.g. segregation and/or aggregation of flows or traffic associated with data) for various interfaces and/or radio access technologies (RATs) that may be included in a LAN, device, and/or communication system. The policy may be locally stored within the CGW. Dynamic flow management, load balancing, offloading, PDF context establishment, prioritization, detection of devices, and the like may also be provided and/or implemented in the CG W and may be used to route flows and/or traffic associated with data.
Abstract:
A Packet Core Function (PCF) (55) and a method of automatic Packet Data Service Node (PDSN) Discovery, Monitoring, and Failure Handover in a packet-switched network that includes a plurality of PDSNs (57). The PDSNs multicast PDSN profile information that includes their ID, status, congestion level, and routing table information. The PCF automatically builds and updates a PDSN database (61) from the profile information it receives. If the PCF fails to receive a predefined number of multicast messages, or fails to receive responses to polling messages from a particular PDSN, the PCF concludes that the PDSN has failed. If a failure is detected, the PCF selects one or more new PDSNs to handle the packet data sessions that were being handled by the failed PDSN. The PCF then hands over the active sessions to the selected PDSN(s).
Abstract:
User equipment (UE) may include dual mode devices that enable two different radio access technologies (RATs) for connection to wireless communication networks. Recently, these RATs have been used for message splitting in which a message is split into two packet flows, for example, that may enable increased throughput to the (UE). Dynamic mobility management may be provided for the UE by allowing a converged gateway (CGW) to discover the UE. For example, the CGW may identify the UE in communication a first CGW that may be within a first subnet. The CGW may store the identity of the WTRU in the memory. The CGW may transmit the identity of the UE to a second CGW that may be in communication with a second subnet.
Abstract:
A Packet Core Function (PCF) (55) and a method of automatic Packet Data Service Node (PDSN) Discovery, Monitoring, and Failure Handover in a packet-switched network that includes a plurality of PDSNs (57). The PDSNs multicast PDSN profile information that includes their ID, status, congestion level, and routing table information. The PCF automatically builds and updates a PDSN database (61) from the profile information it receives. If the PCF fails to receive a predefined number of multicast messages, or fails to receive responses to polling messages from a particular PDSN, the PCF concludes that the PDSN has failed. If a failure is detected, the PCF selects one or more new PDSNs to handle the packet data sessions that were being handled by the failed PDSN. The PCF then hands over the active sessions to the selected PDSN(s).
Abstract:
Systems and methods for providing a converged gateway (CGW) may be disclosed. A policy may be by the CGW to make routing decisions (e.g. segregation and/or aggregation of flows or traffic associated with data) for various interfaces and/or radio access technologies (RATs) that may be included in a LAN, device, and/or communication system. The policy may be locally stored within the CGW. Dynamic flow management, load balancing, offloading, PDF context establishment, prioritization, detection of devices, and the like may also be provided and/or implemented in the CG W and may be used to route flows and/or traffic associated with data.
Abstract:
Point-to-point protocol (PPP) negotiation in a wireless communication system between e.g. a mobile station (MS) and a packet data service node (PDSN). The MS sends to the PDSN a link control protocol option designated option X that identifies a user profile including at least one pre-negotiated PPP parameter. If the PDSN supports the user profile and the at least one parameter, it acknowledges this. In response, the MS acknowledges its acceptance. Then each node sets a state machine in accordance with the user profile. If the PDSN supports the user profile but not one or more of the at least one parameter, it sends a negative-acknowledgment identifying a second, acceptable user profile. If the PDSN does not support the user profile, it rejects the first user profile and a full PPP negotiation is performed without reference to any of the pre-stored user profiles.
Abstract:
Systems and methods for providing a converged gateway (CGW) may be disclosed. A policy may be by the CGW to make routing decisions (e.g. segregation and/or aggregation of flows or traffic associated with data) for various interfaces and/or radio access technologies (RATs) that may be included in a LAN, device, and/or communication system. The policy may be locally stored within the CGW. Dynamic flow management, load balancing, offloading, PDF context establishment, prioritization, detection of devices, and the like may also be provided and/or implemented in the CG W and may be used to route flows and/or traffic associated with data.
Abstract:
A method and apparatus for bandwidth aggregation for an Internet protocol (IP) flow are disclosed. A sender may split IP packets on a single IP flow, and transmit the IP packets to a receiver via at least two interfaces. The sender splitting the IP packets over multiple interfaces may not send any signaling to the receiver. Alternatively, the sender may send information to the receiver for configuring distribution of the IP packets over multiple interfaces. The information may be carried on a binding update message, a binding acknowledgement message, or a binding refresh request message. The IP packets may be split and transmitted by a logical interface that sits between an IP layer and a layer 2, or by a bandwidth aggregation (BWA) middleware located between a transmission control protocol (TCP) layer and an IP layer.
Abstract:
Communication nodes, systems and methods are described which provide offload processing capabilities. Tasks can be offloaded from a host element to an offload processing element. Incoming data streams can have their associated Layer 3/Layer transportation protocol stacks terminated. Data can be repackaged and routed using an internal, offload protocol which also preserves L3 and/or L4 information.