KR101095783B1 - Handoff in a multi-frequency network - Google Patents

Abstract

Methods and apparatus for RF handoff in a multi-frequency network are disclosed. The method may further comprise creating an uninterrupted and partially uninterrupted handoff tables for multiplexes held in a current LOI, wherein the uninterrupted handoff tables and partially uninterrupted handoff tables comprise one or more of the current LOI. Includes neighboring RF channels having multiplexes; Detecting a handoff event initiated by acquisition failures on a current RF; Selecting a selected RF channel from the uninterrupted handoff tables and the partial uninterrupted handoff tables; And performing a handoff to the selected RF channel. The apparatus generates the uninterrupted handoff tables and the partial uninterrupted handoff tables and detects a handoff event initiated by acquisition failures on a current RF, and the uninterrupted handoff tables and the partially uninterrupted hand Processing logic configured to select a selected RF channel from the off tables. The apparatus also includes channel switch logic configured to perform handoff to the selected RF channel.

Description

HANDOFF IN A MULTI-FREQUENCY NETWORK}

This patent application contains provisional application No. 60 / 896,255 entitled "Methods and Apparatus for Providing Handoff in Multiple Frequency Networks" filed March 21, 2007, and "Methods and Apparatus filed June 20, 2007." Provisional Application No. 60 / 945,292 entitled "for Providing Handoff in a Multiple Frequency Network" is a priority, both of which are assigned to the applicant and specifically incorporated herein by reference.

This application is filed on April 4, 2007, entitled Provisional Application No. 60 / 910,191, entitled "Methods and Apparatus for Providing Flow Data Acquisition Priority Scheme in a Multiple Frequency Network," and issued June 20, 2007. Provisional Application No. 60 / 945,317 entitled "Methods and Apparatus for Providing Flow Data Acquisition Priority Scheme in a Multiple Frequency Network", both of which are assigned to the applicant and specifically incorporated herein by reference.

FIELD This application relates generally to the operation of data networks, and more particularly to methods and apparatus for RF channel selection in a multi-frequency network.

Data networks, such as wireless communication networks, must trade off between customized services for a single terminal and services provided to a large number of terminals. For example, distributing multimedia content to a large number of resource-constrained portable devices (subscribers) is a complex problem. It is therefore important for network operators, content sellers, and service providers to have a way to distribute content and / or other network services in a fast and efficient manner and in a way that increases bandwidth usage and power efficiency.

Multi-frequency netwrok (MFN) is a network in which multiple radio frequencies (RFs) (or RF channels) are used to transmit media content. Some types of MFNs are horizontal multi-frequency networks (HMFNs) in which a distribution waveform is transmitted over different RF channels in different local regions. The same or different content may be transmitted as part of the distributed waveforms carried on different RF channels in these local regions. Another type of MFN is a Vertical Multi-Frequency Network (MFN), where a local area is given for transmitting independent distributed waveforms for the purpose of increasing network capacity (in terms of the ability to deliver more content to device / end users). Multiple radio frequency (RF) channels are used. MFN deployment may also consist of VMFNs in certain other zones and HMFNs in certain other zones.

In a typical HMFN, a local operations infrastructure (LOI) includes transmission points that operate to transmit a single distributed waveform over a selected RF channel. In a typical VMFN, a local operation infrastructure (LOI) includes transmission points that operate to transmit multiple distributed waveforms over multiple RF channels in a selected region. Each distributed waveform may include one or more content flows that may be selected at a receiving device for rendering. Neighbor LOIs may use the same RF channels or may use different RF channels.

During operation, the receiving device may perform RF handoff as a result of data acquisition failures for the desired content. For example, acquisition failures may occur due to fluctuations in channel conditions as a result of device mobility. Typically, the device can handoff to any available RF channel that carries the desired content. However, if the device randomly handoffs to any RF channel that has the desired content, then the LOI associated with the selected RF channel may not have other content that is common with the current LOI. In addition, the LOI associated with the selected RF channel may not have any additional content that is not currently available in the LOI. For example, the LOI associated with the selected RF channel may have less common content (with current LOI) than the LOIs associated with other available RF channels that retain the desired content. This situation may result in the device not accessing common content and additional content after RF handoff, which will adversely affect the user experience.

It is therefore desirable to have a handoff mechanism that operates to enable the device to perform handoffs in a multi-frequency network in a fast and efficient manner and to maximize common and additional content for improved user experience.

In one or more aspects, a handoff system is provided that includes methods and apparatus that operate to provide handoff in a multi-frequency network. For example, when a handoff event is detected, the handoff system determines a new RF channel that the device can tune to receive the desired content. The handoff system operates to determine a new RF channel by considering a number of factors, including but not limited to signal strength, content availability, and other factors. After switching to the new RF channel, the device has the ability to receive the desired content and to switch to additional content that is available on other RF channels in the associated LOI in a fast and efficient manner.

In one aspect, a method for RF channel handoff in a multi-frequency network is provided. The method comprises creating seamless handoff tables and partially seamless handoff tables for multiplexes currently held in a LOI, the seamless handoff tables and partially unauthorized The section handoff tables include neighboring RF channels carrying one or more of the multiplexes of the current LOI; Detecting a handoff event initiated by acquisition failures on the current RF; Selecting the selected RF channel from the seamless handoff tables and the partial seamless handoff tables; And performing a handoff to the selected RF channel.

In one aspect, an apparatus for RF channel handoff in a multi-frequency network is provided. The apparatus comprises processing logic configured to generate the interruption handoff tables and the partial interruption handoff tables for multiplexes held in the current LOI—the interruption handoff tables and the partial interruption Handoff tables include neighboring RF channels that hold one or more of the multiplexes of the current LOI, and the processing logic detects a handoff event initiated by acquisition failures on current RF and the disconnected hand. Further configured to select a selected RF channel from the off tables and the partially disconnected handoff tables; And channel switch logic configured to perform a handoff to the selected RF channel.

In one aspect, an apparatus for RF channel handoff in a multi-frequency network is provided. The apparatus may further comprise means for creating breakdown handoff tables and partially breakdown handoff tables for multiplexes held in a current LOI, wherein the breakdown handoff tables and partially breakdown handoff tables Neighboring RF channels having one or more of the multiplexes of the current LOI; And means for detecting a handoff event initiated by acquisition failures on the current RF. The apparatus also includes means for selecting a selected RF channel from uninterrupted and partially uninterrupted handoff tables; And means for performing a handoff to the selected RF channel.

In one aspect, a computer program product for RF channel handoff in a multi-frequency network is provided. The computer program product includes a first set of codes for causing a computer to generate uninterrupted handoff tables and partial uninterrupted handoff tables for multiplexes held in a current LOI—the uninterrupted handoff Tables and partial uninterrupted handoff tables include neighboring RF channels having one or more of the multiplexes of the current LOI; And a second set of codes for causing the computer to detect a handoff event initiated by acquisition failures on current RF. The computer program product also includes a third set of codes for causing the computer to select a selected RF channel from the uninterrupted handoff tables and the partially uninterrupted handoff tables; And a fourth set of codes for causing the computer to perform a handoff to the selected RF channel.

In one aspect, at least one integrated circuit is provided that is configured for RF channel handoff in a multi-frequency network. The at least one integrated circuit is configured to generate interruption handoff tables and partial interruption handoff tables for multiplexes held in a current LOI—the interruption handoff tables and partial Disconnection handoff tables include neighboring RF channels having one or more of the multiplexes of the current LOI; And a second module configured to detect a handoff event initiated by acquisition failures on the current RF. The at least one integrated circuit further comprises a third module configured to select a selected RF channel from the uninterrupted handoff tables and the partially uninterrupted handoff tables; And a fourth module configured to perform handoff to the selected RF channel.

Other aspects will become apparent after a review of the following detailed description, examples, and claims.

The foregoing aspects described herein will become more readily apparent with reference to the following description in connection with the accompanying drawings.

1 shows a network illustrating the operation of aspects of a handoff system for use in a multi-frequency network.

2 illustrates a transmission frame and neighbor description information for use in aspects of a handoff system.

3 illustrates RF channel selection logic for use in aspects of a selection system.

4 illustrates an example interruption handoff table applicable for use as a wide area or local interruption handoff table in aspects of a handoff system.

FIG. 5 illustrates an exemplary seamless handoff table applicable for use as a wide area + local seamless handoff in aspects of a handoff system.

FIG. 6 illustrates an example partial uninterrupted handoff table applicable for use as a wide, local, or wide + local partial uninterrupted handoff table in aspects of a handoff system.

7 illustrates a method for performing handoff for use in aspects of a handoff system.

8 illustrates a method for performing a handoff procedure for use in aspects of a handoff system.

9 illustrates a method for providing a handoff event trigger for activated flows for use in aspects of a handoff system.

10 shows a method for providing a handoff event trigger for triggered flows for use in aspects of a handoff system.

11 illustrates a method for providing a handoff event trigger for registered flows for use in aspects of a handoff system.

12 illustrates a method for providing a handoff event trigger for registered flows for use in aspects of a handoff system.

13 shows examples of an uninterrupted handoff tables for use in aspects of a handoff system.

14 shows examples of partial uninterrupted handoff tables for use in aspects of a handoff system.

15 illustrates RF handoff logic for use in aspects of a handoff system.

In one or more aspects, a handoff system is provided that operates in a device to determine an RF channel in a multi-frequency network where handoff may be performed such that desired content can be received. In one aspect, the handoff system combines information related to neighboring RF channels with the content they hold. This information is combined into both uninterrupted and partially uninterrupted handoff tables. If data acquisition for the desired content fails, a handoff event is initiated. If a handoff event is detected, the handoff system operates to process the generated handoff tables to determine a new RF channel that the device can switch to receiving the desired content.

The system is well suited for use in wireless network environments, but is not limited to communication networks, public networks such as the Internet, private networks such as virtual private networks (VPNs), local area networks, wide area networks. Can be used in any type of network environment, including long haul networks, or any other type of data network.

Definitions

The following definitions are used herein to describe aspects of the selection system.

1. Local Area-refers to a local area, such as a building, a group of buildings, a community, a city, a county or other local area, through which services can be broadcast.

2. Wide Area-refers to a wide area such as a county, state, multiple states, states, multiple countries, or other wide area areas in which services may be broadcast.

3. Multiplex-refers to the grouping of content flows.

4. Wide Area Multiplexing-refers to the grouping of content flows broadcast over at least one wide area.

5. Local Area Multiplex-Refers to a grouping of content flows broadcast over at least one local area.

6. Wide Area Operation Infrastructure (WOI) —A grouping of transmitters and interworking systems that operate to transmit content flows over a wide area. WOI maps to the smallest geographic area that can hold a wide area multiplex. A wide area multiplex can be broadcast over one or more WOIs.

7. Local Area Operation Infrastructure (LOI) —A grouping of transmitters and interworking systems that operate to transmit content flows over a local area. The LOI maps to the smallest geographic local area that can hold a local area multiplex. The local area multiplex may be broadcast over one or more LOIs.

8. RF Channel—Refers to the RF frequency used to convey the content distribution waveform over the selected LOI.

9. Content Channel—Indicates the selected content flows within a particular distributed waveform. For example, a distributed waveform can include a number of content channels, each of which can include one or more content flows.

Abbreviations

The following abbreviations are used herein to describe aspects of the selection system.

LM-Local Area Multiplex

WM-Wide Area Multiplex

NOC-Network Operations Center

WOI-Wide Area Operations Infrastructure

LOI-Local Area Operations Infrastructure

NDM-Neighbor Description Message

WID-Wide Area Descrambling Identifier

LID-Local Area Descramble Identifier

OIS-Overhead Information Symbols

CC-control channel

