Method and user equipment for prioritizing data and control transmissions

Abstract

A method and system for prioritizing data and control transmissions where scheduled transmission resources overlap. The user equipment selects a transmission based on transmission characteristics, such as priority or message type. In some cases, both transmissions can be multiplexed for transmission.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to priority in relation to transmissions, in particular to handling of priority when data and control uplink transmissions collide. BACKGROUND

[0002] Wireless communication systems such as the third generation (3G) mobile telephone standards and technologies are well known. Such 3G standards and technologies are developed by the Third Generation Partnership Project (3GPP) (RTM). Third generation wireless communication is typically used to support macro cellular mobile telephone communications. The communication systems and networks have evolved towards broadband and mobile systems.

[0003] In a cellular wireless communication system, user equipment (UE) is connected to a radio access network (RAN) over a wireless link. The RAN comprises a set of base stations which provide wireless links to UEs in cells covered by the base stations, and the RAN also provides an interface to a core network (CN) which provides overall network control. Notably, the RAN and CN each perform respective functions in relation to the overall network. For convenience, the term cellular network is used to refer to the combination of the RAN and CN, it being understood that the term is used to refer to the corresponding system for performing the disclosed functionality.

[0004] The Third Generation Partnership Project has developed a so-called Long Term Evolution (LTE) system for mobile access networks, namely the Evolved Universal Mobile Telecommunications System Terrestrial Radio Access Network (E-UTRAN), in which one or more macro cells are supported by base stations known as eNodeBs or eNBs. More recently, LTE is being further developed towards a 5G or New Radio (NR) system in which one or more cells are supported by base stations known as gNBs. The NR proposes to use an Orthogonal Frequency Division Multiplexing (OFDM) physical transmission format.

[0005] The NR protocol aims to provide an option to operate in unlicensed radio bands, referred to as NR-U. When operating in unlicensed radio bands, the gNB and UEs must contend for physical medium / resource access with other devices. For example, Wi-Fi (RTM), NR-U and LAA can use the same physical resources.

[0006] A trend in wireless communications is to provide services with lower latency and higher reliability. For example, NR aims to support Ultra-Reliable and Low-Latency Communications (URLLC), while Massive Machine Type Communications (mMTC) aims to provide low latency and high reliability for small data packets, typically 32 bytes in size, with a user plane latency of 1 ms, a reliability of 99.99999%, and a packet loss rate of 10-5or 10-6at the physical layer.

[0007] The mMTC service aims to support a large number of devices over a long life cycle through a highly energy efficient communication channel, where data transmission with each device is occasional and infrequent. For example, one cell can need to support thousands of devices.

[0008] The following disclosure relates to various improvements to a cellular wireless communication system. SUMMARY

[0009] This abstract presents a simplified summary of the concepts disclosed herein, which will be further described in the detailed description. This abstract is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used to determine the scope of the claimed subject matter.

[0010] The present disclosure provides a method of prioritizing data transmission and control transmission from a user equipment (UE) to a base station. Where the transmissions have overlapping resources. The control transmission can be HARQ feedback. If both cannot be transmitted in the scheduled resources, the UE can prioritize the data transmission over the control transmission. When the base station does not receive the expected HARQ feedback, it can set the feedback to be a NACK. The base station can act appropriately, for example by scheduling a retransmission.

[0011] The UE can select to transmit the control transmission or the data transmission according to the relative priority of the control transmission or the data transmission. If the control transmission or the data transmission has the same priority, the data transmission can be performed. In the case of the same priority, the UE's behavior can depend on the priority. In the case of the lower priority, the UE can multiplex the control information with the data transmission on PUSCH. In the case of the higher priority, the UE can transmit the data on PUSCH instead of the control information. Further, the transmission of data or control information can be selected based on the type of control information. If the control information is a NACK message, the data is transmitted, and if the control information is an ACK message, the control information is sent. If multiplexing is enabled, the ACK message can be multiplexed.

[0012] In the case where the feedback is CBG-based feedback, the UE can switch to TB-based feedback before transmitting the control information according to the method.

[0013] The non-transitory computer readable medium can include a hard disk, a CD-ROM, an optical storage device, a magnetic storage device, a Read Only Memory, a Programmable Read Only Memory, an Erasable Programmable Read Only Memory, an EPROM, an Electrically Erasable Programmable Read Only Memory, and a flash memory. BRIEF DESCRIPTION OF DRAWINGS

