Title of Invention

A METHOD OF REPORTING TRANSMISSION BACKLOG INFORMATION AND A DEVICE THEREOF

Abstract

Methods and apparatus related to reporting transmission backlog information are described. A wireless communications device maintains and updates transmission backlog information corresponding to a plurality of different transmission request groups. Different request groups may correspond to different uplink traffic queues. For a request reporting opportunity, the communications device selects a request group from among the plurality of different transmission request groups as a function of: request group changes in backlog with respect to previously reported requests, the changes taking into consideration base station allocation of transmission resources; and request group priority information. A request report is generated conveying backlog information corresponding to the selected request group, and the generated report is transmitted over a wireless communications link.

Full Text

FORM 2 THE PATENTS ACT, 1970 (39 of 1970) & THE PATENTS RULES, 2003 COMPLETE SPECIFICATION (See section 10, rule 13) 'METHODS AND APPARATUS TO SELECT A REQUEST GROUP FOR A REQUEST REPORT" QUALCOMM INCORPORATED, 5775 Morehouse Drive, San Diego, California 92121 -1714, United states of America. The following specification particularly describes the invention and the manner in which it is to be performed. WO 2007/075814 PCT/US2006/048653 METHODS AND-APPARATUS RELATED TO SELECTING A REQUEST CROUP FOR A REQUEST REPORT FIELD OF THE INVENTION [0001] The present invention relates to wireless communications methods and apparatus and, more particularly, to methods and apparatus related to selecting a request group from among a plurality of possible request groups which can be reported in a request report, for example, in an uplink traffic channel request report. BACKGROUND [0002] 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 traffic signaling, typically needs to communicate control information to a base station attachment point. The information may be communicated in the form of one or more control information reports which allow the base station attachment point to characterize the wireless terminal and allocate resources such as uplink transmission resources. [0003] A wireless terminal may support uplink traffic corresponding to a plurality of different types of applications. At different times the wireless terminal may have different traffic channel reporting needs. Accordingly, there is a need for methods and apparatus which would allow for a variety of reporting alternatives. For example, in systems which used a fixed bit size request report format, it would be beneficial if reporting alternatives corresponding to -2 — WO 2007/075814 PCT/US2006/048653 different groupings of traffic could be supported without changing the number of bits used for a report. In addition, assuming methods and apparatus for supporting reporting alternatives were developed, it would also be beneficial if methods and/or apparatus which could be used to select between available reporting alternatives could also be developed and/or supported. Improvements in reporting, and/or selection between reporting alternatives, if available, could facilitate efficient air link resource allocation and/or help to satisfy a wireless terminal's changing traffic needs and/or quality of service requirements. SUMMARY {0004] Various embodiments are directed to methods and apparatus for supporting a plurality of reporting alternatives, e.g., for a fixed size report. Some features are related to selecting a request group associated with a reporting alternative for a control information request report, e.g., an uplink traffic report which provides information on the amount of data waiting at a communications device to be transmitted. Such a report may be viewed and/or interpreted as a request for uplink transmission resources and is therefore sometimes referred to as an uplink request report. [0005] Various embodiments are directed to reporting transmission backlog information, m some such embodiments, a wireless communications device maintains and updates transmission backlog information corresponding to a plurality of different transmission request groups. Different request groups may correspond to different uplink traffic queues. For a request reporting opportunity, the communications device selects a request group from among the plurality of different transmission request groups as a function of: request group changes in backlog with respect to previously reported requests, the changes taking into consideration base station knowledge, e.g., base station allocation of transmission resources; and request group priority information. A request report is generated conveying backlog information corresponding to the selected request group and, the generated report transmitted over a wireless communications link [0006] An exemplary method of reporting transmission backlog information in accordance with various embodiments comprises: maintaining backlog information corresponding to a plurality of different transmission request groups; and selecting a request WO 2007/075814 PCT7US2006/048653 group from the plurality of different transmission request groups for which backlog information is maintained, wherein said selecting is performed as a function of a request group change in backlog with respect to previously reported backlog information after taking into consideration changes in backlog due to base station allocation of transmission resources. [0007] Various embodiments are also directed to wireless communication devices, e.g., wireless terminals such as mobile nodes. One exemplary wireless communications device is intended for use in a wireless communications system and communicates transmission backlog information to a base station using one of a plurality of supported reporting alternatives. The exemplary wireless communications device includes: a transmission backlog management module for maintaining backlog information corresponding to a plurality of different transmission request groups; and a selection module for selecting a request group from the plurality of different transmission request groups for which back log information is maintained, wherein said selecting is performed as a function of a request group change in backlog with respect to previously reported backlog information after taking into consideration changes in backlog due to base station allocation of transmission resources. [0008] 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 are discussed in the detailed description which follows. BRIEF DESCRIPTION OF THE FIGURES [0009] Figure 1 is drawing of an exemplary wireless communications systen implemented in accordance with various embodiments. [0010J Figure 2 is a drawing of an exemplary wireless terminal, e.g., mobile node, in accordance with various embodiments. [0011] Figure 3 is a drawing of an exemplary base station in accordance with various embodiments. 4 WO 2007/075814 PCT/US2006/048653 [0012] Figure 4 comprising the combination of Figure 4A, Figure 4B, Figure 4C and Figure 4D is a drawing of a flowchart of an exemplary method of reporting transmission backlog information. [0013] Figure 5 comprising the combination of Figure 5A, Figure 5B, Figure 5C, Figure 5D, Figure 5E and Figure 5F is a drawing of a flowchart of an exemplary method of operating a wireless communications device to report transmission backlog information. [0014] Figure 6 is a drawing of exemplary uplink dedicated control channel (DCCH) segments in an exemplary uplink timing and frequency structure in an exemplary orthogonal frequency division multiplexing (OFDM) multiple access wireless communications system. [0015] Figure 7 includes a table of a set of exemplary Dedicated Control Channel Reports (DCRs) used in an exemplary DCCH reporting structure. [0016] Figure 8 is a drawing illustrating an exemplary dedicated control channel reporting format including the dedicated control channel reports of Figure 9. [0017] Figure 9 is a drawing including a table describing an exemplary format of exemplary 4 bit uplink traffic request report (ULRQST4) and a column describing reporting alternatives. [0018] Figure 10 is a drawing including a table describing another exemplary format of exemplary 4 bit uplink traffic request report (ULRQST4) and a column describing reporting alternatives. [0019] Figure 11 is a drawing describing three exemplary request groups in an exemplary wireless terminal. WO 2007/075814 PCT/US2006/048653 PETATILED DESCRIPTION [0020] Figure 1 is drawing of ah exemplary wireless communications system 100 implemented in accordance with various embodiments. Exemplary wireless communications system 100 is, e.g., an orthogonal frequency division multiplexing (OFDM) multiple access wireless communications system using a dedicated control channel uplink reporting structure including at least some fixed size multi-bit request reports. The fixed bit size request reports can be used to report transmission backlog information, e.g., the number of frames of information waiting to be transmitted with regard to a queue or set of queues. A backlog report may provide information on one or more request groups where different request groups correspond to different queues or sets of queues which can be used to store information to be transmitted. [0021] Exemplary wireless communications system 100 includes a plurality of base stations (base station 1 102,..., base station M 104). Each base station (102, 104) has a corresponding wireless coverage area (cell 1 106, 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. • [0022] System 100 also includes a plurality of wireless terminals. At least some of the wireless terminals are mobile nodes which may move throughout the communication system. In Figure 1, wireless terminals (WT 1 110, WT N 112) are located in cell 1 106 and coupled to base station 1 102 via wireless links (126, 128), respectively. In Figure 1, wireless terminals (WT 1' 114, WTN' 116) are located in cell M 108 and coupled to base station Ml 04 via wireless links (130, 132), respectively. In accordance with various embodiments, at least some of the wireless terminals use a request report format, e.g., for a fixed bit size uplink traffic channel request report, allowing the wireless terminal to select, for a request report to be transmitted, between reporting alternatives, said reporting alternatives corresponding to at least two different request groups. For example, an exemplary 4 bit uplink traffic channel request report format may include 16 distinct bit patterns, and a first subset of the 16 bit mapping patterns may be associated with mapping request group 1 frame count backlog information, WO 2007/075814 PCT/US2006/048653 while a second subset of the 16 bit mapping patterns may be associated with mapping request group 2 frame count backlog information, and a third subset of the 16 bit mapping patterns may be associated with mapping request group 3 frame count backlog information said first and second and third subsets being non-overlapping. Continuing with the example, the wireless terminal selects, for a given reporting opportunity, one of the request groups on which to report backlog information. In some embodiments, the selection is performed as a function of: changes in backlog in request groups, whether there is information in a request group, the priority levels associated with the request groups, previous request reports, and/or base station previous allocation. [0023J Figure 2 is a drawingof an exemplary wireless terminal 200, e.g., mobile node, in accordance with various embodiments. Exemplary wireless terminal 200 is, e.g., a handheld mobile communications device. Exemplary wireless terminal 200 may be any of the wireless terminals 110, 112, 114, 116 of system 100 of Figure 1. [0024] Exemplary wireless terminal 200 includes a receiver module 202, a transmitter module 204, a processor 206, user I/O devices 208, and a memory 210 coupled together via a bus 212 over which the various elements may interchange data and information. Memory 214 includes routines 214 and data/information 216. The processor 206, e.g., a CPU, executes the . routines 214 and the data/information 216 in memory 210 to control the operation of the wireless terminal 200 and implement methods. [0025] Receiver module 202, e.g., an OFDM receiver, is coupled to receive antenna.203 via which the wireless terminal receives downlink signals from base stations. The received downlink signals include assignment signals conveying assignments for uplink traffic channel segments. [0026] Transmitter module 204, e.g., an OFDM transmitter, is coupled to transmit antenna 205 via which the wireless terminal transmits uplink signals to base stations. The uplink signals include dedicated control channel segment signals and traffic channel segment signals. At least some of the dedicated control channel segment signals convey uplink request reports for traffic channel air link resources, e.g., 1 bit uplink traffic channel request report, 3 bit 7 WO 2007/075814 PCT/US2006/048653 uplink traffic channel request reports and 4 bit uplink traffic channel request reports. In some embodiments, the same antenna is used for receiver and transmitter. [0027] User I/O devices 208, e.g., microphone, keypad, keyboard, switches, camera, speaker, display, etc., allow a user of wireless terminal 200 to input data/information and access output data/information. User I/O devices 208 also allow a user of wireless terminal 200 to control at least some functions of wireless terminal 200, e.g., initiate or terminate a communications session and/or application. [0028] Routines 214 include a transmission backlog management module 218, a selection module 220, a report generation module 222, and a transmission control module 224. Transmission backlog management module 218 includes a backlog update module 226. Selection module 220 includes a primary selection module 228 and a default selection module 230. Default selection module 230 includes one or more of alternative default selection modules (round robin selection module 232, priority ordering selection module 234). [0029J Transmission backlog management module 218 maintains backlog information corresponding to a plurality of different transmission request groups. Backlog update module 226 updates the maintained backlog information as a function of at least one of received information to be transmitted, dropped information, and transmitted information. [0030] Selection module 220 selects a request group from the plurality of different transmission request groups for which backlog information is maintained, wherein said selecting is performed as a function of a request group change in backlog with respect to previously reported backlog information after taking into consideration changes in backlog due to base station allocation of transmission resources. For example, for each of a plurality of request opportunities for a certain type of n bit uplink traffic channel request report, e.g., a 4 bit uplink traffic channel request report, selection module 220 performs a selection identifying a request group on which backlog information is to be conveyed for that reporting opportunity. [0031] In some embodiments, primary selection module 228, selects, when at least one of the transmission request groups has a non-zero change in backlog with respect to the last previously reported request report conveying that particular request group's backlog information WO 2007/075814 PCT/US2006/048653 after taking into consideration changes in backlog due to base station allocation of transmission resources, the request group having the highest priority from among the request groups having a non-zero change in backlog with respect to the last previously reported request report conveying that particular request groups backlog information after taking into consideration changes in backlog due to base station allocation of transmission resources. [0032] In some embodiments, primary selection module 228, selects, when at least one of the transmission request groups has a positive change in backlog with respect to the last •previously reported request report conveying that particular request group's backlog information after taking into consideration changes in backlog due to base station allocation of transmission resources, the request group having the highest priority from among the request groups having a positive change in backlog with respect to the last previously reported request report conveying that particular request groups backlog information after taking into consideration changes in backlog due to base station allocation of transmission resources. [0033] In some embodiments, primary selection module 228, selects, when at least one of the transmission request groups has a positive backlog and a non-negative change in backlog with respect to the last previously reported request report conveying mat particular request group's backlog information after taking into consideration changes in backlog due to base station allocation of transmission resources, the request group having the highest priority from among trie request groups having a positive backlog and a non-negative change in backlog with respect to the last previously reported request report conveying that particular request groups backlog information after taking into consideration changes in backlog due to base station allocation of transmission resources. [0034] In some embodiments, default selection module 230 selects a request group from among the plurality of request groups when none of the individual request groups have a non¬zero change in backlog with respect to the last previously reported request report conveying that particular individual request group's backlog information after taking into consideration changes in backlog due to base station allocation of transmission resources. [0035] In some embodiments, default selection module 230 selects a request group from among the plurality of request groups when none of the individual request groups have a WO 2007/075814 PCT/US2006/048653 positive change in backlog with respect to the last previously reported request report conveying that particular individual request group's backlog information after taking into consideration changes in backlog due to base station allocation of transmission resources.. [0036] In some embodiments, default selection module 230 selects a request group from among the plurality of request groups when none of the individual request groups have a positive backlog and a non-negative change in backlog with respect to the last previously reported request report conveying that particular individual request group's backlog information after taking into consideration changes in backlog due to base station allocation of transmission resources. [0037] Round robin selection module 232 performs the selection for the default selection module 230 as a function of a round robin selection process. Flowchart 533 of Figure 5E represents an example of a round robin selection process. Priority ordering selection module 234 performs the selection for the default selection module 230 as a function of a priority ordered selection process. Flowchart 531 of Figure 5E represents an example of a priority ordered selection process. [0038] In some embodiments, the default selection module 230, at times, determines that it should be reported that there is no backlog in any of the request groups. [0039] Report generation module 222 generates an n-bit size request report in accordance with N bit size request report format information 236 and the reporting alternative indicated by information 254 corresponding to the selected request group indicated by information 252. [0040] Transmitter module 204 transmits the generated n-bit size request report over a wireless communications link, e.g., to a base station serving as the wireless terminal's current point of network attachment. Transmission control module 224 controls the operation of transmitter module 204 to control the transmission of the generated n-bit size request report over a wireless communications link, 10 WO 2007/075814 PCT/US2006/048653 [0041] Data/information 216 includes N bit size, e.g., 4 bit size, request report format information 236, dedicated control channel reporting structure information 238, a plurality of request group communication queues (request group 1 communication queue 240,..., request group in communication queue 242), a plurality of request group priority information (request group 1 priority information 244,.... request group m priority information 246), a plurality of request group queue statistics information (request group 1 queue stats information 248,..., request group m queue stats information 250), selected request group information 252, selected reporting alternative infonnation 254, and generated uplink request report information 256. N bit size report format information 236 includes a plurality of sets of reporting alternative bit mapping information (reporting alternative 1 bit mapping information 258,..., reporting alternative X bit mapping information 260). Request group 1 queue statistics information 248 includes frame counts N[l] 262, and delta frame counts AN[1] 264. Request group m queue statistics information 250 includes frame counts N[m] 266, and delta frame counts AN[m] 269. [0042] Figure 9 represents one example of exemplary N bit size request report format information 236 used in some embodiments. Figure 10 represents another example of exemplary N bit size request report format information 236 used in some embodiments. In various embodiments, the n-bit size request report format information supports a plurality of reporting alternatives, different reporting alternatives corresponding to different request groups. [0043] Dedicated control channel (DCCH) reporting structure information 238 includes information identifying DCCH logical channel tones, DCCH segments, mapping of different types of reports to segments, and associated timing in a recurring, reporting structure. The different types of reports in the DCCH reporting structure include a request report type in accordance with the N bit size request report format information 236. Figures 6, 7, and 8 include some exemplary DCCH reporting structure information. [0044] Request groups communication queues (request group 1 communication queue 240,... request group m communication queue 242) are a plurality of communication queues fo storing data to be transmitted, where each request group corresponds to one communication queue. In some embodiments, at least some of the different request groups correspond to a set of communication queues. Request group priority information (request group 1 priority information 244,..., request group m priority information 246) are stored request group priority 11 WO 2007/075814 PCT/US2006/048653 information associated with the different request groups. Selection of a reporting alternative is • performed, in some embodiments, as a function of request group priority information. In various embodiments the request group priorities are predetermined. Request groups queue statistics information (request group 1 queue stats info 248,..., request group m queue stats info 250) includes frame counts of backlog, e.g., MAC frame counts of bacldog, (N[l] 262,..., N[m] 266), respectively corresponding to (request group 1 communication queue 240,..., request group m communication queue 242), respectively. Request groups queue statistics information (request group 1 queue stats info 248,..., request group m queue stats info 250) includes delta frame counts of backlog, e.g., delta MAC frame counts of backlog, (AN[1] 264, ..., AN[m] 269), respectively corresponding to (request group 1 communication queue 240, ..., request group m communication queue 242), respectively. The delta frame count information for a request group, e.g., AN[1] 264 for request group 1, is calculated with respect to the last previously transmitted backlog information with respect to that request group after taking into consideratior changes due to base station knowledge, e.g., base station allocation of transmission resources. Selection module 220, uses the queue stats info (248,.... 250) in determining a selected request group. [0045] Selected request group information 252, an output of module 220 and an input to module 222, is, e.g., an identifier identifying which of the in request groups has been selected by selection module 220. In some embodiments, selected request group information, at time, indicates that none of the request groups have backlog. Selected reporting alternative information 254, which corresponds to the selected request group information 252 identifies one of the X reporting alternatives in accordance with request report format information 236. Generated uplink request report information 256 is an output of report generation module 222. For example, if the uplink request report is a four bit uplink request report, the report is one of 16 different bit patterns. [0046] Figure 3 is a drawing of an exemplary base station 300 in accordance with various embodiments. Exemplary base station 300 may be any of the exemplary base stations (BS 1102,..., BS M 104) of system 100 of Figure 1. Base station 300 includes a receiver module 304, a transmitter module 308^ a processor 310, an I/O interface 312, and a memory 314 coupled together via a bus 316 over which the various elements may interchange data and information. Memory 314 includes routines 318 and data/information 320. The processor 310, - I 2.- WO 2007/075814 PCT/US2006/048653 e.g., a CPU, executes the routines 318 and uses the data/information 320 in memory 314 to . control the operation of the base station 300 and implement methods. [0047] Receiver module 304, e.g., an OFDM receiver, is coupled to receive antenna 302 via which the base station. 300 receives uplink signals from wireless terminals, said received uplink signals including dedicated control channel segment signals, at least some of the dedicated control channel segment signal conveying traffic channel request reports. Received uplink signals also include traffic channel segment signals. Transmitter module 308, e.g., an OFDM transmitter, is coupled to transmit antenna 306 via which the base station transmits downlink signals to wireless terminals, said downlink signals including assignment signals conveying assignments for uplink traffic channel segments. I/O interface 312 couples the base station to other network node, e.g., other base stations and/or the Internet. Thus I/O interface 312, by coupling the base station 300 to a backhaul network allows a wireless terminal using an attachment point of base station 300 to participate in a communications session with a peer node, e.g., another wireless terminal, using a different base station as its point of network attachment. [0048] Routines 318 include a request report information recovery module 322, a scheduler module 324, a request group inference module 326 and a request group updating module 327. Request report information recovery module 322 uses data/information 320 including N bit size request report format information 334 to obtain recovered information from a received request report, e.g., a 4 bit request report for traffic channel resources communicated in an uplink dedicated control channel segment. For example corresponding to WT 1, the recovered information includes recovered information from processed request report 342. The information bits of the request report may be one of a plurality, e.g., 16, of different patterns, and the particular bit pattern is interpreted to mean that one request group or a set of request groups has a certain number of frames in backlog or has a number of frames within a range in its backlog. For example consider an example where the request report format corresponds to that of Figure 10, bit pattern = 0010 may signify that request group 1 has 2 frames in its backlog waiting to be transmitted. [0049] Scheduler module 324 schedules uplink and downlink traffic channel segments to wireless terminals. For example, scheduler module 324 schedules uplink traffic channel - 13- WO 2007/075814 PCT/US2006/048653 segments in response to received requests communicated in fixed bit size uplink traffic channel request reports, e.g., ULRQST4 reports, from wireless terminals in an On-state of operation using the base station 300 as a current point of network attachment. Assigned uplink traffic channel segment information 350 corresponds to scheduler 324 assignments for WT 1, e.g., information identifying particular indexed uplink traffic channel segments assigned to WT 1. [0050] Request group inference module 326 performs inferences about request groups not directly reported in the received request report. For example, consider that the predetermined request group priority information 336 identifies that request group 1 has a higher predetermined priority than request group 2 or request group 3, and the reporting rules are such that a wireless terminal reports the backlog of the highest priority group with a positive delta backlog after taking into consideration base station knowledge, e.g., base station previous allocation of uplink segments. If in such a situation, the base station received a report which conveyed information about request group 2, the base station could infer that request group 1 does not have a positive delta backlog. [0051] Request group updating module 327 uses the recovered information, e.g., info 342, obtained from recovery module 322 and the inferred information, e.g., info 344, obtained from inference module 326 to update the set of request group information corresponding to the wireless terminal, e.g., (request group 1 information 346,..., request group m information 348). For example, request group updating module 327 loads new request group frame counts, modifies request frame counts, and/or clears request group cotmts with regard to one or more of request group information sets, e.g., (request group 1 information 346,..., request group m information 348). [0052] Data/information 320 includes a plurality of sets of wireless terminal data/information (WT 1 data/information 328,..., WT N data/information 330), dedicated control channel reporting structure information 332, N bit size request report format information 334, and predetermined request group priority information 336. WT 1 data/information 328 includes recovered information from processed request report 342, inferred information regarding request groups 344, a plurality of sets of request group information (request group 1 information 346 request group m information 348), and assigned uplink traffic channel segment information 350. -14 WO 2007/075814 PCT/US2006/048653 [0053] N bit size, e.g., 4 bit size, report format information 334 includes interpretation information for a plurality of bit patterns (interpretation information for bit pattern 1 338,.... interpretation information for bit pattern 2N 340). For example in one exemplary embodiment, where N = 4 there are 16 distinct bit patterns (0000, 0001,..., 1111) where each bit pattern has a different interpretation of the information being conveyed in the report. [0054] Predetermined request group priority information 336 includes information associating different uplink traffic request groups with different predetermined priorities. In some embodiments, different wireless terminals have different priorities orderings associated with the request groups being used. [0055] Dedicated control channel (DCCH) reporting structure information 332 includes information identifying DCCH logical channel tones, DCCH segments, mapping of different types of reports to segments, and associated timing in a recurring reporting structure. The different types of reports in the DCCH reporting structure include a request report type in accordance with the N bit size request report format information 334. [0056] Figure 4 comprising the combination of Figure 4A, Figure 4B, Figure 4C and Figure 4D is a drawing of a flowchart 400 of an exemplary method of reporting transmission backlog information that may be implemented by a wireless communications device. For example, an exemplary wireless terminal such as a mobile node in an exemplary OFDM multiple access wireless communications system, may implement the method of flowchart 400 to report backlog information about different transmission request requests for uplink traffic to a base station. In some embodiments, each request group corresponds to a request group queue used to store information to be transmitted. The exemplary method is started in step 402, e.g., where the communications device is powered on and initialized. Operation proceeds from start step 402 to step 404 [0057] In step 404, the communications device maintains backlog information corresponding to a plurality of different transmission request groups. Backlog information includes, e.g., counts of frames, e.g., counts of MAC frames, waiting to be transmitted corresponding to a request group. Operation proceeds from step 404 to step 406. WO 2007/075814 PCT/US2006/048653 [0058] In step 406, the communications device selects a request group from the plurality of different transmission request groups for which backlog information is maintained, wherein said selecting is performed as a function of a request group change in backlog with respect to previously reported backlog information after taking into consideration changes in backlog due to base station allocation of transmission resources. In step 406 three exemplary alternative selection methods are included (alternative A selection method 414, alternative B selection method 416, alternative G selection method 418). [0059] In alternative A selection method 414 (See Figure 4B), the communications device determines in sub-step 420 if at least one of the transmission request groups have a non¬zero change in backlog with respect to the last previously reported request report conveying that particular request group's backlog information after taking into consideration changes in backlog due to the base station allocation of transmission resources. If it is determined in sub-step 420 that at least one of the request groups has a non-zero change operation proceeds from sub-step 420 to sub-step 422; otherwise, operation proceeds from sub-step 420 to sub-step 424. [0060] In sub-step 422, the communications device selects the request group having the highest priority from among the request groups having a non-zero change in backlog with respect to the last previously transmitted request report conveying that particular request group's backlog information after taking into consideration changes in backlog due to the base station allocation of transmission resources. In sub-step 424, the communication device selects a request group from among the plurality of different request groups. Sub-step 424 includes two alternative sub-steps, sub-step 426 and sub-step 428. In sub-step 426, the communications device selects a request group according to a round robin selection process. In sub-step 428, the communications device selects a request group according to a priority ordering selection process. [0061] In alternative B selection method 416 (See Figure 4C), the communications device determines in sub-step 430 if at least one of the transmission request groups have a positive change in backlog with respect to the last previously reported request report conveying that particular request group's backlog information after taking into consideration changes in backlog due to the base station allocation of transmission resources. If it is determined in sub- WO 2007/075814 PCT/US2006/048653 step 430 that at least one of the request groups has a positive change operation proceeds from sub-step 430 to.sub-step 432; otherwise, operation proceeds from sub-step 430 to sub7step 434. [0062) In sub-step 432, the communications device selects the request group having the highest priority from among the request groups having a positive change in backlog with respect to the last previously transmitted request report conveying that particular request group's backlog information after taking into consideration changes in backlog due to the base station allocation of transmission resources. In sub-step 434, the communication device selects a request group from among the plurality of different request groups. Sub-step 434 includes two alternative sub-steps, sub-step 436 and sub-step 438. In sub-step 436, the communications device selects a request group according to a round robin selection process. In sub-step 438, the communications device selects a request group according to apriority ordering selection process [0063] In alternative C selection method 418 (See Figure 4D), the communications device determines in sub-step 440 if at least one of the transmission request groups have a positive backlog and a non-negative change in backlog with respect to the last previously reported request report conveying that particular request group's backlog information after taking into consideration changes in backlog due to the base station allocation of transmission resources. If it is determined in sub-step 440 that at least one of the request groups has a positive backlog and a non-negative change in backlog operation proceeds from sub-step 440 to sub-step 442; otherwise, operation proceeds from sub-step 440 to sub-step 434. [0064] In sub-step 442, the communications device selects the request group having the highest priority from among the request groups having a positive backlog and a non-negative change in backlog with respect to the last previously transmitted request report conveying that particular request group's backlog information after taking into consideration changes in backlog due to the base station allocation of transmission resources. In sub-step 444, the communication device selects a request group from among the plurality of different request groups. Sub-step 444 includes two alternative sub-steps, sub-step 446 and sub-step 448. In sub-step 446, the communications device selects a request group according to a round robin selection process. In sub-step 448, the communications device selects a request group according to a priority ordering selection process. WO 2007/075814 PCT/US2006/048653 [0065] Returning to Figure 4A, operation proceeds from step 406 to step 408. In step 408, the communications device generates a request report, e.g., an N bit size uplink request report, which reports backlog information corresponding to the selected request group. In some embodiments, the selected request group corresponds to one of a plurality of supported reporting alternatives of an n bit size request report format, different reporting alternatives corresponding to different request groups, and the generated n-bit size request report is in accordance with the n-bit size request report format and said reporting alternative corresponding to the selected request group. [0066] Operation proceeds from step 408 to step 410. In step 410, the communications device transmits the generated request report, e.g., N bit size request report, over a wireless communications link. [0067] Operation proceeds from step 410 to step 412. In step 412, the communications device updates the maintained backlog information as a function of at least one of received information to be transmitted, dropped information, and transmitted information. Operation proceeds from step 412 to step 406, where the communication device performs another request group selection, e.g., for another request report to be transmitted. 10068] Figure 5 comprising the combination of Figure 5 A, Figure 5B, Figure 5C, Figure 5D, Figure 5E and Figure 5F is a drawing of a flowchart 500 of an exemplary method of operating a wireless communications device to report transmission backlog information. For example, an exemplary wireless terminal such as a mobile node in an exemplary OFDM multiple access wireless communications system, may implement the method of flowchart 500 to report backlog information about three different transmission request groups for uplink traffic to a base station. Operation starts in step 502 where the communications device is powered on and initialized. Ooeration nroceeds from start steo 502 to sten 504 and sten 508. [0069] In step 508, the communications device maintains backlog information corresponding to a plurality of different transmission request groups. In this example, the wireless terminal maintains backlog information 505 corresponding to request group 1 (RG1), request group 2 (RG2), and request group 3 (RG3). Each request group (RGl ; RG2, RG3) corresponds to a request group queue used to store information to be transmitted, e.g., uplink WO 2007/075814 PCT/US2006/048653 traffic to be transmitted. Backlog information 505 includes, e.g. frames counts of backlog to be transmitted, e.g., MAC frames of backlog, corresponding to the request groups where N[l] is the frame count for RG1, N[2] is the frame count for RG2, and N[3] is the frame count for RG3. Backlog information 505 also includes delta information corresponding to the request groups: AN[1] corresponding to RG1, AN[2] corresponding to RG2, and AN[3] corresponding to RG3, where a delta indicates a change with respect to the last previously reported request report conveying that particular request group's backlog information after taking into consideration changes in backlog expected to be known to the base station, e.g., changes in backlog due to base station allocation of transmission resources. [0070] Operation proceeds from step 504 to step 506. In step 506, the communications device updates the maintained backlog information 505 as a function of at least one of received information to be transmitted, dropped information, and transmitted information. Step 506" is performed on an ongoing basis. [0071] Operation proceeds from start step 502 to step 508, for each of a plurality of reporting opportunities which report selection including request group 1, request group 2, and request group 3 consideration. For example, each opportunity, in some embodiments, is a multi-bit, e.g., 4 bit, uplink traffic channel request report opportunity in a dedicated control channel reporting structure. Step 508 uses backlog information 505 as input. Step 508 directs operation to a report selection subroutine. Drawing 509 of Figure 5B is a flowchart of an exemplary report selection subroutine, alternative 1 report selection subroutine. Drawing 511 of Figure 5C is a flowchart of another exemplary report selection subroutine, alternative 2 report selection subroutine. Drawing 535 of Figure 5D is a flowchart of still another exemplary report selection subroutine, alternative 3 report selection subroutine. [0072] Exemplary alternative 1 report selection subroutine of Figure 5B will now be described. Operation of alternative 1 report selection subroutine starts in step 516, e.g., where the subroutine receives backlog information 505 including delta count information corresponding to the request groups. Operation proceeds from start step 516 to step 518. [0073] In step 518, the communications device determines whether the delta count associated with request group 1 is equal to zero. If it is determined in step 518 that AN[1] is not WO 2007/075814 PCT/US2006/048653 equal to zero, then operation proceeds to step 520 where the communication device selects RG1 as the selected request group; otherwise operation proceeds from step 518 to step 522. [0074] In step 522, the communications device determines whether the delta count associated with request group 2 is equal to zero. If it is determined in step 522 that AN[2] is not equal to zero, then operation proceeds to step 524 where the communication device selects RG2 as the selected request group; otherwise operation proceeds from step 522 to step 526. [0075] In step 526, the communications device determines whether the delta count associated with request group 3 is equal to zero. If it is determined in step 526 that AN[3] is not equal to zero, then operation proceeds to step 528 where the communication device selects RG3 as the selected request group; otherwise operation proceeds from step 526 to step 530. [0076] In step 530, operation is directed to a default selection subroutine. Flowchart 531 of Figure 5E is-a flowchart of a first alternative default selection subroutine using a priority ordered selection process. Flowchart 533 of Figure 5D is a flowchart of a second alternative default selection subroutine using a round robin selection process. [0077] Operation proceeds to step 534, where operation returns from a default selection subroutine, e.g., from step 554 or step 576, with an identified selected request group or an indication of no backlog. Operation proceeds from one of steps 520, 524, 534, and 528 to step 536. In step 536, the report selection subroutine ends and the subroutine returns an identified selected request group or an indication of no backlog. [0078] Exemplary alternative 2 report selection subroutine of Figure 5C will now be described. Operation of alternative 2 report selection subroutine starts in step 513, e.g., where the subroutine receives backlog information 505 including delta count information corresponding to the request groups. Operation proceeds from start step 513 to step 515. lOU7yj In step 515, the communications device determines whether the delta count associated with request group 1 is greater than zero. If it is determined in step 515 that AN[1] is greater than zero, then operation proceeds to step 519 where the communication device selects RG1 as the selected request group; otherwise operation proceeds from step 515 to step 517. 20 WO 2007/075814 PCT/US2006/048653 [0080] In step 517, the communications device determines whether the delta count associated with request group 2 is greater than zero. If it is determined in step 517 that AN[2] is greater than zero, then operation proceeds to step 523 where the communication device selects RG2 as the selected request group; otherwise operation proceeds from step 5i7 to step 521. [0081] In step 521, the communications device determines whether the delta count associated with request group 3 is greater than zero. If it is determined in step 521 that AN[3] is greater than zero, then operation proceeds to step 525 where the communication device selects RG3 as the selected request group; otherwise operation proceeds from step 521 to step 527. [0082] In step 527, operation is directed to a default selection subroutine. Flowchart 531 of Figure 5E is a flowchart of a first alternative default selection subroutine using a priority ordered selection process. Flowchart 533 of Figure 5F is a flowchart of a second alternative default selection subroutine using a round robin selection process. [0083] Operation proceeds to step 529, where operation returns from a default selection subroutine, e.g., from step 554 or step 576, with an identified selected request group or an indication of no backlog. Operation proceeds from one of steps 519, 523, 525, and 529 to step 531. In step 531, the report selection subroutine ends and the subroutine returns an identified selected request group or an indication of no backlog. [0084] Exemplary alternative 3 report selection subroutine of Figure 5D will now be described. Operation of alternative 3 report selection subroutine starts in step 537, e.g., where the subroutine receives backlog information 505 including count information and delta count information corresponding to the request groups. Operation proceeds from start step 537 to step 539. [0085] In step 539, the communications device determines whether request group 1 has a positive backlog and whether the delta count associated with request group 1 is greater than or equal to zero. If it is determined in step 539 that N[l] is greater than 0 and AN[1] is greater than or equal to zero, then operation proceeds to step 543 where the communication device selects RG1 as the selected request group; otherwise operation proceeds from step 539 to step 541. WO 2007/075814 PCT/US2006/048653 [0086] In step 541 j the communications device determines whether request group 2 has a positive backlog and whether the delta count associated with request group 2 is greater than or equal to zero. If it is determined in step 541 that N[2] is greater than 0 and AN[2] is greater than or equal to zero, then operation proceeds to step 547 where the communication device selects RG2 as the selected request group; otherwise operation proceeds from step 541 to step 545. [0087] - In step 545, the communications device determines whether request group 3 has a positive backlog and whether the delta count associated with request group 3 is greater than or equal to zero. If it is determined in step 545 thatN[3] is greater than 0 and AN[3] is greater than or equal to zero, then operation proceeds to step 549 where the communication device selects RG3 as the selected request group; otherwise operation proceeds from step 545 to step 551. {0088] In step 551, operation is directed to a default selection subroutine. Flowchart 531 of Figure 5E is a flowchart of a first alternative default selection subroutine using a priority ordered selection process. Flowchart 533 of Figure 5F is a flowchart of a second alternative default selection subroutine using a round robin selection process. {0089] Operation proceeds to step 553, where operation returns from a default selection subroutine, e.g., from step 554 or step 576, with an identified selected request group or an indication of no backlog. Operation proceeds from one of steps 543, 547, 549, and 553 to step i . 555. In step 555, the report selection subroutine ends and the subroutine returns an identified selected request group or an indication of no backlog. [0090] The exemplary method of default selection subroutine (alternative A) of flowchart 531 of Figure 5E will now be described. Operation of the default selection subroutine starts in step 538 and proceeds to step 540. In step 540, the communication device determines whether the frame count corresponding to request group 1 is equal to zero. If it is determined that N[l] = 0 operation proceeds from step 540 to step 544; otherwise operation proceeds from step 540 to step 542, where the communication device selects RGl as the selected request group. [0091] In step 544, the communication device determines whether the frame count corresponding to request group 2 is equal to zero. If it is determined that N[2] = 0 operation proceeds from step 544 to step 548; otherwise operation proceeds from step 544 to step 546, 22 WO 2007/075814 PCT/US2006/048653 where the communication device selects RG2 as the selected request group. [0092] in step 548, the communication device determines, whether the frame count corresponding to request group 3 is equal to zero. If it is determined that N[3] = 0 operation proceeds from step 548 to step 552; otherwise operation proceeds from step 548 to step 550, where the communication device selects RG3 as the selected request group. In step 552, the subroutine provides an indication of no backlog corresponding to RGl, RG2 and RG3. [00931 Operation proceeds from one of steps 542, 546, 550 and 552 to step 554. In step 554, the subroutine ends and returns an identified selected request group or an indication of no backlog. [0094] The exemplary method of default selection subroutine (alternative B) of . flowchart 533 of Figure 5F will now be described. Operation of the default selection subroutim starts in step 556 and proceeds to step 562. In step 562, the subroutine retrieves the stored last selected request group from stored information 560, e.g., the last selected request group selecte by this subroutine on a previous iteration of the subroutine or an initialization value if this happens to be a first iteration of the subroutine. [0095] Operation proceeds from step 562 to step 564. In step 564, it is determined whether the stored last selected request group was RGl. If it is determined in step 564, that the stored last selected request group is RGl, then operation proceeds to step 566, where the subroutine selects RG2 as the selected request group; otherwise operation proceeds to step 568. [0096] In step 568, it is determined whether the stored last selected request group was RG2. If it is determined in step 564, that the stored last selected request group is RG2, then operation proceeds to step 570, where the subroutine selects RG3 as the selected request group; otherwise operation proceeds to step 572. In step 572, the subroutine selects RGl as the selected request group, since by default RG3 was the stored last selected request group. [0097] Operation proceeds from one of steps 566, 570, and 572 to step 574. In step 574 the subroutine updates the stored last selected request group in information 560 based on the '-2.3- WO 2007/075814 PCT/US2006/048653 selection of the one of steps 566, 570 and 572. Operation proceeds from step 574 to step 576, where the subroutine ends and the subroutine returns the identified selected request group. [0098] Returning to Figure 5 A, operation proceeds to step 510, where operation returns from the report selection subroutine, e.g., from one of step 536, step 531 and 555, with ar^ identified selected request group or an indication to report no backlog. In some embodiments, the selected request group corresponds to one of a plurality of supported reporting alternatives of an n-bit size request report, different reporting alternatives corresponding to different request groups. For example, the n-bit size report may be a 4 bit report with 16 alternative possible 4 bit bit patterns, and a first reporting alternative associated with reporting request group 1 backlog may include a first subset of those 16 bit patterns, a second reporting alternative associated with reporting request group 2 backlog may include a second subset of those 16 bit patterns, and a third reporting alternative associated with reporting request group 3 backlog may include a third subset of those 16 bit patterns, where said first, second, and third subsets are non-overlapping. [0099] Then, in step 512, the communications device generates a request report, e.g., an N-bit size request report, which reports backlog information corresponding to the selected request group or reports no backlog. In some embodiments, the generated n-bit size request report is in accordance with the n-bit size request report format and said reporting alternative corresponding to the selected request group. [00100] Operation proceeds from step 512 to step 514. In step 514, the communication device transmits the generated request report, e.g., an N bit size request report, over a wireless communications link. [00101] In some embodiments, the number of request groups under consideration for selection is two. In some embodiments, the number of request groups under consideration for selection is a number greater than three, e.g., four, five six, seven, eight, or nine. [00102] Figure 6 is a drawing 600 of exemplary uplink dedicated control channel (DCCH) segments in an exemplary uplink timing and frequency structure in an exemplary orthogonal frequency division multiplexing (OFDM) multiple access wireless communications system. The uplink dedicated control channel is used to send Dedicated Control Reports (DCR) 24 WO 2007/075814 PCT/US2006/048653 from wireless terminals to base stations. Vertical axis 602 plots logical uplink tone index while horizontal axis 604 plots the uplink index of the halfslot within a beaconslot. In this example, an uplink tone block includes 113 logical uplink tones indexed (0,..., 112); there are seven successive OFDM symbol transmission time periods within a halfslot, 2 additional OFDM symbol time periods followed by 16 successive half-slots within a superslot, and 8 successive superslots within a beacon slot. The first 9 OFDM symbol transmission time periods within a superslot are an access interval, and the dedicated control channel does not use the air link resources of the access interval. [00103] The exemplary dedicated control channel is subdivided into 31 logical tones (uplink tone index 81 606, uplink tone index 82 608, ..., uplink tone index 111 610). 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). [00104] For each tone in the dedicated control channel there are 40 segments in the beaconslot corresponding to forty columns (612, 614, 616, 618, 620, 622,..., 624). The segment structure repeats on a beaconslot basis. For a given tone in the dedicated control channel mere are 40 segments corresponding to a beaconslot 628; each of the eight superslots c the beaconslot includes 5 successive segments for the given tone. For example, for first superslot 626 of beaconslot 628, 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 626 of beaconslot 628, 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 626 of beaconslot 628, 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]). . [00105] 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. 25 WO 2007/075814 PCT/US2006/048653 [00106] 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 (606, 608,.... 610) mav be currently assigned to (WT A 630, WT B 632, ... , WT N' 634), respectively. [00107] 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 700 of Figure 7. First column 702 of table 700 describes abbreviated names used for each exemplary report. The name of each report ends with a number which specifies the number of bits of the DCR. Second column 704 of table 700 briefly describes each named report. [00108] Figure 8 is a drawing 899 illustrating an exemplary reporting format information in an exemplary beaconslot for a given DCCH tone, e.g., corresponding to a wireless terminal. In Figure 8, each block (800, 801, 802, 803, 804, 805, 806, 807, 808, 809, 810, 811, 812, 813, 814, 815, 816, 817, 818, 819, 820, 821, 822, 823, 824, 825, 826, 827, 828, 829, 830, 831, 832, 833, 834, 835, 836, 837, 838, 839) represents one segment whose index s2 (0,..., 39) is shown above the block in rectangular region 840. Each block, e.g., block 800 representing segment 0, conveys 6 information bits; each block comprises 6 rows corresponding to the 6 bits in the segment, where the bits are listed from the most significant bit to the least significant bit downwards from the too row to the bottom row as shown in rectangular reeion 843. [00109] Figure 9 is a drawing 900 including a table 902 describing an exemplary format of exemplary 4 bit uplink traffic request report (ULRQST4) and a column 904 describing reporting alternatives. Column 906 of table 902 lists the 16 possible information bit patterns for the report, and column 908 lists reported backlog information conveyed corresponding to each of the possible bit patterns. For example, N[l J = 2 indicates that request group 1 has two frames in its backlog to be transmitted; N[2] = 4:5 indicates that request group 2 has 4 or 5 frames in its backlog to be transmitted; N[3]>=33 indicates that request group 3 has 33 or more frames in its backlog. Column 904 indicates that reporting alternative A reports that request groups 1, 2, and 3 have no backlog and corresponds to the bit pattern 0000. Column 904 also indicates that: reporting alternative B reports on request group 1 backlog and corresponds to bit patterns (0001, 0010 and 0011); reporting alternative C reports on request group 2 backlog and corresponds to WO 2007/075814 PCT/US2006/048653 . bit patterns (0100, 0101, 0110 and 0111); and reporting alternative D reports on request group 3 backlog andcorresponds to bit patterns (1000, 1001, 1010, 1011, 1100, 1101, 1110 andOlll). [00110] Figure 10 is a drawing 1000 including a table 1002 describing another exemplary format of exemplary 4 bit uplink traffic request report (ULRQST4) and a column 1004 describing reporting alternatives. Column 1006 of table 1002 lists the 16 possible information bit patterns for the report, and column 1008 lists reported backlog information conveyed corresponding to each of the possible bit patterns. For example, N[l] = 0 indicates that request group 1 has no frames in its backlog to be transmitted; N[2] = 3:6 indicates that request group 2 has 3, 4, 5 or 6 frames in its backlog to be transmitted; N[3]>=33 indicates that request group 3 has 33 or more frames in its backlog. Column 1004 indicates that:, reporting alternative A reports on request group 1 backlog and corresponds to bit patterns (0000, 0001, 0010 and 0011); reporting alternative B reports on request group 2 backlog and corresponds to bit patterns (0100, 0101, 0110 and 0111); and reporting alternative C reports on request group 3 backlog and corresponds to bit patterns (1000, 1001, 1010, 1011, 1100, 1101, 1110 and 0111). [00111] Figure 11 is a drawing 1100 describing three exemplary request groups in an exemplary wireless terminal. In some embodiments, the information of Figure 11 is includes as part of data/information 216 of wireless terminal 200. Column 1102 describes that request group 1 has a queue for uplink traffic, a current frame count N[l] of its queue, a last reported frame count NRPTOLD[1]> a frame count adjustment for base station allocation NBSADJ[1] and a delta frame count AN[1]. The last reported frame count transmitted in a report corresponding to the request group, NRPTOLD[1], may have been communicated in the same type of request report, e.g., the same bit size request report, or a different type of request report, e.g., a different bit size request report. The base station adjustment value NBSADJ[1] may correspond to a previous assignment of an uplink traffic channel segment for conveying frames of request group 1 information. In some embodiments, AN[1] = (N[l] - NRPTOLD[I]) - NBSADJ[ 1]. [00112] Column 1104 describes that request group 2 has a queue for uplink traffic, a current frame count N[2] of its queue, a last reported frame count NRPTOLD[2], a frame count adjustment for base station allocation NBSADJ[2] and a delta frame count AN[2]. Column 1106 describes that request group 3 has a queue for uplink traffic, a current frame count N[3] of its -27 WO 2007/075814 PCT/US2006/048653 queue, a last reported frame count NRPTOLD[3], a frame count adjustment for base station allocation NBSADJ[3] and a delta frame count AN[3]. [00113] In some embodiments, the different request groups correspond to different types of traffic. For example, in one exemplary embodiment, request group 1 corresponds to control traffic, request group 2 corresponds to voice traffic, and request group 3 corresponds to data traffic. In another exemplary embodiment, request group 1 corresponds to voice traffic, request group 2 corresponds to other time sensitive traffic, e.g., gaming traffic, and request group 3 corresponds to relatively time insensitive traffic, e.g., traffic including data file transfer traffic. [00114] 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. [00115] 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, transmission backlog management, request group selection, report generation, etc.. 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). [00116] 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 28 WO 2007/075814 PCT/US2006/048653 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. WO 2007/075814 PCT/US2006/048653 WE CLAIM 1 1. A method of reporting transmission backlog information, the method comprising: 2 maintaining backlog information corresponding to a plurality of different transmission 3 request groups; and 4 selecting a request group from the plurality of different transmission request groups for 5 which backlog information is maintained, wherein said selecting is performed as a function of a 6 request group change in backlog with respect to previously reported backlog information after 7 taking into consideration changes in backlog due to base station allocation of transmission 8 resources. 1 2. The method of claim 1, wherein said selecting includes: 2 selecting, when at least one of the transmission request groups has a non-zero change in 3 backlog with respect to the last previously reported request report conveying that particular 4 request group's backlog information after taking into consideration changes in backlog due to 5 base station allocation of transmission resources, the request group having the highest priority 6 from among the request groups having a non-zero change in backlog with respect to the last 7 previously reported request report conveying that particular request group's backlog information 8 after taking into consideration changes in backlog due to base station allocation of transmission 9 resources. 1 3. The method of claim 1, 2 wherein said selected request group corresponds to one of a plurality of supported 3 reporting alternatives of an n-bit size request report format, different reporting alternatives 4 corresponding to different request groups; and 5 generating a n-bit size request report in accordance with said n-bit size request report 6 format and said reporting alternative corresponding to the selected request group. 1 '4. The method of claim 3, further comprising: 2 transmitting the generated n-bit size request report over a wireless communications link. 1 5. The method of claim 1, wherein selecting a request group from the plurality of different 2 transmission request groups for which backlog information is maintained, includes: WO 2007/075814 PCT/US2006/048653 3 selecting, when none of the individual request groups have a non-zero change in backlog 4 with respect to the last previously reported request report conveying that particular individual 5 request group's backlog information after taking into consideration changes in backlog due to 6 base station allocation of transmission resources, a request group from the plurality of request 7 groups according to a round robin selection process. 1 6. The method of claim 1, wherein selecting a request group from the plurality of different 2 transmission request groups for which backlog information is maintained, includes: 3 selecting, when none of the individual request groups has a non-zero change in backlog 4 with respect to the last previously reported request report conveying that particular individual 5 request group's backlog information after taking into consideration changes in backlog due to 6 base station allocation of transmission resources, a request group from the plurality of request 7 groups according to a prio'rity ordering selection process. 1 7. The method of claim 1, further comprising: 2 updating said maintained backlog information as a function of at least one of received 3 information to be transmitted, dropped information and transmitted information. 1 8. The method of claim 7, wherein each request group corresponds to a request group queue 2 used to store information to be transmitted. 1 9. The method of claim 1, wherein said selecting includes: 2 selecting, when at least one of the transmission request groups has a positive change in 3 backlog with respect to the last previously reported request report conveying that particular 4 request group's backlog information after taking into consideration changes in backlog due to 5 base station allocation of transmission resources, the request group having the highest priority 6 from among the request groups having a positive change in backlog with respect to the last 7 previously reported request report conveying that particular request group's backlog information 8 after taking into consideration changes in backlog due to base station allocation of transmission 9 resources. 1 10. The method of claim 1, wherein said selecting includes: WO 2007/075814 PCT/US2006/048653 2 selecting, when at least one of the transmission request groups has a positive backlog and 3 a non-negative change in backlog with respect to the last previously reported request report . 4 conveying that particular request group's backlog information after taking into consideration 5 changes in backlog due. to base station allocation of transmission resources, the request group 6 having the highest priority from among the request groups having a positive backlog and a non- 7 negative change in backlog with respect to the last previously reported request report conveying 8 that particular request group's backlog information after taking into consideration changes in 9 backlog due to base station allocation of transmission resources. 1 11. A wireless communications device, comprising: 2 a transmission backlog management module for maintaining backlog information 3 corresponding to a plurality of different transmission request groups; and 4 a selection module for selecting a request group from the plurality of different 5 transmission request groups for which backlog information is maintained, wherein said selecting 6 is performed as a function of a request group change in backlog with respect to previously 7 reported backlog information after taking into consideration changes in backlog due to base 8 station allocation of transmission resources. 1 12. The wireless communications device of claim 11, wherein said selecting includes: 2 selecting, when at least one of the transmission request groups has a non-zero change in 3 backlog with respect to the last previously reported request report conveying that particular 4 request group's backlog information after taking into consideration changes in backlog due to 5 base station allocation of transmission resources, the request group having the highest priority 6 from among the request groups having a non-zero change in backlog with respect to the last 7 previously reported request report conveying that particular request group's backlog information 8 after taking into consideration changes in backlog due to base station allocation of transmission 9 resources. 1 13. The wireless communications device of claim 11, further comprising: 2 memory including n-bit size request report format information, said n-bit size request 3 report format information supporting a plurality of reporting alternatives, different reporting 4 alternatives corresponding to different request groups; and 32 WO 2007/075814 PCT/US2006/048653 5 a report generation module for generating a n-bit size request report in accordance with 6 said n-bit size request report format and said reporting alternative corresponding to the selected 7 request group. 1 14. The wireless communications device of claim 13, further comprising: 2 a transmission module for transmitting the generated n-bit size request report over a 3 wireless communications link. 1 15. The wireless communications device of claim 11, wherein said selection module 2 includes a default selection module for selecting, a request group from the plurality of request 3 groups according to a round robin selection process, when none of the individual request groups 4 have a non-zero change in backlog with respect to the last previously reported request report 5 conveying that particular individual request group's backlog information after taking into 6 consideration changes in backlog due to base station allocation of transmission resources. 1 16. The wireless communications device of claim 11, wherein said selection module 2 includes a default selection module for selecting, a request group from the plurality of request 3 groups according to a priority ordering selection process when none of the individual request 4 groups has a non-zero change in backlog with respect to the last previously reported request 5 report conveying that particular individual request group's backlog information after taking into 6 consideration changes in backlog due to base station allocation of transmission resources. 1 17. The wireless communications device of claim 11, wherein the transmission backlog 2 management module includes: 3 a backlog update module for updating the maintained backlog information as a function 4 of at least one of received information to be transmitted, dropped information and transmitted 5 information. 1 18. The wireless communications device of claim 17, further including: 2 a plurality of request group queues used to store information to be transmitted, each 3 request group corresponding to a request group queue. 3 3 WO 2007/075814 PCT/US2006/048653 1 19- The wireless communications device of claim 15, wherein said wireless communications 2 device is a wireless terminal which is a hand held mobile communications device. 1 20. . The wireless communications device of claim 11, wherein said selecting includes: •2 - selecting, when at least one of the transmission request groups has a positive change in 3 backlog with respect to the last previously reported request report conveying that particular 4 request group's backlog information after taking into consideration changes in backlog due to 5 base station allocation of transmission resources, the request group having the highest priority 6 from among the request groups having a positive change in backlog with respect to the last 7 previously reported request report conveying that particular request group's backlog information 8 after taking into consideration changes in backlog due to base station allocation of transmission 9 resources. 1 21. The wireless communications device of claim 11, wherein said selecting includes: 2 selecting, when at least one of the transmission request groups has a positive backlog and 3 a non-negative change in backlog with respect to the last previously reported request report 4 conveying that particular request group's backlog information after taking into consideration 5 changes in backlog due to base station allocation of transmission resources, the request group 6 having the highest priority from among the request groups having a positive backlog and a non- 7 negative change in backlog with respect to the last previously reported request report conveying 8 . that particular request group's backlog information after taking into consideration changes in 9 backlog due to base station allocation of transmission resources. 1 22. A wireless communications device, comprising: 2 means for maintaining backlog information corresponding to a plurality of different 3 transmission request groups; and 4 means for selecting a request group from the plurality of different transmission request 5 groups for which backlog information is maintained, wherein said selecting is performed as a 6 function of a request group change in backlog with respect to previously reported backlog 7 information after taking into consideration changes in backlog due to base station allocation of 8 transmission resources. 1 .23. The wireless communications device of claim 22, wherein said selecting includes: 34. WO 2007/075814 PCT/US2006/048653 2 selecting, when at least one of the transmission request groups has a non-zero change 3 in backlog with respect to the last previously reported request report conveying that particular 4 request group's backlog information after taking into consideration changes in backlog due to 5 base station allocation of transmission resources, the request group having the highest priority 6 from among the request groups having a non-zero change in backlog with respect to the last 7 previously reported request report conveying that particular request group's backlog information 8 after taking into consideration changes in backlog due to base station allocation of transmission 9 resources. 1 24. The wireless communications device of claim 22, further comprising: 2 means for storing n-bit size request report format information, said n-bit size request 3 report format information supporting a plurality of reporting alternatives, different reporting 4 alternatives corresponding to different request groups; and 5 means for generating a n-bit size request report in accordance with said n-bit size request 6 report format and said reporting alternative corresponding to the selected request group. 1 25. The wireless communications device of claim 24, further comprising: 2 means for transmitting the generated n-bit size request report over a wireless 3 communications link. 1 26. The wireless communications device of claim 22, wherein said means for selecting a 2 request group includes means for selecting, a request group from the plurality of request groups 3 according to a round robin selection process, when none of the individual request groups have a 4 non-zero change in backlog with respect to the last previously reported request report conveying 5 that particular individual request group's backlog information after taking into consideration 6 changes in backlog due to base station allocation of transmission resources. 1 27. The wireless communications device of claim 22, wherein said means for selecting a 2 request group includes means for selecting, a request group from the plurality of request groups 3 according to a priority ordering selection process when none of the individual request groups has 4 a non-zero change in backlog with respect to the last previously reported request report 5 conveying that particular individual request group's backlog information after taking into 6 consideration changes in backlog due to base station allocation of transmission resources. 3 5 WO 2007/075814 PCT/US2006/048653 1 28. The wireless communications device of claim 22, wherein the means for maintaining 2 backlog information includes: 3 means for updating the riiaintained backlog information as a function of at least one of 4 received information to be transmitted, dropped information and transmitted information. 1 29. The wireless communications device of claim 28, further including: 2 means for storing a plurality of request group queues used to store information to be 3 transmitted^ each request group corresponding to a request group queue. 1 30. The wireless communications device of claim 22, wherein said wireless communications 2 device is a wireless terminal which is a hand held mobile communications device. 1 31. A computer readable mtfdmm embodying machine executable instruction for controlling 2 a wireless communications device to implement a method, the method comprising: 3 maintaining backlog information corresponding to a plurality of different transmission 4 request groups; and 5 selecting a request group from the plurality of different transmission request groups for 6 which backlog information is maintained, wherein said selecting is performed as a function of a 7 request group change in backlog with respect to previously reported backlog information after 8 taking into consideration changes in backlog due to base station allocation of transmission 9 resources. 1 32. The computer readable medium of claim 31, further embodying machine executable 2 instructions for: 3 . selecting, when at least one of the transmission request groups has a non-zero change in 4 backlog with respect to the last previously reported request report conveying that 5 particular request group'? backlog information after taking into consideration changes in 6 backlog due to base station allocation of transmission resources, the request group 7 having the highest priority from among the request groups having a non-zero change in : 8 backlog with respect to the last previously reported request report conveying that 9 particular request groups backlog information after taking into consideration changes in 10 backlog due to base station allocation of transmission resources, as part of said step of WO 2007/075814 PCT/US2006/048653 1 selecting a request group from the plurality of different transmission request groups for 2 which backlog information is maintained. 1 33. The computer readable medium of claim 31, 2 wherein said selected request group corresponds to one of a plurality of supported 3 reporting alternatives of an n-bit size request report format, different reporting alternatives 4 corresponding to different request groups, the computer readable medium further embodying 5 machine executable instructions for: 6 generating a n-bit size request report in accordance with said n-bit size request report 7 format and said reporting alternative corresponding to the selected request group. 1 34. The computer" readable medium of claim 33, further embodying machine executable 2 instructions for: 3 controlling transmission of the generated n-bit size request report over a wireless 4 communications link. 1 35. The computer readable medium of claim 31, further embodying machine executable 2 instructions for: 3 selecting, when none of the individual request groups have a non-zero change in backlog 4 with respect to the last previously reported request report conveying that particular individual 5 request group's backlog information after taking into consideration changes in backlog due to 6 base station allocation of transmission resources, a request group from the plurality of request 7 groups according to a round robin selection process as part of said step of selecting a request 8 group from the plurality of different transmission request groups for which backlog information 9 is maintained. 1 36. The computer readable medium of claim 31, further embodying machine executable 2 instructions for: 3 selecting, when none of the individual request groups have a non-zero change in backlog 4 with respect to the last previously reported request report conveying that particular individual 5 request group's backlog information after taking into consideration changes in backlog due to 6 base station allocation of transmission resources, a request group from the plurality of request •7 groups according to a priority ordering selection process as part of said step of selecting a 37 WO 2007/075814 PCT/US2006/048653 1 request group from the plurality of different transmission request groups for which backlog 2 information is maintained. 1 37. A device comprising: 2 a processor configured to: 3 maintain backlog information corresponding to a plurality of different 4 transmission request groups; and 5 select a request group from the plurality of different transmission request 6 groups for which backlog information is maintained, wherein said selecting is performed as a 7 function of a request group change in backlog with respect to previously reported backlog 8 information after taking into consideration changes in backlog due to base station allocation of 9 transmission resources. 1 38. The device of claim 37, wherein said processor is further configured to: 2 select, when at least one of the transmission request groups has a non-zero change in 3 . backlog with respect to the last previously reported request report conveying that 4 particular request group's backlog-information after taking into consideration changes in 5 backlog due to base station allocation of transmission resources, the request group 6 having the highest priority from among the request groups having a non-zero change in 7 backlog with respect to the last previously reported request report conveying that 8 particular request group's backlog information after taking into consideration changes in 9 backlog due to base station allocation of.transmission resources. 1 39. The device of claim 37, 2 wherein said selected request group corresponds to one of a plurality of supported 3 reporting alternatives of an n-bit size request report format, different reporting alternatives 4 corresponding to different request groups, and wherein the processor is further configured to: 5 generate a n-bit size request report in accordance with said n-bit size request 6 report format and said reporting alternative corresponding to the selected request group. 1 40. The device of claim 39, wherein said processor is further configured to: 2 control transmission of the generated n-bit size request report over a wireless 3 communications link. - 38 WO 2007/075814 PCT/US2006/048653 1 41. ; The device of claim 37, wherein said processor is further configure to: 2 select, when none of the individual request groups have a non-zero change in backlog 3 with respect, to the last previously reported request report conveying that particular individual 4 request group's backlog information after taking into consideration changes in backlog due to 5 base station allocation of transmission resources, a request group from the plurality of request 6 groups according to a round robin selection process. 1 42. The device of claim 37, wherein said processor is further configure to: 2 select, when none of the individual request groups have a non-zero change in backlog 3 with respect to the last previously reported request report conveying that particular individual 4 request group's backlog information after taking into consideration changes in backlog due to 5 base station allocation of transmission resources, a request group from the plurality of request 6 groups according to a priority ordering selection process. Dated this 4th day of June 2008 39

Documents:

1162-mumnp-2008 abstract.doc

1162-mumnp-2008 claims.doc

1162-mumnp-2008 description(complete).doc

1162-mumnp-2008 form 2.doc

1162-MUMNP-2008-ABSTRACT(15-5-2013).pdf

1162-mumnp-2008-abstract.pdf

1162-MUMNP-2008-CLAIMS(AMENDED)-(20-5-2013).pdf

1162-MUMNP-2008-CLAIMS(MARKED COPY)-(20-5-2013).pdf

1162-MUMNP-2008-Claims-161214.pdf

1162-mumnp-2008-claims.pdf

1162-MUMNP-2008-COPY OF ASSIGNMENT(27-8-2008).pdf

1162-MUMNP-2008-CORRESPONDENCE(11-11-2014).pdf

1162-MUMNP-2008-CORRESPONDENCE(14-5-2013).pdf

1162-MUMNP-2008-CORRESPONDENCE(18-3-2014).pdf

1162-MUMNP-2008-CORRESPONDENCE(2-4-2014).pdf

1162-MUMNP-2008-CORRESPONDENCE(25-11-2008).pdf

1162-MUMNP-2008-CORRESPONDENCE(26-11-2008).pdf

1162-MUMNP-2008-CORRESPONDENCE(27-3-2014).pdf

1162-MUMNP-2008-CORRESPONDENCE(27-8-2008).pdf

1162-MUMNP-2008-CORRESPONDENCE(3-6-2013).pdf

1162-MUMNP-2008-CORRESPONDENCE(5-12-2014).pdf

1162-MUMNP-2008-CORRESPONDENCE(8-5-2014).pdf

1162-mumnp-2008-correspondence.pdf

1162-mumnp-2008-description(complete).pdf

1162-MUMNP-2008-DRAWING(15-5-2013).pdf

1162-MUMNP-2008-DRAWING(9-6-2008).pdf

1162-mumnp-2008-drawing.pdf

1162-MUMNP-2008-FORM 1(15-5-2013).pdf

1162-mumnp-2008-form 1.pdf

1162-MUMNP-2008-FORM 13(15-5-2013).pdf

1162-mumnp-2008-form 18.pdf

1162-MUMNP-2008-FORM 2(TITLE PAGE)-(15-5-2013).pdf

1162-mumnp-2008-form 2(title page).pdf

1162-mumnp-2008-form 2.pdf

1162-MUMNP-2008-FORM 26(14-5-2013).pdf

1162-MUMNP-2008-FORM 26(15-5-2013).pdf

1162-MUMNP-2008-FORM 3(15-5-2013).pdf

1162-MUMNP-2008-FORM 3(25-11-2008).pdf

1162-MUMNP-2008-FORM 3(3-6-2013).pdf

1162-mumnp-2008-form 3.pdf

1162-MUMNP-2008-FORM 5(15-5-2013).pdf

1162-mumnp-2008-form 5.pdf

1162-mumnp-2008-form-pct-ib-304.pdf

1162-mumnp-2008-form-pct-isa-210.pdf

1162-MUMNP-2008-Marked copy-161214.pdf

1162-MUMNP-2008-OTHER DOCUMENT(15-5-2013).pdf

1162-MUMNP-2008-OTHER DOCUMENT-(15-5-2013).pdf

1162-MUMNP-2008-OTHERS-161214.pdf

1162-MUMNP-2008-PETITION UNDER RULE 137(3-6-2013).pdf

1162-MUMNP-2008-PETITION UNDER RULE-137(15-5-2013).pdf

1162-MUMNP-2008-Power of Attorney-161214.pdf

1162-MUMNP-2008-REPLY TO EXAMINATION REPORT(15-5-2013).pdf

1162-MUMNP-2008-REPLY TO EXAMINATION REPORT(20-5-2013).pdf

1162-mumnp-2008-wo-international publication report a3.pdf

abstract1.jpg