UL/DL scheduling for full bandwidth utilization

ES 2 425 309 T3

DESCRIPTION

UL / DL planning for full bandwidth utilization

Technical field

The implementations described herein generally refer to scheduling schemes for uplink and downlink transmissions in a communication system.

Background

According to some communication systems, a user equipment (UE) may have a multi-interval class capability. The multi-slot class can define a maximum transfer rate in the uplink (UL - UpLink) and downlink (DL - DownLink) directions. Depending on the multi-slot class of the UE, the UE may be unable to receive and transmit data simultaneously.

Typically, the UE can make its multi-slot class known to a network during a registration process. The network can then, among other things, determine the main transfer direction (eg UL or DL) of a session. Depending on the type of session (eg, an interactive services session), the network may be required to rapidly switch bandwidth demands from UL to DL, and vice versa. However, switching between the UL and DL addresses often takes a significant amount of time. Thus, for the UE unable to receive and transmit data simultaneously, there may be an under-utilization of the available bandwidth, which, in turn, may degrade a quality of service to a user.

In a Global System for Mobile Communications (GSM) / EDGE Radio Access Network (GERAN), for example, the existing specifications for GERAN may not be able to quickly handle changing bandwidth demands since re-assignments of Temporary Block Flows (TBFs) are required. Thus, GERAN can often provide equal bandwidth for ULs and DLs. However, such an approach may result in an under-utilization of the UE's multi-slot capacity and available bandwidth. Additionally or alternatively, the UE's processing resources may be subject to significant demands in order to switch between reception and transmission at any time. This is particularly the case when the UE supports a large number of time slots (eg more than four time slots) for reception and transmission, respectively. As a result, in practice, for example, the UE may be limited to five or six time slots per carrier in one direction, and one or two time slots in the opposite direction.

Document EP 1045559A describes a packet radio network that provides communications on uplink and downlink channels between a base station and user terminals. In periods following the time when the user terminal has no user data to transmit on the uplink, the base station reuses the uplink channel for data communication with another user terminal and queries the user terminal. repeatedly to determine if you have user data to transmit.

The document “Uplink allocation strategies for RTTI TBFs”, Draft 3GPP; GP-070272_FTA & RTTI, 20070207 Collaborative Project of 3^to Generación (3GPP - 3rd Generation Partnership Project, in English), Competence Center for Mobile; 650, route des Lucioles; F-06921 Sophia-Antipolis Cedex; France, describes methods for assigning uplink radio blocks for RTTI TBFs. In particular, “DA per pair” are considered useful to increase the efficiency of the VolP services provided over the GERAN.

EP 1562395A describes a method for controlling packet data transmissions in a TDMA wireless network to provide additional choice in communication channel allocation. The fixed relationship in the timing of downlink assignment signaling and subsequent uplink transmission is altered for certain classes of mobile station in order to avoid physical constraints.

Compendium

One object is to obviate at least some of the above disadvantages and to improve the operability of devices within a communication system.

According to one aspect, a method may include receiving, a user equipment unable to transmit and receive simultaneously, a schedule to transmit data on an uplink, the user equipment detecting whether there is data to be transmitted on the link. upstream, and receiving, the user equipment, during a time corresponding to the schedule, data associated with a downlink, when it is determined that there is no data to be transmitted.

ES 2 425 309 T3

In accordance with another aspect, a device may include a memory for storing instructions and a processor for executing the instructions. The processor can execute instructions to receive an uplink schedule to transmit to another device, detect if there is data to be transmitted, and select a time within a time window of the uplink schedule to transmit when it is determined that there is data to be transmitted, or received from a downlink within the uplink scheduling time window, when it is determined that there is no data to be transmitted, where the device is of a multi-slot class that is unable to receive from the downlink and transmit to the uplink at the same time.

In accordance with yet another aspect, a device may include memory for storing instructions and a processor for executing instructions. The processor can execute the instructions and recognize a multi-slot class from a user equipment that is unable to receive and transmit simultaneously, transmit on a downlink to the user equipment a schedule for the user equipment to transmit, and transmit data. on the downlink to the user equipment to be received during planning to transmit.

According to yet another aspect, a system may include user equipment capable of receiving an uplink schedule to transmit, read the uplink schedule, determine if there is data to be transmitted, prioritize a data transmission when it is determined that there is data to be transmitted and transmit the data based on the uplink planning, or receive data associated with a downlink during uplink planning when it is determined that there is no data to be transmitted.

According to another aspect, a computer-readable medium can contain instructions executable by at least one processor of a device that is unable to receive and transmit at the same time. The computer-readable medium may include one or more instructions to receive a schedule to transmit data on an uplink, one or more instructions to determine whether there is data to be transmitted on the uplink, and one or more instructions to receive data associated with a downlink, during a time corresponding to the schedule to transmit, when it is determined that there is no data to be transmitted.

Brief description of the drawings

Fig. 1 is a diagram illustrating devices communicating with each other through 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;

Figs. 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, where the UE includes a radiotelephone;

Figs. 5-11 are diagrams illustrating an example use of time slots that may be associated with the concepts described herein; and Figs. 12-14 are flow charts 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 can identify the same or similar elements. Also, the following description does not limit the invention.

