Information transmission method and apparatus, terminal, and network side device

Abstract

The present application relates to the technical field of communications, and discloses an information transmission method and apparatus, a terminal, and a network side device. The information transmission method in embodiments of the present application comprises: a terminal sends terminal capability information to a network side device, the terminal capability information being used for indicating whether the terminal supports simultaneous transmission of a physical uplink control channel (PUCCH) and a physical uplink shared channel (PUSCH) having the same priority in different cells under carrier aggregation.

Description

Information transmission method, device, terminal and network side equipment

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the China Patent Office on November 2, 2023, with application number 202311450284.X and invention name “Information Transmission Method, Device, Terminal and Network Side Equipment”, the entire contents of which are incorporated by reference into this application. Technical Field

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

[0004] New Radio (NR) supports multiplexing of the Physical Uplink Control Channel (PUCCH) and PUCCH or PUCCH and Physical Uplink Shared Channel (PUSCH) of the same or different priorities, prioritization of PUCCH and PUCCH or PUCCH and PUSCH of different priorities, and simultaneous transmission of PUCCH and PUSCH of different priorities across different serving cells in the inter-band. However, there are some restrictions on the scheduling of PUCCH and PUSCH. These scheduling restrictions can cause significant system throughput loss in actual network deployments.

[0005] Summary of the Invention

[0006] 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.

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

[0008] The terminal sends terminal capability information to the 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.

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

[0010] The first sending module is used to send terminal capability information to the 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.

[0011] In a third aspect, a method for transmitting information is provided, the method comprising:

[0012] 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.

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

[0014] 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.

[0015] 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 run 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.

[0016] 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.

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

[0018] 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 the 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.

[0019] 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.

[0020] 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.

[0021] In the eleventh aspect, a chip is provided, 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 steps of the method described in the first aspect or the third aspect.

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

[0023] 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

[0024] FIG1 is a block diagram of a wireless communication system to which embodiments of the present application may be applied;

[0025] FIG2 is a flow chart of an information transmission method according to an embodiment of the present application;

[0026] FIG3 is a schematic diagram of existing scheduling constraints;

[0027] FIG4 is a transmission diagram of an embodiment of the present application;

[0028] FIG5 is a second transmission diagram of an embodiment of the present application;

[0029] FIG6 is a third transmission diagram of an embodiment of the present application;

[0030] FIG7 is a second flow chart of the information transmission method according to an embodiment of the present application;

[0031] FIG8 is a schematic diagram of a module of an information transmission device according to an embodiment of the present application;

[0032] FIG9 is a schematic structural diagram of a terminal according to an embodiment of the present application;

[0033] FIG10 is a second schematic diagram of a module of an information transmission device according to an embodiment of the present application;

[0034] FIG11 is a schematic structural diagram of a network-side device according to an embodiment of the present application;

[0035] FIG12 is a schematic structural diagram of a communication device according to an embodiment of the present application. DETAILED DESCRIPTION

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

[0037] The terms "first", "second", etc. in this 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 the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0038] The term "indication" in this application can be either 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, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.

[0039] 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 technology described 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 the NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as the 6th generation (6G) system. th Generation, 6G) communication system.

[0040] FIG1 is a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device (Wearable Device), an aircraft (Flight Vehicle), a vehicle-mounted device (VUE), a ship-mounted device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), a game console, a personal computer (PC), an ATM, or a self-service machine, or 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 called 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 (WLAN) access point (AP) or a wireless fidelity (WiFi) node, etc.Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B (home evolved Node B), 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 vocabulary. It should be noted that in the embodiment 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.

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

[0042] Compared to previous mobile communication systems, future 5G mobile communication systems will need to adapt to more diverse scenarios and service requirements. Key 5G scenarios include enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine type communication (mMTC). These scenarios place high reliability, low latency, large bandwidth, and wide coverage requirements on the system. Some user equipment (UE) may support different services, such as supporting both URLLC and high-capacity, high-rate eMBB services. In New Radio (NR) systems, because different channels can have different starting symbols and lengths, transmission resources may overlap in the time domain. Typically, to maintain the uplink single-carrier characteristic, when multiple overlapping physical uplink control channels (PUCCHs) are transmitted in a timeslot, this single-carrier characteristic is compromised, and the varying transmit powers can degrade channel estimation performance. This situation is usually regarded as a conflict, and corresponding conflict resolution methods need to be designed to merge or discard some information.

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

