Information transmission method and device, terminal and network side equipment

Abstract

The invention discloses an information transmission method and device, a terminal and network side equipment, and belongs to the technical field of communication, and the information transmission method comprises the steps that the terminal sends terminal capability information to the network side equipment, the terminal capability information is used for indicating whether the terminal supports simultaneous transmission of a physical uplink control channel (PUCCH) and a physical uplink shared channel (PUSCH) with the same priority on different cells under carrier aggregation.

Description

Technical Field

[0001] The present application belongs to the field of communication technology, and specifically relates to an information transmission method, device, terminal and network side equipment. Background Art

[0002] New Radio (NR) supports the multiplexing of Physical Uplink Control Channel (PUCCH) and PUCCH or PUCCH and Physical Uplink Shared Channel (PUSCH) of the same or different priorities, supports the prioritization of PUCCH and PUCCH or PUCCH and PUSCH of different priorities, and supports the simultaneous transmission of PUCCH and PUSCH of different priorities on different serving cells in inter-band, but there are some restrictions on the scheduling of PUCCH and PUSCH. Such scheduling restrictions will cause serious system throughput loss in actual network deployment. Summary of the invention

[0003] Embodiments of the present application provide an information transmission method, apparatus, terminal, and network-side equipment to reduce the problem of system throughput loss caused by scheduling restrictions.

[0004] In a first aspect, a method for transmitting information is provided, the method comprising:

[0005] The terminal sends terminal capability information to a network side device, where the terminal capability information is used to indicate whether the terminal supports simultaneous transmission of physical uplink control channels PUCCH and physical uplink shared channels PUSCH of the same priority on different cells under carrier aggregation.

[0006] In a second aspect, an information transmission device is provided, which is applied to a terminal and includes:

[0007] The first sending module is used to send terminal capability information to a network side device, where the terminal capability information is used to indicate whether the terminal supports simultaneous transmission of physical uplink control channels PUCCH and physical uplink shared channels PUSCH of the same priority on different cells under carrier aggregation.

[0008] In a third aspect, an information transmission method is provided, the method comprising:

[0009] The network side device receives terminal capability information sent by the terminal, where the terminal capability information is used to indicate whether the terminal supports transmission of physical uplink control channels PUCCH and physical uplink shared channels PUSCH of the same priority on different cells under carrier aggregation.

[0010] In a fourth aspect, an information transmission device is provided, which is applied to a network side device, including:

[0011] The first receiving module is used to receive terminal capability information sent by the terminal, where the terminal capability information is used to indicate whether the terminal supports transmission of physical uplink control channels PUCCH and physical uplink shared channels PUSCH of the same priority on different cells under carrier aggregation.

[0012] In a fifth aspect, a terminal is provided, comprising a processor and a memory, wherein the memory stores a program or instruction that can be executed on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented.

[0013] In the sixth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the communication interface is used to send terminal capability information to a network side device, and the terminal capability information is used to indicate whether the terminal supports the simultaneous transmission of physical uplink control channels PUCCH and physical uplink shared channels PUSCH of the same priority on different cells under carrier aggregation.

[0014] In the seventh aspect, a network side device is provided, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the third aspect are implemented.

[0015] In the eighth aspect, a network side device is provided, including a processor and a communication interface, wherein the communication interface is used to receive terminal capability information sent by a terminal, and the terminal capability information is used to indicate whether the terminal supports the transmission of physical uplink control channels PUCCH and physical uplink shared channels PUSCH of the same priority on different cells under carrier aggregation.

[0016] In a ninth aspect, a communication system is provided, comprising: a terminal and a network side device, wherein the terminal can be used to execute the steps of the method described in the first aspect, and the network side device can be used to execute the steps of the method described in the third aspect.

[0017] In a tenth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect or the third aspect are implemented.

[0018] In the eleventh aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the steps of the method described in the first aspect or the third aspect.

[0019] In the twelfth aspect, a computer program / program product is provided, wherein the computer program / program product is stored in a storage medium and is executed by at least one processor to implement the steps of the method described in the first aspect or the third aspect.

[0020] In an embodiment of the present application, the terminal capability information is indicated to the network side device so that the network side device can know whether the terminal supports the simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under carrier aggregation, so as to perform scheduling based on the indication of the terminal side, thereby avoiding the loss of system throughput caused by scheduling restrictions as much as possible. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1 is a block diagram of a wireless communication system to which the embodiments of the present application can be applied;

[0022] Figure 2 This is one of the flowcharts of the information transmission method according to the embodiment of the present application;

[0023] Figure 3 is a schematic diagram of existing scheduling constraints;

[0024] Figure 4 This is one of the transmission schematic diagrams of the embodiment of the present application;

[0025] Figure 5 This is the second transmission schematic diagram of the embodiment of the present application;

[0026] Figure 6 This is the third transmission schematic diagram of the embodiment of the present application;

[0027] Figure 7 This is the second flow chart of the information transmission method according to the embodiment of the present application;

[0028] Figure 8 It is one of the module schematic diagrams of the information transmission device according to the embodiment of the present application;

[0029] Fig. 9 is a schematic diagram of the structure of a terminal in an embodiment of the present application;

[0030] Fig.10 This is the second module schematic diagram of the information transmission device according to the embodiment of the present application;

[0031] Fig.11 is a schematic diagram of the structure of a network side device in an embodiment of the present application;

[0032] Fig.12 It is a schematic diagram of the structure of the communication device of an embodiment of the present application. DETAILED DESCRIPTION

[0033] The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field belong to the scope of protection of this application.

[0034] The terms "first", "second", etc. of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of one type, and the number of objects is not limited, for example, the first object can be one or more. In addition, "or" in the present application represents at least one of the connected objects. For example, "A or B" covers three schemes, namely, Scheme 1: including A but not including B; Scheme 2: including B but not including A; Scheme 3: including both A and B. The character " / " generally indicates that the objects associated with each other are in an "or" relationship.

[0035] The term "indication" in this application can be a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, operations to be performed, or request results in the sent indication; an indirect indication can be understood as the receiver determining the corresponding information according to the indication sent by the sender, or making a judgment and determining the operation to be performed or the request result according to the judgment result.

[0036] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used for the systems and radio technologies mentioned above as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following descriptions, but these technologies can also be applied to systems other than NR systems, such as the 6th generation (6 th Generation, 6G) communication system.

[0037] Figure 1A block diagram of a wireless communication system applicable to an embodiment of the present application is shown. The wireless communication system includes a terminal 11 and a network side device 12. Among them, the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (Ultra-mobile Personal Computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), an augmented reality (Augmented Reality, AR), a virtual reality (Virtual Reality, VR) device, a robot, a wearable device (Wearable Device), an aircraft (flight vehicle), a vehicle-mounted device (Vehicle User Equipment, VUE), a ship-mounted device, a pedestrian terminal (Pedestrian User Equipment, PUE), a smart home (home appliances with wireless communication functions, such as refrigerators, televisions, washing machines or furniture, etc.), a game console, a personal computer (Personal Computer, PC), a teller machine or a self-service machine and other terminal side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be referred to as a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (Wireless Local Area Network, WLAN) access point (Access Point, AP) or a wireless fidelity (Wireless Fidelity, WiFi) node, etc.Among them, the base station may be referred to as a Node B (NB), an evolved Node B (eNB), a next generation Node B (gNB), a New Radio Node B (NR Node B), an access point, a Relay Base Station (RBS), a Serving Base Station (SBS), a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a Home Node B (HNB), a Home Evolved Node B, a Transmission Reception Point (TRP) or other appropriate terms in the field. As long as the same technical effect is achieved, the base station is not limited to specific technical terms. It should be noted that in the embodiments of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0038] The following first describes the related technologies of the embodiments of the present application.

[0039] Compared with previous mobile communication systems, the future 5G mobile communication system needs to adapt to more diverse scenarios and business requirements. The main scenarios of 5G include Enhanced Mobile Broadband (eMBB), Ultra Reliable Low Latency Communication (URLLC), and Massive Machine Type Communication (mMTC). These scenarios put forward requirements for high reliability, low latency, large bandwidth, and wide coverage for the system. Some user equipment (UE) may support different services. For example, UE supports both URLLC and high-capacity and high-rate eMBB services. Since different channels in the New Radio (NR) system can have different starting symbols and lengths, there will be time domain overlap of transmission resources. Generally, in order to maintain the uplink single carrier characteristics, when there are multiple overlapping physical uplink control channels (PUCCH) in a time slot, the single carrier characteristics of the UE will be destroyed, and the difference in transmit power will cause the channel estimation performance to deteriorate. This situation is usually regarded as a conflict, and a corresponding conflict resolution method needs to be designed to merge or discard some information.

[0040] 1.1 Multiplexing of PUCCH and PUCCH or PUCCH and Physical Uplink Shared Channel (PUSCH) in the first case

[0041] Uplink Control Information (UCI) is mainly transmitted on the uplink control channel (e.g., PUCCH). Uplink data is transmitted on the uplink data channel (e.g., PUSCH). Due to flexible configuration or indication of the starting symbol and symbol length, there may be temporal overlap between different PUCCHs or between PUCCH and PUSCH. In principle, PUCCH and PUSCH can be sent at the same time, that is, UCI is retained on PUCCH. However, this will increase the cubic metric of uplink transmission; in addition, if the requirements for out-of-band transmission are to be met at a higher transmit power, and the interval in the frequency domain when PUSCH and PUCCH are transmitted simultaneously is large (PUCCH is generally transmitted at both ends of the frequency band), this will bring challenges to the implementation of radio frequency (RF). Therefore, under normal circumstances, if the PUCCHs that need to transmit UCI are multiplexed when the time domain resources overlap or the PUCCH resources that need to transmit UCI overlap in time with the PUSCH resources, and the base station will ensure that the UCI multiplexing processing time conditions are met when scheduling the PUCCH / PUSCH, UCI will be multiplexed on one PUCCH or UCI and data will be multiplexed on PUSCH to avoid sending different PUCCHs at the same time or avoid sending PUCCH and PUSCH at the same time.

[0042] Currently, the timeline for multiplexing of PUCCH and PUCCH, or PUCCH and PUSCH is defined, that is, the predefined timeline that needs to be met for multiplexing between PUCCHs or multiplexing of UCI on PUSCH. If the scheduling on the network side does not meet the timeline, it is considered as an error case.

[0043] In addition, considering the complexity of multiplexing and coding, NR has some limitations in the multiplexing of PUCCH and PUSCH. For example, when the subcarrier spacing of PUSCH is smaller than the subcarrier spacing of PUCCH (for example, PUSCH 15kHz, PUCCH 30kHz), the terminal does not expect to multiplex the UCI of PUCCH carrying the same type of UCI in multiple time slots on one PUSCH.

[0044] 1.1.1. Processing order of multiplexing between PUCCHs or multiplexing UCI on PUSCH

[0045] In a PUCCH group, there may be overlap between multiple PUCCHs, and a PUCCH may also overlap with multiple PUSCHs. In order to solve the problem of time domain resource overlap between multiple uplink transmission channels, in one case, the NR defines the processing order of UE uplink multiplexing, specifically:

[0046] 1) In a time unit, if there are multiple PUCCHs and at least two PUCCHs overlap with each other, the UE first resolves the overlap between PUCCHs and then obtains at most two non-overlapping PUCCHs;

[0047] 2) For a certain PUCCH outputted in 1), if the PUCCH does not overlap with the PUSCH, the UE transmits the PUCCH. If the PUCCH overlaps with the PUSCH, the UE multiplexes the UCI (excluding the Scheduling Request (SR)) carried by the PUCCH on a certain overlapping PUSCH for transmission according to certain rules. If the PUCCH overlaps with only one PUSCH, the UCI (excluding the SR) is multiplexed on the PUSCH. If the PUCCH overlaps with multiple PUSCHs, the UE selects a PUSCH for multiplexing according to the corresponding rules. The rules are as follows:

[0048] a) First priority: PUSCH with aperiodic channel state information (A-CSI);

[0049] b) Second priority: the earliest PUSCH in the starting time slot (optional step, may not be required);

[0050] c) Third priority: dynamically scheduled PUSCH > configured authorized PUSCH or semi-persistent PUSCH (semiPersistentOnPUSCH);

[0051] d) Fourth priority: PUSCH with smaller serving cell index > PUSCH with larger serving cell index;

[0052] e) Fifth priority: PUSCH with early transmission > PUSCH with late transmission.

[0053] 1.2 Multiplexing and Priority of Uplink Transmission within UE in the Second Case

[0054] In order to support different business requirements, in one case, NR introduces different physical layer priorities (specifically, represented by priority index, priority index = 1 indicates high priority, priority index = 0 indicates low priority), supports the following conflict scenarios, and defines the UE behavior for the following conflict scenarios.

[0055] High Priority (HP) uplink transmission vs. high priority uplink transmission, the UE handles it in the first case;

[0056] Low priority (LP) uplink transmission vs. low priority uplink transmission, the UE handles it in the first case;

[0057] High priority uplink transmission vs. low priority uplink transmission, the UE transmits the high priority uplink transmission and cancels the low priority uplink transmission, and defines the following cancellation timeline.

[0058] Similarly, in order to enable the UE to have sufficient capability / time to cancel the transmission of low-priority PUCCH / PUSCH and transmit high-priority PUCCH / PUSCH, the base station needs to meet certain timeline requirements when scheduling PUCCH / PUSCH. The relevant technology also defines the timeline when PUCCH and PUCCH, or PUCCH and PUSCH are prioritized.

[0059] 1.2.1. Priority processing order between PUCCH or PUCCH and PUSCH

[0060] In a PUCCH group, there may be multiple PUCCHs overlapping each other, and a PUCCH may also overlap with multiple PUSCHs. In addition, PUCCH / PUSCH may have low priority or high priority. In order to solve the problem of time domain resource overlap between multiple uplink transmission channels, in this case, NR defines the order of UE uplink conflict processing, specifically:

[0061] 1) In a time unit, if there are multiple LP PUCCH / PUSCH, the UE first resolves the overlap between low priority PUCCH / PUSCH according to the method of the first case.

[0062] 2) If the LP PUCCH / PUSCH after multiplexing overlaps with the high-priority PUCCH / PUSCH, the UE cancels the overlapping LP PUCCH / PUSCH transmission.

[0063] 3) If there are multiple HP PUCCH / PUSCH, the overlap between high priority PUCCH / PUSCH is first resolved according to the method of the first case.

[0064] 4) If the channel output in 3) collides with the LP PUCCH / PUSCH output in 1), the UE cancels the conflicting LPPUCCH / PUSCH transmission.

[0065] 1.3. Multiplexing between different priorities and simultaneous transmission of PUCCH and PUSCH in the third case

[0066] In order to reduce the impact on low-priority uplink transmission, especially low-priority hybrid automatic repeat request acknowledgement (HARQ-ACK), NR rel-17 supports simultaneous transmission of PUCCCH and PUSCH of different priorities on different serving cells in the inter-band bandwidth. It also supports multiplexing of PUCCH and PUCCH of different priorities or PUCCH and PUSCH of different priorities.

[0067] 1.3.1. Processing order between PUCCH or PUCCH and PUSCH multiplexing

[0068] In a PUCCH group, there may be multiple PUCCHs overlapping each other, and a PUCCH may also overlap with multiple PUSCHs. In addition, PUCCH / PUSCH may have low priority or high priority. In order to solve the problem of time domain resource overlap between multiple uplink transmission channels, in this case, NR defines the order of UE uplink conflict processing, specifically:

[0069] 1) Within a time unit, if there are multiple overlapping PUCCH / PUSCH, the UE first resolves the overlap between PUCCH / PUSCH with the same priority according to the method of the first case.

[0070] 2) The UE resolves the overlap between PUCCHs of different priorities. For PUCCHs of different priorities, the UE supports multiplexing between some types of PUCCHs, such as multiplexing of HARQ-ACK PUCCHs of different priorities, but does not support multiplexing of HARQ-ACK PUCCHs and CSIPUCCHs of different priorities.

[0071] 3) The UE resolves the overlap between PUCCH and PUSCH of different priorities, and supports multiplexing in some scenarios. For example, if the high-priority positive SR PUCCH overlaps with the low-priority PUSCH, the LP PUSCH transmission is discarded; if the HARQ-ACK PUCCH overlaps with PUSCH of different priorities, the UE multiplexes the HARQ-ACK on the PUSCH for transmission (except for individual scenarios, such as the LP HARQ-ACK PUCH overlaps with the HP PUSCH and there is CSI part 2 on the HP PUSCH).

[0072] The schemes for overlapping PUCCH and PUSCH time domain resources supported in the prior art include multiplexing, prioritization, and simultaneous transmission, but there are still some restrictions, such as priority, the number of PUCCHs overlapping with PUSCH, etc. In actual network deployment, for example, in a carrier aggregation (CA) scenario, the primary cell (Pcell) is time division duplex (TDD), the subcarrier spacing (SCS) is 30kHz, and the secondary cell (Scell) is frequency division duplex (FDD), and its SCS is 15kHz; PUCCH is sent in PCell and PUSCH is sent in Scell, then scheduling two PUCCHs carrying HARQ-ACK feedback to overlap with one PUSCH in different time slots is not allowed, and such scheduling restrictions will cause a serious loss of system throughput. One solution is that the base station schedules PUCCH and PUSCH with different priorities and enables simultaneous transmission of PUCCH and PUSCH between different priorities. But this means that the UE must be able to support the indication of the priority of PUCCH / PUSCH through DCI, that is, to couple different technical features. However, the technical feature of DCI indicating different priorities is not such an urgent issue in actual deployment. Another more practical solution is to support simultaneous transmission of PUCCH and PUSCH of the same priority. However, when supporting simultaneous transmission of PUCCH and PUSCH of the same priority, the processing method when the uplink channel overlaps and the interoperability with other features, such as multiplexing / simultaneous transmission of PUCCH and PUSCH of different priorities, need to be considered.

[0073] The information transmission method, apparatus, terminal and network side equipment provided in the embodiments of the present application are described in detail below with reference to the accompanying drawings through some embodiments and their application scenarios.

[0074] like Figure 2 As shown, the embodiment of the present application provides an information transmission method, including:

[0075] Step 201: The terminal sends terminal capability information to a network side device, where the terminal capability information is used to indicate whether the terminal supports simultaneous transmission of a physical uplink control channel (PUCCH) and a physical uplink shared channel (PUSCH) of the same priority on different cells under carrier aggregation.

[0076] It should be noted that by indicating the terminal capability information to the network side device, so that the network side device can know whether the terminal supports the simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under carrier aggregation, and perform scheduling based on the indication of the terminal side, the loss of system throughput caused by scheduling restrictions can be avoided as much as possible.

[0077] Optionally, the terminal supports simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under carrier aggregation, which may include at least one of the following:

[0078] Supports simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under inter-band carrier aggregation;

[0079] Supports simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under intra-band carrier aggregation.

[0080] Optionally, in one implementation, the PUCCH includes hybrid automatic repeat request acknowledgement (HARQ-ACK) information.

[0081] This situation can be understood as the ability to support simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under carrier aggregation is only for HARQ-ACK transmission, that is, the PUCCH that can be transmitted simultaneously with PUSCH is the PUCCH including HARQ-ACK information. If the PUCCH overlapping with the PUSCH does not contain HARQ-ACK information (for example, the PUCCH only contains channel state information (CSI) or scheduling request (SR)), the simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under carrier aggregation is not supported.

[0082] Optionally, in one implementation, the terminal supports simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under carrier aggregation.

[0083] Optionally, this situation can be understood as the premise that the ability to support simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under inter-bandwidth carrier aggregation is that the terminal needs to support simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, that is, the terminal that supports the simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under inter-bandwidth carrier aggregation must / must support the simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation;

[0084] Optionally, this situation can be understood as a terminal that supports the simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under intra-bandwidth carrier aggregation. If the terminal supports PUCCH / PUSCH scheduling of different priorities, then the terminal also supports the simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under intra-bandwidth carrier aggregation.

[0085] Optionally, in one implementation, the method further includes:

[0086] The terminal receives a first configuration parameter sent by the network side device;

[0087] The first configuration parameter is used to enable simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under carrier aggregation of the terminal.

[0088] Optionally, the first configuration parameter satisfies at least one of the following:

[0089] The first configuration parameter is used to enable simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under carrier aggregation between bandwidths of the terminal;

[0090] The first configuration parameter is used to enable simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under carrier aggregation within the bandwidth of the terminal.

[0091] This implementation can be understood as whether the terminal uses the simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under carrier aggregation to determine how to perform uplink transmission, which needs to be enabled by the network side device; optionally, the first configuration parameter can be configured, for example, through high-level signaling, optionally, the first configuration parameter can be configured, for example, through radio resource control (Radio Resource Control, RRC) parameter configuration.

[0092] For example, the terminal sends terminal capability information to the network side device, and the terminal capability information is used to indicate whether the terminal supports the simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under inter-bandwidth carrier aggregation. When the network side device determines to enable the simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under inter-bandwidth carrier aggregation, it is necessary to send a first configuration parameter to the terminal, and the first configuration parameter is used to enable the simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under inter-bandwidth carrier aggregation of the terminal.

[0093] It should be noted that, when the terminal is enabled with carrier aggregation and PUCCH and PUSCH of the same priority are transmitted simultaneously on different cells, the terminal may perform overlapping processing in at least one of the following ways.

[0094] Method 1:

[0095] Optionally, in one implementation, the method further includes:

[0096] In a case where the first PUCCH overlaps with at least one PUSCH, the terminal multiplexes the first PUCCH with one or more PUSCHs of the at least one PUSCH;

[0097] The first PUCCH and the at least one PUSCH have the same priority; and the at least one PUSCH cannot be transmitted simultaneously with the first PUCCH.

[0098] It should be noted that the at least one PUSCH cannot be transmitted simultaneously with the first PUCCH, which can be understood as the at least one PUSCH and the first PUCCH do not meet the requirements of different service cells between bandwidths; for example, the cell where the first PUCCH and at least one PUSCH are located is located in the same bandwidth (band), then at least one PUSCH and the first PUCCH do not meet the requirements of different service cells between bandwidths; or,

[0099] The at least one PUSCH cannot be transmitted simultaneously with the first PUCCH, which can be understood as the at least one PUSCH and the first PUCCH do not meet the requirements of different service cells within the bandwidth; for example, the first PUCCH and at least one PUSCH are located in the same service cell, then the at least one PUSCH and the first PUCCH do not meet the requirements of different service cells within the bandwidth.

[0100] It should be noted that the overlap of the first PUCCH and at least one PUSCH can be understood as the overlap of the first PUCCH and at least one PUSCH in time domain, for example, the time domain of the first PUCCH partially or completely overlaps the time domain of at least one PUSCH.

[0101] This situation can be understood as follows: if a PUCCH overlaps with one or more PUSCHs, and the one or more PUSCHs overlapping with the PUCCH cannot be transmitted simultaneously with the PUCCH, the terminal needs to multiplex the PUCCH for transmission. Specifically, the PUCCH can be multiplexed into one PUSCH in one or more PUSCHs, or the PUCCH can be multiplexed into multiple PUSCHs in one or more PUSCHs. How the terminal determines which PUSCH to multiplex the UCI onto can be implemented according to the prior art and is not limited in this application.