The term "may" be used throughout this application and is intended to be construed, for example, as "which has the potential to", "configured to", or "what it can do", and not in a mandatory sense (eg, as it should"). The terms "a", "an", "some", "a" and "the", "the", "the", "the" are intended to be construed as including one or more elements. Where a single item is intended, the term "one" or similar language is used. Furthermore, the phrase "based on" is intended to be construed as "based, at least in part, on", unless explicitly stated otherwise. The term "and / or" is intended to be construed as including any and all combinations of one or more of the associated list items.

The concepts described in this specification refer to improving the use of bandwidth in a communication system, as well as other advantages that may necessarily be derived from them or are apparent from the description that follows. The communication system is intended to be interpreted broadly to include any type of wireless network, such as cellular or mobile networks (for example, GSM, Universal Mobile Telecommunication System (UMTS), Evolution to Long Term Evolution (LTE), Multiple Access by Band Code Division

ES 2 425 309 T3

Wideband Code Division Multiple Access (WCDMA), Ultra Broadband for Mobile (UMB Ultra Mobile Broadband), 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 cable networks (eg, Digital Subscriber Line (DSL), Integrated Services Digital Network (ISDN), etc.). The terms "communication system" and "network" can be used interchangeably throughout this description. The term "packet", as used herein, is intended to be interpreted broadly to include a data diagram, a frame, a cell, a block, or any other type of data transmission / reception unit. The embodiments described herein may employ one or more rule-based schemes in conjunction with UL and DL. Rule-based schemes may include prioritizing UL transmissions in the UE before reading DL receptions. Additionally or alternatively, the UE can read DL receptions when the UE has nothing to transmit. Additionally or alternatively, the UE may select UL timeslots in which to transmit so that the loss of DL timeslots for reading is minimized.

In one implementation, rule-based schemas can supplement existing GERAN specifications. Rule-based schemes can employ a Flexible Time Slot Allocation. That is, the time slot assignment (for example, the number of UL time slots and the number of DL time slots) assigned to the Ue can be changed by Time Transmission Interval (TTI). English).

For the purpose of explanation, a multi-slot communication system will be described herein. It will be apparent that the concepts described herein are not dependent on the use of this particular type of communication system. On the contrary, these concepts can be adapted to other types of networks, communication standards, etc., which are not specifically described in this specification. A "multi-slot class enabled communication system" may include a network, such as a GERAN or a General Packet Radio Service (GPRS) network.

In view of rule-based schemes, the UE's multi-slot class capacity can be utilized in a way that uses all available bandwidth. Additionally or alternatively, the UE may support more time slots for reception and transmission (eg, up to eight time slots per carrier and address) even though the multiple slot class capability of the UE does not support simultaneous reception and transmission. Additionally or alternatively, a lower demand requirement may be provided in the switching time between UL and DL and / or a greater number of time slots for reception and transmission than corresponding to the multiple slot class. Additionally or alternatively, the communication system can simultaneously schedule the UE in all available time slots in both UL and DL, and the switching time requirements can limit the receive bandwidth only in cases where there is a UL broadcast (prioritized).

FIG. 1 is a diagram illustrating an exemplary communication system 100 in which the concepts described herein may be implemented. As illustrated, the communication system 100 may include the UE 105-1, a network 110 that includes a device 115, and a device 120. As illustrated, the UE 105-1 may be coupled in communication to the device 120 through from network 110. For example, device 115 may be communicatively coupled to UE 105-1.

The UE 105-1 may include a device that is communication capable and capable of executing one or more of the rule-based schemes described herein. For example, the UE 105-1 can include a telephone, a computer, a personal digital assistant (PDA), a browser, a terminal for personal communication systems (PCS). ), a kiosk terminal, pervasive computing device, and / or some other type of user device configured to perform one or more of the functions (i.e. rule-based schemas) associated with the concepts described herein. The UE 105-1 may include a device that has multi-slot class capability. The UE 105-1 may include a device that is unable to receive and transmit simultaneously.

Network 110 may include, in addition to device 115, one or more networks of any type, including a wireless network or a wired network. For example, network 110 may include a local area network (LAN), a wide area network (WAN), a telephone network, such as the Switched Telephone Network. Public Switched Telephone Network (PSTN) or a Public Land Mobile Network (PLMN), a satellite network, an intranet, the Internet, or a combination of networks or systems Communication. Device 115 may include a device that is communication capable. For example, device 115 can include a wireless station or a cable station. The term "wireless station" is intended to be interpreted broadly to include any type of device that can communicate with the UE 105-1 over a wireless link. For example, a wireless station can include a base station (BS - Base Station, in English), a base station transceiver (BTS - Base Station Transceiver, in English) (for example, in a GSM communication system) , an eNodeB (for example, in an LTE communication system), a Node B (for example, in a communication system

ES 2 425 309 T3 UMTS communication), a repeater, a repeater node or some other type of device. The term "cable station" is intended to be interpreted broadly to include any type of device that can communicate with the UE-105-1 over a cable link. For example, a cable station can include an edge router, switch, gateway, or some other type of device. Device 115 may include a device capable of recognizing a multi-slot capability from another device ^ such as UE 105-1. Additionally or alternatively, device 115 may include a device capable of recognizing that another device is unable to receive and transmit simultaneously. Device 120 may include a device that is communication capable. For example, device 120 may include a UE, a server that provides resources and / or services, and / or some other type of device capable of maintaining end-to-end communication with UE 105-1 through device 115.

FIG. 2A is a diagram illustrating example components of the UE 105-1. As illustrated, the UE 105-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 in This specification is intended to be interpreted broadly to include, for example, hardware, software and hardware, firmware, etc. Transceiver 205 may include a component capable of transmitting and receiving information. For example, transceiver 205 may include transceiver circuitry for transmitting packets to, and receiving packets from, other communication devices and / or systems.

Processor 210 may include a component capable of interpreting and / or executing instructions. For example, processor 210 may include a general purpose processor, a microprocessor, a data processor, a coprocessor, 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 a component capable of storing information (eg, data and / or instructions). For example, memory 215 may include Random Access Memory (RAM), Dynamic Random Access Memory (DRAM), Static Random Access Memory (SRAM). - Static Random Access Memory, a Synchronous Dynamic Random Access Memory (SDRAM), a Ferroelectric Random Access Memory (FRAM), Read Only Memory (ROM), Programmable Read Only Memory (PROM), Erasable Programmable Read Only Memory (EPROM) Memory, an Electrically Erasable Programmable Read Only Memory (EEPROM), and a flash memory.

