Abstract:
During an initial sending and receiving of QoS parameters between a QoS-based application and a data stack controller of a mobile terminal, the parameters are stored to a data stack of the mobile terminal. The parameters are used in an initial negotiation between the data stack controller and a base station. Subsequent re-negotiations of parameters between the data stack controller and other base stations does not require any subsequent re-sending and re-receiving of QoS parameters between the application and the data stack controller as any subsequent re-negotiations are implemented by retrieving the parameters from the data stack. As such, the application is “kept blind” of later re-negotiations between the data stack controller and base stations and continues its operation without disruption even during re-negotiations at handoffs between QoS and non-QoS aware base stations as the application receives QoS support during operation or operates under “best effort” conditions.
Abstract:
A wireless network assigns a single IP address to the wireless device, which assigns this IP address over to a TE2 device coupled to the wireless device. The wireless device derives a private IP address for communication with the TE2 device. The wireless device forwards packets exchanged between the TE2 device and the wireless network using the single IP address. The wireless device exchanges packets with the TE2 device by (1) using the private IP address for outbound packets sent to the TE2 device and (2) performing either address-based routing or packet filtering on inbound packets received from the TE2 device. The wireless device exchanges packets with the wireless network by (1) using the single IP address for outbound packets sent to the wireless network and (2) performing packet filtering on inbound packets received from the wireless network.
Abstract:
According to the invention an embodiment, a network node for communicating using a MAC address is disclosed. The network node includes a point-to-point interface, a bridge and a MAC address register. The point-to-point interface uses a first protocol. The bridge is coupled to the point-to-point interface and provides a fixed route for the Ethernet interface. The first protocol encapsulates the data of a second protocol. The MAC address register stores the MAC address for the second protocol, were the MAC address is dynamically determined in the field and written to the MAC address register. The MAC address is used when communicating with the network node through the point-to-point interface.
Abstract:
A generic quality of service (QoS) model that is not dependent on network technology is used to support QoS for communication networks utilizing different network technologies. The generic QoS model may include a superset of all QoS parameters for all network technologies being supported, e.g., 3GPP and 3GPP2. An application at a device may specify QoS for a traffic flow based on the generic QoS parameters in the superset. The generic QoS parameters may be converted to QoS parameters that are specific to a serving network. The converted QoS parameters are exchanged with the serving network and are used while exchanging traffic with the serving network.
Abstract:
The disclosure is directed to techniques for supporting failover between different network protocol addressing families in a wireless communication network. The techniques may be implemented in a mobile wireless communication device. A logical interface selects a physical interface for access to the network in response to a request from an application module. The network access request issued by the application module need not specify a network protocol type. Instead, upon selection of the physical interface, the logical interface notifies the application of the network protocol type associated with the physical interface. The logical interface may select a physical interface corresponding to a particular network protocol when available, based on connection preferences specified by the application module or a global setting within the device. If a physical interface corresponding to the network protocol is not available, however, the logical interface selects a physical interface corresponding to a different network protocol.
Abstract:
Techniques to efficiently filter fragmented datagrams and route fragments are described. For each fragmented datagram, a filtering node obtains filter parameters as fragments for the datagram are received. When all filter parameters are available, the node applies one or more filters on the filter parameters to obtain a filter result for the datagram and stores the filter result in an entry in a routing table. Prior to obtaining the filter result, the node stores all fragments received for the datagram in a memory. When the filter result becomes available, the node processes all fragments already received for the datagram in accordance with the filter result. As each remaining fragment for the datagram is received, the node immediately processes the fragment in accordance with the filter result. When the last fragment is received, the node clears the memory and the routing table entry for the datagram.
Abstract:
A method for configuring an IP address to receive broadcast or multicast data flow which modifies the bind( ) Application Programming Interface (API) to survey available local interfaces to determine their ability to be configured to receive data from a particular IP address, configure a interface to receive the IP address if it is so configurable, bind the IP address to that interface. The modified bind*( ) API may interact with one or more interfaces to see if each interface is capable of being configured to the IP address. Alternatively, the modified bind*( ) API determines the configurability of interfaces by consulting the access control list. Policy based routing rules may be implemented so that the modified bind*( ) operation configures the highest priority interface based upon policy parameters.
Abstract:
An apparatus and method for determining an authorized IP service for an access terminal during an establishment of a PPP connection. In an aspect of the disclosure, a data link is established with the access terminal, and a request to authenticate the access terminal is provided to an authentication/authorization server. During authentication, an IP Service Authorized Parameter is provided by the authentication/authorization server, the IP Service Authorized Parameter for indicating the authorized IP service for the access terminal. Thereby, a network layer protocol and a mobility protocol are each configured according to the authorized IP service that corresponds to the IP Service Authorized Parameter.
Abstract:
A system and method for optimizing robust header compression between a compressor (residing at AN/AT) and a decompressor (residing at AT/AN), the method comprising initializing the compressor with an estimated jitter value before the compressor; notifying the decompressor of the estimated jitter value before the compressor; estimating various threshold limits at the decompressor based on the sum of the jitter between the compressor and the decompressor (JITTER_CD) and that before the compressor (JITTER_BC); the decompressor sending a JITTER option whenever the threshold limits are exceeded; and the compressor adjusting a packet size in response the received JITTER option. The estimated jitter value before the compressor may be based on simulations or channel characteristics. Notification to the decompressor of the jitter value before the compressor may be achieved by signaling or hard-coding a same value at the compressor and the decompressor.
Abstract:
Multiple applications sharing common resources are arbitrated such that failures resulting from unavailable resources can be avoided. Whenever an application (e.g., a data application) desires to perform an operation (e.g., PPP resynchronization) that requires the use of a shared resource (e.g., an RF receiver), a determination is made as to whether that resource is available. The operation may be delayed while the resource is unavailable. The application may be assigned the resource if it is available or becomes available and may then start the operation. The resource is locked while the operation is pending to avoid assignment to another application. The resource arbitration allows applications to complete their operations without encountering failures due to other applications taking over the resources.