WO2020228419A1 - 一种信令传输的方法、用户终端、基站及存储介质 - Google Patents

一种信令传输的方法、用户终端、基站及存储介质 Download PDF

Info

Publication number
WO2020228419A1
WO2020228419A1 PCT/CN2020/080749 CN2020080749W WO2020228419A1 WO 2020228419 A1 WO2020228419 A1 WO 2020228419A1 CN 2020080749 W CN2020080749 W CN 2020080749W WO 2020228419 A1 WO2020228419 A1 WO 2020228419A1
Authority
WO
WIPO (PCT)
Prior art keywords
uci
pusch
service type
code rate
rate offset
Prior art date
Application number
PCT/CN2020/080749
Other languages
English (en)
French (fr)
Inventor
司倩倩
高雪娟
Original Assignee
大唐移动通信设备有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 大唐移动通信设备有限公司 filed Critical 大唐移动通信设备有限公司
Publication of WO2020228419A1 publication Critical patent/WO2020228419A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network

Definitions

  • This application relates to the field of communications, and in particular to a method for signaling transmission, user terminals, base stations, and storage media.
  • a radio access network (NEW Radio, NR) communication system
  • UCI uplink control information
  • UE User Equipment
  • PUSCH physical Uplink Share Channel
  • CSI Channel State Information
  • the RE resources occupied by the UCI of the same service type on PUSCH transmission are controlled by the beta-offset value, where the beta-offset value represents the code rate offset value of UCI and data transmission.
  • the beta-offset value represents the code rate offset value of UCI and data transmission.
  • the resource element (Resource Element, RE) occupied by UCI mapping on the PUSCH when there is uplink shared channel (UL-SCH) data transmission in the PUSCH, the UCI code rate is determined according to the data code rate and beta-offset, And determine the number of RE resources occupied by UCI according to the UCI code rate; when there is no UL-SCH data transmission in the PUSCH, determine the number of RE resources occupied by HARQ-ACK and CSI Part 1 according to the indicated code rate and beta-offset respectively , The remaining RE resources in the RE resources available for UCI transmission on PUSCH are used for CSI Part 2 transmission.
  • the parameter scaling configured by higher layers limits the upper limit of resources that can be allocated to UCI on PUSCH
  • NR supports semi-static configuration of the beta-offset value and dynamic beta-offset indication, for the downlink control information (Downlink Control Information, DCI) format 0_0 or the DCI format 0_1 that does not contain the beta-offset indication domain information, the scheduled PUSCH.
  • the beta-offset value used for UCI transmission is semi-statically configured by the base station through RRC signaling.
  • the DCI format 0_1 contains 2-bit indication information, which is used to indicate one of the four sets of beta-offset values configured by RRC.
  • the group beta-offset value contains multiple values, corresponding to different UCI types or number of bits.
  • the physical uplink control channel (PUCCH) of different service types will overlap with the PUSCH. If the current UCI multiplexing on PUSCH is still used With the transmission method, the transmission performance of UCI or PUSCH with higher service type priority cannot be guaranteed. However, there is no multiplexing transmission scheme between UCI and PUSCH of different service types.
  • PUCCH physical uplink control channel
  • the present application provides a signaling transmission method, user terminal, base station, and storage medium to solve the technical problem in the prior art that UCI of different service classes cannot be transmitted in PUSCH.
  • a method for signaling transmission provided by an embodiment of the present application is applied to a user terminal that is configured with at least two service types at the same time.
  • the technical solution of the method is as follows:
  • the high-level configuration information is the bit rate offset value used when UCI of at least one service type is multiplexed to PUSCH of any service type among the at least two service types And/or the maximum resource ratio occupied by UCI on PUSCH;
  • the PUCCH carrying UCI to be transmitted overlaps the PUSCH scheduled by DCI, based on the first service type of the UCI to be transmitted, the second service type corresponding to the PUSCH scheduled by the DCI, and the high-level configuration information, the The UCI to be transmitted is multiplexed on the PUSCH scheduled by the DCI and transmitted to the base station.
  • the user terminal When the user terminal is configured with at least two service types at the same time, after receiving the high-level configuration information sent by the base station, when the PUCCH carrying UCI to be transmitted overlaps the PUSCH scheduled by DCI, based on the first service type of UCI to be transmitted, DCI The second service type corresponding to the scheduled PUSCH and the high-level configuration information, the UCI to be transmitted is multiplexed on the DCI scheduled PUSCH and transmitted to the base station; wherein, the high-level configuration information is at least one of the at least two service types
  • the code rate offset value and/or the maximum resource ratio occupied by UCI on PUSCH can be used to transmit UCI of different service types in PUSCH, and can be used in multiplexing. In the case of transmission, the transmission performance of the service with high priority is guaranteed.
  • the transmission of PUSCH to the base station includes:
  • the format of the DCI is 0_0, or does not contain 0_1 of the code rate offset indication field information, then based on the first service type and the second service type, a corresponding one is matched from the high-level configuration information.
  • a group code rate offset value and/or a maximum resource ratio multiplexing the UCI to be transmitted on the PUSCH scheduled by the DCI and transmitting to the base station;
  • the format of the DCI is 0_1 containing dynamic code rate offset indication domain information, based on the first service type and the second service type, the corresponding four sets of codes are matched from the high-level configuration information Rate offset value and/or maximum resource ratio; and according to the 2-bit indication information carried in the DCI, determine a set of actually used code rate offset values and/or maximum resource ratio, and multiplex the UCI to be transmitted Transmitting to the base station on the PUSCH scheduled by the DCI.
  • the format of the DCI is 0_0 or does not contain 0_1 of the code rate offset indication field information
  • matching is performed from the high-level configuration information
  • a corresponding set of code rate offset values and/or maximum resource ratios including:
  • the first service type is URLLC and the second service type is eMBB, obtain a set of code rate offset values and/or maximum resource ratios corresponding to URLLC UCI and eMBB PUSCH from the high-level configuration information;
  • the first service type is URLLC and the second service type is URLLC, obtain a set of code rate offset values and/or maximum resource ratios corresponding to URLLC UCI and URLLC PUSCH from the high-level configuration information;
  • the first service type is eMBB and the second service type is URLLC, obtain a set of code rate offset values and/or maximum resource ratios corresponding to eMBB UCI and URLLC PUSCH from the high-level configuration information;
  • a set of code rate offset values and/or maximum resource ratios corresponding to eMBB UCI and eMBB PUSCH are obtained from the high-layer configuration information.
  • the format of the DCI is 0_1 containing dynamic code rate offset indication domain information
  • the corresponding data is matched from the high-level configuration information
  • the four sets of code rate offset values and/or maximum resource ratios include:
  • the first service type is URLLC and the second service type is eMBB, obtain four sets of code rate offset values and/or maximum resource ratios corresponding to URLLC UCI and eMBB PUSCH from the high-level configuration information;
  • the first service type is URLLC and the second service type is URLLC, obtain four sets of code rate offset values and/or maximum resource ratios corresponding to URLLC UCI and URLLC PUSCH from the high-level configuration information;
  • the first service type is eMBB and the second service type is URLLC
  • four sets of code rate offset values and/or maximum resource ratios corresponding to eMBB UCI and URLLC PUSCH are obtained from the high-level configuration information
  • the first service type is eMBB and the second service type is eMBB
  • four sets of code rate offset values and/or maximum resource ratios corresponding to eMBB UCI and eMBB PUSCH are obtained from the high-layer configuration information.
  • the code rate offset value includes a dynamic code rate offset value and a static code rate offset value; wherein, the static code rate offset value includes a set of offset values, and the dynamic code rate offset value
  • the code rate offset value includes four sets of offset values.
  • a method for signaling transmission provided by an embodiment of the present application is applied to a base station, and the technical solution of the method is as follows:
  • the high-level configuration information is that UCI of at least one service type is multiplexed into any of the at least two service types.
  • the code rate offset value includes a dynamic code rate offset value and a static code rate offset value; wherein, the static code rate offset value includes a set of offset values, and the dynamic code rate offset value
  • the code rate offset value includes four sets of offset values.
  • the high-level configuration information includes:
  • each combination of the at least two service types corresponds to a set of code rate offset values and/or UCI in the PUSCH The largest proportion of resources occupied on the Internet;
  • each combination of the at least two service types corresponds to four sets of code rate offset values and/or UCI in the PUSCH The largest proportion of resources occupied by the system.
  • the included combinations are:
  • an embodiment of the present application provides a user terminal for signaling transmission.
  • the user terminal is configured with at least two service types at the same time, and the terminal includes:
  • Receiving unit used to receive high-level configuration information sent by the base station; wherein the high-level configuration information is used when UCI of at least one service type is multiplexed into PUSCH of any service type among the at least two service types The code rate offset value and/or the maximum resource ratio occupied by UCI on PUSCH;
  • the multiplexing transmission unit is used for when the PUCCH carrying UCI to be transmitted overlaps with the PUSCH scheduled by DCI, based on the first service type of the UCI to be transmitted, the second service type corresponding to the PUSCH scheduled by the DCI, and the High-level configuration information, multiplexing the UCI to be transmitted on the PUSCH scheduled by the DCI and transmitting to the base station.
  • the multiplexing transmission unit is used for:
  • the format of the DCI is 0_0, or does not contain 0_1 of the code rate offset indication field information, then based on the first service type and the second service type, a corresponding one is matched from the high-level configuration information.
  • a group code rate offset value and/or a maximum resource ratio multiplexing the UCI to be transmitted on the PUSCH scheduled by the DCI and transmitting to the base station;
  • the format of the DCI is 0_1 containing dynamic code rate offset indication domain information, based on the first service type and the second service type, the corresponding four sets of codes are matched from the high-level configuration information Rate offset value and/or maximum resource ratio; and according to the 2-bit indication information carried in the DCI, determine a set of actually used code rate offset values and/or maximum resource ratio, and multiplex the UCI to be transmitted Transmitting to the base station on the PUSCH scheduled by the DCI.
  • the multiplexing transmission unit is further configured to:
  • the first service type is URLLC and the second service type is eMBB, obtain a set of code rate offset values and/or maximum resource ratios corresponding to URLLC UCI and eMBB PUSCH from the high-level configuration information;
  • the first service type is URLLC and the second service type is URLLC, obtain a set of code rate offset values and/or maximum resource ratios corresponding to URLLC UCI and URLLC PUSCH from the high-level configuration information;
  • the first service type is eMBB and the second service type is URLLC, obtain a set of code rate offset values and/or maximum resource ratios corresponding to eMBB UCI and URLLC PUSCH from the high-level configuration information;
  • a set of code rate offset values and/or maximum resource ratios corresponding to eMBB UCI and eMBB PUSCH are obtained from the high-layer configuration information.
  • the multiplexing transmission unit is further configured to:
  • the first service type is URLLC and the second service type is eMBB, obtain four sets of code rate offset values and/or maximum resource ratios corresponding to URLLC UCI and eMBB PUSCH from the high-level configuration information;
  • the first service type is URLLC and the second service type is URLLC, obtain four sets of code rate offset values and/or maximum resource ratios corresponding to URLLC UCI and URLLC PUSCH from the high-level configuration information;
  • the first service type is eMBB and the second service type is URLLC
  • four sets of code rate offset values and/or maximum resource ratios corresponding to eMBB UCI and URLLC PUSCH are obtained from the high-level configuration information
  • the first service type is eMBB and the second service type is eMBB
  • four sets of code rate offset values and/or maximum resource ratios corresponding to eMBB UCI and eMBB PUSCH are obtained from the high-layer configuration information.
  • the code rate offset value includes a dynamic code rate offset value and a static code rate offset value; wherein, the static code rate offset value includes a set of offset values, and the dynamic code rate offset value
  • the code rate offset value includes four sets of offset values.
  • an embodiment of the present application also provides a user terminal configured with at least two service types at the same time, and the user terminal includes: a processor, a memory, and a transceiver;
  • the processor is used to read the program in the memory and execute the following process:
  • the high-level configuration information is the bit rate offset value used when UCI of at least one service type is multiplexed to PUSCH of any service type among the at least two service types And/or the maximum resource ratio occupied by UCI on PUSCH;
  • the PUCCH carrying UCI to be transmitted overlaps the PUSCH scheduled by DCI, based on the first service type of the UCI to be transmitted, the second service type corresponding to the PUSCH scheduled by the DCI, and the high-level configuration information, the The UCI to be transmitted is multiplexed on the PUSCH scheduled by the DCI and transmitted to the base station.
  • the processor is further configured to:
  • the format of the DCI is 0_0, or does not contain 0_1 of the code rate offset indication field information, then based on the first service type and the second service type, a corresponding one is matched from the high-level configuration information.
  • a group code rate offset value and/or a maximum resource ratio multiplexing the UCI to be transmitted on the PUSCH scheduled by the DCI and transmitting to the base station;
  • the format of the DCI is 0_1 containing dynamic code rate offset indication domain information, based on the first service type and the second service type, the corresponding four sets of codes are matched from the high-level configuration information Rate offset value and/or maximum resource ratio; and according to the 2-bit indication information carried in the DCI, determine a set of actually used code rate offset values and/or maximum resource ratio, and multiplex the UCI to be transmitted Transmitting to the base station on the PUSCH scheduled by the DCI.
  • the processor is further configured to:
  • the first service type is URLLC and the second service type is eMBB, obtain a set of code rate offset values and/or maximum resource ratios corresponding to URLLC UCI and eMBB PUSCH from the high-level configuration information;
  • the first service type is URLLC and the second service type is URLLC, obtain a set of code rate offset values and/or maximum resource ratios corresponding to URLLC UCI and URLLC PUSCH from the high-level configuration information;
  • the first service type is eMBB and the second service type is URLLC, obtain a set of code rate offset values and/or maximum resource ratios corresponding to eMBB UCI and URLLC PUSCH from the high-level configuration information;
  • a set of code rate offset values and/or maximum resource ratios corresponding to eMBB UCI and eMBB PUSCH are obtained from the high-layer configuration information.
  • the processor is further configured to:
  • the first service type is URLLC and the second service type is eMBB, obtain four sets of code rate offset values and/or maximum resource ratios corresponding to URLLC UCI and eMBB PUSCH from the high-level configuration information;
  • the first service type is URLLC and the second service type is URLLC, obtain four sets of code rate offset values and/or maximum resource ratios corresponding to URLLC UCI and URLLC PUSCH from the high-level configuration information;
  • the first service type is eMBB and the second service type is URLLC, obtain four sets of bit rate offset values and/or maximum resource ratios corresponding to eMBB UCI and URLLC PUSCH from the high-level configuration information;
  • the first service type is eMBB and the second service type is eMBB
  • four sets of code rate offset values and/or maximum resource ratios corresponding to eMBB UCI and eMBB PUSCH are obtained from the high-layer configuration information.
  • the code rate offset value includes a dynamic code rate offset value and a static code rate offset value; wherein, the static code rate offset value includes a set of offset values, and the dynamic code rate offset value
  • the code rate offset value includes four sets of offset values.
  • an embodiment of the present application also provides a base station, which includes a processor, a memory, and a transceiver;
  • the processor is used to read the program in the memory and execute the following process:
  • the high-level configuration information is that UCI of at least one service type is multiplexed into any of the at least two service types.
  • the code rate offset value includes a dynamic code rate offset value and a static code rate offset value; wherein, the static code rate offset value includes a set of offset values, and the dynamic code rate offset value
  • the code rate offset value includes four sets of offset values.
  • the high-level configuration information includes:
  • each combination of the at least two service types corresponds to a set of code rate offset values and/or UCI in the PUSCH The largest proportion of resources occupied on the Internet;
  • each combination of the at least two service types corresponds to four sets of code rate offset values and/or UCI in the PUSCH The largest proportion of resources occupied by the system.
  • the included combinations are:
  • an embodiment of the present application also provides a computer-readable storage medium, including:
  • the computer-readable storage medium stores computer instructions, and when the computer instructions run on a computer, the computer executes the method described in the first or second aspect.
  • the embodiments of the present application have at least the following technical effects:
  • the user terminal when the user terminal is configured with at least two service types at the same time, after receiving the high-level configuration information sent by the base station, when the PUCCH carrying UCI to be transmitted overlaps with the PUSCH scheduled by DCI, it is based on the Transmit the first service type of UCI, the second service type corresponding to the PUSCH scheduled by DCI, and high-level configuration information, and multiplex the UCI to be transmitted on the PUSCH scheduled by DCI and transmit to the base station; wherein, the high-level configuration information is at least two services Among the types, the code rate offset value used when UCI of at least one service type is multiplexed into PUSCH of any service type and/or the maximum resource ratio occupied by UCI on PUSCH, so as to be able to compare different service types in PUSCH UCI is used for transmission, and can guarantee the transmission performance of high-priority services in the case of multiplexing transmission.
  • FIG. 1 is a flowchart of a signaling transmission method on the user terminal side according to an embodiment of the application
  • FIG. 2 is a schematic structural diagram of a user terminal provided by an embodiment of the application.
  • FIG. 3 is a schematic structural diagram of another user terminal provided by an embodiment of the application.
  • Fig. 4 is a schematic structural diagram of a base station provided by an embodiment of the application.
  • the embodiment of the present application provides a signaling transmission method, user terminal, base station, and device to solve the technical problem in the prior art that UCI of different service types cannot be transmitted in PUSCH.
  • the method for signaling transmission is applied to a user terminal configured with at least two types of services at the same time.
  • the method includes: receiving high-level configuration information sent by a base station; wherein, the high-level configuration information is at least two types of services Among the types, the code rate offset value used when UCI of at least one service type is multiplexed to PUSCH of any service type and/or the maximum resource ratio occupied by UCI on PUSCH; when carrying PUCCH and DCI of UCI to be transmitted When the scheduled PUSCH overlaps, based on the first service type of UCI to be transmitted, the second service type corresponding to the PUSCH scheduled by DCI, and high-level configuration information, the UCI to be transmitted is multiplexed on the PUSCH scheduled by DCI and transmitted to the base station.
  • the user terminal when the user terminal is configured with at least two service types at the same time, after receiving the high-level configuration information sent by the base station, when the PUCCH carrying UCI to be transmitted overlaps with the PUSCH scheduled by DCI, based on the UCI to be transmitted
  • the first service type, the second service type corresponding to the DCI-scheduled PUSCH and the high-level configuration information, the UCI to be transmitted is multiplexed on the DCI-scheduled PUSCH and transmitted to the base station; wherein, the high-level configuration information is at least two service types, at least The code rate offset used when UCI of one service type is multiplexed to PUSCH of any service type and/or the maximum resource ratio occupied by UCI on PUSCH, so that UCI of different service types can be transmitted in PUSCH , And can ensure the transmission performance of high-priority services in the case of multiplexing transmission.
  • an embodiment of the present application provides a signaling transmission method, which is applied to a user terminal configured with at least two service types at the same time.
  • the processing process of the method is as follows.
  • Step 101 Receive high-level configuration information sent by the base station; where the high-level configuration information is the bit rate offset value used when UCI of at least one service type is multiplexed to PUSCH of any service type among at least two service types, and / Or the maximum resource ratio occupied by UCI on PUSCH;
  • Step 102 When the PUCCH carrying UCI to be transmitted overlaps with the PUSCH scheduled by DCI, based on the first service type of UCI to be transmitted, the second service type corresponding to the PUSCH scheduled by DCI, and high-level configuration information, multiplex the UCI to be transmitted It is transmitted to the base station on the PUSCH scheduled by DCI.
  • UCIs of different service types correspond to different priorities, that is, UCIs of different service types may be UCIs of different priorities.
  • the code rate offset value includes a dynamic code rate offset value and a static code rate offset value; the static code rate offset value includes a set of offset values, and the dynamic code rate offset value includes Four sets of offset values.
  • Each set of offset values includes the following information:
  • betaOffsetACK-Index1 the bit number is less than or equal to the ACK code rate offset value corresponding to 2;
  • betaOffsetACK-Index2 the ACK code rate offset value corresponding to the number of bits from 3 to 11;
  • betaOffsetACK-Index3 the number of bits is greater than the ACK code rate offset value corresponding to 11;
  • betaOffsetCSI-Part1-Index1 the bit rate offset value corresponding to the first part of the CSI with the number of bits less than 11;
  • betaOffsetCSI-Part1-Index2 the bit rate offset value corresponding to the first part of the CSI with the number of bits greater than or equal to 11;
  • betaOffsetCSI-Part2-Index1 the bit rate offset value corresponding to the second part of the CSI with the number of bits less than 11;
  • betaOffsetCSI-Part2-Index2 the bit rate offset value corresponding to the second part of the CSI with the number of bits greater than or equal to 11.
  • Combination 1 eMBB UCI and URLLC PUSCH;
  • Combination 2 eMBB UCI and eMBB PUSCH;
  • Combination 3 URLLC UCI and eMBB PUSCH;
  • Combination 3 URLLC UCI and URLLC PUSCH.
  • the code rate offset value is divided into static code rate offset value and dynamic code rate offset value, each of the above combinations is divided into static code rate offset value (only one set of offset value), and dynamic code rate offset value.
  • the bit rate offset value (specific four sets of offset values). Therefore, when the base station is configured with two service types at the same time, the high-level configuration information includes the static and dynamic code rate offset values corresponding to the four combinations.
  • the UCI to be transmitted is multiplexed on the PUSCH scheduled by DCI and transmitted to the base station, according to the instructions in the DCI
  • the type of bit rate offset is different, including the following two methods:
  • the first type if the format of DCI is 0_0, or 0_1 that does not contain the bit rate offset indication domain information, then based on the first service type and the second service type, a corresponding set of bit rate offsets are matched from the high-level configuration information Shift value and/or maximum resource ratio, multiplex the UCI to be transmitted on the PUSCH scheduled by DCI and transmit it to the base station.
  • the user terminal After the user terminal receives the high-level configuration information sent by the base station, when UCI to be transmitted needs to occur, it is found that the PUCCH carrying the UCI to be transmitted overlaps with the PUSCH scheduled by DCI.
  • the user terminal decides to multiplex the UCI to be transmitted in the DCI scheduled Transmission on PUSCH. Assuming that the first service type of UCI to be transmitted is eMBB, and the second service type of PUSCH scheduled by DCI is URLLC, and the format of DCI is 0_0, or 0_1 that does not contain the bit rate offset indication domain information, it means that the static is used
  • the code rate offset value corresponds to a set of code rate offset values.
  • the user terminal according to the first service type eMBB of the UCI to be transmitted, and the second service type URLLC of the PUSCH scheduled by DCI, find out a set of bitrate offset values corresponding to eMBB UCI and URLLC PUSCH from the high-level configuration information and/ Or the largest proportion of resources occupied by UCI on PUSCH. And according to the set of code rate offset values found, multiplex the UCI to be transmitted on the PUSCH scheduled by DCI and transmit it to the base station, so that the base station receives the UCI to be transmitted multiplexed and transmitted according to the service type of the UCI to be transmitted and the PUSCH transmitted by the terminal. And PUSCH.
  • the second type if the format of the DCI is 0_1 containing dynamic code rate offset indication domain information, then based on the first service type and the second service type, the corresponding four sets of code rate offset values are matched from the high-level configuration information And/or the maximum resource ratio; and according to the 2-bit indication information carried in the DCI, determine the actually used set of code rate offset values and/or the maximum resource ratio, and multiplex the UCI to be transmitted on the PUSCH scheduled by the DCI for transmission to Base station.
  • the user terminal After the user terminal receives the high-level configuration information sent by the base station, when UCI to be transmitted needs to occur, it is found that the PUCCH carrying the UCI to be transmitted overlaps with the PUSCH scheduled by DCI.
  • the user terminal decides to multiplex the UCI to be transmitted in the DCI scheduled Transmission on PUSCH. Assuming that the first service type of UCI to be transmitted is eMBB, the second service type of PUSCH scheduled by DCI is URLLC, and the format of DCI is 0_1 containing dynamic bit rate offset indication domain information, which means that the dynamic bit rate is used
  • the offset value corresponds to the configuration of four sets of code rate offset values.
  • the user terminal according to the first service type eMBB of the UCI to be transmitted, and the second service type URLLC of the PUSCH scheduled by DCI, find the four sets of code rate offset values corresponding to eMBB UCI and URLLC PUSCH from the high-level configuration information and/ Or the maximum resource ratio occupied by UCI on PUSCH, and then according to the 2bit information field in DCI (assuming the corresponding binary data is 10, it corresponds to the third group), the third group of code rates is obtained from these four groups of code rate offset values
  • the offset value is the code rate offset value used when multiplexing the UCI to be transmitted on the PUSCH scheduled by DCI for transmission, so that the base station receives the UCI and the UCI to be transmitted multiplexed according to the service type of the UCI and PUSCH to be transmitted by the terminal. PUSCH.
  • UCI multiplexing on PUSCH will have 4 combinations, specifically if the DCI format is 0_0, or does not include the code rate
  • the 0_1 of the offset indication field information is based on the first service type and the second service type, and a corresponding set of code rate offset values and/or maximum resource ratios are matched from the high-level configuration information, including:
  • the first method if the first service type is URLLC and the second service type is eMBB, obtain a set of bit rate offset values and/or maximum resource ratios corresponding to URLLC UCI and eMBB PUSCH from the high-level configuration information. In this way, URLLC UCI can be multiplexed on eMBB PUSCH and transmitted to the base station.
  • the second method if the first service type is URLLC and the second service type is URLLC, obtain a set of code rate offset values and/or maximum resource ratios corresponding to URLLC UCI and URLLC PUSCH from the high-level configuration information. In this way, URLLC UCI can be multiplexed on URLLC PUSCH and transmitted to the base station.
  • the third method if the first service type is eMBB and the second service type is URLLC, obtain a set of bit rate offset values and/or maximum resource ratios corresponding to eMBB UCI and URLLC PUSCH from the high-level configuration information. In this way, eMBB UCI can be multiplexed on URLLC PUSCH and transmitted to the base station.
  • the fourth method if the first service type is eMBB and the second service type is eMBB, obtain a set of code rate offset values and/or maximum resource ratios corresponding to eMBB UCI and eMBB PUSCH from the high-level configuration information. In this way, eMBB UCI can be multiplexed on eMBB PUSCH and transmitted to the base station.
  • UCI multiplexing on PUSCH will also have 4 combinations. Specifically, if the DCI format includes dynamic bit rate offset Shift 0_1 of the indication domain information, based on the first service type and the second service type, match the corresponding four sets of code rate offset values and/or the maximum resource ratio from the high-level configuration information, including:
  • the first method if the first service type is URLLC and the second service type is eMBB, four sets of code rate offset values and/or maximum resource ratios corresponding to URLLC UCI and eMBB PUSCH are obtained from the high-level configuration information. In this way, after the user terminal finds the corresponding four sets of offset values/or the maximum resource ratio from the high-level configuration information according to the first service type and the second service type, it can determine which to use according to the 2-bit information field in the DCI Group offset value, multiplex URLLC UCI on eMBB PUSCH and transmit to the base station.
  • the second method if the first service type is URLLC and the second service type is URLLC, the four sets of code rate offset values and/or maximum resource ratios corresponding to URLLC UCI and URLLC PUSCH are obtained from the high-level configuration information. In this way, after the user terminal finds the corresponding four sets of offset values/sum or maximum resource ratio from the high-level configuration information according to the first service type and the second service type, it can determine which to use according to the 2-bit information field in the DCI Group offset value, multiplex URLLC UCI on URLLC PUSCH and transmit to the base station.
  • the third method if the first service type is eMBB and the second service type is URLLC, the four sets of code rate offset values and/or maximum resource ratios corresponding to eMBB UCI and URLLC PUSCH are obtained from the high-level configuration information. In this way, after the user terminal finds the corresponding four sets of offset values/or the maximum resource ratio from the high-level configuration information according to the first service type and the second service type, it can determine which to use according to the 2-bit information field in the DCI Group offset value, multiplex eMBB UCI on URLLC PUSCH and transmit to the base station.
  • the fourth method if the first service type is eMBB and the second service type is eMBB, the four sets of code rate offset values and/or maximum resource ratios corresponding to eMBB UCI and eMBB PUSCH are obtained from the high-level configuration information. In this way, after the user terminal finds the corresponding four sets of offset values/or the maximum resource ratio from the high-level configuration information according to the first service type and the second service type, it can determine which to use according to the 2-bit information field in the DCI Group offset value, multiplex eMBB UCI on eMBB PUSCH and transmit to the base station.
  • the base station can obtain the corresponding code rate offset from the high-level configuration information according to the first service type of UCI to be sent and the second service type of PUSCH called by the current DCI Value and/or maximum resource ratio, multiplex the UCI to be sent on the PUSCH called by the DCI and transmit it to the base station.
  • the code rate offset value and/or the maximum resource ratio corresponding to different combinations may be the same or different.
  • the code rate offset value is dynamic, each The four sets of offset values in this combination are generally different, but may also be partly the same, which is not specifically limited here.
  • the user terminal when the user terminal is configured with three service types at the same time, such as eMBB, URLLC, and Massive Machine Type Communication (mMTC), when there are two types of UCI services (such as eMBB and URLLC).
  • eMBB enhanced Mobile Broadband
  • URLLC Massive Machine Type Communication
  • the user terminal When multiplexing on the PUSCH with the service type of mMTC, the user terminal only needs to find the bit rate offset value and/or the maximum resource ratio corresponding to eMBB UCI and mMTC PUSCH from the high-level configuration information, and the URLLC UCI and mMTC PUSCH correspondence
  • the bit rate offset value and/or the maximum resource ratio can be multiplexed with eMBB UCI and URLLC UCI simultaneously on mMTC PUSCH and transmitted to the base station.
  • the high-level configuration information can configure the corresponding bit rate offset value and/or the maximum resource ratio for each combination, so that the user
  • the terminal is configured with multiple service types at the same time, it can find out the code rate offset value and/or the maximum resource ratio corresponding to the actually used combination from the high-level configuration information for multiplexing transmission.
  • the above describes how to perform multiplexing transmission from the perspective of the user terminal when the user terminal is configured with at least two service types at the same time.
  • the following describes the process from the perspective of the base station.
  • an embodiment of the present application provides a method for signaling transmission.
  • the method is applied to the base station. , The method includes:
  • the code rate offset value and/or the maximum resource ratio occupied by UCI on the PUSCH so that when the PUCCH carrying the user terminal to be transmitted UCI overlaps with the PUSCH scheduled by DCI, the user terminal is allowed to be based on the service type of the UCI to be transmitted With the PUSCH scheduled by DCI and high-level configuration information, the UCI to be transmitted is multiplexed on the PUSCH scheduled by DCI for transmission.
  • the code rate offset value includes a dynamic code rate offset value and a static code rate offset value; wherein, the static code rate offset value includes a set of offset values, and the dynamic code rate offset The value includes four sets of offset values.
  • the high-level configuration information includes:
  • each combination of the at least two service types corresponds to a set of code rate offset values and/or UCI in the PUSCH The largest proportion of resources occupied on the Internet;
  • each combination of the at least two service types corresponds to four sets of code rate offset values and/or UCI in the PUSCH The largest proportion of resources occupied by the system.
  • the included combinations are:
  • an embodiment of the present application provides a user terminal for signaling transmission.
  • the signaling transmission method of the user terminal please refer to the description of the method embodiment on the user terminal side. Without repeating it, please refer to Figure 2.
  • the user terminal includes:
  • Receiving unit 201 used to receive high-level configuration information sent by a base station; wherein, the high-level configuration information is used when UCI of at least one service type is multiplexed into PUSCH of any service type among the at least two service types The code rate offset value of and/or the maximum resource ratio occupied by UCI on PUSCH;
  • the multiplexing transmission unit 202 is used for when the PUCCH carrying UCI to be transmitted overlaps with the PUSCH scheduled by DCI, based on the first service type of the UCI to be transmitted, the second service type corresponding to the PUSCH scheduled by the DCI, and The high-level configuration information multiplexes the UCI to be transmitted on the PUSCH scheduled by the DCI and transmits it to the base station.
  • the multiplexing transmission unit 202 is configured to:
  • the format of the DCI is 0_0, or does not contain 0_1 of the code rate offset indication field information, then based on the first service type and the second service type, a corresponding one is matched from the high-level configuration information.
  • a group code rate offset value and/or a maximum resource ratio multiplexing the UCI to be transmitted on the PUSCH scheduled by the DCI and transmitting to the base station;
  • the format of the DCI is 0_1 containing dynamic code rate offset indication domain information, based on the first service type and the second service type, the corresponding four sets of codes are matched from the high-level configuration information Rate offset value and/or maximum resource ratio; and according to the 2-bit indication information carried in the DCI, determine a set of actually used code rate offset values and/or maximum resource ratio, and multiplex the UCI to be transmitted Transmitting to the base station on the PUSCH scheduled by the DCI.
  • the multiplexing transmission unit 202 is further configured to:
  • the first service type is URLLC and the second service type is eMBB, obtain a set of code rate offset values and/or maximum resource ratios corresponding to URLLC UCI and eMBB PUSCH from the high-level configuration information;
  • the first service type is URLLC and the second service type is URLLC, obtain a set of code rate offset values and/or maximum resource ratios corresponding to URLLC UCI and URLLC PUSCH from the high-level configuration information;
  • the first service type is eMBB and the second service type is URLLC, obtain a set of code rate offset values and/or maximum resource ratios corresponding to eMBB UCI and URLLC PUSCH from the high-level configuration information;
  • a set of code rate offset values and/or maximum resource ratios corresponding to eMBB UCI and eMBB PUSCH are obtained from the high-layer configuration information.
  • the multiplexing transmission unit 202 is further configured to:
  • the first service type is URLLC and the second service type is eMBB, obtain four sets of code rate offset values and/or maximum resource ratios corresponding to URLLC UCI and eMBB PUSCH from the high-level configuration information;
  • the first service type is URLLC and the second service type is URLLC, obtain four sets of code rate offset values and/or maximum resource ratios corresponding to URLLC UCI and URLLC PUSCH from the high-level configuration information;
  • the first service type is eMBB and the second service type is URLLC
  • four sets of code rate offset values and/or maximum resource ratios corresponding to eMBB UCI and URLLC PUSCH are obtained from the high-level configuration information
  • the first service type is eMBB and the second service type is eMBB
  • four sets of code rate offset values and/or maximum resource ratios corresponding to eMBB UCI and eMBB PUSCH are obtained from the high-layer configuration information.
  • the code rate offset value includes a dynamic code rate offset value and a static code rate offset value; wherein, the static code rate offset value includes a set of offset values, and the dynamic code rate offset value
  • the code rate offset value includes four sets of offset values.
  • an embodiment of the present application provides a user terminal configured with at least two service types at the same time, and the user terminal includes: a processor 301, a memory 302, and a transceiver 303;
  • the processor 301 is configured to read the program in the memory 302 and execute the following process:
  • the high-level configuration information is the bit rate offset value used when UCI of at least one service type is multiplexed to PUSCH of any service type among the at least two service types And/or the maximum resource ratio occupied by UCI on PUSCH;
  • the PUCCH carrying UCI to be transmitted overlaps the PUSCH scheduled by DCI, based on the first service type of the UCI to be transmitted, the second service type corresponding to the PUSCH scheduled by the DCI, and the high-level configuration information, the The UCI to be transmitted is multiplexed on the PUSCH scheduled by the DCI and transmitted to the base station.
  • the processor 301 is further configured to:
  • the format of the DCI is 0_0, or does not contain 0_1 of the code rate offset indication field information, then based on the first service type and the second service type, a corresponding one is matched from the high-level configuration information.
  • a group code rate offset value and/or a maximum resource ratio multiplexing the UCI to be transmitted on the PUSCH scheduled by the DCI and transmitting to the base station;
  • the format of the DCI is 0_1 containing dynamic code rate offset indication domain information, based on the first service type and the second service type, the corresponding four sets of codes are matched from the high-level configuration information Rate offset value and/or maximum resource ratio; and according to the 2-bit indication information carried in the DCI, determine a set of actually used code rate offset values and/or maximum resource ratio, and multiplex the UCI to be transmitted Transmitting to the base station on the PUSCH scheduled by the DCI.
  • the processor 301 is further configured to:
  • the first service type is URLLC and the second service type is eMBB, obtain a set of code rate offset values and/or maximum resource ratios corresponding to URLLC UCI and eMBB PUSCH from the high-level configuration information;
  • the first service type is URLLC and the second service type is URLLC, obtain a set of code rate offset values and/or maximum resource ratios corresponding to URLLC UCI and URLLC PUSCH from the high-level configuration information;
  • the first service type is eMBB and the second service type is URLLC, obtain a set of code rate offset values and/or maximum resource ratios corresponding to eMBB UCI and URLLC PUSCH from the high-level configuration information;
  • a set of code rate offset values and/or maximum resource ratios corresponding to eMBB UCI and eMBB PUSCH are obtained from the high-layer configuration information.
  • the processor 301 is further configured to:
  • the first service type is URLLC and the second service type is eMBB, obtain four sets of code rate offset values and/or maximum resource ratios corresponding to URLLC UCI and eMBB PUSCH from the high-level configuration information;
  • the first service type is URLLC and the second service type is URLLC, obtain four sets of code rate offset values and/or maximum resource ratios corresponding to URLLC UCI and URLLC PUSCH from the high-level configuration information;
  • the first service type is eMBB and the second service type is URLLC
  • four sets of code rate offset values and/or maximum resource ratios corresponding to eMBB UCI and URLLC PUSCH are obtained from the high-level configuration information
  • the first service type is eMBB and the second service type is eMBB
  • four sets of code rate offset values and/or maximum resource ratios corresponding to eMBB UCI and eMBB PUSCH are obtained from the high-layer configuration information.
  • the code rate offset value includes a dynamic code rate offset value and a static code rate offset value; wherein, the static code rate offset value includes a set of offset values, and the dynamic code rate offset value
  • the code rate offset value includes four sets of offset values.
  • the processor 301 is responsible for managing the bus architecture and general processing, and the memory 302 can store data used by the processor 301 when performing operations.
  • the transceiver 303 is used to receive and send data under the control of the processor 301.
  • the bus architecture may include any number of interconnected buses and bridges. Specifically, one or more processors represented by the processor 301 and various circuits of the memory represented by the memory 302 are linked together.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, power management circuits, etc., which are all known in the art, and therefore, no further descriptions are provided herein.
  • the bus interface provides the interface.
  • the processor 301 is responsible for managing the bus architecture and general processing, and the memory 302 can store data used by the processor 301 when performing operations.
  • the process disclosed in the embodiment of the present application may be applied to the processor 301 or implemented by the processor 301.
  • each step of the signal processing flow can be completed by hardware integrated logic circuits in the processor 301 or instructions in the form of software.
  • the processor 301 can be a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, and can implement or execute the embodiments of the present application The disclosed methods, steps and logic block diagrams.
  • the general-purpose processor may be a microprocessor or any conventional processor.
  • the steps of the method disclosed in the embodiments of the present application may be directly embodied as executed and completed by a hardware processor, or executed and completed by a combination of hardware and software modules in the processor 301.
  • the software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • the storage medium is located in the memory 302, and the processor 301 reads the information in the memory 302 and completes the steps of the signal processing flow in combination with its hardware.
  • a base station provided by an embodiment of the present application includes: a processor 401, a memory 402, and a transceiver 403;
  • the processor 401 is configured to read the program in the memory 402 and execute the following process:
  • the high-level configuration information is that UCI of at least one service type is multiplexed into any of the at least two service types.
  • the code rate offset value includes a dynamic code rate offset value and a static code rate offset value; wherein, the static code rate offset value includes a set of offset values, and the dynamic code rate offset value
  • the code rate offset value includes four sets of offset values.
  • the high-level configuration information includes:
  • each combination of the at least two service types corresponds to a set of code rate offset values and/or UCI in the PUSCH The largest proportion of resources occupied on the Internet;
  • each combination of the at least two service types corresponds to four sets of code rate offset values and/or UCI in the PUSCH The largest proportion of resources occupied by the system.
  • the included combinations are:
  • the processor 401 is responsible for managing the bus architecture and general processing, and the memory 402 can store data used by the processor 401 when performing operations.
  • the transceiver 403 is used to receive and send data under the control of the processor 401.
  • the bus architecture may include any number of interconnected buses and bridges. Specifically, one or more processors represented by the processor 401 and various circuits of the memory represented by the memory 402 are linked together.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, power management circuits, etc., which are all known in the art, and therefore, no further descriptions are provided herein.
  • the bus interface provides the interface.
  • the processor 401 is responsible for managing the bus architecture and general processing, and the memory 402 can store data used by the processor 401 when performing operations.
  • the process disclosed in the embodiment of the present application may be applied to the processor 401 or implemented by the processor 401.
  • each step of the signal processing flow can be completed by hardware integrated logic circuits in the processor 401 or instructions in the form of software.
  • the processor 401 may be a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, and can implement or execute the embodiments of the present application The disclosed methods, steps and logic block diagrams.
  • the general-purpose processor may be a microprocessor or any conventional processor.
  • the steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware processor, or executed and completed by a combination of hardware and software modules in the processor 401.
  • the software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • the storage medium is located in the memory 402, and the processor 401 reads the information in the memory 402 and completes the steps of the signal processing flow in combination with its hardware.
  • an embodiment of the present application also provides a computer-readable storage medium, including:
  • the computer-readable storage medium stores computer instructions, and when the computer instructions run on the computer, the computer executes the signaling transmission method on the user terminal side or the signaling transmission method on the base station side as described above.
  • the user terminal when the user terminal is configured with at least two service types at the same time, after receiving the high-level configuration information sent by the base station, when the PUCCH carrying UCI to be transmitted overlaps with the PUSCH scheduled by DCI, it is based on the Transmit the first service type of UCI, the second service type corresponding to the PUSCH scheduled by DCI, and high-level configuration information, and multiplex the UCI to be transmitted on the PUSCH scheduled by DCI and transmit to the base station; wherein, the high-level configuration information is at least two services Among the types, the code rate offset value used when UCI of at least one service type is multiplexed into PUSCH of any service type and/or the maximum resource ratio occupied by UCI on PUSCH, so as to be able to compare different service types in PUSCH UCI is used for transmission, and can guarantee the transmission performance of high-priority services in the case of multiplexing transmission.
  • the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the embodiments of the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the embodiments of the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device.
  • the device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
  • These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment.
  • the instructions provide steps for implementing functions specified in a flow or multiple flows in the flowchart and/or a block or multiple blocks in the block diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开了一种信令传输的方法、用户终端、基站及存储介质，用以解决现有技术中存在的不能对不同业务类的UCI进行传输的技术问题。该方法包括：被同时配置至少两种业务类型的用户终端，接收基站发送的高层配置信息；其中，高层配置信息为至少两种业务类型中，至少一种业务类型的UCI复用到任一种业务类型的PUSCH时使用的码率偏移值和/或UCI在PUSCH上占用的最大资源比例；当承载待传输UCI的PUCCH与DCI调度的PUSCH重叠时，基于待传输UCI的第一业务类型，DCI调度的PUSCH对应的第二业务类型，以及高层配置信息，将待传输UCI复用在DCI调度的PUSCH上传输到基站。

