HK1148418B - Ul/dl scheduling for full bandwidth utilization - Google Patents

Description

UL/DL scheduling with full utilization of bandwidth

Technical Field

Implementations described herein relate generally to scheduling schemes for uplink and downlink transmissions in a communication system.

Background

According to some communication systems, a User Equipment (UE) may have multi-slot class capability. The multislot class may define the maximum transmission rate in the Uplink (UL) and Downlink (DL) directions. Depending on the multislot class of the UE, the UE may not be able to receive and transmit data simultaneously.

Typically, during the registration process, the UE may make its multislot class known to the network. Thereafter, the network may determine the primary transmission direction (e.g., UL or DL) of the session, and so on. Depending on the session type (e.g., interactive service session), the network may be required to quickly shift the bandwidth requirements from the UL to the DL and vice versa. However, transitioning between UL and DL directions typically takes a significant amount of time. Thus, for UEs that cannot receive and transmit data simultaneously, there may be an under-utilization of available bandwidth, which in turn may degrade the quality of service to the user.

In global system for mobile communications (GSM)/EDGE radio access network (GERAN), for example, the existing specification for GERAN may not be able to handle fast transfer bandwidth requirements because it requires the reallocation of a Temporary Block Flow (TBF). Therefore, GERAN may typically provide equal bandwidth to UL and DL. However, this approach may translate into an under-utilization of the multislot capability and available bandwidth of the UE. In addition, or alternatively, a significant amount of UE processing resources may be required to switch between receiving and transmitting at any time. This is especially true when the UE supports a large number of slots (e.g., more than 4 slots) for reception and transmission, respectively. Thus, in practice, for example, a UE may be limited to 5 or 6 slots per carrier in one direction, and 1 or 2 slots in the opposite direction.

Disclosure of Invention

It is an object of the present invention to obviate at least some of the above disadvantages and to improve the operability of devices in a communication system.

According to one aspect, a method may include: user equipment incapable of simultaneously performing transmission and reception receives scheduling of transmitting data on an uplink; the user equipment detects whether data is transmitted on an uplink or not; and the user equipment receiving data associated with a downlink upon determining that there is no data to transmit during a time corresponding to the schedule.

According to another aspect, an apparatus may include: a memory to store instructions and a processor to execute instructions. The processor may execute the instructions to receive an uplink schedule for transmission to another device; detecting whether data is to be transmitted; and selecting a time to transmit in a time window of an uplink schedule when it is determined that there is data to transmit, or receiving from a downlink in a time window of an uplink schedule when it is determined that there is no data to transmit; wherein the device is a multislot class of device and is incapable of simultaneously receiving from a downlink and transmitting to an uplink.

According to another aspect, an apparatus may include: a memory to store instructions and a processor to execute instructions. The processor may execute the instructions to identify a multislot class of user equipment that is not capable of receiving and transmitting simultaneously; transmitting a schedule to the user equipment on the downlink for the user equipment to transmit; and transmitting data to be received to the user equipment on a downlink during the scheduling of the transmission.

According to another aspect, a system may include: a user equipment capable of receiving an uplink schedule for transmission; reading an uplink schedule; determining whether there is data to send; when it is determined that there is data to transmit, preferentially transmitting the data and transmitting the data based on uplink scheduling; or receiving data associated with the downlink during uplink scheduling when it is determined that there is no data to transmit.

According to another aspect, a computer-readable medium may contain instructions executable by at least one processor of a device that is incapable of receiving and transmitting simultaneously. The computer-readable medium may include: one or more instructions for receiving a schedule to transmit data on an uplink; one or more instructions for determining whether there is data to send on an uplink; and one or more instructions for receiving data associated with the downlink upon determining that there is no data to transmit during a time corresponding to the schedule at which to transmit.

Drawings

Fig. 1 is a diagram illustrating devices communicating with each other via a communication system;

FIG. 2A is a diagram illustrating example components of the UE of FIG. 1;

FIG. 2B is a diagram illustrating example components of the device of FIG. 1;

3A-3C are diagrams illustrating example functions of the UE of FIG. 1;

FIG. 4 is a diagram illustrating an example implementation of the UE of FIG. 1, wherein the UE includes a wireless telephone;

5-11 are diagrams illustrating example utilizations of time slots that may be associated with the concepts described herein; and

12-14 are flowcharts illustrating example processes associated with the concepts described herein.

Detailed Description

The following detailed description refers to the accompanying drawings. The same reference numbers in different drawings may identify the same or similar elements. Furthermore, the following description does not limit the invention.

The word "may" is used throughout this application and should be interpreted as, for example, "having the potential to," "configured to," or "capable," without mandatory meaning (e.g., "must"). The words "a" and "an" should be interpreted to include one or more items. When only one item is being addressed, "one" or similar language is used. Further, the phrase "based on" should be interpreted as "based, at least in part, on" unless explicitly stated otherwise. The term "and/or" should be interpreted to include any and all combinations of one or more of the associated listed items.

The concepts described herein relate to improving bandwidth utilization in a communication system, as well as other advantages that must be derived therefrom or become apparent from the following description. The communication system should be broadly construed to include any type of wireless network, such as a cellular or mobile network (e.g., GSM, Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), Wideband Code Division Multiple Access (WCDMA), Ultra Mobile Broadband (UMB), High Speed Packet Access (HSPA), ad hoc networks, Worldwide Interoperability for Microwave Access (WiMAX), Institute of Electrical and Electronics Engineers (IEEE)802.X, etc.), or other types of wireless networks. The communication system may also include a wired network (e.g., cable, Digital Subscriber Line (DSL), Integrated Services Digital Network (ISDN), etc.). Throughout this description, the terms "communication system" and "network" may be used interchangeably. The term "packet" as used herein should be broadly construed to include datagrams, frames, cells, blocks, or any other type of data transmission/reception unit. Embodiments described herein may employ one or more rule-based schemes associated with UL and DL. The rule-based scheme may include: UL transmission is prioritized at the UE before reading for DL reception. Additionally, or alternatively, the UE may read for DL reception when the UE does not need to transmit. Additionally, or alternatively, the UE may select the UL slot to transmit such that the loss of DL slots for reading is minimized.

