English:
[0001] The present invention relates generally to communication networks. More specifically, the present invention relates to apparatuses, systems and methods for allocating resources in such networks.
[0002] Scheduling and resource allocation is an aspect of telecommunications technology. Developments according to the third generation partnership project (3GPP) are directed to the evolution of the radio access network. Developments according to the long term evolution of radio technology are, in some cases, directed to evolved universal terrestrial radio access networks, also known as E-UTRAN. Proposals regarding scheduling in E-UTRAN include, for example, E-UTRAN being capable of dynamically allocating resources, such as physical resource blocks (PRBs) and modulation coating schemes (MCS) , to user equipment at each transmission time interval (TTI) via control channels. User equipment (UE) monitors control channels, such as L1/L2, in order to find potential allocations during downlink when downlink reception is enabled. Furthermore, radio access networks such as E- UTRAN can allocate predefined downlink resources for transmissions, such as a first hybrid automatic repeat request (HARQ) error control to user equipment. Retransmissions can be explicitly signaled via L1/L2 control channels. If the user equipment cannot identify its cell radio network temporary identifier (C-RNTI) on the control channels in the sub-frames where the user equipment has been pre-assigned resources, a downlink transmission according to a predefined allocation is assumed. The user equipment, therefore, can sometimes perform blind decoding of the predefined resources. Otherwise, in the sub-frames where the user equipment has been pre-assigned resources, if the user equipment finds its C-RNTI on the control channels, the control channel allocation overrides the predefined allocation for the transmission time interval, and user equipment does not perform blind decoding of the predefined resources.
[0004] In both uplink and downlink configurations, the possibility of allocating predefined resources for the first HARQ transmissions was introduced to minimize signaling overhead for services that would require frequent scheduling, such as voice over internet protocol (VOIP) .
[0005] As described above, two kinds of allocations are possible in E-UTRAN: dynamic allocations and predefined allocations for the first HARQ transmissions. Due to these two types of allocations, collisions may occur between predefined resources for the first HARQ transmission and resources allocated for retransmission. A "collision" occurs when two transmissions are supposed to take place in the same TTI - one following the dynamic allocation and the other following the predefined allocation. It may be desirable to avoid such collisions in communications networks.
[0007] In one embodiment, a method may include receiving a request for retransmission from user equipment for a predetermined transmission time interval in a communication network, determining whether a collision risk exists between the retransmission and another transmission during the predetermined time interval, and ignoring the retransmission request when the determined collision risk exists. In some embodiments, a load in the communication network may be sufficiently high that retransmission cannot be scheduled.
[0008] In another embodiment, an apparatus may include a receiving unit configured to receive a request for retransmission from user equipment for a predetermined transmission time interval in a communication network, a determining unit configured to determine whether a collision risk exists between the retransmission and another transmission during the predetermined time interval and an ignoring unit configured to ignore the retransmission request when the determining unit determines that the collision risk exists. In some embodiments, a load in the communication network may be sufficiently high that the apparatus cannot schedule retransmission. In certain embodiments, the apparatus may be an enhanced node B of the third generation partnership project .
[0009] In yet another embodiment, a method may include determining that a transmission from user equipment was unsuccessful, determining whether a retransmission will collide with a predefined resource for a predetermined transmission time interval, and transmitting an acknowledgement to the user equipment, rather than requesting retransmission, when it is determined that the retransmission will collide with the predefined resource. In some embodiments, collisions may occur due to one or more of synchronous hybrid automatic repeat request and signaling errors in control signaling. In certain embodiments, first transmissions on the predefined allocation may be prioritized over retransmissions.
[0010] In still another embodiment, an apparatus may include a first determining unit configured to determine that a transmission from user equipment was unsuccessful, a second determining unit configured to determine whether a retransmission will collide with a predefined resource for a predetermined transmission time interval, and a transmitting unit configured to transmit an acknowledgement to the user equipment, rather than a request for retransmission, when the second determining unit determines that the retransmission will collide with the predefined resource. In some embodiments, collisions may occur due to one or more of synchronous hybrid automatic repeat request and signaling errors in control signaling. In certain embodiments, first transmissions on the predefined allocation may be prioritized over retransmissions. In certain embodiments, the apparatus may be an enhanced node B of the third generation partnership project.
[0011] In another embodiment, a method may include receiving a request for retransmission from a node, determining that the request for retransmission collides with a predefined allocation, prioritizing a first transmission on the predefined allocation and the retransmission in accordance with a prioritization rule, and transmitting either the first transmission or the retransmission depending on the prioritization rule. In some embodiments, the prioritization rule may prioritize first transmissions on the predefined allocation over retransmissions. In some embodiments, the prioritization rule may prioritize retransmissions over first transmissions on the predefined allocation.
[0012] In yet another embodiment, an apparatus may include a receiving unit configured to receive a request for retransmission from a node, a determining unit configured to determine that the request for retransmission collides with a predefined allocation, a prioritizing unit configured to prioritize a first transmission on the predefined allocation and the retransmission in accordance with a prioritization rule, and a transmitting unit configured to transmit either the first transmission or the retransmission depending on the prioritization rule.
[0014] Fig. 1 is a block diagram illustrating a node configured to avoid downlink collisions between dynamic and semi-persistent allocations in a communication network, in accordance with one embodiment of the present invention .
[0015] Fig. 2 is a flow chart diagram illustrating a method for avoiding downlink collisions between dynamic and semi-persistent allocations in a communication network, in accordance with one embodiment of the present invention .
[0016] Fig. 3 is a block diagram illustrating a node configured to avoid uplink collisions between dynamic and semi-persistent allocations in a communication network, in accordance with one embodiment of the present invention.
[0017] Fig. 4 is a flow chart diagram illustrating a method for avoiding uplink collisions between dynamic and semi-persistent allocations in a communication network, in accordance with one embodiment of the present invention.
[0018] Fig. 5 is a block diagram illustrating user equipment configured to prioritize first transmissions on a predefined allocation and retransmissions, in accordance with one embodiment of the present invention.
[0019] Fig. 6 is a flow diagram illustrating a method for prioritizing first transmissions on a predefined allocation and retransmissions, in accordance with one embodiment of the present invention.
[0020] It will be readily understood that the components of various embodiments of the present invention, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the following more detailed description of the embodiments of an apparatus, system, and method of the present invention, as represented in the attached figures, is not intended to limit the scope of the invention as claimed, but is merely representative of selected embodiments of the invention.
[0021] The features, structures, or characteristics of the invention described throughout this specification may be combined in any suitable manner in one or more embodiments. For example, reference throughout this specification to "certain embodiments," "some embodiments," or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, appearances of the phrases "in certain embodiments," "in some embodiment," "in other embodiments," or similar language throughout this specification do not necessarily all refer to the same group of embodiments and the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
[0022] As discussed above, two kinds of allocations for radio access networks, such as E-UTRAN, may be utilized - dynamic allocations and predefined allocations for transmissions, such as first HARQ transmissions. However, with two kinds of allocations for the same user equipment, collisions may occur between predefined resources for the first HARQ transmission, and resources allocated for a retransmission. Certain embodiments are directed to avoiding collisions that can occur when two transmissions are intended to take place during a same transmission time interval. In particular, some embodiments are directed to avoiding collisions between a dynamic allocation and a predefined allocation.
[0023] Since only one transmission can typically take place for or from a given piece of user equipment during a given TTI, collisions should generally be avoided. Though an asynchronous HARQ may avoid many collisions through allowing nodes to freely schedule retransmissions, certain high load conditions result in nodes (such as enhanced node B, or eNB) not having the appropriate freedom to schedule a transmission appropriately. In such cases, the eNB may ignore the request from the user equipment for a downlink retransmission. In some embodiments, if a downlink retransmission cannot be scheduled in order to avoid a collision with the predefined resource, no downlink retransmission takes place at the eNB .
[0024] Fig. 1 is a block diagram illustrating a node 100 configured to avoid downlink collisions between dynamic and semi-persistent allocations in a communication network, in accordance with one embodiment of the present invention. The node 100 includes a receiving unit 110, a determining unit 120, an ignoring unit 130, a processor 140 and memory 150. One skilled in the art will recognize that the "node" could also be embodied as a server, a router, or any other suitable network device, or combination of devices. Presenting the above-described functions as being performed by a "node" is not intended to limit the scope of the present invention in any way, but is intended to provide one example of many embodiments of the present invention. Indeed, methods, systems and apparatuses disclosed herein may be implemented in localized and distributed forms consistent with networking technology. "Memory", as discussed herein, may be, for instance, a hard disk drive, flash device, random access memory (RAM) , tape, or any other such medium used to store data .
[0025] The receiving unit 110 may be configured to receive a request for retransmission from user equipment for a predetermined transmission time interval in a communication network. The determining unit 120 may be configured to determine whether a collision risk exists between the retransmission and another transmission during the predetermined time interval. The ignoring unit 130 may be configured to ignore the retransmission request when the determining unit 120 determines that the collision risk exists. A load in the communication network may be sufficiently high that the node 100 cannot schedule retransmission. The node 100 may be an eNB of the third generation partnership project.
[0026] It should be noted that many of the functional features described in this specification have been presented as units, in order to more particularly emphasize their implementation independence. For example, a unit may be implemented as a hardware circuit comprising custom very large scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A unit may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.
[0027] Units may also be at least partially implemented in software for execution by various types of processors. An identified unit of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified unit need not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the unit and achieve the stated purpose for the unit. Units may be stored on a computer-readable medium, which may be, for instance, a hard disk drive, flash device, random access memory (RAM) , tape, or any other such medium used to store data .
[0028] Indeed, a unit of executable code could be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within units, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network.
[0029] Fig. 2 is a flow chart diagram illustrating a method for avoiding downlink collisions between dynamic and semi-persistent allocations in a communication network, in accordance with one embodiment of the present invention. In certain embodiments, the operations of the method depicted in Fig. 2 may be executed by the node 100 of Fig. 1. The method includes receiving a request for retransmission 200 from user equipment for a predetermined transmission time interval in a communication network, determining whether a collision risk exists 210 between the retransmission and another transmission during the predetermined time interval, and ignoring the retransmission request 220 when the determined collision risk exists. A load in the communication network may be sufficiently high that retransmission cannot be scheduled.
[0030] In uplink conditions, collisions in some embodiments may be more likely due to synchronous HARQ, and signaling errors in the L1/L2 control signaling. If an uplink retransmission is known to collide with a predefined resource, the eNB may acknowledge the transmission, and avoid requesting retransmission. If an eNB requests an uplink retransmission that would result in a collision with a predefined resource, the eNB may acknowledge the uplink transmissions from the user equipment, even though unsuccessful. As a result, the user equipment will not be asked to perform a retransmission, and the collision with a first transmission on a predefined resource may be avoided.
[0031] Fig. 3 is a block diagram illustrating a node 300 configured to avoid uplink collisions between dynamic and semi-persistent allocations in a communication network, in accordance with one embodiment of the present invention. The node 300 includes a first determining unit 310, a second determining unit 320, a transmitting unit 330, a processor 340 and memory 350. The first determining unit 310 may be configured to determine that a transmission from user equipment was unsuccessful. The second determining unit 320 may be configured to determine whether a retransmission will collide with a predefined resource for a predetermined transmission time interval. The transmitting unit 330 may be configured to transmit an acknowledgement to the user equipment, rather than a request for retransmission, when the second determining unit 320 determines that the retransmission will collide with the predefined resource.
[0032] Collisions may occur due to one or more of synchronous hybrid automatic repeat request and signaling errors in control signaling. First transmissions on the predefined allocation may be prioritized over retransmissions. The node 300 may be an eNB of the third generation partnership project.
[0033] Fig. 4 is a flow chart diagram illustrating a method for avoiding uplink collisions between dynamic and semi-persistent allocations in a communication network, in accordance with one embodiment of the present invention. In certain embodiments, the operations of the method depicted in Fig. 4 may be executed by the node 300 of Fig. 3. The method includes determining that a transmission from user equipment was unsuccessful 400, determining whether a retransmission will collide with a predefined resource for a predetermined transmission time interval 410, and transmitting an acknowledgement to the user equipment 420, rather than requesting retransmission, when it is determined that the retransmission will collide with the predefined resource. Collisions may occur due to one or more of synchronous hybrid automatic repeat request and signaling errors in control signaling. First transmissions on the predefined allocation may be prioritized over retransmissions.
[0034] However, since signaling errors can occur in any event, the user equipment may still be requested to perform a retransmission although it collides with the predefined allocation. In such case, the user equipment may prioritize first transmission on the predefined allocation over retransmissions. The user equipment can therefore be configured to prioritize first transmissions on the predefined allocation over requested retransmissions .
[0035] In some embodiments, the user equipment may be configured to prioritize retransmission to occur prior to the predefined allocation. The determination of which prioritization rule to use may depend on a particular application or the particular needs of the particular application. The implementation of a prioritization rule may be implemented in either the user equipment or in a node, such as an eNB, as appropriate.
[0036] Fig. 5 is a block diagram illustrating user equipment 500 configured to prioritize first transmissions on a predefined allocation and retransmissions, in accordance with one embodiment of the present invention. The user equipment 500 includes a receiving unit 510, a determining unit 520, a prioritizing unit 530, a transmitting unit 540, a processor 550 and memory 560. One skilled in the art will readily understand that "user equipment" may include a cellular phone, a pager, a personal data assistant (PDA) , a personal computer, or any other device capable of performing the operations associated with the "user equipment" as described herein.
[0037] The receiving unit 510 may be configured to receive a request for retransmission from a node. In some embodiments, the node may be the node 100 or the node 300 illustrated in Figs. 1 and 3, respectively. The determining unit 520 may be configured to determine that the request for retransmission collides with a predefined allocation. The prioritizing unit 530 may be configured to prioritize a first transmission on the predefined allocation and the retransmission in accordance with a prioritization rule. The transmitting unit 540 may be configured to transmit either the first transmission or the retransmission depending on the prioritization rule. The prioritizing unit 540 may prioritize first transmissions on the predefined allocation over retransmissions. The prioritizing unit 540 may also prioritize retransmissions over first transmissions on the predefined allocation.
[0038] Fig. 6 is a flow diagram illustrating a method for prioritizing first transmissions on a predefined allocation and retransmissions, in accordance with one embodiment of the present invention. In certain embodiments, the operations of the method depicted in Fig. 6 may be executed by the user equipment 500 of Fig. 5. The method includes receiving a request for retransmission from a node 600, determining that the request for retransmission collides with a predefined allocation 610, prioritizing a first transmission on the predefined allocation and the retransmission in accordance with a prioritization rule 620, and transmitting either the first transmission or the retransmission depending on the prioritization rule 630. The prioritization rule may prioritize first transmissions on the predefined allocation over retransmissions. The prioritization rule may also prioritize retransmissions over first transmissions on the predefined allocation.
[0039] In the above embodiments, signaling between the user equipment and node, such as eNB, may occur on appropriate control channels. For example, the L1/L2 control channels may be used, since user equipment may monitor L1/L2 control channels in order to identify possible allocations when downlink reception is enabled.
[0040] One having ordinary skill in the art will readily understand that the invention as discussed above may be practiced with steps in a different order, and/or with hardware elements in configurations which are different than those which are disclosed. Therefore, although the invention has been described based upon these preferred embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of the invention. In order to determine the metes and bounds of the invention, therefore, reference should be made to the appended claims.
[0041] It should be noted that reference throughout this specification to features, advantages, or similar language does not imply that all of the features and advantages that may be realized with the present invention should be or are in any single embodiment of the invention. Rather, language referring to the features and advantages is understood to mean that a specific feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the present invention. Thus, discussion of the features and advantages, and similar language, throughout this specification may, but do not necessarily, refer to the same embodiment.
[0042] Furthermore, the described features, advantages, and characteristics of the invention may be combined in any suitable manner in one or more embodiments. One skilled in the relevant art will recognize that the invention can be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of the invention.

