User-in-device multiplexing method, user equipment, and wireless node enabling the method

Abstract

A user equipment (UE) internal multiplexing method is performed in a UE. The UE obtains a time condition for multiplexing a high priority uplink transmission and a low priority uplink transmission when a collision between the different priority uplink transmissions is detected in time. The UE multiplexes the different priority uplink transmissions when the time condition is met.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of communication systems, in particular to a user equipment internal uplink traffic multiplexing. BACKGROUND

[0002] Wireless communication systems and networks have evolved into a broadband and mobile system. 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 (BS) providing wireless links to the UEs located in cells covered by the base stations and an interface to a core network (CN) providing overall network control. It is understood that the overall network related functionality. The 3rd Generation Partnership Project (3GPP) has developed a so-called Long Term Evolution (LTE) system, i.e. an Evolved Universal Mobile Telecommunication System Territorial Radio Access Network (E-UTRAN), for mobile access networks, in which one or more macro cells are supported by a base station called eNodeB or eNB. Recently, LTE is further developed towards the so-called 5G or new radio (NR) system, in which one or more cells are supported by a base station called gNB.

[0003] Ultra-reliable low-latency communication (URLLC) is one of several different types of use cases supported by the 5G NR standard specified by 3GPP Release 15. URLLC is a communication service for successful delivery of data packets with stringent requirements, in particular in terms of availability, latency and reliability. URLLC is developed to support emerging applications and services such as wireless control and automation in industrial factory environments, inter-vehicle communication for improved safety and efficiency, and the tactile internet. URLLC is therefore important for 5G, supporting verticals bringing new business to the whole telecom industry.

[0004] One of the key points of the URLLC is low latency, which makes self-driving cars and remote surgery possible. Low latency optimizes the network to handle an incredible amount of data with minimal latency or no latency. The quality of service (QoS) required by URLLC is completely different from that of mobile broadband services.

[0005] URLLC guarantees a latency of 1 millisecond (ms) or less. Time-sensitive networking (TSN) is another component of the 5G URLLC. All devices connected along the URLLC must be synchronized on the same time basis. For example, the enabling technologies for URLLC include: integrated frame structure, incredibly fast turnaround, efficient control and data resource sharing, grant-free based uplink transmission, and advanced channel coding schemes.

[0006] Technical problem

[0007] 5G NR communication requires intra-UE multiplexing and traffic priority handling of different priorities. The scenario of coexistence of channels with different priorities is very important for industrial internet of things (IIoT) / URLLC use cases. The uplink (UL) traffic of high priority channels is prioritized over low priority channels. However, from the perspective of system performance, it is not good to always discard low priority UL transmissions. Therefore, new enhancements are needed for the current multiplexing mechanism for different priorities of UL transmissions. SUMMARY

[0008] One object of the present disclosure is to propose an intra-UE multiplexing method, a wireless node and a user equipment (UE).

[0009] A first aspect of the disclosure provides an intra-UE multiplexing method that can be performed in a UE.

[0010] The method comprises:

[0011] identifying a set of overlapping uplink transmissions in a time resource unit, wherein the set of overlapping uplink transmissions comprises a first high priority uplink transmission of a high priority traffic type and a first low priority uplink transmission of a low priority traffic type;

[0012] obtaining a first multiplexing time condition for the high priority traffic type and a second multiplexing time condition for the low priority traffic type; and

[0013] multiplexing the first high-priority uplink transmission and the first low-priority uplink transmission in the time resource unit when the first high-priority uplink transmission satisfies the first multiplexing time condition and the first low-priority uplink transmission satisfies the second multiplexing time condition.

[0014] A second aspect of the disclosure provides a method of user equipment (UE) intra- multiplexing that can be performed in a wireless node device. The method comprises:

[0015] transmitting a control signal to enable a multiplexing mode to multiplex a set of overlapping uplink transmissions in a time resource unit at a user equipment (UE) side;

[0016] when the set of overlapping uplink transmissions comprises a first high-priority uplink transmission of a high-priority traffic type and a first low-priority uplink transmission of a low-priority traffic type, allowing the user equipment (UE) to acquire, in the multiplexing mode, a first multiplexing time condition of the high-priority traffic type and a second multiplexing time condition of the low-priority traffic type; and

[0017] when the first high-priority uplink transmission satisfies the first multiplexing time condition and the first low-priority uplink transmission satisfies the second multiplexing time condition, allowing the user equipment (UE) to multiplex, in the multiplexing mode, the first high-priority uplink transmission and the first low-priority uplink transmission in the time resource unit.

[0018] A third aspect of the disclosure provides a user equipment comprising a transceiver and a processor connected with the transceiver. The processor is configured to perform steps comprising:

[0019] identifying a set of overlapping uplink transmissions in a time resource unit, wherein the set of overlapping uplink transmissions comprises a first high-priority uplink transmission of a high-priority traffic type and a first low-priority uplink transmission of a low-priority traffic type;

[0020] acquiring a first multiplexing time condition of the high-priority traffic type and a second multiplexing time condition of the low-priority traffic type; and

[0021] multiplexing the first high-priority uplink transmission and the first low-priority uplink transmission in the time resource unit when the first high-priority uplink transmission satisfies the first multiplexing time condition and the first low-priority uplink transmission satisfies the second multiplexing time condition.

[0022] A fourth aspect of the present disclosure provides a wireless node device, comprising a transceiver and a processor connected with the transceiver. The processor is configured to perform the following steps, comprising:

[0023] transmitting a control signal to enable a multiplexing mode to multiplex a set of overlapping uplink transmissions in a time resource unit at a user equipment (UE) side;

[0024] when the set of overlapping uplink transmissions comprises a first high priority uplink transmission of a high priority service type and a first low priority uplink transmission of a low priority service type, allowing the user equipment (UE) to acquire a first multiplexing time condition of the high priority service type and a second multiplexing time condition of the low priority service type in the multiplexing mode; and

[0025] when the first high priority uplink transmission satisfies the first multiplexing time condition and the first low priority uplink transmission satisfies the second multiplexing time condition, allowing the user equipment (UE) to multiplex the first high priority uplink transmission and the first low priority uplink transmission in the time resource unit in the multiplexing mode.

[0026] The disclosed method can be implemented in a chip. The chip can comprise a processor configured to invoke and run a computer program stored in a memory to cause a device installed with the chip to perform the disclosed method.

[0027] The disclosed method can be programmed as computer executable instructions stored in a non-transitory computer readable medium. The non-transitory computer readable medium, when loaded into a computer, instructs a processor of the computer to perform the disclosed method.

