WO2024022159A1 - 信息配置方法、装置、终端、网络侧设备及可读存储介质 - Google Patents

信息配置方法、装置、终端、网络侧设备及可读存储介质 Download PDF

Info

Publication number
WO2024022159A1
WO2024022159A1 PCT/CN2023/107885 CN2023107885W WO2024022159A1 WO 2024022159 A1 WO2024022159 A1 WO 2024022159A1 CN 2023107885 W CN2023107885 W CN 2023107885W WO 2024022159 A1 WO2024022159 A1 WO 2024022159A1
Authority
WO
WIPO (PCT)
Prior art keywords
time domain
pucch
domain unit
configuration information
configuration
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2023/107885
Other languages
English (en)
French (fr)
Inventor
曾超君
王理惠
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Vivo Mobile Communication Co Ltd
Original Assignee
Vivo Mobile Communication Co Ltd
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 Vivo Mobile Communication Co Ltd filed Critical Vivo Mobile Communication Co Ltd
Publication of WO2024022159A1 publication Critical patent/WO2024022159A1/zh
Priority to US19/034,547 priority Critical patent/US20250175987A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/001—Synchronization between nodes
    • H04W56/0015—Synchronization between nodes one node acting as a reference for the others
    • 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
    • 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 signalling, i.e. of overhead other than pilot signals
    • 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/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • 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/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H04W72/231—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the layers above the physical layer, e.g. RRC or MAC-CE signalling