中文:
[0001]本发明总体上涉及通信网络。更具体而言,本发明涉及用于分配这样的网络中的资源的装置、系统、以及方法。
[0002]调度和资源分配是电信技术的一方面。根据第三代合作伙伴计划(3GPP)的开发所针对的是无线电接入网络的演进。在一些情况下,根据无线电技术长期演进的开发所针对的是演进通用陆地无线电接入网络(亦称E-UTRAN)。关于在E-UTRAN中进行调度的提议例如包括:E-UTRAN能够在每个传输时间间隔(TTI)通过控制信道将资源(诸如物理资源块(PRB)以及调制编码方案(MCS))动态地分配给用户设备。用户设备(UE)监测控制信道、诸如L1/L2,以便找出在下行链路接收被使能时在下行链路期间的潜在分配。此外,诸如E-UTRAN的无线电接入网络可以将预先定义的用于传输的下行链路资源、诸如第一混合自动重复请求(HARQ)差错控制分配给用户设备。重传可以通过L1/L2控制信道被显式地用信号通知。如果用户设备不能在已经给该用户设备预先指派了资源的子帧中在控制信道上识别其小区无线电网络临时标识符(C-RNTI),则假定根据预先定义的分配的下行链路传输。因此,该用户设备有时可以执行对预先定义的资源的盲解码。否则,在已经给该用户设备预先指派了资源的子帧中,如果该用户设备在控制信道上找出其C-RNTI,则控制信道分配撤销预先定义的针对该传输时间间隔的分配,并且用户设备不执行对预先定义的资源的盲解码。
[0004]在上行链路和下行链路配置二者中,针对第一HARQ传输来分配预先定义的资源的可能性已被引入,以使用于将需要频繁调度的业务(诸如网际协议承载语音(VOIP))的信令开销最小化。
[0005]如上所述,有两种分配在E-UTRAN中是可能的:针对第一HARQ传输的动态分配和预先定义的分配。由于这两类分配,可能在用于第一HARQ传输的预先定义的资源与针对重传所分配的资源之间发生冲突。当两种传输应该在同一TTI中进行时发生“冲突”(一个遵循动态分配,而另一个遵循预先定义的分配)。可能期望避免通信网络中的这样的冲突。
[0007]在一个实施例中,一种方法可以包括:在通信网络中在预先确定的传输时间间隔内接收来自用户设备的重传请求;确定在所述预先确定的时间间隔期间在重传与另一传输之间是否存在冲突风险;以及在存在所确定的冲突风险时忽略该重传请求。在一些实施例中,该通信网络中的负载可能足够高以至于不能调度重传。
[0008]在另一实施例中,一种装置可以包括:接收单元,其被配置为在通信网络中在预先确定的传输时间间隔内接收来自用户设备的重传请求;确定单元,其被配置为确定在所述预先确定的时间间隔期间在重传与另一传输之间是否存在冲突风险;以及忽略单元,其被配置为在确定单元确定存在冲突风险时忽略该重传请求。在一些实施例中,该通信网络中的负载可能足够高以至于该装置不能调度重传。在某些实施例中,该装置可以是第三代合作伙伴计划的增强型节点B。
[0009]在又一实施例中,一种方法可以包括:确定从用户设备进行的传输不成功;确定在预先定义的传输时间间隔内重传是否将与预先定义的资源相冲突;以及当确定重传将与预先定义的资源相冲突时将确认发射给该用户设备而不是请求重传。在一些实施例中,由于同步混合自动重复请求和控制信令中的信令差错中的一个或多个而可能发生冲突。在某些实施例中,根据预先定义的分配的第一传输可以被确定为优先于重传。
[0010]在另一实施例中,一种装置可以包括:第一确定单元,其被配置为确定从用户设备进行的传输不成功;第二确定单元,其被配置为确定在预先定义的传输时间间隔内重传是否将与预先定义的资源相冲突;以及发射单元,其被配置为当第二确定单元确定重传将与预先定义的资源相冲突时将确认而不是重传请求发射给该用户设备。在一些实施例中,由于同步混合自动重复请求和控制信令中的信令差错中的一个或多个而可能发生冲突。在某些实施例中,根据预先定义的分配的第一传输可以被确定为优先于重传。在某些实施例中,该装置可以是第三代合作伙伴计划的增强型节点B。
[0011]在另一实施例中,一种方法可以包括:接收来自节点的重传请求;确定该重传请求与预先定义的分配相冲突;根据优先级确定(prioritization)规则来确定根据预先定义的分配的第一传输和重传的优先级;以及根据该优先级确定规则来发射第一传输或者重传。在一些实施例中,该优先级确定规则可以确定根据预先定义的分配的第一传输优先于重传。在一些实施例中,该优先级确定规则可以确定重传优先于根据预先定义的分配的第一传输。
[0012]在又一实施例中,一种装置可以包括:接收单元,其被配置为接收来自节点的重传请求;确定单元,其被配置为确定该重传请求与预先定义的分配相冲突;优先级确定单元,其被配置为根据优先级确定规则来确定根据预先定义的分配的第一传输和重传的优先级;以及发射单元,其被配置为根据该优先级确定规则来发射第一传输或者重传。在一些实施例中,该优先级确定单元可以确定根据预先定义的分配的第一传输优先于重传。在一些实施例中,该优先级确定单元可以确定重传优先于根据预先定义的分配的第一传输。在某些实施例中,该装置可以是用户设备。
[0014]图1是示出根据本发明的一个实施例的节点的方框图,所述节点被配置为避免通信网络中动态分配与半持久分配之间的下行链路冲突。
[0015]图2是示出根据本发明的一个实施例的、用于避免通信网络中动态分配与半持久分配之间的下行链路冲突的方法的流程图。
[0016]图3是示出根据本发明的一个实施例的节点的方框图,所述节点被配置为避免通信网络中动态分配与半持久分配之间的上行链路冲突。
[0017]图4是示出根据本发明的一个实施例的、用于避免通信网络中动态分配与半持久分配之间的上行链路冲突的方法的流程图。
[0018]图5是示出根据本发明的一个实施例的用户设备的方框图,所述用户设备被配置为确定根据预先定义的分配的第一传输和重传的优先级。
[0019]图6是示出根据本发明的一个实施例的、用于确定根据预先定义的分配的第一传输和重传的优先级的方法的流程图。
[0020]将容易地理解,可以以多种多样的不同配置来布置和设计本发明的各个实施例的如在此被一般性描述的和在图中被示出的组件。因此,下面对本发明的如在附图中所表示的装置、系统、以及方法的实施例的更详细的描述并不旨在限制本发明的所请求保护的范围,而是仅仅表示本发明的所选实施例。
[0021]在一个或多个实施例中,贯穿本说明书所描述的本发明的特征、结构、或者特性可以以任何合适的方式相组合。例如,贯穿本说明书对“某些实施例”、“一些实施例”或者类似措辞的提及意指联系该实施例所述的特定特征、结构或特性被包括在本发明的至少一个实施例中。因此,贯穿本说明书的用语“在某些实施例中”、“在一些实施例中”、“在其它实施例中”或者类似措辞的出现并不一定全部指同一组实施例,并且在一个或多个实施例中,所描述的特征、结构或者特性可以以任何合适的方式相组合。
[0022]如上所述,可以利用两种用于无线电接入网络(诸如E-UTRAN)的分配:针对传输(诸如第一HARQ传输)的动态分配和预先定义的分配。然而,在对于同一用户设备来说有两种分配的情况下,可能在用于第一HARQ传输的预先定义的资源与针对重传所分配的资源之间发生冲突。某些实施例所针对的是避免在两种传输预期在同一传输时间间隔期间进行时可能发生的冲突。具体来说,一些实施例所针对的是避免动态分配与预先定义的分配之间的冲突。
[0023]由于通常在给定TTI期间针对或者从一个给定的用户设备只能进行仅仅一种传输,因此一般将避免冲突。尽管异步HARQ可以通过允许节点自由调度重传来避免许多冲突,但是某些高负载状况导致节点(诸如增强型节点B或eNB)不具有适当地调度传输的适当自由。在这种情况下,eNB可能忽略来自用户设备的对下行链路重传的请求。在一些实施例中,如果为了避免与预先定义的资源的冲突而不能调度下行链路重传,则在该eNB处不进行下行链路重传。
[0024]图1是示出根据本发明的一个实施例的节点100的方框图,所述节点100被配置为避免通信网络中动态分配与半持久分配之间的下行链路冲突。节点100包括:接收单元110、确定单元120、忽略单元130、处理器140、以及存储器150。本领域的技术人员能够认识到,“节点”也可以被具体化为服务器、路由器、或者任何其它合适的网络设备、或者设备的组合。将上述功能呈现为由“节点”执行并不旨在以任何方式限制本发明的范围,而是旨在提供本发明的许多实施例的一个例子。实际上,在此所公开的方法、系统、以及装置可以以符合联网技术的局域化或者分布式形式来实施。举例来说,如在此所讨论的“存储器”可以是硬盘驱动器、闪存设备、随机存取存储器(RAM)、磁带、或者任何其它这样的被用于存储数据的介质。
[0025]接收单元110可以被配置为在通信网络中在预先确定的传输时间间隔内接收来自用户设备的重传请求。确定单元120可以被配置为确定在所述预先确定的时间间隔期间在重传与另一传输之间是否存在冲突风险。忽略单元130可以被配置为在确定单元120确定存在冲突风险时忽略该重传请求。该通信网络中的负载可能足够高以至于节点100不能调度重传。节点100可以是第三代合作伙伴计划的eNB。
[0026]应当注意,在本说明书中所描述的许多功能性特征已经被呈现为单元,以便更具体地强调这些功能性特征的实施独立性。例如,单元可以被实施为硬件电路,所述硬件电路包括:定制的超大规模集成(VLSI)电路或者门阵列、现成的半导体(诸如逻辑芯片、晶体管、或者其它分立组件)。还可以以可编程硬件器件(诸如现场可编程门阵列、可编程阵列逻辑、可编程逻辑器件等等)来实施单元。
[0027]还可以至少部分地以用于由各种类型的处理器执行的软件来实施单元。举例来说,所识别出的可执行代码单元可以包括一个或多个物理或逻辑的计算机指令块,所述计算机指令块例如可以被组织为对象、程序、或者功能。但是,所识别出的单元的可执行代码不必物理上被定位在一起,而是可以包括被存储在不同位置的不同指令,其中所述不同指令在逻辑上被联合在一起时包括该单元并且实现该单元的所陈述的目的。单元可以被存储在计算机可读介质上,举例来说,所述计算机可读介质可以是:硬盘驱动器、闪存设备、随机存取存储器(RAM)、磁带、或者任何其它这样的被用于存储数据的介质。
[0028]实际上,可执行代码单元可以是单个指令或者许多指令,并且甚至可以分布在多个不同的代码段上、不同的程序之中、以及跨越多个存储设备。类似地,操作数据可以在此在单元之内被识别出和示出,并且可以以任何合适的形式被具体化以及被组织在任何合适类型的数据结构内。操作数据可以被聚集为单个数据集,或者可以分布在不同的位置上(包括分布在不同的存储设备上),并且可以至少部分地仅仅作为电子信号存在于系统或网络上。
[0029]图2是示出根据本发明的一个实施例的、用于避免通信网络中动态分配与半持久分配之间的下行链路冲突的方法的流程图。在某些实施例中,在图2中所描绘的该方法的操作可以由图1的节点100来执行。该方法包括:在通信网络中在预先确定的传输时间间隔内接收来自用户设备的重传请求200;确定在所述预先确定的时间间隔期间在重传与另一传输之间是否存在冲突风险210;以及在存在所确定的冲突风险时忽略该重传请求220。该通信网络中的负载可能足够高以至于不能调度重传。
[0030]在上行链路状况中,在一些实施例中,由于同步HARQ以及L1/L2控制信令中的信令差错而更可能发生冲突。如果已知上行链路重传与预先定义的资源冲突,则该eNB可以确认该传输,并且避免请求重传。如果eNB请求将导致与预先定义的资源发生冲突的上行链路重传,则该eNB即使在不成功的情况下也可以确认从该用户设备进行的上行链路传输。因此,该用户设备将不被要求执行重传,并且与预先定义的资源上的第一传输的冲突可以被避免。
[0031]图3是示出根据本发明的一个实施例的节点300的方框图,所述节点300被配置为避免通信网络中动态分配与半持久分配之间的上行链路冲突。节点300包括:第一确定单元310、第二确定单元320、发射单元330、处理器340、以及存储器350。第一确定单元310可以被配置为确定从用户设备进行的传输不成功。第二确定单元可以被配置为确定重传是否将在预先确定的传输时间间隔内与预先定义的资源相冲突。发射单元330可以被配置为当第二确定单元320确定重传将与预先定义的资源相冲突时将确认而不是重传请求发射给该用户设备。
[0032]由于同步混合自动重复请求和控制信令中的信令差错中的一个或多个而可能发生冲突。根据预先定义的分配的第一传输可以被确定为优先于重传。节点300可以是第三代合作伙伴计划的eNB。
[0033]图4是示出根据本发明的一个实施例的、用于避免通信网络中动态分配与半持久分配之间的上行链路冲突的方法的流程图。在某些实施例中,在图4中所描绘的方法的操作可以由图3的节点300来执行。该方法包括:确定从用户设备进行的传输不成功400;确定重传是否将在预先确定的传输时间间隔内与预先定义的资源相冲突410;以及当确定重传将与预先定义的资源相冲突时将确认发射给该用户设备420,而不是请求重传。由于同步混合自动重复请求和控制信令中的信令差错中的一个或多个而可能发生冲突。根据预先定义的分配的第一传输可以被确定为优先于重传。
[0034]然而,由于信令差错可能在任何情况下发生,所以尽管重传与预先定义的分配相冲突,用户设备仍然可能被请求执行重传。在这样的情况下,该用户设备可以确定根据预先定义的分配的第一传输优先于重传。因此,该用户设备可以被配置为确定根据预先定义的分配的第一传输优先于所请求的重传。
[0035]在一些实施例中,用户设备可以被配置为确定重传优先发生在预先定义的分配之前。对使用哪个优先级确定规则的确定可以取决于具体应用或者该具体应用的具体需求。优先级确定规则的实施方案可以酌情地在用户设备中或者诸如eNB的节点中被实施。
[0036]图5是示出根据本发明的一个实施例的用户设备500的方框图,所述用户设备500被配置为确定根据预先定义的分配的第一传输和重传的优先级。用户设备500包括:接收单元510、确定单元520、优先级确定单元530、发射单元540、处理器550、以及存储器560。本领域的技术人员将容易地理解,“用户设备”可以包括手机、寻呼机、个人数字助理(PDA)、个人计算机、或者任何其它能够执行在此所述的与“用户设备”相关联的操作的设备。
[0037]接收单元510可以被配置为接收来自节点的重传请求。在一些实施例中,该节点可以是分别在图1和图3中所示的节点100或者节点300。确定单元520可以被配置为确定重传请求与预先定义的分配相冲突。优先级确定单元530可以被配置为根据优先级确定规则来确定根据预先定义的分配的第一传输和重传的优先级。发射单元540可以被配置为根据该优先级确定规则来发射第一传输或者重传。优先级确定单元540可以确定根据预先定义的分配的第一传输优先于重传。优先级确定单元540也可以确定重传优先于根据预先定义的分配的第一传输。
[0038]图6是示出根据本发明的一个实施例的、用于确定根据预先定义的分配的第一传输和重传的优先级的方法的流程图。在某些实施例中,在图6中所描绘的方法的操作可以由图5的用户设备500来执行。该方法包括:接收来自节点的重传请求600;确定重传请求与预先定义的分配相冲突610;根据优先级确定规则来确定根据预先定义的分配的第一传输和重传的优先级620;以及根据该优先级确定规则来发射第一传输或者重传630。该优先级确定规则可以确定根据预先定义的分配的第一传输优先于重传。该优先级确定规则也可以确定重传优先于根据预先定义的分配的第一传输。
[0039]在上述实施例中,在用户设备与诸如eNB的节点之间的信令可以发生在适当的控制信道上。例如,可以使用L1/L2控制信道,因为用户设备可以监测L1/L2控制信道以便识别在下行链路接收被使能时的可能的分配。
[0040]本领域的普通技术人员将容易地理解,可以利用按不同顺序的步骤和/或利用具有与所公开的这些配置不同的配置中的硬件元件来实践上面所讨论的本发明。因此,尽管已经基于这些优选实施例描述了本发明,但是对于本领域的技术人员而言将是显而易见的是,某些修改、变型、以及替代的构造在保持在本发明的精神和范围之内的同时将是显而易见的。因此,为了确定本发明的边界和界限,应当参考所附的权利要求书。
[0041]应当注意,贯穿本说明书对特征、优点、或者类似措辞的提及并不意味着所有可以利用本发明而被实现的特征和优点应当在或者在本发明的任何单个实施例中。更确切地说,涉及特征和优点的措辞被理解为意指联系实施例所述的特定特征、优点、或者特性被包括在本发明的至少一个实施例中。因此,贯穿本说明书对特征和优点以及类似措辞的讨论可以但不一定涉及同一实施例。
[0042]此外,本发明的所述特征、优点、以及特性可以在一个或多个实施例中以任何合适的方式相组合。相关领域中的技术人员将认识到,可以在没有具体实施例的一个或多个特定特征或优点的情况下实践本发明。在其它实例中,可能在某些实施例中认识到可能在本发明的所有实施例中都未呈现的附加特征和优点。