[0102] For example, PUCCH1 overlaps with PUSCH1 and PUSCH2, PUCCH1, PUSCH1 and PUSCH2 have the same priority, and PUSCH1 and PUSCH2 cannot be transmitted simultaneously with PUCCH1, then the terminal multiplexes PUCCH1 onto PUSCH1 for transmission, or the terminal multiplexes PUCCH1 onto PUSCH2 for transmission, or the terminal multiplexes PUCCH1 onto PUSCH1 and PUSCH2 for transmission.

[0103] Method 2:

[0104] Optionally, in one implementation, the method further includes:

[0105] In a case where the second PUCCH overlaps with multiple PUSCHs, the terminal multiplexes the second PUCCH with at least one PUSCH in the target PUSCH;

[0106] The second PUCCH and the multiple PUSCHs have the same priority, the target PUSCH is a PUSCH among the multiple PUSCHs that does not support simultaneous transmission with the second PUCCH, or the target PUSCH is a PUSCH among the multiple PUSCHs excluding the PUSCH that can be transmitted simultaneously with the second PUCCH.

[0107] This situation can be understood as follows: if a PUCCH overlaps with one or more PUSCHs, and some of the one or more PUSCHs overlapping with the PUCCH cannot be transmitted simultaneously with the PUCCH, and some can be transmitted simultaneously with the PUCCH, then the terminal needs to multiplex the PUCCH onto the PUSCH that can be transmitted simultaneously with the PUCCH.

[0108] For example, PUCCH1 overlaps with PUSCH1, PUSCH2 and PUSCH3, and PUCCH1, PUSCH1, PUSCH2 and PUSCH3 have the same priority. PUSCH1 cannot be transmitted simultaneously with PUCCH1, but PUSCH2 and PUSCH3 can both be transmitted simultaneously with PUCCH1. Then the terminal multiplexes PUCCH1 onto PUSCH2 for transmission, or the terminal multiplexes PUCCH1 onto PUSCH3 for transmission, or the terminal multiplexes PUCCH1 onto PUSCH2 and PUSCH3 for transmission.

[0109] Method 3:

[0110] Optionally, in one implementation, the method further includes:

[0111] In a case where the third PUCCH overlaps with the first PUSCH, the terminal transmits the third PUCCH and the first PUSCH respectively;

[0112] The third PUCCH and the first PUSCH have the same priority; the first PUSCH can be transmitted simultaneously with the third PUCCH.

[0113] It should be noted that the first PUSCH can be transmitted simultaneously with the third PUCCH, which can be understood as the first PUSCH and the third PUCCH meeting the requirements of different service cells between bandwidths. For example, the first PUSCH and the third PUCCH are located in different service cells with different bandwidths, and the first PUSCH and the third PUCCH meet the requirements of different service cells between bandwidths; or,

[0114] The first PUSCH can be transmitted simultaneously with the third PUCCH, which can be understood as the first PUSCH and the third PUCCH meeting the requirements of different service cells within the bandwidth. For example, the first PUSCH and the third PUCCH are located in different service cells of the same bandwidth, then the first PUSCH and the third PUCCH meet the requirements of different service cells within the bandwidth.

[0115] It should be noted that the first PUSCH mentioned in the embodiment of the present application may be one or more PUSCHs.

[0116] This situation can be understood as follows: if a certain PUCCH overlaps with one or more PUSCHs, and the one or more PUSCHs overlapping with the PUCCH can be transmitted simultaneously with the PUCCH, then the terminal can transmit the overlapping PUCCH and PUSCH at the positions of the PUCCH and PUSCH, respectively, that is, the terminal can transmit the overlapping PUCCH and PUSCH at the same time. Optionally, the simultaneous transmission here can be understood as: transmitting the PUCCH and PUSCH at the respective resource positions of the PUCCH and PUSCH, respectively.

[0117] Method 4:

[0118] Optionally, in one implementation, the method further includes:

[0119] In a case where the fourth PUCCH overlaps with the fifth PUCCH, the terminal multiplexes the fourth PUCCH and the fifth PUCCH to obtain a sixth PUCCH, and the fourth PUCCH and the fifth PUCCH have different priorities;

[0120] In the case that the sixth PUCCH overlaps with the second PUSCH, the terminal will transmit the sixth PUCCH and the second PUSCH respectively, wherein the sixth PUCCH and the second PUSCH have the same priority; the second PUSCH can be transmitted simultaneously with the sixth PUCCH.

[0121] It should be noted that the second PUSCH can be transmitted simultaneously with the sixth PUCCH, which can be understood as the second PUSCH and the sixth PUCCH meeting the requirements of different service cells between bandwidths. For example, the second PUSCH and the sixth PUCCH are located in different service cells of different bandwidths, then the second PUSCH and the sixth PUCCH meet the requirements of different service cells between bandwidths; or

[0122] The second PUSCH can be transmitted simultaneously with the sixth PUCCH, which can be understood as the second PUSCH and the sixth PUCCH meeting the requirements of different service cells within the bandwidth. For example, the second PUSCH and the sixth PUCCH are located in different service cells of the same bandwidth, then the second PUSCH and the sixth PUCCH meet the requirements of different service cells within the bandwidth.

[0123] It should be noted that the second PUSCH mentioned in the embodiment of the present application may be one or more PUSCHs.

[0124] This situation can be understood as follows: if there are multiple overlapping PUCCHs of different priorities, these PUCCHs can be multiplexed to obtain a multiplexed PUCCH, and the multiplexed PUCCH has a specific priority, for example, the multiplexed PUCCH has a high priority. If the priority of the multiplexed PUCCH overlaps with one or more PUSCHs of the same priority, and the multiplexed PUCCH can be transmitted simultaneously with one or more PUSCHs of the same priority, the terminal transmits the multiplexed PUCCH and these PUSCHs respectively.

[0125] It should also be noted here that the multiplexing between PUCCHs of different priorities needs to be enabled by the network side equipment, that is, the network side equipment sends high-level signaling or RRC signaling to enable the multiplexing between PUCCHs of different priorities. If the network side equipment does not enable the multiplexing between PUCCHs of different priorities, the terminal cannot multiplex PUCCHs of different priorities.

[0126] Method 5:

[0127] Optionally, in one implementation, the method further includes:

[0128] In the case where the seventh PUCCH overlaps with the third PUSCH, the terminal transmits the seventh PUCCH and the third PUSCH respectively;

[0129] The priorities of the seventh PUCCH and the third PUSCH are different; the third PUSCH can be transmitted simultaneously with the seventh PUCCH.

[0130] It should be noted that the third PUSCH can be transmitted simultaneously with the seventh PUCCH, which can be understood as the third PUSCH and the seventh PUCCH meeting the requirements of different service cells between bandwidths. For example, the third PUSCH and the seventh PUCCH are located in different bandwidths and different service cells, then the third PUSCH and the seventh PUCCH meet the requirements of different service cells between bandwidths; or

[0131] The third PUSCH can be transmitted simultaneously with the seventh PUCCH, which can be understood as the third PUSCH and the seventh PUCCH meeting the requirements of different service cells within the bandwidth. For example, the third PUSCH and the seventh PUCCH are located in different service cells of the same bandwidth, then the third PUSCH and the seventh PUCCH meet the requirements of different service cells within the bandwidth.

[0132] It should be noted that the third PUSCH mentioned in the embodiment of the present application may be one or more PUSCHs.

[0133] This situation can be understood as, if a PUCCH overlaps with one or more PUSCHs, the PUCCH and one or more PUSCHs have different priorities, and the one or more PUSCHs overlapping with the PUCCH can be transmitted simultaneously with the PUCCH, then the terminal can transmit the overlapping PUCCH and PUSCH at the positions of PUCCH and PUSCH respectively.

[0134] It should be noted that the implementation of this situation requires that the simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation is also enabled. Optionally, in one case, when the terminal receives the first configuration parameter, the terminal defaults to the simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation. It is also enabled; or, optionally, in another case, the enabling of simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation is also configured by the network side device. Optionally, in one implementation, the method further includes:

[0135] The terminal receives a second configuration parameter sent by the network side device;

[0136] The second configuration parameter is used to enable simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under carrier aggregation of the terminal.

[0137] Optionally, the second configuration parameter satisfies at least one of the following:

[0138] The second configuration parameter is used to enable simultaneous transmission of PUCCHs and PUSCHs of different priorities on different cells under inter-bandwidth carrier aggregation of the terminal;

[0139] The second configuration parameter is used to enable simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under carrier aggregation within the bandwidth of the terminal.

[0140] That is, in this case, the network side device not only needs to send the first configuration parameter to enable the simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under carrier aggregation, but also needs to send the second configuration parameter to enable the simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under carrier aggregation. For example, if the terminal is enabled for the simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under inter-bandwidth carrier aggregation, if the terminal is also configured or indicated for PUCCH / PUSCH of different priorities, the terminal expects the network side device to send the second configuration parameter to enable the simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation.

[0141] Optionally, when the terminal is enabled with simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under carrier aggregation, in one implementation manner, the method further includes at least one of the following:

[0142] A11, the terminal processes overlap between PUCCHs of the same priority;

[0143] A12, the terminal processes the overlap between PUCCH and PUSCH of the same priority;

[0144] A13, the terminal processes overlap between PUCCHs of different priorities;

[0145] A14. The terminal processes overlap between PUCCH and PUSCH of different priorities.

[0146] It should be noted that the above-mentioned implementations can be used in any combination in specific use. If there is overlap between multiple PUCCHs of different priorities, overlap between PUCCHs and PUSCHs of different priorities, overlap between multiple PUCCHs of the same priority, and overlap between PUCCHs and PUSCHs of the same priority, the terminal needs to first process the overlap between multiple PUCCHs of the same priority, then process the overlap between PUCCHs and PUSCHs of the same priority, then process the overlap between multiple PUCCHs of different priorities, and finally process the overlap between PUCCHs and PUSCHs of different priorities. That is, the processing order of the terminal in this case is:

[0147] Step 1: Handle the overlap between PUCCHs of the same priority level;

[0148] Step 2: Handle the overlap between PUCCH and PUSCH of the same priority;

[0149] Step 3: Handle the overlap between PUCCHs of different priorities;

[0150] Step 4: Process the overlap between PUCCH and PUSCH of different priorities, or process the overlap between PUCCH and PUSCH of the same priority and the overlap between PUCCH and PUSCH of different priorities;

[0151] It should be noted that when the multiplexed PUCCH obtained by processing the overlap between PUCCHs of different priorities in step 3 overlaps with the PUSCH with the same priority, the terminal needs to process the overlap between PUCCH and PUSCH of the same priority in step 4; if the multiplexed PUCCH obtained by processing the overlap between PUCCHs of different priorities in step 3 does not overlap with the PUSCH with the same priority, the terminal only needs to process the overlap between PUCCH and PUSCH of different priorities in step 4.

[0152] It should be noted that the specific implementation of the above-mentioned A12 can adopt one or more of the above-mentioned methods 1, 2 and 3. The specific implementation of the above-mentioned A13 can adopt the above-mentioned method 4; the specific implementation of the above-mentioned A14 can adopt the above-mentioned method 5;

[0153] It is particularly important to note that if PUCCH multiplexing is required when processing the overlap between PUCCHs of different priorities, the multiplexed PUCCH obtained can only overlap with the PUSCH of the same priority that supports simultaneous transmission with the PUCCH. At this time, the terminal only needs to transmit the multiplexed PUCCH and the PUSCH separately.

[0154] The following takes the simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under inter-bandwidth carrier aggregation supported by the terminal as an example, and illustrates the specific application of the embodiments of the present application as follows.