[0028] The non-transitory computer readable medium can comprise at least one from a group consisting of a hard disk, a compact disc read only memory (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 (EPROM), an electrically erasable programmable read-only memory (EEPROM), and a flash memory.

[0029] The disclosed method can be programmed as a computer program product to cause a computer to perform the disclosed method.

[0030] The disclosed method can be programmed as a computer program to enable a computer to perform the disclosed method.

[0031] Advantageous effects

[0032] The disclosed uplink (UL) multiplexing method solves the problem of collision between UL transmissions with different priorities. It is clear that always dropping / skipping the low priority channel can severely impact the overall latency of the system and cause unnecessary inefficiency. With respect to multiplexing, the conventional mechanism is not suitable for UL transmissions with different traffics. The disclosure provides several embodiments to accommodate different scenarios. Considering the compatibility with previous releases, we provide alternative designs to enable multiplexing for UL transmissions with different priorities. To achieve better performance, new time conditions, UCI bit sequence generation, and collision handling procedures are introduced for multiplexing of UL transmissions with different priorities.

[0033] For traffics with different priorities, including uplink control information (UCI) on physical uplink shared channel (PUCCH) and UCI on PUSCH, it is necessary to determine the multiplexing between hybrid automatic repeat request (HARQ) acknowledgement (HARQ-ACK), scheduling request (SR), channel state information (CSI), and physical uplink shared channel (PUSCH). Since URLLC traffic has more stringent requirements on delay and reliability, how to multiplex different services is still a problem. For example, dropping eMBB transmission can cause retransmission of eMBB traffic. For HARQ feedback, dropping HARQ-ACK can cause PDSCH retransmission with large transport block size (TBS). One aspect of the disclosure provides a multiplexing method for different services with different priorities to improve the performance of eMBB.

[0034] The disclosed method provides alternative designs for multiplexing mechanisms, including forward-compatible multiplexing, time-domain resource allocation to improve URLLC latency, UCI bit sequence generation for different priority UCI, and collision handling for different priority traffics. In addition, the disclosed method provides different specific designs to provide flexibility and accommodate different scenarios. BRIEF DESCRIPTION OF DRAWINGS

[0035] For more clearly illustrating the embodiments of the present disclosure or related technology, the following figures will briefly introduce the embodiments. Obviously, the skilled in the art can obtain other figures according to these figures without prior premise.

[0036] Figure 1 is a schematic diagram of a system according to embodiments of the present disclosure.

[0037] Figure 2 shows a method disclosed according to embodiments of the present disclosure.

[0038] Figure 3 a schematic diagram shows a first example of collision between uplink transmissions with different priorities.

[0039] Figure 4 a schematic diagram shows a second example of collision between uplink transmissions with different priorities.

[0040] Figure 5 a schematic diagram shows a third example of collision between uplink transmissions with different priorities.

[0041] Figure 6 a schematic diagram shows a fourth example of collision between uplink transmissions with different priorities.

[0042] Figure 7 a schematic diagram shows a fifth example of collision between uplink transmissions with different priorities.

[0043] Figure 8 a schematic diagram shows a sixth example of collision between uplink transmissions with different priorities.

[0044] Figure 9 is a structural block diagram of a system for wireless communication according to embodiments of the present disclosure. DETAILED DESCRIPTION

[0045] The disclosed embodiments describe the technical matters, structural features, implementation purposes and effects in detail with reference to the drawings, as follows. Specifically, the terms in the embodiments of the present disclosure are only for the purpose of illustrating a certain embodiment, not for limiting the present disclosure.

[0046] URLLC and time sensitive communication (TSC) are examples of high priority traffic types. Enhanced mobile broadband (eMBB), machine type communication (MTC), and massive MTC are examples of low priority traffic types. Embodiments of the disclosed methods facilitate intra-UE multiplexing of UL transmissions with different priorities.

[0047] Reference is made to Figure 1 a telecommunication system including a UE 10a, a UE 10b, a base station (BS) 200a, and a network entity 300, which perform the disclosed methods according to an embodiment of the present application. Figure 1 The figures are shown for illustration and not limitation, and the system can include more UEs, BSs, and CN entities. Connections between devices and device components are shown as lines and arrows in Figure 1 The UE 10a can include a processor 11a, a memory 12a, and a transceiver 13a. The UE 10b can include a processor 11b, a memory 12b, and a transceiver 13b. The base station 200a can include a processor 201a, a memory 202a, and a transceiver 203a. The network entity 300 can include a processor 301, a memory 302, and a transceiver 303. Each of the processors 11a, 11b, 201a, and 301 can be configured to implement the functions, procedures, and / or methods described in the description. Layers of the radio interface protocol can be implemented in the processors 11a, 11b, 201a, and 301. Each of the memories 12a, 12b, 202a, and 302 can be operable to store various programs and information for operating the connected processors. Each of the transceivers 13a, 13b, 203a, and 303 can be operatively connected with the connected processors to transmit and / or receive radio signals or wired signals. The UE 10a can communicate with the UE 10b through a sidelink 110. The base station 200a can be one of an eNB, a gNB, or other similar radio node, and can configure radio resources for the UE 10a and the UE 10b.

[0048] Each of the processors 11a, 11b, 201a, and 301 can include an application-specific integrated circuit (ASIC), other chip sets, logic circuit, and / or a data processing device. Each of the memories 12a, 12b, 202a, and 302 can include a read-only memory (ROM), a random access memory (RAM), a flash memory, a memory card, a storage medium, and / or other storage devices. Each of the transceivers 13a, 13b, 203a, and 303 can include a baseband circuit and a radio frequency (RF) circuit to process radio frequency signals. When the embodiments are implemented in software, the techniques can be implemented with a module, a procedure, a function, an entity, and / or the like for performing the functions. The module can be stored in the memory and executed by the processor. The memory can be implemented within the processor or external to the processor in which those can be communicatively coupled by various means as is known in the art.

[0049] The network entity device 300 can be a node in a CN. The CN can include an LTE CN or a 5G core (5GC) including a user plane function (UPF), a session management function (SMF), a mobility management function (AMF), a unified data management (UDM), a policy control function (PCF), a control plane / user plane separation (CUPS), an authentication server (AUSF), a network slice selection function (NSSF), and the network exposure function (NEF).

[0050] Reference Figure 2 , a UE, for example Figure 1The UE 10a or 10b described in the foregoing will perform the intra-UE multiplexing method. The UE enters a multiplexing mode to perform the intra-UE multiplexing method (block 210). The UE can actively enable the multiplexing mode or passively enter the multiplexing mode in response to control signaling from a network entity, such as the BS 200a or the network entity device 300.

[0051] Embodiments of the disclosed method for enabling intra-UE multiplexing with different priorities are described in detail below.

[0052] To be compatible with previous versions of 3GPP standards, multiplexing of uplink (UL) transmissions with different priorities can be selectively configured by a base station, such as the aforementioned BS 200a, or triggered by certain conditions. Release 16 of the 3GPP standard can be used as a reference. The disclosed method can be applied to multiplexing HARQ-ACK / SR / CSI and PUSCH for traffic with different priorities. In the description herein, HARQ-ACK represents HARQ feedback, which can include acknowledgment (ACK) and negative acknowledgment (NACK).

[0053] Embodiments of the disclosed method for command-enabled intra-UE multiplexing are described in detail below.

[0054] The multiplexing procedure for different priorities can be configured by downlink control information (DCI) or higher layer signaling, such as radio resource control (RRC) signaling. For example, the base station can send the parameter IntraUEMUXDiffPrio to the UE to indicate that the multiplexing mode is enabled. The UE multiplexes UL transmissions with different priorities in response to the parameter IntraUEMUXDiffPrio configured by DCI or higher layer signaling. For example, the aforementioned IntraUEMUXDiffPrio indication indicates that the multiplexing mode is enabled to support the multiplexing procedure for different priorities. On the other hand, the IntraUEMUXDiffPrio deactivation indicates that the multiplexing mode is disabled and the multiplexing procedure for different priorities is not supported.

[0055] Embodiments of the disclosed method for event-triggered intra-UE multiplexing are described in detail below.

[0056] Certain conditions can also enable uplink transmission multiplexing with different priorities. With the current mechanism in NR Release 16, only traffic priority handling and cancellation is performed for UL transmission conflicts between different traffic priorities. Thus, eMBB traffic type is a lower priority traffic type than URLLC, and will be dropped when UL transmission conflicts with URLLC, resulting in poor system performance. Thus, the UE can use a counter to count the number of dropped eMBB transmissions. When the counter is greater than a configured threshold, the UE can send a request to the base station to enable the multiplexing mode for UL transmissions with different priorities. The request can be transmitted through PUCCH or PUSCH. The base station receives the request and enables the multiplexing mode in response to the request.

[0057] Thus, the UE can enable the multiplexing mode in response to a condition that the counter counts the number of dropped low-priority uplink transmissions has reached a predetermined number of times. Alternatively, the UE can enable the multiplexing mode in response to a condition that the number of dropped low-priority uplink transmissions in a period of time reaches a predetermined ratio of all low-priority uplink transmissions.

[0058] Frequent dropping of eMBB transmissions can result in frequent retransmission of eMBB. The base station can determine whether to enable the multiplexing procedure for UL transmissions with different priorities based on the retransmission time of eMBB, the eMBB transport block (TB) size, the channel quality, etc. The enablement command can be the same as shown in the paragraph related to the parameter IntraUEMUXDiffPrio. The base station can enable the multiplexing mode when it detects that the number of eMBB retransmissions exceeds a predetermined number of times. The base station can enable the multiplexing mode for eMBB traffic whose TB size is greater than a predetermined TB size. The base station can enable the multiplexing mode in response to a channel quality condition that is below a predetermined channel quality level.

[0059] Embodiments of the disclosed method of providing time condition enhancements are detailed below.

[0060] In Release 16, the multiplexing procedure is only performed between UL transmissions of the same priority. The UE multiplexes all UCI types if the time condition is met. The UE expects the first symbol S0 of the earliest PUCCH or PUSCH in a set of overlapping PUCCHs and PUSCHs in a slot to meet the following time condition. Taking PDSCH as an example, S0 is not preceded by a symbol with cyclic prefix (CP) that is Starts after the last symbol of any corresponding PDSCH associated with the earliest PUCCH or PUSCH. The processing time is given by the maximum of , where for the ith PDSCH with a corresponding HARQ-ACK transmission in the set of overlapping PUCCH and PUSCH, is selected according to 3GPP Technical Specification TS 38.214 clause 5.3 for the ith PDSCH 1,1 . N1 is selected according to the UE PDSCH processing capability and subcarrier spacing (SCS) configuration μ of the ith PDSCH. The μ corresponds to the smallest SCS configuration in the SCS configurations used for all relevant uplink and downlink transmissions, including: the ith PDSCH, the PDCCH used to schedule the ith PDSCH (if any), the PUCCH with a corresponding HARQ-ACK transmission for the ith PDSCH, and all PUSCHs in the set of overlapping PUCCH and PUSCH. N1 and d 1,1 are defined in TS 38.214 clause 6, and κ and T C are defined in TS 38.211 clause 4.

[0061] Figures 3-8 An example of collision between uplink transmissions with different priorities in a slot is shown. Referring to Figure 3 , PDSCH1 is a low-priority downlink transmission with a corresponding HARQ-ACK feedback HARQ1. PDSCH2 is a high-priority uplink transmission with a corresponding HARQ-ACK feedback HARQ2. The low-priority downlink transmission can belong to the eMBB traffic type. The high-priority uplink transmission can belong to the URLLC traffic type. The HARQ1 and HARQ2 overlap with each other in one time resource unit (e.g., one slot). If the repetition of the mechanism in Release 16 is enabled for the multiplexing procedure, S0 is the first symbol of the HARQ1, and the processing time is given by the maximum of . is applicable for the low-priority downlink transmission PDSCH1. Applicable to the high priority downlink transmission PDSCH2. For URLLC traffic, due to the low latency requirement of the URLLC traffic, PDSCH2 corresponding to processing capability 2 is often performed according to TS 38.214 Section 5.3. PDSCH1 corresponding to processing capability 1 or capability 2 has a higher subcarrier spacing than the PDSCH2. Such a relationship PDSCH1 >μ PDSCH2 Means the higher the priority, the shorter the PDSCH processing time, then Where μ PDSCH1 is the subcarrier spacing of PDSCH1, μ PDSCH2 is the subcarrier spacing of PDSCH2. However, according to the aforementioned multiplexing time condition, in previous versions (e.g. version 15 and version 16), S0 will not be before the symbol with CP, which starts after The last symbol of any corresponding PDSCH. The time condition requires that the duration T1 between PDSCH1 and HARQ1 and the duration T2 between PDSCH2 and HARQ2 are both greater than That is And This time condition is too strict, especially for high priority traffic, because T2 is very likely to be less than However, the multiplexing procedure can be enabled in Case, because if The time is still sufficient to multiplex PDSCH1 and PDSCH2. When the multiplexing procedure is not enabled, the priority mechanism will discard the UL transmission with low priority. In order to minimize the eMBB performance degradation, especially when URLLC traffic is continuously scheduled, it is necessary to enhance the multiplexing time condition for UL transmissions with different priorities.

[0062] In an embodiment of the disclosed method, referring to Figure 2 , the UE identifies a set of overlapping uplink transmissions (block 211) in a time resource unit (e.g. one slot) in the multiplexing mode. The set of overlapping uplink transmissions includes a first high-priority uplink transmission of a high-priority traffic type and a first low-priority uplink transmission of a low-priority traffic type. The first high-priority uplink transmission can be any UCI type or PUSCH. The first low-priority uplink transmission can be any UCI type or PUSCH.

[0063] The UE obtains the first multiplexing time condition for the high-priority service type and the second multiplexing time condition for the low-priority service type (block 212). The UE determines whether the first high-priority uplink transmission meets the first multiplexing time condition and whether the first low-priority uplink transmission meets the second multiplexing time condition (block 213).

[0064] For multiple uplink transmissions of the high-priority service type in the set of overlapping uplink transmissions within a time resource unit, the first multiplexing time condition of the high-priority service type includes multiple processing time values ​​(e.g., The first processing time is obtained by maximizing the value in ). The first multiplexing time condition requires that, in the multiple uplink transmissions of the high-priority service type in the set of overlapping uplink transmissions, the first symbol of the earliest high-priority uplink transmission is not S0 before the delimiter symbol with a cyclic prefix (CP), and after the last symbol of the high-priority downlink transmission associated with the earliest high-priority uplink transmission, and that the delimiter symbol with a cyclic prefix begins after the first processing time. The delimiter symbol, as in... Figure 3 S in d1 It can be located far from the last symbol (with CP) of the high-priority downlink transmission, at a distance from the first processing time from the last symbol. The earliest high-priority uplink transmission can be the Hybrid Automatic Repeat Request (HARQ) feedback signal of the high-priority downlink transmission. Alternatively, the earliest high-priority uplink transmission can be a PUCCH or a PUSCH scheduled by the high-priority downlink transmission.

[0065] For multiple uplink transmissions of the low-priority service type in the set of overlapping uplink transmissions within a time resource unit, the second multiplexing time condition for the low-priority service type includes a second processing time. This time is derived from multiple processing time values ​​(e.g.) The value is obtained from the maximum value in ). The second multiplexing time condition requires that, in the multiple uplink transmissions of the low-priority service type in the set of overlapping uplink transmissions, the first symbol S0 of the earliest low-priority uplink transmission is not before the delimiter symbol with a cyclic prefix (CP), and after the last symbol of the low-priority downlink transmission associated with the earliest low-priority uplink transmission, and the delimiter symbol with the cyclic prefix begins after the second processing time. The delimiter symbol, such as Figure 3 The separator S in d2The earliest low-priority uplink transmission can be located at a position away from a last symbol (with CP) of the preceding low-priority downlink transmission, by a length of the second processing time from the last symbol x. The earliest low-priority uplink transmission can be a HARQ feedback signal of the low-priority downlink transmission. Alternatively, the earliest low-priority uplink transmission can be a PUCCH or a PUSCH scheduled by the low-priority downlink transmission.

