WO2021159386A1 - 上行信号的发送和接收方法、装置和通信系统 - Google Patents

上行信号的发送和接收方法、装置和通信系统 Download PDF

Info

Publication number
WO2021159386A1
WO2021159386A1 PCT/CN2020/075079 CN2020075079W WO2021159386A1 WO 2021159386 A1 WO2021159386 A1 WO 2021159386A1 CN 2020075079 W CN2020075079 W CN 2020075079W WO 2021159386 A1 WO2021159386 A1 WO 2021159386A1
Authority
WO
WIPO (PCT)
Prior art keywords
configuration information
pucch
physical uplink
control channel
uplink control
Prior art date
Application number
PCT/CN2020/075079
Other languages
English (en)
French (fr)
Inventor
陈哲
宋磊
蒋琴艳
张磊
王昕�
Original Assignee
富士通株式会社
陈哲
宋磊
蒋琴艳
张磊
王昕�
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 富士通株式会社, 陈哲, 宋磊, 蒋琴艳, 张磊, 王昕� filed Critical 富士通株式会社
Priority to PCT/CN2020/075079 priority Critical patent/WO2021159386A1/zh
Publication of WO2021159386A1 publication Critical patent/WO2021159386A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation

Definitions

  • the embodiments of the present application relate to the field of wireless communication technology.
  • the communication system has enhanced the transmission mechanism of uplink signals.
  • the parameters related to the uplink signal can be configured separately for different service types.
  • RRC radio resource control
  • PUCCH physical uplink control channel
  • the PUCCH resource with the smallest ID is called the dedicated PUCCH resource with the smallest identification number (ID) of the group; in this case, if the terminal When the device needs to use the downlink control signal format 0_0 (DCI format 0_0) to schedule the uplink physical uplink shared channel (PUSCH), it needs to determine which group of dedicated configuration information to use, and according to the dedicated group with the smallest identification number (ID)
  • the spatial relationship of physical uplink control channel resources (dedicated PUCCH resources) or power control reference signals are used to transmit the PUSCH.
  • the terminal device cannot determine which set of dedicated configuration information to use, so there is a problem that the DCI format 0_0 scheduled PUSCH has a spatial relationship or the power control reference signal indicates ambiguity.
  • the embodiments of the present application provide a method, device, and communication system for sending and receiving uplink signals.
  • the downlink control signal is sent Format 0_0 (DCI format 0_0) scheduled physical uplink shared channel (PUSCH), this method can avoid the problem of spatial relationship or power control reference signal ambiguity in the PUSCH scheduled by DCI format 0_0.
  • a method for transmitting an uplink signal which is applied to a terminal device, and the method is based on the space of the PUCCH configuration information corresponding to the first configuration information or the second configuration information.
  • the relationship or power control reference signal is used to transmit the PUSCH scheduled by DCI format 0_0.
  • a method for receiving uplink signals which is applied to a network device, and the method is based on the spatial relationship of the PUCCH configuration information corresponding to the first configuration information or the second configuration information. Or power control reference signal to receive PUSCH scheduled by DCI format 0_0.
  • an uplink signal sending apparatus which is applied to a terminal device, and the apparatus executes the uplink signal sending method of the first aspect or the second aspect of the embodiments of the present application.
  • an uplink signal receiving apparatus which is applied to a network device, and the apparatus executes the uplink signal receiving method of the third aspect or the fourth aspect of the embodiments of the present application.
  • a terminal device having the uplink signal sending apparatus described in the fifth aspect of the embodiments of the present application.
  • a network device having the uplink signal receiving apparatus described in the sixth aspect of the embodiments of the present application.
  • a communication system which has the terminal device described in the seventh aspect of the embodiments of the present application and the network device described in the eighth aspect.
  • a computer-readable program wherein when the program is executed in an uplink signal sending apparatus or terminal device, the program causes the uplink signal sending apparatus or terminal to The device executes the uplink signal sending method of the first aspect or the second aspect of the embodiments of the present application.
  • a storage medium storing a computer-readable program, wherein the computer-readable program enables the sending apparatus or terminal device of the uplink signal to execute the first aspect or The uplink signal transmission method described in the second aspect.
  • a computer-readable program wherein when the program is executed in an uplink signal receiving apparatus or network device, the program causes the uplink signal receiving apparatus or network
  • the device executes the uplink signal receiving method described in the third aspect or the fourth aspect of the embodiments of the present application.
  • a storage medium storing a computer-readable program, wherein the computer-readable program enables the receiving apparatus or network equipment of the uplink signal to execute the third aspect of the embodiments of the present application Or the uplink signal receiving method described in the fourth aspect.
  • the beneficial effects of the embodiments of the present application are: according to the spatial relationship or power control reference signal of the PUCCH configuration information corresponding to the first configuration information or the second configuration information, the physical uplink scheduled by the downlink control signal format 0_0 (DCI format 0_0) is sent Shared channel (PUSCH), this method can avoid the problem of spatial relationship or ambiguity in power control reference signal indication for PUSCH scheduled by DCI format 0_0.
  • DCI format 0_0 the physical uplink scheduled by the downlink control signal format 0_0
  • PUSCH Shared channel
  • Fig. 1 is a schematic diagram of a communication system according to an embodiment of the present application.
  • FIG. 2 is a schematic diagram of the uplink signal sending method according to the first aspect of the embodiments of the present application
  • FIG. 3 is another schematic diagram of the uplink signal sending method according to the first aspect of the embodiments of the present application.
  • FIG. 4 is a schematic diagram of the uplink signal sending method according to the second aspect of the embodiments of the present application.
  • FIG. 5 is another schematic diagram of the uplink signal sending method according to the second aspect of the embodiments of the present application.
  • FIG. 6 is a schematic diagram of the uplink signal receiving method of the third aspect of the embodiments of the present application.
  • FIG. 7 is another schematic diagram of the uplink signal receiving method of the third aspect of the embodiments of the present application.
  • FIG. 8 is a schematic diagram of the uplink signal receiving method according to the fourth aspect of the embodiments of the present application.
  • FIG. 9 is another schematic diagram of the uplink signal receiving method according to the fourth aspect of the embodiments of the present application.
  • FIG. 10 is a schematic diagram of the uplink signal sending device in the fifth aspect of the embodiments of the present application.
  • FIG. 11 is another schematic diagram of the uplink signal sending apparatus in the fifth aspect of the embodiments of the present application.
  • FIG. 12 is another schematic diagram of the uplink signal sending apparatus in the fifth aspect of the embodiments of the present application.
  • FIG. 13 is still another schematic diagram of the uplink signal sending apparatus in the fifth aspect of the embodiments of the present application.
  • FIG. 14 is a schematic diagram of the uplink signal receiving apparatus in the sixth aspect of the embodiments of the present application.
  • 15 is another schematic diagram of the uplink signal receiving apparatus in the sixth aspect of the embodiments of the present application.
  • FIG. 16 is another schematic diagram of the uplink signal receiving apparatus in the sixth aspect of the embodiments of the present application.
  • FIG. 17 is still another schematic diagram of the uplink signal receiving apparatus in the sixth aspect of the embodiments of the present application.
  • FIG. 18 is a schematic block diagram of the system configuration of the terminal device in the seventh aspect of the embodiments of the present application.
  • FIG. 19 is a schematic diagram of the structure of the network device in the eighth aspect of the embodiments of the present application.
  • the terms “first”, “second”, etc. are used to distinguish different elements from the terms, but they do not indicate the spatial arrangement or chronological order of these elements. These elements should not be used by these terms. Limited.
  • the term “and/or” includes any and all combinations of one or more of the associated listed terms.
  • the terms “comprising”, “including”, “having” and the like refer to the existence of the stated features, elements, elements or components, but do not exclude the presence or addition of one or more other features, elements, elements or components.
  • the term "communication network” or “wireless communication network” can refer to a network that meets any of the following communication standards, such as Long Term Evolution (LTE), and Enhanced Long Term Evolution (LTE-A, LTE-A). Advanced), Wideband Code Division Multiple Access (WCDMA, Wideband Code Division Multiple Access), High-Speed Packet Access (HSPA, High-Speed Packet Access), etc.
  • LTE Long Term Evolution
  • LTE-A Enhanced Long Term Evolution
  • LTE-A LTE-A
  • Advanced Wideband Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • High-Speed Packet Access High-Speed Packet Access
  • HSPA High-Speed Packet Access
  • the communication between devices in the communication system can be carried out according to any stage of communication protocol, for example, it can include but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and future 5G, New Radio (NR, New Radio), etc., and/or other communication protocols currently known or to be developed in the future.
  • 1G generation
  • 2G 2.5G
  • 2.75G 3G
  • 4G 4G
  • 4.5G future 5G
  • New Radio NR, New Radio
  • Network device refers to, for example, a device in a communication system that connects a terminal device to a communication network and provides services for the terminal device.
  • Network equipment may include but not limited to the following equipment: base station (BS, Base Station), access point (AP, Access Point), transmission and reception point (TRP, Transmission Reception Point), broadcast transmitter, mobile management entity (MME, Mobile Management Entity), gateway, server, radio network controller (RNC, Radio Network Controller), base station controller (BSC, Base Station Controller), etc.
  • the base station may include but is not limited to: Node B (NodeB or NB), evolved Node B (eNodeB or eNB), 5G base station (gNB), etc., and may also include remote radio head (RRH, Remote Radio Head) , Remote Radio Unit (RRU, Remote Radio Unit), relay (relay), or low-power node (such as femto, pico, etc.).
  • NodeB Node B
  • eNodeB or eNB evolved Node B
  • gNB 5G base station
  • RRH Remote Radio Head
  • RRU Remote Radio Unit
  • relay relay
  • low-power node such as femto, pico, etc.
  • base station can include some or all of their functions, and each base station can provide communication coverage for a specific geographic area.
  • the term "cell” may refer to a base station and/or its coverage area, depending on the context in which the term is used.
  • the term "User Equipment” (UE, User Equipment) or “Terminal Equipment” (TE, Terminal Equipment), for example, refers to equipment that accesses a communication network through a network device and receives network services.
  • the user equipment may be fixed or mobile, and may also be called a mobile station (MS, Mobile Station), terminal, subscriber station (SS, Subscriber Station), access terminal (AT, Access Terminal), station, etc.
  • user equipment may include, but is not limited to, the following devices: Cellular Phone, Personal Digital Assistant (PDA, Personal Digital Assistant), wireless modem, wireless communication device, handheld device, machine-type communication device, laptop computer, Cordless phones, smart phones, smart watches, digital cameras, etc.
  • PDA Personal Digital Assistant
  • wireless modem wireless communication device
  • handheld device machine-type communication device
  • laptop computer machine-type communication device
  • Cordless phones smart phones
  • smart watches digital cameras, etc.
  • user equipment may also be a machine or device that performs monitoring or measurement.
  • it may include, but is not limited to: Machine Type Communication (MTC) terminals, In-vehicle communication terminals, device to device (D2D, Device to Device) terminals, machine to machine (M2M, Machine to Machine) terminals, etc.
  • MTC Machine Type Communication
  • D2D Device to Device
  • M2M Machine to Machine
  • FIG. 1 is a schematic diagram of a communication system according to an embodiment of the present application, schematically illustrating a case where a terminal device and a network device are taken as an example.
  • the communication system 100 may include a network device 101 and a terminal device 102.
  • Figure 1 only uses one terminal device as an example for illustration.
  • eMBB enhanced mobile broadband
  • mMTC large-scale machine type communication
  • URLLC Ultra-Reliable and Low- Latency Communication
  • the terminal device 102 can send data to the network device 101, for example, using an unauthorized transmission mode.
  • the network device 101 can receive data sent by one or more terminal devices 102, and feedback information (for example, correct ACK/negative acknowledgement NACK) information to the terminal device 102, and the terminal device 102 can confirm the end of the transmission process according to the feedback information, or it can also New data transmission can be performed, or data retransmission can be performed.
  • feedback information for example, correct ACK/negative acknowledgement NACK
  • the following takes the network device in the communication system as the receiving end or sending short, and the terminal device as the sending end or receiving end as examples, but the application is not limited to this, and the sending end and/or receiving end may also be other devices. .
  • this application is not only applicable to uplink unauthorized transmission between network equipment and terminal equipment, but also applicable to side link unauthorized transmission between two terminal equipment.
  • the first aspect of the embodiments of the present application relates to a method for sending an uplink signal.
  • PHY layer priority In some communication standards (for example, Rel-16 of the 5G standard), the concept of physical layer priority (PHY layer priority) is introduced. Generally speaking, most uplink signals can determine their physical layer priority according to the corresponding indication information. class.
  • the corresponding priority indication can help the uplink control signal determine its corresponding RRC configuration parameters (for example, PUCCH-config), so that different types of service transmissions can be configured in parallel and scheduled in parallel, thereby improving The efficiency of the system.
  • RRC configuration parameters for example, PUCCH-config
  • the terminal device transmits the PUSCH scheduled by the downlink control signal format 0_0 (DCI format 0_0), when the spatial relationship is applied (that is, when there is a configured spatial relationship), the spatial relationship of the PUSCH is based on the activated uplink
  • the spatial relationship of the dedicated PUCCH resource with the smallest identifier (ID) in the bandwidth part (UL BWP) is set. Therefore, the uplink data transmission scheduled by the DCI format 0_0 can be independent of the RRC configuration information related to the PUSCH, so that the uplink signal can be correctly transmitted when the terminal device and the network device have inconsistent understanding of the configuration information.
  • the terminal device When the terminal device transmits the PUSCH scheduled by DCI format 0_0 on carrier f, and the PUCCH resource (resource) with the smallest ID on the activated bandwidth part (BWP) of carrier f is configured with spatial relationship information (PUCCH-SpatialRelationInfo), the terminal device uses The same power control reference signal corresponding to the PUCCH resource transmits the PUSCH.
  • the first aspect of the embodiments of the present application relates to a method for sending an uplink signal, which is applied to a terminal device, such as the terminal device 102, which has the ability to simultaneously assemble or generate at least two hybrid automatic repeat request-acknowledgement codebooks (HARQ-ACK). codebook) capabilities.
  • HARQ-ACK hybrid automatic repeat request-acknowledgement codebooks
  • FIG. 2 is a schematic diagram of the uplink signal sending method of the first aspect of the embodiments of the present application. As shown in FIG. 2, the uplink signal sending method includes:
  • Operation 201 Configure first configuration information related to a physical uplink control channel (PUCCH) by a network device;
  • Operation 202 According to the spatial relation of the physical uplink control channel (PUCCH) configuration information corresponding to the first configuration information, transmission is scheduled by downlink control signal format 0_0 (DCI format 0_0) in a cell (DCI format 0_0) The physical uplink shared channel (PUSCH).
  • PUCCH physical uplink control channel
  • the physical uplink shared channel (PUSCH) scheduled by the downlink control signal format 0_0 (DCI format 0_0) can be transmitted according to the spatial relationship of the PUCCH configuration information corresponding to the first configuration information, thus,
  • the terminal device has the ability to assemble or generate at least two hybrid automatic repeat request-acknowledgement codebooks (HARQ-ACK codebook) at the same time, it can also avoid the problem of ambiguity in the spatial relationship indication of the PUSCH scheduled by DCI format 0_0, so as to be accurate To indicate the spatial relationship.
  • HARQ-ACK codebook hybrid automatic repeat request-acknowledgement codebooks
  • the first configuration information configured in operation 201 is subordinate to the dedicated parameters configuration information of the active uplink bandwidth part (UL BWP) of the cell, wherein the dedicated parameters of the uplink bandwidth part
  • the parameter configuration information corresponds to, for example, BWP-UplinkDedicated.
  • the first configuration information may be dedicated PUCCH configuration information of the uplink bandwidth part, for example, pucch-Config subordinate to BWP-UplinkDedicated.
  • the first configuration information may include a PUCCH configuration information list (for example, resourceToAddModList), and the list may add PUCCH resources to the uplink bandwidth part.
  • the first configuration information may include another PUCCH configuration information list (for example, resourceToReleaseList), and the list may release PUCCH resources for the uplink bandwidth part.
  • the first configuration information may correspond to one or more than one PUCCH resource. Among them, each PUCCH resource has (will be configured) a corresponding identification number (ID).
  • the terminal device may send the downlink control signal format 0_0 ( DCI format 0_0) Scheduled physical uplink shared channel (PUSCH).
  • DCI format 0_0 Scheduled physical uplink shared channel
  • the terminal device may transmit the downlink control signal format 0_0 (DCI format 0_0) according to the spatial relationship of the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) corresponding to the first configuration information.
  • the physical uplink shared channel (PUSCH) scheduled by the downlink control signal format 0_0 DCI format 0_0
  • DCI format 0_0 may be transmitted according to the spatial relationship of the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) corresponding to the first configuration information.
  • the uplink signal sending method further includes:
  • Operation 203 Send a report message to the network device, and the report message reports to the network device that the terminal device has the ability to simultaneously assemble or generate at least two hybrid automatic repeat request-acknowledgement codebooks (HARQ-ACK codebook).
  • HARQ-ACK codebook hybrid automatic repeat request-acknowledgement codebooks
  • the terminal device can report to the network device that the terminal device has the ability to assemble or generate at least two hybrid automatic repeat request-acknowledgement codebooks (HARQ-ACK codebook) at the same time, so that the network device can configure the terminal device
  • HARQ-ACK codebook hybrid automatic repeat request-acknowledgement codebooks
  • the second configuration information refers to physical uplink control channel (PUCCH) configuration information used for (for) at least two simultaneously assembled (simultaneous constructed) hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebooks (codebook) .
  • PUCCH physical uplink control channel
  • HARQ-ACK hybrid automatic repeat request-acknowledgement
  • the second configuration information is subordinate to dedicated parameters (dedicated parameters) configuration information of the active uplink bandwidth part (active UL BWP) of the cell.
  • the second configuration information may be a dedicated PUCCH configuration information list of the uplink bandwidth part, for example, pucch-ConfigurationList subordinate to BWP-UplinkDedicated.
  • the second configuration information may have at least one set of PUCCH configuration information, each set of PUCCH configuration information (similar to the first configuration information) may correspond to one or more than one PUCCH resource, and each PUCCH resource has (will Configured) the corresponding identification number (ID).
  • the second configuration information may have one set of PUCCH configuration information; for another example, the second configuration information may have two or more sets of PUCCH configuration information, and each set of PUCCH configuration information may correspond to one or more than one PUCCH configuration information.
  • PUCCH resources each PUCCH resource has (will be configured) a corresponding identification number (ID).
  • ID identification number
  • each group of PUCCH configuration information corresponds to a different priority.
  • the first group of PUCCH configuration information corresponds to a low priority (for example, the priority index is 0), and the second group of PUCCH configuration information corresponds to a high priority (for example, , The priority index is 1).
  • the priority refers to the physical layer priority.
  • the network device may configure the second configuration information to the terminal device, or may not configure the second configuration information to the terminal device.
  • the uplink signal sending method shown in FIG. 2 will be illustrated by examples of Example 1, Example 2 and Example 3.
  • the first configuration information may be pucch-Config subordinate to BWP-UplinkDedicated
  • the second configuration information may be pucch-ConfigurationList subordinate to BWP-UplinkDedicated.
  • the pucch-ConfigurationList may include one or two sets of PUCCH configuration information.
  • the PUCCH configuration information is, for example, represented as PUCCH-Config.
  • the PUCCH configuration information is an IE used to configure terminal device specific PUCCH parameters (UE specific PUCCH parameters).
  • the terminal device is provided with first configuration information, namely pucch-Config, where the first configuration information is subordinate to dedicated parameters configuration information (BWP-UplinkDedicated) of the uplink bandwidth part (UL BWP); and ,
  • the terminal device is not provided with the second configuration information, that is, pucch-ConfigurationList is not configured in the BWP-UplinkDedicated.
  • the terminal device may be configured according to the pucch-Config.
  • the PUSCH scheduled by DCI format 0_0 is sent.
  • the spatial configuration information is, for example, PUCCH-SpatialRelationInfo.
  • Example 1 when the terminal device can be provided with pucch-ConfigurationList but not provided with pucch-ConfigurationList, the terminal device obtains the spatial direction of the PUSCH scheduled by DCI format 0_0 according to the configuration information pucch-Config in BWP-UplinkDedicated, In this way, the problem of ambiguity in the indication of the spatial relationship of the PUSCH scheduled by the DCI format 0_0 can be avoided, and the spatial direction of the PUSCH scheduled by the DCI format 0_0 can be accurately indicated, thereby improving system stability.
  • the terminal device is provided with first configuration information, namely pucch-Config, where the first configuration information is subordinate to dedicated parameters configuration information (BWP-UplinkDedicated) of the uplink bandwidth part (UL BWP).
  • the terminal device may also be provided with second configuration information, that is, the terminal device is configured with pucch-ConfigurationList-r16 in the BWP-UplinkDedicated.
  • the second configuration information only has one set of PUCCH configuration information (pucch-Config).
  • the terminal device may be configured according to the pucch-Config.
  • the PUSCH scheduled by DCI format 0_0 is sent.
  • the spatial configuration information is, for example, PUCCH-SpatialRelationInfo.
  • Example 2 when the terminal device is provided with a pucch-ConfigurationList that includes only one set of PUCCH configuration information, the terminal device obtains the spatial direction of the PUSCH scheduled by DCI format 0_0 according to the configuration information pucch-Config in the BWP-UplinkDedicated, In this way, the problem of ambiguity in the indication of the spatial relationship of the PUSCH scheduled by the DCI format 0_0 can be avoided, and the spatial direction of the PUSCH scheduled by the DCI format 0_0 can be accurately indicated, thereby improving system stability.
  • the terminal device is provided with first configuration information, that is, pucch-Config, where the first configuration information is subordinate to dedicated parameter configuration information (in BWP-UplinkDedicated) of the uplink bandwidth part (UL BWP).
  • first configuration information that is, pucch-Config
  • second configuration information that is, the terminal device is configured with pucch-ConfigurationList in the BWP-UplinkDedicated.
  • the second configuration information has two sets of PUCCH configuration information (pucch-Config).
  • the terminal device may be configured according to the pucch-Config.
  • the PUSCH scheduled by DCI format 0_0 is sent.
  • the spatial configuration information is, for example, PUCCH-SpatialRelationInfo.
  • the terminal device when the terminal device is provided with a pucch-ConfigurationList that includes two sets of PUCCH configuration information, the terminal device obtains the spatial direction of the PUSCH scheduled by DCI format 0_0 according to the pucch-Config configured in BWP-UplinkDedicated, thereby avoiding
  • the PUSCH scheduled by DCI format 0_0 has the problem of ambiguity in the spatial relationship indication, which can accurately indicate the spatial direction of the PUSCH scheduled by DCI format 0_0, which improves system stability.
  • FIG. 3 is another schematic diagram of the uplink signal sending method of the first aspect of the embodiments of the present application. As shown in FIG. 3, the uplink signal sending method includes:
  • Operation 301 The network device configures second configuration information related to the physical uplink control channel (PUCCH), where the second configuration information refers to at least two simultaneous constructed (simultaneous constructed) hybrid automatic repeat request-confirmation (HARQ-ACK) physical uplink control channel (PUCCH) configuration information of the codebook; and
  • Operation 302 According to the spatial relation of the physical uplink control channel (PUCCH) configuration information corresponding to the second configuration information, the transmission is scheduled by the downlink control signal format 0_0 (DCI format 0_0) in a cell.
  • the physical uplink shared channel (PUSCH) scheduled by the downlink control signal format 0_0 can be transmitted according to the spatial relationship of the PUCCH configuration information corresponding to the second configuration information, and it can also avoid DCI format 0_0 scheduled PUSCH has the problem of ambiguity in the indication of the spatial relationship, thereby accurately indicating the spatial relationship.
  • the terminal device can generate at least two hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebooks.
  • the terminal device may generate two HARQ-ACK codebooks according to configuration information, where the configuration information is, for example, a physical downlink shared channel hybrid automatic repeat request confirmation codebook list (pdsch-HARQ-ACK-Codebook-List).
  • Information refers to the PUCCH configuration information used for at least two simultaneously assembled (simultaneous constructed) HARQ-ACK codebooks (codebook) in the configuration information of cell-group specific L1 parameters (cell-group specific L1parameters), the configuration information ( pdsch-HARQ-ACK-Codebook-List) is different from the second configuration information.
  • the configuration information may separately determine the type of each HARQ-ACK codebook (the type is, for example, dynamic or semi-static).
  • the terminal device may use the identification number (ID) corresponding to the set of physical uplink control channel (PUCCH) configuration information of the second configuration information.
  • ID the identification number
  • PUSCH physical uplink shared channel
  • the terminal device may send the downlink control signal format 0_0 (DCI format 0_0) according to the spatial relationship of the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) corresponding to the second configuration information.
  • the physical uplink shared channel (PUSCH) scheduled by the downlink control signal format 0_0 DCI format 0_0
  • DCI format 0_0 may be sent according to the spatial relationship of the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) corresponding to the second configuration information.
  • the terminal device In the case where the second configuration information includes two sets of physical uplink control channel (PUCCH) configuration information, the terminal device according to the first set of physical uplink control channel (PUCCH) configuration information in the two sets of physical uplink control channel (PUCCH) configuration information of the second configuration information (PUCCH) configuration information or the spatial relationship of the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) corresponding to the second group of physical uplink control channel (PUCCH) configuration information, sent by the downlink control signal format 0_0 (DCI format 0_0) Scheduled physical uplink shared channel (PUSCH).
  • PUCCH physical uplink control channel
  • the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) corresponding to the first group of physical uplink control channel (PUCCH) configuration information or the second group of physical uplink control channel (PUCCH) configuration information is configured
  • the terminal device may correspond to the first group of physical uplink control channel (PUCCH) configuration information or the second group of physical uplink control channel (PUCCH) configuration information
  • the terminal device may be configured with the first configuration information or not configured with the first configuration information by the network device.
  • the description of the first configuration information is the same as the foregoing description of the first aspect of the embodiment of the present application.
  • the uplink signal sending method shown in FIG. 3 will be illustrated by examples four, five and six.
  • the second configuration information may be pucch-ConfigurationList subordinate to BWP-UplinkDedicated.
  • pucch-ConfigurationList may include one or two sets of PUCCH configuration information.
  • the PUCCH configuration information for example, is represented as PUCCH-Config.
  • the PUCCH configuration information is an IE used to configure terminal device specific PUCCH parameters (UE specific PUCCH parameters).
  • the terminal device is provided with second configuration information, that is, pucch-ConfigurationList, and the second configuration information is subordinate to dedicated parameters configuration information of the uplink bandwidth part (UL BWP).
  • the second configuration information only has one set of PUCCH configuration information (pucch-Config).
  • the terminal device may send the PUSCH scheduled by DCI format 0_0 according to the spatial relationship of the PUCCH resource with the smallest ID in the set of PUCCH configuration information (pucch-Config) in the pucch-ConfigurationList.
  • the spatial configuration information is, for example, PUCCH-SpatialRelationInfo.
  • Example 4 when the terminal device is provided with a pucch-ConfigurationList that includes only one set of PUCCH configuration information, the terminal device obtains the DCI format according to the configuration information pucch-ConfigurationList in the BWP-UplinkDedicated.
  • the spatial direction of the PUSCH scheduled by 0_0 so as to avoid the problem of ambiguity in the spatial relationship indication of the PUSCH scheduled by DCI format 0_0, and can accurately indicate the spatial direction of the PUSCH scheduled by DCI format 0_0, which improves system stability.
  • the terminal device is provided with second configuration information, that is, pucch-ConfigurationList, and the second configuration information is subordinate to dedicated parameters configuration information of the uplink bandwidth part (UL BWP).
  • the second configuration information has two sets of PUCCH configuration information (pucch-Config), and the two sets of PUCCH configuration information (pucch-Config) include, for example, a first set of PUCCH configuration information (pucch-Config) and a second set of PUCCH configuration information.
  • Information (pucch-Config).
  • the terminal device may transmit the PUSCH scheduled by DCI format 0_0 according to the spatial relationship of the first group of PUCCH configuration information (pucch-Config).
  • the terminal device may send the PUSCH scheduled by DCI format 0_0 according to the spatial relationship of the PUCCH resource with the smallest ID in the first group of PUCCH configuration information (pucch-Config) in the pucch-ConfigurationList.
  • the spatial configuration information is, for example, PUCCH-SpatialRelationInfo.
  • Example 5 when the terminal device is provided with a pucch-ConfigurationList including two sets of PUCCH configuration information, the terminal device obtains the DCI format according to the configuration information pucch-ConfigurationList in the BWP-UplinkDedicated.
  • the spatial direction of the PUSCH scheduled by 0_0 so as to avoid the problem of ambiguity in the spatial relationship indication of the PUSCH scheduled by DCI format 0_0, and can accurately indicate the spatial direction of the PUSCH scheduled by DCI format 0_0, which improves system stability.
  • the terminal device is provided with second configuration information, that is, pucch-ConfigurationList, and the second configuration information is subordinated to the dedicated parameter configuration information BWP-UplinkDedicated of the uplink bandwidth part (UL BWP).
  • the second configuration information has two sets of PUCCH configuration information (pucch-Config), and the two sets of PUCCH configuration information (pucch-Config) include, for example, a first set of PUCCH configuration information (pucch-Config) and a second set of PUCCH configuration information.
  • Information (pucch-Config) is, for example, a first set of PUCCH configuration information (pucch-Config) and a second set of PUCCH configuration information.
  • the terminal device may transmit the PUSCH scheduled by DCI format 0_0 according to the spatial relationship of the second group of PUCCH configuration information (pucch-Config).
  • the terminal device may send the PUSCH scheduled by DCI format 0_0 according to the spatial relationship of the PUCCH resource with the smallest ID in the second group of PUCCH configuration information (pucch-Config) in the pucch-ConfigurationList.
  • the spatial configuration information is, for example, PUCCH-SpatialRelationInfo.
  • Example 6 when the terminal device is provided with a pucch-ConfigurationList that includes two sets of PUCCH configuration information, the terminal device obtains the DCI format according to the configuration information pucch-ConfigurationList in the BWP-UplinkDedicated.
  • the spatial direction of the PUSCH scheduled by 0_0 so as to avoid the problem of ambiguity in the spatial relationship indication of the PUSCH scheduled by DCI format 0_0, and can accurately indicate the spatial direction of the PUSCH scheduled by DCI format 0_0, which improves system stability.
  • the terminal device may be configured with the first configuration information by the network device, and the first configuration information may be, for example, dedicated parameters (dedicated parameters) configuration information subordinate to the uplink bandwidth part (UL BWP) PUCCH configuration information (pucch-Config) of BWP-UplinkDedicated.
  • the terminal device may not be configured with the first configuration information by the network device.
  • the physical uplink shared channel (PUSCH) scheduled by the downlink control signal format 0_0 (DCI format 0_0) can be transmitted according to the spatial relationship of the PUCCH configuration information corresponding to the first configuration information or the second configuration information. ), therefore, it is possible to avoid the problem of ambiguity in the indication of the spatial relationship of the PUSCH scheduled by DCI format 0_0, thereby accurately indicating the spatial relationship.
  • the second aspect of the embodiments of the present application relates to a method for sending an uplink signal, which is applied to a terminal device, such as the terminal device 102.
  • FIG. 4 is a schematic diagram of the uplink signal sending method of the second aspect of the embodiments of the present application. As shown in FIG. 4, the uplink signal sending method includes:
  • Operation 401 Configure first configuration information related to a physical uplink control channel (PUCCH) by a network device;
  • Operation 402 According to the power control reference signal of the physical uplink control channel (PUCCH) configuration information corresponding to the first configuration information, transmit the physical data scheduled by the downlink control signal format 0_0 (DCI format 0_0) on a cell (cell). Uplink shared channel (PUSCH).
  • PUCCH physical uplink control channel
  • the physical uplink shared channel (PUSCH) scheduled by the downlink control signal format 0_0 (DCI format 0_0) can be transmitted according to the power control reference signal of the PUCCH configuration information corresponding to the first configuration information. Therefore, when the terminal device has the ability to assemble or generate at least two hybrid automatic repeat request-acknowledgement codebooks (HARQ-ACK codebook) at the same time, it can also prevent the DCI format 0_0 scheduled PUSCH from appearing in the power control reference signal indicator. Problem, which accurately indicates the power control reference signal.
  • HARQ-ACK codebook hybrid automatic repeat request-acknowledgement codebooks
  • the power control reference signal may be a reference signal used for downlink path loss estimation.
  • the first configuration information configured in operation 401 is subordinate to the dedicated parameters configuration information of the active uplink bandwidth part (UL BWP) of the cell, wherein the dedicated parameters of the uplink bandwidth part are
  • the parameter configuration information corresponds to, for example, BWP-UplinkDedicated.
  • the first configuration information may be dedicated PUCCH configuration information of the uplink bandwidth part, for example, pucch-Config subordinate to BWP-UplinkDedicated.
  • the first configuration information may include a PUCCH configuration information list (for example, resourceToAddModList), and the list may add PUCCH resources to the uplink bandwidth part.
  • the first configuration information may include another PUCCH configuration information list (for example, resourceToReleaseList), and the list may release PUCCH resources for the uplink bandwidth part.
  • the first configuration information may correspond to one or more than one PUCCH resource. Among them, each PUCCH resource has (will be configured) a corresponding identification number (ID).
  • the terminal device may send the downlink control signal format according to the power control reference signal of the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) corresponding to the first configuration information.
  • PUCCH physical uplink control channel
  • ID the smallest identification number
  • 0_0 DCI format 0_0 scheduled physical uplink shared channel (PUSCH).
  • the terminal device may use the identification number ( ID) The power control reference signal of the smallest physical uplink control channel (PUCCH) resource, and transmits the physical uplink shared channel (PUSCH) scheduled by the downlink control signal format 0_0 (DCI format 0_0).
  • ID The power control reference signal of the smallest physical uplink control channel (PUCCH) resource
  • PUSCH physical uplink shared channel
  • the terminal device can use the same power control reference signal index (index) of the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) corresponding to the first configuration information.
  • the IE corresponding to the PUCCH power control parameter is, for example, PUCCH-SpatialRelationInfo.
  • the uplink signal sending method further includes:
  • Operation 403 Send a report message to the network device, and the report message reports to the network device that the terminal device has the ability to simultaneously assemble or generate at least two hybrid automatic repeat request-acknowledgement codebooks (HARQ-ACK codebook).
  • HARQ-ACK codebook hybrid automatic repeat request-acknowledgement codebooks
  • the terminal device can report to the network device that the terminal device has the ability to assemble or generate at least two hybrid automatic repeat request-acknowledgement codebooks (HARQ-ACK codebook) at the same time, so that the network device can configure the terminal device
  • HARQ-ACK codebook hybrid automatic repeat request-acknowledgement codebooks
  • the second configuration information refers to physical uplink control channel (PUCCH) configuration information used for (for) at least two simultaneously assembled (simultaneous constructed) hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebooks (codebook) .
  • PUCCH physical uplink control channel
  • HARQ-ACK hybrid automatic repeat request-acknowledgement
  • the second configuration information is subordinate to dedicated parameters (dedicated parameters) configuration information of the active uplink bandwidth part (active UL BWP) of the cell.
  • the second configuration information may be a dedicated PUCCH configuration information list of the uplink bandwidth part, for example, pucch-ConfigurationList subordinate to BWP-UplinkDedicated.
  • the second configuration information may have at least one set of PUCCH configuration information, each set of PUCCH configuration information (similar to the first configuration information) may correspond to one or more than one PUCCH resource, and each PUCCH resource has (will Configured) the corresponding identification number (ID).
  • the second configuration information may have one set of PUCCH configuration information; for another example, the second configuration information may have two or more sets of PUCCH configuration information, and each set of PUCCH configuration information may correspond to one or more than one PUCCH configuration information.
  • PUCCH resources each PUCCH resource has (will be configured) a corresponding identification number (ID).
  • ID identification number
  • each group of PUCCH configuration information corresponds to a different priority.
  • the first group of PUCCH configuration information corresponds to a low priority (for example, the priority index is 0), and the second group of PUCCH configuration information corresponds to a high priority (for example, , The priority index is 1).
  • the priority refers to the physical layer priority.
  • the network device may configure the second configuration information to the terminal device, or may not configure the second configuration information to the terminal device.
  • the uplink signal sending method shown in FIG. 4 will be illustrated with examples through example one, example two and example three.
  • the first configuration information may be pucch-Config subordinate to BWP-UplinkDedicated
  • the second configuration information may be pucch-ConfigurationList subordinate to BWP-UplinkDedicated.
  • the pucch-ConfigurationList may include one or two sets of PUCCH configuration information.
  • the PUCCH configuration information is, for example, represented as PUCCH-Config.
  • the PUCCH configuration information is an IE used to configure terminal device specific PUCCH parameters (UE specific PUCCH parameters).
  • the terminal device is provided with first configuration information, namely pucch-Config, where the first configuration information is subordinated to the dedicated parameter configuration information BWP-UplinkDedicated of the uplink bandwidth part (UL BWP); and, the terminal The device is not provided with the second configuration information, that is, pucch-ConfigurationList is not configured in the BWP-UplinkDedicated.
  • the terminal device may control the power according to the power control reference signal of the PUCCH resource with the smallest ID corresponding to the pucch-Config (In other words, according to the power control reference signal having the same index as the power control reference signal of the PUCCH resource with the smallest ID corresponding to the pucch-Config), the PUSCH scheduled by the DCI format 0_0 is transmitted.
  • the terminal device when the terminal device can be provided with pucch-ConfigurationList but not provided with pucch-ConfigurationList, the terminal device obtains the power control reference of the PUSCH scheduled by DCI format 0_0 according to the configuration information pucch-Config in BWP-UplinkDedicated Therefore, the problem of ambiguity in the indication of the power control reference signal for the PUSCH scheduled by the DCI format 0_0 can be avoided, and the power control reference signal of the PUSCH scheduled by the DCI format 0_0 can be accurately indicated, thereby improving system stability.
  • the terminal device is provided with first configuration information, namely pucch-Config, where the first configuration information is subordinate to dedicated parameters configuration information (BWP-UplinkDedicated) of the uplink bandwidth part (UL BWP).
  • the terminal device may also be provided with second configuration information, that is, the terminal device is configured with pucch-ConfigurationList in the BWP-UplinkDedicated.
  • the second configuration information only has one set of PUCCH configuration information (pucch-Config).
  • the terminal device may control the power according to the power control reference signal of the PUCCH resource with the smallest ID corresponding to the pucch-Config (In other words, according to the power control reference signal having the same index as the power control reference signal of the PUCCH resource with the smallest ID corresponding to the pucch-Config), the PUSCH scheduled by the DCI format 0_0 is transmitted.
  • the terminal device when the terminal device is provided with a pucch-ConfigurationList that includes only one set of PUCCH configuration information, the terminal device obtains the power control reference for the PUSCH scheduled by DCI format 0_0 according to the configuration information pucch-Config in the BWP-UplinkDedicated Therefore, the problem of ambiguity in the indication of the power control reference signal for the PUSCH scheduled by the DCI format 0_0 can be avoided, and the power control reference signal of the PUSCH scheduled by the DCI format 0_0 can be accurately indicated, thereby improving system stability.
  • the terminal device is provided with first configuration information, namely pucch-Config, where the first configuration information is subordinated to dedicated parameters (in BWP-UplinkDedicated) of the uplink bandwidth part (UL BWP).
  • the terminal device may also be provided with second configuration information, that is, the terminal device is configured with pucch-ConfigurationList in the BWP-UplinkDedicated.
  • the second configuration information has two sets of PUCCH configuration information (pucch-Config).
  • the terminal device may use the PUCCH resource with the smallest ID corresponding to the pucch-Config configured in the BWP-UplinkDedicated (Or, according to the power control reference signal with the same index according to the power control reference signal of the PUCCH resource with the smallest ID corresponding to the pucch-Config), the PUSCH scheduled by DCI format 0_0 is sent.
  • the terminal device when the terminal device is provided with a pucch-ConfigurationList including two sets of PUCCH configuration information, the terminal device obtains the power control reference signal of the PUSCH scheduled by DCI format 0_0 according to the pucch-Config configured in the BWP-UplinkDedicated, In this way, the problem of ambiguity in the indication of the power control reference signal for the PUSCH scheduled by the DCI format 0_0 can be avoided, and the power control reference signal of the PUSCH scheduled by the DCI format 0_0 can be accurately indicated, thereby improving system stability.
  • FIG. 5 is another schematic diagram of the uplink signal sending method of the second aspect of the embodiments of the present application. As shown in FIG. 5, the uplink signal sending method includes:
  • Operation 501 The network device configures second configuration information related to the physical uplink control channel (PUCCH), where the second configuration information refers to at least two simultaneous constructed (simultaneous constructed) hybrid automatic repeat request-confirmation (HARQ-ACK) physical uplink control channel (PUCCH) configuration information of the codebook; and
  • Operation 502 According to the power control reference signal (spatial relation) of the physical uplink control channel (PUCCH) configuration information corresponding to the second configuration information, send the downlink control signal format 0_0 (DCI format 0_0) in a cell (DCI format 0_0). ) Scheduled physical uplink shared channel (PUSCH).
  • PUCCH physical uplink control channel
  • the physical uplink shared channel (PUSCH) scheduled by the downlink control signal format 0_0 (DCI format 0_0) can be transmitted according to the power control reference signal of the PUCCH configuration information corresponding to the second configuration information. It can avoid the problem of ambiguity in the indication of the power control reference signal in the PUSCH scheduled by the DCI format 0_0, so as to accurately indicate the power control reference signal.
  • the description of the second configuration information is the same as the foregoing description of the second aspect of the embodiment of the present application.
  • the terminal device can generate at least two hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebooks.
  • the terminal device may generate two HARQ-ACK codebooks according to configuration information, where the configuration information is, for example, a physical downlink shared channel hybrid automatic repeat request confirmation codebook list (pdsch-HARQ-ACK-Codebook-List).
  • Information refers to the PUCCH configuration information used for at least two simultaneously assembled (simultaneous constructed) HARQ-ACK codebooks in the configuration information of cell-group specific L1 parameters.
  • the configuration information (pdsch-HARQ-ACK-Codebook-List) is different from the second configuration information.
  • the configuration information may separately determine the type of each HARQ-ACK codebook (the type is, for example, dynamic or semi-static).
  • the terminal device may use the identification number (ID) corresponding to the set of physical uplink control channel (PUCCH) configuration information of the second configuration information.
  • ID the identification number
  • the power control reference signal of the smallest physical uplink control channel (PUCCH) resource is used to transmit the physical uplink shared channel (PUSCH) scheduled by the downlink control signal format 0_0 (DCI format 0_0).
  • the terminal device may use the identification number ( ID) The power control reference signal of the smallest physical uplink control channel (PUCCH) resource, and transmits the physical uplink shared channel (PUSCH) scheduled by the downlink control signal format 0_0 (DCI format 0_0).
  • ID The power control reference signal of the smallest physical uplink control channel (PUCCH) resource, and transmits the physical uplink shared channel (PUSCH) scheduled by the downlink control signal format 0_0 (DCI format 0_0).
  • the terminal device In the case where the second configuration information includes two sets of physical uplink control channel (PUCCH) configuration information, the terminal device according to the first set of physical uplink control channel (PUCCH) configuration information in the two sets of physical uplink control channel (PUCCH) configuration information of the second configuration information (PUCCH) configuration information or the power control reference signal of the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) corresponding to the second group of physical uplink control channel (PUCCH) configuration information, sent by the downlink control signal format 0_0( DCI format 0_0) Scheduled physical uplink shared channel (PUSCH).
  • PUCCH physical uplink control channel
  • the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) corresponding to the first group of physical uplink control channel (PUCCH) configuration information or the second group of physical uplink control channel (PUCCH) configuration information is configured
  • the terminal device can use the smallest identification number (ID) corresponding to the first set of physical uplink control channel (PUCCH) configuration information or the second set of physical uplink control channel (PUCCH) configuration information.
  • the power control reference signal of the physical uplink control channel (PUCCH) resource transmits the physical uplink shared channel (PUSCH) scheduled by the downlink control signal format 0_0 (DCI format 0_0).
  • the terminal device may be configured with the first configuration information or not configured with the first configuration information by the network device.
  • the description of the first configuration information is the same as the foregoing description of the second aspect of the embodiment of the present application.
  • the uplink signal sending method shown in FIG. 3 will be illustrated by examples four, five and six.
  • the second configuration information may be pucch-ConfigurationList subordinate to BWP-UplinkDedicated.
  • the pucch-ConfigurationList may include one or two sets of PUCCH configuration information.
  • the PUCCH configuration information is, for example, represented as PUCCH-Config.
  • the PUCCH configuration information is an IE used to configure terminal device specific PUCCH parameters (UE specific PUCCH parameters).
  • the terminal device is provided with second configuration information, that is, pucch-ConfigurationList, and the second configuration information is subordinate to dedicated parameters configuration information of the uplink bandwidth part (UL BWP).
  • the second configuration information only has one set of PUCCH configuration information (pucch-Config).
  • the terminal device may perform the operation according to the pucch- The power control reference signal of the PUCCH resource with the smallest ID in the group of PUCCH configuration information (pucch-Config) in the ConfigurationList (or, according to the power control reference signal of the PUCCH resource with the smallest ID corresponding to the group of pucch-Config) Power control reference signals with the same index), and transmit the PUSCH scheduled by DCI format 0_0.
  • Example 4 when the terminal device is provided with a pucch-ConfigurationList that includes only one set of PUCCH configuration information, the terminal device obtains the DCI format according to the configuration information pucch-ConfigurationList in the BWP-UplinkDedicated. 0_0 scheduled PUSCH power control reference signal, so as to avoid DCI format 0_0 scheduled PUSCH power control reference signal indication ambiguity, can accurately indicate DCI format 0_0 scheduled PUSCH power control reference signal, improve system stability.
  • the terminal device is provided with second configuration information, that is, pucch-ConfigurationList, and the second configuration information is subordinate to dedicated parameters configuration information of the uplink bandwidth part (UL BWP).
  • the second configuration information has two sets of PUCCH configuration information (pucch-Config), and the two sets of PUCCH configuration information (pucch-Config) include, for example, a first set of PUCCH configuration information (pucch-Config) and a second set of PUCCH configuration information.
  • Information (pucch-Config).
  • the terminal device may transmit the PUSCH scheduled by DCI format 0_0 according to the power control reference signal of the first group of PUCCH configuration information (pucch-Config).
  • the terminal device may perform according to the pucch-ConfigurationList
  • the power control reference signal of the PUCCH resource with the smallest ID in the first group of PUCCH configuration information (pucch-Config) (or, according to the power control reference signal of the PUCCH resource with the smallest ID corresponding to the first group of pucch-Config) Signals have the same index power control reference signal), and send the PUSCH scheduled by DCI format 0_0.
  • Example 5 when the terminal device is provided with a pucch-ConfigurationList including two sets of PUCCH configuration information, the terminal device obtains the DCI format according to the configuration information pucch-ConfigurationList in the BWP-UplinkDedicated. 0_0 scheduled PUSCH power control reference signal, so as to avoid DCI format 0_0 scheduled PUSCH power control reference signal indication ambiguity, can accurately indicate DCI format 0_0 scheduled PUSCH power control reference signal, improve system stability.
  • the terminal device is provided with second configuration information, that is, pucch-ConfigurationList, and the second configuration information is subordinate to the dedicated parameters configuration information BWP-UplinkDedicated of the uplink bandwidth part (UL BWP).
  • the second configuration information has two sets of PUCCH configuration information (pucch-Config), and the two sets of PUCCH configuration information (pucch-Config) include, for example, a first set of PUCCH configuration information (pucch-Config) and a second set of PUCCH configuration information.
  • Information (pucch-Config) is provided with second configuration information, that is, pucch-ConfigurationList, and the second configuration information is subordinate to the dedicated parameters configuration information BWP-UplinkDedicated of the uplink bandwidth part (UL BWP).
  • the terminal device may transmit the PUSCH scheduled by DCI format 0_0 according to the power control reference signal of the second group of PUCCH configuration information (pucch-Config).
  • the terminal device may perform the PUCCH configuration according to the pucch-
  • the power control reference signal of the PUCCH resource with the smallest ID in the second set of PUCCH configuration information (pucch-Config) in the ConfigurationList (or, according to the power control of the PUCCH resource with the smallest ID corresponding to the second set of pucch-Config)
  • the reference signal has a power control reference signal with the same index), and the PUSCH scheduled by DCI format 0_0 is sent.
  • Example 6 when the terminal device is provided with a pucch-ConfigurationList that includes two sets of PUCCH configuration information, the terminal device obtains the DCI format according to the configuration information pucch-ConfigurationList in the BWP-UplinkDedicated. 0_0 scheduled PUSCH power control reference signal, so as to avoid DCI format 0_0 scheduled PUSCH power control reference signal indication ambiguity, can accurately indicate DCI format 0_0 scheduled PUSCH power control reference signal, improve system stability.
  • the terminal device may be configured with the first configuration information by the network device, and the first configuration information may be, for example, dedicated parameters (dedicated parameters) configuration information subordinate to the uplink bandwidth part (UL BWP) PUCCH configuration information pucch-Config of BWP-UplinkDedicated.
  • the terminal device may not be configured with the first configuration information by the network device.
  • the physical uplink shared channel scheduled by the downlink control signal format 0_0 (DCI format 0_0) can be transmitted according to the power control reference signal of the PUCCH configuration information corresponding to the first configuration information or the second configuration information (PUSCH), thus, it is possible to avoid the problem of ambiguity in the indication of the power control reference signal in the PUSCH scheduled by DCI format 0_0, so as to accurately indicate the power control reference signal.
  • the third aspect of the embodiments of the present application relates to a method for receiving an uplink signal, which is applied to a network device, such as network device 101, which communicates with a terminal device.
  • the terminal device may have simultaneous assembly or generation of at least two hybrid automatic repeats.
  • Request-acknowledgement codebook (HARQ-ACK codebook) capability is provided.
  • FIG. 6 is a schematic diagram of the uplink signal receiving method of the third aspect of the embodiments of the present application. As shown in FIG. 6, the uplink signal sending method includes:
  • Operation 601 Configure first configuration information related to a physical uplink control channel (PUCCH) to a terminal device;
  • Operation 602 According to the spatial relation of the physical uplink control channel (PUCCH) configuration information corresponding to the first configuration information, in a cell, receive the downlink control signal format 0_0 (DCI format 0_0) scheduling The physical uplink shared channel (PUSCH).
  • PUCCH physical uplink control channel
  • the terminal device has the ability to assemble or generate at least two hybrid automatic repeat request-acknowledgement codebooks (HARQ-ACK codebook) at the same time, it can also avoid the problem of ambiguity in the spatial relationship indication of the PUSCH scheduled by DCI format 0_0, so as to be accurate To indicate the spatial relationship.
  • HARQ-ACK codebook hybrid automatic repeat request-acknowledgement codebooks
  • the first configuration information configured in operation 601 is subordinate to the dedicated parameters configuration information of the active uplink bandwidth part (UL BWP) of the cell, wherein the dedicated parameters of the uplink bandwidth part
  • the parameter configuration information corresponds to, for example, BWP-UplinkDedicated.
  • the first configuration information may be dedicated PUCCH configuration information of the uplink bandwidth part, for example, pucch-Config subordinate to BWP-UplinkDedicated.
  • the first configuration information may include a PUCCH configuration information list (for example, resourceToAddModList), and the list may add PUCCH resources to the uplink bandwidth part.
  • the first configuration information may include another PUCCH configuration information list (for example, resourceToReleaseList), and the list may release PUCCH resources for the uplink bandwidth part.
  • the first configuration information may correspond to one or more than one PUCCH resource. Among them, each PUCCH resource has (will be configured) a corresponding identification number (ID).
  • the network device may receive the downlink control signal format 0_0 ( DCI format 0_0) Scheduled physical uplink shared channel (PUSCH).
  • DCI format 0_0 Scheduled physical uplink shared channel
  • the network device when the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) corresponding to the first configuration information is configured with spatial setting or is applicable to the spatial relationship, the network device
  • the physical uplink shared channel (PUSCH) scheduled by the downlink control signal format 0_0 (DCI format 0_0) may be received according to the spatial relationship of the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) corresponding to the first configuration information.
  • the uplink signal sending method further includes:
  • Operation 603 Receive a report message from a terminal device, and the report message reports to the network device that the terminal device has the ability to simultaneously assemble or generate at least two hybrid automatic repeat request-acknowledgement codebooks (HARQ-ACK codebook).
  • HARQ-ACK codebook hybrid automatic repeat request-acknowledgement codebooks
  • the terminal device can report to the network device that the terminal device has the ability to assemble or generate at least two hybrid automatic repeat request-acknowledgement codebooks (HARQ-ACK codebook) at the same time, so that the network device can configure the terminal device
  • HARQ-ACK codebook hybrid automatic repeat request-acknowledgement codebooks
  • the second configuration information refers to physical uplink control channel (PUCCH) configuration information used for (for) at least two simultaneously assembled (simultaneous constructed) hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebooks (codebook) .
  • PUCCH physical uplink control channel
  • HARQ-ACK hybrid automatic repeat request-acknowledgement
  • the second configuration information is subordinate to dedicated parameters (dedicated parameters) configuration information of the active uplink bandwidth part (active UL BWP) of the cell.
  • the second configuration information may be a dedicated PUCCH configuration information list of the uplink bandwidth part, for example, pucch-ConfigurationList subordinate to BWP-UplinkDedicated.
  • the second configuration information may have at least one set of PUCCH configuration information, each set of PUCCH configuration information may correspond to one or more than one PUCCH resource, and each PUCCH resource has (will be configured) a corresponding identification number ( ID).
  • the second configuration information may have one set of PUCCH configuration information; for another example, the second configuration information may have two or more sets of PUCCH configuration information, and each set of PUCCH configuration information may correspond to one or more than one PUCCH configuration information.
  • PUCCH resources each PUCCH resource has (will be configured) a corresponding identification number (ID).
  • ID identification number
  • each group of PUCCH configuration information corresponds to a different priority.
  • the first group of PUCCH configuration information corresponds to a low priority (for example, the priority index is 0), and the second group of PUCCH configuration information corresponds to a high priority (for example, , The priority index is 1).
  • the priority refers to the physical layer priority.
  • the network device may configure the second configuration information to the terminal device, or may not configure the second configuration information to the terminal device.
  • the uplink signal sending method shown in FIG. 6 will be illustrated by examples of example one, example two, and example three.
  • the first configuration information may be pucch-Config subordinate to BWP-UplinkDedicated
  • the second configuration information may be pucch-ConfigurationList subordinate to BWP-UplinkDedicated.
  • the pucch-ConfigurationList may include one or two sets of PUCCH configuration information.
  • the PUCCH configuration information is represented as PUCCH-Config, for example, and the PUCCH configuration information is an IE used to configure terminal device specific PUCCH parameters (UE specific PUCCH parameters).
  • the network device provides first configuration information, that is, pucch-Config, to the terminal device, where the first configuration information is subordinate to dedicated parameters (BWP-UplinkDedicated) configuration information (BWP-UplinkDedicated) of the uplink bandwidth part (UL BWP) ; And, the network device does not provide the second configuration information to the terminal device, that is, pucch-ConfigurationList is not configured in the BWP-UplinkDedicated.
  • the network device can be configured according to the corresponding pucch-Config For the spatial relationship of the PUCCH resource with the smallest ID, receive the PUSCH scheduled by DCI format 0_0.
  • the spatial configuration information is, for example, PUCCH-SpatialRelationInfo.
  • the network device obtains the spatial direction of the PUSCH scheduled by DCI format 0_0 according to the configuration information pucch-Config in BWP-UplinkDedicated, In this way, the problem of ambiguity in the indication of the spatial relationship of the PUSCH scheduled by the DCI format 0_0 can be avoided, and the spatial direction of the PUSCH scheduled by the DCI format 0_0 can be accurately indicated, thereby improving system stability.
  • the network device provides first configuration information, that is, pucch-Config, to the terminal device, where the first configuration information is subordinate to dedicated parameters (BWP-UplinkDedicated) configuration information (BWP-UplinkDedicated) of the uplink bandwidth part (UL BWP) .
  • the network device may also provide second configuration information to the terminal device, that is, configure pucch-ConfigurationList in the BWP-UplinkDedicated.
  • the second configuration information only has one set of PUCCH configuration information (pucch-Config).
  • the network device can be configured according to the pucch-Config.
  • the PUSCH scheduled by DCI format 0_0 is sent and received.
  • the spatial configuration information is, for example, PUCCH-SpatialRelationInfo.
  • the network device when the network device provides the terminal device with pucch-ConfigurationList including only one set of PUCCH configuration information, the network device obtains the space of the PUSCH scheduled by DCI format 0_0 according to the configuration information pucch-Config in the BWP-UplinkDedicated Direction, so as to avoid the problem of ambiguity in the spatial relationship indication of the PUSCH scheduled by DCI format 0_0, can accurately indicate the spatial direction of the PUSCH scheduled by DCI format 0_0, and improve system stability.
  • the network device provides first configuration information, namely pucch-Config, to the terminal device, where the first configuration information is subordinate to the dedicated parameters of the uplink bandwidth part (UL BWP) configuration information (in BWP-UplinkDedicated) ).
  • the network device may also provide second configuration information to the terminal device, that is, configure pucch-ConfigurationList in the BWP-UplinkDedicated.
  • the second configuration information has two sets of PUCCH configuration information (pucch-Config).
  • the network device can be configured according to the pucch-Config.
  • the spatial configuration information is, for example, PUCCH-SpatialRelationInfo.
  • Example 3 when the network device provides the terminal device with a pucch-ConfigurationList that includes two sets of PUCCH configuration information, the network device obtains the spatial direction of the PUSCH scheduled by DCI format 0_0 according to the pucch-Config configured in BWP-UplinkDedicated, thereby The problem of ambiguity in the spatial relationship indication of the PUSCH scheduled by DCI format 0_0 is avoided, and the spatial direction of the PUSCH scheduled by DCI format 0_0 can be accurately indicated, which improves system stability.
  • FIG. 7 is another schematic diagram of the uplink signal receiving method of the third aspect of the embodiments of the present application. As shown in FIG. 7, the uplink signal sending method includes:
  • Operation 701 Configure second configuration information related to the physical uplink control channel (PUCCH) to the terminal device, where the second configuration information refers to at least two simultaneous constructed (simultaneous constructed) hybrid automatic repeat request-confirmation (HARQ-ACK) physical uplink control channel (PUCCH) configuration information of the codebook; and
  • Operation 702 According to the spatial relation of the physical uplink control channel (PUCCH) configuration information corresponding to the second configuration information, in a cell, receive a downlink control signal format 0_0 (DCI format 0_0) scheduling The physical uplink shared channel (PUSCH).
  • PUCCH physical uplink control channel
  • the physical uplink shared channel (PUSCH) scheduled by the downlink control signal format 0_0 can be received according to the spatial relationship of the PUCCH configuration information corresponding to the second configuration information, and it can also avoid DCI format 0_0 scheduled PUSCH has the problem of ambiguity in the indication of the spatial relationship, thereby accurately indicating the spatial relationship.
  • the terminal device can generate at least two hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebooks.
  • the terminal device may generate two HARQ-ACK codebooks according to configuration information, where the configuration information is, for example, a physical downlink shared channel hybrid automatic repeat request confirmation codebook list (pdsch-HARQ-ACK-Codebook-List).
  • Information refers to the PUCCH configuration information used for at least two simultaneously assembled (simultaneous constructed) HARQ-ACK codebooks in the configuration information of cell-group specific L1 parameters.
  • the configuration information (pdsch-HARQ-ACK-Codebook-List) is different from the second configuration information.
  • the configuration information may separately determine the type of each HARQ-ACK codebook (the type is, for example, dynamic or semi-static).
  • the network device may use the identification number (ID) corresponding to the set of physical uplink control channel (PUCCH) configuration information of the second configuration information.
  • ID The spatial relationship of the smallest physical uplink control channel (PUCCH) resource, receiving the physical uplink shared channel (PUSCH) scheduled by the downlink control signal format 0_0 (DCI format 0_0).
  • the network The device can receive the physical uplink shared channel (PUSCH) scheduled by the downlink control signal format 0_0 (DCI format 0_0) according to the spatial relationship of the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) corresponding to the second configuration information .
  • PUSCH physical uplink shared channel
  • the network device uses the first set of physical uplink control channels in the two sets of physical uplink control channel (PUCCH) configuration information according to the second configuration information (PUCCH) configuration information or the spatial relationship of the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) corresponding to the second group of physical uplink control channel (PUCCH) configuration information, received by the downlink control signal format 0_0 (DCI format 0_0) Scheduled physical uplink shared channel (PUSCH).
  • PUCCH physical uplink control channel
  • the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) corresponding to the first group of physical uplink control channel (PUCCH) configuration information or the second group of physical uplink control channel (PUCCH) configuration information is configured If the spatial configuration information or is applicable to the spatial relationship, the network device can correspond to the first group of physical uplink control channel (PUCCH) configuration information or the second group of physical uplink control channel (PUCCH) configuration information
  • the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) receives the physical uplink shared channel (PUSCH) scheduled by the downlink control signal format 0_0 (DCI format 0_0).
  • the network device may configure the first configuration information to the terminal device or not configure the first configuration information.
  • the description of the first configuration information is the same as the foregoing description of the third aspect of the embodiment of the present application.
  • the method for receiving the uplink signal shown in FIG. 7 will be illustrated by examples four, five and six.
  • the second configuration information may be pucch-ConfigurationList subordinate to BWP-UplinkDedicated.
  • the pucch-ConfigurationList may include one or two sets of PUCCH configuration information.
  • the PUCCH configuration information is, for example, represented as PUCCH-Config.
  • the PUCCH configuration information is an IE used to configure terminal device specific PUCCH parameters (UE specific PUCCH parameters).
  • the network device provides second configuration information, that is, pucch-ConfigurationList, to the terminal device, and the second configuration information is subordinate to dedicated parameters configuration information of the uplink bandwidth part (UL BWP).
  • the second configuration information only has one set of PUCCH configuration information (pucch-Config).
  • the PUCCH resource with the smallest ID in the set of PUCCH configuration information (pucch-Config) in the pucch-ConfigurationList is configured with spatial setting or is applicable to the spatial relationship
  • the network device may receive the PUSCH scheduled by the DCI format 0_0 according to the spatial relationship of the PUCCH resource with the smallest ID in the set of PUCCH configuration information (pucch-Config) in the pucch-ConfigurationList.
  • the spatial configuration information (spatial setting) is, for example, PUCCH-SpatialRelationInfo.
  • Example 4 when the network device provides a pucch-ConfigurationList that includes only one set of PUCCH configuration information, the network device obtains the set of PUCCH configuration information from the configuration information pucch-ConfigurationList in the BWP-UplinkDedicated by DCI format 0_0.
  • the spatial direction of the scheduled PUSCH so as to avoid the problem of ambiguity in the spatial relationship indication of the PUSCH scheduled by DCI format 0_0, can accurately indicate the spatial direction of the PUSCH scheduled by DCI format 0_0, and improve system stability.
  • the network device provides second configuration information, that is, pucch-ConfigurationList, and the second configuration information is subordinate to dedicated parameter configuration information of the uplink bandwidth part (UL BWP).
  • the second configuration information has two sets of PUCCH configuration information (pucch-Config), and the two sets of PUCCH configuration information (pucch-Config) include, for example, a first set of PUCCH configuration information (pucch-Config) and a second set of PUCCH configuration information.
  • Information (pucch-Config).
  • the network device may receive the PUSCH scheduled by the DCI format 0_0 according to the spatial relationship of the first group of PUCCH configuration information (pucch-Config).
  • the network device may receive the PUSCH scheduled by the DCI format 0_0 according to the spatial relationship of the PUCCH resource with the smallest ID in the first group of PUCCH configuration information (pucch-Config) in the pucch-ConfigurationList.
  • the spatial configuration information is, for example, PUCCH-SpatialRelationInfo.
  • Example 5 when the network device provides a pucch-ConfigurationList that includes two sets of PUCCH configuration information, the network device obtains the first group of PUCCH configuration information from the configuration information pucch-ConfigurationList in the BWP-UplinkDedicated by DCI format 0_0.
  • the spatial direction of the scheduled PUSCH so as to avoid the problem of ambiguity in the spatial relationship indication of the PUSCH scheduled by DCI format 0_0, can accurately indicate the spatial direction of the PUSCH scheduled by DCI format 0_0, and improve system stability.
  • the network device provides second configuration information, that is, pucch-ConfigurationList, and the second configuration information is subordinate to dedicated parameter configuration information of the uplink bandwidth part (UL BWP).
  • the second configuration information has two sets of PUCCH configuration information (pucch-Config), and the two sets of PUCCH configuration information (pucch-Config) include, for example, a first set of PUCCH configuration information (pucch-Config) and a second set of PUCCH configuration information.
  • Information (pucch-Config).
  • the network device device may receive the PUSCH scheduled by the DCI format 0_0 according to the spatial relationship of the second group of PUCCH configuration information (pucch-Config).
  • the network device may receive the PUSCH scheduled by the DCI format 0_0 according to the spatial relationship of the PUCCH resource with the smallest ID in the second group of PUCCH configuration information (pucch-Config) in the pucch-ConfigurationList.
  • the spatial configuration information is, for example, PUCCH-SpatialRelationInfo.
  • Example 6 when the network device provides a pucch-ConfigurationList that includes two sets of PUCCH configuration information, the network device obtains the second set of PUCCH configuration information from the configuration information pucch-ConfigurationList in the BWP-UplinkDedicated by DCI format 0_0.
  • the spatial direction of the scheduled PUSCH so as to avoid the problem of ambiguity in the spatial relationship indication of the PUSCH scheduled by DCI format 0_0, can accurately indicate the spatial direction of the PUSCH scheduled by DCI format 0_0, and improve system stability.
  • the network device may configure the first configuration information to the terminal device, and the first configuration information may be, for example, dedicated parameters (dedicated parameters) configuration information subordinate to the uplink bandwidth part (UL BWP) PUCCH configuration information (pucch-Config) of BWP-UplinkDedicated.
  • the network device may not configure the terminal device with the first configuration information.
  • PUSCH physical uplink shared channel
  • DCI format 0_0 downlink control signal format 0_0
  • the fourth aspect of the embodiments of the present application relates to a method for sending an uplink signal, which is applied to a network device, such as the network device 101.
  • FIG. 8 is a schematic diagram of the uplink signal receiving method according to the fourth aspect of the embodiments of the present application. As shown in FIG. 8, the uplink signal receiving method includes:
  • Operation 801 Configure a terminal device with first configuration information related to a physical uplink control channel (PUCCH); and
  • Operation 802 According to the power control reference signal (spatial relation) of the physical uplink control channel (PUCCH) configuration information corresponding to the first configuration information, receive the downlink control signal format 0_0 (DCI format 0_0) in a cell (DCI format 0_0). ) Scheduled physical uplink shared channel (PUSCH).
  • PUCCH physical uplink control channel
  • the terminal device has the ability to assemble or generate at least two hybrid automatic repeat request-acknowledgement codebooks (HARQ-ACK codebook) at the same time, it can also prevent the DCI format 0_0 scheduled PUSCH from appearing in the power control reference signal indicator. Problem, which accurately indicates the power control reference signal.
  • HARQ-ACK codebook hybrid automatic repeat request-acknowledgement codebooks
  • the power control reference signal may be a reference signal used for downlink path loss estimation.
  • the first configuration information configured in operation 801 is subordinate to the dedicated parameters configuration information of the active uplink bandwidth part (UL BWP) of the cell, wherein the dedicated parameters of the uplink bandwidth part
  • the parameter configuration information corresponds to, for example, BWP-UplinkDedicated.
  • the first configuration information may be dedicated PUCCH configuration information of the uplink bandwidth part, for example, pucch-Config subordinate to BWP-UplinkDedicated.
  • the first configuration information may include a PUCCH configuration information list (for example, resourceToAddModList), and the list may add PUCCH resources to the uplink bandwidth part.
  • the first configuration information may include another PUCCH configuration information list (for example, resourceToReleaseList), and the list may release PUCCH resources for the uplink bandwidth part.
  • the first configuration information may correspond to one or more than one PUCCH resource. Among them, each PUCCH resource has (will be configured) a corresponding identification number (ID).
  • the terminal device may receive the downlink control signal format according to the power control reference signal of the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) corresponding to the first configuration information.
  • PUCCH physical uplink control channel
  • ID the smallest identification number
  • 0_0 DCI format 0_0
  • PUSCH physical uplink shared channel
  • the terminal device may use the identification number ( ID) The power control reference signal of the smallest physical uplink control channel (PUCCH) resource, receiving the physical uplink shared channel (PUSCH) scheduled by the downlink control signal format 0_0 (DCI format 0_0).
  • ID The power control reference signal of the smallest physical uplink control channel (PUCCH) resource, receiving the physical uplink shared channel (PUSCH) scheduled by the downlink control signal format 0_0 (DCI format 0_0).
  • the terminal device can use the same power control reference signal index (index) of the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) corresponding to the first configuration information.
  • the IE corresponding to the PUCCH power control parameter is, for example, PUCCH-SpatialRelationInfo.
  • the uplink signal receiving method further includes:
  • Operation 803 Receive a report message from a terminal device, and the report message reports to the network device that the terminal device has the ability to simultaneously assemble or generate at least two hybrid automatic repeat request-acknowledgement codebooks (HARQ-ACK codebook).
  • HARQ-ACK codebook hybrid automatic repeat request-acknowledgement codebooks
  • the terminal device can report to the network device that the terminal device has the ability to assemble or generate at least two hybrid automatic repeat request-acknowledgement codebooks (HARQ-ACK codebook) at the same time, so that the network device can configure the terminal device
  • HARQ-ACK codebook hybrid automatic repeat request-acknowledgement codebooks
  • the second configuration information refers to physical uplink control channel (PUCCH) configuration information used for (for) at least two simultaneously assembled (simultaneous constructed) hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebooks (codebook) .
  • PUCCH physical uplink control channel
  • HARQ-ACK hybrid automatic repeat request-acknowledgement
  • the second configuration information is subordinate to dedicated parameters (dedicated parameters) configuration information of the active uplink bandwidth part (active UL BWP) of the cell.
  • the second configuration information may be a dedicated PUCCH configuration information list of the uplink bandwidth part, for example, pucch-ConfigurationList subordinate to BWP-UplinkDedicated.
  • the second configuration information may have at least one set of PUCCH configuration information, each set of PUCCH configuration information (similar to the first configuration information) may correspond to one or more than one PUCCH resource, and each PUCCH resource has (will Configured) the corresponding identification number (ID).
  • the second configuration information may have one set of PUCCH configuration information; for another example, the second configuration information may have two or more sets of PUCCH configuration information, and each set of PUCCH configuration information may correspond to one or more than one PUCCH configuration information.
  • PUCCH resources each PUCCH resource has (will be configured) a corresponding identification number (ID).
  • ID identification number
  • each group of PUCCH configuration information corresponds to a different priority.
  • the first group of PUCCH configuration information corresponds to a low priority (for example, the priority index is 0), and the second group of PUCCH configuration information corresponds to a high priority (for example, , The priority index is 1).
  • the priority refers to the physical layer priority.
  • the network device may configure the second configuration information to the terminal device, or may not configure the second configuration information to the terminal device.
  • the uplink signal receiving method shown in FIG. 8 will be illustrated with examples through example one, example two and example three.
  • the first configuration information may be pucch-Config subordinate to BWP-UplinkDedicated
  • the second configuration information may be pucch-ConfigurationList subordinate to BWP-UplinkDedicated.
  • the pucch-ConfigurationList may include one or two sets of PUCCH configuration information.
  • the PUCCH configuration information is represented as PUCCH-Config, for example, and the PUCCH configuration information is an IE used to configure terminal device specific PUCCH parameters (UE specific PUCCH parameters).
  • the network device provides first configuration information, that is, pucch-Config, to the terminal device, where the first configuration information is subordinate to the dedicated parameters (BWP-UplinkDedicated) configuration information (BWP-UplinkDedicated) of the uplink bandwidth part (UL BWP) ; And, the network device does not provide the second configuration information, that is, pucch-ConfigurationList is not configured in the BWP-UplinkDedicated.
  • first configuration information that is, pucch-Config
  • the network device may control the power according to the power control reference signal of the PUCCH resource with the smallest ID corresponding to the pucch-Config (In other words, according to the power control reference signal having the same index as the power control reference signal of the PUCCH resource with the smallest ID corresponding to the pucch-Config), receive the PUSCH scheduled by the DCI format 0_0.
  • the network device when the terminal device can be provided with pucch-ConfigurationList but not provided with pucch-ConfigurationList, the network device obtains the power control reference signal of the PUSCH scheduled by DCI format 0_0 according to pucch-Config, thereby avoiding DCI format 0_0
  • the scheduled PUSCH has the problem of ambiguous power control reference signal indication, which can accurately indicate the power control reference signal of the PUSCH scheduled by DCI format 0_0, which improves system stability.
  • the network device provides first configuration information, that is, pucch-Config, to the terminal device, where the first configuration information is subordinate to the dedicated parameters (BWP-UplinkDedicated) configuration information (BWP-UplinkDedicated) of the uplink bandwidth part (UL BWP) .
  • the network device may also provide second configuration information to the terminal device, that is, the network device configures pucch-ConfigurationList in the BWP-UplinkDedicated.
  • the second configuration information only has one set of PUCCH configuration information (pucch-Config).
  • the network device may control the power according to the power control reference signal of the PUCCH resource with the smallest ID corresponding to the pucch-Config (In other words, according to the power control reference signal having the same index as the power control reference signal of the PUCCH resource with the smallest ID corresponding to the pucch-Config), receive the PUSCH scheduled by the DCI format 0_0.
  • the network device when the network device provides a pucch-ConfigurationList that only includes a set of PUCCH configuration information, the network device obtains the power control reference signal of the PUSCH scheduled by DCI format 0_0 according to the configuration information pucch-Config in the BWP-UplinkDedicated Therefore, the problem of ambiguity in the indication of the power control reference signal of the PUSCH scheduled by the DCI format 0_0 can be avoided, and the power control reference signal of the PUSCH scheduled by the DCI format 0_0 can be accurately indicated, thereby improving system stability.
  • the network device provides first configuration information, that is, pucch-Config, to the terminal device, where the first configuration information is subordinate to dedicated parameters (in BWP-UplinkDedicated) of the uplink bandwidth part (UL BWP). ).
  • the network device may also provide second configuration information to the terminal device, that is, the network device configures pucch-ConfigurationList in the BWP-UplinkDedicated.
  • the second configuration information has two sets of PUCCH configuration information (pucch-Config).
  • the network device may, according to the configuration information in the BWP-UplinkDedicated, with the smallest ID corresponding to the pucch-Config
  • the power control reference signal of the PUCCH resource (or, according to the power control reference signal having the same index as the power control reference signal of the PUCCH resource with the smallest ID corresponding to the pucch-Config), the PUSCH scheduled by the DCI format 0_0 is received.
  • the network device when the network device provides a pucch-ConfigurationList including two sets of PUCCH configuration information to the terminal device, the network device obtains the power control reference for the PUSCH scheduled by DCI format 0_0 according to the pucch-Config configured in the BWP-UplinkDedicated Therefore, the problem of ambiguity in the indication of the power control reference signal for the PUSCH scheduled by the DCI format 0_0 can be avoided, and the power control reference signal of the PUSCH scheduled by the DCI format 0_0 can be accurately indicated, thereby improving system stability.
  • FIG. 9 is another schematic diagram of the uplink signal receiving method of the fourth aspect of the embodiments of the present application. As shown in FIG. 9, the uplink signal receiving method includes:
  • Operation 901 Configure second configuration information related to a physical uplink control channel (PUCCH) to a terminal device, where the second configuration information refers to at least two simultaneous constructed (simultaneous constructed) hybrid automatic repeat request-confirmation (HARQ-ACK) physical uplink control channel (PUCCH) configuration information of the codebook; and
  • Operation 902 According to the power control reference signal (spatial relation) of the physical uplink control channel (PUCCH) configuration information corresponding to the second configuration information, receive the downlink control signal format 0_0 (DCI format 0_0) in a cell (DCI format 0_0). ) Scheduled physical uplink shared channel (PUSCH).
  • PUCCH physical uplink control channel
  • the fourth aspect of the embodiments of the present application it is possible to receive the physical uplink shared channel (PUSCH) scheduled by the downlink control signal format 0_0 (DCI format 0_0) according to the power control reference signal of the PUCCH configuration information corresponding to the second configuration information. It can avoid the problem of ambiguity in the indication of the power control reference signal in the PUSCH scheduled by the DCI format 0_0, so as to accurately indicate the power control reference signal.
  • the description of the second configuration information is the same as the foregoing description of the fourth aspect of the embodiment of the present application.
  • the terminal device can generate at least two hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebooks.
  • the terminal device may generate two HARQ-ACK codebooks according to configuration information, where the configuration information is, for example, a physical downlink shared channel hybrid automatic repeat request confirmation codebook list (pdsch-HARQ-ACK-Codebook-List).
  • Information refers to the PUCCH configuration information used for at least two simultaneously assembled (simultaneous constructed) HARQ-ACK codebooks (codebook) in the configuration information of cell-group specific L1 parameters (cell-group specific L1parameters), the configuration information ( pdsch-HARQ-ACK-Codebook-List) is different from the second configuration information.
  • the configuration information may separately determine the type of each HARQ-ACK codebook (the type is, for example, dynamic or semi-static).
  • the network device may use the identification number (ID) corresponding to the set of physical uplink control channel (PUCCH) configuration information of the second configuration information.
  • ID the identification number
  • the power control reference signal of the smallest physical uplink control channel (PUCCH) resource receives the physical uplink shared channel (PUSCH) scheduled by the downlink control signal format 0_0 (DCI format 0_0).
  • the network device may use the identification number ( ID)
  • ID The power control reference signal of the smallest physical uplink control channel (PUCCH) resource, receiving the physical uplink shared channel (PUSCH) scheduled by the downlink control signal format 0_0 (DCI format 0_0).
  • the network device uses the first set of physical uplink control channels in the two sets of physical uplink control channel (PUCCH) configuration information according to the second configuration information (PUCCH) configuration information or the power control reference signal of the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) corresponding to the second group of physical uplink control channel (PUCCH) configuration information, received by the downlink control signal format 0_0( DCI format 0_0) Scheduled physical uplink shared channel (PUSCH).
  • PUCCH physical uplink control channel
  • the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) corresponding to the first group of physical uplink control channel (PUCCH) configuration information or the second group of physical uplink control channel (PUCCH) configuration information is configured
  • the terminal device can use the smallest identification number (ID) corresponding to the first set of physical uplink control channel (PUCCH) configuration information or the second set of physical uplink control channel (PUCCH) configuration information.
  • the power control reference signal of the physical uplink control channel (PUCCH) resource receives the physical uplink shared channel (PUSCH) scheduled by the downlink control signal format 0_0 (DCI format 0_0).
  • the network device may configure the first configuration information to the terminal device or not configure the first configuration information.
  • the description of the first configuration information is the same as the foregoing description of the fourth aspect of the embodiment of the present application.
  • the method for receiving the uplink signal shown in FIG. 9 will be illustrated by examples four, five and six.
  • the second configuration information may be pucch-ConfigurationList subordinate to BWP-UplinkDedicated.
  • the pucch-ConfigurationList may include one or two sets of PUCCH configuration information.
  • the PUCCH configuration information is, for example, represented as PUCCH-Config.
  • the PUCCH configuration information is an IE used to configure terminal device specific PUCCH parameters (UE specific PUCCH parameters).
  • the network device provides second configuration information, that is, pucch-ConfigurationList, to the terminal device, and the second configuration information is subordinate to the dedicated parameters (BWP-UplinkDedicated) configuration information (BWP-UplinkDedicated) of the uplink bandwidth part (UL BWP).
  • the second configuration information only has one set of PUCCH configuration information (pucch-Config).
  • the network device may perform according to the one in the pucch-ConfigurationList.
  • the power control reference signal of the PUCCH resource with the smallest ID in the group PUCCH configuration information (pucch-Config) (or, according to the power control reference signal of the PUCCH resource with the smallest ID corresponding to the group of pucch-Config) Control reference signal), receive the PUSCH scheduled by DCI format 0_0.
  • Example 4 when the network device provides a pucch-ConfigurationList that includes only one set of PUCCH configuration information, the network device obtains the set of PUCCH configuration information from the configuration information pucch-ConfigurationList in the BWP-UplinkDedicated by DCI format 0_0.
  • the power control reference signal of the scheduled PUSCH can avoid the problem of ambiguity in the indication of the power control reference signal of the PUSCH scheduled by the DCI format 0_0, and can accurately indicate the power control reference signal of the PUSCH scheduled by the DCI format 0_0, which improves system stability.
  • the network device provides second configuration information, that is, pucch-ConfigurationList, to the terminal device, and the second configuration information is subordinate to the dedicated parameters (BWP-UplinkDedicated) configuration information (BWP-UplinkDedicated) of the uplink bandwidth part (UL BWP).
  • the second configuration information has two sets of PUCCH configuration information (pucch-Config), and the two sets of PUCCH configuration information (pucch-Config) include, for example, a first set of PUCCH configuration information (pucch-Config) and a second set of PUCCH configuration information.
  • Information (pucch-Config).
  • the network device may receive the PUSCH scheduled by the DCI format 0_0 according to the power control reference signal of the first group of PUCCH configuration information (pucch-Config).
  • the network device may be configured according to the information in the pucch-ConfigurationList.
  • the power control reference signal of the PUCCH resource with the smallest ID in the first group of PUCCH configuration information (pucch-Config) (or in other words, according to the power control reference signal of the PUCCH resource with the smallest ID corresponding to the first group of pucch-Config) Power control reference signal with the same index), and receive the PUSCH scheduled by DCI format 0_0.
  • Example 5 when the network device provides a pucch-ConfigurationList that includes two sets of PUCCH configuration information, the network device obtains the first group of PUCCH configuration information from the configuration information pucch-ConfigurationList in the BWP-UplinkDedicated by DCI format 0_0.
  • the power control reference signal of the scheduled PUSCH can avoid the problem of ambiguity in the indication of the power control reference signal of the PUSCH scheduled by the DCI format 0_0, and can accurately indicate the power control reference signal of the PUSCH scheduled by the DCI format 0_0, which improves system stability.
  • the network device provides second configuration information, that is, pucch-ConfigurationList, to the terminal device, and the second configuration information is subordinate to the dedicated parameters (BWP-UplinkDedicated) configuration information (BWP-UplinkDedicated) of the uplink bandwidth part (UL BWP).
  • the second configuration information has two sets of PUCCH configuration information (pucch-Config), and the two sets of PUCCH configuration information (pucch-Config) include, for example, a first set of PUCCH configuration information (pucch-Config) and a second set of PUCCH configuration Information (pucch-Config).
  • the network device may receive the PUSCH scheduled by the DCI format 0_0 according to the power control reference signal of the second group of PUCCH configuration information (pucch-Config).
  • the network device may The power control reference signal of the PUCCH resource with the smallest ID in the second set of PUCCH configuration information (pucch-Config) (or, according to the power control reference signal of the PUCCH resource with the smallest ID corresponding to the second set of pucch-Config) Power control reference signals with the same index), receive the PUSCH scheduled by DCI format 0_0.
  • Example 6 when the network device provides a pucch-ConfigurationList that includes two sets of PUCCH configuration information, the network device obtains the second set of PUCCH configuration information from the configuration information pucch-ConfigurationList in the BWP-UplinkDedicated by DCI format 0_0.
  • the power control reference signal of the scheduled PUSCH can avoid the problem of ambiguity in the indication of the power control reference signal of the PUSCH scheduled by the DCI format 0_0, and can accurately indicate the power control reference signal of the PUSCH scheduled by the DCI format 0_0, which improves system stability.
  • the network device may configure the first configuration information to the terminal device, and the first configuration information may, for example, be subordinate to the dedicated parameter configuration information BWP of the uplink bandwidth part (UL BWP) -UplinkDedicated PUCCH configuration information pucch-Config.
  • the network device may not configure the terminal device with the first configuration information.
  • the fourth aspect of the embodiments of the present application it is possible to receive the physical uplink shared channel scheduled by the downlink control signal format 0_0 (DCI format 0_0) according to the power control reference signal of the PUCCH configuration information corresponding to the first configuration information or the second configuration information (PUSCH), therefore, it is possible to avoid the problem of ambiguity in the indication of the power control reference signal in the PUSCH scheduled by DCI format 0_0, so as to accurately indicate the power control reference signal.
  • DCI format 0_0 the physical uplink shared channel scheduled by the downlink control signal format 0_0
  • the fifth aspect of the embodiments of the present application provides an uplink signal sending apparatus, which is applied to a terminal device, for example, the terminal device 102.
  • FIG. 10 is a schematic diagram of an uplink signal sending apparatus in the fifth aspect of an embodiment of the present application. As shown in FIG. 10, the uplink signal sending apparatus 1000 includes a first processing unit 1001.
  • the first processing unit 1001 may implement the uplink signal sending method described in FIG. 2 in the first aspect of the embodiments of the present application.
  • the description of the method for transmitting the uplink signal implemented by the first processing unit 1001 reference may be made to the description of FIG. 2 in the first aspect of the embodiment of the present application.
  • FIG. 11 is another schematic diagram of the uplink signal sending apparatus in the fifth aspect of the embodiments of the present application. As shown in FIG. 11, the uplink signal sending apparatus 1100 includes a second processing unit 1101.
  • the second processing unit 1101 may implement the uplink signal sending method described in FIG. 3 in the first aspect of the embodiments of the present application.
  • the description of the method for transmitting the uplink signal by the second processing unit 1101 reference may be made to the description of FIG. 3 in the first aspect of the embodiment of the present application.
  • FIG. 12 is another schematic diagram of the uplink signal sending apparatus in the fifth aspect of the embodiments of the present application. As shown in FIG. 12, the uplink signal sending apparatus 1200 includes a third processing unit 1201.
  • the third processing unit 1201 may implement the uplink signal sending method described in FIG. 4 in the second aspect of the embodiments of the present application.
  • the description of the method for transmitting the uplink signal implemented by the third processing unit 1201 reference may be made to the description of FIG. 4 in the second aspect of the embodiment of the present application.
  • FIG. 13 is another schematic diagram of the uplink signal sending method and apparatus of the fifth aspect of the embodiments of the present application.
  • the uplink signal sending apparatus 1300 includes a fourth processing unit 1301.
  • the fourth processing unit 1301 may implement the uplink signal sending method described in FIG. 5 in the second aspect of the embodiments of the present application.
  • the description of the method for transmitting the uplink signal implemented by the fourth processing unit 1301 reference may be made to the description of FIG. 5 in the second aspect of the embodiment of the present application.
  • the sixth aspect of the embodiments of the present application provides an uplink signal receiving apparatus, which is applied to a network device, for example, the network device 101.
  • FIG. 14 is a schematic diagram of an uplink signal receiving apparatus in the sixth aspect of an embodiment of the present application. As shown in FIG. 14, the uplink signal receiving apparatus 1400 includes a fifth processing unit 1401.
  • the fifth processing unit 1401 may implement the uplink signal receiving method described in FIG. 6 in the third aspect of the embodiments of the present application.
  • the description of the method for receiving the uplink signal implemented by the fifth processing unit 1401 reference may be made to the description of FIG. 6 in the third aspect of the embodiment of the present application.
  • FIG. 15 is another schematic diagram of the uplink signal receiving apparatus in the sixth aspect of the embodiments of the present application. As shown in FIG. 15, the uplink signal receiving apparatus 1500 includes a sixth processing unit 1501.
  • the sixth processing unit 1501 may implement the uplink signal receiving method described in FIG. 7 in the third aspect of the embodiments of the present application.
  • the description of the method for receiving the uplink signal implemented by the sixth processing unit 1501 reference may be made to the description of FIG. 7 in the sixth aspect of the embodiments of the present application.
  • FIG. 16 is another schematic diagram of the apparatus for receiving an uplink signal in the sixth aspect of an embodiment of the present application. As shown in FIG. 16, the apparatus for receiving an uplink signal 1600 includes a seventh processing unit 1601.
  • the seventh processing unit 1601 may implement the uplink signal receiving method described in FIG. 8 in the third aspect of the embodiments of the present application.
  • the description of the method for receiving the uplink signal implemented by the seventh processing unit 1601 reference may be made to the description of FIG. 8 in the third aspect of the embodiment of the present application.
  • FIG. 17 is another schematic diagram of the apparatus for receiving uplink signals in the sixth aspect of the embodiments of the present application. As shown in FIG. 17, the apparatus for receiving uplink signals 1700 includes an eighth processing unit 1701.
  • the eighth processing unit 1701 may implement the uplink signal receiving method described in FIG. 9 in the fourth aspect of the embodiments of the present application.
  • the description of the method for receiving the uplink signal implemented by the eighth processing unit 1701 reference may be made to the description of FIG. 9 in the fourth aspect of the embodiment of the present application.
  • a seventh aspect of the embodiments of the present application provides a terminal device, which includes the uplink signal sending apparatus 1000, 1100, 1200, or 1300 as described in the fifth aspect of the embodiment.
  • FIG. 18 is a schematic block diagram of the system configuration of the terminal device 1800 in the seventh aspect of the embodiments of the present application.
  • the terminal device 1800 may include a processor 1810 and a memory 1820; the memory 1820 is coupled to the processor 1810. It is worth noting that this figure is exemplary; other types of structures can also be used to supplement or replace this structure to implement telecommunication functions or other functions.
  • the functions of the uplink signal sending apparatus 1000, 1100, 1200, or 1300 may be integrated into the processor 1810.
  • the processor 1810 may be configured to be able to implement the uplink signal sending method of the first aspect or the second aspect of the embodiment.
  • the uplink signal sending apparatus 1000, 1100, 1200, or 1300 can be configured separately from the processor 1810.
  • the uplink signal sending apparatus 1000, 1100, 1200, or 1300 can be configured to be connected to the processor 1810.
  • the chip realizes the function of the uplink signal sending device 1000, 1100, 1200, or 1300 through the control of the processor 1810.
  • the terminal device 1800 may further include: a communication module 1830, an input unit 1840, a display 1850, and a power supply 1860. It is worth noting that the terminal device 1800 does not necessarily include all the components shown in FIG. 18; in addition, the terminal device 1800 may also include components not shown in FIG. 18, and reference may be made to the prior art.
  • the processor 1810 is sometimes called a controller or an operating control, and may include a microprocessor or other processor device and/or logic device.
  • the processor 1810 receives input and controls the operation of the various components of the terminal device 1800. operate.
  • the memory 1820 may be, for example, one or more of a cache, a flash memory, a hard drive, a removable medium, a volatile memory, a non-volatile memory, or other suitable devices.
  • Various data can be stored, in addition to the program that executes related information.
  • the processor 1810 can execute the program stored in the memory 1820 to implement information storage or processing.
  • the functions of other components are similar to the existing ones, so I won't repeat them here.
  • Each component of the terminal device 1800 can be implemented by dedicated hardware, firmware, software, or a combination thereof, without departing from the scope of the present application.
  • An eighth aspect of the embodiments of the present application provides a network device, which includes the uplink signal receiving apparatus 1400, 1500, 1600, or 1700 as described in the sixth aspect of the embodiments.
  • FIG. 19 is a schematic diagram of a structure of a network device according to an embodiment of the present application.
  • the network device 1900 may include: a processor 1910 and a memory 1920; the memory 1920 is coupled to the processor 1910.
  • the memory 1920 can store various data; in addition, it also stores an information processing program 1930, and the program 1930 is executed under the control of the processor 1910 to receive various information sent by the user equipment and send request information to the user equipment.
  • the function of the receiving device 1400, 1500, 1600, or 1700 of the uplink signal may be integrated into the processor 1910.
  • the processor 1910 may be configured to implement the random access method described in the second aspect of the embodiments of the present application.
  • the uplink signal receiving device 1400, 1500, 1600, or 1700 can be configured separately from the processor 1910.
  • the uplink signal receiving device 1400, 1500, 1600, or 1700 can be configured to be connected to the processor 1910.
  • the chip realizes the function of the receiving device 1400, 1500, 1600 or 1700 of the uplink signal through the control of the processor 1910.
  • the network device 1900 may further include: a transceiver 1940, an antenna 1950, etc.; wherein the functions of the above-mentioned components are similar to those of the prior art, and will not be repeated here. It is worth noting that the network device 1900 does not necessarily include all the components shown in FIG. 19; in addition, the network device 1900 may also include components not shown in FIG. 19, and reference may be made to the prior art.
  • the ninth aspect of the embodiments of the present application also provides a communication system, including the network device described in the eighth aspect of the embodiment and the terminal device described in the seventh aspect of the embodiment.
  • the above devices and methods of this application can be implemented by hardware, or can be implemented by hardware combined with software.
  • This application relates to such a computer-readable program, when the program is executed by a logic component, the logic component can realize the above-mentioned device or constituent component, or the logic component can realize the above-mentioned various methods Or steps.
  • This application also relates to storage media used to store the above programs, such as hard disks, magnetic disks, optical disks, DVDs, flash memory, etc.
  • the method/device described in conjunction with the embodiments of the present application may be directly embodied as hardware, a software module executed by a processor, or a combination of the two.
  • one or more of the functional block diagrams and/or one or more combinations of the functional block diagrams shown in the figure may correspond to each software module of the computer program flow or each hardware module.
  • These software modules can respectively correspond to the steps shown in the figure.
  • These hardware modules can be implemented by solidifying these software modules by using a field programmable gate array (FPGA), for example.
  • FPGA field programmable gate array
  • the software module can be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM or any other form of storage medium known in the art.
  • a storage medium may be coupled to the processor, so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be a component of the processor.
  • the processor and the storage medium may be located in the ASIC.
  • the software module can be stored in the memory of the mobile terminal, or can be stored in a memory card that can be inserted into the mobile terminal.
  • the software module can be stored in the MEGA-SIM card or a large-capacity flash memory device.
  • One or more of the functional blocks and/or one or more combinations of the functional blocks described in the drawings can be implemented as general-purpose processors, digital signal processors (DSPs) for performing the functions described in this application. ), application specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or any appropriate combination thereof.
  • DSPs digital signal processors
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • One or more of the functional blocks described in the drawings and/or one or more combinations of the functional blocks can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, and multiple micro-processing Processor, one or more microprocessors in communication with the DSP, or any other such configuration.
  • the first configuration information related to the physical uplink control channel (PUCCH) is configured by the network device.
  • PUSCH physical uplink shared channel
  • the first configuration information is subordinate to dedicated parameter configuration information of the active (active) uplink bandwidth part (BWP) of the cell.
  • HARQ-ACK codebook Send a report message to the network device, the report message reporting to the network device that the terminal device has the ability to simultaneously assemble or generate at least two hybrid automatic repeat request-acknowledgement codebooks (HARQ-ACK codebook).
  • HARQ-ACK codebook hybrid automatic repeat request-acknowledgement codebooks
  • the terminal device is not configured by the network device with the second configuration information related to the physical uplink control channel (PUCCH),
  • PUCCH physical uplink control channel
  • the second configuration information refers to physical uplink control channel (PUCCH) configuration information used for (for) at least two simultaneous constructed (simultaneous constructed) hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebooks (codebook).
  • PUCCH physical uplink control channel
  • HARQ-ACK hybrid automatic repeat request-acknowledgement
  • the terminal device is configured by the network device with second configuration information related to the physical uplink control channel (PUCCH),
  • PUCCH physical uplink control channel
  • the second configuration information refers to physical uplink control channel (PUCCH) configuration information for at least two simultaneous constructed (simultaneous constructed) hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebooks (codebook).
  • PUCCH physical uplink control channel
  • HARQ-ACK hybrid automatic repeat request-acknowledgement
  • the second configuration information is subordinate to dedicated parameters (dedicated parameters) configuration information of the activated uplink bandwidth part (BWP) of the cell.
  • the second configuration information includes one set of physical uplink control channel (PUCCH) configuration information or two or more sets of physical uplink control channel (PUCCH) configuration information.
  • PUCCH physical uplink control channel
  • PUCCH physical uplink control channel
  • the terminal device transmits the physical uplink share scheduled by the downlink control signal format 0_0 (DCI format 0_0) according to the spatial relationship of the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) corresponding to the first configuration information Channel (PUSCH).
  • DCI format 0_0 downlink control signal format 0_0
  • ID identification number
  • the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) corresponding to the first configuration information is configured with spatial configuration information (spatial setting) or is applicable to a spatial relationship.
  • a method for sending an uplink signal, applied to a terminal device comprising:
  • the second configuration information related to the physical uplink control channel (PUCCH) is configured by the network device, where the second configuration information refers to at least two simultaneous assembled (simultaneous constructed) hybrid automatic repeat request-acknowledgement (HARQ- ACK) physical uplink control channel (PUCCH) configuration information of the codebook; and
  • PUSCH physical uplink shared channel
  • the terminal device generates at least two hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebooks.
  • HARQ-ACK hybrid automatic repeat request-acknowledgement
  • the second configuration information is subordinate to dedicated parameters (dedicated parameters) configuration information of the activated uplink bandwidth part (BWP) of the cell.
  • the second configuration information includes 1 set of physical uplink control channel (PUCCH) configuration information.
  • PUCCH physical uplink control channel
  • the terminal device transmits the downlink data according to the spatial relationship of the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) corresponding to the 1 set of physical uplink control channel (PUCCH) configuration information of the second configuration information.
  • Control signal format 0_0 DCI format 0_0 scheduled physical uplink shared channel (PUSCH).
  • the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) corresponding to the 1 set of physical uplink control channel (PUCCH) configuration information of the second configuration information is configured with spatial configuration information or is applicable to )Spatial Relations.
  • the second configuration information includes 2 sets of physical uplink control channel (PUCCH) configuration information.
  • PUCCH physical uplink control channel
  • the terminal device according to the first group of physical uplink control channel (PUCCH) configuration information or the second group of physical uplink control channel (PUCCH) configuration information in the 2 groups of physical uplink control channel (PUCCH) configuration information of the second configuration information Corresponding to the spatial relationship of the physical uplink control channel (PUCCH) resource with the smallest identification number (ID), the physical uplink shared channel (PUSCH) scheduled by the downlink control signal format 0_0 (DCI format 0_0) is transmitted.
  • PUCCH physical uplink control channel
  • PUCH physical uplink control channel
  • DCI format 0_0 downlink control signal format 0_0
  • the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) corresponding to the first group of physical uplink control channel (PUCCH) configuration information or the second group of physical uplink control channel (PUCCH) configuration information is configured
  • Spatial configuration information may be applicable to spatial relationships.
  • the first configuration information related to the physical uplink control channel (PUCCH) is configured by the network device.
  • the physical uplink share scheduled by the downlink control signal format 0_0 (DCI format 0_0) is sent Channel (PUSCH).
  • the first configuration information is subordinate to dedicated parameter configuration information of the active (active) uplink bandwidth part (BWP) of the cell.
  • HARQ-ACK codebook Send a report message to the network device, the report message reporting to the network device that the terminal device has the ability to simultaneously assemble or generate at least two hybrid automatic repeat request-acknowledgement codebooks (HARQ-ACK codebook).
  • HARQ-ACK codebook hybrid automatic repeat request-acknowledgement codebooks
  • the terminal device is not configured by the network device with the second configuration information related to the physical uplink control channel (PUCCH),
  • PUCCH physical uplink control channel
  • the second configuration information refers to physical uplink control channel (PUCCH) configuration information used for (for) at least two simultaneous constructed (simultaneous constructed) hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebooks (codebook).
  • PUCCH physical uplink control channel
  • HARQ-ACK hybrid automatic repeat request-acknowledgement
  • the terminal device is configured by the network device with second configuration information related to the physical uplink control channel (PUCCH),
  • PUCCH physical uplink control channel
  • the second configuration information refers to physical uplink control channel (PUCCH) configuration information for at least two simultaneous constructed (simultaneous constructed) hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebooks (codebook).
  • PUCCH physical uplink control channel
  • HARQ-ACK hybrid automatic repeat request-acknowledgement
  • the second configuration information is subordinate to dedicated parameters (dedicated parameters) configuration information of the activated uplink bandwidth part (BWP) of the cell.
  • the second configuration information includes one set of physical uplink control channel (PUCCH) configuration information or two or more sets of physical uplink control channel (PUCCH) configuration information.
  • PUCCH physical uplink control channel
  • PUCCH physical uplink control channel
  • the terminal device transmits the physical uplink control signal format scheduled by the downlink control signal format 0_0 (DCI format 0_0) according to the power control reference signal of the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) corresponding to the first configuration information.
  • Uplink shared channel (PUSCH) Uplink shared channel
  • the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) corresponding to the first configuration information is configured with PUCCH power control parameters.
  • a method for sending an uplink signal, applied to a terminal device comprising:
  • the second configuration information related to the physical uplink control channel (PUCCH) is configured by the network device, where the second configuration information refers to at least two simultaneous assembled (simultaneous constructed) hybrid automatic repeat request-acknowledgement (HARQ- ACK) physical uplink control channel (PUCCH) configuration information of the codebook; and
  • the physical uplink share scheduled by the downlink control signal format 0_0 (DCI format 0_0) is sent Channel (PUSCH).
  • the terminal device generates at least two hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebooks.
  • HARQ-ACK hybrid automatic repeat request-acknowledgement
  • the second configuration information is subordinate to dedicated parameters (dedicated parameters) configuration information of the activated uplink bandwidth part (BWP) of the cell.
  • the second configuration information includes 1 set of physical uplink control channel (PUCCH) configuration information.
  • PUCCH physical uplink control channel
  • the terminal device transmits the power control reference signal of the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) corresponding to the 1 set of physical uplink control channel (PUCCH) configuration information of the second configuration information
  • the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) corresponding to the 1 group of physical uplink control channel (PUCCH) configuration information of the second configuration information is configured with PUCCH power control parameters.
  • the second configuration information includes 2 sets of physical uplink control channel (PUCCH) configuration information.
  • PUCCH physical uplink control channel
  • the terminal device according to the first group of physical uplink control channel (PUCCH) configuration information or the second group of physical uplink control channel (PUCCH) configuration information in the 2 groups of physical uplink control channel (PUCCH) configuration information of the second configuration information
  • the corresponding power control reference signal of the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) transmits the physical uplink shared channel (PUSCH) scheduled by the downlink control signal format 0_0 (DCI format 0_0).
  • the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) corresponding to the first group of physical uplink control channel (PUCCH) configuration information or the second group of physical uplink control channel (PUCCH) configuration information is configured PUCCH power control parameters.
  • a method for receiving uplink signals, applied to a network device comprising:
  • the network device configures the terminal device with first configuration information related to the physical uplink control channel (PUCCH), and the terminal device has the capability to simultaneously assemble or generate at least two hybrid automatic repeat request-acknowledgement codebooks (HARQ-ACK codebook) Ability; and
  • PUCCH physical uplink control channel
  • HARQ-ACK codebook hybrid automatic repeat request-acknowledgement codebooks
  • PUSCH physical uplink control channel
  • the first configuration information is subordinate to dedicated parameters configuration information of the active uplink bandwidth part (BWP) of the cell.
  • HARQ-ACK codebook Receiving a report message sent by the terminal device, the report message reporting to the network device that the terminal device has the ability to simultaneously assemble or generate at least two hybrid automatic repeat request-acknowledgement codebooks (HARQ-ACK codebook).
  • HARQ-ACK codebook Hybrid automatic repeat request-acknowledgement codebooks
  • the network device does not configure second configuration information related to the physical uplink control channel (PUCCH) for the terminal device,
  • PUCCH physical uplink control channel
  • the second configuration information refers to physical uplink control channel (PUCCH) configuration information used for (for) at least two simultaneous constructed (simultaneous constructed) hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebooks (codebook).
  • PUCCH physical uplink control channel
  • HARQ-ACK hybrid automatic repeat request-acknowledgement
  • the network device configures the terminal device with second configuration information related to a physical uplink control channel (PUCCH),
  • PUCCH physical uplink control channel
  • the second configuration information refers to physical uplink control channel (PUCCH) configuration information for at least two simultaneous constructed (simultaneous constructed) hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebooks (codebook).
  • PUCCH physical uplink control channel
  • HARQ-ACK hybrid automatic repeat request-acknowledgement
  • the second configuration information is subordinate to dedicated parameters (dedicated parameters) configuration information of the activated uplink bandwidth part (BWP) of the cell.
  • the second configuration information includes one set of physical uplink control channel (PUCCH) configuration information or two or more sets of physical uplink control channel (PUCCH) configuration information.
  • PUCCH physical uplink control channel
  • PUCCH physical uplink control channel
  • the network device receives the physical uplink share scheduled by the downlink control signal format 0_0 (DCI format 0_0) according to the spatial relationship of the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) corresponding to the first configuration information Channel (PUSCH).
  • DCI format 0_0 downlink control signal format 0_0
  • ID identification number
  • the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) corresponding to the first configuration information is configured with spatial configuration information or is applicable to a spatial relationship.
  • a method for receiving uplink signals, applied to a network device comprising:
  • the network device configures the terminal device with second configuration information related to the physical uplink control channel (PUCCH), where the second configuration information refers to at least two simultaneous constructed (simultaneous constructed) hybrid automatic repeat requests- Acknowledgment (HARQ-ACK) physical uplink control channel (PUCCH) configuration information of the codebook (codebook); and
  • PUCCH physical uplink control channel
  • the physical uplink shared channel scheduled by the downlink control signal format 0_0 (DCI format 0_0) (PUSCH).
  • the second configuration information is subordinate to dedicated parameters (dedicated parameters) configuration information of the activated uplink bandwidth part (BWP) of the cell.
  • the second configuration information includes 1 set of physical uplink control channel (PUCCH) configuration information.
  • PUCCH physical uplink control channel
  • the network device receives Control signal format 0_0 (DCI format 0_0) scheduled physical uplink shared channel (PUSCH).
  • DCI format 0_0 DCI format 0_0
  • the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) corresponding to the 1 set of physical uplink control channel (PUCCH) configuration information of the second configuration information is configured with the spatial configuration information or is applicable (is applicable to) spatial relationship.
  • the second configuration information includes 2 sets of physical uplink control channel (PUCCH) configuration information.
  • PUCCH physical uplink control channel
  • the network device according to the first group of physical uplink control channel (PUCCH) configuration information or the second group of physical uplink control channel (PUCCH) configuration information in the 2 groups of physical uplink control channel (PUCCH) configuration information of the second configuration information Corresponding to the spatial relationship of the physical uplink control channel (PUCCH) resource with the smallest identification number (ID), the physical uplink shared channel (PUSCH) scheduled by the downlink control signal format 0_0 (DCI format 0_0) is received.
  • PUCCH physical uplink control channel
  • PUCH physical uplink control channel
  • the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) corresponding to the first group of physical uplink control channel (PUCCH) configuration information or the second group of physical uplink control channel (PUCCH) configuration information is configured
  • the spatial configuration information may be applicable to the spatial relationship.
  • a method for receiving uplink signals, applied to a network device comprising:
  • the network device configures the terminal device with first configuration information related to the physical uplink control channel (PUCCH), and the terminal device has the capability to simultaneously assemble or generate at least two hybrid automatic repeat request-acknowledgement codebooks (HARQ-ACK codebook) Ability; and
  • PUCCH physical uplink control channel
  • HARQ-ACK codebook hybrid automatic repeat request-acknowledgement codebooks
  • the power control reference signal of the physical uplink control channel (PUCCH) configuration information corresponding to the first configuration information in a cell, receive the physical uplink sharing scheduled by the downlink control signal format 0_0 (DCI format 0_0) Channel (PUSCH).
  • DCI format 0_0 DCI format 0_0
  • the first configuration information is subordinate to dedicated parameter configuration information of the active (active) uplink bandwidth part (BWP) of the cell.
  • the report message reporting to the network device that the terminal device has the ability to assemble or generate at least two hybrid automatic repeat request-acknowledgement codebooks (HARQ-ACK codebook) at the same time.
  • HARQ-ACK codebook hybrid automatic repeat request-acknowledgement codebooks
  • the network device does not configure second configuration information related to the physical uplink control channel (PUCCH) for the terminal device,
  • PUCCH physical uplink control channel
  • the second configuration information refers to physical uplink control channel (PUCCH) configuration information used for (for) at least two simultaneous constructed (simultaneous constructed) hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebooks (codebook).
  • PUCCH physical uplink control channel
  • HARQ-ACK hybrid automatic repeat request-acknowledgement
  • the network device configures the terminal device with second configuration information related to a physical uplink control channel (PUCCH),
  • PUCCH physical uplink control channel
  • the second configuration information refers to physical uplink control channel (PUCCH) configuration information for at least two simultaneous constructed (simultaneous constructed) hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebooks (codebook).
  • PUCCH physical uplink control channel
  • HARQ-ACK hybrid automatic repeat request-acknowledgement
  • the second configuration information is subordinate to dedicated parameters (dedicated parameters) configuration information of the activated uplink bandwidth part (BWP) of the cell.
  • the second configuration information includes one set of physical uplink control channel (PUCCH) configuration information or two or more sets of physical uplink control channel (PUCCH) configuration information.
  • PUCCH physical uplink control channel
  • PUCCH physical uplink control channel
  • the network device receives the physical uplink scheduled by the downlink control signal format 0_0 (DCI format0_0) according to the power control reference signal of the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) corresponding to the first configuration information Shared channel (PUSCH).
  • DCI format0_0 downlink control signal format 0_0
  • ID the identification number
  • the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) corresponding to the first configuration information is configured with PUCCH power control parameters.
  • the network device configures the terminal device with second configuration information related to the physical uplink control channel (PUCCH), where the second configuration information refers to at least two simultaneous constructed (simultaneous constructed) hybrid automatic repeat requests- Acknowledgment (HARQ-ACK) physical uplink control channel (PUCCH) configuration information of the codebook (codebook); and
  • PUCCH physical uplink control channel
  • the power control reference signal of the physical uplink control channel (PUCCH) configuration information corresponding to the second configuration information in a cell, receive the physical uplink sharing scheduled by the downlink control signal format 0_0 (DCI format 0_0) Channel (PUSCH).
  • DCI format 0_0 DCI format 0_0
  • the second configuration information is subordinate to dedicated parameters (dedicated parameters) configuration information of the activated uplink bandwidth part (BWP) of the cell.
  • the second configuration information includes 1 set of physical uplink control channel (PUCCH) configuration information.
  • PUCCH physical uplink control channel
  • the network device receives the power control reference signal of the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) corresponding to the 1 set of physical uplink control channel (PUCCH) configuration information of the second configuration information, and receives The physical uplink shared channel (PUSCH) scheduled by the downlink control signal format 0_0 (DCI format 0_0).
  • PUCCH physical uplink control channel
  • ID the smallest identification number
  • PUSCH physical uplink shared channel scheduled by the downlink control signal format 0_0 (DCI format 0_0).
  • the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) corresponding to the 1 group of physical uplink control channel (PUCCH) configuration information of the second configuration information is configured with PUCCH power control parameters.
  • the second configuration information includes 2 sets of physical uplink control channel (PUCCH) configuration information.
  • PUCCH physical uplink control channel
  • the network device according to the first group of physical uplink control channel (PUCCH) configuration information or the second group of physical uplink control channel (PUCCH) configuration information in the 2 groups of physical uplink control channel (PUCCH) configuration information of the second configuration information
  • the corresponding power control reference signal of the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) receives the physical uplink shared channel (PUSCH) scheduled by the downlink control signal format 0_0 (DCI format 0_0).
  • the physical uplink control channel (PUCCH) resource with the smallest identification number (ID) corresponding to the first group of physical uplink control channel (PUCCH) configuration information or the second group of physical uplink control channel (PUCCH) configuration information is configured PUCCH power control parameters.