1 shows a network 100 illustrating the operation of aspects of a handoff system for providing RF channel selection in a multi-frequency network. For example, network 100 includes four WOIs (WOI1, WOI2, WOI3, and WOI4) each comprising one LOI (LOI1, LOI2, LOI3, and LOI4) of a multi-frequency network. Within each LOI, one or more RF channels are used to transmit content. LOI2 and LOI3 have a vertical MFN with two RF channels in each of these LOIs. LOI1 and LOI4 have only one RF channel. Each RF channel has an associated WID / LID that identifies descrambling sequences that can be used to descramble content transmitted over that RF channel. LOI1, LOI2, LOI3, and LOI4 are neighbor LOIs as shown in network 100. LOI1 has LOI2 as its neighbor, LOI2 has LOI1, LOI3 and LOI4 as its neighbors, LOI3 has LOI2 as its neighbor, and LOI4 has LOI2 as its neighbor.

Network 100 includes a network operation center (NOC) 102 that operates to receive wide area and local content multiplexes for distribution across selected wide area and local areas of a multi-frequency network. NOC 102 also operates to configure a multi-frequency network to distribute its content. To achieve this, NOC 102 may be needed to configure the geographical areas of the network covered by the LOIs, the RF channels used in each area, and to configure the network to distribute wide area and local area content multiplexes. Recognize any other network information that exists. It should be noted that the network 100 may include any number of LOIs.

In one aspect, NOC 102 includes neighbor description logic 104. Neighbor description logic 104 is operative to collect information related to the list of neighbor LOIs for each LOI and WID / LID descrambling identifiers associated with the RF channels of each LOI. For example, wide area and local area content multiplexes are scrambled into wide area and local area scrambling sequences prior to transmission across the network 100. In an aspect, neighbor description logic 104 is configured to provide a list of WID / LID identifiers that identify descrambling sequences associated with a particular LOI and RF channels of the neighboring LOIs, and a list of neighboring LOIs associated with the particular LOI. Operate to generate description messages (NDMs). In another aspect, the NDM messages are configured to provide a list of neighboring LOIs and WID / LID identifiers associated with the RF channels for any selected group of LOIs. A more detailed description of the NDM messages generated by the neighbor description logic 104 is provided elsewhere herein.

The NOC 102 operates to send wide area and local area multiplexes and the generated NDMs to the LOIs of the network 100. Although only four LOIs are shown, it should be noted that NOC 102 may send multiplexes and associated NDMs to any number of LOIs.

In one aspect, LOI1, LOI2, LOI3, and LOI4 include one or more transmitter points. For example, LOI1 includes transmitter point 106. Each transmitter point operates to transmit a distributed waveform over a selected RF channel for its respective LOI. Each transmitter point includes one or more servers as shown at 108.

In one aspect, NOC 102 operates to send content multiplexes and NDMs to transmitter points using any suitable transport mechanism. For example, content multiplexes and NDMs are sent to servers associated with each transmitter point, as shown at 110. In one aspect, the NOC 102 sends content multiplexes and NDM messages to transmitter points using an MPEG-2 transport mechanism. In this configuration, MPEG-2 transport identifiers are assigned to multiplexes and NDM messages so that servers at each transmitter point can respectively detect and receive selected content multiplexes and NDM messages directed to them.

Servers at the transmitter points use the transport identifiers to determine which multiplexes and NDM messages are intended to distribute across their LOIs. The servers then operate to pack their multiplexes and NDM messages for transmission on selected RF channels. Servers use any suitable physical layer process to pack multiplexes and NDM messages into transport frames for transmission. Servers at the transmitter points use transmission identifiers to determine NDM messages and multiplexes intended for transmission across respective LOIs, so that servers at the transmitter points need to decode any multiplexes or NDM messages. none. The servers simply need to detect the appropriate transport identifiers and then pack the identified multiplexes and the NDM message into transport frames according to the physical layer process.

Transport frames include NDM messages generated by neighbor description logic 104 and content flows associated with wide area and local area multiplexes. In one aspect, the transmission frames include wide area and local data partitions used to convey wide area and local area content flows, respectively. In addition, wide area and local partitions include wide area and local control channels. In one aspect, the local control channel is used to distribute the NDM message generated by the neighbor description logic 104 to the devices of each LOI.

In one aspect, transmitter points transmit transmission frames over respective LOIs using designated RF channels. By using multiple RF channels of LOIs to transmit transmission frames, network 100 can transmit more content flows over those LOIs. It should be noted that the transmitter points within the LOI may be co-located or may be separated by any desired distance. Because each LOI may have a different set of neighboring LOIs and each neighboring LOI may be associated with different RF channels and associated with descrambling sequences to descramble the transmitted content, over each LOI. Note that distributed NDMs can be different.

Within each LOI, descrambling sequence identifiers are associated with each RF channel. The descrambling sequence identifiers include global descrambling sequence identifiers (WID) and local area descrambling sequence identifiers (LID). Descrambling sequence identifiers identify descrambling sequences that can be used to descramble content received at a particular LOI over a particular RF channel. The descrambling sequence identifiers also identify content multiplexes held on a particular RF channel. For example, LOI2 has two RF channels (ie RF2, RF3), each RF channel descrambling identifying descrambling sequences that can be used to descramble the associated wide area and local area content multiplexes. Associated with sequence identifiers. For example, RF2 is associated with WID1 and LID1 and has a wide area multiplex WM1 and a local multiplex LM1; RF3 is associated with WID2 and LID2 and has a wide area multiplex WM2 and a local multiplex LM2. WID1, LID1, WID2 and LID2 identify the multiplexes WM1, LM1, WM2 and LM2, respectively.

Device 112 operating at LOI2 is adapted to receive wide area content over channel RF2, which may be descrambled with the descrambling sequence identified by WID1. Details of the device 112 are shown at 114. The device 112 includes a receiver 116 that operates to tune to a selected RF channel for receiving transmission frames. For example, receiver 116 is tuned to RF2 of LOI2 to receive transmission frames. The received transmission frames include a local control channel that carries neighbor description information in one or more NDMs. For example, NDMs are generated by neighbor description logic 104 and distributed to the LOIs shown in FIG. 1. In one aspect, the NDM is a list of neighboring LOIs for a device's current LOI (ie, LOI2 for device 112), and the current LOI (ie, LOI2) and its neighboring LOIs (ie, LOI1, LOI3 and WID / LID descrambling identifiers that identify the descrambling sequences associated with the RF channels of LOI4).

Receiver 116 passes the neighbor description information (or NDM itself) received at the NDM to RF handoff logic 118, as shown at 122. Receiver 116 also descrambles the received content using the correct WID / LID identifiers associated with RF2 of LOI2 and delivers the descrambled content to decoder 120 operative to provide content for the device user.

RF handoff logic 118 operates to receive an NDM of 122. The NDM specifies a list of neighbor LOIs for a given LOI, and WID / LID identifiers for the RF channels of the given LOI and its neighboring LOIs. From this information, the RF handoff logic 118 operates to generate unceasing handoff tables and partial unceasing handoff tables for content multiplexes held in the device's current LOI. Uninterrupted and partially uninterrupted handoff tables for a given content multiplex held in the current LOI provide a list of neighbor RFs that can be switched to obtain a given content multiplex. Uninterrupted and partially uninterrupted handoff tables are calculated separately for wide area and local content multiplexes. For example, if a neighbor RF channel has a given wide content multiplex and the LOI associated with the neighbor RF channel has the same set or superset of wide content multiplexes as the device's current LOI, Has an entry in the wide area uninterrupted handoff table associated with a given wide area content multiplex currently held in the LOI. If the neighbor RF channel has a given wide content multiplex and the LOI associated with the neighbor RF channel does not have the same set or superset of wide area content multiplexes as the device's current LOI, the neighbor RF channel is held at the current LOI. It has an entry in a partial, uninterrupted handoff table of a wide area associated with a given wide area content multiplex.

In one aspect, RF handoff may be desirable due to one or more handoff events. The handoff event causes the handoff logic 118 to determine a new RF channel and send a request 124 to the receiver 116 to adjust to the new RF channel. Handoff events are events that cause device 112 to switch from one RF channel to another to receive the desired content flow. In one aspect, the handoff event may be performed or triggered as a result of content acquisition failures (eg, failures due to fluctuations in channel conditions due to device movement) associated with the desired content.

In one aspect, content acquisition failures associated with device mobility occur when device 112 moves from an area covered by LOI2 to an area covered by one or more neighboring LOIs. For example, device receiver 116 is adapted to receive the desired content flow over a particular RF channel of LOI2. The RF handoff logic 118 is the RF of the neighboring LOI that can be adjusted to keep the receiver 116 receiving the desired content flow when a content acquisition failure is detected as the device 112 moves out of the coverage area of LOI2. Operate to determine the channel.

To determine a new RF channel with a desired content flow, RF handoff logic 118 operates to perform one or more of the following functions in aspects of the handoff system.

1. Determine (from received neighbor description information) a list of RF channels available in neighboring LOIs that have a desired content flow so that a smooth transition can be performed in terms of content acquisition.

2. Monitor signal strength of neighboring RF channels.

3. Create uninterrupted and partial uninterrupted handoff tables for the desired content. These tables have entries based on the list of available RF channels and the content available in the LOIs associated with these RF channels.

4. Rank the RF channels in the uninterrupted and partially uninterrupted tables.

5. Select the selected RF channel from the seamless handoff table based on the ranking, wherein the selected RF channel meets the RF selection criteria.

6. Select the selected RF channel from the partial uninterrupted handoff table based on the ranking, wherein the selected RF channel meets the RF selection criteria if the selection from the uninterruptible handoff table fails.

Once the RF channel is determined, RF handoff logic 118 outputs an RF channel switch message 124 to receiver 116 to implement RF handoff. The RF channel switch message contains the correct WID / LID identifiers for the selected RF channel, so that the desired content flow can be descrambled by the receiver 116. Receiver 116 performs RF channel switching to the selected RF channel and descrambles the content using the WID / LID received in the channel switching message.

Thus, in various aspects, the handoff system may handoff any of the available RF channels of the multi-frequency network so that the desired content can continue to be received after content acquisition failures for the desired content are detected. Operate to determine whether to select for. The handoff system determines the selected RF channel based on the uninterrupted and partial uninterrupted handoff tables used to rank the available RF channels. The handoff system thus operates to select the available RF channel with the highest ranking that meets the RF selection criteria. RF selection criteria ensure that the selected RF channel has a sufficiently large received signal strength indicator (RSSI) value and also meets RF handoff criteria. Details of the RF handoff criteria are provided in other parts of this specification.

2 shows a diagram of a transmission frame 200 for use in aspects of a handoff system. For example, the transmission frame 200 may be packed into wide area and local content multiplexes and transmitted on the RF channels of the LOIs shown in FIG. 1.

The transmission frame 200 includes four sub-frames, shown generally at 202, used to convey wide area and local content. For example, each sub-frame 202 includes a wide area partition 204 packed with wide area content, and a local area partition 206 packed with local area content.

The global control channel 208 is included in the global partition 204. The wide area control channel 208 operates to convey messages related to wide area content multiplexes. Local area control channel 210 is included in local area partition 206. Local area control channel 210 operates to convey messages related to local area content multiplexes. In one aspect, the local area control channel is used to convey neighbor description information as part of an NDM message for use in aspects of the handoff system.

At the beginning of the transmission frame 200, overhead information symbols (OIS) 212 are used to place the wide area and local content packed within the wide area control channel, the local area control channel, and the sub-frames 202. Provides overhead information used. OIS 212 includes wide area overhead information symbols (WOIS) and local overhead information symbols (LOIS).

In one aspect, content flows are transmitted using Media Logical Channels (MLCs) within sub-frames 202. A single MLC can be used to hold one or more content flows. Content flow data can be successfully obtained even if all packets of the MLC are not received correctly because of redundancy added to the data transmitted as part of the MLC. If the MLC packet erasures exceed the allowed error threshold based on redundancy added to the data transmitted as part of the MLC, data acquisition for the content flow fails.

In one aspect, the neighbor description information included in the NDM message is configured for each LOI and configured to provide a list of RF channels associated with the selected LOI and its neighboring LOIs. In another aspect, the NDM message is generated for the LOIs (which may or may not be neighbors) of the selected group and includes all adjacent LOIs for each LOI of the LOIs of the selected group. Each RF channel described in the neighbor description information is associated with WID / LID descrambling identifiers.