Definitions

  • This application belongs to the field of communication technology, and specifically relates to an information configuration method, device, terminal, network side equipment and readable storage medium.
  • This flexible duplex mode is: full duplex on the network side, that is, at the same time, uplink transmission and downlink transmission can be performed simultaneously at different frequency domain locations, and half duplex on the terminal side, which is the same as Time Division Duplex. TDD), at the same time, only uplink transmission or downlink transmission can be performed, and both cannot be performed at the same time.
  • TDD Time Division Duplex
  • Control channel Physical Uplink Control Channel
  • PUCCH Physical Uplink Control Channel
  • Embodiments of the present application provide an information configuration method, device, terminal, network side device and readable storage medium, which can solve the problem of how to ensure the performance of PUCCH transmission in flexible duplex mode.
  • the first aspect provides an information configuration method, including:
  • the terminal receives the first configuration information from the network side device
  • the first configuration information at most M sets of configuration information are configured for a single PUCCH resource, and each set of configuration information corresponds to a time domain unit that meets specific requirements; or, the first configuration information includes at most N PUCCH configurations , each PUCCH configuration corresponds to a time domain unit that meets specific requirements; the M is an integer greater than 1, and the N is an integer greater than 1.
  • the second aspect provides an information configuration method, including:
  • the network side device sends the first configuration information to the terminal
  • the first configuration information at most M sets of configuration information are configured for a single PUCCH resource, and each set of configuration information corresponds to a time domain unit that meets specific requirements; or, the first configuration information includes at most N items of PUCCH Configuration, each PUCCH configuration corresponds to a time domain unit that meets specific requirements; the M is an integer greater than 1, and the N is an integer greater than 1.
  • an information configuration device applied to a terminal, including:
  • a receiving module configured to receive the first configuration information from the network side device
  • the first configuration information at most M sets of configuration information are configured for a single PUCCH resource, and each set of configuration information corresponds to a time domain unit that meets specific requirements; or, the first configuration information includes at most N PUCCH configurations , each PUCCH configuration corresponds to a time domain unit that meets specific requirements; the M is an integer greater than 1, and the N is an integer greater than 1.
  • an information configuration device applied to network side equipment, including:
  • a sending module used to send the first configuration information to the terminal
  • the first configuration information at most M sets of configuration information are configured for a single PUCCH resource, and each set of configuration information corresponds to a time domain unit that meets specific requirements; or, the first configuration information includes at most N PUCCH configurations , each PUCCH configuration corresponds to a time domain unit that meets specific requirements; the M is an integer greater than 1, and the N is an integer greater than 1.
  • a terminal in a fifth aspect, includes a processor and a memory.
  • the memory stores programs or instructions that can be run on the processor.
  • the program or instructions are executed by the processor, the following implementations are implemented: The steps of the method described in one aspect.
  • a terminal including a processor and a communication interface, wherein the communication interface is used to receive first configuration information from a network side device; wherein in the first configuration information, for a single PUCCH resource Configure at most M sets of configuration information, each set of configuration information corresponding to a time domain unit that meets specific requirements; or, the first configuration information includes at most N PUCCH configurations, and each PUCCH configuration corresponds to a time domain unit that meets specific requirements;
  • the M is an integer greater than 1
  • the N is an integer greater than 1.
  • a network side device in a seventh aspect, includes a processor and a memory.
  • the memory stores programs or instructions that can be run on the processor.
  • the program or instructions are executed by the processor.
  • a network side device including a processor and a communication interface, wherein the communication interface is used to send first configuration information to a terminal; in the first configuration information, the maximum number of configurations for a single PUCCH resource is M sets of configuration information, each set of configuration information corresponds to a time domain unit that meets specific requirements; or, the first configuration information includes at most N PUCCH configurations, each PUCCH configuration corresponds to a time domain unit that meets specific requirements; M is an integer greater than 1, and N is an integer greater than 1.
  • a ninth aspect provides a communication system, including: a terminal and a network side device.
  • the terminal can be used to perform the steps of the information configuration method as described in the first aspect.
  • the network side device can be used to perform the steps of the information configuration method as described in the second aspect. The steps of the information configuration method.
  • a readable storage medium is provided. Programs or instructions are stored on the readable storage medium. When the programs or instructions are executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method are implemented as described in the first aspect. mentioned in the second aspect Method steps.
  • a chip in an eleventh aspect, includes a processor and a communication interface.
  • the communication interface is coupled to the processor.
  • the processor is used to run programs or instructions to implement the method described in the first aspect. The steps of a method, or steps of implementing a method as described in the second aspect.
  • a computer program/program product is provided, 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 as described in the first aspect
  • the terminal can receive the first configuration information from the network side device; in the first configuration information, up to M sets of configuration information are configured for a single PUCCH resource, and each set of configuration information is associated with a time domain unit that meets specific requirements. corresponding; or, the first configuration information includes at most N PUCCH configurations, each PUCCH configuration corresponding to a time domain unit that meets specific requirements. Therefore, for PUCCH transmission, parameters matching their related characteristics can be configured for different uplink resources, such as time-frequency location, code rate, power, etc., so as to make full use of uplink resources based on the characteristics of different uplink resources and ensure the performance of PUCCH transmission. .
  • Figure 1 is a block diagram of a wireless communication system applicable to the embodiment of the present application.
  • Figure 2 is a schematic diagram of the flexible duplex mode in the embodiment of the present application.
  • Figure 3 is a flow chart of an information configuration method provided by an embodiment of the present application.
  • Figure 4 is a flow chart of another information configuration method provided by an embodiment of the present application.
  • Figure 5 is a schematic structural diagram of an information configuration device provided by an embodiment of the present application.
  • Figure 6 is a schematic structural diagram of another information configuration device provided by an embodiment of the present application.
  • Figure 7 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • Figure 8 is a schematic structural diagram of a terminal provided by an embodiment of the present application.
  • Figure 9 is a schematic structural diagram of a network side device provided by an embodiment of the present application.
  • first, second, etc. in the description and claims of this application are used to distinguish similar objects and are not used to describe a specific order or sequence. It is to be understood that the terms so used are interchangeable under appropriate circumstances so that the embodiments of the present application can be practiced in sequences other than those illustrated or described herein, and that "first" and “second” are distinguished objects It is usually one type, and the number of objects is not limited.
  • the first object can be one or multiple.
  • “and/or” in the description and claims means at least one of the connected objects, The character “/” generally indicates that the related objects are in an "or” relationship.
  • LTE Long Term Evolution
  • LTE-Advanced, LTE-A Long Term Evolution
  • LTE-A Long Term Evolution
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency Division Multiple Access
  • NR New Radio
  • FIG. 1 shows a block diagram of a wireless communication system to which embodiments of the present application are applicable.
  • the wireless communication system includes a terminal 11 and a network side device 12.
  • the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, or a super mobile personal computer.
  • Tablet Personal Computer Tablet Personal Computer
  • laptop computer laptop computer
  • PDA Personal Digital Assistant
  • PDA Personal Digital Assistant
  • UMPC ultra-mobile personal computer
  • UMPC mobile Internet device
  • MID mobile Internet device
  • augmented reality augmented reality, AR
  • VR virtual reality
  • robots wearable devices
  • Vehicle user equipment VUE
  • pedestrian terminal pedestrian terminal
  • PUE pedestrian terminal
  • smart home home equipment with wireless communication functions, such as refrigerators, TVs, washing machines or furniture, etc.
  • game consoles personal computers (personal computer, PC), teller machine or self-service machine and other terminal-side devices.
  • Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets) bracelets, smart anklets, etc.), smart wristbands, smart clothing, etc.
  • the network side equipment 12 may include access network equipment or core network equipment, where the access network equipment may also be called wireless access network equipment, radio access network (Radio Access Network, RAN), radio access network function or wireless access network unit.
  • Access network equipment can include base stations, Wireless Local Area Network (WLAN) access points or WiFi nodes, etc.
  • WLAN Wireless Local Area Network
  • the base station can be called Node B, Evolved Node B (eNB), access point, base transceiver station ( Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), home B-node, home evolved B-node, sending and receiving point ( Transmitting Receiving Point (TRP) or some other suitable term in the field, as long as the same technical effect is achieved, the base station is not limited to specific technical terms. It should be noted that in the embodiment of this application, only the NR system is used The base station is introduced as an example, and the specific type of base station is not limited.
  • frequency division duplex Frequency Division Duplex
  • TDD time division duplex
  • This flexible duplex method can be called wireless Overlapping sub-band full duplex (non-overlapping sub-band full duplex, SBFD) mode.
  • SBFD non-overlapping sub-band full duplex
  • This SBFD is: full duplex on the network side, that is, at the same time, uplink transmission and downlink transmission can be performed simultaneously at different frequency domain positions.
  • a certain guard band (Guard Band) is reserved between corresponding duplex sub-bands); terminal side half-duplex is consistent with time division duplex TDD.
  • TDD time division duplex
  • only uplink transmission or downlink transmission can be performed, not both at the same time. conduct. It can be understood that in this duplex mode, the uplink transmission and downlink transmission on the network side at the same time can only be for different terminals.
  • Figure 2 gives a schematic diagram of the above-mentioned flexible duplex mode.
  • the network side equipment semi-statically divides the frequency domain of a single carrier into three duplex sub-bands within a part of the downlink symbols, where both sides of the carrier are Downlink duplex sub-band, with uplink duplex sub-band in the middle to reduce interference to adjacent carriers.
  • UE1 and UE2 perform uplink transmission and downlink reception respectively.
  • the TDD method is generally used.
  • the TDD uplink and downlink common configuration TDD-UL-DL-ConfigCommon can be configured in the cell public parameters to indicate the TDD frame structure information, including the TDD frame period and the number of complete downlink/uplink time slots (Slots) included in a single frame period. , the number of additional downstream/upstream symbols (Symbols) included in addition to the complete downstream/upstream Slot, etc.
  • RRC Radio Resource Control
  • the modification here is only limited to further indicating the flexible symbol (Flexible symbol) in the Slot as a downlink symbol (DL symbol) or an uplink symbol (UL symbol).
  • the DL/UL symbol in the Slot time slot cannot be modified to other directions.
  • Flexible symbol is a symbol whose transmission direction is not specified. It can be determined later whether it is used for downlink transmission or uplink transmission as needed.
  • TDD-UL-DL-ConfigCommon and/or TDD-UL-DL-ConfigDedicated are optional configurations. Since these configuration information can only be semi-statically configured/modified based on RRC signaling, the single TDD frame period determined by these configuration information Each Symbol inside, combined with its configured transmission direction, is called a semi-static (Semi-static) DL/UL/flexible symbol in the following. In addition, symbols can be further abstracted into time domain units, which can correspond to time slots (Slots), symbols (Symbols), etc., then a single TDD frame period can contain multiple Semi-static DL/UL/ based on the above configuration information. flexible time domain unit.
  • each NR cell Each Slot/Symbol in the wireless frame can be understood as a Semi-static flexible slot/symbol, or abstracted as a Semi-static flexible time domain unit.
  • the Semi-static flexible time domain unit refers to a Semi-static flexible time domain unit that allows flexible duplex operation. For whether there are uplink resource occupancy restrictions corresponding to the uplink sub-band (UL sub-band) in the Semi-static flexible time domain unit (that is, the uplink resources must be limited to the frequency domain range corresponding to the UL sub-band), you can use any of the following Way:
  • Frequency domain limitation method 1 There is a limitation. In the Semi-static flexible time domain unit, only the frequency domain range corresponding to the UL sub-band is used as available uplink resources.
  • Frequency domain restriction method 2 There is no restriction.
  • the frequency domain range corresponding to the uplink bandwidth part (Bandwidth Part, BWP) (that is, not limited to the frequency domain range corresponding to the UL sub-band) is Can be used as available uplink resources.
  • BWP Bandwidth Part
  • the Synchronization Signal and PBCH block (SSB) time domain unit cannot be configured as a Semi-static UL time domain unit, nor can it be indicated by the Slot Format Indicator (SFI) as a Dynamic UL time domain unit. unit.
  • the time domain unit here can be understood as a symbol, and the SSB time domain unit is, for example, SSB symbol.
  • the terminal does not send uplink transmissions that overlap with the SSB time domain unit.
  • the uplink transmissions may include at least one of the following: Physical Uplink Shared Channel (PUSCH) transmission, Physical Uplink Control Channel (Physical Uplink Control Channel) , PUCCH) transmission, Physical Random Access Channel (Physical Random Access Channel, PRACH) transmission, Sounding Reference Signal (SRS) transmission, etc.
  • PUSCH Physical Uplink Shared Channel
  • PUCCH Physical Uplink Control Channel
  • PRACH Physical Random Access Channel
  • SRS Sounding Reference Signal
  • SSB collision restriction method 1 Maintain the above uplink transmission restrictions, that is, flexible duplex operation is not allowed within the SSB time domain unit, and the terminal does not send PUSCH/PUCCH/PRACH/SRS transmissions that overlap with the SSB time domain unit.
  • the last time domain unit of an SSB time domain unit set is the same as the first time domain unit of PUSCH/PUCCH/PRACH/SRS transmission.
  • the interval between domain units is less than the downlink to uplink conversion time (referred to as downlink to uplink conversion time), or the last time domain unit of PUSCH/PUCCH/PRACH/SRS transmission to the first time domain unit of an SSB time domain unit set If the interval is less than the uplink to downlink conversion time (referred to as the uplink to downlink conversion time), the terminal does not send this PUSCH/PUCCH/PRACH/SRS transmission.
  • the SSB time domain unit set may be composed of one or more SSB time domain units that are continuous in time domain.
  • SSB collision restriction method 2 Lift or partially lift the above uplink transmission restrictions, that is, flexible duplex operation is allowed in the SSB time domain unit, and when flexible duplex operation is configured in the SSB time domain unit, the terminal is allowed to operate when predefined conditions are met.
  • the above predefined conditions can include at least one of the following:
  • the frequency domain resources occupied by PUSCH/PUCCH/PRACH/SRS transmission are limited to the frequency domain range of the UL sub-band configured in the SSB time domain unit;
  • PUSCH/PUCCH/PRACH/SRS transmission is scheduled according to dynamic signaling
  • the priority of PUSCH/PUCCH transmission is high priority, such as configured or indicated as 1.
  • SSB when SSB is transmitted within a Semi-static UL time domain unit, or a dynamic (Dynamic) UL time domain unit indicated by Downlink Control Information (DCI) (such as DCI format 2_0), for SSB transmission
  • DCI Downlink Control Information
  • the time domain unit where it is located can also adopt the SSB collision limitation method 2 mentioned above.
  • Figure 3 is a flow chart of an information configuration method provided by an embodiment of the present application. The method is applied to a terminal. As shown in Figure 3, the method includes the following steps:
  • Step 31 The terminal receives the first configuration information from the network side device.
  • the first configuration information up to M sets of configuration information are configured for a single PUCCH resource (such as PUCCH Resource), and each set of configuration information corresponds to a time domain unit that meets specific requirements; or, the first configuration information includes up to N items of PUCCH configuration (such as PUCCH Config), each PUCCH configuration corresponds to a time domain unit that meets specific requirements; the M is an integer greater than 1, and the N is an integer greater than 1.
  • the above configuration information can be understood as including at least one or more items of relevant configuration information in the parameter structure PUCCH-Resource, including time domain resource information (such as starting symbol index, number of occupied symbols, etc.), Frequency domain resource information (such as the starting Physical Resource Block (PRB) index, the number of occupied PRBs, whether intra-slot frequency hopping is enabled, and the starting PRB corresponding to the second hop when intra-slot frequency hopping is enabled) Index, etc.) and code domain resource information (such as Orthogonal Cover Code (OCC) related configuration, etc.).
  • the above configuration information may also include configuration information such as code rate and power.
  • the above PUCCH configuration may at least include parameter configuration for each PUCCH Resource, parameter configuration for each PUCCH resource set (such as PUCCH Resource Set), and various PUCCH formats (Format). Parameter configuration, power control parameter configuration for PUCCH transmission, spatial relationship list (Spatial Relation Info List) configuration, etc.
  • parameters matching their relevant characteristics can be configured for different uplink resources, such as time-frequency location, code rate, power, etc., so that based on different The characteristics of uplink resources make full use of uplink resources to ensure the performance of PUCCH transmission.
  • the above-mentioned time domain units that meet specific requirements may include a first type of time domain unit and/or a second type of time domain unit.
  • the first type of time domain unit is when there are available uplink resources within the uplink BWP range.
  • Domain unit, the second type of time domain unit is a time domain unit with available uplink resources only within the uplink subband range.
  • the embodiments of the present application are described using examples involving two types of time domain units (i.e., the first type of time domain unit and the second type of time domain unit), but these descriptions can be further extended to more than two types of time domain units as needed.
  • domain unit At this time, it can be adjusted accordingly: Class A time domain unit.
  • the following other categories of time domain units are all other categories of time domain units except the predefined category time domain units/specified category time domain units, or, except for the predefined category time domain units/specified category Any category of time domain units other than time domain units.
  • the above-mentioned first type of time domain unit may include at least one of the following: 1) Semi-static uplink time domain unit; 2) First Semi-static flexible time domain unit, wherein the first Semi-static flexible time domain unit In the time domain unit, the frequency domain range corresponding to the uplink BWP can be used as available uplink resources, that is, the above frequency domain restriction method 2 is adopted; the first Semi-static flexible time domain unit is a Semi-static flexible time domain that allows flexible duplex operation unit.
  • the first Semi-static flexible time domain unit here does not include the SSB time domain unit.
  • the above-mentioned second type of time domain unit may include at least one of the following:
  • the Semi-static downlink time domain unit here can be understood as a Semi-static DL time domain unit configured with UL sub-band;
  • the Semi-static DL time domain unit here does not include the SSB time domain unit.
  • the second Semi-static flexible time domain unit in which, in the second Semi-static flexible time domain unit, only the frequency domain range corresponding to the uplink subband can be used as available uplink resources, that is, the above frequency domain restriction method 1 is adopted;
  • the second Semi-static flexible time domain unit is a Semi-static flexible time domain unit that allows flexible duplex operation.
  • the second Semi-static flexible time domain unit here does not include the SSB time domain unit.
  • each BWP corresponds to a single PUCCH configuration
  • each physical layer priority (PHY priority) of each BWP corresponds to a single PUCCH configuration.
  • PHY priority physical layer priority
  • a single PUCCH Resource can configure up to M sets of configuration information.
  • Each set of configurations Information corresponds to or applies to time domain units that meet specific requirements.
  • the network side device can configure a single set of configuration information or two sets of configuration information for a single PUCCH resource. If two sets of configuration information are configured for a single PUCCH resource, and the two sets of configuration information include a first set of configuration information and a second set of configuration information, then: the first set of configuration information corresponds to the first type of time domain unit, and the second set of configuration information Corresponds to the second type of time domain unit; or, the first set of configuration information corresponds to the second type of time domain unit, and the second set of configuration information corresponds to the first type of time domain unit.
  • the single set of configuration information corresponds to the first type of time domain unit or the second type of time domain unit.
  • the number of sets of configuration information configured for different PUCCH resources may be the same or different.
  • these PUCCH resources may be configured with only the first set of configuration information or the second set of configuration information, or at least one of the PUCCH resources may only be configured with the first set of configuration information or the second set of configuration information.
  • the first set of configuration information is configured, and other PUCCH resources are only configured with the second set of configuration information.
  • the following situations can be distinguished and processed accordingly.
  • Case 1 Only a single set of configuration information is configured for a single PUCCH resource, such as only the first set of configuration information or the second set of configuration information.
  • a single set of configuration information for this configuration can default to correspond to or be applied to a predefined category of time domain units.
  • the predefined category time domain unit can be the first category time domain unit; when only the second set of configuration information is configured, the predefined category time domain unit can be the second category time domain unit. unit.
  • the predefined type of time domain unit is always the first type of time domain unit or the second type of time domain unit, which may be specified by the protocol or configured by high-level signaling, etc.
  • predefined category time domain unit is the first category time domain unit
  • other category time domain units are the second category time domain unit
  • the predefined category time domain unit is the second category time domain unit
  • other category time domain units is the first type of time domain unit.
  • the terminal can determine unavailable resources or unavailable transmission in any of the following ways:
  • the terminal may perform one of the following:
  • the terminal does not initiate corresponding PUCCH transmission, and other types of time domain units are treated as illegal time domain units;
  • time domain units of other categories are regarded as legal when meeting the first predefined condition time domain unit, otherwise it is an illegal time domain unit.
  • the terminal may perform one of the following:
  • the predefined delay (Deferral) mechanism can be used to determine the next available repeated transmission, that is, determine the next available PUCCH Repetition time domain position;
  • the predefined Deferral mechanism can be used to determine the next available repeated transmission, that is, to determine the next available PUCCH Repetition time domain position.
  • the above-mentioned second configuration information is a single set of configuration information configured for the first PUCCH resource.
  • the type of the time domain unit corresponding to the second configuration information is different from the types of the other types of time domain units.
  • the time domain unit corresponding to the second configuration information is a first type of time domain unit, and the other types of time domain units are a second type of time domain unit; or, the time domain unit corresponding to the second configuration information is The second type of time domain unit, the other types of time domain units are the first type of time domain unit.
  • the above predefined Deferral mechanism is that when a certain PUCCH resource is configured with repeated transmission, assuming that the expected number of repeated transmissions is B, then for the b-th repeated transmission of this PUCCH resource (b is a positive integer between 1 and B, Starting from the value 1 and gradually increasing based on the step size 1 during the transmission process corresponding to this PUCCH resource), if in a certain PUCCH time slot, the repeated transmission determined based on the configuration information of the PUCCH resource application is consistent with at least one Semi-static DL time domain unit (that is, a time domain unit configured as a downlink by higher layer signaling TDD-UL-DL-ConfigCommon and/or TDD-UL-DL-ConfigDedicated; regardless of whether there is an uplink subband configured in the time domain unit) and /or there is overlap in SSB time domain units (that is, at least one of the time domain units occupied by this repeated transmission is a Semi-static DL time domain unit and/or SSB time domain unit), then this repeated transmission
  • the existence of overlap in (1) above may be understood to mean that at least one of the time domain units occupied by the first PUCCH resource is a time domain unit of another type.
  • the collision processing between the first PUCCH resource and time domain units other than the first/second type time domain units in this application can adopt a predefined method.
  • the PUCCH transmission corresponding to the first PUCCH resource is associated with at least one Semi -static DL time domain unit (that is, a time domain unit configured as a downlink by higher layer signaling TDD-UL-DL-ConfigCommon and/or TDD-UL-DL-ConfigDedicated; regardless of whether there is an uplink subband configured in the time domain unit ) and/or SSB time domain units overlap (that is, at least one of the time domain units occupied by this PUCCH transmission is a Semi-static DL time domain unit and/or an SSB time domain unit), then it is determined that the first PUCCH resource is illegal or unavailable use.
  • the first PUCCH resource is illegal or unavailable use.
  • time domain units other than the above may include: Semi-static DL time domain units that are not configured with UL sub-band, and/or, Semi-static flexible time domain units, etc. that do not allow flexible duplex operation.
  • the terminal when using the third configuration information to determine the PUCCH transmission corresponding to the first PUCCH resource, the terminal does not It is expected that the first PUCCH resource (this corresponds to repeated transmission without configuration) or the second repeated transmission of the first PUCCH resource (this corresponds to repeated transmission) overlaps with other types of time domain units; or, in the first PUCCH resource (this corresponds to repeated transmission) When repeated transmission is not configured) or the second repeated transmission of the first PUCCH resource (this corresponding repeated transmission is configured) overlaps with other types of time domain units, the terminal does not expect to be unsatisfied in at least one overlapping time domain unit of other types.
  • the third configuration information is a single set of configuration information configured for the first PUCCH resource, and the second repeated transmission is any repeated transmission of the first PUCCH resource.
  • the type of the time domain unit corresponding to the third configuration information is different from the types of the other types of time domain units.
  • the time domain unit corresponding to the third configuration information is the first type of time domain unit, and the other types
  • the time domain unit of the category is the time domain unit of the second category
  • the time domain unit corresponding to the third configuration information is the time domain unit of the second category, and the time domain units of the other categories are the time domain unit of the first category.
  • the above-mentioned first predefined condition may include at least one of the following:
  • time domain units are the first type of time domain units;
  • the first PUCCH resource (this corresponds to no repeated transmission configured) or the repeated transmission of the first PUCCH resource (this corresponds to repeated transmission configured) is in the overlapping time domain of other types.
  • Any resource unit (Resource Element, RE) occupied in the unit is located in the frequency domain range corresponding to the uplink subband.
  • Case 2 Configure two sets of configuration information for a single PUCCH resource, such as configuring the first set of configuration information and the second set of configuration information.
  • the terminal can determine the application configuration information from the two configured sets of configuration information based on at least one of the following:
  • the configuration information of the application is determined based on the category of the time domain unit in which a single PUCCH resource (this corresponds to no repeated transmission is configured) or a single PUCCH resource is repeatedly transmitted (this corresponds to repeated transmission is configured).
  • the time domain unit where a certain PUCCH resource (this corresponds to no repeated transmission is configured) or the repeated transmission of the PUCCH resource (this corresponds to configured repeated transmission) is located is a first-type time domain unit
  • the first set of configurations for this PUCCH resource shall be applied.
  • set of configuration information may be specified by the protocol or configured by high-layer signaling, etc.
  • each repeated transmission of the PUCCH resource can satisfy at least one of the following to ensure that when polar coding (Polar coding) is used Repeated merge operations when:
  • the number of REs used to carry uplink control information (UCI) is the same, that is, the REs used to carry demodulation reference signals (Demodulation Reference Signals, DM-RS) are not considered;
  • the number of occupied time domain units is the same.
  • each of the above repeated transmissions is an actual repeated transmission.
  • Each of the above repeated transmissions corresponds to the corresponding PUCCH resource.
  • the terminal can determine the application configuration from the configured two sets of configuration information based on at least one of the following information:
  • the category of the nominal time domain unit of the PUCCH resource is the category of the nominal time domain unit of the PUCCH resource
  • the category of the time domain unit in which the first actually initiated repeated transmission of the PUCCH resource is located.
  • the PUCCH format (Format) corresponding to this PUCCH resource is configured with corresponding parameters, such as the number of time slots nrofSlots, and the value is greater than 1, and/or, A dynamic repetition factor is configured for this PUCCH resource, and the value is greater than 1.
  • the nominal time domain unit of a PUCCH resource can be understood as: based on high-level signaling configuration or DCI indication, the time domain unit where the PUCCH transmission corresponding to this PUCCH resource is located (repetition transmission is not configured), or the time domain unit of the PUCCH transmission corresponding to this PUCCH resource. Starting time domain unit (with Repetition transmission configured).
  • the time domain unit here can be a time slot (slot) or a sub-time slot (sub-slot), etc.
  • PUCCH repeated transmission may be dropped due to UCI multiplexing processing or priority processing (multiplexing/prioritization) rules, or may be delayed due to collision with illegal time domain units ( postpone), so the configuration information of the application can be determined based on the category of the time domain unit in which the first repeated transmission of the PUCCH resource is actually initiated.
  • the determined configuration information is applied to subsequent repeated transmissions (Repetition) of this PUCCH transmission.
  • the first high-level signaling that is, the configuration information configured by the high-level signaling.
  • SPS Semi-Persistent Scheduling
  • HARQ-ACK Hybrid Automatic Repeat reQuest Acknowledgment
  • the configuration information of the application can be configured uniformly for the terminal or each PUCCH cell or each PUCCH BWP or each PUCCH Config, or additional parameters in the high-level parameter SchedulingRequestResourceConfig can be used to indicate the SchedulingRequestResourceConfig.
  • the configuration information of the PUCCH Resource application corresponding to the resource parameter.
  • the configuration information of the application can be configured uniformly for the terminal or each PUCCH cell, or in the reportConfigType in the high-level parameter CSI-ReportConfig Additional parameters are used in the pucch-CSI-ResourceList in periodic to uniformly indicate the configuration information of the PUCCH Resource application corresponding to each PUCCH BWP configured with PUCCH Resource on the PUCCH cell, or in the periodic in reportConfigType in the high-level parameter CSI-ReportConfig.
  • CSI channel state information
  • Each list record of the pucch-CSI-ResourceList (corresponding to a single PUCCH BWP of the PUCCH cell, indicated by the field uplinkBandwidthPartId) uses additional parameters to indicate the configuration information of the PUCCH Resource application corresponding to the pucch-Resource field of this list record.
  • the configuration information of the application can be configured uniformly for the terminal or each PUCCH cell, or the pucch-CSI- in the reportConfigType in the high-level parameter CSI-ReportConfig Additional parameters are used in ResourceList to uniformly indicate the configuration information of the PUCCH Resource application corresponding to each PUCCH BWP configured with PUCCH Resource on the PUCCH cell, or the pucch-CSI-ResourceList in semiPersistentOnPUCCH in the reportConfigType in the high-level parameter CSI-ReportConfig.
  • Each list record (corresponding to a single PUCCH BWP of the PUCCH cell, indicated by the field uplinkBandwidthPartId) uses additional parameters to indicate the configuration information of the PUCCH Resource application corresponding to the pucch-Resource field of this list record.
  • the first DCI that is, the configuration information of the application is determined based on the DCI.
  • the configuration information indicating the application may be determined implicitly or displayed, and any of the following may be used:
  • the configuration information of the application corresponds to the category of the time domain unit in which the PUCCH transmission indicated by the first DCI is located.
  • This can be understood as a special case of determining application configuration information based on the nominal time domain unit (indicated by DCI) of PUCCH transmission. For example, if the first DCI indicates the location or starting time domain unit of the PUCCH transmission that carries HARQ-ACK feedback, and the PUCCH resource corresponding to this PUCCH transmission, then for this PUCCH resource, the application is in the same time domain as the location or starting time domain of the PUCCH transmission. Configuration information corresponding to the unit category.
  • the indication field in the first DCI may explicitly indicate which set of configuration information of the PUCCH resource is specifically applied.
  • the configuration information of the application can satisfy any of the following:
  • the configuration information of the application is indicated by an independent indication field in the first DCI.
  • the second indication field in the first DCI jointly indicates the PUCCH resource indication PRI and the configuration information of the application; wherein the number of bits occupied by the joint indication field can be expanded as needed relative to the number of bits occupied by the PRI indication field;
  • the third indication field in the first DCI jointly indicates K1 and the configuration information of the application; the number of bits occupied by the joint indication field can be expanded as needed relative to the number of bits occupied by the K1 indication field.
  • the terminal always uses configured/indicated configuration information for PUCCH resources.
  • the single set of configuration information configured/indicated corresponds to/applies to the time domain unit of the specified category.
  • the time domain unit of the specified category is the first type time domain unit.
  • the configured/indicated application When configuring the second set of information, specify the type of time domain unit as the second type of time domain unit.
  • the mapping relationship between time domain unit categories and configuration information may be specified by a protocol or configured by high-level signaling.
  • time domain units of other categories are the second category time domain unit; when the time domain unit of the specified category is the second category time domain unit, the time domain units of other categories are The first type of time domain unit.
  • the terminal can determine unavailable resources/unavailable transmission in any of the following ways:
  • the terminal may perform one of the following:
  • time domain units of other categories are regarded as legal when the first predefined condition is met time domain unit, otherwise it is an illegal time domain unit.
  • the terminal may perform one of the following:
  • the predefined Deferral mechanism can be used, as mentioned above, to determine the next available repetition Transmission, that is, determining the next available PUCCH Repetition time domain position.
  • the above-mentioned second configuration information is one set of configuration information determined from two sets of configuration information configured for the first PUCCH resource.
  • any one of the above 1), 2) and 3) can be used to determine the set of configuration information.
  • the above-mentioned 1) is used here, which can be understood that for PUCCH resources configured with repeated transmission, the terminal determines the application configuration information from the two configured sets of configuration information.
  • the type of the time domain unit corresponding to the second configuration information is different from the types of the other types of time domain units.
  • the time domain unit corresponding to the second configuration information is a first type of time domain unit, and the other types of time domain units are a second type of time domain unit; or, the time domain unit corresponding to the second configuration information is The second type of time domain unit, the other types of time domain units are the first type of time domain unit.
  • time domain units other than the above may include: Semi-static DL time domain units that are not configured to have UL sub-band, and/or Semi-static flexible time domain units that do not allow flexible duplex operation, etc.
  • a postpone operation needs to be performed, that is, starting from the next time slot, it is continued to determine whether the candidate Candidate PUCCH repetition in this slot conflicts with the illegal time domain unit.
  • this Candidate PUCCH repetition can actually be transmitted.
  • the postpone operation may not be performed based on the predefined Deferral mechanism, but directly dropped.
  • the traversed Candidate PUCCH repetition reaches the predefined threshold, this PUCCH transmission ends.
  • whether to use the first predefined condition to determine unavailable resources/transmissions can be stipulated by the protocol, or can be targeted at the terminal or each PUCCH cell or each PUCCH BWP. Or configure all PUCCH Config uniformly, or independently configure each SPS-Config/SchedulingRequestResourceConfig/CSI-ReportConfig and other functional configuration items.
  • the terminal when using the third configuration information to determine the PUCCH transmission corresponding to the first PUCCH resource, the terminal does not expect any repetition of the first PUCCH resource (this corresponds to unconfigured repeated transmission) or the first PUCCH resource.
  • the transmission (this corresponds to repeated transmission configured) overlaps with other types of time domain units; or, in the first PUCCH resource (this corresponds to repeated transmission not configured) or the third repeated transmission of the first PUCCH resource (this corresponds to When there is overlap with time domain units of other categories (corresponding to which repeated transmission is configured), the terminal does not expect that the first predefined condition is not satisfied in at least one overlapping time domain unit of other categories.
  • the third configuration information is a set of configuration information determined from two sets of configuration information configured for the first PUCCH resource, and the third configuration information is determined based on configuration or indication, for example, the above 2) can be used Or determine the set of configuration information in 3).
  • the third repeated transmission is any repeated transmission of the first PUCCH resource.
  • the type of the time domain unit corresponding to the third configuration information is different from the types of the other types of time domain units.
  • the time domain unit corresponding to the third configuration information is a first type of time domain unit, and the other types of time domain units are a second type time domain unit; or, the time domain unit corresponding to the third configuration information is The second type of time domain unit, the other types of time domain units are the first type of time domain unit.
  • the above-mentioned first predefined condition may include at least one of the following:
  • time domain units are the first type of time domain units;
  • the first PUCCH resource (this corresponds to no repeated transmission configured) or the repeated transmission of the first PUCCH resource (this corresponds to repeated transmission configured) is in the overlapping other categories.
  • Any resource unit RE occupied in the domain unit is located in the frequency domain range corresponding to the uplink subband.
  • the first configuration information includes at most N PUCCH configurations.
  • each BWP corresponds to up to N PUCCH configurations, or each physical layer priority (PHY priority) of each BWP corresponds to up to N PUCCH configurations, and each PUCCH configuration corresponds to/applies to a time domain unit that meets specific requirements. .
  • PHY priority physical layer priority
  • the first configuration information includes two PUCCH configurations, and the two PUCCH configurations include a first PUCCH configuration and a second PUCCH configuration
  • the first PUCCH configuration corresponds to the first type of time domain unit
  • the The two PUCCH configurations correspond to the second type of time domain unit
  • the first PUCCH configuration corresponds to the second type of time domain unit
  • the second PUCCH configuration corresponds to the first type of time domain unit.
  • the single PUCCH Config of this configuration only applies to the first type of time domain unit, or at the same time Applies to the first type of time domain unit and the second type of time domain unit.
  • the terminal may determine the applied PUCCH configuration from the two configured PUCCH configurations according to at least one of the following:
  • the nominal time domain unit of PUCCH transmission here can be understood as PUCCH transmission based on high-layer signaling configuration or DCI indication (this corresponds to no repeated transmission configured) or the time domain unit where the PUCCH starts transmission (this corresponds to configured repeated transmission) The time domain unit in which it is located.
  • the bearer DG HARQ-ACK can be determined based on the K1 indicated in the downlink scheduling DCI and the time domain unit where the physical downlink shared channel (Physical Downlink Shared Channel, PDSCH) transmission is located.
  • the nominal time domain unit for PUCCH transmission of ACK is located.
  • the nominal time domain unit for PUCCH transmission carrying SPS HARQ-ACK can be determined based on K1 indicated in the SPS activation DCI, and the time domain unit for SPS PDSCH transmission.
  • the nominal time domain unit carrying SR PUCCH transmission can be determined based on the periodicityAndOffset in the high-level parameter SchedulingRequestResourceConfig.
  • the nominal time domain unit for PUCCH transmission carrying CSI can be determined based on the reportSlotConfig parameter in periodic in reportConfigType in CSI-ReportConfig, or, for Semi-persistent CSI on PUCCH , the nominal time domain unit for PUCCH transmission carrying CSI can be determined based on the reportSlotConfig parameter in semiPersistentOnPUCCH in reportConfigType in CSI-ReportConfig.
  • the first PUCCH Config configured for the current BWP is applied, or the first item configured for the PHY priority corresponding to the current BWP and this PUCCH transmission is applied.
  • Item PUCCH Config when the nominal time domain unit for PUCCH transmission belongs to the second type of time domain unit, the second PUCCH Config configured for the current BWP is applied, or the second item PUCCH Config configured for the current BWP and the PHY priority corresponding to this PUCCH transmission is applied.
  • Binary PUCCH Config can be specified by the protocol or configured by high-level signaling.
  • the current BWP here can be understood as the BWP where the PUCCH transmission is located or corresponding.
  • the PHY priority corresponding to this PUCCH transmission can be configured by high-level signaling or indicated by DCI.
  • the nominal time domain unit transmitted by the PUCCH corresponding to different transmission periods may belong to the first type of time domain unit or the second type of time domain unit, so it is necessary to Use the PUCCH Resource configured in the first PUCCH Config and the second PUCCH Config respectively.
  • the applied PUCCH configuration is determined based on the category of the nominal time domain unit for PUCCH transmission, for the configuration of the identifier of the PUCCH resource used by the semi-static UCI in the first PUCCH configuration and the second PUCCH configuration, it can be satisfied Any of the following:
  • the second identifier of the PUCCH resource used is determined based on the second identifier; that is, only the ID of the PUCCH resource used in a certain PUCCH configuration is configured, and the ID of the PUCCH resource used in another PUCCH configuration is determined based on the second identifier.
  • the ID of the PUCCH resource used in the configuration is derived based on the aforementioned configuration ID.
  • the PUCCH Resource ID configured in the existing parameter configuration structure applies to both PUCCH Config, that is, this semi-static UCI is used in the first PUCCH Config and the second PUCCH Config.
  • the IDs of the PUCCH Resource used in the PUCCH Config items are consistent.
  • Another optional method is to introduce an identification offset (ID Offset).
  • ID Offset an identification offset
  • the PUCCH Resource ID configured in the existing parameter configuration structure is applicable to the first or second PUCCH Config (that is, indicating that the PUCCH Resource corresponding to this configuration ID in this PUCCH Config is used for the transmission of this semi-static UCI)
  • ID Offset the value is a non-negative integer such as 0, 1, etc.
  • the ID of the corresponding PUCCH Resource in the first PUCCH Config and the second PUCCH Config can be indicated in the parameter SPS-Config respectively.
  • n1PUCCH-AN in the existing parameter SPS-Config corresponds to the ID of the PUCCH Resource corresponding to the first PUCCH Config
  • an additional parameter is introduced in SPS-Config to indicate the ID of the PUCCH Resource corresponding to the second PUCCH Config.
  • sps-PUCCH-AN-List-r16 in the parameter PUCCH-Config is configured in the first PUCCH Config and the second PUCCH Config respectively, and no additional enhancement is required.
  • the parameter SchedulingRequestResourceConfig can be configured separately in the first PUCCH Config and the second PUCCH Config. Just set the parameter schedulingRequestID of these two SchedulingRequestResourceConfig to the same value, that is, it is associated with the same SR Config ID.
  • the PUCCH Resource list corresponding to the first PUCCH Config and the second PUCCH Config can be configured in the periodic in reportConfigType in the parameter CSI-ReportConfig.
  • the existing parameter CSI -The pucch-CSI-ResourceList in the periodic in reportConfigType in ReportConfig corresponds to the ID of the PUCCH Resource configured in the first PUCCH Config of each PUCCH BWP.
  • Additional parameters are introduced in the periodic in reportConfigType in CSI-ReportConfig to configure each The ID of the PUCCH Resource configured in the PUCCH Config of the second item of the PUCCH BWP; or, each list record of the pucch-CSI-ResourceList in the periodic in the reportConfigType in the parameter CSI-ReportConfig (corresponding to a single PUCCH BWP of the PUCCH cell,
  • the ID of the PUCCH Resource corresponding to the first PUCCH Config and the second PUCCH Config is respectively configured in the field uplinkBandwidthPartId).
  • the list record field pucch-Resource corresponds to the first PUCCH Config of the PUCCH BWP corresponding to this list record.
  • the ID of the PUCCH Resource configured in the list record introduce additional parameters in the list record to configure the ID of the PUCCH Resource configured in the second PUCCH Config of the PUCCH BWP corresponding to this list record.
  • the first item can be configured separately in semiPersistentOnPUCCH in reportConfigType in parameter CSI-ReportConfig PUCCH Config and the PUCCH Resource list corresponding to the second PUCCH Config.
  • the pucch-CSI-ResourceList in semiPersistentOnPUCCH in the reportConfigType in the existing parameter CSI-ReportConfig corresponds to the PUCCH Resource configured in the first PUCCH Config of each PUCCH BWP.
  • the list record The field pucch-Resource corresponds to the ID of the PUCCH Resource configured in the PUCCH Config of the first item of the PUCCH BWP corresponding to this list record. Additional parameters are introduced in the list record to configure the second item PUCCH of the PUCCH BWP corresponding to this list record.
  • the second high-level signaling that is, the PUCCH configuration applied by the high-level signaling configuration.
  • SPS HARQ-ACK For example, for SPS HARQ-ACK, you can configure it uniformly for the terminal, or use additional parameters in SPS-Config to indicate the PUCCH Config where the PUCCH Resource corresponding to the n1PUCCH-AN parameter in SPS-Config is located, or indicate the PUCCH Config corresponding to Which PUCCH Config does SPS HARQ-ACK use?
  • the sps-PUCCH-AN-List-r16 parameter in PUCCH-Config is configured in the first PUCCH Config and the second PUCCH Config respectively.
  • the parameter SchedulingRequestResourceConfig can be configured separately in the first PUCCH Config and the second PUCCH Config.
  • the schedulingRequestID in the parameter SchedulingRequestResourceConfig a certain SR Config ID can only be associated with a certain PUCCH BWP of a certain PUCCH cell.
  • the SchedulingRequestResourceConfig configured in the first PUCCH Config or the second PUCCH Config.
  • CSI PUCCH transmission such as Periodic CSI on PUCCH
  • the parameters uniformly indicate the PUCCH Config where the PUCCH BWP corresponding to the PUCCH Resource is configured on the PUCCH cell, or each list record of the pucch-CSI-ResourceList in the periodic in the reportConfigType in the CSI-ReportConfig (corresponding to A single PUCCH BWP of a PUCCH cell (indicated by the field uplinkBandwidthPartId) uses additional parameters to each indicate the PUCCH Config where the PUCCH Resource corresponding to the pucch-Resource field in this list record is located.
  • CSI PUCCH transmission for Semi-persistent CSI on PUCCH, it can be targeted at the terminal or each The PUCCH cell uniformly configures the applied PUCCH Config, or uses additional parameters in the pucch-CSI-ResourceList in semiPersistentOnPUCCH in the reportConfigType in the high-level parameter CSI-ReportConfig to uniformly indicate the PUCCH BWP corresponding to each PUCCH Resource configured on the PUCCH cell.
  • the PUCCH Config where the PUCCH Resource is located or each list record of the pucch-CSI-ResourceList in the semiPersistentOnPUCCH in the reportConfigType in the high-level parameter CSI-ReportConfig (corresponding to a single PUCCH BWP of the PUCCH cell, indicated by the field uplinkBandwidthPartId).
  • the parameters each indicate the PUCCH Config where the PUCCH Resource corresponding to the pucch-Resource field in this list record is located.
  • the second DCI that is, the PUCCH configuration to be applied is determined based on the DCI.
  • DCI can be activated based on downlink dynamic scheduling DCI and/or SPS, and the PUCCH Config where the used PUCCH Resource is located can be determined.
  • the applied PUCCH configuration when determining the applied PUCCH configuration based on the second DCI, the applied PUCCH configuration may be determined implicitly or explicitly indicated, and any of the following may be used:
  • the applied PUCCH configuration corresponds to the category of the time domain unit in which the PUCCH transmission indicated by the second DCI is located. For example, if the time domain unit where the PUCCH transmission carrying HARQ-ACK feedback is located is indicated in the second DCI (this corresponds to no repeated transmission configured) or the starting time domain unit (this corresponds to repeated transmission configured), and the PUCCH corresponding to this PUCCH transmission Resource, for this PUCCH Resource, apply the PUCCH Config corresponding to the category of the time domain unit where the PUCCH transmission is located (this corresponds to no repeated transmission configured) or the starting time domain unit (this corresponds to repeated transmission configured).
  • the PUCCH Config where the used PUCCH Resource is located can be explicitly indicated by the indication field in the second DCI.
  • the PUCCH configuration of the application can satisfy any of the following:
  • the PUCCH Config is indicated by an independent indication field in the second DCI.
  • whether the fourth indication field in the second DCI exists can be configured by high-level signaling.
  • the default PUCCH Config (such as the first item PUCCH Config) is used.
  • the fifth indication field in the second DCI jointly indicates the PRI and the applied PUCCH configuration; wherein the number of bits occupied by the joint indication field can be expanded as needed relative to the number of bits occupied by the PRI indication field;
  • the sixth indication field in the second DCI jointly indicates K1 and the applied PUCCH configuration; the number of bits occupied by the joint indication field can be expanded as needed relative to the number of bits occupied by the PRI indication field.
  • the terminal always considers the PUCCH Resource used to come from the configured/indicated PUCCH Config.
  • the configured/indicated PUCCH Config corresponds to/is applied to the time domain unit of the specified category.
  • the time domain unit of the specified category is the first type time domain unit.
  • the time domain unit is of the first type.
  • the time domain unit category is the same as
  • the mapping relationship between PUCCH Config can be specified by the protocol or configured by high-level signaling.
  • time domain units of other categories are the second category time domain unit; when the time domain unit of the specified category is the second category time domain unit, the time domain units of other categories are The first type of time domain unit.
  • the terminal can determine unavailable PUCCH resources or PUCCH transmission in any of the following ways:
  • the terminal may perform one of the following:
  • the second PUCCH resource is determined to be illegal/unavailable; at this time, time domain units of other categories are regarded as legal when meeting the second predefined condition time domain unit, otherwise it is an illegal time domain unit.
  • the terminal may perform one of the following:
  • the fourth repeated transmission is illegal/unavailable; at this time, other types of time domain units are regarded as illegal time domain units, and the predefined Deferral mechanism can be used.
  • the next available repeated transmission is determined, that is, the next available PUCCH is determined. Repetition time domain position;
  • the predefined Deferral mechanism can be used, as mentioned above, to determine the next available repeated transmission, that is, to determine the next available PUCCH Repetition time domain position.
  • the above-mentioned second PUCCH resource is a single PUCCH resource in the applied PUCCH configuration
  • the fourth configuration information is the configuration information corresponding to the second PUCCH resource in the applied PUCCH configuration.
  • the type of time domain unit corresponding to the applied PUCCH configuration is different from the types of time domain units of other types.
  • the time domain unit corresponding to the PUCCH configuration of the application is a first type of time domain unit
  • the other types of time domain units are a second type of time domain unit
  • the time domain unit corresponding to the PUCCH configuration of the application is The second type of time domain unit, the other types of time domain units are the first type of time domain unit.
  • time domain units other than the above may include: UL is not configured to exist Sub-band Semi-static DL time domain unit, and/or, Semi-static flexible time domain unit that does not allow flexible duplex operation, etc.
  • the terminal when using the fifth configuration information to determine the PUCCH transmission corresponding to the second PUCCH resource, the terminal does not expect the second PUCCH resource (this corresponds to no repeated transmission) or any repeated transmission of the second PUCCH resource (this corresponds to no repeated transmission). This corresponds to repeated transmission configured) and overlaps with other types of time domain units; or, in the second PUCCH resource (this corresponds to repeated transmission is not configured) or the fifth repeated transmission of the second PUCCH resource (this corresponds to configured). When there is overlap with other types of time domain units (for repeated transmission), the terminal does not expect that the second predefined condition is not satisfied in at least one overlapping time domain unit of other types; wherein the second PUCCH resource is an applied PUCCH A single PUCCH resource in the configuration.
  • the fifth configuration information is the configuration information corresponding to the second PUCCH resource in the PUCCH configuration of the application.
  • the PUCCH configuration of the application is determined based on the configuration or indication. For example, the above-mentioned Determine in 2) or 3).
  • the fifth repeated transmission is any repeated transmission of the second PUCCH resource.
  • the type of time domain unit corresponding to the applied PUCCH configuration is different from the types of time domain units of other types.
  • the time domain unit corresponding to the PUCCH configuration of the application is a first type of time domain unit, and the other types of time domain units are a second type of time domain unit; or, the time domain unit corresponding to the PUCCH configuration of the application is The second type of time domain unit, the other types of time domain units are the first type of time domain unit.
  • the above-mentioned second predefined condition may include at least one of the following:
  • time domain units are the first type of time domain units;
  • the second PUCCH resource (this corresponds to no repeated transmission configured) or the repeated transmission of the second PUCCH resource (this corresponding configured repeated transmission) is in the overlapping time domain of other categories.
  • Any resource unit RE occupied in the unit is located in the frequency domain range corresponding to the uplink subband.
  • the terminal when flexible duplex operation is not allowed in the time domain unit where the SSB transmission is located, the terminal does not send uplink transmissions that overlap with the time domain unit where the SSB transmission is located.
  • the terminal meets the third predefined condition Next, the uplink transmission that overlaps with the time domain unit where the SSB transmission is located is sent.
  • the above-mentioned third predefined condition may include at least one of the following:
  • the frequency domain resources occupied by uplink transmission are limited to the frequency domain range of the uplink subband, which is the uplink subband configured to exist in the time domain unit occupied by SSB transmission;
  • Uplink transmission is a transmission scheduled according to dynamic signaling
  • the priority of upstream transmission is configured or indicated as high priority.
  • the above-mentioned uplink transmission may include but is not limited to PUSCH/PUCCH/PRACH/SRS transmission.
  • Figure 4 is a flow chart of an information configuration method provided by an embodiment of the present application. The method is applied to network side devices. As shown in Figure 4, the method includes the following steps:
  • Step 41 The network side device sends the first configuration information to the terminal.
  • the first configuration information up to M sets of configuration information are configured for a single PUCCH resource (such as PUCCH Resource), and each set of configuration information corresponds to a time domain unit that meets specific requirements; or, the first configuration information includes up to N items of PUCCH configuration (such as PUCCH Config), each PUCCH configuration corresponds to a time domain unit that meets specific requirements; the M is an integer greater than 1, and the N is an integer greater than 1.
  • parameters matching their related characteristics can be configured for different uplink resources, such as time-frequency location, code rate, power, etc., so as to make full use of uplink resources based on the characteristics of different uplink resources and ensure the performance of PUCCH transmission.
  • the above-mentioned time domain units that meet specific requirements may include a first type of time domain unit and/or a second type of time domain unit.
  • the first type of time domain unit is when there are available uplink resources within the uplink BWP range.
  • Domain unit, the second type of time domain unit is a time domain unit with available uplink resources only within the uplink subband range.
  • the above-mentioned first type of time domain unit may include at least one of the following:
  • the first Semi-static flexible time domain unit in which, in the first Semi-static flexible time domain unit, the frequency domain range corresponding to the uplink BWP can be used as available uplink resources, that is, the above frequency domain restriction method 2 is adopted;
  • a Semi-static flexible time domain unit is a Semi-static flexible time domain unit that allows flexible duplex operation.
  • the first Semi-static flexible time domain unit here does not include the SSB time domain unit.
  • the above-mentioned second type of time domain unit may include at least one of the following:
  • the Semi-static downlink time domain unit here can be understood as a Semi-static DL time domain unit configured with UL sub-band;
  • the Semi-static DL time domain unit here does not include the SSB time domain unit.
  • the second Semi-static flexible time domain unit in which, in the second Semi-static flexible time domain unit, only the frequency domain range corresponding to the uplink subband can be used as available uplink resources, that is, the above frequency domain restriction method 1 is adopted;
  • the second Semi-static flexible time domain unit is a Semi-static flexible time domain unit that allows flexible duplex operation.
  • the second Semi-static flexible time domain unit here does not include the SSB time domain unit.
  • the single set of configuration information corresponds to the first type of time domain unit or the second type of time domain unit;
  • the two sets of configuration information include a first set of configuration information and a second set of configuration information
  • the first set of configuration information corresponds to the first type of time domain unit
  • the second set of configuration information corresponds to the second type of time domain unit
  • the first set of configuration information corresponds to the second type of time domain unit
  • the second set of configuration information corresponds to the first type time domain unit
  • the network side device may send the first higher layer signaling and/or the first DCI to the terminal; wherein the first higher layer signaling and/or the first DCI are from the terminal Determine the application configuration information from the two sets of configuration information described above.
  • the configuration information of the application meets any of the following:
  • the second indication field in the first DCI jointly indicates the PRI and the configuration information of the application
  • the third indication field in the first DCI jointly indicates K1 and the configuration information of the application.
  • the first configuration information includes two items of PUCCH configuration, and the two items of PUCCH configuration include a first item of PUCCH configuration and a second item of PUCCH configuration
  • the first item of PUCCH configuration corresponds to the first item of PUCCH configuration.
  • time domain unit the second PUCCH configuration corresponds to the second type time domain unit; or the first PUCCH configuration corresponds to the second type time domain unit, and the second PUCCH configuration corresponds to all Describe the first type of time domain unit.
  • the network side device may send the second higher layer signaling and/or the second DCI to the terminal; wherein the second higher layer signaling and/or the second DCI are used by the terminal to determine from the two PUCCH configurations The applied PUCCH configuration.
  • the PUCCH configuration of the application meets any of the following:
  • the fifth indication field in the second DCI jointly indicates the PRI and the PUCCH configuration of the application
  • the sixth indication field in the second DCI jointly indicates K1 and the applied PUCCH configuration.
  • the execution subject may be an information configuration device.
  • the information configuration device performing the information configuration method is taken as an example to illustrate the information configuration device provided by the embodiment of the present application.
  • Figure 5 is a schematic structural diagram of an information configuration device provided by an embodiment of the present application. The device is applied to a terminal. As shown in Figure 5, the information configuration device 50 includes:
  • the receiving module 51 is used to receive the first configuration information from the network side device
  • the first configuration information at most M sets of configuration information are configured for a single PUCCH resource, and each set of configuration information corresponds to a time domain unit that meets specific requirements; or, the first configuration information includes at most N PUCCH configurations , each PUCCH configuration corresponds to a time domain unit that meets specific requirements; the M is an integer greater than 1, and the N is an integer greater than 1.
  • the time domain unit that meets specific requirements includes a first type of time domain unit and/or a second type of time domain unit.
  • the first type of time domain unit is any time domain unit with available uplink resources within the uplink BWP range.
  • a time domain unit, the second type of time domain unit is any time domain unit with available uplink resources only within the uplink subband range.
  • the first type of time domain unit includes at least one of the following:
  • a first Semi-static flexible time domain unit wherein in the first Semi-static flexible time domain unit, the frequency domain range corresponding to the uplink BWP can be used as available uplink resources;
  • the second type of time domain unit includes at least one of the following:
  • the second Semi-static flexible time domain unit wherein in the second Semi-static flexible time domain unit, only the frequency domain range corresponding to the uplink subband can be used as available uplink resources.
  • the single set of configuration information corresponds to the first type of time domain unit or the second type of time domain unit;
  • the two sets of configuration information include a first set of configuration information and a second set of configuration information
  • the first set of configuration information corresponds to the first type of time domain unit
  • the second set of configuration information corresponds to the second type of time domain unit
  • the first set of configuration information corresponds to the second type of time domain unit
  • the second set of configuration information corresponds to the first type time domain unit
  • the information configuration device 50 also includes:
  • a first determination module configured to determine application configuration information from the two sets of configuration information based on at least one of the following:
  • the category of the time domain unit where the single PUCCH resource is located or the category of the time domain unit where the repeated transmission of the single PUCCH resource is located;
  • the first downlink control information DCI DCI.
  • each repeated transmission of the PUCCH resource satisfies at least one of the following:
  • the number of included REs used to carry uplink control information UCI is consistent
  • the number of occupied time domain units is the same.
  • the first determination module is further configured to: determine the application from the two sets of configuration information according to at least one of the following: Configuration information:
  • the category of the nominal time domain unit of the PUCCH resource is the category of the nominal time domain unit of the PUCCH resource
  • the category of the time domain unit in which the first actually initiated repeated transmission of the PUCCH resource is located.
  • the configuration information of the application meets any of the following:
  • the second indication field in the first DCI jointly indicates the PUCCH resource indication PRI and the configuration information of the application;
  • the third indication field in the first DCI jointly indicates K1 and the configuration information of the application.
  • the information configuration device 50 also includes:
  • the first execution module is used to perform any of the following:
  • the first PUCCH resource When the first PUCCH resource is not configured for repeated transmission, if the first PUCCH resource overlaps with other types of time domain units based on the second configuration information, perform one of the following: determine that the first PUCCH resource is not available used to determine the first predefined condition when the first predefined condition is not met in at least one overlapping other category time domain unit. PUCCH resources are not available;
  • the first repeated transmission of the first PUCCH resource overlaps with other types of time domain units, perform one of the following: determine the The first repeated transmission is unavailable, and it is determined that the first repeated transmission is unavailable when the first predefined condition is not met within at least one overlapping other category time domain unit;
  • the second configuration information is a single set of configuration information configured for the first PUCCH resource, or the second configuration information is one determined from two sets of configuration information configured for the first PUCCH resource. set of configuration information;
  • the time domain unit corresponding to the second configuration information is the first type of time domain unit, and the other types of time domain units are the second type time domain unit; or, the time domain unit corresponding to the second configuration information is The time domain unit is the second type of time domain unit, and the other types of time domain units are the first type of time domain unit.
  • the terminal when using the third configuration information to determine the PUCCH transmission corresponding to the first PUCCH resource, the terminal does not expect the first PUCCH resource or the first PUCCH resource.
  • the first repeated transmission overlaps with time domain units of other categories, or when the first PUCCH resource or the first repeated transmission of the first PUCCH resource overlaps with time domain units of other categories, the The terminal does not expect to not satisfy the first predefined condition in at least one overlapping other category time domain unit;
  • the third configuration information is a single set of configuration information configured for the first PUCCH resource
  • the time domain unit corresponding to the third configuration information is the first type of time domain unit, and the other types of time domain units
  • the unit is the second type of time domain unit; or the time domain unit corresponding to the third configuration information is the second type of time domain unit, and the other types of time domain units are the first type of time domain unit.
  • the terminal when using the third configuration information to determine the PUCCH transmission corresponding to the first PUCCH resource, the terminal does not expect the first PUCCH resource or any repeated transmission of the first PUCCH resource to exist with other types of time domain units. Overlap; or, when the first PUCCH resource or the third repeated transmission of the first PUCCH resource overlaps with other types of time domain units, the terminal does not expect to transmit in at least one overlapping time domain unit of other types.
  • the first predefined condition is not satisfied within the unit; wherein the third configuration information is a set of configuration information determined from two sets of configuration information configured for the first PUCCH resource, and the third configuration information is based on the configuration Or indicate confirmation; the time domain unit corresponding to the third configuration information is the first type of time domain unit, and the other types of time domain units are the second type of time domain unit; or, the third configuration information The corresponding time domain unit is the second type of time domain unit, and the other types of time domain units are the first type of time domain unit.
  • the first predefined condition includes at least one of the following:
  • time domain units are the first type of time domain units
  • the first PUCCH resource or any resource occupied by the repeated transmission of the first PUCCH resource in the overlapping time domain unit of other types The units RE are all located in the frequency domain range corresponding to the uplink subband.
  • the first configuration information includes two items of PUCCH configuration, and the two items of PUCCH configuration include a first item of PUCCH configuration and a second item of PUCCH configuration
  • the first item of PUCCH configuration corresponds to the first item of PUCCH configuration.
  • time domain unit the second PUCCH configuration corresponds to the second type time domain unit; or the first PUCCH configuration corresponds to the second type time domain unit, and the second PUCCH configuration corresponds to all Describe the first type of time domain unit.
  • the information configuration device 50 further includes:
  • the second determination module is configured to determine the applied PUCCH configuration from the two PUCCH configurations according to at least one of the following:
  • the PUCCH resources used in the first PUCCH configuration and the second PUCCH configuration are The configuration of the identifier must meet at least one of the following:
  • the second identifier of the PUCCH resource used in the second PUCCH configuration, the identifier of the PUCCH resource used in the first PUCCH configuration is determined based on the second identifier;
  • Identifiers of PUCCH resources used in the first PUCCH configuration and the second PUCCH configuration are respectively configured.
  • the applied PUCCH configuration when the applied PUCCH configuration is determined from the two PUCCH configurations according to the second DCI, the applied PUCCH configuration satisfies any of the following:
  • the fifth indication field in the second DCI jointly indicates the PRI and the PUCCH configuration of the application
  • the sixth indication field in the second DCI jointly indicates K1 and the applied PUCCH configuration.
  • the information configuration device 50 further includes:
  • the second execution module is used to perform any of the following:
  • the second PUCCH resource When the second PUCCH resource is not configured for repeated transmission, if the second PUCCH resource overlaps with other types of time domain units based on the fourth configuration information, perform one of the following: determine that the second PUCCH resource is not available Determining that the second PUCCH resource is unavailable when the second predefined condition is not met in at least one overlapping other category time domain unit;
  • the fourth repeated transmission of the second PUCCH resource overlaps with other types of time domain units based on the fourth configuration information, perform one of the following: determine the The fourth repeated transmission is unavailable, and it is determined that the fourth repeated transmission is unavailable when the second predefined condition is not met in at least one overlapping other category time domain unit;
  • the second PUCCH resource is a single PUCCH resource in the PUCCH configuration of the application, so
  • the fourth configuration information is the configuration information corresponding to the second PUCCH resource in the PUCCH configuration of the application;
  • the time domain unit corresponding to the PUCCH configuration of the application is the first type of time domain unit, and the other
  • the type of time domain unit is the second type of time domain unit; or the time domain unit corresponding to the applied PUCCH configuration is the second type of time domain unit, and the other types of time domain units are the first type of time domain unit. time domain unit.
  • the terminal when using the fifth configuration information to determine the PUCCH transmission corresponding to the second PUCCH resource, the terminal does not expect the second PUCCH resource or any repeated transmission of the second PUCCH resource to exist with other types of time domain units. Overlap; or, when the second PUCCH resource or the fifth repeated transmission of the second PUCCH resource overlaps with other types of time domain units, the terminal does not expect to transmit in at least one overlapping time domain unit of other types.
  • the second predefined condition is not satisfied within the unit; wherein the second PUCCH resource is a single PUCCH resource in the PUCCH configuration of the application, and the fifth configuration information is the same as the third PUCCH resource in the PUCCH configuration of the application. 2. Configuration information corresponding to PUCCH resources.
  • the PUCCH configuration of the application is determined based on the configuration or indication; the time domain unit corresponding to the PUCCH configuration of the application is the first type of time domain unit, and the other types of time domain units are all The second type of time domain unit; or, the time domain unit corresponding to the applied PUCCH configuration is the second type of time domain unit, and the other types of time domain units are the first type of time domain unit.
  • the second predefined condition includes at least one of the following:
  • time domain units are the first type of time domain units
  • the second PUCCH resource or the repeated transmission of the second PUCCH resource is occupied by any of the overlapping time domain units of other types.
  • One RE is located in the frequency domain range corresponding to the uplink subband.
  • the information configuration device 50 also includes:
  • the third execution module is used to perform any of the following:
  • the third predefined condition includes at least one of the following:
  • the frequency domain resources occupied by the uplink transmission are limited to the frequency domain range of the uplink subband, and the uplink subband is the uplink subband configured to exist in the time domain unit occupied by the SSB transmission;
  • the uplink transmission is transmission scheduled according to dynamic signaling
  • the priority of the uplink transmission is configured or indicated as high priority.
  • the information configuration device 50 in the embodiment of the present application may be an electronic device, such as an electronic device with an operating system, or may be a component in the electronic device, such as an integrated circuit or chip.
  • the electronic device may be a terminal or other devices other than the terminal.
  • the terminal may include but is not limited to the types of terminal 11 listed above, Other devices may be servers, network attached storage (Network Attached Storage, NAS), etc., which are not specifically limited in the embodiments of this application.
  • NAS Network Attached Storage
  • the information configuration device 50 provided by the embodiment of the present application can implement each process implemented by the method embodiment shown in Figure 3 and achieve the same technical effect. To avoid duplication, the details will not be described here.
  • Figure 6 is a schematic structural diagram of an information configuration device provided by an embodiment of the present application. The device is applied to network side equipment. As shown in Figure 6, the information configuration device 60 includes:
  • the sending module 61 is used to send the first configuration information to the terminal;
  • the first configuration information at most M sets of configuration information are configured for a single PUCCH resource, and each set of configuration information corresponds to a time domain unit that meets specific requirements; or, the first configuration information includes at most N PUCCH configurations , each PUCCH configuration corresponds to a time domain unit that meets specific requirements; the M is an integer greater than 1, and the N is an integer greater than 1.
  • the above-mentioned time domain units that meet specific requirements may include a first type of time domain unit and/or a second type of time domain unit.
  • the first type of time domain unit is when there are available uplink resources within the uplink BWP range.
  • Domain unit, the second type of time domain unit is a time domain unit with available uplink resources only within the uplink subband range.
  • the above-mentioned first type of time domain unit may include at least one of the following:
  • the first Semi-static flexible time domain unit in which, in the first Semi-static flexible time domain unit, the frequency domain range corresponding to the uplink BWP can be used as available uplink resources, that is, the above frequency domain restriction method 2 is adopted;
  • a Semi-static flexible time domain unit is a Semi-static flexible time domain unit that allows flexible duplex operation.
  • the first Semi-static flexible time domain unit here does not include the SSB time domain unit.
  • the above-mentioned second type of time domain unit may include at least one of the following:
  • the Semi-static downlink time domain unit here can be understood as a Semi-static DL time domain unit configured with UL sub-band;
  • the Semi-static DL time domain unit here does not include the SSB time domain unit.
  • the second Semi-static flexible time domain unit in which, in the second Semi-static flexible time domain unit, only the frequency domain range corresponding to the uplink subband can be used as available uplink resources, that is, the above frequency domain restriction method 1 is adopted;
  • the second Semi-static flexible time domain unit is a Semi-static flexible time domain unit that allows flexible duplex operation.
  • the second Semi-static flexible time domain unit here does not include the SSB time domain unit.
  • the single set of configuration information corresponds to the first type of time domain unit or the second type of time domain unit;
  • the two sets of configuration information include a first set of configuration information and a second set of configuration information
  • the first set of configuration information corresponds to the first type of time domain unit
  • the mentioned Two sets of configuration information correspond to the second type of time domain unit
  • the first set of configuration information corresponds to the second type of time domain unit
  • the second set of configuration information corresponds to the first type of time domain unit.
  • the sending module 61 is also configured to: send the first higher layer signaling and/or the first DCI to the terminal; wherein the first higher layer signaling and/or the first DCI A DCI is used by the terminal to determine application configuration information from the two sets of configuration information.
  • the configuration information of the application meets any of the following:
  • the second indication field in the first DCI jointly indicates the PRI and the configuration information of the application
  • the third indication field in the first DCI jointly indicates K1 and the configuration information of the application.
  • the first configuration information includes two items of PUCCH configuration, and the two items of PUCCH configuration include a first item of PUCCH configuration and a second item of PUCCH configuration
  • the first item of PUCCH configuration corresponds to the first item of PUCCH configuration.
  • time domain unit the second PUCCH configuration corresponds to the second type time domain unit; or the first PUCCH configuration corresponds to the second type time domain unit, and the second PUCCH configuration corresponds to all Describe the first type of time domain unit.
  • the sending module 61 is also configured to: send the second high-level signaling and/or the second DCI to the terminal; wherein the second high-level signaling and/or the second DCI are used for the terminal to obtain the information from the two items of PUCCH. Determine the applied PUCCH configuration in the configuration.
  • the PUCCH configuration of the application meets any of the following:
  • the fifth indication field in the second DCI jointly indicates the PRI and the PUCCH configuration of the application
  • the sixth indication field in the second DCI jointly indicates K1 and the applied PUCCH configuration.
  • the information configuration device 60 provided by the embodiment of the present application can implement each process implemented by the method embodiment shown in Figure 4 and achieve the same technical effect. To avoid duplication, the details will not be described here.
  • this embodiment of the present application also provides a communication device 70, which includes a processor 71 and a memory 72.
  • the memory 72 stores programs or instructions that can be run on the processor 71, such as , when the communication device 70 is a terminal, when the program or instruction is executed by the processor 71, each step of the information configuration method embodiment shown in FIG. 3 is implemented, and the same technical effect can be achieved.
  • the communication device 70 is a network-side device, when the program or instruction is executed by the processor 71, the steps of the information configuration method embodiment shown in FIG. 4 are implemented, and the same technical effect can be achieved. To avoid duplication, the steps are not included here. Again.
  • An embodiment of the present application also provides a terminal, including a processor and a communication interface.
  • the communication interface is used to receive first configuration information from a network side device; wherein, in the first configuration information, a maximum of M sets are configured for a single PUCCH resource.
  • Configuration information each set of configuration information corresponds to a time domain unit that meets specific requirements; or, the first configuration information includes at most N PUCCH configurations, each PUCCH configuration corresponds to a time domain unit that meets specific requirements; the M is An integer greater than 1, and N is an integer greater than 1.
  • This terminal embodiment corresponds to the above-mentioned terminal-side method embodiment.
  • Each implementation process and implementation manner of the above-mentioned method embodiment can be applied to this terminal embodiment, and the same technology can be achieved. Technological effect.
  • FIG. 8 is a schematic diagram of the hardware structure of a terminal that implements an embodiment of the present application.
  • the terminal 800 includes but is not limited to: a radio frequency unit 801, a network module 802, an audio output unit 803, an input unit 804, a sensor 805, a display unit 806, a user input unit 807, an interface unit 808, a memory 809, a processor 810, etc. At least some parts.
  • the terminal 800 may also include a power supply (such as a battery) that supplies power to various components.
  • the power supply may be logically connected to the processor 810 through a power management system, thereby managing charging, discharging, and power consumption through the power management system. Management and other functions.
  • the terminal structure shown in FIG. 8 does not constitute a limitation on the terminal.
  • the terminal may include more or fewer components than shown in the figure, or some components may be combined or arranged differently, which will not be described again here.
  • the input unit 804 may include a graphics processing unit (Graphics Processing Unit, GPU) 8041 and a microphone 8042.
  • the graphics processor 8041 is responsible for the image capture device (GPU) in the video capture mode or the image capture mode. Process the image data of still pictures or videos obtained by cameras (such as cameras).
  • the display unit 806 may include a display panel 8061, which may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like.
  • the user input unit 807 includes a touch panel 8071 and at least one of other input devices 8072 .
  • Touch panel 8071 also known as touch screen.
  • the touch panel 8071 may include two parts: a touch detection device and a touch controller.
  • Other input devices 8072 may include but are not limited to physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, and joysticks, which will not be described again here.
  • the radio frequency unit 801 after receiving downlink data from the network side device, the radio frequency unit 801 can transmit it to the processor 810 for processing; in addition, the radio frequency unit 801 can send uplink data to the network side device.
  • the radio frequency unit 801 includes, but is not limited to, an antenna, amplifier, transceiver, coupler, low noise amplifier, duplexer, etc.
  • Memory 809 may be used to store software programs or instructions as well as various data.
  • the memory 809 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instructions required for at least one function (such as a sound playback function, Image playback function, etc.) etc.
  • memory 809 may include volatile memory or non-volatile memory, or memory 809 may include both volatile and non-volatile memory.
  • non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically removable memory. Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • Volatile memory can be random access memory (Random Access Memory, RAM), static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDRSDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (Synch link DRAM) , SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DRRAM).
  • RAM Random Access Memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM Double Data Rate SDRAM
  • DDRSDRAM double data rate synchronous dynamic random access memory
  • Enhanced SDRAM, ESDRAM enhanced synchronous dynamic random access memory
  • Synch link DRAM synchronous link dynamic random access memory
  • SLDRAM direct memory bus
  • Processor 810 may include one or more processing units; optionally, processor 810 integrates an application processor and modulation Demodulation processor, among which the application processor mainly processes operations involving the operating system, user interface and application programs, etc., and the modem processor mainly processes wireless communication signals, such as baseband processor. It can be understood that the above modem processor may not be integrated into the processor 810.
  • the radio frequency unit 801 is used to receive the first configuration information from the network side device; in the first configuration information, up to M sets of configuration information are configured for a single PUCCH resource, and each set of configuration information is associated with a time domain unit that meets specific requirements. corresponding; or, the first configuration information includes at most N PUCCH configurations, each PUCCH configuration corresponds to a time domain unit that meets specific requirements; the M is an integer greater than 1, and the N is an integer greater than 1.
  • the terminal 800 provided by the embodiment of this application can implement each process implemented by the method embodiment shown in Figure 3 and achieve the same technical effect. To avoid duplication, the details will not be described here.
  • Embodiments of the present application also provide a network side device, including a processor and a communication interface.
  • the communication interface is used to send first configuration information to the terminal; in the first configuration information, up to M sets of configuration information are configured for a single PUCCH resource. , each set of configuration information corresponds to a time domain unit that meets specific requirements; or, the first configuration information includes at most N PUCCH configurations, each PUCCH configuration corresponds to a time domain unit that meets specific requirements; the M is greater than 1 an integer, and N is an integer greater than 1.
  • This network-side device embodiment corresponds to the above-mentioned network-side device method embodiment. Each implementation process and implementation manner of the above-mentioned method embodiment can be applied to this network-side device embodiment, and can achieve the same technical effect.
  • the embodiment of the present application also provides a network side device.
  • the network side device 90 includes: an antenna 91 , a radio frequency device 92 , a baseband device 93 , a processor 94 and a memory 95 .
  • the antenna 91 is connected to the radio frequency device 92 .
  • the radio frequency device 92 receives information through the antenna 91 and sends the received information to the baseband device 93 for processing.
  • the baseband device 93 processes the information to be sent and sends it to the radio frequency device 92.
  • the radio frequency device 92 processes the received information and then sends it out through the antenna 91.
  • the method performed by the network side device in the above embodiment can be implemented in the baseband device 93, which includes a baseband processor.
  • the baseband device 93 may include, for example, at least one baseband board, which is provided with multiple chips, as shown in FIG. Program to perform the network device operations shown in the above method embodiments.
  • the network side device may also include a network interface 96, which is, for example, a common public radio interface (CPRI).
  • a network interface 96 which is, for example, a common public radio interface (CPRI).
  • CPRI common public radio interface
  • the network side device 90 in this embodiment of the present invention also includes: instructions or programs stored in the memory 95 and executable on the processor 94.
  • the processor 94 calls the instructions or programs in the memory 95 to execute each of the steps shown in Figure 6. The method of module execution and achieving the same technical effect will not be described in detail here to avoid duplication.
  • Embodiments of the present application also provide a readable storage medium.
  • Programs or instructions are stored on the readable storage medium.
  • each process of the information configuration method embodiment shown in Figure 3 is implemented.
  • each process of the above-mentioned information configuration method embodiment shown in Figure 4 can achieve the same technical effect. To avoid duplication, details will not be described here.
  • the processor is the processor in the terminal described in the above embodiment.
  • the readable storage medium includes computer readable storage media, such as computer read-only memory ROM, random access memory RAM, magnetic disk or optical disk, etc.
  • An embodiment of the present application further provides a chip.
  • the chip includes a processor and a communication interface.
  • the communication interface is coupled to the processor.
  • the processor is used to run programs or instructions to implement the information shown in Figure 3.
  • Each process of the configuration method embodiment, or each process of implementing the above-mentioned information configuration method embodiment shown in Figure 4, can achieve the same technical effect. To avoid duplication, it will not be described again here.
  • chips mentioned in the embodiments of this application may also be called system-on-chip, system-on-a-chip, system-on-chip or system-on-chip, etc.
  • Embodiments of the present application further provide a computer program/program product.
  • the computer program/program product is stored in a storage medium.
  • the computer program/program product is executed by at least one processor to implement the above information configuration method embodiment.
  • Each process can achieve the same technical effect. To avoid repetition, we will not go into details here.
  • Embodiments of the present application also provide a communication system, including: a terminal and a network side device.
  • the terminal can be used to perform the steps of the information configuration method as shown in Figure 3 above.
  • the network side device can be used to perform the steps of the information configuration method as shown in Figure 4 above. The steps of the information configuration method shown below.
  • the methods of the above embodiments can be implemented by means of software plus the necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is better. implementation.
  • the technical solution of the present application can be embodied in the form of a computer software product that is essentially or contributes to the existing technology.
  • the computer software product is stored in a storage medium (such as ROM/RAM, disk , CD), including several instructions to cause a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in various embodiments of this application.