In one implementation, the rule-based scheme may supplement existing GERAN specifications. A rule-based scheme may employ flexible slot allocation. That is, the slot allocation (e.g., the number of UL slots and the number of DL slots) allocated to the UE may be changed for each Time Transmission Interval (TTI).

For purposes of discussion, a communication system having multislot class capability will be described herein. It will be appreciated that the concepts described herein are not dependent upon the particular type of communication system being employed. Rather, these concepts may be adapted for other types of networks, communication standards, and the like not specifically described herein. The "multislot class capable communication system" may comprise a network such as a GERAN or General Packet Radio Service (GPRS) network.

In view of the rule-based scheme, the multislot class capability of the UE may be utilized in a manner that takes all available bandwidth. Additionally, or alternatively, the UE may support more slots to receive and transmit (e.g., up to 8 slots per carrier and direction) even if the multi-slot class capability of the UE does not support simultaneous reception and transmission. Additionally, or alternatively, a lower required summation of transition times between UL and DL and/or a greater number of slots for reception and transmission may be provided compared to the corresponding multislot class. Additionally, or alternatively, the communication system may schedule UEs on all available time slots in both UL and DL simultaneously, and the transfer time requirement may limit the reception bandwidth only when (prioritized) UL transmissions are present.

Fig. 1 is a diagram illustrating an example communication system 100 in which concepts described herein may be implemented. As shown, communication system 100 may include a UE105-1, a network 110 including a device 115, and a device 120. As shown, UE-105-1 may be communicatively coupled to device 120 via network 110. For example, the device 115 may be communicatively coupled to the UE 105-1.

The UE105-1 may include a device having communication capabilities and capable of performing one or more of the rule-based schemes described herein. For example, the UE105-1 may comprise a telephone, a computer, a Personal Digital Assistant (PDA), a web browser, a Personal Communication System (PCS) terminal, a kiosk terminal, a pervasive computing device, and/or some other type of user device configured to perform one or more functions associated with the concepts described herein (i.e., a rule-based scheme). The UE105-1 may include a multislot class capable device. UE105-1 may include devices that are not capable of receiving and transmitting simultaneously.

In addition to the devices 115, the network 110 may include one or more networks of any type, including wireless networks or wired networks. For example, the network 110 may include a Local Area Network (LAN), a Wide Area Network (WAN), a telephone network (such as the Public Switched Telephone Network (PSTN) or Public Land Mobile Network (PLMN)), a satellite network, an intranet, the Internet, or a combination of networks or communication systems.

The devices 115 may include devices with communication capabilities. For example, the device 115 may include a wireless station or a wired station. The term "wireless station" should be broadly construed to include any type of device that may communicate with the UE105-1 via a wireless link. For example, a wireless station may include a Base Station (BS), a Base Transceiver Station (BTS) (e.g., in a GSM communication system), an eNodeB (e.g., in an LTE communication system), a NodeB (e.g., in a UMTS communication system), a repeater, a relay, or some other type of device. The term "wireline station" should be broadly construed to include any type of device that may communicate with the UE105-1 via a wireline link. For example, a wireline station may include an edge router, a switch, a gateway, or some other type of device.

The device 115 may comprise a device capable of identifying the multislot capability of another device, such as the UE 105-1. Additionally, or alternatively, the device 115 may include a device capable of recognizing that another device is not capable of receiving and transmitting simultaneously.

Device 120 may include a device having communication capabilities. For example, device 120 may include a UE, a server providing resources and/or services, and/or some other type of device capable of maintaining end-to-end communication with UE105-1 via device 115.

FIG. 2A is a diagram illustrating example components of the UE 105-1. As shown, the UE105-1 may include a transceiver 205, a processor 210, a memory 215, an input device 220, an output device 225, and a bus 230. The term "component" as used herein should be broadly interpreted to include, for example, hardware, software, and hardware, firmware, and the like.

The transceiver 205 may include components capable of transmitting and receiving information. For example, the transceiver 205 may include transceiver circuitry for transmitting and receiving packets to and from other devices and/or communication systems.

Processor 210 may include components capable of interpreting and/or executing instructions. For example, the processor 210 may include a general purpose processor, a microprocessor, a data processor, a co-processor, a network processor, an Application Specific Integrated Circuit (ASIC), a controller, a programmable logic device, a chipset, and/or a Field Programmable Gate Array (FPGA).

Memory 215 may include components capable of storing information (e.g., data and/or instructions). For example, the memory 215 may include Random Access Memory (RAM), Dynamic Random Access Memory (DRAM), Static Random Access Memory (SRAM), Synchronous Dynamic Random Access Memory (SDRAM), Ferroelectric Random Access Memory (FRAM), Read Only Memory (ROM), Programmable Read Only Memory (PROM), Erasable Programmable Read Only Memory (EPROM), Electrically Erasable Programmable Read Only Memory (EEPROM), and/or flash memory.

Input device 220 may include components capable of receiving input from a user and/or another device. For example, the input device 220 may include a keyboard, keypad, mouse, buttons, switches, microphone, display, and/or voice recognition logic.

Output device 225 may include components capable of outputting information to a user and/or another device. For example, output device 225 may include a display, a speaker, one or more Light Emitting Diodes (LEDs), and/or a vibrator.

Bus 230 may include components that enable communication among components of UE 105-1. For example, bus 230 may include a system bus, an address bus, a data bus, and/or a control bus. Bus 230 may also include a bus driver, a bus arbiter, a bus interface, and/or a clock.

Although fig. 2A illustrates example components of the UE105-1, in other implementations, the UE105-1 may include fewer, additional, and/or different components than those illustrated in fig. 2A. For example, the UE105-1 may include a hard disk or some other type of computer-readable medium, and a corresponding drive. The term "computer-readable medium" as used herein should be broadly interpreted as encompassing physical or logical storage devices. It may be appreciated that one or more components of UE105-1 may be capable of performing one or more other tasks associated with one or more other components of UE 105-1.

