Patent Grant
9462604
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.
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.
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 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.
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.
Various embodiments are directed to reporting transmission backlog information. In 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.
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 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.
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.
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.
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 nodes which may move throughout the communication system. In
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.
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.
Transmitter module 204, e.g., an OFDM transmitter, is coupled to transmit antenna 205 via which the wireless terminal transmits uplink signals 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 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.
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.
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).
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.
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.
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 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.
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.
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 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 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.
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.
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 change in backlog with respect to the last previously reported request reports conveying that particular individual request group's backlog information after taking into consideration changes in backlog due to base station allocation of transmission resources.
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.
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
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.
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.
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.
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 m 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 information 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[1] 262, and delta frame counts ΔN[1] 264. Request group m queue statistics information 250 includes frame counts N[m] 266, and delta frame counts ΔN[m] 269.
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.
Request groups communication queues (request group 1 communication queue 240, . . . request group m communication queue 242) are a plurality of communication queues for 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 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 backlog, (N[1] 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, (ΔN[1] 264, . . . , ΔN[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., ΔN[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 consideration 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.
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 m 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.
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.
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
Scheduler module 324 schedules uplink and downlink traffic channel segments to wireless terminals. For example, scheduler module 324 schedules uplink traffic channel 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 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.
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.
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 counts with regard to one or more of request group information sets, e.g., (request group 1 information 346, . . . , request group m information 348).
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.
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 1338, . . . , 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.
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.
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.
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.
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 C selection method 418).
In alternative A selection method 414 (See
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.
In alternative B selection method 416 (See
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 a priority ordering selection process.
In alternative C selection method 418 (See
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.
Returning to
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.
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.
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 (RG1, RG2, RG3) corresponds to a request group queue used to store information to be transmitted e.g., uplink traffic to be transmitted. Backlog information 505 includes, e.g., frames counts of backlog to be transmitted, e.g., MAC frames of backlog, corresponding the request groups where N[1] 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: ΔN[1] corresponding to RG1, ΔN[2] corresponding to RG2, and ΔN[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.
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.
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
Exemplary alternative 1 report selection subroutine of
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 ΔN[1] is not 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.
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 ΔN[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.
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 ΔN[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.
In step 530, operation is directed to a default selection subroutine. Flowchart 531 of
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.
Exemplary alternative 2 report selection subroutine of
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 ΔN[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.
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 ΔN[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 517 to step 521.
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 ΔN[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.
In step 527, operation is directed to a default selection subroutine. Flowchart 531 of
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.
Exemplary alternative 3 report selection subroutine of
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[1] is greater than 0 and ΔN[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.
In step 541, 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 ΔN[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.
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 that N[3] is greater than 0 and ΔN[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.
In step 551, operation is directed to a default selection subroutine. Flowchart 531 of
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 555. In step 555, the report selection subroutine ends and the subroutine returns an identified selected request, group or an indication of no backlog.
The exemplary method of default selection subroutine (alternative A) of flowchart 531 of
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 for step 544 step 546, where the communication device selects RG2 as the selected request group.
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 RG1, RG2 and RG3.
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.
The exemplary method of default selection subroutine (alternative B) of flowchart 533 of
Operation proceeds from step 562 to step 564. In step 564, it is determined whether the stored last selected request group was RG1. If it is determined in step 564, that the stored last selected request group is RG1, then operation proceeds to step 566, where the subroutine selects RG2 as the selected request group; otherwise operation proceeds to step 568.
In step 568, it is determined whether the stored last selected request group was RG2. If it is determined in step 568, 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 RG1 as the selected request group, since by default RG3 was the stored last selected request group.
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 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.
Returning to
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.
Operation proceeds front 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.
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.
The exemplary dedicated control channel is subdivided into 31 logical tones (uplink tone index 81606, uplink tone index 82608, . . . , uplink tone index 111610). 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 (612, 614, 616, 618, 620, 622, . . . , 624). 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 628; each of the eight superslots of 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 [1][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]).
In this example each segment, e.g., segment [0][0], comprises one tone for 3 successive half-slots, e.g., representing an allocated uplink 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 (606, 608, . . . , 610) may be currently assigned to (WT A 630, WT B 632, . . . , WT N′ 634), 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 700 of
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 at delta frame count ΔN[2]. Column 1106 describes that request group 3 has a queue for uplink traffic, a current frame count N[3] of its queue, a last reported frame count NRPTOLD[3], a frame count adjustment for base station allocation NBSADJ[3] and a delta frame count ΔN[3].
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.
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, 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).
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 for patent is a Continuation-in-Part of 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”, pending, which claims priority to Provisional Application No. 60/752,973, filed on Dec. 22, 2005, titled “COMMUNICATIONS METHODS AND APPARATUS”, and assigned to the assignee hereof and 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 |
| 5491837 | Haartsen | Feb 1996 | 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 et al. | Feb 2000 | A |
| 6028842 | Chapman et al. | Feb 2000 | A |
| 6028843 | Delp et al. | Feb 2000 | A |
| 6035000 | Bingham et al. | 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 |
| 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 et al. | 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 |
| 6889257 | Patel | May 2005 | B1 |
| 6892071 | Park et al. | May 2005 | B2 |
| 6895005 | Malin et al. | May 2005 | B1 |
| 6895364 | Banfer | May 2005 | B2 |
| 6901268 | Chang et al. | 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 et al. | Oct 2005 | B2 |
| 6957072 | Kangras et al. | Oct 2005 | B2 |
| 6967937 | Gormley | Nov 2005 | B1 |
| 6968156 | Sugaya et al. | Nov 2005 | B2 |
| 7006841 | Monogioudis 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 et al. | 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 et al. | 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 | May 2007 | B2 |
| 7218948 | Laroia et al. | May 2007 | B2 |
| 7245935 | Lin | Jul 2007 | B2 |
| 7260054 | Olszewski et al. | 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 |
| 7430206 | Terry et al. | Sep 2008 | B2 |
| 7430207 | Wu et al. | Sep 2008 | B2 |
| 7430420 | Derakhshan et al. | Sep 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 |
| RE43593 | Kayama et al. | Aug 2012 | E |
| 8325621 | Simonsson et al. | Dec 2012 | B2 |
| 20010007552 | Schiff et al. | Jul 2001 | A1 |
| 20010036181 | Rogers | Nov 2001 | A1 |
| 20010046878 | Chang et al. | Nov 2001 | A1 |
| 20010055293 | Parsa et al. | Dec 2001 | A1 |
| 20020012326 | Chang et al. | Jan 2002 | A1 |
| 20020031105 | Zeira et al. | Mar 2002 | A1 |
| 20020037729 | Kitazawa et al. | Mar 2002 | A1 |
| 20020045448 | Park et al. | Apr 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 et al. | Sep 2002 | A1 |
| 20020142788 | Chawla et al. | Oct 2002 | A1 |
| 20020143858 | Teague et al. | Oct 2002 | A1 |
| 20020147017 | Li et al. | Oct 2002 | A1 |
| 20020160802 | Hiramatsu et al. | Oct 2002 | A1 |
| 20020177452 | Ruutu et al. | Nov 2002 | A1 |
| 20020186678 | Averbuch et al. | Dec 2002 | A1 |
| 20030003921 | Laakso et al. | Jan 2003 | A1 |
| 20030007498 | Angle et al. | Jan 2003 | A1 |
| 20030012212 | Earnshaw et al. | Jan 2003 | A1 |
| 20030016641 | Terry et al. | Jan 2003 | A1 |
| 20030027587 | Proctor, Jr. et al. | 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 et al. | Nov 2003 | A1 |
| 20030223354 | Olszewski et al. | 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 |
| 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 et al. | Dec 2004 | A1 |
| 20040248568 | Lucidarme et al. | Dec 2004 | A1 |
| 20040252647 | Chang et al. | Dec 2004 | A1 |
| 20040252662 | Cho et al. | 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 et al. | Dec 2004 | A1 |
| 20050003847 | Love et al. | Jan 2005 | A1 |
| 20050008892 | Yamamoto et al. | Jan 2005 | A1 |
| 20050047344 | Seol et al. | Mar 2005 | A1 |
| 20050047393 | Liu et al. | Mar 2005 | A1 |
| 20050047416 | Heo et al. | Mar 2005 | A1 |
| 20050053099 | Spear et al. | Mar 2005 | A1 |
| 20050058637 | Lynn 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 |
| 20050118993 | Roux et al. | Jun 2005 | A1 |
| 20050122900 | Tuulos et al. | Jun 2005 | A1 |
| 20050128999 | Kwon et al. | Jun 2005 | A1 |
| 20050135320 | Tiedemann 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 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 |
| 20050207373 | Roy et al. | Sep 2005 | A1 |
| 20050220052 | Uehara et al. | Oct 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 et al. | 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 |
| 20060256747 | Jaakkola | Nov 2006 | A1 |
| 20060270399 | Qi et al. | 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 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 et al. | 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 |
| 20070149131 | Li et al. | Jun 2007 | A1 |
| 20070149132 | Li et al. | Jun 2007 | A1 |
| 20070149137 | Richardson et al. | Jun 2007 | A1 |
| 20070149138 | Das et al. | 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 |
| 20070177510 | Natarajan et al. | Aug 2007 | A1 |
| 20070183308 | Korobkov 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 |
| 20070253358 | Das et al. | Nov 2007 | A1 |
| 20070253385 | Li et al. | Nov 2007 | A1 |
| 20070253449 | Das 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 |
| 20080212524 | Niwano | Sep 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 |
| 20090252122 | Leinonen et al. | Oct 2009 | A1 |
| 20090303900 | Cho et al. | Dec 2009 | A1 |
| 20100177731 | Ananthaiyer et al. | Jul 2010 | 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 |
| 20150333948 | Richardson | Nov 2015 | A1 |
| 20150334590 | Das | Nov 2015 | A1 |
| Number | Date | Country |
|---|---|---|
| 3603-2006 | Dec 2006 | CL |
| 3604-2006 | Dec 2006 | CL |
| 3605-2006 | Dec 2006 | CL |
| 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 |
| 1338878 | Mar 2002 | CN |
| 1507708 | Jun 2004 | CN |
| 1545252 | Nov 2004 | CN |
| 1604685 | Apr 2005 | CN |
| 1 684457 | Oct 2005 | CN |
| 10162564 | Jul 2003 | DE |
| 1037419 | Sep 2000 | EP |
| 1037491 | Sep 2000 | EP |
| 1 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 |
| 1 594 260 | Nov 2005 | EP |
| 1758276 | Feb 2007 | EP |
| 1841259 | Oct 2007 | EP |
| 2340693 | Feb 2000 | GB |
| 8008806 | 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 |
| 2006518578 | Aug 2006 | JP |
| 06268574 | Oct 2006 | JP |
| 2006524966 | Nov 2006 | JP |
| 2006526323 | Nov 2006 | JP |
| 2007503156 | Feb 2007 | JP |
| 2007509531 | Apr 2007 | JP |
| 2007514364 | May 2007 | JP |
| 2007514378 | May 2007 | JP |
| 2007521685 | Aug 2007 | JP |
| 2007522692 | Aug 2007 | JP |
| 2007525044 | Aug 2007 | JP |
| 2007525045 | Aug 2007 | JP |
| 2011045054 | Mar 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 |
| 200539627 | Dec 2005 | 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 |
| WO-0001188 | Jan 2000 | 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 |
| 2008084503 | Sep 2004 | WO |
| WO2004084452 | Sep 2004 | WO |
| WO-2004084575 | Sep 2004 | WO |
| 2004100450 | Nov 2004 | WO |
| WO-2004098072 | Nov 2004 | WO |
| 2004110081 | Dec 2004 | WO |
| WO2004105420 | Dec 2004 | WO |
| 2005018115 | Feb 2005 | WO |
| 2005020490 | Mar 2005 | WO |
| WO2005034438 | Apr 2005 | WO |
| 2005050132 | Jun 2005 | WO |
| 2005060132 | Jun 2005 | WO |
| WO2005057812 | Jun 2005 | WO |
| WO2005060271 | Jun 2005 | WO |
| WO2005060277 | Jun 2005 | WO |
| 05065056 | Jul 2005 | WO |
| 2005065056 | Jul 2005 | WO |
| WO2005065056 | Jul 2005 | WO |
| WO2005069519 | Jul 2005 | WO |
| 2005107311 | Nov 2005 | WO |
| WO2005125049 | Dec 2005 | WO |
| WO2006044718 | Apr 2006 | WO |
| 2006075293 | Jul 2006 | WO |
| 2007031956 | Mar 2007 | WO |
| Entry |
|---|
| 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 of 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. |
| Written Opinion—PCT/US06/048653, 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, IEEE, New York, NY USA (Apr. 28, 2002). |
| 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. |
| 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. |
| Supplementary European Search Report—EP04713438, Search Authority—The Hague Patent Office, Nov. 30, 2010. |
| 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 JP200106152 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, WO9845967, EP1377100, US5867478, US20010007552, US6035000 and US5933421 dated Dec. 9, 2010. |
| 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. |
| 3GPP: ETSI TS 125 331 V6.3.0: Radio Resource Control (RRC) protocol specification (3GPP TS 25.331 version 6.3.0 Release 6), ETSI TS 125 331, Sep. 1, 2004, pp. 49, 202-209, 220,221,406,579-585, 589, 930. |
| Ericsson: Discussion on SIR Measurement, TSG-RAN Working Group 4 (Radio) meeting #18, Berlin, Germany, 3GPP TS 25.101 V3.7.0, Jul. 9, 2001, R4-010895, URL: http://www.3gpp.org/ftp/tsg—ran/WG4—Radio/TSGR4—18/Docs/R4-010895.zip. |
| European Search Report—EP11165270, Search Authority—Berlin Patent Office, Jun. 6, 2011. |
| Qualcomm, Scheduling Information Contents, #3GPP TSG-RAW WG2 meeting #48,3GPP, Aug. 29, 2005, R2-051957, URL: http://3gpp.org/ftp/tsg—ran/WG2—RL2/TSGR2—48/Docments/R2-095517.zip. |
| Sumsung, EDCH Buffer Status Reporting. 3GPP TSG RAN2#45bis, 3GPP, Jan. 10, 2005, R2-050026, URL: http://www.3gpp.org/ftp/tsg—ran/WG2—RL2/TSGR2—45bis/Dcs/R2-050026.zip. |
| Sumsung, Uplink control signaling structure (Revision of R1-041086), 3GPP TSG-RAN WG1 Meeting #38bis, 3GPP, Sep. 20, 2004, R1-041222, 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,3GPP, May 21, 2001, R4-010647, URL: http://www.3gpp.org/ftp/tsg—ran/WG4—Radio/TSGR4—17/Docs/R4-010647.Zip. |
| 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%20Transmit%20Power%20Issues%20in%20a%20WCDMA%20Cellular%20System.pdf. |
| 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. |
| 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/tsg—ran/WG2—RL2/TSGR2—46bis/Documents/R2-050852.zip. |
| Taiwan Search Report—TW095148259—TIPO—Nov. 6, 2012. |
| 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-Oct. 20, 2004, pp. 654-658. |
| Kwon, at 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-5121. |
| Majmundar, “Impact of Mobile-Orignated 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, lEEE, Sep. 24, 2000, pp. 1550-1555. |
| International Search Report—PCT/US06/048653, International Search Authority—European Patent Office, Mar. 27, 2008. |
| Number | Date | Country | |
|---|---|---|---|
| 20070253357 A1 | Nov 2007 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60752973 | Dec 2005 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 11333792 | Jan 2006 | US |
| Child | 11609627 | US |