Input device 220 may include a component capable of receiving input from one user device and / or another. For example, input device 220 can include a keyboard, numeric keypad, mouse, button, switch, microphone, display, and / or speech recognition logic.

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

The bus 230 may include a component capable of allowing communication between two and / or between several of the components of the 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 bus triggers, bus arbiters, bus interfaces, and / or clocks.

Although Fig. 2A illustrates example components of the UE 105-1, in other implementations, the UE 105-1 may include fewer, additional, and / or different components other than those depicted in Fig. 2A. For example, the UE 105-1 may include a hard disk or some other type of computer-readable medium along with a corresponding trigger. The term "computer-readable medium", as used herein, is intended to be interpreted broadly to include a physical or logical storage device. It will be apparent that one or more components of the UE 105-1 may or may be capable or capable of performing one or more of the other tasks associated with one or more of the other components of the UE 105-1.

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

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

Processor 255 may include a component capable of interpreting and / or executing instructions. For example, processor 255 may include a general purpose processor, a microprocessor, a data processor, a coprocessor, a network processor, an application-specific integrated circuit (ASIC - Application

ES 2 425 309 T3

Specific Integrated Circuit, a controller, a programmable logic device, a chipset, and / or a Field Programmable Gate Array (FPGA).

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

Bus 265 may include a component capable of allowing communication between two and / or several of the components of device 115. For example, bus 265 may include a system bus, an address bus, a data bus, and / or or a control bus. Bus 265 may also include bus triggers, bus arbitrators, 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 those depicted in FIG. 2B. For example, device 115 may include a hard disk or some other type of computer-readable medium along with a corresponding trigger. It will be apparent that one or more components of device 115 may be capable of performing one or more of other tasks associated with one or more other components of device 115.

Figs. 3A-3C are diagrams illustrating exemplary functional components capable of implementing one or more of the rule-based schemes described herein. These example functional components will be described in conjunction with UE 105-1. As previously mentioned previously, one of the rule-based schemes includes prioritizing the UL transmissions before reading the DL receptions. Fig. 3A illustrates exemplary functional components to accomplish this function, referred to as a UL 305 prioritizer. The UL 305 prioritizer can be implemented using one or more of the components depicted in FIG. 2A. For example, the UL 305 prioritizer can be implemented in transceiver 205 and memory 215.

The UL 305 prioritizer may include functional components, such as a UL 310 scheduler and a 315 transmit buffer. The UL 310 scheduler may have knowledge of a UL transmit schedule and the ability to detect when a packet is stored. in the transmit buffer 315. The transmit buffer 315 can store packets for transmission on the UL.

In an example operation, the UL scheduler 310 can determine if the transmission buffer 315 is storing a packet for a transmission on the UL. The UL 310 scheduler can make such a determination in the vicinity of a time when the UE 105-1 can be scheduled for a transmission on the UL. If the UL scheduler 310 determines that the transmission buffer 315 is storing a packet for a transmission on the UL, then the UE 105-1 may prioritize transmission of the packet on the UL before reading a reception on the DL. The prioritization of a transmission in the UL will be described in more detail below.

Additionally or alternatively, the UE 105-1 can read a reception from the DL when it has nothing to transmit. FIG. 3B illustrates exemplary functional components to accomplish this function, referred to as the DL 320 reader determiner. The DL 320 reader determiner can be implemented using one or more components depicted in FIG. 2A. For example, DL reader determiner 320 can be implemented in transceiver 205 and memory 215.

The DL reader determiner 320 may include functional components, such as the UL scheduler 310, the transmit buffer 315, a DL reader 325, and a receive buffer 330. The scheduler 310 and a transmit buffer 315 it can operate in a manner similar to that previously described. DL reader 325 may be able to read a packet and store it in transmit buffer 330. Transmission buffer 330 can store a packet received from a transmission on the DL.

In an example operation, the UL scheduler 310 can determine if the transmission buffer 315 is storing a packet for a transmission on the UL. The UL 310 scheduler may make such a determination in the vicinity of a time when the UE 105-1 may be scheduled for a transmission on the UL. If the UL 310 scheduler determines that the transmit buffer 315 is not storing a packet for a transmission on the UL, then the UL 310 scheduler can notify the DL 325 reader. The DL 325 reader can read from a transmission on the DL and store in the receive buffer 330. For example, the DL reader 325 can read in a DL timeslot and check if there is a packet for itself. If there is a packet for itself, the packet can be stored in the transmit buffer

ES 2 425 309 T3

330. It will be apparent that, for example, the UL scheduler 310 may also be aware that the receive buffer 330 is storing a packet. The reading of the receptions in the Dl will be described in more detail in the following.

Additionally or alternatively, the UE 105-1 can select a UL time slot to transmit so that the loss of time slots on the DL for reading is minimized, also considering that the transmission on the DL is not using all slots. time of the DL at a given TTI. FIG. 3C illustrates example functional components to perform this function, referred to as a transmission selector 335. Transmission selector 335 can be implemented using one or more components depicted in FIG. 2A. For example, transmission selector 335 can be implemented in transceiver 205 and memory 215.

The transmit selector 335 may include functional components, such as the UL 310 scheduler, the transmit buffer 315, and a timeslot selector 340. The UL 310 scheduler and the transmit buffer 315 may operate in a way. similar to that previously described. The timeslot selector 340 may select a UL timeslot to transmit that minimizes the loss of DL timeslots for reading, or in other words, maximizes the number of DL timeslots for reading.

In an example operation, the UL scheduler 310 can determine if the transmission buffer 315 is storing a packet for a transmission on the UL. The UL 310 scheduler can make such a determination in the vicinity of a time when the UE 105-1 can be scheduled for a transmission on the UL. If the UL 310 scheduler determines that the transmission buffer 315 is storing a packet for a transmission on the UL, then the UL 310 scheduler may notify the time slot selector 340. The time slot selector 340 may select a UL timeslot to transmit the packet that minimizes the loss of DL timeslots. The packet or packets in the transmission buffer 315 may or may be transmitted or transmitted based on the selected or selected time slot (s). The selection of a UL time slot by the time slot selector 340 will be described in more detail below.

FIG. 4 is a diagram of an example implementation of the UE 105-1 in which the UE 105-1 includes a radiotelephone. As illustrated, the UE 105-1 may include, among other things, a microphone 405 (for example, from input device 220) for inputting audio information into the UE 105-1, a speaker 410 (for example, from the output device 225) to provide audio output from the UE 105-1, a keypad 415 (for example, from input device 220) to enter data or select device functions, and a display 420 (for example, input device 220 and / or output device 225) to display data to a user and / or provide a user interface for entering data or selecting device functions.

As mentioned above, the implementations described herein provide rule-based schemes in conjunction with UL and DL that can, among other things, improve bandwidth utilization, etc. For the purpose of explanation, these concepts will be described with reference to the existing GERAN specifications. Furthermore, for the purpose of explanation, it is assumed that the UE 105-1 has a multi-slot class capability that it is unable to receive and transmit simultaneously. Currently, the GERAN specification outlines multi-interval classes ranging from one to forty-five, as well as a corresponding classification of user equipment, such as Type 1 or Type 2. The UE 105-1 can be considered a Type 1 device that has, among other things, a maximum number of time slots to receive, a maximum number of time slots to transmit, and a sum (i.e., a total number of UL and DL time slots that can be used by TTI). Furthermore, device 115 can be considered a wireless station in the GERAN.

Based on this framework, the GERAN would not transmit to the UE 105-1 on the DL when the UE 105-1 is scheduled to transmit. However, according to the concepts described in this specification, the GERAN can transmit to the UE 105-1 on the DL even when the UE 105-1 is scheduled to transmit.

Figs. 5-11 are diagrams illustrating example uses of time slots that may be associated with the concepts described herein. It will be apparent that the UL and DL time slots are illustrated in Figs. 5-11 as changed in time. For example, the UL frame (eg, eight time slots) may be shifted in time by a number of time slots (eg, three time slots) from one DL frame to accommodate the class capability of multiple interval of the UE 1051.

For the purpose of explanation in conjunction with Figs. 5-11, it is assumed that the time change capability (for example, from DL reading to UL transmission, and vice versa) of the UE 105-1 is equivalent to Ttb = 1 time interval (that is, where Ttb is a time required for UE 105-1 to be ready to transmit) and Trb = 1 time slot (ie, where Trb is a time required for UE 105-1 to be ready to receive). Also, measurements of the signal level in the adjacent cell are ignored in these examples, and the Packet Associated Control Channel (PACCH), which includes Piggy-backed Acknowledgment (PAN), in English), it can be sent on the DL in a time interval that the UE 105