[0066] When the first high-priority uplink transmission does not satisfy the first multiplexing time condition, or when the first low-priority uplink transmission does not satisfy the second multiplexing time condition, the UE performs uplink traffic cancellation to drop low-priority uplink traffic (block 214).

[0067] When the first high-priority uplink transmission satisfies the first multiplexing time condition and the first low-priority uplink transmission satisfies the second multiplexing time condition, the UE multiplexes the first high-priority uplink transmission and the first low-priority uplink transmission in the time resource unit (block 215).

[0068] For example, S0 is the first symbol of the earliest PUCCH or PUSCH. However, the calculation is performed separately for different priorities and whether the first and second multiplexing time conditions are satisfied are determined separately. Specifically, the multiplexing time conditions are calculated separately for different priorities, given by the maximum given by the maximum The UE performs the determination for each priority to determine whether a duration between a relevant downlink transmission and an uplink transmission satisfies a time condition for the priority. For different relationships between the relevant downlink transmission and the uplink transmission, may be used as or or other processing times specified in TS 38.213 Section 9.2.5. For example, may be the maximum selected from may be the maximum selected from may be the maximum selected from may be the maximum selected from may be the maximum selected from may be the maximum selected from may be the maximum selected from may be the maximum selected from

[0069] Similarly, may be used as or or other processing time. The or The exact functionality can be the same as in Release 16 or later releases.

[0070] In the above mentioned Figure 3 In an example, two UL transmissions HARQ1 and HARQ2, and the multiplexing time condition for different priorities may be used and If both T1 and T2 satisfy the time condition, the multiplexing procedure is performed. That is, if and The UE can multiplex HARQ1 and HARQ2. If T1 and T2 do not satisfy the multiplexing time condition, the UE performs UL cancellation to drop the low priority UL transmission, e.g. HARQ1.

[0071] Embodiments of UCI bit sequence generation are detailed below.

[0072] The UE generates a UCI bit sequence a0, a1, a2, a3,..., an, an+1, an+2,..., a A-1 to represent the first high priority uplink transmission of the high priority traffic type and the first low priority uplink transmission of the low priority traffic type. The variable A = O ACK + O SR + O CSI If there is no HARQ-ACK for transmission on PUCCH, the UE will set O ACK = 0. If there is no SR for transmission on PUCCH, the UE will set O SR = 0. If there is no CSI for transmission on PUCCH, the UE sets O CSI = 0.

[0073] - O ACK is the total number of HARQ-ACK information bits (if any). If there is no HARQ-ACK for transmission on the PUCCH, the UE sets O ACK = 0;

[0074] - O SR is the total number of SR bits. If O SR = 0 the UE has no scheduling request bits;

[0075] - O where O CSI -part1,n is the number of 1st part CSI report bits of a CSI report with priority value n, OCSI-part2,n is the number of 2nd part CSI report bits (if any) of the CSI report with priority value n, and is the number of CSI reports containing overlapping CSI reports.