In one aspect, the NDM message is distributed over the LOI using a local control channel that is part of the transmission frames transmitted by the RF channels of the LOI. Neighbor description information held in the NDM may be formatted, encoded or encrypted in any suitable format, and / or partitioned or reorganized into two or more message components.

Table 214 illustrates how the parameters provided in the NDM message can be configured and stored at the device. Table 214 includes a LOI identifier 216 that identifies the current LOI (ie, LOI2) of the device. The table 214 also includes a neighbor LOI list 218 that identifies the current LOI itself, along with the neighbor LOIs of the device's current LOI. The table 214 includes RF channel identifiers 220 that represent identifiers that can be used to refer to specific RF channels of the current LOI in other control channel messages. Note that RF channel identifiers 220 are provided only for the current LOI (ie, LOI2).

Table 214 also includes RF frequency identifiers 222 that identify the RF frequencies associated with each LOI identified in neighboring LOI list 218. The table 214 also includes WID / LID identifiers 224 that identify WID / LID descrambling sequence identifiers associated with each RF frequency 222. Thus, the table 214 can be created and stored at the receiving device and used during operation of the handoff system.

3 illustrates RF handoff logic 300 for use in aspects of a handoff system. For example, the RF handoff logic 300 may be suitable for use as the RF handoff logic 118 shown in FIG. 1. RF handoff logic 300 includes processing logic 302, message decoder 304, channel switching logic 310, and overhead input logic 306, all of which are coupled to data bus 308. .

Overhead input logic 306 includes at least one of a CPU, processor, gate array, hardware logic, memory elements, and / or hardware execution software. Overhead input logic 306 operates to receive OIS and control channel data over an RF channel on which the device is currently being adjusted. Overhead input logic 306 passes the received CC data to message decoder 304. For example, overhead input logic 306 operates to receive an NDM message sent over a local control channel as shown in FIG.

The message decoder 304 includes at least one of a CPU, a processor, a gate array, hardware logic, memory elements, and / or hardware execution software. In one aspect, the message decoder 304 operates to decode the NDM message received by the control channel input logic 306. For example, message decoder 304 operates to decode the received NDM message to determine available RF channels associated with the current LOI and its neighboring LOIs. The message decoder 304 decodes the received NDM message to determine the WID / LID descrambling sequence identifiers associated with each RF channel in the device's current LOI and its neighboring LOIs. For example, the information received in the NDM message may be configured and stored as shown in FIG. 2 to provide WID / LID descrambling identifiers associated with RF channels in the device's current LOI and its neighboring LOIs.

Processing logic 302 includes at least one of a CPU, processor, gate array, hardware logic, memory elements, and / or hardware execution software. In one aspect, processing logic 302 is a handoff event indicating that RF handoff is desirable due to changes in network conditions (eg, due to device mobility) or because of data acquisition failures associated with the desired content for other reasons. To receive it. In such a case, it may be necessary to perform a handoff to switch to the RF channel of the neighboring LOI with the desired content in order to continue receiving the desired content.

Processing logic 302 is operative to process the information received in the NDM to generate uninterrupted and partial uninterrupted handoff tables for the desired content. In one aspect, processing logic 302 collects handoff tables to include RF channels of neighboring LOIs associated with the WID / LID of the desired content. In one aspect, neighboring RF channels associated with the same WID have the same wide area content, and neighboring RF channels associated with the same LID have the same local area content. In one aspect, the handoff tables include wide area, local, and wide + local uninterrupted and partially uninterrupted handoff tables.

Once the RF channels are determined in the handoff tables, processing logic 302 operates to determine signal strength information related to those RF channels. For example, processing logic 302 is operative to perform RF monitoring on neighboring RFs to receive signal strength parameters associated with the RF channels identified in the uninterrupted and partially uninterrupted handoff tables. For example, in one aspect, this information is obtained from a device receiver, such as receiver 116 shown in FIG.

Processing logic 302 also operates to determine information about the content available for LOIs associated with respective RF channels of the handoff tables. For example, the content information includes the number of common multiplexes currently available in the LOI, and the total number of multiplexes available in each identified LOI. Processing logic 302 operates to use the content information to rank the RF channels of the uninterrupted and partially uninterrupted handoff tables.

Processing logic 302 is operative to receive a handoff event. The handoff event indicates that handoff to another RF channel is required to continue obtaining the desired content. For example, a handoff event may indicate that handoff is desirable because of content acquisition failures for the desired content due to changes in network conditions.

If a handoff event for the desired content is detected, processing logic 302 operates to process the RF channels of the uninterrupted handoff table associated with the desired content to determine the selected RF channel for the handoff. If there are no RF channels in the associated seamless handoff table, or if the RF channels in the associated seamless handoff table do not meet the RF selection criteria, the processing logic 302 desires to determine the selected RF channel for the handoff. It handles the RF channels of the partial uninterrupted handoff table associated with the content. Processing logic 302 is operative to process the RF channels of the uninterruptible handoff table and the partially uninterrupted handoff table according to their ranking order. Once the selected RF channel is determined, processing logic 302 communicates the identity of this RF channel to channel switching logic 310. A more detailed description of the operation of processing logic 302 to select a selected RF channel from the handoff tables is provided elsewhere herein.

Channel switch logic 310 includes at least one of a CPU, a processor, a gate array, hardware logic, memory elements, and / or hardware execution software. Channel switch logic 310 operates to generate an RF channel switch message that includes the identity of the selected RF channel and its WID / LID descrambling sequence identifiers. The RF channel switch message is sent to the device receiver 116. Using this information, receiver 116 can quickly switch to the selected RF channel and use the received WID / LID descrambling sequences to receive the desired content. Thus, during handoff, the RF channel that provides the desired content, meets the RF selection criteria, and is ranked at the top in terms of common content (in the current LOI) and additional content held in the associated LOI for improved user experience. Can be.

In one aspect, the handoff system is embedded in or stored in a machine-readable medium that, when executed by a processor such as, for example, the processor of processing logic 302, causes the computer to provide the functions described herein. Computer program product having a set of " codes " or one or more program instructions (" instructions "). For example, sets of codes may be a floppy disk, CDROM, memory card, flash memory device, RAM, ROM, or any other type of memory device or machine-readable medium that interfaces to RF handoff logic 300. It may be loaded into the RF handoff logic 300 from the machine-readable medium. In another aspect, the sets of codes may be downloaded to the RF handoff logic 300 from an external device or network resource. The sets of codes allow the computer at runtime to provide aspects of a handoff system as described herein.

RF channel monitoring

In one aspect, the handoff system of the device is operative to perform monitoring of these RF channels held in the device's current LOI and neighboring LOIs to maintain information related to the signal strength for the RF channels. For example, processing logic 302 operates to obtain a received signal strength indicator (RSSI) for the RF channels of the current LOI and neighboring LOIs. In addition, for each available RF channel, processing logic 302 may maintain a timestamp associated with RSSI measurements. Time stamps associated with RSSI measurements may be used to invalidate previous RSSI entries. Processing logic 302 operates to maintain tables of RF channel monitoring information in local memory. During handoff, processing logic 302 uses the information collected during RF channel monitoring to select an RF channel for handoff purposes. For example, signal strength information is used to evaluate the RF channels of the uninterrupted and partial uninterrupted handoff tables for handoff purposes.

Wide Area and Local Content Handoffs

In one aspect, the handoff system operates to initiate RF handoff based on handoff events. RF handoff may be initiated for wide area content flows and / or local content flows. In one aspect, if the device is attempting to decode only the desired wide area content flows and content acquisition failures are detected, wide area content RF handoff will be initiated. In one aspect, if the device is attempting to decode only the desired local content flows and content acquisition failures are detected, local content RF handoff will be initiated. In another aspect, if the device is attempting to decode both the desired wide area flow and local flow and content acquisition failures are detected, wide area + local content RF handoff will be initiated. Wide area content RF handoff aims at a handoff to RF having at least the desired wide area content. Local content RF handoff aims at handoff to at least RF having desired local content, and wide + local content RF handoff aims at handoff to RF having both desired wide area and local content. The particular RF handoff type (wide, local or wide + local) will initiate a handoff to the RF channel of the associated uninterrupted or partially uninterrupted handoff table. For example, wide area content RF handoff will initiate a handoff to an RF channel of an uninterrupted or partial uninterrupted handoff table associated with the desired wide area content.

Real-time and non-real-time content handoff

The handoff event may be initiated when the device is attempting to acquire real time content flows and content acquisition failures occur. The handoff event may also be initiated when the device is attempting to acquire non real time content flows and content acquisition failures occur. Real-time flows are also referred to as activated flows, and non-real-time flows are referred to as registered flows. The data acquisition procedure for capturing data for these flows can be performed in a variety of ways. For example, one data acquisition procedure for capturing data for invoked (real-time) flows and registered (non-real-time) flows is described in the application cited above, filed April 4, 2007, " Methods and Apparatus for Providing Flow Data Acquisition Priority Scheme in a Multiple Frequency Network, Provisional Application No. 60 / 910,191, and "Methods and Apparatus for Providing Flow Data Acquisition Priority Scheme in a Provisional Application No. 60 / 945,317 entitled "Multiple Frequency Network". The handoff process for executing RF handoff is the same for both started flows and registered flows, but the handoff process may operate for different timer periods for launched flows and registered flows. . A detailed description of the handoff process for launched flows and registered flows is provided in other parts of this specification.

By handoff event trigger

In one aspect, the handoff event is triggered by specific criteria related to the started flows and registered flows. Handoff event trigger criteria are evaluated separately for launched flows and registered flows. If both started flows and registered flows are being decoded, the handoff event trigger criteria is evaluated only for the started flows. This is because flows that are started (ie, real time flows) are given higher priority than registered flows (ie, non-real time flows). Failure to obtain the appropriate set of overhead information, including the OIS and control channel (CC), will trigger a handoff event for both launched and registered flows. Overhead information is used to obtain flow data for launched flows and registered flows.

In various aspects, a handoff event is triggered for flows initiated under one or more of the following conditions.

1. Failure to obtain the appropriate OIS and control channel (CC) (if required) for the desired wide area and / or local initiated flows. For example, if only wide activated flows are being decoded, WOIS and wide CC acquisition failure for the current RF.

2. Data acquisition failures for all launched flows on the current RF.

3. Failure of acquisition of local OIS and local CC (if required) when both wide area and local launched flows are being decoded on the current RF channel.

4. Data acquisition failures for a subset of flows invoked on the current RF.

To obtain the registered flows, the device determines the selected flow group (FG) and attempts to decode the registered flows associated with that selected FG. For example, in one aspect, a flow group includes a grouping of non-real-time data flows that are grouped together based on selected criteria such as priority. An example of various types of flow groups is Provisional Application No. 60 / 910,191, entitled "Methods and Apparatus for Providing Flow Data Acquisition Priority Scheme in a Multiple Frequency Network, filed April 4, 2007". And Provisional Application No. 60 / 945,317, entitled "Methods and Apparatus for Providing Flow Data Acquisition Priority Scheme in a Multiple Frequency Network," filed June 20, 2007. The device also attempts to decode any other registered flows held by the same RF channel as the selected FG. In various aspects, a handoff event is triggered for registered flows in one or more of the following conditions.

1. Failure to obtain the appropriate OIS and CC (if required) for wide area and / or locally registered flows in the selected flow group (FG). For example, if the selected FG has only wide registered flows, it fails to obtain WOIS and wide CC.

2. Data acquisition failures for all registered flows of the selected FG.

3. Acquisition failures of the local OIS and the local CC (if needed) if the selected FG includes both wide area and locally registered flows.

4. Data acquisition failures for a subset of registered flows of the selected FG.

Uninterrupted Handoff Tables

