Methods, wireless communications apparatus, machine-readable mediums, and processors for efficiently providing and obtaining scheduling information

Method, wireless communication device, machine-readable medium, and processor for efficiently providing and obtaining scheduling information

The following description is generally about wireless communication, and more specifically, about efficiently providing scheduling information to a central scheduler in a wireless communication system.

Wireless communication systems are widely used to provide various types of communication. For example, voice and/or data can be provided via these wireless communication systems. A typical wireless communication system or network can provide multiple users with access to one or more shared resources. For example, the system may use various multiple access technologies, such as frequency division multiplexing (FDM), time division multiplexing (TDM), code division multiplexing (CDM), orthogonal frequency division multiplexing (OFDM), and others.

Common wireless communication systems use one or more base stations that provide a coverage area. A typical base station can transmit multiple data streams for broadcast, multicast, and/or unicast services. The data stream can be a data stream that has independent reception benefits for user equipment. The user equipment in the coverage area of this base station can be used to receive one, more than one, or all data streams carried by the composite stream. Similarly, the user equipment can transmit data to the base station or another user equipment.

The base station can schedule the reverse link communication transmitted from the user equipment to the base station. For example, when using Orthogonal Frequency Division Multiplexing (OFDM), the base station can complete scheduling decisions regarding reverse link communication (for example, allocating resources such as time, frequency, power, etc. to one or moreDevice), and therefore, the base station can help maintain orthogonality. However, the conventional technique of providing scheduling information from the user equipment to the base station can be inefficient, time-consuming, and difficult. In addition, scheduling information may not be provided to the central scheduler (e.g., base station) from time to time. For example, early voice cellular systems generally use circuit-switched scheduling, in which each user can be assigned a dedicated circuit-switched channel within the duration of a call; in this case, the collection of scheduling information can be very Occurs at a low rate and the information can be sent as a high-level data packet. In addition, data-based systems (Data Only, DO) usually use signal transport layer protocols for high-level data packets. In addition, DO rev A often enables access terminals to make scheduling decisions in a distributed manner. However, this distributed scheduling can inhibit the ability to maintain orthogonality associated with reverse link communication.

The following introduces a brief summary of one or more embodiments in order to provide a basic understanding of these embodiments. This summary is not an extensive overview of all the embodiments covered, and it is neither intended to identify the key or critical elements of all embodiments nor limit the scope of any or all embodiments. Its sole purpose is to introduce some concepts of one or more embodiments in a simplified form as a prelude to the more detailed description that will be introduced later.

According to one or more embodiments and the corresponding disclosures, various aspects related to the efficient provision of scheduling information from the access terminal to the base station so that the scheduling decision can be completed are described. The access terminal can transmit scheduling information in the fork request. For example, a dedicated out-of-band channel can be used to transmit rough scheduling information, and an in-band channel can be used to transmit precise scheduling information.

According to relevant aspects, this article describes a method that helps to efficiently provide scheduling information to the central scheduler. The method may include transmitting rough scheduling information to the base station via an out-of-band channel. In addition, the method includes transmitting precise scheduling information to the base station via an in-band channel.

Another aspect relates to a wireless communication device, which may include a memory for storing data related to scheduling information. In addition, the processor can transmit the rough scheduling information to the base station via the out-of-band channel and can transmit the precise scheduling information to the base station via the in-band channel.

Another aspect relates to a wireless communication device for efficiently transmitting scheduling information to a central scheduler to help allocate in-band resources. The wireless communication device may include means for transmitting rough information via the out-of-band channel; means for obtaining an assignment for reverse link communication associated with the rough scheduling information; and means for passing the in-band channel based on the assignment The component that transmits detailed scheduling information.

Another aspect relates to a machine-readable medium on which is stored machine executable instructions for transmitting rough scheduling information to the base station via an out-of-band channel and transmitting precise scheduling information to the base station via an in-band channel.

According to another aspect, a processor is described herein, where the processor can execute instructions for transmitting coarse scheduling information on a dedicated out-of-band channel. In addition, the processor can execute instructions for transmitting precise scheduling on the assigned in-band channel.

According to another aspect, this article describes a method that helps to efficiently obtain scheduling information. The method may include receiving an out-of-band transmission including rough scheduling information. In addition, the method may include transmitting a resource assignment based on rough scheduling information. In addition, the method may include receiving an in-band transmission provided based on the resource assignment, the in-band transmission including precise scheduling information.

Another aspect relates to a wireless communication device, which may include a memory that stores information about the allocation of resources associated with reverse link communication. In addition, a processor may be able to obtain rough scheduling data, allocate resources based on the rough scheduling data, receive precise scheduling data, and/or dynamically adjust resource allocation based on the precise scheduling data.

Another aspect relates to a wireless communication device for efficiently receiving scheduling information so as to allocate in-band resources. The wireless communication device may include means for obtaining rough schedule information via an out-of-band channel, means for sending a resource assignment based on the rough schedule information, and means for obtaining data via an in-band channel completed by using the resource assignment. A component for obtaining precise scheduling information.

Another aspect relates to a machine-readable medium on which is stored for receiving out-of-band transmission including rough scheduling information; transmitting a resource assignment based on the rough scheduling information; and receiving the precise information provided based on the resource assignment. Machine executable commands transmitted in-band of scheduling information.

According to another aspect, a processor is described herein, wherein the processor is executable for receiving coarse scheduling information via an out-of-band channel, transmitting a resource assignment based on the coarse scheduling information, and receiving fine scheduling information via an in-band channel The command of the precise scheduling information is provided based on the resource assignment.

