Abstract:
Higher layer packet (HLP) framing information is transmitted across an air interface only as necessary, utilizing the Radio Link Protocol (RLP). In one embodiment, HLP framing information is transmitted in RLP control frames, between each HLP. In another embodiment, HLP framing information is transmitted in RLP data frames, with the RLP data frames including an indicator of that framing information. In three other embodiments, HLP framing information is transmitted in RLP data frames, and those RLP data frames containing HLP framing information are identified by RLP control frame functions. The control frame functions may comprise unnumbered RLP control frames, RLP data frames numbered using the RLP data frame sequence space but containing no HLP data, or RLP control frames numbered using an alternate sequence space.
Abstract:
Formulating an integrated disaster recovery (DR) plan based upon a plurality of DR requirements for an application by receiving a first set of inputs identifying one or more entity types for which the plan is to be formulated, such as an enterprise, one or more sites of the enterprise, the application, or a particular data type for the application. At least one data container representing a subset of data for an application is identified. A second set of inputs is received identifying at least one disaster type for which the plan is to be formulated. A third set of inputs is received identifying a DR requirement for the application as a category of DR Quality of Service (QoS) class to be applied to the disaster type. A composition model is generated specifying one or more respective DR QoS parameters as a function of a corresponding set of one or more QoS parameters representative of a replication technology solution. The replication technology solution encompasses a plurality of storage stack levels. A solution template library is generated for mapping the application to each of a plurality of candidate replication technology solutions. The template library is used to select a DR plan in the form of a replication technology solution for the application.
Abstract:
Systems and methodologies are described that facilitate adjusting allocation of carriers in wireless communications. A mobile device can establish communication with a base station over a number of allocated carriers for simultaneous transmission thereover. The mobile device can experience a decrease in power amplifier (PA) headroom causing dropping of at least one carrier and can report the drop to the base station. The base station can subsequently await a carrier request message from the mobile device before allocating additional carriers, or can allocate an additional carrier based on a determination that the mobile device can handle the new carrier. The mobile device can transmit a carrier request message when the PA headroom returns to a threshold level.
Abstract:
Systems and methodologies are described that facilitate adjusting allocation of carriers based on inactivity in wireless communications. An inactivity and dormancy timer are provided to allow carrier deallocation in periods of communicative inactivity (after expiration of the inactivity timer) without terminating the connection until expiration of the dormancy timer. Upon expiration of the inactivity timer, carriers can be deallocated from communication to conserve resources and reduce interference while still allowing requests to be made over the connection. If such requests are made, carriers can be reallocated to efficiently transmit a response. The timers are reset when communications are active. In addition, the timers can have expiration times related to aspects of connection, such as a protocol utilized thereover, connection quality, and/or the like.
Abstract:
Providing for centralized access management to diverse types of mobile network access points is described herein. By way of example, network components can generate a system determination list (SDL) for a user terminal (UT) that is customized to access capabilities of the UT and/or current position of the UT. The SDL can be employed by the UT to determine which network access points to camp on, handoff to, or the like. The network components can include a network database that maintains UT subscriber and related home Femto cell information, or such information can be maintained at a network operator's home location register. In some aspects, the information can be obtained over the air from the UT or from a base station serving the UT.
Abstract:
As part of the normal crawling process, a crawler parses a page and computes a de-tagged hash, called a fingerprint, of the page content. A lookup structure consisting of the host hash (hash of the host portion of the URL) and the fingerprint of the page is maintained. Before the crawler writes a page to a store, this lookup structure is consulted. If the lookup structure already contains the tuple (i.e., host hash and fingerprint), then the page is not written to the store. Thus, a lot of duplicates are eliminated at the crawler itself, saving CPU and disk cycles which would otherwise be needed during current duplicate elimination processes.
Abstract:
Methods and systems to facilitate mobility of devices between WWAN and WLAN systems/domains are described herein. A mobile station is registered with a preferred system/domain and a non-preferred system/domain and uses one or more public identities and one or more associated private identities to perform registrations over the preferred and non-preferred systems/domains. One or more of the associated systems/domains are further monitored for a paging signal transmitted over the network. In response to the paging signal, the mobile station transmits a paging response signal over the system/domain that facilitated transmission of the paging signal.
Abstract:
A method of coordinating broadcast parameter settings enables autonomous soft handoff by a mobile station. Any base station can initiate a broadcast parameter coordination process. The initiating base station assumes the role of an arbitrator and is responsible for determining the broadcast parameters. The broadcast parameter coordination process does not require any intervention or involvement by the PDSN or any signaling with the mobile station, except to inform the mobile station of the soft handoff sectors after the broadcast parameter coordination process is completed. The list of soft handoff sectors may be sent to the mobile station in a common overhead message.
Abstract:
Techniques for performing WLAN system scanning and selection are described. A terminal performs multiple iterations of scan to detect for WLAN systems. A scan list containing at least one WLAN system to detect for is initially determined. For each scan iteration, a scan type may be selected from among the supported scan types. The selected scan type may indicate passive scan or active scan, frequency channels to scan, etc. A scan may be performed based on the selected scan type. Signal strength measurements are obtained for access points received during the scan and used to identify detected access points. After all scan iterations are completed, candidates access points are identified based on the scan results, e.g., based on the signal strength measurements for the detected access points and a detection threshold. The best candidate access point may be selected for association by the terminal.
Abstract:
Techniques to configure quality of service (QoS) for communication are described. An access terminal configures a first QoS profile prior to a call. This QoS profile is for a set of QoS parameters that provides certain QoS. The access terminal thereafter establishes (e.g., originates or terminates) a call with an access network. If the first QoS profile is appropriate for the call, then QoS is not reconfigured. However, the access terminal may determine that a second QoS profile is to be used for the call, e.g., based on a format or a rate set supported by a remote/other terminal for the call. The access terminal would then configure the second QoS profile during the call. The access terminal may exchange data in accordance with (a) the first QoS profile before the second QoS profile is configured and activated and (b) the second QoS profile after it is configured and activated.