[0076] When the multiplexing procedure for UL transmissions with different priorities is enabled, the UE will rearrange the UCI bit sequence. UCI bits of UCI types with higher priority are transmitted first. Regardless of the UCI type of the first high priority uplink transmission and the UCI type of the first low priority uplink transmission, bits in the UCI bit sequence representing the first high priority uplink transmission of the high priority traffic type come before bits in the UCI bit sequence representing the first low priority uplink transmission of the low priority traffic type. For example, all UCI types with high priority should be prioritized, which means the first A HP bits of the UCI bit sequence are of high priority, where A = A HP + A LP . HP denotes the high priority and LP denotes the low priority. For example, if there are HARQ-ACK, SR, and CSI transmissions on PUCCH, the UCI bit sequence can be where A HP = O ACK,HP + O SR,HP + O CSI,HP and A LP = O ASCK,LP + O SR,LP + O CSI,LP .

[0077] UCI bits of UCI types with higher priority are transmitted first. Regardless of the UCI type of the first high priority uplink transmission and the UCI type of the first low priority uplink transmission, bits in the UCI bit sequence representing the first high priority uplink transmission of the high priority traffic type come before bits in the UCI bit sequence representing the first low priority uplink transmission of the low priority traffic type. For example, for each UCI type, UL transmissions with high priority are prioritized first, where A = A HP + A LP . For example, if there are HARQ-ACK, SR, and CSI transmissions on PUCCH, the total number of UCI bits can also be calculated as A = O ACK.HP + O ACK.LP + O SR.HP + O SR.LP + O CSI.HP + O CSI.LP where A HP = O ACK,HP+O SR,HP +O CSI,HP and A LP =O ACK,LP +O SR,LP +O CSI,LP .

[0078] For example, for a total number of O ACK HARQ-ACK information bits, a UE determines HARQ-ACK information bits, where O ACK =O ACK,HP +O ACK,LP The aforementioned HARQ-ACK bits are mapped to the aforementioned UCI bit sequence a0, a1, a2, a3,..., a OACK-1 , where for i = 0, 1,..., O ACK.HP -1, then and for i = O ACK.HP , O ACK.HP +1,..., O ACK -1, then The aforementioned HARQ-ACK bit sequence is given by clause 9.1 of TS 38.213, and O ACK is the total number of HARQ-ACK bits; if the aforementioned UE has no HARQ-ACK for transmission on the PUCCH, set O ACK = 0. The order is the same for SR and CSI transmission.

[0079] When there are multiple high priority UL transmissions or multiple low priority UL transmissions to multiplex, the UE always puts high priority before low priority. When there are two UL transmissions with the same priority, the UE puts the UL transmission with the earlier first symbol before the UL transmission with the later first symbol. For two UL transmissions with the same first symbol and the same priority, their positions are arbitrary.

[0080] The BS receives the UCI bit sequence from the UE. If the number of UCI bits is not enough to satisfy the UCI type, the UCI bits of high priority UL transmission are processed first in the UCI bit sequence.

[0081] Embodiments of collision handling between more than two 2-tunnel are described in detail below.

[0082] One of the main functions of URLLC is the low latency. Therefore, multiplexing does not have any adverse impact on the latency of the URLLC traffic, which means that the end of PUCCH or PUSCH after the multiplexing cannot be later than the end of PUCCH or PUSCH for URLLC. In the following, the UE enables the multiplexing procedure for UL transmissions with different priorities to ensure that the multiplexed UL transmission is not later than the URLLC UL transmission. When it is determined that the multiplexed UL transmission can be later than the URLLC UL transmission, the UE does not enable the multiplexing procedure for UL transmissions with different priorities, but performs UL prioritization and cancellation.

[0083] In Rel-16, to resolve the collision between UL transmissions, the UE performs the following operations:

[0084] • Step 1: Resolve the collision between UL transmissions with the same priority; and

[0085] • Step 2: Resolve the collision between UL transmissions with different priorities.

[0086] This consensus procedure does not apply to all collision cases during multiplexing of UL transmissions with different priorities, and can cause UL loss. As shown in Figure 4 , a first low priority UL transmission (LP UL1) overlaps with a second low priority UL transmission (LP UL2) in a slot, and the LP UL2 collides with a first high priority UL transmission (HP UL1). According to the agreed procedure in Rel-16, the UE resolves the collision between the low priorities in the first step. The LP UL2 will be dropped when the two low priority UL transmissions do not meet the multiplexing time condition. However, if the LP UL2 can be multiplexed with the HP UL1, all the three UL transmissions can be transmitted without loss. Therefore, this protocol has a negative impact on the performance of the low priority UL transmission. If the multiplexing procedure is performed, the latency of the high priority UL transmission and the reliability of the low priority UL transmission can be guaranteed.

[0087] The multiplexing procedure for more than two UL transmissions collision is detailed below. If the time condition is met, the UE will perform the multiplexing procedure. The set of overlapping uplink transmissions in the time resource unit also includes a second low priority uplink transmission of the low priority traffic type, e.g., LP UL2 in Figure 5 When multiplexing the first and second low priority uplink transmissions with the first high priority uplink transmission is not allowed, the UE can drop one of the first and second low priority uplink transmissions based on the UCI type of the first and second low priority uplink transmissions.

[0088] The set of overlapping uplink transmissions in the time resource unit also includes a second high priority uplink transmission of the high priority traffic type, as in Figure 6 HP UL2. When multiplexing of the first and second high priority uplink transmissions with the first low priority uplink transmission is not allowed, the UE drops the first low priority uplink transmission according to a comparison of the low priority traffic type and the high priority traffic type.

[0089] For example, in Figure 5 and Figure 6 three UL transmissions overlap each other. If the three UL transmissions satisfy the time condition, the UE multiplexes the three UL transmissions together. However, if the UCI sequence does not have enough space to multiplex all the UL transmissions, the UE first prioritizes and multiplexes the UL transmissions with higher priority. As shown in Figure 5 If the multiplexing has limitations, the UE only allows one of the low priority UL transmissions to be multiplexed with high priority UL transmissions. The UE can arbitrarily select or select one among the low priority UL transmissions based on the UCI type. As shown in Figure 6 When the three UL transmissions all satisfy the multiplexing time condition, and the multiplexing has a limitation that only two of the UL transmissions can be multiplexed, the UE drops LP UL1 and multiplexes HP UL1 and HP UL2, as shown in

[0090] From the perspective of the lower priority UL transmission, postponing the low priority UL transmission to a future available UL transmission can miss the appropriate cancellation time. Therefore, a new limitation is set for the multiplexing procedure. As shown in Figure 7As shown, a first low priority UL transmission (LP UL1) overlaps with a first high priority UL transmission (HP UL1) and a second high priority UL transmission (HP UL2), respectively. In some cases, the BS schedules HP UL2 using a second high priority DL transmission (HP DL2). In another case, the HP UL2 is a response to feedback, such as HARQ feedback, of the HP DL2. If the LP UL1 and the HP UL2 satisfy the multiplexing time condition, the UE can multiplex the LP UL1 with the HP UL2 to resolve the collision. However, the UE does not know that the HP UL2 coming after the LP UL1 can be used for multiplexing until the HP DL2 is detected. Between the LP UL1 and the HP UL1, only prioritization can be performed because the multiplexing channel must be later than the end of the HP UL1. If the UE performs prioritization between the LP UL1 and the HP UL1, the LP UL1 needs to be dropped, cancelling the time point as Figure 7

[0091] The UE determines a cancellation time point based on the first high priority uplink transmission (e.g., HP UL1) and the first low priority uplink transmission (e.g., LP UL1). The cancellation time point specifies a location in time to discard at least a portion of the first low priority uplink transmission (LP UL1) that overlaps with the first high priority uplink transmission (HP UL1) when the multiplexing is not enabled.

[0092] When a high priority downlink transmission (HP DL2) containing downlink control information is successfully received before a threshold time range (MuxTh) from the cancellation time point, the downlink control information schedules the subsequent high priority uplink transmission (HP UL2), the UE defers the first low priority uplink transmission (LP UL1) to be multiplexed with the subsequent high priority uplink transmission (HP UL2).

[0093] ​In the example mentioned above, the UE multiplexes LP UL1 and HP UL2 only if HP DL2 is not later than the cancellation time point, and T ≥ 1. T can be measured in units of several symbols. In addition, a new threshold parameter can be identified as MuxTh, which can be determined by DCI or higher layer parameters, such as RRC information element (IE). If the end of the high priority downlink transmission HP DL2 scheduling the HP UP2 is located MuxTh symbols before the cancellation time point, the UE can postpone the first low priority UL transmission LP UL1 to be multiplexed with HP UL2 instead of dropping the LP UL1. As shown in Figure 7 if T ≥ MuxTh, the UE can multiplex LP UL1 and HP UL2.