Landscapes

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

Abstract

本申请公开了一种信息配置方法、装置、终端、网络侧设备及可读存储介质，属于通信技术领域，本申请实施例的信息配置方法包括：终端从网络侧设备接收第一配置信息；其中，在所述第一配置信息中，针对单个物理上行控制信道资源PUCCH资源配置最多M套配置信息，每套配置信息与满足特定要求的时域单元对应，或者，所述第一配置信息包括最多N项PUCCH配置，每项PUCCH配置与满足特定要求的时域单元对应；所述M为大于1的整数，所述N为大于1的整数。

Description

信息配置方法、装置、终端、网络侧设备及可读存储介质
相关申请的交叉引用
本申请主张在2022年7月25日提交的中国专利申请No.202210877636.9的优先权，其全部内容通过引用包含于此。
技术领域
本申请属于通信技术领域，具体涉及一种信息配置方法、装置、终端、网络侧设备及可读存储介质。
背景技术
为了更灵活地利用有限的频谱资源，以动态地匹配业务需求，提升资源利用效率，以及数据传输的上行覆盖、时延等性能，当前提出了灵活双工方式。此灵活双工方式为：网络侧全双工，即在同一时刻，上行传输和下行传输可在不同的频域位置同时进行，以及终端侧半双工，即与时分双工(Time Division Duplex，TDD)一致，在同一时刻，只能作上行传输或下行传输，两者不可同时进行。在此灵活双工方式下，在TDD帧结构的下行符号和上行符号内都存在可用上行资源，但这两种上行资源对应的可用带宽、产生/受到的干扰等都有所不同，对物理上行控制信道(Physical Uplink Control Channel，PUCCH)传输的要求不同，若按照相同的配置进行PUCCH传输，可能会影响PUCCH传输的性能。
发明内容
本申请实施例提供一种信息配置方法、装置、终端、网络侧设备及可读存储介质，能够解决在灵活双工方式下，如何保障PUCCH传输的性能的问题。
第一方面，提供了一种信息配置方法，包括：
终端从网络侧设备接收第一配置信息；
其中，在所述第一配置信息中，针对单个PUCCH资源配置最多M套配置信息，每套配置信息与满足特定要求的时域单元对应；或者，所述第一配置信息包括最多N项PUCCH配置，每项PUCCH配置与满足特定要求的时域单元对应；所述M为大于1的整数，所述N为大于1的整数。
第二方面，提供了一种信息配置方法，包括：
网络侧设备向终端发送第一配置信息；
其中，在所述第一配置信息中，针对单个PUCCH资源配置最多M套配置信息，每套配置信息与满足特定要求的时域单元对应；或者，所述第一配置信息包括最多N项PUCCH 配置，每项PUCCH配置与满足特定要求的时域单元对应；所述M为大于1的整数，所述N为大于1的整数。
第三方面，提供了一种信息配置装置，应用于终端，包括：
接收模块，用于从网络侧设备接收第一配置信息；
其中，在所述第一配置信息中，针对单个PUCCH资源配置最多M套配置信息，每套配置信息与满足特定要求的时域单元对应；或者，所述第一配置信息包括最多N项PUCCH配置，每项PUCCH配置与满足特定要求的时域单元对应；所述M为大于1的整数，所述N为大于1的整数。
第四方面，提供了一种信息配置装置，应用于网络侧设备，包括：
发送模块，用于向终端发送第一配置信息；
其中，在所述第一配置信息中，针对单个PUCCH资源配置最多M套配置信息，每套配置信息与满足特定要求的时域单元对应；或者，所述第一配置信息包括最多N项PUCCH配置，每项PUCCH配置与满足特定要求的时域单元对应；所述M为大于1的整数，所述N为大于1的整数。
第五方面，提供了一种终端，该终端包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤。
第六方面，提供了一种终端，包括处理器及通信接口，其中，所述通信接口用于从网络侧设备接收第一配置信息；其中，在所述第一配置信息中，针对单个PUCCH资源配置最多M套配置信息，每套配置信息与满足特定要求的时域单元对应；或者，所述第一配置信息包括最多N项PUCCH配置，每项PUCCH配置与满足特定要求的时域单元对应；所述M为大于1的整数，所述N为大于1的整数。
第七方面，提供了一种网络侧设备，该网络侧设备包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第二方面所述的方法的步骤。
第八方面，提供了一种网络侧设备，包括处理器及通信接口，其中，所述通信接口用于向终端发送第一配置信息；在所述第一配置信息中，针对单个PUCCH资源配置最多M套配置信息，每套配置信息与满足特定要求的时域单元对应；或者，所述第一配置信息包括最多N项PUCCH配置，每项PUCCH配置与满足特定要求的时域单元对应；所述M为大于1的整数，所述N为大于1的整数。
第九方面，提供了一种通信系统，包括：终端及网络侧设备，所述终端可用于执行如第一方面所述的信息配置方法的步骤，所述网络侧设备可用于执行如第二方面所述的信息配置方法的步骤。
第十方面，提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如第一方面所述的方法的步骤，或者实现如第二方面所述的 方法的步骤。
第十一方面，提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如第一方面所述的方法的步骤，或者实现如第二方面所述的方法的步骤。
第十二方面，提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在存储介质中，所述计算机程序/程序产品被至少一个处理器执行以实现如第一方面所述的方法的步骤，或者实现如第二方面所述的方法的步骤。
在本申请实施例中，终端可以从网络侧设备接收第一配置信息；在该第一配置信息中，针对单个PUCCH资源配置最多M套配置信息，每套配置信息与满足特定要求的时域单元对应；或者，该第一配置信息包括最多N项PUCCH配置，每项PUCCH配置与满足特定要求的时域单元对应。由此，对于PUCCH传输，可以针对不同上行资源分别配置匹配其相关特性的参数，比如包括时频位置、码率、功率等，从而基于不同上行资源的特性充分利用上行资源，保障PUCCH传输的性能。
附图说明
图1是本申请实施例可应用的一种无线通信系统的框图；
图2是本申请实施例中的灵活双工方式的示意图；
图3是本申请实施例提供的一种信息配置方法的流程图；
图4是本申请实施例提供的另一种信息配置方法的流程图；
图5是本申请实施例提供的一种信息配置装置的结构示意图；
图6是本申请实施例提供的另一种信息配置装置的结构示意图；
图7是本申请实施例提供的一种通信设备的结构示意图；
图8是本申请实施例提供的一种终端的结构示意图；
图9是本申请实施例提供的一种网络侧设备的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员所获得的所有其他实施例，都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”所区别的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，说明书以及权利要求中“和/或”表示所连接对象的至少其中之一， 字符“/”一般表示前后关联对象是一种“或”的关系。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(Long Term Evolution，LTE)/LTE的演进(LTE-Advanced，LTE-A)系统，还可用于其他无线通信系统，诸如码分多址(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)和其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用，所描述的技术既可用于以上提及的系统和无线电技术，也可用于其他系统和无线电技术。以下描述出于示例目的描述了新空口(New Radio，NR)系统，并且在以下大部分描述中使用NR术语，但是这些技术也可应用于NR系统应用以外的应用，如第6代(6th Generation，6G)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的框图。无线通信系统包括终端11和网络侧设备12。其中，终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)或称为笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计算机(ultra-mobile personal computer，UMPC)、移动上网装置(Mobile Internet Device，MID)、增强现实(augmented reality，AR)/虚拟现实(virtual reality，VR)设备、机器人、可穿戴式设备(Wearable Device)、车载设备(Vehicle User Equipment，VUE)、行人终端(Pedestrian User Equipment，PUE)、智能家居(具有无线通信功能的家居设备，如冰箱、电视、洗衣机或者家具等)、游戏机、个人计算机(personal computer，PC)、柜员机或者自助机等终端侧设备，可穿戴式设备包括：智能手表、智能手环、智能耳机、智能眼镜、智能首饰(智能手镯、智能手链、智能戒指、智能项链、智能脚镯、智能脚链等)、智能腕带、智能服装等。需要说明的是，在本申请实施例并不限定终端11的具体类型。网络侧设备12可以包括接入网设备或核心网设备，其中，接入网设备也可以称为无线接入网设备、无线接入网(Radio Access Network，RAN)、无线接入网功能或无线接入网单元。接入网设备可以包括基站、无线局域网(Wireless Local Area Network，WLAN)接入点或WiFi节点等，基站可被称为节点B、演进节点B(eNB)、接入点、基收发机站(Base Transceiver Station，BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set，BSS)、扩展服务集(Extended Service Set，ESS)、家用B节点、家用演进型B节点、发送接收点(Transmitting Receiving Point，TRP)或所述领域中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR系统中的基站为例进行介绍，并不限定基站的具体类型。
为了便于理解本申请实施例，首先说明以下内容。
在部署传统的蜂窝网络时，基于可用的频谱，以及业务特性等，可采用频分双工(Frequency Division Duplex，FDD)或时分双工(Time Division Duplex，TDD)方式。当 采用FDD方式时，上行传输和下行传输位于不同的频点上，两者互不干扰，可同时进行。当采用TDD方式时，上行传输和下行传输位于同一个频点上，采用时分的方式交错进行。这两种双工方式各有优缺点。
为了更灵活地利用有限的频谱资源，以动态地匹配业务需求，提升资源利用效率，以及数据传输的上行覆盖、时延等性能，提出了灵活双工方式，此灵活双工方式可称为无重叠子带全双工(non-overlapping sub-band full duplex，SBFD)方式。此SBFD为：网络侧全双工，即在同一时刻，上行传输和下行传输可在不同的频域位置同时进行，为避免上下行之间的干扰，可在对应不同传输方向的频域位置(对应双工子带)之间留出一定的保护频带(Guard Band)；终端侧半双工，即与时分双工TDD一致，在同一时刻，只能作上行传输或下行传输，两者不可同时进行。可以理解的是，在这种双工方式下，网络侧在同一时刻的上行传输和下行传输只能针对不同的终端。
如图2所示，图2给出了上述灵活双工方式的示意图，网络侧设备在一部分下行符号内，将单个载波的频域半静态划分为三个双工子带，其中载波两侧为下行双工子带，中间为上行双工子带，以减少对相邻载波造成的干扰。在第三个时隙内，UE1和UE2分别作上行发送和下行接收。
可选地，当小区(比如NR小区)部署在非对称频谱上时，一般采用TDD方式。此时可以在小区公共参数中配置TDD上下行公共配置TDD-UL-DL-ConfigCommon，以指示TDD帧结构信息，包括TDD帧周期、单个帧周期内包含的完整下行/上行时隙(Slot)数目、在完整下行/上行Slot之外额外包含的下行/上行符号(Symbol)数目等。可选地，还可以针对各个终端采用无线资源控制(Radio Resource Control，RRC)信令独立配置TDD上下行专用配置TDD-UL-DL-ConfigDedicated，用于在TDD-UL-DL-ConfigCommon的基础上进一步修改单个帧周期内一个或多个Slot的上下行Symbol配置，即，Slot的上下行Symbol配置的初始值由TDD-UL-DL-ConfigCommon规定，然后由TDD-UL-DL-ConfigDedicated进一步修改，此修改仅应用于接收此RRC信令的终端。但是，这里的修改仅局限于将Slot内的灵活符号(Flexible symbol)进一步指示为下行符号(DL symbol)或上行符号(UL symbol)，不能将Slot时隙内的DL/UL symbol修改为其它方向。Flexible symbol为未明确传输方向的符号，后续可根据需要再确定是用于下行传输还是上行传输。
上述TDD-UL-DL-ConfigCommon和/或TDD-UL-DL-ConfigDedicated为可选配置，由于这些配置信息只能基于RRC信令半静态配置/修改，所以由这些配置信息确定的单个TDD帧周期内各个Symbol，结合为其配置的传输方向，在下文中称之为半静态(Semi-static)DL/UL/flexible symbol。此外，可以将符号进一步抽象为时域单元，时域单元可对应时隙(Slot)、符号(Symbol)等，则单个TDD帧周期内可基于上述配置信息包含多个Semi-static DL/UL/flexible时域单元。当未配置上述TDD-UL-DL-ConfigCommon和TDD-UL-DL-ConfigDedicated时，不存在明确的TDD帧周期的概念，此时NR小区各个 无线帧内的各个Slot/Symbol都可以理解为Semi-static flexible slot/symbol，或者抽象为Semi-static flexible时域单元。
在前述灵活双工方式下，在TDD帧结构的下行符号和上行符号内都存在可用上行资源，但这两种上行资源对应的可用带宽、产生/受到的干扰等都有所不同。对于物理上行控制信道(Physical Uplink Control Channel，PUCCH)传输，可以考虑针对这两种上行资源分别配置匹配其相关特性的参数，比如包括时频位置、码率、功率等，以基于不同上行资源的特性充分利用上行资源，并保障PUCCH传输的性能。
本申请实施例中，Semi-static flexible时域单元指允许灵活双工操作的Semi-static flexible时域单元。对于Semi-static flexible时域单元中是否存在上行子带(UL sub-band)对应的上行资源占用限制(即上行资源必须限制在UL sub-band对应的频域范围内)，可以采用以下任一方式：
频域限制方式1：存在限制，在Semi-static flexible时域单元中，仅UL sub-band对应的频域范围作为可用上行资源。
频域限制方式2：不存在限制，在Semi-static flexible时域单元中，上行带宽部分(Bandwidth Part，BWP)对应的频域范围(即不局限于UL sub-band对应的频域范围)都可作为可用上行资源。
对于同步信号块(Synchronization Signal and PBCH block，SSB)时域单元，既不能被配置为Semi-static UL时域单元，也不能被时隙格式指示(Slot Format Indicator，SFI)指示为Dynamic UL时域单元。这里的时域单元可以理解为符号，SSB时域单元比如为SSB symbol。此外，终端不发送与SSB时域单元存在交叠的上行传输，该上行传输可以包括以下至少之一：物理上行共享信道(Physical Uplink Shared Channel，PUSCH)传输、物理上行控制信道(Physical Uplink Control Channel，PUCCH)传输、物理随机接入信道(Physical Random Access Channel，PRACH)传输、探测参考信号(Sounding Reference Signal，SRS)传输等。比如，对于PUSCH/PUCCH/PRACH传输，当其与至少一个SSB时域单元存在交叠时，终端不发送此PUSCH/PUCCH/PRACH传输；对于SRS传输，当其与至少一个SSB时域单元存在交叠时，终端在发生交叠的SSB时域单元内不发送SRS传输。
在前述灵活双工方式下，是否可在SSB时域单元内允许灵活双工操作，或者允许上行传输，可以采用以下任一方式：
SSB碰撞限制方式1：保持上述上行传输限制，即在SSB时域单元内不允许灵活双工操作，并且终端不发送与SSB时域单元存在交叠的PUSCH/PUCCH/PRACH/SRS传输。
可选地，如果PUSCH/PUCCH/PRACH/SRS传输与SSB时域单元不存在交叠，但是一个SSB时域单元集合的最后一个时域单元与PUSCH/PUCCH/PRACH/SRS传输的第一个时域单元之间的间隔小于下行到上行转换时间(简称下上行转换时间)，或者，PUSCH/PUCCH/PRACH/SRS传输的最后一个时域单元到一个SSB时域单元集合的第一个时域单元之间的间隔小于上行到下行转换时间(简称上下行转换时间)，则终端不发送此 PUSCH/PUCCH/PRACH/SRS传输。该SSB时域单元集合可以由一到多个时域连续的SSB时域单元构成。
SSB碰撞限制方式2：解除或部分解除上述上行传输限制，即在SSB时域单元内允许灵活双工操作，并且当SSB时域单元内配置灵活双工操作时，允许终端在满足预定义条件时，发送与SSB时域单元存在交叠的PUSCH/PUCCH/PRACH/SRS传输，或者，发送与SSB时域单元不存在交叠，但最后一个时域单元与一个SSB时域单元集合的第一个时域单元之间的间隔小于上下行转换时间的PUSCH/PUCCH/PRACH/SRS传输，或者，发送与SSB时域单元不存在交叠，但第一个时域单元与一个SSB时域单元集合的最后一个时域单元之间的间隔小于下上行转换时间的PUSCH/PUCCH/PRACH/SRS传输。
可选地，上述的预定义条件可以包含以下至少一项：
1)PUSCH/PUCCH/PRACH/SRS传输占用的频域资源与SSB频域资源不存在交叠；
2)PUSCH/PUCCH/PRACH/SRS传输占用的频域资源限制在SSB时域单元内配置存在的UL sub-band的频域范围内；
3)PUSCH/PUCCH/PRACH/SRS传输是根据动态信令调度的传输；
4)PUSCH/PUCCH传输的优先级为高优先级，比如被配置或指示为1。
可选地，当SSB在Semi-static UL时域单元，或者由下行控制信息(Downlink Control Information，DCI)(例如DCI format 2_0)指示的动态(Dynamic)UL时域单元内传输时，对于SSB传输所在的时域单元，也可采用上述的SSB碰撞限制方式2。
下面结合附图，通过一些实施例及其应用场景对本申请实施例提供的信息配置方法、装置、终端、网络侧设备及可读存储介质进行详细地说明。
请参见图3，图3是本申请实施例提供的一种信息配置方法的流程图，该方法应用于终端，如图3所示，该方法包括如下步骤：
步骤31：终端从网络侧设备接收第一配置信息。
本实施例中，在第一配置信息中，针对单个PUCCH资源(如PUCCH Resource)配置最多M套配置信息，每套配置信息与满足特定要求的时域单元对应；或者，第一配置信息包括最多N项PUCCH配置(如PUCCH Config)，每项PUCCH配置与满足特定要求的时域单元对应；所述M为大于1的整数，所述N为大于1的整数。
需指出的是，上述的配置信息可以理解为至少包含参数结构PUCCH-Resource中的相关配置信息中的一到多项，包括时域资源信息(如起始符号索引、占用的符号数等)、频域资源信息(如起始物理资源模块(Physical Resource Block，PRB)索引、占用的PRB数目、是否开启时隙内跳频，以及当开启时隙内跳频时第二跳对应的起始PRB索引等)和码域资源信息(如正交覆盖码(Orthogonal Cover Code，OCC)相关配置等)等。可选地，上述配置信息还可以包括码率、功率等配置信息。
上述PUCCH配置至少可包括针对各个PUCCH Resource的参数配置、针对各个PUCCH资源集(如PUCCH Resource Set)的参数配置、针对各种PUCCH格式(Format) 的参数配置、针对PUCCH传输的功控参数配置、空间关系列表(Spatial Relation Info List)配置等。
本申请实施例的信息配置方法，通过上述的第一配置信息，对于PUCCH传输，可以针对不同上行资源分别配置匹配其相关特性的参数，比如包括时频位置、码率、功率等，从而基于不同上行资源的特性充分利用上行资源，保障PUCCH传输的性能。
可选地，上述满足特定要求的时域单元可以包括第一类时域单元和/或第二类时域单元，所述第一类时域单元为在上行BWP范围内存在可用上行资源的时域单元，所述第二类时域单元为仅在上行子带范围内存在可用上行资源的时域单元。
需说明的是，本申请实施例以涉及两类时域单元(即第一类时域单元和第二类时域单元)为例进行描述，但这些描述可以根据需要进一步推广到大于两类时域单元的情况。此时可相应地调整为：第A类时域单元。本申请实施例中下述的其它类别时域单元为除预定义类别时域单元/指定类别时域单元之外的所有其它类别的时域单元，或者，除预定义类别时域单元/指定类别时域单元之外的任一类别的时域单元。
可选地，上述的第一类时域单元可以包括以下至少一项：1)Semi-static上行时域单元；2)第一Semi-static灵活时域单元，其中，在第一Semi-static灵活时域单元中，上行BWP对应的频域范围都可作为可用上行资源，即采用上述频域限制方式2；第一Semi-static灵活时域单元为允许灵活双工操作的Semi-static flexible时域单元。
可以理解的是，当采用上述的SSB碰撞限制方式1时，这里的第一Semi-static灵活时域单元不包括SSB时域单元。
可选地，上述的第二类时域单元可以包括以下至少一项：
1)Semi-static下行时域单元，这里的Semi-static下行时域单元可以理解为配置存在UL sub-band的Semi-static DL时域单元；
可以理解的是，当采用上述SSB碰撞限制方式1时，这里的Semi-static DL时域单元不包括SSB时域单元。
2)第二Semi-static灵活时域单元，其中，在第二Semi-static灵活时域单元中，仅上行子带对应的频域范围可作为可用上行资源，即采用上述频域限制方式1；第二Semi-static灵活时域单元为允许灵活双工操作的Semi-static flexible时域单元。
可以理解的是，当采用上述SSB碰撞限制方式1时，这里的第二Semi-static灵活时域单元不包括SSB时域单元。
本申请实施例中，对于第一配置信息，可采用不同配置方式，说明如下。
配置方式一
此配置方式下，在第一配置信息中，针对单个PUCCH资源配置最多M套配置信息。比如，每个BWP对应单项PUCCH配置，或者，每个BWP的每种物理层优先级(PHY priority)对应单项PUCCH配置，为此PUCCH配置中的单个PUCCH Resource配置最多M套配置信息，每套配置信息对应或者应用于满足特定要求的时域单元。
可选地，网络侧设备可为单个PUCCH资源配置单套配置信息或两套配置信息。如果针对单个PUCCH资源配置两套配置信息，所述两套配置信息包括第一套配置信息和第二套配置信息，则：第一套配置信息对应第一类时域单元，第二套配置信息对应第二类时域单元；或者，第一套配置信息对应第二类时域单元，第二套配置信息对应第一类时域单元。而如果针对单个PUCCH资源仅配置单套配置信息，例如仅配置第一套配置信息或第二套配置信息，则：所述单套配置信息对应第一类时域单元或者第二类时域单元。为不同的PUCCH资源配置的配置信息套数可以相同，也可以不同。当为大于一个PUCCH资源中的每一个PUCCH资源都仅配置了单套配置信息时，这些PUCCH资源可以都仅配置了第一套配置信息或第二套配置信息，或者，其中至少一个PUCCH资源仅配置了第一套配置信息，其它的PUCCH资源仅配置了第二套配置信息。
基于为单个PUCCH资源配置的配置信息，可以区分如下情况进行相应处理。
情况1：针对单个PUCCH资源仅配置单套配置信息，比如仅配置第一套配置信息或第二套配置信息。
此情况下，此配置的单套配置信息可默认对应或者应用于预定义类别时域单元。例如，当仅配置第一套配置信息时，预定义类别时域单元可以为第一类时域单元；当仅配置第二套配置信息时，预定义类别时域单元可以为第二类时域单元。可选地，当仅配置单套配置信息时，预定义类别时域单元总是为第一类时域单元或第二类时域单元，可以由协议规定或由高层信令配置等。假设当预定义类别时域单元为第一类时域单元时，其它类别时域单元为第二类时域单元；当预定义类别时域单元为第二类时域单元时，其它类别时域单元为第一类时域单元。
可选地，此情况下，终端可以采用如下任一方式确定不可用资源或者不可用传输：
(1)当第一PUCCH资源未配置重复(Repetition)传输时，如果基于第二配置信息，第一PUCCH资源与其它类别时域单元存在交叠，则终端可执行以下之一：
-确定第一PUCCH资源非法或者不可用；此时，终端不发起对应的PUCCH传输，其它类别时域单元都作为非法时域单元；
-在至少一个交叠的其它类别时域单元内不满足第一预定义条件时，确定第一PUCCH资源非法或者不可用；此时，其它类别时域单元在满足第一预定义条件时作为合法时域单元，否则作为非法时域单元。
(2)当第一PUCCH资源配置了重复(Repetition)传输时，如果基于第二配置信息，第一PUCCH资源的第一重复传输(如某个Repetition时域位置)与其它类别时域单元存在交叠，所述第一重复传输为第一PUCCH资源的任一个重复传输，则终端可执行以下之一：
-确定第一重复传输非法/不可用；此时，其它类别时域单元都作为非法时域单元，可沿用预定义延迟(Deferral)机制，确定下一个可用的重复传输，即确定下一个可用PUCCH Repetition时域位置；
-在至少一个交叠的其它类别时域单元内不满足第一预定义条件时，确定第一重复传输非法/不可用；此时，其它类别时域单元在满足第一预定义条件时作为合法时域单元，否则作为非法时域单元；可沿用预定义Deferral机制，确定下一个可用的重复传输，即确定下一个可用PUCCH Repetition时域位置。
其中，上述的第二配置信息是为第一PUCCH资源配置的单套配置信息。所述第二配置信息对应的时域单元的类别，与所述其它类别时域单元的类别不同。比如，所述第二配置信息对应的时域单元为第一类时域单元，所述其它类别时域单元为第二类时域单元；或者，所述第二配置信息对应的时域单元为第二类时域单元，所述其它类别时域单元为第一类时域单元。
上述预定义Deferral机制为，当某个PUCCH资源配置了重复传输时，假设期望的重复传输次数为B，则对于此PUCCH资源的第b次重复传输(b为1～B之间的正整数，从取值1开始，并且在此PUCCH资源对应的传输过程中基于步长1逐渐递增)，如果在某个PUCCH时隙内，基于PUCCH资源应用的配置信息确定的重复传输与至少一个Semi-static DL时域单元(即由高层信令TDD-UL-DL-ConfigCommon和/或TDD-UL-DL-ConfigDedicated配置为下行的时域单元；不考虑在时域单元内是否配置存在上行子带)和/或SSB时域单元存在交叠(即此重复传输占用的时域单元中至少一个为Semi-static DL时域单元和/或SSB时域单元)，则忽略此PUCCH时隙内的此重复传输，并且在此PUCCH时隙的下一个PUCCH时隙内继续基于PUCCH资源应用的配置信息确定重复传输并判断与Semi-static DL时域单元和/或SSB时域单元的交叠情况；如此循环执行，直至在一个PUCCH时隙内确定的重复传输与Semi-static DL时域单元和/或SSB时域单元不存在交叠时，将此PUCCH时隙内确定的重复传输确定为此PUCCH资源的第b次重复传输。在确定此PUCCH资源的第b次重复传输后：当b<B时，将b的取值加1，并基于上述操作步骤继续确定此PUCCH资源的第b次重复传输；当b＝B时，已确定此PUCCH资源的所有B次重复传输，因此此PUCCH资源的传输操作结束。
需要注意的是，上述(1)中存在交叠可理解为第一PUCCH资源占用的时域单元中的至少一个时域单元为其它类别时域单元。第一PUCCH资源与除了本申请中第一类/第二类时域单元之外的时域单元的碰撞处理，可采用预定义方法，例如，如果第一PUCCH资源对应的PUCCH传输与至少一个Semi-static DL时域单元(即由高层信令TDD-UL-DL-ConfigCommon和/或TDD-UL-DL-ConfigDedicated配置为下行的时域单元；不考虑在时域单元内是否配置存在上行子带)和/或SSB时域单元存在交叠(即此PUCCH传输占用的时域单元中至少一个为Semi-static DL时域单元和/或SSB时域单元)，则确定第一PUCCH资源非法或者不可用。上述(2)中存在交叠可理解为第一重复传输占用的时域单元中的至少一个时域单元为其它类别时域单元。第一重复传输与除了本申请中第一类/第二类时域单元之外的时域单元的碰撞处理，可采用预定义方法，如上所述。这里，上述的之外的时域单元可以包括：未配置存在UL sub-band的Semi-static DL时域单元， 和/或，不允许灵活双工操作的Semi-static flexible时域单元等。
可选地，对于动态指示的第一PUCCH资源(即由DCI指示与此第一PUCCH资源对应的PUCCH传输)，当使用第三配置信息确定所述第一PUCCH资源对应的PUCCH传输时，终端不期望第一PUCCH资源(此对应未配置重复传输)或者第一PUCCH资源的第二重复传输(此对应配置重复传输)与其它类别时域单元存在交叠；或者，在第一PUCCH资源(此对应未配置重复传输)或者第一PUCCH资源的第二重复传输(此对应配置重复传输)与其它类别时域单元存在交叠时，终端不期望在至少一个交叠的其它类别时域单元内不满足第一预定义条件。其中，所述第三配置信息是为所述第一PUCCH资源配置的单套配置信息，所述第二重复传输为第一PUCCH资源的任一个重复传输。所述第三配置信息对应的时域单元的类别，与所述其它类别时域单元的类别不同，比如：所述第三配置信息对应的时域单元为第一类时域单元，所述其它类别时域单元为第二类时域单元；或者，所述第三配置信息对应的时域单元为第二类时域单元，所述其它类别时域单元为第一类时域单元。
可选地，上述的第一预定义条件可以包括以下至少一项：
其它类别时域单元为所述第一类时域单元；
当其它类别时域单元为第二类时域单元时，第一PUCCH资源(此对应未配置重复传输)或者第一PUCCH资源的重复传输(此对应配置重复传输)在交叠的其它类别时域单元内占用的任一资源单元(Resource Element，RE)，都位于上行子带对应的频域范围内。
情况2：针对单个PUCCH资源配置两套配置信息，比如配置第一套配置信息和第二套配置信息。
此情况下，对于单个PUCCH资源，终端可以根据以下至少一项，从配置的两套配置信息中确定应用的配置信息：
1)所述单个PUCCH资源(此对应未配置重复传输)所在时域单元的类别，或者，所述单个PUCCH资源的重复传输(此对应配置重复传输)所在时域单元的类别。即，基于单个PUCCH资源(此对应未配置重复传输)或单个PUCCH资源的重复传输(此对应配置重复传输)所在时域单元的类别确定应用的配置信息。
比如，当某PUCCH资源(此对应未配置重复传输)或PUCCH资源的重复传输(此对应配置重复传输)所在时域单元为第一类时域单元时，应用为此PUCCH资源配置的第一套配置信息；当某PUCCH资源(此对应未配置重复传输)或PUCCH资源的重复传输(此对应配置重复传输)所在时域单元为第二类时域单元时，应用为此PUCCH资源配置的第二套配置信息。可选地，时域单元类别与配置信息之间的映射关系可以由协议规定或由高层信令配置等。
可选地，当根据PUCCH资源的重复传输所在时域单元的类别确定应用的配置信息时，所述PUCCH资源的各个重复传输可满足以下至少一项，以保证当采用极性编码(Polar coding)时的重复合并操作：
包含的RE数目一致；
包含的用于承载上行控制信息(Uplink Control Information，UCI)的RE数目一致，即不考虑用于承载解调参考信号(Demodulation Reference Signals，DM-RS)的RE；
占用的时域单元数目一致。
需指出的是，上述各个重复传输比如为各个实际的重复传输。上述各个重复传输都与相应PUCCH资源对应。
可选地，为了保证当采用极性编码(Polar coding)时的重复合并操作，对于配置了重复传输的PUCCH资源，终端可根据以下至少一项，从配置的两套配置信息中确定应用的配置信息：
所述PUCCH资源的名义时域单元的类别；
所述PUCCH资源的第一个实际发起的重复传输所在时域单元的类别。
需指出的是，对于配置了重复传输的PUCCH资源，可以理解为：此PUCCH资源对应的PUCCH格式(Format)配置了对应的参数，如时隙数量nrofSlots，且取值大于1，和/或，为此PUCCH资源配置了动态重复因子，且取值大于1。对于PUCCH资源的名义时域单元，可以理解为：基于高层信令配置或DCI指示，此PUCCH资源对应的PUCCH传输所在的时域单元(未配置Repetition传输)，或者此PUCCH资源对应的PUCCH传输的起始时域单元(配置了Repetition传输)。这里的时域单元可以为时隙(slot)或子时隙(sub-slot)等。
考虑到在PUCCH传输的名义时域单元内，PUCCH重复传输可能因为UCI复用处理或者优先级处理(multiplexing/prioritization)规则被丢弃(drop)，或者因为与非法时域单元碰撞而被推迟传输(postpone)，故可以根据PUCCH资源的第一个实际发起的重复传输所在时域单元的类别，确定应用的配置信息。在针对PUCCH传输确定应用的配置信息之后，此PUCCH传输的后续重复传输(Repetition)都应用此确定的配置信息。
2)第一高层信令，即由高层信令配置应用的配置信息。
此2)中，可以在配置使用PUCCH资源的高层信令中，配置应用此PUCCH资源的哪套配置信息。
例如，对于半持续调度(Semi-Persistent Scheduling，SPS)混合自动重传请求应答(Hybrid Automatic Repeat reQuest Acknowledgement，HARQ-ACK)，可以针对终端统一配置，或在SPS-Config中使用额外的参数指示SPS-Config中的n1PUCCH-AN参数对应的PUCCH Resource应用的配置信息；或者，针对终端或各个PUCCH小区(cell)或各个PUCCH BWP(即某个PUCCH cell上的某个UL BWP，此UL BWP可对应一到多项PUCCH Config)统一配置，或在高层参数PUCCH-Config中的sps-PUCCH-AN-List-r16中使用额外的参数统一指示列表中各个PUCCH Resource应用的配置信息，或，在PUCCH-Config中的sps-PUCCH-AN-List-r16的每个列表记录中使用额外的参数各自指示此列表记录字段sps-PUCCH-AN-ResourceID-r16对应的PUCCH Resource应用的配置信息。
对于调度请求(Scheduling Request，SR)PUCCH传输，可以针对终端或各个PUCCH cell或各个PUCCH BWP或各项PUCCH Config统一配置应用的配置信息，或者，在高层参数SchedulingRequestResourceConfig中使用额外的参数指示SchedulingRequestResourceConfig中的resource参数对应的PUCCH Resource应用的配置信息。
对于信道状态信息(Channel State Information，CSI)PUCCH传输，比如周期性CSI(Periodic CSI)，可以针对终端或各个PUCCH cell统一配置应用的配置信息，或者，在高层参数CSI-ReportConfig中的reportConfigType中的periodic中的pucch-CSI-ResourceList中使用额外的参数统一指示PUCCH cell上配置了PUCCH Resource的各个PUCCH BWP对应的PUCCH Resource应用的配置信息，或者，在高层参数CSI-ReportConfig中的reportConfigType中的periodic中的pucch-CSI-ResourceList的每个列表记录(对应PUCCH cell的单个PUCCH BWP，由字段uplinkBandwidthPartId指示)中使用额外的参数各自指示此列表记录字段pucch-Resource对应的PUCCH Resource应用的配置信息。
对于CSI PUCCH传输，比如半持续CSI(Semi-persistent CSI)，可以针对终端或各个PUCCH cell统一配置应用的配置信息，或者，在高层参数CSI-ReportConfig中的reportConfigType中的semiPersistentOnPUCCH中的pucch-CSI-ResourceList中使用额外的参数统一指示PUCCH cell上配置了PUCCH Resource的各个PUCCH BWP对应的PUCCH Resource应用的配置信息，或者，在高层参数CSI-ReportConfig中的reportConfigType中的semiPersistentOnPUCCH中的pucch-CSI-ResourceList的每个列表记录(对应PUCCH cell的单个PUCCH BWP，由字段uplinkBandwidthPartId指示)中使用额外的参数各自指示此列表记录字段pucch-Resource对应的PUCCH Resource应用的配置信息。
3)第一DCI，即基于DCI确定应用的配置信息。
此3)中，可以基于下行动态调度DCI和/或SPS激活DCI，确定具体应用PUCCH资源的哪一套配置信息。
可选地，在基于第一DCI确定应用的配置信息时，可以隐式确定或显示指示应用的配置信息，可以采用以下任一项：
①隐式确定应用的配置信息
具体地，所述应用的配置信息与第一DCI指示的PUCCH传输所在时域单元的类别对应。此可理解为基于PUCCH传输的名义时域单元(由DCI指示)确定应用的配置信息的一种特殊情况。比如，若在第一DCI中指示承载HARQ-ACK反馈的PUCCH传输所在或起始时域单元，以及此PUCCH传输对应的PUCCH资源，则针对此PUCCH资源，应用与PUCCH传输所在或起始时域单元的类别对应的配置信息。
②显式指示应用的配置信息
具体地，可以由第一DCI中的指示域显式指示具体应用PUCCH资源的哪一套配置信息。所述应用的配置信息可以满足以下任一项：
由第一DCI中的第一指示域指示，即由第一DCI中独立的指示域来指示应用的配置信息。比如，第一DCI中的第一指示域可以由高层信令配置其是否存在，当不存在时，应用默认配置信息(例如第一套配置信息)，当存在时，对应的比特数可以为ceiling(log2(M))，ceiling表示向上取整操作，比如当M＝2时为1比特。
由第一DCI中的第二指示域联合指示PUCCH资源指示PRI和应用的配置信息；其中，联合指示域占用的比特数相对于PRI指示域所占用的比特数可根据需要进行扩充；
由第一DCI中的第三指示域联合指示K1和应用的配置信息；其中，联合指示域占用的比特数相对于K1指示域所占用的比特数可根据需要进行扩充。
需指出的，对于上述2)和3)，终端针对PUCCH资源总是使用配置/指示的配置信息。
假设配置/指示的单套配置信息对应/应用于指定类别时域单元，例如当配置/指示应用第一套配置信息时，指定类别时域单元为第一类时域单元，当配置/指示应用第二套配置信息时，指定类别时域单元为第二类时域单元。可选地，时域单元类别与配置信息之间的映射关系可以由协议规定或高层信令配置等。假设当指定类别时域单元为第一类时域单元时，其它类别时域单元为第二类时域单元；当指定类别时域单元为第二类时域单元时，其它类别时域单元为第一类时域单元。
可选地，在单个PUCCH资源配置两套配置信息的情况下，终端可以采用如下任一方式确定不可用资源/不可用传输：
(1)当第一PUCCH资源未配置重复(Repetition)传输时，如果基于第二配置信息，第一PUCCH资源与其它类别时域单元存在交叠，则终端可执行以下之一：
-确定第一PUCCH资源非法/不可用；此时，终端不发起对应的PUCCH传输，其它类别时域单元都作为非法时域单元；
-在至少一个交叠的其它类别时域单元内不满足第一预定义条件时，确定第一PUCCH资源非法/不可用；此时，其它类别时域单元在满足第一预定义条件时作为合法时域单元，否则作为非法时域单元。
(2)当第一PUCCH资源配置了重复(Repetition)传输时，如果基于第二配置信息，第一PUCCH资源的第一重复传输(如某个Repetition时域位置)与其它类别时域单元存在交叠，所述第一重复传输为第一PUCCH资源的任一个重复传输，则终端可执行以下之一：
-确定第一重复传输非法/不可用；此时，其它类别时域单元都作为非法时域单元，可沿用现有延迟(Deferral)机制，确定下一个可用的重复传输，即确定下一个可用PUCCH Repetition时域位置；
-在至少一个交叠的其它类别时域单元内不满足第一预定义条件时，确定第一重复传输非法/不可用；此时，其它类别时域单元在满足第一预定义条件时作为合法时域单元，否则作为非法时域单元；可沿用预定义Deferral机制，如上所述，确定下一个可用的重复 传输，即确定下一个可用PUCCH Repetition时域位置。
其中，上述的第二配置信息是从为第一PUCCH资源配置的两套配置信息中确定的一套配置信息。比如，可以采用上述1)、2)和3)中任一种来确定该一套配置信息。可选地，这里采用上述1)，可以理解为对于配置了重复传输的PUCCH资源，终端从配置的两套配置信息中确定应用的配置信息。所述第二配置信息对应的时域单元的类别，与所述其它类别时域单元的类别不同。比如，所述第二配置信息对应的时域单元为第一类时域单元，所述其它类别时域单元为第二类时域单元；或者，所述第二配置信息对应的时域单元为第二类时域单元，所述其它类别时域单元为第一类时域单元。
需要注意的是，上述(1)中存在交叠可理解为第一PUCCH资源占用的时域单元中的至少一个时域单元为其它类别时域单元。第一PUCCH资源与除了本申请中第一类/第二类时域单元之外的时域单元的碰撞处理，可采用预定义方法，参见前述描述。上述(2)中存在交叠可理解为第一重复传输占用的时域单元中的至少一个时域单元为其它类别时域单元。第一重复传输与除了本申请中第一类/第二类时域单元之外的时域单元的碰撞处理，可采用预定义方法，参见前述描述。这里，上述的之外的时域单元可以包括：未配置存在UL sub-band的Semi-static DL时域单元，和/或，不允许灵活双工操作的Semi-static flexible时域单元等。
例如，在使用某个PUCCH Resource(假设其支持Repetition)的SPS-Config/SchedulingRequestResourceConfig/CSI-ReportConfig中配置使用此PUCCH Resource的第二套配置信息(对应第二类时域单元)时，假设此PUCCH Resource的第n个PUCCH repetition在第二类时域单元内实际传输，如果下一个候选Candidate PUCCH repetition与第一类时域单元存在交叠(假设此PUCCH Resource的重复传输次数还没有达到预定义门限)，则视为与非法时域单元存在冲突，基于预定义Deferral机制需要执行postpone操作，即从下一个时隙开始继续判断此时隙内的候选Candidate PUCCH repetition是否与非法时域单元存在冲突。当找到的Candidate PUCCH repetition占用的各个Symbol都为第二类时域单元时，此Candidate PUCCH repetition才可实际进行传输。
又例如，在使用某个PUCCH Resource(假设其支持Repetition)的SPS-Config/SchedulingRequestResourceConfig/CSI-ReportConfig中配置使用此PUCCH Resource的第一套配置信息(对应第一类时域单元)时，假设此PUCCH Resource的第n个PUCCH repetition在第一类时域单元内实际传输，如果下一个Candidate PUCCH repetition与第二类时域单元存在交叠(假设此PUCCH Resource的重复传输次数还没有达到预定义门限)，则当满足第一预定义条件时，此Candidate PUCCH repetition可实际传输，否则继续执行postpone操作。
可选地，当某个Candidate PUCCH repetition与非法时域单元存在冲突时，也可以不基于预定义Deferral机制执行postpone操作，而是直接drop。当遍历的Candidate PUCCH repetition达到预定义门限时，本次PUCCH传输结束。
可以理解的是，所述(1)和/或(2)中，对于是否采用第一预定义条件确定不可用资源/传输，可以由协议规定，也可以针对终端或各个PUCCH cell或各个PUCCH BWP或各项PUCCH Config统一配置，或者针对各个SPS-Config/SchedulingRequestResourceConfig/CSI-ReportConfig等功能配置项独立配置。
可选地，当使用第三配置信息确定第一PUCCH资源对应的PUCCH传输时，所述终端不期望所述第一PUCCH资源(此对应未配置重复传输)或者所述第一PUCCH资源的任意重复传输(此对应配置了重复传输)与其它类别时域单元存在交叠；或者，在所述第一PUCCH资源(此对应未配置重复传输)或者所述第一PUCCH资源的第三重复传输(此对应配置了重复传输)与其它类别时域单元存在交叠时，所述终端不期望在至少一个交叠的其它类别时域单元内不满足第一预定义条件。其中，所述第三配置信息是从为所述第一PUCCH资源配置的两套配置信息中确定的一套配置信息，且所述第三配置信息基于配置或指示确定，比如可采用上述2)或3)中方式确定该一套配置信息。所述第三重复传输为第一PUCCH资源的任一个重复传输。所述第三配置信息对应的时域单元的类别，与所述其它类别时域单元的类别不同。比如，所述第三配置信息对应的时域单元为第一类时域单元，所述其它类别时域单元为第二类时域单元；或者，所述第三配置信息对应的时域单元为第二类时域单元，所述其它类别时域单元为第一类时域单元。
可选地，上述的第一预定义条件可以包括以下至少一项：
其它类别时域单元为所述第一类时域单元；
当其它类别时域单元为第二类时域单元时，第一PUCCH资源(此对应未配置重复传输)或者第一PUCCH资源的重复传输(此对应配置了重复传输)在交叠的其它类别时域单元内占用的任一资源单元RE，都位于上行子带对应的频域范围内。
配置方式二
此配置方式下，第一配置信息包括最多N项PUCCH配置。比如，每个BWP对应最多N项PUCCH配置，或者，每个BWP的每种物理层优先级(PHY priority)对应最多N项PUCCH配置，每项PUCCH配置对应/应用于满足特定要求的时域单元。
可选地，如果第一配置信息包括两项PUCCH配置，所述两项PUCCH配置包括第一项PUCCH配置和第二项PUCCH配置，则：第一项PUCCH配置对应第一类时域单元，第二项PUCCH配置对应第二类时域单元；或者，第一项PUCCH配置对应第二类时域单元，第二项PUCCH配置对应第一类时域单元。需要注意的是，为每个BWP配置单项PUCCH Config，或者，为每个BWP的每种PHY priority配置单项PUCCH Config时，此配置的单项PUCCH Config仅应用于第一类时域单元，或者，同时应用于第一类时域单元和第二类时域单元。
可选地，如果第一配置信息包括两项PUCCH配置，终端可以根据以下至少一项，从配置的两项PUCCH配置中确定应用的PUCCH配置：
Ⅰ)PUCCH传输的名义时域单元的类别。即，基于PUCCH传输的名义时域单元的 类别确定应用的PUCCH配置。
这里的PUCCH传输的名义时域单元，可以理解为，基于高层信令配置或DCI指示的PUCCH传输(此对应未配置重复传输)或者PUCCH起始传输所在的时域单元(此对应配置重复传输)所在的时域单元。
例如，对于动态调度(Dynamic Scheduling，DG)HARQ-ACK，可以基于下行调度DCI中指示的K1，以及物理下行共享信道(Physical Downlink Shared Channel，PDSCH)传输所在的时域单元，确定承载DG HARQ-ACK的PUCCH传输的名义时域单元。
对于SPS HARQ-ACK，可以基于SPS激活DCI中指示的K1，以及SPS PDSCH传输的时域单元，确定承载SPS HARQ-ACK的PUCCH传输的名义时域单元。
对于SR PUCCH传输，可以基于高层参数SchedulingRequestResourceConfig中的periodicityAndOffset，确定承载SR的PUCCH传输的名义时域单元。
对于CSI PUCCH传输，比如对于PUCCH上的Periodic CSI，可以基于CSI-ReportConfig中的reportConfigType中的periodic中的reportSlotConfig参数确定承载CSI的PUCCH传输的名义时域单元，或者，对于PUCCH上的Semi-persistent CSI，可以基于CSI-ReportConfig中的reportConfigType中的semiPersistentOnPUCCH中的reportSlotConfig参数确定承载CSI的PUCCH传输的名义时域单元。
又例如，当PUCCH传输的名义时域单元属于第一类时域单元时，应用为当前BWP配置的第一项PUCCH Config，或者，应用为当前BWP与此PUCCH传输对应的PHY priority配置的第一项PUCCH Config；当PUCCH传输的名义时域单元属于第二类时域单元时，应用为当前BWP配置的第二项PUCCH Config，或者，应用为当前BWP与此PUCCH传输对应的PHY priority配置的第二项PUCCH Config。可选地，时域单元类别与PUCCH Config之间的映射关系可以由协议规定或由高层信令配置等。这里的当前BWP可以理解为PUCCH传输所在或者对应的BWP，与此PUCCH传输对应的PHY priority可以由高层信令配置或者由DCI指示。
可选地，对于周期性传输或半持续传输的半静态UCI，其在不同的传输周期对应的PUCCH传输的名义时域单元可能属于第一类时域单元或第二类时域单元，因此需要分别使用第一项PUCCH Config和第二项PUCCH Config中配置的PUCCH Resource。
可选地，当根据PUCCH传输的名义时域单元的类别确定应用的PUCCH配置时，对于半静态UCI在第一项PUCCH配置和第二项PUCCH配置中使用的PUCCH资源的标识的配置，可以满足以下任一项：
ⅰ)仅配置在第一项PUCCH配置中使用的PUCCH资源的第一标识，在第二项PUCCH配置中使用的PUCCH资源的标识基于第一标识确定；或者，仅配置在第二项PUCCH配置中使用的PUCCH资源的第二标识，在第一项PUCCH配置中使用的PUCCH资源的标识基于第二标识确定；即，仅配置在某项PUCCH配置中使用的PUCCH资源的ID，在另一项PUCCH配置中使用的PUCCH资源的ID基于前述配置ID进行推导。
一种最简单的方式为，保持现有参数配置结构不变，现有参数配置结构中配置的PUCCH Resource ID同时适用于两项PUCCH Config，即此半静态UCI在第一项PUCCH Config和第二项PUCCH Config中使用的PUCCH Resource的ID一致。
另一种可选的方式为：引入一个标识偏移(ID Offset)。假设现有参数配置结构中配置的PUCCH Resource ID适用于第一项或第二项PUCCH Config(即指示此PUCCH Config中与此配置ID对应的PUCCH Resource用于此半静态UCI的传输)，则在另一项PUCCH Config中使用的PUCCH Resource的ID＝配置ID+ID Offset。这里的ID Offset(例如取值为0、1等非负整数)可以由协议规定或由高层信令配置。
ⅱ)分别配置在第一项PUCCH配置和第二项PUCCH配置中使用的PUCCH资源的标识。
例如，对于SPS HARQ-ACK，可在参数SPS-Config中分别指示第一项PUCCH Config和第二项PUCCH Config中对应的PUCCH Resource的ID。例如，现有参数SPS-Config中的n1PUCCH-AN对应第一项PUCCH Config中对应的PUCCH Resource的ID，在SPS-Config中引入额外的参数指示第二项PUCCH Config中对应的PUCCH Resource的ID。需要注意的是，参数PUCCH-Config中的sps-PUCCH-AN-List-r16在第一项PUCCH Config和第二项PUCCH Config中分别配置，无需额外增强。
对于SR PUCCH传输，参数SchedulingRequestResourceConfig可以在第一项PUCCH Config和第二项PUCCH Config中分别配置，只需将这两项SchedulingRequestResourceConfig的参数schedulingRequestID设置为相同取值即可，即关联至同一SR Config ID。
对于CSI PUCCH传输，比如PUCCH上的Periodic CSI，可在参数CSI-ReportConfig中的reportConfigType中的periodic中分别配置第一项PUCCH Config和第二项PUCCH Config对应的PUCCH Resource列表，例如，现有参数CSI-ReportConfig中的reportConfigType中的periodic中的pucch-CSI-ResourceList对应各PUCCH BWP的第一项PUCCH Config中配置的PUCCH Resource的ID，在CSI-ReportConfig中的reportConfigType中的periodic中引入额外的参数配置各PUCCH BWP的第二项PUCCH Config中配置的PUCCH Resource的ID；或者，在参数CSI-ReportConfig中的reportConfigType中的periodic中的pucch-CSI-ResourceList的每个列表记录(对应PUCCH cell的单个PUCCH BWP，由字段uplinkBandwidthPartId指示)中分别配置第一项PUCCH Config和第二项PUCCH Config对应的PUCCH Resource的ID，例如，列表记录字段pucch-Resource对应于与此列表记录对应的PUCCH BWP的第一项PUCCH Config中配置的PUCCH Resource的ID，在列表记录中引入额外的参数配置与此列表记录对应的PUCCH BWP的第二项PUCCH Config中配置的PUCCH Resource的ID。
对于CSI PUCCH传输，对于PUCCH上的Semi-persistent CSI，可在参数CSI-ReportConfig中的reportConfigType中的semiPersistentOnPUCCH中分别配置第一项 PUCCH Config和第二项PUCCH Config对应的PUCCH Resource列表，例如，现有参数CSI-ReportConfig中的reportConfigType中的semiPersistentOnPUCCH中的pucch-CSI-ResourceList对应各PUCCH BWP的第一项PUCCH Config中配置的PUCCH Resource的ID，在CSI-ReportConfig中的reportConfigType中的semiPersistentOnPUCCH中引入额外的参数配置各PUCCH BWP的第二项PUCCH Config中配置的PUCCH Resource的ID；或者，在参数CSI-ReportConfig中的reportConfigType中的semiPersistentOnPUCCH中的pucch-CSI-ResourceList的每个列表记录(对应PUCCH cell的单个PUCCH BWP，由字段uplinkBandwidthPartId指示)中分别配置第一项PUCCH Config和第二项PUCCH Config对应的PUCCH Resource的ID，例如，列表记录字段pucch-Resource对应于与此列表记录对应的PUCCH BWP的第一项PUCCH Config中配置的PUCCH Resource的ID，在列表记录中引入额外的参数配置与此列表记录对应的PUCCH BWP的第二项PUCCH Config中配置的PUCCH Resource的ID。
Ⅱ)第二高层信令，即由高层信令配置应用的PUCCH配置。
此Ⅱ)中，可以在配置使用PUCCH Resource的高层信令中，配置使用在哪套PUCCH Config中配置的PUCCH Resource。
例如，对于SPS HARQ-ACK，可以针对终端统一配置，或在SPS-Config中使用额外的参数指示SPS-Config中的n1PUCCH-AN参数对应的PUCCH Resource所在的PUCCH Config，或者指示SPS-Config对应的SPS HARQ-ACK使用哪项PUCCH Config对应的PUCCH-Config中的sps-PUCCH-AN-List-r16参数。PUCCH-Config中的sps-PUCCH-AN-List-r16参数在第一项PUCCH Config和第二项PUCCH Config中分别配置。
对于SR PUCCH传输，参数SchedulingRequestResourceConfig可在第一项PUCCH Config和第二项PUCCH Config中分别配置，通过配置参数SchedulingRequestResourceConfig中的schedulingRequestID，可将某一SR Config ID仅与某个PUCCH cell的某个PUCCH BWP的第一项PUCCH Config或第二项PUCCH Config中配置的SchedulingRequestResourceConfig进行关联。
对于CSI PUCCH传输，比如PUCCH上的Periodic CSI，可以针对终端或各个PUCCH cell统一配置应用的PUCCH Config，或者，在高层参数CSI-ReportConfig中的reportConfigType中的periodic中的pucch-CSI-ResourceList中使用额外的参数统一指示PUCCH cell上配置了PUCCH Resource的各个PUCCH BWP对应的PUCCH Resource所在的PUCCH Config，或者，在CSI-ReportConfig中的reportConfigType中的periodic中的pucch-CSI-ResourceList的每个列表记录(对应PUCCH cell的单个PUCCH BWP，由字段uplinkBandwidthPartId指示)中使用额外的参数各自指示此列表记录字段pucch-Resource对应的PUCCH Resource所在的PUCCH Config。
对于CSI PUCCH传输，对于PUCCH上的Semi-persistent CSI，可以针对终端或各个 PUCCH cell统一配置应用的PUCCH Config，或者，在高层参数CSI-ReportConfig中的reportConfigType中的semiPersistentOnPUCCH中的pucch-CSI-ResourceList中使用额外的参数统一指示PUCCH cell上配置了PUCCH Resource的各个PUCCH BWP对应的PUCCH Resource所在的PUCCH Config，或者，在高层参数CSI-ReportConfig中的reportConfigType中的semiPersistentOnPUCCH中的pucch-CSI-ResourceList的每个列表记录(对应PUCCH cell的单个PUCCH BWP，由字段uplinkBandwidthPartId指示)中使用额外的参数各自指示此列表记录字段pucch-Resource对应的PUCCH Resource所在的PUCCH Config。
Ⅲ)第二DCI，即基于DCI确定应用的PUCCH配置。
此Ⅲ)中，可以基于下行动态调度DCI和/或SPS激活DCI，确定使用的PUCCH Resource所在的PUCCH Config。
可选地，在基于第二DCI确定应用的PUCCH配置时，可以隐式确定或显示指示应用的PUCCH配置，可以采用以下任一项：
①隐式确定应用的PUCCH配置
具体地，所述应用的PUCCH配置与第二DCI指示的PUCCH传输所在时域单元的类别对应。比如，若在第二DCI中指示承载HARQ-ACK反馈的PUCCH传输所在时域单元(此对应未配置重复传输)或起始时域单元(此对应配置重复传输)，以及此PUCCH传输对应的PUCCH Resource，则针对此PUCCH Resource，应用与PUCCH传输所在时域单元(此对应未配置重复传输)或起始时域单元(此对应配置重复传输)的类别对应的PUCCH Config。
②显式指示应用的PUCCH配置
具体地，可以由第二DCI中的指示域显式指示使用的PUCCH Resource所在的PUCCH Config。所述应用的PUCCH配置可以满足以下任一项：
由第二DCI中的第四指示域指示，即由第二DCI中独立的指示域来指示所在的PUCCH Config。比如，第二DCI中的第四指示域可以由高层信令配置其是否存在，当不存在时，使用默认PUCCH Config(例如第一项PUCCH Config)，当存在时，对应的比特数可以为ceiling(log2(M))，当M＝2时为1比特；
由第二DCI中的第五指示域联合指示PRI和应用的PUCCH配置；其中，联合指示域占用的比特数相对于PRI指示域所占用的比特数可根据需要进行扩充；
由第二DCI中的第六指示域联合指示K1和应用的PUCCH配置；其中，联合指示域占用的比特数相对于PRI指示域所占用的比特数可根据需要进行扩充。
需指出的，对于上述Ⅱ)和Ⅲ)，终端针对使用的PUCCH Resource总是认为来自配置/指示的PUCCH Config。
假设配置/指示的PUCCH Config对应/应用于指定类别时域单元，例如当配置/指示应用第一项PUCCH Config时，指定类别时域单元为第一类时域单元，当配置/指示应用第二项PUCCH Config时，指定类别时域单元为第二类时域单元。可选地，时域单元类别与 PUCCH Config之间的映射关系可以由协议规定或由高层信令配置等。假设当指定类别时域单元为第一类时域单元时，其它类别时域单元为第二类时域单元；当指定类别时域单元为第二类时域单元时，其它类别时域单元为第一类时域单元。
可选地，在应用的PUCCH配置基于配置或指示确定的情况下，终端可以采用如下任一方式确定不可用的PUCCH资源或者PUCCH传输：
(a)当第二PUCCH资源未配置重复传输时，若基于第四配置信息，第二PUCCH资源与其它类别时域单元存在交叠，则终端可执行以下之一：
-确定第二PUCCH资源非法/不可用；此时，终端不发起对应的PUCCH传输，其它类别时域单元都作为非法时域单元；
-在至少一个交叠的其它类别时域单元内不满足第二预定义条件时，确定第二PUCCH资源非法/不可用；此时，其它类别时域单元在满足第二预定义条件时作为合法时域单元，否则作为非法时域单元。
(b)当第二PUCCH资源配置了重复(Repetition)传输时，若基于第四配置信息，第二PUCCH资源的第四重复传输(如某个Repetition时域位置)与其它类别时域单元存在交叠，所述第四重复传输为第二PUCCH资源的任一个重复传输，则终端可执行以下之一：
确定第四重复传输非法/不可用；此时，其它类别时域单元都作为非法时域单元，可沿用预定义Deferral机制，如上所述，确定下一个可用的重复传输，即确定下一个可用PUCCH Repetition时域位置；
在至少一个交叠的其它类别时域单元内不满足第二预定义条件时，确定第四重复传输非法/不可用；此时，其它类别时域单元在满足第二预定义条件时作为合法时域单元，否则作为非法时域单元；可沿用预定义Deferral机制，如上所述，确定下一个可用的重复传输，即确定下一个可用PUCCH Repetition时域位置。
其中，上述的第二PUCCH资源为应用的PUCCH配置中的单个PUCCH资源，所述第四配置信息为应用的PUCCH配置中，与所述第二PUCCH资源对应的配置信息。所述应用的PUCCH配置对应的时域单元的类别，与所述其它类别时域单元的类别不同。比如，所述应用的PUCCH配置对应的时域单元为第一类时域单元，所述其它类别时域单元为第二类时域单元；或者，所述应用的PUCCH配置对应的时域单元为第二类时域单元，所述其它类别时域单元为第一类时域单元。
需要注意的是，上述(a)中存在交叠可理解为第二PUCCH资源占用的时域单元中的至少一个时域单元为其它类别时域单元。第二PUCCH资源与除了本申请中第一类/第二类时域单元之外的时域单元的碰撞处理，可采用预定义方法，如上所述。上述(b)中存在交叠可理解为第二重复传输占用的时域单元中的至少一个时域单元为其它类别时域单元。第二重复传输与除了本申请中第一类/第二类时域单元之外的时域单元的碰撞处理，可采用预定义方法，如上所述。这里，上述的之外的时域单元可以包括：未配置存在UL  sub-band的Semi-static DL时域单元，和/或，不允许灵活双工操作的Semi-static flexible时域单元等。
可选地，当使用第五配置信息确定第二PUCCH资源对应的PUCCH传输时，终端不期望所述第二PUCCH资源(此对应未配置重复传输)或者所述第二PUCCH资源的任意重复传输(此对应配置了重复传输)与其它类别时域单元存在交叠；或者，在所述第二PUCCH资源(此对应未配置重复传输)或者所述第二PUCCH资源的第五重复传输(此对应配置了重复传输)与其它类别时域单元存在交叠时，终端不期望在至少一个交叠的其它类别时域单元内不满足第二预定义条件；其中，所述第二PUCCH资源为应用的PUCCH配置中的单个PUCCH资源，所述第五配置信息为所述应用的PUCCH配置中，与所述第二PUCCH资源对应的配置信息，所述应用的PUCCH配置基于配置或指示确定，比如可采用上述2)或3)中方式确定。所述第五重复传输为第二PUCCH资源的任一个重复传输。所述应用的PUCCH配置对应的时域单元的类别，与所述其它类别时域单元的类别不同。比如，所述应用的PUCCH配置对应的时域单元为第一类时域单元，所述其它类别时域单元为第二类时域单元；或者，所述应用的PUCCH配置对应的时域单元为第二类时域单元，所述其它类别时域单元为第一类时域单元。
可选地，上述的第二预定义条件可以包括以下至少一项：
其它类别时域单元为所述第一类时域单元；
当其它类别时域单元为第二类时域单元时，第二PUCCH资源(此对应未配置重复传输)或者第二PUCCH资源的重复传输(此对应配置重复传输)在交叠的其它类别时域单元内占用的任一资源单元RE，都位于上行子带对应的频域范围内。
一些实施例中，当SSB传输所在的时域单元内不允许灵活双工操作时，终端不发送与所述SSB传输所在的时域单元存在交叠的上行传输。
另一些实施例中，当SSB传输所在的时域单元内允许灵活双工操作，并且在所述SSB传输所在的时域单元内配置灵活双工操作时，终端在满足第三预定义条件的情况下，发送与所述SSB传输所在的时域单元存在交叠的上行传输。
可选地，上述的第三预定义条件可以包括以下至少一项：
上行传输占用的频域资源与SSB传输占用的频域资源不存在交叠；
上行传输占用的频域资源限制在上行子带的频域范围内，所述上行子带为SSB传输占用的时域单元内配置存在的上行子带；
上行传输是根据动态信令调度的传输；
上行传输的优先级被配置或指示为高优先级。
可选地，上述的上行传输可包括但不限于PUSCH/PUCCH/PRACH/SRS传输。
请参见图4，图4是本申请实施例提供的一种信息配置方法的流程图，该方法应用于网络侧设备，如图4所示，该方法包括如下步骤：
步骤41：网络侧设备向终端发送第一配置信息。
本实施例中，在第一配置信息中，针对单个PUCCH资源(如PUCCH Resource)配置最多M套配置信息，每套配置信息与满足特定要求的时域单元对应；或者，第一配置信息包括最多N项PUCCH配置(如PUCCH Config)，每项PUCCH配置与满足特定要求的时域单元对应；所述M为大于1的整数，所述N为大于1的整数。
这样，对于PUCCH传输，可以针对不同上行资源分别配置匹配其相关特性的参数，比如包括时频位置、码率、功率等，从而基于不同上行资源的特性充分利用上行资源，保障PUCCH传输的性能。
可选地，上述满足特定要求的时域单元可以包括第一类时域单元和/或第二类时域单元，所述第一类时域单元为在上行BWP范围内存在可用上行资源的时域单元，所述第二类时域单元为仅在上行子带范围内存在可用上行资源的时域单元。
可选地，上述的第一类时域单元可以包括以下至少一项：
1)Semi-static上行时域单元；
2)第一Semi-static灵活时域单元，其中，在第一Semi-static灵活时域单元中，上行BWP对应的频域范围都可作为可用上行资源，即采用上述频域限制方式2；第一Semi-static灵活时域单元为允许灵活双工操作的Semi-static flexible时域单元。
可以理解的是，当采用上述的SSB碰撞限制方式1时，这里的第一Semi-static灵活时域单元不包括SSB时域单元。
可选地，上述的第二类时域单元可以包括以下至少一项：
1)Semi-static下行时域单元，这里的Semi-static下行时域单元可以理解为配置存在UL sub-band的Semi-static DL时域单元；
可以理解的是，当采用上述SSB碰撞限制方式1时，这里的Semi-static DL时域单元不包括SSB时域单元。
2)第二Semi-static灵活时域单元，其中，在第二Semi-static灵活时域单元中，仅上行子带对应的频域范围可作为可用上行资源，即采用上述频域限制方式1；第二Semi-static灵活时域单元为允许灵活双工操作的Semi-static flexible时域单元。
可以理解的是，当采用上述SSB碰撞限制方式1时，这里的第二Semi-static灵活时域单元不包括SSB时域单元。
可选地，如果针对单个PUCCH资源仅配置单套配置信息，则：所述单套配置信息对应所述第一类时域单元或者所述第二类时域单元；
或者，如果针对单个PUCCH资源配置两套配置信息，所述两套配置信息包括第一套配置信息和第二套配置信息，则：所述第一套配置信息对应所述第一类时域单元，所述第二套配置信息对应所述第二类时域单元；或者，所述第一套配置信息对应所述第二类时域单元，所述第二套配置信息对应所述第一类时域单元。
可选地，如果针对单个PUCCH资源配置两套配置信息，网络侧设备可以向终端发送第一高层信令和/或第一DCI；其中，所述第一高层信令和/或第一DCI用于所述终端从所 述两套配置信息中确定应用的配置信息。
可选地，所述应用的配置信息满足以下任一项：
与第一DCI指示的PUCCH传输所在时域单元的类别对应；
由第一DCI中的第一指示域指示；
由第一DCI中的第二指示域联合指示PRI和所述应用的配置信息；
由第一DCI中的第三指示域联合指示K1和所述应用的配置信息。
可选地，如果所述第一配置信息包括两项PUCCH配置，所述两项PUCCH配置包括第一项PUCCH配置和第二项PUCCH配置，则：所述第一项PUCCH配置对应所述第一类时域单元，所述第二项PUCCH配置对应所述第二类时域单元；或者，所述第一项PUCCH配置对应所述第二类时域单元，所述第二项PUCCH配置对应所述第一类时域单元。
可选地，网络侧设备可以向终端发送第二高层信令和/或第二DCI；其中，所述第二高层信令和/或第二DCI用于终端从所述两项PUCCH配置中确定应用的PUCCH配置。
可选地，所述应用的PUCCH配置满足以下任一项：
与第二DCI指示的PUCCH传输所在时域单元的类别对应；
由第二DCI中的第四指示域指示；
由第二DCI中的第五指示域联合指示PRI和所述应用的PUCCH配置；
由第二DCI中的第六指示域联合指示K1和所述应用的PUCCH配置。
本申请实施例提供的信息配置方法，执行主体可以为信息配置装置。本申请实施例中以信息配置装置执行信息配置方法为例，说明本申请实施例提供的信息配置装置。
请参见图5，图5是本申请实施例提供的一种信息配置装置的结构示意图，该装置应用于终端，如图5所示，信息配置装置50包括：
接收模块51，用于从网络侧设备接收第一配置信息；
其中，在所述第一配置信息中，针对单个PUCCH资源配置最多M套配置信息，每套配置信息与满足特定要求的时域单元对应；或者，所述第一配置信息包括最多N项PUCCH配置，每项PUCCH配置与满足特定要求的时域单元对应；所述M为大于1的整数，所述N为大于1的整数。
可选地，所述满足特定要求的时域单元包括第一类时域单元和/或第二类时域单元，所述第一类时域单元为在上行BWP范围内存在可用上行资源的任一时域单元，所述第二类时域单元为仅在上行子带范围内存在可用上行资源的任一时域单元。
可选地，所述第一类时域单元包括以下至少一项：
Semi-static上行时域单元；
第一Semi-static灵活时域单元，其中，在所述第一Semi-static灵活时域单元中，上行BWP对应的频域范围都可作为可用上行资源；
和/或，所述第二类时域单元包括以下至少一项：
Semi-static下行时域单元；
第二Semi-static灵活时域单元，其中，在所述第二Semi-static灵活时域单元中，仅上行子带对应的频域范围可作为可用上行资源。
可选地，如果针对单个PUCCH资源仅配置单套配置信息，则：所述单套配置信息对应所述第一类时域单元或者所述第二类时域单元；
或者，如果针对单个PUCCH资源配置两套配置信息，所述两套配置信息包括第一套配置信息和第二套配置信息，则：所述第一套配置信息对应所述第一类时域单元，所述第二套配置信息对应所述第二类时域单元；或者，所述第一套配置信息对应所述第二类时域单元，所述第二套配置信息对应所述第一类时域单元。
可选地，如果针对单个PUCCH资源配置两套配置信息，信息配置装置50还包括：
第一确定模块，用于根据以下至少一项，从所述两套配置信息中确定应用的配置信息：
所述单个PUCCH资源所在时域单元的类别，或者，所述单个PUCCH资源的重复传输所在时域单元的类别；
第一高层信令；
第一下行控制信息DCI。
可选地，当根据所述PUCCH资源的重复传输所在时域单元的类别确定应用的配置信息时，所述PUCCH资源的各个重复传输满足以下至少一项：
包含的RE数目一致；
包含的用于承载上行控制信息UCI的RE数目一致；
占用的时域单元数目一致。
可选地，如果针对单个PUCCH资源配置两套配置信息，对于配置了重复传输的PUCCH资源，所述第一确定模块还用于：根据以下至少一项，从所述两套配置信息中确定应用的配置信息：
所述PUCCH资源的名义时域单元的类别；
所述PUCCH资源的第一个实际发起的重复传输所在时域单元的类别。
可选地，所述应用的配置信息满足以下任一项：
与所述第一DCI指示的PUCCH传输所在时域单元的类别对应；
由所述第一DCI中的第一指示域指示；
由所述第一DCI中的第二指示域联合指示PUCCH资源指示PRI和所述应用的配置信息；
由所述第一DCI中的第三指示域联合指示K1和所述应用的配置信息。
可选地，信息配置装置50还包括：
第一执行模块，用于执行以下任一项：
当第一PUCCH资源未配置重复传输时，在基于第二配置信息，所述第一PUCCH资源与其它类别时域单元存在交叠的情况下，执行以下之一：确定所述第一PUCCH资源不可用、在至少一个交叠的其它类别时域单元内不满足第一预定义条件时确定所述第一 PUCCH资源不可用；
当第一PUCCH资源配置了重复传输时，在基于第二配置信息，所述第一PUCCH资源的第一重复传输与其它类别时域单元存在交叠的情况下，执行以下之一：确定所述第一重复传输不可用、在至少一个交叠的其它类别时域单元内不满足第一预定义条件时确定所述第一重复传输不可用；
其中，所述第二配置信息是为所述第一PUCCH资源配置的单套配置信息，或者，所述第二配置信息是从为所述第一PUCCH资源配置的两套配置信息中确定的一套配置信息；
其中，所述第二配置信息对应的时域单元为所述第一类时域单元，所述其它类别时域单元为所述第二类时域单元；或者，所述第二配置信息对应的时域单元为所述第二类时域单元，所述其它类别时域单元为所述第一类时域单元。
可选地，对于动态指示的第一PUCCH资源，当使用第三配置信息确定所述第一PUCCH资源对应的PUCCH传输时，所述终端不期望所述第一PUCCH资源或者所述第一PUCCH资源的第一个重复传输与其它类别时域单元存在交叠，或者，在所述第一PUCCH资源或者所述第一PUCCH资源的第一个重复传输与其它类别时域单元存在交叠时，所述终端不期望在至少一个交叠的其它类别时域单元内不满足第一预定义条件；
其中，所述第三配置信息是为所述第一PUCCH资源配置的单套配置信息，所述第三配置信息对应的时域单元为所述第一类时域单元，所述其它类别时域单元为所述第二类时域单元；或者，所述第三配置信息对应的时域单元为所述第二类时域单元，所述其它类别时域单元为所述第一类时域单元。
可选地，当使用第三配置信息确定第一PUCCH资源对应的PUCCH传输时，所述终端不期望所述第一PUCCH资源或者所述第一PUCCH资源的任意重复传输与其它类别时域单元存在交叠；或者，在所述第一PUCCH资源或者所述第一PUCCH资源的第三重复传输与其它类别时域单元存在交叠时，所述终端不期望在至少一个交叠的其它类别时域单元内不满足第一预定义条件；其中，所述第三配置信息是从为所述第一PUCCH资源配置的两套配置信息中确定的一套配置信息，且所述第三配置信息基于配置或指示确定；所述第三配置信息对应的时域单元为所述第一类时域单元，所述其它类别时域单元为所述第二类时域单元；或者，所述第三配置信息对应的时域单元为所述第二类时域单元，所述其它类别时域单元为所述第一类时域单元。
可选地，所述第一预定义条件包括以下至少一项：
所述其它类别时域单元为所述第一类时域单元；
当所述其它类别时域单元为所述第二类时域单元时，所述第一PUCCH资源或者所述第一PUCCH资源的重复传输在交叠的其它类别时域单元内占用的任一资源单元RE，都位于上行子带对应的频域范围内。
可选地，如果所述第一配置信息包括两项PUCCH配置，所述两项PUCCH配置包括第一项PUCCH配置和第二项PUCCH配置，则：所述第一项PUCCH配置对应所述第一 类时域单元，所述第二项PUCCH配置对应所述第二类时域单元；或者，所述第一项PUCCH配置对应所述第二类时域单元，所述第二项PUCCH配置对应所述第一类时域单元。
可选地，如果所述第一配置信息包括两项PUCCH配置，信息配置装置50还包括：
第二确定模块，用于根据以下至少一项，从所述两项PUCCH配置中确定应用的PUCCH配置：
PUCCH传输的名义时域单元的类别；
第二高层信令；
第二DCI。
可选地，当根据所述PUCCH传输的名义时域单元的类别确定应用的PUCCH配置时，对于半静态UCI在所述第一项PUCCH配置和所述第二项PUCCH配置中使用的PUCCH资源的标识的配置，满足以下至少一项：
仅配置在所述第一项PUCCH配置中使用的PUCCH资源的第一标识，在所述第二项PUCCH配置中使用的PUCCH资源的标识基于所述第一标识确定；或者，仅配置在所述第二项PUCCH配置中使用的PUCCH资源的第二标识，在所述第一项PUCCH配置中使用的PUCCH资源的标识基于所述第二标识确定；
分别配置在所述第一项PUCCH配置和所述第二项PUCCH配置中使用的PUCCH资源的标识。
可选地，当根据所述第二DCI，从所述两项PUCCH配置中确定应用的PUCCH配置时，所述应用的PUCCH配置满足以下任一项：
与所述第二DCI指示的PUCCH传输所在时域单元的类别对应；
由所述第二DCI中的第四指示域指示；
由所述第二DCI中的第五指示域联合指示PRI和所述应用的PUCCH配置；
由所述第二DCI中的第六指示域联合指示K1和所述应用的PUCCH配置。
可选地，在所述应用的PUCCH配置基于配置或指示确定的情况下，信息配置装置50还包括：
第二执行模块，用于执行以下任一项：
当第二PUCCH资源未配置重复传输时，在基于第四配置信息，所述第二PUCCH资源与其它类别时域单元存在交叠的情况下，执行以下之一：确定所述第二PUCCH资源不可用、在至少一个交叠的其它类别时域单元内不满足第二预定义条件时确定所述第二PUCCH资源不可用；
当第二PUCCH资源配置了重复传输时，在基于第四配置信息，所述第二PUCCH资源的第四重复传输与其它类别时域单元存在交叠的情况下，执行以下之一：确定所述第四重复传输不可用、在至少一个交叠的其它类别时域单元内不满足第二预定义条件时确定所述第四重复传输不可用；
其中，所述第二PUCCH资源为所述应用的PUCCH配置中的单个PUCCH资源，所 述第四配置信息为所述应用的PUCCH配置中，与所述第二PUCCH资源对应的配置信息；所述应用的PUCCH配置对应的时域单元为所述第一类时域单元，所述其它类别时域单元为所述第二类时域单元；或者，所述应用的PUCCH配置对应的时域单元为所述第二类时域单元，所述其它类别时域单元为所述第一类时域单元。
可选地，当使用第五配置信息确定第二PUCCH资源对应的PUCCH传输时，所述终端不期望所述第二PUCCH资源或者所述第二PUCCH资源的任意重复传输与其它类别时域单元存在交叠；或者，在所述第二PUCCH资源或者所述第二PUCCH资源的第五重复传输与其它类别时域单元存在交叠时，所述终端不期望在至少一个交叠的其它类别时域单元内不满足第二预定义条件；其中，所述第二PUCCH资源为所述应用的PUCCH配置中的单个PUCCH资源，所述第五配置信息为所述应用的PUCCH配置中，与所述第二PUCCH资源对应的配置信息，所述应用的PUCCH配置基于配置或指示确定；所述应用的PUCCH配置对应的时域单元为所述第一类时域单元，所述其它类别时域单元为所述第二类时域单元；或者，所述应用的PUCCH配置对应的时域单元为所述第二类时域单元，所述其它类别时域单元为所述第一类时域单元。
可选地，所述第二预定义条件包括以下至少一项：
所述其它类别时域单元为所述第一类时域单元；
当所述其它类别时域单元为所述第二类时域单元时，所述第二PUCCH资源或者所述第二PUCCH资源的重复传输在所述交叠的其它类别时域单元内占用的任一RE，都位于上行子带对应的频域范围内。
可选地，信息配置装置50还包括：
第三执行模块，用于执行以下任一项：
当SSB传输所在的时域单元内不允许灵活双工操作时，不发送与所述SSB传输所在的时域单元存在交叠的上行传输；
当SSB传输所在的时域单元内允许灵活双工操作，并且在所述SSB传输所在的时域单元内配置灵活双工操作时，在满足第三预定义条件的情况下，发送与所述SSB传输所在的时域单元存在交叠的上行传输。
可选地，所述第三预定义条件包括以下至少一项：
所述上行传输占用的频域资源与所述SSB传输占用的频域资源不存在交叠；
所述上行传输占用的频域资源限制在上行子带的频域范围内，所述上行子带为所述SSB传输占用的时域单元内配置存在的上行子带；
所述上行传输是根据动态信令调度的传输；
所述上行传输的优先级被配置或指示为高优先级。
本申请实施例中的信息配置装置50可以是电子设备，例如具有操作系统的电子设备，也可以是电子设备中的部件，例如集成电路或芯片。该电子设备可以是终端，也可以为除终端之外的其他设备。示例性的，终端可以包括但不限于上述所列举的终端11的类型， 其他设备可以为服务器、网络附属存储器(Network Attached Storage，NAS)等，本申请实施例不作具体限定。
本申请实施例提供的信息配置装置50能够实现图3所示的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
请参见图6，图6是本申请实施例提供的一种信息配置装置的结构示意图，该装置应用于网络侧设备，如图6所示，信息配置装置60包括：
发送模块61，用于向终端发送第一配置信息；
其中，在所述第一配置信息中，针对单个PUCCH资源配置最多M套配置信息，每套配置信息与满足特定要求的时域单元对应；或者，所述第一配置信息包括最多N项PUCCH配置，每项PUCCH配置与满足特定要求的时域单元对应；所述M为大于1的整数，所述N为大于1的整数。
可选地，上述满足特定要求的时域单元可以包括第一类时域单元和/或第二类时域单元，所述第一类时域单元为在上行BWP范围内存在可用上行资源的时域单元，所述第二类时域单元为仅在上行子带范围内存在可用上行资源的时域单元。
可选地，上述的第一类时域单元可以包括以下至少一项：
1)Semi-static上行时域单元；
2)第一Semi-static灵活时域单元，其中，在第一Semi-static灵活时域单元中，上行BWP对应的频域范围都可作为可用上行资源，即采用上述频域限制方式2；第一Semi-static灵活时域单元为允许灵活双工操作的Semi-static flexible时域单元。
可以理解的是，当采用上述的SSB碰撞限制方式1时，这里的第一Semi-static灵活时域单元不包括SSB时域单元。
可选地，上述的第二类时域单元可以包括以下至少一项：
1)Semi-static下行时域单元，这里的Semi-static下行时域单元可以理解为配置存在UL sub-band的Semi-static DL时域单元；
可以理解的是，当采用上述SSB碰撞限制方式1时，这里的Semi-static DL时域单元不包括SSB时域单元。
2)第二Semi-static灵活时域单元，其中，在第二Semi-static灵活时域单元中，仅上行子带对应的频域范围可作为可用上行资源，即采用上述频域限制方式1；第二Semi-static灵活时域单元为允许灵活双工操作的Semi-static flexible时域单元。
可以理解的是，当采用上述SSB碰撞限制方式1时，这里的第二Semi-static灵活时域单元不包括SSB时域单元。
可选地，如果针对单个PUCCH资源仅配置单套配置信息，则：所述单套配置信息对应所述第一类时域单元或者所述第二类时域单元；
或者，如果针对单个PUCCH资源配置两套配置信息，所述两套配置信息包括第一套配置信息和第二套配置信息，则：所述第一套配置信息对应所述第一类时域单元，所述第 二套配置信息对应所述第二类时域单元；或者，所述第一套配置信息对应所述第二类时域单元，所述第二套配置信息对应所述第一类时域单元。
可选地，如果针对单个PUCCH资源配置两套配置信息，发送模块61还用于：向终端发送第一高层信令和/或第一DCI；其中，所述第一高层信令和/或第一DCI用于所述终端从所述两套配置信息中确定应用的配置信息。
可选地，所述应用的配置信息满足以下任一项：
与第一DCI指示的PUCCH传输所在时域单元的类别对应；
由第一DCI中的第一指示域指示；
由第一DCI中的第二指示域联合指示PRI和所述应用的配置信息；
由第一DCI中的第三指示域联合指示K1和所述应用的配置信息。
可选地，如果所述第一配置信息包括两项PUCCH配置，所述两项PUCCH配置包括第一项PUCCH配置和第二项PUCCH配置，则：所述第一项PUCCH配置对应所述第一类时域单元，所述第二项PUCCH配置对应所述第二类时域单元；或者，所述第一项PUCCH配置对应所述第二类时域单元，所述第二项PUCCH配置对应所述第一类时域单元。
可选地，发送模块61还用于：向终端发送第二高层信令和/或第二DCI；其中，所述第二高层信令和/或第二DCI用于终端从所述两项PUCCH配置中确定应用的PUCCH配置。
可选地，所述应用的PUCCH配置满足以下任一项：
与第二DCI指示的PUCCH传输所在时域单元的类别对应；
由第二DCI中的第四指示域指示；
由第二DCI中的第五指示域联合指示PRI和所述应用的PUCCH配置；
由第二DCI中的第六指示域联合指示K1和所述应用的PUCCH配置。
本申请实施例提供的信息配置装置60能够实现图4所示的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
可选地，如图7所示，本申请实施例还提供一种通信设备70，包括处理器71和存储器72，存储器72上存储有可在所述处理器71上运行的程序或指令，例如，该通信设备70为终端时，该程序或指令被处理器71执行时实现上述图3所示的信息配置方法实施例的各个步骤，且能达到相同的技术效果。该通信设备70为网络侧设备时，该程序或指令被处理器71执行时实现上述图4所示的信息配置方法实施例的各个步骤，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供一种终端，包括处理器和通信接口，通信接口用于从网络侧设备接收第一配置信息；其中，在所述第一配置信息中，针对单个PUCCH资源配置最多M套配置信息，每套配置信息与满足特定要求的时域单元对应；或者，所述第一配置信息包括最多N项PUCCH配置，每项PUCCH配置与满足特定要求的时域单元对应；所述M为大于1的整数，所述N为大于1的整数。该终端实施例与上述终端侧方法实施例对应，上述方法实施例的各个实施过程和实现方式均可适用于该终端实施例中，且能达到相同的技 术效果。
具体地，图8为实现本申请实施例的一种终端的硬件结构示意图。
该终端800包括但不限于：射频单元801、网络模块802、音频输出单元803、输入单元804、传感器805、显示单元806、用户输入单元807、接口单元808、存储器809以及处理器810等中的至少部分部件。
本领域技术人员可以理解，终端800还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理系统与处理器810逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。图8中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置，在此不再赘述。
应理解的是，本申请实施例中，输入单元804可以包括图形处理单元(Graphics Processing Unit，GPU)8041和麦克风8042，图形处理器8041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元806可包括显示面板8061，可以采用液晶显示器、有机发光二极管等形式来配置显示面板8061。用户输入单元807包括触控面板8071以及其他输入设备8072中的至少一种。触控面板8071，也称为触摸屏。触控面板8071可包括触摸检测装置和触摸控制器两个部分。其他输入设备8072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
本申请实施例中，射频单元801接收来自网络侧设备的下行数据后，可以传输给处理器810进行处理；另外，射频单元801可以向网络侧设备发送上行数据。通常，射频单元801包括但不限于天线、放大器、收发信机、耦合器、低噪声放大器、双工器等。
存储器809可用于存储软件程序或指令以及各种数据。存储器809可主要包括存储程序或指令的第一存储区和存储数据的第二存储区，其中，第一存储区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外，存储器809可以包括易失性存储器或非易失性存储器，或者，存储器809可以包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synch link DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DRRAM)。本申请实施例中的存储器809包括但不限于这些和任意其它适合类型的存储器。
处理器810可包括一个或多个处理单元；可选地，处理器810集成应用处理器和调制 解调处理器，其中，应用处理器主要处理涉及操作系统、用户界面和应用程序等的操作，调制解调处理器主要处理无线通信信号，如基带处理器。可以理解的是，上述调制解调处理器也可以不集成到处理器810中。
其中，射频单元801，用于从网络侧设备接收第一配置信息；在所述第一配置信息中，针对单个PUCCH资源配置最多M套配置信息，每套配置信息与满足特定要求的时域单元对应；或者，所述第一配置信息包括最多N项PUCCH配置，每项PUCCH配置与满足特定要求的时域单元对应；所述M为大于1的整数，所述N为大于1的整数。
本申请实施例提供的终端800能够实现图3所示的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供一种网络侧设备，包括处理器和通信接口，通信接口用于向终端发送第一配置信息；在所述第一配置信息中，针对单个PUCCH资源配置最多M套配置信息，每套配置信息与满足特定要求的时域单元对应；或者，所述第一配置信息包括最多N项PUCCH配置，每项PUCCH配置与满足特定要求的时域单元对应；所述M为大于1的整数，所述N为大于1的整数。该网络侧设备实施例与上述网络侧设备方法实施例对应，上述方法实施例的各个实施过程和实现方式均可适用于该网络侧设备实施例中，且能达到相同的技术效果。
具体地，本申请实施例还提供了一种网络侧设备。如图9所示，该网络侧设备90包括：天线91、射频装置92、基带装置93、处理器94和存储器95。天线91与射频装置92连接。在上行方向上，射频装置92通过天线91接收信息，将接收的信息发送给基带装置93进行处理。在下行方向上，基带装置93对要发送的信息进行处理，并发送给射频装置92，射频装置92对收到的信息进行处理后经过天线91发送出去。
以上实施例中网络侧设备执行的方法可以在基带装置93中实现，该基带装置93包括基带处理器。
基带装置93例如可以包括至少一个基带板，该基带板上设置有多个芯片，如图9所示，其中一个芯片例如为基带处理器，通过总线接口与存储器95连接，以调用存储器95中的程序，执行以上方法实施例中所示的网络设备操作。
该网络侧设备还可以包括网络接口96，该接口例如为通用公共无线接口(common public radio interface，CPRI)。
具体地，本发明实施例的网络侧设备90还包括：存储在存储器95上并可在处理器94上运行的指令或程序，处理器94调用存储器95中的指令或程序执行图6所示各模块执行的方法，并达到相同的技术效果，为避免重复，故不在此赘述。
本申请实施例还提供一种可读存储介质，所述可读存储介质上存储有程序或指令，该程序或指令被处理器执行时实现上述图3所示的信息配置方法实施例的各个过程，或者实现上述图4所示的信息配置方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
其中，该处理器为上述实施例中所述的终端中的处理器。该可读存储介质，包括计算机可读存储介质，如计算机只读存储器ROM、随机存取存储器RAM、磁碟或者光盘等。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现上述图3所示的信息配置方法实施例的各个过程，或者实现上述图4所示的信息配置方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
本申请实施例另提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在存储介质中，所述计算机程序/程序产品被至少一个处理器执行以实现上述信息配置方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供了一种通信系统，包括：终端及网络侧设备，所述终端可用于执行如上图3所示的信息配置方法的步骤，所述网络侧设备可用于执行如上图4所示的信息配置方法方法的步骤。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、省去、或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以计算机软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本申请的保护之内。