[0044] Uplink Control Information (UCI) is mainly transmitted on the uplink control channel (for example, PUCCH). Uplink data is transmitted on the uplink data channel (for example, PUSCH). Due to reasons such as flexible configuration or indication of the starting symbol and symbol length, temporal overlap may occur 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 the uplink transmission; in addition, if the out-of-band emission requirements are to be met at a higher transmit power, and the PUSCH and PUCCH are transmitted simultaneously with a large interval in the frequency domain (PUCCH is generally transmitted at both ends of the frequency band), this will bring challenges to the implementation of the 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 with the PUSCH resources in time, 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.

[0045] Currently, a timeline is defined for multiplexing PUCCHs or PUCCHs with PUSCHs. This means that multiplexing between PUCCHs or UCI multiplexing on PUSCHs must meet a predefined timeline. If the network-side scheduling does not meet this timeline, it is considered an error case.

[0046] In addition, considering the complexity of multiplexing and coding, NR has some restrictions on 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 PUCCHs carrying the same type of UCI in multiple time slots on one PUSCH.

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

[0048] Within a PUCCH group, multiple PUCCHs may overlap, and a PUCCH may also overlap with multiple PUSCHs. To address the time domain resource overlap between multiple uplink transmission channels, NR defines the processing order of UE uplink multiplexing in one case, specifically:

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

[0050] 2) For a PUCCH output 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 onto one of the overlapping PUSCHs according to certain rules. If the PUCCH overlaps with only one PUSCH, the UCI (excluding the SR) is multiplexed onto the PUSCH. If the PUCCH overlaps with multiple PUSCHs, the UE selects one PUSCH for multiplexing according to the corresponding rules. The rules are as follows:

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

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

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

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

[0055] e) Fifth priority: PUSCH transmitted earlier > PUSCH transmitted later.

[0056] 1.2 Multiplexing and Prioritization of Uplink Transmissions within the UE in the Second Case

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

[0058] For high priority (HP) uplink transmission vs. high priority uplink transmission, the UE handles it in the same way as the first case.

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

[0060] 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.

[0061] 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.

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

[0063] 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, NR defines the order of UE uplink conflict handling in this case, specifically:

[0064] 1) Within 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.

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

[0066] 3) If there are multiple HP PUCCHs / PUSCHs, the overlap between high-priority PUCCHs / PUSCHs is first resolved using the method of the first case.

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

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

[0069] To reduce the impact on low-priority uplink transmissions, 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 across the bandwidth. It also supports multiplexing of PUCCH and PUCCH of different priorities, or PUCCH and PUSCH of different priorities.

[0070] 1.3.1 Processing order between PUCCHs or PUCCH and PUSCH multiplexing

[0071] 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, NR defines the order of UE uplink conflict handling in this case, specifically:

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

[0073] 2) The UE resolves the overlap between PUCCHs of different priorities. For PUCCHs of different priorities, it 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.

[0074] 3) The UE resolves the overlap between PUCCH and PUSCH of different priorities, supporting 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 PUSCHs 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 CSI part 2 is present on the HP PUSCH).

[0075] Existing technologies support overlapping PUCCH and PUSCH time domain resources, including multiplexing, prioritization, and simultaneous transmission. However, there are still some limitations, such as priority and the number of PUCCHs that overlap with PUSCH. In actual network deployments, such as carrier aggregation (CA) scenarios, where the primary cell (Pcell) uses time division duplex (TDD) with a subcarrier spacing (SCS) of 30 kHz and the secondary cell (Scell) uses frequency division duplex (FDD) with an SCS of 15 kHz, and PUCCH is transmitted in the PCell and PUSCH in the Scell, scheduling two PUCCHs carrying HARQ-ACK feedback in different time slots to overlap with a single PUSCH is prohibited. Such scheduling restrictions can result in significant system throughput loss. One solution is for the base station to schedule PUCCH and PUSCH with different priorities and enable simultaneous transmission of PUCCH and PUSCH at different priorities. However, this requires the UE to support DCI indicating PUCCH / PUSCH priority, which means coupling different technical features. However, the technical feature of DCI indicating different priorities is not a critical 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 handling of uplink channel overlap and interoperability with other features, such as multiplexing / simultaneous transmission of PUCCH and PUSCH of different priorities, need to be considered.