[0094] Further analysis and solutions for specific scenarios are given below.

[0095] The embodiments detailed above apply to all UCI types or PUSCH. However, for certain specific UCI types, collision handling needs specific procedures.

[0096] In the case of UL collision involving eMBB HARQ and URLLC HARQ, embodiments of the disclosed method are detailed below.

[0097] NR Release 16 supports sub-slot-based HARQ-ACK feedback and supports simultaneously building up to two HARQ-ACK codebooks with different priorities. If multiplexing is performed between eMBB HARQ-ACK and URLLC HARQ-ACK, a solution is needed to handle eMBB and URLLC traffic with different time granularity to minimize the eMBB performance degradation. If there is no collision between the UL resources of eMBB HARQ-ACK and URLLC HARQ-ACK, the UE will transmit the eMBB HARQ-ACK in eMBB PUCCH and the URLLC HARQ-ACK in URLLC PUCCH, respectively.

[0098] When multiplexing the eMBB HARQ feedback and the URLLC HARQ feedback, the UE places sub-slot based HARQ-ACK feedback before slot based HARQ-ACK feedback. In this case, at least a portion of the HARQ-ACK feedback in PUCCH or PUSCH is sub-slot based, which means that the time granularity of the PUCCH or PUSCH is sub-slot based. The UE can set the remaining bits in PUCCH to zero after multiplexing. The BS receives the HARQ-ACK feedback from the UE.

[0099] In the case of UL collision involving HARQ and PUSCH, embodiments of the disclosed method are detailed below.

[0100] In Rel-15, if the UE detects a DCI format scheduling a PUSCH transmission in a slot previously and if the UE multiplexes HARQ-ACK information in the PUSCH transmission, the UE is not expected to detect a DCI format scheduling a PDSCH reception or a SPS PDSCH release in the slot and the DCI format indicates a PUCCH transmission resource with corresponding HARQ-ACK information in the slot. This restriction can introduce additional delay and reduce reliability for URLLC or eMBB and can be removed in Rel-17. As Figure 8 As shown, DCI1 provides scheduling information for PDSCH1 of URLLC service type and HARQ-ACK feedback 80 is a response to PDSCH1. Earlier DCI2 provides scheduling information for PUSCH 82 of eMBB service type. If the restriction in Rel-15 is reused, the overlapping HARQ 80 and PUSCH 82 cannot be multiplexed. URLLC traffic has higher priority than eMBB traffic, so PUSCH of eMBB traffic is dropped in case of collision with URLLC HARQ-ACK feedback 80. Frequent dropping procedure has significant negative impact on the performance of eMBB service. If the multiplexing is performed with the time condition satisfied, the multiplexing procedure is performed to guarantee the performance of URLLC and eMBB. In addition, the BS can indicate a beta offset to the UE to determine the number of radio resources used to multiplex HARQ-ACK 80 in PUSCH 82. Similarly, in another example where DCI1 is of eMBB service type and DCI2 is of URLLC service type, the embodiments apply as well. Any combination of the embodiments is possible.

[0101] Figure 9is a block diagram of a system 700 for wireless communication as an example in accordance with an embodiment of the application. The embodiments described herein can be implemented into a system using any suitable configuration of hardware and / or software. Figure 9 The system 700 is shown comprising a radio frequency (RF) circuitry 710, a baseband circuitry 720, a processing unit 730, a memory / storage 740, a display 750, a camera 760, a sensor 770, and an input / output (I / O) interface 780, coupled with each other as shown.

[0102] The processing unit 730 can include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor can include any combination of general-purpose processors and dedicated processors such as graphics processors and application processors. The processor can be coupled with the memory / storage and configured to execute instructions stored in the memory / storage to enable various applications and / or an operating system to execute on the system.

[0103] The baseband circuitry 720 can include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor can include a baseband processor. The baseband circuitry can handle various radio control functions to enable the communication with one or more radio networks via the radio frequency circuitry. The radio control functions can include, but are not limited to, signal modulation, encoding, decoding, frequency shifting, and the like. In some embodiments, the baseband circuitry can provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry can support communication with a 5G NR, LTE, Evolved Universal Terrestrial Radio Access Network (EUTRAN), and / or other wireless metropolitan area networks (WMANs), wireless local area networks (WLANs), and wireless personal area networks (WPANs). Embodiments in which the baseband circuitry is configured to enable wireless communication using more than one wireless protocol can be referred to as multi-mode baseband circuitry. In various embodiments, the baseband circuitry 720 can include circuitry to operate signals that are not strictly considered a baseband frequency. For example, in some embodiments, the baseband circuitry can include circuitry to operate signals having an intermediate frequency, which is between a baseband frequency and a frequency shifted.

[0104] The RF circuitry 710 can enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry can include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. In various embodiments, the RF circuitry 710 can include circuitry to operate with signals that are not strictly considered as being in a radio frequency. For example, in some embodiments, the RF circuitry can include circuitry to operate with signals having intermediate frequency.

[0105] In various embodiments, the transmitter circuitry, control circuitry, or receiver circuitry discussed above with respect to a UE, eNB, or gNB can be embodied in whole or in part in one or more of the RF circuitry, baseband circuitry, and / or processing unit. As used herein, "circuitry" can refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and / or a memory (shared, dedicated, or group) that executes one or more software or firmware programs, a combinational logic circuit, and / or other suitable hardware components that provide the described functionality. In some embodiments, the electronic device circuitry can be implemented in, or functions

[0106] The memory / storage 740 can be used to load and store data and / or instructions, e.g., for the system described above. The memory / storage 740 of one embodiment can include any combination of suitable volatile memory, such as dynamic random access memory (DRAM), and / or non-volatile memory, such as flash memory. In various embodiments, the I / O interface 780 can include one or more user interfaces to enable a user to interact with the system described above and / or one or more peripheral interfaces to enable peripheral component interaction with the system described above. The user interface can include, without limitation, a physical keyboard or keypad, a touchpad, a speaker, a microphone, etc. The peripheral component interface can include, without limitation, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, and a power supply interface.

[0107] In various implementations, the aforementioned sensors 770 can include one or more sensing devices to determine environmental conditions and / or location information related to the aforementioned system. In some implementations, the aforementioned sensors can include, but are not limited to, a gyroscope sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit. The aforementioned positioning unit can also be part of, or interact with, a baseband circuitry and / or a radio frequency circuitry to communicate with components of a positioning network, such as global positioning system (GPS) satellites. In various implementations, the aforementioned display 750 can include one display, such as a liquid crystal display, and a touch screen display. In various implementations, the aforementioned system 700 can be a mobile computing device, such as, but not limited to, a notebook computer, a tablet computer, a netbook, an Ultrabook, a smartphone, and the like. In various implementations, the system can have more or less components, and / or different architectures. Where appropriate, the methods described herein can be implemented as computer programs. The computer program can be stored on a storage medium, such as a non-transitory storage medium.

[0108] Embodiments of the present application are combinations of techniques / processes that can be adopted in 3GPP specifications to create a final product.

[0109] Those skilled in the art understand that each unit, algorithm and step described and disclosed in the embodiments of the present application is implemented using a combination of electronic hardware or software of a computer and electronic hardware. Whether these functions are executed in hardware or software depends on the conditions of application and design requirements of the technical solution. Those skilled in the art can use different ways to implement the functions of each specific application, and such implementation should not exceed the scope of the present application. Those skilled in the art can understand that, since the working processes of the systems, devices and units in the above embodiments are basically the same, reference can be made to the working processes of the systems, devices and units in the above embodiments. For the purpose of description and simplification, these working processes will not be described in detail.

[0110] It can be understood that the systems, devices and methods disclosed in the embodiments of the present application can be implemented in other ways. The above embodiments are only illustrative. The division of the above-mentioned units is only based on logical function division, and other division methods can also be used in implementation. It is possible that multiple units or components are combined or integrated into another system. It is also possible that some features are omitted or skipped. On the other hand, the mutual coupling, direct coupling or communication coupling described or discussed above is achieved by some ports, devices or units, whether indirectly or through electronic, mechanical or other kinds of communication to achieve coupling.

[0111] The units mentioned above can be physically separated or not physically separated components for explanation. The units mentioned above can be physical units or not physical units, that is, can be arranged in one place or distributed on multiple network units. Some of the above-mentioned units or all of the above-mentioned units can be used according to the purpose of the embodiment. In addition, each functional unit in each embodiment can be integrated into one processing unit, or physically independent, or integrated into a processing unit with two or more units.