ES 2 425 309 T3 can read or at a time interval that the UE 105-1 is most likely to be able to read. Furthermore, for the purpose of explanation in conjunction with Figs. 5-11, it is assumed that the UE 105-1 has packets to read from the DL at all times. That is, as previously mentioned, for example, the GERAN can transmit to the UE 105-1 on the DL even when the UE 105-1 is scheduled to transmit.

Fig. 5 is a diagram illustrating the concept of prioritizing a UL transmission over reading a DL reception. As illustrated, a timing chart 500 may include a DL 505 and a UL 510.

The DL 505 and UL 510 may each include a time slot matrix for transmissions on the UL and receptions on the DL.

In each of the DL 505 and UL 510, the time slots are numbered from (0) to (7). For the purpose of explanation, assume that the instruction allocation for the UE 105-1 is four timeslots for the UL and eight timeslots for the DL. These time slot assignments are illustrated in Fig. 5 as a time slot group 520, and a time slot group 525 in the UL 510, and a time slot group 530, a time slot group 535, and a time slot group 540 in the DL 505 . As also illustrated, Uplink State Flags (USFs), as indicated by the letters “U”, can be received on DL 505, from, by For example, device 115, to provide UE 105-1 with an allocation of time slots to transmit. In this example, the receipt of the USF indicates an actual availability to transmit packets during a next group of time slots (ie, time slot group 520 versus time slot group 515). This type of allocation method is called an Extended Dynamic Allocation (EDA) method. It is therefore assumed that the UE 105-1 is operating in EDA mode.

Based on the above, the following scenario can occur. The UE 105-1 may receive a USF during the time slot (4) of the time slot group 530. At a time near that time, the UL 310 scheduler can detect that there are packets in the transmit buffer 315 to be transmitted. The UL 305 prioritizer can prioritize the transmission of these packets over the reading of packets in the receive buffer 330. For example, a change from DL to UL may occur during time slot (6) of time slot group 535. As also illustrated by the letters "X", a no-read time slot group 550 indicates that The UE 105-1 may not read from the time slot (6) of the time slot group 535 to the time slot (3) of the time slot group 540. In the time slot (4) of the time slot group 520 in the UL 510, the UE 105-1 can start transmitting. As also illustrated by the letters "T", a transmission time slot group 545 indicates that the UE 105-1 can transmit from time slot (4) to time slot (7) of the time slot group. 520. Then, during the time slot (3) of the time slot group 540, the UE 105-1 can switch back to the DL 505.