[0014] Further details, aspects and embodiments of the application will be described, by way of example only, with reference to the drawings. Components in the drawings are for ease of illustration and are not necessarily drawn to scale. For ease of understanding, the same reference numbers and designations will be used throughout the drawings and the following detailed description to refer to the same or like parts.

[0015] Figure 1 A schematic diagram illustrating exemplary components of a cellular communication network is shown.

[0016] Figures 2 to 7 A method of transmission prioritization is illustrated. DETAILED DESCRIPTION

[0017] Those skilled in the art will recognize and appreciate that the specific details described herein are merely illustrative of some embodiments and that the teachings provided herein can apply to a wide variety of alternative settings.

[0018] Figure 1 A schematic diagram showing three base stations (e.g., eNB or gNB, depending on the specific cellular standard and terminology) that make up a cellular network is shown. Typically, each base station is deployed by a cellular network operator to provide geographic coverage for UEs in the area. The base stations form a Radio Area Network (RAN). Each base station provides wireless network coverage for UEs in its area or cell. The base stations are interconnected by an X2 interface and connected to a core network by an S1 interface. To illustrate key features of a cellular network, only basic details are shown here. Between UEs, a PC5 interface is used for SideLink (SL) communication. The relevant interfaces and component names are used only as examples, and different systems operating on the same principles can use different nomenclature. Figure 1 The relevant interfaces and component names are used only as examples, and different systems operating on the same principles can use different nomenclature.

[0019] Each base station contains hardware and software that implements RAN functionality, including communication with the core network and other base stations, control and data signal transmission between the core network and UEs, and maintaining wireless communication with UEs associated with each base station. The core network includes hardware and software that implements network functionality, such as overall network management and control, and routing of calls and data.

[0020] As mentioned above, certain services provided using the NR radio standard have strict reliability and latency targets. URLLC services generally require (as defined by TR 38.913) 32 bytes with 1x10-5 reliability and 1 ms user plane latency. To achieve this target, rules for allocating transmission resources can be modified to allow control and data transmissions to overlap in time. For example,

[0021] Physical Uplink Control Channel (PUCCH) carries uplink control information (UCI), where UCI includes hybrid automatic repeat request (HARQ) feedback, while physical uplink shared channel (PUSCH) mainly carries data from logical shared channels, and PUCCH and PUSCH can overlap. In other scenarios, a UE can be running services of different priorities. Since the priority of an incoming data packet is not known in advance, a high-priority data packet that arrives after a low-priority data packet can cause resource overlap. This overlap can happen frequently when a base station has already allocated periodic resources for a UE transmission. Then a downlink transmission that requires uplink control transmission or dynamic uplink control can cause resource overlap with the UE periodic resources. UE hardware can not support simultaneous transmission of such channels on separate frequency resources. The overlapping transmission in this disclosure aims to cover transmissions that have two transmissions overlapping in time domain. This time domain overlap covers the case where two transmissions share at least one orthogonal frequency division modulation (OFDM) symbol. It also covers the case where two transmissions fall within the same time slot and the UE cannot transmit both of them within the time slot (e.g., due to hardware limitations). Overlapping resources have been supported previously by either masking UCI on PUSCH resources or rate matching PUSCH data, multiplexing PUCCH control information on PUSCH. This multiplexing improves the effective code rate, and thus can result in reduced reliability of both channels. Reliability is significantly reduced if a large number of transport blocks (TBs) need to be acknowledged, or a configuration has a large HARQ codebook that needs to transmit a large number of bits.

[0022] Similarly, code block group (CBG) feedback can result in a large number of feedback bits needing to be transmitted.

[0023] In addition, each transmission has an associated priority, which affects how conflicts are handled. Uniformly multiplexing two transmissions with very different priorities can result in unfair degradation of the higher priority transmission, which in turn allows transmission of lower priority signals. In the case of different priorities, a fair transmission algorithm can choose to delay transmission of lower priority signals to improve the reliability of higher priority transmissions. This is particularly important when retransmissions are required, when a higher priority transmission has an unmet delay requirement. A special case can arise when two transmissions have equal priority and collide, requiring the UE to decide how to resolve the conflict without explicit indication of relative importance.