[0112] If the software functional unit is implemented as a product for use and sale, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solutions proposed by the present application can be implemented as a software product in a basic key part or part. Alternatively, part of the technical plan beneficial to the prior art can be implemented as a software product. The software product in the computer is stored in a storage medium, including a plurality of commands for a computing device (such as a personal computer, a server, or a network device) to execute all or part of the steps disclosed in the embodiments of the present application. The storage medium includes a USB disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a floppy disk, or other types of media capable of storing program codes.

[0113] The present application provides a method related to the intra-UE multiplexing for traffic with different priorities. The current intra-UE multiplexing in the UE only supports prioritizing high priority traffic to drop low priority signals and channels. The intra-UE multiplexing of UL signals / channels with different priorities can improve the system efficiency.

[0114] Although the present content has been described in conjunction with embodiments that are considered to be the most practical and preferred, it is understood that the present content is not limited to the disclosed embodiments, but is intended to cover various arrangements made without departing from the scope of the appended claims, which are interpreted in the broadest sense.

Claims

1. A method of multiplexing within a user equipment (UE), executable in a user equipment (UE), comprising: identifying a set of overlapping uplink transmissions in a time resource unit, wherein the set of overlapping uplink transmissions comprises a first high priority uplink transmission of a high priority traffic type and a first low priority uplink transmission of a low priority traffic type; and enabling multiplexing of the first high priority uplink transmission and the first low priority uplink transmission in the time resource unit in response to a downlink control information (DCI) signal or a radio resource control (RRC) signal; wherein the first high priority uplink transmission of the high priority traffic type has a number of uplink control information (UCI) bits equal to a first total number of bits, wherein the first total number of bits is a sum of a total number of high priority hybrid automatic repeat request acknowledgment (HARQ-ACK) information bits, scheduling request (SR) bits and high priority channel state information (CSI) bits; the first low priority uplink transmission of the low priority traffic type has a number of UCI bits equal to a second total number of bits, wherein the second total number of bits is a sum of a total number of low priority HARQ-ACK information bits, SR bits and CSI bits; a total number of UCI bits is a sum of the number of UCI bits of the first high priority uplink transmission and the number of UCI bits of the first low priority uplink transmission; and a physical uplink control channel (PUCCH) resource for multiplexing is based on the total number of UCI bits. The time resource unit is a slot.

2. The method of claim 1, wherein, The first multiplexing time condition for the high priority traffic type comprises a first processing time obtained from a maximum value among a plurality of processing time values of a plurality of uplink transmissions of the high priority traffic type in the set of overlapping uplink transmissions in the time resource unit.

3. The method of claim 1, wherein, The first multiplexing time condition requires that a first symbol of a high priority earliest uplink transmission among the plurality of uplink transmissions of the high priority traffic type in the set of overlapping uplink transmissions is not before a symbol with a cyclic prefix (CP), but after a last symbol of a high priority downlink transmission associated with the high priority earliest uplink transmission, the symbol with the cyclic prefix starts after the first processing time.

4. The method of claim 3, wherein, ​ 5. The method of claim 4, wherein, The high-priority earliest uplink transmission is a hybrid automatic repeat request (HARQ) feedback signal of the high-priority downlink transmission.

6. The method of claim 4, wherein, The high-priority earliest uplink transmission is a physical uplink shared channel (PUSCH) scheduled by the high-priority downlink transmission.

7. The method of claim 1, wherein, The second multiplexing time condition for the low-priority traffic type comprises a second processing time obtained from a maximum value among a plurality of processing time values of a plurality of uplink transmissions of the low-priority traffic type in the set of overlapping uplink transmissions in the time resource unit.

8. The method of claim 7, wherein, The second multiplexing time condition requires that a first symbol of a low-priority earliest uplink transmission among the plurality of uplink transmissions of the low-priority traffic type in the set of overlapping uplink transmissions is not before a symbol with cyclic prefix (CP) but after a last symbol of a low-priority downlink transmission associated with the low-priority earliest uplink transmission, the symbol with cyclic prefix starts after the second processing time.

9. The method of claim 8, wherein, The low-priority earliest uplink transmission is a hybrid automatic repeat request (HARQ) feedback signal of the low-priority downlink transmission.

10. The method of claim 8, wherein, The low-priority earliest uplink transmission is a physical uplink shared channel (PUSCH) scheduled by the low-priority downlink transmission.

11. The method of claim 1, further comprising: transmitting a sequence of uplink control information (UCI) bits representing a first high-priority uplink transmission of the high-priority traffic type and a first low-priority uplink transmission of the low-priority traffic type, wherein bits in the sequence of UCI bits representing the first high-priority uplink transmission of the high-priority traffic type are placed before bits in the sequence of UCI bits representing the first low-priority uplink transmission of the low-priority traffic type with respect to a UCI type of the first high-priority uplink transmission and a UCI type of the first low-priority uplink transmission.

12. The method of claim 1, further comprising: transmitting a sequence of uplink control information (UCI) bits for a first high priority uplink transmission representing the high priority traffic type and a first low priority uplink transmission representing the low priority traffic type, wherein bits in the sequence of UCI bits for the first high priority uplink transmission representing the high priority traffic type precede bits in the sequence of UCI bits for the first low priority uplink transmission representing the low priority traffic type regardless of a UCI type for the first high priority uplink transmission and a UCI type for the first low priority uplink transmission.

13. The method of claim 1, further comprising: transmitting a sequence of uplink control information (UCI) bits for a first high priority uplink transmission representing the high priority traffic type and a first low priority uplink transmission representing the low priority traffic type, wherein bits in the sequence of UCI bits representing HARQ feedback for a sub-slot based downlink transmission precede bits in the sequence of UCI bits representing HARQ feedback for a slot based downlink transmission.

14. The method of claim 1, further comprising: determining a cancellation time point from the first high priority uplink transmission and the first low priority uplink transmission, wherein the cancellation time point specifies a time position at which at least a portion of the first low priority uplink transmission overlapping the first high priority uplink transmission is dropped when multiplexing is not enabled; and when a high priority downlink transmission containing downlink control information is successfully received, deferring the first low priority uplink transmission such that the first low priority uplink transmission is multiplexed with a subsequent high priority uplink transmission, the downlink control information scheduling the subsequent high priority uplink transmission before a threshold time range from the cancellation time point.

15. The method of claim 1, wherein, the set of overlapping uplink transmissions in the time resource unit further includes a second low priority uplink transmission of the low priority traffic type, the method further comprising: when the first and second low priority uplink transmissions are not allowed to be multiplexed with the first high priority uplink transmission, dropping one of the first low priority uplink transmission and the second low priority uplink transmission based on a UCI type of the first and second low priority uplink transmissions.

16. The method of claim 1, wherein, the set of overlapping uplink transmissions in the time resource unit further includes a second high priority uplink transmission of the high priority traffic type, the method further comprising: when the first and second high priority uplink transmissions are not allowed to be multiplexed with the first low priority uplink transmission, dropping the first low priority uplink transmission based on a comparison of the low priority traffic type and the high priority traffic type.

17. The method of claim 1, wherein, further comprising: If a multiplexing condition is satisfied to multiplex uplink transmissions with different priorities, a multiplexing procedure is performed on a HARQ-ACK transmission with a high priority and a PUSCH with a low priority, a beta offset is indicated to the user equipment to determine a number of radio resources in the PUSCH for multiplexing the HARQ-ACK.

18. The method of claim 1, wherein, Also included are: If a multiplexing condition is satisfied to multiplex uplink transmissions with different priorities, a multiplexing procedure is performed on a HARQ-ACK transmission with a low priority and a PUSCH with a high priority, a beta offset is indicated to the user equipment to determine a number of radio resources in the PUSCH for multiplexing the HARQ-ACK.

19. The method of claim 1, wherein, Responsive to a condition that discarding low priority uplink transmissions over a period of time constitutes a predetermined ratio of all low priority uplink transmissions to enable the multiplexing.