In order to accomplish the foregoing and related objectives, one or more embodiments include features fully described below and clearly indicated in the scope of the patent application. The following description and accompanying drawings detail certain illustrative aspects of one or more embodiments. However, these aspects only indicate a few of the various ways in which the principles of the various embodiments can be used, and the described embodiments are intended to include all these aspects and their equivalents.

Various embodiments are now described with reference to the drawings, in which the same reference numbers are used throughout the text to denote the same elements. In the following description, for explanatory purposes, many specific details are set forth in order to provide a thorough understanding of one or more embodiments. However, it is obvious that the embodiment(s) can be practiced without such special details. In other instances, well-known structures and devices are shown in block diagram form to help describe one or more embodiments.

As used in this application, the terms "component", "module", "system" and the like are intended to refer to computer-related entities, which can be hardware, firmware, a combination of hardware and software, software or Running software. For example, the component may be, but is not limited to, a process running on a processor, a processor, an object, an executable instruction, an execution thread, a program, and/or a computer. For example, an application program running on a computer device and the computer device may both be a component. One or more components can reside in a process and/or thread of execution and a component can be located on a computer and/or distributed between two or more computers. In addition, these components can be executed from various computer-readable media on which various data structures are stored. A component can be based on, for example, a signal with one or more data packets (for example, data from a component that interacts with another component in a local system, a distributed system, and/or via the signal in a network such as the Internet It communicates with other systems on the network via local and/or remote processing.

In addition, various embodiments related to user terminals are described herein. The user terminal may be a device that provides voice and/or data connectivity to the user. The user terminal can be connected to a computing device such as a laptop or desktop computer, or it can be a self contained device such as a personal digital assistant (PDA). User terminal can also be called system, user unit, user station, mobile station, mobile remote station, access point, remote terminal, access terminal, user terminal, user agent, user equipment , Or user equipment. User terminals can be user stations, wireless devices, cellular phones, PCS phones, cordless phones, conversation initiation protocol (SIP) phones, wireless zone loop (WLL) stations, personal digital assistants (PDA), and have wireless connection capabilities The handheld device, or other processing equipment connected to the wireless modem.

A base station (for example, an access point) can refer to a device that communicates with a user terminal via one or more zones on an air-interface in an access network. The base station can act as a router between the user terminal and the rest of the access network by converting the received air interface frame into an IP packet, and the access network can include an IP network. The base station also coordinates the management of the attributes of the air interface.

In addition, the various aspects or features described herein can be implemented as methods, devices, or manufactured articles using standard programs and/or engineering techniques. The term "article of manufacture" as used herein is intended to include a computer program accessible from any computer-readable device, carrier or medium. For example, computer-readable media include, but are not limited to, magnetic storage devices (for example, hard disks, floppy disks, magnetic stripes, etc.), optical discs (for example, compact discs (CD), digital versatile discs (DVD), etc.) ), smart cards, and flash memory devices (for example, EPROM, cards, sticks, key drivers, etc.). In addition, the various storage media described herein may represent one or more devices and/or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and/or carrying instructions and/or data.

Referring now to FIG. 1, a wireless communication system 100 is illustrated according to various embodiments described herein. The system 100 may include one or more base stations 102 in one or more zones, which receive, transmit, and repeat wireless communication signals to each other and/or to one or more access terminals (AT) 104. Those familiar with the technology should understand that each base station 102 may include a transmitter chain and a receiver chain, and each of them may include a plurality of components associated with signal transmission and reception (for example, processors, Modulator, multiplexer, demodulator, demultiplexer (demultiplexer), antenna, etc.). The base station 102 can be a fixed station and/or a mobile station, and can also be referred to as an access point, a basic transceiver system, and the like. The access terminal 104 may be, for example, a cellular phone, a smart phone, a laptop computer, a palm-type communication device, a palm-type computing device, a satellite radio, a global positioning system, a PDA, and/or a wireless communication system 100. Any other suitable equipment for communication. The access terminal 104 may be fixed or mobile and may also be referred to as a mobile station, user equipment (UE), user terminal, wireless device, mobile phone, and so on.

Each access terminal 104 can communicate with one or more base stations 102 on the forward link and/or reverse link at any given instant. The forward link (FL) refers to the communication link from the base station 102 to the access terminal 104, and the reverse link (RL) refers to the communication link from the access terminal 104 to the base station 102. The base station 102 can further communicate with an operation and management center 106 via a data network 108 (for example, the Internet). The operation and management center 106 can perform functions such as authentication and authorization of the access terminal 104, billing, and billing.

The system 100 can provide scheduling information from the access terminal 104 to the base station 102 in an effective manner. This information can be used by base station 102 to schedule reverse link communications. By using the central scheduler associated with the base station 102, the orthogonality between the transmissions occurring within the system 100 can be maintained.

The system 100 completes the effective transmission of scheduling information by using a fork request from the access terminal 104 to the base station 102. For example, rough scheduling information can be transmitted through out-of-band signal transmission and more detailed scheduling information can be provided through in-band signal transmission. For example, the rough information can be transmitted to the base station 102 via a dedicated channel. For example, the rough information may include data related to the buffer level of the access terminal 104, the quality of service (QoS) associated with the access terminal 104, and the like. According to another example, detailed scheduling information may be included as a header, which is transmitted with an access terminal 104 after receiving an assignment from a base station 102 in response to a rough, out-of-band scheduling request Is associated with the data packet. The access terminal 104 can transmit packets on the reverse link according to this assignment, and the packet(s) can include additional scheduling information that can be used by the base station 102. According to an example, the rough information may indicate a range including the number of bits that must be transmitted by the access terminal 104, such as greater than 1000 bits, greater than 0 bits but less than 1000 bits, or 0 bits, and The detailed scheduling information can describe the number of bits to be transmitted with an accuracy of up to 1 bit. Additionally or otherwise, the rough information may be a QoS flow priority 1 with at least 1000 bits to be sent, and the detailed scheduling information may be the number of bits in each non-empty QoS flow with a certain accuracy.

