Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04J—MULTIPLEX COMMUNICATION
  • H04J3/00—Time-division multiplex systems
  • H04J3/02—Details
  • H04J3/06—Synchronising arrangements
  • H04J3/0602—Systems characterised by the synchronising information used
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04B—TRANSMISSION
  • H04B7/00—Radio transmission systems, i.e. using radiation field
  • H04B7/14—Relay systems
  • H04B7/15—Active relay systems
  • H04B7/204—Multiple access
  • H04B7/212—Time-division multiple access [TDMA]
  • H04B7/2121—Channels assignment to the different stations
  • H04B7/2123—Variable assignment, e.g. demand assignment
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04B—TRANSMISSION
  • H04B7/00—Radio transmission systems, i.e. using radiation field
  • H04B7/24—Radio transmission systems, i.e. using radiation field for communication between two or more posts
  • H04B7/26—Radio transmission systems, i.e. using radiation field for communication between two or more posts at least one of which is mobile
  • H04B7/2643—Radio transmission systems, i.e. using radiation field for communication between two or more posts at least one of which is mobile using time-division multiple access [TDMA]
  • H04B7/2659—Radio transmission systems, i.e. using radiation field for communication between two or more posts at least one of which is mobile using time-division multiple access [TDMA] for data rate control
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04J—MULTIPLEX COMMUNICATION
  • H04J3/00—Time-division multiplex systems
  • H04J3/02—Details
  • H04J3/06—Synchronising arrangements
  • H04J3/0602—Systems characterised by the synchronising information used
  • H04J3/0605—Special codes used as synchronising signal
  • H04J3/0608—Detectors therefor, e.g. correlators, state machines
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04J—MULTIPLEX COMMUNICATION
  • H04J3/00—Time-division multiplex systems
  • H04J3/16—Time-division multiplex systems in which the time allocation to individual channels within a transmission cycle is variable, e.g. to accommodate varying complexity of signals, to vary number of channels transmitted
  • H04J3/1694—Allocation of channels in TDM/TDMA networks, e.g. distributed multiplexers
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L47/00—Traffic control in data switching networks
  • H04L47/10—Flow control; Congestion control
  • H04L47/15—Flow control; Congestion control in relation to multipoint traffic
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L47/00—Traffic control in data switching networks
  • H04L47/10—Flow control; Congestion control
  • H04L47/30—Flow control; Congestion control in combination with information about buffer occupancy at either end or at transit nodes
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L47/00—Traffic control in data switching networks
  • H04L47/70—Admission control; Resource allocation
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L47/00—Traffic control in data switching networks
  • H04L47/70—Admission control; Resource allocation
  • H04L47/76—Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions
  • H04L47/762—Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions triggered by the network
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L47/00—Traffic control in data switching networks
  • H04L47/70—Admission control; Resource allocation
  • H04L47/82—Miscellaneous aspects
  • H04L47/824—Applicable to portable or mobile terminals
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L7/00—Arrangements for synchronising receiver with transmitter
  • H04L7/04—Speed or phase control by synchronisation signals
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L7/00—Arrangements for synchronising receiver with transmitter
  • H04L7/04—Speed or phase control by synchronisation signals
  • H04L7/041—Speed or phase control by synchronisation signals using special codes as synchronising signal
  • H04L7/042—Detectors therefor, e.g. correlators, state machines
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W28/00—Network traffic management; Network resource management
  • H04W28/02—Traffic management, e.g. flow control or congestion control
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04H—BROADCAST COMMUNICATION
  • H04H20/00—Arrangements for broadcast or for distribution combined with broadcast
  • H04H20/28—Arrangements for simultaneous broadcast of plural pieces of information
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W28/00—Network traffic management; Network resource management
  • H04W28/02—Traffic management, e.g. flow control or congestion control
  • H04W28/10—Flow control between communication endpoints
  • H04W28/14—Flow control between communication endpoints using intermediate storage
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W72/00—Local resource management
  • H04W72/50—Allocation or scheduling criteria for wireless resources
  • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
  • H04W72/543—Allocation or scheduling criteria for wireless resources based on quality criteria based on requested quality, e.g. QoS

Definitions