[0155] The deployment scenario of the embodiment to which the present application can be applied is the uplink carrier aggregation (UL CA) scenario, for example, the terminal is deployed with UL CA, and the cell where the PUCCH is located (it is worth noting that the cell where the PUCCH is located may be the primary cell (Pcell) or if the terminal is configured with PUCCH cell switching, the cell where the PUCCH is located may also be an Scell, such as PUCCH switching Scell, PUCCH-sSCell, and the cell where the PUCCH is located may also refer to the cell where the PUCCH may be located) has a larger subcarrier spacing (SCS) than the SCS of the cell where the PUSCH is located. For example, the terminal is configured with UL CA, wherein its PCell is in the time division duplex (TDD) frequency band, and its SCS is configured to be 30kHz, and its SCell is in the frequency division duplex (FDD) frequency band, and its SCS is configured to be 15kHz.

[0156] The existing scheduling restrictions are: Figure 3As shown, if the base station schedules a PUSCH in a time slot on the secondary cell (Scell), and its time domain resources overlap with two slots of the PCell, the base station is not allowed to schedule two PUCCHs in these two slots to carry HARQ-ACK feedback information respectively, and these two PUCCHs overlap with the PUSCH and the terminal will multiplex the HARQ-ACK information on the two PUCCHs on the PUSCH according to the corresponding protocol rules. For example, the two PUCCHs have the same priority as the PUSCH, or the two PUCCHs have the same priority and the priority of the PUCCH is different from that of the PUSCH and the terminal is enabled for multiplexing between different priorities (for example, the terminal is configured with uci-MuxWithDiffPrio). However, such scheduling restrictions will cause a serious loss of system throughput.

[0157] In order to solve the above-mentioned scheduling limitations, one solution is to support the simultaneous transmission of PUCCH and PUSCH of the same priority on different service cells in inter-band bandwidth. It can be based on terminal capabilities, for example, by introducing terminal capability information (such as parallelTxPUCCH-PUSCH-samePrio), which is used to indicate whether the terminal supports the simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under inter-band carrier aggregation.

[0158] Optionally, this capability may be only for HARQ-ACK transmission, that is, the PUCCH that can be transmitted simultaneously with the PUSCH contains HARQ-ACK information. If the PUCCH overlapping with the PUSCH does not contain HARQ-ACK information (for example, the PUCCH only contains CSI or SR), the simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under inter-bandwidth carrier aggregation is not supported.

[0159] Optionally, this capability is premised on supporting simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, that is, a terminal that supports this capability, if it also supports PUCCH / PUSCH transmission of different priorities, must / must support simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation.

[0160] When the terminal indicates to the base station whether it supports this capability, the base station can enable the terminal to simultaneously transmit PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, for example, by configuring / indicating through high-level signaling, such as through RRC parameter configuration (for example, through simultaneousPUCCH-PUSCHWithSamePrio configuration). When the terminal is enabled for simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under inter-bandwidth carrier aggregation (for example, the parameter simultaneousPUCCH-PUSCHWithSamePrio is configured), the base station does not need to meet the above scheduling restrictions when scheduling PUCCH / PUSCH. That is, if the base station schedules a PUSCH in a slot on the Scell, and its time domain resources overlap with two slots of the PCell, the base station is allowed to schedule two PUCCHs in the two slots for carrying HARQ-ACK feedback information, respectively, and both PUCCHs overlap with the PUSCH, and the two PUCCHs have the same priority as the PUSCH.

[0161] Under the above solution, the method for the terminal to handle the overlap of PUCCH and PUSCH is as follows: when the terminal is enabled for simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under inter-bandwidth carrier aggregation, if the base station schedules a PUSCH in a slot on the Scell, and its time domain resources overlap with two slots of the PCell, the base station schedules / configures multiple PUCCHs in these two slots for carrying the same type of UCI (such as HARQ-ACK feedback information), and these multiple PUCCHs overlap with the PUSCH.

[0162] For example, the terminal processes in the following order:

[0163] Step 1: The terminal handles the overlap between channels of the same priority;

[0164] Step 1-1, the terminal processes the overlap of PUCCH and PUCCH of the same priority;

[0165] Step 1-2: The terminal processes the overlap of PUCCH and PUSCH of the same priority.

[0166] Step 2: The terminal handles the overlap of channels with different priorities;

[0167] Step 2-1, the terminal processes PUCCHs of different priorities and overlaps PUCCHs;

[0168] Step 2-2: The terminal processes the overlap of PUCCH and PUSCH of different priorities;

[0169] Among them, for steps 1-2, if the terminal is enabled for simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under inter-bandwidth carrier aggregation, when the terminal processes the overlap of PUCCH and PUSCH of the same priority, the terminal multiplexes UCI on PUSCH of the same priority, and the terminal excludes PUSCH that supports simultaneous transmission with PUCCH (UCI is multiplexed to PUSCH that does not support simultaneous transmission with PUCCH, if any).

[0170] Among them, for step 2-1, if the terminal is enabled to multiplex PUCCHs and PUSCHs of different priorities, some PUCCHs of different priorities may be multiplexed, such as HARQ-ACK PUCCHs of different priorities.

[0171] For 2-2, if the terminal is enabled for multiplexing of PUCCH and PUSCH of different priorities and simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under inter-bandwidth carrier aggregation, when the terminal processes the overlap of PUCCH and PUSCH of different priorities, when the terminal multiplexes UCI onto PUSCH of different priorities, the terminal excludes PUSCH that supports simultaneous transmission with PUCCH (UCI is multiplexed onto PUSCH that does not support simultaneous transmission, if any).

[0172] It should be noted that all the following application scenarios are based on the premise that the terminal is enabled to transmit PUCCH and PUSCH of the same priority on different cells under inter-bandwidth carrier aggregation, where a larger priority index indicates a higher priority.

[0173] Application scenario 1: A PUSCH overlaps with the PUCCH time domain resources carrying the same UCI type (such as HARQ-ACK) in two different time slots. Figure 4 And as shown in Table 1.

[0174] Table 1 Application of PUCCH and PUSCH transmission position and priority correspondence table

[0175]

[0176] Case 1-1: All PUCCHs have the same priority, and all PUCCHs have the same priority as the PUSCH, then the terminal transmits PUCCH#1, PUCCH#2 and PUSCH#1 simultaneously.

[0177] For example, the priority indexes of all PUCCHs and PUSCHs are 0 or 1.

[0178] Case 1-2: PUCCH1#1 and PUCCH#2 have different priorities. Specifically, at least one of the following cases exists:

[0179] Case 1-2-1, the priority index of PUCCH#1 is 0, the priority index of PUCCH#2 is 1, and the priority index of PUSCH#1 is 0

[0180] This situation includes one of the following:

[0181] 1. If the terminal does not enable simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, nor does it enable multiplexing between different priorities (including multiplexing between PUCCH and PUCCH of different priorities or between PUCCH and PUSCH, for example, the terminal is not configured with uci-MuxWithDiffPrio), the terminal discards PUSCH#1 and transmits PUCCH#1 and PUCCH#2 respectively;

[0182] Optionally, the terminal does not expect this scenario to occur.

[0183] 2. If the terminal is also enabled with simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, the terminal transmits the above-mentioned PUCCH#1, PUCCH#2 and PUSCH#1 respectively at the same time;

[0184] Among them, optionally, when the terminal is enabled for simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under inter-bandwidth carrier aggregation, it means that the terminal is also enabled for simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation (if the terminal is scheduled / configured with PUCCH and PUSCH of different priorities, or the terminal supports PUCCH and / or PUSCH transmission of different priorities)

[0185] It should be noted that, when the terminal supports the simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under inter-bandwidth carrier aggregation, if the UE is scheduled for PUCCH and PUSCH transmission of different priorities, the terminal is enabled by default for the simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation; or, when the terminal supports the simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under inter-bandwidth carrier aggregation, if the terminal is configured or scheduled for PUCCH and PUSCH transmission of different priorities, the base station must enable the simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation of the terminal.

[0186] 3. If the terminal is enabled with multiplexing between different priorities (including multiplexing between PUCCH and PUSCH of different priorities), for example, the terminal is configured with uci-MuxWithDiffPrio, and simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation is not enabled, the terminal multiplexes the UCI on PUCCH#2 on PUSCH#1 for transmission, and cancels the transmission of PUCCH#1;

[0187] Optionally, the terminal does not expect this scenario to occur.

[0188] 4. If the terminal is also enabled with multiplexing between different priorities (including multiplexing between PUCCH and PUSCH of different priorities) and simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, the terminal transmits PUCCH#1, PUCCH#2 and PUSCH#1 respectively at the same time, or the terminal multiplexes the UCI on PUCCH#1 or PUCCH#2 to PUSCH#1 for transmission.

[0189] Case 1-2-2, the priority index of PUCCH#1 is 0, the priority index of PUCCH#2 is 1, and the priority index of PUSCH is 1

[0190] This situation includes one of the following:

[0191] 1. If the terminal does not enable simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, nor does it enable multiplexing between different priorities (including multiplexing between PUCCH and PUCCH of different priorities or between PUCCH and PUSCH, for example, the terminal is not configured with uci-MuxWithDiffPrio), the terminal discards PUCCH#1 and transmits PUCCH#2 and PUSCH#1 respectively;

[0192] Optionally, the terminal does not expect this scenario to occur.

[0193] 2. If the terminal is enabled with simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, the terminal transmits the above-mentioned PUCCH#1, PUCCH#2 and PUSCH#1 respectively at the same time.

[0194] 3. If the terminal is also enabled with multiplexing between different priorities (including multiplexing between PUCCH and PUCCH of different priorities or between PUCCH and PUSCH), for example, the terminal is configured with uci-MuxWithDiffPrio, and the terminal is not enabled with simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, the terminal multiplexes the UCI on PUCCH#1 on PUSCH for transmission, and transmits PUCCH#2 and PUSCH#1 separately.

[0195] 4. If the terminal is also enabled with multiplexing between different priorities (including multiplexing between PUCCHs of different priorities and PUCCHs or between PUCCHs and PUSCHs, for example, the terminal is configured with uci-MuxWithDiffPrio) and simultaneous transmission of PUCCHs and PUSCHs of different priorities on different cells under inter-bandwidth carrier aggregation, the terminal transmits PUCCH#1, PUCCH#2 and PUSCH#1 respectively at the same time, or the terminal multiplexes the UCI on PUCCH#1 or PUCCH#2 to PUSCH#1 for transmission.

[0196] Case 1-2-3, the priority index of PUCCH#1 is 1, the priority index of PUCCH#2 is 0, and the priority index of PUSCH#1 is 0

[0197] This situation includes one of the following:

[0198] 1. If the terminal neither enables simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, nor enables multiplexing between different priorities (including multiplexing between PUCCH and PUCCH of different priorities or between PUCCH and PUSCH, for example, the terminal is not configured with uci-MuxWithDiffPrio), the terminal discards PUSCH#1 and transmits PUCCH#1 and PUCCH#2 respectively.

[0199] Optionally, the terminal does not expect this scenario to occur.

[0200] 2. If the terminal is enabled with simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, the terminal transmits the above-mentioned PUCCH#1, PUCCH#2 and PUSCH#1 respectively at the same time.

[0201] 3. If the terminal is also enabled with different priorities (including multiplexing between PUCCH and PUSCH of different priorities), for example, the terminal is configured with uci-MuxWithDiffPrio, and the terminal is not enabled for simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, the terminal multiplexes the UCI on PUCCH#1 for transmission on PUSCH#1 and cancels the transmission of PUCCH#2.

[0202] Optionally, the terminal does not expect this scenario to occur.

[0203] 4. If the terminal is also enabled with multiplexing between different priorities (including multiplexing between PUCCHs of different priorities and PUCCHs or between PUCCHs and PUSCHs, for example, the terminal is configured with uci-MuxWithDiffPrio) and simultaneous transmission of PUCCHs and PUSCHs of different priorities on different cells under inter-bandwidth carrier aggregation, the terminal transmits PUCCH#1, PUCCH#2 and PUSCH#1 respectively at the same time, or the terminal multiplexes the UCI on PUCCH#1 or PUCCH#2 to PUSCH#1 for transmission.