Referring to FIG. 2, a system 200 that efficiently provides information to the base station 202 to facilitate scheduling associated with reverse link communication is illustrated. The system 200 may include any number of access terminals, such as access terminal 1 204 and access terminal 2 206. The base station 202 can use a packet-based central scheduler for the reverse link. In addition, the base station 202 can gather information to make an assignment, determine the resource allocation to each access terminal 204-206, and transmit the assignment to the access terminal 204-206.

The access terminals 204-206 will efficiently provide information about the schedule to the base station 202. Each access terminal 204-206 can transmit rough information to the base station 202 in a dedicated out-of-band channel. Similarly, the access terminals 204-206 can send more precise information about the schedule to the base station 202. For example, more precise information can be appended to the data packet transmitted to the base station 202 according to resource assignment (eg, scheduled time, assigned subcarriers, packet format, etc.). Therefore, additional scheduling information can be provided through in-band communication completed with assigned resources.

Access terminals 204-206 can transmit any information used in conjunction with scheduling. For example, the information can include the buffer size of the access terminal, the queue-latency measurement for quality of service (QoS) purposes, the buffer size of multiple QoS, and the latency of the line packet (head of line packet latency), access terminal power control parameters (such as transmission power or transmission power spectral density, maximum power limit) and so on. Each access terminal 204-206 can transmit rough information in a dedicated out-of-band channel. For example, the rough information may include a 2-bit buffer level and a 2-bit QoS level; however, the claimed subject matter is not limited to this. For example, a dedicated channel can be used to obtain a data channel; therefore, a request can be transmitted to the base station 202 via a dedicated out-of-band channel so as to be able to receive an in-band data channel assignment. According to another example, after scheduling an access terminal (for example, access terminal 1 204), the access terminal can transmit in-band precision information according to the resource assignment obtained in response to the out-of-band transmission. Additionally or otherwise, the scheduled access terminal (e.g., access terminal 1 204) can transmit any different data via the scheduled in-band channel.

Turning to FIG. 3, it illustrates a system 300 for transmission bifurcation of requests for assigning resources associated with the reverse link. Although a base station 302 and an access terminal 304 are described, it should be understood that the system 300 can include any number of base stations and any number of access terminals. The access terminal 304 can efficiently provide requests to the base station 302. The base station 302 may further include a central scheduler 306 that assigns resources to the access terminal 304 (and/or any different access terminal similar to the access terminal 304 that also provides the request). The central scheduler 306 can collect information from the access terminal 304 (and/or different access terminals), allocate resources to the access terminal 304 (and/or different access terminals), and transmit an assignment To the access terminal 304 (and/or a different access terminal).

The access terminal 304 may further include a rough requester 308, an in-band transmission controller 310, and a tailoring requester 312. Similarly, the central scheduler 306 of the base station 302 may include a rough information collector 314 and a precise information collector 316. The coarse requester 308 may send an out-of-band transmission to the base station 302, and the coarse information collector 314 may obtain the out-of-band transmission and then evaluate it (e.g., the central scheduler 306) to allocate resources. The coarse requester 308 can transmit coarse information via a dedicated channel, which can be a code division multiple access (CDMA) channel, a time division multiple access (TDMA) channel, a frequency division multiple access (FDMA) channel, and an OFDMA channel. , Its combination and the like. For example, the dedicated channel may be an overhead request channel. In addition or otherwise, the dedicated channel may be a contention-free channel on which the rough requester 308 provides information. The coarse requester 308 (and/or the access terminal 304) can automatically select when to send the scheduling parameters to the base station 302 and/or can periodically cycle through the parameters. In addition, it should be understood that the base station 302 can request certain parameters from the access terminal 304.

The rough information collector 314 and/or the central scheduler 306 can evaluate the rough information received from the rough requester 308 and provide an assignment in response to the access terminal 304. According to an example, the system 300 may use Orthogonal Frequency Division Multiple Access (OFDMA) related to in-band communication. According to this example, the resource assignment provided by the central scheduler 306 may be many subcarriers (e.g., a subset of the available subcarriers). However, the claimed subject matter is not limited to the foregoing examples, but encompasses any type of in-band communication (such as CDMA, TDMA, FDMA, etc.) and/or the allocation of any resources associated with reverse link communication.

The central scheduler 306 can transmit the assignment to the access terminal 304. According to an example, the assignment may be provided to the in-band transmission controller 310. The in-band transmission controller 310 can enable the access terminal 304 to send a reverse link transmission to the base station 302 according to the received assignment. The obtained assignment can enable the in-band transmission controller 310 to permit the transmission of one or more packets on the reverse link; therefore, the control burden can be reduced compared with the conventional technique of using an assignment for each packet. In addition, the tailoring requester 312 may transmit additional information used in conjunction with scheduling on the reverse link via in-band transmission. The sophisticated information collector 316 obtains this additional information and then the central scheduler 306 uses the additional information to modify assignments related to reverse link communication (for example, related to current and/or future transmissions). According to an example, the coarse requester 308 is used to complete the out-of-band transmission of the scheduling information and the in-band transmission of the scheduling information by the tailoring requester 312 can occur at different times. According to another example, the burden can be reduced by using the coarse requester 308 and the tailored requester 312. According to this example, a rough requester 308 that can be used to initially allocate resources can be used to provide a rough approximation of the resource to the central scheduler 306, and thereafter the tailoring requester 312 can be appended with the time frame, buffer size, and power bit. Further information related to standards and their analogs can be used to dynamically change the allocation of resources used to access the terminal 304.