[0024] In one embodiment, the current standard suggests that Configured grant (CG)-UCI and HARQ-ACK are not configured when multiplexing is configured, and the colliding CG-PUSCH should be skipped. In some cases, for example, if the transmission priority of PUSCH is low, it can be appropriate to skip the PUSCH transmission and attempt to transmit later. If the PUSCH transmission has a low delay requirement, skipping the PUSCH in the given case can result in a violation of the delay target and ultimately dropping the data packet. The following sets out methods for multiplexing or prioritization of PUCCH and PUSCH to address this difficulty.

[0025] The present disclosure focuses on overlapping control transmissions and data transmissions within a UE. Uplink data transmissions on PUSCH include dynamic grant (DG) based and configured grant (CG) based PUSCH transmissions. Therefore, the methods proposed in the present disclosure are applicable to both types of PUSCH transmissions. For UE control transmissions, the main focus is on control information including HARQ feedback. This HARQ feedback will correspond to TBs received by the UE from other communication entities, such as a base station. Although the present disclosure focuses on HARQ feedback, the principles set out below are applicable to general control transmissions, including HARQ feedback, scheduling requests, and channel state information, etc. In addition, when the system operates in licensed bands and in shared bands, the range of scenarios of interest includes unlicensed bands. Unlicensed band operation brings some problems, mainly due to the uncertainty of channel access on unlicensed carriers. This results in the PUCCH and PUSCH collision problem becoming worse compared to licensed band operation. However, the methods and principles proposed in the present disclosure are applicable to licensed and unlicensed operation by providing principles to resolve collisions / conflicts in a variety of scenarios.

[0026] Below is a set of collision transmission priority ranking methods based on transmission type and relative priority. A common principle is that data transmission takes precedence over control transmissions carrying HARQ ACK / NACK (or other) control information. The base station assumes feedback loss, therefore transmitting PUSCH instead of PUCCH is a NACK, and proceeds as if receiving a NACK (generally assuming data retransmission has failed). Prioritizing data over control information improves the ability to meet service delay targets.

[0027] When conflicting transmissions have the same priority, the UE's behavior may depend on the priority. For example, for lower-priority transmissions, the signal may be multiplexed, accepting potentially reduced reliability, while for higher-priority transmissions, data transmission may proceed and conflicting control transmissions may be skipped. This helps meet the latency requirements of high-priority data transmission, and the base station can assume that NACK is used for unreceived control transmissions. This can trigger an appropriate response from the base station to protect the UE for transmissions whose HARQ feedback priority has been removed. This response could be a fast retransmission corresponding to the downlink (DL) TB. In this way, the result is ensuring that the performance objectives of both transmissions are met.

[0028] Furthermore, transmissions can be prioritized based on the content of the control data. For example, data can take precedence over HARQ NACK transmissions (and the base station can assume NACK), while HARQ ACK transmissions can take precedence over data transmission.

[0029] As mentioned above, when using CBG feedback, the feedback transmission can be very large. In cases where this feedback conflicts with data transmission, especially when priorities are the same, the feedback can be changed to TB-based feedback.

[0030] These principles can be used in combination or individually, depending on the situation. Data transfer can occur on either Configuration Grant (CG) or Dynamic Grant (DG) resources. Some examples of these principles are listed below.

[0031] In the first example, such as Figure 2 As shown, data and control (HARQ feedback) are scheduled on time-overlapping PUSCH and PUCCH (200). In step 201, the UE skips the control transmission, and in step 202, data is transmitted on the PUSCH. In step 203, the base station receives the PUSCH transmission and detects a lost PUCCH transmission (since the transmission of HARQ feedback is expected). In step 204, the base station assumes that the HARQ feedback will be NACK and triggers appropriate behavior (e.g., retransmission).

[0032] This approach ensures that data transmission is carried out as planned, thus meeting the delay requirement. According to this approach, if the HARQ feedback is not sent in favor of data, the base station will assume that the feedback will be NACK. If the actual feedback will be NACK, the base station will operate correctly and in the same way as if the feedback was sent. The transmission priority and the remaining Packet Delay Budget (PDB) can also be used by the base station to decide on retransmission if the HARQ feedback is missing for a TB. If there is enough time before the PDB expires, the base station can trigger the HARQ feedback. If the PDB is about to expire, it can choose to schedule a retransmission. Again, the priority of the transmission will affect the way the base station responds to missing HARQ feedback. Furthermore, the data transmission is carried out without multiplexing it with control information, thus preserving the reliability of the transmission. This approach also avoids the delay of data transmission, thus preserving the delay performance. If the actual feedback will be ACK, the base station will make a wrong assumption and can attempt to retransmit the data that it assumed was lost. This retransmission is not actually needed, thus the transmission resource utilization efficiency is reduced, but the improvement in data transmission reliability can outweigh the reduction in efficiency.