Description

一种信令传输的方法、用户终端、基站及存储介质
相关申请的交叉引用
本申请要求在2019年5月14日提交中国专利局、申请号为201910399221.3、发明名称为“一种信令传输的方法、用户终端、基站及存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，尤其是涉及一种信令传输的方法、用户终端、基站及存储介质。
背景技术
目前，在无线接入网(NEW Radio，NR)通信系统中，当用户终端(User Equipment，UE)需要向基站发送上行链路控制信息(uplink control information，UCI)时，可以通过在物理上行共享信道(Physical Uplink Share Channel，PUSCH)上进行传输，UCI通过PUSCH信道传输的信息包括混合自动重传请求的应答(Hybrid Automatic Repeat request Acknow ledgement，HARQ ACK)和信道状态信息(Channel State Information，CSI)等。
在现有技术中，对于同一业务类型的UCI在PUSCH上传输上所占用的RE资源是通过beta-offset值进行控制的，其中beta-offset值表示UCI和数据传输的码率偏移值。对于UCI映射在PUSCH上占用的资源元素(Resource Element，RE)，当PUSCH中存在上行共享信道(Uplink share channel，UL-SCH)数据传输时，按照数据码率和beta-offset确定UCI码率，并根据UCI码率确定UCI占用的RE资源个数；当PUSCH中不存在UL-SCH数据传输时，按照指示的码率和beta-offset分别确定HARQ-ACK和CSI Part 1占用的RE资源个数，PUSCH上可用于UCI传输的RE资源中剩余的RE资源用于CSI Part 2传输。在确定UCI的资源上限时，高层配置的参数scaling限制了PUSCH上能够分配给UCI的资源上限。
由于NR支持半静态的配置beta-offset值和动态的beta-offset指示，所以对于下行控制信息(Downlink Control Information，DCI)格式0_0或者不包含beta-offset指示域信息的DCI格式0_1调度的PUSCH，UCI传输使用的beta-offset值是基站通过RRC信令半静态配置的。而对于DCI格式0_1调度的PUSCH，当配置使用动态的beta-offset指示时，在DCI格式0_1中包含2比特的指示信息，用于指示RRC配置的4组beta-offset值中的一个，每一组beta-offset值包含多个值，对应于不同的UCI类型或者比特数。
当NR需要支持多种业务类型的混合传输时，将会出现不同业务类型的物理上行链路控制信道(Physical Uplink Control Channel，PUCCH)和PUSCH的重叠，如果仍使用目前的UCI在PUSCH上的复用传输办法，将不能保证业务类型优先级较高的UCI或者PUSCH的传输性能。而目前还没有不同业务类型的UCI和PUSCH之间的复用传输方案。例如，当支持高可靠低延迟业务(Ultra-Reliability and Low-Latency Service，URLLC)的UCI在增强移动宽带(Enhanced Mobile Broadband，eMBB)的PUSCH上复用传输时，由于URLLC UCI的传输可靠性要求远高于eMBB PUSCH的传输可靠性，URLLC UCI和eMBB PUSCH之间的码率偏移值和eMBB UCI和eMBB PUSCH之间的码率偏移值有较大的差异。如果按照现有方式配置四组UCI和数据传输的码率偏移值，则无法动态的适应所有情况，导致UCI在PUSCH上的传输性能下降。
鉴于此，在PUSCH中如何对不同业务类的UCI进行传输，成为一个亟待解决的技术问题。
发明内容
本申请提供一种信令传输的方法、用户终端、基站及存储介质，用以解决现有技术中存在的在PUSCH中不能对不同业务类的UCI进行传输的技术问题。
第一方面，为解决上述技术问题，本申请实施例提供的一种信令传输的方法，应用于用户终端，所述用户终端被同时配置至少两种业务类型，该方法的技术方案如下：
接收基站发送的高层配置信息；其中，所述高层配置信息为所述至少两种业务类型中，至少一种业务类型的UCI复用到任一种业务类型的PUSCH时使用的码率偏移值和/或UCI在PUSCH上占用的最大资源比例；
当承载待传输UCI的PUCCH与DCI调度的PUSCH重叠时，基于所述待传输UCI的第一业务类型，所述DCI调度的PUSCH对应的第二业务类型，以及所述高层配置信息，将所述待传输UCI复用在所述DCI调度的PUSCH上传输到所述基站。
当用户终端被同时配置至少两种业务类型时，通过在接收基站发送的高层配置信息后，当承载待传输UCI的PUCCH与DCI调度的PUSCH重叠时，基于待传输UCI的第一业务类型，DCI调度的PUSCH对应的第二业务类型，以及高层配置信息，将待传输UCI复用在DCI调度的PUSCH上传输到基站；其中，高层配置信息为至少两种业务类型中，至少一种业务类型的UCI复用到任一种业务类型的PUSCH时使用的码率偏移值和/或UCI在PUSCH上占用的最大资源比例，从而能够在PUSCH中对不同业务类型的UCI进行传输，并能在复用传输的情况下保证优先级高的业务的传输性能。
可选的，基于所述待传输UCI的第一业务类型，所述DCI调度的PUSCH对应的第二业务类型，以及所述高层配置信息，将所述待传输UCI复用在所述DCI调度的PUSCH上传输到所述基站，包括：
若所述DCI的格式为0_0，或不包含码率偏移指示域信息的0_1，则基于所述第一业务类型和所述第二业务类型，从所述高层配置信息中匹配出对应的一组码率偏移值和/或最大资源比例，将所述待传输UCI复用在所述DCI调度的PUSCH上传输到所述基站；
若所述DCI的格式为包含动态的码率偏移指示域信息的0_1，则基于所述第一业务类型和所述第二业务类型，从所述高层配置信息中匹配出对应的四组码率偏移值和/或最大资源比例；并根据所述DCI中携带的2比特指示信息，确定实际使用的一组码率偏移值和/或最大资源比例，将所述待传输UCI复用在所述DCI调度的PUSCH上传输到所述基站。
可选的，若所述DCI的格式为0_0，或不包含码率偏移指示域信息的0_1，则基于所述第一业务类型和所述第二业务类型，从所述高层配置信息中匹配出对应的一组码率偏移值和/或最大资源比例，包括：
若所述第一业务类型为URLLC，所述第二业务类型为eMBB，则从所述高层配置信息中获取URLLC UCI和eMBB PUSCH对应的一组码率偏移值和/或最大资源比例；
若所述第一业务类型为URLLC，所述第二业务类型为URLLC，则从所述高层配置信息中获取URLLC UCI和URLLC PUSCH对应的一组码率偏移值和/或最大资源比例；
若所述第一业务类型为eMBB，所述第二业务类型为URLLC，则从所述高层配置信息中获取eMBB UCI和URLLC PUSCH对应的一组码率偏移值和/或最大资源比例；
若所述第一业务类型为eMBB，所述第二业务类型为eMBB，则从所述高层配置信息中获取eMBB UCI和eMBB PUSCH对应的一组码率偏移值和/或最大资源比例。
可选的，若所述DCI的格式为包含动态的码率偏移指示域信息的0_1，则基于所述第一业务类型和所述第二业务类型，从所述高层配置信息中匹配出对应的四组码率偏移值和/或最大资源比例，包括：
若所述第一业务类型为URLLC，所述第二业务类型为eMBB，则从所述高层配置信息中获取URLLC UCI和eMBB PUSCH对应的四组码率偏移值和/或最大资源比例；
若所述第一业务类型为URLLC，所述第二业务类型为URLLC，则从所述高层配置信息中获取URLLC UCI和URLLC PUSCH对应的四组码率偏移值和/或最大资源比例；
若所述第一业务类型为eMBB，所述第二业务类型为URLLC，则从所述高层配置信息中获取eMBB UCI和URLLC PUSCH对应的四组码率偏移值和/或最大资源比例；
若所述第一业务类型为eMBB，所述第二业务类型为eMBB，则从所述高层配置信息 中获取eMBB UCI和eMBB PUSCH对应的四组码率偏移值和/或最大资源比例。
可选的，所述码率偏移值包括动态的码率偏移值和静态的码率偏移值；其中，所述静态的码率偏移值包括一组偏移值，所述动态的码率偏移值包括四组偏移值。
第二方面，本申请实施例提供的一种信令传输的方法，应用于基站，该方法的技术方案如下：
发送用户终端被同时配置的至少两种业务类型的高层配置信息到所述用户终端，其中，所述高层配置信息为所述至少两种业务类型中，至少一种业务类型的UCI复用到任一种业务类型的PUSCH时使用的码率偏移值和/或UCI在PUSCH上占用的最大资源比例；使得当承载所述用户终端的待传输UCI的PUCCH与DCI调度的PUSCH重叠时，让所述用户终端根据所述待传输UCI的业务类型和所述DCI调度的PUSCH及所述高层配置信息，将所述待传输UCI复用在所述DCI调度的PUSCH上进行传输。
可选的，所述码率偏移值包括动态的码率偏移值和静态的码率偏移值；其中，所述静态的码率偏移值包括一组偏移值，所述动态的码率偏移值包括四组偏移值。
可选的，所述高层配置信息，包括：
若调度PUSCH的DCI的格式为0_0，或不包含码率偏移值指示域信息的0_1时，所述至少两种业务类型的每种组合对应一组码率偏移值和/或UCI在PUSCH上占用的最大资源比例；
若调度PUSCH的DCI的格式为包含动态的码率偏移值的指示域信息的0_1时，所述至少两种业务类型的每种组合都对应四组码率偏移值和/或UCI在PUSCH上占用的最大资源比例。
可选的，所述至少两种业务类型为eMBB和URLLC时，包含的组合为：
eMBB UCI与URLLC PUSCH；
URLLC UCI与eMBB PUSCH；
eMBB UCI与eMBB PUSCH；
URLLC UCI与URLLC PUSCH。
第三方面，本申请实施例提供了一种用于信令传输的用户终端，该用户终端被同时配置至少两种业务类型，该终端包括：
接收单元：用于接收基站发送的高层配置信息；其中，所述高层配置信息为所述至少两种业务类型中，至少一种业务类型的UCI复用到任一种业务类型的PUSCH时使用的码率偏移值和/或UCI在PUSCH上占用的最大资源比例；
复用传输单元，用于当承载待传输UCI的PUCCH与DCI调度的PUSCH重叠时，基 于所述待传输UCI的第一业务类型，所述DCI调度的PUSCH对应的第二业务类型，以及所述高层配置信息，将所述待传输UCI复用在所述DCI调度的PUSCH上传输到所述基站。
可选的，所述复用传输单元用于：
若所述DCI的格式为0_0，或不包含码率偏移指示域信息的0_1，则基于所述第一业务类型和所述第二业务类型，从所述高层配置信息中匹配出对应的一组码率偏移值和/或最大资源比例，将所述待传输UCI复用在所述DCI调度的PUSCH上传输到所述基站；
若所述DCI的格式为包含动态的码率偏移指示域信息的0_1，则基于所述第一业务类型和所述第二业务类型，从所述高层配置信息中匹配出对应的四组码率偏移值和/或最大资源比例；并根据所述DCI中携带的2比特指示信息，确定实际使用的一组码率偏移值和/或最大资源比例，将所述待传输UCI复用在所述DCI调度的PUSCH上传输到所述基站。
可选的，所述复用传输单元还用于：
若所述第一业务类型为URLLC，所述第二业务类型为eMBB，则从所述高层配置信息中获取URLLC UCI和eMBB PUSCH对应的一组码率偏移值和/或最大资源比例；
若所述第一业务类型为URLLC，所述第二业务类型为URLLC，则从所述高层配置信息中获取URLLC UCI和URLLC PUSCH对应的一组码率偏移值和/或最大资源比例；
若所述第一业务类型为eMBB，所述第二业务类型为URLLC，则从所述高层配置信息中获取eMBB UCI和URLLC PUSCH对应的一组码率偏移值和/或最大资源比例；
若所述第一业务类型为eMBB，所述第二业务类型为eMBB，则从所述高层配置信息中获取eMBB UCI和eMBB PUSCH对应的一组码率偏移值和/或最大资源比例。
可选的，所述复用传输单元还用于：
若所述第一业务类型为URLLC，所述第二业务类型为eMBB，则从所述高层配置信息中获取URLLC UCI和eMBB PUSCH对应的四组码率偏移值和/或最大资源比例；
若所述第一业务类型为URLLC，所述第二业务类型为URLLC，则从所述高层配置信息中获取URLLC UCI和URLLC PUSCH对应的四组码率偏移值和/或最大资源比例；
若所述第一业务类型为eMBB，所述第二业务类型为URLLC，则从所述高层配置信息中获取eMBB UCI和URLLC PUSCH对应的四组码率偏移值和/或最大资源比例；
若所述第一业务类型为eMBB，所述第二业务类型为eMBB，则从所述高层配置信息中获取eMBB UCI和eMBB PUSCH对应的四组码率偏移值和/或最大资源比例。
可选的，所述码率偏移值包括动态的码率偏移值和静态的码率偏移值；其中，所述静态的码率偏移值包括一组偏移值，所述动态的码率偏移值包括四组偏移值。
第四方面，本申请实施例还提供一种用户终端，该用户终端被同时配置至少两种业务 类型，该用户终端包括：处理器、存储器和收发机；
其中，处理器，用于读取存储器中的程序并执行下列过程：
接收基站发送的高层配置信息；其中，所述高层配置信息为所述至少两种业务类型中，至少一种业务类型的UCI复用到任一种业务类型的PUSCH时使用的码率偏移值和/或UCI在PUSCH上占用的最大资源比例；
当承载待传输UCI的PUCCH与DCI调度的PUSCH重叠时，基于所述待传输UCI的第一业务类型，所述DCI调度的PUSCH对应的第二业务类型，以及所述高层配置信息，将所述待传输UCI复用在所述DCI调度的PUSCH上传输到所述基站。
可选的，所述处理器还用于：
若所述DCI的格式为0_0，或不包含码率偏移指示域信息的0_1，则基于所述第一业务类型和所述第二业务类型，从所述高层配置信息中匹配出对应的一组码率偏移值和/或最大资源比例，将所述待传输UCI复用在所述DCI调度的PUSCH上传输到所述基站；
若所述DCI的格式为包含动态的码率偏移指示域信息的0_1，则基于所述第一业务类型和所述第二业务类型，从所述高层配置信息中匹配出对应的四组码率偏移值和/或最大资源比例；并根据所述DCI中携带的2比特指示信息，确定实际使用的一组码率偏移值和/或最大资源比例，将所述待传输UCI复用在所述DCI调度的PUSCH上传输到所述基站。
可选的，所述处理器还用于：
若所述第一业务类型为URLLC，所述第二业务类型为eMBB，则从所述高层配置信息中获取URLLC UCI和eMBB PUSCH对应的一组码率偏移值和/或最大资源比例；
若所述第一业务类型为URLLC，所述第二业务类型为URLLC，则从所述高层配置信息中获取URLLC UCI和URLLC PUSCH对应的一组码率偏移值和/或最大资源比例；
若所述第一业务类型为eMBB，所述第二业务类型为URLLC，则从所述高层配置信息中获取eMBB UCI和URLLC PUSCH对应的一组码率偏移值和/或最大资源比例；
若所述第一业务类型为eMBB，所述第二业务类型为eMBB，则从所述高层配置信息中获取eMBB UCI和eMBB PUSCH对应的一组码率偏移值和/或最大资源比例。
可选的，所述处理器还用于：
若所述第一业务类型为URLLC，所述第二业务类型为eMBB，则从所述高层配置信息中获取URLLC UCI和eMBB PUSCH对应的四组码率偏移值和/或最大资源比例；
若所述第一业务类型为URLLC，所述第二业务类型为URLLC，则从所述高层配置信息中获取URLLC UCI和URLLC PUSCH对应的四组码率偏移值和/或最大资源比例；
若所述第一业务类型为eMBB，所述第二业务类型为URLLC，则从所述高层配置信息 中获取eMBB UCI和URLLC PUSCH对应的四组码率偏移值和/或最大资源比例；
若所述第一业务类型为eMBB，所述第二业务类型为eMBB，则从所述高层配置信息中获取eMBB UCI和eMBB PUSCH对应的四组码率偏移值和/或最大资源比例。
可选的，所述码率偏移值包括动态的码率偏移值和静态的码率偏移值；其中，所述静态的码率偏移值包括一组偏移值，所述动态的码率偏移值包括四组偏移值。
第五方面，本申请实施例还提供一种基站，该基站包括：处理器、存储器和收发机；
其中，处理器，用于读取存储器中的程序并执行下列过程：
发送用户终端被同时配置的至少两种业务类型的高层配置信息到所述用户终端，其中，所述高层配置信息为所述至少两种业务类型中，至少一种业务类型的UCI复用到任一种业务类型的PUSCH时使用的码率偏移值和/或UCI在PUSCH上占用的最大资源比例；使得当承载所述用户终端的待传输UCI的PUCCH与DCI调度的PUSCH重叠时，让所述用户终端根据所述待传输UCI的业务类型和所述DCI调度的PUSCH及所述高层配置信息，将所述待传输UCI复用在所述DCI调度的PUSCH上进行传输。
可选的，所述码率偏移值包括动态的码率偏移值和静态的码率偏移值；其中，所述静态的码率偏移值包括一组偏移值，所述动态的码率偏移值包括四组偏移值。
可选的，所述高层配置信息，包括：
若调度PUSCH的DCI的格式为0_0，或不包含码率偏移值指示域信息的0_1时，所述至少两种业务类型的每种组合对应一组码率偏移值和/或UCI在PUSCH上占用的最大资源比例；
若调度PUSCH的DCI的格式为包含动态的码率偏移值的指示域信息的0_1时，所述至少两种业务类型的每种组合都对应四组码率偏移值和/或UCI在PUSCH上占用的最大资源比例。
可选的，所述至少两种业务类型为eMBB和URLLC时，包含的组合为：
eMBB UCI与URLLC PUSCH；
URLLC UCI与eMBB PUSCH；
eMBB UCI与eMBB PUSCH；
URLLC UCI与URLLC PUSCH。
第六方面，本申请实施例还提供一种计算机可读存储介质，包括：
所述计算机可读存储介质存储有计算机指令，当所述计算机指令在计算机上运行时，使得计算机执行如上述第一方面或第二方面所述的方法。
通过本申请实施例的上述一个或多个实施例中的技术方案，本申请实施例至少具有如 下技术效果：
在本申请提供的实施例中，当用户终端被同时配置至少两种业务类型时，通过在接收基站发送的高层配置信息后，当承载待传输UCI的PUCCH与DCI调度的PUSCH重叠时，基于待传输UCI的第一业务类型，DCI调度的PUSCH对应的第二业务类型，以及高层配置信息，将待传输UCI复用在DCI调度的PUSCH上传输到基站；其中，高层配置信息为至少两种业务类型中，至少一种业务类型的UCI复用到任一种业务类型的PUSCH时使用的码率偏移值和/或UCI在PUSCH上占用的最大资源比例，从而能够在PUSCH中对不同业务类型的UCI进行传输，并能在复用传输的情况下保证优先级高的业务的传输性能。
附图说明
图1为本申请实施例提供的用户终端侧的一种信令传输方法的流程图；
图2为本申请实施例提供的一种用户终端的结构示意图；
图3为本申请实施例提供的另一种用户终端的结构示意图；
图4为本申请实施例提供的一种基站的结构示意图。
具体实施方式
本申请实施列提供一种信令传输的方法、用户终端、基站及装置，以解决现有技术中存在的在PUSCH中不能对不同业务类的UCI进行传输的技术问题。
本申请实施例提供的一种信令传输的方法，应用于被同时配置至少两种业务类型的用户终端，该方法包括：接收基站发送的高层配置信息；其中，高层配置信息为至少两种业务类型中，至少一种业务类型的UCI复用到任一种业务类型的PUSCH时使用的码率偏移值和/或UCI在PUSCH上占用的最大资源比例；当承载待传输UCI的PUCCH与DCI调度的PUSCH重叠时，基于待传输UCI的第一业务类型，DCI调度的PUSCH对应的第二业务类型，以及高层配置信息，将待传输UCI复用在DCI调度的PUSCH上传输到基站。
由于在上述方案中，当用户终端被同时配置至少两种业务类型时，通过在接收基站发送的高层配置信息后，当承载待传输UCI的PUCCH与DCI调度的PUSCH重叠时，基于待传输UCI的第一业务类型、DCI调度的PUSCH对应的第二业务类型以及高层配置信息，将待传输UCI复用在DCI调度的PUSCH上传输到基站；其中，高层配置信息为至少两种业务类型中，至少一种业务类型的UCI复用到任一种业务类型的PUSCH时使用的码率偏移值和/或UCI在PUSCH上占用的最大资源比例，从而能够在PUSCH中对不同业务类型的UCI进行传输，并能在复用传输的情况下保证优先级高的业务的传输性能。
为了更好的理解上述技术方案，下面通过附图以及具体实施例对本申请技术方案做详细的说明，应当理解本申请实施例以及实施例中的具体特征是对本申请技术方案的详细的说明，而不是对本申请技术方案的限定，在不冲突的情况下，本申请实施例以及实施例中的技术特征可以相互组合。
请参考图1，本申请实施例提供一种信令传输的方法，应用于被同时配置至少两种业务类型的用户终端，该方法的处理过程如下。
步骤101：接收基站发送的高层配置信息；其中，高层配置信息为至少两种业务类型中，至少一种业务类型的UCI复用到任一种业务类型的PUSCH时使用的码率偏移值和/或UCI在PUSCH上占用的最大资源比例；
步骤102：当承载待传输UCI的PUCCH与DCI调度的PUSCH重叠时，基于待传输UCI的第一业务类型，DCI调度的PUSCH对应的第二业务类型，以及高层配置信息，将待传输UCI复用在DCI调度的PUSCH上传输到基站。
本申请实施例中，可选地，不同业务类型的UCI对应不同优先级，也即不同业务类型的UCI可以是不同优先级的UCI。
本申请实施例中，码率偏移值包括动态的码率偏移值和静态的码率偏移值；静态的码率偏移值包括一组偏移值，动态的码率偏移值包括四组偏移值。
每一组偏移值包括下列信息：
betaOffsetACK-Index1，比特数小于或等于2对应的ACK码率偏移值；
betaOffsetACK-Index2，比特数为3～11对应的ACK码率偏移值；
betaOffsetACK-Index3，比特数大于11对应的ACK码率偏移值；
betaOffsetCSI-Part1-Index1，比特数小于11的CSI第一部分对应的码率偏移值；
betaOffsetCSI-Part1-Index2，比特数大于或等于11的CSI第一部分对应的码率偏移值；
betaOffsetCSI-Part2-Index1，比特数小于11的CSI第二部分对应的码率偏移值；
betaOffsetCSI-Part2-Index2，比特数大于或等于11的CSI第二部分对应的码率偏移值。
例如，至少两种业务类型为2种业务类型eMBB和URLLC，则在将UCI复用到PUSCH上时，它们对应的组合方式有四种：
组合一：eMBB UCI与URLLC PUSCH；
组合二：eMBB UCI与eMBB PUSCH；
组合三：URLLC UCI与eMBB PUSCH；
组合三：URLLC UCI与URLLC PUSCH。
由于码率偏移值分为静态的码率偏移值和动态的码率偏移值，所以上述每种组合又分 为静态的码率偏移值(只有一组偏移值)，和动态的码率偏移值(具体四组偏移值)。所以，当基站被同时配置两种业务类型在高层配置信息中就包含了上述四种组合分别对应的静态和动态的码率偏移值。
可选的，基于待传输UCI的第一业务类型，DCI调度的PUSCH对应的第二业务类型，以及高层配置信息，将待传输UCI复用在DCI调度的PUSCH上传输到基站，根据DCI中指示的码率偏移值的类型不同，包括以下两种方式：
第一种：若DCI的格式为0_0，或不包含码率偏移指示域信息的0_1，则基于第一业务类型和第二业务类型，从高层配置信息中匹配出对应的一组码率偏移值和/或最大资源比例，将待传输UCI复用在DCI调度的PUSCH上传输到基站。
例如，在用户终端接收到基站发送的高层配置信息后，在需要发生待传输UCI时，发现承载待传输UCI的PUCCH与DCI调度的PUSCH重叠，用户终端决定将待传输UCI复用在DCI调度的PUSCH上进行传输。假设待传输UCI的第一业务类型为eMBB、DCI调度的PUSCH的第二业务类型为URLLC，DCI的格式为0_0，或不包含码率偏移指示域信息的0_1，即说明使用的是静态的码率偏移值，对应配置了一组码率偏移值。
用户终端，根据待传输UCI的第一业务类型eMBB，及DCI调度的PUSCH的第二业务类型URLLC，从高层配置信息中找出与eMBB UCI和URLLC PUSCH对应的一组码率偏移值和/或UCI在PUSCH上占用的最大资源比例。并根据找出的这组码率偏移值将待传输UCI复用在DCI调度的PUSCH上传输给基站，使基站根据终端传输的待传输UCI和PUSCH的业务类型接收复用传输的待传输UCI和PUSCH。
第二种：若DCI的格式为包含动态的码率偏移指示域信息的0_1，则基于第一业务类型和第二业务类型，从高层配置信息中匹配出对应的四组码率偏移值和/或最大资源比例；并根据DCI中携带的2比特指示信息，确定实际使用的一组码率偏移值和/或最大资源比例，将待传输UCI复用在DCI调度的PUSCH上传输到基站。
例如，在用户终端接收到基站发送的高层配置信息后，在需要发生待传输UCI时，发现承载待传输UCI的PUCCH与DCI调度的PUSCH重叠，用户终端决定将待传输UCI复用在DCI调度的PUSCH上进行传输。假设待传输UCI的第一业务类型为eMBB、DCI调度的PUSCH的第二业务类型为URLLC，DCI的格式为包含动态的码率偏移指示域信息的0_1，即说明使用的是动态的码率偏移值，对应配置了四组码率偏移值。
用户终端，根据待传输UCI的第一业务类型eMBB，及DCI调度的PUSCH的第二业务类型URLLC，从高层配置信息中找出与eMBB UCI和URLLC PUSCH对应的四组码率偏移值和/或UCI在PUSCH上占用的最大资源比例，然后根据DCI中的2bit信息域(假 设对应的二进制数据为10，则对应第三组)从这四组码率偏移值中获取第三组码率偏移值，作为将待传输UCI复用在DCI调度的PUSCH上传输时使用的码率偏移值，使基站根据终端传输的待传输UCI和PUSCH的业务类型接收复用传输的待传输UCI和PUSCH。
当终端被同时配置两种业务类型，并且采用的是静态的码率偏移值时，UCI复用在PUSCH上将有4种组合方式，具体为若DCI的格式为0_0，或不包含码率偏移指示域信息的0_1，则基于第一业务类型和第二业务类型，从高层配置信息中匹配出对应的一组码率偏移值和/或最大资源比例，包括：
第一种方式：若第一业务类型为URLLC，第二业务类型为eMBB，则从高层配置信息中获取URLLC UCI和eMBB PUSCH对应的一组码率偏移值和/或最大资源比例。这样就可以将URLLC UCI复用在eMBB PUSCH上传输到基站。
第二种方式：若第一业务类型为URLLC，第二业务类型为URLLC，则从高层配置信息中获取URLLC UCI和URLLC PUSCH对应的一组码率偏移值和/或最大资源比例。这样就可以将URLLC UCI复用在URLLC PUSCH上传输到基站。
第三种方式：若第一业务类型为eMBB，第二业务类型为URLLC，则从高层配置信息中获取eMBB UCI和URLLC PUSCH对应的一组码率偏移值和/或最大资源比例。这样就可以将eMBB UCI复用在URLLC PUSCH上传输到基站。
第四种方式：若第一业务类型为eMBB，第二业务类型为eMBB，则从高层配置信息中获取eMBB UCI和eMBB PUSCH对应的一组码率偏移值和/或最大资源比例。这样就可以将eMBB UCI复用在eMBB PUSCH上传输到基站。
当终端被同时配置两种业务类型，并且采用的是动态的码率偏移值时，UCI复用在PUSCH上也将有4种组合方式，具体为若DCI的格式为包含动态的码率偏移指示域信息的0_1，则基于第一业务类型和第二业务类型，从高层配置信息中匹配出对应的四组码率偏移值和/或最大资源比例，包括：
第一种方式：若第一业务类型为URLLC，第二业务类型为eMBB，则从高层配置信息中获取URLLC UCI和eMBB PUSCH对应的四组码率偏移值和/或最大资源比例。这样在用户终端根据第一业务类型和第二业务类型从高层配置信息中，找出对应四组偏移值/和或最大资源比例后，根据DCI中的2比特信息域就能确定具体使用哪组偏移值，将URLLC UCI复用在eMBB PUSCH上传输给基站。
第二种方式：若第一业务类型为URLLC，第二业务类型为URLLC，则从高层配置信息中获取URLLC UCI和URLLC PUSCH对应的四组码率偏移值和/或最大资源比例。这样在用户终端根据第一业务类型和第二业务类型从高层配置信息中，找出对应四组偏移值/ 和或最大资源比例后，根据DCI中的2比特信息域就能确定具体使用哪组偏移值，将URLLC UCI复用在URLLC PUSCH上传输给基站。
第三种方式：若第一业务类型为eMBB，第二业务类型为URLLC，则从高层配置信息中获取eMBB UCI和URLLC PUSCH对应的四组码率偏移值和/或最大资源比例。这样在用户终端根据第一业务类型和第二业务类型从高层配置信息中，找出对应四组偏移值/和或最大资源比例后，根据DCI中的2比特信息域就能确定具体使用哪组偏移值，将eMBB UCI复用在URLLC PUSCH上传输给基站。
第四种方式：若第一业务类型为eMBB，第二业务类型为eMBB，则从高层配置信息中获取eMBB UCI和eMBB PUSCH对应的四组码率偏移值和/或最大资源比例。这样在用户终端根据第一业务类型和第二业务类型从高层配置信息中，找出对应四组偏移值/和或最大资源比例后，根据DCI中的2比特信息域就能确定具体使用哪组偏移值，将eMBB UCI复用在eMBB PUSCH上传输给基站。
需要说明的是，不管码率偏移值时静态还是动态情况下的，它们各自对应的四种方式中，由于基站发给用户终端的高层配置信息中，已经为上述每种方式提供了对应的码率偏移值和/或最大资源比例，所以，基站根据待发送UCI的第一业务类型，和当前DCI调用的PUSCH的第二业务类型，可以从高层配置信息中获取对应的码率偏移值和/或最大资源比例，将待发送UCI复用在DCI调用的PUSCH上传输给基站。并且，在上述各种方式中的UCI与PUSCH的组合中，不同组合对应的码率偏移值和/或最大资源比例可以相同，也可以不同，对于码率偏移值为动态的情况，每种组合中的四组偏移值一般而言是不同的，但也可以部分相同，具体在此不做限定。
需要说明的是，当用户终端被同时配置3种业务类型时，例如eMBB、URLLC、海量机器类通信(massive Machine Type Communication，mMTC)，当有2种业务类型的UCI(如eMBB和URLLC)需要复用在业务类型为mMTC的PUSCH上时，用户终端只需从高层配置信息中分别找出eMBB UCI与mMTC PUSCH对应的码率偏移值和/或最大资源比例，以及URLLC UCI与mMTC PUSCH对应的码率偏移值和/或最大资源比例，便可将eMBB UCI和URLLC UCI同时复用在mMTC PUSCH上传输给基站。以此类推，用户终端被同时配置大于3种业务类型时，按照排列组合的方式，高层配置信息中可以为每种组合方式配置对应的码率偏移值和/或最大资源比例，从而让用户终端在被同时配置多种业务类型时，能够从高层配置信息中找出实际使用的那个组合对应的码率偏移值和/或最大资源比例进行复用传输。
上面从用户终端的角度描述了用户终端被同时配置至少两种业务类型时，如何进行复 用传输的过程，下面将从基站的角度进行描述。
基于同一发明构思，本申请一实施例中提供一种信令传输的方法，该方法的具体实施方式可参见用户终端侧方法实施例部分的描述，重复之处不再赘述，该方法应用于基站，该方法包括：
发送用户终端被同时配置的至少两种业务类型的高层配置信息到用户终端，其中，高层配置信息为至少两种业务类型中，至少一种业务类型的UCI复用到任一种业务类型的PUSCH时使用的码率偏移值和/或UCI在PUSCH上占用的最大资源比例；使得当承载用户终端的待传输UCI的PUCCH与DCI调度的PUSCH重叠时，让用户终端根据待传输UCI的业务类型和DCI调度的PUSCH及高层配置信息，将待传输UCI复用在DCI调度的PUSCH上进行传输。
可选的，所述码率偏移值包括动态的码率偏移值和静态的码率偏移值；其中，静态的码率偏移值包括一组偏移值，动态的码率偏移值包括四组偏移值。
可选的，所述高层配置信息，包括：
若调度PUSCH的DCI的格式为0_0，或不包含码率偏移值指示域信息的0_1时，所述至少两种业务类型的每种组合对应一组码率偏移值和/或UCI在PUSCH上占用的最大资源比例；
若调度PUSCH的DCI的格式为包含动态的码率偏移值的指示域信息的0_1时，所述至少两种业务类型的每种组合都对应四组码率偏移值和/或UCI在PUSCH上占用的最大资源比例。
可选的，所述至少两种业务类型为eMBB和URLLC时，包含的组合为：
eMBB UCI与URLLC PUSCH；
URLLC UCI与eMBB PUSCH；
eMBB UCI与eMBB PUSCH；
URLLC UCI与URLLC PUSCH。
基于同一发明构思，本申请一实施例中提供一种用于信令传输的用户终端，该用户终端的信令传输方法的具体实施方式可参见用户终端侧方法实施例部分的描述，重复之处不再赘述，请参见图2，该用户终端包括：
接收单元201：用于接收基站发送的高层配置信息；其中，所述高层配置信息为所述至少两种业务类型中，至少一种业务类型的UCI复用到任一种业务类型的PUSCH时使用的码率偏移值和/或UCI在PUSCH上占用的最大资源比例；
复用传输单元202，用于当承载待传输UCI的PUCCH与DCI调度的PUSCH重叠时， 基于所述待传输UCI的第一业务类型，所述DCI调度的PUSCH对应的第二业务类型，以及所述高层配置信息，将所述待传输UCI复用在所述DCI调度的PUSCH上传输到所述基站。
可选的，所述复用传输单元202用于：
若所述DCI的格式为0_0，或不包含码率偏移指示域信息的0_1，则基于所述第一业务类型和所述第二业务类型，从所述高层配置信息中匹配出对应的一组码率偏移值和/或最大资源比例，将所述待传输UCI复用在所述DCI调度的PUSCH上传输到所述基站；
若所述DCI的格式为包含动态的码率偏移指示域信息的0_1，则基于所述第一业务类型和所述第二业务类型，从所述高层配置信息中匹配出对应的四组码率偏移值和/或最大资源比例；并根据所述DCI中携带的2比特指示信息，确定实际使用的一组码率偏移值和/或最大资源比例，将所述待传输UCI复用在所述DCI调度的PUSCH上传输到所述基站。
可选的，所述复用传输单元202还用于：
若所述第一业务类型为URLLC，所述第二业务类型为eMBB，则从所述高层配置信息中获取URLLC UCI和eMBB PUSCH对应的一组码率偏移值和/或最大资源比例；
若所述第一业务类型为URLLC，所述第二业务类型为URLLC，则从所述高层配置信息中获取URLLC UCI和URLLC PUSCH对应的一组码率偏移值和/或最大资源比例；
若所述第一业务类型为eMBB，所述第二业务类型为URLLC，则从所述高层配置信息中获取eMBB UCI和URLLC PUSCH对应的一组码率偏移值和/或最大资源比例；
若所述第一业务类型为eMBB，所述第二业务类型为eMBB，则从所述高层配置信息中获取eMBB UCI和eMBB PUSCH对应的一组码率偏移值和/或最大资源比例。
可选的，所述复用传输单元202还用于：
若所述第一业务类型为URLLC，所述第二业务类型为eMBB，则从所述高层配置信息中获取URLLC UCI和eMBB PUSCH对应的四组码率偏移值和/或最大资源比例；
若所述第一业务类型为URLLC，所述第二业务类型为URLLC，则从所述高层配置信息中获取URLLC UCI和URLLC PUSCH对应的四组码率偏移值和/或最大资源比例；
若所述第一业务类型为eMBB，所述第二业务类型为URLLC，则从所述高层配置信息中获取eMBB UCI和URLLC PUSCH对应的四组码率偏移值和/或最大资源比例；
若所述第一业务类型为eMBB，所述第二业务类型为eMBB，则从所述高层配置信息中获取eMBB UCI和eMBB PUSCH对应的四组码率偏移值和/或最大资源比例。
可选的，所述码率偏移值包括动态的码率偏移值和静态的码率偏移值；其中，所述静态的码率偏移值包括一组偏移值，所述动态的码率偏移值包括四组偏移值。
如图3所示，本申请实施例提供的一种用户终端，该用户终端被同时配置至少两种业务类型，该用户终端包括：处理器301、存储器302和收发机303；
其中，处理器301，用于读取存储器302中的程序并执行下列过程：
接收基站发送的高层配置信息；其中，所述高层配置信息为所述至少两种业务类型中，至少一种业务类型的UCI复用到任一种业务类型的PUSCH时使用的码率偏移值和/或UCI在PUSCH上占用的最大资源比例；
当承载待传输UCI的PUCCH与DCI调度的PUSCH重叠时，基于所述待传输UCI的第一业务类型，所述DCI调度的PUSCH对应的第二业务类型，以及所述高层配置信息，将所述待传输UCI复用在所述DCI调度的PUSCH上传输到所述基站。
可选的，所述处理器301还用于：
若所述DCI的格式为0_0，或不包含码率偏移指示域信息的0_1，则基于所述第一业务类型和所述第二业务类型，从所述高层配置信息中匹配出对应的一组码率偏移值和/或最大资源比例，将所述待传输UCI复用在所述DCI调度的PUSCH上传输到所述基站；
若所述DCI的格式为包含动态的码率偏移指示域信息的0_1，则基于所述第一业务类型和所述第二业务类型，从所述高层配置信息中匹配出对应的四组码率偏移值和/或最大资源比例；并根据所述DCI中携带的2比特指示信息，确定实际使用的一组码率偏移值和/或最大资源比例，将所述待传输UCI复用在所述DCI调度的PUSCH上传输到所述基站。
可选的，所述处理器301还用于：
若所述第一业务类型为URLLC，所述第二业务类型为eMBB，则从所述高层配置信息中获取URLLC UCI和eMBB PUSCH对应的一组码率偏移值和/或最大资源比例；
若所述第一业务类型为URLLC，所述第二业务类型为URLLC，则从所述高层配置信息中获取URLLC UCI和URLLC PUSCH对应的一组码率偏移值和/或最大资源比例；
若所述第一业务类型为eMBB，所述第二业务类型为URLLC，则从所述高层配置信息中获取eMBB UCI和URLLC PUSCH对应的一组码率偏移值和/或最大资源比例；
若所述第一业务类型为eMBB，所述第二业务类型为eMBB，则从所述高层配置信息中获取eMBB UCI和eMBB PUSCH对应的一组码率偏移值和/或最大资源比例。
可选的，所述处理器301还用于：
若所述第一业务类型为URLLC，所述第二业务类型为eMBB，则从所述高层配置信息中获取URLLC UCI和eMBB PUSCH对应的四组码率偏移值和/或最大资源比例；
若所述第一业务类型为URLLC，所述第二业务类型为URLLC，则从所述高层配置信息中获取URLLC UCI和URLLC PUSCH对应的四组码率偏移值和/或最大资源比例；
若所述第一业务类型为eMBB，所述第二业务类型为URLLC，则从所述高层配置信息中获取eMBB UCI和URLLC PUSCH对应的四组码率偏移值和/或最大资源比例；
若所述第一业务类型为eMBB，所述第二业务类型为eMBB，则从所述高层配置信息中获取eMBB UCI和eMBB PUSCH对应的四组码率偏移值和/或最大资源比例。
可选的，所述码率偏移值包括动态的码率偏移值和静态的码率偏移值；其中，所述静态的码率偏移值包括一组偏移值，所述动态的码率偏移值包括四组偏移值。
处理器301负责管理总线架构和通常的处理，存储器302可以存储处理器301在执行操作时所使用的数据。收发机303用于在处理器301的控制下接收和发送数据。
总线架构可以包括任意数量的互联的总线和桥，具体由处理器301代表的一个或多个处理器和存储器302代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。处理器301负责管理总线架构和通常的处理，存储器302可以存储处理器301在执行操作时所使用的数据。
本申请实施例揭示的流程，可以应用于处理器301中，或者由处理器301实现。在实现过程中，信号处理流程的各步骤可以通过处理器301中的硬件的集成逻辑电路或者软件形式的指令完成。处理器301可以是通用处理器、数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器301中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器302，处理器301读取存储器302中的信息，结合其硬件完成信号处理流程的步骤。
如图4所示，本申请实施例提供的一种基站，该基站包括：处理器401、存储器402和收发机403；
其中，处理器401，用于读取存储器402中的程序并执行下列过程：
发送用户终端被同时配置的至少两种业务类型的高层配置信息到所述用户终端，其中，所述高层配置信息为所述至少两种业务类型中，至少一种业务类型的UCI复用到任一种业务类型的PUSCH时使用的码率偏移值和/或UCI在PUSCH上占用的最大资源比例；使得当承载所述用户终端的待传输UCI的PUCCH与DCI调度的PUSCH重叠时，让所述用户终端根据所述待传输UCI的业务类型和所述DCI调度的PUSCH及所述高层配置信息，将 所述待传输UCI复用在所述DCI调度的PUSCH上进行传输。
可选的，所述码率偏移值包括动态的码率偏移值和静态的码率偏移值；其中，所述静态的码率偏移值包括一组偏移值，所述动态的码率偏移值包括四组偏移值。
可选的，所述高层配置信息，包括：
若调度PUSCH的DCI的格式为0_0，或不包含码率偏移值指示域信息的0_1时，所述至少两种业务类型的每种组合对应一组码率偏移值和/或UCI在PUSCH上占用的最大资源比例；
若调度PUSCH的DCI的格式为包含动态的码率偏移值的指示域信息的0_1时，所述至少两种业务类型的每种组合都对应四组码率偏移值和/或UCI在PUSCH上占用的最大资源比例。
可选的，所述至少两种业务类型为eMBB和URLLC时，包含的组合为：
eMBB UCI与URLLC PUSCH；
URLLC UCI与eMBB PUSCH；
eMBB UCI与eMBB PUSCH；
URLLC UCI与URLLC PUSCH。
处理器401负责管理总线架构和通常的处理，存储器402可以存储处理器401在执行操作时所使用的数据。收发机403用于在处理器401的控制下接收和发送数据。
总线架构可以包括任意数量的互联的总线和桥，具体由处理器401代表的一个或多个处理器和存储器402代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。处理器401负责管理总线架构和通常的处理，存储器402可以存储处理器401在执行操作时所使用的数据。
本申请实施例揭示的流程，可以应用于处理器401中，或者由处理器401实现。在实现过程中，信号处理流程的各步骤可以通过处理器401中的硬件的集成逻辑电路或者软件形式的指令完成。处理器401可以是通用处理器、数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器401中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器402，处理器401读取存储器 402中的信息，结合其硬件完成信号处理流程的步骤。
基于同一发明构思，本申请实施例还提一种计算机可读存储介质，包括：
所述计算机可读存储介质存储有计算机指令，当所述计算机指令在计算机上运行时，使得计算机执行如上所述的用户终端侧的信令传输方法或基站侧的信令传输方法。
在本申请提供的实施例中，当用户终端被同时配置至少两种业务类型时，通过在接收基站发送的高层配置信息后，当承载待传输UCI的PUCCH与DCI调度的PUSCH重叠时，基于待传输UCI的第一业务类型，DCI调度的PUSCH对应的第二业务类型，以及高层配置信息，将待传输UCI复用在DCI调度的PUSCH上传输到基站；其中，高层配置信息为至少两种业务类型中，至少一种业务类型的UCI复用到任一种业务类型的PUSCH时使用的码率偏移值和/或UCI在PUSCH上占用的最大资源比例，从而能够在PUSCH中对不同业务类型的UCI进行传输，并能在复用传输的情况下保证优先级高的业务的传输性能。
本领域内的技术人员应明白，本申请实施例可提供为方法、系统、或计算机程序产品。因此，本申请实施例可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请实施例可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请实施例是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (20)

  1. 一种信令传输的方法，应用于用户终端，其特征在于，所述用户终端被同时配置至少两种业务类型，所述方法包括：
    接收基站发送的高层配置信息；其中，所述高层配置信息为所述至少两种业务类型中，至少一种业务类型的上行链路控制信息UCI复用到任一种业务类型的物理上行共享信道PUSCH时使用的码率偏移值和/或UCI在PUSCH上占用的最大资源比例；
    当承载待传输UCI的物理上行链路控制信道PUCCH与下行控制信息DCI调度的PUSCH重叠时，基于所述待传输UCI的第一业务类型、所述DCI调度的PUSCH对应的第二业务类型以及所述高层配置信息，将所述待传输UCI复用在所述DCI调度的PUSCH上传输到所述基站。
  2. 如权利要求1所述的方法，其特征在于，基于所述待传输UCI的第一业务类型、所述DCI调度的PUSCH对应的第二业务类型以及所述高层配置信息，将所述待传输UCI复用在所述DCI调度的PUSCH上传输到所述基站，包括：
    若所述DCI的格式为0_0或不包含码率偏移指示域信息的0_1，则基于所述第一业务类型和所述第二业务类型，从所述高层配置信息中匹配出对应的一组码率偏移值和/或最大资源比例，将所述待传输UCI复用在所述DCI调度的PUSCH上传输到所述基站；
    若所述DCI的格式为包含动态的码率偏移指示域信息的0_1，则基于所述第一业务类型和所述第二业务类型，从所述高层配置信息中匹配出对应的四组码率偏移值和/或最大资源比例；并根据所述DCI中携带的2比特指示信息，确定实际使用的一组码率偏移值和/或最大资源比例，将所述待传输UCI复用在所述DCI调度的PUSCH上传输到所述基站。
  3. 如权利要求2所述的方法，其特征在于，若所述DCI的格式为0_0或不包含码率偏移指示域信息的0_1，则基于所述第一业务类型和所述第二业务类型，从所述高层配置信息中匹配出对应的一组码率偏移值和/或最大资源比例，包括：
    若所述第一业务类型为高可靠低延迟业务URLLC，所述第二业务类型为增强移动宽带eMBB，则从所述高层配置信息中获取URLLC UCI和eMBB PUSCH对应的一组码率偏移值和/或最大资源比例；
    若所述第一业务类型为URLLC，所述第二业务类型为URLLC，则从所述高层配置信息中获取URLLC UCI和URLLC PUSCH对应的一组码率偏移值和/或最大资源比例；
    若所述第一业务类型为eMBB，所述第二业务类型为URLLC，则从所述高层配置信息中获取eMBB UCI和URLLC PUSCH对应的一组码率偏移值和/或最大资源比例；
    若所述第一业务类型为eMBB，所述第二业务类型为eMBB，则从所述高层配置信息中获取eMBB UCI和eMBB PUSCH对应的一组码率偏移值和/或最大资源比例。
  4. 如权利要求2所述的方法，其特征在于，若所述DCI的格式为包含动态的码率偏移指示域信息的0_1，则基于所述第一业务类型和所述第二业务类型，从所述高层配置信息中匹配出对应的四组码率偏移值和/或最大资源比例，包括：
    若所述第一业务类型为URLLC，所述第二业务类型为eMBB，则从所述高层配置信息中获取URLLC UCI和eMBB PUSCH对应的四组码率偏移值和/或最大资源比例；
    若所述第一业务类型为URLLC，所述第二业务类型为URLLC，则从所述高层配置信息中获取URLLC UCI和URLLC PUSCH对应的四组码率偏移值和/或最大资源比例；
    若所述第一业务类型为eMBB，所述第二业务类型为URLLC，则从所述高层配置信息中获取eMBB UCI和URLLC PUSCH对应的四组码率偏移值和/或最大资源比例；
    若所述第一业务类型为eMBB，所述第二业务类型为eMBB，则从所述高层配置信息中获取eMBB UCI和eMBB PUSCH对应的四组码率偏移值和/或最大资源比例。
  5. 如权利要求1-4任一项所述的方法，其特征在于，所述码率偏移值包括动态的码率偏移值和静态的码率偏移值；其中，所述静态的码率偏移值包括一组偏移值，所述动态的码率偏移值包括四组偏移值。
  6. 一种信令传输的方法，应用于基站，其特征在于，包括：
    发送用户终端被同时配置的至少两种业务类型的高层配置信息到所述用户终端，其中，所述高层配置信息为所述至少两种业务类型中，至少一种业务类型的上行链路控制信息UCI复用到任一种业务类型的物理上行共享信道PUSCH时使用的码率偏移值和/或UCI在PUSCH上占用的最大资源比例；使得当承载所述用户终端的待传输UCI的物理上行链路控制信道PUCCH与下行控制信息DCI调度的PUSCH重叠时，让所述用户终端根据所述待传输UCI的业务类型和所述DCI调度的PUSCH及所述高层配置信息，将所述待传输UCI复用在所述DCI调度的PUSCH上进行传输。
  7. 如权利要求6所述的方法，其特征在于，所述码率偏移值包括动态的码率偏移值和静态的码率偏移值；其中，所述静态的码率偏移值包括一组偏移值，所述动态的码率偏移值包括四组偏移值。
  8. 如权利要求7所述的方法，其特征在于，所述高层配置信息，包括：
    若调度PUSCH的DCI的格式为0_0或不包含码率偏移值指示域信息的0_1时，所述至少两种业务类型的每种组合对应一组码率偏移值和/或UCI在PUSCH上占用的最大资源比例；
    若调度PUSCH的DCI的格式为包含动态的码率偏移值的指示域信息的0_1时，所述至少两种业务类型的每种组合都对应四组码率偏移值和/或UCI在PUSCH上占用的最大资源比例。
  9. 如权利要求8所述的方法，其特征在于，所述至少两种业务类型为eMBB和URLLC时，包含的组合为：
    eMBBUCI与URLLC PUSCH；
    URLLC UCI与eMBBPUSCH；
    eMBB UCI与eMBB PUSCH；
    URLLC UCI与URLLC PUSCH。
  10. 一种用户终端，其特征在于，所述用户终端被同时配置至少两种业务类型，所述用户终端包括：
    接收单元：用于接收基站发送的高层配置信息；其中，所述高层配置信息为所述至少两种业务类型中，至少一种业务类型的上行链路控制信息UCI复用到任一种业务类型的物理上行共享信道PUSCH时使用的码率偏移值和/或UCI在PUSCH上占用的最大资源比例；
    复用传输单元，用于当承载待传输UCI的物理上行链路控制信道PUCCH与下行控制信息DCI调度的PUSCH重叠时，基于所述待传输UCI的第一业务类型、所述DCI调度的PUSCH对应的第二业务类型以及所述高层配置信息，将所述待传输UCI复用在所述DCI调度的PUSCH上传输到所述基站。
  11. 一种用户终端，其特征在于，用户终端被同时配置至少两种业务类型，该用户终端包括：处理器、存储器和收发机；
    其中，处理器，用于读取存储器中的程序并执行下列过程：
    接收基站发送的高层配置信息；其中，所述高层配置信息为所述至少两种业务类型中，至少一种业务类型的上行链路控制信息UCI复用到任一种业务类型的物理上行共享信道PUSCH时使用的码率偏移值和/或UCI在PUSCH上占用的最大资源比例；
    当承载待传输UCI的物理上行链路控制信道PUCCH与下行控制信息DCI调度的PUSCH重叠时，基于所述待传输UCI的第一业务类型，所述DCI调度的PUSCH对应的第二业务类型，以及所述高层配置信息，将所述待传输UCI复用在所述DCI调度的PUSCH上传输到所述基站。
  12. 如权利要求11所述的用户终端，其特征在于，所述处理器还用于：
    若所述DCI的格式为0_0或不包含码率偏移指示域信息的0_1，则基于所述第一业务类型和所述第二业务类型，从所述高层配置信息中匹配出对应的一组码率偏移值和/或最大 资源比例，将所述待传输UCI复用在所述DCI调度的PUSCH上传输到所述基站；
    若所述DCI的格式为包含动态的码率偏移指示域信息的0_1，则基于所述第一业务类型和所述第二业务类型，从所述高层配置信息中匹配出对应的四组码率偏移值和/或最大资源比例；并根据所述DCI中携带的2比特指示信息，确定实际使用的一组码率偏移值和/或最大资源比例，将所述待传输UCI复用在所述DCI调度的PUSCH上传输到所述基站。
  13. 如权利要求12所述的用户终端，其特征在于，所述处理器还用于：
    若所述第一业务类型为高可靠低延迟业务URLLC，所述第二业务类型为增强移动宽带eMBB，则从所述高层配置信息中获取URLLC UCI和eMBB PUSCH对应的一组码率偏移值和/或最大资源比例；
    若所述第一业务类型为URLLC，所述第二业务类型为URLLC，则从所述高层配置信息中获取URLLC UCI和URLLC PUSCH对应的一组码率偏移值和/或最大资源比例；
    若所述第一业务类型为eMBB，所述第二业务类型为URLLC，则从所述高层配置信息中获取eMBB UCI和URLLC PUSCH对应的一组码率偏移值和/或最大资源比例；
    若所述第一业务类型为eMBB，所述第二业务类型为eMBB，则从所述高层配置信息中获取eMBB UCI和eMBB PUSCH对应的一组码率偏移值和/或最大资源比例。
  14. 如权利要求12所述的用户终端，其特征在于，所述处理器还用于：
    若所述第一业务类型为URLLC，所述第二业务类型为eMBB，则从所述高层配置信息中获取URLLC UCI和eMBB PUSCH对应的四组码率偏移值和/或最大资源比例；
    若所述第一业务类型为URLLC，所述第二业务类型为URLLC，则从所述高层配置信息中获取URLLC UCI和URLLC PUSCH对应的四组码率偏移值和/或最大资源比例；
    若所述第一业务类型为eMBB，所述第二业务类型为URLLC，则从所述高层配置信息中获取eMBB UCI和URLLC PUSCH对应的四组码率偏移值和/或最大资源比例；
    若所述第一业务类型为eMBB，所述第二业务类型为eMBB，则从所述高层配置信息中获取eMBB UCI和eMBB PUSCH对应的四组码率偏移值和/或最大资源比例。
  15. 如权利要求11-14任一项所述的用户终端，其特征在于，所述码率偏移值包括动态的码率偏移值和静态的码率偏移值；其中，所述静态的码率偏移值包括一组偏移值，所述动态的码率偏移值包括四组偏移值。
  16. 一种基站，其特征在于，该基站包括：处理器、存储器和收发机；
    其中，处理器，用于读取存储器中的程序并执行下列过程：
    发送用户终端被同时配置的至少两种业务类型的高层配置信息到所述用户终端，其中，所述高层配置信息为所述至少两种业务类型中，至少一种业务类型的上行链路控制信息 UCI复用到任一种业务类型的物理上行共享信道PUSCH时使用的码率偏移值和/或UCI在PUSCH上占用的最大资源比例；使得当承载所述用户终端的待传输UCI的物理上行链路控制信道PUCCH与下行控制信息DCI调度的PUSCH重叠时，让所述用户终端根据所述待传输UCI的业务类型和所述DCI调度的PUSCH及所述高层配置信息，将所述待传输UCI复用在所述DCI调度的PUSCH上进行传输。
  17. 如权利要求16所述的基站，其特征在于，所述码率偏移值包括动态的码率偏移值和静态的码率偏移值；其中，所述静态的码率偏移值包括一组偏移值，所述动态的码率偏移值包括四组偏移值。
  18. 如权利要求16所述的基站，其特征在于，所述高层配置信息，包括：
    若调度PUSCH的DCI的格式为0_0，或不包含码率偏移值指示域信息的0_1时，所述至少两种业务类型的每种组合对应一组码率偏移值和/或UCI在PUSCH上占用的最大资源比例；
    若调度PUSCH的DCI的格式为包含动态的码率偏移值的指示域信息的0_1时，所述至少两种业务类型的每种组合都对应四组码率偏移值和/或UCI在PUSCH上占用的最大资源比例。
  19. 如权利要求18所述的基站，其特征在于，所述至少两种业务类型为eMBB和URLLC时，包含的组合为：
    eMBB UCI与URLLC PUSCH；
    URLLC UCI与eMBB PUSCH；
    eMBB UCI与eMBB PUSCH；
    URLLC UCI与URLLC PUSCH。
  20. 一种计算机可读存储介质，其特征在于：
    所述计算机可读存储介质存储有计算机指令，当所述计算机指令在计算机上运行时，使得计算机执行如权利要求1-9中任一项所述的方法。