[0204] Case 1-2-4, the priority index of PUCCH#1 is 1, the priority index of PUCCH#2 is 0, and the priority index of PUSCH#1 is 1

[0205] This situation includes one of the following:

[0206] 1. If the terminal neither enables simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, nor enables multiplexing between different priorities (including multiplexing between PUCCH and PUCCH of different priorities or between PUCCH and PUSCH, for example, the terminal is not configured with uci-MuxWithDiffPrio), the terminal discards PUCCH#2 and transmits PUCCH#1 and PUSCH#1 respectively.

[0207] Optionally, the terminal does not expect this scenario to occur.

[0208] 2. If the terminal is also enabled with simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, the terminal transmits the above-mentioned PUCCH#2 and PUSCH#1 respectively at the same time.

[0209] 3. If the terminal is also enabled with multiplexing between different priorities (including multiplexing between PUCCH and PUCCH of different priorities or between PUCCH and PUSCH), for example, the terminal is configured with uci-MuxWithDiffPrio, and the terminal is not enabled with simultaneous transmission of PUCCH and PUSCH of different priorities in different cells under inter-bandwidth carrier aggregation, the terminal multiplexes the UCI on PUCCH#2 on PUSCH#1 for transmission, and transmits PUCCH#1 and PUSCH#1 separately.

[0210] 4. If the terminal is also enabled with multiplexing between different priorities (including multiplexing between PUCCHs of different priorities and PUCCHs or between PUCCHs and PUSCHs, for example, the terminal is not configured with uci-MuxWithDiffPrio) and simultaneous transmission of PUCCHs and PUSCHs of different priorities on different cells under inter-bandwidth carrier aggregation, the terminal transmits the above-mentioned PUCCH#1, PUCCH#2 and PUSCH#1 respectively at the same time, or the terminal multiplexes the UCI on PUCCH#1 or PUCCH#2 to PUSCH#1 for transmission.

[0211] To summarize, if the terminal is enabled for simultaneous transmission of PUCCH and PUSCH of the same priority and different priorities on different cells under inter-bandwidth carrier aggregation (regardless of whether the terminal is enabled for multiplexing between different priorities), then in the following application scenario, the terminal transmits the above-mentioned PUCCH and PUSCH separately.

[0212] Application scenario 2: A PUSCH overlaps with three PUCCH time domain resources carrying the same UCI type (such as HARQ-ACK) in different time slots, where two PUCCHs are in one time slot and have different priority indexes.

[0213] Case 2-1, the priority index of PUCCH#1 is 1, and the priority index of PUSCH#1 is 0, such as Figure 5 And as shown in Table 2.

[0214] Table 2 PUCCH and PUSCH transmission position and priority correspondence table 1 under application case 2

[0215]

[0216] This situation includes one of the following:

[0217] 1. If the terminal neither enables simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, nor enables multiplexing between different priorities (including multiplexing between PUCCH and PUCCH of different priorities or between PUCCH and PUSCH, for example, the terminal is not configured with uci-MuxWithDiffPrio), the terminal discards PUCCH#2 and PUSCH#1, and transmits PUCCH#1 and PUCCH#3 respectively.

[0218] Or, optionally, the terminal does not expect the scenario to occur.

[0219] 2. If the terminal is also enabled with simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, and multiplexing between different priorities is not enabled (including multiplexing between PUCCH and PUCCH of different priorities or between PUCCH and PUSCH, for example, the terminal is not configured with uci-MuxWithDiffPrio), the terminal discards PUCCH#2 and transmits the above-mentioned PUCCH#1, PUCCH#3 and PUSCH#1 respectively.

[0220] Or, optionally, the terminal does not expect the scenario to occur.

[0221] 3. If the terminal is also enabled with multiplexing between different priorities (including multiplexing between PUCCHs of different priorities and PUCCHs or between PUCCHs and PUSCHs, for example, the terminal is configured with uci-MuxWithDiffPrio), and the simultaneous transmission of PUCCHs and PUSCHs of different priorities on different cells under inter-bandwidth carrier aggregation is not enabled, the terminal will multiplex the UCI on PUCCH#2 and PUCCH#3 on one PUCCH. Assuming that the multiplexed PUCCH is PUCCH#R, if PUCCH#R (whose priority index is 1) overlaps with PUSCH#1, the terminal will multiplex the UCI carried on PUCCH#R and / or PUCCH#1 to PUSCH#1 for transmission.

[0222] Optionally, the terminal does not expect this scenario to occur, or the terminal does not expect PUCCH#R to overlap with PUSCH#1.

[0223] 4. If the terminal is also enabled with multiplexing between different priorities (including multiplexing between PUCCHs of different priorities and PUCCHs or between PUCCHs and PUSCHs, for example, the terminal is configured with uci-MuxWithDiffPrio) and simultaneous transmission of PUCCHs and PUSCHs of different priorities on different cells under inter-bandwidth carrier aggregation, the terminal multiplexes PUCCH#2 and PUCCH#3. Assuming that the multiplexed PUCCH is PUCCH#R (high priority), the terminal transmits PUCCH#1, PUCCH#R and PUSCH#1 respectively.

[0224] Case 2-2, the priority index of PUCCH#1 is 0, and the priority index of PUSCH#1 is 1, as shown in Table 3:

[0225] Table 3 PUCCH and PUSCH transmission position and priority correspondence table 2 under application scenario 2

[0226]

[0227] This situation includes one of the following:

[0228] 1. If the terminal does not enable simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, nor is multiplexing between different priorities enabled (including multiplexing between PUCCH and PUCCH of different priorities or between PUCCH and PUSCH, for example, the terminal is not configured with uci-MuxWithDiffPrio), the terminal discards PUCCH#1 and PUCCH#2, and transmits PUCCH#3 and PUSCH#1 respectively;

[0229] Or, optionally, the terminal does not expect the scenario to occur.

[0230] 2. If the terminal is also enabled with simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, and multiplexing between different priorities is not enabled (including multiplexing between PUCCH and PUCCH of different priorities or between PUCCH and PUSCH, for example, the terminal is not configured with uci-MuxWithDiffPrio), the terminal discards PUCCH#2 and transmits the above-mentioned PUCCH#1, PUCCH#3 and PUSCH#1 respectively.

[0231] Or, optionally, the terminal does not expect the scenario to occur.

[0232] 3. If the terminal is also enabled with multiplexing between different priorities (including multiplexing between PUCCH and PUCCH of different priorities or between PUCCH and PUSCH, for example, the terminal is configured with uci-MuxWithDiffPrio), and the terminal is not enabled with simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, the terminal multiplexes the UCI on PUCCH#2 and PUCCH#3 on one PUCCH. Assuming that the multiplexed PUCCH is PUCCH#R, where PUCCH#R (whose priority index is 1), optionally, PUCCH#R can overlap with PUSCH#1, the terminal multiplexes the UCI carried on PUCCH#1 to PUSCH#1, and transmits PUCCH#R and PUSCH#1 respectively;

[0233] Optionally, the terminal does not expect this scenario to occur.

[0234] 4. If the terminal is also enabled with multiplexing between different priorities (including multiplexing between PUCCHs of different priorities and PUCCHs or between PUCCHs and PUSCHs, for example, the terminal is configured with uci-MuxWithDiffPrio) and simultaneous transmission of PUCCHs and PUSCHs of different priorities on different cells under inter-bandwidth carrier aggregation, the terminal multiplexes PUCCH#2 and PUCCH#3. Assuming that the multiplexed PUCCH is PUCCH#R (high priority), optionally, PUCCH#R can overlap with PUSCH#1, and the terminal transmits PUCCH#1, PUCCH#R and PUSCH#1 respectively.

[0235] Case 2-3, the priority index of PUCCH#1 is 1, and the PUSCH priority index is 0, as shown in Table 4:

[0236] Table 4 PUCCH and PUSCH transmission position and priority correspondence table 3 under application case 2

[0237]

[0238] This situation includes one of the following:

[0239] 1. If the terminal does not enable simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, nor is multiplexing between different priorities enabled (including multiplexing between PUCCH and PUCCH of different priorities or between PUCCH and PUSCH, for example, the terminal is not configured with uci-MuxWithDiffPrio), the terminal discards PUCCH#2 and PUSCH#1, and transmits PUCCH#1 and PUCCH#3 respectively;

[0240] Or, optionally, the terminal does not expect the scenario to occur.

[0241] 2. If the terminal is also enabled with simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, and multiplexing between different priorities is not enabled (including multiplexing between PUCCH and PUCCH of different priorities or between PUCCH and PUSCH, for example, the terminal is not configured with uci-MuxWithDiffPrio), the terminal discards PUCCH#2 and transmits the above-mentioned PUCCH#1, PUCCH#3 and PUSCH#1 respectively.

[0242] Or, optionally, the terminal does not expect the scenario to occur.

[0243] 3. If the terminal is also enabled with multiplexing between different priorities (including multiplexing between PUCCH and PUCCH of different priorities or between PUCCH and PUSCH), for example, the terminal is configured with uci-MuxWithDiffPrio, and the terminal is not enabled with simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, the terminal will multiplex the UCI on PUCCH#2 and PUCCH#3 on one PUCCH. Assuming that the multiplexed PUCCH is PUCCH#R, if PUCCH#R (whose priority index is 1) overlaps with PUSCH#1, the terminal will multiplex the UCI carried on PUCCH#R to PUSCH#1 for transmission and discard PUCCH#1. Or if the multiplexed PUCCH#R cannot overlap with PUSCH#1, the UE will multiplex the UCI carried on PUCCH#1 on PUSCH#1 and transmit PUCCH#R and PUSCH#1 separately.

[0244] Optionally, the terminal does not expect this scenario to occur.

[0245] 4. If the terminal is also enabled with multiplexing between different priorities (including multiplexing between PUCCHs of different priorities and PUCCHs or between PUCCHs and PUSCHs, for example, the terminal is configured with uci-MuxWithDiffPrio), and simultaneous transmission of PUCCHs and PUSCHs of different priorities on different cells under inter-bandwidth carrier aggregation, the terminal multiplexes PUCCH#2 and PUCCH#3. Assuming that the multiplexed PUCCH is PUCCH#R (high priority), where PUCCH#R, if it can be transmitted simultaneously with PUSCH (inter-band, different cells (such as component carriers (CC))), the terminal transmits PUCCH#1, PUCCH#R and PUSCH#1 respectively (where PUCCH#R can overlap with PUSCH#1).

[0246] Case 2-4, the priority index of PUCCH#1 is 1, and the priority index of PUSCH#1 is 1, as shown in Table 5:

[0247] Table 5 PUCCH and PUSCH transmission position and priority correspondence table 4 under application case 2

[0248]

[0249] This situation includes one of the following:

[0250] 1. If the terminal does not enable simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, nor is multiplexing between different priorities enabled (including multiplexing between PUCCH and PUCCH of different priorities or between PUCCH and PUSCH, for example, the terminal is not configured with uci-MuxWithDiffPrio), the terminal drops PUCCH#2 and transmits and discards PUCCH#1, PUCCH#3 and PUSCH#1 respectively.

[0251] Optionally, the terminal does not expect this scenario to occur.

[0252] 2. If the terminal is also enabled with simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, and multiplexing between different priorities is not enabled (including multiplexing between PUCCH and PUCCH of different priorities or between PUCCH and PUSCH, for example, the terminal is not configured with uci-MuxWithDiffPrio), the terminal discards PUCCH#2 and transmits the above-mentioned PUCCH#1, PUCCH#3 and PUSCH#1 respectively.

[0253] Optionally, the terminal does not expect this scenario to occur.