Various information can be determined by the access terminal 304 and/or provided from the access terminal 304 to the base station 302 for the central scheduler 306 to use. For example, the access terminal 304 can use a distributed power control algorithm that determines the transmission power spectral density of the data channel, where the power spectral density (PSD) is the amount of transmission power per subcarrier. Similarly, the access terminal 304 can provide information related to the maximum transmission power, which can determine the maximum number of subcarriers that the access terminal 304 can support under the determined PSD related to the access terminal 304. In addition, the access terminal 304 can be associated with several QoS flows (such as best effort data, control, and voice). For latency-sensitive QoS flows (such as voice), a queue can have a relative latency related to the maximum amount of time any packet has been in the queue.

The rough requester 308 can utilize a dedicated periodic request (REQ) channel associated with the access terminal 304 to send rough information on the channel. For example, the REQ channel can be a 4-bit REQ channel, in which the first 2 bits indicate the highest QoS level of the data to be sent by the access terminal 304, and the second 2 bits indicate the access terminal 304's progress The maximum number of subcarriers that the method can support, such as 1-8, 9-16, 17-32 or more than 32. The maximum number of sub-carriers can be determined (for example, by access terminal 304, rough requester 308, etc.) as the smaller of the following numbers: the number of sub-carriers that can be supported based on the buffer level and the number of sub-carriers that can be supported based on the maximum power limit The number of carriers.

The access terminal 304 can determine the number of subcarriers that can be supported based on the buffer level by determining the data spectral density. For example, the unit of data spectral density can be the number of bits per packet per subcarrier. The number of subcarriers that can be supported can be obtained by dividing the number of bits in the buffer associated with the access terminal 304 by the data spectral density. The data spectral density may be the power spectral density determined based on the power control.

The spectral density of the data can be estimated from the PSD in various ways. For example, a last reported PSD level can be used to determine the data spectral density. Additionally or otherwise, the decayed version of the PSD level of the last report can be used to estimate the data spectral density. Those familiar with this technology should understand that any prediction technology can be used to predict the data spectral density that can be assigned by the base station 302 and/or the access terminal 304 to determine the data spectral density. In addition, the present invention anticipates that the number of subcarriers can be determined based on the total buffer size, the highest QoS level buffer size, the reported QoS level buffer size, or some other function of various buffer sizes.

The access terminal 304 may further determine the number of subcarriers that can be supported based on the maximum power limit. Therefore, the access terminal 304 can divide the maximum transmission power associated with the access terminal 304 by the PSD determined by the power control. Additionally or otherwise, the access terminal 304 can use the filtered average of the PSD levels, the filtered maximum number of subcarriers, or the predicted maximum number of subcarriers.

Referring to FIG. 4, it illustrates an exemplary data packet 400 that can be transmitted to a base station by an access terminal on an in-band channel. The data packet 400 may be sent on the reverse link based on the assignment obtained in response to a rough, out-of-band request. The data packet 400 may include a packet header including information (for example, 1 bit) indicating that additional scheduler information (for example, scheduler message 402) is included in the data packet 400. If this bit is set, the data packet 400 includes one or more scheduler messages 402. According to an example, a field may indicate the number of scheduler messages 402. According to another example, a continuation bit may be included in each of the scheduler messages 402, which indicates whether additional scheduler messages 402 are included as part of the data packet 400.

It should be understood that any information used in conjunction with scheduled reverse link communication can be included as part of the scheduler message 402. For example, the scheduler information 402 may include the buffer size of each QoS flow, the line latency head of each QoS flow, the power control transmission power spectral density, and the number of sub-carriers supported under the transmission power spectral density. Maximum number, etc. related information. For the parameters specifically for the QoS flow, the QoS flow may be explicitly and/or implicitly indicated; the implicit indication may include the level of the buffer level. The transmission power spectral density can be expressed as the offset from the reference level, such as the offset from the power-controlled steering or the power of the control channel controlled as the performance of the given level. Data transmission (eg, data 404) can be performed using the hold-schedule location element; therefore, the scheduled data transmission can efficiently include detailed scheduling information.

In addition, it is expected that precise scheduling information (e.g., provided via in-band signal transmission) can be used to modify current transmissions and/or transmissions that occur at a later scheduled time. For example, the precise scheduling information (for example, provided by the tailoring requester 312 of FIG. 3) may include data related to data packet format changes in one or more scheduler messages 402. Therefore, the access terminal can indicate to the base station that the next packet sent on the reverse link in-band channel can be in a special format. According to another example, any modification associated with resource allocation can be dynamically completed based at least in part on the precise scheduling information.

With reference to Figures 5-7, methods related to efficiently providing scheduling information about communications on a reverse link to a central scheduler are described. At the same time, for the sake of simplicity of explanation, the method is shown and described as a series of actions. It should be understood and understood that the method is not limited by the order of the actions, because according to one or more embodiments, certain actions can occur in a different order and/or Simultaneously with other actions shown and described in this article. For example, those familiar with the art will understand and understand that the method can or can be represented as a series of related states or events such as a state diagram. In addition, not all of the illustrated actions are required to implement a method according to one or more embodiments.