[0076] 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 some embodiments and their application scenarios in conjunction with the accompanying drawings.

[0077] As shown in FIG2 , an embodiment of the present application provides an information transmission method, including:

[0078] In 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 physical uplink control channels (PUCCH) and physical uplink shared channels (PUSCH) of the same priority on different cells under carrier aggregation.

[0079] It should be noted that by indicating the terminal capability information to the network side device, 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, which can avoid the loss of system throughput caused by scheduling restrictions as much as possible.

[0080] 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:

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

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

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

[0084] 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.

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

[0086] Optionally, this situation can be understood as the capability of supporting simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under inter-bandwidth carrier aggregation, which is premised on the terminal needing to support simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, that is, the terminal capable of supporting simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under inter-bandwidth carrier aggregation, necessarily / must support simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation;

[0087] Optionally, this situation can be understood as a terminal capable of supporting 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 simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under intra-bandwidth carrier aggregation.

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

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

[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 of the terminal.

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

[0092] 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 the bandwidths of the terminal;

[0093] 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.

[0094] 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 (RRC) parameters.

[0095] 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.

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

[0097] Method 1:

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

[0099] 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;

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

[0101] 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 not meeting the requirements of different serving cells between bandwidths; for example, if the cell where the first PUCCH and at least one PUSCH are located is in the same bandwidth (band), then the at least one PUSCH and the first PUCCH do not meet the requirements of different serving cells between bandwidths; or,

[0102] 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 not meeting 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.

[0103] 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 with the time domain of at least one PUSCH.

[0104] 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, then 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 existing technologies and is not limited in this application.

[0105] 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.

[0106] Method 2:

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

[0108] 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;

[0109] 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.

[0110] 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.

[0111] 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, and PUSCH2 and PUSCH3 can both be transmitted simultaneously with PUCCH1. The terminal then 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.

[0112] Method 3:

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

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

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

[0116] 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 serving cells between bandwidths. For example, the first PUSCH and the third PUCCH are located in different serving cells with different bandwidths, then the first PUSCH and the third PUCCH meet the requirements of different serving cells between bandwidths; or,

[0117] 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.

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

[0119] 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 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 simultaneously. Optionally, the simultaneous transmission here can be understood as: transmitting the PUCCH and PUSCH at their respective resource positions.

[0120] Method 4:

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

[0122] 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, where the fourth PUCCH and the fifth PUCCH have different priorities;

[0123] 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.

[0124] 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 serving cells between bandwidths. For example, the second PUSCH and the sixth PUCCH are located in different serving cells with different bandwidths, then the second PUSCH and the sixth PUCCH meet the requirements of different serving cells between bandwidths; or

[0125] 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.

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

[0127] This situation can be understood as follows: if there is an overlap of multiple PUCCHs of different priorities, these PUCCHs can be multiplexed to obtain a multiplexed PUCCH, which has a specific priority, for example, the multiplexed PUCCH is 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 separately.

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

[0129] Method 5:

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

[0131] In the case where the seventh PUCCH overlaps with the third PUSCH, the terminal shall transmit the seventh PUCCH and the third PUSCH separately;

[0132] The seventh PUCCH and the third PUSCH have different priorities; the third PUSCH can be transmitted simultaneously with the seventh PUCCH.

[0133] 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 serving cells between bandwidths. For example, the third PUSCH and the seventh PUCCH are located in different bandwidths and different serving cells, then the third PUSCH and the seventh PUCCH meet the requirements of different serving cells between bandwidths; or

[0134] 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.

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

[0136] This situation can be understood as follows: if a PUCCH overlaps with one or more PUSCHs, the priorities of the PUCCH and the one or more PUSCHs are different, 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.

[0137] 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:

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

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

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

[0141] 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;

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

[0143] 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, and 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.

[0144] 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, the method further includes at least one of the following:

[0145] A11. The terminal processes overlap between PUCCHs of the same priority;

[0146] A12. The terminal processes overlap between PUCCH and PUSCH of the same priority;

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

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

[0149] It should be noted that the above-mentioned implementations can be used in any combination in specific applications. 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 of the same priority and PUSCHs, 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:

[0150] Step 1: Handle the overlap between PUCCHs of the same priority level.

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

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

[0153] 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 between PUCCH and PUSCH of different priorities;

[0154] 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.

[0155] 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;

[0156] 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.

[0157] 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 to illustrate the specific application of the embodiment of the present application.

[0158] The deployment scenario of the embodiment to which the present application can be applied is an 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 a 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, where its PCell is in a time division duplex (TDD) frequency band, its SCS is configured to 30 kHz, and the SCell is in a frequency division duplex (FDD) frequency band, and its SCS is configured to 15 kHz.

[0159] The existing scheduling restrictions are as follows: As shown in Figure 3, if the base station schedules a PUSCH in a time slot on the secondary cell (Scell), and its time domain resources overlap with the 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.

[0160] 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 serving cells in inter-band. This 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.

[0161] Optionally, this capability may be for HARQ-ACK transmission only, i.e., 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 (e.g., the PUCCH only contains CSI or SR), simultaneous transmission of PUCCH and PUSCH of the same priority on different cells under inter-bandwidth carrier aggregation is not supported.

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

[0163] 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-layer 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 these 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.

[0164] Under the above solution, the terminal handles the overlap of PUCCH and PUSCH as follows: when the terminal is enabled with 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, then the base station schedules / configures multiple PUCCHs in these two slots to carry the same type of UCI (such as HARQ-ACK feedback information), and these multiple PUCCHs all overlap with the PUSCH.

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

[0166] Step 1: The terminal handles the overlap between channels of the same priority level.

[0167] Step 1-1: The terminal processes PUCCHs of the same priority and overlaps PUCCHs;

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

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

[0170] Step 2-1: The terminal processes PUCCHs of different priorities and overlaps PUCCHs;

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

[0172] 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 onto PUSCH of the same priority, and the terminal excludes PUSCH that supports simultaneous transmission with PUCCH (UCI is multiplexed onto PUSCH that does not support simultaneous transmission with PUCCH, if any).

[0173] 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.

[0174] 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).