• the present invention generally relates to communication systems and methods and more particularly to a system and method for a dynamic (adaptive) bandwidth allocation of a communication bandwidth among multiple sources of communication.
• a communication array, hub or base station In communication systems, it is common to use a communication array, hub or base station to provide a communication means such as an airlink between physically separated sources of commumcation such as voice or data communication, utilizing a communication device, or node. For communication such sources of communication exchange information. To exchange information an airlink bandwidth is shared among the sources of communication.
• the communication systems have to accurately and periodically process bandwidth information exchanged back and forth between these sources of communication.
• a wireless communication system provides bilateral communication between a plurality of remote stations or remote units and one or more base stations. The remote units could be either fixed or portable. The base station services the remote units.
• Such wireless communication systems provide commumcation channels or links on demand between the remote units and the base station to communicatively connect the remote unit with the base station.
• One group of conventional wireless systems using multiple access schemes utilize time segments or time bursts, often organized into frames of multiple burst periods, to provide bandwidth for use by communication systems, e.g. time division multiple access (TDMA).
• time segments may be used for control purposes, for information transfer, e.g., (data payload), or for a combination thereof.
• Information is typically transmitted to a specific remote unit or a base station during the time segments in the frame according to a time segment assignment to the specific remote unit or the base station.
• Remote units may communicate with the base station using a duplexing scheme which allows for the exchange of information in both directions of connection. Transmissions from the base station to the remote unit correspond to downlink or forward transmissions. Transmissions from the remote unit to the base station correspond to uplink or reverse transmissions.
• such wireless communication systems may use time division duplexing (TDD) methods to exchange information between the base station and the remote units.
• TDD duplexing schemes are well known in the art.
• the channel in such TDD systems comprises a sequence of frames. Each frame is time-divided into repetitive time periods or time segments which are employed for uplink and downlink transmissions.
• bandwidth requirements can significantly vary for these services.
• Such substantially varying bandwidth requirements may cause asymmetric bandwidth demand between sources of commumcation and/or the links, i.e., forward and reverse links, of the system.
• Implementation of typical prior art TDD schemes provides equal bandwidth in the forward and reverse links.
• these asymmetric bandwidth demands are often not efficiently served by such equal bandwidth allocation.
• Prior solutions have attempted to accommodate asymmetric bandwidth demand through implementing asymmetric airlinks.
• DBA dynamic bandwidth allocation
• communication bandwidth is dynamically allocated over a communication link among a plurality of sources of communication while in commumcation with at least one common source of commumcation within a communication system or network.
• the common source of communication preferably provides point to multipoint information communication to the plurality of sources of communication.
• the preferred embodiment of the present invention provides a scheduler that enables a dynamic bandwidth allocation (DBA) method to process bandwidth utilization information, such as may be derived from transmissions between the plurality of sources of communication and the common source of communication.
• DBA dynamic bandwidth allocation
• the present invention is particularly advantageous when used in a communication system having a plurality of sources of commumcation each of the plurality of sources of communication servicing a plurality of bursty data traffic sources, although the invention may also be used with a single communication link and/or non-bursty traffic sources.
• the communication system preferably includes one or more communication arrays, or hubs, which are centrally located to provide an airlink between a plurality of physically separated processor-based systems or remote units, or other sources of communication such as voice communication, utilizing a communication device, or node.
• Each hub and remote unit preferably includes one or more controllers.
• the preferred embodiment scheduler utilizes the controllers, or other information collection, analysis, and or compilation apparatus, to track and process bandwidth utilization information for dynamically sharing airlink bandwidth between one or more hubs and ones of the plurality of remote units.
• the scheduler tracks airlink communication traffic in both the "Forward" (FWD) or downlink and "Reverse” (REV) or uplink directions to accurately determine airlink bandwidth demand/requests for the plurality of remote units.
• a scheduler utilizes one or more controllers corresponding to the plurality of sources of commumcation to process bandwidth information.
• the DBA method preferably dynamically allocates airlink bandwidth in both commumcation directions of the communication traffic.
• queue size data associated with each source of communication is utilized to derive an accurate bandwidth demand/request for the source of communication.
• bandwidth demand/requests may be utilized in the alternative to or in combination with the aforementioned queue size data, if desired. For example, historical data, such as a particular time of day/days of week, may be utilized to predict bandwidth demand.
• a scheduler formulates non-redundant bandwidth requests. For example, in a request- grant cycle of a preferred embodiment, queue size data is utilized in conjunction with bandwidth utilization information to dynamically allocate an airlink bandwidth to a plurality of remote units.
• the bandwidth utilization information may include bandwidth commumcation parameters, such as a bandwidth request, a bandwidth grant, a traffic source queue size, information or data generated by aggregated traffic sources at a remote unit, information or data transmitted in a remote unit's one or more time slots during a predetermined time period such as a frame, and/or a request-grant shortfall being the difference between the requested and the granted bandwidth.
• bandwidth commumcation parameters such as a bandwidth request, a bandwidth grant, a traffic source queue size, information or data generated by aggregated traffic sources at a remote unit, information or data transmitted in a remote unit's one or more time slots during a predetermined time period such as a frame, and/or a request-grant shortfall being the difference between the requested and the granted bandwidth.
• the scheduler of the preferred embodiment tracks and processes bandwidth demand/request information, such as the aforementioned queue size data and/or bandwidth utilization information to implement current bandwidth requests for one or more remote units into scheduled bandwidth grants (allocations). Any delayed bandwidth grants are preferably decoupled from a new bandwidth request associated with the one or more remote units. This preferred embodiment distinguishes between those bits still in the queue (for example, due to any congestion) and those that are simply awaiting their pending transmission bandwidth grant. The scheduled bandwidth grants may then be utilized to determine a new transmission schedule for data communication through the airlinks, which may be transmitted to the remote units and/or other systems implementing the transmission schedule.
• bandwidth demand/request information such as the aforementioned queue size data and/or bandwidth utilization information to implement current bandwidth requests for one or more remote units into scheduled bandwidth grants (allocations). Any delayed bandwidth grants are preferably decoupled from a new bandwidth request associated with the one or more remote units. This preferred embodiment distinguishes between those bits still in the queue (for example, due to any congestion) and those that are simply awaiting their
• the preferred embodiment resets system states to reflect the implementation of the new transmission schedule, both at the hub and at the remote units and the request-grant cycle repeats.
• the preferred embodiment scheduler determines the number of new bytes, or other quantity of information, (e.g., those bytes arriving in queues subsequent to a previous bandwidth grant). For example, the scheduler may determine the number of new bytes generated for each remote unit from any changes in a queue size of a current frame compared to a queue size of a previous frame. In such an embodiment, for each remote unit, the scheduler may add the number of new bytes to the number of bytes transmitted by the remote umt within the current frame to calculate the number of new bytes generated for each remote unit within that current frame.
• the requested bandwidth may be compared with the granted bandwidth, wherein the grant occurs at the end of the previous frame.
• the difference between the requested bandwidth and the granted bandwidth provides a determination of the amount of the request-grant shortfall.
• the number of new bytes generated may be added to the amount of the request-grant shortfall corresponding to the remote unit. Accordingly, uplink or downlink bandwidth allocations may be dynamically modified to accommodate the uplink or downlink bandwidth requirements of the plurality of remote units within the airlink bandwidth, without granting bandwidth requests/demand with respect to particular data multiple times.
• the preferred DBA method provides desired dynamic bandwidth allocations substantially free of redundant bandwidth requests. For example, in a point to multipoint broadband communication system employing one or more radio frequency carriers operating in a time division duplex (TDD) mode, bandwidth allocations to multiple remote units or subscriber terminals associated with a carrier may be dynamically adjusted as bandwidth needs change.
• the present invention is particularly useful with subscribers having bursty data traffic.
• the present invention provides for a dynamic bandwidth allocation with a TDD boundary responding adaptively in response to traffic asymmetry varying dynamically. This allows the present invention to dynamically allocate a first number and/or size of time segments of a frame for downlink transmissions and configure a second number and or size of time segments of the frame for uplink transmissions. Alternatively, a first number of time segments of a frame could be allocated for one link direction transmissions and the remaining time segments of the frame for the other link direction transmissions.
• the preferred DBA method generally includes two phases, an initialization phase and a tracking phase to formulate bandwidth requests.
• a scheduler performs centralized processing to formulate bandwidth request determinations and dynamically allocating an airlink bandwidth among multiple sources of communication communicating with one common source of communication.
• a scheduler performs distributed processing to formulate bandwidth request determination and dynamically allocating an airlink bandwidth between multiple sources of communication communicating with one common source of communication.
• a scheduler sets a new bandwidth request equal to raw queue size data for dynamically allocating the uplink or downlink bandwidth to remote units sharing an airlink bandwidth while each remote unit independently servicing multiple, bursty data traffic sources.
• DBA dynamic bandwidth allocation
• FIGURE 1 illustrates an embodiment of the composition of a signal communicated by the present invention in a frame during a time division duplex burst period
• FIGURE 2 A shows an embodiment of the composition of a signal communicated by a preferred dynamic bandwidth allocation method consistent with the present invention in adjacent frames during a time division duplex multiple access burst period;
• FIGURE 2B shows an embodiment of the composition of a bandwidth request formulated from adjacent frames of FIGURE 2A in accordance with the present invention;
• FIGURE 3 is a functional depiction of the conceptual relationship between a scheduler and a commumcation network being managed utilizing a dynamic bandwidth allocation method consistent with the present invention
• FIGURE 4 A shows a flow chart of the one embodiment of the preferred dynamic bandwidth allocation method utilized to formulate bandwidth requests and dynamically allocating an airlink bandwidth among multiple sources of communication;
• FIGURE 4B shows a flow chart of the alternate embodiment of the preferred dynamic bandwidth allocation method utilized to formulate bandwidth requests and dynamically allocating an airlink bandwidth among multiple sources of communication;
• FIGURE 5 depicts an interconnection of processor-based systems consistent with a preferred embodiment of the present invention
• FIGURE 6 is a block diagram of the centralized commumcation array or hub depicted in FIGURE 5; and FIGURE 7 is a block diagram of the remote unit depicted in FIGURE 5.
• FIGURE 1 illustrates an embodiment of the composition of a signal communicated by a preferred embodiment of a preferred embodiment of the present invention in a frame 100 during a time division duplex burst period.
• frame 100 comprises a first time segment 110 and a second time segment 120.
• First time segment 110 preferably comprises a first set of time slots or burst periods for forward link data communication.
• second time segment 120 preferably comprises a second set of time slots or burst periods for reverse link data communication.
• the time segment allocations shown in FIGURE 1 are exemplary only, and the scope of the present invention should not be limited by the depicted allocations of time segments 110 and 120 or the uplink and downlink allocations shown.
• the particular time segments be associated with a particular link direction.
• a number of time slots in the first and second set of time slots assigned to the corresponding first and second time segments 110, 120 can vary without departing from the scope of the present invention.
• a number of time segments 110, 120 in frame 100 can vary without departing from the scope of the present invention.
• the amount of data or information communicated by the present invention in frame 100 could include but is not limited to either bits or bytes of data or information. Additionally, the data commumcation in frame 100 may include data packets of particular protocols, such as ATM or Ethernet data packets, and/or inband signaling information.
• DBA dynamic bandwidth allocation
• the preferred DBA method dynamically allocates a first set of time slots to first time segment 110 of frame 100 based upon downlink transmission or demand and the second time segment 120 of frame 100 is dynamically configured to include a second set of time slots based upon uplink transmission demand.
• FIGURE 2 A shows an embodiment of the composition of a signal communicated by the preferred DBA method in adjacent frames, including a current FRAME(N) 100a and a previous FRAME(N-1) 110b, during an exemplary time division duplex (TDD) multiple access burst period.
• Current FRAME(N) 100a comprises a first time segment 110a for downlink transmissions and a second time segmentl20a for uplink transmissions.
• previous TDD time division duplex
• FRAME(N-1) 100b comprises a first time segment 110b for downlink transmissions and a second time segment 120b for uplink transmissions.
• First time segments 110a, 110b, 120a, and 120b comprise a number of time slots each for data or information communication.
• a first frame boundary 230a indicates the end of current FRAME(N) 100a and could separate current FRAME(N) 100a from a next frame (not shown).
• a second frame boundary 230b indicates beginning of current FRAME(N) 100a and end of the previous FRAME(N-1) 100b.
• the frame boundaries may implement an amount of time as a guard band well known in the art.
• the boundary between the forward and reverse link time slots may include an amount of time to provide a guard band, if desired.
• the preferred DBA method utilizes useful bandwidth information associated with current FRAME(N) 100a and previous FRAME(N-1) 100b.
• Useful bandwidth information corresponding to current FRAME(N) 100a may include a bandwidth request BR(N) 240a, a bandwidth grant BG( N+5) 250a, a traffic source queue size QUEUE(N) 260a, a number of bits generated by aggregated traffic sources at a remote unit GEN(N) 270a, a number of bits transmitted in a remote unit's one or more time slots during current FRAME(N) 100a, TX(N) 280a, and or a request-grant shortfall SF(N) 290a being the difference between the requested and the granted bandwidth.
• useful bandwidth information corresponding to previous FRAME(N-1) 100b may include a bandwidth request BR(N-1) 240b, a bandwidth grant BG( N+4) 250b, a traffic source queue size QUEUE(N-1) 260b, a number of bits generated by aggregated traffic sources at a remote unit GEN(N-1) 270b, a number of bits transmitted in a remote unit's one or more time slots during previous FRAME(N-1) 100b, TX(N-1) 280b, and/or a request-grant shortfall SF(N-1) 290b.
• FIGURE 2B shows a preferred embodiment of the composition of a bandwidth request signal 240a formulated from adjacent frames current FRAME(N) 100a and previous FRAME(N- 1 ) 100b of FIGURE 2 A in accordance with the preferred DBA method consistent with the present invention.
• Exemplary signal composition 294 communicated by the present invention is shown.
• Exemplary signal composition 294 generally includes multiple time division duplex (TDD) multiple access burst periods to illustrate the preferred dynamic bandwidth allocation (DBA) method of the present invention.
• TDD time division duplex
• DBA dynamic bandwidth allocation
• TDD frames is utilized in the preferred DBA method to dynamically allocate the uplink or downlink bandwidth to one or more remote units for efficiently sharing an airlink to serve multiple, bursty data traffic sources.
• Super frame 296 corresponds to a finite communication delay.
• super frame 296 is of a predetermined length of four frames which starts at first frame boundary 230a and ends at a super frame boundary 298.
• the super frame 296 length could be suitably selected, for example, super frame 296 could include one or more frame lengths.
• FIGURE 3 functionally depicts the conceptual relationship between a commumcation system or network 300 being tracked and a scheduler 310. Moreover, FIGURE 3 illustrates the overseeing nature of scheduler 310 in one embodiment of the present invention to provide a general dynamic bandwidth allocation solution within communication system or network 300, regardless of their particular configurations and protocols.
• Communication system or network 300 of the illustrated embodiment includes a hub 320 and remote units (RUs) 330a through 330f.
• Hub 320 preferably comprises a hub controller 340.
• Each remote unit 330a through 330f preferably comprises a corresponding remote controller 350a through 350f, respectively.
• Each remote unit 330a through 330f generally services a plurality of bursty data traffic sources.
• Scheduler 310 of a preferred embodiment utilizes hub controller 340 and remote controllers 350a through 350f to track and process bandwidth information for commumcating between hub 320 and remote units 330a through 330f. Accordingly, scheduler 310 may be implemented as instruction sets operable upon controller 340 and or remote controllers 350a. Of course, scheduler 310 may be embodied in any number of processor based systems, whether general purpose or dedicated purpose, coupled to network 300, if desired.
• Scheduler 310 preferably tracks airlinks 360a through 360f (or some subset thereof) commumcation traffic in both "Forward” (FWD) or downlinks 370a through 370f and/or "Reverse” (REV) or uplinks 380a through 380f to accurately determine airlink bandwidth requests for the remote units 330a through 330f for which scheduling according to the present invention is to be provided.
• FWD Forward
• REV reverse
• uplinks 380a through 380f to accurately determine airlink bandwidth requests for the remote units 330a through 330f for which scheduling according to the present invention is to be provided.
• Remote units (RUs) 330a through 330f correspond to, generally physically separated, processor-based systems, or other sources of communication such as voice communication, utilizing a communication device, or node that are tracked by scheduler 310.
• Scheduler 310 preferably implements a dynamic bandwidth allocation method consistent with the present invention.
• the preferred embodiment of the present invention not only implements dynamic bandwidth allocation, but also provides a dynamic bandwidth allocation system and method that have improved efficiency over existing bandwidth allocation systems.
• the dynamic bandwidth allocation (DBA) system and method dynamically shares a communication bandwidth within a communication link.
• the communication bandwidth is dynamically allocated among the link directions (i.e., forward and reverse links) and/or a plurality of sources of communication that corresponding to RUs 330a through 330f while in commumcation with at least one common source of commumcation that corresponding to hub 320 within communication system or network 300.
• Hub 320 of the illustrated embodiment provides a point to multipoint information commumcation to RUs 330a through 330f.
• Scheduler 310 implements a dynamic bandwidth allocation (DBA) method to process bandwidth information associated with data transmitted back and forth between to RUs 330a through 330f and hub 320.
• DBA dynamic bandwidth allocation
• scheduler 310 of a preferred embodiment utilizes controllers 340 and 350a through 35 Of corresponding to hub 320 and RUs 330a through
• the DBA method dynamically allocates airlink bandwidth in both communication directions of the commumcation traffic.
• queue size data associated with each source of commumcation to receive dynamic allocation of bandwidth is utilized to derive accurate bandwidth requests such as BR(N) 240a or BR(N-1) 240b for RUs 330a through 330f.
• a queue size such as
• QUEUE(N) 260a or QUEUE(N-1) 260b preferably includes the amount of data awaiting transmission from a source of communication RUs 330a through 330f to a common source of communication hub 320.
• a queue size could include the amount of data awaiting transmission from a common source of communication RUs 330a through 330f to a source of communication hub 320.
• Each remote umt controller 350a through 35 Of preferably provides a REV queue size to hub 320 for bandwidth allocation analysis and allocation.
• hub controller 340 may provide a FWD queue size for corresponding RUs 330a through 330f.
• hub 320 can downlink downlinks 370a through 370f the FWD queue sizes to the RUs 330a through 330f, respectively.
• the preferred embodiment scheduler receives the REV queue size from each remote unit and the FWD queue size generated by the hub.
• the queue size QUEUE(N) 260a or QUEUE(N-1) 260b data within the REV and FWD queues may be referenced as often as once within FRAME(N) 100a or FRAME(N-1) 100b in order to determine the bandwidth requests BR(N) 240a or BR(N- 1) 240b, in both directions of the traffic from the sources of commumcation RUs 330a through 330f.
• scheduler 310 formulates non- redundant bandwidth requests BR(N) 240a or BR(N-1) 240b.
• a queue size data in conjunction with useful bandwidth information is utilized to dynamically allocate an airlink bandwidth to the plurality of remote units RUs 330a through 330f.
• Scheduler 310 of the preferred embodiment tracks and processes current bandwidth requests BR(N-1) 240b for each of a plurality of remote units RUs 330a through 330f into scheduled bandwidth grants (allocations) such as BG(N+4) 250b for the plurality of remote umts RUs 330a through 33 Of.
• Any delayed bandwidth grants are preferably decoupled from a new bandwidth request such as BR(N) 240a for each to plurality of remote units RUs 330a through 330f. This distinguishes between those bits still in the queue (for example, due to any congestion) and those that are simply awaiting their pending transmission bandwidth grant such as BG(N+4) 250b.
• a new transmission schedule is generated for remote umts RUs 330a through 330f and subsequently broadcasted to remote umts RUs 330a through 330f and/or hub 320.
• the system 300 states are preferably reset to reflect the implementation of the new transmission schedule, both at hub 320 and at remote units RUs 330a through 330f and the request-grant cycle repeats.
• scheduler 310 preferably tracks the number of new bytes, or other measure of new data to be carried via the links, that are generated in each frame FRAME(N) 100a or FRAME(N-1) 100b for each remote unit RUs 330a through 330f. Scheduler 310 may determine the number of new bytes generated for each remote unit RU 330a through
• scheduler 310 may add the number of new bytes to the number of bytes transmitted by the remote unit RUs 330a through 330f within the current FRAME(N) 100a to calculate the number of new bytes generated GEN(N) 270a for each remote unit RU 330a through 330f within that current FRAME(N) 100a.
• requested bandwidth such as BR(N-1) 240b may be compared with the granted bandwidth BG(N+4) 250b, wherein the grant occurs at the end of the previous FRAME(N-1) 100b.
• the difference between the requested bandwidth BR(N-1) 240b and the granted bandwidth BG(N+4) 250b provides a request-grant shortfall SF(N-1) 290b amount.
• the number of new bytes generated GEN(N) 270a may be added to the amount of the request-grant shortfall SF(N-1) 290b corresponding to remote unit RU 330a through 330f.
• uplinks 380a through 380f or downlinks 370a through 370b bandwidth allocations may be dynamically modified to accommodate uplinks 380a through 380b or downlinks 370a through 370b bandwidth requirements of the plurality of remote units RUs 330a through 330f to share one of airlinks 360a through 360f bandwidth while each RU 330a through 33 Of independently servicing multiple, bursty data traffic sources.
• scheduler 310 performs centralized processing to formulate a bandwidth request such as BR(N) 240a for dynamically allocating one of airlink 360a through 360f bandwidth among multiple sources of communication, remote units RUs 330a through 33 Of.
• FIGURE 4 A shows a flow chart of the one embodiment of the preferred dynamic bandwidth allocation method utilized to formulate a bandwidth request such as BR(N) 240a for dynamically allocating one of airlink 360a through 360f bandwidth among multiple sources of communication, remote units RUs 330a through 330f.
• N indicates frame index and J indicates remote index.
• a super frame length of four frame 100 lengths is selected for implementation of bandwidth. That is, there is a four frame delay between the time a BR is generated and the time a responsive BG is implemented. It is to be understood that the selected value four frames for super frame 296 length shown in FIGURE 4 A is exemplary only, and the scope of the present invention should not be limited by the selected value four of super frame 296 length.
• Scheduler 310 preferably does all of the processing required to form a non-redundant BR.
• scheduler 310 calculates the value of GEN at each remote RU 330a through 33 Of in an indirect fashion by using reported Q and observed TXB history.
• scheduler 310 does not have to be implemented this way.
• each remote RU 330a through 33 Of could simply uplink GEN directly, if remote umts RUs 330a through 330f have a means of keeping track of this parameter.
• Scheduler 310 in this scenario may calculate BR from GEN, whether scheduler 310 calculates GEN indirectly from monitoring each remote's RU 330a through 33 Of Q and TXB history, or whether each remote RU 330a through 33 Of supplies GEN directly in its uplink 380a through 380f time slot.
• step 405 indicates end of Nth Frame (Prior to Start of Frame[N+l ]).
• scheduler 310 initializes indexing for multiple remote umts RUs 330a through 330f, and starts looping through all active remote units among remote units RUs 330a through 330f.
• scheduler 310 records number of bits transmitted and the reported queue size from Remote[J] during Frame[N] that just ended.
• the uplinked queue size data may be slightly out-of-date (by some fraction of a frame) due to the time gap between the Remote's TX time slot and the end of the frame, when data from all remotes is complete and compiled for the scheduler 310.
• scheduler 310 estimates the number of bits of traffic generated by Remote[J] during Frame[N].
• scheduler 310 calculates the non-redundant BW request for Remote[J] as the sum of the bits of traffic it generated during Frame[N] and its request-grant shortfall from the prior frame (Frame[N-l]).
• scheduler 310 proceeds (in a loop) until this calculation has been performed for all active remote units.
• all remote units' non-redundant BW requests are supplied to the BW allocation algorithm so that BW can be granted to each remote. These BW grants are not implemented by the remotes until 4 frames from now due to turn-around delays.
• step 450 scheduler 310 initializes indexing for multiple remote units, and starts looping through all active remote units.
• scheduler 310 records the shortfall between requested BW and granted BW for Frame[N]'s allocation cycle. Then scheduler 310 resets SF to zero for BW request of zero.
• steps 460 and 465 scheduler 310 proceeds (in a loop) until this calculation has been performed for all active remote umts.
• scheduler 310 performs a distributed processing to formulate a bandwidth request such as BR(N) 240a for dynamically allocating one of airlink 360a through 360f bandwidth between multiple sources of communication, remote units RUs 330a through 330f.
• FIGURE 4B shows a flow chart of the alternate embodiment of the preferred dynamic bandwidth allocation method utilized to formulate a bandwidth request such as BR(N) 240a for dynamically allocating one of airlink 360a through 360f bandwidth among multiple sources of commumcation, remote units RUs 330a through 33 Of.
• scheduler 310 tracks the set of parameters of FIGURE 4 A flow chart.
• indexing in this scenario is slightly different from FIGURE 4A flow chart because processing is performed at least in part at remote units RUs 330a through 330f. Accordingly, the BR's at hub 320 are indexed by the frame that just ended, while BR's for the remote units RUs 330a through 330f are indexed by the current frame being used for transmission.
• a step 480 indicates end of N-l Frame (prior to start of FramefN]).
• each remote unit RU 330a through 330f records number of bits of traffic generated (disregarding amount transmitted) during the just finished frame (Frame[N-l]).
• remote unit receives downlink broadcast TX schedule from scheduler 310 at hub 320 to be used in this frame.
• Scheduler 310 includes BW grant and the time to start transmission (time slot start time).
• this frame's BW grant is in response to a request the remote made just slightly over 4 frames ago, near the end of Frame[N-5].
• Remote unit calculates the shortfall between what was requested and what was granted. Shortfall is reset to zero if bandwidth request is zero.
• the remote umt uses the shortfall and the number of traffic bits generated in the most recently completed frame to form a non-redundant BW request to be uplinked in this frame.
• Request is stored at the remote so it can be compared to the eventual responsive grant in Frame[N+5].
• the BW request is uplinked to hub 320 for scheduler 310 as overhead, along with payload traffic allowed by BG[N].
• hub 320 will have received all remote units' BW requests and uses them as input to the scheduler 310.
• the preferred DBA method provides desired dynamic bandwidth allocations substantially free of redundant bandwidth requests. For example, in a point to multipoint broadband communication system employing a plurality of radio frequency carriers operating in a time division duplex (TDD) mode, bandwidth allocations to multiple remote units RUs 330a through
• TDD time division duplex
• the present invention provides for a dynamic bandwidth allocation with a TDD boundary such as first frame boundary 230a or second frame boundary 230b responding adaptively in response to traffic asymmetry varying dynamically.
• the preferred DBA method consistent with the present invention provides an adaptive time division duplexing (ATDD) method and system for dynamically allocating bandwidth in wireless communication systems.
• ATDD adaptive time division duplexing
• the present invention is particularly useful in wideband or broadband wireless commumcation systems, although it may also be used in any data communication system where an adaptive and dynamic bandwidth allocation method is desirable.
• the preferred DBA method of the present invention having an adaptive time division duplexing (TDD) method and system provides an efficient use of commumcation channels in wireless commumcation systems by adapting to the uplink or downlink bandwidth requirements of multiple traffic sources within an airlink or a channel.
• TDD adaptive time division duplexing
• the preferred DBA method generally includes two phases, an initialization phase and a tracking phase to formulate bandwidth requests.
• scheduler 310 sets a new bandwidth request BR(N) 240a equal to raw queue size Q(N- 1) 260b data for dynamically allocating uplinks 380a through 380b or downlinks 370a through
• FIGURE 5 depicts an interconnection of processor-based systems consistent with a preferred embodiment of the present invention.
• the processor-based systems may include local area networks (LAN), such as LANs 510 and 520, or individual computer systems, such as PC 530.
• LAN local area networks
• PC 530 individual computer systems
• the processor-based systems utilizing the present invention may be general purpose computers, both standing alone and interconnected such as by a LAN.
• the system can connect other communication systems such as voice or video in combination with, or in place of, commumcation sourced by the above mentioned processor-based systems.
• Systems bridged by the present invention may utilize a communication device, hereinafter referred to as a "node,” for commumcating with a centralized commumcation device, hereinafter referred to as a "hub.”
• a hub is illustrated as element 501 and several nodes are illustrated as elements 550, 551, and 552 connected to LANs 510 and 520 as well as to PC 530.
• such wireless commumcation may be utilized to provide high speed communication between a processor-based system, having a node coupled thereto, and communication backbone, such as backbone 560, through hub 501.
• backbone 560 may be any form of commumcation means, such as a broadband fibre-optic gateway or other broadband data grade connection, TI communications lines, a cable commumcation system, the Internet, or the like, physically connected to hub 501.
• backbones such as illustrated by backbone 560, may be utilized to interconnect a plurality of hubs into a communications network.
• FIGURE 6 is a block diagram of the centralized communication array or hub 501 depicted in FIGURE 5. It can be seen in FIGURE 6 that preferred embodiment hub 501 includes outdoor unit (ODU) controller 630 coupled to each individual antenna element 600. ODU controller 630 is coupled to RF modem 640 and indoor unit (IDU) controller 650. Although a separate connection from ODU controller 630 is illustrated to modem 640 and CPU 660, it shall be appreciated that communication between ODU controller 630 and IDU controller 650 may be accomplished through the path connecting modem 640 to the ODU controller and CPU 660.
• ODU outdoor unit
• IDU indoor unit
• control information relevant to the operation of ODU controller 630 may be generated by modem 640 rather than CPU 660 and therefore be communicated through a connection between ODU controller 630 and modem 640.
• modem 640 rather than CPU 660 and therefore be communicated through a connection between ODU controller 630 and modem 640.
• alternate configurations of hub 501 are within the scope of the present invention
• ODU controller 630 preferably includes circuitry suitable for enabling the various antenna elements of hub 501 to communicate with RF modem 640 at the proper interval so as to transmit or receive the desired signal.
• ODU controller 630 includes a time division digitally controlled switch operating in synchronization with burst periods defined by IDU controller 650.
• IDU controller 650 provides a strobe pulse to the switch of ODU controller 630 to provide switching in synchronization with burst periods defined by IDU controller 650. It shall be appreciated that utilization of such a switch provides simple integration into the antenna array at a low cost. However, any switching means synchronizable to the burst periods defined by IDU controller 650 may be used if desired.
• Operation of ODU controller 630 results in each individual antenna element being in communication with IDU controller 650 according to a predetermined regime of communication sequence timing, i.e., frames of burst periods. This, in turn, results in each individual antenna element being in communication with modem 640 within IDU controller 650. It shall be appreciated that such switching results in the time division multiplexing (TDM) of each antenna element to modem 640.
• TDM time division multiplexing
• a second connection between ODU controller 630 and the various antenna elements may be utilized to provide synchronization, such as through the above discussed strobe pulse, to circuitry within the antenna elements to select between transmit or receive circuits at a proper frame and/or burst period.
• the antenna elements may be coupled to modem 640 at the proper instances to provide bi-directional communication through modem 640 resulting in time division duplexing (TDD).
• TDD time division duplexing
• IDU controller 650 of hub 501 may be re-directed in a variety of ways.
• IDU controller 650 correlates communication through a particular antenna element 600, or burst period associated therewith, as indicated by control of ODU controller 630, with a predefined communication path.
• communication received by IDU controller 650 at antenna element 600a illustrated in FIGURE 6, for example, may be routed by IDU controller 650 through antenna element 600b, as indicated by a correlation table, or the like, in RAM 670.
• a correlation table, or other correlation information could be utilized by IDU controller 650 to direct any communication received through a particular element, burst period, or channel of hub 501, including a backbone, to another particular element, burst period, or channel of hub 501.
• Such a embodiment is efficient where, for example, a processor-based system, in commumcation with hub 501 through antenna element 600a, is only desirous of commumcating with a processor-based system, in communication with hub 501 through element 600b.
• information communicated through hub 501 includes routing information .
• Such information is preferably in the form of data packets conforming to the open systems interconnection (OSI) model.
• OSI routing information is the transmission control protocol (TCP) standard.
• TCP transmission control protocol
• modem 640 modulates and demodulates communication between the antenna elements and IDU controller 650. Therefore, RF communication received at any antenna element may be stored within RAM 670 as digital information. Interface/router 680 may utilize predetermined pieces of information contained within the digital information, such as may be stored in RAM 670, to determine the routing of the received communication. In the preferred embodiment, routing information is provided by the network layer of a data packet conforming to the OSI model. Such information would be, for example, contained within each LAN data packet.
• the digital information may be re-directed by hub 501 through backbone 560 or through an antenna element via modem 640. It shall be understood that, because of the utilization of TDMA, the digital information may be stored in RAM 670 until such time as
• FIGURE 7 is a block diagram of the remote unit depicted in FIGURE 5.
• node 550 is comprised of two primary components, outdoor unit 710 and indoor unit 750, as depicted in FIGURE 7 .
• Outdoor unit 710 includes antenna 720, module 730 and modem 740.
• antenna 720 is preferably a parabolic dish antenna providing approximately 42 dB of gain with a communication lobe of approximately 2 degrees.
• Module 730 is a synthesized mm Wave front-end module accepting and transmitting 38 GHz RF through antenna 720 converted to an IF in the range of 400-500 MHZ for communication with RF modem 740.
• module 730 includes the various tuner and TDD switching components with respect to module 620.
• any number of component configurations are acceptable for use in module 730, as they are in module 620.
• the link illustrated between CPU 760 and module 730 may provide a signal controlling the synchronized switching the synchronized switching of the TDD switches according to a TDD frame of an associated hub.
• Modem 740 may be a variable rate modem, having a fixed baud rate with a variable density of bits per symbol, corresponding to the use of a variable rate modem utilized at a associated hub.
• the antenna and module attributes of node 550 may be different than that stated above where, for example, a different carrier frequency or beam patter is desired.
• Indoor unit 750 includes CPU 760, RAM 770 and interface 780. It shall be understood that indoor unit 750 and outdoor unit 710 are coupled such that information received by antenna 720 as RF energy is communicated to indoor unit 750. Of course, alternate configuration of node 550 are within the scope of the present invention.
• Interface 780 provides data communication between indoor unit 750, and thus node 550, and a processor-based system such as LAN 790 illustrated in FIGURE 7. Furthermore, interface 780 formats the data communication to be compatible with the processor-based system so coupled. As for example, where LAN 790 is coupled to node 550, interface 780 may both send and receive Ethernet data packets where LAN 790 utilizes Ethernet compatible commumcation protocol.
• interface 780 may include multiple communications protocols within a single embodiment, being user selectable, or may be individual modules to be included within controller 750 as needed.
• RAM 770 is coupled to both interface 780 and CPU 760. Where TDM is being used at hub 501, RAM 770 may store information received at node 150 through interface 780 while awaiting transmission to hub 501. RAM 770 may also contain additional stored information such as, for example, initialization instructions and link management information such as modem configuration instructions, power control instructions and error correction instructions discussed in detail below.
• RAM 670 of hub 501 and RAM 770 of node 550 may include instructions for the operation of CPUs 660 and 760 respectively. These instructions may include, for example, a method for programming hub 501 and node 550 for communication and a method for link management including communication error correction.
• both RAM 670 and RAM 770 may temporarily store information communicated via the device for re-transmission in the case a transmission error is detected.
• Transmission error may be detected by CPUs 660 and 760 by various methods.
• One such method well know in the art is the transmission of error detection information accompanying transmitted data packets. Such a method is defined in the data link layer of the aforementioned OSI model.
• a dynamic bandwidth allocation (DBA) system and method utilizes an "Immediate Response”technique to accurately process bandwidth information transmitted back and forth between a plurality of sources of communication.
• the sources of commumcation may include a plurality of remote units and one or more hubs.
• the "Immediate Response" dynamic bandwidth allocation system preferably includes a controller to implement an
• a finite delay in the "Immediate Response" DBA system's response to such bandwidth requests may cause a relatively inefficient bandwidth allocation among the sources of communication.
• the finite delay corresponds to a dynamic bandwidth allocation (DBA) response delay.
• This dynamic bandwidth allocation (DBA) response delay is generally introduced in a commumcation system from a delay caused between a bandwidth grant actually being implemented relative to a bandwidth request.
• the dynamic bandwidth allocation (DBA) response delay causes redundant bandwidth requests to be generated in the interim.
• the "Immediate Response" DBA system having a DBA response delay is relatively inefficient when a remote unit queue size is reported to a hub for the bandwidth request.
• the response delay from the time that the hub grants a bandwidth request to the remote unit until the remote unit can use that bandwidth grant may cause a relatively inefficient performance of an airlink shared with other remote units.
• a DBA response delay can cause a generation of one or more redundant bandwidth requests from remote units to the hub if the bandwidth requests are derived from the queue sizes. Therefore, it can be difficult to implement substantially efficient dynamic bandwidth allocation methodologies.
• An adapted system and method of sharing a bandwidth among multiple, bursty data traffic sources is desirable to avoid an inefficient dynamic bandwidth allocations to the multiple, bursty data traffic sources. Therefore, "Immediate Response" DBA systems and methods are adapted according to the present invention to provide desired dynamic bandwidth allocations substantially free of redundant bandwidth requests. Such adapted systems and methods decouple delayed grants from new bandwidth requests to provide a substantially efficient dynamic bandwidth allocation technique in communication systems including wireless commumcation systems. In particular, an adapted method and system dynamically allocates an uplink or downlink bandwidth in a time division duplexing (TDD) scheme among multiple traffic sources.
• TDD time division duplexing
• the adapted method and system is responsive to the needs of a particular airlink bandwidth allocation. Since the bandwidth needs may vary due to several factors, including the type of service provided over the airlink or the user type. Therefore, an adaptive time division duplexing method and system is provided that can flexibly, efficiently, and dynamically allocate the uplink or downlink bandwidth among multiple sources of communication for use in a broadband service network.
• an accounting system and method accurately process bandwidth information transmitted back and forth between a plurality of remote units and one or more hubs to dynamically share an airlink bandwidth.
• Such accounting system and method corresponds to a "Delayed Response" dynamic bandwidth allocation system and method.
• the plurality of remote units and the one or more hubs correspond to multiple, bursty data traffic sources.
• the plurality of remote units service multiple subscribers of one or more commumcation services over a broad band service network.
• the "Delayed Response" dynamic bandwidth allocation system preferably includes a controller to implement a "Delayed Response" dynamic bandwidth allocation (DBA) method.
• the "Delayed Response" DBA method provides an efficient use of an airlink bandwidth in both the communication traffic directions.
• the controller formulates non-redundant bandwidth requests to dynamically allocate bandwidth to the plurality of remote units.
• the dynamic bandwidth allocation (DBA) method preferably incorporates efficiency through statistical multiplexing of time-varying bandwidth requests from multiple subscribers of the one or more communication services.
• a feature of the present invention is to allow the mean packet or cell delay performance of a "Delayed Response" dynamic bandwidth allocation system to approach the performance of an"Immediate Response" dynamic bandwidth allocation system, to within an additive delay offset bounded by the dynamic bandwidth allocation response time.
• a further feature of the present invention is to avoid an inefficient airlink performance caused by using queue sizes directly as bandwidth requests which result in redundant bandwidth requests in a commumcation system with delayed dynamic bandwidth allocation response.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Mobile Radio Communication Systems (AREA)
• Time-Division Multiplex Systems (AREA)
• Small-Scale Networks (AREA)
• Data Exchanges In Wide-Area Networks (AREA)
• Synchronisation In Digital Transmission Systems (AREA)
• Synchronizing For Television (AREA)
• Electrophonic Musical Instruments (AREA)
• Hardware Redundancy (AREA)
• Radio Relay Systems (AREA)