In one aspect, the handoff system operates to generate and maintain uninterrupted handoff tables for wide area and local content multiplexes held on RF channels of the current LOI. In one aspect, the seamless handoff table for a given wide area or local content multiplex includes neighboring RF channels, each having a predetermined same wide area or local content multiplex, and the LOI associated with the neighboring RF channel is retained in the current LOI. It holds the same set or superset of global or local content multiplexes. In one aspect, the seamless handoff table for any combination of wide area + local multiplexes includes neighboring RF channels having the same combination of wide area + local content multiplexes, and the LOI associated with the neighboring RF is currently held in the LOI. It holds the same set or superset of the same wide area and local content multiplexes. Neighbor RFs included in a given uninterrupted handoff table are referred to as uninterrupted RFs for the associated content multiplex (es).

The following types of seamless handoff tables are maintained.

a. Wide Area Handoff Table: A separate wide area handoff table is created and maintained for each wide area content multiplex currently held in the LOI. This table identifies neighboring RF channels that have the same wide content multiplex, and their associated LOI holds the same set or superset of wide area content multiplexes as the current LOI.

b. Local Uninterruptible Handoff Table: A separate local uninterrupted handoff table is created and maintained for each local content multiplex currently held in the LOI. This table identifies neighboring RF channels that have the same local content multiplex, and their associated LOI holds the same set or superset of local content multiplexes as the current LOI.

c. Wide + Local Uninterruptible Handoff Table: A separate wide + local uninterruptible handoff table is created and maintained for each combination of wide + local content multiplexes held in a single RF of the current LOI. This table identifies neighboring RF channels that have the same combination of wide + local content multiplexes, and their associated LOI holds the same set or superset of wide + local content multiplexes as the current LOI.

Depending on the content held by neighboring RFs, the seamless handoff tables may be empty for one or more content multiplexes (wide, local or wide + local) currently held in the LOI. In one aspect, the seamless handoff table includes (i) the total number of wide area and local content multiplexes common between the LOI associated with the uninterrupted RF channel and the current LOI of the device; And (ii) maintain information for each uninterrupted RF channel relating to the total number of content multiplexes held in the LOI associated with the uninterrupted RF channel. Information (i) and (ii) maintained for the uninterrupted RF channels are used to rank these RF channels for the purpose of performing RF handoff.

4 illustrates an example interruption handoff table 400 applicable for use as a wide area or local interruption handoff table in aspects of a handoff system. In one aspect, the seamless handoff table 400 is generated by the processing logic 302. The seamless handoff table 400 includes a content multiplex identifier 402 that identifies a wide area or local content multiplex generated in such a seamless handoff table. The uninterrupted handoff table 400 also includes an {RF, LOI} identifier 404 that identifies the RF frequency and the associated adjacent LOI having the wide or local content multiplex identified by the content multiplex identifier 402. do. The seamless handoff table 400 also includes a total number indicator 406 of common multiplexes that indicates the total number of multiplexes common between the LOI associated with the identified RF and the current LOI. The seamless handoff table 400 also includes a total number of multiplex indicator 408 indicating the total number of multiplexes available for the LOI associated with the identified uninterrupted RF.

5 illustrates an example wide area + local uninterrupted handoff table 500 applicable for use in wide area + local uninterrupted handoff in aspects of a handoff system. In one aspect, the global + local uninterrupted handoff table 500 is generated by the processing logic 302. The global + local uninterrupted handoff table 500 includes a content multiplex identifier 502 that identifies a combination of the global + local content multiplexes generated in this uninterrupted handoff table. The global + local uninterrupted handoff table 500 may also include a {RF, LOI} identifier 504 that identifies the associated adjacent LOI and RF frequency with the global + local content multiplexes identified by the content multiplex identifier 502. It includes. The seamless handoff table 500 also includes a total number of multiplex indicator 506 indicating the total number of multiplexes available for the LOI associated with the identified uninterrupted RF.

Partial uninterrupted handoff tables

In one aspect, the handoff system operates to generate and maintain partial uninterrupted handoff tables for the wide area and local content multiplexes held in the RF channels of the current LOI. In one aspect, the partial uninterrupted handoff table for a given wide area or local content multiplex includes neighbor RF channels, each holding a predetermined same wide area or local content multiplex, and the LOI associated with the neighbor RF channels is currently It does not have the same set or superset of wide area or local content multiplexes, respectively. In an aspect, the partially uninterrupted handoff table for a given combination of wide area + local multiplexes includes neighboring RF channels having the same combination of wide area + local content multiplexes, and the LOI associated with the neighboring RF channels is the current LOI. It does not have the same set or superset of wide area and local content multiplexes as it is held in. Adjacent RFs included in a given partial uninterrupted handoff table are referred to as partial uninterrupted RFs for the associated content multiplex (es). By definition, the sets of uninterrupted RFs and partially uninterrupted RFs for a given content multiplex disjoint.

In various aspects, the following types of partially disconnected handoff tables are maintained.

a. Wide, partially seamless handoff table: A separate, wide-area seamless handoff table is created and maintained for each wide-area content multiplex currently held in the LOI. This table identifies neighboring RF channels that hold the same wide content multiplex, and their associated LOI does not have the same set or superset of wide area content multiplexes as the current LOI.

b. Local partially seamless handoff table: A separate local partial seamless handoff table is created and maintained for each local content multiplex currently held in the LOI. This table identifies neighboring RF channels that hold the same local content multiplex, and their associated LOI does not hold the same set or superset of local content multiplexes as the current LOI.

c. Wide + Local Partial Seamless Handoff Table: A separate wide + local partial Uninterruptible Handoff table is created and maintained for each combination of wide area + local content multiplexes held in a single RF of the current LOI. This table identifies neighboring RF channels that hold a combination of the same wide area + local content multiplexes, and their associated LOI does not have the same set or superset of wide area + local content multiplexes as the current LOI.

Depending on the content held by neighboring RFs, the partial disconnected handoff tables may be empty for one or more of the content multiplexes (wide, local or wide + local) currently held in the LOI. In one aspect, the partial uninterrupted handoff table includes (i) the total number of wide area and local content multiplexes common between the LOI associated with the partial uninterrupted RF channel and the current LOI of the device; And (ii) for each partial uninterrupted RF channel information relating to the total number of content multiplexes retained in the LOI associated with the partially uninterrupted RF channel. The information (i) and (ii) maintained for the partially uninterrupted RF channels is used to rank these RF channels for the purpose of performing RF handoff.

FIG. 6 illustrates an example partial uninterrupted handoff table 600 applicable for use as a wide, local, or wide + local partial uninterrupted handoff table for use in aspects of a handoff system. . In one aspect, the partial uninterrupted handoff table 600 is generated by the processing logic 302. The partial uninterrupted handoff table 600 includes a content multiplex identifier 602 that identifies the wide area, local or wide + local content multiplexes generated in this partial uninterrupted handoff table. The partial uninterrupted handoff table 600 also includes a {RF, LOI} identifier that identifies the associated neighbor LOI and RF frequency with the wide, local or wide + local content multiplexes identified by the content multiplex identifier 602. 604.

The partial uninterrupted handoff table 600 also includes a total number of common multiplex indicators 606 that indicate the total number of multiplexes that are common between the LOI associated with the identified partial uninterrupted RF and the current LOI. Partial seamless handoff table 600 also includes a total number of multiplex indicator 608 that indicates the total number of multiplexes available for the LOI associated with the identified partial uninterrupted RF.

Handoff table examples

13 shows examples of seamless handoff tables 1300 for use in aspects of a handoff system. For example, it will be assumed that device 112 is operable to receive content multiplexes associated with WID1, WID2, LID1, LID2 that are currently located in LOI2 and transmitted on RF2 or RF3 of LOI2. Thus, the seamless handoff tables 1300 reflect the distribution of content in the network configuration shown in FIG. 1 when associated with the device 112 operating at LOI2.

The wide range handoff tables associated with the wide area content of LOI2 are shown at 1302 and 1304. The wide interruption handoff table 1302 is associated with the wide area content multiplex identified by WID1 and includes an uninterrupted RF channel RF4 of LOI3 having the same wide area content multiplex. Table 1302 also shows that LOI3 has four multiplexes in common with LOI2 and the total number of multiplexes held in LOI3 is four.

The wide range handoff table 1304 is associated with the wide range content multiplex identified by WID2, and includes the uninterrupted RF channel RF5 of LOI3 having the same wide range content multiplex. Table 1304 also indicates that LOI3 has four multiplexes common to LOI2 and that the total number of multiplexes held in LOI3 is four.

Local uninterrupted handoff tables are shown at 1306 and 1308. The local uninterrupted handoff table 1306 is associated with the local content multiplex identified by LID1 and includes an uninterrupted RF channel RF4 of LOI3 that holds the same local content multiplex. Table 1306 also indicates that LOI3 has four multiplexes common to LOI2 and that the total number of multiplexes of LOI3 is four.

The local uninterrupted handoff table 1308 is associated with the local content multiplex identified by LID2 and includes an uninterrupted RF channel RF5 of LOI3 that holds the same local content multiplex. Table 1308 also shows that LOI3 has four multiplexes in common with LOI2 and that the total number of multiplexes of LOI3 is four.

Wide + Local Uninterruptible Handoff Tables are shown at 1310 and 1312. Wide + Local Uninterruptible Handoff Table 1310 is associated with the combination of Wide + Local Content Multiplexes identified by WID1 + LID1 and has an uninterrupted RF channel RF4 of LOI3 having the same combination of Wide + Local Content Multiplexes. Include. Table 1310 also indicates that the total number of multiplexes of LOI3 is four.

Wide + local uninterrupted handoff table 1312 is associated with the combination of wide-area + local content multiplexes identified by WID2 + LID2, and has an uninterrupted RF channel RF5 of LOI3 having the same wide-area + local content multiplex combination. Include. Table 1312 also indicates that the total number of multiplexes of LOI3 is four.

Thus, the uninterrupted handoff tables 1300 can be used to provide wide and / or local content multiplexes of LOI2, uninterrupted RF channels for these content multiplexes and their associated LOI identifiers, and aspects of a handoff system. Identifies the multiplex information for LOIs associated with uninterrupted RFs for use in.

14 shows examples of partial uninterrupted handoff tables 1400 for use in aspects of a handoff system. For example, it will be assumed that device 112 is operable to receive content multiplexes associated with WID1, WID2, LID1, LID2 currently located at LOI2 and transmitted over RF2 or RF3 of LOI2. Thus, the partially disconnected handoff tables 1400 reflect the distribution of content in the network configuration shown in FIG. 1 when associated with the device 112 operating at LOI2.

The broad, uninterrupted handoff tables are shown at 1402. The partial, uninterrupted handoff table 1402 of the wide area is associated with the wide-area content multiplex identified by WID1 and has a partial uninterrupted RF channel RF1 of LOI1, and a partial of LOI4, having the same wide-area content multiplex. Uninterrupted RF channel includes RF6. For LOI1, table 1402 shows one total multiple of LOI1 with one multiplex in common with LOI2. For LO4, table 1402 has two multiplexes in common with LOI2 and indicates that the total number of multiplexes in LOI4 is two.

Local partial uninterrupted handoff tables are shown at 1404. The local partially uninterrupted handoff table 1404 is associated with the local content multiplex identified by LID1 and includes a partially uninterrupted RF channel RF6 of LOI4 having the same local content multiplex. Table 1404 also shows that LOI4 has two multiplexes in common with LOI2 and that the total number of multiplexes of LOI4 is two.

The wide + local partial uninterrupted handoff tables are shown at 1406. Wide + local partial uninterrupted handoff table 1406 is associated with a combination of wideband + local content multiplexes identified by WID1 + LID1, and an uninterrupted RF at LOI4 having the same wideband + local content multiplexes combination. Channel RF6. Table 1406 also indicates that LOI4 has two multiplexes in common with LOI2 and that the total number of multiplexes of LOI4 is two. Note that the partial uninterrupted handoff tables for WID2, LID2 and WID2 + LID2 are empty and thus not shown.

Thus, the partial uninterrupted handoff tables 1400 may include the wide and / or local content multiplexes of LOI2, partial uninterrupted RF channels for these content multiplexes and their associated LOI identifiers, and handoffs. Identify multiplex information for LOIs associated with partial uninterrupted RFs for use in aspects of the system.

RF Channel Ranking