[0175] 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.

[0176] Application scenario 1: The time domain resources of one PUSCH and two PUCCHs carrying the same UCI type (such as HARQ-ACK) in different time slots overlap, as shown in Figure 4 and Table 1.

[0177] Table 1 PUCCH and PUSCH transmission position and priority correspondence table for the following application scenarios

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

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

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

[0181] 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

[0182] This situation specifically includes one of the following:

[0183] 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 separately;

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

[0185] 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;

[0186] 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)

[0187] 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.

[0188] 3. If the terminal is enabled for 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;

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

[0190] 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.

[0191] 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

[0192] This situation specifically includes one of the following:

[0193] 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 separately;

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

[0195] 2. If the terminal is enabled to simultaneously transmit PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, the terminal simultaneously transmits the above-mentioned PUCCH#1, PUCCH#2 and PUSCH#1 respectively.

[0196] 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.

[0197] 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 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.

[0198] 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

[0199] This situation specifically includes one of the following:

[0200] 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 separately.

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

[0202] 2. If the terminal is enabled to simultaneously transmit PUCCH and PUSCH of different priorities on different cells under inter-bandwidth carrier aggregation, the terminal simultaneously transmits the above-mentioned PUCCH#1, PUCCH#2 and PUSCH#1 respectively.

[0203] 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 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 on PUSCH#1 for transmission, and cancels the transmission of PUCCH#2.

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

[0205] 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 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.

[0206] 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

[0207] This situation specifically includes one of the following:

[0208] 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.

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

[0210] 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.