Applications Claiming Priority (3)

Publications (2)

Family

ID=23014733

Family Applications (6)

Family Applications After (5)

Country Status (6)

Families Citing this family (35)

Citations (3)

Family Cites Families (29)

• 2002
  • 2002-02-06 CA CA002437476A patent/CA2437476A1/en not_active Abandoned
  • 2002-02-06 WO PCT/US2002/003323 patent/WO2002067514A1/en not_active Application Discontinuation
  • 2002-02-06 EP EP02706145A patent/EP1364474A4/de not_active Withdrawn
  • 2002-02-06 DE DE60210933T patent/DE60210933T2/de not_active Expired - Fee Related
  • 2002-02-06 CN CNA028066774A patent/CN1541463A/zh active Pending
  • 2002-02-06 WO PCT/US2002/003322 patent/WO2002063891A1/en active IP Right Grant
  • 2002-02-06 AT AT02709322T patent/ATE383685T1/de not_active IP Right Cessation
  • 2002-02-06 CA CA002437725A patent/CA2437725A1/en not_active Abandoned
  • 2002-02-06 DE DE60224506T patent/DE60224506T2/de not_active Expired - Lifetime
  • 2002-02-06 EP EP02709321A patent/EP1366587A4/de not_active Withdrawn
  • 2002-02-06 CN CNA028066758A patent/CN1498472A/zh active Pending
  • 2002-02-06 WO PCT/US2002/003189 patent/WO2002063807A1/en active IP Right Grant
  • 2002-02-06 CN CNB028071212A patent/CN1251521C/zh not_active Expired - Fee Related
  • 2002-02-06 CA CA002437467A patent/CA2437467A1/en not_active Abandoned
  • 2002-02-06 EP EP02740071A patent/EP1366629B1/de not_active Expired - Lifetime
  • 2002-02-06 CN CNA028066766A patent/CN1498461A/zh active Pending
  • 2002-02-06 AT AT02740071T patent/ATE341167T1/de not_active IP Right Cessation
  • 2002-02-06 EP EP02720902A patent/EP1366585B1/de not_active Expired - Lifetime
  • 2002-02-06 CA CA002437546A patent/CA2437546A1/en not_active Abandoned
  • 2002-02-06 WO PCT/US2002/003324 patent/WO2002063798A1/en not_active Application Discontinuation
  • 2002-02-06 CA CA002437733A patent/CA2437733A1/en not_active Abandoned
  • 2002-02-06 CA CA002441487A patent/CA2441487A1/en not_active Abandoned
  • 2002-02-06 CN CNA02806674XA patent/CN1498469A/zh active Pending
  • 2002-02-06 CN CNA028069242A patent/CN1498485A/zh active Pending
  • 2002-02-06 WO PCT/US2002/003193 patent/WO2002063805A1/en active IP Right Grant
  • 2002-02-06 EP EP02714833A patent/EP1364496A4/de not_active Withdrawn
  • 2002-02-06 WO PCT/US2002/003187 patent/WO2002063810A1/en not_active Application Discontinuation
  • 2002-02-06 AT AT02720902T patent/ATE324716T1/de not_active IP Right Cessation
  • 2002-02-06 DE DE60214981T patent/DE60214981T2/de not_active Expired - Fee Related
  • 2002-02-06 EP EP02709322A patent/EP1366584B1/de not_active Expired - Lifetime

Patent Citations (3)

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events