[0033] Figure 3 Another example is shown that shows the prioritization between data and control transmissions.

[0034] At step 300, the PUCCH transmission and the PUSCH transmission overlap in time, e.g. for at least one OFDM symbol duration. At step 301, the UE determines the relative priority of the two transmissions, the PUCCH transmission and the PUSCH transmission. If the priorities are different, the UE proceeds to step 302 or 303 to transmit the transmission with the highest priority. The priority can be provided to the PHY layer in RRC / Higher layer configuration based on an indication from the base station, or dynamically in the PHY layer signaling (e.g. in the related DCI). If the priority is not specified, the UE can assume normal or lowest priority. It can be assumed that control information such as HARQ feedback (FB) has its indicated priority, which can be configured with the related HARQ codebook. In the absence of HARQ codebook priority or other control information, the priority can be assumed to be that of the related PDSCH.

[0035] At step 301, if the priorities are the same, the UE prioritizes the control transmission on the PUCCH (step 304) and the data on the PUSCH. Obviously, the control transmission is only carried out if its priority is higher than that of the data transmission.

[0036] If the control transmission is not carried out, as explained with reference to Figure 2 the base station assumes that the HARQ feedback will be NACK and proceeds accordingly.

[0037] Figure 3 The flowchart of the method of the present application can be summarized as follows:

[0038] - PUSCH has higher or same priority than PUCCH (HARQ FB):

[0039] → transmit PUSCH and skip PUCCH (use HARQ FB).

[0040] → in case of time overlap with PUSCH, the base station assumes NACK for the HARQ feedback upon skipping.

[0041] Else:

[0042] → transmit PUCCH and skip PUSCH.

[0043] Figure 3 The method of the present application ensures that the transmission with the highest priority is transmitted and the reliability of the transmission is not degraded by multiplexing control and data together. The advantages and effects are as described in Figure 3 Particularly, in case the expected HARQ feedback is NACK, the actual behavior is identical to the behavior when control transmission is done, while if the HARQ feedback is ACK, an unnecessary data transmission can be performed, reducing the transmission resource efficiency, but with the advantage of improving the reliability of the data transmission. The base station can minimize unnecessary retransmissions by analyzing the transmission priority and the remaining PDB of the related data packet.

[0044] In case control information is prioritized over data transmission, the data can be rescheduled to a later transmission opportunity (either configured grant or dynamic grant, as appropriate). For the case of dynamic grant, the base station sends a new scheduling command to directly retransmit the scheduling. For the case of configured grant, the UE can transmit on the next periodic resource, or can send a scheduling request regarding the data packet priority and PDB.

[0045] Figure 3 The procedure of the present application solves a potential problem that the number of HARQ feedback bits actually transmitted can be unknown if the HARQ feedback bits are multiplexed with PUSCH. This can be particularly relevant for configured grant PUSCH. Since there is no multiplexing of control and data transmission in the proposed solution, the base station either receives the full, original transmission or nothing. Otherwise, when multiplexing according to the conventional procedure, the misalignment between the base station and the UE regarding how many feedback bits are part of the multiplexed control information can lead to decoding errors at the base station, making the multiplexed transmission worthless.

[0046] It is clear that the methods and procedures discussed herein apply to PUSCH transmissions that collide with PUCCH. They are agnostic of whether the resources are allocated as dynamic or configured grant and apply to all types of PUSCH transmissions.

[0047] Figure 4 Another method of determining transmission priority is shown. In step 400, PUCCH and PUSCH are allocated to transmission resources that overlap in time, e.g. at least one OFDM symbol duration. In step 401, the UE evaluates the relative priority of the transmissions, if they are different, then proceed to step 402 or 403 to perform the transmission of highest priority. If both transmissions have the same priority, then the UE proceeds to step 404.