[0211] 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 on PUSCH#1 for transmission, and transmits PUCCH#1 and PUSCH#1 separately.

[0212] 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 not configured with uci-MuxWithDiffPrio) and 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, or the terminal multiplexes the UCI on PUCCH#1 or PUCCH#2 to PUSCH#1 for transmission.

[0213] To sum up, 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.

[0214] 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 the same time slot and have different priority indexes.

[0215] Case 2-1: The priority index of PUCCH#1 is 1, and the priority index of PUSCH#1 is 0, as shown in FIG5 and Table 2.

[0216] Table 2 PUCCH and PUSCH transmission position and priority correspondence table 1 under application scenario 2

[0217] This situation specifically includes one of the following:

[0218] 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.

[0219] Alternatively, the terminal does not expect the scenario to occur.

[0220] 2. If the terminal is also enabled for 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.

[0221] Alternatively, the terminal does not expect the scenario to occur.

[0222] 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 simultaneous transmission of PUCCH and PUSCH 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.

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

[0224] 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), the terminal transmits PUCCH#1, PUCCH#R and PUSCH#1 respectively.

[0225] 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:

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

[0227] This situation specifically 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] Alternatively, the terminal does not expect the scenario to occur.

[0230] 2. If the terminal is also enabled for 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] Alternatively, 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 (its priority index is 1), optionally, PUCCH#R can overlap with PUSCH#1, the terminal multiplexes the UCI carried on PUCCH#1 onto PUSCH#1, and transmits PUCCH#R and PUSCH#1 separately;

[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 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), 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 scenario 2

[0237] This situation specifically includes one of the following:

[0238] 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;

[0239] Alternatively, the terminal does not expect the scenario to occur.

[0240] 2. If the terminal is also enabled for 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.

[0241] Alternatively, the terminal does not expect the scenario to occur.

[0242] 3. If the terminal is also enabled for multiplexing between different priorities (including multiplexing between PUCCHs of different priorities or between PUCCHs and PUSCHs), for example, the terminal is configured with uci-MuxWithDiffPrio, and the terminal is not enabled for simultaneous transmission of PUCCHs and PUSCHs 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 onto 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 onto PUSCH#1 and transmit PUCCH#R and PUSCH#1 separately.

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

[0244] 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), where PUCCH#R, if it can be transmitted simultaneously with PUSCH (inter-band, different cells (such as component carrier (CC))), the terminal transmits PUCCH#1, PUCCH#R and PUSCH#1 respectively (where PUCCH#R can overlap with PUSCH#1).

[0245] 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:

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

[0247] This situation specifically includes one of the following:

[0248] 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.

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

[0250] 2. If the terminal is also enabled for 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.

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

[0252] 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.

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

[0254] 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). 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.

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

[0256] Case 3-1: The priority indexes of PUSCH#1 and PUSCH#2 are both 0, as shown in Figure 6 and Table 6:

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

[0258] This situation specifically includes one of the following:

[0259] 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, PUSCH#1 and PUSCH#2, and transmits PUCCH#1 and PUCCH#3 respectively;

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

[0261] 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.

[0262] 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 PUCCH#1 transmission and transmits PUSCH#1 and PUSCH#2 respectively, or the terminal transmits PUCCH#1, PUSCH#1 and PUSCH#2 respectively.

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

[0264] 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.

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

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

[0267] This situation specifically includes one of the following:

[0268] 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.

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

[0270] 2. If the terminal is also enabled for 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.

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

[0272] 3. If the terminal is also enabled for 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 for 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 or not overlap with PUSCH#1 or PUSCH#2, and transmit PUCCH#1, PUCCH#R, PUSCH#1 and PUSCH#2 respectively.

[0273] 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.

[0274] 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:

[0275] Table 8 PUCCH and PUSCH transmission position and priority correspondence table 3 under application scenario 3

[0276] This situation specifically includes one of the following:

[0277] 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.

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

[0279] 2. If the terminal is also enabled for 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.

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

[0281] 3. If the terminal is also enabled for 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 for 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.

[0282] 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.

[0283] 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 transmit simultaneously while meeting the inter-band requirement.

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