In view of this scheme, the available bandwidth is used to its full extent in light of the switching time capabilities of the UE 105-1. That is, as many time slots as possible are used for transmission on the DL, and the remaining bandwidth is used for transmission on the UL. Furthermore, although the UE 1051 is unable to receive packets during the group of no read time slots 550, and these packets may need to be retransmitted to the UE 105-1, the GERAN can identify any rejected packets (i.e. packets not received ) based on the time slot numbers associated with the received transmission (ie, transmission time slot group 545) from the UE 105-1. Thus, any packets not received can be (immediately) retransmitted thereafter.

Fig. 6 is a diagram illustrating the read concept for a DL reception when the UE 105-1 has nothing to transmit. That is, as long as the Ue 105-1 can be scheduled for transmission on the UL, but the UE 105-1 has nothing to transmit, the UE 105-1 can read receptions on the DL.

As illustrated, a timing chart 600 may include the DL 505 and UL 510 as previously described in conjunction with Fig. 5. Also, the UE 105-1 may be operating in EDA mode with a four slot allocation. time slot for the UL and an allocation of eight time slots for the DL.

In this scenario, the UE 105-1 may not have any packets in transmit buffer 315 to be transmitted. For example, the UE 105-1 may receive a USF during the time slot (4) of the time slot group 530 to transmit during the time slot 520. In a time close to it, the UL 310 scheduler can detect that there are no packets in the transmit buffer 315 to be transmitted. At such a time, according to the DL 320 reader determiner, the UL 310 scheduler can report the status (ie, there are no packets to be transmitted) of the transmit buffer 315 to the DL 325 reader. In this case, the DL 325 reader can read from a transmission on the DL and store in the receive buffer 330 during the time slots assigned in the UL. That is, as illustrated by the time slot group 605, the UE 105-1 can read receptions on the DL during this time period and therefore efficiently use bandwidth, etc. Thus, the allocation of four UL time slots associated with the time slot group 520 (corresponding to the time slots of the time slot group 605) can be used to read DL receptions. This is possible since the GERAN can transmit to the UE 105-1 on the DL even when the UE 105-1 is scheduled to transmit.

ES 2 425 309 T3

Fig. 7 is a diagram illustrating the concept of selecting the time interval for transmission on the UL so that the loss of reading of DL receptions can be minimized. As illustrated, a time chart 700 may include the DL 505 and UL 510 as previously described in conjunction with Fig. 5. Also, the UE 105-1 may be operating in EDA mode with an allocation of four timeslots for the UL and an allocation of eight timeslots for the DL.

In this scenario, the UE 105-1 can select from the UL timeslots to transmit so that the loss of DL timeslots for reading is minimized. For example, the UE 105-1 may receive a USF during the time slot (4) of the time slot group 530 to transmit (for example, during the time slot 520). In a time close to this, the UL scheduler 310 can detect that there are packets in the transmit buffer 315 to be transmitted. In this example case, the UL scheduler 310 may detect that the number of packets to be transmitted is less than a number of packets capable of being transmitted in the time slot group 520. The UL scheduler 310 can report the status of the transmission buffer 315 to the time slot selector 340. The time slot selector 340 can select a time slot or time slots to transmit the packets in the buffer. transmission 315 so that a minimum number of DL time slots can be missed for reading.

In one implementation, the time slot or time slots used or used to transmit may be selected or they may be selected according to an order starting from a last time slot in a group of UL transmission time slots up to a first time slot within the UL transmission time slot group. For example, based on the state of the transmit buffer 315, assume that only one time interval is needed to transmit the packets in the transmit buffer 315. In such a case, the transmit selector 335 may select the interval of time. time or time slots in which or in which these packets will be transmitted during the time slot group 520. For example, as illustrated by the letter "T", a transmission time slot group 705 indicates that the UE 105-1 can transmit these packets during time slot (7) of the time slot group 520. This that is, the time slot selector 340 may select the time to transmit starting from the last time slot within the time slot group 520. As also illustrated by the letters "X", a group of no-read time slots 710 indicates that the UE 105-1 may not read from time slot (1) to time slot (3) of the group of time slots. time 540, which may require retransmission of the corresponding packets associated with those time slots.

On the basis of the above, it will be apparent that the UE 105-1 can read receptions from the DL during the time slots (4) and (5) of the time slot group 520 (corresponding to the time slot (7) of the time slot group time slot 535 and time slot (0) of time slot group 540). Thus, the UL time slot assignment associated with the time slot group 520 can be partially used to read the DL time slots. As a result, a minimum number of DL time slots for reading can be lost during this period. That is, in contrast to transmitting in time slots (5) or (6), where only one time slot can be used for reading, or where no time slot can be used for reading, the UE 105-1 can read during a portion of the time slot group 520.

Depending on the number of packets to be transmitted, however, the selection of the time slots may be different. For example, if two time slots are required to transmit the packets, the time slot selector 340 can select the time slots (6) and (7) from the time slot group 520, if three time slots are required , the time slot selector 340 can select the time slots (5), (6) and (7) of the time slot group 520, if four time slots were necessary to transmit the packets, the time slot selector 340 can select the time slots (4), (5), (6) and (7) of the time slot group 520, if five time slots were necessary to transmit the packets the time slot selector time slot you can select time slots (4), (5), (6) and (7) from time slot group 520 and time slot (7) (not illustrated) from time slot group 525 to broadcast.

It will also be apparent that in another implementation, the time slot or time slots used or used for transmitting may be selected or they may be selected according to an order, starting from a first time slot within a group of time slots. UL transmission time slot until a last time slot within the UL transmission time slot group. In the scenario of Fig. 7, such an implementation would lead to the same result (that is, two time slots can be used for reading).