[0048] In step 404, the UE evaluates the actual priority of both transmissions. If the priority is low, then in step 405, the UE multiplexes data and control information and transmits the multiplexed data on the PUSCH. In step 406, if the priority is high, then the UE transmits the data transmission on the PUSCH with priority over the control information. As mentioned above, the base station assumes the unsent HARQ feedback is a NACK message. An example of the priority can be a physical layer priority indication. For URLLC services, the base station sets this indication to 1 (high priority). For normal priority, the indication is set to 0 (normal or low priority). A missing indication is also assumed to be 0. Then in step 401, the priority of the PUCCH and PUSCH are compared to decide whether to perform step 402 or step 403. If both PUCCH and PUSCH have the same priority, then step 404 compares what the actual priority is. In step 405, in the case of 0 (low priority), the UE multiplexes control and data. In the case of 1 (high priority), the UE transmits the PUSCH as per step 404.

[0049] Figure 4 The method of ensures low priority transmission according to the scheduled timing, although the reliability can be reduced due to the multiplexing of control and data transmissions. However, for high priority transmissions, this reduced reliability can result in the delay and QoS targets not being met, hence the transmission is of data rather than control information. The base station will assume a NACK for the feedback. Then, taking into account the priority and PDB, it can decide to trigger the feedback or retransmit the related data, thus ensuring good transmission quality of the uplink and downlink data flow.

[0050] Figure 5Another example of prioritization is shown, where the PUSCH transmission is for a dynamic grant or configured grant based PUSCH, but without CG-UCI. At step 500, the PUCCH and PUSCH transmissions are scheduled on resources that overlap in time, e.g. by at least one OFDM symbol. At step 501, the UE evaluates the relative priority of the two transmissions, and if they are different, proceeds to step 502 or 503 to transmit the transmission of highest priority.

[0051] If the two transmissions have the same priority, the UE proceeds to step 504, where the nature of the PUCCH transmission is evaluated. If the HARQ feedback in the control transmission is NACK, the UE proceeds to step 505 and prioritizes the PUSCH transmission over the PUCCH transmission. As mentioned above, the base station assumes that the expected HARQ feedback is a NACK message and proceeds accordingly.

[0052] At step 504, if the PUCCH transmission is an ACK message, at step 506 the UE prioritizes the PUCCH transmission over the PUSCH transmission. The advantage of this scheme is that the base station will not perform any useless retransmission for a lost HARQ feedback, since the HARQ feedback is only lost in step 505, where the HARQ feedback is NACK.

[0053] Figure 6 A modification to the method of Figure 5 is shown, where the system operates in unlicensed spectrum and is configured to use a per configured grant UCI. This UCI can be referred to as CG-UCI. The same steps have the same reference numerals. Figure 5

[0054] At step 600, if the HARQ feedback is ACK, the UE further checks if CG-UCI and HARQ feedback multiplexing is enabled. If multiplexing is enabled, the UE multiplexes the HARQ feedback with the CG-UCI at step 601 and transmits the multiplexed CG-UCI and ACKed CG-PUSCH. If multiplexing is not enabled, the PUCCH (with HARQ feedback) is transmitted at step 602 and the CG-PUSCH (together with CG-UCI) is not transmitted.

[0055] If the HARQ feedback is available for multiple TBs, the HARQ feedback value (ACK or NACK) of the last received TB before the collision can be used at step 600. Another option is to combine the feedback of multiple TBs in a single Boolean value to facilitate Figure 6 the decision of

[0056] ​In this approach, if the feedback is NACK, the base station behavior is as expected and there is no drawback of not sending the feedback. If the feedback is ACK, the base station can schedule a retransmission, resulting in a reduced efficiency of the transmission resources, but the transmission of the PUSCH does not reduce the reliability.

[0057] Figure 7 Another prioritization approach is shown, applicable to PUSCH and PUCCH transmission overlap (step 700), e.g. at least one OFDM symbol, and the HARQ feedback is configured with CBG based feedback.

[0058] At step 701, the relative priorities are evaluated and if they are different, the transmission of higher priority is performed at step 702 or 703 and the other transmission is skipped. If the two transmissions have the same priority, the UE proceeds to step 704 and switches to TB based HARQ feedback. At step 705, the UE transmits the PUCCH (with HARQ feedback) multiplexed with the PUSCH. If the PUSCH is a configured grant PUSCH transmission with CG-UCI and the HARQ feedback has the same priority, the TB level HARQ feedback will be multiplexed with the CG-UCI and transmitted together with the PUSCH.

