The present invention relates to wireless communications methods and apparatus and, more particularly, to methods and apparatus for implementing and using control channels.
In multiple access wireless communications systems, multiple wireless terminals are typically in competition for limited air link resources. A wireless terminal, operating in a state supporting uplink and downlink user data traffic signaling, typically tries to routinely communicate control information to a base station attachment point. In some systems control information may be communicated in the form of control information reports which allow the base station attachment point to obtain information about the wireless terminal status and effectively allocate resources. As the popularity and variety of wireless communication services has increased, the need to support ever larger numbers of concurrent users has grown. In addition, events and/or time of day can drive peak concurrent user demand.
Changes in the number of concurrent users can affect the demand for control information communication resources. However, it should also be appreciated that different wireless terminals can have different needs at different times and that the demand for resources in many cases is not simply a matter of the total number of terminals in the system that have the ability to communicate user data to the base station.
Different wireless terminals using the same base station attachment point often have different reporting needs and priorities. For example, a first wireless terminal operating from a current stationary position, with no or minimal obstructions between itself and the base station attachment point, and needing to communicate small amounts of user data infrequently may have very different control information reporting needs than another, e.g., second, wireless terminal, e.g., a mobile node in a moving automobile, experiencing rapidly changing channel conditions and/or needing to communicate large amounts of data frequently. Using a universal single control information reporting format to report control information to a base station although simple to implement can result in inefficiencies due to tradeoffs made to accommodate the wide variety of different types of anticipated concurrent users with reasonable degree of effectiveness.
In view of the above, it should be appreciated that there is a need for methods and apparatus which provide flexibility with regard to control information reporting, e.g., flexibility in terms of supported report formats. Improved methods and/or apparatus which tend to match a wireless terminal's current needs and/or conditions to a well suited control information report format would tend to increase efficiency and be beneficial, e.g., in terms of increasing traffic throughput capability. The ability to change control information reporting formats, if it could be supported, could also be useful in some cases.
Various embodiments are directed to methods and apparatus related to control information reporting over wireless communication channels including communicating control information format definition information over a wireless link. For example, in some embodiments, a base station downloads reporting format definition information, e.g., corresponding to a new release or a custom reporting format, into a wireless terminal. The reporting format information may define, e.g., control information report formats. The reporting format information may include, e.g., one or more report definitions. In some but not necessarily all embodiments the report format information may specify content to be included in one or more reports in addition to report transmission scheduling information indicating a schedule according to which defined reports should be transmitted. As another example, a wireless terminal generates a custom reporting format, that it intends to use, and communicates report format definition information corresponding to the generated custom reporting format to a base station.
An exemplary method of operating a first communications device, e.g., a wireless terminal, which interacts with a second communications device, e.g., a base station, includes: performing at least one of receiving and transmitting control information reporting format definition information from a wireless communications link. In some embodiments a wireless terminal receives report format definition information while in other embodiments it generates and transmits such information. In various exemplary embodiments, the first communications device generates a control information report in accordance with received and/or transmitted reporting format definition information. An exemplary communications device, e.g., wireless terminal, in accordance with some but not necessarily all embodiments, includes: at least one of: i) a receiver module for receiving control information reporting format definition information from a wireless communications link and ii) a transmitter module for transmitting control information reporting format definition information via a wireless communications link. The communications device may also include a control information report generation module for generating a control information report in accordance with at least one of i) received reporting format definition information and ii) transmitted reporting format definition information.
An exemplary method of operating a first communications device, e.g., a base station, which interacts with a second communications device, e.g., a wireless terminal, in accordance with some embodiments, includes: performing at least one of receiving report format definition information from a wireless communications link and transmitting report format definition information over a wireless communications link. The report definition information may define a control information report format. In one such exemplary embodiment, the first communication device recovers control information corresponding to a received control information report in accordance with one of received reporting format definition information and transmitted reporting format definition information. A communications device, e.g., a base station, in some but not necessarily all embodiments, includes: at least one of: i) a receiver module for receiving control information reporting format definition information from a wireless communications link and ii) a transmitter module for transmitting control information reporting format definition information via a wireless communications link. In such an exemplary embodiment the communications device may further include a control information report recovery module for recovering control information reports' information in accordance with at least one of i) received reporting format definition information and ii) transmitted reporting format definition information.
While various embodiments have been discussed in the summary above, it should be appreciated that not necessarily all embodiments include the same features and some of the features described above are not necessary but can be desirable in some embodiments. Numerous additional features, embodiments and benefits of the present invention are discussed in the detailed description which follows.
Exemplary wireless communications system 100 includes a plurality of base stations (base station 1102, . . . , base station M 104). Each base station (102, 104) has a corresponding wireless coverage area (cell 1106, cell M 108), respectively. System 100 also includes network node 118 which is coupled to base stations (102, 104) via network links (120, 122), respectively. Network node 118 is also coupled to other network nodes and/or the Internet via link 124. Network links (120, 122, 124) are, e.g., fiber optic links. System 100 may also include cells with multiple sectors and/or cells using multiple carriers.
System 100 also includes a plurality of wireless terminals. At least some of the wireless terminals are mobile node which may move throughout the communication system. In
Receiver module 204, e.g., an OFDM receiver, is coupled to receive antenna 202 via which the communications device 200 receives uplink signals from a plurality of wireless terminals. Received uplink signals include control channel signals, e.g., dedicated control channel signals, conveying control information reports, e.g., uplink traffic channel request reports, power reports, SNR reports, interference reports, noise reports, latency reports, etc. In some embodiments, the received uplink signals include information conveying a wireless terminal's format selection for control information reports to be transmitted by the wireless terminal. Receiver module 204 includes a decoding and demodulation module 218 for implementing decoding and demodulation operations on received control channel signals in accordance with the reporting format being used by the wireless terminal.
Transmitter module 208, e.g., an OFDM transmitter, is coupled to transmit antenna 206 via which the communications device transmits downlink signals to wireless terminals. In some embodiments, the downlink signals include signals conveying, on a per wireless terminal basis, a selected reporting format to be used by a particular wireless terminal for uplink control information reports, e.g., uplink dedicated control channel reports.
Memory 214 includes routines 220 and data/information 222. The processor 210, e.g., a CPU, executes the routines 220 and uses the data/information 222 in memory 214 to control the operation of the communications device and implement methods. I/O interface 212 couples the communications device 200 to other network nodes, e.g., other base stations, routers, AAA nodes, Home Agent nodes, central control nodes, etc., and/or the Internet.
Routines 220 include a report format selection module 224 and a report format recovery module 226. The report format selection module 224 selects, on a per wireless terminal basis, a reporting format to be used for control information reports, e.g., uplink dedicated control information reports. The report format selection module 224 selects a reporting format from a plurality of different reporting formats (reporting format 1 info 232, . . . reporting format N information 234) as a function of at least one of: received format selection control signal information 250, application type information 240, user quality of service information 242, device capability information 244, channel condition information 246 and system loading information 248. Selected reporting format 252 is an output of report format selection module 224 and identifies one of (reporting format 1 information 232, . . . , reporting format N information 234). In some embodiments, e.g., an embodiment where the communication device 200 decides upon the reporting format selection as a function of at least one of application type information 240, user QoS information 242, device capability information 244, channel condition information 246, and system loading information 248, the communications device 200 generates transmit signal information to convey the selected reporting format 254 to convey the selected format, and transmits the selection information to the wireless terminal. In some embodiments, a wireless terminal evaluates and decides upon a reporting format to use and conveys that information to communications device 200, which is received as received format selection control signal information 250. In some such embodiments, communications device 200 does not include transmit selected format control signal information 254.
Report format selection module 224 generates receiver control signal information 256 and recovery module control signal information 258. The decoding and demodulation module 218 of receiver module 204 uses the receiver control signal information 256 to identify and implement the appropriate coding and modulation scheme corresponding to the selected reporting format 252. Report format recovery module 226, operating on a per wireless terminal basis, uses the recovery module control signal information 258 to identify and implement the appropriate reporting schedule information, e.g., info 264, set of report definition information, e.g., info 266, and particular reporting definitions, e.g. some of info (236, . . . 238) being used for the sequence of uplink control information reports being communicated from the wireless terminal. Received control report channel signal information 260 includes information input to and output from decoding and demodulation module 218. Recovered control report information 262 includes information output from report format recover module 226.
Data/information 222 includes a plurality of sets of wireless terminal data/information (WT 1 data/information 228, . . . WT N data/information 230), a plurality of sets of reporting format information (reporting format 1 information 232, . . . , reporting format N information 234), and a plurality of sets of report definition information (report definition 1 information 236, . . . , report definition X information 238). WT 1 data/information 228 includes application type information 240, user quality of service information 242, device capability information 244, channel condition information 246, system loading information 248, selected reporting format 252, receiver control signal information 256, recovery module control signal information 258, received control report channel signal information 260, and recovered control report information 262. In some embodiments, WT 1 data/information includes at least one of a received format selection control signal information 250 and a transmit selected format control signal information 254. Reporting format 1 information 232 includes reporting schedule information 264, set of report definition information 266, and coding and modulation scheme information 268.
The report format selection module 320 selects a reporting format, said reporting format being one of a plurality of supported reporting formats, said reporting format indicating a reporting schedule and a set of report definitions. The report format selection module 320 includes: an input for receiving application type information 308, an input for receiving user quality of service information 312, an input for receiving channel condition information 314, an input for receiving device capability information 316, an input for receiving system loading information 318, and an input for receiving a report format selection control signal 306.
In some embodiments, report format selection module 320 selects a reporting format as a function of an application being executed by one of said communications device and another communications device. In some such embodiments, said application is one of a voice and a data application. In some embodiments, the reporting format stored in memory that is selected in response to a voice application includes a latency report. In some embodiments, the reporting format stored in memory that is selected in response to a data application includes less frequent uplink request reports than the format selected in response to a voice application but more bits per uplink request on average than used for reports selected in response to a voice application. For example, a reporting format used for a voice application may use 1 bit uplink request reports and a 1 bit uplink request report may be included in each successive dedicated control channel segment, while a reporting format used for a data application may use 4 bit uplink request reports, and a 4 bit uplink request report may be included in once for every 4 successive dedicated control channel segments.
In various embodiments, the report format selection module 320 selects a reporting format as a function of at least one of device capability information, user quality of service information, channel condition information 314, and system loading information 318. Device capability information includes, e.g., number of antennas; number of antennas per channel; device classification information, e.g., strong receiver, weak receiver, voice capable, data capable, voice and data capable, stationary device, low velocity mobile device, high velocity mobile device; rate capability information; power capability information; remaining battery power information, etc.
Receiver module 304 is coupled to receive antenna 302 via which the communication devices receives signals. In some embodiments, received signals include a report format selection control signal 306, e.g., a command from a base station to switch to a particular reporting format. The received signal 306 is conveyed to the report format selection module 306 which selects the format as a function received signal 306.
The report format selection module 320 is coupled to memory 324 via bus 322. Memory 324 includes a plurality of predetermined reporting format information sets (reporting format 1 information 326, . . . , reporting format N information 334) and report definition information (report definition 1 information 336, . . . , report definition X information 338). Report definition information, e.g., report definition 1 information 336, specifies a type of control information and control information to bit mapping information to be communicated in a report, e.g., an SNR report format, a traffic request report format, a power information report format, an interference request format. Report format 1 information 326 includes a reporting schedule 328, a set of report definitions 330, and a coding and modulation scheme 332. The set of report definitions 330 identifies a subset of set of report definitions (336, . . . , 338) used when the wireless terminal is operating in reporting format 1. The reporting schedule 328 includes information identifying a sequence of reports to be communicated within a reporting structure, e.g., a predetermined recurring reporting structure, when using reporting format 1. Coding and modulation scheme 332 identifies a coding and modulation scheme to be used to communicate control information reports when using reporting format 1, e.g., BPSK or QPSK, a number of information bits per segment, a number of coded bits per segment, and a mapping between coded bits and modulation symbols.
Report generation module 342 generates a sequence of reports 354 in accordance with the selected reporting schedule and at least some definitions in the set of report definitions. Report generation module 342 includes a plurality of different report type generation modules (report type 1 generation module 348, . . . , report type X generation module 350) and a multiplexer module 352. Report type 1 generation module 348 implements the report definition 1336 mapping report control information 344 to generate a set of control information report bits 349. For example, consider that report type 1 is a 4 bit uplink traffic channel request report which communicates backlog information about queued frames of information waiting to be communicated. In one such a case module 348 maps a count of frames to a quantization level represented by one of the sixteen potential 4 bit pattern which can be communicated by the report. Similarly report type X generation module 350 implements the report definition X 338 mapping report control information 346 to generate a set of control information report bits 351. For example, consider that report type X is a 5 bit SNR report. In one such case module 350 maps a determined SNR level to a quantization level represented by one of the thirty-two potential 5 bit patterns which can be communicated by the report.
Report format selection module 320 sends report generation control signal 340 to report generation module 342 to control which reports are to be generated and the sequencing of the reporting in accordance with the selected reporting format to be implemented. For example, control signal 340 enables a sub-set of report generation modules corresponding to the set of report definition corresponding to the selected reporting format. Report format selection module 320 also sends a control signal 356 to the transmitter module 358 to control the coding and modulation scheme to be implemented by coding and modulation module 360 corresponding to the selected reporting format. Coding and modulation module 360 performs a coding and modulation operation on the generated sequence of reports using a predetermined coding and modulation scheme corresponding to selected reporting format. For example, in one exemplary embodiment for one particular reporting format, a first coding and modulation scheme is used where the sequences of reports are grouped into sets of 6 information bits and the six information bits are coded into 21 QPSK modulation symbols. In the same exemplary embodiment, for another particular reporting format, a second coding and modulation scheme is used where the sequence of reports are grouped into sets of 8 information bits, and the eight information bits are coded into 21 QPSK modulation symbols. In some embodiments, different reporting formats may correspond to different modulation constellations, e.g., a BPSK modulation constellation and a QPSK modulation constellation. Transmitter module 358, e.g., an OFDM transmitter, transmits OFDM signals including the sequence of generated reports via transmit antenna 362. The generated sequence of reports, in some embodiments, corresponds to dedicated control channel reports.
Receiver module 404, e.g., an OFDM receiver, is coupled to receive antenna 402 via which the communications device 400 receives uplink signals from a plurality of wireless terminals. The received uplink signals include control channel signals, e.g., dedicated control channel signals conveying dedicated control channel reports. In some embodiments, the received uplink signals also include control channel information reporting format definition information, e.g., control channel format information corresponding to a custom reporting format determined by a wireless terminal.
Transmitter module 408, e.g., an OFDM transmitter, is coupled to transmit antenna 406 via which the communications device 400 transmits downlink signals to a plurality of wireless terminals. In some embodiments, the transmitted downlink signals include control channel information reporting format definition information, e.g., control channel format information corresponding to a custom reporting format determined by communications device 400, e.g., base station 400.
In accordance with various embodiments, different wireless terminals, using communications device 400, e.g., base station 400, as their point of network attachment can, and sometimes do, use different custom reporting formats for reporting uplink control information reports, e.g., different dedicated control channel reporting formats. For example, each of the customized reporting formats may be tailored to the current attributes, needs, and/or conditions of the particular wireless terminal and/or the environment in which the wireless terminal is currently operating.
I/O interface module 412 couples the communications device 400 to other network nodes and/or the Internet. Thus I/O interface 412 couples communications device 400 to a backhaul network facilitating a WT using base station 400 as its point of network attachment to participate in a communications session with a peer node using another base station as its point of network attachment.
Routines 418 include a control information report recovery module 422 and a reporting format control module 424. In some embodiments, routines 418 include a custom control information reporting format generation module. The control information report recovery module 422 is used to process received control information signals and recover control information report information. The control information report recovery module 422, which operates on a per wireless terminal basis, uses the selected reporting format information corresponding to the wireless terminal to identify which particular set of stored format information should be utilized to process the control information report signals from the wireless terminal. For example, consider that report recovery module 422 is processing received control information reports signals 440 from WT 1, if selected reporting format information 438 identifies the custom reporting format, stored control information reporting format definition information 436 is utilized; however, if selected reporting format information 438 identifies the default format, then, stored default reporting format information 434 is utilized.
Reporting format control module 424 checks at least one of device capability information, channel condition information, application information, quality of service information, system loading information and a command control signal; and the reporting format control module 424 controls switching between different possible formats as a function of the result of the checking. Reporting format control module 424 includes an evaluation sub-module 426 and a switching control sub-module 428. Evaluation sub-module 426 checks at least one of device capability information, channel condition information, application information, quality of service information and system loading information, e.g., against predetermined criteria, and/or checks for the presence of a command control signal. In some embodiments, a plurality of sets of stored control information reporting format definition information 436 have been stored, e.g., corresponding to a plurality of possible custom reporting formats and evaluation sub-module 428 is used to select between said plurality of alternative formats. Switching control sub-module 428 is responsive to determinations by evaluation sub-module 426, e.g., implementing a control information reporting format switch from a default reporting format to a first custom reporting format, from a first custom reporting format to a second custom reporting format, and/or from a custom reporting format back to a default reporting format. Custom control information reporting format generation module 425 generates for a wireless terminal a custom control information reporting format, e.g., a control information reporting format for its dedicated control channel signaling tailored to accommodate the wireless terminal's current application(s), needs, requirements, conditions, capabilities, and/or environment.
Data/information 420 includes a plurality of sets of wireless terminal data/information (WT 1 data/information 430, . . . , WT N data/information 432), and stored default reporting format information 434. WT 1 data/information includes stored control information reporting format information 436, selected reporting format information 438, received control information reports information 440 and recovered control information reports information 442. WT 1 data/information 430 includes at least one of received control information reporting format information 456, e.g., e.g., a customized control information reporting format determined by WT 1 for uplink control information reports, and transmitted control information reporting format information 458, e.g., a customized control information reporting format determined by BS 400 to be used by WT 1 for uplink control information reports. At least some of the stored control information reporting format information 436 corresponds to one of information 456 and information 458.
Stored control information reporting format definition information 436, e.g., custom reporting format definition information, includes a plurality of report definition information (report 1 definition information 444, report X definition information 446, set of reports information 448, reporting schedule information 450, e.g., information indicating a sequence in which reports are to be transmitted by WT 1, and coding and modulation scheme information 452, e.g., information specifying a coding and modulation scheme to be applied to the set of control information reports being communicated. Report 1 definition information 444 includes mapping information 454. Mapping information 454 defines a mapping between information communicated in said report and possible report values. Selected reporting format 438, e.g., indicates whether WT 1 is using custom reporting format definition information 436 or stored default reporting format information 434. Selected reporting format information 438 represents a control input used by control information report recovery module 422 when processing received control information reports 440 to determined recovered control information reports information 442.
In some embodiments, a wireless terminal generates control information reporting format information, e.g., a custom control information reporting format, and communicates the information to a base station, which will be receiving the control information reports in accordance with the custom reporting format. In some embodiments, the base generates control information reporting format information, e.g., a custom control information reporting format, and communicates the information to a wireless terminal, which will be generating control information reports in accordance with the custom reporting format. Thus, in accordance with various embodiments, a base station may be, and sometimes is receiving control information reports, e.g., dedicated control channel information reports, from a plurality of different wireless terminals, with at least some of the plurality of different wireless terminals using different custom reporting formats. In addition, the same wireless terminal may, and sometimes does, use different custom reporting formats at different times, e.g., with the particular report being tailored to accommodate current device capability information, system loading conditions, needs, applications, quality of service information and/or channel conditions.
Receiver module 504, e.g., an OFDM receiver, is coupled to receive antenna 502, via which the communications device receives signals, e.g., downlink signals from a base station. In some embodiments, the received signals include received control information reporting format definition information. Transmitter module 508, e.g., an OFDM transmitter, is coupled to transmit antenna 506 via which the communications device 500 transmits signals, e.g., uplink signals to a base station. In some embodiments, the transmitted signals include control channel reports, e.g., dedicated control channel reports, in accordance with a stored reporting format. For example, the stored reporting format is, at times, a default reporting format; while at other times the reporting format is a custom reporting format. In some embodiments, another node, e.g., a base station determines a custom reporting format for the communications device 500 to use and transmits control information reporting format definition information to communications device 500 which is received via receiver module 504 as received control information reporting format definition information 546. In some embodiments, communications device 500 determines a custom reporting format for the communications device 500 to use and transmits control information reporting format definition information 548 to another node, e.g., a base station. In this way the communications device 500 and the other node, e.g., base station, both can apply the same custom control information reporting format definition to control information reports being communicated, e.g., dedicated control channel reports.
Routines 516 include a control information report generation module 524 and a reporting format control module 526. In some embodiments, routines 516 include a custom control information reporting format generation module 527. The reporting format control module 526 includes an evaluation sub-module 528 and a switching control sub-module 530. Control information report generation module 524 generates a control information report in accordance with at least one of i) received reporting format definition information and ii) transmitted reporting format definition information.
Data/information 518 includes stored control information reporting format definition information 532 and stored default reporting format information 534. Data/information 518 includes at least one of received control information reporting format definition information 546 and transmitted control information reporting format definition information 548. Information 546 and/or information 548 corresponds to at least some of the information in stored control information reporting format definition information 532. Stored control information reporting format definition information 532, e.g., a custom reporting format to be used by wireless terminal 500, includes a plurality of report definition information (report 1 definition information 536, . . . , report X definition information 538), a set of reports information 540, reporting schedule information 542, and coding and modulation information 544.
Report 1 definition information 536 includes information corresponding to a particular type of report with a particular information bit size, e.g., a 4 bit uplink request report, a 5 bit SNR report, a 5 bit delay information report, etc. Report 1 definition information 536 includes mapping information 546 which maps a particular type of control information to one of a plurality of information bit patterns. Thus mapping information 546 defines a mapping between information to be included in a generated report and possible report values. Set of reports information 540 includes information identifying the different types of reports used for the custom reporting format. Reporting schedule information 542 includes information indicating a sequence in which reports of different types are to be transmitted. For example, the reporting schedule information 542 may identify an ordered sequence of report types in a predetermined reporting schedule. Alternatively, or in addition, the reporting schedule information may include information identifying time intervals for reports to be communicated, e.g., which OFDM symbol transmission time intervals are to be used to carry the sequence of control information reports to be transmitted. Coding and modulation scheme information 544 includes information identifying coding rates, modulation schemes, and/or modulation constellations used. Coding and modulation scheme information 544 includes information specifying a coding and modulation scheme to be applied to the defined set of reports to be communicated when using this reporting format.
Stored default reporting format information 534 includes a similar set of information to information 532. The default reporting formation information 534 is, in some embodiments, to be used, when communicating with another communications device, e.g., another base station, prior to receiving control information reporting format information from said another device or transmitting control information reporting format definition information to said another device. In some such embodiments, the stored default report format information 534 is used for an initial communication with said another communications device.
Reporting format control module 526 is used for checking at least one of device capability information, channel condition information, application information, quality of service information, system loading information and a command control signal and for controlling switching to another format as a result of said checking, e.g., switching to a custom reporting format, defined by information 532, which has been received or transmitted. Evaluation sub-module 528 checks at least one of device capability information, channel condition information, application information, quality of service information and system loading information, e.g., against predetermined criteria, and/or checks for the presence of a command control signal. In some embodiments, a plurality of sets of stored control information reporting format definition information 532 have been stored, e.g., corresponding to a plurality of possible custom reporting formats and evaluation sub-module 528 is used to select between said plurality of alternative formats. Switching control sub-module 530 is response to determinations by evaluation sub-module 530, e.g., implementing a control information reporting format switch from a default reporting format to a first custom reporting format, from a first custom reporting format to a second custom reporting format, and from a custom reporting format back to a default reporting format.
Custom control information reporting format generation module 527 generates for wireless terminal 500 a custom control information reporting format, e.g., a control information reporting format to be used subsequently for its dedicated control channel signaling, the generated custom control information reporting format tailored to accommodate the wireless terminal's current application(s), needs, requirements, conditions, capabilities, and/or environment.
Operation starts in step 602, where the first communications device is powered on and initialized. Operation proceeds from start step 602 to step 604. In step 604, the first communication device determines a set of control information reports to be transmitted, said set of control information reports corresponding to a first reporting format. Step 604 includes sub-step 606, in which the first communications device selects between a plurality of predetermined reporting formats. In some embodiments, each of said plurality of predetermined reporting formats specifies a plurality of different types of reports and an ordering of said different types of reports. In various embodiments, the different report types includes at least two of a SNR report, a traffic request report, a power information report and an interference report. In some such embodiments, the reporting format further specifies the control information to be communicated in said different types of reports, e.g., report parameter, report parameter units, quantization level information, and/or bit mapping information. Operation proceeds from step 604 to step 608.
In step 608, the first communications device generates the determined set of reports, and then in step 610, the first communications device communicates the generated set of reports. Step 610 includes sub-steps 612, 614 and 616. In sub-step 612, the first communications device multiplexes the generated reports of different types in accordance with the determined reporting format. Operation proceeds from sub-step 612 to sub-step 614. In sub-step 614, the first communications device performs a coding and modulation operation on the multiplexed generated set of reports to generate a set of coded symbols. In some embodiments, the step of coding and modulation includes using a predetermined coding and modulation scheme corresponding to the determined reporting format, with different coding and modulation schemes being used for at least some of said plurality of reporting formats. Then, in sub-step 616, the first communications device maps the coded symbols to segments of a wireless communications channel. For example, a set of ordered coded modulation symbols such as BPSK or QPSK modulation symbols are mapped to an ordered sequence of dedicated control channel segments. Operation proceeds from step 610 to step 604, where the first communications device determines another set of control information reports to be transmitted.
Operation starts in step 702, where the first communications device is powered on and initialized. Operation proceeds from start step 702 to step 704. In step 704, the first communication device determines a set of control information reports to be transmitted, said set of control information reports corresponding to a first reporting format. Step 704 includes sub-step 706, in which the first communications device selects the reporting format as a function of an application being executed by one of said first and second communications devices.
In some embodiments, the application is one of a voice and data application. In some such embodiments, a reporting format selected in response to a voice application includes a latency report and a reporting format selected in response to a data application includes less frequency uplink request reports than a format used for voice but more bits per uplink request on average than used for voice.
In some embodiments, each of said plurality of predetermined reporting formats specifies a plurality of different types of reports and an ordering of said different types of reports. In various embodiments, the different report types includes at least two of a SNR report, a traffic request report, a power information report, an interference report, and a delay report. In some such embodiments, the reporting format further specifies the control information to be communicated in said different types of reports, e.g., report parameter, report parameter units, quantization level information, and/or bit mapping information. Operation proceeds from step 704 to step 708.
In step 708, the first communications device generates the determined set of reports, and then in step 710, the first communications device communicates the generated set of reports. Operation proceeds from step 710 to step 704, where the first communications device determines another set of control information reports to be transmitted.
Operation starts in step 802, where the first communications device is powered on and initialized. Operation proceeds from start step 802 to step 804. In step 804, the first communication device determines a set of control information reports to be transmitted, said set of control information reports corresponding to a first reporting format. Step 804 includes sub-step 806, in which the first communications device determines a reporting format as a function of at least one of: device capability information, channel conditions, system loading, and quality of service information. Device capability information includes, e.g., information regarding number of antennas, information regarding number of receiver chains, power information, data rates supported, modulation schemes supported, receiver sensitivity, self noise information, and application support. For example, wireless terminals may be classified in sub-groups as a function of device capability, e.g., voice capable cellphones, voice and data capable cell phones, data terminals, voice and data terminals. Another exemplary classification may be in terms of mobility capability. Some wireless terminals may be suitable for stationary operation but not intended for dynamic operations, others may be suitable for mobile operation at up to a first rate of motion, and still others may be suitable for mobile operations at upto a second rate of motion, said second rate being higher than said first rate. Power information is also used in some embodiments to determine a reporting format to be used. Power information may include, power source information, e.g., battery vs external source, different power modes, e.g., a normal communications mode and a power saving mode, remaining battery power information, transmission power level information, rate of usage of battery power, etc.
In some embodiments, each of said plurality of predetermined reporting formats specifies a plurality of different types of reports and an ordering of said different types of reports. In various embodiments, the different report types includes at least two of a SNR report, a traffic request report, a power information report format, an interference report, and a delay report. In some such embodiments, the reporting format further specifies the control information to be communicated in said different types of reports, e.g., report parameter, report parameter units, quantization level information, and/or bit mapping information. Operation proceeds from step 804 to step 808.
In step 808, the first communications device generates the determined set of reports, and then in step 810, the first communications device communicates the generated set of reports. Operation proceeds from step 810 to step 804, where the first communications device determines another set of control information reports to be transmitted.
Operation starts in step 902, where the first communications device is powered on and initialized. Operation proceeds from start step 902 to step 904. In step 904, the first communication device uses a default reporting format when communicating with said second communications device. Then, in step 906, the first communications device performs at least one of receiving and transmitting control information reporting format definition information via a wireless communications link. The reporting format definition information communicated over the wireless communications link, in some embodiments, is sufficient to define the reporting format. For example, the reporting format definition information communicated over the wireless link may include individual report format information corresponding to a plurality of different types of reports and reporting sequence information. The reporting format definition information communicated over the wireless communications link, in some embodiments, is used in combination with pre-stored information to define the reporting format. For example, the first and second communication devices may have pre-stored a plurality of individual report format definitions corresponding to a plurality of different types of reports, and the reporting format definition information communicated over the wireless link may include information identifying a subset of those different types of reports and an ordered sequence of reports corresponding to members of the identified subset Operation proceeds from step 906 to step 908. In step 908, the first communications device generates a control information report in accordance with one of the received and transmitted reporting format definition information.
In some embodiments, the reporting format provides a definition mapping information to be included in a control information report to possible report values, e.g., for a plurality of different reports. For example, the reporting format may include a report definition for a 5 bit SNR report, a report definition for a 1 bit uplink traffic channel request report, a report definition for a 3 bit uplink traffic channel request report, a report definition for a 4 bit power report, etc. In various embodiments, the reporting format defines a reporting schedule according to which reports are to be transmitted. In some embodiments, the reporting format defines a set of reports which are to be transmitted in accordance with the defined reporting schedule. A reporting format may, and sometime does, specify a coding and modulation scheme to be applied to a set of reports.
Operation starts in step 1002, where the first communications device is powered on and initialized. Operation proceeds from start step 1002 to step 1004. In step 1004, the first communication device uses a default report format as a current reporting format when communicating with said second communications device. Then, in step 1006, the first communications device performs at least one of receiving and transmitting control information reporting format definition information from a wireless communications link. In some embodiments, the reporting format definition information is received from a base station, e.g., the base station which the first communications device is using as its current attachment point. In some embodiments, the reporting format definition information is received from a centralized server. Operation proceeds from step 1006 to step 1008.
In step 1008, the first communications device checks at least one of device capability information, channel conditions, application information, quality of service information and system loading. Then, in step 1010, the first communications device determines if the result of the check of step 1008 indicates that the reporting format should be changed. If the determination of step 1010 is that the reporting format should be changed, then operation proceeds to step 1012; otherwise, operation proceeds to step 1014. In step 1012, the first wireless terminal switches the current reporting format to a new reporting format, e.g., said new reporting format in accordance with said control information reporting format definition information from a wireless communications link. Operation proceeds from step 1012 to step 1014. In step 1014, the first communications device generates a control information report in accordance with the current report format definition information. Operation proceeds from step 1014 to step 1008, where the first communication device performs another check of at least one of device capability information, channel condition, application information, quality of service information and system loading.
In some embodiments, the reporting format provides a definition mapping information to be included in said report to possible report values. In various embodiments, the reporting format further defines a reporting schedule according to which reports are to be transmitted. In some embodiments, the reporting format defines a set of reports which are to be transmitted in accordance with the defined reporting schedule. A reporting format may, and sometime does, specify a coding and modulation scheme to be applied to a set of reports.
Second row 1104 will now be described. Wireless terminal 1110 processes control command signal 1130 and selects to use DCCH reporting format 2 as indicated by arrow 1132.
Third row 1106 will now be described. Wireless terminal 1110 generates a sequence of uplink DCCH reports in accordance with DCCH reporting format 2 as indicated by generated information 1134. Wireless terminal transmits DCCH report signals 1136 to base station 1108. The base station 1108 receives and processes the DCCH report signals using DCCH reporting format 2 information 1114 obtaining recovered DCCH report information 1138.
Second row 1204 will now be described. Base station 1208 processes control command signal 1230 and selects to use DCCH reporting format 2 as indicated by arrow 1232.
Third row 1206 will now be described. Wireless terminal 1210 generates a sequence of uplink DCCH reports in accordance with DCCH reporting format 2 as indicated by generated information 1234. Wireless terminal 1210 transmits DCCH report signals 1236 to base station 1208. The base station 1208 receives and processes the DCCH report signals using DCCH reporting format 2 information 1214 obtaining recovered DCCH report information 1238.
Second row 1304 will now be described. Wireless terminal 1310 processes received signals 1318 conveying custom DCCH reporting format 1 information and stores custom DCCH reporting format 1 information 1320.
Third row 1306 will now be described. Arrow 1322 pointing to custom DCCH reporting format 1 information 1320 in wireless terminal 1310 and arrow 1324 pointing to DCCH custom reporting format 1 information 1414 in base station 1308 indicate that at this time both WT 1310 and base station 1308 are using DCCH custom reporting format 1. Wireless terminal 1310 generates a sequence of uplink DCCH reports in accordance with custom DCCH reporting format 1 as indicated by information 1326. Wireless terminal 1310 transmits DCCH report signals 1328 to base station 1308. The base station 1308 receives and processes the DCCH report signals using custom DCCH reporting format 1 information 1314 obtaining recovered DCCH report information 1330.
Second row 1404 will now be described. Base station 1408 processes received signals 1418 conveying custom DCCH reporting format 1 information and stores custom DCCH reporting format 1 information 1420.
Third row 1406 will now be described. Arrow 1422 pointing to custom DCCH reporting format 1 information 1416 in wireless terminal 1410 and arrow 1424 pointing to DCCH custom reporting format 1 information 1420 in base station 1408 indicate that at this time both WT 1410 and base station 1408 are using DCCH custom reporting format 1. Wireless terminal 1410 generates a sequence of uplink DCCH reports in accordance with custom DCCH reporting format 1 as indicated by information 1426. Wireless terminal 1410 transmits DCCH report signals 1428 to base station 1408. The base station 1408 receives and processes the DCCH report signals using custom DCCH reporting format 1 information 1420 obtaining recovered DCCH report information 1430.
Exemplary DCCH custom reporting format wireless signals 1502 includes a plurality of report type definition information (report type 1 definition information 1504, . . . , report type N definition information 1506), reporting schedule information 1508, and coding and modulation information 1510. Each report type definition information (1504, 1506) includes mapping information (1512, 1514), respectively, which defines mapping of control information to potential information bit patterns used by the report. Reporting schedule information 1508 includes report sequencing information 1516, recurring timing structure information 1518, and DCCH segment definition information 1520.
Exemplary DCCH custom reporting format wireless signals 1504 includes sequence information corresponding to known report types, e.g., a sequence indicating report C, report A, report B, report J, report D, . . . , report A, report D. In some embodiments, a recurring DCCH reporting structure is known, e.g., 40 indexed DCCH segments in a beaconslot, and the reporting sequence communicated in signals 1504 is such to identify the report types used for the segments. In some embodiments, the number and/or type of reports communicated in the reporting sequence in signals 1504 is used to identify the number of reports to be communicated and/or the size of a recurring reporting structure.
First row 1608 indicates that exemplary WT 1 is using a voice traffic application, and the DCCH reporting format being used includes a delay report and frequent small bit size traffic request reports, e.g., frequent single bit uplink traffic channel request reports. Second row 1610 indicates that exemplary WT 2 is using a delay insensitive data traffic application, e.g., a file transfer protocol (FTP) application, and the DCCH reporting format being used does not include delay reports, but does include infrequent large bit size traffic request reports, e.g., infrequent 4 bit uplink traffic channel request reports. Third row 1612 indicates that exemplary WT 3 has a need to communicate a mixture of voice and data traffic, e.g., WT 3 is running a voice application an Internet gaming application, and the DCCH reporting format being used includes a mixture of different size traffic request reports, e.g., a 1 bit uplink traffic channel request report, a 3 bit traffic channel request report, and a 4 bit traffic channel request report. Fourth row 1614 indicates that exemplary WT 4 is a multiple antenna device, and the DCCH reporting format being used includes additional SNR reports for reporting various alternatives. Fifth row 1616 indicates that exemplary WT 5 is experiencing low battery power level, and the DCCH reporting format being used has less segments per unit time to conserve energy. Sixth row 1618 indicates that exemplary WT 6 is a stationary device, and the DCCH reporting format being used less frequently reports SNR and transmission power information, e.g., transmission power backoff information. Seventh row 1620 indicates that exemplary WT 7 is a moving high velocity device, and the DCCH reporting format being used more frequently reports SNR and transmission power information, e.g., transmission power backoff information. Eighth row 1622 indicates that exemplary WT 8 includes an expensive high quality receiver, and the DCCH reporting format being used omits self-noise reports. Ninth row 1624 indicates that exemplary WT 9 is using an isolated base station, and the DCCH reporting format being used omits interference reports comparing signals from different base stations, e.g., beacon ratio reports are not included. Tenth row 1626 indicates that exemplary WT 10 is experiencing very good and stable channel conditions, and the DCCH reporting format being used includes an SNR report that has a narrow range around relatively high values, and the DCCH reporting format being used includes at least some differential reports, e.g., delta reports with respect to previously communicated DCCH reports. Eleventh row 1628 indicates that exemplary WT 11 is experiencing poor but stable channel conditions, and the DCCH reporting format being used includes an SNR report that has a narrow range around relatively low values. Twelfth row 1630 indicates that exemplary WT 12 is experiencing widely varying channel conditions, and the DCCH reporting format being used include an SNR report that has a wide reporting range. Thirteenth row 1632 indicates that exemplary WT 13 is using a base station experiencing high system loading, and the DCCH reporting format being used has less segments allocated to WT per time interval to free up resources for the other wireless terminals. Fourteenth row 1634 indicates that exemplary WT 14 has high QoS requirements, and the DCCH reporting format being used provides for additional opportunities for traffic requests. Fifteenth row 1636 indicates that exemplary WT 15 has just recently accessed the base station, and the DCCH reporting format being used is a default format.
The exemplary dedicated control channel is subdivided into 31 logical tones (uplink tone index 811706, uplink tone index 821708, . . . , uplink tone index 1111710). Each logical uplink tone (81, . . . , 111) in the logical uplink frequency structure corresponds to a logical tone indexed with respect to the DCCH channel (0, . . . , 30).
For each tone in the dedicated control channel there are 40 segments in the beaconslot corresponding to forty columns (1712, 1714, 1716, 1718, 1720, 1722, . . . , 1724). The segment structure repeats on a beaconslot basis. For a given tone in the dedicated control channel there are 40 segments corresponding to a beaconslot 1728; each of the eight superslots of the beaconslot includes 5 successive segments for the given tone. For example, for first superslot 1726 of beaconslot 1728, corresponding to tone 0 of the DCCH, there are five indexed segments (segment [0] [0], segment [0] [1], segment [0][2], segment [0][3], segment [0][4]). Similarly, for first superslot 1726 of beaconslot 1728, corresponding to tone 1 of the DCCH, there are five indexed segments (segment [1][0], segment [1][1], segment [1][2], segment [1][3], segment [1][4]). Similarly, for first superslot 1726 of beaconslot 1728, corresponding to tone 30 of the DCCH, there are five indexed segments (segment [30][0], segment [30][1], segment [30][2], segment [30][3], segment [30][4]).
In this example each segment, e.g., segment [0][0], comprises one tone for 3 successive half-slots, e.g., representing an allocated uplink air link resource of 21 OFDM tone-symbols. In some embodiments, logical uplink tones are hopped to physical tones in accordance with an uplink tone hopping sequence such that the physical tone associated with a logical tone may be different for successive half-slots, but remains constant during a given half-slot.
Each logical tone of the dedicated control channel may be assigned by the base station to a different wireless terminal using the base station as its current point of attachment. For example, logical tone (506, 508, . . . , 510) may be currently assigned to (WT A 1730, WT B 1732, . . . , WT N′ 1734), respectively.
Each uplink DCCH segment is used to transmit a set of Dedicated Control Channel Reports (DCRs). A list of exemplary DCRs is given in table 1800 of
Different wireless terminals may be using different control information reporting formats at the same time. In addition the same wireless terminal may use different control information reporting formats at different times.
In step 2104, the base station determines a set of control information reports to be received, said set of control information reports corresponding to a reporting format. Step 2104 includes sub-step 2106. In sub-step 2106, the base station selects between a plurality of predetermined reporting formats. Sub-step 2106 includes one or more of sub-step 2108, 2110, and 2112. In sub-step 2108, the base station selects the control information reporting format as a function of an application being executed, e.g., by said base station or said wireless terminal or a peer node in a communications session with said wireless terminal. In some embodiments, the application is one of a voice and a data application. In some such embodiments, a reporting format selected in response to a voice application includes a latency report or includes latency information embedded in a traffic channel request report, and a reporting format selected in response to a data application includes less frequent uplink request reports than a reporting format used for voice but more bits per uplink request on average than used for voice. For example, frequently scheduled 1 bit uplink request reports may be used in an exemplary reporting format tailored for a voice application, while less frequently scheduled 3 and/or 4 bit uplink traffic channel request reports may be used in an exemplary reporting format tailored for a data application. In sub-step 2110, the base station selects the control information reporting format as a function of at least one of: device capability information, channel condition information, system loading information, and user quality of service (QoS) information. In sub-step 2112, the base station selects the control information reporting format as a function of at least one of: a command signal or a request signal received from said wireless terminal.
In some embodiments, each of said plurality of predetermined reporting formats specifies a plurality of different types of reports and an ordering of said different types of reports. In some embodiments, the different reporting types includes at least two of a SNR report, a traffic request report, a power information report, an interference report, and a delay report, e.g., a latency report. In some embodiments, the reporting format specifies the control information to be communicated in the different types of reports, e.g., counts of frames of traffic backlog with defined quanitization, SNR level in dB with defined quantization, power gain level in dBs with defined quantization, etc.
Operation proceeds from step 2104 to step 2114. In step 2114, the base station receives signals, e.g., dedicated control channel segment OFDM signals, conveying said determined set of reports. Then, in step 2116, the base station performs a demodulation and decoding operation on said received signals to generate sets of ordered information bits, each set of ordered information bits corresponding to a communications segment. Step 2116 includes sub-step 2118. In sub-step 2118, the base station uses a predetermined decoding and demodulation scheme corresponding to said reporting format, different decoding and demodulation schemes being used for at least some of said plurality of reporting formats. For example, in one exemplary embodiment one exemplary control information reporting format uses a demodulation and decoding scheme which obtains 6 information bits from 21 QPSK modulation symbols corresponding to a dedicated control channel communications segment; while a different exemplary control information format uses a demodulation and decoding scheme which obtains 8 information bits from 21 QPSK modulation symbols corresponding to a dedicated control channel communications segment. Operation proceeds from step 2116 to step 2120.
In step 2110, the base station maps the ordered bits of a segment to one or more control information reports in accordance with said reporting format. For example, corresponding to one exemplary control information reporting format, a first segment in a recurring structure may convey 6 ordered information bits, and bits 1-5 convey a 5 bit downlink SNR report, while bit 0 (LSb) conveys a 1 bit uplink traffic channel request report. Operation proceeds from step 2120 to step 2122.
In step 2122, the base station recovers information from said set of determined control information reports in accordance with said reporting format. For example, the bit pattern, e.g., 01110, of a received SNR report may report a pilot channel SNR measurement value, e.g., 2 dB.
Operation proceeds from step 2122 to step 2104, where the base station determines another set of control information reports to be received by the wireless terminal assuming the wireless terminal is still allocated a dedicated control channel by the base station.
In some embodiments, the received signals, e.g., dedicated control channel segment signals, from multiple wireless terminal using the base station are received concurrently, and the control information reporting format for at least some of the different wireless terminals, at at least some times is different. For example, a first wireless terminal communicating with the base station may be using a control information reporting format tailored for a voice application, and a second wireless terminal communicating with the base station may be using a control information reporting format tailored to delay insensitive data communications, e.g., file transfers.
Operation proceeds from step 2204 to step 2206, where the base station performs at least one of receiving and transmitting control information reporting format definition information from a wireless communications link. In some embodiments, a control information reporting format includes reporting format definition information providing definition mapping information to be included in said report to possible report values. In some embodiments, a control information reporting format includes reporting format definition information defining a reporting schedule according to which reports are to be transmitted. In some embodiments, a control information reporting format includes reporting format definition information defining a set of reports which are to be transmitted, e.g., by a wireless terminal to the base station, in accordance with the defined reporting schedule. In some embodiments, a control information reporting format includes reporting format definition information specifying a coding and modulation scheme to be applied to the set of reports.
Then, in step 2208, the base station checks at least one of device capability information, channel condition information, application information, quality of service information, system loading information, and the reception of a control information format switching command or request from said wireless terminal.
In step 2210, the base station decides how to proceed based on the result of the check of step 2208. If the result of the check indicates that the reporting format should be changed, operation proceeds to step 2212; otherwise operation proceeds to step 2214.
In step 2212, the base station switches the current reporting format to a new reporting format, e.g., said new reporting format in accordance with said control information reporting format definition information received or transmitted from a wireless communication link of step 2206. Operation proceeds from step 2212 to step 2214.
In step 2214, the base station recovers control information corresponding to a received control information report in accordance with the current reporting format. Operation proceeds from step 2214 to step 2208, where the base station perform another check.
In some embodiments, reporting format information, e.g., corresponding to customized control information reports, is communicated between a base station and a wireless terminal using the base station as its attachment point. In some embodiments, reporting format information corresponding to a wireless terminal is communicated to and/or stored at a centralized server and/or a home agent node. In some such embodiments, state information corresponding to a control information reporting format, for a wireless terminal is stored, e.g., in a centralized server, home agent node, and/or base station. In some embodiments such stored information can, and sometimes is, retrieved and transferred to a new base station, e.g., as part of a handoff process and/or initialization process when attaching to a new base station.
While described in the context of an OFDM system, the methods and apparatus of various embodiments, are applicable to a wide range of communications systems including many non-OFDM and/or non-cellular systems.
In various embodiments nodes described herein are implemented using one or more modules to perform the steps corresponding to one or more methods, for example, signal processing, beacon generation, beacon detection, beacon measuring, connection comparisons, connection implementations. In some embodiments various features are implemented using modules. Such modules may be implemented using software, hardware or a combination of software and hardware. Many of the above described methods or method steps can be implemented using machine executable instructions, such as software, included in a machine readable medium such as a memory device, e.g., RAM, floppy disk, etc. to control a machine, e.g., general purpose computer with or without additional hardware, to implement all or portions of the above described methods, e.g., in one or more nodes. Accordingly, among other things, various embodiments are directed to a machine-readable medium including machine executable instructions for causing a machine, e.g., processor and associated hardware, to perform one or more of the steps of the above-described method(s).
Numerous additional variations on the methods and apparatus described above will be apparent to those skilled in the art in view of the above descriptions. Such variations are to be considered within scope. The methods and apparatus of various embodiments may be, and in various embodiments are, used with CDMA, orthogonal frequency division multiplexing (OFDM), and/or various other types of communications techniques which may be used to provide wireless communications links between access nodes and mobile nodes. In some embodiments the access nodes are implemented as base stations which establish communications links with mobile nodes using OFDM and/or CDMA. In various embodiments the mobile nodes are implemented as notebook computers, personal data assistants (PDAs), or other portable devices including receiver/transmitter circuits and logic and/or routines, for implementing the methods of various embodiments.
The present application claims the benefit of U.S. Provisional Patent Application Ser. No. 60/752,973, filed on Dec. 22, 2005, titled “COMMUNICATIONS METHODS AND APPARATUS”, and is a continuation in part of U.S. Utility patent application Ser. No. 11/333,792, filed on Jan. 17, 2006, titled “METHODS AND APPARATUS OF IMPLEMENTING AND/OR USING A DEDICATED CONTROL CHANNEL” each of which is hereby expressly incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
4631720 | Koeck | Dec 1986 | A |
4660196 | Gray et al. | Apr 1987 | A |
4679244 | Kawasaki et al. | Jul 1987 | A |
4833701 | Comroe et al. | May 1989 | A |
5128938 | Borras | Jul 1992 | A |
5203013 | Breeden et al. | Apr 1993 | A |
5387905 | Grube et al. | Feb 1995 | A |
5434848 | Chimento, Jr. et al. | Jul 1995 | A |
5461645 | Ishii | Oct 1995 | A |
5465389 | Agrawal et al. | Nov 1995 | A |
5506865 | Weaver, Jr. | Apr 1996 | A |
5537414 | Takiyasu et al. | Jul 1996 | A |
5579307 | Richetta et al. | Nov 1996 | A |
5732328 | Mitra et al. | Mar 1998 | A |
5835847 | Gilmore et al. | Nov 1998 | A |
5867478 | Baum et al. | Feb 1999 | A |
5898925 | Honkasalo et al. | Apr 1999 | A |
5914950 | Tiedemann et al. | Jun 1999 | A |
5915221 | Sawyer et al. | Jun 1999 | A |
5923650 | Chen et al. | Jul 1999 | A |
5933421 | Alamouti et al. | Aug 1999 | A |
5940771 | Gollnick et al. | Aug 1999 | A |
5966657 | Sporre | Oct 1999 | A |
5966662 | Murto | Oct 1999 | A |
5978657 | Suzuki | Nov 1999 | A |
5999534 | Kim | Dec 1999 | A |
6002676 | Fleming | Dec 1999 | A |
6004276 | Wright et al. | Dec 1999 | A |
6026081 | Hamabe | Feb 2000 | A |
6028842 | Chapman et al. | Feb 2000 | A |
6028843 | Delp et al. | Feb 2000 | A |
6035000 | Bingham | Mar 2000 | A |
6069871 | Sharma et al. | May 2000 | A |
6070072 | Dorenbosch et al. | May 2000 | A |
6073025 | Chheda et al. | Jun 2000 | A |
6075025 | Bishop et al. | Jun 2000 | A |
6122270 | Whinnett et al. | Sep 2000 | A |
6128506 | Knutsson et al. | Oct 2000 | A |
6131016 | Greenstein et al. | Oct 2000 | A |
6141565 | Feuerstein et al. | Oct 2000 | A |
6169896 | Sant et al. | Jan 2001 | B1 |
6173005 | Kotzin et al. | Jan 2001 | B1 |
6181948 | Kondo | Jan 2001 | B1 |
6201793 | Chen et al. | Mar 2001 | B1 |
6205129 | Esteves et al. | Mar 2001 | B1 |
6215791 | Kim | Apr 2001 | B1 |
6236646 | Beming et al. | May 2001 | B1 |
6256478 | Allen et al. | Jul 2001 | B1 |
6259927 | Butovitsch et al. | Jul 2001 | B1 |
6263392 | McCauley | Jul 2001 | B1 |
6298233 | Souissi et al. | Oct 2001 | B1 |
6308080 | Burt et al. | Oct 2001 | B1 |
6310857 | Duffield et al. | Oct 2001 | B1 |
6311065 | Ushiki et al. | Oct 2001 | B1 |
6374085 | Saints et al. | Apr 2002 | B1 |
6377583 | Lyles et al. | Apr 2002 | B1 |
6377955 | Hartmann et al. | Apr 2002 | B1 |
6405047 | Moon | Jun 2002 | B1 |
6414946 | Satou et al. | Jul 2002 | B1 |
6445917 | Bark et al. | Sep 2002 | B1 |
6453151 | Kiang et al. | Sep 2002 | B1 |
6493539 | Falco et al. | Dec 2002 | B1 |
6526281 | Gorsuch et al. | Feb 2003 | B1 |
6538986 | Isaksson et al. | Mar 2003 | B2 |
6545999 | Sugita | Apr 2003 | B1 |
6553336 | Johnson et al. | Apr 2003 | B1 |
6590890 | Stolyar et al. | Jul 2003 | B1 |
6597914 | Silventoinen et al. | Jul 2003 | B1 |
6600903 | Lilja et al. | Jul 2003 | B1 |
6609007 | Eibling et al. | Aug 2003 | B1 |
6621808 | Sadri | Sep 2003 | B1 |
6625133 | Balachandran et al. | Sep 2003 | B1 |
6662024 | Walton et al. | Dec 2003 | B2 |
6671512 | Laakso | Dec 2003 | B2 |
6680909 | Bansal et al. | Jan 2004 | B1 |
6697417 | Fernandez-Corbaton et al. | Feb 2004 | B2 |
6710651 | Forrester | Mar 2004 | B2 |
6742020 | Dimitroff et al. | May 2004 | B1 |
6745003 | Maca et al. | Jun 2004 | B1 |
6745044 | Holtzman et al. | Jun 2004 | B1 |
6751187 | Walton et al. | Jun 2004 | B2 |
6771934 | Demers et al. | Aug 2004 | B2 |
6788963 | Laroia et al. | Sep 2004 | B2 |
6798761 | Cain et al. | Sep 2004 | B2 |
6804289 | Takahashi | Oct 2004 | B2 |
6804521 | Tong et al. | Oct 2004 | B2 |
6816476 | Kim et al. | Nov 2004 | B2 |
6836673 | Trott | Dec 2004 | B1 |
6865168 | Sekine | Mar 2005 | B1 |
6889056 | Shibutani | May 2005 | B2 |
6892071 | Park et al. | May 2005 | B2 |
6895005 | Malin et al. | May 2005 | B1 |
6895364 | Banfer | May 2005 | B2 |
6901268 | Chang | May 2005 | B2 |
6901270 | Beach | May 2005 | B1 |
6904016 | Kuo et al. | Jun 2005 | B2 |
6912405 | Hiramatsu et al. | Jun 2005 | B2 |
6917607 | Yeom et al. | Jul 2005 | B1 |
6940827 | Li et al. | Sep 2005 | B2 |
6954643 | Petrus | Oct 2005 | B2 |
6957072 | Kangras et al. | Oct 2005 | B2 |
6967937 | Gormley | Nov 2005 | B1 |
6968156 | Sugaya et al. | Nov 2005 | B2 |
7006841 | Momogioudis et al. | Feb 2006 | B2 |
7024460 | Koopmas et al. | Apr 2006 | B2 |
7027782 | Moon et al. | Apr 2006 | B2 |
7031983 | Israni et al. | Apr 2006 | B2 |
7034254 | Grabowski et al. | Apr 2006 | B2 |
7039029 | Lee et al. | May 2006 | B2 |
7043254 | Chawla et al. | May 2006 | B2 |
7047009 | Laroia et al. | May 2006 | B2 |
7054643 | Trossen et al. | May 2006 | B2 |
7061885 | Kurtz | Jun 2006 | B2 |
7092672 | Pekonen et al. | Aug 2006 | B1 |
7120123 | Quigley et al. | Oct 2006 | B1 |
7120448 | Brouwer | Oct 2006 | B2 |
7123910 | Lucidarme et al. | Oct 2006 | B2 |
7139536 | Chiu | Nov 2006 | B2 |
7142548 | Fong et al. | Nov 2006 | B2 |
7146172 | Li et al. | Dec 2006 | B2 |
7158796 | Tiedemann, Jr. et al. | Jan 2007 | B2 |
7161909 | Sharma | Jan 2007 | B2 |
7162203 | Brunner | Jan 2007 | B1 |
7164883 | Rappaport et al. | Jan 2007 | B2 |
7197025 | Chuah | Mar 2007 | B2 |
7203493 | Fujii et al. | Apr 2007 | B2 |
7212821 | Laroia et al. | May 2007 | B2 |
7218948 | Laroia et al. | May 2007 | B2 |
7245935 | Lin | Jul 2007 | B2 |
7260054 | Olszewski | Aug 2007 | B2 |
7269406 | Qi | Sep 2007 | B2 |
7277709 | Vadgama | Oct 2007 | B2 |
7277737 | Vollmer et al. | Oct 2007 | B1 |
7280814 | Austin et al. | Oct 2007 | B2 |
7283559 | Cho et al. | Oct 2007 | B2 |
7283836 | Hwang et al. | Oct 2007 | B2 |
7299277 | Moran et al. | Nov 2007 | B1 |
7317921 | Mueckenheim et al. | Jan 2008 | B2 |
7319680 | Cho | Jan 2008 | B2 |
7321563 | Kim et al. | Jan 2008 | B2 |
7340267 | Budka et al. | Mar 2008 | B2 |
7349667 | Magee et al. | Mar 2008 | B2 |
7356635 | Woodings et al. | Apr 2008 | B2 |
7362702 | Terrell et al. | Apr 2008 | B2 |
7382755 | Dugad et al. | Jun 2008 | B2 |
7395058 | Kalofonos et al. | Jul 2008 | B1 |
7397803 | Love et al. | Jul 2008 | B2 |
7400901 | Kostic et al. | Jul 2008 | B2 |
7412265 | Chen et al. | Aug 2008 | B2 |
7418260 | Lucidarme | Aug 2008 | B2 |
7420939 | Laroia et al. | Sep 2008 | B2 |
7430206 | Terry et al. | Sep 2008 | B2 |
7430207 | Wu et al. | Sep 2008 | B2 |
7430420 | Derakhshan et al. | Sep 2008 | B2 |
7447148 | Gao et al. | Nov 2008 | B2 |
7463577 | Sudo et al. | Dec 2008 | B2 |
7486620 | Seol | Feb 2009 | B2 |
7486638 | Ofuji et al. | Feb 2009 | B2 |
7502614 | Uchida et al. | Mar 2009 | B2 |
7508792 | Petrovic et al. | Mar 2009 | B2 |
7510828 | Lynn et al. | Mar 2009 | B2 |
7512076 | Kwon et al. | Mar 2009 | B2 |
7512185 | Sharon et al. | Mar 2009 | B2 |
7519013 | Destino et al. | Apr 2009 | B2 |
7519033 | Soomro | Apr 2009 | B2 |
7522544 | Cheng et al. | Apr 2009 | B2 |
7525971 | Carroll et al. | Apr 2009 | B2 |
7526091 | Jeong et al. | Apr 2009 | B2 |
7558235 | Lester et al. | Jul 2009 | B2 |
7558572 | Anigstein | Jul 2009 | B2 |
7561893 | Moulsley et al. | Jul 2009 | B2 |
7668573 | Laroia et al. | Feb 2010 | B2 |
7743284 | Taylor et al. | Jun 2010 | B1 |
8040831 | Kurtz et al. | Oct 2011 | B2 |
8325621 | Simonsson et al. | Dec 2012 | B2 |
8437251 | Das et al. | May 2013 | B2 |
8503938 | Laroia et al. | Aug 2013 | B2 |
8514692 | Laroia et al. | Aug 2013 | B2 |
8514771 | Das et al. | Aug 2013 | B2 |
20010007552 | Schiff et al. | Jul 2001 | A1 |
20010036181 | Rogers | Nov 2001 | A1 |
20010046878 | Chang | Nov 2001 | A1 |
20010055293 | Parsa et al. | Dec 2001 | A1 |
20020012326 | Chang | Jan 2002 | A1 |
20020031105 | Zeira et al. | Mar 2002 | A1 |
20020037729 | Kitazawa et al. | Mar 2002 | A1 |
20020049040 | Sugaya et al. | Apr 2002 | A1 |
20020075835 | Krishnakumar et al. | Jun 2002 | A1 |
20020077140 | Monogioudis et al. | Jun 2002 | A1 |
20020080967 | Abdo et al. | Jun 2002 | A1 |
20020082011 | Fujii et al. | Jun 2002 | A1 |
20020085516 | Bridgelall | Jul 2002 | A1 |
20020093953 | Naim et al. | Jul 2002 | A1 |
20020107028 | Rantalainen et al. | Aug 2002 | A1 |
20020122431 | Cho et al. | Sep 2002 | A1 |
20020136195 | Kurtz | Sep 2002 | A1 |
20020142788 | Chawla et al. | Oct 2002 | A1 |
20020143858 | Teague et al. | Oct 2002 | A1 |
20020147017 | Li et al. | Oct 2002 | A1 |
20020177452 | Ruutu et al. | Nov 2002 | A1 |
20020186678 | Averbuch et al. | Dec 2002 | A1 |
20030003921 | Laakso | Jan 2003 | A1 |
20030007498 | Angle et al. | Jan 2003 | A1 |
20030012212 | Earnshaw et al. | Jan 2003 | A1 |
20030027587 | Proctor, Jr. | Feb 2003 | A1 |
20030028606 | Koopmans et al. | Feb 2003 | A1 |
20030064737 | Eriksson et al. | Apr 2003 | A1 |
20030078067 | Kim et al. | Apr 2003 | A1 |
20030095519 | Kuo et al. | May 2003 | A1 |
20030100269 | Lehtinen et al. | May 2003 | A1 |
20030114180 | Black et al. | Jun 2003 | A1 |
20030123396 | Seo et al. | Jul 2003 | A1 |
20030123410 | Youm | Jul 2003 | A1 |
20030139197 | Kostic et al. | Jul 2003 | A1 |
20030144042 | Weinfield et al. | Jul 2003 | A1 |
20030157899 | Trossen et al. | Aug 2003 | A1 |
20030161285 | Tiedemann et al. | Aug 2003 | A1 |
20030169705 | Knisely et al. | Sep 2003 | A1 |
20030185224 | Ramanan et al. | Oct 2003 | A1 |
20030185285 | Talwar | Oct 2003 | A1 |
20030193915 | Lee et al. | Oct 2003 | A1 |
20030198204 | Taneja et al. | Oct 2003 | A1 |
20030198206 | Cain et al. | Oct 2003 | A1 |
20030206541 | Yun et al. | Nov 2003 | A1 |
20030207691 | Chen | Nov 2003 | A1 |
20030207693 | Roderique | Nov 2003 | A1 |
20030214906 | Hu et al. | Nov 2003 | A1 |
20030214928 | Chuah | Nov 2003 | A1 |
20030223354 | Olszewski | Dec 2003 | A1 |
20040001429 | Ma et al. | Jan 2004 | A1 |
20040004954 | Terry et al. | Jan 2004 | A1 |
20040013103 | Zhang et al. | Jan 2004 | A1 |
20040057402 | Ramos et al. | Mar 2004 | A1 |
20040062206 | Soong et al. | Apr 2004 | A1 |
20040081089 | Ayyagari | Apr 2004 | A1 |
20040082344 | Moilanen et al. | Apr 2004 | A1 |
20040085936 | Gopalakrishnan et al. | May 2004 | A1 |
20040091026 | Nakayama | May 2004 | A1 |
20040111640 | Baum | Jun 2004 | A1 |
20040120411 | Walton et al. | Jun 2004 | A1 |
20040125776 | Haugli et al. | Jul 2004 | A1 |
20040127226 | Dugad et al. | Jul 2004 | A1 |
20040127266 | Aagaard et al. | Jul 2004 | A1 |
20040131007 | Smee et al. | Jul 2004 | A1 |
20040141466 | Kim et al. | Jul 2004 | A1 |
20040147262 | Lescuyer et al. | Jul 2004 | A1 |
20040147276 | Gholmieh et al. | Jul 2004 | A1 |
20040160922 | Nanda et al. | Aug 2004 | A1 |
20040162097 | Vijayan et al. | Aug 2004 | A1 |
20040166869 | Laroia et al. | Aug 2004 | A1 |
20040166886 | Laroia et al. | Aug 2004 | A1 |
20040166887 | Laroia et al. | Aug 2004 | A1 |
20040171401 | Balachandran et al. | Sep 2004 | A1 |
20040180658 | Uchida et al. | Sep 2004 | A1 |
20040184410 | Park | Sep 2004 | A1 |
20040192371 | Zhao et al. | Sep 2004 | A1 |
20040196802 | Bae et al. | Oct 2004 | A1 |
20040203717 | Wingrowicz et al. | Oct 2004 | A1 |
20040203981 | Budka et al. | Oct 2004 | A1 |
20040218617 | Sagfors | Nov 2004 | A1 |
20040223455 | Fong et al. | Nov 2004 | A1 |
20040224677 | Kuchibhotla et al. | Nov 2004 | A1 |
20040228313 | Cheng et al. | Nov 2004 | A1 |
20040233838 | Sudo et al. | Nov 2004 | A1 |
20040235510 | Elicegui et al. | Nov 2004 | A1 |
20040248518 | Kashiwase | Dec 2004 | A1 |
20040248568 | Lucidarme | Dec 2004 | A1 |
20040252662 | Cho | Dec 2004 | A1 |
20040253996 | Chen et al. | Dec 2004 | A1 |
20040258040 | Joshi et al. | Dec 2004 | A1 |
20040259546 | Balachandran et al. | Dec 2004 | A1 |
20040264414 | Dorenbosch | Dec 2004 | A1 |
20040266474 | Petrus | Dec 2004 | A1 |
20050003847 | Love et al. | Jan 2005 | A1 |
20050008892 | Yamamoto et al. | Jan 2005 | A1 |
20050037775 | Moeglein et al. | Feb 2005 | A1 |
20050047344 | Seol | Mar 2005 | A1 |
20050047393 | Liu | Mar 2005 | A1 |
20050047416 | Heo et al. | Mar 2005 | A1 |
20050053099 | Spear et al. | Mar 2005 | A1 |
20050064821 | Hedberg et al. | Mar 2005 | A1 |
20050068922 | Jalali | Mar 2005 | A1 |
20050085197 | Laroia et al. | Apr 2005 | A1 |
20050099987 | Lester et al. | May 2005 | A1 |
20050111361 | Hosein | May 2005 | A1 |
20050111462 | Walton et al. | May 2005 | A1 |
20050118993 | Roux et al. | Jun 2005 | A1 |
20050122900 | Tuulos et al. | Jun 2005 | A1 |
20050128999 | Kwon et al. | Jun 2005 | A1 |
20050135320 | Tiedemann, Jr. et al. | Jun 2005 | A1 |
20050136937 | Qian et al. | Jun 2005 | A1 |
20050143084 | Cheng et al. | Jun 2005 | A1 |
20050143114 | Moulsley et al. | Jun 2005 | A1 |
20050152320 | Marinier et al. | Jul 2005 | A1 |
20050157803 | Kim et al. | Jul 2005 | A1 |
20050157876 | Jeong et al. | Jul 2005 | A1 |
20050170782 | Rong et al. | Aug 2005 | A1 |
20050181732 | Kang et al. | Aug 2005 | A1 |
20050185632 | Draves, Jr. et al. | Aug 2005 | A1 |
20050195765 | Sharon et al. | Sep 2005 | A1 |
20050201331 | Gaal et al. | Sep 2005 | A1 |
20050201353 | Lee et al. | Sep 2005 | A1 |
20050207335 | Schmidl et al. | Sep 2005 | A1 |
20050207359 | Hwang et al. | Sep 2005 | A1 |
20050232154 | Bang et al. | Oct 2005 | A1 |
20050243938 | Armstrong et al. | Nov 2005 | A1 |
20050249118 | Terry et al. | Nov 2005 | A1 |
20050250509 | Choksi | Nov 2005 | A1 |
20050250510 | Kaikkonen et al. | Nov 2005 | A1 |
20050250529 | Funnell et al. | Nov 2005 | A1 |
20050255873 | Zhang et al. | Nov 2005 | A1 |
20050259662 | Kim et al. | Nov 2005 | A1 |
20050265301 | Heo et al. | Dec 2005 | A1 |
20050281232 | Kim et al. | Dec 2005 | A1 |
20050281278 | Black et al. | Dec 2005 | A1 |
20050289256 | Cudak et al. | Dec 2005 | A1 |
20060003767 | Kim et al. | Jan 2006 | A1 |
20060015357 | Cagan | Jan 2006 | A1 |
20060018284 | Rudolf et al. | Jan 2006 | A1 |
20060019694 | Sutivong et al. | Jan 2006 | A1 |
20060034174 | Nishibayashi et al. | Feb 2006 | A1 |
20060040696 | Lin | Feb 2006 | A1 |
20060045013 | Vannithamby et al. | Mar 2006 | A1 |
20060056346 | Vadgama et al. | Mar 2006 | A1 |
20060073836 | Laroia et al. | Apr 2006 | A1 |
20060079257 | Iochi et al. | Apr 2006 | A1 |
20060079267 | Kim et al. | Apr 2006 | A1 |
20060083161 | Laroia et al. | Apr 2006 | A1 |
20060089104 | Kaikkonen et al. | Apr 2006 | A1 |
20060092881 | Laroia et al. | May 2006 | A1 |
20060104240 | Sebire et al. | May 2006 | A1 |
20060120470 | Hwang et al. | Jun 2006 | A1 |
20060126497 | Na et al. | Jun 2006 | A1 |
20060128410 | Derryberry et al. | Jun 2006 | A1 |
20060128412 | Mantha et al. | Jun 2006 | A1 |
20060133346 | Chheda et al. | Jun 2006 | A1 |
20060135193 | Ratasuk et al. | Jun 2006 | A1 |
20060140154 | Kwak et al. | Jun 2006 | A1 |
20060142032 | Derakhshan et al. | Jun 2006 | A1 |
20060164981 | Olsson et al. | Jul 2006 | A1 |
20060165029 | Melpignano et al. | Jul 2006 | A1 |
20060176807 | Wu et al. | Aug 2006 | A1 |
20060182022 | Abedi | Aug 2006 | A1 |
20060203765 | Laroia et al. | Sep 2006 | A1 |
20060205356 | Laroia et al. | Sep 2006 | A1 |
20060205396 | Laroia et al. | Sep 2006 | A1 |
20060215604 | Mueckenheim et al. | Sep 2006 | A1 |
20060234722 | Hanebeck et al. | Oct 2006 | A1 |
20060245452 | Frederiksen et al. | Nov 2006 | A1 |
20060246916 | Cheng et al. | Nov 2006 | A1 |
20060270399 | Qi | Nov 2006 | A1 |
20060285481 | Lane et al. | Dec 2006 | A1 |
20060287743 | Sampath et al. | Dec 2006 | A1 |
20070002757 | Soomro et al. | Jan 2007 | A1 |
20070002806 | Soomro | Jan 2007 | A1 |
20070004437 | Harada et al. | Jan 2007 | A1 |
20070010226 | Laroia et al. | Jan 2007 | A1 |
20070015541 | Dominique et al. | Jan 2007 | A1 |
20070026803 | Malm | Feb 2007 | A1 |
20070026808 | Love et al. | Feb 2007 | A1 |
20070026810 | Love et al. | Feb 2007 | A1 |
20070030828 | Vimpari et al. | Feb 2007 | A1 |
20070036116 | Eiger et al. | Feb 2007 | A1 |
20070054624 | Kashiwagi | Mar 2007 | A1 |
20070057952 | Swedberg et al. | Mar 2007 | A1 |
20070066273 | Laroia et al. | Mar 2007 | A1 |
20070070894 | Wang et al. | Mar 2007 | A1 |
20070081492 | Petrovic et al. | Apr 2007 | A1 |
20070081498 | Niwano | Apr 2007 | A1 |
20070104128 | Laroia et al. | May 2007 | A1 |
20070104164 | Laroia et al. | May 2007 | A1 |
20070109999 | Brunner | May 2007 | A1 |
20070133412 | Hutter et al. | Jun 2007 | A1 |
20070140168 | Laroia et al. | Jun 2007 | A1 |
20070140179 | Zhang et al. | Jun 2007 | A1 |
20070141994 | Cheng | Jun 2007 | A1 |
20070147283 | Laroia et al. | Jun 2007 | A1 |
20070147377 | Laroia et al. | Jun 2007 | A1 |
20070149126 | Rangan et al. | Jun 2007 | A1 |
20070149128 | Das et al. | Jun 2007 | A1 |
20070149129 | Das et al. | Jun 2007 | A1 |
20070149132 | Li et al. | Jun 2007 | A1 |
20070149137 | Richardson et al. | Jun 2007 | A1 |
20070149138 | Das | Jun 2007 | A1 |
20070149194 | Das et al. | Jun 2007 | A1 |
20070149227 | Parizhsky et al. | Jun 2007 | A1 |
20070149228 | Das | Jun 2007 | A1 |
20070149238 | Das et al. | Jun 2007 | A1 |
20070159969 | Das et al. | Jul 2007 | A1 |
20070168326 | Das et al. | Jul 2007 | A1 |
20070169326 | Das et al. | Jul 2007 | A1 |
20070173208 | Nishio et al. | Jul 2007 | A1 |
20070183308 | Korobokov et al. | Aug 2007 | A1 |
20070213087 | Laroia et al. | Sep 2007 | A1 |
20070243882 | Edge | Oct 2007 | A1 |
20070249287 | Das et al. | Oct 2007 | A1 |
20070249360 | Das et al. | Oct 2007 | A1 |
20070253355 | Hande et al. | Nov 2007 | A1 |
20070253357 | Das et al. | Nov 2007 | A1 |
20070253358 | Das et al. | Nov 2007 | A1 |
20070253385 | Li et al. | Nov 2007 | A1 |
20070258365 | Das et al. | Nov 2007 | A1 |
20080031368 | Lindoff et al. | Feb 2008 | A1 |
20080037474 | Niwano | Feb 2008 | A1 |
20080051086 | Etemad et al. | Feb 2008 | A2 |
20080057969 | Agami et al. | Mar 2008 | A1 |
20080076462 | Iochi et al. | Mar 2008 | A1 |
20080144521 | Soomro et al. | Jun 2008 | A1 |
20080159235 | Son et al. | Jul 2008 | A1 |
20080167047 | Abedi | Jul 2008 | A1 |
20090004983 | Darabi | Jan 2009 | A1 |
20090034455 | Lee et al. | Feb 2009 | A1 |
20090103507 | Gu et al. | Apr 2009 | A1 |
20090106507 | Gu et al. | Apr 2009 | A1 |
20090303900 | Cho et al. | Dec 2009 | A1 |
20100220626 | Das et al. | Sep 2010 | A1 |
20110090812 | Aoyama | Apr 2011 | A1 |
20110149789 | Edge | Jun 2011 | A1 |
20120140756 | Rudolf et al. | Jun 2012 | A1 |
20130230027 | Das et al. | Sep 2013 | A1 |
20130242888 | Das et al. | Sep 2013 | A1 |
20150043374 | Hande et al. | Feb 2015 | A1 |
Number | Date | Country |
---|---|---|
1159262 | Sep 1997 | CN |
1159286 | Sep 1997 | CN |
1265792 | Sep 2000 | CN |
1286006 | Feb 2001 | CN |
1286821 | Mar 2001 | CN |
1286832 | Mar 2001 | CN |
1316140 | Oct 2001 | CN |
1335036 | Feb 2002 | CN |
1338877 | Mar 2002 | CN |
1507708 | Jun 2004 | CN |
1545252 | Nov 2004 | CN |
1604685 | Apr 2005 | CN |
10162564 | Jul 2003 | DE |
1037419 | Sep 2000 | EP |
1037491 | Sep 2000 | EP |
054 518 | Nov 2000 | EP |
1089500 | Apr 2001 | EP |
1179962 | Feb 2002 | EP |
1180881 | Feb 2002 | EP |
1180907 | Feb 2002 | EP |
1221273 | Jul 2002 | EP |
1233637 | Aug 2002 | EP |
1377100 | Jan 2004 | EP |
1493284 | Jan 2005 | EP |
1511245 | Mar 2005 | EP |
1564953 | Aug 2005 | EP |
1571762 | Sep 2005 | EP |
594 260 | Nov 2005 | EP |
1758276 | Feb 2007 | EP |
1841259 | Oct 2007 | EP |
2340693 | Feb 2000 | GB |
08008806 | Jan 1996 | JP |
8503591 | Apr 1996 | JP |
9275582 | Oct 1997 | JP |
09307939 | Nov 1997 | JP |
10022975 | Jan 1998 | JP |
10173585 | Jun 1998 | JP |
11122167 | Apr 1999 | JP |
2000049689 | Feb 2000 | JP |
2001007761 | Jan 2001 | JP |
2001016152 | Jan 2001 | JP |
2001510974 | Aug 2001 | JP |
2001512921 | Aug 2001 | JP |
2001251680 | Sep 2001 | JP |
2001523901 | Nov 2001 | JP |
2001525135 | Dec 2001 | JP |
2002077992 | Mar 2002 | JP |
2002111627 | Apr 2002 | JP |
2002262330 | Sep 2002 | JP |
2003018641 | Jan 2003 | JP |
2003500911 | Jan 2003 | JP |
2003509983 | Mar 2003 | JP |
2003510887 | Mar 2003 | JP |
2003520153 | Jul 2003 | JP |
2003244161 | Aug 2003 | JP |
2004153585 | May 2004 | JP |
2004297284 | Oct 2004 | JP |
2004533731 | Nov 2004 | JP |
2004350052 | Dec 2004 | JP |
2005073276 | Mar 2005 | JP |
2005130482 | May 2005 | JP |
2005136773 | May 2005 | JP |
2005142965 | Jun 2005 | JP |
2005525730 | Aug 2005 | JP |
2005526417 | Sep 2005 | JP |
2005333671 | Dec 2005 | JP |
2006514735 | May 2006 | JP |
06268574 | Oct 2006 | JP |
2006526323 | Nov 2006 | JP |
2007503156 | Feb 2007 | JP |
2007509531 | Apr 2007 | JP |
2007514364 | May 2007 | JP |
2007514378 | May 2007 | JP |
2007522692 | Aug 2007 | JP |
2007525044 | Aug 2007 | JP |
2007525045 | Aug 2007 | JP |
2006518578 | Mar 2011 | JP |
2006524966 | May 2011 | JP |
1019990084525 | Dec 1999 | KR |
20010014223 | Feb 2001 | KR |
20040018526 | Mar 2004 | KR |
20040053859 | Jun 2004 | KR |
20040084599 | Oct 2004 | KR |
20040110044 | Dec 2004 | KR |
20050021083 | Mar 2005 | KR |
20050023187 | Mar 2005 | KR |
20050039376 | Apr 2005 | KR |
1020050099633 | Oct 2005 | KR |
1020050121274 | Dec 2005 | KR |
20060012282 | Feb 2006 | KR |
2149518 | May 2000 | RU |
2181529 | Apr 2002 | RU |
2188506 | Aug 2002 | RU |
2202154 | Apr 2003 | RU |
200423642 | Nov 2004 | TW |
9408432 | Apr 1994 | WO |
WO9623371 | Aug 1996 | WO |
WO9845967 | Oct 1998 | WO |
WO9856120 | Dec 1998 | WO |
9907090 | Feb 1999 | WO |
9909779 | Feb 1999 | WO |
WO9913600 | Mar 1999 | WO |
WO9959254 | Nov 1999 | WO |
WO0101610 | Jan 2001 | WO |
0122759 | Mar 2001 | WO |
WO0135548 | May 2001 | WO |
0142047 | Jun 2001 | WO |
WO0182504 | Nov 2001 | WO |
0199291 | Dec 2001 | WO |
WO0232183 | Apr 2002 | WO |
WO0233841 | Apr 2002 | WO |
WO0239760 | May 2002 | WO |
WO0249305 | Jun 2002 | WO |
WO02073831 | Sep 2002 | WO |
WO02101941 | Dec 2002 | WO |
WO02104058 | Dec 2002 | WO |
WO03094544 | Nov 2003 | WO |
WO03105498 | Dec 2003 | WO |
2004031918 | Apr 2004 | WO |
2004077685 | Sep 2004 | WO |
2004077728 | Sep 2004 | WO |
2004084503 | Sep 2004 | WO |
WO2004084452 | Sep 2004 | WO |
2004100450 | Nov 2004 | WO |
2004110081 | Dec 2004 | WO |
WO2004105420 | Dec 2004 | WO |
2005018115 | Feb 2005 | WO |
2005020490 | Mar 2005 | WO |
WO2005034438 | Apr 2005 | WO |
2005057812 | Jun 2005 | WO |
2005060132 | Jun 2005 | WO |
WO2005060271 | Jun 2005 | WO |
WO2005060277 | Jun 2005 | WO |
WO2005065056 | Jul 2005 | WO |
WO2005069519 | Jul 2005 | WO |
WO2005125049 | Dec 2005 | WO |
WO2006044718 | Apr 2006 | WO |
2006075293 | Jul 2006 | WO |
2007031956 | Mar 2007 | WO |
Entry |
---|
Hosein, et al., “Optimal Assignment of Mobile Station Serving Sector for the Forward Link of a Time-Shared Wireless Packet Data Channel,” Fifth IEE International Conference on 3G Mobile Communication Technologies (3G 2004), Oct. 18-20, 2004, pp. 654-658. |
Kwon, et al, “Quasi-Dedicated Access Scheme for Uplink Realtime Services in Future Wireless Communication Systems,” Vehicular Technology Conference, 2005. VTC 2005—Spring. 2005 IEEE 61st Stockholm, Sweden, Apr. 20-May 1, 2005; Piscataway, NJ, USA May 30, 2005, pp. 3117-3121. |
Majmundar, “Impact Mobile-Originated Short Message Service on the Digital Control Channel of TDMA Systems,” Vehicular Technology Conference, 2000. IEEE VTS Fall VTC 2000. 52nd Sep. 24-28, 2000, Piscataway, NJ, USA, IEEE, Sep. 24, 2000, pp. 1550-1555. |
International Search Report—PCT/US06/048674, International Search Authority—European Patent Office, Mar. 27, 2008. |
Gunnarson, F., et al., “Uplink Admission Control in WCDMA Based on Relative Load Estimates”, IEEE International Conference on Communications, vol. 1, pp. 3091-3095. |
Wada, “Study of an OFDM Cellular System Using a Single Band,” 2002 Communication Society Convention, Collection of Lecture Papers 1, Japan, IEEE, Aug. 20, 2002, p. 355, B-5-58. |
Written Opinion—PCT/US06/048674, International Search Authority—European Patent Office, Mar. 27, 2008. |
Hang Zhang et al, “Clean up for Closed-Loop MIMO in H-ARQ MAP IE”, IEEE P802.16e/D7 Broadband Wireless Access Working Group <http://ieee802.org/16>, pp. 1-6, Mar. 10, 2010. |
IEEE P802.16e/D5: “Draft IEEE Standard for Local and metropolitan area networks, Part 16: Air Interface for Fixed and Mobile Broadband Wireless Access Systems Amendment for Physical and Medium Access Control Layers for Combined Fixed and Mobile Operation in Licensed Bands”, pp. 1-356, Sep. 2004. |
IEEE P802.16e/D5: “Draft IEEE Standard for Local and metropolitan area networks, Part 16: Air Interface for Fixed and Mobile Broadband Wireless Access Systems Amendment for Physical and Medium Access Control Layers for Combined Fixed and Mobile Operation in Licensed Bands”, pp. 184-190, Sep. 2004. |
Translation of Office Action in Chinese application 200680047991.2 corresponding to U.S. Appl. No. 11/608,785, citing CN1604685 dated Dec. 31, 2010. |
Translation of Office Action in Japanese application 2008-535789 corresponding to U.S. Appl. No. 11/549,611, citing JP2003244161, JP200277992 and JP2001016152 dated Jan. 18, 2011. |
Translation of Office Action in Ukraine application 200508984 corresponding to U.S. Appl. No. 11/748,433, citing US20020160802, WO0232183, RU2181529, Feb. 20, 2004. |
Translation of Office Action in Ukraine Application 201010406 corresponding to U.S. Appl. No. 11/748,433, citing US5867478 ,US20010007552 ,US6035000 ,US5933421 ,WO02073831 ,WO02032183 ,RU2181529 and EP1377100 dated Feb. 22, 2011. |
Taiwan Search Report—TW095148226—TIPO—Aug. 19, 2013. |
3GPP TSG RAN2#45bis. “EDCH Buffer Status Reporting,” R2-050026, Sophia Antipolis, France, Jan. 10-14, 2005, URL: http://www.3gpp.org/ftp/tsg—ran/WG2—RL2/TSGR2—45bis/Dcs/R2-050026.zip. |
3GPP TSG-RAN WG2 meeting #48. “Scheduling Information Contents,” R2-051957, London, United Kingdom, Aug. 29, 2005, URL: http://3gpp.org/ftp/tsg—ran/WG2—RL2/TSGR2 48/Docments/R2-095517.zip. |
3GPP: ETSI TS 125 331 V6.3.0: Radio Resource Control (RRC) protocol specification (3GPP TS 25.331 version 6.3.0 Release 6), Sep. 1, 2004, pp. 49, 202-209, 220,221,406,579-585, 589, 930. |
Chang, Cheng-Ta: “Downlink Transmit Power Issues in a WCDMA Cellular System,”Dec. 14, 2004, p. 3, Fig. 1, Retrieved online: http://wintech.ee.nctu.edu.tw/handoff/MediaTek/Material/Wintech/1214/Downlink%20Tra nsmit%20Power%20Issues%20in%20a%20WCDMA%20Cellular%20System.pdf. |
Ericsson: Discussion on SIR Measurement, TSG-RAN Working Group 4 (Radio) meeting #18, R4-010895, Berlin, Germany, 3GPP TS 25.101 V3.7.0, Jul. 9, 2001, URL: http://www.3gpp.org/ftp/tsg—ran/WG4 Radio/TSGR4—18/Docs/R4-010895.zip. |
European Search Report—EP10160313—Search Authority—Berlin—Feb. 21, 2012. |
European Search Report—EP10162154—Search Authority—Berlin—Feb. 21, 2012. |
Gunnarson, F., et al.: “Uplink Admission Control in WCDMA Based on Relative Load Estimates”, IEEE International Conference on Communications, vol. 1, pp. 3091-3095, IEEE, New York, NY USA (Apr. 28, 2002). |
Hobfeld, T. et al., “Supporting Vertical Handover by Using a Pastry Peer-to-Peer Overlay Network,” Fourth Annual IEEE International Conference on Pervasive Computing and Communications Workshops, 2006. Percom Workshops 2006. Mar. 13-17, 2006, pp. 163-167, p. 164, paragraph III, IEEE, Piscataway, NJ, USA, XP010910514, ISBN: 0/7695-2520-2. |
LG Electronics Inc., “Relative Buffer Status Reporting,” 3GPP TSG-RAN WG2 meeting #46bis, R2-050852, Apr. 4, 2005, pp. 1-3, URL, http://www.3gpp.org/ftp/tsg13 ran/WG213 RL2/TSGR2—46bis/Documents/R2-050852.zip. |
Samsung: “Uplink control signaling structure (Revision of R1-041086),” 3GPP TSG-RAN WG1 Meeting #38bis, Tdoc R1-041222, 3GPP, Sep. 20, 2004, URL:. |
http://www.3gpp.org/ftp/tsg—ran/WG1—RL1/TSGR1—38bis/Dcs/R1-041222.zip. |
Tim/Tilab, Blu, Mobilkom Austria, One2one,Telefonica: “Re-introduction of SIR measurement,” 3GPP TSG-RAN4 Meeting #17, R4-010647, 3GPP, Goteborg, Sweden, May 21,2001, URL: http://www.3gpp.org/ftp/tsg—ran/WG4—Radio/TSGR4—17/Docs/R4-010647.Zip. |
Gunnarsson, G. et al.,“Location Trial System for Mobile Phones,” Global Telecommunications Conference, 1998. Globecom 98. The Bridge to Global Integration. IEEE, vol. 4, pp. 2211-2216, Nov. 8-12, 1998. |
Taiwan Search Report—TW095148233—TIPO—Oct. 19, 2012. |
Number | Date | Country | |
---|---|---|---|
20070149131 A1 | Jun 2007 | US |
Number | Date | Country | |
---|---|---|---|
60752973 | Dec 2005 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 11333792 | Jan 2006 | US |
Child | 11581212 | US |