Fig. 2B is a diagram illustrating example components of device 115. Device 120 may be similarly configured.

The transceiver 250 may include components capable of transmitting and receiving information. For example, the transceiver 250 may include transceiver circuitry for transmitting and receiving packets to and from other devices and/or communication systems.

Processor 255 may include components capable of interpreting and/or executing instructions. For example, the processor 255 may include a general purpose processor, a microprocessor, a data processor, a co-processor, a network processor, an Application Specific Integrated Circuit (ASIC), a controller, a programmable logic device, a chipset, and/or a Field Programmable Gate Array (FPGA).

Memory 260 may include components capable of storing information (e.g., data and/or instructions). For example, the memory 260 may include Random Access Memory (RAM), Dynamic Random Access Memory (DRAM), Static Random Access Memory (SRAM), Synchronous Dynamic Random Access Memory (SDRAM), Ferroelectric Random Access Memory (FRAM), Read Only Memory (ROM), Programmable Read Only Memory (PROM), Erasable Programmable Read Only Memory (EPROM), Electrically Erasable Programmable Read Only Memory (EEPROM), and/or flash memory.

Bus 265 may include components that enable communication among components of device 115. For example, bus 265 may include a system bus, an address bus, a data bus, and/or a control bus. Bus 265 may also include bus drivers, bus arbiters, bus interfaces, and/or clocks.

Although fig. 2B illustrates example components of device 115, in other implementations, device 115 may include fewer, additional, and/or different components than shown in fig. 2B. For example, device 115 may include a hard disk or some other type of computer-readable medium, and a corresponding drive. It may be appreciated that one or more components of the device 115 may be capable of performing one or more other tasks associated with one or more other components of the device 115.

3A-3C are diagrams illustrating example functional components capable of performing one or more rule-based schemes described herein. These example functional components will be described in connection with the UE 105-1. As described above, one of the rule-based schemes includes prioritizing UL transmissions before reading for DL reception. Fig. 3A illustrates an example functional component, referred to as UL priority processor 305, that performs this function. UL priority processor 305 may be implemented using one or more of the components described in fig. 2A. For example, UL priority processor 305 may be implemented in transceiver 205 and memory 215.

UL priority processor 305 may include functional elements such as UL scheduler 310 and transmit buffer 315. UL scheduler 310 may have knowledge of the UL transmit schedule and the ability to detect when packets are stored in transmit buffer 315. The transmit buffer 315 may store packets for UL transmission.

In an example operation, UL scheduler 310 may determine whether transmit buffer 315 is storing packets for UL transmissions. UL scheduler 310 may make this determination at a time close to when UE105-1 may be scheduled for UL transmission. If UL scheduler 310 determines that transmit buffer 315 is storing packets for UL transmissions, UE105-1 may prioritize UL transmissions of packets before reading for DL reception. The priority handling of UL transmissions will be described in more detail below.

Additionally, or alternatively, the UE105-1 may read for DL reception when the UE105-1 does not need to transmit. Fig. 3B illustrates an example functional component for performing this function, referred to as DL reader determiner 320. The DL reader determiner 320 may be implemented with one or more of the components described in fig. 2A. For example, the DL reader determiner 320 may be implemented in the transceiver 205 and the memory 215.

The DL reader determiner 320 may include functional components such as a UL scheduler 310, a transmit buffer 315, a DL reader 325, and a receive buffer 330. UL scheduler 310 and transmit buffer 315 may operate in a similar manner as described above. The DL reader 325 may be able to read and store packets in the receive buffer 330. Receive buffer 330 may store packets received from a DL transmission.

In an example operation, UL scheduler 310 may determine whether transmit buffer 315 is storing packets for UL transmissions. UL scheduler 310 may make this determination at a time close to when UE105-1 may be scheduled for UL transmission. If UL scheduler 310 determines that transmit buffer 315 does not store packets for UL transmissions, UE105-1 may notify DL reader 325. The DL reader 325 may read from the DL transmission and store in the receive buffer 330. For example, DL reader 325 may read on a DL slot and check if there is a packet for itself. If there is a packet for itself, the packet may be stored in the receive buffer 330. It can be appreciated that UL scheduler 310 may also have knowledge that receive buffer 330 is storing packets, for example. Reading of DL reception will be described in more detail below.

Additionally, or alternatively, UE105-1 may select the UL slot to transmit such that the loss of DL slots for reading is minimized and all DL slots in a given TTI are not used in view of DL transmissions. Fig. 3C illustrates an example functional component for performing this function, referred to as transmit selector 335. Transmit selector 335 may be implemented using one or more of the components described in FIG. 2A. For example, the transmit selector 335 may be implemented in the transceiver 205 and the memory 215.

The transmit selector 335 may include functional components such as a UL scheduler, a transmit buffer 315, and a time slot selector 340. UL scheduler 310 and transmit buffer 315 may operate in a similar manner as described above. The slot selector 340 may select the UL slots for transmission such that the loss of DL slots for reading is minimized, or in other words, the number of DL slots for reading is maximized.

In an example operation, UL scheduler 310 may determine whether transmit buffer 315 is storing packets for UL transmissions. UL scheduler 310 may make this determination at a time that is close to when UE105-1 may be scheduled for UL transmission. If UL scheduler 310 determines that transmit buffer 315 is storing packets for UL transmissions, UL scheduler 310 may notify slot selector 340. The slot selector 340 may select the UL slot to transmit the packet such that the loss of the DL slot is minimized. The packets in the transmit buffer 315 may be transmitted based on the selected time slot. The selection of the UL slot by the slot selector 340 will be described in more detail below.

FIG. 4 is a diagram of an example implementation of UE105-1, where UE105-1 comprises a wireless telephone. As shown, UE105-1 may include: a microphone 405 (e.g., of input device 220) for inputting audio information to UE 105-1; a speaker 410 (e.g., of output device 225) for providing audio output from UE 105-1; a keypad 415 (e.g., of input device 220) for entering data or selecting device functions; and a display 420 (e.g., of input device 220 and output device 225) for displaying data to a user and/or providing a user interface for inputting data or selecting device functions, and the like.