[0059] CBG based feedback typically contains more data than TB based feedback, so switching to TB based feedback reduces the feedback data to be transmitted. Therefore, as less puncturing is needed to accommodate the PUCCH transmission, the reduction of the PUSCH transmission reliability due to multiplexing is reduced. This approach also ensures that the TB level feedback is transmitted without delay, eliminating the need for the base station to make assumptions on the feedback due to missing PUCCH transmission.

[0060] As mentioned above, aspects of each example can be used in different combinations than shown and described herein, in particular with respect to the change from CBG based HARQ feedback to TB based HARQ feedback, which can be in any of the above examples.

[0061] Thus, various approaches for resolving a conflict between scheduling data and control transmissions are provided. The conflict can be resolved by selecting the transmission to be performed based on the relative priority of the transmissions, the type of transmission or other relevant parameters of the two transmissions.

[0062] Although not shown in detail, any apparatus forming part of the network can comprise at least a processor, a storage unit and a communication interface, wherein the processor, storage unit and communication interface are configured to perform the method of any aspect of the application. Further options and choices are described below.

[0063] The signal processing functionality of embodiments of the present application, particularly of the gNB and the UE, can be achieved using a computer system or architecture known to those having ordinary skill in the art. The computer system can be a desktop computer, a laptop or notebook computer, a handheld computing device (PDA, cell phone, palmtop, etc.), a server, a client, or any other type of general purpose computing device that can be used in a given application or environment. The computer system can include one or more processors that can be implemented using a general or special purpose processing engine such as a microprocessor, microcontroller or other control module.

[0064] The computer system can also include a main memory, such as random access memory (RAM) or other dynamic storage devices, for storing information and instructions to be executed by the processor. The main memory also can be used for storing temporary variables or other intermediate information during execution of instructions by the processor. The computer system can likewise include a read only memory (ROM) or other static storage device for storing static information and instructions for the processor.

[0065] The computer system can further include an information storage system. The information storage system can include a media drive and a removable storage interface. The media drive can include a drive or other mechanism to accept and read or write a media, such as a hard disk drive, a floppy disk drive, a magnetic tape drive, an optical drive, a compact disc (CD) or digital video drive (DVD) (RTM) read or write drive (including a writeable and re-writeable drive), or other removable or fixed media drive. A media drive can read from and / or write to a media, such as a hard disk, a floppy disk, magnetic tape, an optical disc, CD or DVD, or other fixed or removable media. Storage media can include computer-readable storage media that has stored thereon computer-executable instructions or data structures representing a computer program, program components.

[0066] In alternative embodiments, the information storage system can include other similar components for allowing computer programs or other instructions or data to be loaded into the computer system. Such components can include, for example, a removable storage unit and an interface, such as a program cartridge and cartridge interface, a removable memory (for example, a flash memory or other removable memory module) and memory slot, and other removable storage units and interfaces that allow software and data to be transferred from the removable storage unit to the computer system.

[0067] The computer system can also include a communications interface. This communications interface can be used to allow software and data to be transferred between the computer system and external devices. Examples of communications interface can include a modem, a network interface (such as an Ethernet or other NIC card), a communications port (such as a Universal Serial Bus (USB) port), a PCMCIA slot and card, etc. Software and data transferred via the communications interface are in the form of signals which can be electronic, electromagnetic, and optical or other signals capable of being received by a communications interface.

[0068] In this document, the terms "computer program product," "computer-readable medium," and the like can be used to generally refer to tangible media such as memory, memory devices, or storage units. These, and other forms of computer-readable media, can store one or more instructions for use by a processor including, for example, a computer system, to create an artificial neural network for performing specified operations. Such instructions, generally referred to as "computer program code" (which can be grouped in the form of computer programs or other groupings), when executed, enable the computer system to perform the functions of embodiments of the present application. Note that the code can directly cause a processor to perform specified operations, be compiled to execute such operations, and / or be combined with other software, hardware, and / or firmware elements (e.g., a function library) to execute such operations.

[0069] A non-transitory computer-readable medium can include at least one of the following: a hard disk, a CD-ROM, an optical storage device, a magnetic storage device, a ROM, a PROM, an EPROM, an EEPROM, and a flash memory. In embodiments where the components are implemented using software, the software can be stored in a computer-readable medium and loaded into the computer system using, for example, a removable storage drive. The control module (in this example, software instructions or executable computer program code) when executed by the processor in the computer system, causes the processor to perform the functions of the present application as described herein.