Claims (35)

  1. 一种信息配置方法，包括：
    终端从网络侧设备接收第一配置信息；
    其中，在所述第一配置信息中，针对单个物理上行控制信道资源PUCCH资源配置最多M套配置信息，每套配置信息与满足特定要求的时域单元对应；或者，所述第一配置信息包括最多N项PUCCH配置，每项PUCCH配置与满足特定要求的时域单元对应；所述M为大于1的整数，所述N为大于1的整数。
  2. 根据权利要求1所述的方法，其中，所述满足特定要求的时域单元包括第一类时域单元和/或第二类时域单元，所述第一类时域单元为在上行带宽部分BWP范围内存在可用上行资源的时域单元，所述第二类时域单元为仅在上行子带范围内存在可用上行资源的时域单元。
  3. 根据权利要求2所述的方法，其中，所述第一类时域单元包括以下至少一项：
    半静态Semi-static上行时域单元；
    第一Semi-static灵活时域单元，其中，在所述第一Semi-static灵活时域单元中，上行BWP对应的频域范围都可作为可用上行资源；
    和/或，
    所述第二类时域单元包括以下至少一项：
    Semi-static下行时域单元；
    第二Semi-static灵活时域单元，其中，在所述第二Semi-static灵活时域单元中，仅上行子带对应的频域范围可作为可用上行资源。
  4. 根据权利要求2所述的方法，其中，如果针对单个PUCCH资源仅配置单套配置信息，则：所述单套配置信息对应所述第一类时域单元或者所述第二类时域单元；
    或者，
    如果针对单个PUCCH资源配置两套配置信息，所述两套配置信息包括第一套配置信息和第二套配置信息，则：所述第一套配置信息对应所述第一类时域单元，所述第二套配置信息对应所述第二类时域单元；或者，所述第一套配置信息对应所述第二类时域单元，所述第二套配置信息对应所述第一类时域单元。
  5. 根据权利要求4所述的方法，其中，如果针对单个PUCCH资源配置两套配置信息，所述方法还包括：
    所述终端根据以下至少一项，从所述两套配置信息中确定应用的配置信息：
    所述单个PUCCH资源所在时域单元的类别，或者，所述单个PUCCH资源的重复传输所在时域单元的类别；
    第一高层信令；
    第一下行控制信息DCI。
  6. 根据权利要求5所述的方法，其中，当根据所述PUCCH资源的重复传输所在时域单元的类别确定应用的配置信息时，所述PUCCH资源的各个重复传输满足以下至少一项：
    包含的RE数目一致；
    包含的用于承载上行控制信息UCI的RE数目一致；
    占用的时域单元数目一致。
  7. 根据权利要求4所述的方法，其中，如果针对单个PUCCH资源配置两套配置信息，对于配置了重复传输的PUCCH资源，所述方法还包括：
    所述终端根据以下至少一项，从所述两套配置信息中确定应用的配置信息：
    所述PUCCH资源的名义时域单元的类别；
    所述PUCCH资源的第一个实际发起的重复传输所在时域单元的类别。
  8. 根据权利要求5所述的方法，其中，当根据第一DCI，从所述两套配置信息中确定应用的配置信息时，所述应用的配置信息满足以下任一项：
    与所述第一DCI指示的PUCCH传输所在时域单元的类别对应；
    由所述第一DCI中的第一指示域指示；
    由所述第一DCI中的第二指示域联合指示PUCCH资源指示PRI和所述应用的配置信息；
    由所述第一DCI中的第三指示域联合指示K1和所述应用的配置信息。
  9. 根据权利要求4所述的方法，其中，所述方法还包括以下任一项：
    当第一PUCCH资源未配置重复传输时，如果基于第二配置信息，所述第一PUCCH资源与其它类别时域单元存在交叠，则所述终端执行以下之一：确定所述第一PUCCH资源不可用、在至少一个交叠的其它类别时域单元内不满足第一预定义条件时确定所述第一PUCCH资源不可用；
    当第一PUCCH资源配置了重复传输时，如果基于第二配置信息，所述第一PUCCH资源的第一重复传输与其它类别时域单元存在交叠，则所述终端执行以下之一：确定所述第一重复传输不可用、在至少一个交叠的其它类别时域单元内不满足第一预定义条件时确定所述第一重复传输不可用；
    其中，所述第二配置信息是为所述第一PUCCH资源配置的单套配置信息，或者，所述第二配置信息是从为所述第一PUCCH资源配置的两套配置信息中确定的一套配置信息；
    其中，所述第二配置信息对应的时域单元为所述第一类时域单元，所述其它类别时域单元为所述第二类时域单元；或者，所述第二配置信息对应的时域单元为所述第二类时域单元，所述其它类别时域单元为所述第一类时域单元。
  10. 根据权利要求4所述的方法，其中，对于动态指示的第一PUCCH资源，当使用第三配置信息确定所述第一PUCCH资源对应的PUCCH传输时，所述终端不期望所述第一PUCCH资源或者所述第一PUCCH资源的第二重复传输与其它类别时域单元存在交叠；或者，在所述第一PUCCH资源或者所述第一PUCCH资源的第二重复传输与其它类别时 域单元存在交叠时，所述终端不期望在至少一个交叠的其它类别时域单元内不满足第一预定义条件；
    其中，所述第三配置信息是为所述第一PUCCH资源配置的单套配置信息，所述第三配置信息对应的时域单元为所述第一类时域单元，所述其它类别时域单元为所述第二类时域单元；或者，所述第三配置信息对应的时域单元为所述第二类时域单元，所述其它类别时域单元为所述第一类时域单元。
  11. 根据权利要求4所述的方法，其中，当使用第三配置信息确定第一PUCCH资源对应的PUCCH传输时，所述终端不期望所述第一PUCCH资源或者所述第一PUCCH资源的任意重复传输与其它类别时域单元存在交叠；或者，在所述第一PUCCH资源或者所述第一PUCCH资源的第三重复传输与其它类别时域单元存在交叠时，所述终端不期望在至少一个交叠的其它类别时域单元内不满足第一预定义条件；
    其中，所述第三配置信息是从为所述第一PUCCH资源配置的两套配置信息中确定的一套配置信息，且所述第三配置信息基于配置或指示确定；
    其中，所述第三配置信息对应的时域单元为所述第一类时域单元，所述其它类别时域单元为所述第二类时域单元；或者，所述第三配置信息对应的时域单元为所述第二类时域单元，所述其它类别时域单元为所述第一类时域单元。
  12. 根据权利要求9、10或11所述的方法，其中，所述第一预定义条件包括以下至少一项：
    所述其它类别时域单元为所述第一类时域单元；
    当所述其它类别时域单元为所述第二类时域单元时，所述第一PUCCH资源或者所述第一PUCCH资源的重复传输在交叠的其它类别时域单元内占用的任一资源单元RE，都位于上行子带对应的频域范围内。
  13. 根据权利要求2所述的方法，其中，如果所述第一配置信息包括两项PUCCH配置，所述两项PUCCH配置包括第一项PUCCH配置和第二项PUCCH配置，则：所述第一项PUCCH配置对应所述第一类时域单元，所述第二项PUCCH配置对应所述第二类时域单元；或者，所述第一项PUCCH配置对应所述第二类时域单元，所述第二项PUCCH配置对应所述第一类时域单元。
  14. 根据权利要求13所述的方法，其中，所述方法还包括：
    所述终端根据以下至少一项，从所述两项PUCCH配置中确定应用的PUCCH配置：
    PUCCH传输的名义时域单元的类别；
    第二高层信令；
    第二DCI。
  15. 根据权利要求14所述的方法，其中，当根据所述PUCCH传输的名义时域单元的类别确定应用的PUCCH配置时，对于半静态UCI在所述第一项PUCCH配置和所述第二项PUCCH配置中使用的PUCCH资源的标识的配置，满足以下至少一项：
    仅配置在所述第一项PUCCH配置中使用的PUCCH资源的第一标识，在所述第二项PUCCH配置中使用的PUCCH资源的标识基于所述第一标识确定；或者，仅配置在所述第二项PUCCH配置中使用的PUCCH资源的第二标识，在所述第一项PUCCH配置中使用的PUCCH资源的标识基于所述第二标识确定；
    分别配置在所述第一项PUCCH配置和所述第二项PUCCH配置中使用的PUCCH资源的标识。
  16. 根据权利要求14所述的方法，其中，当根据所述第二DCI，从所述两项PUCCH配置中确定应用的PUCCH配置时，所述应用的PUCCH配置满足以下任一项：
    与所述第二DCI指示的PUCCH传输所在时域单元的类别对应；
    由所述第二DCI中的第四指示域指示；
    由所述第二DCI中的第五指示域联合指示PRI和所述应用的PUCCH配置；
    由所述第二DCI中的第六指示域联合指示K1和所述应用的PUCCH配置。
  17. 根据权利要求14所述的方法，其中，在所述应用的PUCCH配置基于配置或指示确定的情况下，所述方法还包括以下任一项：
    当第二PUCCH资源未配置重复传输时，若基于第四配置信息，所述第二PUCCH资源与其它类别时域单元存在交叠，则所述终端执行以下之一：确定所述第二PUCCH资源不可用、在至少一个交叠的其它类别时域单元内不满足第二预定义条件时确定所述第二PUCCH资源不可用；
    当第二PUCCH资源配置了重复传输时，若基于第四配置信息，所述第二PUCCH资源的第四重复传输与其它类别时域单元存在交叠，则所述终端执行以下之一：确定所述第四重复传输不可用、在至少一个交叠的其它类别时域单元内不满足第二预定义条件时确定所述第四重复传输不可用；
    其中，所述第二PUCCH资源为所述应用的PUCCH配置中的单个PUCCH资源，所述第四配置信息为所述应用的PUCCH配置中，与所述第二PUCCH资源对应的配置信息；所述应用的PUCCH配置对应的时域单元为所述第一类时域单元，所述其它类别时域单元为所述第二类时域单元；或者，所述应用的PUCCH配置对应的时域单元为所述第二类时域单元，所述其它类别时域单元为所述第一类时域单元。
  18. 根据权利要求14所述的方法，其中，当使用第五配置信息确定第二PUCCH资源对应的PUCCH传输时，所述终端不期望所述第二PUCCH资源或者所述第二PUCCH资源的任意重复传输与其它类别时域单元存在交叠；或者，在所述第二PUCCH资源或者所述第二PUCCH资源的第五重复传输与其它类别时域单元存在交叠时，所述终端不期望在至少一个交叠的其它类别时域单元内不满足第二预定义条件；
    其中，所述第二PUCCH资源为所述应用的PUCCH配置中的单个PUCCH资源，所述第五配置信息为所述应用的PUCCH配置中，与所述第二PUCCH资源对应的配置信息，所述应用的PUCCH配置基于配置或指示确定；
    其中，所述应用的PUCCH配置对应的时域单元为所述第一类时域单元，所述其它类别时域单元为所述第二类时域单元；或者，所述应用的PUCCH配置对应的时域单元为所述第二类时域单元，所述其它类别时域单元为所述第一类时域单元。
  19. 根据权利要求17或18所述的方法，其中，所述第二预定义条件包括以下至少一项：
    所述其它类别时域单元为所述第一类时域单元；
    当所述其它类别时域单元为所述第二类时域单元时，所述第二PUCCH资源或者所述第二PUCCH资源的重复传输在所述交叠的其它类别时域单元内占用的任一RE，都位于上行子带对应的频域范围内。
  20. 根据权利要求1所述的方法，其中，所述方法还包括以下至少一项：
    当同步信号块SSB传输所在的时域单元内不允许灵活双工操作时，所述终端不发送与所述SSB传输所在的时域单元存在交叠的上行传输；
    当SSB传输所在的时域单元内允许灵活双工操作，并且在所述SSB传输所在的时域单元内配置灵活双工操作时，所述终端在满足第三预定义条件的情况下，发送与所述SSB传输所在的时域单元存在交叠的上行传输。
  21. 根据权利要求20所述的方法，其中，所述第三预定义条件包括以下至少一项：
    所述上行传输占用的频域资源与所述SSB传输占用的频域资源不存在交叠；
    所述上行传输占用的频域资源限制在上行子带的频域范围内，所述上行子带为所述SSB传输占用的时域单元内配置存在的上行子带；
    所述上行传输是根据动态信令调度的传输；
    所述上行传输的优先级被配置或指示为高优先级。
  22. 一种信息配置方法，包括：
    网络侧设备向终端发送第一配置信息；
    其中，在所述第一配置信息中，针对单个PUCCH资源配置最多M套配置信息，每套配置信息与满足特定要求的时域单元对应；或者，所述第一配置信息包括最多N项PUCCH配置，每项PUCCH配置与满足特定要求的时域单元对应；所述M为大于1的整数，所述N为大于1的整数。
  23. 根据权利要求22所述的方法，其中，所述满足特定要求的时域单元包括第一类时域单元和/或第二类时域单元，所述第一类时域单元为在上行带宽部分BWP范围内存在可用上行资源的时域单元，所述第二类时域单元为仅在上行子带范围内存在可用上行资源的时域单元。
  24. 根据权利要求23所述的方法，其中，所述第一类时域单元包括以下至少一项：
    半静态Semi-static上行时域单元；
    第一Semi-static灵活时域单元，其中，在所述第一Semi-static灵活时域单元中，上行BWP对应的频域范围都可作为可用上行资源；
    和/或，
    所述第二类时域单元包括以下至少一项：
    Semi-static下行时域单元；
    第二Semi-static灵活时域单元，其中，在所述第二Semi-static灵活时域单元中，仅上行子带对应的频域范围可作为可用上行资源。
  25. 根据权利要求23所述的方法，其中，
    如果针对单个PUCCH资源仅配置单套配置信息，则：所述单套配置信息对应所述第一类时域单元或者所述第二类时域单元；
    或者，
    如果针对单个PUCCH资源配置两套配置信息，所述两套配置信息包括第一套配置信息和第二套配置信息，则：所述第一套配置信息对应所述第一类时域单元，所述第二套配置信息对应所述第二类时域单元；或者，所述第一套配置信息对应所述第二类时域单元，所述第二套配置信息对应所述第一类时域单元。
  26. 根据权利要求25所述的方法，其中，如果针对单个PUCCH资源配置两套配置信息，所述方法还包括：
    所述网络侧设备向所述终端发送第一高层信令和/或第一DCI；
    其中，所述第一高层信令和/或第一DCI用于所述终端从所述两套配置信息中确定应用的配置信息。
  27. 根据权利要求26所述的方法，其中，所述应用的配置信息满足以下任一项：
    与所述第一DCI指示的PUCCH传输所在时域单元的类别对应；
    由所述第一DCI中的第一指示域指示；
    由所述第一DCI中的第二指示域联合指示PRI和所述应用的配置信息；
    由所述第一DCI中的第三指示域联合指示K1和所述应用的配置信息。
  28. 根据权利要求23所述的方法，其中，如果所述第一配置信息包括两项PUCCH配置，所述两项PUCCH配置包括第一项PUCCH配置和第二项PUCCH配置，则：所述第一项PUCCH配置对应所述第一类时域单元，所述第二项PUCCH配置对应所述第二类时域单元；或者，所述第一项PUCCH配置对应所述第二类时域单元，所述第二项PUCCH配置对应所述第一类时域单元。
  29. 根据权利要求28所述的方法，其中，所述方法还包括：
    所述网络侧设备向所述终端发送第二高层信令和/或第二DCI；
    其中，所述第二高层信令和/或第二DCI用于所述终端从所述两项PUCCH配置中确定应用的PUCCH配置。
  30. 根据权利要求29所述的方法，其中，所述应用的PUCCH配置满足以下任一项：
    与所述第二DCI指示的PUCCH传输所在时域单元的类别对应；
    由所述第二DCI中的第四指示域指示；
    由所述第二DCI中的第五指示域联合指示PRI和所述应用的PUCCH配置；
    由所述第二DCI中的第六指示域联合指示K1和所述应用的PUCCH配置。
  31. 一种信息配置装置，包括：
    接收模块，用于从网络侧设备接收第一配置信息；
    其中，在所述第一配置信息中，针对单个PUCCH资源配置最多M套配置信息，每套配置信息与满足特定要求的时域单元对应；或者，所述第一配置信息包括最多N项PUCCH配置，每项PUCCH配置与满足特定要求的时域单元对应；所述M为大于1的整数，所述N为大于1的整数。
  32. 一种信息配置装置，包括：发送模块，用于向终端发送第一配置信息；
    其中，在所述第一配置信息中，针对单个PUCCH资源配置最多M套配置信息，每套配置信息与满足特定要求的时域单元对应；或者，所述第一配置信息包括最多N项PUCCH配置，每项PUCCH配置与满足特定要求的时域单元对应；所述M为大于1的整数，所述N为大于1的整数。
  33. 一种终端，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1至21任一项所述的信息配置方法的步骤。
  34. 一种网络侧设备，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求22至30任一项所述的信息配置方法的步骤。
  35. 一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如权利要求1至21任一项所述的信息配置方法，或者实现如权利要求22至30任一项所述的信息配置方法的步骤。