[0254] 3. If the terminal is also enabled with multiplexing between different priorities (including multiplexing between PUCCH and PUCCH of different priorities or between PUCCH and PUSCH, for example, the terminal is configured with uci-MuxWithDiffPrio), and the terminal is not enabled with simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, the terminal will multiplex the UCI on PUCCH#2 and PUCCH#3 on one PUCCH. Assuming that the multiplexed PUCCH is PUCCH#R (where PUCCH#R (its priority index is 1), optionally, if PUCCH#R can be transmitted simultaneously with PUSCH (inter-band, different CCs), PUCCH#R can overlap with PUSCH#1), the terminal will transmit PUCCH#1, PUCCH#R and PUSCH#1 respectively.

[0255] Optionally, the terminal does not expect this scenario to occur.

[0256] 4. If the terminal is also enabled with multiplexing between different priorities (including multiplexing between PUCCH and PUCCH of different priorities or between PUCCH and PUSCH, for example, the terminal is configured with uci-MuxWithDiffPrio) and simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, the terminal multiplexes PUCCH#2 and PUCCH#3, assuming that the multiplexed PUCCH is PUCCH#R (high priority), wherein, optionally, if PUCCH#R can be transmitted simultaneously with PUSCH (inter-band, different CCs), it can overlap with PUSCH#1; the terminal transmits PUCCH#1, PUCCH#R and PUSCH#1 respectively.

[0257] Application scenario 3: The terminal schedules / configures PUSCH transmission on two different SCells, and the overlapping channel contains 2 PUSCHs and 3 PUCCHs

[0258] Case 3-1, PUSCH#1 and PUSCH#2 priority indexes are both 0, as shown below Figure 6 As shown in Table 6:

[0259] Table 6 PUCCH and PUSCH transmission position and priority correspondence table 1 under application case 3

[0260]

[0261] This situation includes one of the following:

[0262] 1. If the terminal does not enable simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, and does not enable multiplexing between different priorities, including multiplexing between PUCCH and PUCCH of different priorities or between PUCCH and PUSCH, for example, the terminal is not configured with uci-MuxWithDiffPrio), the terminal discards PUCCH#2, PUSCH#1 and PUSCH#2, and transmits PUCCH#1 and PUCCH#3 respectively;

[0263] Optionally, the terminal does not expect this scenario.

[0264] 2. If the terminal is also enabled with simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, and multiplexing between different priorities is not enabled (including multiplexing between PUCCH and PUCCH of different priorities or between PUCCH and PUSCH, for example, the terminal is not configured with uci-MuxWithDiffPrio), the terminal discards PUCCH#2 and transmits the above-mentioned PUCCH#1, PUCCH#3 and PUSCH#1, PUSCH#2 respectively; or, the terminal multiplexes the UCI carried by PUCCH#2 on one of PUSCH#1 and PUSCH#2, for example, multiplexes it on PUSCH#2, and transmits PUCCH#1, PUCCH#3 and PUSCH#1, PUSCH#2 respectively.

[0265] 3. If the terminal is also enabled with multiplexing between different priorities (including multiplexing between PUCCH and PUSCH of different priorities), for example, the terminal is configured with uci-MuxWithDiffPrio, and the terminal is not enabled with simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, the terminal will multiplex the UCI on PUCCH#2 and PUCCH#3 on one PUCCH. Assuming that the multiplexed PUCCH is PUCCH#R, if PUCCH#R (whose priority index is 1) overlaps with PUSCH#1 and / or PUSCH#2, the terminal will multiplex the UCI carried on PUCCH#R to PUSCH#1 or PUSCH#2. For example, if it is multiplexed to PUSCH#2, the terminal cancels the PUCCH#1 transmission and transmits PUSCH#1 and PUSCH#2 respectively, or the terminal transmits PUCCH#1, PUSCH#1 and PUSCH#2 respectively.

[0266] Optionally, the terminal does not expect this scenario.

[0267] 4. If the terminal is also enabled with multiplexing between different priorities (including multiplexing between PUCCH and PUCCH of different priorities or between PUCCH and PUSCH, for example, the terminal is configured with uci-MuxWithDiffPrio) and simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, the terminal will multiplex PUCCH#2 and PUCCH#3. Assuming that the multiplexed PUCCH is PUCCH#R (high priority), PUCCH#R can be transmitted simultaneously with PUSCH#1 and PUSCH#2 (that is, the requirement that the serving cells where PUCCH and PUSCH are located are inter-band and different CCs is met), PUCCH#R can overlap with PUSCH#1, and the terminal transmits PUCCH#1, PUCCH#R and PUSCH#1 and PUSCH#2 respectively.

[0268] Case 3-2, the priority indexes of PUSCH#1 and PUSCH#2 are both 1, as shown in Table 7:

[0269] Table 7 PUCCH and PUSCH transmission position and priority correspondence table 2 under application case 3

[0270]

[0271] This situation includes one of the following:

[0272] 1. If the terminal neither enables simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, nor enables multiplexing between different priorities (including multiplexing between PUCCH and PUCCH of different priorities or between PUCCH and PUSCH, for example, the terminal is not configured with uci-MuxWithDiffPrio), the terminal discards PUCCH#1 and PUCCH#2, and transmits PUCCH#3 and PUSCH#1, PUSCH#2 respectively.

[0273] Or, optionally, the terminal does not expect this scenario.

[0274] 2. If the terminal is also enabled with simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, and multiplexing between different priorities is not enabled (including multiplexing between PUCCH and PUCCH of different priorities or between PUCCH and PUSCH, for example, the terminal is not configured with uci-MuxWithDiffPrio), the terminal discards PUCCH#2 and transmits the above-mentioned PUCCH#1, PUCCH#3 and PUSCH#1, PUSCH#2 respectively; or , the terminal multiplexes the UCI carried by PUCCH#2 on one of PUSCH#1 and PUSCH#2, for example, multiplexes it on PUSCH#2, and transmits PUCCH#1, PUCCH#3 and PUSCH#1, PUSCH#2 respectively; or, the terminal multiplexes the UCI carried by PUCCH#3 on one of PUSCH#1 and PUSCH#2, for example, multiplexes it on PUSCH#2, and transmits PUCCH#1, PUCCH#2 and PUSCH#1, PUSCH#2 respectively.

[0275] Or, optionally, the terminal does not expect this scenario.

[0276] 3. If the terminal is also enabled with multiplexing between different priorities (including multiplexing between PUCCH and PUSCH of different priorities), for example, the terminal is configured with uci-MuxWithDiffPrio, and the terminal is not enabled with simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, the terminal will multiplex the UCI on PUCCH#2 and PUCCH#3 on one PUCCH, assuming that the multiplexed PUCCH is PUCCH#R, where PUCCH#R (whose priority index is 1) can overlap or not overlap with PUSCH#1 or PUSCH#2, and transmit PUCCH#1, PUCCH#R, PUSCH#1 and PUSCH#2 respectively.

[0277] 4. If the terminal is also enabled with multiplexing between different priorities, including multiplexing between PUCCHs of different priorities and PUCCHs or between PUCCHs and PUSCHs, for example, the terminal is configured with uci-MuxWithDiffPrio) and simultaneous transmission of PUCCHs and PUSCHs of different priorities on different cells under inter-band carrier aggregation, the terminal multiplexes PUCCH#2 and PUCCH#3. Assume that the multiplexed PUCCH is PUCCH#R (high priority), where PUCCH#R can be transmitted simultaneously with PUSCH (i.e., meeting the requirements of inter-band, different cells (such as CC)). Optionally, PUCCH#R can overlap with PUSCH#1 and / or PUSCH#2, and the terminal transmits PUCCH#1, PUCCH#R and PUSCH#1, PUSCH#2 respectively.

[0278] Case 3-3, the priority index of PUSCH#1 is 1, and the priority index of PUSCH#2 is 0, as shown in Table 8:

[0279] Table 8 PUCCH and PUSCH transmission position and priority correspondence table 3 under application case 3

[0280]

[0281] This situation includes one of the following:

[0282] 1. If the terminal neither enables simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, nor enables multiplexing between different priorities (including multiplexing between PUCCH and PUCCH of different priorities or between PUCCH and PUSCH, for example, the terminal is not configured with uci-MuxWithDiffPrio), the terminal discards PUCCH#1, PUCCH#2 and PUSCH#1, and transmits PUCCH#3 and PUSCH#2 respectively.

[0283] Or, optionally, the terminal does not expect this scenario.

[0284] 2. If the terminal is also enabled with simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, and multiplexing between different priorities is not enabled (including multiplexing between PUCCH and PUCCH of different priorities or between PUCCH and PUSCH, for example, the terminal is not configured with uci-MuxWithDiffPrio), the terminal discards PUCCH#2 and transmits the above-mentioned PUCCH#1, PUCCH#3 and PUSCH#1, PUSCH#2 respectively; or , the terminal multiplexes the UCI carried by PUCCH#2 on one of PUSCH#1 and PUSCH#2, for example, multiplexes it on PUSCH#2, and transmits PUCCH#1, PUCCH#3 and PUSCH#1, PUSCH#2 respectively; or, the terminal multiplexes the UCI carried by PUCCH#3 on one of PUSCH#1 and PUSCH#2, for example, multiplexes it on PUSCH#2, and transmits PUCCH#1, PUCCH#2 and PUSCH#1, PUSCH#2 respectively.

[0285] Or, optionally, the terminal does not expect this scenario.

[0286] 3. If the terminal is also enabled with multiplexing between different priorities (including multiplexing between PUCCH and PUSCH of different priorities), for example, the terminal is configured with uci-MuxWithDiffPrio, and the terminal is not enabled with simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, the terminal will multiplex the UCI on PUCCH#2 and PUCCH#3 on one PUCCH. Assume that the multiplexed PUCCH is PUCCH#R, where PUCCH#R (whose priority index is 1) can overlap with PUSCH#1. If it overlaps with PUSCH 1, the UCI carried by PUCCH#R will be multiplexed on PUSCH#1, and PUCCH#1, PUSCH#1 and PUSCH#2 will be transmitted respectively. If PUCCH#R does not overlap with PUSCH#1, PUCCH#1, PUCCH#R, PUSCH#1 and PUSCH#2 will be transmitted respectively.

[0287] 4. If the terminal is also enabled with multiplexing between different priorities, including multiplexing between PUCCHs of different priorities and PUCCHs or between PUCCHs and PUSCHs, for example, the terminal is configured with uci-MuxWithDiffPrio) and simultaneous transmission of PUCCHs and PUSCHs of different priorities on different cells under inter-band carrier aggregation, the terminal multiplexes PUCCH#2 and PUCCH#3. Assume that the multiplexed PUCCH is PUCCH#R (high priority), where PUCCH#R can be transmitted simultaneously with PUSCH (i.e., meeting the requirements of inter-band, different cells (such as CC)). Optionally, PUCCH#R can overlap with PUSCH#1 and / or PUSCH#2, and the terminal transmits PUCCH#1, PUCCH#R and PUSCH#1, PUSCH#2 respectively.

[0288] It should be noted that the premise of the embodiment of the present application is that the Pcell and the Scell ​​are already in different bands and can be transmitted simultaneously in interband.

[0289] It should be noted that the embodiment of the present application provides a terminal capability reporting and an overlap processing method, which can alleviate some existing scheduling restrictions to improve the flexibility and throughput of the system.

[0290] like Figure 7 As shown, the embodiment of the present application provides an information transmission method, including:

[0291] Step 701: A network side device receives terminal capability information sent by a terminal, where the terminal capability information is used to indicate whether the terminal supports transmission of physical uplink control channels PUCCH and physical uplink shared channels PUSCH of the same priority on different cells under carrier aggregation.

[0292] Optionally, the PUCCH includes hybrid automatic repeat request acknowledgement HARQ-ACK information.

[0293] Optionally, the method further includes:

[0294] The network side device sends a first configuration parameter to the terminal;

[0295] The first configuration parameter is used to enable simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under carrier aggregation of the terminal.