As described above, implementations described herein provide UL and DL related rule-based schemes that can improve bandwidth utilization, etc. For discussion purposes, these concepts will be described with reference to the existing GERAN specification. Further, for discussion purposes, the UE105-1 is assumed to have multislot class capability that is incapable of receiving and transmitting simultaneously. Currently, GERAN specifications describe multislot classes ranging from 1 to 45, and corresponding user equipment classes, such as type 1 or type 2. The UE105-1 may be considered a type 1 device with a maximum number of slots for receiving, a maximum number of slots for transmitting, and a sum (i.e., the total number of UL and DL slots that may be used per TTI). Further, the device 115 may be considered a wireless station in GERAN.

Based on this framework, when the UE105-1 is scheduled to transmit, GERAN will not be able to transmit on the DL to the UE 105-1. However, according to the concepts described herein, GERAN may transmit on the DL to UE105-1 even when UE105-1 is scheduled to transmit.

Fig. 5-11 are diagrams illustrating example utilizations of time slots that may be associated with the concepts described herein. It can be appreciated that the UL and DL slots are illustrated as time offsets in fig. 5-11. For example, an UL frame (e.g., 8 slots) may be time-offset from a DL frame by multiple slots (e.g., 3 slots) to accommodate the multi-slot class capability of UE 105-1.

For purposes of discussion in conjunction with fig. 5-11, assume that the time transfer capability of UE105-1 (e.g., from DL read to UL transmit, or vice versa) is equal to T_tb1 time slot (i.e., T)_tbIs the time required for the UE105-1 to be ready to transmit) and T_rb1 time slot (i.e., T)_rbIs the time required for the UE105-1 to be ready for reception). Further, neighbor cell signal level measurements are not considered in these examples, and the DL may send Packet Associated Control Channels (PACCHs), including Piggyback Acknowledgements (PANs), on time slots that the UE105-1 may read, or on time slots that the UE105-1 is most likely to read. Further, for purposes of discussion in connection with FIGS. 5-11, assume that the UE105-1 always has packets to read from the DL. That is, as described above, GERAN may transmit to UE105-1 on the DL even when UE105-1 is scheduled to transmit, for example.

Fig. 5 is a diagram illustrating a concept of performing UL transmission prior to reading for DL reception. As shown, timing diagram 500 may include DL505 and UL 510. Both DL505 and UL510 may include an array of slots for UL transmission and DL reception.

In each of the DL505 and UL510, the slots are numbered (0) to (7). For purposes of discussion, assume that the slot allocation for UE105-1 is 4 slots for UL and 8 slots for DL. These time slot allocations are illustrated in fig. 5 as time slot group 515, time slot group 520, and time slot group 525 in UL 510; and slot group 530, slot group 535, and slot group 540 in DL 505. As further illustrated, an Uplink State Flag (USF), indicated by the letter "U," may be received in DL505 from, for example, device 115 to provide UE105-1 with a time slot allocation for transmission. In this example, receipt of the USF indicates the actual availability to transmit packets during the next set of time slots (i.e., time slot set 520 as opposed to time slot set 515). This allocation method is called an Extended Dynamic Allocation (EDA) method. Thus, assume that UE105-1 is operating in EDA mode.

Based on the above, the following scenarios may arise. UE105-1 may receive the USF during slot (4) in slot group 530. Near this point, UL scheduler 310 may detect that there is a packet in transmit buffer 315 to transmit. UL priority processor 305 may prioritize the transmission of these packets to be transmitted over the reading of the packets in receive buffer 330. For example, the transition from DL to UL may occur during slot (6) of slot 535. As further illustrated by the letter "X," the non-read slot group 550 indicates that the UE105-1 cannot read from slot (6) of slot group 535 to slot (3) of slot group 540. In slot (4) of slot group 520 in UL510, UE105-1 may begin transmitting. As further illustrated by the letter "T," the transmit slot group 545 indicates that the UE105-1 may transmit from slot (4) to slot (7) of the slot group 520. Thereafter, at slot (3) of slot group 540, UE105-1 may switch back to DL 505.

In view of this scheme, the available bandwidth is fully utilized in accordance with the handover time capability of the UE 105-1. That is, as many time slots as possible are utilized for DL transmission, and the remaining bandwidth is used for UL transmission. Further, although the UE105-1 may not be able to receive packets during the non-read slot group 550, but these packets may need to be re-sent to the UE105-1, the GERAN may identify any rejected packets (i.e., non-received packets) based on the slot number associated with the transmission received from the UE105-1 (i.e., the transmit slot group 545). Any non-received packets can therefore be re-sent (immediately) thereafter.

Fig. 6 is a diagram illustrating the concept of reading for DL reception when the UE105-1 does not need to transmit. That is, when the UE105-1 is scheduled for UL transmission, but the UE105-1 does not need to transmit, the UE105-1 may read for DL reception.

As shown, timing diagram 600 may include DL505 and UL510 described above with respect to fig. 5. Further, UE105-1 may operate in EDA mode with 4 slot allocations for UL and 8 slot allocations for DL.

In this scenario, the UE105-1 does not have any packets to send in the transmit buffer 315. For example, UE105-1 may receive a USF during slot (4) of slot group 530 to transmit during slot 520. Near this point, UL scheduler 310 may detect that there are no packets to transmit in transmit buffer 315. At this time, according to the DL reader determiner 320, the UL scheduler 310 may inform the DL reader 325 of the status of the transmission buffer 315 (no packet to be transmitted). In such an instance, DL reader 325 may read from the DL transmission during the UL allocation slot and store in receive buffer 330. That is, as shown by the time slot group 605, the UE105-1 may read for DL reception during this time period, thereby efficiently utilizing bandwidth, etc. Thus, the 4 UL slot assignments associated with slot group 520 (corresponding to the slots of slot group 605) may be used for reading for DL reception. This is possible because the GERAN may transmit on the DL to the UE105-1 even when the UE105-1 is scheduled to transmit.