In one aspect, the RF channels of the uninterrupted and partially uninterrupted handoff tables are ranked based on the information maintained in these tables. Neighbor RF channels included in the uninterrupted and partially uninterrupted handoff tables include: i) maximizing the number of wide area and / or local content multiplexes common between the LOI associated with the neighbor RF channel and the current LOI of the device; And ii) ranking is achieved to achieve maximization of the total total number of content multiplexes of the LOI associated with the neighboring RF channel. Adjacent disconnected and partially disconnected RF channels are evaluated in their ranking order for handoff execution to provide an improved user experience. In various aspects, neighboring RF channels of the wide area or local disconnection handoff table are ranked as follows.

1. A higher ranking is assigned to an RF channel having a greater number of common multiplexes in the associated LOI (in the current LOI of the device).

2. Of the RF channels with the same number of common multiplexes in the device's current LOI, a higher ranking is assigned to an RF channel with a greater number of total multiplexes in the associated LOI.

3. Among the RF channels with the same number of total multiplexes, a ranking may be assigned to the RF channels in any random order.

In various aspects, neighboring RF channels of the wide + local disconnection handoff table are ranked as follows.

1. A higher ranking is assigned to an RF channel with a larger number of total multiplexes of the associated LOI.

2. Of the RF channels having the same number of total multiplexes, the RF channels may be assigned a ranking in any random order.

In various aspects, neighboring RF channels of the wide, local and wide + local partial uninterrupted handoff tables are ranked as follows.

1. A higher ranking is assigned to an RF channel with a larger number of common multiplexes in the associated LOI (in the current LOI).

2. Of the RF channels with the same number of common multiplexes in the associated LOI, a higher ranking is assigned to the RF channel with the greater number of total multiplexes.

3. Among the RF channels with the same number of total multiplexes in the associated LOI, the ranking may be assigned to the RF channels in any random order.

In another aspect, RSSI values (if available) for RF channels having common wide area and / or local content multiplexes in associated LOIs may also be used to rank both uninterrupted and partially uninterrupted RF channels. have. Higher ratings may be assigned to both uninterrupted and partially uninterrupted RF channels with higher RSSI values associated with RF channels having common wide area and / or local content multiplexes in associated LOIs. This will provide better availability of common multiplexes in the new LOI after handoff. Uninterrupted and partially uninterrupted RF channels are evaluated in their ranking order to effect RF handoff. In one aspect, an uninterrupted or partially uninterrupted RF channel is considered for handoff only if the RSSI for the RF channel meets a signal strength criterion that is greater than a defined threshold.

Handoff Overview

RF handoff to the neighboring LOI's RF channel is initiated whenever a handoff event (ie, content acquisition failures) is detected for the desired content. RF channels of the uninterrupted and partial uninterrupted handoff tables associated with the desired content are considered to perform the handoff. A handoff RF list is created by combining the uninterrupted and partial uninterrupted RF channels associated with the desired content. Uninterrupted RF channels are listed higher than partial uninterrupted RF channels in the handoff RF list. In addition, separate sets of uninterrupted and partially uninterrupted RF channels are listed in their ranking order in the handoff RF list. RFs in the handoff RF list are evaluated for handoff in their listed order.

The handoff_trigger_RF parameter, which specifies the current RF channel when the handoff event is first initiated, is maintained. In order to perform a handoff to a particular neighbor RF, the neighbor RF must meet RF selection criteria. Meeting RF selection criteria includes meeting signal strength criteria and meeting handoff criteria where the RSSI of the selected RF channel must be greater than a defined threshold. Handoff criteria are evaluated in relation to handoff_trigger_RF. In one aspect, the neighbor RF meets the handoff criterion when keeping the following true.

RSSI> = Handoff_Trigger_RF RSSI + RSSI_Hysteresis of adjacent RF (1)

RSSI_Hysteresis is used to minimize ping ponging between the neighbor RF and the handoff_trigger_RF. If a WOIS is successfully obtained on the neighbor RF, the handoff trigger trigger RF parameter is set to the neighbor RF.

Handoff to neighbors of a set of partially uninterrupted and partially uninterrupted RFs to desired RFs for the desired content is attempted for a finite time period. The handoff timer is maintained to specify a time duration during which the handoff should be executed. The handoff timer may be set to different values for flows that are started and flows that have been registered. For example, the handoff timer may be set to a larger value for flows that are started compared to registered flows because of the real-time nature of the flows that were started. If the desired content cannot be obtained after the handoff timer expires, the system gives up attempting to acquire the desired content. Device operation for flows that are started and for registered flows after the handoff timer expires is provided elsewhere herein.

7 illustrates a method 700 for performing handoff for use in aspects of a handoff system. For clarity, the method 700 is described herein with reference to the handoff logic 300 shown in FIG. 3. For example, in one aspect, processing logic 302 executes one or more sets of codes for controlling handoff logic 300 to perform the functions described below.

At block 702, neighbor description information is received as part of the NDM. For example, the neighbor description information identifies the neighbor LOIs of the device's current LOI, their associated RF channels, and the multiplexes retained on those RF channels (identified by WID and LID information). In one aspect, neighbor description information is received by the control channel logic 306 over the control channel and passed to the message decoder 304 to decode the information for use by the processing logic 302.

At block 704, RF channels of the current LOI and its neighboring LOIs are monitored to measure signal strengths (RSSI) for these RF channels. In one aspect, processing logic 302 operates to request and receive signal strength parameters related to RFs of the current LOI and neighboring LOIs.

In block 706, uninterrupted handoff tables are created and maintained. In one aspect, processing logic 302 operates to generate and maintain uninterrupted handoff tables based on the received neighbor description information. For example, for each multiplex of the current LOI, the wide area and local seamless handoff tables are formatted as shown in FIG. 4, and the wide area + local seamless handoff tables are formatted as shown in FIG. 5. do.

In block 708, partial uninterrupted handoff tables are created and maintained. In one aspect, processing logic 302 operates to generate and maintain partial uninterrupted handoff tables based on the received neighbor description information. For example, for each multiplex of the current LOI, partial, uninterrupted handoff tables of wide, local, and wide + local are formatted as shown in FIG.

At block 710, a determination is made whether a handoff event has been detected for the desired content. In one aspect, processing logic 302 operates to detect a handoff event. In one aspect, the handoff event is triggered as a result of acquisition failures associated with the desired content. For example, acquisition failures can occur due to device mobility. If no handoff event is detected, the handoff method ends. If a handoff event is detected, the method proceeds to block 712.

At block 712, a determination is made whether any RF channels of the seamless handoff table associated with the desired content are present. In one aspect, processing logic 302 makes this determination based on the set of uninterrupted handoff tables maintained. If there are any RF channels in the seamless handoff table associated with the desired content, the method proceeds to block 714. If there are no RF channels in the seamless handoff table associated with the desired content, the method proceeds to block 732.

At block 714, RF channels of the uninterrupted handoff table associated with the desired content are classified by increasing the ranking. In one aspect, processing logic 302 operates to perform this classification in accordance with the ranking algorithms described above.

At block 716, a determination is made as to whether any RF channels are present in the partial uninterrupted handoff table associated with the desired content. In one aspect, processing logic 302 makes this determination based on the set of partially uninterrupted handoff tables maintained. If there are RF channels available in the partially disconnected handoff table associated with the desired content, the method proceeds to block 718. If there are no RF channels in the partially disconnected handoff table associated with the desired content, the method proceeds to block 722.

In block 718, RF channels of the partially disconnected handoff table associated with the desired content are classified by increasing the ranking. In one aspect, processing logic 302 operates to perform this classification in accordance with the ranking algorithms described above.

At block 720, a handoff RF list is generated that includes the classified partial uninterrupted RF channels after the classified uninterrupted RF channels. In one aspect, processing logic 302 operates to generate a handoff RF list.

At block 722, a handoff RF list is generated that includes the classified uninterrupted RF channels. In one aspect, processing logic 302 operates to generate a handoff RF list.

At block 724, a determination is made whether the detected handoff trigger event is based on one of the first or second handoff trigger conditions among the four handoff trigger conditions described above. In one aspect, processing logic 302 makes this determination. If the handoff event is based on the first or second trigger condition, the method proceeds to block 728. If the handoff event is not based on any of the first or second trigger conditions, the method proceeds to block 726.

At block 726, the handoff trigger_RF is assigned to the current RF channel. In one aspect, processing logic 302 performs this assignment.

At block 728, a handoff timer is started. In one aspect, the handoff timer is maintained by processing logic 302 that operates to start the timer. In one aspect, the handoff timer parameter may be set to different values for handoffs initiated for initiated flows and registered flows.

At block 730, a handoff procedure is executed based on the current handoff RF list. In one aspect, the handoff procedure is provided by the method 800 shown in FIG.

At block 732, a determination is made as to whether any RF channels are present in the partially disconnected handoff table associated with the desired content. In one aspect, processing logic 302 makes this determination based on the maintained set of partially disconnected handoff tables. If there are any RF channels in the partially disconnected handoff table associated with the desired content, the method proceeds to block 734. If there are no RF channels in the partially disconnected handoff table associated with the desired content, the method proceeds to block 738.

In block 734, RF channels of the partially disconnected handoff table associated with the desired content are classified by increasing the ranking. In one aspect, processing logic 302 operates to perform this classification according to the ranking algorithm described above.

At block 736, a handoff RF list is generated that includes the classified partial uninterrupted RF channels. In one aspect, processing logic 302 operates to generate a handoff RF list.

At block 738, a determination is made whether the handoff type is wide + local handoff. In one aspect, processing logic 302 makes this determination. If the handoff is a global + local handoff, the method proceeds to block 742. If the handoff is not a global + local handoff, the method proceeds to block 740.

At block 740, an attempt is made to obtain the desired content on the RF channel of the current LOI. This is because at this point in method 700, it has been determined that there are no interruption or partial interruption RF channels available for the desired content.

At block 742, the handoff type is wide + local, and no uninterrupted or partially uninterrupted RF channels are available for the desired wide + local content. As a result, an attempt is made to perform wide area handoff for the desired wide area content. If wide area handoff fails, an attempt is made to perform a local handoff for the desired local content.

Thus, method 700 operates to perform a handoff for use in aspects of a handoff system. It should be noted that the method 700 represents only one implementation and that other implementations may be possible within the scope of aspects.

8 shows a method 800 for performing a handoff procedure for use in aspects of a handoff system. For example, the method 800 is suitable for use at block 730 of the method 700. For clarity, the method 800 is described herein with reference to the handoff logic 300 shown in FIG. For example, in one aspect, processing logic 302 executes one or more sets of codes to control handoff logic 300 to perform the functions described below.

At block 802, the acquisition RF list is set equivalent to the current handoff RF list. In one aspect, the handoff RF list is determined by processing logic 302 as discussed above with reference to method 700.

In block 804, RF channels of the acquired RF list are monitored to measure signal strength (RSSI) for these RF channels. In one aspect, processing logic 302 is operative to communicate with the reception logic of the device to request RF signal strength characteristics of the RFs of the acquired RF list.

At block 806, a determination is made whether the signal strength of all the RFs in the acquired RF list is below the selected signal strength threshold. In one aspect, processing logic 302 operates to compare the signal strength characteristics of all the RFs in the acquired RF list with a selected threshold to make this determination. If the signal strength of all the RFs in the acquired RF list is equal to or below the threshold, the method proceeds to block 808. If there are any RFs in the acquisition RF list with signal strength greater than the selected threshold, the method proceeds to block 814.

At block 808, a determination is made whether the handoff timer has expired. In one aspect, processing logic 302 maintains a handoff timer as discussed with reference to method 700 (at block 728). Processing logic 302 determines whether the handoff timer has expired, and if so, the method proceeds to block 812. If the handoff timer has not expired, the method proceeds to block 810.

At block 812, a handoff failure is declared. In one aspect, processing logic 302 determines that the attempted handoff failed because all the RFs in the acquired RF list are below the selected threshold or have the same signal strength and the handoff timer has expired.

At block 810, the acquisition RF list is set equal to the current handoff RF list. In one aspect, the handoff RF list is determined by processing logic 302 as discussed above with reference to method 700.