Landscapes

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

Abstract

本申请提供一种上行信号的发送和接收方法、装置和通信系统。该上行信号的发送装置包括第一处理单元，所述第一处理单元：被网络设备配置与物理上行控制信道(PUCCH)相关的第一配置信息；以及根据所述第一配置信息所对应的物理上行控制信道(PUCCH)配置信息的空间关系，在一个小区(cell)上，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。

Description

上行信号的发送和接收方法、装置和通信系统 技术领域
本申请实施例涉及无线通信技术领域。
背景技术
为了同时满足高可靠低时延通信(URLLC)业务的需求，通信系统增强了上行信号的发送机制。
另外，为了同时满足不同业务(e.g.eMBB,URLLC)的需求，与上行信号相关的参数可以针对不同的业务类型分别配置。
应该注意，上面对技术背景的介绍只是为了方便对本申请的技术方案进行清楚、完整的说明，并方便本领域技术人员的理解而阐述的。不能仅仅因为这些方案在本申请的背景技术部分进行了阐述而认为上述技术方案为本领域技术人员所公知。
发明内容
本申请的发明人发现：当通信系统中需要对上行控制信号进行优先级指示时，需要至少两个相应的与物理上行控制信道(PUCCH)相关的无线资源控制(RRC)配置信息，也就是说，对于PUCCH而言，有至少两组专用的(dedicated)配置信息，每组专用的配置信息中都关联/包括有一个或多于一个PUCCH资源，每个PUCCH资源都有其相应的ID(其中，每个PUCCH资源的ID不相同)。在上述一个或多于一个PUCCH资源中，ID最小的PUCCH资源被称为该组的具有最小标识号(ID)的专用物理上行控制信道资源(dedicated PUCCH resource)；在这种情况下，如果终端设备需要使用下行控制信号格式0_0(DCI format 0_0)调度上行的物理上行共享信道(PUSCH)时，需要确定使用哪一组专用的配置信息，并根据该组中具有最小标识号(ID)的专用物理上行控制信道资源(dedicated PUCCH resource)的空间关系或功率控制参考信号来发送PUSCH。但是，在现有技术中，终端设备并不能确定使用那一组专用的配置信息，因而存在DCI format 0_0调度的PUSCH出现空间关系或功率控制参考信号指示模糊的问题。
本申请实施例提供一种上行信号的发送和接收方法、装置和通信系统，根据第一 配置信息或第二配置信息所对应的PUCCH配置信息的空间关系或功率控制参考信号，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)，该方法能够避免DCI format 0_0调度的PUSCH出现空间关系或功率控制参考信号指示模糊的问题。
根据本申请实施例的第一方面或第二方面，提供了一种上行信号的发送方法，应用于终端设备，所述方法根据第一配置信息或第二配置信息所对应的PUCCH配置信息的空间关系或功率控制参考信号，发送由DCI format 0_0调度的PUSCH。
根据本申请实施例的第三方面或第四方面，提供了一种上行信号的接收方法，应用于网络设备，该方法根据第一配置信息或第二配置信息所对应的PUCCH配置信息的空间关系或功率控制参考信号，接收由DCI format 0_0调度的PUSCH。
根据本申请实施例的第五方面，提供了一种上行信号的发送装置，应用于终端设备，该装置执行本申请实施例的第一方面或第二方面的上行信号的发送方法。
根据本申请实施例的第六方面，提供了一种上行信号的接收装置，应用于网络设备，该装置执行本申请实施例的第三方面或第四方面的上行信号的接收方法。
根据本申请实施例的第七方面，提供了一种终端设备，其具有本申请实施例的第五方面所述的上行信号的发送装置。
根据本申请实施例的第八方面，提供了一种网络设备，其具有本申请实施例的第六方面所述的上行信号的接收装置。
根据本申请实施例的第九方面，提供了一种通信系统，其具有本申请实施例的第七方面所述的终端设备以及第八方面所述的网络设备。
根据本申请实施例的第十方面，提供了一种计算机可读程序，其中当在上行信号的发送装置或终端设备中执行所述程序时，所述程序使得所述上行信号的发送装置或终端设备执行本申请实施例的第一方面或第二方面的上行信号的发送方法。
根据本申请实施例的第九方面，提供了一种存储有计算机可读程序的存储介质，其中所述计算机可读程序使得上行信号的发送装置或终端设备执行本申请实施例的第一方面或第二方面所述的上行信号的发送方法。
根据本申请实施例的第十方面，提供了一种计算机可读程序，其中当在上行信号的接收装置或网络设备中执行所述程序时，所述程序使得所述上行信号的接收装置或网络设备执行本申请实施例的第三方面或第四方面所述的上行信号的接收方法。
根据本申请实施例的第十一方面，提供了一种存储有计算机可读程序的存储介质，其中所述计算机可读程序使得上行信号的接收装置或网络设备执行本申请实施例的第三方面或第四方面所述的上行信号的接收方法。
本申请实施例的有益效果在于：根据第一配置信息或第二配置信息所对应的PUCCH配置信息的空间关系或功率控制参考信号，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)，该方法能够避免DCI format 0_0调度的PUSCH出现空间关系或功率控制参考信号指示模糊的问题。
参照后文的说明和附图，详细公开了本申请的特定实施方式，指明了本申请的原理可以被采用的方式。应该理解，本申请的实施方式在范围上并不因而受到限制。在所附权利要求的条款的范围内，本申请的实施方式包括许多改变、修改和等同。
针对一种实施方式描述和/或示出的特征可以以相同或类似的方式在一个或更多个其它实施方式中使用，与其它实施方式中的特征相组合，或替代其它实施方式中的特征。
应该强调，术语“包括/包含”在本文使用时指特征、整件、步骤或组件的存在，但并不排除一个或更多个其它特征、整件、步骤或组件的存在或附加。
附图说明
在本申请实施例的一个附图或一种实施方式中描述的元素和特征可以与一个或更多个其它附图或实施方式中示出的元素和特征相结合。此外，在附图中，类似的标号表示几个附图中对应的部件，并可用于指示多于一种实施方式中使用的对应部件。
所包括的附图用来提供对本申请实施例的进一步的理解，其构成了说明书的一部分，用于例示本申请的实施方式，并与文字描述一起来阐释本申请的原理。显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。在附图中：
图1是本申请实施例的通信系统的一示意图；
图2是本申请实施例的第一方面的上行信号发送方法的一个示意图；
图3是本申请实施例的第一方面的上行信号发送方法的另一个示意图；
图4是本申请实施例的第二方面的上行信号发送方法的一个示意图；
图5是本申请实施例的第二方面的上行信号发送方法的另一个示意图；
图6是本申请实施例的第三方面的上行信号接收方法的一个示意图；
图7是本申请实施例的第三方面的上行信号接收方法的另一个示意图；
图8是本申请实施例的第四方面的上行信号接收方法的一个示意图；
图9是本申请实施例的第四方面的上行信号接收方法的另一个示意图；
图10是本申请实施例的第五方面的上行信号发送装置的一个示意图；
图11是本申请实施例的第五方面的上行信号发送装置的另一个示意图；
图12是本申请实施例的第五方面的上行信号发送装置的又一个示意图；
图13是本申请实施例的第五方面的上行信号发送装置的再一个示意图；
图14是本申请实施例的第六方面的上行信号接收装置的一个示意图；
图15是本申请实施例的第六方面的上行信号接收装置的另一个示意图；
图16是本申请实施例的第六方面的上行信号接收装置的又一个示意图；
图17是本申请实施例的第六方面的上行信号接收装置的再一个示意图；
图18是本申请实施例的第七方面的终端设备的系统构成的一示意框图；
图19是本申请实施例的第八方面的网络设备的一构成示意图。
具体实施方式
参照附图，通过下面的说明书，本申请的前述以及其它特征将变得明显。在说明书和附图中，具体公开了本申请的特定实施方式，其表明了其中可以采用本申请的原则的部分实施方式，应了解的是，本申请不限于所描述的实施方式，相反，本申请包括落入所附权利要求的范围内的全部修改、变型以及等同物。下面结合附图对本申请的各种实施方式进行说明。这些实施方式只是示例性的，不是对本申请的限制。
在本申请实施例中，术语“第一”、“第二”等用于对不同元素从称谓上进行区分，但并不表示这些元素的空间排列或时间顺序等，这些元素不应被这些术语所限制。术语“和/或”包括相关联列出的术语的一种或多个中的任何一个和所有组合。术语“包含”、“包括”、“具有”等是指所陈述的特征、元素、元件或组件的存在，但并不排除存在或添加一个或多个其他特征、元素、元件或组件。
在本申请实施例中，单数形式“一”、“该”等包括复数形式，应广义地理解为“一种”或“一类”而并不是限定为“一个”的含义；此外术语“所述”应理解为既包括单数形式也包括复数形式，除非上下文另外明确指出。此外术语“根据”应理解为“至少部分根 据……”，术语“基于”应理解为“至少部分基于……”，除非上下文另外明确指出。
在本申请实施例中，术语“通信网络”或“无线通信网络”可以指符合如下任意通信标准的网络，例如长期演进(LTE，Long Term Evolution)、增强的长期演进(LTE-A，LTE-Advanced)、宽带码分多址接入(WCDMA，Wideband Code Division Multiple Access)、高速报文接入(HSPA，High-Speed Packet Access)等等。
并且，通信系统中设备之间的通信可以根据任意阶段的通信协议进行，例如可以包括但不限于如下通信协议：1G(generation)、2G、2.5G、2.75G、3G、4G、4.5G以及未来的5G、新无线(NR，New Radio)等等，和/或其他目前已知或未来将被开发的通信协议。
在本申请实施例中，术语“网络设备”例如是指通信系统中将终端设备接入通信网络并为该终端设备提供服务的设备。网络设备可以包括但不限于如下设备：基站(BS，Base Station)、接入点(AP、Access Point)、发送接收点(TRP，Transmission Reception Point)、广播发射机、移动管理实体(MME、Mobile Management Entity)、网关、服务器、无线网络控制器(RNC，Radio Network Controller)、基站控制器(BSC，Base Station Controller)等等。
其中，基站可以包括但不限于：节点B(NodeB或NB)、演进节点B(eNodeB或eNB)以及5G基站(gNB)，等等，此外还可包括远端无线头(RRH，Remote Radio Head)、远端无线单元(RRU，Remote Radio Unit)、中继(relay)或者低功率节点(例如femto、pico等等)。并且术语“基站”可以包括它们的一些或所有功能，每个基站可以对特定的地理区域提供通信覆盖。术语“小区”可以指的是基站和/或其覆盖区域，这取决于使用该术语的上下文。
在本申请实施例中，术语“用户设备”(UE，User Equipment)或者“终端设备”(TE，Terminal Equipment)例如是指通过网络设备接入通信网络并接收网络服务的设备。用户设备可以是固定的或移动的，并且也可以称为移动台(MS，Mobile Station)、终端、用户台(SS，Subscriber Station)、接入终端(AT，Access Terminal)、站，等等。
其中，用户设备可以包括但不限于如下设备：蜂窝电话(Cellular Phone)、个人数字助理(PDA，Personal Digital Assistant)、无线调制解调器、无线通信设备、手持设备、机器型通信设备、膝上型计算机、无绳电话、智能手机、智能手表、数字相机， 等等。
再例如，在物联网(IoT，Internet of Things)等场景下，用户设备还可以是进行监控或测量的机器或装置，例如可以包括但不限于：机器类通信(MTC，Machine Type Communication)终端、车载通信终端、设备到设备(D2D，Device to Device)终端、机器到机器(M2M，Machine to Machine)终端，等等。
以下通过示例对本申请实施例的场景进行说明，但本申请不限于此。
图1是本申请实施例的通信系统的一示意图，示意性说明了以终端设备和网络设备为例的情况，如图1所示，通信系统100可以包括网络设备101和终端设备102。为简单起见，图1仅以一个终端设备为例进行说明。
在本申请实施例中，网络设备101和终端设备102之间可以进行现有的业务或者未来可实施的业务。例如，这些业务包括但不限于：增强的移动宽带(eMBB，enhanced Mobile Broadband)、大规模机器类型通信(mMTC，massive Machine Type Communication)和高可靠低时延通信(URLLC，Ultra-Reliable and Low-Latency Communication)，等等。
其中，终端设备102可以向网络设备101发送数据，例如使用免授权传输方式。网络设备101可以接收一个或多个终端设备102发送的数据，并向终端设备102反馈信息(例如正确应答ACK/否定应答NACK)信息，终端设备102根据反馈信息可以确认结束传输过程、或者还可以再进行新的数据传输，或者可以进行数据重传。
以下以将通信系统中的网络设备作为接收端或发送短、将终端设备作为发送端或接收端为例进行说明，但本申请不限于此，发送端和/或接收端还可以是其他的设备。例如，本申请不仅适用于网络设备和终端设备之间的上行免授权传输，还可以适用于两个终端设备之间的边链路免授权传输。
实施例的第一方面
本申请实施例的第一方面涉及一种上行信号的发送方法。
下面，首先对物理层优先级以及上行数据发送的方法进行说明。
在有些通信标准(例如，5G标准的Rel-16)中，引入了物理层优先级(PHY layer priority)的概念，一般来说，大部分上行信号都能够根据对应的指示信息确定其物理层优先级。
例如，对于上行控制信号而言，相应的优先级指示可以帮助上行控制信号确定其对应的RRC配置参数(例如，PUCCH-config)，以使得不同类型的业务传输能够并行配置，并行调度，从而提高系统的效率。
当终端设备发送由下行控制信号格式0_0(DCI format 0_0)调度的PUSCH时，在适用空间关系的时候(即，存在配置的空间关系时)，该PUSCH的空间关系(spatial relation)根据激活的上行带宽部分(UL BWP)中最小标识(ID)的专用(dedicated)PUCCH资源的空间关系来设定。由此，DCI format 0_0调度的上行数据发送，可以独立于与PUSCH相关的RRC配置信息，以便能够在终端设备和网络设备对配置信息理解不一致的情况下，正确地发送上行信号。
当终端设备在载波f发送由DCI format 0_0调度的PUSCH，并且在载波f激活的带宽部分(BWP)上最小ID的PUCCH资源(resource)配置了空间关系信息(PUCCH-SpatialRelationInfo)时，终端设备使用与该PUCCH resource对应的相同的功率控制参考信号发送该PUSCH。
本申请实施例的第一方面涉及一种上行信号的发送方法，应用于终端设备，例如终端设备102，该终端设备具有同时组装或生成至少两个混合自动重复请求-确认码本(HARQ-ACK codebook)的能力。
图2是本申请实施例的第一方面的上行信号发送方法的一个示意图，如图2所示，该上行信号发送方法包括：
操作201、被网络设备配置与物理上行控制信道(PUCCH)相关的第一配置信息；以及
操作202、根据该第一配置信息所对应的物理上行控制信道(PUCCH)配置信息的空间关系(spatial relation)，在一个小区(cell)上，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
根据本申请实施例的第一方面，能够根据第一配置信息对应的PUCCH配置信息的空间关系，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)，由此，在终端设备具有同时组装或生成至少两个混合自动重复请求-确认码本(HARQ-ACK codebook)的能力的情况下，也能够避免DCI format 0_0调度的PUSCH出现空间关系指示模糊的问题，从而准确地指示该空间关系。
在至少一个实施例中，操作201所配置的第一配置信息从属于该小区的激活 (active)上行带宽部分(UL BWP)的专用参数(dedicated parameters)配置信息，其中，该上行带宽部分的专用参数配置信息例如对应于BWP-UplinkDedicated。
该第一配置信息可以是上行带宽部分的专用PUCCH配置信息，例如，从属于BWP-UplinkDedicated的pucch-Config。该第一配置信息可以包括一个PUCCH配置信息列表(例如，resourceToAddModList)，该列表可以为该上行带宽部分添加PUCCH资源。另外，该第一配置信息可以包括另外一个PUCCH配置信息列表(例如，resourceToReleaseList)，该列表可以为该上行带宽部分释放PUCCH资源。通过上述两个列表的指示，该第一配置信息可以对应一个或多于一个PUCCH资源。其中，每个PUCCH资源具有(会被配置)相应的标识号(ID)。
在至少一个实施例中，在操作202中，终端设备可以根据第一配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的空间关系，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
例如，在第一配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源被配置了空间配置信息(spatial setting)或适用(is applicable to)空间关系的情况下，终端设备可以根据第一配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的空间关系，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
在至少一个实施例中，如图2所示，该上行信号发送方法还包括：
操作203、向网络设备发送报告消息，报告消息向网络设备报告该终端设备具有同时组装或生成至少两个混合自动重复请求-确认码本(HARQ-ACK codebook)的能力。
通过操作203，终端设备可以向网络设备报告该终端设备具有同时组装或生成至少两个混合自动重复请求-确认码本(HARQ-ACK codebook)的能力，由此，网络设备能够为该终端设备配置与物理上行控制信道(PUCCH)相关的第二配置信息。
其中，该第二配置信息是指用于(for)至少两个同时组装的(simultaneous constructed)混合自动重复请求-确认(HARQ-ACK)码本(codebook)的物理上行控制信道(PUCCH)配置信息。
在至少一个实施例中，第二配置信息从属于该小区的激活上行带宽部分(active UL BWP)的专用参数(dedicated parameters)配置信息。该第二配置信息可以是上 行带宽部分的专用PUCCH配置信息列表，例如，从属于BWP-UplinkDedicated的pucch-ConfigurationList。
在至少一个实施例中，该第二配置信息可以具有至少一组PUCCH配置信息，各组PUCCH配置信息(类似于第一配置信息)可以对应一个或多于一个PUCCH资源，各PUCCH资源具有(会被配置)相应的标识号(ID)。
例如，该第二配置信息可以具有一组PUCCH配置信息；又例如，该第二配置信息可以具有两组或两组以上的PUCCH配置信息，并且，各组PUCCH配置信息可以对应一个或多于一个PUCCH资源，各PUCCH资源具有(会被配置)相应的标识号(ID)。另外，各组PUCCH配置信息对应于不同的优先级，比如，第一组PUCCH配置信息对应于低优先级(例如，优先级index为0)，第二组PUCCH配置信息对应于高优先级(例如，优先级index为1)。其中，所述优先级是指物理层优先级。
在至少一个实施例中，网络设备可以向终端设备配置该第二配置信息，也可以不向终端设备配置该第二配置信息。
下面，通过实例一、实例二和实例三，对图2所示的上行信号发送方法进行举例说明。在下述的实例一、实例二和实例三中：第一配置信息可以是从属于BWP-UplinkDedicated的pucch-Config；第二配置信息可以是从属于BWP-UplinkDedicated的pucch-ConfigurationList。其中，pucch-ConfigurationList可以包括一组或两组PUCCH配置信息，PUCCH配置信息，例如，被表示为PUCCH-Config，PUCCH配置信息是用于配置终端设备特定PUCCH参数(UE specific PUCCH参数)的IE。
实例一、
在操作201中，终端设备被提供第一配置信息，即pucch-Config，其中该第一配置信息从属于上行带宽部分(UL BWP)的专用参数(dedicated parameters)配置信息(BWP-UplinkDedicated)；并且，终端设备没有被提供第二配置信息，即，没有在该BWP-UplinkDedicated中配置pucch-ConfigurationList。
在上述pucch-Config所对应的ID最小的PUCCH资源被配置了空间配置信息(spatial setting)或适用(is applicable to)空间关系的情况下，在操作202中，终端设备可以根据该pucch-Config所对应的ID最小的PUCCH资源的空间关系，发送由DCI format 0_0调度的PUSCH。其中，空间配置信息(spatial setting)例如为 PUCCH-SpatialRelationInfo。根据实例一，终端设备在能够被提供pucch-ConfigurationList，却没有被提供pucch-ConfigurationList的情况下，终端设备根据BWP-UplinkDedicated中的配置信息pucch-Config得到由DCI format 0_0调度的PUSCH的空间方向，从而避免DCI format 0_0调度的PUSCH出现空间关系指示模糊的问题，能够准确地指示DCI format 0_0调度的PUSCH的空间方向，提升了系统稳定性。
实例二、
在操作201中，终端设备被提供第一配置信息，即pucch-Config，其中该第一配置信息从属于上行带宽部分(UL BWP)的专用参数(dedicated parameters)配置信息(BWP-UplinkDedicated)。此外，终端设备还可以被提供第二配置信息，即，终端设备在该BWP-UplinkDedicated中被配置pucch-ConfigurationList-r16。其中，该第二配置信息中仅具有一组PUCCH配置信息(pucch-Config)。
在上述pucch-Config所对应的ID最小的PUCCH资源被配置了空间配置信息(spatial setting)或适用(is applicable to)空间关系的情况下，在操作202中，终端设备可以根据该pucch-Config所对应的ID最小的PUCCH资源的空间关系，发送由DCI format 0_0调度的PUSCH。其中，空间配置信息(spatial setting)例如为PUCCH-SpatialRelationInfo。
根据实例二，终端设备在被提供了仅包括一组PUCCH配置信息的pucch-ConfigurationList的情况下，终端设备根据BWP-UplinkDedicated中的配置信息pucch-Config得到由DCI format 0_0调度的PUSCH的空间方向，从而避免DCI format 0_0调度的PUSCH出现空间关系指示模糊的问题，能够准确地指示DCI format 0_0调度的PUSCH的空间方向，提升了系统稳定性。
实例三、
在操作201中，终端设备被提供第一配置信息，即pucch-Config，其中该第一配置信息从属于上行带宽部分(UL BWP)的专用参数(dedicated parameters)配置信息(in BWP-UplinkDedicated)。此外，终端设备还可以被提供第二配置信息，即，终端设备在该BWP-UplinkDedicated中被配置pucch-ConfigurationList。其中，该第二配置信息中具有两组PUCCH配置信息(pucch-Config)。
在上述pucch-Config所对应的ID最小的PUCCH资源被配置了空间配置信息 (spatial setting)或适用(is applicable to)空间关系的情况下，在操作202中，终端设备可以根据该pucch-Config所对应的ID最小的PUCCH资源的空间关系，发送由DCI format 0_0调度的PUSCH。其中，空间配置信息(spatial setting)例如为PUCCH-SpatialRelationInfo。
根据实例三，终端设备在被提供了包括两组PUCCH配置信息的pucch-ConfigurationList的情况下，终端设备根据BWP-UplinkDedicated中配置的pucch-Config得到由DCI format 0_0调度的PUSCH的空间方向，从而避免DCI format0_0调度的PUSCH出现空间关系指示模糊的问题，能够准确地指示DCI format 0_0调度的PUSCH的空间方向，提升了系统稳定性。
图3是本申请实施例的第一方面的上行信号发送方法的另一个示意图，如图3所示，该上行信号发送方法包括：
操作301、被网络设备配置与物理上行控制信道(PUCCH)相关的第二配置信息，其中，该第二配置信息是指用于至少两个同时组装的(simultaneous constructed)混合自动重复请求-确认(HARQ-ACK)码本(codebook)的物理上行控制信道(PUCCH)配置信息；以及
操作302、根据该第二配置信息所对应的物理上行控制信道(PUCCH)配置信息的空间关系(spatial relation)，在一个小区(cell)上，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
根据本申请实施例的第一方面，能够根据第二配置信息对应的PUCCH配置信息的空间关系，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)，也能够避免DCI format 0_0调度的PUSCH出现空间关系指示模糊的问题，从而准确地指示该空间关系。
关于第二配置信息的说明与本申请实施例的第一方面的前述说明相同。
在至少一个实施例中，由于在步骤301中被配置了第二配置信息，终端设备可以生成至少两个混合自动重复请求-确认(HARQ-ACK)码本(codebook)。例如，终端设备可以根据配置信息生成两个HARQ-ACK码本，其中，该配置信息例如是物理下行共享信道混合自动重复请求确认码本列表(pdsch-HARQ-ACK-Codebook-List)，该配置信息是指在小区组特定L1参数(cell-group specific L1parameters)的配置信息中，用于至少两个同时组装的(simultaneous constructed)HARQ-ACK码本(codebook) 的PUCCH配置信息，该配置信息(pdsch-HARQ-ACK-Codebook-List)不同于第二配置信息。另外，该配置信息可以分别确定每个HARQ-ACK码本的类型(该类型例如为动态或半静态)。
在第二配置信息包括一组物理上行控制信道(PUCCH)配置信息的情况下，终端设备可以根据该第二配置信息的该一组物理上行控制信道(PUCCH)配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的空间关系，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
例如，在第二配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源被配置了空间配置信息(spatial setting)或适用(is applicable to)空间关系的情况下，终端设备可以根据第二配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的空间关系，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
在第二配置信息包括两组物理上行控制信道(PUCCH)配置信息的情况下，该终端设备根据第二配置信息的两组物理上行控制信道(PUCCH)配置信息中的第一组物理上行控制信道(PUCCH)配置信息或第二组物理上行控制信道(PUCCH)配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的空间关系，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
例如，在第一组物理上行控制信道(PUCCH)配置信息或所述第二组物理上行控制信道(PUCCH)配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源被配置了空间配置信息或适用(is applicable to)空间关系的情况下，终端设备可以根据该第一组物理上行控制信道(PUCCH)配置信息或该第二组物理上行控制信道(PUCCH)配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的空间关系，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
此外，终端设备可以被网络设备配置第一配置信息或者不被配置第一配置信息。关于第一配置信息的说明与本申请实施例的第一方面的前述说明相同。
下面，通过实例四、实例五和实例六，对图3所示的上行信号发送方法进行举例说明。在下述的实例四、实例五和实例六中：第二配置信息可以是从属于BWP-UplinkDedicated的pucch-ConfigurationList。其中，pucch-ConfigurationList可 以包括一组或两组PUCCH配置信息，PUCCH配置信息，例如，被表示为PUCCH-Config，PUCCH配置信息是用于配置终端设备特定PUCCH参数(UE specific PUCCH参数)的IE。
实例四、
在操作301中，终端设备被提供第二配置信息，即，pucch-ConfigurationList，该第二配置信息从属于上行带宽部分(UL BWP)的专用参数(dedicated parameters)配置信息。其中，该第二配置信息中仅具有一组PUCCH配置信息(pucch-Config)。
在上述pucch-ConfigurationList的该一组PUCCH配置信息(pucch-Config)中ID最小的PUCCH资源被配置了空间配置信息(spatial setting)或适用(is applicable to)空间关系的情况下，在操作302中，终端设备可以根据该pucch-ConfigurationList中的该一组PUCCH配置信息(pucch-Config)中ID最小的PUCCH资源的空间关系，发送由DCI format 0_0调度的PUSCH。其中，空间配置信息(spatial setting)例如为PUCCH-SpatialRelationInfo。
根据实例四，终端设备在被提供了仅包括一组PUCCH配置信息的pucch-ConfigurationList的情况下，终端设备根据BWP-UplinkDedicated中的配置信息pucch-ConfigurationList中的该一组PUCCH配置信息得到由DCI format 0_0调度的PUSCH的空间方向，从而避免DCI format 0_0调度的PUSCH出现空间关系指示模糊的问题，能够准确地指示DCI format 0_0调度的PUSCH的空间方向，提升了系统稳定性。
实例五、
在操作301中，终端设备被提供第二配置信息，即，pucch-ConfigurationList，该第二配置信息从属于上行带宽部分(UL BWP)的专用参数(dedicated parameters)配置信息。其中，该第二配置信息中具有两组PUCCH配置信息(pucch-Config)，该两组PUCCH配置信息(pucch-Config)例如包括第一组PUCCH配置信息(pucch-Config)和第二组PUCCH配置信息(pucch-Config)。
在操作302中，终端设备可以根据第一组PUCCH配置信息(pucch-Config)的空间关系来发送由DCI format 0_0调度的PUSCH。
例如，在该pucch-ConfigurationList中的该第一组PUCCH配置信息(pucch-Config)中ID最小的PUCCH资源被配置了空间配置信息(spatial setting) 或适用(is applicable to)空间关系的情况下，在操作302中，终端设备可以根据该pucch-ConfigurationList中的该第一组PUCCH配置信息(pucch-Config)中ID最小的PUCCH资源的空间关系，发送由DCI format 0_0调度的PUSCH。其中，空间配置信息(spatial setting)例如为PUCCH-SpatialRelationInfo。
根据实例五，终端设备在被提供了包括两组PUCCH配置信息的pucch-ConfigurationList的情况下，终端设备根据BWP-UplinkDedicated中的配置信息pucch-ConfigurationList中的该第一组PUCCH配置信息得到由DCI format 0_0调度的PUSCH的空间方向，从而避免DCI format 0_0调度的PUSCH出现空间关系指示模糊的问题，能够准确地指示DCI format 0_0调度的PUSCH的空间方向，提升了系统稳定性。
实例六、
在操作301中，终端设备被提供第二配置信息，即，pucch-ConfigurationList，该第二配置信息从属于上行带宽部分(UL BWP)的专用参数(dedicated parameters)配置信息BWP-UplinkDedicated。其中，该第二配置信息中具有两组PUCCH配置信息(pucch-Config)，该两组PUCCH配置信息(pucch-Config)例如包括第一组PUCCH配置信息(pucch-Config)和第二组PUCCH配置信息(pucch-Config)。
在操作302中，终端设备可以根据第二组PUCCH配置信息(pucch-Config)的空间关系来发送由DCI format 0_0调度的PUSCH。
例如，在该pucch-ConfigurationList中的该第二组PUCCH配置信息(pucch-Config)中ID最小的PUCCH资源被配置了空间配置信息(spatial setting)或适用(is applicable to)空间关系的情况下，在操作302中，终端设备可以根据该pucch-ConfigurationList中的该第二组PUCCH配置信息(pucch-Config)中ID最小的PUCCH资源的空间关系，发送由DCI format 0_0调度的PUSCH。其中，空间配置信息(spatial setting)例如为PUCCH-SpatialRelationInfo。
根据实例六，终端设备在被提供了包括两组PUCCH配置信息的pucch-ConfigurationList的情况下，终端设备根据BWP-UplinkDedicated中的配置信息pucch-ConfigurationList中的该第二组PUCCH配置信息得到由DCI format 0_0调度的PUSCH的空间方向，从而避免DCI format 0_0调度的PUSCH出现空间关系指示模糊的问题，能够准确地指示DCI format 0_0调度的PUSCH的空间方向，提升了系统稳 定性。
在上述实例四、实例五和实例六中，终端设备可以被网络设备配置第一配置信息，该第一配置信息例如可以是从属于上行带宽部分(UL BWP)的专用参数(dedicated parameters)配置信息BWP-UplinkDedicated的PUCCH配置信息(pucch-Config)。此外，在上述实例四、实例五和实例六中，终端设备也可以不被网络设备配置第一配置信息。
根据本申请实施例的第一方面，能够根据第一配置信息或第二配置信息对应的PUCCH配置信息的空间关系，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)，由此，能够避免DCI format 0_0调度的PUSCH出现空间关系指示模糊的问题，从而准确地指示该空间关系。
实施例的第二方面
本申请实施例的第二方面涉及一种上行信号的发送方法，应用于终端设备，例如终端设备102。
图4是本申请实施例的第二方面的上行信号发送方法的一个示意图，如图4所示，该上行信号发送方法包括：
操作401、被网络设备配置与物理上行控制信道(PUCCH)相关的第一配置信息；以及
操作402、根据该第一配置信息所对应的物理上行控制信道(PUCCH)配置信息的功率控制参考信号，在一个小区(cell)上，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
根据本申请实施例的第二方面，能够根据第一配置信息对应的PUCCH配置信息的功率控制参考信号，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)，由此，在终端设备具有同时组装或生成至少两个混合自动重复请求-确认码本(HARQ-ACK codebook)的能力的情况下，也能够避免DCI format 0_0调度的PUSCH出现功率控制参考信号指示模糊的问题，从而准确地指示该功率控制参考信号。
在本申请实施例的第二方面中，功率控制参考信号可以是用于下行路径损失估计(downlink pathloss estimation)的参考信号。
在至少一个实施例中，操作401所配置的第一配置信息从属于该小区的激活(active)上行带宽部分(UL BWP)的专用参数(dedicated parameters)配置信息，其中，该上行带宽部分的专用参数配置信息例如对应于BWP-UplinkDedicated。
该第一配置信息可以是上行带宽部分的专用PUCCH配置信息，例如，从属于BWP-UplinkDedicated的pucch-Config。该第一配置信息可以包括一个PUCCH配置信息列表(例如，resourceToAddModList)，该列表可以为该上行带宽部分添加PUCCH资源。另外，该第一配置信息可以包括另外一个PUCCH配置信息列表(例如，resourceToReleaseList)，该列表可以为该上行带宽部分释放PUCCH资源。通过上述两个列表的指示，该第一配置信息可以对应一个或多于一个PUCCH资源。其中，每个PUCCH资源具有(会被配置)相应的标识号(ID)。
在至少一个实施例中，在操作402中，终端设备可以根据第一配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的功率控制参考信号，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
例如，在第一配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源被配置了PUCCH功率控制参数的情况下，终端设备可以根据第一配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的功率控制参考信号，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。上述描述也可以理解为，终端设备可以根据与第一配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的功率控制参考信号的索引(index)相同的功率控制参考信号，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。其中，PUCCH功率控制参数对应的IE例如为PUCCH-SpatialRelationInfo。
在至少一个实施例中，如图4所示，该上行信号发送方法还包括：
操作403、向网络设备发送报告消息，报告消息向网络设备报告该终端设备具有同时组装或生成至少两个混合自动重复请求-确认码本(HARQ-ACK codebook)的能力。
通过操作403，终端设备可以向网络设备报告该终端设备具有同时组装或生成至少两个混合自动重复请求-确认码本(HARQ-ACK codebook)的能力，由此，网络设备能够为该终端设备配置与物理上行控制信道(PUCCH)相关的第二配置信息。
其中，该第二配置信息是指用于(for)至少两个同时组装的(simultaneous constructed)混合自动重复请求-确认(HARQ-ACK)码本(codebook)的物理上行控制信道(PUCCH)配置信息。
在至少一个实施例中，第二配置信息从属于该小区的激活上行带宽部分(active UL BWP)的专用参数(dedicated parameters)配置信息。该第二配置信息可以是上行带宽部分的专用PUCCH配置信息列表，例如，从属于BWP-UplinkDedicated的pucch-ConfigurationList。
在至少一个实施例中，该第二配置信息可以具有至少一组PUCCH配置信息，各组PUCCH配置信息(类似于第一配置信息)可以对应一个或多于一个PUCCH资源，各PUCCH资源具有(会被配置)相应的标识号(ID)。
例如，该第二配置信息可以具有一组PUCCH配置信息；又例如，该第二配置信息可以具有两组或两组以上的PUCCH配置信息，并且，各组PUCCH配置信息可以对应一个或多于一个PUCCH资源，各PUCCH资源具有(会被配置)相应的标识号(ID)。另外，各组PUCCH配置信息对应于不同的优先级，比如，第一组PUCCH配置信息对应于低优先级(例如，优先级index为0)，第二组PUCCH配置信息对应于高优先级(例如，优先级index为1)。其中，所述优先级是指物理层优先级。在至少一个实施例中，网络设备可以向终端设备配置该第二配置信息，也可以不向终端设备配置该第二配置信息。
下面，通过实例一、实例二和实例三，对图4所示的上行信号发送方法进行举例说明。在下述的实例一、实例二和实例三中：第一配置信息可以是从属于BWP-UplinkDedicated的pucch-Config；第二配置信息可以是从属于BWP-UplinkDedicated的pucch-ConfigurationList。其中，pucch-ConfigurationList可以包括一组或两组PUCCH配置信息，PUCCH配置信息，例如，被表示为PUCCH-Config，PUCCH配置信息是用于配置终端设备特定PUCCH参数(UE specific PUCCH参数)的IE。
实例一、
在操作401中，终端设备被提供第一配置信息，即pucch-Config，其中该第一配置信息从属于上行带宽部分(UL BWP)的专用参数(dedicated parameters)配置信息BWP-UplinkDedicated；并且，终端设备没有被提供第二配置信息，即，没有在该 BWP-UplinkDedicated中配置pucch-ConfigurationList。
在上述pucch-Config所对应的ID最小的PUCCH资源被配置了PUCCH功率控制参数的情况下，在操作402中，终端设备可以根据该pucch-Config所对应的ID最小的PUCCH资源的功率控制参考信号(或者说，根据与该pucch-Config所对应的ID最小的PUCCH资源的功率控制参考信号具有相同索引的功率控制参考信号)，发送由DCI format 0_0调度的PUSCH。
根据实例一，终端设备在能够被提供pucch-ConfigurationList，却没有被提供pucch-ConfigurationList的情况下，终端设备根据BWP-UplinkDedicated中的配置信息pucch-Config得到由DCI format 0_0调度的PUSCH的功率控制参考信号，从而避免DCI format 0_0调度的PUSCH出现功率控制参考信号指示模糊的问题，能够准确地指示DCI format 0_0调度的PUSCH的功率控制参考信号，提升了系统稳定性。
实例二、
在操作401中，终端设备被提供第一配置信息，即pucch-Config，其中该第一配置信息从属于上行带宽部分(UL BWP)的专用参数(dedicated parameters)配置信息(BWP-UplinkDedicated)。此外，终端设备还可以被提供第二配置信息，即，终端设备在该BWP-UplinkDedicated中被配置pucch-ConfigurationList。其中，该第二配置信息中仅具有一组PUCCH配置信息(pucch-Config)。
在上述pucch-Config所对应的ID最小的PUCCH资源被配置了PUCCH功率控制参数的情况下，在操作402中，终端设备可以根据该pucch-Config所对应的ID最小的PUCCH资源的功率控制参考信号(或者说，根据与该pucch-Config所对应的ID最小的PUCCH资源的功率控制参考信号具有相同索引的功率控制参考信号)，发送由DCI format 0_0调度的PUSCH。
根据实例二，终端设备在被提供了仅包括一组PUCCH配置信息的pucch-ConfigurationList的情况下，终端设备根据BWP-UplinkDedicated中的配置信息pucch-Config得到由DCI format 0_0调度的PUSCH的功率控制参考信号，从而避免DCI format 0_0调度的PUSCH出现功率控制参考信号指示模糊的问题，能够准确地指示DCI format 0_0调度的PUSCH的功率控制参考信号，提升了系统稳定性。
实例三、
在操作401中，终端设备被提供第一配置信息，即pucch-Config，其中该第一配 置信息从属于上行带宽部分(UL BWP)的专用参数(dedicated parameters)配置信息(in BWP-UplinkDedicated)。此外，终端设备还可以被提供第二配置信息，即，终端设备在该BWP-UplinkDedicated中被配置pucch-ConfigurationList。其中，该第二配置信息中具有两组PUCCH配置信息(pucch-Config)。
在该pucch-Config所对应的ID最小的PUCCH资源被配置了PUCCH功率控制参数的情况下，在操作402中，终端设备可以根据BWP-UplinkDedicated中配置的pucch-Config所对应的ID最小的PUCCH资源的功率控制参考信号(或者说，根据与该pucch-Config所对应的ID最小的PUCCH资源的功率控制参考信号具有相同索引的功率控制参考信号)，发送由DCI format 0_0调度的PUSCH。
根据实例三，终端设备在被提供了包括两组PUCCH配置信息的pucch-ConfigurationList的情况下，终端设备根据BWP-UplinkDedicated中配置的pucch-Config得到由DCI format 0_0调度的PUSCH的功率控制参考信号，从而避免DCI format 0_0调度的PUSCH出现功率控制参考信号指示模糊的问题，能够准确地指示DCI format 0_0调度的PUSCH的功率控制参考信号，提升了系统稳定性。
图5是本申请实施例的第二方面的上行信号发送方法的另一个示意图，如图5所示，该上行信号发送方法包括：
操作501、被网络设备配置与物理上行控制信道(PUCCH)相关的第二配置信息，其中，该第二配置信息是指用于至少两个同时组装的(simultaneous constructed)混合自动重复请求-确认(HARQ-ACK)码本(codebook)的物理上行控制信道(PUCCH)配置信息；以及
操作502、根据该第二配置信息所对应的物理上行控制信道(PUCCH)配置信息的功率控制参考信号(spatial relation)，在一个小区(cell)上，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
根据本申请实施例的第二方面，能够根据第二配置信息对应的PUCCH配置信息的功率控制参考信号，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)，也能够避免DCI format 0_0调度的PUSCH出现功率控制参考信号指示模糊的问题，从而准确地指示该功率控制参考信号。关于第二配置信息的说明与本申请实施例的第二方面的前述说明相同。
在至少一个实施例中，由于在步骤501中被配置了第二配置信息，终端设备可以 生成至少两个混合自动重复请求-确认(HARQ-ACK)码本(codebook)。例如，终端设备可以根据配置信息生成两个HARQ-ACK码本，其中，该配置信息例如是物理下行共享信道混合自动重复请求确认码本列表(pdsch-HARQ-ACK-Codebook-List)，该配置信息是指在小区组特定L1参数(cell-group specific L1 parameters)的配置信息中，用于至少两个同时组装的(simultaneous constructed)HARQ-ACK码本(codebook)的PUCCH配置信息，该配置信息(pdsch-HARQ-ACK-Codebook-List)不同于第二配置信息。另外，该配置信息可以分别确定每个HARQ-ACK码本的类型(该类型例如为动态或半静态)。
在第二配置信息包括一组物理上行控制信道(PUCCH)配置信息的情况下，终端设备可以根据该第二配置信息的该一组物理上行控制信道(PUCCH)配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的功率控制参考信号，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
例如，在第二配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源被配置了PUCCH功率控制参数的情况下，终端设备可以根据第二配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的功率控制参考信号，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
在第二配置信息包括两组物理上行控制信道(PUCCH)配置信息的情况下，该终端设备根据第二配置信息的两组物理上行控制信道(PUCCH)配置信息中的第一组物理上行控制信道(PUCCH)配置信息或第二组物理上行控制信道(PUCCH)配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的功率控制参考信号，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
例如，在第一组物理上行控制信道(PUCCH)配置信息或所述第二组物理上行控制信道(PUCCH)配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源被配置了PUCCH功率控制参数的情况下，终端设备可以根据该第一组物理上行控制信道(PUCCH)配置信息或该第二组物理上行控制信道(PUCCH)配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的功率控制参考信号，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
此外，终端设备可以被网络设备配置第一配置信息或者不被配置第一配置信息。关于第一配置信息的说明与本申请实施例的第二方面的前述说明相同。
下面，通过实例四、实例五和实例六，对图3所示的上行信号发送方法进行举例说明。在下述的实例四、实例五和实例六中：第二配置信息可以是从属于BWP-UplinkDedicated的pucch-ConfigurationList。其中，pucch-ConfigurationList可以包括一组或两组PUCCH配置信息，PUCCH配置信息，例如，被表示为PUCCH-Config，PUCCH配置信息是用于配置终端设备特定PUCCH参数(UE specific PUCCH参数)的IE。
实例四、
在操作501中，终端设备被提供第二配置信息，即，pucch-ConfigurationList，该第二配置信息从属于上行带宽部分(UL BWP)的专用参数(dedicated parameters)配置信息。其中，该第二配置信息中仅具有一组PUCCH配置信息(pucch-Config)。
在上述pucch-ConfigurationList in BWP-UplinkDedicated的该一组PUCCH配置信息(pucch-Config)中ID最小的PUCCH资源被配置了PUCCH功率控制参数的情况下，在操作502中，终端设备可以根据该pucch-ConfigurationList中的该一组PUCCH配置信息(pucch-Config)中ID最小的PUCCH资源的功率控制参考信号(或者说，根据与该一组pucch-Config所对应的ID最小的PUCCH资源的功率控制参考信号具有相同索引的功率控制参考信号)，发送由DCI format 0_0调度的PUSCH。
根据实例四，终端设备在被提供了仅包括一组PUCCH配置信息的pucch-ConfigurationList的情况下，终端设备根据BWP-UplinkDedicated中的配置信息pucch-ConfigurationList中的该一组PUCCH配置信息得到由DCI format 0_0调度的PUSCH的功率控制参考信号，从而避免DCI format 0_0调度的PUSCH出现功率控制参考信号指示模糊的问题，能够准确地指示DCI format 0_0调度的PUSCH的功率控制参考信号，提升了系统稳定性。
实例五、
在操作501中，终端设备被提供第二配置信息，即，pucch-ConfigurationList，该第二配置信息从属于上行带宽部分(UL BWP)的专用参数(dedicated parameters)配置信息。其中，该第二配置信息中具有两组PUCCH配置信息(pucch-Config)，该两组PUCCH配置信息(pucch-Config)例如包括第一组PUCCH配置信息 (pucch-Config)和第二组PUCCH配置信息(pucch-Config)。
在操作502中，终端设备可以根据第一组PUCCH配置信息(pucch-Config)的功率控制参考信号来发送由DCI format 0_0调度的PUSCH。
例如，在该pucch-ConfigurationList中的该第一组PUCCH配置信息(pucch-Config)中ID最小的PUCCH资源被配置了PUCCH功率控制参数的情况下，在操作502中，终端设备可以根据pucch-ConfigurationList中的该第一组PUCCH配置信息(pucch-Config)中ID最小的PUCCH资源的功率控制参考信号(或者说，根据与该第一组pucch-Config所对应的ID最小的PUCCH资源的功率控制参考信号具有相同索引的功率控制参考信号)，发送由DCI format 0_0调度的PUSCH。
根据实例五，终端设备在被提供了包括两组PUCCH配置信息的pucch-ConfigurationList的情况下，终端设备根据BWP-UplinkDedicated中的配置信息pucch-ConfigurationList中的该第一组PUCCH配置信息得到由DCI format 0_0调度的PUSCH的功率控制参考信号，从而避免DCI format 0_0调度的PUSCH出现功率控制参考信号指示模糊的问题，能够准确地指示DCI format 0_0调度的PUSCH的功率控制参考信号，提升了系统稳定性。
实例六、
在操作501中，终端设备被提供第二配置信息，即，pucch-ConfigurationList，该第二配置信息从属于上行带宽部分(UL BWP)的专用参数(dedicated parameters)配置信息BWP-UplinkDedicated。其中，该第二配置信息中具有两组PUCCH配置信息(pucch-Config)，该两组PUCCH配置信息(pucch-Config)例如包括第一组PUCCH配置信息(pucch-Config)和第二组PUCCH配置信息(pucch-Config)。
在操作502中，终端设备可以根据第二组PUCCH配置信息(pucch-Config)的功率控制参考信号来发送由DCI format 0_0调度的PUSCH。
例如，在该pucch-ConfigurationList中的该第二组PUCCH配置信息(pucch-Config)中ID最小的PUCCH资源被配置了PUCCH功率控制参数的情况下，在操作502中，终端设备可以根据该pucch-ConfigurationList中的该第二组PUCCH配置信息(pucch-Config)中ID最小的PUCCH资源的功率控制参考信号(或者说，根据与该第二组pucch-Config所对应的ID最小的PUCCH资源的功率控制参考信号具有相同索引的功率控制参考信号)，发送由DCI format 0_0调度的PUSCH。
根据实例六，终端设备在被提供了包括两组PUCCH配置信息的pucch-ConfigurationList的情况下，终端设备根据BWP-UplinkDedicated中的配置信息pucch-ConfigurationList中的该第二组PUCCH配置信息得到由DCI format 0_0调度的PUSCH的功率控制参考信号，从而避免DCI format 0_0调度的PUSCH出现功率控制参考信号指示模糊的问题，能够准确地指示DCI format 0_0调度的PUSCH的功率控制参考信号，提升了系统稳定性。
在上述实例四、实例五和实例六中，终端设备可以被网络设备配置第一配置信息，该第一配置信息例如可以是从属于上行带宽部分(UL BWP)的专用参数(dedicated parameters)配置信息BWP-UplinkDedicated的PUCCH配置信息pucch-Config。此外，在上述实例四、实例五和实例六中，终端设备也可以不被网络设备配置第一配置信息。
根据本申请实施例的第二方面，能够根据第一配置信息或第二配置信息对应的PUCCH配置信息的功率控制参考信号，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)，由此，能够避免DCI format 0_0调度的PUSCH出现功率控制参考信号指示模糊的问题，从而准确地指示该功率控制参考信号。
实施例的第三方面
本申请实施例的第三方面涉及一种上行信号的接收方法，应用于网络设备，例如网络设备101，该网络设备与终端设备通信，该终端设备可以具有同时组装或生成至少两个混合自动重复请求-确认码本(HARQ-ACK codebook)的能力。
图6是本申请实施例的第三方面的上行信号接收方法的一个示意图，如图6所示，该上行信号发送方法包括：
操作601、对终端设备配置与物理上行控制信道(PUCCH)相关的第一配置信息；以及
操作602、根据该第一配置信息所对应的物理上行控制信道(PUCCH)配置信息的空间关系(spatial relation)，在一个小区(cell)上，接收由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
根据本申请实施例的第三方面，能够根据第一配置信息对应的PUCCH配置信息的空间关系，接收由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享 信道(PUSCH)，由此，在终端设备具有同时组装或生成至少两个混合自动重复请求-确认码本(HARQ-ACK codebook)的能力的情况下，也能够避免DCI format 0_0调度的PUSCH出现空间关系指示模糊的问题，从而准确地指示该空间关系。
在至少一个实施例中，操作601所配置的第一配置信息从属于该小区的激活(active)上行带宽部分(UL BWP)的专用参数(dedicated parameters)配置信息，其中，该上行带宽部分的专用参数配置信息例如对应于BWP-UplinkDedicated。
该第一配置信息可以是上行带宽部分的专用PUCCH配置信息，例如，从属于BWP-UplinkDedicated的pucch-Config。该第一配置信息可以包括一个PUCCH配置信息列表(例如，resourceToAddModList)，该列表可以为该上行带宽部分添加PUCCH资源。另外，该第一配置信息可以包括另外一个PUCCH配置信息列表(例如，resourceToReleaseList)，该列表可以为该上行带宽部分释放PUCCH资源。通过上述两个列表的指示，该第一配置信息可以对应一个或多于一个PUCCH资源。其中，每个PUCCH资源具有(会被配置)相应的标识号(ID)。
在至少一个实施例中，在操作602中，网络设备可以根据第一配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的空间关系，接收由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
例如，在第一配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源被配置了空间配置信息(spatial setting)或适用(is applicable to)空间关系的情况下，网络设备可以根据第一配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的空间关系，接收由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
在至少一个实施例中，如图6所示，该上行信号发送方法还包括：
操作603、从终端设备接收报告消息，报告消息向网络设备报告该终端设备具有同时组装或生成至少两个混合自动重复请求-确认码本(HARQ-ACK codebook)的能力。
通过操作603，终端设备可以向网络设备报告该终端设备具有同时组装或生成至少两个混合自动重复请求-确认码本(HARQ-ACK codebook)的能力，由此，网络设备能够为该终端设备配置与物理上行控制信道(PUCCH)相关的第二配置信息。
其中，该第二配置信息是指用于(for)至少两个同时组装的(simultaneous  constructed)混合自动重复请求-确认(HARQ-ACK)码本(codebook)的物理上行控制信道(PUCCH)配置信息。
在至少一个实施例中，第二配置信息从属于该小区的激活上行带宽部分(active UL BWP)的专用参数(dedicated parameters)配置信息。该第二配置信息可以是上行带宽部分的专用PUCCH配置信息列表，例如，从属于BWP-UplinkDedicated的pucch-ConfigurationList。
在至少一个实施例中，该第二配置信息可以具有至少一组PUCCH配置信息，各组PUCCH配置信息可以对应一个或多于一个PUCCH资源，各PUCCH资源具有(会被配置)相应的标识号(ID)。
例如，该第二配置信息可以具有一组PUCCH配置信息；又例如，该第二配置信息可以具有两组或两组以上的PUCCH配置信息，并且，各组PUCCH配置信息可以对应一个或多于一个PUCCH资源，各PUCCH资源具有(会被配置)相应的标识号(ID)。另外，各组PUCCH配置信息对应于不同的优先级，比如，第一组PUCCH配置信息对应于低优先级(例如，优先级index为0)，第二组PUCCH配置信息对应于高优先级(例如，优先级index为1)。其中，所述优先级是指物理层优先级。
在至少一个实施例中，网络设备可以向终端设备配置该第二配置信息，也可以不向终端设备配置该第二配置信息。
下面，通过实例一、实例二和实例三，对图6所示的上行信号发送方法进行举例说明。在下述的实例一、实例二和实例三中：第一配置信息可以是从属于BWP-UplinkDedicated的pucch-Config；第二配置信息可以是从属于BWP-UplinkDedicated的pucch-ConfigurationList。其中，pucch-ConfigurationList可以包括一组或两组PUCCH配置信息，PUCCH配置信息例如被表示为PUCCH-Config，PUCCH配置信息是用于配置终端设备特定PUCCH参数(UE specific PUCCH参数)的IE。
实例一、
在操作601中，网络设备向终端设备提供第一配置信息，即pucch-Config，其中该第一配置信息从属于上行带宽部分(UL BWP)的专用参数(dedicated parameters)配置信息(BWP-UplinkDedicated)；并且，网络设备没有向终端设备提供第二配置信息，即，没有在该BWP-UplinkDedicated中配置pucch-ConfigurationList。
在上述pucch-Config所对应的ID最小的PUCCH资源被配置了空间配置信息(spatial setting)或适用(is applicable to)空间关系的情况下，在操作602中，网络设备可以根据pucch-Config所对应的ID最小的PUCCH资源的空间关系，接收由DCI format 0_0调度的PUSCH。其中，空间配置信息(spatial setting)例如为PUCCH-SpatialRelationInfo。
根据实例一，终端设备在能够被提供pucch-ConfigurationList，却没有被提供pucch-ConfigurationList的情况下，网络设备根据BWP-UplinkDedicated中的配置信息pucch-Config得到由DCI format 0_0调度的PUSCH的空间方向，从而避免DCI format 0_0调度的PUSCH出现空间关系指示模糊的问题，能够准确地指示DCI format 0_0调度的PUSCH的空间方向，提升了系统稳定性。
实例二、
在操作601中，网络设备向终端设备提供第一配置信息，即pucch-Config，其中该第一配置信息从属于上行带宽部分(UL BWP)的专用参数(dedicated parameters)配置信息(BWP-UplinkDedicated)。此外，网络设备还可以向终端设备提供第二配置信息，即，在该BWP-UplinkDedicated中配置pucch-ConfigurationList。其中，该第二配置信息中仅具有一组PUCCH配置信息(pucch-Config)。
在该pucch-Config所对应的ID最小的PUCCH资源被配置了空间配置信息(spatial setting)或适用(is applicable to)空间关系的情况下，在操作602中，网络设备可以根据该pucch-Config所对应的ID最小的PUCCH资源的空间关系，发接收由DCI format 0_0调度的PUSCH。其中，空间配置信息(spatial setting)例如为PUCCH-SpatialRelationInfo。
根据实例二，网络设备在向终端设备提供了仅包括一组PUCCH配置信息的pucch-ConfigurationList的情况下，网络设备根据BWP-UplinkDedicated中的配置信息pucch-Config得到由DCI format 0_0调度的PUSCH的空间方向，从而避免DCI format 0_0调度的PUSCH出现空间关系指示模糊的问题，能够准确地指示DCI format 0_0调度的PUSCH的空间方向，提升了系统稳定性。
实例三、
在操作601中，网络设备向终端设备提供第一配置信息，即pucch-Config，其中该第一配置信息从属于上行带宽部分(UL BWP)的专用参数(dedicated parameters) 配置信息(in BWP-UplinkDedicated)。此外，网络设备还可以向终端设备提供第二配置信息，即，在该BWP-UplinkDedicated中配置pucch-ConfigurationList。其中，该第二配置信息中具有两组PUCCH配置信息(pucch-Config)。
在该pucch-Config所对应的ID最小的PUCCH资源被配置了空间配置信息(spatial setting)或适用(is applicable to)空间关系的情况下，在操作602中，网络设备可以根据该pucch-Config所对应的ID最小的PUCCH资源的空间关系，接收由DCI format 0_0调度的PUSCH。其中，空间配置信息(spatial setting)例如为PUCCH-SpatialRelationInfo。
根据实例三，网络设备向终端设备提供了包括两组PUCCH配置信息的pucch-ConfigurationList的情况下，网络设备根据BWP-UplinkDedicated中配置的pucch-Config得到由DCI format 0_0调度的PUSCH的空间方向，从而避免DCI format 0_0调度的PUSCH出现空间关系指示模糊的问题，能够准确地指示DCI format 0_0调度的PUSCH的空间方向，提升了系统稳定性。
图7是本申请实施例的第三方面的上行信号接收方法的另一个示意图，如图7所示，该上行信号发送方法包括：
操作701、向终端设备配置与物理上行控制信道(PUCCH)相关的第二配置信息，其中，该第二配置信息是指用于至少两个同时组装的(simultaneous constructed)混合自动重复请求-确认(HARQ-ACK)码本(codebook)的物理上行控制信道(PUCCH)配置信息；以及
操作702、根据该第二配置信息所对应的物理上行控制信道(PUCCH)配置信息的空间关系(spatial relation)，在一个小区(cell)上，接收由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
根据本申请实施例的第三方面，能够根据第二配置信息对应的PUCCH配置信息的空间关系，接收由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)，也能够避免DCI format 0_0调度的PUSCH出现空间关系指示模糊的问题，从而准确地指示该空间关系。
关于第二配置信息的说明与本申请实施例的第三方面的前述说明相同。
在至少一个实施例中，由于在步骤701中被配置了第二配置信息，终端设备可以生成至少两个混合自动重复请求-确认(HARQ-ACK)码本(codebook)。例如，终端 设备可以根据配置信息生成两个HARQ-ACK码本，其中，该配置信息例如是物理下行共享信道混合自动重复请求确认码本列表(pdsch-HARQ-ACK-Codebook-List)，该配置信息是指在小区组特定L1参数(cell-group specific L1 parameters)的配置信息中，用于至少两个同时组装的(simultaneous constructed)HARQ-ACK码本(codebook)的PUCCH配置信息，该配置信息(pdsch-HARQ-ACK-Codebook-List)不同于第二配置信息。另外，该配置信息可以分别确定每个HARQ-ACK码本的类型(该类型例如为动态或半静态)。
在第二配置信息包括一组物理上行控制信道(PUCCH)配置信息的情况下，网络设备可以根据该第二配置信息的该一组物理上行控制信道(PUCCH)配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的空间关系，接收由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
例如，在第二配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源被配置了空间配置信息(spatial setting)或适用(is applicable to)该空间关系的情况下，网络设备可以根据第二配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的空间关系，接收由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
在第二配置信息包括两组物理上行控制信道(PUCCH)配置信息的情况下，该网络设备根据第二配置信息的两组物理上行控制信道(PUCCH)配置信息中的第一组物理上行控制信道(PUCCH)配置信息或第二组物理上行控制信道(PUCCH)配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的空间关系，接收由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
例如，在第一组物理上行控制信道(PUCCH)配置信息或所述第二组物理上行控制信道(PUCCH)配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源被配置了空间配置信息或适用(is applicable to)空间关系的情况下，网络设备可以根据该第一组物理上行控制信道(PUCCH)配置信息或该第二组物理上行控制信道(PUCCH)配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的空间关系，接收由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
此外，网络设备可以向终端设备配置第一配置信息或者不配置第一配置信息。关 于第一配置信息的说明与本申请实施例的第三方面的前述说明相同。
下面，通过实例四、实例五和实例六，对图7所示的上行信号接收方法进行举例说明。在下述的实例四、实例五和实例六中：第二配置信息可以是从属于BWP-UplinkDedicated的pucch-ConfigurationList。
其中，pucch-ConfigurationList可以包括一组或两组PUCCH配置信息，PUCCH配置信息，例如，被表示为PUCCH-Config，PUCCH配置信息是用于配置终端设备特定PUCCH参数(UE specific PUCCH参数)的IE。
实例四、
在操作701中，网络设备向终端设备提供第二配置信息，即，pucch-ConfigurationList，该第二配置信息从属于上行带宽部分(UL BWP)的专用参数(dedicated parameters)配置信息。其中，该第二配置信息中仅具有一组PUCCH配置信息(pucch-Config)。
在上述pucch-ConfigurationList的该一组PUCCH配置信息(pucch-Config)中ID最小的PUCCH资源被配置了空间配置信息(spatial setting)或适用(is applicable to)空间关系的情况下，在操作702中，网络设备可以根据该pucch-ConfigurationList中的该一组PUCCH配置信息(pucch-Config)中ID最小的PUCCH资源的空间关系，接收由DCI format 0_0调度的PUSCH。其中，空间配置信息(spatial setting)例如为PUCCH-SpatialRelationInfo。
根据实例四，网络设备在提供了仅包括一组PUCCH配置信息的pucch-ConfigurationList的情况下，网络设备根据BWP-UplinkDedicated中的配置信息pucch-ConfigurationList中的该一组PUCCH配置信息得到由DCI format 0_0调度的PUSCH的空间方向，从而避免DCI format 0_0调度的PUSCH出现空间关系指示模糊的问题，能够准确地指示DCI format 0_0调度的PUSCH的空间方向，提升了系统稳定性。
实例五、
在操作701中，网络设备提供第二配置信息，即，pucch-ConfigurationList，该第二配置信息从属于上行带宽部分(UL BWP)的专用参数(dedicated parameters)配置信息。其中，该第二配置信息中具有两组PUCCH配置信息(pucch-Config)，该两组PUCCH配置信息(pucch-Config)例如包括第一组PUCCH配置信息(pucch-Config) 和第二组PUCCH配置信息(pucch-Config)。
在操作702中，网络设备可以根据第一组PUCCH配置信息(pucch-Config)的空间关系来接收由DCI format 0_0调度的PUSCH。
例如，在该pucch-ConfigurationList中的该第一组PUCCH配置信息(pucch-Config)中ID最小的PUCCH资源被配置了空间配置信息(spatial setting)或适用(is applicable to)空间关系的情况下，在操作702中，网络设备可以根据该pucch-ConfigurationList中的该第一组PUCCH配置信息(pucch-Config)中ID最小的PUCCH资源的空间关系，接收由DCI format 0_0调度的PUSCH。其中，空间配置信息(spatial setting)例如为PUCCH-SpatialRelationInfo。
根据实例五，网络设备在提供了包括两组PUCCH配置信息的pucch-ConfigurationList的情况下，网络设备根据BWP-UplinkDedicated中的配置信息pucch-ConfigurationList中的该第一组PUCCH配置信息得到由DCI format 0_0调度的PUSCH的空间方向，从而避免DCI format 0_0调度的PUSCH出现空间关系指示模糊的问题，能够准确地指示DCI format 0_0调度的PUSCH的空间方向，提升了系统稳定性。
实例六、
在操作701中，网络设备提供第二配置信息，即，pucch-ConfigurationList，该第二配置信息从属于上行带宽部分(UL BWP)的专用参数(dedicated parameters)配置信息。其中，该第二配置信息中具有两组PUCCH配置信息(pucch-Config)，该两组PUCCH配置信息(pucch-Config)例如包括第一组PUCCH配置信息(pucch-Config)和第二组PUCCH配置信息(pucch-Config)。
在操作702中，网络设备设备可以根据第二组PUCCH配置信息(pucch-Config)的空间关系来接收由DCI format 0_0调度的PUSCH。
例如，在pucch-ConfigurationList中的该第二组PUCCH配置信息(pucch-Config)中ID最小的PUCCH资源被配置了空间配置信息(spatial setting)或适用(is applicable to)空间关系的情况下，在操作702中，网络设备可以根据pucch-ConfigurationList中的该第二组PUCCH配置信息(pucch-Config)中ID最小的PUCCH资源的空间关系，接收由DCI format 0_0调度的PUSCH。其中，空间配置信息(spatial setting)例如为PUCCH-SpatialRelationInfo。
根据实例六，网络设备在提供了包括两组PUCCH配置信息的pucch-ConfigurationList的情况下，网络设备根据BWP-UplinkDedicated中的配置信息pucch-ConfigurationList中的该第二组PUCCH配置信息得到由DCI format 0_0调度的PUSCH的空间方向，从而避免DCI format 0_0调度的PUSCH出现空间关系指示模糊的问题，能够准确地指示DCI format 0_0调度的PUSCH的空间方向，提升了系统稳定性。
在上述实例四、实例五和实例六中，网络设备可以向终端设备配置第一配置信息，该第一配置信息例如可以是从属于上行带宽部分(UL BWP)的专用参数(dedicated parameters)配置信息BWP-UplinkDedicated的PUCCH配置信息(pucch-Config)。此外，在上述实例四、实例五和实例六中，网络设备也可以不向终端设备配置第一配置信息。
根据本申请实施例的第三方面，能够根据第一配置信息或第二配置信息对应的PUCCH配置信息的空间关系，接收由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)，由此，能够避免DCI format 0_0调度的PUSCH出现空间关系指示模糊的问题，从而准确地指示该空间关系。
实施例的第四方面
本申请实施例的第四方面涉及一种上行信号的发送方法，应用于网络设备，例如网络设备101。
图8是本申请实施例的第四方面的上行信号接收方法的一个示意图，如图8所示，该上行信号接收方法包括：
操作801、对终端设备配置与物理上行控制信道(PUCCH)相关的第一配置信息；以及
操作802、根据该第一配置信息所对应的物理上行控制信道(PUCCH)配置信息的功率控制参考信号(spatial relation)，在一个小区(cell)上，接收由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
根据本申请实施例的第四方面，能够根据第一配置信息对应的PUCCH配置信息的功率控制参考信号，接收由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)，由此，在终端设备具有同时组装或生成至少两个混合自动 重复请求-确认码本(HARQ-ACK codebook)的能力的情况下，也能够避免DCI format 0_0调度的PUSCH出现功率控制参考信号指示模糊的问题，从而准确地指示该功率控制参考信号。
在本申请实施例的第四方面中，功率控制参考信号可以是用于下行路径损失估计(downlink pathloss estimation)的参考信号。
在至少一个实施例中，操作801所配置的第一配置信息从属于该小区的激活(active)上行带宽部分(UL BWP)的专用参数(dedicated parameters)配置信息，其中，该上行带宽部分的专用参数配置信息例如对应于BWP-UplinkDedicated。
该第一配置信息可以是上行带宽部分的专用PUCCH配置信息，例如，从属于BWP-UplinkDedicated的pucch-Config。该第一配置信息可以包括一个PUCCH配置信息列表(例如，resourceToAddModList)，该列表可以为该上行带宽部分添加PUCCH资源。另外，该第一配置信息可以包括另外一个PUCCH配置信息列表(例如，resourceToReleaseList)，该列表可以为该上行带宽部分释放PUCCH资源。通过上述两个列表的指示，该第一配置信息可以对应一个或多于一个PUCCH资源。其中，每个PUCCH资源具有(会被配置)相应的标识号(ID)。
在至少一个实施例中，在操作802中，终端设备可以根据第一配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的功率控制参考信号，接收由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
例如，在第一配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源被配置了PUCCH功率控制参数的情况下，终端设备可以根据第一配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的功率控制参考信号，接收由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。上述描述也可以理解为，终端设备可以根据与第一配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的功率控制参考信号的索引(index)相同的功率控制参考信号，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。其中，PUCCH功率控制参数对应的IE例如为PUCCH-SpatialRelationInfo。
在至少一个实施例中，如图8所示，该上行信号接收方法还包括：
操作803、从终端设备接收报告消息，报告消息向网络设备报告该终端设备具有同时组装或生成至少两个混合自动重复请求-确认码本(HARQ-ACK codebook)的能力。
通过操作803，终端设备可以向网络设备报告该终端设备具有同时组装或生成至少两个混合自动重复请求-确认码本(HARQ-ACK codebook)的能力，由此，网络设备能够为该终端设备配置与物理上行控制信道(PUCCH)相关的第二配置信息。
其中，该第二配置信息是指用于(for)至少两个同时组装的(simultaneous constructed)混合自动重复请求-确认(HARQ-ACK)码本(codebook)的物理上行控制信道(PUCCH)配置信息。
在至少一个实施例中，第二配置信息从属于该小区的激活上行带宽部分(active UL BWP)的专用参数(dedicated parameters)配置信息。该第二配置信息可以是上行带宽部分的专用PUCCH配置信息列表，例如，从属于BWP-UplinkDedicated的pucch-ConfigurationList。
在至少一个实施例中，该第二配置信息可以具有至少一组PUCCH配置信息，各组PUCCH配置信息(类似于第一配置信息)可以对应一个或多于一个PUCCH资源，各PUCCH资源具有(会被配置)相应的标识号(ID)。
例如，该第二配置信息可以具有一组PUCCH配置信息；又例如，该第二配置信息可以具有两组或两组以上的PUCCH配置信息，并且，各组PUCCH配置信息可以对应一个或多于一个PUCCH资源，各PUCCH资源具有(会被配置)相应的标识号(ID)。另外，各组PUCCH配置信息对应于不同的优先级，比如，第一组PUCCH配置信息对应于低优先级(例如，优先级index为0)，第二组PUCCH配置信息对应于高优先级(例如，优先级index为1)。其中，所述优先级是指物理层优先级。
在至少一个实施例中，网络设备可以向终端设备配置该第二配置信息，也可以不向终端设备配置该第二配置信息。
下面，通过实例一、实例二和实例三，对图8所示的上行信号接收方法进行举例说明。在下述的实例一、实例二和实例三中：第一配置信息可以是从属于BWP-UplinkDedicated的pucch-Config；第二配置信息可以是从属于BWP-UplinkDedicated的pucch-ConfigurationList。
其中，pucch-ConfigurationList可以包括一组或两组PUCCH配置信息，PUCCH 配置信息例如被表示为PUCCH-Config，PUCCH配置信息是用于配置终端设备特定PUCCH参数(UE specific PUCCH参数)的IE。
实例一、
在操作801中，网络设备向终端设备提供第一配置信息，即pucch-Config，其中该第一配置信息从属于上行带宽部分(UL BWP)的专用参数(dedicated parameters)配置信息(BWP-UplinkDedicated)；并且，网络设备没有提供第二配置信息，即，没有在该BWP-UplinkDedicated中配置pucch-ConfigurationList。
在该pucch-Config所对应的ID最小的PUCCH资源被配置了PUCCH功率控制参数的情况下，在操作802中，网络设备可以根据该pucch-Config所对应的ID最小的PUCCH资源的功率控制参考信号(或者说，根据与该pucch-Config所对应的ID最小的PUCCH资源的功率控制参考信号具有相同索引的功率控制参考信号)，接收由DCI format 0_0调度的PUSCH。
根据实例一，终端设备在能够被提供pucch-ConfigurationList，却没有被提供pucch-ConfigurationList的情况下，网络设备根据pucch-Config得到由DCI format 0_0调度的PUSCH的功率控制参考信号，从而避免DCI format 0_0调度的PUSCH出现功率控制参考信号指示模糊的问题，能够准确地指示DCI format 0_0调度的PUSCH的功率控制参考信号，提升了系统稳定性。
实例二、
在操作801中，网络设备向终端设备提供第一配置信息，即pucch-Config，其中该第一配置信息从属于上行带宽部分(UL BWP)的专用参数(dedicated parameters)配置信息(BWP-UplinkDedicated)。此外，网络设备还可以向终端设备提供第二配置信息，即，网络设备在该BWP-UplinkDedicated中配置pucch-ConfigurationList。其中，该第二配置信息中仅具有一组PUCCH配置信息(pucch-Config)。
在该pucch-Config所对应的ID最小的PUCCH资源被配置了PUCCH功率控制参数的情况下，在操作802中，网络设备可以根据该pucch-Config所对应的ID最小的PUCCH资源的功率控制参考信号(或者说，根据与该pucch-Config所对应的ID最小的PUCCH资源的功率控制参考信号具有相同索引的功率控制参考信号)，接收由DCI format 0_0调度的PUSCH。
根据实例二，网络设备在提供了仅包括一组PUCCH配置信息的 pucch-ConfigurationList的情况下，网络设备根据BWP-UplinkDedicated中的配置信息pucch-Config得到由DCI format 0_0调度的PUSCH的功率控制参考信号，从而避免DCI format 0_0调度的PUSCH出现功率控制参考信号指示模糊的问题，能够准确地指示DCI format 0_0调度的PUSCH的功率控制参考信号，提升了系统稳定性。
实例三、
在操作801中，网络设备向终端设备提供第一配置信息，即pucch-Config，其中该第一配置信息从属于上行带宽部分(UL BWP)的专用参数(dedicated parameters)配置信息(in BWP-UplinkDedicated)。此外，网络设备还可以向终端设备提供第二配置信息，即，网络设备在该BWP-UplinkDedicated中配置pucch-ConfigurationList。其中，该第二配置信息中具有两组PUCCH配置信息(pucch-Config)。
在该pucch-Config所对应的ID最小的PUCCH资源被配置了PUCCH功率控制参数的情况下，在操作802中，网络设备可以根据该BWP-UplinkDedicated中的配置信息pucch-Config所对应的ID最小的PUCCH资源的功率控制参考信号(或者说，根据与该pucch-Config所对应的ID最小的PUCCH资源的功率控制参考信号具有相同索引的功率控制参考信号)，接收由DCI format 0_0调度的PUSCH。
根据实例三，网络设备在向终端设备提供了包括两组PUCCH配置信息的pucch-ConfigurationList的情况下，网络设备根据BWP-UplinkDedicated中配置的pucch-Config得到由DCI format 0_0调度的PUSCH的功率控制参考信号，从而避免DCI format 0_0调度的PUSCH出现功率控制参考信号指示模糊的问题，能够准确地指示DCI format 0_0调度的PUSCH的功率控制参考信号，提升了系统稳定性。
图9是本申请实施例的第四方面的上行信号接收方法的另一个示意图，如图9所示，该上行信号接收方法包括：
操作901、对终端设备配置与物理上行控制信道(PUCCH)相关的第二配置信息，其中，该第二配置信息是指用于至少两个同时组装的(simultaneous constructed)混合自动重复请求-确认(HARQ-ACK)码本(codebook)的物理上行控制信道(PUCCH)配置信息；以及
操作902、根据该第二配置信息所对应的物理上行控制信道(PUCCH)配置信息的功率控制参考信号(spatial relation)，在一个小区(cell)上，接收由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
根据本申请实施例的第四方面，能够根据第二配置信息对应的PUCCH配置信息的功率控制参考信号，接收由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)，也能够避免DCI format 0_0调度的PUSCH出现功率控制参考信号指示模糊的问题，从而准确地指示该功率控制参考信号。关于第二配置信息的说明与本申请实施例的第四方面的前述说明相同。
在至少一个实施例中，由于在步骤901中被配置了第二配置信息，终端设备可以生成至少两个混合自动重复请求-确认(HARQ-ACK)码本(codebook)。例如，终端设备可以根据配置信息生成两个HARQ-ACK码本，其中，该配置信息例如是物理下行共享信道混合自动重复请求确认码本列表(pdsch-HARQ-ACK-Codebook-List)，该配置信息是指在小区组特定L1参数(cell-group specific L1parameters)的配置信息中，用于至少两个同时组装的(simultaneous constructed)HARQ-ACK码本(codebook)的PUCCH配置信息，该配置信息(pdsch-HARQ-ACK-Codebook-List)不同于第二配置信息。另外，该配置信息可以分别确定每个HARQ-ACK码本的类型(该类型例如为动态或半静态)。
在第二配置信息包括一组物理上行控制信道(PUCCH)配置信息的情况下，网络设备可以根据该第二配置信息的该一组物理上行控制信道(PUCCH)配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的功率控制参考信号，接收由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
例如，在第二配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源被配置了PUCCH功率控制参数的情况下，网络设备可以根据第二配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的功率控制参考信号，接收由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
在第二配置信息包括两组物理上行控制信道(PUCCH)配置信息的情况下，该网络设备根据第二配置信息的两组物理上行控制信道(PUCCH)配置信息中的第一组物理上行控制信道(PUCCH)配置信息或第二组物理上行控制信道(PUCCH)配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的功率控制参考信号，接收由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
例如，在第一组物理上行控制信道(PUCCH)配置信息或所述第二组物理上行 控制信道(PUCCH)配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源被配置了PUCCH功率控制参数的情况下，终端设备可以根据该第一组物理上行控制信道(PUCCH)配置信息或该第二组物理上行控制信道(PUCCH)配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的功率控制参考信号，接收由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
此外，网络设备可以向终端设备配置第一配置信息或者不配置第一配置信息。关于第一配置信息的说明与本申请实施例的第四方面的前述说明相同。
下面，通过实例四、实例五和实例六，对图9所示的上行信号接收方法进行举例说明。在下述的实例四、实例五和实例六中：第二配置信息可以是从属于BWP-UplinkDedicated的pucch-ConfigurationList。
其中，pucch-ConfigurationList可以包括一组或两组PUCCH配置信息，PUCCH配置信息，例如，被表示为PUCCH-Config，PUCCH配置信息是用于配置终端设备特定PUCCH参数(UE specific PUCCH参数)的IE。
实例四、
在操作901中，网络设备向终端设备提供第二配置信息，即，pucch-ConfigurationList，该第二配置信息从属于上行带宽部分(UL BWP)的专用参数(dedicated parameters)配置信息(BWP-UplinkDedicated)。其中，该第二配置信息中仅具有一组PUCCH配置信息(pucch-Config)。
在该pucch-ConfigurationList的该一组PUCCH配置信息(pucch-Config)中ID最小的PUCCH资源被配置了PUCCH功率控制参数的情况下，在操作902中，网络设备可以根据pucch-ConfigurationList中的该一组PUCCH配置信息(pucch-Config)中ID最小的PUCCH资源的功率控制参考信号(或者说，根据与该一组pucch-Config所对应的ID最小的PUCCH资源的功率控制参考信号具有相同索引的功率控制参考信号)，接收由DCI format 0_0调度的PUSCH。
根据实例四，网络设备在提供了仅包括一组PUCCH配置信息的pucch-ConfigurationList的情况下，网络设备根据BWP-UplinkDedicated中的配置信息pucch-ConfigurationList中的该一组PUCCH配置信息得到由DCI format 0_0调度的PUSCH的功率控制参考信号，从而避免DCI format 0_0调度的PUSCH出现功率控制 参考信号指示模糊的问题，能够准确地指示DCI format 0_0调度的PUSCH的功率控制参考信号，提升了系统稳定性。
实例五、
在操作901中，网络设备向终端设备提供第二配置信息，即，pucch-ConfigurationList，该第二配置信息从属于上行带宽部分(UL BWP)的专用参数(dedicated parameters)配置信息(BWP-UplinkDedicated)。其中，该第二配置信息中具有两组PUCCH配置信息(pucch-Config)，该两组PUCCH配置信息(pucch-Config)例如包括第一组PUCCH配置信息(pucch-Config)和第二组PUCCH配置信息(pucch-Config)。
在操作902中，网络设备可以根据第一组PUCCH配置信息(pucch-Config)的功率控制参考信号来接收由DCI format 0_0调度的PUSCH。
例如，在pucch-ConfigurationList中的该第一组PUCCH配置信息(pucch-Config)中ID最小的PUCCH资源被配置了PUCCH功率控制参数的情况下，在操作902中网络设备可以根据pucch-ConfigurationList中的该第一组PUCCH配置信息(pucch-Config)中ID最小的PUCCH资源的功率控制参考信号(或者说，根据与该第一组pucch-Config所对应的ID最小的PUCCH资源的功率控制参考信号具有相同索引的功率控制参考信号)，接收由DCI format 0_0调度的PUSCH。
根据实例五，网络设备在提供了包括两组PUCCH配置信息的pucch-ConfigurationList的情况下，网络设备根据BWP-UplinkDedicated中的配置信息pucch-ConfigurationList中的该第一组PUCCH配置信息得到由DCI format 0_0调度的PUSCH的功率控制参考信号，从而避免DCI format 0_0调度的PUSCH出现功率控制参考信号指示模糊的问题，能够准确地指示DCI format 0_0调度的PUSCH的功率控制参考信号，提升了系统稳定性。
实例六、
在操作901中，网络设备向终端设备提供第二配置信息，即，pucch-ConfigurationList，该第二配置信息从属于上行带宽部分(UL BWP)的专用参数(dedicated parameters)配置信息(BWP-UplinkDedicated)。其中，该第二配置信息中具有两组PUCCH配置信息(pucch-Config)，该两组PUCCH配置信息(pucch-Config)例如包括第一组PUCCH配置信息(pucch-Config)和第二组PUCCH 配置信息(pucch-Config)。
在操作902中，网络设备可以根据第二组PUCCH配置信息(pucch-Config)的功率控制参考信号来接收由DCI format 0_0调度的PUSCH。
例如，在pucch-ConfigurationList中的该第二组PUCCH配置信息(pucch-Config)中ID最小的PUCCH资源被配置了PUCCH功率控制参数的情况下，在操作902中，网络设备可以根据pucch-ConfigurationList中的该第二组PUCCH配置信息(pucch-Config)中ID最小的PUCCH资源的功率控制参考信号(或者说，根据与该第二组pucch-Config所对应的ID最小的PUCCH资源的功率控制参考信号具有相同索引的功率控制参考信号)，接收由DCI format 0_0调度的PUSCH。
根据实例六，网络设备在提供了包括两组PUCCH配置信息的pucch-ConfigurationList的情况下，网络设备根据BWP-UplinkDedicated中的配置信息pucch-ConfigurationList中的该第二组PUCCH配置信息得到由DCI format 0_0调度的PUSCH的功率控制参考信号，从而避免DCI format 0_0调度的PUSCH出现功率控制参考信号指示模糊的问题，能够准确地指示DCI format 0_0调度的PUSCH的功率控制参考信号，提升了系统稳定性。
在上述实例四、实例五和实例六中，网络设备可以向终端设备配置第一配置信息，该第一配置信息例如可以从属于上行带宽部分(UL BWP)的专用参数(dedicated parameters)配置信息BWP-UplinkDedicated的PUCCH配置信息pucch-Config。此外，在上述实例四、实例五和实例六中，网络设备也可以不向终端设备配置第一配置信息。
根据本申请实施例的第四方面，能够根据第一配置信息或第二配置信息对应的PUCCH配置信息的功率控制参考信号，接收由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)，由此，能够避免DCI format 0_0调度的PUSCH出现功率控制参考信号指示模糊的问题，从而准确地指示该功率控制参考信号。
实施例的第五方面
本申请实施例的第五方面提供一种上行信号的发送装置，应用于终端设备，例如，终端设备102。
图10是本申请实施例的第五方面的上行信号的发送装置的一个示意图，如图10 所示，上行信号的发送装置1000包括第一处理单元1001。
第一处理单元1001可以实施本申请实施例的第一方面的图2所述的上行信号的发送方法。关于第一处理单元1001实施上行信号的发送方法方法的说明，可以参考本申请实施例的第一方面中对图2的说明。
图11是本申请实施例的第五方面的上行信号的发送装置的另一个示意图，如图11所示，上行信号的发送装置1100包括第二处理单元1101。
第二处理单元1101可以实施本申请实施例的第一方面的图3所述的上行信号的发送方法。关于第二处理单元1101实施上行信号的发送方法方法的说明，可以参考本申请实施例的第一方面中对图3的说明。
图12是本申请实施例的第五方面的上行信号的发送装置的又一个示意图，如图12所示，上行信号的发送装置1200包括第三处理单元1201。
第三处理单元1201可以实施本申请实施例的第二方面的图4所述的上行信号的发送方法。关于第三处理单元1201实施上行信号的发送方法方法的说明，可以参考本申请实施例的第二方面中对图4的说明。
图13是本申请实施例的第五方面的上行信号的发送方法装置的再一个示意图，如图13所示，上行信号的发送装置1300包括第四处理单元1301。
第四处理单元1301可以实施本申请实施例的第二方面的图5所述的上行信号的发送方法。关于第四处理单元1301实施上行信号的发送方法方法的说明，可以参考本申请实施例的第二方面中对图5的说明。
实施例的第六方面
本申请实施例的第六方面提供一种上行信号的接收装置，应用于网络设备，例如，网络设备101。
图14是本申请实施例的第六方面的上行信号的接收装置的一个示意图，如图14所示，上行信号的接收装置1400包括第五处理单元1401。
第五处理单元1401可以实施本申请实施例的第三方面的图6所述的上行信号的接收方法。关于第五处理单元1401实施上行信号的接收方法方法的说明，可以参考本申请实施例的第三方面中对图6的说明。
图15是本申请实施例的第六方面的上行信号的接收装置的另一个示意图，如图 15所示，上行信号的接收装置1500包括第六处理单元1501。
第六处理单元1501可以实施本申请实施例的第三方面的图7所述的上行信号的接收方法。关于第六处理单元1501实施上行信号的接收方法方法的说明，可以参考本申请实施例的第六方面中对图7的说明。
图16是本申请实施例的第六方面的上行信号的接收装置的又一个示意图，如图16所示，上行信号的接收装置1600包括第七处理单元1601。
第七处理单元1601可以实施本申请实施例的第三方面的图8所述的上行信号的接收方法。关于第七处理单元1601实施上行信号的接收方法的说明，可以参考本申请实施例的第三方面中对图8的说明。
图17是本申请实施例的第六方面的上行信号的接收装置的再一个示意图，如图17所示，上行信号的接收装置1700包括第八处理单元1701。
第八处理单元1701可以实施本申请实施例的第四方面的图9所述的上行信号的接收方法。关于第八处理单元1701实施上行信号的接收方法的说明，可以参考本申请实施例的第四方面中对图9的说明。
实施例的第七方面
本申请实施例的第七方面提供一种终端设备，该终端设备包括如实施例的第五方面所述的上行信号的发送装置1000、1100、1200或1300。
图18是本申请实施例的第七方面的终端设备1800的系统构成的一示意框图。如图18所示，该终端设备1800可以包括处理器1810和存储器1820；存储器1820耦合到处理器1810。值得注意的是，该图是示例性的；还可以使用其他类型的结构，来补充或代替该结构，以实现电信功能或其他功能。
在一个实施方式中，上行信号的发送装置1000、1100、1200或1300的功能可以被集成到处理器1810中。其中，处理器1810可以被配置为能够实施实施例的第一方面或第二方面的上行信号的发送方法。
在另一个实施方式中，上行信号的发送装置1000、1100、1200或1300可以与处理器1810分开配置，例如可以将上行信号的发送装置1000、1100、1200或1300配置为与处理器1810连接的芯片，通过处理器1810的控制来实现上行信号的发送装置1000、1100、1200或1300的功能。
如图18所示，该终端设备1800还可以包括：通信模块1830、输入单元1840、显示器1850、电源1860。值得注意的是，终端设备1800也并不是必须要包括图18中所示的所有部件；此外，终端设备1800还可以包括图18中没有示出的部件，可以参考现有技术。
如图18所示，处理器1810有时也称为控制器或操作控件，可以包括微处理器或其他处理器装置和/或逻辑装置，该处理器1810接收输入并控制终端设备1800的各个部件的操作。
其中，存储器1820，例如可以是缓存器、闪存、硬驱、可移动介质、易失性存储器、非易失性存储器或其它合适装置中的一种或更多种。可储存各种数据，此外还可存储执行有关信息的程序。并且处理器1810可执行该存储器1820存储的该程序，以实现信息存储或处理等。其他部件的功能与现有类似，此处不再赘述。终端设备1800的各部件可以通过专用硬件、固件、软件或其结合来实现，而不偏离本申请的范围。
实施例的第八方面
本申请实施例的第八方面提供一种网络设备，该网络设备包括如实施例的第六方面所述的上行信号的接收装置1400、1500、1600或1700。
图19是本申请实施例的网络设备的一构成示意图。如图19所示，网络设备1900可以包括：处理器(processor)1910和存储器1920；存储器1920耦合到处理器1910。其中该存储器1920可存储各种数据；此外还存储信息处理的程序1930，并且在处理器1910的控制下执行该程序1930，以接收用户设备发送的各种信息、并且向用户设备发送请求信息。
在一个实施方式中，上行信号的接收装置1400、1500、1600或1700的功能可以被集成到处理器1910中。其中，处理器1910可以被配置为能够实施本申请实施例的第二方面所述的随机接入方法。
在另一个实施方式中，上行信号的接收装置1400、1500、1600或1700可以与处理器1910分开配置，例如可以将上行信号的接收装置1400、1500、1600或1700配置为与处理器1910连接的芯片，通过处理器1910的控制来实现上行信号的接收装置1400、1500、1600或1700的功能。
此外，如图19所示，网络设备1900还可以包括：收发机1940和天线1950等；其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，网络设备1900也并不是必须要包括图19中所示的所有部件；此外，网络设备1900还可以包括图19中没有示出的部件，可以参考现有技术。
实施例的第九方面
本申请实施例的第九方面还提供一种通信系统，包括如实施例的第八方面所述的网络设备以及如实施例的第七方面所述的终端设备。
本申请以上的装置和方法可以由硬件实现，也可以由硬件结合软件实现。本申请涉及这样的计算机可读程序，当该程序被逻辑部件所执行时，能够使该逻辑部件实现上文所述的装置或构成部件，或使该逻辑部件实现上文所述的各种方法或步骤。本申请还涉及用于存储以上程序的存储介质，如硬盘、磁盘、光盘、DVD、flash存储器等。
结合本申请实施例描述的方法/装置可直接体现为硬件、由处理器执行的软件模块或二者组合。例如，图中所示的功能框图中的一个或多个和/或功能框图的一个或多个组合，既可以对应于计算机程序流程的各个软件模块，亦可以对应于各个硬件模块。这些软件模块，可以分别对应于图中所示的各个步骤。这些硬件模块例如可利用现场可编程门阵列(FPGA)将这些软件模块固化而实现。
软件模块可以位于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动磁盘、CD-ROM或者本领域已知的任何其它形式的存储介质。可以将一种存储介质耦接至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息；或者该存储介质可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。该软件模块可以存储在移动终端的存储器中，也可以存储在可插入移动终端的存储卡中。例如，若设备(如移动终端)采用的是较大容量的MEGA-SIM卡或者大容量的闪存装置，则该软件模块可存储在该MEGA-SIM卡或者大容量的闪存装置中。
针对附图中描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，可以实现为用于执行本申请所描述功能的通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其它可编程逻辑器件、分立 门或者晶体管逻辑器件、分立硬件组件或者其任意适当组合。针对附图描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，还可以实现为计算设备的组合，例如，DSP和微处理器的组合、多个微处理器、与DSP通信结合的一个或多个微处理器或者任何其它这种配置。
以上结合具体的实施方式对本申请进行了描述，但本领域技术人员应该清楚，这些描述都是示例性的，并不是对本申请保护范围的限制。本领域技术人员可以根据本申请的精神和原理对本申请做出各种变型和修改，这些变型和修改也在本申请的范围内。
关于包括以上实施例的实施方式，还公开下述的附记：
1.一种上行信号的发送方法，应用于终端设备，所述终端设备具有同时组装或生成至少两个混合自动重复请求-确认码本(HARQ-ACK codebook)的能力，所述方法包括：
被网络设备配置与物理上行控制信道(PUCCH)相关的第一配置信息；以及
根据所述第一配置信息所对应的物理上行控制信道(PUCCH)配置信息的空间关系，在一个小区(cell)上，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
2.如附记1所述的方法，其中，
所述第一配置信息从属于所述小区的激活(active)上行带宽部分(BWP)的专用参数(dedicated parameters)配置信息。
3.如附记1所述的方法，其中，所述方法还包括：
向所述网络设备发送报告消息，所述报告消息向所述网络设备报告所述终端设备具有同时组装或生成至少两个混合自动重复请求-确认码本(HARQ-ACK codebook)的能力。
4.如附记1所述的方法，其中，
所述终端设备没有被网络设备配置与物理上行控制信道(PUCCH)相关的第二配置信息，
其中，
所述第二配置信息是指用于(for)至少两个同时组装的(simultaneous constructed)混合自动重复请求-确认(HARQ-ACK)码本(codebook)的物理上行控制信道 (PUCCH)配置信息。
5.如附记1所述的方法，其中，
所述终端设备被网络设备配置与物理上行控制信道(PUCCH)相关的第二配置信息，
其中，
所述第二配置信息是指用于至少两个同时组装的(simultaneous constructed)混合自动重复请求-确认(HARQ-ACK)码本(codebook)的物理上行控制信道(PUCCH)配置信息。
6.如附记4或5所述的方法，其中，
所述第二配置信息从属于所述小区的激活上行带宽部分(BWP)的专用参数(dedicated parameters)配置信息。
7.如附记5所述的方法，其中，
所述第二配置信息包括1组物理上行控制信道(PUCCH)配置信息或者2组以上的物理上行控制信道(PUCCH)配置信息。
8.如附记1所述的方法，其中，
所述终端设备根据所述第一配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的空间关系，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
9.如附记1所述的方法，其中，
所述第一配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源被配置了空间配置信息(spatial setting)或适用(is applicable to)空间关系。
10.一种上行信号的发送方法，应用于终端设备，所述方法包括：
被网络设备配置与物理上行控制信道(PUCCH)相关的第二配置信息，其中，所述第二配置信息是指用于至少两个同时组装的(simultaneous constructed)混合自动重复请求-确认(HARQ-ACK)码本(codebook)的物理上行控制信道(PUCCH)配置信息；以及
根据所述第二配置信息所对应的物理上行控制信道(PUCCH)配置信息的空间关系，在一个小区(cell)上，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
11.如附记10所述的方法，其中，
所述终端设备生成至少两个混合自动重复请求-确认(HARQ-ACK)码本(codebook)。
12.如附记10所述的方法，其中，
所述第二配置信息从属于所述小区的激活的上行带宽部分(BWP)的专用参数(dedicated parameters)配置信息。
13.如附记10所述的方法，其中，
所述第二配置信息包括1组物理上行控制信道(PUCCH)配置信息。
14.如附记13所述的方法，其中，
所述终端设备根据所述第二配置信息的所述1组物理上行控制信道(PUCCH)配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的空间关系，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
15.如附记13所述的方法，其中，
所述第二配置信息的所述1组物理上行控制信道(PUCCH)配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源被配置了空间配置信息或适用(is applicable to)空间关系。
16.如附记10所述的方法，其中，
所述第二配置信息包括2组物理上行控制信道(PUCCH)配置信息。
17.如附记16所述的方法，其中，
所述终端设备根据所述第二配置信息的2组物理上行控制信道(PUCCH)配置信息中的第一组物理上行控制信道(PUCCH)配置信息或第二组物理上行控制信道(PUCCH)配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的空间关系，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
18.如附记16所述的方法，其中，
所述第一组物理上行控制信道(PUCCH)配置信息或所述第二组物理上行控制信道(PUCCH)配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源被配置了空间配置信息或适用(is applicable to)空间关系。
19.一种上行信号的发送方法，应用于终端设备，所述终端设备具有同时组装或生成至少两个混合自动重复请求-确认码本(HARQ-ACK codebook)的能力，所述方法包括：
被网络设备配置与物理上行控制信道(PUCCH)相关的第一配置信息；以及
根据所述第一配置信息所对应的物理上行控制信道(PUCCH)配置信息的功率控制参考信号，在一个小区(cell)上，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
20.如附记19所述的方法，其中，
所述第一配置信息从属于所述小区的激活(active)上行带宽部分(BWP)的专用参数(dedicated parameters)配置信息。
21.如附记19所述的方法，其中，所述方法还包括：
向所述网络设备发送报告消息，所述报告消息向所述网络设备报告所述终端设备具有同时组装或生成至少两个混合自动重复请求-确认码本(HARQ-ACK codebook)的能力。
22.如附记19所述的方法，其中，
所述终端设备没有被网络设备配置与物理上行控制信道(PUCCH)相关的第二配置信息，
其中，
所述第二配置信息是指用于(for)至少两个同时组装的(simultaneous constructed)混合自动重复请求-确认(HARQ-ACK)码本(codebook)的物理上行控制信道(PUCCH)配置信息。
23.如附记19所述的方法，其中，
所述终端设备被网络设备配置与物理上行控制信道(PUCCH)相关的第二配置信息，
其中，
所述第二配置信息是指用于至少两个同时组装的(simultaneous constructed)混合自动重复请求-确认(HARQ-ACK)码本(codebook)的物理上行控制信道(PUCCH)配置信息。
24.如附记22或23所述的方法，其中，
所述第二配置信息从属于所述小区的激活上行带宽部分(BWP)的专用参数(dedicated parameters)配置信息。
25.如附记23所述的方法，其中，
所述第二配置信息包括1组物理上行控制信道(PUCCH)配置信息或者2组以上的物理上行控制信道(PUCCH)配置信息。
26.如附记19所述的方法，其中，
所述终端设备根据所述第一配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的功率控制参考信号，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
27.如附记19所述的方法，其中，
所述第一配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源被配置了PUCCH功率控制参数。
28.一种上行信号的发送方法，应用于终端设备，所述方法包括：
被网络设备配置与物理上行控制信道(PUCCH)相关的第二配置信息，其中，所述第二配置信息是指用于至少两个同时组装的(simultaneous constructed)混合自动重复请求-确认(HARQ-ACK)码本(codebook)的物理上行控制信道(PUCCH)配置信息；以及
根据所述第二配置信息所对应的物理上行控制信道(PUCCH)配置信息的功率控制参考信号，在一个小区(cell)上，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
29.如附记28所述的方法，其中，
所述终端设备生成至少两个混合自动重复请求-确认(HARQ-ACK)码本(codebook)。
30.如附记28所述的方法，其中，
所述第二配置信息从属于所述小区的激活的上行带宽部分(BWP)的专用参数(dedicated parameters)配置信息。
31.如附记28所述的方法，其中，
所述第二配置信息包括1组物理上行控制信道(PUCCH)配置信息。
32.如附记31所述的方法，其中，
所述终端设备根据所述第二配置信息的所述1组物理上行控制信道(PUCCH)配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的功率控制参考信号，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
33.如附记31所述的方法，其中，
所述第二配置信息的所述1组物理上行控制信道(PUCCH)配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源被配置了PUCCH功率控制参数。
34.如附记28所述的方法，其中，
所述第二配置信息包括2组物理上行控制信道(PUCCH)配置信息。
35.如附记34所述的方法，其中，
所述终端设备根据所述第二配置信息的2组物理上行控制信道(PUCCH)配置信息中的第一组物理上行控制信道(PUCCH)配置信息或第二组物理上行控制信道(PUCCH)配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的功率控制参考信号，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
36.如附记34所述的方法，其中，
所述第一组物理上行控制信道(PUCCH)配置信息或所述第二组物理上行控制信道(PUCCH)配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源被配置了PUCCH功率控制参数。
37.一种上行信号的接收方法，应用于网络设备，所述方法包括：
所述网络设备为终端设备配置与物理上行控制信道(PUCCH)相关的第一配置信息，所述终端设备具有同时组装或生成至少两个混合自动重复请求-确认码本(HARQ-ACK codebook)的能力；以及
根据所述第一配置信息所对应的物理上行控制信道(PUCCH)配置信息的空间关系，在一个小区(cell)上，接收由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
38.如附记37所述的方法，其中，
所述第一配置信息从属于所述小区的激活(active)上行带宽部分(BWP)的专 用参数(dedicated parameters)配置信息。
39.如附记37所述的方法，其中，所述方法还包括：
接收所述终端设备发送的报告消息，所述报告消息向所述网络设备报告所述终端设备具有同时组装或生成至少两个混合自动重复请求-确认码本(HARQ-ACK codebook)的能力。
40.如附记37所述的方法，其中，
所述网络设备没有为所述终端设备配置与物理上行控制信道(PUCCH)相关的第二配置信息，
其中，
所述第二配置信息是指用于(for)至少两个同时组装的(simultaneous constructed)混合自动重复请求-确认(HARQ-ACK)码本(codebook)的物理上行控制信道(PUCCH)配置信息。
41.如附记37所述的方法，其中，
所述网络设备为所述终端设备配置与物理上行控制信道(PUCCH)相关的第二配置信息，
其中，
所述第二配置信息是指用于至少两个同时组装的(simultaneous constructed)混合自动重复请求-确认(HARQ-ACK)码本(codebook)的物理上行控制信道(PUCCH)配置信息。
42.如附记40或41所述的方法，其中，
所述第二配置信息从属于所述小区的激活上行带宽部分(BWP)的专用参数(dedicated parameters)配置信息。
43.如附记41所述的方法，其中，
所述第二配置信息包括1组物理上行控制信道(PUCCH)配置信息或者2组以上的物理上行控制信道(PUCCH)配置信息。
44.如附记37所述的方法，其中，
所述网络设备根据所述第一配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的空间关系，接收由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
45.如附记37所述的方法，其中，
所述第一配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源被配置了空间配置信息或适用(is applicable to)空间关系。
46.一种上行信号的接收方法，应用于网络设备，所述方法包括：
所述网络设备为终端设备配置与物理上行控制信道(PUCCH)相关的第二配置信息，其中，所述第二配置信息是指用于至少两个同时组装的(simultaneous constructed)混合自动重复请求-确认(HARQ-ACK)码本(codebook)的物理上行控制信道(PUCCH)配置信息；以及
根据所述第二配置信息所对应的物理上行控制信道(PUCCH)配置信息的空间关系，在一个小区(cell)上，接收由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
47.如附记46所述的方法，其中，
所述第二配置信息从属于所述小区的激活的上行带宽部分(BWP)的专用参数(dedicated parameters)配置信息。
48.如附记46所述的方法，其中，
所述第二配置信息包括1组物理上行控制信道(PUCCH)配置信息。
49.如附记48所述的方法，其中，
所述网络设备根据所述第二配置信息的所述1组物理上行控制信道(PUCCH)配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的空间关系，接收由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
50.如附记48所述的方法，其中，
所述第二配置信息的所述1组物理上行控制信道(PUCCH)配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源被配置了所述空间配置信息或适用(is applicable to)空间关系。
51.如附记46所述的方法，其中，
所述第二配置信息包括2组物理上行控制信道(PUCCH)配置信息。
52.如附记51所述的方法，其中，
所述网络设备根据所述第二配置信息的2组物理上行控制信道(PUCCH)配置 信息中的第一组物理上行控制信道(PUCCH)配置信息或第二组物理上行控制信道(PUCCH)配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的空间关系，接收由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
53.如附记51所述的方法，其中，
所述第一组物理上行控制信道(PUCCH)配置信息或所述第二组物理上行控制信道(PUCCH)配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源被配置了所述空间配置信息或适用(is applicable to)空间关系。
54.一种上行信号的接收方法，应用于网络设备，所述方法包括：
所述网络设备为终端设备配置与物理上行控制信道(PUCCH)相关的第一配置信息，所述终端设备具有同时组装或生成至少两个混合自动重复请求-确认码本(HARQ-ACK codebook)的能力；以及
根据所述第一配置信息所对应的物理上行控制信道(PUCCH)配置信息的功率控制参考信号，在一个小区(cell)上，接收由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
55.如附记54所述的方法，其中，
所述第一配置信息从属于所述小区的激活(active)上行带宽部分(BWP)的专用参数(dedicated parameters)配置信息。
56.如附记54所述的方法，其中，所述方法还包括：
接收所述终端设备发送的报告消息，所述报告消息向所述网络设备报告所述终端设备具有同时组装或生成至少两个混合自动重复请求-确认码本(HARQ-ACK codebook)的能力。
57.如附记54所述的方法，其中，
所述网络设备没有为所述终端设备配置与物理上行控制信道(PUCCH)相关的第二配置信息，
其中，
所述第二配置信息是指用于(for)至少两个同时组装的(simultaneous constructed)混合自动重复请求-确认(HARQ-ACK)码本(codebook)的物理上行控制信道 (PUCCH)配置信息。
58.如附记54所述的方法，其中，
所述网络设备为所述终端设备配置与物理上行控制信道(PUCCH)相关的第二配置信息，
其中，
所述第二配置信息是指用于至少两个同时组装的(simultaneous constructed)混合自动重复请求-确认(HARQ-ACK)码本(codebook)的物理上行控制信道(PUCCH)配置信息。
59.如附记57或58所述的方法，其中，
所述第二配置信息从属于所述小区的激活上行带宽部分(BWP)的专用参数(dedicated parameters)配置信息。
60.如附记58所述的方法，其中，
所述第二配置信息包括1组物理上行控制信道(PUCCH)配置信息或者2组以上的物理上行控制信道(PUCCH)配置信息。
61.如附记54所述的方法，其中，
所述网络设备根据所述第一配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的功率控制参考信号，接收由下行控制信号格式0_0(DCI format0_0)调度的物理上行共享信道(PUSCH)。
62.如附记54所述的方法，其中，
所述第一配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源被配置了PUCCH功率控制参数。
63.一种上行信号的发接收方法，应用于网络设备，所述方法包括：
所述网络设备为终端设备配置与物理上行控制信道(PUCCH)相关的第二配置信息，其中，所述第二配置信息是指用于至少两个同时组装的(simultaneous constructed)混合自动重复请求-确认(HARQ-ACK)码本(codebook)的物理上行控制信道(PUCCH)配置信息；以及
根据所述第二配置信息所对应的物理上行控制信道(PUCCH)配置信息的功率控制参考信号，在一个小区(cell)上，接收由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
64.如附记63所述的方法，其中，
所述第二配置信息从属于所述小区的激活的上行带宽部分(BWP)的专用参数(dedicated parameters)配置信息。
65.如附记63所述的方法，其中，
所述第二配置信息包括1组物理上行控制信道(PUCCH)配置信息。
66.如附记65所述的方法，其中，
所述网络设备根据所述第二配置信息的所述1组物理上行控制信道(PUCCH)配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的功率控制参考信号，接收由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
67.如附记65所述的方法，其中，
所述第二配置信息的所述1组物理上行控制信道(PUCCH)配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源被配置了PUCCH功率控制参数。
68.如附记63所述的方法，其中，
所述第二配置信息包括2组物理上行控制信道(PUCCH)配置信息。
69.如附记68所述的方法，其中，
所述网络设备根据所述第二配置信息的2组物理上行控制信道(PUCCH)配置信息中的第一组物理上行控制信道(PUCCH)配置信息或第二组物理上行控制信道(PUCCH)配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的功率控制参考信号，接收由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
70.如附记68所述的方法，其中，
所述第一组物理上行控制信道(PUCCH)配置信息或所述第二组物理上行控制信道(PUCCH)配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源被配置了PUCCH功率控制参数。