Fig. 7 is a diagram illustrating a concept of selecting a time slot for UL transmission so that a loss of reading for DL reception can be minimized. As shown, timing diagram 700 may include DL505 and UL510 described above with respect to fig. 5. Further, UE105-1 may operate in EDA mode with 4 slot allocations for UL and 8 slot allocations for DL.

In such a scenario, UE105-1 may choose to transmit from the UL slots such that the loss of DL slots for reading is minimized. For example, UE105-1 may receive a USF during slot (4) of slot group 530 to transmit (e.g., during slot 520). Near this point, UL scheduler 310 may detect that there is a packet in transmit buffer 315 to transmit. In this example case, UL scheduler 310 may detect that the number of packets to be transmitted is less than the number of packets that can be transmitted within slot group 520. UL scheduler 310 may inform time slot selector 340 of the status of transmit buffer 315. The time slot selector 340 may select the time slot for transmitting the packet in the transmit buffer 315 such that the number of DL time slots lost for reading is minimized.

In one implementation, the time slots for transmission may be selected according to an order from the last time slot within the UL transmission time slot set to the earliest time slot within the UL transmission time slot set. For example, based on the state of the transmit buffer 315, it is assumed that only one time slot is needed to transmit the packet in the transmit buffer 315. In such an instance, the transmit selector 335 may select the time slot during the set of time slots 530 in which the packets are to be transmitted. For example, as indicated by the letter "T," the transmit slot group 705 indicates that the UE105-1 may transmit these packets during slot (7) of the slot group 520. That is, the slot selector 340 may select the time to transmit starting with the last slot within the slot group 520. As further illustrated by the letter "X," the non-read slot group 710 indicates that the UE105-1 cannot read in slots (1) through (3) from the slot group 540, which may require retransmission of the corresponding packets associated with these slots.

Based on the above description, it may be appreciated that UE105-1 may read for DL reception during slots (4) and (5) of slot group 520 (corresponding to slot (7) of slot group 535 and slot (0) of slot group 540). Thus, the UL slot allocation associated with slot group 520 may be partially used for reading the DL slot. Therefore, during this period, the number of DL slots lost for reading is minimal. That is, rather than transmitting in time slots (5) or (6), where only one time slot may be used for reading, or where no time slot may be used for reading, UE105-1 may read during a portion of time slot group 520.

However, the choice of time slot may differ depending on the number of packets to be transmitted. For example, if two slots are needed to transmit a packet, the slot selector 340 may select slots (6) and (7) of the slot group 520; if 3 slots are needed, slot selector 340 may select slots (5), (6), and (7) of slot group 520; if 4 slots are needed to transmit a packet, slot selector 340 may select slots (4), (5), (6), and (7) of slot group 520; if 5 slots are needed to transmit a packet, slot selector 540 may select slots (4), (5), (6), and (7) of slot group 520 and slot (7) (not shown) of slot group 525 to transmit.

It can also be appreciated that in another implementation, the slots for transmission can be selected according to an order from an earliest slot within the group of UL transmission slots to a last slot within the group of UL transmission slots. In the scenario of fig. 7, this implementation would yield the same result (i.e., two slots could be utilized for reading).

Fig. 8 is a diagram illustrating the following concept: performing UL transmission prior to reading for DL reception, when the UE105-1 does not need to perform transmission, reading for DL reception, and selecting a slot for UL transmission, makes it possible to minimize the loss of reading for DL reception. As shown, timing diagram 800 may include DL505 and UL510 as described above in connection with fig. 5. However, assume that the time slot allocation for UE105-1 is 2 slots for UL (as indicated by slot groups 515, 520, and 525); 8 slots are used for DL (as indicated by slot groups 530, 535, and 540). The UE105-1 may operate in a Dynamic Assignment (DA) mode. This allocation method is similar to EDA mode except that the USF is received for each available UL timeslot (e.g., in a one-to-one manner). In addition to the USF, fig. 8 illustrates Relative Reserved Block Period (RRBP) polling, as indicated by the letter "P", for DL positive Acknowledgement (ACK)/DL Negative Acknowledgement (NACK).

Based on the above description, the following scenario may arise. UE105-1 may receive the RRBP poll and the USF prior to slot group 530. Near this point, UL scheduler 310 may detect that there is a packet in transmit buffer 315 to transmit. UL priority processor 305 may prioritize the transmission of these packets to be transmitted over the reading of the packets in receive buffer 330. For example, the transition from DL to UL may occur during slot (0) of slot 535. As further illustrated by the letter "X," the non-read slot group 820 indicates that the UE105-1 cannot read from slot (0) to slot (3) of the slot group 535. In slot (6) of slot group 515 in UL510, UE105-1 may begin transmitting. As further illustrated by the letter "T," the transmit slot group 805 indicates that the UE105-1 may transmit from slot (6) to slot (7) of the slot group 515. Thereafter, at slot (3) of slot group 540, UE105-1 may switch back to DL 505.

In connection with transmitting packets during the transmit slot group 810, FIG. 8 illustrates the UE105-1 receiving USFs during slots (6) and (7) of the slot group 530. At a time proximate thereto, UL scheduler 310 may detect that there are packets corresponding to the first USF to transmit, but no packets corresponding to the second USF to transmit. However, in one implementation, the UE105-1 may choose to transmit the packet at slot (7) of the slot group 520. For example, UE105-1 may switch to transmitting on the UL during time slot (1) of transmit time slot group 825. During time slot (7) of transmit time slot group 810, UE105-1 may transmit. Thereafter, given the status of the transmit buffer 315, the UL scheduler 310 may inform the DL reader 325 to read from the receive buffer 330. However, the DL reader 315 may not be able to read because the UE105-1 may switch back during slot (3) of the non-read slot set 825.