At block 814, the first RF channel with RSSI> threshold is selected from the ordered acquisition RF list. An evaluation is then performed to evaluate the handoff criteria for the selected RF channel. The handoff criterion is evaluated as described above in Equation (1) above. In one aspect, processing logic 302 performs RF selection and handoff criteria evaluation.

At block 816, a determination is made to determine whether the handoff criteria evaluated at block 814 are met for the selected RF channel. In one aspect, processing logic 302 makes this determination. If the handoff criteria are met for the selected RF channel of the acquisition RF list, the method proceeds to block 818. If the handoff criterion is not met, the method proceeds to block 820.

At block 820, the selected RF channel is removed from the acquired RF list. In one aspect, because such RF fails to meet the handoff criteria as determined at 816, or because the OIS cannot be successfully obtained on the selected RF as determined at block 830, or for CC (if necessary). Because acquisition fails for the selected RF as determined at block 838, or because the MLC cannot be successfully decoded as determined at block 842, processing logic 302 removes the selected RF from the acquisition RF list.

At block 822, a determination is made whether the handoff timer has expired. In one aspect, processing logic 302 maintains a handoff timer as discussed with reference to method 700. Processing logic 302 determines whether the handoff timer has expired, and if so, the method proceeds to block 824. If the handoff timer has not expired, the method proceeds to block 826.

At block 824, a handoff failure is declared. In one aspect, because the handoff timer has expired, processing logic 302 determines that the attempted handoff failed.

At block 826, if the acquisition RF list is empty, the acquisition RF list is reset equal to the handoff RF list. In one aspect, processing logic 302 determines whether the acquisition RF list is empty, and if so, resets it to the handoff RF list.

At block 818, switching to the selected RF is performed using the WID / LID associated with the RF. In one aspect, processing logic 302 controls channel switching logic 310 to use the associated WID / LID to switch to the selected RF and descramble the content on the selected RF.

At block 828, an attempt is made to obtain an OIS on the selected RF channel. In one aspect, OIS is obtained by overhead input logic 306.

At block 830, a determination is made whether the OIS was successfully obtained on the selected RF. In one aspect, processing logic 302 makes this determination. If the OIS was not successfully obtained, the method proceeds to block 832. If the OIS was successfully obtained, the method proceeds to block 834.

At block 832, a switch to handoff_trigger_RF is made. In one aspect, processing logic 302 controls channel switch logic 310 to switch back to handoff_trigger_RF because OIS acquisition failed on the selected RF.

At block 834, the handoff trigger_RF is set to the current RF. In one aspect, processing logic 302 performs this operation.

At block 836, an attempt is made to obtain an appropriate control channel, if necessary. In one aspect, overhead input logic 306 performs this operation.

At block 838, a determination is made whether the control channel has been successfully acquired. In one aspect, processing logic 302 makes this determination. If the control channel was not successfully acquired, the method proceeds to block 820. If the control channel was successfully acquired, the method proceeds to block 840.

At block 840, an attempt is made to decode media logic channels (MLCs) from the current RF. In one aspect, the receiving logic of the device attempts to decode the MLCs and reports the results to the processing logic 302.

At block 842, a determination is made whether the at least one MLC associated with the desired content has been successfully decoded. In one aspect, processing logic 302 makes this determination. If at least one MLC associated with the desired content was not successfully decoded, the method proceeds to block 820. If at least one MLC associated with the desired content has been successfully decoded, the method proceeds to block 844.

At block 844, it is determined that the handoff is successful and the handoff procedure ends. In one aspect, processing logic 302 makes this determination because at least one MLC associated with the desired content has been successfully decoded.

Thus, method 800 operates to perform a handoff for use in aspects of a handoff system. It should be noted that the method 800 represents just one implementation and that other implementations may be possible within the scope of the aspects.

9 illustrates a method 900 for providing a handoff event trigger for triggered flows for use in aspects of a handoff system. For clarity, the method 900 is described herein with reference to the handoff logic 300 shown in FIG. 3. For example, in one aspect, processing logic 302 executes one or more sets of codes to control handoff logic 300 to perform the functions described below.

At block 902, one or more real-time flows are successfully launched. In one aspect, applications of the device attempt to obtain one or more real time flows.

At block 904, a determination is made whether the required control channel information is stored locally. In one aspect, processing logic 302 operates to determine whether the required control channel information is stored locally. If control channel data is stored locally, the method proceeds to block 906. If the control channel data is not stored locally, the method proceeds to block 908.

At block 906, a transition is performed (if necessary) to switch to the RF channel with the newly started flows. In one aspect, processing logic 302 controls channel switching logic 310 for switching to an RF channel with newly activated flows. If the device's current RF is an RF with newly activated flows, no RF switching will be required.

At block 908, an attempt is made to obtain an appropriate set of OIS and control channel information from the new RF channel. In one aspect, overhead input logic 306 obtains OIS and control channel information from the new RF channel.

At block 910, a determination is made whether an appropriate set of OIS and control channel information has been successfully obtained. In one aspect, processing logic 302 operates to make this determination. If the OIS and control channel data were not successfully obtained, the method proceeds to block 914. If the OIS and control channel data have been successfully obtained, the method proceeds to block 912.

At block 912, newly launched flows are decoded on the new RF. In one aspect, the receiving logic of the device operates to decode the newly invoked flows.

At block 914, the handoff procedure is executed in an attempt to obtain flows invoked on the neighbor RF channel. In one aspect, processing logic 302 operates to execute a handoff procedure because OIS and CC acquisition fails on the RF channel with the activated flows of the current LOI. In one aspect, the handoff procedure is described above with reference to FIG. 8.

At block 916, a determination is made whether the handoff was successful. In one aspect, processing logic 302 makes this determination. If the handoff was successful, the method proceeds to block 912. If the handoff was not successful, the method proceeds to block 918.

At block 918, the handoff has failed and all activated flows are deactivated. In one aspect, processing logic 302 operates to deactivate all started flows.

At block 920, system acquisition logic is executed. In one aspect, processing logic 302 operates to initiate system acquisition logic to acquire a system because the handoff failed.

Thus, the method 900 operates to perform providing a handoff event trigger on triggered flows for use in aspects of the handoff system. It should be noted that the method 900 represents only one implementation but other implementations may be possible within the scope of the aspects.

10 illustrates a method 1000 for providing a handoff event trigger for triggered flows for use in aspects of a handoff system. For clarity, the method 1000 is described herein with reference to the handoff logic 300 shown in FIG. 3. For example, in one aspect, processing logic 302 executes one or more sets of codes for controlling handoff logic 300 to perform the functions described below.

At block 1002, the device is currently decoding the activated flows on the current RF channel.

At block 1004, a determination is made to determine whether data acquisition for all MLCs associated with the launched flows has failed or whether OIS acquisition has failed on the current RF channel. In one aspect, processing logic 302 makes this determination. If there are no MLCs and OIS failures, the method proceeds to block 1002. If any one of an OIS acquisition failure or a failure of all MLCs associated with activated flows exists, the method proceeds to block 1006.

At block 1006, a handoff procedure for executed flows is executed. For example, the handoff procedure described in FIG. 8 is executed to handoff to a new neighbor RF channel to successfully obtain the OIS and initiated flows.

At block 1008, a determination is made whether the handoff was successful. In one aspect, processing logic 302 makes this determination. If the handoff was successful, the method proceeds to block 1010. If the handoff was not successful, the method proceeds to block 1012.

At block 1010, the started flows are decoded from the new RF channel. In one aspect, the device has handed off to a new RF channel and can obtain flows initiated from that RF channel.

In block 1012, the handoff has failed and all started flows are deactivated. In one aspect, processing logic 302 operates to deactivate the started flow because the handoff to the different RF channel was not successful.

At block 1014, system acquisition logic is executed. In one aspect, processing logic 302 operates to initiate system acquisition logic to acquire a system because the handoff failed.

Thus, the method 1000 operates to perform a handoff event trigger on triggered flows for use in aspects of the handoff system. It should be noted that the method 1000 represents only one implementation and that other implementations may be possible within the scope of the aspects.

11 illustrates a method 1100 for providing a handoff trigger event for registered flows for use in aspects of a handoff system. In one aspect, the method 1100 initiates a handoff at a data acquisition failure event in association with registered flows. It should be noted that a detailed description of the data acquisition procedure (DAP) for registered flows is not provided and that specific embodiments of such data acquisition procedure are not essential to the operation of the methods and apparatus of the various embodiments herein. do. However, an example of a data acquisition procedure for registered flows is a provisional application entitled "Methods and Apparatus for Providing Flow Data Acquisition Priority Scheme in a Multiple Frequency Network" filed April 4, 2007. No. 60 / 910,191, and Provisional Application No. 60 / 945,317, entitled "Methods and Apparatus for Providing Flow Data Acquisition Priority Scheme in a Multiple Frequency Network," filed June 20, 2007). . In one aspect, processing logic 302 executes one or more sets of codes to control handoff logic 300 to perform the functions described below.

At block 1102, a determination is made whether the required control channel information is stored locally. In one aspect, processing logic 302 operates to make this determination. If the required control channel information is stored locally, the method proceeds to block 1104. If the control channel information is not stored locally, the method proceeds to block 1108.

In block 1104, flow groups (FGs) containing registered flows for which data is to be obtained are stored in DAP_FG [..] in their ranking order. The highest ranking FG (DAP_FG [0]) is selected to obtain registered flow data. In one aspect, processing logic 302 operates to perform these operations. Processing logic 302 is operative to attempt flow data acquisition for registered flows of the selected FG along with other registered flows held on the same RF channel.

At block 1106, a switch to RF with the selected flow group (if required) is performed. In one aspect, processing logic 302 controls channel switching logic 310 to switch to the RF channel having the selected FG. RF switching will not be required if the device's current RF is an RF with a selected FG.

At block 1108, an attempt is made to obtain an appropriate set of OIS and control channel information on the new RF channel. In one aspect, overhead input logic 306 obtains OIS and control channel information from the new RF channel.

At block 1110, a determination is made whether the acquisition of the OIS and control channel information was successful. In one aspect, if the acquisition of the OIS and control channel information was successful, the method proceeds to block 1112. If the acquisition of the OIS and control channel information was not successful, the method proceeds to block 1114.

In block 1112, execution of the DAP procedure continues to obtain data associated with registered flows. In one aspect, processing logic 302 operates to continue executing the DAP procedure.

At block 1114, a handoff procedure is executed for registered flows of the selected FG. For example, the handoff procedure described in FIG. 8 is executed to handoff to a new neighbor RF channel in an attempt to obtain data for registered flows of the selected FG.

At block 1116, a determination is made whether the handoff was successful. If the handoff was successful, the method proceeds to block 1112. If the handoff was not successful, the method proceeds to block 1118.

At block 1118, all flow groups currently held in the RF channel are removed from the DAP flow group list. In one aspect, processing logic 302 operates to remove FGs from the DAP flow group list.

At block 1120, a determination is made whether any further flow groups remain in the DAP flow group list. In one aspect, processing logic 302 operates to make this determination. In one aspect, if more flow groups remain in the DAP flow group list, the method proceeds to block 1104. If no flow groups remain in the DAP flow group list, the method proceeds to block 1122.

At block 1122, the DAP flow group list is reset to all calculated flow groups. In one aspect, processing logic 302 operates to reset the DAP flow group list.

In block 1124, monitoring of OIS information is scheduled so that acquisition of flow data for OIS, CC and FGs may be attempted again after a selected time interval.

Thus, the method 1100 operates to provide a handoff event trigger for registered flows for use in aspects of the handoff system. It should be noted that the method 1100 represents only one implementation but other implementations may be possible within the scope of the aspects.

12 illustrates a method 1200 for providing a handoff trigger event for registered flows for use in aspects of a handoff system. In one aspect, the method 1200 initiates a handoff in a data acquisition failure event associated with registered flows. In one aspect, processing logic 302 executes one or more sets of codes for controlling handoff logic 300 to perform the functions described below.

At block 1202, the device is currently decoding the registered flows associated with the selected flow group on the current RF. The device also decodes registered flows associated with other FGs currently held on the RF.