Referring to FIG. 5, a method 500 that helps to efficiently provide scheduling information from the access terminal to the base station is illustrated. At 502, rough scheduling information can be transmitted via out-of-band signal transmission. For example, rough scheduling information can be sent on a dedicated channel. It is expected that this dedicated channel can be a CDMA channel, a TDMA channel, an FDMA channel, an OFDMA channel, a combination thereof and the like. The rough scheduling information may include information about buffer levels, QoS levels, power limits, supported sub-carriers, and so on.

At 504, an assignment corresponding to rough scheduling information can be received. This assignment can allocate any resources associated with reverse link communication. For example, the assignment can allocate subcarriers, time, power, packet format, etc. to be used in conjunction with reverse link transmission. At 506, detailed scheduling information can be transmitted via in-band signal transmission according to the assignment. According to one example, data packets can be transmitted as assigned on the reverse link and these data packets(s) can include additional precise scheduling information. According to an example, the additional scheduling information may include one or more headers associated with the data packet. Additional scheduling information can help to dynamically adjust the reverse link assignment of resources. In addition, additional scheduling information can indicate the format of one or more of the data packets to be transmitted in-band.

Turning to FIG. 6, a method 600 that helps to efficiently obtain scheduling information at the central scheduler is described. At 602, rough scheduling data can be received on a dedicated channel. According to one example, rough scheduling data can be obtained from any number of access terminals. According to this example, rough scheduling data can be received on a contention-free channel dedicated to accessing each of the terminals. For example, rough scheduling data can be periodically obtained from each of the access terminals at various times; however, the claimed subject matter is not limited to this. At 604, resources for reverse link communication can be assigned based on rough scheduling data. In addition, the assignment can be transmitted to the corresponding access terminal. Resources may include, for example, subcarriers, time slots, power levels, packet formats, and the like. According to an example, the rough scheduling data may include an indication of the maximum number of subcarriers that can be supported; therefore, if available, this number of subcarriers can be assigned to the access terminal, from which the access terminal is the reverse link Road communication obtains rough scheduling information.

At 606, the precise scheduling data sent with the assigned resource can be received. The precise scheduling data may include one or more headers that are attached to different data obtained in the in-band communication. At 608, the assigned resources can be adjusted based on the precise scheduling data. Therefore, low-burden, coarse scheduling data can be obtained through the out-of-band channel, and precise scheduling data can be received through the in-band channel, thereby enabling effective reception of this information.

Now referring to FIG. 7, a method 700 that helps provide rough scheduling information to the central scheduler is described. At 702, the first number of subcarriers that can be supported is accurately determined based on the buffer bits. For example, the first number of subcarriers that can be supported can be estimated by dividing the number of bits in the buffer by the data spectral density (for example, bits per packet per subcarrier). At 704, a second number of subcarriers that can be supported can be determined based on the power limitation. For example, the second number of subcarriers that can be supported can be identified by dividing the maximum transmission power of the access terminal by the power spectral density (PSD) determined by the power control. At 706, the minimum of the first number of supportable subcarriers and the second number of supportable subcarriers can be identified. At 708, scheduling information can be transmitted via a dedicated channel. The scheduling information can identify the range that includes the identified minimum value. Therefore, it is possible to efficiently provide a rough indication of the maximum number of subcarriers that can be supported to the central scheduler. In addition, it is expected that more sophisticated scheduling information can be provided through in-band communication.

It should be understood that, according to one or more of the aspects described in this article, reasoning about efficiently providing scheduling information, determining how to fork a request including scheduling information, etc. can be performed. As used herein, the term "infer" ("infer" or "inference") generally refers to the inference or inference of the state of the system, environment, and/or user from a set of observations obtained through events and/or data the process of. For example, reasoning can be used to identify special content or actions, or a probability distribution can be generated across states. Reasoning can be probabilistic, which means that the calculation of the probability distribution on the state of interest is based on consideration of data and events. Inference can also refer to techniques used to compose higher-level events from a set of events and/or data. This reasoning leads to the construction of new events or actions from a set of observed events and/or stored event data, regardless of whether the events are temporarily closely related, and whether the events and data come from one event and data source or several Events and data sources.

According to an example, one or more of the methods introduced above may include inferences on how to efficiently branch scheduling information for transmission via out-of-band and in-band channels. For further example, inferences can be made about determining the spectral density level of the data associated with the access terminal. It should be understood that the foregoing examples are illustrative in nature and are not intended to limit the number of inferences that can be made or the manner in which such inferences can be made in conjunction with the various embodiments and/or methods described herein.

FIG. 8 is an example of an access terminal 800 that helps to efficiently transmit reverse link information. The access terminal 800 includes, for example, a receiver 802 that receives a signal from a receiving antenna (not shown), and performs typical actions (eg, filtering, amplifying, down-conversion, etc.) on the received signal on it and digitizing it The adjusted signal is used to obtain samples. For example, the receiver 802 may be an MMSE receiver, and includes a demodulator 804 that can demodulate the received symbol and provide it to the processor 806 for channel estimation. The processor 806 may be a processor dedicated to analyzing information received by the receiver 802 and/or generating information for transmission by the transmitter 816, a processor controlling access to one or more components of the terminal 800, and/or It not only analyzes the information received by the receiver 802, but also generates the information for transmission by the transmitter 816 and controls the processor that accesses one or more components of the terminal 800.

The access terminal 800 may additionally include a memory 808 operatively coupled to the processor 806 and capable of storing data to be transmitted, received data, and the like. The memory 808 can store information. The information is used for scheduling such as the buffer size of the access terminal 800, the buffer size of multiple QoS, the line packet latency head, and the queue latency measurement for QoS purposes. , Power control parameters, etc.