Fig. 8 is a diagram illustrating the concepts of prioritizing a UL transmission over reading a DL reception, reading a DL reception when the UE 105-1 has nothing to transmit, and selecting the interval time for UL transmission so that the loss of reading from DL receptions can be minimized. As illustrated, a time chart 800 may include the DL 505 and UL 510 as previously described in conjunction with Fig. 5. However, it should be assumed that the time slot allocation for the UE 105-1 is two time slots for the UL (as indicated by the time slot groups 515, 520 and 525) and eight time slots for the DL (as indicated by the groups of

ES 2 425 309 T3 time intervals 530, 535 and 540). The UE 105-1 may be operating in DA Dynamic Allocation mode. This type of allocation method is analogous to EDA mode, except that one EDA is received for each available UL time slot (for example, one by one). In addition to the USFs, Fig. 8 illustrates a Relative Reserved Block Period (RRBP) question, as indicated by the letter “P”, used for DL ​​Acknowledgment (ACK) / DL Non-Recognition ( NACK - Not Acknowledge).

Based on the above, the following scenario can occur. The UE 105-1 may receive an inquiry from RRBP and the USFs before the time slot group 530. In a time close to this, the UL scheduler 310 may detect that there are packets in the transmit buffer 315 to be transmitted. The UL 305 prioritizer can prioritize the transmission of these packets over the reading of a packet or packets in the receive buffer 330. For example, a change from DL to UL may occur during time slot (0) of time slot group 535. As also illustrated by the letters "X", a no-read time slot group 820 indicates that the UE 105-1 may not read from the time slot (0) to the time slot (3) of the time slot group 535. In the time slot (6) of the time slot group 515 in the UL 510, the UE 105-1 can start transmitting. As also illustrated by the letters "T", a transmission time slot group 805 indicates that the UE 105-1 can transmit from time slot (6) to time slot (7) of the time slot group. 515. Then, during the time slot (3) of the time slot group 535, the UE 105-1 can switch back to the DL 505.

Along with transmitting packets during a group of transmission time slots 810, Fig. 8 illustrates the UE 105-1 receiving USFs during time slots (6) and (7) of the time slot group 530. In Nearly this time, the UL scheduler 310 can detect that there are packets to be transmitted in correspondence with the first USF, but that there are no packets to be transmitted in correspondence with the second USF. However, in one implementation, the UE 105-1 may select to transmit the packets in the time slot (7) of the time slot group 520. For example, the UE 105-1 may switch to transmit on the UL during the time slot (1) of a group of transmission time slots 825. During the time slot (7) of a group of transmission time slots 810, the UE 105-1 can transmit. Then, given the status of the transmit buffer 315, the UL 310 scheduler may notify the DL 325 reader to read from the receive buffer 330. However, since the UE 105-1 may be changing Again during the time slot (2) of the no-read time slot group 825, the DL reader 325 may not be able to read.

Along with transmitting packets during a transmission time slot group 815, Fig. 8 illustrates the UE 105-1 receiving a uSf during the time slot (7) of the time slot group 535. The sign (" + ”) Illustrated in time slot (6) of time slot group 535 indicates that a USF may not be received since the RRBP query may be scheduled for time slot (6) of time slot group transmission 815. As illustrated in FIG. 8, a group of no-read time slots 830 indicates that the UE 105-1 may not read from time slots (0) to (2). During the time slot (6) of the transmission time slot group 815, the UE 105-1 may transmit an ACK or a NACk. It should be noted, however, that the GERAN may not transmit on the DL during the no-read time interval 830 since the GERAN knows that the UE 105-1 will be transmitting the ACK or the NACK during this time. In light of this, a retransmission may not be necessary.

Furthermore, the scheduler of the UL 310 can detect that there is no packet to be transmitted in correspondence with the USF, and that the UE 105-1 can switch back to reading the DL receptions during the time interval (2) of the group. of no-read time intervals 830.

Fig. 9 is a diagram illustrating the concepts of prioritizing a UL transmission, reading a DL reception when the UE 105-1 has nothing to transmit, and selecting a time slot that minimizes the loss of time slots by DL. As illustrated, a timing chart 900 may include the DL 505 and UL 510 as previously described above in conjunction with Fig. 5. In this example, the time slot assignment for the UE 105-1 is four time slots for the UL (as indicated by the time slot groups 515, 520, etc.), and eight time slots for DL ​​(as indicated by time slot groups 530, 535, etc.).

The UE 105-1 may be operating in EDA mode with USF Basic Transmit Time Interval (BTTI) mode and Reduced Transmit Time Interval (RTTI) mode. Time Interval) (for example, a TTI of 10 milliseconds (ms)). That is, as outlined in the GERAN specification, in BTTI's USF mode a USF can be mapped into four bursts transmitted on one of the Physical Downlink Channels (PDCHs) of a DL PDCH pair for four consecutive Time Division Multiple Access (TDMA) frames. For the purpose of explanation together with Fig. 9, a TDMA frame can correspond to eight time slots. In RTTI mode, a radio block includes four bursts sent using a PDCH pair in each of two consecutive TDMA frames. As a result, the time to transmit can be half a basic radio block period (ie, 10 ms instead of 20 ms). Thus, for the purpose of explanation, the TTI for Fig. 9 may be based on two time slots.

ES 2 425 309 T3

Based on the above, the following scenario can occur. The UE 105-1 may receive a USF (not shown) for the time slot group 515. At a time near this, the UL 310 scheduler may detect that there is no packet in the transmit buffer 315 to be transmitted. The DL reader 325 can read from the receive buffer 330 during the UL assigned time slots.

In conjunction with transmitting packets during the transmission time slot group 905, Fig. 9 illustrates the UE 105-1 receiving a USF during the time slot (4) of the time slot group 530. In a time close to this, the UL scheduler 310 can detect that there are packets in the transmit buffer 315 to be transmitted and the transmit selector 335 can (prioritize the transmission of the detected packets and) select the time slots to to transmit. For example, based on the status of the transmit buffer 315, the transmit selector 335 may determine to transmit during the time slots (6) and (7) of a group of transmission time slots 905. As also illustrated , a group of no-read time slots 910 indicates that the UE 105-1 may not read from time slots (0) to (3) of time slot group 540. However, the DL read determiner 320 can read during the time slot (4) of the transmission time slot group 905.