20. A method of multiplexing within a user equipment (UE), executable in a wireless node device, comprising: transmitting a control signal to enable a multiplexing mode to multiplex a set of overlapping uplink transmissions in a time resource unit at a user equipment (UE) side; when the set of overlapping uplink transmissions includes a first high priority uplink transmission of a high priority traffic type and a first low priority uplink transmission of a low priority traffic type, allowing the user equipment (UE) to acquire a first multiplexing time condition of the high priority traffic type and a second multiplexing time condition of the low priority traffic type in the multiplexing mode; and when the first high priority uplink transmission satisfies the first multiplexing time condition and the first low priority uplink transmission satisfies the second multiplexing time condition, allowing the user equipment (UE) to multiplex the first high priority uplink transmission and the first low priority uplink transmission in the time resource unit in the multiplexing mode; wherein the first multiplexing time condition requires a first symbol of a high priority earliest uplink transmission among a plurality of uplink transmissions of the high priority traffic type in the set of overlapping uplink transmissions is not before a symbol with a cyclic prefix (CP) but after a last symbol of a high priority downlink transmission associated with the high priority earliest uplink transmission, the symbol with the cyclic prefix starts after a first processing time; wherein the second multiplexing time condition requires a first symbol of a low priority earliest uplink transmission among a plurality of uplink transmissions of the low priority traffic type in the set of overlapping uplink transmissions is not before a symbol with a cyclic prefix (CP) but after a last symbol of a low priority downlink transmission associated with the low priority earliest uplink transmission, the symbol with the cyclic prefix starts after a second processing time.

21. The method of claim 20, wherein, The control signal comprises a downlink control information (DCI) signal or a radio resource control (RRC) signal.

22. The method of claim 20, wherein, The time resource unit is one slot.

23. The method of claim 20, wherein, The first multiplexing time condition of the high priority service type comprises the first processing time obtained from a maximum value among a plurality of processing time values of a plurality of uplink transmissions of the high priority service type in the set of overlapping uplink transmissions in the time resource unit.

24. The method of claim 20, wherein, The high priority earliest uplink transmission is a hybrid automatic repeat request (HARQ) feedback signal of the high priority downlink transmission.

25. The method of claim 20, wherein, The high priority earliest uplink transmission is a physical uplink shared channel (PUSCH) scheduled by the high priority downlink transmission.

26. The method of claim 23, wherein, The second multiplexing time condition of the low priority service type comprises the second processing time obtained from a maximum value among a plurality of processing time values of a plurality of uplink transmissions of the low priority service type in the set of overlapping uplink transmissions in the time resource unit.

27. The method of claim 20, wherein, The low priority earliest uplink transmission is a hybrid automatic repeat request (HARQ) feedback signal of the low priority downlink transmission.

28. The method of claim 20, wherein, The low priority earliest uplink transmission is a physical uplink shared channel (PUSCH) scheduled by the low priority downlink transmission.

29. The method of claim 20, further comprising: receiving a sequence of uplink control information (UCI) bits representing a first high priority uplink transmission of the high priority service type and a first low priority uplink transmission of the low priority service type, wherein bits in the sequence of UCI bits representing the first high priority uplink transmission of the high priority service type precede bits in the sequence of UCI bits representing the first low priority uplink transmission of the low priority service type with respect to a UCI type of the first high priority uplink transmission and a UCI type of the first low priority uplink transmission.

30. The method of claim 20, further comprising: receiving a sequence of uplink control information (UCI) bits for a first high priority uplink transmission representing the high priority traffic type and a first low priority uplink transmission representing the low priority traffic type, wherein bits in the sequence of UCI bits representing HARQ feedback for the first high priority uplink transmission precede bits in the sequence of UCI bits representing HARQ feedback for the first low priority uplink transmission regardless of a UCI type for the first high priority uplink transmission and a UCI type for the first low priority uplink transmission.

31. The method of claim 20, further comprising: receiving a sequence of uplink control information (UCI) bits for a first high priority uplink transmission representing the high priority traffic type and a first low priority uplink transmission representing the low priority traffic type, wherein bits in the sequence of UCI bits representing HARQ feedback for a sub-slot based downlink transmission precede bits in the sequence of UCI bits representing HARQ feedback for a slot based downlink transmission.

32. The method of claim 20, wherein, transmitting the control signal to enable the multiplexing mode in response to receiving a request for the multiplexing mode from the user equipment (UE).

33. The method of claim 20, wherein, transmitting the control signal to enable the multiplexing mode when a number of enhanced mobile broadband (eMBB) retransmissions exceeds a predetermined number of retransmissions.

34. The method of claim 20, wherein, transmitting the control signal to enable the multiplexing mode for eMBB traffic having a transport block (TB) size greater than a predetermined TB size.

35. The method of claim 20, wherein, transmitting the control signal to enable the multiplexing mode in response to a channel quality condition being below a predetermined channel quality level.

36. A user equipment comprising: a transceiver; and a processor coupled to the transceiver and configured to perform steps comprising: identifying a set of overlapping uplink transmissions in a time resource unit, wherein the set of overlapping uplink transmissions includes a first high priority uplink transmission of a high priority traffic type and a first low priority uplink transmission of a low priority traffic type; and enabling multiplexing of the first high priority uplink transmission and the first low priority uplink transmission in the time resource unit in response to a downlink control information (DCI) signal or a radio resource control (RRC) signal; and The first high-priority uplink transmission of the high-priority traffic type has a quantity of uplink control information (UCI) bits that is a first total number of bits, wherein the first total number of bits is a sum of a total number of high-priority hybrid automatic repeat request acknowledgment (HARQ-ACK) information bits, scheduling request (SR) bits, and channel state information (CSI) bits; The first low-priority uplink transmission of the low-priority traffic type has a quantity of UCI bits that is a second total number of bits, wherein the second total number of bits is a sum of a total number of low-priority HARQ-ACK information bits, SR bits, and CSI bits; The UCI total number of bits is a sum of the UCI bits of the first high-priority uplink transmission and the UCI bits of the first low-priority uplink transmission; and The physical uplink control channel (PUCCH) resource for multiplexing is based on the UCI total number of bits.

37. The user equipment of claim 36, wherein, The time resource unit is one slot.

38. The user equipment of claim 36, wherein, The first multiplexing time condition for the high-priority traffic type includes a first processing time obtained from a maximum value of a plurality of processing time values of a plurality of uplink transmissions of the high-priority traffic type in the set of overlapping uplink transmissions in the time resource unit.

39. The user equipment of claim 38, wherein, The first multiplexing time condition requires that a first symbol of a high-priority earliest uplink transmission among the plurality of uplink transmissions of the high-priority traffic type in the set of overlapping uplink transmissions is not before a symbol with a cyclic prefix (CP) and is after a last symbol of a high-priority downlink transmission associated with the high-priority earliest uplink transmission, the symbol with the CP starting after the first processing time.

40. The user equipment of claim 39, wherein, The high-priority earliest uplink transmission is a hybrid automatic repeat request (HARQ) feedback signal of the high-priority downlink transmission.

41. The user equipment of claim 39, wherein, The high-priority earliest uplink transmission is a physical uplink shared channel (PUSCH) scheduled by the high-priority downlink transmission.

42. The user equipment of claim 36, wherein, The second multiplexing time condition for the low-priority traffic type includes a second processing time obtained from a maximum value of a plurality of processing time values of a plurality of uplink transmissions of the low-priority traffic type in the set of overlapping uplink transmissions in the time resource unit.

43. The user equipment of claim 42, wherein, The second multiplexing time condition requires that a first symbol of a low priority earliest uplink transmission among a plurality of uplink transmissions of the low priority traffic type in the set of overlapping uplink transmissions is not preceded by a symbol with cyclic prefix (CP) but is followed by a last symbol of a low priority downlink transmission associated with the low priority earliest uplink transmission, the symbol with cyclic prefix starting after the second processing time.

44. The user equipment of claim 43, wherein, The low priority earliest uplink transmission is a hybrid automatic repeat request (HARQ) feedback signal of the low priority downlink transmission.

45. The user equipment of claim 43, wherein, The low priority earliest uplink transmission is a physical uplink shared channel (PUSCH) scheduled by the low priority downlink transmission.