It should be understood that the data storage (for example, the memory 808) described herein may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. For example, and without limitation, non-volatile memory may include read-only memory (ROM), programmable read-only memory (PROM), electronically programmable read-only memory (EPROM), and electronically erasable and programmable Read memory (EEPROM), or flash memory. Volatile memory may include random access memory (RAM), which acts as external cache memory. For example and without limitation, RAM can be used in many forms, such as synchronous RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM) ), Synchrolink DRAM (SLDRAM) and Rambus RAM (DRRAM). The memory 808 of the target system and method is intended to include, but is not limited to, these and any other suitable types of memory.

The receiver 802 is further operatively coupled to a coarse requester 810 that generates a request, which can be transmitted via the transmitter 816 on a dedicated, out-of-band channel. The coarse requester 810 may collect scheduling information used to obtain the assignment of resources associated with the reverse link from the central scheduler. For example, the coarse requester 810 can automatically complete the out-of-band, coarse request transmission. Additionally or otherwise, the coarse requester 810 may periodically transmit such requests. According to another example, the receiver 802 can obtain information that initiates the generation and/or transmission (for example, via the transmitter 816) of the request by the coarse requester 810. In addition, the rough requester 810 may transmit rough scheduling information in response to data arrival (for example, a non-empty buffer).

In addition, a tailoring requestor 812 can utilize the allocated resources related to the reverse link and transmit additional, sophisticated scheduling information in-band. For example, the subcarrier, time, power level, packet format, etc. can be assigned to the access terminal 800 for reverse link communication; therefore, the tailoring requestor 812 can be based on the assigned subcarrier, time, and power level. Standard, packet format, etc. attach additional scheduling information (eg, header) to the data to be transmitted on the reverse link. The tailoring requestor 812 can facilitate the transmission of precise scheduling information via the transmitter 816 so as to dynamically modify the resource assignments for accessing the terminal 800. The access terminal 800 further includes a modulator 814 and a transmitter 816 that transmits signals to, for example, a base station, another user device, a remote agent, and so on. Although the coarse requester 810, crop requester 812, and/or modulator 814 are described as separate from the processor 806, it should be understood that they may be part of the processor 806 or many processors (not shown).

FIG. 9 is an example of a scheduling information system 900 that helps to efficiently obtain the allocation of resources for roughly assigning and/or adjusting the reverse link communication. The system 900 includes a base station 902 having a receiver 910 for receiving information from one or more user equipment 904 via a plurality of receiving antennas 906 and transmitting to one or more user equipment 904 via a transmitting antenna 908 The transmitter 924. The receiver 910 can receive information from the receiving antenna 906 and is operatively associated with a demodulator 912 that demodulates the received information. A processor 914 analyzes the demodulated symbol. The processor 914 can be similar to the processor described above with respect to FIG. 8, and the processor 914 is coupled to a memory 916 that stores: Allocate resources associated with the reverse link communication (for example, data associated with the buffer level, QoS level, power limit, etc. of the user equipment 904) that can be measured and/or from the user equipment 904 (Or a different base station (not shown)) received information, and/or any other suitable information for performing the various actions and functions described in this article. The processor 914 is further coupled to a rough resource allocator 918, which evaluates the rough scheduling information obtained from the user equipment 904 to generate an assignment to be transmitted to the user equipment 904. The rough resource allocator 918 can analyze the out-of-band scheduling information provided via a dedicated channel. For example and without limitation, the out-of-band scheduling information evaluated by the rough schedule allocator 918 can be a 4-bit request that includes an indication and description of the highest QoS level of the data to be transmitted A range of the maximum number of sub-carriers supported by the device. It should be understood that the coarse resource allocator 918 may be included in a central scheduler associated with the base station 902 (for example, the central scheduler 306 of FIG. 3).

The processor 914 can be further coupled to a dynamic resource assignment adjuster 920, which can be enabled to modify the resource assignment based on the obtained in-band scheduling information. For example, the dynamic resource assignment adjuster 920 may analyze the scheduling information provided as a header in the data packet received on the reverse link transmitted according to the assignment generated by the coarse resource allocator 918. The dynamic resource assignment adjuster 920 may also be included in the central scheduler. The dynamic resource assignment adjuster 920 and/or the coarse resource allocator 918 may be further coupled to a modulator 922. The modulator 922 can multiplex the assignment information for the transmitter 924 to transmit to the user equipment 904 via the antenna 908. Although the coarse resource allocator 918, the dynamic resource assignment adjuster 920, and/or the modulator 922 are described as separate from the processor 914, it should be understood that they may be part of the processor 914 or many processors (not shown).

FIG. 10 shows an exemplary wireless communication system 1000. For the sake of brevity, the wireless communication system 1100 describes an access point 1002 (for example, a base station) and a terminal 1004 (for example, an access terminal). However, it should be understood that the system 1000 may include more than one access point and/or more than one terminal, where additional access points and/or terminals may be substantially similar to or different from the exemplary access points 1002 and 1002 described below. Terminal 1004. In addition, it should be understood that the access point 1002 and/or the terminal 1004 can use the systems (Figures 1-3 and 8-9) and/or methods (Figures 5-7) described herein to facilitate wireless communication therebetween.

Referring now to FIG. 10, the forward link (FL) facilitates data transmission from the access point 1002 to the access terminal 1004. The reverse link (RL) facilitates data transmission from the access terminal 1004 to the access point 1002. The access point 1002 can simultaneously transmit data to one or more access terminals on the forward link. The access terminal 1004 can transmit the same data to one or more access points on the reverse link.