[0296] Optionally, the method further includes:

[0297] The network side device sends a second configuration parameter to the terminal;

[0298] The second configuration parameter is used to enable transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation of the terminal.

[0299] It should be noted that all descriptions about the network side device side in the above embodiments are applicable to the embodiments of the information transmission method applied to the network side device side, and can achieve the same technical effects, and will not be repeated here.

[0300] The information transmission method provided in the embodiment of the present application can be executed by an information transmission device. In the embodiment of the present application, the information transmission device provided in the embodiment of the present application is described by taking the information transmission method executed by the information transmission device as an example.

[0301] like Figure 8 As shown, the information transmission device 800 of the embodiment of the present application is applied to a terminal, including:

[0302] The first sending module 801 is used to send terminal capability information to a network side device, where the terminal capability information is used to indicate whether the terminal supports simultaneous transmission of physical uplink control channels PUCCH and physical uplink shared channels PUSCH of the same priority on different cells under carrier aggregation.

[0303] Optionally, the PUCCH includes hybrid automatic repeat request acknowledgement HARQ-ACK information.

[0304] Optionally, the device further comprises:

[0305] A second receiving module, used to receive a first configuration parameter sent by the network side device;

[0306] The first configuration parameter is used to enable simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under carrier aggregation of the terminal.

[0307] Optionally, the device further comprises at least one of the following:

[0308] A first processing module, used for processing overlap between PUCCHs of the same priority;

[0309] A second processing module, used for processing overlap between PUCCH and PUSCH of the same priority;

[0310] A third processing module, used for processing overlap between PUCCHs of different priorities;

[0311] The fourth processing module is used to process the overlap between PUCCH and PUSCH of different priorities.

[0312] Optionally, the device further comprises:

[0313] A first execution module, configured to multiplex the first PUCCH with one or more PUSCHs in the at least one PUSCH when the first PUCCH overlaps with the at least one PUSCH;

[0314] The first PUCCH and the at least one PUSCH have the same priority; and the at least one PUSCH cannot be transmitted simultaneously with the first PUCCH.

[0315] Optionally, the device further comprises:

[0316] A second execution module, configured to multiplex the second PUCCH with at least one PUSCH in the target PUSCH when the second PUCCH overlaps with multiple PUSCHs;

[0317] The second PUCCH and the multiple PUSCHs have the same priority, the target PUSCH is a PUSCH among the multiple PUSCHs that does not support simultaneous transmission with the second PUCCH, or the target PUSCH is a PUSCH among the multiple PUSCHs excluding the PUSCH that can be transmitted simultaneously with the second PUCCH.

[0318] Optionally, the device further comprises:

[0319] A first transmission module, configured to transmit the third PUCCH and the first PUSCH respectively when the third PUCCH overlaps with the first PUSCH;

[0320] The third PUCCH and the first PUSCH have the same priority; the first PUSCH can be transmitted simultaneously with the third PUCCH.

[0321] Optionally, the device further comprises:

[0322] an acquisition module, configured to multiplex the fourth PUCCH and the fifth PUCCH to acquire a sixth PUCCH when the fourth PUCCH overlaps with the fifth PUCCH, and the fourth PUCCH and the fifth PUCCH have different priorities;

[0323] The second transmission module is used for, when the sixth PUCCH overlaps with the second PUSCH, the terminal will transmit the sixth PUCCH and the second PUSCH respectively, wherein the sixth PUCCH and the second PUSCH have the same priority; the second PUSCH can be transmitted simultaneously with the sixth PUCCH.

[0324] Optionally, the device further comprises:

[0325] A third receiving module, used to receive a second configuration parameter sent by the network side device;

[0326] The second configuration parameter is used to enable simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under carrier aggregation of the terminal.

[0327] Optionally, the device further comprises:

[0328] A third transmission module, configured to transmit the seventh PUCCH and the third PUSCH respectively when the seventh PUCCH and the third PUSCH overlap;

[0329] The priorities of the seventh PUCCH and the third PUSCH are different; the third PUSCH can be transmitted simultaneously with the seventh PUCCH.

[0330] Optionally, the terminal supports simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under carrier aggregation.

[0331] It should be noted that the device embodiment is a device corresponding to the above-mentioned method, and all implementation methods in the above-mentioned method embodiment are applicable to the device embodiment and can achieve the same technical effect, which will not be repeated here.

[0332] The information transmission device in the embodiment of the present application may be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device may be a terminal, or may be other devices other than a terminal. For example, the terminal may include but is not limited to the types of terminals 11 listed above, and other devices may be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiment of the present application.

[0333] An embodiment of the present application also provides a terminal, including a processor and a communication interface, wherein the communication interface is used to send terminal capability information to a network side device, and the terminal capability information is used to indicate whether the terminal supports the simultaneous transmission of physical uplink control channels PUCCH and physical uplink shared channels PUSCH of the same priority on different cells under carrier aggregation.

[0334] Optionally, the PUCCH includes hybrid automatic repeat request acknowledgement HARQ-ACK information.

[0335] Optionally, the communication interface is further used for:

[0336] Receiving a first configuration parameter sent by the network side device;

[0337] The first configuration parameter is used to enable simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under carrier aggregation of the terminal.

[0338] Optionally, the processor is further configured to implement at least one of the following:

[0339] Handling overlap between PUCCHs of the same priority;

[0340] Handling overlap between PUCCH and PUSCH of the same priority;

[0341] Handling overlap between PUCCHs of different priorities;

[0342] Handle the overlap between PUCCH and PUSCH of different priorities.

[0343] Optionally, the processor is configured to:

[0344] In a case where the first PUCCH overlaps with at least one PUSCH, multiplexing the first PUCCH with one or more PUSCHs of the at least one PUSCH;

[0345] The first PUCCH and the at least one PUSCH have the same priority; and the at least one PUSCH cannot be transmitted simultaneously with the first PUCCH.

[0346] Optionally, the processor is further configured to:

[0347] In a case where the second PUCCH overlaps with multiple PUSCHs, multiplexing the second PUCCH with at least one PUSCH in the target PUSCH;

[0348] The second PUCCH and the multiple PUSCHs have the same priority, the target PUSCH is a PUSCH among the multiple PUSCHs that does not support simultaneous transmission with the second PUCCH, or the target PUSCH is a PUSCH among the multiple PUSCHs excluding the PUSCH that can be transmitted simultaneously with the second PUCCH.

[0349] Optionally, the communication interface is further used for:

[0350] In a case where the third PUCCH overlaps with the first PUSCH, transmitting the third PUCCH and the first PUSCH respectively;

[0351] The third PUCCH and the first PUSCH have the same priority; the first PUSCH can be transmitted simultaneously with the third PUCCH.

[0352] Optionally, the processor is further configured to:

[0353] In a case where the fourth PUCCH overlaps with the fifth PUCCH, multiplexing the fourth PUCCH and the fifth PUCCH to obtain a sixth PUCCH, wherein the fourth PUCCH and the fifth PUCCH have different priorities;

[0354] The communication interface is used for, when the sixth PUCCH overlaps with the second PUSCH, the terminal will transmit the sixth PUCCH and the second PUSCH respectively, wherein the sixth PUCCH and the second PUSCH have the same priority; the second PUSCH can be transmitted simultaneously with the sixth PUCCH.

[0355] Optionally, the communication interface is further used for:

[0356] Receiving a second configuration parameter sent by the network side device;

[0357] The second configuration parameter is used to enable simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under carrier aggregation of the terminal.

[0358] Optionally, the communication interface is further used for:

[0359] In the case where the seventh PUCCH overlaps with the third PUSCH, the seventh PUCCH and the third PUSCH will be transmitted respectively;

[0360] The priorities of the seventh PUCCH and the third PUSCH are different; the third PUSCH can be transmitted simultaneously with the seventh PUCCH.

[0361] Optionally, the terminal supports simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under carrier aggregation.

[0362] Preferably, the embodiment of the present application further provides a terminal, including a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements each process of the above-mentioned information transmission method embodiment and can achieve the same technical effect, which will not be described here to avoid repetition. Specifically, Fig. 9 A schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application.

[0363] The terminal 900 includes but is not limited to: a radio frequency unit 901, a network module 902, an audio output unit 903, an input unit 904, a sensor 905, a display unit 906, a user input unit 907, an interface unit 908, a memory 909 and at least some of the components of a processor 910.

[0364] Those skilled in the art will appreciate that the terminal 900 may also include a power source (such as a battery) for supplying power to various components, and the power source may be logically connected to the processor 910 through a power management system, thereby implementing functions such as managing charging, discharging, and power consumption management through the power management system. Fig. 9 The terminal structure shown in the figure does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be described in detail here.

[0365] It should be understood that in the embodiment of the present application, the input unit 904 may include a graphics processing unit (GPU) 9041 and a microphone 9042, and the graphics processor 9041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 906 may include a display panel 9061, and the display panel 9061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 907 includes a touch panel 9071 and at least one of other input devices 9092. The touch panel 9071 is also called a touch screen. The touch panel 9071 may include two parts: a touch detection device and a touch controller. Other input devices 9072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0366] In the embodiment of the present application, after receiving downlink data from the access network device, the radio frequency unit 901 can transmit the data to the processor 910 for processing; in addition, the radio frequency unit 901 can send uplink data to the network side device. Generally, the radio frequency unit 901 includes but is not limited to an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

[0367] The memory 909 can be used to store software programs or instructions and various data. The memory 909 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory 909 may include a volatile memory or a non-volatile memory, or the memory 909 may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM) and a direct memory bus random access memory (DRRAM). The memory 909 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0368] The processor 910 may include one or more processing units; optionally, the processor 910 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to an operating system, a user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 910.

[0369] Among them, the interface unit 908 is used to send terminal capability information to the network side device, and the terminal capability information is used to indicate whether the terminal supports the simultaneous transmission of physical uplink control channels PUCCH and physical uplink shared channels PUSCH of the same priority on different cells under carrier aggregation.

[0370] Optionally, the PUCCH includes hybrid automatic repeat request acknowledgement HARQ-ACK information.

[0371] Optionally, the interface unit 908 is further configured to:

[0372] Receiving a first configuration parameter sent by the network side device;

[0373] The first configuration parameter is used to enable simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under carrier aggregation of the terminal.

[0374] Optionally, the processor 910 is further configured to implement at least one of the following:

[0375] Handling overlap between PUCCHs of the same priority;

[0376] Handling overlap between PUCCH and PUSCH of the same priority;

[0377] Handling overlap between PUCCHs of different priorities;

[0378] Handle the overlap between PUCCH and PUSCH of different priorities.

[0379] Optionally, the processor 910 is configured to:

[0380] In a case where the first PUCCH overlaps with at least one PUSCH, multiplexing the first PUCCH with one or more PUSCHs of the at least one PUSCH;

[0381] The first PUCCH and the at least one PUSCH have the same priority; and the at least one PUSCH cannot be transmitted simultaneously with the first PUCCH.

[0382] Optionally, the processor 910 is further configured to:

[0383] In a case where the second PUCCH overlaps with multiple PUSCHs, multiplexing the second PUCCH with at least one PUSCH in the target PUSCH;

[0384] The second PUCCH and the multiple PUSCHs have the same priority, the target PUSCH is a PUSCH among the multiple PUSCHs that does not support simultaneous transmission with the second PUCCH, or the target PUSCH is a PUSCH among the multiple PUSCHs excluding the PUSCH that can be transmitted simultaneously with the second PUCCH.

[0385] Optionally, the interface unit 908 is further configured to:

[0386] In a case where the third PUCCH overlaps with the first PUSCH, transmitting the third PUCCH and the first PUSCH respectively;

[0387] The third PUCCH and the first PUSCH have the same priority; the first PUSCH can be transmitted simultaneously with the third PUCCH.