Claims (20)

  1. 一种上行信号的发送装置，应用于终端设备，所述终端设备具有同时组装或生成至少两个混合自动重复请求-确认码本(HARQ-ACK codebook)的能力，所述装置包括第一处理单元，所述第一处理单元被配置为：
    被网络设备配置与物理上行控制信道(PUCCH)相关的第一配置信息；以及
    根据所述第一配置信息所对应的物理上行控制信道(PUCCH)配置信息的空间关系，在一个小区(cell)上，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
  2. 如权利要求1所述的装置，其中，
    所述第一配置信息从属于所述小区的激活(active)上行带宽部分(BWP)的专用参数(dedicated parameters)配置信息。
  3. 如权利要求1所述的装置，其中，
    所述终端设备没有被网络设备配置与物理上行控制信道(PUCCH)相关的第二配置信息，
    其中，
    所述第二配置信息是指用于(for)至少两个同时组装的(simultaneous constructed)混合自动重复请求-确认(HARQ-ACK)码本(codebook)的物理上行控制信道(PUCCH)配置信息。
  4. 如权利要求1所述的装置，其中，
    所述终端设备被网络设备配置与物理上行控制信道(PUCCH)相关的第二配置信息，
    其中，
    所述第二配置信息是指用于至少两个同时组装的(simultaneous constructed)混合自动重复请求-确认(HARQ-ACK)码本(codebook)的物理上行控制信道(PUCCH)配置信息。
  5. 如权利要求3所述的装置，其中，
    所述第二配置信息从属于所述小区的激活上行带宽部分(BWP)的专用参数(dedicated parameters)配置信息。
  6. 如权利要求1所述的装置，其中，
    所述终端设备根据所述第一配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的空间关系，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
  7. 如权利要求1所述的装置，其中，
    所述第一配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源被配置了空间配置信息(spatial setting)或适用(is applicable to)空间关系。
  8. 一种上行信号的发送装置，应用于终端设备，所述装置包括第二处理单元，所述第二处理单元被配置为：
    被网络设备配置与物理上行控制信道(PUCCH)相关的第二配置信息，其中，所述第二配置信息是指用于至少两个同时组装的(simultaneous constructed)混合自动重复请求-确认(HARQ-ACK)码本(codebook)的物理上行控制信道(PUCCH)配置信息；以及
    根据所述第二配置信息所对应的物理上行控制信道(PUCCH)配置信息的空间关系，在一个小区(cell)上，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
  9. 如权利要求8所述的装置，其中，
    所述第二配置信息从属于所述小区的激活的上行带宽部分(BWP)的专用参数(dedicated parameters)配置信息。
  10. 如权利要求8所述的装置，其中，
    所述第二配置信息包括1组物理上行控制信道(PUCCH)配置信息。
  11. 如权利要求10所述的装置，其中，
    所述终端设备根据所述第二配置信息的所述1组物理上行控制信道(PUCCH)配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的空间关系，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
  12. 如权利要求10所述的装置，其中，
    所述第二配置信息的所述1组物理上行控制信道(PUCCH)配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源被配置了空间配置信息或适 用(is applicable to)空间关系。
  13. 如权利要求8所述的装置，其中，
    所述第二配置信息包括2组物理上行控制信道(PUCCH)配置信息。
  14. 如权利要求13所述的装置，其中，
    所述终端设备根据所述第二配置信息的2组物理上行控制信道(PUCCH)配置信息中的第一组物理上行控制信道(PUCCH)配置信息或第二组物理上行控制信道(PUCCH)配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的空间关系，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
  15. 如权利要求13所述的装置，其中，
    所述第一组物理上行控制信道(PUCCH)配置信息或所述第二组物理上行控制信道(PUCCH)配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源被配置了空间配置信息或适用(is applicable to)空间关系。
  16. 一种上行信号的发送装置，应用于终端设备，所述终端设备具有同时组装或生成至少两个混合自动重复请求-确认码本(HARQ-ACK codebook)的能力，所述装置包括第三处理单元，所述第三处理单元被配置为：
    被网络设备配置与物理上行控制信道(PUCCH)相关的第一配置信息；以及
    根据所述第一配置信息所对应的物理上行控制信道(PUCCH)配置信息的功率控制参考信号，在一个小区(cell)上，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
  17. 如权利要求16所述的装置，其中，
    所述第一配置信息从属于所述小区的激活(active)上行带宽部分(BWP)的专用参数(dedicated parameters)配置信息。
  18. 如权利要求16所述的装置，其中，
    所述终端设备被网络设备配置与物理上行控制信道(PUCCH)相关的第二配置信息，
    其中，
    所述第二配置信息是指用于至少两个同时组装的(simultaneous constructed)混合自动重复请求-确认(HARQ-ACK)码本(codebook)的物理上行控制信道(PUCCH) 配置信息。
  19. 如权利要求16所述的装置，其中，
    所述终端设备根据所述第一配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源的功率控制参考信号，发送由下行控制信号格式0_0(DCI format 0_0)调度的物理上行共享信道(PUSCH)。
  20. 如权利要求16所述的装置，其中，
    所述第一配置信息所对应的标识号(ID)最小的物理上行控制信道(PUCCH)资源被配置了PUCCH功率控制参数。