In connection with transmitting packets at the transmit slot group 815 component, fig. 8 illustrates UE105-1 receiving a USF during slot (7) of slot group 535. The plus sign ("+") illustrated in slot (6) of slot group 535 indicates that a USF may not be received because an RRBP poll may be scheduled for slot (6) of slot group 815. As shown in fig. 8, the non-read slot group 830 indicates that UE105-1 cannot read from slots (0) through (2). During slot (6) of transmit slot group 815, UE105-1 may transmit an ACK or NACK. It should be noted, however, that GERAN may not transmit on the DL during the non-read slot 830 because GERAN knows that UE105-1 will transmit an ACK or NACK during this time. For this, no retransmission is necessary.

Further, UL scheduler 310 may detect that there are no packets corresponding to the USF to transmit, and during slot (2) of non-read slot group 830, UE105-1 may switch back to reading for DL reception.

Fig. 9 is a diagram illustrating the following concept: prioritizing UL transmissions, reading for DL reception when UE105-1 does not need to transmit, and selecting the time slot that minimizes DL slot loss. As shown, timing diagram 900 may include DL505 and UL510 as described above in connection with fig. 5. In this example, the time slot allocation for UE105-1 is 4 slots for UL (as indicated by time slot groups 515, 520, etc.); 8 slots are used for DL (as indicated by slot groups 530, 535, etc.).

UE105-1 may operate in EDA mode with a Basic Transmission Time Interval (BTTI) USF mode and a shortened transmission time interval (RTTI) mode (e.g., 10 millisecond (ms) TTI). That is, as described in the GERAN specification, in the BTTI USF mode, the USF may be mapped to 4 bursts transmitted on one of a pair of DL Physical Downlink Channels (PDCHs) during 4 consecutive Time Division Multiple Access (TDMA) frames. For purposes of discussion in conjunction with fig. 9, a TDMA frame may correspond to 8 time slots. In RTTI mode, a radio block includes 4 bursts transmitted using a pair of PDCHs in each of two consecutive TDMA frames. Thus, the transmission time may be half of the basic radio block period (i.e., 10ms instead of 20 ms). Thus, for purposes of discussion, the TTI of fig. 9 may be based on two slots.

Based on the above, the following scenario may occur. UE105-1 may receive a USF (not shown) for slot group 515. Near this point, UL scheduler 310 may detect that there are no packets to transmit in transmit buffer 315. The DL reader 325 may read from the receive buffer 330 during the UL allocation slots.

In connection with transmitting packets during transmit slot group 905, FIG. 9 illustrates UE105-1 receiving a USF during slot (4) of slot group 530. At a time close to this, the UL scheduler may detect that there is a packet in the transmit buffer 315 to transmit, and the transmit selector 335 may (prioritize the transmission of the detected packet and) select a time slot for transmission. For example, based on the state of transmit buffer 315, transmit selector 335 may determine to transmit during time slots (6) and (7) of transmit time slot group 905. As further illustrated, the non-read slot group 910 indicates that the UE105-1 is unable to read from slots (0) through (3) of the slot group 540. However, the DL reader determiner 320 may read during time slot (4) of the transmission time slot group 905.

Fig. 10 is a diagram illustrating the following concept: when the UE105-1 does not need to transmit, UL transmission is prioritized and reading is performed for DL reception. As shown, timing diagram 1000 may include DL505 and UL510 as described above in connection with fig. 5. The time slot allocation for UE105-1 is 4 slots for UL (as indicated by slot groups 515, 520, etc.); 8 slots are used for DL (as indicated by slot groups 530, 535, etc.). In this example, the slot stream is set to a 5ms TTI mode. However, it should be appreciated that the 5ms TTI is not yet available according to existing GERAN specifications. For purposes of discussion, a 5ms slot stream may correspond to 4 slots. The UE105-1 may operate in EDA mode.

Based on the above, the following scenario may occur. UE105-1 may receive a USF (not shown) for slot group 515. Near this point, UL scheduler 310 may detect that there are no packets to transmit in transmit buffer 315. DL reader 325 may read from the DL transmission and store in receive buffer 330 during the UL allocation slot (i.e., slot group 515) corresponding to slot (7) of slot group 530 through slot (2) of slot group 535.

In connection with transmitting packets during transmit slot group 1005, FIG. 10 illustrates UE105-1 receiving a USF during slot (4) of slot group 530. Near this point, UL scheduler 310 may detect that there are packets to send in transmit buffer 315 and may send the detected packets in preference to reading the packets in receive buffer 330. Based on the state of the transmit buffer 315, the UE105-1 may transmit the detected packet, as shown by the transmit slot group 1005. As further illustrated by the non-read slot set 1010, UE105-1 is unable to read from slot (4) of slot set 535 to slot (3) of slot set 540.

Fig. 11 is a diagram illustrating the following concept: the UL transmission is prioritized, the reading is done for DL reception when no transmission is needed, and the slot that minimizes the DL slot loss is selected. As shown, timing diagram 1100 may include DL505 and UL510 as described above in connection with fig. 5. In this example, the time slot allocation for UE105-1 is 8 time slots for UL (as indicated by time slot groups 515, 520, etc.); 8 slots are used for DL (as indicated by slot groups 530, 535, etc.). The UE105-1 may operate in EDA mode. Further, UE105-1 may receive the USF during time slots (0) and (4). As described below, this measure of USF granularity may improve UL throughput for the associated TBF. That is, in the event that the UE105-1 cannot read a particular USF, subsequent USFs may be read, which improves the throughput of the UE 105-1.

Based on the above description, the following scenario may arise. UE105-1 may receive an RRBP poll (as indicated by the letter "P") and a USF prior to slot group 530. Near this point, UL scheduler 310 may detect that there is a packet in transmit buffer 315 to transmit. UL priority processor 305 may transmit these packets to be transmitted in preference to reading packets from DL transmissions. Thus, the transmit slot group 1105 indicates that the UE105-1 may transmit from slot (0) to slot (7) of the slot group 515, and the non-read slot group 1120 indicates that the UE105-1 cannot read from slot (2) of the slot group 530 to slot (3) of the slot group 535. Thus, if a USF is received during the non-read slot group 1120, UE105-1 may not be able to read it. For example, the USF received during slot (0) within the non-read slot group 1120 cannot be read. However, since in this example the USF granularity provides that the USF is also sent during slot (4), the throughput of UE105-1 may be improved.