PCT/CN2023/107885 2022-07-25 2023-07-18 信息配置方法、装置、终端、网络侧设备及可读存储介质 Ceased WO2024022159A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US19/034,547 US20250175987A1 (en) 2022-07-25 2025-01-22 Information configuration method and apparatus, terminal, network side device, and readable storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210877636.9 2022-07-25
CN202210877636.9A CN117528798A (zh) 2022-07-25 2022-07-25 信息配置方法、装置、终端、网络侧设备及可读存储介质

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US19/034,547 Continuation US20250175987A1 (en) 2022-07-25 2025-01-22 Information configuration method and apparatus, terminal, network side device, and readable storage medium

Publications (1)

Publication Number Publication Date
WO2024022159A1 true WO2024022159A1 (zh) 2024-02-01

Family

ID=89705373

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/107885 Ceased WO2024022159A1 (zh) 2022-07-25 2023-07-18 信息配置方法、装置、终端、网络侧设备及可读存储介质

Country Status (3)

Country Link
US (1) US20250175987A1 (zh)
CN (1) CN117528798A (zh)
WO (1) WO2024022159A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2025167542A1 (zh) * 2024-02-08 2025-08-14 中国移动通信有限公司研究院 Pucch传输方法、装置、终端、网络设备及介质

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN121510314A (zh) * 2024-08-09 2026-02-10 维沃移动通信有限公司 参数配置方法、装置、终端及网络侧设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018169937A1 (en) * 2017-03-15 2018-09-20 Intel IP Corporation Determination of new radio (nr) physical uplink control channel(pucch) resource for hybrid automatic repeat request acknowledgement (harq-ack) feedback
CN113939024A (zh) * 2020-07-14 2022-01-14 中国移动通信有限公司研究院 一种传输方法、终端及网络侧设备
CN114340001A (zh) * 2020-09-28 2022-04-12 华为技术有限公司 一种上行控制信道的传输方法、装置、存储介质及芯片
CN114365530A (zh) * 2019-11-08 2022-04-15 Oppo广东移动通信有限公司 一种信息传输方法、装置、终端以及存储介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018169937A1 (en) * 2017-03-15 2018-09-20 Intel IP Corporation Determination of new radio (nr) physical uplink control channel(pucch) resource for hybrid automatic repeat request acknowledgement (harq-ack) feedback
CN114365530A (zh) * 2019-11-08 2022-04-15 Oppo广东移动通信有限公司 一种信息传输方法、装置、终端以及存储介质
CN113939024A (zh) * 2020-07-14 2022-01-14 中国移动通信有限公司研究院 一种传输方法、终端及网络侧设备
CN114340001A (zh) * 2020-09-28 2022-04-12 华为技术有限公司 一种上行控制信道的传输方法、装置、存储介质及芯片

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2025167542A1 (zh) * 2024-02-08 2025-08-14 中国移动通信有限公司研究院 Pucch传输方法、装置、终端、网络设备及介质