PCT/CN2020/080749 2019-05-14 2020-03-23 一种信令传输的方法、用户终端、基站及存储介质 WO2020228419A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910399221.3 2019-05-14
CN201910399221.3A CN111953456B (zh) 2019-05-14 2019-05-14 一种信令传输的方法、用户终端、基站及存储介质

Publications (1)

Publication Number Publication Date
WO2020228419A1 true WO2020228419A1 (zh) 2020-11-19

Family

ID=73290020

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/080749 WO2020228419A1 (zh) 2019-05-14 2020-03-23 一种信令传输的方法、用户终端、基站及存储介质

Country Status (2)

Country Link
CN (1) CN111953456B (zh)
WO (1) WO2020228419A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112235868B (zh) * 2020-12-16 2021-04-13 京信通信系统（中国）有限公司 资源调度方法、装置、基站、终端设备和存储介质
CN116547936A (zh) * 2021-01-13 2023-08-04 华为技术有限公司 信息发送方法、信息接收方法及通信装置
CN115174016B (zh) * 2021-04-02 2023-12-26 大唐移动通信设备有限公司 信息传输方法、装置、设备以及存储介质
CN114399318B (zh) * 2022-01-19 2024-08-27 中国平安人寿保险股份有限公司 链路处理方法、装置、计算机设备及存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014046457A1 (en) * 2012-09-20 2014-03-27 Lg Electronics Inc. Method and apparatus for performing uplink transmission in a wireless communication system
CN108702776A (zh) * 2018-05-10 2018-10-23 北京小米移动软件有限公司 信息复用传输方法及装置、信息接收方法及装置

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101860411B (zh) * 2009-04-13 2013-03-06 电信科学技术研究院 高速下行分组接入中的资源分配方法及基站
MX362944B (es) * 2014-01-15 2019-02-27 Nec Corp Método para transmitir información de control del enlace ascendente, terminal inalámbrica y estación base.
KR101931948B1 (ko) * 2014-04-08 2018-12-24 엘지전자 주식회사 무선 자원의 용도 변경을 지원하는 무선 통신 시스템에서 상향링크 제어 정보 송신 방법 및 이를 위한 장치
US10616869B2 (en) * 2016-02-12 2020-04-07 Qualcomm Incorporated Uplink channel design for slot-based transmission time interval (TTI)
WO2018026224A1 (ko) * 2016-08-03 2018-02-08 엘지전자 주식회사 무선 통신 시스템에서 단말에 의해 수행되는 상향링크 통신 수행 방법 및 상기 방법을 이용하는 단말

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014046457A1 (en) * 2012-09-20 2014-03-27 Lg Electronics Inc. Method and apparatus for performing uplink transmission in a wireless communication system
CN108702776A (zh) * 2018-05-10 2018-10-23 北京小米移动软件有限公司 信息复用传输方法及装置、信息接收方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI ET AL.: "UCI Enhancements for URLLC", R1-1906058, 4 May 2019 (2019-05-04), XP051727515, DOI: 20200528084439Y *