At block 1204, a determination is made whether data acquisition for all MLCs associated with registered flows of the selected FG failed or whether OIS acquisition failed on the current RF. In one aspect, processing logic 302 makes this determination. If there are no MLCs and OIS failures, the method proceeds to block 1202. If any one of the failure of OIS acquisition or the failure of all MLCs associated with registered flows of the selected FG is present, the method proceeds to block 1206.

At block 1206, a handoff procedure is executed for registered flows of the selected FG. For example, the handoff procedure described in FIG. 8 is executed to handoff to a new neighbor RF channel to successfully obtain the registered flows and OIS of the selected FG.

At block 1208, a determination is made whether the handoff was successful. In one aspect, processing logic 302 makes this determination. If the handoff was successful, the method proceeds to block 1210. If the handoff was not successful, the method proceeds to block 1212.

At block 1212, all flow groups currently held in the RF channel are removed from the DAP flow group list. In one aspect, processing logic 302 operates to remove FGs from the DAP flow group list.

At block 1214, a determination is made whether any further flow groups remain in the DAP flow group list. In one aspect, processing logic 302 operates to make this determination. If more flow groups remain, the method proceeds to block 1216 to initiate DAP procedure execution. If no flow groups remain in the DAP flow group list, the method proceeds to block 1218.

At block 1216, the DAP procedure is executed to obtain data for additional flow groups remaining in the DAP flow group list.

At block 1218, the DAP flow group list is reset to list all calculated flow groups. In one aspect, processing logic 302 operates to reset the DAP flow group list.

In block 1220, monitoring of OIS information is scheduled such that acquisition for flow data for OIS, CC and FGs may be retried after the selected time interval.

Thus, the method 1200 operates to provide a handoff event trigger for registered flows for use in aspects of the handoff system. It should be noted that the method 1200 represents only one implementation and that other implementations may be possible within the scope of the aspects.

15 shows handoff logic 1500 for use in aspects of a handoff system. For example, the handoff logic 1500 may be suitable for use as the handoff logic 300 shown in FIG. 3. In one aspect, handoff logic 300 is implemented by at least one integrated circuit that includes one or more modules configured to provide aspects of a handoff system as described herein. For example, in one aspect, each module includes hardware and / or hardware execution software.

The handoff logic 1500 includes a first module that includes a means for generating unceasing handoff tables and partial unceasing handoff tables for multiplexes currently held in the LOI, including unauthorized The clause and partial uninterrupted handoff tables include neighboring RF channels that hold one or more multiplexes of the current LOI, and the first module includes processing logic 302 in one aspect. The handoff logic 1500 also includes a second module that includes means 1504 for detecting a handoff event initiated by acquisition failures on a current RF, the second module comprising in one aspect processing logic ( 302). The handoff logic 1500 also includes a third module including means 1506 for selecting a selected RF channel from the uninterrupted and partially uninterrupted handoff tables, which third module processes in one aspect. Includes logic 302. The handoff logic 1500 also includes a fourth module that includes means 1508 for performing a handoff to the selected RF channel, which in one aspect comprises the channel switch logic 310. .

Various illustrative logics, logic blocks, modules, and circuits presented in connection with aspects disclosed herein may be a general purpose processor, digital signal processor (DSP), application specific integrated circuit (ASIC), field programmable gate array (FPGA). Or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions presented herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, eg, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

The steps of a method or algorithm presented in connection with the aspects disclosed herein may be embedded directly in hardware, a software module executed by a processor, or a combination of the two. The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from and write information to the storage medium. Alternatively, the storage medium may be integrated into the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.

The description of the disclosed aspects is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these aspects may be apparent to those skilled in the art, and the basic principles defined herein may be used, such as instant messaging services or any general purpose wireless data communication applications, without departing from the spirit or scope of the invention. It can be applied to other aspects. Thus, the present invention is not intended to be limited to the aspects illustrated herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein. The word "exemplary" is used herein generically to mean "acting as an example, illustration, or illustration." Any aspect described herein as "exemplary" need not be considered as preferred or preferred over other aspects.

Thus, while aspects of the handoff system have been illustrated and described herein, it will be appreciated that various changes may be made to the aspects without departing from their spirit or essential characteristics. Accordingly, the disclosures and descriptions herein are intended to be illustrative, and do not limit the scope of the invention, which is detailed in the following claims.

Claims (59)