For forward link data transmission, at the access point 1002, a buffer 1006 receives and stores data packets from higher-level applications. An FL TX LP entity 1008 performs processing on the data packet in the buffer 1006 and provides a frame sequence including frames. A MAC/PHY TX processor 1010 performs forward link MAC and physical layer processing (for example, multiplexing, encoding, modulation, mixing, channelization, etc.) on the frame sequence from the entity 1008 ) And provide a data sample stream. A transmitter unit (TMTR) 1012 processes (eg, converts to analog, amplifies, filters, and up-converts) the data sample stream from the processor 1010 and generates a forward link signal, which is transmitted via an antenna 1014 Road signal.

At the access terminal 1004, the antenna 1016 receives the forward link signal from the access point 1002 and a receiver unit (RCVR) 1018 processes it (for example, filtering, amplifying, down-converting and digitizing) to obtain Samples have been received. A MAC/PHY RX processor 1020 performs forward link MAC and physical layer processing (for example, de-channelization, de-stirring, demodulation, decoding, de-multiplexing, etc.) on the received samples and provides a Receive frame sequence. An FL RX LP entity 1022 performs receiver processing on the received frame sequence and provides decoded data to a re-assembly buffer 1024. The FL RX LP entity 1022 can also generate NACKs for data detected as missing and can also generate ACKs for correctly decoded data. The NACK and ACK are sent to the access point 1002 via the reverse link and provided to the FL TX LP entity 1008, and the FL TX LP entity 1008 performs retransmission of the missing data (if any). A retransmission timer 1026 facilitates the retransmission of the last frame to completely erase the buffer. A NACK timer 1028 facilitates the retransmission of NACK. These timers are described below.

For reverse link data transmission, at an access terminal 1004, a buffer 1030 receives and stores data packets from higher-level applications. An RL TX LP entity 1032 performs processing on the data packet in the buffer 1030 and provides a frame sequence including frames. A MAC/PHY TX processor 1034 performs reverse link MAC and physical layer processing on the frame sequence from the entity 1032 and provides a data sample stream. A transmitter unit (TMTR) 1036 processes the data sample stream from the processor 1034 and generates a reverse link signal, which is transmitted via the antenna 1016.

At the access point 1002, the antenna 1014 receives the reverse link signal from the access terminal 1004 and a receiver unit (RCVR) 1038 processes it to obtain received samples. A MAC/PHY RX processor 1040 performs reverse link MAC and physical layer processing on the received samples and provides the received frame sequence. An RL RX LP entity 1042 performs receiver processing on the received frame sequence and provides decoded data to a reassembly buffer 1044. The RL RX LP entity 1042 can also generate NACKs for data detected as missing (for example, using a NAK timer 1046) and can also generate ACKs for correctly decoded data. NACK and ACK are sent to the access terminal 1004 via the forward link and provided to the RL TX LP entity 1032, and the RL TX LP entity 1032 performs retransmission of the missing data (if any) (for example, using a retransmission timer) 1048). The FL and RL are described in detail below. Generally speaking, ACK and/or NACK feedback can be sent through a link protocol (LP), and ACK and/or NACK feedback can also be sent through the physical layer.

The controllers 1050 and 1052 guide operations at the access point 1002 and the access terminal 1004, respectively. The memory units 1054 and 1056 store program codes and data used by the controllers 1050 and 1052, respectively, in order to implement the disclosed embodiments.

For multiple access systems (for example, FDMA, OFDMA, CDMA, TDMA, etc.), multiple terminals can simultaneously transmit on the uplink. For this system, a pilot subband can be shared between different terminals. The channel estimation technique can be used when the sub-pilot band of each terminal spans the entire operating frequency band (except for the band edge). This sub-pilot band structure will be needed to obtain frequency diversity for each terminal. The techniques described herein can be implemented in various ways. For example, these technologies can be implemented in hardware, software, or a combination thereof. For hardware implementation, the processing unit for channel estimation can be implemented in one or more application-specific integrated circuits (ASIC), digital signal processor (DSP), digital signal processing device (DSPD), programmable logic device (PLD) ), field programmable gate arrays (FPGA), processors, controllers, microcontrollers, microprocessors, other electronic units designed to perform the functions described herein, or combinations thereof. For software, it can be implemented through modules (for example, programs, functions, etc.) that perform the functions described herein. The software code can be stored and executed in the memory units 1054 and 1056.

Referring to FIG. 11, a system 1100 that efficiently transmits scheduling information to a central scheduler to help allocate in-band resources is illustrated. It should be understood that the system 1100 is represented as including functional blocks, which represent functions implemented by a processor, software, or a combination thereof (for example, firmware). The system 1100 can be implemented in a wireless device and can include a logic module 1102 for transmitting rough scheduling information via an out-of-band channel. For example, a request can be sent on a dedicated channel (for example, automatically, periodically, in response to receiving data from a different resource, etc.). The request includes the buffer level, the QoS level, and the supported subcarriers. Rough information about the number and its analogues. In addition, the system 1100 may include a logic module 1104 for obtaining an assignment for reverse link communication. According to an example, the assignment may be related to subcarriers, time, power level, etc., to be used by an access terminal for reverse link communication. In addition, the system 1100 may include a logic module 1106 for transmitting detailed scheduling information via the in-band channel based on the assignment. For example, the different data can include detailed scheduling information as a header and this detailed scheduling information can enable the assigned resources associated with the reverse link to be dynamically adjusted.