In connection with transmitting packets during the transmit slot group 1110, fig. 11 illustrates that the UE105-1 may transmit an ACK or NACK based on the received RRBP poll. In one implementation, sending an ACK or NACK may not involve the selection of a time slot by the transmit selector 335, as RRBP polling may schedule the sending of the ACK or NACK to a particular time slot. In another implementation, this may not be the case. However, as shown, the ACK or NACK may be transmitted during slot (0) indicated by the transmission slot group 1110. Thus, the non-read slot group 1125 indicates that the UE105-1 cannot read from slots (2) through (4) of the slot group 540. It should be noted, however, that GERAN may not transmit on the DL during the non-read slot set 1125, because GERAN knows that UE105-1 will transmit an ACK or NACK during this time. For this, no retransmission is necessary.

In connection with transmitting packets during the set of transmit slots 1115, the UE105-1 may select UL slots for transmission such that the loss of DL slots for reading is minimized. For example, as described above, UE105-1 may receive the USF during slot (4) of slot group 535. Near this point in time, transmit selector 335 may select the time slot in which the packets will be transmitted during time slot group 535. For example, based on the state of the transmit buffer 315, it is assumed that only one time slot is needed to transmit the packets in the transmit buffer 315. Thus, a packet may be transmitted during slot (7) of slot set 525.

It should be appreciated that 5-11 provide illustrations of scenarios in which one or more rule-based schemes may be employed, the scenarios and/or combinations of rule-based schemes described should not be considered an exhaustive application of the concepts described herein.

Fig. 12 and 13 are flowcharts illustrating example processes that may be associated with the rule-based schemes described herein. It can be appreciated that a UE that is not capable of transmitting and receiving simultaneously, such as UE105-1, may perform the processes described in conjunction with fig. 12 and 13. Further, a network (e.g., network 110) may be configured to transmit on the DL to UE105-1 even when UE105-1 may be scheduled to transmit.

Fig. 12 illustrates a flow diagram related to UL transmission prior to DL reception and reading when there are no packets to transmit. As shown in fig. 12, example process 1200 may begin with receiving a USF indicating a transmission time instant (block 1205). For example, UE105-1 may receive a USF from device 115 indicating a time to transmit a packet. The amount of time that the UE105-1 may transmit may be based on the UL slot allocation corresponding to the multislot class capability of the UE 105-1. The value of the USF may be determined (block 1210). UE105-1 may determine the value of the USF to have knowledge of the available UL resources.

It may be determined whether there are packets to send (block 1215). For example, UL scheduler 310 of UE105-1 may determine whether there are packets in transmit buffer 315 to transmit. If it is determined that there are packets to send (block 1215 — yes), UL priority processor 305 may send UL packets in preference to the reading of DL packets (block 1220). The UE105-1 may transmit the packet based on the USF (block 1225).

On the other hand, if it is determined that there are no packets to send (block 1215 — no), the DL reader determiner 320 may determine that the UE105-1 may read the DL packets (block 1230). For example, the UE105-1 may read and store packets in the receive buffer 330 during times when the UE105-1 may be scheduled to transmit.

Although fig. 12 illustrates an example process 1200, in other implementations, fewer, additional, or different operations may be performed.

Fig. 13 illustrates a flow chart for selecting a time slot for transmission to minimize the loss of read and/or receive packets. As shown in fig. 13, the example process 1300 may begin with receiving a USF indicating a transmission time instant (block 1305). For example, UE105-1 may receive a USF from device 115 indicating a time to transmit a packet. The amount of time that the UE105-1 may transmit may be based on the UL slot allocation corresponding to the multislot class capability of the UE 105-1. The value of the USF may be determined (block 1210). UE105-1 may determine the value of the USF to have knowledge of the available UL resources.

A determination may be made as to whether there is a packet to send (block 1315). For example, UL scheduler 310 of UE105-1 may determine whether there are packets in transmit buffer 315 to transmit. If it is determined that there are packets to send (block 1315 — yes), UL priority processor 305 may send the UL packet in preference to the reading of the DL packet (block 1320).

The time slot for transmitting the packet may be selected to minimize the loss of time slots for reading DL packets (block 1325). For example, transmit selector 335 may select a time slot for transmitting the packet as described above. In one implementation, the time slots for transmission may be selected according to an order from the last time slot of the group of UL transmission time slots to the earliest time slot within the group of UL transmission time slots. In another implementation, the slots for transmission may be selected according to an order from an earliest slot within the group of UL transmission slots to a last slot within the group of UL transmission slots.

The packet may be transmitted based on the selected time slot (block 1330). The UE105-1 may transmit the packets in the transmit buffer 315 according to the time slot selected by the transmit selector 335.

On the other hand, if it is determined that there are no packets to send (block 1315-no), the DL reader determiner 320 may determine that the UE105-1 may read the DL packets (block 1335). For example, the UE105-1 may read and store packets in the receive buffer 330 during times when the UE105-1 may be scheduled to transmit.

Although fig. 13 illustrates an example process 1300, in other implementations, fewer, additional, or different operations may be performed.

Fig. 14 illustrates a flow chart of an example process for transmitting to a UE, such as UE 105-1. It may be appreciated that the process described in connection with fig. 14 may be performed by a wireless station (e.g., device 115). As shown in fig. 14, the example process 1400 may begin by identifying a multislot class for a UE (block 1405). For example, the device 115 may identify that the UE105-1 is not capable of receiving and transmitting simultaneously.

The schedule for transmission may be sent on the DL to the UE (block 1410). The device 115 may transmit one or more USFs indicating to the UE105-1 the time at which the data is transmitted.

Data to be received during the scheduling of transmissions may be transmitted to the UE on the DL (block 1415). The device 115 may transmit data on the DL to the UE105-1 to be received during scheduling for transmission. The above-described operations may be performed even if the device 115 recognizes that the UE105-1 cannot receive and transmit simultaneously.