PCT/CN2020/075079 2020-02-13 2020-02-13 上行信号的发送和接收方法、装置和通信系统 WO2021159386A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/075079 WO2021159386A1 (zh) 2020-02-13 2020-02-13 上行信号的发送和接收方法、装置和通信系统

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/075079 WO2021159386A1 (zh) 2020-02-13 2020-02-13 上行信号的发送和接收方法、装置和通信系统

Publications (1)

Publication Number Publication Date
WO2021159386A1 true WO2021159386A1 (zh) 2021-08-19

Family

ID=77292655

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/075079 WO2021159386A1 (zh) 2020-02-13 2020-02-13 上行信号的发送和接收方法、装置和通信系统

Country Status (1)

Country Link
WO (1) WO2021159386A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109905211A (zh) * 2017-12-08 2019-06-18 电信科学技术研究院 一种传输、接收方法、终端及基站
US20190306841A1 (en) * 2018-03-28 2019-10-03 Asustek Computer Inc. Method and apparatus for determining codebook size in a wireless communication system
CN110311762A (zh) * 2019-07-16 2019-10-08 北京展讯高科通信技术有限公司 反馈信息传输方法、装置、终端及存储介质
CN110475360A (zh) * 2018-05-10 2019-11-19 华硕电脑股份有限公司 无线通信系统中上行链路传送的波束指示的方法和设备
CN110536435A (zh) * 2019-02-15 2019-12-03 中兴通讯股份有限公司 一种传输信息的方法和装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109905211A (zh) * 2017-12-08 2019-06-18 电信科学技术研究院 一种传输、接收方法、终端及基站
US20190306841A1 (en) * 2018-03-28 2019-10-03 Asustek Computer Inc. Method and apparatus for determining codebook size in a wireless communication system
CN110475360A (zh) * 2018-05-10 2019-11-19 华硕电脑股份有限公司 无线通信系统中上行链路传送的波束指示的方法和设备
CN110536435A (zh) * 2019-02-15 2019-12-03 中兴通讯股份有限公司 一种传输信息的方法和装置
CN110311762A (zh) * 2019-07-16 2019-10-08 北京展讯高科通信技术有限公司 反馈信息传输方法、装置、终端及存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI,: "CR to 38.212 capturing the RAN1 #92bis agreements,", 3GPP TSG RAN WG1 MEETING #92BIS, R1-1805794,, 20 April 2018 (2018-04-20), XP051461511 *