Referring now to FIG. 12, a system 1200 that helps to efficiently receive scheduling information so as to allocate in-band resources is illustrated. The system 1200 is represented as including functional blocks, and the functional blocks may represent functions implemented by a processor, software, or a combination thereof (for example, firmware). The system 1200 can be implemented in a base station and can include a logic module 1202 for obtaining rough scheduling information through an out-of-band channel. The system 1200 may also include a logic module 1204 for sending a resource assignment based on the rough scheduling information. In addition, the system 1200 may include a logic module 1206 for obtaining precise scheduling information by using the in-band channel completed by the resource assignment.

For software implementation, modules (for example, programs, functions, etc.) that perform the functions described herein can be used to implement the techniques described herein. The software code can be stored in the memory unit and executed by the processor. The memory unit may be implemented within or outside the processor, in which case it may be communicatively coupled to the processor via various methods known in the art.

The content described above includes examples of one or more embodiments. Of course, it is impossible to describe every conceivable combination of components or methods in order to describe the aforementioned embodiments, but those skilled in the art may realize that many further combinations and modifications of various embodiments are possible. Therefore, the described embodiments are intended to include all such changes, modifications, and changes that fall within the spirit and scope of the scope of the appended patent application. In addition, to the extent that the term "includes" is used in the implementation or the scope of the patent application, this term is expected to be inclusive in a manner similar to the term "include", because when the term "includes" is used in the scope of the patent application, it is Understand as transitional words.

<p>100. . . Wireless communication system</p><p>102. . . Base station</p><p>104. . . Access terminal</p><p>106. . . Operation and Management Center</p><p>108. . . Data network</p><p>200. . . system</p><p>202. . . Base station</p><p>204. . . Access terminal</p><p>206. . . Access terminal</p><p>300. . . system</p><p>302. . . Base station</p><p>304. . . Access terminal</p><p>306. . . Central Scheduler</p><p>308. . . Rough requester</p><p>310. . . In-band transmission controller</p><p>312. . . Crop requester</p><p>314. . . Rough information collector</p><p>316. . . Precision Information Collector</p><p>400. . . Data packet</p><p>402. . . Scheduler message</p><p>404. . . material</p><p>500. . . method</p><p>600. . . method</p><p>700. . . method</p><p>800. . . Access terminal</p><p>802. . . receiver</p><p>804. . . Demodulator</p><p>806. . . processor</p><p>808. . . Memory</p><p>810. . . Rough requester</p><p>812. . . Crop requester</p><p>814. . . Modulator</p><p>816. . . Transmitter</p><p>900. . . system</p><p>902. . . Base station</p><p>904. . . User equipment</p><p>906. . . antenna</p><p>908. . . antenna</p><p>910. . . receiver</p><p>912. . . Demodulator</p><p>914. . . processor</p><p>916. . . Memory</p><p>918. . . Rough resource allocator</p><p>920. . . Dynamic resource assignment adjuster</p><p>922. . . Modulator</p><p>924. . . Transmitter</p><p>1000. . . Wireless communication system</p><p>1002. . . Access point</p><p>1004. . . Access terminal</p><p>1006. . . buffer</p><p>1008. . . FL TX LP entity</p><p>1010. . . MAC/PHY TX processor</p><p>1012. . . Transmitter unit</p><p>1014. . . antenna</p><p>1016. . . antenna</p><p>1018. . . Receiver unit</p><p>1020. . . MAC/PHY RX processor</p><p>1022. . . FL RX LP entity</p><p>1024. . . Reorganization buffer</p><p>1026. . . Retransmission timer</p><p>1028. . . Timer</p><p>1030. . . buffer</p><p>1032. . . RL TX LP entity</p><p>1034. . . MAC/PHY TX processor</p><p>1036. . . Transmitter unit</p><p>1038. . . Receiver unit</p><p>1040. . . MAC/PHY RX processor</p><p>1042. . . RL RX LP entity</p><p>1044. . . Reorganization buffer</p><p>1046. . . Timer</p><p>1048. . . Retransmission timer</p><p>1050. . . Controller</p><p>1052. . . Controller</p><p>1054. . . Memory unit</p><p>1056. . . Memory unit</p><p>1100. . . Wireless communication system</p><p>1102. . . Logic module</p><p>1104. . . Logic module</p><p>1106. . . Logic module</p><p>1200. . . system</p><p>1202. . . Logic module</p><p>1204. . . Logic module</p><p>1206. . . Logic module</p>

Fig. 1 is an example of a wireless communication system according to various aspects stated herein.

Figure 2 is an example of a system that efficiently provides information to a base station to facilitate scheduling associated with reverse link communication.

Figure 3 is an example of a system used to assign requested transmission forks of resources associated with reverse link communications.

Figure 4 is an example of an exemplary data packet that can be transmitted to a base station via an access terminal on an in-band channel.

FIG. 5 is an example of a method that helps to efficiently provide scheduling information from the access terminal to the base station.

Figure 6 is an example of a method that helps to efficiently obtain scheduling information at the central scheduler.

Figure 7 is an example of a method that helps provide rough scheduling information to the central scheduler.

Figure 8 is an example of an access terminal that helps to efficiently transmit reverse link scheduling information.

FIG. 9 is an example of a system that helps to efficiently obtain scheduling information for roughly assigning and/or adjusting the allocation of resources associated with reverse link communication.

Figure 10 is an example of a wireless network environment that can be used with the various systems and methods described herein.

Figure 11 is an example of a system that helps to send scheduling information to the central scheduler to help allocate in-band resources.

Figure 12 is an example of a system that helps to efficiently receive scheduling information so that in-band resources can be allocated.