Fig. 10 is a diagram illustrating the concepts of prioritizing a UL transmission and reading a DL reception when the UE 105-1 has nothing to transmit. As illustrated, a time chart 1000 may include the DL 505 and UL 510 as previously described above in conjunction with Fig. 5. The time slot allocation for the UE 105-1 is four time slots for the UL (as indicated by the time slot groups 515, 520, etc.), and eight time slots for the DL ( as indicated by time slot groups 510, 535, etc.). In this example, the time slot streams are set in the 5 ms TTI mode. It should be understood, however, that the 5 ms TTI is not yet available according to the existing GERAN specification. For the purpose of explanation, a 5 ms time slot flow may correspond to four time slots. The UE 105-1 may be operating in EDA mode.

Based on the above, the following scenario can occur. The UE 105-1 may receive a USF (not shown) for the time slot group 515. In a time close to this, the UL scheduler may detect that there is no packet in the transmit buffer 315 to be transmitted. . The DL reader 325 can read from a DL transmission and store in the receive buffer 330 during the time slots assigned to the UL (i.e., the time slot group 515) corresponding to the time slot (7) of the time slot group 530 to time slot (2) of time slot group 535.

Along with transmitting packets during a transmission time slot group 1005, FIG. 10 illustrates the UE 105-1 receiving a USF during the time slot (4) of the time slot group 530. In a time close to this, the UL scheduler 310 can detect that there are packets in the transmit buffer 315 to be transmitted, and the transmission of the detected packets can be prioritized over the reading of a packet or packets in the buffer. 330. Based on the status of the transmit buffer 315, the UE 105-1 can transmit the detected packets, as illustrated by the transmit time slot group 1005. As also illustrated by the no-read time slot group 1010, the UE 105-1 is unable to read from the time slot (4) of the time slot group 535 to the time slot (3) of the slot group. time 540.

Fig. 11 is a diagram illustrating the concepts of prioritizing a UL transmission, reading a DL reception when there is nothing to transmit, and selecting a time slot that minimizes the loss of DL time slots. As illustrated, a time chart 1100 may include the DL 505 and UL 510 as previously described in conjunction with Fig. 5. In this example, the time slot assignment for the UE 105-1 is eight time slots for the UL (as indicated by the time slot groups 515, 520, etc.) and eight time slots for the DL (as indicated by 530, 535, etc.). The UE 105-1 may be operating in EDA mode. Furthermore, the UE 105-1 can receive USFs during the time intervals (0) and (4). As will be described below, this USF Granularity measure can improve the UL result for relevant TBFs. That is, in cases where a particular USF may not be read by the UE 105-1, a subsequent USF may be read, which can improve the performance of the UE 105-1.

Based on the above, the following scenario can occur. The UE 105-1 may receive an RRBP inquiry (as indicated by the letter "P") and a USF before the 530 time slot group. In a time close to this, the UL 310 scheduler may detect that there are packets in the transmit buffer 315 to be transmitted. The UL 305 prioritizer can prioritize the transmission of these packets over reading a packet or packets from a DL transmission. As a result, a group of transmission time slots 1105 indicates that the UE 105-1 can transmit from time slot (0) to time slot (7) of time slot group 515, and that a group of slots time slot 1120 indicates that the UE 105-1 may not read from time slot (2) of time slot group 530 to time slot (3) of time slot group 535. Thus, if a USF is received during the group and non-read time intervals 1120, the UE 105-1 may not be able to read it. For example, the USF received during the time slot (0) within the no-read time slot group 1120 may not be read. However, since the

ES 2 425 309 T3

Granularity of the USF of this example provides that the USFs are transmitted during the time slots (4) also, the performance of the UE 105-1 can be improved.

Along with transmitting packets during a group of transmission time slots 1110, FIG. 11 illustrates that the UE 105-1 can transmit an ACK or a NACK based on the received RRBP query. In one implementation, the transmission of the ACK or the NACK may not involve the time slot selection carried out by the transmission selector 335 since the RRBP query may schedule the transmission of the ACK or the NACK for a particular time slot. . In another implementation, this may not be the case. As illustrated, however, the ACK or NACK may be transmitted during the time slot (0), as indicated by the transmission time slot group 1110. As a result, a non-read time slot group 1125 indicates that the UE 105-1 may not read from time slots (2) to (4) from time slot group 540. It should be noted, however, that the GERAN may not transmit on the DL during the no-read time interval 1125 since the GERAN knows that the UE 105-1 will be transmitting the ACK or the NACK during this time. In light of this, a retransmission may not be necessary.

Along with transmitting packets during a group of transmission timeslots 1115, the UE 105-1 can select the UL timeslots to transmit so that the loss of DL timeslots for reading is minimized. For example, as previously described, the UE 105-1 may receive the uSf during the time slot (4) of the time slot group 535. In time close to this, the transmission selector 335 may select the time slot or time slots in which or in which these packets will be transmitted during the time slot group 525. For example, based on status from the transmit buffer 315, it should be assumed that only one time interval is needed to transmit the packets in the transmit buffer 315. As a result, the packets can be transmitted during the time slot (7) of the time slot group 525.

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

Figs. 12 and 13 are flow charts illustrating example processes that can be associated with the rule-based schemes described herein. It will be apparent that the processes described in conjunction with Figs. 12 and 13 can be implemented by a UE that is unable to transmit and receive simultaneously, such as UE 105-1. Furthermore, that a network, such as network 110, can be configured to transmit on the DL to the UE 105-1 even when the UE 105-1 may be scheduled to transmit.