Similar Documents

Publication Publication Date Title
WO2020220910A1 (en) Method and apparatus for handling sidelink reports
WO2020191740A1 (zh) 信号接收或发送方法、装置和系统
CN110932820A (zh) 发送和接收上行控制信息的方法以及通信装置
US20220014901A1 (en) Method and apparatus for identifying user equipment capability in sidelink transmission
TWI829756B (zh) 一種通訊方法、終端設備和網路設備
WO2020088189A1 (en) Method and apparatus for lbt option selection for wideband operation
JP7419553B2 (ja) フィードバックリソース決定方法およびフィードバックリソース決定装置
WO2021159386A1 (zh) 上行信号的发送和接收方法、装置和通信系统
US20210376968A1 (en) Feedback method and apparatus
US20220295574A1 (en) Method and apparatus for channel state information
WO2021226972A1 (zh) 边链路反馈信息的发送和接收方法以及装置
WO2021203438A1 (zh) 发送数据的方法、装置和通信系统
KR20240068679A (ko) 신호 송수신 방법 및 장치, 및 통신 시스템
WO2021159381A1 (zh) 上行信号处理方法、装置和系统
WO2021159401A1 (zh) 随机接入方法、装置和通信系统
WO2020087361A1 (zh) 信号发送方法、天线面板信息的指示方法、装置和系统
WO2023206293A1 (zh) 信号发送和接收装置以及方法
WO2023206302A1 (zh) 信号发送、信号接收装置以及方法
WO2024060078A1 (zh) 信息收发方法与装置
WO2024031696A1 (zh) 信道状态信息的上报方法和装置
WO2024031290A1 (zh) 信息收发方法与装置
US20230397201A1 (en) Method and apparatus for supporting more users in a multicast group
WO2024026858A1 (zh) 上行数据发送、上行数据接收装置以及方法
WO2023206272A1 (zh) 波束信息的发送和接收方法、装置和通信系统
WO2024016230A1 (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: 20918813

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

Country of ref document: EP

Kind code of ref document: A1