Although fig. 14 illustrates an example process 1400, in other implementations, fewer, additional, or different operations may be performed. For example, device 115 may retransmit packets that were not received by UE105-1 during scheduling for transmission. As described above, the device 115 may determine which packets to retransmit based on the packet reception from the UE105-1 and the corresponding time slots.

The foregoing description of implementations provides illustration, but is not intended to be exhaustive or to limit the implementations to the precise form disclosed. In this regard, the concepts described herein may have broader application. Furthermore, based on the concepts described herein, a UE that is not capable of receiving and transmitting simultaneously may be able to support 8 slots per carrier, which is currently limited to UEs with type 2 classification.

Further, while the sequence of blocks has been described with respect to the processes shown in fig. 12-14, the order of the blocks may be modified in other implementations. Furthermore, independent blocks may be performed in parallel. It should also be noted that the processes illustrated in fig. 12-14 and/or other processes described herein may be performed by one or more devices based on instructions stored on a computer-readable medium. It will be apparent that the devices described herein may be implemented in many different forms of software, firmware, and hardware, and in the implementations illustrated in the figures. The actual software code or specialized control hardware used to implement these concepts is not limiting of the invention. Thus, the operation and behavior of the devices were described without reference to the specific software code — it being understood that software and control hardware could be designed to implement the concepts based on the description herein.

Although particular combinations of features are recited in the claims and/or disclosed in the specification, these combinations should not be construed as limiting the invention. Indeed, many of these features may be combined in ways not specifically recited in the claims and/or disclosed in the specification.

No element, act, or instruction used in the present application should be construed as critical or essential to the implementations described herein unless explicitly described as such.

Claims (21)

1. A method performed by a user equipment (105) for downlink reception, characterized by:

receiving (1205, 1305), by a user equipment (105) that is not capable of simultaneous transmission and reception, a schedule for transmitting data on an uplink;

the user equipment detecting (1215, 1315) whether there is data to be sent on the uplink; and

the user equipment receives (1230, 1335) data associated with the downlink during a time corresponding to the schedule when it is determined that there is no data to transmit.

2. The method of claim 1, further comprising:

upon determining that there is data to transmit on the uplink, transmitting the data in preference to receiving data associated with the downlink (1220); and

transmitting (1225) data on an uplink based on the scheduling.

3. The method of claim 1, further comprising:

upon determining that there is data to transmit on the uplink, transmitting the data on the uplink in preference to receiving data associated with the downlink (1320); and

selecting (1325) a time within the schedule to begin transmitting data on the uplink such that a remaining time within the schedule for receiving data associated with the downlink is maximized.

4. The method of claim 3, wherein an amount of data to transmit is less than an available bandwidth associated with the schedule.

5. The method of claim 4, further comprising:

the user equipment receives data on a downlink during a time corresponding to the schedule when it is determined that there is data to transmit.

6. A method according to claim 1, 2 or 3, wherein the user equipment operates in one of an extended dynamic allocation mode or a dynamic allocation mode.

7. A method according to claim 1, 2 or 3, wherein the schedule for transmitting data identifies time slots associated with uplink time slot assignments.

8. The method of claim 7, further comprising:

the user equipment selects (1325) a time slot for transmitting data according to an order from a last time slot to an earliest time slot within time slots available for transmitting data when it is determined that there is data to transmit on the uplink.

9. An apparatus (105) for prioritizing uplink transmissions, comprising:

means for receiving (1205, 1305) uplink scheduling for transmitting data on an uplink;

means for detecting (1215, 1315) whether there is data to send; and

means for receiving (1230, 1335) from the downlink in a time window of an uplink schedule when it is determined that there is no data to transmit;

wherein the device is a multislot class of device and is incapable of simultaneously receiving from a downlink and transmitting to an uplink.

10. The apparatus of claim 9, further comprising:

means for selecting (1225, 1325) a time to transmit in a time window of an uplink schedule when it is determined that there is data to transmit.

11. The apparatus of claim 9 or 10, further comprising:

means for transmitting data prior to receiving from the downlink when it is determined that there is data to transmit.

12. The apparatus of claim 10, further comprising:

in selecting the time, the time slot to begin transmission is selected such that the remaining time within the uplink schedule is used for the means to receive from the downlink.

13. The apparatus of claim 10, further comprising:

means for transmitting data on the uplink based on the selected time.

14. The apparatus of claim 12, further comprising:

means for receiving from the downlink within a time window scheduled on the uplink prior to transmitting data on the uplink.

15. The device of claim 12, wherein the device comprises a mobile phone.

16. The device of claim 9, wherein the device comprises a user equipment compliant with global system for mobile communications/EDGE radio access network, GERAN, specification.

17. A network side device (115) for performing downlink transmission, characterized by comprising:

means for identifying (1405) a multislot class of a user equipment (105) that is not capable of receiving and transmitting simultaneously;

means for transmitting (1410), on a downlink, to a user equipment, a schedule for the user equipment to transmit; and

means for transmitting (1415) data on the downlink to the user equipment for receipt by the user equipment during scheduling for user equipment transmission.

18. The network-side device of claim 17, wherein the network-side device comprises a wireless station of a mobile network.

19. A wireless communication system, comprising:

user equipment (105) capable of:

receiving (1205, 1305) uplink scheduling for transmission;

reading (1210, 1310) uplink scheduling;

determining (1215, 1315) whether there is data to send; when it is determined that there is no data to transmit, receiving (1230, 1335) data associated with the downlink during uplink scheduling,

wherein the user equipment is unable to transmit and receive simultaneously.

20. The wireless communication system of claim 19, wherein the user equipment is further capable of preferentially transmitting data when it is determined that there is data to transmit (1220, 1320), and transmitting data based on uplink scheduling.

21. The wireless communication system of claim 19, further comprising:

a wireless station (115) capable of transmitting uplink scheduling for transmission to the user equipment.