[0070] Furthermore, the inventive concept can be applied to any circuitry for performing signal processing functions within a network component. It is further envisaged that, for example, a semiconductor manufacturer can employ the inventive concept in the design of stand-alone devices, such as microcontrollers of digital signal processors (DSPs), or application specific integrated circuits (ASICs) and / or any other sub-system elements.

[0071] For clarity, the above description has described embodiments of the present application with reference to a single processing logic. However, the inventive concept can equally be implemented by a plurality of different functional units and processors to provide the signal processing functionality. Therefore, reference to a particular functional unit is only by way of example and without implying any limitation on the scope and spirit of the application.

[0072] Aspects of the application can be implemented in any suitable form including hardware, software, firmware or any combination of these. The application can be implemented at least partly as computer software running on one or more data processors and / or digital signal processors or configurable module components such as FPGA devices.

[0073] Thus, the components of the embodiments of the application can be physically, functionally and logically implemented in any suitable way. Indeed, the functionality can be implemented in a single unit, in a plurality of units or as part of other functional units. Although the application has been described in connection with some embodiments, it is not intended to be limited to the particular form set forth herein. Rather, the scope of the present application is limited only by the claims. Furthermore, although features of the application can appear to be described in conjunction with particular embodiments, one of ordinary skill in the art will understand that various features of the described embodiments can be combined in accordance with the application. In the claims, the term comprising does not exclude the presence of other elements or steps than those listed in a claim.

[0074] Furthermore, although individually listed, a plurality of means, components or method steps can be implemented by e.g. a single unit or processor. Additionally, although individual features can be included in different claims, these can advantageously be combined, and the inclusion of a dependency in a claim is not meant to require the combination of the dependent features into the specific combination recited in that claim. Also, the inclusion of a feature in one category of claims does not preclude that it can also be included in another category of claims. Furthermore, those of ordinary skill in the art will recognize that certain features of the described embodiments can be interchanged or reversed or otherwise modified without departing from the scope of the described embodiments.

[0075] Furthermore, the order of the features in the claims does not imply any specific order of performing the features and for method claims the order of dependent claims is not interpreted as a requirement for performing the steps of these in the order listed in the claims. In addition, single units can fulfill the functions of several features recited in the claims. The recognition of have a single product as several units and recognizing the interrelation of these units is a matter of normal skill in the art. Furthermore, the terms in the claims have their plain, ordinary meaning unless otherwise explicitly qualified by the application. Use of the term "including" as well as other forms of the term, such as "comprising" or "having," is not limiting.

[0076] Although the application has been described in connection with some embodiments, it is not intended to be limited to the particular form set forth herein. Rather, the scope of the present application is limited only by the claims. Furthermore, although features of the application can appear to be described in conjunction with particular embodiments, one of ordinary skill in the art will understand that various features of the described embodiments can be combined in accordance with the application. In the claims, the terms "including" or "comprising" do not exclude the presence of other elements or steps than those listed in a claim.

Claims

1. A method of prioritizing data transmission and control transmission from a user equipment (UE) to a base station, wherein the data transmission and the control transmission have overlapping resources, characterized in that, The method comprises: scheduling, at the UE, a data transmission and a control transmission, wherein transmission resources of each transmission overlap; and selecting, at the UE, one of the data transmission and the control transmission to be transmitted in the transmission resources; wherein the selecting is based on characteristics of the data transmission and the control transmission; wherein when the control transmission is HARQ feedback, if the HARQ feedback is ACK, the control transmission is prioritized for transmission, if the HARQ feedback is NACK, the data transmission is prioritized for transmission, and when the data transmission is selected, unreceived HARQ feedback is considered as NACK and retransmission of data is scheduled; and when the control transmission is CBG feedback and collides with the data transmission, in case of same priority of the control transmission and the data transmission, the CBG feedback is switched to TB feedback and the control transmission is multiplexed with the data transmission.

2. The method according to claim 1, characterized in that, The characteristics are relative priorities of the data transmission and the control transmission.

3. The method of claim 1, wherein, The data transmission is selected based on characteristics of the transmission carrying data.

4. The method of claim 1, wherein, When the absolute priority is low, the UE selects the data transmission and the control transmission and multiplexes the control transmission with the data transmission, and when the absolute priority is high, the UE selects the data transmission.

5. The method of claim 4, wherein, The UE switches to TB-based feedback for multiplexing the control transmission.

6. A user equipment configured to perform the method of any one of claims 1 to 5.

Images