[0285] As shown in FIG7 , an embodiment of the present application provides an information transmission method, including:

[0286] In 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.

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

[0288] Optionally, the method further includes:

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

[0290] 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.

[0291] Optionally, the method further includes:

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

[0293] 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.

[0294] 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, so they will not be repeated here.

[0295] 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.

[0296] As shown in FIG8 , an information transmission device 800 according to an embodiment of the present application, applied to a terminal, includes:

[0297] The first sending module 801 is used to send terminal capability information to the 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.

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

[0299] Optionally, the device further includes:

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

[0301] 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.

[0302] Optionally, the device further includes at least one of the following:

[0303] A first processing module, configured to process overlap between PUCCHs of the same priority;

[0304] The second processing module is used to process the overlap between PUCCH and PUSCH of the same priority;

[0305] A third processing module is used to process overlaps between PUCCHs of different priorities;

[0306] The fourth processing module is configured to process overlaps between PUCCHs and PUSCHs of different priorities.

[0307] Optionally, the device further includes:

[0308] A first execution module is 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;

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

[0310] Optionally, the device further includes:

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

[0312] 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.

[0313] Optionally, the device further includes:

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

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

[0316] Optionally, the device further includes:

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

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

[0319] Optionally, the device further includes:

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

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

[0322] Optionally, the device further includes:

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

[0324] The seventh PUCCH and the third PUSCH have different priorities; the third PUSCH can be transmitted simultaneously with the seventh PUCCH.

[0325] Optionally, the terminal supports simultaneous transmission of PUCCHs and PUSCHs of different priorities on different cells under carrier aggregation.

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

[0327] The information transmission device in the embodiments of the present application can 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 chip. The electronic device can be a terminal, or it can be other devices other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0328] 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 simultaneous transmission of physical uplink control channels PUCCH and physical uplink shared channels PUSCH of the same priority on different cells under carrier aggregation.

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

[0330] Optionally, the communication interface is further used to:

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

[0332] 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.

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

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

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

[0336] Handling overlap between PUCCHs of different priorities;

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

[0338] Optionally, the processor is configured to:

[0339] 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;

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

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

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

[0343] 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.

[0344] Optionally, the communication interface is further used to:

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

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

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

[0348] 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, where the fourth PUCCH and the fifth PUCCH have different priorities;

[0349] 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.

[0350] Optionally, the communication interface is further used to:

[0351] receiving a second configuration parameter sent by the network-side device;

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

[0353] Optionally, the communication interface is further used to:

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

[0355] The seventh PUCCH and the third PUSCH have different priorities; the third PUSCH can be transmitted simultaneously with the seventh PUCCH.

[0356] Optionally, the terminal supports simultaneous transmission of PUCCHs and PUSCHs of different priorities on different cells under carrier aggregation.

[0357] Preferably, an embodiment of the present application further provides a terminal comprising a processor, a memory, and a program or instruction stored in the memory and executable on the processor. When executed by the processor, the program or instruction implements the various processes of the above-described information transmission method embodiment and can achieve the same technical effect. To avoid repetition, they are not described here. Specifically, Figure 9 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

[0358] 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 the processor 910.

[0359] Those skilled in the art will appreciate that the terminal 900 may further include a power source (such as a battery) for powering various components. The power source may be logically connected to the processor 910 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in FIG9 does not limit the terminal. The terminal may include more or fewer components than shown, or may combine certain components, or have different component arrangements, which will not be described in detail here.

[0360] It should be understood that in an 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 an operating stick, which will not be repeated here.

[0361] 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.

[0362] 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, applications or instructions 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. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM 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.

[0363] Processor 910 may include one or more processing units. Optionally, processor 910 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 910.

[0364] 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.

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

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

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

[0368] 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.

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

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

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

[0372] Handling overlap between PUCCHs of different priorities;

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

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

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

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

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

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

[0379] 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.

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

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

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

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

[0384] 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, where the fourth PUCCH and the fifth PUCCH have different priorities;