46. The user equipment of claim 36, wherein, The processor further performs the following steps: transmitting a sequence of uplink control information (UCI) bits representing a first high priority uplink transmission of the high priority traffic type and a first low priority uplink transmission of the low priority traffic type, wherein bits in the sequence of UCI bits representing the first high priority uplink transmission of the high priority traffic type are placed before bits in the sequence of UCI bits representing the first low priority uplink transmission of the low priority traffic type regardless of UCI types of the first high priority uplink transmission and the first low priority uplink transmission. 47.The user equipment of claim 36, wherein, The processor further performs the following steps: transmitting a sequence of uplink control information (UCI) bits representing a first high priority uplink transmission of the high priority traffic type and a first low priority uplink transmission of the low priority traffic type, wherein bits in the sequence of UCI bits representing the first high priority uplink transmission of the high priority traffic type are placed before bits in the sequence of UCI bits representing the first low priority uplink transmission of the low priority traffic type regardless of UCI types of the first high priority uplink transmission and the first low priority uplink transmission. 48.The user equipment of claim 36, wherein, The processor further performs the following steps: transmitting a sequence of uplink control information (UCI) bits representing a first high priority uplink transmission of the high priority traffic type and a first low priority uplink transmission of the low priority traffic type, wherein bits in the sequence of UCI bits representing HARQ feedback of a sub-slot based downlink transmission are placed before bits in the sequence of UCI bits representing HARQ feedback of a slot based downlink transmission. 49.The user equipment of claim 36, wherein, The processor further performs the following steps: determining a cancellation time point based on the first high priority uplink transmission and the first low priority uplink transmission, wherein the cancellation time point specifies a time position at which at least a portion of the first low priority uplink transmission overlapping with the first high priority uplink transmission is dropped when multiplexing is not enabled; and when a high priority downlink transmission containing downlink control information is successfully received, deferring the first low priority uplink transmission so that the first low priority uplink transmission is multiplexed with a subsequent high priority uplink transmission, the downlink control information scheduling the subsequent high priority uplink transmission before a threshold time range from the cancellation time point.

50. The user equipment of claim 36, wherein, the set of overlapping uplink transmissions in the time resource unit further comprises a second low priority uplink transmission of the low priority traffic type, and the steps performed by the processor further comprise: when multiplexing the first and second low priority uplink transmissions with the first high priority uplink transmission is not allowed, dropping one of the first low priority uplink transmission and the second low priority uplink transmission based on a UCI type of the first and second low priority uplink transmissions.

51. The user equipment of claim 36, wherein, the set of overlapping uplink transmissions in the time resource unit further comprises a second high priority uplink transmission of the high priority traffic type, and the steps performed by the processor further comprise: when multiplexing the first and second high priority uplink transmissions with the first low priority uplink transmission is not allowed, dropping the first low priority uplink transmission based on a comparison between the low priority traffic type and the high priority traffic type.

52. The user equipment of claim 36, wherein, further comprising: if a multiplexing condition is satisfied to multiplex uplink transmissions with different priorities, performing a multiplexing procedure on a HARQ-ACK transmission with a high priority and a PUSCH with a low priority, and indicating a beta offset to the user equipment to determine a number of radio resources in the PUSCH for multiplexing the HARQ-ACK.

53. The user equipment of claim 36, wherein, further comprising: if a multiplexing condition is satisfied to multiplex uplink transmissions with different priorities, performing a multiplexing procedure on a HARQ-ACK transmission with a low priority and a PUSCH with a high priority, and indicating a beta offset to the user equipment to determine a number of radio resources in the PUSCH for multiplexing the HARQ-ACK.

54. The user equipment of claim 36, wherein, in response to a condition that dropping low priority uplink transmissions over a period of time constitutes a predetermined ratio of all low priority uplink transmissions to enable the multiplexing.

55. A wireless node device, comprising: a transceiver; and a processor connected with the transceiver and configured to perform steps comprising: transmitting a control signal to enable a multiplexing mode to multiplex a set of overlapping uplink transmissions in a time resource unit at a user equipment (UE) side; allow the user equipment (UE) to acquire a first multiplexing time condition of the high priority service type and a second multiplexing time condition of the low priority service type in the multiplexing mode when the set of overlapping uplink transmissions includes a first high priority uplink transmission of the high priority service type and a first low priority uplink transmission of the low priority service type; and allow the user equipment (UE) to multiplex the first high priority uplink transmission and the first low priority uplink transmission in the time resource unit in the multiplexing mode when the first high priority uplink transmission satisfies the first multiplexing time condition and the first low priority uplink transmission satisfies the second multiplexing time condition; wherein the first multiplexing time condition requires a first symbol of a high priority earliest uplink transmission among a plurality of uplink transmissions of the high priority service type in the set of overlapping uplink transmissions is not before a symbol with cyclic prefix (CP) but after a last symbol of a high priority downlink transmission associated with the high priority earliest uplink transmission, the symbol with cyclic prefix starts after a first processing time; wherein the second multiplexing time condition requires a first symbol of a low priority earliest uplink transmission among a plurality of uplink transmissions of the low priority service type in the set of overlapping uplink transmissions is not before a symbol with cyclic prefix (CP) but after a last symbol of a low priority downlink transmission associated with the low priority earliest uplink transmission, the symbol with cyclic prefix starts after a second processing time.

56. The wireless node device of claim 55, wherein, The control signal includes a downlink control information (DCI) signal or a radio resource control (RRC) signal.

57. The wireless node device of claim 55, wherein, The time resource unit is a slot.

58. The wireless node device of claim 55, wherein, The first multiplexing time condition of the high priority service type includes the first processing time, which is obtained from a maximum value among a plurality of processing time values of the plurality of uplink transmissions of the high priority service type in the set of overlapping uplink transmissions in the time resource unit.

59. The wireless node device of claim 55, wherein, The high priority earliest uplink transmission is a hybrid automatic repeat request (HARQ) feedback signal of the high priority downlink transmission.

60. The wireless node device of claim 55, wherein, The high priority earliest uplink transmission is a physical uplink shared channel (PUSCH) scheduled by the high priority downlink transmission.

61. The wireless node device of claim 58, wherein, The second multiplexing time condition for the low priority traffic type comprises the second processing time obtained from a maximum value among a plurality of processing time values for a plurality of uplink transmissions of the low priority traffic type in the set of overlapping uplink transmissions in the time resource unit.

62. The wireless node device of claim 55, wherein, The low priority earliest uplink transmission is a hybrid automatic repeat request (HARQ) feedback signal for the low priority downlink transmission.

63. The wireless node device of claim 55, wherein, The low priority earliest uplink transmission is a physical uplink shared channel (PUSCH) scheduled by the low priority downlink transmission.

64. The wireless node device of claim 55, wherein, The processor further performs the following steps: receiving a sequence of uplink control information (UCI) bits for a first high priority uplink transmission of the high priority traffic type and a first low priority uplink transmission of the low priority traffic type, wherein bits in the sequence of UCI bits for the first high priority uplink transmission of the high priority traffic type are placed before bits in the sequence of UCI bits for the first low priority uplink transmission of the low priority traffic type, irrespective of UCI types for the first high priority uplink transmission and the first low priority uplink transmission.

65. The wireless node device of claim 55, wherein, The processor further performs the following steps: receiving a sequence of uplink control information (UCI) bits for a first high priority uplink transmission of the high priority traffic type and a first low priority uplink transmission of the low priority traffic type, wherein bits in the sequence of UCI bits for the first high priority uplink transmission of the high priority traffic type are placed before bits in the sequence of UCI bits for the first low priority uplink transmission of the low priority traffic type, irrespective of UCI types for the first high priority uplink transmission and the first low priority uplink transmission.

66. The wireless node device of claim 55, wherein, The processor further performs the following steps: receiving a sequence of uplink control information (UCI) bits for a first high priority uplink transmission of the high priority traffic type and a first low priority uplink transmission of the low priority traffic type, wherein bits in the sequence of UCI bits for HARQ feedback for a sub-slot based downlink transmission are placed before bits in the sequence of UCI bits for HARQ feedback for a slot based downlink transmission.

67. The wireless node device of claim 55, wherein, In response to receiving a request for the multiplexing pattern from the user equipment (UE), the transmitting the control signal to enable the multiplexing pattern is performed.

68. The wireless node device of claim 55, wherein, The control signal is transmitted to enable the multiplexing mode when it is detected that the number of retransmissions for enhanced mobile broadband (eMBB) exceeds a predetermined number.

69. The wireless node device of claim 55, wherein, The control signal is transmitted to enable the multiplexing mode for eMBB traffic with a transport block (TB) size greater than a predetermined TB size.

70. The wireless node device of claim 55, wherein, The control signal is transmitted to enable the multiplexing mode in response to a channel quality condition that is below a predetermined channel quality level.

71. A chip comprising: a processor configured to call and run a computer program stored in a memory to cause a device in which the chip is installed to perform the method of any one of claims 1 to 19.

72. A chip comprising: a processor configured to call and run a computer program stored in a memory to cause a device in which the chip is installed to perform the method of any one of claims 20 to 35.

73. A computer readable storage medium having stored therein a computer program, wherein the computer program causes a computer to perform the method of any one of claims 1 to 19.

74. A computer readable storage medium having stored therein a computer program, wherein the computer program causes a computer to perform the method of any one of claims 20 to 35.

Images