[0388] Optionally, the processor 910 is further configured to:

[0389] In a case where the fourth PUCCH overlaps with the fifth PUCCH, multiplexing the fourth PUCCH and the fifth PUCCH to obtain a sixth PUCCH, wherein the fourth PUCCH and the fifth PUCCH have different priorities;

[0390] The interface unit 908 is used for, when the sixth PUCCH overlaps with the second PUSCH, the terminal will transmit the sixth PUCCH and the second PUSCH respectively, wherein the sixth PUCCH and the second PUSCH have the same priority; the second PUSCH can be transmitted simultaneously with the sixth PUCCH.

[0391] Optionally, the interface unit 908 is further configured to:

[0392] Receiving a second configuration parameter sent by the network side device;

[0393] The second configuration parameter is used to enable simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under carrier aggregation of the terminal.

[0394] Optionally, the interface unit 908 is further configured to:

[0395] In the case where the seventh PUCCH overlaps with the third PUSCH, the seventh PUCCH and the third PUSCH will be transmitted respectively;

[0396] The priorities of the seventh PUCCH and the third PUSCH are different; the third PUSCH can be transmitted simultaneously with the seventh PUCCH.

[0397] Optionally, the terminal supports simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under carrier aggregation.

[0398] Preferably, an embodiment of the present application also provides a terminal, including a processor, a memory, and a program or instruction stored in the memory and executable on the processor. When the program or instruction is executed by the processor, each process of the above-mentioned information transmission method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0399] An embodiment of the present application also provides a computer-readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned information transmission method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0400] The computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0401] like Fig.10 As shown, the information transmission device 1000 of the embodiment of the present application is applied to a network side device, including:

[0402] The first receiving module 1001 is used to receive terminal capability information sent by a terminal, where the terminal capability information is used to indicate whether the terminal supports transmission of physical uplink control channels PUCCH and physical uplink shared channels PUSCH of the same priority on different cells under carrier aggregation.

[0403] Optionally, the PUCCH includes hybrid automatic repeat request acknowledgement HARQ-ACK information.

[0404] Optionally, the device further comprises:

[0405] A second sending module, used to send a first configuration parameter to the terminal;

[0406] The first configuration parameter is used to enable simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under carrier aggregation of the terminal.

[0407] Optionally, the device further comprises:

[0408] A third sending module, used to send a second configuration parameter to the terminal;

[0409] The second configuration parameter is used to enable transmission of PUCCH and PUSCH of different priorities on different cells under carrier aggregation of the terminal.

[0410] It should be noted that the device embodiment corresponds to the above method, and all implementation methods in the above method embodiment are applicable to the device embodiment and can achieve the same technical effect.

[0411] The communication processing device provided in the embodiment of the present application can realize Figure 7The various processes implemented by the method embodiment and achieving the same technical effect are not described here to avoid repetition.

[0412] An embodiment of the present application also provides a network side device, including a processor and a communication interface, wherein the communication interface is used to receive terminal capability information sent by a terminal, and the terminal capability information is used to indicate whether the terminal supports the transmission of physical uplink control channels PUCCH and physical uplink shared channels PUSCH of the same priority on different cells under carrier aggregation.

[0413] Optionally, the PUCCH includes hybrid automatic repeat request acknowledgement HARQ-ACK information.

[0414] Optionally, the communication interface is further used for:

[0415] Sending a first configuration parameter to the terminal;

[0416] The first configuration parameter is used to enable simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under carrier aggregation of the terminal.

[0417] Optionally, the communication interface is further used for:

[0418] Sending a second configuration parameter to the terminal;

[0419] The second configuration parameter is used to enable transmission of PUCCH and PUSCH of different priorities on different cells under carrier aggregation of the terminal.

[0420] Specifically, the embodiment of the present application also provides a network side device. Fig.11 As shown, the network side device 1100 includes: an antenna 1101, a radio frequency device 1102, a baseband device 1103, a processor 1104 and a memory 1105. The antenna 1101 is connected to the radio frequency device 1102. In the uplink direction, the radio frequency device 1102 receives information through the antenna 1101 and sends the received information to the baseband device 1103 for processing. In the downlink direction, the baseband device 1103 processes the information to be sent and sends it to the radio frequency device 1102. The radio frequency device 1102 processes the received information and sends it out through the antenna 1101.

[0421] The method executed by the network-side device in the above embodiment may be implemented in the baseband device 1103, which includes a baseband processor.

[0422] The baseband device 1103 may include, for example, at least one baseband board on which a plurality of chips are arranged. Fig.11As shown, one of the chips is, for example, a baseband processor, which is connected to the memory 1105 through a bus interface to call the program in the memory 1105 to execute the network device operations shown in the above method embodiment.

[0423] The network side device may further include a network interface 1106, which is, for example, a common public radio interface (CPRI).

[0424] Specifically, the network side device 1100 of the embodiment of the present application further includes: instructions or programs stored in the memory 1105 and executable on the processor 1104, and the processor 1104 calls the instructions or programs in the memory 1105 to execute Fig.10 The methods executed by the modules shown achieve the same technical effects, and therefore will not be described here in detail to avoid repetition.

[0425] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned information transmission method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0426] The processor is a processor in the access network device described in the above embodiment. The readable storage medium may be non-volatile or non-transient. The readable storage medium may include a computer-readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk.

[0427] Optional, such as Fig.12 As shown, the embodiment of the present application also provides a communication device 1200, including a processor 1201 and a memory 1202, and the memory 1202 stores a program or instruction that can be run on the processor 1201. For example, when the communication device 1200 is a terminal, the program or instruction is executed by the processor 1201 to implement the various steps of the above-mentioned information transmission method embodiment, and can achieve the same technical effect. When the communication device 1200 is a network side device, the program or instruction is executed by the processor 1201 to implement the various steps of the above-mentioned information transmission method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0428] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned information transmission method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0429] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0430] The embodiments of the present application further provide a computer program / program product, which is stored in a storage medium, and is executed by at least one processor to implement the various processes of the above-mentioned information transmission method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0431] An embodiment of the present application also provides a communication system, including: a terminal and a network side device, wherein the terminal can be used to execute the steps of the above-mentioned information transmission method, and the network side device can be used to execute the steps of the above-mentioned information transmission processing method.

[0432] An embodiment of the present application also provides a communication system, including: a terminal and a network side device, wherein the terminal can be used to execute the steps of the above-mentioned information transmission method, and the network side device can be used to execute the steps of the above-mentioned information transmission method.

[0433] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises one..." does not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the method and device in the embodiment of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0434] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general hardware platform, and of course, can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, disk, CD, etc.), including several instructions to enable a terminal or a network-side device to execute the methods described in each embodiment of the present application.

[0435] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of the present application and the scope of protection of the claims, and these implementation methods are all within the protection of the present application.

Claims

1. An information transmission method, characterized in that: include: The terminal sends terminal capability information to a network side device, where the terminal capability information is used to indicate whether the terminal supports simultaneous transmission of physical uplink control channels PUCCH and physical uplink shared channels PUSCH of the same priority on different cells under carrier aggregation.

2. The method according to claim 1, characterized in that: The PUCCH includes hybrid automatic repeat request acknowledgement HARQ-ACK information.

3. The method according to claim 1 or 2, characterized in that: Also includes: The terminal receives a first configuration parameter sent by the network side device; The first configuration parameter is used to enable simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under carrier aggregation of the terminal.

4. The method according to claim 3, characterized in that Also includes at least one of the following: The terminal processes overlap between PUCCHs of the same priority; The terminal processes overlap between PUCCH and PUSCH of the same priority; The terminal processes overlap between PUCCHs of different priorities; The terminal handles the overlap between PUCCH and PUSCH of different priorities.

5. The method according to claim 3, characterized in that: Also includes: In a case where the first PUCCH overlaps with at least one PUSCH, the terminal multiplexes the first PUCCH with one or more PUSCHs of the at least one PUSCH; The first PUCCH and the at least one PUSCH have the same priority; and the at least one PUSCH cannot be transmitted simultaneously with the first PUCCH.

6. The method according to claim 3, characterized in that Also includes: In a case where the second PUCCH overlaps with multiple PUSCHs, the terminal multiplexes the second PUCCH with at least one PUSCH in the target PUSCH; The second PUCCH and the multiple PUSCHs have the same priority, the target PUSCH is a PUSCH among the multiple PUSCHs that does not support simultaneous transmission with the second PUCCH, or the target PUSCH is a PUSCH among the multiple PUSCHs excluding the PUSCH that can be transmitted simultaneously with the second PUCCH.

7. The method according to claim 3, characterized in that Also includes: In a case where the third PUCCH overlaps with the first PUSCH, the terminal transmits the third PUCCH and the first PUSCH respectively; The third PUCCH and the first PUSCH have the same priority; the first PUSCH can be transmitted simultaneously with the third PUCCH.

8. The method according to claim 3, characterized in that Also includes: In a case where the fourth PUCCH overlaps with the fifth PUCCH, the terminal multiplexes the fourth PUCCH and the fifth PUCCH to obtain a sixth PUCCH, and the fourth PUCCH and the fifth PUCCH have different priorities; In the case that the sixth PUCCH overlaps with the second PUSCH, the terminal will transmit the sixth PUCCH and the second PUSCH respectively, wherein the sixth PUCCH and the second PUSCH have the same priority; the second PUSCH can be transmitted simultaneously with the sixth PUCCH.

9. The method according to any one of claims 3 to 8, characterized in that: Also includes: The terminal receives a second configuration parameter sent by the network side device; The second configuration parameter is used to enable simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under carrier aggregation of the terminal.

10. The method according to any one of claims 3 to 9, characterized in that: Also includes: In the case where the seventh PUCCH overlaps with the third PUSCH, the terminal transmits the seventh PUCCH and the third PUSCH respectively; The priorities of the seventh PUCCH and the third PUSCH are different; the third PUSCH can be transmitted simultaneously with the seventh PUCCH.

11. The method according to any one of claims 1 to 10, characterized in that: The terminal supports simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under carrier aggregation.

12. An information transmission method, characterized in that: include: The network side device receives terminal capability information sent by the terminal, where the terminal capability information is used to indicate whether the terminal supports transmission of physical uplink control channels PUCCH and physical uplink shared channels PUSCH of the same priority on different cells under carrier aggregation.

13. The method according to claim 12, characterized in that The PUCCH includes hybrid automatic repeat request acknowledgement HARQ-ACK information.

14. The method according to claim 12 or 13, characterized in that Also includes: The network side device sends a first configuration parameter to the terminal; The first configuration parameter is used to enable simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under carrier aggregation of the terminal.

15. The method according to claim 14, characterized in that Also includes: The network side device sends a second configuration parameter to the terminal; The second configuration parameter is used to enable transmission of PUCCH and PUSCH of different priorities on different cells under carrier aggregation of the terminal.

16. An information transmission device, applied to a terminal, characterized in that: include: The first sending module is used to send terminal capability information to a network side device, where the terminal capability information is used to indicate whether the terminal supports simultaneous transmission of physical uplink control channels PUCCH and physical uplink shared channels PUSCH of the same priority on different cells under carrier aggregation.

17. A terminal, characterized in that: The method comprises a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the information transmission method according to any one of claims 1 to 11 are implemented.

18. An information transmission device, applied to a network side device, characterized in that: include: The first receiving module is used to receive terminal capability information sent by the terminal, where the terminal capability information is used to indicate whether the terminal supports transmission of physical uplink control channels PUCCH and physical uplink shared channels PUSCH of the same priority on different cells under carrier aggregation.

19. A network side device, characterized in that: It comprises a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the information transmission method as described in any one of claims 12 to 15 are implemented.

20. A readable storage medium, characterized in that: The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, the steps of the information transmission method according to any one of claims 1 to 11 or the steps of the information transmission method according to any one of claims 12 to 15 are implemented.

Images