[0385] The interface unit 908 is configured to, when the sixth PUCCH overlaps with the second PUSCH, cause the terminal to transmit the sixth PUCCH and the second PUSCH respectively, wherein the sixth PUCCH and the second PUSCH have the same priority; and the second PUSCH can be transmitted simultaneously with the sixth PUCCH.

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

[0387] receiving a second configuration parameter sent by the network-side device;

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

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

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

[0391] The seventh PUCCH and the third PUSCH have different priorities; the third PUSCH can be transmitted simultaneously with the seventh PUCCH.

[0392] Optionally, the terminal supports simultaneous transmission of PUCCHs and PUSCHs of different priorities on different cells under carrier aggregation.

[0393] 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, 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 described here.

[0394] 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.

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

[0396] As shown in FIG10 , an information transmission apparatus 1000 according to an embodiment of the present application, applied to a network-side device, includes:

[0397] The first receiving module 1001 is configured 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.

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

[0399] Optionally, the device further includes:

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

[0401] 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.

[0402] Optionally, the device further includes:

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

[0404] 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.

[0405] 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 effects.

[0406] The communication processing device provided in the embodiment of the present application can implement the various processes implemented in the method embodiment of Figure 7 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0407] 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.

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

[0409] Optionally, the communication interface is further used to:

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

[0411] 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.

[0412] Optionally, the communication interface is further used to:

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

[0414] 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.

[0415] Specifically, embodiments of the present application also provide a network-side device. As shown in Figure 11, 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. Antenna 1101 is connected to radio frequency device 1102. In the uplink direction, radio frequency device 1102 receives information via antenna 1101 and sends the received information to baseband device 1103 for processing. In the downlink direction, baseband device 1103 processes the information to be transmitted and sends it to radio frequency device 1102. Radio frequency device 1102 processes the received information and then sends it through antenna 1101.

[0416] 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.

[0417] The baseband device 1103 may, for example, include at least one baseband board, on which multiple chips are arranged, as shown in Figure 11, 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 and execute the network device operations shown in the above method embodiment.

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

[0419] Specifically, the network side device 1100 of the embodiment of the present application also includes: instructions or programs stored in the memory 1105 and executable on the processor 1104. The processor 1104 calls the instructions or programs in the memory 1105 to execute the methods executed by the modules shown in FIG10 and achieve the same technical effect. To avoid repetition, they will not be elaborated here.

[0420] 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.

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

[0422] Optionally, as shown in Figure 12, an embodiment of the present application further provides a communication device 1200, including a processor 1201 and a memory 1202, wherein 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.

[0423] 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.

[0424] 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.

[0425] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product 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.

[0426] An embodiment of the present application further 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.

[0427] An embodiment of the present application further 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.

[0428] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising 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 a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments 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 the opposite 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.

[0429] Through the description of the above embodiments, 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-purpose hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or network-side device to execute the methods described in each embodiment of the present application.

[0430] 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 this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. A method for transmitting information, wherein: 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, wherein: The PUCCH includes hybrid automatic repeat request acknowledgement HARQ-ACK information.

3. The method according to claim 1 or 2, wherein: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, wherein: Also includes: In the case where the fourth PUCCH overlaps with the fifth PUCCH, the terminal multiplexes the fourth PUCCH and the fifth PUCCH to obtain the sixth PUCCH, and the priority of the fourth PUCCH and the fifth PUCCH is Different levels; 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, wherein: 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, wherein: 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, wherein: The terminal supports simultaneous transmission of PUCCH and PUSCH of different priorities on different cells under carrier aggregation.

12. A method for transmitting information, wherein: 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, wherein: The PUCCH includes hybrid automatic repeat request acknowledgement HARQ-ACK information.

14. The method according to claim 12 or 13, wherein: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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.

21. A chip, wherein: The chip includes a processor and a communication interface, 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 information transmission method as described in any one of claims 1-11, or to implement the steps of the information transmission method as described in any one of claims 12-15.

22. A computer program product, wherein: The program product is executed by at least one processor to implement the steps of the information transmission method according to any one of claims 1 to 11, or to implement the steps of the information transmission method according to any one of claims 12 to 15.

23. An information transmission device / equipment, wherein: The device / equipment is configured to execute 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.

Images