Also Published As

Publication number Publication date
CN111953456B (zh) 2021-10-29
CN111953456A (zh) 2020-11-17

Similar Documents

Publication Publication Date Title
WO2020228419A1 (zh) 一种信令传输的方法、用户终端、基站及存储介质
CN110278062B (zh) 资源指示、确定方法及装置
CN111435878B (zh) 一种信息传输方法、终端及网络设备
CN110505697B (zh) 一种混合自动重传请求的传输方法、终端及基站
CN110809320B (zh) 一种上行控制信息的传输方法、设备和计算机存储介质
US12101762B2 (en) Information transmission method, apparatus and device
US11646819B2 (en) Information transmission method, terminal and base station
US12101776B2 (en) Uplink control channel resource allocation methods and devices
JP2020523884A (ja) アップリンク制御チャネルの送信方法、受信方法、装置、端末及び基地局
EP4007404B1 (en) Uci transmission and reception methods and apparatuses
CN111953458B (zh) 一种pucch资源确定方法和通信设备
CN111726216A (zh) 一种应答信息处理方法、设备及存储介质
CN110035525A (zh) 信道状态信息传输资源的确定方法、用户设备及基站
EP3739997B1 (en) Method and device for determining cap of transmission resources available for control information, and communication apparatus
EP4322436A1 (en) Hybrid automatic repeat request acknowledgement feedback method and apparatus
US12101797B2 (en) Methods and systems for use of carrier aggregation capability
CN113285789B (zh) 辅链路控制信息的资源指示方法与装置、终端设备
WO2022193329A1 (zh) 上行控制信息传输资源的确定方法、装置、设备及介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20805892

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20805892

Country of ref document: EP

Kind code of ref document: A1