Also Published As

Publication number Publication date
US20250175987A1 (en) 2025-05-29
CN117528798A (zh) 2024-02-06

Similar Documents

Publication Publication Date Title
WO2024061261A1 (zh) 资源配置方法及装置、终端及网络侧设备
EP4459882A1 (en) Frequency hopping method and apparatus for uplink transmission, indication method and apparatus, and terminal and network side device
WO2024067571A1 (zh) 灵活双工sbfd信息指示方法、终端及网络侧设备
US20250175987A1 (en) Information configuration method and apparatus, terminal, network side device, and readable storage medium
WO2024022160A1 (zh) 信息配置方法、装置、终端、网络侧设备及可读存储介质
US20240365297A1 (en) Transmission Determining Method and Apparatus, Device, and Medium
EP4510744A1 (en) Information receiving method and apparatus, information sending method and apparatus, and device
WO2024027747A1 (zh) 数据传输处理方法、装置、终端及网络侧设备
CN114765798A (zh) 信道信息发送方法、信道信息接收方法及相关设备
US20250168830A1 (en) Information configuration method and apparatus, terminal, network-side device, and readable storage medium
WO2023125906A1 (zh) 资源传输方向确定方法、装置及终端
WO2024140634A1 (zh) 传输方法、设备及可读存储介质
WO2024001965A1 (zh) 时分复用载波聚合的配置方法、终端及网络侧设备
CN118301748A (zh) 一种传输参数配置方法、装置及终端设备
WO2025077607A1 (zh) 动态sbfd指示方法、装置、设备及存储介质
EP4561221A1 (en) Transmission processing method and apparatus, and device
CN120835410A (zh) 下行接收和测量方法、装置及通信设备
WO2025130733A1 (zh) Sps harq-ack的传输方法、终端及网络侧设备
WO2024125428A1 (zh) 传输方法、设备及可读存储介质
WO2025113369A1 (zh) 资源激活方法、装置、终端及网络侧设备
WO2024235067A1 (zh) 灵活双工的实现方法、装置、终端、网络侧设备及介质
WO2024104152A1 (zh) 频域资源确定方法、终端及网络侧设备
WO2026032175A1 (zh) 参数配置方法、装置、终端及网络侧设备
WO2025140605A1 (zh) 无线通信方法、装置、设备以及可读存储介质
CN121013199A (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: 23845371

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: 23845371

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 16/07/2025)

122 Ep: pct application non-entry in european phase

Ref document number: 23845371

Country of ref document: EP

Kind code of ref document: A1