A method for RF channel handoff in a multi-frequency network, comprising: Creating seamless handoff tables and partially seamless handoff tables for multiplexes currently carried in a local operations infrastructure, the seamless Handoff tables and the partially disconnected handoff tables include neighboring RF channels holding one or more of the multiplexes of the current LOI; Detecting a handoff event initiated by acquisition failures on a current RF; Selecting a selected RF channel from the seamless handoff tables and the partial seamless handoff tables; And Performing a handoff to the selected RF channel. The method of claim 1, The generating includes generating a wide range handoff table for each wide multiplex of the current LOI, the wide range handoff table having the same set of wide area multiplexes as the current LOI. And neighboring RF channels associated with local operation infrastructures (LOIs) and retaining the respective wide area multiplexes. The method of claim 1, The generating step includes generating a local disconnected handoff table for each local multiplex of the current LOI, the local disconnected handoff table having the same set of local multiplexes as the current LOI. And neighboring RF channels associated with local operation infrastructures (LOIs) and retaining each of the local multiplexes. The method of claim 1, The generating step includes generating a global + local uninterruptible handoff table for each combination of global + local multiplexes of the current LOI, wherein the global + local uninterruptible handoff table is associated with the current LOI. RF channel hand in a multi-frequency network, associated with local operation infrastructures (LOIs) having the same set of wide area and local multiplexes, and including a neighboring RF channel having each combination of the wide area plus local multiplexes. Way for off. The method of claim 1, The generating step includes generating a widespread, uninterrupted handoff table for each wide area multiplex of the current LOI, wherein the widespread, uninterrupted handoff table is the same set as the current LOI. And neighboring RF channels associated with local operation infrastructures (LOIs) that do not possess the wide area multiplex of the plurality and which retain the respective wide area multiplex. The method of claim 1, The generating step includes generating a local partially disconnected handoff table for each local multiplex of the current LOI, wherein the local partially disconnected handoff table is the same set as the current LOI. And neighboring RF channels associated with local operation infrastructures (LOIs) that do not possess local multiplexes of said local multiplex, said neighboring RF channels retaining each local multiplex. The method of claim 1, The generating step includes generating a global + local partial seamless handoff table for each combination of global + local multiplexes of the current LOI, wherein the global + local partial seamless handoff table comprises: A table is associated with local operation infrastructures (LOIs) that do not have the same set of wide area and local multiplexes as the current LOI, and includes neighboring RF channels that hold each combination of the wide area + local multiplexes. -Method for RF channel handoff in a frequency network. The method of claim 1, Determining that the two or more neighboring RF channels have the same wide area multiplex if two or more neighboring RF channels are associated with the same wide area descrambling identifier (WID); Determining that the two or more neighboring RF channels have the same local multiplex if two or more neighboring RF channels are associated with the same local area descrambling identifier (LID); And If two or more neighboring RF channels are associated with the same combination of wide area descrambling identifier (WID) and local area descrambling identifier (LID), determine that the two or more neighboring RF channels have the same combination of wide + local multiplexes. Further comprising the step of: performing an RF channel handoff in a multi-frequency network. The method of claim 1, The detecting step may include acquisition failure for data associated with one or more activated flows, acquisition failure for data associated with one or more registered flows, overhead informaton (OIS) overhead informaton detecting the handoff event based on at least one of an acquisition failure for symbols) and an acquisition failure for a control channel (CC). Way. The method of claim 1, The detecting step includes a wide area handoff type where only wide area flows are associated with acquisition failures, a local handoff type when only local flows are associated with acquisition failures, and acquisition failures with both wide area flows and local flows. Detecting the handoff event comprising one of a wide area + local handoff type when associated with the RF channel handoff in a multi-frequency network. 11. The method of claim 10, The selecting step may include: when the handoff event includes the wide area handoff type, from the one of a wide range uninterrupted handoff table and a wide area uninterrupted handoff table associated with a wide area multiplex on the current RF. Selecting the selected RF, the method for RF channel handoff in a multi-frequency network. 11. The method of claim 10, The selecting step includes the local disconnection handoff table associated with a local multiplex on the current RF and a local partial disconnection handoff table when the handoff event includes the local handoff type. Selecting the selected RF, the method for RF channel handoff in a multi-frequency network. 11. The method of claim 10, The selecting step includes a wide area + local seamless handoff table and a wide area + local portion associated with the combination of wide area + local multiplex on the current RF if the handoff event includes the wide area + local handoff type. Selecting the selected RF from one of an uninterrupted handoff table. The method of claim 13, Detecting the handoff event comprising the wide + local handoff type; Determining that the global + local uninterrupted handoff table associated with the global + local multiplexes on the current RF and the global + local partially uninterrupted handoff table are empty; Selecting the selected RF from one of a wide range uninterruptible table associated with the wide area multiplex on the current RF and a wide range partially uninterrupted handoff table; Attempting to handoff to the selected RF; And Selecting the selected RF from one of a local disconnected handoff table associated with the local multiplex on the current RF and a local partially disconnected handoff table if the attempted handoff fails; Method for RF Channel Handoff in a Multi-Frequency Network. 11. The method of claim 10, Generating a handoff RF list by combining RF channels from selected and partially broken handoff tables associated with at least one selected multiplex on the current RF based on the handoff type; And Until a successful handoff is performed, Selecting the selected RF channel from the handoff RF list; Performing a handoff to the selected RF channel; Determining that handoff to the selected RF channel has failed; And Repeating the operation of removing the selected RF from the handoff RF list. The method of claim 15, Wherein the repeating step includes repeating the selecting, determining, and canceling operations for a selected handoff time duration. The method of claim 15, And said selecting comprises selecting said selected RF from said selected uninterrupted handoff table prior to said selected partially uninterrupted handoff table. The method of claim 15, The selecting step, Ranking the RF channels in the selected uninterrupted and partially uninterrupted handoff tables based on the total number of multiplexes in the LOIs associated with each of the RF channels and the number of common multiplexes. ; And Selecting the selected RF channel from the selected uninterrupted and partially uninterrupted handoff tables based on the ranking of the RF channels. The method of claim 15, The selecting step includes selecting the selected RF channel such that the selected RF channel meets a signal strength threshold and has a signal strength that is greater than the sum of the signal strengths for the hysteresis value + handoff_trigger_RF. And a method for RF channel handoff in a multi-frequency network. The method of claim 15, And determining that the handoff is successful if data associated with at least one desired media logical channel is successfully obtained. The method of claim 15, Determining that the handoff failed based on at least one of an OIS acquisition failure, a control channel acquisition failure, and a data acquisition failure associated with at least one desired media logic channel. Method for handoff. The method of claim 1, Performing the handoff to obtain one or more invoked flows; Determining that the handoff has failed; Deactivating the one or more activated flows; And Performing system acquisition further comprising performing a system acquisition. The method of claim 1, Performing the handoff to obtain data for flows in at least one flow group from a list of flow groups, each flow group associated with one or more registered flows; Determining that the handoff has failed; Removing all flow groups held on the current RF from the list of flow groups; Performing another handoff to obtain data for other flow groups if there are flow groups remaining in the list of flow groups; Resetting the list of flow groups to all flow groups if there are no remaining flow groups in the list of flow groups; And Scheduling the monitoring of the OIS to enable data acquisition for the selected registered flows after the selected time interval. An apparatus for RF channel handoff in a multi-frequency network, the apparatus comprising: Processing logic configured to generate disconnection handoff tables and partial disconnection handoff tables for multiplexes held in the current LOI, wherein the disconnection handoff tables and the partially disconnection handoff tables Neighboring RF channels holding one or more of the multiplexes of a LOI, wherein the processing logic is further to detect a handoff event initiated by acquisition failures on a current RF; Select a selected RF channel from partial uninterrupted handoff tables; And And channel switch logic configured to perform a handoff to the selected RF channel. The method of claim 24, The processing logic is configured to generate a wide range handoff table for each wide multiplex of the current LOI, the wide range handoff table having a local operation infrastructure having the same set of wide area multiplexes as the current LOI. And neighboring RF channels associated with structures (LOIs) and retaining the respective wide area multiplex. The method of claim 24, The processing logic is configured to generate a widespread, uninterrupted handoff table for each wide-area multiplex of the current LOI, wherein the widespread, uninterrupted handoff table is in the same set of wide-area multipliers as the current LOI. And neighboring RF channels associated with local operation infrastructures (LOIs) that do not have plexes and that retain the respective wide area multiplex. The method of claim 24, The processing logic includes acquisition failure for data associated with one or more activated flows, acquisition failure for data associated with one or more registered flows, acquisition failure for overhead information symbols (OIS), and control channel (CC). And detect the handoff event based on at least one of the failed acquisitions. The method of claim 24, The processing logic may include a wide area handoff type when only wide flows are associated with acquisition failures, a local handoff type when only local flows are associated with acquisition failures, and acquisition failures with both wide area flows and local flows. And detect the handoff event comprising one of a wide area + local handoff type when associated with a multi-frequency network. 29. The method of claim 28, The processing logic is further configured to select the one from a wide range handoff table associated with a wide area multiplex on the current RF and a wide range participant handoff table when the handoff event includes the wide handoff type. Configured to select RF and for RF channel handoff in a multi-frequency network. 29. The method of claim 28, The processing logic is, Generate a handoff RF list by combining RF channels from selected and partially broken handoff tables associated with at least one selected multiplex on the current RF based on the handoff type; And Until a successful handoff is performed, Selecting the selected RF channel from the handoff RF list; Performing a handoff to the selected RF channel; Determining that a handoff to the selected RF has failed; And And repeat the operation of removing the selected RF from the handoff RF list. 31. The method of claim 30, And the processing logic is configured to select the selected RF channel from the selected broken handoff table prior to the selected partially broken handoff table. 31. The method of claim 30, The processing logic is configured to select the selected RF channel such that the selected RF channel meets a signal strength threshold and has a signal strength that is greater than the sum of the signal strengths for hysteresis value + handoff_trigger_RF. Device for RF channel handoff in a network. An apparatus for RF channel handoff in a multi-frequency network, the apparatus comprising: Means for creating breakdown handoff tables and partial breakdown handoff tables for multiplexes held at a current LOI, wherein the breakdown handoff tables and the partially breakdown handoff tables are the current LOI. Neighboring RF channels that retain one or more of the multiplexes of the multiplexed circuits; Means for detecting a handoff event initiated by acquisition failures on a current RF; Means for selecting a selected RF channel from the seamless handoff tables and the partial seamless handoff tables; And Means for performing a handoff to the selected RF channel. The method of claim 33, wherein The means for generating comprises means for generating a wide range handoff table for each wide area multiplex of the current LOI, wherein the wide range handoff table is the same set of wide area multiplex as the current LOI. And neighboring RF channels associated with local operation infrastructures (LOIs) having a plurality of nodes and having respective wide area multiplexes. The method of claim 33, wherein The means for generating comprises means for generating a widespread, uninterrupted handoff table for each wide area multiplex of the current LOI, wherein the widespread, uninterrupted handoff table is associated with the current LOI. Apparatus for RF channel handoff in a multi-frequency network, comprising neighboring RF channels associated with local operation infrastructures (LOIs) that do not have the same set of wide area multiplexes and retaining each respective wide area multiplex . The method of claim 33, wherein The means for detecting may include acquisition failure for data associated with one or more activated flows, acquisition failure for data associated with one or more registered flows, acquisition failure for overhead information symbols (OIS), and a control channel. Means for detecting the handoff event based on at least one of an acquisition failure for (CC). The method of claim 33, wherein The means for detecting includes a wide area handoff type where only wide area flows are associated with acquisition failures, a local handoff type when only local flows are associated with acquisition failures, and both wide area flows and local flows. Means for detecting the handoff event comprising one of a wide area + local handoff type when associated with failures. 39. The method of claim 37, The means for selecting is from one of a wide range uninterruptible handoff table and a wide range uninterrupted handoff table associated with the wide area multiplex on the current RF, if the handoff event includes the wide range handoff type. Means for selecting the selected RF; apparatus for RF channel handoff in a multi-frequency network. 39. The method of claim 37, Means for generating a handoff RF list by combining RF channels from selected and partially broken handoff tables associated with at least one selected multiplex on the current RF based on the handoff type; And Until a successful handoff is performed, Selecting the selected RF channel from the handoff RF list; Performing a handoff to the selected RF channel; Determining that a handoff to the selected RF has failed; And And means for repeating the operation of removing the selected RF from the handoff RF list. 40. The method of claim 39, And the means for selecting comprises means for selecting the selected RF channel from the selected uninterrupted handoff table prior to the selected partial uninterrupted handoff table. Device. 40. The method of claim 39, The means for selecting includes means for selecting the selected RF channel such that the selected RF channel meets a signal strength threshold and has a signal strength greater than the sum of the signal strengths for hysteresis value + handoff_trigger_RF. And apparatus for RF channel handoff in a multi-frequency network. A machine-readable medium for RF channel handoff in a multi-frequency network, A first set of codes for causing a computer to create breakdown handoff tables and partial breakdown handoff tables for multiplexes currently held in the LOI, the breakdown handoff tables and partially unauthorized Clause handoff tables include neighboring RF channels holding one or more of the multiplexes of the current LOI; A second set of codes for causing the computer to detect a handoff event initiated by acquisition failures on a current RF; A third set of codes for causing the computer to select a selected RF channel from the seamless handoff tables and the partial seamless handoff tables; And And a fourth set of codes for causing the computer to perform a handoff to the selected RF channel. 10. The machine-readable medium for RF channel handoff in a multi-frequency network. 43. The method of claim 42, The first set of codes is configured to cause the computer to generate a wide range handoff table for each wide area multiplex in the current LOI, wherein the wide range handoff table is the same set as the current LOI. A machine-readable medium for RF channel handoff in a multi-frequency network, comprising neighboring RF channels associated with local operation infrastructures (LOIs) having wide area multiplexes and having respective wide area multiplexes. . 43. The method of claim 42, The first set of codes is configured to cause the computer to generate a widespread, uninterrupted handoff table for each wide-area multiplex at the current LOI, wherein the widespread, uninterrupted handoff table is RF channel hand in a multi-frequency network, comprising neighboring RF channels associated with local operation infrastructures (LOIs) that do not have the same set of wide area multiplexes as the current LOI, and holding the respective wide area multiplexes. Machine-readable medium for off. 43. The method of claim 42, The second set of codes causes the computer to fail to acquire data associated with one or more activated flows, fail to acquire data associated with one or more registered flows, or to overhead information symbols (OIS). And detect the handoff event based on at least one of an acquisition failure, and an acquisition failure for a control channel (CC). 17. The machine-readable medium for RF channel handoff in a multi-frequency network. 43. The method of claim 42, The second set of codes causes the computer to cause a global handoff type when only wide area flows are associated with acquisition failures, a local handoff type when only local flows are associated with acquisition failures, and wide area flows. Machine-reading for RF channel handoff in a multi-frequency network, configured to detect the handoff event comprising one of a global + local handoff type when both and local flows are associated with acquisition failures. Media available. The method of claim 46, The third set of codes causes the computer to cause a wide range uninterruptible handoff table and a wide range partial disconnection associated with a wide area multiplex on the current RF if the handoff event includes the wide range handoff type. Machine-readable medium for RF channel handoff in a multi-frequency network, configured to select the selected RF from one of a handoff table. The method of claim 46, Generate a handoff RF list by causing the computer to combine RF channels from selected and partially broken handoff tables associated with at least one selected multiplex on the current RF based on the handoff type; A fifth set of codes configured to make a code; And Until the successful handoff is performed, Selecting the selected RF channel from the handoff RF list; Performing a handoff to the selected RF channel; Determining that a handoff to the selected RF has failed; And And a sixth set of codes configured to repeat the operation of removing the selected RF from the handoff RF list. 10. The machine-readable medium for RF channel handoff in a multi-frequency network. 49. The method of claim 48 wherein The third set of codes is configured to cause the computer to select the selected RF channel from the selected uninterrupted handoff table prior to the selected partially uninterrupted handoff table. Machine-readable medium for handoff. 49. The method of claim 48 wherein The third set of codes causes the computer to cause the selected RF channel to meet a signal strength threshold and to have a signal strength greater than the sum of the signal strengths for the hysteresis value + handoff trigger_RF. And a machine-readable medium for RF channel handoff in a multi-frequency network. At least one integrated circuit configured for RF channel handoff in a multi-frequency network, A first module configured to generate disconnection handoff tables and partial disconnection handoff tables for multiplexes held in a current LOI, wherein the disconnection handoff tables and the partial disconnection handoff tables are the current; Includes neighboring RF channels that retain one or more of the multiplexes of the LOI; A second module configured to detect a handoff event initiated by acquisition failures on a current RF; A third module configured to select a selected RF channel from the disconnected handoff tables and the partially disconnected handoff tables; And At least one integrated circuit configured for RF channel handoff in a multi-frequency network, comprising a fourth module configured to perform a handoff to the selected RF channel. 52. The method of claim 51, The first module is configured to generate a wide range handoff table for each wide multiplex of the current LOI, the wide range handoff table having a local operation having the same set of wide area multiplexes as the current LOI. At least one integrated circuit configured for RF channel handoff in a multi-frequency network, the neighboring RF channels associated with infrastructures (LOIs) and retaining the respective wide area multiplex. 52. The method of claim 51, The first module is configured to generate a widespread, uninterrupted handoff table for each wide-area multiplex of the current LOI, wherein the widespread, uninterrupted handoff table is in the same set of wideband as the current LOI. At least one integration configured for RF channel handoff in a multi-frequency network, associated with local operation infrastructures (LOIs) that do not have multiplexes, and including neighboring RF channels that retain each respective widex multiplex Circuit. 52. The method of claim 51, The second module includes a failure to acquire data associated with one or more activated flows, a failure to acquire data associated with one or more registered flows, a failure to acquire overhead information symbols (OIS), and a control channel ( At least one integrated circuit configured for RF channel handoff in a multi-frequency network, configured to detect the handoff event based on at least one of an acquisition failure for CC). 52. The method of claim 51, The second module has a wide area handoff type when only wide flows are associated with acquisition failures, a local handoff type when only local flows are associated with acquisition failures, and both wide flows and local flows have failed acquisition. At least one integrated circuit configured for RF channel handoff in a multi-frequency network, the detector being configured to detect the handoff event comprising one of a wide area + local handoff type when associated with the device. 56. The method of claim 55, The third module is further configured to: from the one of a wide range hand-held handoff table and a wide-area partially broken handoff table associated with a wide area multiplex on the current RF, if the handoff event includes the wide handoff type. At least one integrated circuit configured for RF channel handoff in a multi-frequency network, configured to select the selected RF. 56. The method of claim 55, A fifth module configured to generate a handoff RF list by combining RF channels from selected and partially broken handoff tables associated with at least one selected multiplex on the current RF based on the handoff type ; And Until a successful handoff is performed, Selecting the selected RF channel from the handoff RF list; Performing a handoff to the selected RF channel; Determining that a handoff to the selected RF has failed; And At least one integrated circuit configured for RF channel handoff in a multi-frequency network, further comprising a sixth module configured to repeat removing the selected RF from the handoff RF list. The method of claim 57, The third module is configured to select the selected RF channel from the selected uninterrupted handoff table prior to the selected partial uninterrupted handoff table; at least one configured for RF channel handoff in a multi-frequency network Integrated circuits. The method of claim 57, The third module is configured to select the selected RF channel such that the selected RF channel meets a signal strength threshold and has a signal strength greater than the sum of the signal strengths for the hysteresis value + handoff_trigger_RF. At least one integrated circuit configured for RF channel handoff in a frequency network.

Images