Fig. 12 illustrates a flow chart relating to prioritizing a UL transmission over a DL reception, and a read when there are no packets to transmit. As illustrated in FIG. 12, the example process 1200 may begin with the receipt of a USF indicating a time to transmit (block 1205). For example, the UE 105-1 may receive the USF from the device 115 indicating a time to transmit packets. The amount of time in which the UE 105-1 can transmit may be based on a UL time slot allocation corresponding to the multiple slot class capability of the UE 105-1. A value of the USF can be determined (block 1210). The UE 105-1 can determine a USF value in order to be aware of the available UL resources.

It can be determined if there are packets to be transmitted (block 1215). For example, the UL 310 scheduler of UE 105-1 may determine if there are packets in transmit buffer 315 to be transmitted. If it is determined that there are packets to be transmitted (block 1215-YES), then the UL prioritizer 305 may prioritize the transmission of the UL packets over reading the DL packets (block 1220). The UE 105-1 can transmit the packets based on the USF (block 1225).

On the other hand, if it is determined that there are no packets to be transmitted (block 1215-NO), then the determiner of the DL reader 320 can determine that the UE 105-1 can read packets from the DL (block 1230). For example, the UE 105-1 may read packets and store in the receive buffer 330 for a time that the UE 105-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 time slots to transmit that minimizes packet read and / or receive loss. As illustrated in FIG. 13, the example process 1300 may begin with the receipt of a USF indicating a time to transmit (block 1305). For example, the UE 105-1 may receive the uSf from device 115 indicating a time to transmit packets. The amount of time in which the UE 105-1 can transmit may be based on a UL time slot allocation corresponding to the multiple slot class capability of the UE 105-1. A value of the USF can be determined (block 1210). The UE 105-1 can determine a USF value to have knowledge of the available UL resources.

ES 2 425 309 T3

It can be determined if there are packets to be transmitted (block 1315). For example, the UL 310 scheduler of UE 105-1 may determine if there are packets in transmit buffer 315 to be transmitted. If it is determined that there are packets to be transmitted (block 1315-YES), then the UL 305 prioritizer may prioritize the transmission of the UL packets over a reading of the DL packets (block 1320).

Time slots for transmitting the packets, which minimize a loss of time slots for reading packets from the DL, can be selected (block 1325). For example, the transmission selector 335 may select time slots to transmit the packets, as previously described. In one implementation, the timeslot or timeslots used or used to transmit may be selected or they may be selected according to an order starting from the last timeslot within a group of UL transmission timeslots. up to a first time slot within the UL transmission time slot group. In another implementation, the time slot or time slots used or used to transmit may be selected or they may be selected according to an order starting from a first time slot within a group of UL transmission time slots. up to a last time slot within the UL transmission time slot group.

Packets can be transmitted based on selected time slots (block 1330). The UE 105-1 can transmit the packets in the transmit buffer 315 according to the time slots selected by the transmit selector 335.

On the other hand, if it is determined that there is no packet to be transmitted (block 1315-NO), then the determiner of the DL reader 320 can determine that the UE 105-1 can read packets from the DL (block 1335). For example, the UE 105-1 may read packets and store in the receive buffer 330 for a time that the UE 105-1 may be scheduled to transmit.

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

Fig. 14 illustrates a flow chart showing an example process for transmitting to a UE, such as the UE 105-1. It will be apparent that the process described in conjunction with Fig. 14 can be carried out by a wireless station, such as a device 115. As illustrated in Fig. 14, an example process 1400 can begin with the recognition of a class multiple interval of a UE (block 1405). For example, device 115 may recognize that UE 105-1 is unable to receive and transmit at the same time.

A schedule to transmit may be transmitted on a DL to the UE (block 1410). Device 115 may transmit one or more USFs that indicate to UE 105-1 a time to transmit data.

Data can be transmitted on the DL to the UE to be received during scheduling to transmit (block 1415). Device 115 may transmit data on the DL to UE 105-1 to be received during the schedule to transmit. This can be accomplished even though device 115 recognizes that UE 105-1 is unable to receive and transmit at the same time.

Although FIG. 14 illustrates the example process 1400, in other implementations fewer, additional, or different operations may be performed. For example, device 115 may relay packets not received by UE 105-1 during scheduling to transmit. Device 115 can determine which packets to retransmit based on packet reception from UE 105-1 and corresponding time slots, as previously described previously.

The above description of implementations provides illustration, but is not intended to be exhaustive or limit the implementations to the precise manner described. In this regard, the concepts described herein may have broader application. Furthermore, based on the concepts described herein, a UE unable to receive and transmit at the same time may be able to support eight time slots per carrier, which is currently limited to UEs having a Type 2 classification.

Furthermore, although series of blocks have been described with a view to the processes illustrated in Figs. 12-14, the order of the blocks can be modified in other implementations. Furthermore, non-dependent blocks can be performed in parallel. It will also be understood that the processes illustrated in Figs. 12-14 and / or other processes as 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 device or devices described or described in this specification can be implemented or can be implemented in many different forms of software, firmware and hardware in the implementations illustrated in the figures. Current specialized control hardware or software code used to implement these concepts does not limit the invention. Thus, the operation and behavior of a device or devices was described with reference to specific software code - it being understood that control software and hardware can be designed to implement the concepts based on the description herein.

ES 2 425 309 T3

Although particular combinations of features are cited in the claims and / or disclosed in the specification, these combinations are not intended to limit the invention. Indeed, many of these features can be combined in ways not specifically cited in the claims and / or described in the specification.

No element, act or instruction used in the present application should be considered as critical or essential 5 for the implementations described in this specification, unless explicitly described in that way.