Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W36/00—Hand-off or reselection arrangements
  • H04W36/16—Performing reselection for specific purposes
  • H04W36/18—Performing reselection for specific purposes for allowing seamless reselection, e.g. soft reselection
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W48/00—Access restriction; Network selection; Access point selection
  • H04W48/20—Selecting an access point
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W92/00—Interfaces specially adapted for wireless communication networks
  • H04W92/04—Interfaces between hierarchically different network devices
  • H04W92/10—Interfaces between hierarchically different network devices between terminal device and access point, i.e. wireless air interface
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W99/00—Subject matter not provided for in other groups of this subclass
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W36/00—Hand-off or reselection arrangements
  • H04W36/24—Reselection being triggered by specific parameters
  • H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W36/00—Hand-off or reselection arrangements
  • H04W36/24—Reselection being triggered by specific parameters
  • H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data
  • H04W36/304—Reselection being triggered by specific parameters by measured or perceived connection quality data due to measured or perceived resources with higher communication quality
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W36/00—Hand-off or reselection arrangements
  • H04W36/34—Reselection control
  • H04W36/38—Reselection control by fixed network equipment
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W72/00—Local resource management

Definitions

• This disclosure relates generally to communication systems. More specifically, embodiments disclosed herein relate to adaptive server selection in wireless communications.
• Wireless communication systems are widely deployed to provide various types of communications (e.g., voice, data, etc.) to multiple users. Such systems may be based on code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), or other multiple access techniques.
• CDMA code division multiple access
• TDMA time division multiple access
• FDMA frequency division multiple access
• a wireless communication system may be designed to implement one or more standards, such as IS-95, cdma2000, IS-856, W-CDMA, TD-SCDMA, and other standards.
• FIG. 1 illustrates an embodiment of a wireless communication system
• FIGs. 2A-2C illustrate embodiments of soft handoff timelines in "IxEV-DO
• FIG. 3 illustrates an embodiment of operating timelines of DSC and DRC channels;
• FIG. 4 illustrates an embodiment of DRC cover change;
• FIG. 5 illustrates an embodiment of a sequence of events taking place in a first soft handoff scenario
• FIG. 6 illustrates an embodiment of a sequence of events taking place in a second soft handoff scenario
• FIG. 7 illustrates an embodiment of a sequence of events taking place in a third soft handoff scenario
• FIG. 8 illustrates an embodiment of a sequence of events taking place in a fourth soft handoff scenario
• FIG. 9 illustrates a flow chart of a process, which may be used to implement some disclosed embodiments
• FIG. 10 illustrates a flow chart of a process, which may be used to implement some disclosed embodiments
• FIG. 10 illustrates a flow chart of a process, which may be used to implement some disclosed embodiments
• FIG. 11 illustrates a flow chart of a process, which may be used to implement some disclosed embodiments;
• FIG. 12 illustrates a flow chart of a process, which may be used to implement some disclosed embodiments;
• FIG. 13 illustrates a block diagram of an apparatus, in which some disclosed embodiments may be implemented;
• FIG. 14 illustrates a block diagram of an apparatus, in which some disclosed embodiments may be implemented;
• FIG. 15 illustrates a block diagram of an apparatus, in which some disclosed embodiments may be implemented;
• FIG. 16 illustrates an embodiment of the hysteresis associated with setting the
• FIG. 17 illustrates a flow chart of a process in connection with DRC erasure mapping
• FIGs. 18A-I illustrate flow charts of several processes, which may be used to implement features illustrated in FIG. 17
• FIG. 19 illustrates a flow chart of a process, which may be used to implement features illustrated in FIG. 17 and FIGs. 18A-I
• FIG. 20 illustrates a block diagram of an apparatus, in which some disclosed embodiments may be implemented. DETAILED DESCRIPTION
• Embodiments disclosed herein relate to methods and systems for providing adaptive server selection in wireless communications.
• An access point (AP) disclosed herein may include and/or implement functions of a base-station transceiver system (BTS), an access network transceiver (ANT), a modem pool transceiver (MPT), or a Node B (e.g., in a W-CDMA type system), etc.
• a cell may refer to a coverage area serviced by an AP.
• a cell may further include one or more sectors.
• an access network controller (ANC) may refer to the portion of a communication system configured to interface with a core network (e.g., a packet data network) and route data packets between access terminals (ATs) and the core network, perform various radio access and link maintenance functions (such as soft handoff), control radio transmitters and receivers, and so on.
• An ANC may include and/or implement the functions of abase station controller (BSC), such as found in a 2 nd , 3 rd , or 4 th generation wireless network.
• BSC base station controller
• An ANC and one or more APs may constitute part of an access network (AN).
• An AT disclosed herein may refer to various types of devices, including (but not limited to) a wireless phone, a cellular phone, a laptop computer, a multimedia wireless device, a wireless communication personal computer (PC) card, a personal digital assistant (PDA), an external or internal modem, etc.
• An AT may be any data device that communicates through a wireless channel and/or through a wired channel (e.g., by way of fiber optic or coaxial cables).
• An AT may have various names, such as access unit, access node, subscriber unit, mobile station, mobile device, mobile unit, mobile phone, mobile, remote station, remote terminal, remote unit, user device, user equipment, handheld device, etc. Different ATs may be incorporated into a system. ATs may be mobile or stationary, and may be dispersed throughout a communication system. An AT may communicate with one or more APs on a forward link (FL) and/or a reverse link (RL) at a given moment.
• FL forward link
• RL reverse link
• FIG. 1 illustrates a wireless communication system 100 configured to support a number of users, in which various disclosed embodiments and aspects may be implemented, as further described below.
• system 100 provides communication for a number of cells 102, including cells 102a-102g, with each cell being serviced by a corresponding AP 104 (such as APs 104a-104g). Each cell may be further divided into one or more sectors.
• Various ATs 106 including ATs 106a- 106k, are dispersed throughout the system. Each AT 106 may communicate with one or more APs 104 on a forward link and/or a reverse link at a given moment, depending upon whether the AT is active and whether it is in soft handoff, for example.
• a solid line with an arrow may indicate information (e.g., data) transmission from an AP to an AT.
• Broken lines each with an arrow may indicate that the AT is receiving pilot and other signaling/reference signals from the respective APs (e.g., those in the AT's active set), as further described below.
• the reverse link communication is not explicitly shown in FIG. 1.
• HRPD high rate packet data
• FIGs. 2A-2C illustrate embodiments of soft handoff timelines in "IxEV-DO
• the trigger for the AT to switch its forward link serving sector may result from the forward link channel condition, e.g., the filtered signal-to- interference-and-noise (SINR) ratio (e.g., based on the pilot and/or other forward link signal measurements) from the target sector being consistently higher than that from the source sector according to a predetermined scheme, such as illustrated in FIG. 2A and further described below.
• SINR filtered signal-to- interference-and-noise
• an AT may use data rate control (DRC) channel to indicate to an AN the selected serving sector and the desired data rate associated with transmission on forward link.
• DRC data rate control
• the DRC channel also provides for a feedback mechanism relating the channel quality information to the AN.
• the data portion and sector portion of DRC may be referred to herein as “DRC rate” and “DRC cover,” respectively.
• the DRC rate and DRC cover constitutes a "DRC value.”
• the DRC cover may change at any DRC change boundary, e.g., in slot T such that
• FrameOffset may be measured in unit of slots
• DRCLength may be a predetermined number of slots in duration (e.g., 8 slots).
• DRC cover and DRC rate may take effect half slot after the end of transmission and stays in effect for a number of slots equal to DRCLength.
• a minimum of two DRC lengths of null covers may be needed between different DRC covers (e.g., associated with switching from sector A to sector B), as the following examples illustrate.
• the AT's next DRC cover may not be a different sector cover. It may only be the same sector cover or a null cover.
• the AT may not use a sector cover corresponding to sector B until the AT has determined that packets received from sector B will not overlap in time with packets received from sector A.
• the packet is of a particular data rate (e.g., rate index 1 with 1024 bits over 16 slots), it may have a preamble of 1024 chips in length which is the time offset between the DRC change and the corresponding data packet transmission.
• the AT may not be sure that there is no packet for it when it determines the DRC cover for slot (n+DRCLength+1). Therefore, null cover needs to be transmitted from slot (n+DRCLength+1) to (n+2xDRCLength). As such, at least two null covers may be needed between the DRC cover changes.
• the ANC may need to forward data to sector B before it starts serving the AT.
• sector A may transmit a message (e.g., "ForwardStopped") and sector B may also transmit a message (e.g., "ForwardDesired") to the ANC to indicate soft handoff, such as illustrated in FIG. 2B.
• the AT may not be served for at least one AP-ANC round trip time plus two DRCLengths during soft handoff.
• the non-service time may be at least two DRCLengths.
• the non-service time may be termed "service outage" (or “dark time”) herein, such as illustrated in FIG. 2B.
• the service outage may pose a loss for delay-sensitive applications, such as "voice over Internet Protocol (VoIP)" data.
• VoIP Voice over Internet Protocol
• a data source control (DSC) channel may be introduced (such as in a "IxEV-DO Revision A" type system), representing the serving cell or data source on forward link.
• An AT may use the DSC channel to indicate to an AN the selected serving cell on forward link, and use the DRC channel to indicate to the AN the selected serving sector on forward link. Examples of use of the DSC channel to facilitate the server selection in relation to AT and AN are described below.
• FIGs. 2B and 2C illustrate a comparison of the soft handoff timelines in "IxEV-
• DSC may be configured to have predetermined boundaries, at which DSC is allowed to change.
• DSC may change in slot T such that
• DSCLength may be a predetermined number of slots in duration (e.g., 16 slots).
• DRC may change in slot T such that
• DSC may take effect one slot after the end of transmission and stay in effect for DSCLength slots; whereas DRC may take effect half slot after the end of transmission and stays in effect for a number of slots equal to DRCLength.
• DRC may conform with DSC.
• the DRC cover is a sector cover
• the data source indicated by the DSC is included in the AT's active set and the DRCLock bit associated with the data source is set to "1”
• the sector indicated by the DRC cover may belong to the data source indicated by the DSC that is in effect during the next DRCLength slots following transmission of the DRC.
• DSC may be used as an early indication of handoff, thereby allowing the service outage associated with queue transfer (or "Q-transfer") between AP and ANC to be minimized, or substantially eliminated.
• a plurality of APs in the AT's active set may attempt to detect DSC ahead of DSC length boundary (e.g., on a per-slot basis).
• the ANC may start multicasting data associated with expedited flow (EF) applications (e.g., delay-sensitive data, such as VoIP packets) to some or all of the sectors in the AT's active set. Examples of the multicast mechanism are further described below. Multicast allows sector B to be ready to serve when the DRC cover starts to point at it.
• EF expedited flow
• a minimum of two DR lengths of null cover may also be needed in a "IxEV-
• DO Revision A type system for both soft and softer handoff.
• the service outage for EF data in soft handoff may be reduced to two DRCLengths of null cover.
• For softer handoff it may remain at two DRCLengths of null cover.
• the difference between soft handoff and softer handoff in such systems may be that the latter happens at any DRC change boundary.
• FIG. 3 illustrates an embodiment of the DSC channel timeline for a DRCLength of two slots and a DSCLength of eight slots.
• FIG. 4 illustrates an embodiment of DRC cover change.
• DRC A and DRC B denote DRC covers associated with cell A and cell B, respectively.
• DRC NULL indicates a DRC with null cover.
• PKT A or PKT B indicate potential start of a new packet from cell A or cell B.
• PKT NULL indicates no new packet because of null- covered DRC.
• DSC may not point at a cell with weak reverse link. For example, if an AT receives a DRCLock bit that is set to "0" from a sector in its active set, the AT may not point its DSC to the data source associated with that sector (e.g., to avoid AT initiating a soft handoff).
• DSC/DRC repointing may be delayed, e.g., up to two
• DSCLengths in the worst case. As a result, a short DSCLength may be desirable to reduce the delay and possible service degradation due to bad channel conditions. On the other hand, higher transmit power may be needed to maintain the DSC channel reliability in such cases. Thus, the additional overhead needs to be evaluated against the benefit of shorter delay.
• DSC/DRC repointing may be initiated by the AT, e.g., based on the filtered forward link SINR measurements from different sectors.
• a first-order infinite impulse response (IIR) filter may be used (e.g., with a time constant of 64 slots).
• IIR infinite impulse response
• a parameter, termed "credit" herein and denoted by C B may be maintained for sector B and updated as follows:
• SINR A (n) and SINR B (n) denote the filtered pilot SINR measurements for sector A and sector B, respectively, and n denotes a time index.
• X and Y may be predetermined thresholds (e.g., measured in dB).
• SofterHandoffDelay and “SoftHandoffDelay” herein, associated with the minimum interruption/delay times when the AT switches its DRC from a source sector to a target sector belonging to the same and a different cell, respectively, hi some embodiments, the values of such handoff parameters may be in units of slots (e.g., 8 slots).
• the number of credits needed for repointing may be equal to SoftHandoffDelay. Because handoff would cause the service outage, a large threshold on the credits may limit the frequency at which an AT initiates handoff.
• thresholds may be used. For example: • If an AT is in softer-only handoff (e.g., all members of its active set belonging to the same cell), the threshold on the credit may be given by max(l, SofterHandoffDelay-DRCLength);
• the threshold may be given by max(l, SoftHandoffDelay- DSCLength).
• the threshold may be determined by the composition of the AT's active set (as opposed to at which sector the AT is going to repoint).
• the credit may be computed at the DRC change boundary for softer repointing and at the DSC boundary for soft repointing.
• a timer may be set when soft/softer repointing happens, such that the AT may not initiate another repointing before the timer expires.
• the timer expiration period may be equal to SofterHandoffDelay and SoftHandoffDelay, respectively. (As such, SofterHandoffDelay and SoftHandoffDelay may indicate the cost of softer and soft handoff.)
• ANC related to sector repointing e.g., a message termed "ForwardStopped” herein from sector A and another message termed “ForwardDesired” herein from sector B.
• These messages are processed by ANC to execute Q-transfer from sector A to sector B, and the service outage is associated with this Q-transfer (such as illustrated in FIG. 2B).
• continuous data service e.g., EF data/flows
• EF data/flows may be made possible by use of the DSC channel. Such may be carried out by decoding the DSC channel ahead of the DSC change boundary and letting ANC multicast data to some or all sectors in the AT's active set between the early detection and the final detection at the DSC boundary.
• multicast may be applied only to EF applications (e.g., delay-sensitive data, such as VoIP data), so as to limit the impact on backhaul traffic.
• each sector in the AT's active set may attempt to decode the
• each AP may provide a DSC decoding decision at time T Pd , which proceeds T d by a predetermined (e.g., system-wide configured) number of slots (e.g., 12 slots).
• the same energy threshold may be used as in the final decision at T d .
• ANC and APs e.g., those in the AT's active set:
• Serving AP An AP that has advertised a message (e.g., ForwardDesiredlnd) to ANC, and is considered as the serving AP until it has advertised another message (e.g., ForwardStoppedlnd) to ANC.
• a serving sector may refer to a sector serviced by the serving AP.
• Active serving AP An AP that has advertised a ForwardDesiredlnd message to ANC, and is considered by ANC to be serving data to the AT.
• Non-serving AP An AP that has advertised a ForwardStoppedlnd message to ANC, and is considered as a non-serving AP until it has advertised a ForwardDesiredlnd message to ANC.
• a non-serving sector may refer to a sector serviced by the non-serving AP.
• DSCChangedlnd In addition to ForwardStoppedlnd and ForwardDesiredlnd messages, a new message, termed "DSCChangedlnd" herein, may be used by an AP to indicate to ANC the change in the decoded value associated with the DSC channel. This indication may be issued by any serving AP in the AT's active set and indicates one of the following:
• a DSC value indicating the identity of the AP which the AT intends to handoff to.
• the DSC change time may also be provided, indicating the time at which the indicated DSC value may take effect.
• the handoff messages may be generated under the following conditions, and are also illustrated in Table 1 below: • ForwardDesiredlnd: The AP has successfully decoded the DSC channel received from the AT and the decoded DSC value is the same as its own (or self) DSC value. This may be generated at T P d and T d .
• Table 1 below illustrates combinations of messages and time instants during handoff.
• various handoff messages may be received in any order at ANC except for the following: DSCChangedlnd may not immediately follow
• ANC may enter into the multicast state upon receipt of one of the following events:
• ANC may exit the multicast state if there is only one serving AP in the AT's active set and it has not reported any DSC change.
• the original serving sector may send a ForwardStoppedlnd message to ANC, and the multicast mechanism may handle this situation normally, hi some embodiments, data between ANC and AP may be transmitted using user datagram protocol (UDP), while the signaling messages may be transmitted using transmission control protocol (TCP) for reliability.
• UDP user datagram protocol
• TCP transmission control protocol
• FIG. 5 illustrates an embodiment of a sequence of events taking place in a first soft handoff scenario, where both the active serving AP (or “API” for simplicity) and a non-serving AP (or “AP2” for simplicity) are able to correctly detect the DSC change.
• the active serving AP or "API” for simplicity
• AP2 non-serving AP
• API decodes the DSC channel and determines that the AT is no longer pointing its DSC to API.
• API subsequently sends a DSCChangedlnd message to ANC, which may include the new DSC value, the current queue level, the predicted switch time, etc.
• ANC enters into the multicast state, e.g., starting to multicast forward traffic (e.g., EF data) to all APs in the AT's active set.
• EF data forward traffic
• AP2 successfully decodes the DSC channel at time T Pd1 ⁇ and sends a ForwardDesiredlnd message to ANC.
• API concludes that the AT is switching to AP2, and sends a ForwardStoppedlnd message to ANC.
• ANC sets the active serving AP for the AT to be AP2, stops multicasting and starts to send forward traffic to AP2 only.
• FIG. 6 illustrates an embodiment of a sequence of events taking place in a second soft handoff scenario, where the active serving AP (or “APl) is able to correctly detect the DSC change and a non-serving AP (or "AP2”) detects a DSC erasure.
• the active serving AP or "APl”
• AP2 non-serving AP
• API decodes the DSC channel and determines that the AT is no longer pointing its DSC at API.
• API subsequently sends a DSCChangedlnd message to ANC, which may include the new DSC value, the current queue level, the predicted switch time, etc.
• ANC enters into the multicast state, e.g., starting to multicast forward traffic to all APs in the AT's active set.
• AP2 successfully decodes the DSC channel (which is pointing to itself), and sends a ForwardDesiredlnd message to ANC.
• AP2 decodes a DSC erasure, and sends a DSCChangedlnd message to ANC.
• API concludes that the AT is switching to AP2, and sends a ForwardStoppedlnd message to ANC.
• ANC sets the active serving AP for the AT to be AP2.
• AP2 successfully decodes more DSC symbols (which are the same as its own value). Because AP2 has just sent a DSCChangedlnd message to ANC, it sends another ForwardDesiredlnd message to confirm with ANC that the AT is in fact switching to AP2.
• FIG. 7 illustrates an embodiment of a sequence of events taking place in a third soft handoff scenario, where the active serving AP (or "API”) detects the DSC change after a DSC erasure and a non-serving AP (or "AP2”) is able to correctly detect the DSC change.
• the active serving AP or "API”
• AP2 non-serving AP
• AP2 successfully decodes the DSC channel (which is the same as its own value), and sends a ForwardDesiredlnd message to ANC.
• ANC enters into the multicast state, e.g., starting to multicast forward traffic to all APs in the AT's active set.
• API decodes a DSC erasure, and sends a DSCChangedlnd message to ANC.
• API decodes the DSC channel (which is pointing to a different AP), and sends a DSCChangedlnd message to ANC.
• API concludes that the AT is switching to AP2, and sends a ForwardStoppedlnd message to ANC.
• ANC sets the active serving AP for the AT to be AP2.
• FIG. 8 illustrates an embodiment of a sequence of events taking place in a fourth soft handoff scenario, where the active serving AP (or "API”) recovers from a DSC erasure and a non-serving AP (or "AP2”) recovers from a DSC erasure.
• the active serving AP or "API” recovers from a DSC erasure
• AP2 non-serving AP
• API decodes a DSC erasure, and sends a DSCChangedlnd message to ANC.
• ANC enters into the multicast state, e.g., starting to multicast forward traffic to all APs in the AT's active set.
• AP2 successfully decodes the DSC (which is pointing to itself), and sends a ForwardDesiredlnd message to ANC.
• AP2 decodes a DSC erasure, and sends a DSCChangedlnd message to ANC.
• API concludes that the AT is switching to AP2, and sends a ForwardStoppedlnd message to ANC.
• ANC sets the active serving AP for the AT to be AP2.
• AP2 successfully decodes more DSC symbols (which are the same as its own value). Because AP2 has just sent a DSCChangedlnd message to ANC, it sends another ForwardDesiredlnd message to confirm with ANC that AT is in fact switching to AP2.
• ANC stops multicasting and starts to send forward traffic to AP2 only.
• ANC may multicast forward traffic (e.g., EF data) to a subset of the APs in the AT's active set in the multicast state.
• use of multicast may compensate for the DSC erasure or error at a serving or non-serving sector.
• the multicast state may not start at T p a or T d , even if another AP sends a ForwardDesiredlnd message. In other words, the multicast state may start only after a DSCChangedlnd message is sent from the active serving sector.
• ForwardStoppedlnd message to ANC may also send its queue information.
• the message may indicate the last byte which has been sent.
• ANC may send out commands to every AP that is no longer considered as a serving sector, e.g., to flush their respective data queues. These commands, along with the opening and the closing of the flow, mark the transmission period. ANC may associate each packet it sends out with a tag number that changes incrementally (e.g., by a unit of "1") for each transmission period. Such may be useful in uniquely identifying packets at an AP.
• FIG. 9 illustrates a flow chart of a process 900, which may be used to implement some disclosed embodiments (such as described above).
• Step 910 determines a forward link (FL) quality metric associated with each of a plurality sectors serviced by a plurality of APs (e.g., in the active set of an AT).
• Step 920 assigns credits top each sector in relation to the FL quality metric as determined.
• Step 930 determines if the credits accumulated for a non-serving sector at the DSC change boundary are greater than a predetermined threshold, where the non-serving sector is serviced by a non- serving AP different from a serving AP for the AT.
• step 940 follows and changes the DSC value from the serving AP to the non- serving AP.
• Step 950 transmits the DSC value to the plurality of APs.
• Step 960 changes the DRC cover in accordance with the DSC change (e.g., repointing the DRC cover to the non-serving cover). If the outcome of step 930 is "NO,” process 900 returns to step 910.
• FIG. 10 illustrates a flow chart of a process 1000, which may be used to implement some disclosed embodiments (such as described above).
• Step 1010 decodes the DSC value received from an AT (such as described in the embodiment of FIG. 9).
• Step 1020 determines if the decoding is successful. If the outcome of step 1020 is "YES,” step 1030 determines if there is a change in the decoded DSC value. If the outcome of step 1030 is "YES,” step 1040 follows and sends a DSCChangedrnd message to an ANC. If the outcome of step 1030 is "NO,” process 1000 returns to step 1010. If the outcome of step 1020 is 'TS[O,” step 1050 follows and sends a DSCChangedlnd(Erased) message to the ANC.
• FIG. 11 illustrates a flow chart of a process 1100, which may be used to implement some disclosed embodiments (such as described above).
• Step 1110 decodes the DSC value received from an AT (such as described in the embodiment of FIG. 9).
• Step 1120 determines if the decoded DSC value is equal to the own value (e.g., that of a non-serving AP). If the outcome of step 1120 is ' ⁇ ES,” step 1130 follows and sends a ForwardDesiredlnd message to an ANC. If the outcome of step 1120 is "NO,” process 1100 returns to step 1110.
• FIG. 12 illustrates a flow chart of a process 1200, which may be used to implement some disclosed embodiments (such as described above).
• Process 1200 starts at step 1205.
• Step 1210 determines if a DSCChangedlnd message has been received from a serving AP (e.g., API described above). If the outcome of step 1210 is "YES,” step 1220 follows and starts multicasting forward traffic (e.g., EF data) associated with an AT to a plurality of APs (e.g., those in the AT's active set).
• Step 1230 determines if a ForwardDesiredlnd message has been received from a non-serving AP (e.g., AP2 described above).
• Step 1240 determines if a ForwardStoppedlnd message has been received from API. If the outcomes of both steps 1230 and 1240 are "YES,” step 1250 follows and assigns AP2 to be the active serving AP for the AT. If the outcome of either step 1230 or step 1240 is "NO,” process 1200 returns to step 1220.
• step 1260 follows and determines if a ForwardDesiredlnd message has been received from a non-serving AP (e.g., AP2 described above). If the outcome of step 1260 is "YES,” step 1270 follows and starts multicasting forward traffic (e.g., EF data) associated with the AT to a plurality of APs (e.g., those in the AT's active set).
• step 1280 determines if a DSCChangedlnd message has been received from a serving AP (e.g., API described above).
• Step 1290 determines if a ForwardStoppedlnd message has been received from API.
• step 1250 If the outcomes of both steps 1280 and 1290 are "YES,” process 1200 proceeds to step 1250. If the outcome of either step 1280 or step 1290 is "NO,” process 1200 returns to step 1270. If the outcome of step 1260 is "NO,” process 1200 returns to step 1205.
• FIG. 13 illustrates a block diagram of an apparatus 1300, in which some disclosed embodiments (such as described above) may be implemented.
• apparatus 1300 may include a channel-quality-estimation unit (or module) 1310 configured to determine a forward link quality metric associated with each of a plurality of sectors serviced by the plurality of APs (e.g., those in the active set of an AT); a credit-assigning unit 1320 configured to assign credits to each sector in relation to the FL quality metric; a DSC selection unit 1330 configured to select/change a DSC value for the AT (e.g., if the credits accumulated for a non-serving sector at the DSC change boundary are greater than a predetermined threshold); a transmitting unit 1340 configured to transmit the DSC value to the plurality of APs; and a DRC selection unit 1350 configured to select/change the DRC cover in accordance with the DSC change.
• channel-quality-estimation unit or module 1310 configured to determine a forward link quality
• DSC selection unit 1330 may be coupled to a communication bus 1360.
• a processing unit 1370 and a memory unit 1380 may also be coupled to communication bus 1360.
• Processing unit 1370 may be configured to control and/or coordinate the operations of various units.
• Memory unit 1380 may embody instructions to be executed by processing unit 1370.
• Apparatus 1300 may be implemented in an AT (e.g., AT 106 in FIG. 1), or other communication devices.
• FIG. 14 illustrates a block diagram of an apparatus 1400, which may be used to implement some disclosed embodiments (such as described above).
• apparatus 1400 may include a decoding unit (or module) 1410 configured to determine the DSC value received from an AT; a message-generating unit 1420 configured to generate a message in accordance with the DSC decoding (e.g., DSCChangedlnd, ForwardDesiredmd, ForwardStoppedlnd message or the like, such as described above); and a transmitting unit 1430 configured to send the message thus generated to an ANC.
• a decoding unit or module
• message-generating unit 1420 configured to generate a message in accordance with the DSC decoding (e.g., DSCChangedlnd, ForwardDesiredmd, ForwardStoppedlnd message or the like, such as described above)
• a transmitting unit 1430 configured to send the message thus generated to an ANC.
• decoding unit 1410 may be coupled to a communication bus 1440.
• a processing unit 1450 and a memory unit 1460 may also be coupled to communication bus 1440.
• Processing unit 1450 may be configured to control and/or coordinate the operations of various units.
• Memory unit 1460 may embody instructions to be executed by processing unit 1450.
• Apparatus 1400 may be implemented in an AP (e.g., API or AP2 described above), or other network infrastructure elements.
• AP e.g., API or AP2 described above
• FIG. 15 illustrates a block diagram of an apparatus 1500, which may be used to implement some disclosed embodiments (such as described above).
• apparatus 1500 may include a message-processing unit (or module) 1510 configured to receive a message from an AP (e.g., DSCChangedlnd, ForwardDesiredmd, or ForwardStoppedlnd message from API or AP2 described above); a multicasting unit 1520 configured to multicast forward traffic (e.g., EF data) associated with an AT to a plurality of APs (e.g., those in the active set of the AT); and a server selection unit 1530 configured to select an active serving AP for an AT.
• AP e.g., DSCChangedlnd, ForwardDesiredmd, or ForwardStoppedlnd message from API or AP2 described above
• multicasting unit 1520 configured to multicast forward traffic (e.g., EF data) associated with an AT to a plurality of APs (e.g., those
• message-processing unit 1510, multicasting unit 1520, and server selection unit 1530 may be coupled to a communication bus 1540.
• a processing unit 1550 and a memory unit 1560 may also be coupled to communication bus 1540.
• Processing unit 1550 may be configured to control and/or coordinate the operations of various units.
• Memory unit 1560 may embody instructions to be executed by processing unit 1550.
• Apparatus 1500 may be implemented in an ANC (such described above), or other network controller means.
• the transmit power of reverse link overhead channels may be tied at fixed offsets to the pilot transmit power.
• the latter may be controlled by power control, which may include an inner-loop power control and an outer-loop power control.
• the inner-loop power control may be configured to maintain the received pilot power at an AP to be around a threshold, which may in turn be determined by the outer- loop power control, m some situations, the threshold adjustment by the outer-loop power control may be based on data channel performance.
• the overhead channel performance may need to be considered separately. This may be particularly important in the case of soft handoff on reverse link.
• data decoding may benefit from the selection combining (e.g., combining decoding results from a plurality APs in an AT's active set) at ANC while overhead channels may not.
• the DRC performance may be poor especially in the presence of imbalance, where an AT points its DRC at one sector with which it has the best forward link, but is power- controlled by another sector with which it a better reverse link.
• the DRC channel if an AP makes a wrong decoding and schedules a packet transmission based on such, the packet may not be received by the corresponding AT and all the transmission slots may end up in waste. If the AP cannot decode the DRC channel successfully and declares a DRC erasure, the AT may not be served. In the situation of multiple users with delay insensitive (e.g., best-effort) data flows, this may cause little loss in sector capacity. Therefore, a reasonable DRC erasure rate may be tolerated in relation to a low DRC decoding error probability.
• the DRC candidate with the maximum received energy may be compared with a threshold.
• This candidate may become the DRC in effect when the energy is larger than the threshold; otherwise, a DRC erasure may be declared.
• the threshold on the DRC energy may be equivalent to a threshold on the received pilot power (termed “Ecp/Nt” herein).
• Ecp/Nt a threshold on the received pilot power
• the sector(s) may supply AT with reverse link SINR or DRC erasure rate via a feedback loop, e.g., by way of a DRCLock bit.
• Each sector may set the DRCLock bit for the AT in accordance with the evaluated erasure rate. For example, a DRCLock bit of "1" (“in-lock”) may indicate that the DRC erasure rate is acceptable; a DRCLock bit of "0" (“out-of-lock”) may indicate that the DRC erasure rate is unacceptable.
• Some mechanisms may be devised to avoid long outage for an AT suffering from consistently high erasure rate: e.g., one may be a slow mechanism using the DRCLock bit on forward link, indicating to the AT of high erasure rate and prompting the AT to handoff; another may be a fast mechanism of DRC erasure mapping, and so on.
• the DRCLock bit may be time-division-multiplexed with the power control channel. It may be transmitted once every DRCLockPeriod slots and repeated every DRCLockLength. (The equivalent feedback rate may be [600/(DRCLockPeriodxDRCLockLength)]Hz, for example.)
• the default values for DRCLockPeriod and DRCLockLength may be 8 slots, for example.
• the DRCLock bit may be transmitted along with the power control bit on the in-phase and the quadrature phase of the same MAC channel. The DRCLock bit may be transmitted once every 4 slots, for example.
• the parameter DRCLockLength may be kept for the DRCLock bit to repeat.
• the default value for DRCLockLength may be 16 slots, for example.
• the value of DRCLock bit may be based on the filtered DRC erasure rate.
• DRC erasure event may be mapped to a binary value and used to update an HR filter.
• the filtered value may be considered as an average DRC erasure rate.
• the default time constant for the HR filter may be 32 slots, for example.
• a hysteresis may be present in thresholding the filtered DRC erasure rate. For example, the DRCLock bit may be set to "1" if the filtered erasure rate is below 30%; the DRC Lock bit is set to "0" if the filtered erasure rate is above 50%.
• FIG. 16 illustrates an embodiment of the hysteresis associated with setting the DRCLock bit, where the DRC erasure events may stay constant at either 0 (no erasure) or 1 (erasure) for a relatively long period.
• the filtering operation thus described may render the DRCLock bit stable, yet slowly reacting to channel variation.
• the built-in delay in setting the DRCLock bit may imply a long DRC erasure run length (the time period during which consecutive DRC erasures occur). This may be taken into consideration during handoff. For EF (e.g., delay-sensitive) data, these erasures may result in an unacceptable amount of service outage. Thus, a need exists for a DRC erasure mapping algorithm configured to minimize the service outage on the forward link.
• a DRC erasure mapping algorithm may be performed at an
• the algorithm may be performed at each cell which has an active queue (e.g., set up by the ANC in unicast or multicast state) for the AT.
• the flow may be eligible for "limited" forward link scheduling (e.g., only served by multi-user packets).
• the cost of DRC erasure mapping may arise from sending data without knowing the forward link channel quality and wasting the associated transmission slots if the AT cannot decode the packet. Therefore, in some situations, the DRC erasure mapping algorithm may be activated when all of the following are met:
• a threshold (e.g., termed "Max_Ers_Len” herein) may be associated with the DRC erasure run length.
• the setting for the threshold maybe in the range of 0 to 16 slots, for example.
• DRC erasure mapping needs to be robust to long DRC erasure run lengths.
• an AT may perform a serving sector switching; however, a sector which is receiving erased DRCs may not be aware of this.
• the DSC channel may be used as complimentary information to assist the DRC erasure mapping decision, as further illustrated below.
• over-the-air (OTA) multicasting may be performed from multiple sectors to an AT to enhance the robustness of a DRC erasure mapping algorithm, as further described below.
• FIG. 17 illustrates an embodiment of a process 1700, which an AP may perform for each AT which has this AP in its active set.
• Process 1700 starts at step 1705.
• Step 1710 determines if the DRC cover received from the AT is erased. If the outcome of step 1710 is "NO,” step 1720 follows and schedules transmission for the AT from the sector to which the DRC cover is pointing. If the outcome of step 1710 is "YES", step 1730 follows and determines if DRC cover erasure criteria are met for the DRC cover from the AT.
• the DRC cover erasure criteria may include, for example, DRC erasure run length being greater than Max_Ers_Len, etc.
• step 1740 follows and determines if the DSC value received from the AT is erased. If the outcome of step 1740 is "NO”, step 1750 follows and determines if the DSC value corresponds to the cell serviced by the AP (termed “this cell” herein). If the outcome of step 1750 is "YES”, step 1760 follows and initiates OTA multicasting (e.g., transmitting forward traffic to the AT from a plurality of sectors that are in the AT's active set and in this cell), as FIG. 19 further illustrates. If the outcome of step 1740 is "YES”, process 1700 likewise proceeds to step 1760.
• OTA multicasting e.g., transmitting forward traffic to the AT from a plurality of sectors that are in the AT's active set and in this cell
• process 1700 if the outcome of step 1750 is "NO”, process 1700 ends at step
• step 1770 If the outcome of step 1730 is "NO", process 1700 likewise proceeds to step 1770.
• FIGs. 18A-I illustrate several processes which may be used to implement process 1700 illustrated in FIG. 17 in some embodiments, hi FIG. 18 A, step 1810 determines if the DRC cover received from the AT is not erased (e.g., Ecp/Nt above an erasure threshold), if the DRC cover (or "DRC_Cover") is not null, and if DRC_Cover is the same as the last successfully decoded DRC cover (termed “LDC” herein) or LDC and the second to last successfully decoded DRC cover (termed “2LDC” herein) are null.
• the DRC cover received from the AT is not erased (e.g., Ecp/Nt above an erasure threshold)
• DRC_Cover if the DRC cover (or "DRC_Cover") is not null, and if DRC_Cover is the same as the last successfully decoded DRC cover (termed “LDC” herein) or LDC and the second to last successfully decode
• step 1811 follows and sets the last valid DRC cover (or “Last_Valid_DRC_Cover”) to be DRC_Cover and a flag associated with the DRC cover change (or "DRCCoverChangedFlag") to be zero (or "0").
• DRCCoverChangedFlag may be used to indicate a consistency associated with the DRC covers received from the AT, which may be determined by comparing the DRC cover with one or more previously-received DRC covers from the AT.
• DRCCoverChangedFlag may be set to be "0" if the DRC cover is consistent with (e.g., substantially same as or comparable to) at least one of previously-received DRC covers (e.g., LDC) from the AT.
• Predetermined criteria may also be applied in evaluating the consistency associated with the DRC cover, including (but not limited to) if the DRC cover is valid (e.g., not erased and not null), if the DRC cover change is due to sector switching, etc.
• step 1820 determines if DRC cover is erased (or "DRC_Erasure").
• step 1821 follows and sets: (1) 2LDC to be LDC; (2) LDC to be DRC_Cover; (3) the last valid DRC index (or “Last_Valid_DRC_I ⁇ dex") to be the DRC rate (or “DRCJRate”) associated with the DRC cover; and (4) a count on the number of erasures (or "Erasure_Count”) to be "0". If the outcome of step 1820 is "YES,” step 1822 follows and sets Erasure_Count to be incremented by a DRCLength.
• step 1830 determines if the DSC value transmitted from the AT is erased, or the DSC value is invalid (e.g., having a zero value). If the outcome of step 1830 is "YES”, step 1831 follows and sets the stored DSC value (or "Stored_DSC_Value") to be the DSC value associated with this cell (or "This_Cell_DSC_Value”); a flag associated with DSC erasure (or "DSC_Erased_Flag”) to be one (or "1"); and a counter (or
• Step 1832 sets Stored_DSC_Value to be the decoded DSC value (or “DSC_Value”) and DSC_Erased_Flag to be "0".
• step 1840 determines if Stored_DSC_Value is equal to the last valid DSC value (or "Last_Valid_DSC_Value"). If the outcome of step 1840 is "NO”, step 1841 follows and sets a flag associated with updating Last_Valid_DSC_Value (or "LastValidDSCValue_needs_to_be_u ⁇ dated_flag") to be "1". Step 1842 subsequently determines if Stored_DSC_Value is equal to This_Cell_DSC_Value.
• step 1843 follows and sets Delay__Counter to be the delay (e.g., measured in unit of slots) accounted for DSC switching (or "DSCSwitchDelaylnSlots"). If the outcome of step 1842 is "NO”, step 1844 follows and sets Delay_Counter to be "0".
• step 1850 determines if
• step 1850 follows and decrements StopDRCErasureMap_dueto_DSCErasure_Counter by "1".
• step 1860 determines if
• LastValidDSCValue_needs_to_be_updated_flag is "1". If the outcome of step 1860 is "YES”, step 1861 follows and determines if Delay_Counter is "0". If the outcome of step 1861 is "NO”, step 1862 follows and decrements Delay_Counter by "1". If the outcome of step 1861 is "YES”, step 1863 follows and sets LastValidDSCValue_needs_to_be_updated_flag to be "0" and Last_Valid_DSC_Value to be Stored_DSC_Value. Step 1864 subsequently determines if Stored_DSC_Value is the same as This_Cell_DSC_Value. If the outcome of step 1864 is "YES”, step 1865 follows and sets LastValidDSC_Pointing_State to be "1". Otherwise, it is set to be "0” as shown in step 1866.
• step 1870 determines if Erasure_Count is greater than
• step 1870 Max_Ers_Len and if LastValidDSC_Pointing_State is "1". If the outcome of step 1870 is "YES", then the AT may be eligible for DRC erasure mapping from this cell, e.g., by setting Erasure_Mapped_Flag to be "1" as shown in step 1871.
• step 1880 determines if DSC_Erased_Flag is "1" and
• StopDRCErasureMap_dueto_DSCErasure_Counter is "0". If the outcome of step 1880 is "YES", then the AT is not eligible for DRC erasure mapping from the cell, e.g., by setting Erasure_Mapped_Flag to be "0" as shown in step 1881.
• step 1890 determines if DRC cover is not erased and
• step 1891 follows and schedules transmission for the AT from the sector to which DRC_Cover is pointing and at the corresponding DRC_Rate. If the outcome of step 1890 is "NO”, step 1892 follows and determines if Erasure_Mapped_Flag is "1". If the outcome of step 1892 is "YES”, step 1893 follows and initiates OTA multicasting to the AT, as further described below.
• FIG. 19 illustrates an embodiment of a process 1900, e.g., to implement the
• Step 1900 starts at step 1905.
• Step 1910 determines if there is any data for the AT in queue that is eligible for DRC erasure mapping (e.g., a delay sensitive flow with sufficiently long packet delay). If the outcome of step 1910 is "YES,” step 1920 follows and transmits data for the AT from a plurality of the sectors that are in this cell and in the AT's active set using a particular packet format (termed “DRC_index_mapped” herein). For example, multi-user packet format compatible with a predetermined set of DRC indices may be used. If the outcome of step 1920 is "NO,” process 1900 ends at step 1930.
• a forward link processor may receive 8 bits DRC info from a reverse link processor (e.g., a DSP), including: 1 bit DRC erasure flag indicating if Ecp/Nt is below an erasure threshold (or "DRC_Erasure”); 3 bits DRC cover (or “DRC_Cover”); 4 bits DRC rate (or “DRC_Rate”).
• the forward link processor may receive the decoded DSC value (or "DSCJValue” such as described above).
• a DRC erasure mapping algorithm may be performed (e.g., once every DRCLength) as follows:
• Erasure_Count Erasure_Count + DRCLength
• Delay_Counter 0;
• Delay_Counter DSCSwitchDelaylnSlots
• StopDRCErasureMap_dueto_DSCErasure_Counter > 0
• StopDRCErasureMap_duetoJDSCErasure_Counter StopDRCErasureMap_dueto_DSCErasure_Counter - 1;
• LastValidDSCValue_needs_to_be_updated_flag 0;
• LastValidDSC_Pointing_State 0;
• Delay_Counter Delay__Counter - 1;
• FIG. 20 illustrates a block diagram of an apparatus 2000, which may be implemented in an AP to perform some disclosed processes (such as described above).
• apparatus 2000 may include a DRC-evaluation unit (or module) 2010; a DSC-evaluation unit 2020; and a scheduling unit 2030.
• DRC-evaluation unit 2010 may be configured to determine the DRC value received from an AT; evaluate if DRC cover erasure criteria are met; evaluate the consistency of the received DRC covers; perform DRC erasure mapping, and so on (such as described above).
• DSC-evaluation unit 2020 may be configured to determine the DSC value received from the AT, evaluate if a DSC erasure has occurred; perform various functions in connection with DSC; and so on (such as described above).
• Scheduling unit 2030 may be configured to schedule transmission for the AT, such as described above. Scheduling unit 2030 may further include an OTA-multicasting unit 2035 configured to multicast forward traffic (e.g., data) to the AT from multiple sectors (such as described above).
• DRC-evaluation unit 2010, DSC-evaluation unit 2020, and scheduling unit 2030 may be coupled to a communication bus 2040.
• a processing unit 2050 and a memory unit 2060 may also be coupled to communication bus 2040.
• Processing unit 2050 may be configured to control and/or coordinate the operations of various units.
• Memory unit 2060 may embody instructions to be executed by processing unit 2040.
• Apparatus 2000 may be implemented in an AP, ' and/or other network infrastructure means.
• Embodiments disclosed herein provide some embodiments of adaptive server section in wireless communications. There are other embodiments and implementations. Various embodiments disclosed herein may be implemented in AT, AP, ANC, and/or other network infrastructure elements.
• Various units/modules and embodiments disclosed herein may be implemented in hardware, software, firmware, or a combination thereof.
• various units may be implemented within one or more application specific integrated circuits (ASIC), digital signal processors (DSP), digital signal processing devices (DSPDs), field programmable gate arrays (FPGA), processors, microprocessors, controllers, microcontrollers, programmable logic devices (PLD), other electronic units, or any combination thereof.
• ASIC application specific integrated circuits
• DSP digital signal processors
• DSPDs digital signal processing devices
• FPGA field programmable gate arrays
• processors microprocessors
• controllers microcontrollers
• PLD programmable logic devices
• various units may be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein.
• the software codes may be stored in a memory unit and executed by a processor (or a processing unit).
• the memory unit may be implemented within the processor or external to the processor, in which case it can be
• Various disclosed embodiments may be implemented in a controller, an AT, and other means for providing broadcast/multicast services.
• Embodiments disclosed herein may be applicable to a data processing system, a wireless communication system, a unidirectional broadcast system, and any other system desiring efficient transmission of information.
• DSP digital signal processor
• ASIC application specific integrated circuit
• FPGA field programmable gate array
• 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, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
• a software module may reside in random access memory (RAM), flash memory, read only memory (ROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
• An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium.
• the storage medium may be integral to the processor.
• the processor and the storage medium may reside in an ASIC.
• the ASIC may reside in an AT.
• the processor and the storage medium may reside as discrete components in an AT.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Computer Security & Cryptography (AREA)
• Mobile Radio Communication Systems (AREA)

Priority Applications (8)

Applications Claiming Priority (2)

Publications (2)

Family

ID=37667373

Family Applications (1)

Country Status (16)

Cited By (1)

Families Citing this family (28)

Citations (3)

Family Cites Families (40)

• 2006
  • 2006-08-16 EP EP06801680A patent/EP1922841B1/en not_active Not-in-force
  • 2006-08-16 MY MYPI2010000974A patent/MY144867A/en unknown
  • 2006-08-16 KR KR1020087006390A patent/KR101043563B1/ko active IP Right Grant
  • 2006-08-16 EP EP09153905A patent/EP2058985B1/en not_active Not-in-force
  • 2006-08-16 ES ES09153905T patent/ES2349883T3/es active Active
  • 2006-08-16 ES ES06801680T patent/ES2346565T3/es active Active
  • 2006-08-16 US US11/506,108 patent/US8406774B2/en active Active
  • 2006-08-16 DE DE602006014421T patent/DE602006014421D1/de active Active
  • 2006-08-16 RU RU2008110090/09A patent/RU2407188C2/ru not_active IP Right Cessation
  • 2006-08-16 PL PL09153905T patent/PL2058985T3/pl unknown
  • 2006-08-16 SG SG201006722-1A patent/SG165388A1/en unknown
  • 2006-08-16 WO PCT/US2006/032063 patent/WO2007022319A2/en active Application Filing
  • 2006-08-16 CN CN2010101111605A patent/CN101854689B/zh not_active Expired - Fee Related
  • 2006-08-16 SG SG201006723-9A patent/SG165389A1/en unknown
  • 2006-08-16 MY MYPI20063960A patent/MY142267A/en unknown
  • 2006-08-16 PL PL06801680T patent/PL1922841T3/pl unknown
  • 2006-08-16 BR BRPI0614812-3A patent/BRPI0614812A2/pt not_active IP Right Cessation
  • 2006-08-16 AT AT06801680T patent/ATE468683T1/de not_active IP Right Cessation
  • 2006-08-16 US US11/506,068 patent/US8385923B2/en active Active
  • 2006-08-16 EP EP10170126A patent/EP2242309B1/en not_active Not-in-force
  • 2006-08-16 CA CA2619837A patent/CA2619837C/en not_active Expired - Fee Related
  • 2006-08-16 DE DE602006015725T patent/DE602006015725D1/de active Active
  • 2006-08-16 TW TW095130166A patent/TWI353139B/zh not_active IP Right Cessation
  • 2006-08-16 AT AT10170126T patent/ATE536718T1/de active
  • 2006-08-16 CN CN2006800379878A patent/CN101288269B/zh not_active Expired - Fee Related
  • 2006-08-16 AT AT09153905T patent/ATE475237T1/de not_active IP Right Cessation
  • 2006-08-16 JP JP2008527121A patent/JP5203943B2/ja not_active Expired - Fee Related
• 2010
  • 2010-11-02 RU RU2010144963/08A patent/RU2010144963A/ru not_active Application Discontinuation
• 2011
  • 2011-03-16 JP JP2011058134A patent/JP5174202B2/ja not_active Expired - Fee Related
  • 2011-08-19 JP JP2011179694A patent/JP2012023745A/ja active Pending

Patent Citations (3)

Non-Patent Citations (4)

Also Published As

Similar Documents

Legal Events