WO2020143692A1 - 通信方法和通信装置 - Google Patents

通信方法和通信装置 Download PDF

Info

Publication number
WO2020143692A1
WO2020143692A1 PCT/CN2020/071007 CN2020071007W WO2020143692A1 WO 2020143692 A1 WO2020143692 A1 WO 2020143692A1 CN 2020071007 W CN2020071007 W CN 2020071007W WO 2020143692 A1 WO2020143692 A1 WO 2020143692A1
Authority
WO
WIPO (PCT)
Prior art keywords
cell
trp
terminal device
configuration
configuration parameters
Prior art date
Application number
PCT/CN2020/071007
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 EP20738425.6A priority Critical patent/EP3902149A4/en
Priority to JP2021540208A priority patent/JP7358481B2/ja
Publication of WO2020143692A1 publication Critical patent/WO2020143692A1/zh
Priority to US17/371,352 priority patent/US20210377920A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/022—Site diversity; Macro-diversity
    • H04B7/024—Co-operative use of antennas of several sites, e.g. in co-ordinated multipoint or co-operative multiple-input multiple-output [MIMO] systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/022—Site diversity; Macro-diversity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H04L1/1671—Details of the supervisory signal the supervisory signal being transmitted together with control information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0686—Hybrid systems, i.e. switching and simultaneous transmission
    • H04B7/0695—Hybrid systems, i.e. switching and simultaneous transmission using beam selection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/08—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the receiving station
    • H04B7/0868—Hybrid systems, i.e. switching and combining
    • H04B7/088—Hybrid systems, i.e. switching and combining using beam selection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/046—Wireless resource allocation based on the type of the allocated resource the resource being in the space domain, e.g. beams
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment

Definitions

  • the present application relates to the field of communication, and more specifically, to a communication method and a communication device.
  • the 3rd Generation Partnership Project (3GPP) Wireless Access Network Working Group I (radio access network #working group#1, RAN1) research supports multiple transceivers in a cell Point transmission (multiple transmit point transmission, Multi-TRP transmission) mechanism.
  • TRP Multiple transmission and reception points
  • the present application provides a communication method and a communication device, so that the terminal device can communicate with multiple transceiver points in the cell, and the communication efficiency is guaranteed as much as possible.
  • a communication method is provided.
  • the method may be executed by the terminal device, or may also be executed by a chip or circuit configured in the terminal device, which is not limited in this application.
  • the method includes: receiving configuration information of the serving cell, the configuration information including N sets of configuration parameters related to the downlink control channel corresponding to the serving cell, wherein each set of configuration parameters includes the same parameter type, and N is greater than or equal to Integer of 2; communicate with the serving cell based on N sets of configuration parameters related to the downlink control channel.
  • the serving cell may be a cell configured for uplink and downlink transmission between the network and the terminal device.
  • the communication between the terminal device and the serving cell may also be understood as that the terminal device communicates with the serving cell through transmission resources (for example, frequency domain resources, or spectrum resources) allocated by the serving cell (or the network device to which the serving cell belongs). Communicate with the transceiver point in the.
  • the transceiver point may be a transmission and reception point (transmission and reception point, TRP), and may also be called an access device or a transmission point.
  • TRP transmission and reception point
  • TRP transmission and reception point
  • its naming should not constitute any limitation on this application, and this application is not excluded from future agreements Define other names to indicate the same or similar meanings. In the embodiment of the present application, it is represented by a transceiver point (TRP).
  • N sets of configuration parameters related to the downlink control channel can be understood as that the serving cell includes N transceiver points, and the terminal device can communicate with N transceiver points in the serving cell.
  • the N sets of downlink control channel related configuration parameters correspond to N transceiver points in the serving cell, or each transceiver point corresponds to a set of configuration parameters related to the downlink control channel.
  • Each transceiver point can transmit data with the terminal device based on its corresponding configuration parameters related to the downlink control channel.
  • N sets of configuration parameters related to the downlink control channel can be understood as that the serving cell includes N transceiver points, and when the terminal device communicates with each of the N transceiver points, a corresponding chain can be used respectively Communication, the terminal device can communicate with N links in the serving cell, and the N sets of configuration parameters related to the downlink control channel correspond to the N links between the serving cell and the terminal device, or each link Corresponds to a set of configuration parameters related to the downlink control channel. Each link can transmit data with the terminal device based on its corresponding configuration parameter related to the downlink control channel.
  • the configuration information of the serving cell includes N sets of configuration parameters related to the downlink control channel, and each set of configuration parameters includes the same parameter type, that is, each set of configuration parameters corresponds to a transceiver point in the serving cell
  • the network device configures a set of configuration parameters related to the downlink control channel for each transceiver point in the serving cell. Then, each transceiver point in the serving cell may transmit data with the terminal device based on its corresponding configuration parameter (or the configuration parameter configured for it, or its associated configuration parameter).
  • the method further includes: receiving first downlink control information DCI, and the configuration parameter corresponding to the first DCI belongs to one of N sets of configuration parameters related to the downlink control channel Set; according to the first DCI, determine the link corresponding to the first DCI.
  • receiving the first downlink control information (DCI) from the serving cell can be understood as receiving from a transceiver point in the serving cell (or the transceiver point through its link with the terminal device) DCI sent.
  • the DCI when the transceiver point in the serving cell sends DCI to the terminal device, the DCI may be sent based on a set of configuration parameters corresponding to the transceiver point.
  • the terminal device after receiving the DCI, the terminal device can also determine the transceiver point or link to send the DCI according to the set of configuration parameters, that is, the terminal device can distinguish which transceiver point or link the received DCI is from. Therefore, the terminal device can also send uplink information to the corresponding transceiver point or link.
  • the configuration parameters include at least one of the following: physical downlink control channel PDCCH configuration, cell identification information, cell radio network temporary identification C-RNTI, demodulation reference signal DMRS, Beam set information, or beam information.
  • N sets of configuration parameters related to the downlink control channel correspond to N links of the serving cell, and the N links include the first link and the second link
  • the method further includes: performing a beam failure detection and beam failure recovery process based on the first link; or, performing a random access process based on the first link; or, performing radio link management RLM based on the first link; or, respectively based on The first link and the second link perform RLM, and when a radio link failure RLF occurs on the first link, the radio resource control RRC re-establishment is triggered; where the first link is the primary link.
  • the N links of the serving cell may also be understood as N transceiver points in the serving cell.
  • N sets of configuration parameters related to the downlink control channel correspond to the N links of the serving cell, which can also be understood as N sets of configuration parameters related to the downlink control channel correspond to the N transceiver points in the serving cell, that is, in the serving cell
  • Each sending and receiving point can transmit data with the terminal device based on its corresponding set of configuration parameters.
  • the terminal device may perform some operations based on only one link (for example, denoted as the first link) or only for one transceiver point to avoid performing these processes multiple times with all or multiple TRPs in a serving cell , Simplify the implementation of terminal equipment and protocol complexity.
  • the method further includes: receiving N sets of configuration parameters related to the uplink control channel corresponding to the serving cell, and N sets of configuration parameters related to the uplink control channel and N sets The configuration parameters related to the downlink control channel are associated one by one.
  • N sets of configuration parameters related to the downlink control channel are respectively associated with N sets of configuration parameters related to the uplink control channel, that is, a transceiver point in the serving cell is based on a set of corresponding downlink control channels
  • the terminal device may also send uplink information or uplink feedback to the transceiver point based on a set of configuration parameters related to the uplink control channel corresponding to the set of configuration parameters, so that the terminal device and the transceiver point
  • the communication can be carried out normally and effectively, and the sending and receiving point can receive the corresponding upstream information in time, which improves the robustness and improves the throughput of the terminal device.
  • the method further includes: determining a protocol architecture type for communicating with the serving cell, where the protocol architecture type includes at least one of the following: multi-connection-like architecture, carrier-like aggregation architecture , Or similar single cell architecture.
  • the single-cell-like architecture may be the first-type single-cell architecture or the second-type single-cell architecture, which will be described in detail in the following embodiments. It should be understood that the naming of the first-type single-cell architecture and the second-type single-cell architecture should not constitute any limitation to this application. This application does not exclude the possibility of defining other names to mean the same or similar meanings in future agreements.
  • the method further includes: obtaining indication information, which is used to indicate a protocol architecture type for communication between the terminal device and the serving cell; and determining a protocol architecture type for communicating with the serving cell, Including: determining the protocol architecture type for communicating with the serving cell according to the instruction information.
  • N sets of configuration parameters related to the downlink control channel correspond to N links of the serving cell; when the protocol architecture type is a multi-connection-like architecture, the corresponding configuration can be used
  • the radio bearer RB of the serving cell generates a packet data convergence layer protocol PDCP entity, generates N radio link control RLC entities, generates N media access control MAC entities, and generates N hybrid automatic repeat request HARQ entities, where , One PDCP entity is shared by N links, N RLC entities correspond to N links, N MAC entities correspond to N links, N HARQ entities correspond to N links; or, when the protocol architecture type For a carrier-like aggregation architecture, the corresponding configuration can use the RB of the serving cell to generate a PDCP entity, an RLC entity, and a MAC entity, and generate N HARQ entities, where one PDCP entity is shared by N links and one The RLC entity is shared by N links, one MAC entity is shared by N links, and N
  • a communication method is provided.
  • the method may be executed by a network device, or may also be executed by a chip or circuit configured in the network device, which is not limited in this application.
  • the network device can be understood as the access network device to which the transceiver point belongs or as the access network device that controls the transceiver point (for example, the access network device can be a base station, such as eNB, gNB, CU, or DU, etc. Limited), the serving cell to which the transceiver point belongs belongs to the access network device.
  • the access network device can be a base station, such as eNB, gNB, CU, or DU, etc. Limited
  • the serving cell to which the transceiver point belongs belongs to the access network device.
  • the method includes: generating configuration information of the serving cell, where the configuration information includes N sets of configuration parameters related to the downlink control channel corresponding to the serving cell, wherein each set of configuration parameters includes the same parameter type, and N is greater than or equal to An integer of 2; send the configuration information of the serving cell.
  • the serving cell may be a cell configured by the network device to perform uplink and downlink transmission with the terminal device.
  • the network device may configure N sets of configuration parameters related to the downlink control channel for the serving cell, and each set of configuration parameters includes the same parameter type, or it may be understood that the network device is each of the serving cells
  • the transceiver point is configured with a set of configuration parameters related to the downlink control channel, then each transceiver point in the serving cell can transmit data with the terminal device based on the configuration parameters configured for it.
  • This can not only avoid the interference problems that may occur when multiple transceiver points in the serving cell communicate with the terminal device using a set of configuration parameters, but also allow the terminal device to communicate with the corresponding transceiver point based on the corresponding configuration parameters according to the actual communication situation. Communication, improve communication efficiency.
  • the method further includes: sending first downlink control information DCI, and the configuration parameter corresponding to the first DCI belongs to one of N sets of configuration parameters related to the downlink control channel set.
  • the configuration parameters include at least one of the following: physical downlink control channel PDCCH configuration, cell identification information, cell radio network temporary identification C-RNTI, demodulation reference signal DMRS, Beam set information, or beam information.
  • the method further includes: sending N sets of configuration parameters related to the uplink control channel corresponding to the serving cell, and N sets of configuration parameters related to the uplink control channel and N sets The configuration parameters related to the downlink control channel are associated one by one.
  • the method further includes: sending indication information, where the indication information is used to indicate a protocol architecture type for communication between the terminal device and the serving cell, where the protocol architecture type includes at least one of the following : Similar multi-connection architecture, carrier-like aggregation architecture, or single-cell-like architecture.
  • a communication method is provided.
  • the method may be executed by the terminal device, or may also be executed by a chip or circuit configured in the terminal device, which is not limited in this application.
  • the method includes: communicating with the serving cell based on N sets of configuration parameters related to the uplink control channel corresponding to the serving cell, where N sets of configuration parameters related to the uplink control channel are related to N sets of configuration parameters related to the downlink control channel
  • the configuration parameters are associated one by one.
  • N sets of configuration parameters related to the downlink control channel correspond to N links of the serving cell.
  • the N links of the serving cell share a PDCP entity, an RLC entity, a MAC entity, and a HARQ entity.
  • N is an integer greater than or equal to 2.
  • the terminal device can send uplink information or uplink feedback to the transceiver point based on N sets of configuration parameters related to the uplink control channel, so that the terminal device and the transceiver point can communicate normally and effectively, and the transceiver The point can receive the corresponding upstream information in time, improve the robustness and increase the throughput of the terminal device.
  • the terminal device may not need to generate an RLC entity, a MAC entity, and a HARQ entity for each RB that can be configured to use the serving cell, so as to avoid occupying more resources such as storage and calculation.
  • each transceiver point can directly receive HARQ feedback corresponding to the transceiver point sent by the terminal device, which can avoid the problem of untimely HARQ retransmission and throughput degradation.
  • the terminal device may not need to generate a HARQ entity for each transceiver point, thereby avoiding occupying more storage and computing resources.
  • the configuration parameters include at least one of the following: physical downlink control channel PDCCH configuration, cell identification information, cell radio network temporary identification C-RNTI, demodulation reference signal DMRS, Beam set information, or beam information.
  • a communication method is provided.
  • the method may be executed by a network device, or may also be executed by a chip or circuit configured in the network device, which is not limited in this application.
  • the network device can be understood as the access network device to which the transceiver point belongs or as the access network device that controls the transceiver point (for example, the access network device can be a base station, such as eNB, gNB, CU, or DU, etc. Limited), the serving cell to which the transceiver point belongs belongs to the access network device.
  • the access network device can be a base station, such as eNB, gNB, CU, or DU, etc. Limited
  • the serving cell to which the transceiver point belongs belongs to the access network device.
  • the method includes: communicating with the terminal device based on N sets of configuration parameters related to the downlink control channel corresponding to the serving cell, where the N sets of configuration parameters related to the downlink control channel correspond to N links of the serving cell,
  • the N links of the serving cell share a PDCP entity, an RLC entity, a MAC entity, and a HARQ entity.
  • N sets of configuration parameters related to the downlink control channel are associated with N sets of configuration parameters related to the uplink control channel.
  • N is an integer greater than or equal to 2.
  • the configuration parameters include at least one of the following: physical downlink control channel PDCCH configuration, cell identification information, cell radio network temporary identification C-RNTI, demodulation reference signal DMRS, Beam set information, or beam information.
  • a communication device including: a communication unit and a processing unit, wherein the communication unit is configured to receive configuration information of a serving cell, and the configuration information includes N sets of configurations related to the downlink control channel corresponding to the serving cell Parameters, where each set of configuration parameters includes the same type of parameter, and N is an integer greater than or equal to 2; the processing unit is used to: communicate with the serving cell based on N sets of configuration parameters related to the downlink control channel.
  • the device can be configured in or itself is a terminal device.
  • the communication unit is further configured to: receive first downlink control information DCI, and the configuration parameters corresponding to the first DCI belong to N sets of configuration parameters related to the downlink control channel A set of; the processing unit is used to: according to the first DCI, determine the link corresponding to the first DCI.
  • the configuration parameters include at least one of the following: physical downlink control channel PDCCH configuration, cell identification information, cell radio network temporary identification C-RNTI, demodulation reference signal DMRS, Beam set information, or beam information.
  • N sets of configuration parameters related to the downlink control channel correspond to N links of the serving cell, and the N links include a first link and a second link
  • the processing unit is further configured to: perform a beam failure detection and beam failure recovery process based on the first link; or, perform a random access process based on the first link; or, perform radio link management RLM based on the first link; or, RLM is performed based on the first link and the second link respectively, and when a radio link failure RLF occurs on the first link, RRC re-establishment is triggered; where the first link is the primary link.
  • the communication unit is further configured to: receive N sets of configuration parameters related to the uplink control channel corresponding to the serving cell, and N sets of configuration parameters related to the uplink control channel N sets of configuration parameters related to the downlink control channel are associated one by one.
  • the processing unit is further configured to: determine a protocol architecture type for communicating with the serving cell, where the protocol architecture type includes at least one of the following: multi-connection-like architecture, carrier-like Aggregation architecture, or single-cell-like architecture.
  • the communication unit is further used to: obtain indication information, and the indication information is used to indicate a protocol architecture type for communication between the terminal device and the serving cell; the processing unit is specifically used to: according to the indication The information determines the type of protocol architecture that communicates with the serving cell.
  • N sets of configuration parameters related to the downlink control channel correspond to N links of the serving cell; the processing unit is also used to: when the protocol architecture type is a multi-connection-like architecture At the time, the corresponding configuration can use the radio bearer RB of the serving cell to generate a packet data convergence layer protocol PDCP entity, generate N radio link control RLC entities, generate N media access control MAC entities, and generate N hybrid automatic repeaters HARQ entities are transmitted, one PDCP entity is shared by N links, N RLC entities correspond to N links, N MAC entities correspond to N links, and N HARQ entities correspond to N links; Or, when the protocol architecture type is a carrier-like aggregation architecture, the corresponding configuration can use the RB of the serving cell to generate one PDCP entity, one RLC entity, and one MAC entity, and generate N HARQ entities, where one PDCP entity is N One link is shared, one RLC entity is shared by N links, one MAC entity is shared by
  • each unit in the device is used to execute each step of the above-mentioned first aspect and the communication method in each implementation manner of the first aspect.
  • the device is a communication chip
  • the communication chip may include an input circuit or interface for sending information or data, and an output circuit or interface for receiving information or data.
  • the apparatus is a communication device, and the communication device may include a transmitter for sending information or data, and a receiver for receiving information or data.
  • a communication device including: a communication unit and a processing unit, wherein the processing unit is configured to: generate configuration information of a serving cell, and the configuration information includes N sets of configurations related to the downlink control channel corresponding to the serving cell Parameters, where each set of configuration parameters includes the same type of parameter, N is an integer greater than or equal to 2; the communication unit is used to: send configuration information of the serving cell.
  • the apparatus may be configured or executed by the network device itself, or executed by the serving cell in the base station, or executed by the transceiver point (for example, TRP).
  • TRP transceiver point
  • the communication unit is further configured to: send first downlink control information DCI, and the configuration parameters corresponding to the first DCI belong to N sets of configuration parameters related to the downlink control channel Set.
  • the configuration parameters include at least one of the following: physical downlink control channel PDCCH configuration, cell identification information, cell radio network temporary identification C-RNTI, demodulation reference signal DMRS, Beam set information, or beam information.
  • the communication unit is further configured to send N sets of configuration parameters related to the uplink control channel corresponding to the serving cell, and N sets of configuration parameters related to the uplink control channel.
  • N sets of configuration parameters related to the downlink control channel are associated one by one.
  • the communication unit is further configured to send indication information that is used to indicate a protocol architecture type for communication between the terminal device and the serving cell, where the protocol architecture type includes at least the following One item: multi-connection-like architecture, carrier-like aggregation architecture, or single-cell-like architecture.
  • each unit in the device is used to execute each step of the communication method in the second aspect and the implementation manners of the second aspect.
  • the communication device is a communication chip
  • the communication chip may include an input circuit or interface for transmitting information or data, and an output circuit or interface for receiving information or data.
  • the communication device is a communication device
  • the communication chip may include a transmitter for transmitting information or data, and a receiver for receiving information or data.
  • a communication device Including: a communication unit, wherein the communication unit is used to: communicate with the serving cell based on N sets of configuration parameters related to the uplink control channel corresponding to the serving cell, wherein the N sets of configuration parameters related to the uplink control channel and the N sets of The downlink control channel related configuration parameters are related one by one.
  • N sets of downlink control channel related configuration parameters correspond to N links of the serving cell.
  • the N links of the serving cell share a PDCP entity, an RLC entity, and a MAC entity , And a HARQ entity, N is an integer greater than or equal to 2.
  • the device can be configured in or itself is a terminal device.
  • the configuration parameters include at least one of the following: physical downlink control channel PDCCH configuration, cell identification information, cell radio network temporary identification C-RNTI, demodulation reference signal DMRS, Beam set information, or beam information.
  • a communication device includes: a communication unit and a processing unit, wherein the communication unit is used to: communicate with the terminal device based on N sets of configuration parameters related to the downlink control channel corresponding to the serving cell, wherein the N sets of configuration parameters related to the downlink control channel correspond to N links of the serving cell.
  • the N links of the serving cell share one PDCP entity, one RLC entity, one MAC entity, and one HARQ entity.
  • Related configuration parameters are related one by one, and N is an integer greater than or equal to 2.
  • the apparatus may be configured or executed by the network device itself, or executed by the serving cell in the base station, or executed by the transceiver point (for example, TRP).
  • TRP transceiver point
  • the configuration parameters include at least one of the following: physical downlink control channel PDCCH configuration, cell identification information, cell radio network temporary identification C-RNTI, demodulation reference signal DMRS, Beam set information, or beam information.
  • a communication device including a processor and a memory, where the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the communication device performs the first aspect or the first Communication methods in three aspects and various possible implementations.
  • processors there are one or more processors and one or more memories.
  • the memory may be integrated with the processor, or the memory and the processor are provided separately.
  • the communication device further includes a transmitter (transmitter) and a receiver (receiver).
  • a communication device including a processor and a memory
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program from the memory, so that the communication device performs the second aspect or the first
  • processors there are one or more processors and one or more memories.
  • the memory may be integrated with the processor, or the memory and the processor are set separately.
  • the communication device further includes a transmitter (transmitter) and a receiver (receiver).
  • a communication system is provided, the communication device provided in the ninth aspect, and/or the communication device provided in the tenth aspect.
  • the communication system may further include other devices that interact with the communication device in the solutions provided in the embodiments of the present application.
  • a computer program product includes: a computer program (also referred to as code or instructions) that, when the computer program is executed, causes the computer to perform the first aspect to The method in any possible implementation manner of the fourth aspect.
  • a computer program also referred to as code or instructions
  • a computer-readable medium in a thirteenth aspect, a computer-readable medium is provided, the computer-readable medium storing a computer program (also referred to as code or instructions), which when executed on a computer, causes the computer to perform the above first aspect to The method in any possible implementation manner of the fourth aspect.
  • a computer program also referred to as code or instructions
  • a chip system including a memory and a processor, the memory is used to store a computer program, the processor is used to call and run the computer program from the memory, so that the communication device installed with the chip system is executed
  • the method in any possible implementation manner of the first aspect to the fourth aspect above.
  • the chip system may include an input circuit or interface for sending information or data, and an output circuit or interface for receiving information or data.
  • a communication system which includes multiple transceiver points TRP.
  • a communication system including the foregoing terminal device and base station.
  • the network device may configure N sets of configuration parameters related to the downlink control channel for the serving cell, or it may be understood that the network device configures a set of related downlink control channels for each transceiver point in the serving cell Configuration parameters, then each transceiver point in the serving cell can transmit data with the terminal device based on the configuration parameters configured for it.
  • This can not only avoid the interference problems that may occur when multiple transceiver points in the serving cell communicate with the terminal device using a set of configuration parameters, but also allow the terminal device to communicate with the corresponding transceiver point based on the corresponding configuration parameters according to the actual communication situation. Communication, improve communication efficiency.
  • Figure 1 shows a schematic diagram of a network architecture
  • FIG. 2 shows a schematic diagram of a protocol stack architecture for dual connectivity
  • FIG. 3 shows a schematic diagram of a protocol stack architecture of carrier aggregation
  • FIG. 7 is a schematic diagram of a protocol stack architecture proposed by an embodiment of the present application.
  • FIG. 8 is a schematic diagram of a communication system applicable to an embodiment of the present application.
  • FIG. 10 is a schematic block diagram of an example of a communication device of the present application.
  • FIG. 11 is a schematic structural diagram of an example of a terminal device of the present application.
  • FIG. 12 is a schematic configuration diagram of an example of a network device of the present application.
  • LTE long term evolution
  • FDD frequency division duplex
  • UMTS universal mobile communication system
  • 5G 5th generation
  • NR new radio
  • the terminal equipment in the embodiments of the present application may also be called: user equipment (UE), mobile station (MS), mobile terminal (MT), access terminal, user unit, user station, Mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
  • UE user equipment
  • MS mobile station
  • MT mobile terminal
  • access terminal user unit, user station, Mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
  • the terminal device may be a device that provides voice/data connectivity to the user, for example, a handheld device with a wireless connection function, a vehicle-mounted device, and the like.
  • some examples of terminals are: mobile phones, tablets, laptops, PDAs, mobile internet devices (MID), wearable devices, virtual reality (VR) devices, and augmented reality (augmented reality, AR) equipment, wireless terminals in industrial control, wireless terminals in self-driving, self-driving wireless terminals, wireless terminals in remote medical surgery, and smart grids Wireless terminals, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocols , SIP) telephone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication function, computing device or other processing device connected to a wireless modem, in-vehicle Devices, wearable devices, terminal devices in a 5G network or terminal devices in a public land mobile communication network (PLMN) that will evolve in the
  • the terminal device may also be a wearable device.
  • Wearable devices can also be referred to as wearable smart devices. It is a general term for applying wearable technology to intelligently design everyday wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes.
  • a wearable device is a portable device that is directly worn on the body or integrated into the user's clothes or accessories. Wearable devices are not only a hardware device, but also achieve powerful functions through software support, data interaction, and cloud interaction.
  • Generalized wearable smart devices include full-featured, large-sized, complete or partial functions that do not depend on smartphones, such as smart watches or smart glasses, and only focus on a certain type of application functions, and need to cooperate with other devices such as smartphones Use, such as various smart bracelets and smart jewelry for sign monitoring.
  • the terminal device may also be a terminal device in an Internet of Things (IoT) system.
  • IoT Internet of Things
  • the network device in the embodiment of the present application may be a device for communicating with a terminal device, and the network device may also be called an access network device or a wireless access network device, and may be a transmission and reception point (transmission reception point, TRP) ), can also be a global mobile communications (global system for mobile communications, GSM) system or code division multiple access (code division multiple access (CDMA) base station (base transceiver station, BTS), or broadband code division multiple access (wideband code division multiple access (WCDMA) system base station (NodeB, NB), can also be evolved base station (evolved NodeB, eNB or eNodeB) in LTE system, can also be a base station controller (base station controller (BSC) ), base transceiver station (BTS), home base station (for example, home evolved NodeB, or home Node B, HNB), baseband unit (BBU), or cloud wireless access network (cloud wireless controller in the context of radio access (CRAN), or the network device may be a global
  • the network device may include a centralized unit (CU) node, or a distributed unit (DU) node, or a RAN device including a CU node and a DU node, or a control plane CU node (CU -CP node) and user plane CU node (CU-UP node) and DU node RAN equipment.
  • CU centralized unit
  • DU distributed unit
  • RAN device including a CU node and a DU node, or a control plane CU node (CU -CP node) and user plane CU node (CU-UP node) and DU node RAN equipment.
  • CU -CP node control plane CU node
  • CU-UP node user plane CU node
  • the network device provides services for the cell.
  • the terminal device communicates with the cell or the transceiver point in the cell through the transmission resources (for example, frequency domain resources, or spectrum resources) allocated by the network device.
  • the cell may be the cell corresponding to the transceiver point.
  • a cell may belong to a macro base station (for example, a macro eNB or a macro gNB, etc.), or may belong to a base station corresponding to a small cell (small cell).
  • the small cell here may include: a metro cell, a micro cell, Pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.
  • FIG. 1 shows a schematic diagram of a dual-connectivity (DC) network architecture.
  • a terminal device can have a communication connection with two network devices at the same time and can send and receive data. connection.
  • the two network devices such as base stations
  • one network device may be responsible for interacting with the terminal device for radio resource control messages and for interacting with the core network control plane entity.
  • the network device may be called a master node (master (node, MN), for example, the master node may be MeNB or MgNB, not limited to this; then another network device may be called a secondary node (SN), for example, the secondary node may be SeNB or SgNB, not Limited to this.
  • the master node is the anchor point of the control plane, that is, the terminal device establishes an RRC connection with the master node, and the master plane establishes a control plane connection with the core network.
  • multiple serving cells in the master node form a master cell group (MCG), including a primary cell (primary cell, PCell) and optionally one or more secondary cells (primary cell, PCell) .
  • Multiple serving cells in the secondary node form a secondary cell group (secondary cell group, SCG), including a primary and secondary cell (primary secondary cell, PSCell, or, may also be called a special cell) and optionally one or more SCells .
  • the serving cell refers to a cell configured by the network for the terminal device to perform uplink and downlink transmission.
  • the terminal device can also have a communication connection with multiple network devices and can send and receive data at the same time, which can be called multi-connection or multi-connectivity (MC).
  • MC multi-connection or multi-connectivity
  • the multiple network devices there can be one network
  • the device is responsible for exchanging radio resource control messages with the terminal device and for interacting with the core network control plane entity.
  • the network device can be called MN, and the remaining network devices can be called SN.
  • the user plane protocol stack architecture may include a radio resource control (RRC) layer, a packet data convergence layer protocol (packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, a media access Access control (media access control, MAC) layer and physical layer and other protocol layer functions.
  • RRC radio resource control
  • PDCP packet data convergence layer protocol
  • RLC radio link control
  • MAC media access Access control
  • FIG. 2 shows a protocol stack architecture diagram of DC.
  • DC corresponding to a radio bearer, the two network devices share a PDCP entity, or the PDCP entity is commonly used by two network devices, and the two network devices have their respective RLC and MAC entities.
  • FIG. 1 is a schematic diagram of a network architecture of DC. To facilitate understanding of this application, the following first introduces the carrier aggregation architecture.
  • Carrier aggregation (carrier aggregation, CA): In order to efficiently use fragmented spectrum, the system supports aggregation between different carrier units. The technique of aggregating 2 or more carriers together to support a larger transmission bandwidth may be called carrier aggregation.
  • a terminal device may be configured with multiple carrier units (component carriers, CCs, or component carriers, component carriers, carriers, etc.), and each CC may correspond to an independent cell.
  • One CC can be equivalent to one cell.
  • the primary cell corresponds to the primary CC (or primary carrier), and may be a cell for initial connection establishment for the terminal, or a cell for RRC connection reestablishment, or a primary cell designated during a handover.
  • the secondary cell corresponds to a secondary CC (or secondary carrier), and may be a cell added during RRC reconfiguration to provide additional wireless resources.
  • the terminal device For a terminal device in a connected state, if carrier aggregation is not configured, the terminal device has a serving cell; if carrier aggregation is configured, the terminal device may have multiple serving cells (serving cells), which may be called services Set of cells.
  • serving cells serving cells
  • the primary cell and the secondary cell described above constitute a serving cell set of the terminal device.
  • the serving cell set includes at least one primary cell and at least one secondary cell.
  • a terminal device configured with carrier aggregation can perform data transmission with one PCell and multiple SCells.
  • FIG. 3 shows a protocol stack architecture diagram of carrier aggregation.
  • the protocol stack architecture shown in FIG. 3 is applicable to the scenario where two CCs perform carrier aggregation.
  • two serving cells share a PDCP entity, an RLC entity, and a MAC entity.
  • a PDCP entity, an RLC entity, and One MAC entity is shared by two serving cells, and the two serving cells have their own independent hybrid automatic repeat request (HARQ) entities.
  • HARQ hybrid automatic repeat request
  • TRP transceiver points
  • Figures 4 to 6 show three possible user plane protocol stack architecture diagrams.
  • the protocol stack architectures shown in Figures 4 to 6 are all applicable to Scenarios that support the transmission of multiple transceiver points in a cell are introduced below.
  • the multiple sending and receiving points can communicate through ideal backhaul or non-ideal backhaul, which is not limited.
  • multiple transceiver points or, may also be referred to as multiple transmission points, that is, multiple TRPs, may be understood as a group of antennas at a geographic location.
  • multiple TRPs There are multiple TRPs in the cell. It can be understood that when the cell sends downlink information to the terminal device, the respective information can be sent out through the multiple TRPs respectively.
  • N TRPs in the cell there are N TRPs in the cell, where N is an integer greater than or equal to 2.
  • the N TRPs of the cell can communicate with the terminal device through a link or a channel, in other words, the cell includes N links or N channels.
  • the N TRPs in the cell may also be understood as N channels in which the N TRPs of the cell communicate with the terminal device.
  • protocol stack architectures shown in FIGS. 4 to 6 can be applied to the scenario where two transceiver points in a cell are transmitted.
  • the protocol stack architecture that supports the transmission of multiple transceiver points in a cell can be compared and will not be repeated.
  • the protocol stack architecture shown in FIG. 4 is similar to the DC protocol stack architecture.
  • the protocol stack architecture shown in FIG. 4 may be referred to as a dual-connection-like architecture or a multi-connection-like architecture. Therefore, in the following embodiments, the configuration shown in FIG. 4
  • the protocol stack architecture is simply referred to as the multi-connection architecture. Among them, when there are two TRPs in a cell, it may be called a dual-connected architecture; when there are three TRPs in a cell, it may be called a triple-connected architecture or a multi-connected architecture. It should be understood that the naming of the multi-connection-like architecture or the dual-connection-like architecture should not constitute any limitation to this application. This application does not exclude the possibility of defining other names to mean the same or similar meanings in future agreements.
  • TRP1 and TRP2, respectively two TRPs are denoted as TRP1 and TRP2, respectively, as an example.
  • the protocol stack architecture on the network device side is: TRP1 and TRP2 share a PDCP entity, and TRP1 and TRP2 have their own (physical, PHY) entities and MAC Entity, RLC entity, in addition TRP1 and TRP2 have their own MAC scheduler and HARQ entity.
  • the MAC scheduler has functions such as resource allocation and scheduling, and can implement the scheduling function of the MAC entity.
  • the MAC scheduler can be regarded as a part of the functional module of the MAC entity, or the MAC scheduler can belong to the MAC entity. No limitation. The place where the MAC scheduler appears below will not be repeated.
  • the TRP with the MAC scheduler can be regarded as the main TRP, or the TRP to which the MAC scheduler belongs can be regarded as the main TRP, or the TRP corresponding to the MAC scheduler can be regarded as the main TRP, or the TRP with the MAC scheduling function Seen as the main TRP, there is no restriction on this.
  • the protocol stack architecture on the terminal device side can be consistent with the protocol stack architecture on the network device side. For example, for an RB configured by the network device that can use the serving cell, the network device side includes: one PDCP entity, two MAC entities, and two In the case of RLC entities, the terminal device side also includes: one PDCP entity, two MAC entities, and two RLC entities, which will not be described in detail.
  • TRP1 and TRP2 can send downlink control information (downlink control information, DCI), independently schedule physical downlink shared channel (physical downlink shared channel (PDSCH) and physical uplink shared channel (physical uplink link shared channel) , PUSCH).
  • the terminal device can send corresponding uplink control information (uplink control information, UCI) to TRP1 and TRP2 respectively.
  • the uplink control information includes but is not limited to at least one of the following: scheduling request (SR), channel state information (channel state information, CSI), and HARQ feedback. For example, as shown in FIG.
  • TRP1 can send DCI and PDSCH to the terminal device, which is denoted as DCI1 and PDSCH1 respectively, and the terminal device can also send CSI, SR, HARQ feedback to TRP1, which is CSI1 and SR1 respectively as the distinction.
  • TRP2 can send DCI and PDSCH to the terminal device, which is marked as DCI2 and PDSCH2 respectively, and the terminal device can also send CSI, SR and HARQ feedback to TRP2, which is marked as CSI2, SR2 and HARQ respectively.
  • Feedback 2 is an indication of the terminal device.
  • the protocol stack architecture shown in FIG. 5 is similar to the user plane protocol stack architecture during single-cell communication, so in the following embodiments, the protocol stack architecture similar to that shown in FIG. 5 is simply referred to as the first type of single-cell architecture. It should be understood that the naming of the first type of single-cell architecture should not constitute any limitation to this application. This application does not exclude the possibility of defining other names to mean the same or similar meanings in future agreements.
  • TRP1 and TRP2 are still used as an example for description.
  • the protocol stack architecture on the network device side is: TRP1 and TRP2 share a PDCP entity, an RLC entity, and a MAC entity, and TRP1 and TRP2 share a HARQ entity.
  • the MAC scheduler can be located in TRP1, and TRP1 can be regarded as the main TRP.
  • the link between TRP1 and the terminal device can also be called the main link.
  • the MAC scheduler of TRP1 is also responsible for the transmission of TRP1 and TRP2. Scheduling.
  • the MAC scheduler can also be located in TRP2, and TRP2 can be regarded as the main TRP.
  • the link between TRP2 and the terminal device can also be called the main link.
  • the MAC scheduler of TRP2 is also responsible for TRP1.
  • TRP2 transmission scheduling For ease of understanding, FIG. 5 shows only one case.
  • the protocol stack architecture on the terminal device side can be consistent with the network device side, and will not be repeated here.
  • the two TRPs can send DCI and schedule PDSCH and PUSCH independently; the terminal device only sends uplink control information to TRP1 (that is, the main TRP), that is, the terminal device sends uplink control information corresponding to TRP1 to TRP1 And the upstream control information corresponding to TRP2.
  • the uplink control information includes but is not limited to: SR, CSI and HARQ feedback.
  • TRP1 can send DCI and PDSCH to the terminal device, which is denoted as DCI1 and PDSCH1, respectively
  • TRP2 can send DCI and PDSCH to the terminal device, which is denoted as DCI2 and PDSCH2, respectively.
  • CSI, SR, HARQ feedback corresponding to TRP1 can be sent to TRP1.
  • they are denoted as CSI1, SR1, and HARQ feedback 1, respectively.
  • the terminal device can also send CSI, SR, HARQ feedback corresponding to TRP2 to TRP1. Feedback 2 for CSI2, SR2, HARQ.
  • the protocol stack architecture shown in FIG. 6 is similar to the protocol stack architecture of CA, so in the following embodiments, the protocol stack architecture similar to that shown in FIG. 6 is simply referred to as a carrier-like aggregation architecture. It should be understood that the naming of the carrier-like aggregation architecture should not constitute any limitation to this application. This application does not exclude the possibility of defining other names to mean the same or similar meanings in future agreements.
  • TRP1 and TRP2 are still used as an example for description.
  • the protocol stack architecture on the network device side is: TRP1 and TRP2 share a PDCP entity, an RLC entity, and a MAC entity, and TRP1 and TRP2 have their corresponding PHY entities, HARQ entity.
  • the MAC scheduler is located in TRP1 (TRP1 is regarded as the main TRP, and accordingly, the link between TRP1 and the terminal device can also be regarded as the main link).
  • the MAC scheduler of TRP1 is also responsible for the transmission scheduling of TRP1 and TRP2.
  • the protocol stack architecture on the terminal device side can be consistent with that on the network device side, and will not be repeated here. In FIG.
  • TRP2 can also implement a virtual MAC scheduler to be able to process transmission scheduling on the TRP2 side in time, but the virtual MAC scheduler must work under the control of the TRP1 MAC scheduler.
  • the MAC scheduler of TRP1 and the virtual MAC scheduler of TRP2 belong to the master and slave relationship, that is, TRP1 is regarded as the master TRP, and TRP2 is regarded as the slave TRP.
  • the two TRPs can send DCI separately and independently schedule PDSCH and PUSCH.
  • the terminal device may send corresponding uplink control information to the two TRPs respectively.
  • the uplink control information includes but is not limited to: SR, CSI and HARQ feedback.
  • TRP1 can send DCI and PDSCH to the terminal device, which is denoted as DCI1 and PDSCH1 respectively, and the terminal device can also send CSI, SR, HARQ feedback to TRP1, which is CSI1 and SR1 respectively as the distinction.
  • TRP2 can send DCI and PDSCH to the terminal device, which is marked as DCI2 and PDSCH2 respectively, and the terminal device can also send CSI, SR and HARQ feedback to TRP2, which is marked as CSI2, SR2 and HARQ respectively.
  • Feedback 2
  • the architectures of FIGS. 4 to 6 can be applied to multi-transmission-point transmission in a cell.
  • This application proposes another architecture that can be applied to multi-transmission-point transmission in a cell.
  • the protocol stack architecture proposed by this application is similar to the user plane protocol stack architecture during single-cell communication, so in the following embodiments, the protocol stack architecture proposed by this application is simply referred to as the second type of single-cell architecture. It should be understood that the naming of the second type of single-cell architecture should not constitute any limitation to this application. This application does not exclude the possibility of defining other names to mean the same or similar meanings in future agreements.
  • the protocol stack architecture shown in FIG. 7 can be applied to scenarios that support two TRP transmissions in a cell.
  • the protocol stack architecture that supports multiple TRP transmissions in a cell can be compared. For example, if you need to support three TRP transmissions in a cell
  • the protocol stack architecture on the network device side is: three TRPs share a PDCP entity, an RLC entity, and a MAC entity, and the three TRPs share a HARQ entity.
  • the protocol stack architecture on the terminal device side can be consistent with the protocol stack architecture on the network device side.
  • the protocol stack architecture on the network device side is: TRP1 and TRP2 share a PDCP entity, an RLC entity, and a MAC entity, and TRP1 and TRP2 share a HARQ entity.
  • TRP1 and TRP2 share one PDCP entity, one RLC entity, and one MAC entity, that is, one PDCP entity is shared by TRP1 and TRP2, one RLC entity is shared by TRP1 and TRP2, and one MAC entity is shared by TRP1 and TRP2 ;
  • TRP1 and TRP2 share a HARQ entity, that is to say, the only HARQ entity corresponding to the RB is shared by TRP1 and TRP2.
  • TRP1 can be regarded as the main TRP.
  • the link between TRP1 and the terminal device can also be called the main link.
  • the MAC scheduler of TRP1 is also responsible for the transmission scheduling of TRP1 and TRP2. .
  • the protocol stack architecture on the terminal device side can be consistent with the protocol stack architecture on the network device side, and will not be repeated here.
  • TRP2 can also implement a virtual MAC scheduler and process transmission scheduling on the TRP2 side, but the virtual MAC scheduler needs to work under the control of the TRP1 MAC scheduler.
  • the MAC scheduler of TRP1 and the virtual MAC scheduler of TRP2 can be regarded as a master and slave relationship, that is, TRP1 is regarded as a master TRP, and TRP2 is regarded as a secondary TRP.
  • the link between TRP1 and the terminal device can also be called the main chain Road
  • the link that TRP2 communicates with the terminal device may also be called a secondary link.
  • two TRPs can send DCI separately and schedule PDSCH and PUSCH independently.
  • multiple sets of PUCCH configurations are provided, and the terminal devices are respectively used to send corresponding uplink control information to multiple TRPs.
  • the terminal device can use the corresponding PUCCH configuration to send uplink control information to TRP1 and TRP2, that is, the terminal device sends uplink control information corresponding to TRP1 to TRP1, and sends uplink control information corresponding to TRP2 to TRP2.
  • the uplink control information includes but is not limited to: SR, CSI and HARQ feedback. For example, as shown in FIG.
  • TRP1 can send DCI and PDSCH to the terminal device, which is denoted as DCI1 and PDSCH1 respectively
  • TRP2 can send DCI and PDSCH to the terminal device, which is denoted as DCI2 and PDSCH2 respectively
  • CSI, SR, HARQ feedback corresponding to TRP1 can be sent to TRP1.
  • CSI1, SR1, and HARQ feedback 1 respectively.
  • the terminal device can also send CSI and HARQ feedback corresponding to TRP2 to TRP2. , SR2, HARQ feedback 2.
  • the protocol stack architecture proposed in the embodiments of the present application can not only reduce the waste of storage and calculation resources of the terminal device, but also avoid the decrease of the throughput of the terminal device.
  • the architecture shown in FIG. 7 for the RBs configured by the network that can use the serving cell, there is no need to separately generate RLC entities, MAC entities, and HARQ entities for each transceiver point, so that it can avoid occupying more storage and computing resources.
  • TRP2 can directly receive HARQ feedback corresponding to TRP2 sent by the terminal device, which can avoid the problem of untimely HARQ retransmission and throughput degradation.
  • the architecture shown in FIG. 7, for the RB configured for the network device to use the serving cell there is no need to separately generate a HARQ entity for each transceiver point, so that it can avoid occupying more storage and computing resources.
  • the second-type single-cell architecture proposed in this application and the first-type single-cell architecture shown in FIG. 5 can be collectively referred to as a single-cell-like architecture or a single-carrier-like architecture, where “first” and “first "Two" is just a name for distinguishing different architectures. It should be understood that the naming of the single-cell-like architecture or the single-carrier-like architecture should not constitute any limitation to this application. This application does not exclude the possibility of defining other names to mean the same or similar meanings in future agreements.
  • FIG. 8 is a schematic diagram of a system 100 to which the communication method of the embodiment of the present application can be applied.
  • the communication system 100 may include at least one terminal device, such as the terminal device 101 shown in the figure; the communication system 100 may also include at least two transceiver points, as shown in the figure, transceiver point #1 102 and receiving point #2 103.
  • the transceiver point #1 102 and the transceiver point #2 103 may be transmission nodes in the same cell.
  • the transceiver point #1 102 and the transceiver point #2 103 can communicate with each other through a backhaul link.
  • the backhaul link may be a wired backhaul link (eg, optical fiber, copper cable), or It is a wireless backhaul link (such as microwave).
  • the transceiver point #1 102 and the transceiver point #2 103 can cooperate with each other to provide services for the terminal device 101. Therefore, the terminal device 101 can communicate with the transceiving point #1 102 and the transceiving point #2 103 through the wireless link, respectively.
  • the backhaul can be divided into ideal backhaul and non-ideal backhaul.
  • the communication delay can be in the microsecond level, which can be neglected compared to the scheduling of millisecond level in NR; between two transmission nodes under non-ideal backhaul, the communication delay can be in milliseconds The level, compared with the millisecond level scheduling in NR, cannot be ignored.
  • the protocol stack architecture shown in FIGS. 4 to 6 described above and the protocol stack architecture shown in FIG. 7 proposed in this application can be applied to the communication system 100.
  • the communication system 100 may be a PLMN network, a D2D network, an M2M network, an IoT network, or other networks.
  • FIG. 8 is only a simplified schematic diagram of an example, and the network may also include other network devices, which are not shown in FIG. 8.
  • the communication system may further include a core network device, and the core network device may be connected to multiple access network devices to control the access network devices.
  • the high-level parameters may be included in high-level signaling.
  • the high-level signaling may be, for example, a radio resource control (radio resource control, RRC) message, or other high-level signaling, which is not limited in this application.
  • RRC radio resource control
  • "for indicating” may include both direct indication and indirect indication, and may also include explicit indication and implicit indication.
  • the information indicated by certain information is called information to be indicated.
  • information to be indicated In the specific implementation process, there are many ways to indicate the information to be indicated, such as but not limited to, you can directly indicate the information to be indicated Information, such as the information to be indicated itself or the index of the information to be indicated.
  • the information to be indicated may also be indirectly indicated by indicating other information, where there is an association relationship between the other information and the information to be indicated. It is also possible to indicate only a part of the information to be indicated, while other parts of the information to be indicated are known or agreed in advance.
  • the indication of the information to be indicated can also be realized by means of pre-agreed (for example, the protocol stipulates) whether a certain cell exists, thereby reducing the indication overhead to a certain extent.
  • M sets of configuration parameters related to the downlink control channel are associated with M sets of configuration parameters related to the uplink control channel, which may indicate that there is a correlation between the configuration parameters related to the downlink control channel and the configuration parameters related to the uplink control channel Relationship, that is, each set of configuration parameters related to the downlink control channel is associated with a set of configuration parameters related to the uplink control channel.
  • M sets of configuration parameters related to the downlink control channel are associated with M sets of configuration parameters related to the uplink control channel, which may indicate that there is a correlation between the configuration parameters related to the downlink control channel and the configuration parameters related to the uplink control channel Relationship, that is, each set of configuration parameters related to the downlink control channel is associated with a set of configuration parameters related to the uplink control channel.
  • “correspondence” is mentioned many times, for example, "PDCCH configuration corresponding to DCI", which means that the network device (such as the network device to which the TRP belongs) or the transceiver point (such as TRP) sends The PDCCH configuration on which the DCI is based, or the terminal device detects in the space/time-frequency resource determined by the PDCCH configuration, and then parses to obtain the DCI.
  • the PDCCH is a channel/bearer
  • the DCI is information carried on the PDCCH.
  • the terminal device determines the candidate space/time-frequency resource according to the PDCCH configuration configured by the network device, and the terminal device performs PDCCH detection on the configured candidate space/time-frequency resource, and after detecting the PDCCH, parses the PDCCH to obtain the bearer on the PDCCH On the DCI information.
  • pre-acquisition may include signaling indication or pre-defined by the network device, for example, protocol definition.
  • pre-defined can be achieved by pre-storing corresponding codes, tables or other methods that can be used to indicate relevant information in the device (for example, including terminal devices and network devices), and this application does not do for its specific implementation limited.
  • “save” involved in the embodiments of the present application may refer to being saved in one or more memories.
  • the one or more memories may be set separately, or may be integrated in an encoder or decoder, a processor, or a communication device.
  • the one or more memories may also be partly set separately and partly integrated in a decoder, processor, or communication device.
  • the type of memory may be any form of storage medium, which is not limited in this application.
  • the “protocol” referred to in the embodiments of the present application may refer to a standard protocol in the communication field, for example, it may include the LTE protocol, the NR protocol, and related protocols applied in future communication systems, which are not limited in this application.
  • At least one refers to one or more, and “multiple” refers to two or more.
  • “And/or” describes the relationship of the related objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A exists alone, A and B exist at the same time, B exists alone, where A, B can be singular or plural.
  • the character “/” generally indicates that the related object is a “or” relationship.
  • “At least one of the following” or similar expressions refers to any combination of these items, including any combination of single items or plural items.
  • At least one (a) of a, b, and c may represent: a, or b, or c, or a and b, or a and c, or b and c, or a, b and c, where a, b, c can be single or multiple.
  • the communication method provided by the present application may be applicable to a wireless communication system, for example, the wireless communication system 100 shown in FIG. 8.
  • the terminal device in the embodiment of the present application may communicate with one or more network devices at the same time.
  • the network device in the embodiment of the present application may correspond to the network to which the transceiver point #1 102 and the transceiver point #2 103 in FIG. 8 belong
  • the device that is, the network device to which the transceiver point #1 102 and the transceiver point #2 103 belong is the same network device
  • the network device in the embodiment of the present application may correspond to the transceiver point #1 102 in FIG.
  • Network device or network device to which the transceiver point #2 103 belongs that is, the network devices to which the transceiver point #1 102 and the transceiver point #2 103 belong are different network devices
  • the terminal device in the embodiment of the present application may correspond to Figure 8 terminal device 101.
  • the network device corresponds to the network device to which the transceiver point #1 102 and the transceiver point #2 103 in FIG. 8 belong (that is, the network device to which the transceiver point #1 102 and the transceiver point #2 103 belong is the same network Equipment) as an example.
  • a terminal device interacts with a serving cell in a network device
  • the terminal device may be any terminal device that has a wireless connection relationship with one or more serving cells in a wireless communication system.
  • a terminal device interacts with multiple transceiver points in a serving cell.
  • the terminal device may be any terminal device in a wireless communication system that has a wireless connection relationship with one or more transceiver points. It can be understood that any terminal device in the wireless communication system can implement wireless communication based on the same technical solution. This application does not limit this.
  • the terminal device and/or network device may perform some or all of the steps in the embodiments of the present application. These steps or operations are merely examples. The embodiments of the application may also perform other operations or variations of various operations. In addition, various steps may be performed in different orders presented in the embodiments of the present application, and it may not be necessary to perform all operations in the embodiments of the present application.
  • protocol stack architecture applicable to the embodiments of the present application may be as shown in FIG. 4 to FIG. 7, but is not limited to the protocol stack architecture shown in FIG. 4 to FIG. 7, and others may implement multiple transceiver points in a cell
  • the protocol stack architecture of TRP) transmission can also be applied to the embodiments of the present application.
  • Method 200 includes:
  • the network device configures cell #A.
  • cell #A (ie, an example of a serving cell) is a cell that supports multi-transceiver point (TRP) transmission.
  • TRP multi-transceiver point
  • cell #A the cell that supports multi-transceiver point transmission is referred to as cell #A.
  • Cell #A includes N TRPs, where N is an integer greater than or equal to 2.
  • the network device configures for cell #A. It can be understood that the network device configures N TRPs in cell #A; or, it can be understood that the network device configures one for each TRP in cell #A.
  • each set of configuration parameters includes the same type of parameters. The following describes the specific configuration parameters.
  • the network device may use any of the following methods to configure N TRPs:
  • Method 1 Configure cell #A as a serving cell that includes N sets of configuration parameters related to the downlink control channel.
  • the N sets of configuration parameters related to the downlink control channel correspond to N TRPs. This method may also be called a single cell.
  • Mode configuration ;
  • Method 2 Configure cell #A into N co-frequency cells.
  • Each co-frequency cell includes a set of configuration parameters related to the downlink control channel.
  • Each co-frequency cell corresponds to a TRP. This method can also be called a multi-cell. Way configuration. Wherein, each co-frequency cell may correspond to the same frequency point information and/or the same cell identification information.
  • the frequency point information may include at least one of the following: synchronization signal block (synchronization signal block (SSB) absolute frequency (AbsoluteFrequencySSB)), PointA absolute frequency (absoluteFrequencyPointA), frequency bandwidth list (frequencyBandList), subcarrier spacing (subcarrier spacing), SCS ) A specific carrier list (scs-SpecificCarrierList), etc.
  • SSB synchronization signal block
  • AbsolutteFrequencyPointA PointA absolute frequency
  • frequencyBandList frequency bandwidth list
  • subcarrier spacing subcarrier spacing
  • SCS A specific carrier list
  • the cell identification information may include at least one of the following: cell global identifier (CGI), physical cell identifier (PCI), serving cell index (such as ServCellIndex), and cell group identifier (such as CellGroupId) ).
  • CGI cell global identifier
  • PCI physical cell identifier
  • serving cell index such as ServCellIndex
  • cell group identifier such as CellGroupId
  • the network device sends the configuration information of cell #A to the terminal device, and accordingly, the terminal device receives the configuration information of cell #A sent by the network device.
  • the configuration information includes N sets of configuration parameters related to the downlink control channel corresponding to the cell #A.
  • Each set of configuration parameters related to the downlink control channel includes the same type of parameters. For example, when the configuration parameters include the PDCCH configuration, each set of configuration parameters related to the downlink control channel includes the PDCCH configuration.
  • the configuration information may further include M sets of configuration parameters related to the uplink control channel corresponding to the cell #A, where M is an integer greater than or equal to 1, and M is less than or equal to N.
  • M sets of configuration parameters related to the uplink control channel and M sets of configuration parameters related to the downlink control channel are one-to-one related, and are used for uplink information feedback and downlink information reception, respectively.
  • the configuration information may include N sets of configuration parameters related to the uplink control channel and N sets of Downlink control channel related configuration parameters, that is, each TRP corresponds to a set of configuration parameters related to the uplink control channel and a set of configuration parameters related to the downlink control channel.
  • Each TRP sends downlink information to the terminal device based on the corresponding configuration parameter related to the downlink control channel.
  • the terminal device can also send uplink information to the corresponding TRP based on the corresponding configuration parameter related to the uplink control channel.
  • the configuration information may include M sets of configuration parameters related to the uplink control channel and N sets of configurations related to the downlink control channel
  • the parameters correspond to M sets of configuration parameters related to the uplink control channel and M sets of configuration parameters among the N sets of configuration parameters related to the downlink control channel. That is, among the N TRPs, there are M TRPs corresponding to a set of configuration parameters related to the uplink control channel and a set of configuration parameters related to the downlink control channel respectively, and (NM) TRPs correspond to a set of related configuration related to the downlink control channel Configuration parameters.
  • the configuration information may include one set of configuration parameters related to the uplink control channel and two sets of configuration parameters related to the downlink control channel. That is, of the two TRPs, one TRP (that is, TRP1 in FIG. 5) corresponds to a set of configuration parameters related to the uplink control channel and a set of configuration parameters related to the downlink control channel. There is one TRP (that is, TRP2 in FIG. 5) ) Corresponds to a set of configuration parameters related to the downlink control channel, so the terminal device uses the configuration parameters related to the uplink control channel to send uplink information corresponding to TRP1 and uplink information corresponding to TRP2 to TRP1.
  • the terminal device communicates with the cell #A based on the configuration information of the cell #A.
  • the terminal device communicates with cell #A based on N sets of configuration parameters related to the downlink control channel; or, it can be understood that the terminal device is based on N sets of configuration parameters related to the downlink control channel and cell #A N TRP communications.
  • the terminal device communicates with the cell #A. It can be understood that the terminal device receives information from multiple TRPs from the cell #A. Correspondingly, the multiple TRPs can separately send information to the terminal device. For example, the terminal device receives information from multiple TRPs in the cell #A from the time-frequency resource corresponding to the cell #A. The information transmitted by multiple TRPs may be the same or different.
  • the configuration parameters include at least one of the following: PDCCH configuration (such as PDCCH), cell identification information, cell radio network temporary identification C-RNTI, demodulation reference signal DMRS, and N corresponding TRP identifications (such as TRP ID) , Beam set information, or beam information.
  • PDCCH configuration such as PDCCH
  • cell identification information such as cell radio network temporary identification C-RNTI
  • demodulation reference signal DMRS such as demodulation reference signal
  • N corresponding TRP identifications such as TRP ID
  • Beam set information such as Beam set information
  • the terminal device receives DCI from cell #A, or the terminal device receives DCI from the network device to which cell #A belongs, and the configuration parameter corresponding to the DCI belongs to one of N sets of configuration parameters related to the downlink control channel .
  • the association relationship is expressed by an explicit or implicit method.
  • the correlation between N sets of configuration parameters related to the downlink control channel and N TRPs or N links can be expressed by an explicit method.
  • the configuration information sent by the network device including N sets of configuration parameters related to the downlink control channel corresponding to cell #A may also contain TRP or link information associated with each set of configuration parameters, then, the terminal device may be based on the received
  • the configuration parameter corresponding to the DCI determines which TRP or link of the N TRPs or links of cell #A the TRP or link sending the DCI is.
  • the TRP information may be a TRP identifier (such as TRP ID), or other methods (such as the TRP information may be relevant parameters for distinguishing and identifying TRP), which is not limited.
  • the link information may be a link identifier (such as link ID), or other methods (such as the link information may be related parameters for distinguishing and identifying the link), which is not limited.
  • the N sets of configuration parameters related to the downlink control channel and the association relationship between N TRPs or N links can be expressed by an implicit method.
  • the agreement stipulates that the N sets of configuration parameters related to the downlink control channel sent by the network device corresponding to cell #A, where the first set of configuration parameters are associated with the first TRP or the first link in cell #A (as noted As TRP1 or link 1), the second set of configuration parameters is associated with the second TRP or second link in cell #A (if recorded as TRP2 or link 2), and so on, and will not be repeated here. Or, it can be other agreed criteria without limitation. Then, based on the received configuration parameters corresponding to the DCI, the terminal device may determine which TRP or which link of the N TRPs of the cell #A is the TRP sending the DCI.
  • the N sets of configuration parameters related to the downlink control channel and the association relationship between the N TRPs or N links may be represented by cells or cell structures.
  • a certain cell or a certain cell structure
  • the terminal device can determine which TRP or which of the N TRPs or N links of the cell #A is the TRP or link that sends the DCI based on the received configuration parameters corresponding to the DCI link.
  • the first set of configuration parameters is referred to by the cell first-config
  • the cell first-config contains the corresponding Related parameters of the first set of configuration parameters.
  • the first set of configuration parameters corresponds to the first TRP or the first link.
  • the second set of configuration parameters is referred to by the cell second-config, which contains the corresponding second Relevant parameters of the set of configuration parameters, the second set of configuration parameters corresponds to the second TRP or the second link, and so on, and will not be repeated here.
  • the correspondence between the cell (or the configuration parameter corresponding to the cell) and the TRP (or link) may also be other correspondences.
  • This embodiment is only an example, and when implemented, the network device may be arbitrarily implemented. It should be understood that the cell first-config and the cell second-config are only a naming method and are not limited.
  • the terminal device can distinguish which TRP the received information (such as DCI) is from, or that the transmission channel between each TRP and the terminal device can be regarded as a link, through the embodiment of the present application , The terminal device can distinguish the link from which the received information (such as DCI) comes. If a terminal device wants to process information from multiple TRPs, it needs to distinguish which TRP the received information comes from. For example, the PDCCHs corresponding to multiple TRPs are distinguished to receive DCIs sent by multiple TRPs respectively, and the terminal device determines which TRPs the received DCIs correspond to.
  • the terminal device may receive downlink data from the corresponding physical downlink shared channel (PDSCH) according to the received DCI; or, the terminal device may send uplink data to the PUSCH corresponding to the determined TRP; or, The terminal device may perform uplink power control on a physical uplink shared channel (physical uplink shared channel (PUSCH) or physical uplink control channel (PUCCH) corresponding to the determined TRP. Distinguishing between PDCCH and DCI is also very important for achieving beam failure recovery with specified TRP. Therefore, through the embodiments of the present application, the data transmission rate can be improved through the transmission and reception of multiple points.
  • PUSCH physical uplink shared channel
  • PUCCH physical uplink control channel
  • Case 1 The configuration parameters include PDCCH configuration.
  • PDCCH configuration can be used to configure PDCCH parameters, for example, including control resource set (control resource set, CORESET), search space (search space) and other parameters that can be used for blind detection of PDCCH.
  • the PDCCH configuration may be configured by, for example, a PDCCH configuration control element (PDCCH-config information element, PDCCH-config IE) in higher layer parameters.
  • PDCCH-config information element PDCCH-config IE
  • the PDCCH configuration can also be used to determine the search space/time-frequency resources to detect the PDCCH.
  • Different PDCCH configurations determine different search spaces (or time-frequency resources).
  • Each PDCCH configuration may include one or more control resource sets and one or more search spaces.
  • Each control resource set and each search space can be further configured by high-level parameters.
  • the PDCCH-config may contain a control resource set control element (ControlResourceSetIE) and a search space control element (SearchSpaceIE), ControlResourceSetIE means control resource set related parameters, and SearchSpaceIE means search space related parameters.
  • ControlResourceSet IE and/or SearchSpace IE candidate space/time-frequency resources for detecting PDCCH can be determined.
  • the terminal device can determine the candidate space/time-frequency resource.
  • the terminal device performs PDCCH detection on the configured candidate space/time-frequency resource, and after detecting the PDCCH, parses the PDCCH to obtain the bearer on the PDCCH DCI information.
  • ControlResourceSet IE and SearchSpace IE included in the PDCCH-config are used as examples for illustration, and the embodiments of the present application are not limited thereto.
  • the configuration information includes N sets of configuration parameters related to the downlink control channel corresponding to the cell #A.
  • the configuration information includes N sets of PDCCH configurations, and the N sets of PDCCH configurations correspond to N TRPs, that is, each set of PDCCH configurations corresponds to one TRP.
  • N sets of PDCCH configurations correspond to N links, that is, each set of PDCCH configurations corresponds to one link.
  • the PDCCH configuration corresponding to the received DCI can be understood as the PDCCH configuration on which the DCI is received, or the terminal device is in the space/time-frequency resource determined by the PDCCH configuration Perform PDCCH detection, after detecting the PDCCH, analyze the PDCCH, and then obtain the DCI;
  • the PDCCH configuration corresponding to the DCI can be understood as the PDCCH configuration on which the DCI is sent, or the network device uses the DCI It is carried on the channel or space/time-frequency resource corresponding to the PDCCH configuration.
  • the terminal device may determine the TRP or link that sends the DCI based on the PDCCH configuration corresponding to the DCI.
  • N PDCCH positions of N TRPs are configured on N different time-frequency resource blocks by time-division multiplexing (TDM), and on which time-frequency resource blocks are terminal devices located After monitoring/receiving the DCI, the TRP or link sending the DCI may be determined in combination with the first correspondence.
  • TDM time-division multiplexing
  • the first correspondence relationship represents the correspondence relationship between N PDCCH positions and N different time-frequency resource blocks.
  • the first correspondence relationship may be sent by the network device to the terminal device, or may be pre-stored by the terminal device, It may also be stipulated in the agreement, which is not limited in the embodiments of the present application.
  • cell #A includes two TRPs, which are labeled TRP#1 and TRP#2 for distinction.
  • the time-frequency resource blocks where the PDCCH positions of TRP#1 and TRP#2 are located are denoted as K1 and K2, respectively.
  • the terminal device knows that the information received from K1 is the information sent by TRP#1, and the information received from K2 is the information sent by TRP#2.
  • each set of configuration parameters may be associated with an identifier (identify, ID), which may be an index value or a TRP ID or other, without limitation.
  • ID an identifier
  • the identification may be sent by the network device to the terminal device or specified in the protocol.
  • N sets of configuration parameters each correspond to an identifier, which can be included in the DCI sent by the transceiver point (such as TRP), and the terminal device can combine the identifier according to the received DCI The two correspondences determine the TRP or link sending the DCI.
  • the second correspondence relationship represents the correspondence between N sets of configuration parameters (such as N PDCCH configurations) and N different identifiers.
  • the second correspondence may be sent by the network device to the terminal device, or the terminal device may If it is saved, or as stipulated in the agreement, this embodiment of the present application is not limited.
  • cell #A includes TRP#1 and TRP#2.
  • the identifiers associated with the PDCCH configurations corresponding to TRP#1 and TRP#2 are respectively recorded as index1 and index2.
  • the terminal device knows that the information carrying index1 is the information sent by TRP#1 (for example, the information is DCI), and the information carrying the index2 is the information sent by TRP#2 (for example, the information is DCI).
  • the terminal device may determine the TRP or link that sends the DCI based on the received control resource set-related parameters and/or search space-related parameters corresponding to the received DCI.
  • the configuration information includes N sets of configuration parameters related to the downlink control channel corresponding to the cell #A.
  • the configuration information includes a set of PDCCH configurations.
  • the set of PDCCH configurations includes control resource set-related parameters and search space-related parameters corresponding to N links (or N TRPs), respectively, optionally, for each link
  • the control resource set related parameters (or each TRP) are associated with an identifier. It is also possible to associate an identification for the search space related parameters of each link (or each TRP).
  • the set of PDCCH configurations includes N sets of first parameters, and each set of first parameters (eg, the first parameter includes control resource set related parameters and/or search space related parameters) respectively corresponds to a TRP (or a link ).
  • the terminal device may determine the TRP or link to send the DCI based on the received control resource set-related parameters and/or search space related parameters corresponding to the received DCI.
  • the configuration information provided by the network device includes two sets of downlink control channels corresponding to the cell #A Configuration parameters.
  • the configuration information includes a set of PDCCH configurations, and the set of PDCCH configurations includes control resource set related parameters and search space related parameters corresponding to two links (or two TRPs), respectively.
  • the terminal device may determine the TRP or link that sends the DCI in combination with the third correspondence.
  • the third correspondence indicates the correspondence between N control resource set related parameters and N different identifiers (ie, the N control resource set related parameter associated identifiers), and/or, the third correspondence indicates N search Correspondence between spatially-related parameters and N different identifiers (that is, identifiers associated with N search-space-related parameters).
  • the third correspondence relationship may be sent by the network device to the terminal device, or may be pre-stored by the terminal device, or may be agreed by a protocol, which is not limited in this embodiment of the present application.
  • the terminal device may further perform corresponding PDSCH, PUSCH, or PUCCH processing.
  • TRP#1 the terminal device may instruct the PDSCH to receive downlink data according to the DCI.
  • the terminal device may send uplink data to the PUSCH corresponding to TRP#1.
  • the terminal device may perform uplink power control on the uplink PUSCH or PUCCH corresponding to TRP#1.
  • TRP#1 and TRP#2 may correspond to different HARQ entities, even different MAC and RLC entities. If TRP#1 and TRP#2 correspond to different HARQ entities, the terminal device submits the downlink data received from the PDSCH to the corresponding HARQ entity for processing.
  • the uplink direction is similar. For the uplink data sent to the PUSCH corresponding to the TRP, the terminal device needs to obtain the data from the HARQ entity corresponding to the TRP.
  • Beam failure detection is also similar, for example, the terminal device according to the demodulation reference signal (DMRS) received from TRP#1 (or the time-frequency resource block K1 corresponding to TRP#1). ) To determine whether TRP#1 has a beam failure.
  • DMRS demodulation reference signal
  • the configuration parameters may further include other information, for example, the configuration parameters may also include at least one of the following: cell identification information, cell wireless network temporary identification, demodulation reference signal, TRP identification, beam information, Or beam set information.
  • the terminal device determines the TRP or link that sends the DCI, it may be determined based on the above-mentioned first correspondence, second correspondence, or third correspondence, or may be determined based on the correspondence between other configuration information and TRP. This is not limited.
  • Case 2 The configuration parameters include cell identification information.
  • the cell identification information may be PCI, or CGI, or serving cell index, or cell group identification, or may also be cell index identification (Cell Index, Flag, CIF), etc.
  • the examples are not limited, and any method that can distinguish different TRPs by identification falls within the protection scope of the embodiments of the present application.
  • the cell identification information may be included in a physical layer message (such as DCI) or a layer 2 message (such as MAC CE) or an RRC message (such as RRC reconfiguration message), without limitation.
  • a physical layer message such as DCI
  • a layer 2 message such as MAC CE
  • RRC message such as RRC reconfiguration message
  • Cell #A may be configured with N CIFs, which correspond to N TRPs or N links, respectively.
  • the CIFs corresponding to each TRP or each link may be different. CIFs are used to distinguish different TRPs.
  • CIF can be included in DCI, or can also be included in other messages, without limitation.
  • the CIF is included in the DCI as an example.
  • the configuration information includes N sets of configuration parameters related to the downlink control channel corresponding to the cell #A.
  • the configuration information includes N CIFs.
  • N CIFs correspond to N TRPs or N links, that is, each CIF corresponds to a TRP or a link, and each CIF is included in the corresponding TRP.
  • DCI demodulation-in-Demandiation-In-Demandiation-In-Demandi.
  • the CIF corresponding to the received DCI can be understood as the CIF carried in the DCI; for the network device, the CIF corresponding to the DCI can be understood as being carried in the DCI when sending the DCI CIF in DCI.
  • the terminal device may determine the TRP or link that sends the DCI based on the CIF corresponding to the DCI.
  • the terminal device may determine the TRP or link that sends the DCI according to the CIF included in the DCI and the fourth correspondence between the CIF and the TRP or link.
  • the fourth correspondence relationship may be sent by the network device to the terminal device, or may be pre-stored by the terminal device, or may be specified by a protocol, which is not limited in this embodiment of the present application.
  • the PDCCH configuration corresponding to TRP#1 and the PDCCH configuration corresponding to TRP#2 may be the same or different, or, TRP#1 corresponds to The PDCCH position of T2 and the PDCCH position corresponding to TRP#2 may be the same or different.
  • the terminal device determines which TRP or link the DCI is from based on the CIF carried in the DCI.
  • the terminal device may further perform corresponding PDSCH, PUSCH, or PUCCH processing.
  • the specific processing procedure is similar to the above case 1, and will not be repeated here.
  • the configuration parameters may also include other information, for example, the configuration parameters may also include at least one of the following: PDCCH configuration, cell radio network temporary identification, demodulation reference signal, TRP identification, beam information, or Beam set information, etc.
  • the terminal device determines the TRP or link that sends the DCI, it may be determined based on the fourth correspondence, or may be determined based on the first correspondence, the second correspondence, or the third correspondence, or may be based on other configurations.
  • the correspondence between information and TRP is determined, and there is no limitation on this.
  • the configuration parameters include the cell radio network temporary identifier (cell radio network identifier, C-RNTI).
  • Cell #A can be configured with N different C-RNTIs as scrambling sequences (SS) (or descrambling sequences), and the N different C-RNTIs correspond to N TRP or N, respectively. link.
  • SS scrambling sequences
  • N different C-RNTIs correspond to N TRP or N, respectively. link.
  • the configuration information includes N sets of configuration parameters related to the downlink control channel corresponding to the cell #A.
  • the configuration information includes N C-RNTIs, and the N C-RNTIs correspond to N TRPs or N links, that is, each C-RNTI corresponds to a TRP or a link.
  • the C-RNTI corresponding to each TRP or each link may be different.
  • C-RNTI is a possible example of a scrambling code sequence (or descrambling sequence), and any manner that can distinguish different TRPs by a scrambling code sequence (or descrambling sequence) falls within the protection scope of the embodiments of the present application.
  • N different types or other names of scrambling code sequences (or descrambling sequences) can be configured to correspond to N TRPs or N links, that is, the configuration information includes N scrambling code sequences ( Or descrambling sequence), the scrambling code sequence (or descrambling sequence) includes but is not limited to C-RNTI.
  • the following uses C-RNTI as an example for description.
  • the C-RNTI corresponding to the received DCI can be understood to obtain the descrambling sequence used by the DCI; for the network device, the C-RNTI corresponding to the DCI can be understood to be used for DCI Scrambling code sequence for scrambling.
  • the scrambling code sequence is generally the same as the descrambling sequence, and may be generally called a scrambling code sequence.
  • the terminal device may determine the TRP or link that sends the DCI based on the C-RNTI corresponding to the DCI.
  • the terminal device may determine the TRP or link that sends the DCI according to the C-RNTI used for obtaining the DCI, and the fifth correspondence between the C-RNTI and the TRP or link.
  • the fifth correspondence relationship may be sent by the network device to the terminal device, or may be pre-stored by the terminal device, or may be specified by a protocol, which is not limited in this embodiment of the present application.
  • the PDCCH configuration corresponding to TRP#1 and the PDCCH configuration corresponding to TRP#2 may be the same or different, or in other words, TRP#1 corresponds to The PDCCH position of T2 and the PDCCH position corresponding to TRP#2 may be the same or different.
  • the configuration information includes two SSs. If the SS is a C-RNTI, the two C-RNTIs correspond to TRP#1 and TRP#2, respectively.
  • the terminal device tries two different positions at the PDCCH time-frequency position of cell #A. SS to detect DCI. After the DCI is detected, it is judged from which TRP or link the DCI comes from according to the SS used to obtain the DCI.
  • the terminal device may further perform corresponding PDSCH, PUSCH, or PUCCH processing.
  • the specific processing procedure is similar to the above case 1, and will not be repeated here.
  • the configuration parameters may also include other information, for example, the configuration parameters may also include at least one of the following: PDCCH configuration, cell identification information, demodulation reference signal, TRP identification, beam information, or beam set Information etc.
  • the terminal device determines the TRP or link that sends the DCI, it may be determined based on any one of the above-mentioned first correspondence, second correspondence, third correspondence, fourth correspondence, and fifth correspondence, or it may It is determined based on the correspondence between other configuration information and TRP, which is not limited.
  • Case 4 The configuration parameters include demodulation reference signal (DMRS).
  • DMRS demodulation reference signal
  • the DMRS can be carried on the physical shared channel and sent together with the data signal for demodulating the data signal carried on the physical shared channel.
  • the PDSCH is transmitted together with the downlink data
  • the PUSCH is transmitted together with the uplink data.
  • the DMRS can also be carried in the physical control channel and sent together with the control signaling for demodulating the control signaling carried in the physical control channel summary. For example, it is sent together with downlink control signaling in the PDCCH, or it is sent together with uplink control signaling in the PUCCH.
  • Cell #A may be configured with N different DMRSs, and the N different DMRSs correspond to N TRPs or N links, respectively.
  • the configuration information includes N sets of configuration parameters related to the downlink control channel corresponding to the cell #A.
  • the configuration information includes N DMRSs, and the N DMRSs correspond to N TRPs or N links, that is, each DMRS corresponds to a TRP or a link.
  • DMRS is a possible example of demodulation reference signals, and any method that can distinguish different TRPs through demodulation reference signals falls within the protection scope of the embodiments of the present application.
  • N different demodulation reference signals of other types or other names may be configured to correspond to N TRPs or N links, respectively, which is not limited.
  • the following uses DMRS as an example.
  • the DMRS corresponding to the received DCI can be understood as receiving the DMRS from the time-frequency location where the received DCI is located; for the network device, the DMRS corresponding to the DCI can be understood as sending the DCI The corresponding space/time-frequency resources send DMRS.
  • the terminal device may determine the TRP or link that sends the DCI based on the DMRS corresponding to the DCI.
  • the terminal device may determine the TRP or link that sends the DCI according to the received DMRS and the sixth correspondence between the DMRS and the TRP or link.
  • the sixth correspondence relationship may be sent by the network device to the terminal device, or may be pre-stored by the terminal device, or may be specified by a protocol, which is not limited in this embodiment of the present application.
  • the PDCCH configuration corresponding to TRP#1 and the PDCCH configuration corresponding to TRP#2 may be the same or different, or in other words, TRP#1 corresponds to The PDCCH position of T2 and the PDCCH position corresponding to TRP#2 may be the same or different.
  • the terminal device determines whether the DMRS signal is based on whether the DMRS information of the time-frequency position where the DCI is received is received (for example, whether the signal quality corresponding to the DMRS is greater than a preset threshold Valid) Determine which TRP or link the DCI is from.
  • the terminal device may further perform corresponding PDSCH, PUSCH, or PUCCH processing.
  • the specific processing procedure is similar to the above case 1, and will not be repeated here.
  • the configuration parameters may further include other information, for example, the configuration parameters may also include at least one of the following: PDCCH configuration, cell identification information, cell wireless network temporary identification, TRP identification, beam information, or beam Set information and so on.
  • the terminal device determines the TRP or link that sends the DCI, it may be determined based on any one of the first correspondence, second correspondence, third correspondence, fourth correspondence, fifth correspondence, and sixth correspondence Or, it can also be determined based on the correspondence between other configuration information and TRP, which is not limited.
  • Case 5 The configuration parameters include the TRP identification.
  • Cell #A may be configured with N identifiers for N TRPs, where the N identifiers correspond to N TRPs respectively, and the identifier is used to identify the TRP.
  • the configuration information includes N sets of configuration parameters related to the downlink control channel corresponding to the cell #A.
  • the configuration information includes N identifiers, and the N identifiers correspond to N TRPs, that is, each identifier corresponds to one TRP.
  • the identifier may be TRP ID, which is not limited. The following uses TRP ID as an example for description.
  • the identifier corresponding to the received DCI can be understood as the TRP identifier associated with the PDCCH configuration upon which the DCI is received; for the network device, the identifier corresponding to the DCI can be understood as the network The TRP identifier configured when the device configures the PDCCH configuration, and the configured TRP identifier is associated with the PDCCH configuration.
  • the terminal device may determine the TRP or link that sends the DCI based on the TRP identifier corresponding to the DCI.
  • the terminal device may determine the TRP or link that sends the DCI according to the TRP identifier and the seventh correspondence between the TRP identifier and the TRP or link.
  • the seventh correspondence relationship may be sent by the network device to the terminal device, or may be pre-stored by the terminal device, or may be specified by a protocol, which is not limited in this embodiment of the present application.
  • the PDCCH configuration corresponding to TRP#1 and the PDCCH configuration corresponding to TRP#2 may be the same or different, or, TRP#1 corresponds to The PDCCH position of T2 and the PDCCH position corresponding to TRP#2 may be the same or different.
  • the terminal device determines which TRP or link the DCI is from based on the TRP identifier associated with the PDCCH configuration upon which the DCI is received.
  • the terminal device may further perform corresponding PDSCH, PUSCH, or PUCCH processing.
  • the specific processing procedure is similar to the above case 1, and will not be repeated here.
  • the configuration parameters may further include other information, for example, the configuration parameters may further include at least one of the following: PDCCH configuration, cell identification information, cell wireless network temporary identification, demodulation reference signal, beam information, or Beam set information, etc.
  • the terminal device determines the TRP or link for sending the DCI, it may be based on the above-mentioned first correspondence, second correspondence, third correspondence, fourth correspondence, fifth correspondence, sixth correspondence, and seventh correspondence Any one of them can be determined, or can also be determined based on the correspondence between other configuration information and TRP, which is not limited.
  • Case 6 The configuration parameters include beam information or beam set information.
  • the embodiment of the beam in the NR protocol may be a spatial filter (spatial filter), or a spatial filter or spatial parameters.
  • the beam used to send a signal can be called a transmission beam (transmission beam, Tx beam), it can also be called a spatial transmission filter (spatial domain domain transmit filter) or a spatial transmission parameter (spatial domain domain transmission parameter); a beam used to receive a signal It may be called a reception beam (reception beam, Rx beam), or a spatial reception filter (spatial domain reception filter) or a spatial reception parameter (spatial domain reception parameter).
  • Cell #A can be configured with N beams (or N beam sets), which correspond to N TRPs respectively, and the beam can be represented by a beam identifier (such as SSB index or CSI-RS index); or, The N beam sets correspond to N TRPs, respectively, where the beam set can be represented by a beam set identifier (such as beam set index), the number of beams included in different beam sets can be the same or different, and the beams included in different beam sets Not the same.
  • beam set 1 may include beam1-4
  • beam set 2 may include beam5-8, which is not limited.
  • the configuration information includes N sets of configuration parameters related to the downlink control channel corresponding to the cell #A.
  • the configuration parameters include beam information or beam set information.
  • the beam information may include a beam identification
  • the beam set information may include a beam identification and/or a beam set identification, which is not limited.
  • the configuration information includes N beams (or N beam sets), and the N beams (or N beam sets) correspond to N TRPs or N links, that is, each beam (or each beam set) corresponds to a TRP.
  • the beam (or beam set) corresponding to the received DCI can be understood as the beam for receiving the DCI (or the beam set to which the beam receiving the DCI belongs); and for the network device
  • the beam (or beam set) corresponding to the DCI can be understood as the beam that transmits the DCI (or the beam set to which the beam that transmits the DCI belongs).
  • the terminal device may determine the TRP or link that sends the DCI based on the beam (or beam set) corresponding to the DCI.
  • the terminal device may determine the source of the DCI according to the received DCI beam (or the beam set to which the DCI beam belongs) and the seventh correspondence between the beam (or beam set) and the TRP or link. TRP or link.
  • the seventh correspondence relationship may be sent by the network device to the terminal device, or may be pre-stored by the terminal device, or may be specified by a protocol, which is not limited in this embodiment of the present application.
  • the PDCCH configuration corresponding to TRP#1 and the PDCCH configuration corresponding to TRP#2 may be the same or different, or in other words, TRP#1 corresponds to The PDCCH position of T2 and the PDCCH position corresponding to TRP#2 may be the same or different.
  • the terminal device determines from which TRP or chain the DCI comes from according to the beam that obtains the DCI (or the beam set to which the beam of the DCI belongs) Road.
  • the configuration information includes 2 beam sets, such as beam set 1 and beam set 2, beam set 1 contains beam1-4, and beam set 1 corresponds to TRP#1; beam set 2 contains beam5- 8. The beam set 2 corresponds to TRP#2. If the terminal device receives DCI from beam2, the terminal device determines that the received DCI is sent by TRP#1, or the terminal device determines that the received DCI is sent by the link between the terminal device and TRP#1.
  • the configuration information includes two beams, such as beam 1 and beam 2, respectively, beam 1 corresponds to TRP#1, and beam 2 corresponds to TRP#2. If the terminal device receives DCI from beam 1, the terminal device determines that the received DCI is sent by TRP#1, or the terminal device determines that the received DCI is sent by the link between the terminal device and TRP#1.
  • the terminal device may further perform corresponding PDSCH, PUSCH, or PUCCH processing.
  • the specific processing procedure is similar to the above case 1, and will not be repeated here.
  • the configuration parameters may also include other information, for example, the configuration parameters may also include at least one of the following: PDCCH configuration, cell identification information, cell wireless network temporary identification, demodulation reference signal, TRP identification, etc. .
  • the terminal device determines the TRP or link for sending the DCI, it may be based on the above-mentioned first correspondence, second correspondence, third correspondence, fourth correspondence, fifth correspondence, sixth correspondence, and seventh correspondence Any one of them can be determined, or can also be determined based on the correspondence between other configuration information and TRP, which is not limited.
  • the terminal device can distinguish between the TRP or the received information according to at least one of the following: PDCCH configuration, cell identification information, C-RNTI, DMRS, TRP identification, beam information, or beam set information From which link, in order to further perform the corresponding PDSCH, PUSCH or PUCCH processing, the transmission rate is improved through the transmission and reception of multiple transceiver points in a cell.
  • Method 1 Single cell configuration.
  • the network device may configure cell #A as a serving cell including N sets of PDCCH configurations, and each set of PDCCH configurations corresponds to a TRP.
  • the RRC message uses a multi-level cell structure, that is, one cell may include one or more next-level cells, for example, CellGroupConfig ⁇ Special Cell Configuration/Secondary Cell Configuration(SpCellConfig/SCellConfig) ⁇ Serving Cell Configuration (ServingCellConfig) ⁇ bandwidth-specific parameters (BWP-DownlinkDedicated) ⁇ PDCCH-Config. Therefore, N PDCCH-Config cells may be included in the ServingCellConfig cell or BWP-DownlinkDedicated cell.
  • the following takes cell #A including two TRPs as an example for specific description. For distinction, they are respectively denoted as TRP#1 and TRP#2.
  • two PDCCH-Config cells are included in the BWP-DownlinkDedicated cell. For distinction, they are respectively recorded as PDCCH-Config1 and PDCCH-Config2.
  • a set of ServingCellConfig is provided for cell #A, that is, a set of ServingCellConfig is configured for the terminal device, and the set of ServingCellConfig includes two sets of PDCCH-Config.
  • the information contained in the set of ServingCellConfig can correspond to TRP#1 and TRP#2 at the same time.
  • the cell index (such as ServCellIndex) and the uplink configuration (such as UplinkConfig) corresponding to TRP#1 and TRP#2 may be the same, or may be different, which is not limited.
  • PDCCH-Config1 and PDCCH-Config2 in the set of ServingCellConfig correspond to TRP#1 and TRP#2, in other words, the PDCCH-Config corresponding to TRP#1 and TRP#2 are different.
  • TRP#1 and TRP#2 correspond to different DCI search spaces or time-frequency resources.
  • PDCCH-Config1 and PDCCH-Config2 configured in the BWP-DownlinkDedicated cell correspond to TRP#1 and TRP#2, respectively (for example, PDCCH-Config1 corresponds to TRP#1, PDCCH-Config2 corresponds to TRP#2, or PDCCH-Config2 corresponds to TRP #1, PDCCH-Config1 corresponds to TRP#2).
  • TRP#1 and TRP#2 can perform data transmission with the terminal device based on the respective PDCCH-Config.
  • the PDCCH-Config2 cell is configured in the BWP-DownlinkDedicated cell, or the PDCCH-Config1 cell and the PDCCH-Config2 cell are configured in the BWP-DownlinkDedicated cell, which can also indicate the transmission scenario of the terminal device at this time Transmission for two transceiver points in a serving cell (TRP#1 and TRP#2 are two transceiver points in a serving cell).
  • TRP#1 and TRP#2 are two transceiver points in a serving cell.
  • the terminal device after receiving the configuration of the serving cell including PDCCH-Config2, the terminal device can learn that the network device has configured multi-transmission point transmission for the serving cell.
  • multi-transmission-point transmission is used to indicate that multiple TRPs in a cell communicate with terminal devices. The following is concise and will not be repeated here.
  • a BWP-DownlinkDedicated cell includes a PDCCH-Config cell, but the PDCCH-Config contains N sets of first parameters corresponding to N TRPs (or N links), respectively.
  • the first parameter is as described above and will not be described in detail.
  • a set of PDCCH-Config is provided for cell #A, that is, a set of PDCCH-Config is configured for the terminal device, and the set of PDCCH-Config includes N sets of first parameters, and the first parameters include the first control resource set Parameters (such as ControlResourceSet) and parameters related to the first search space (such as SearchSpace).
  • N 2 and cell #A including two TRPs as an example for specific description. For distinction, they are respectively denoted as TRP#1 and TRP#2.
  • a PDCCH-Config cell is included, and the PDCCH-Config contains two sets of first parameters corresponding to two TRPs (or two links) respectively.
  • the first parameter includes the first control resource set.
  • the parameters such as ControlResourceSet
  • the first search space related parameters such as SearchSpace are distinguished as ControlResourceSet1, SearchSpace1, ControlResourceSet2, and SearchSpace2, respectively.
  • ControlResourceSet1 and SearchSpace1 in the PDCCH-Config correspond to TRP#1
  • ControlResourceSet2 and SearchSpace2 correspond to TRP#2
  • TRP#1 and TRP#2 correspond to a set of PDCCH-Config
  • TRP#1 and TRP#2 correspond to a set of PDCCH-Config
  • TRP#1 and TRP#2 correspond to a set of PDCCH-Config
  • TRP#1 and TRP#2 correspond to a set of PDCCH-Config
  • TRP#1 and TRP#2 correspond to different DCI search spaces and/or time-frequency resources.
  • TRP#1 and TRP#2 can perform data transmission with the terminal device based on the respective candidate space (time-frequency resource) of the PDCCH.
  • the terminal device can also be instructed to transmit at this time the transmission of two transceiver points in a serving cell (TRP#1 and TRP#2 serve Two receiving and sending points in the cell).
  • the terminal device can learn that the network device has configured multiple transmission and reception point transmissions for the serving cell.
  • two BWP-DownlinkDedicated cells are included in the ServingCellConfig cell, and are distinguished as BWP-DownlinkDedicated1 and BWP-DownlinkDedicated2 respectively.
  • a set of ServingCellConfig is provided for cell #A, that is, a set of ServingCellConfig is configured for the terminal device, and the set of ServingCellConfig includes two sets of BWP-DownlinkDedicated.
  • Each set of BWP-DownlinkDedicated includes a set of PDCCH-Config, which is denoted as PDCCH-Config1 and PDCCH-Config2 for distinction.
  • the information contained in the set of ServingCellConfig can correspond to TRP#1 and TRP#2 at the same time.
  • the cell indexes (such as ServCellIndex) corresponding to TRP#1 and TRP#2 may be the same or different
  • the uplink configuration (such as UplinkConfig) may be the same or different, which is not limited.
  • BWP-DownlinkDedicated1 and BWP-DownlinkDedicated2 in the ServingCellConfig respectively correspond to TRP#1 and TRP#2, that is, PDCCH-Config1 in BWP-DownlinkDedicated1 and PDCCH-Config2 in BWP-DownlinkDedicated2 correspond to TRP#1 and TRP, respectively. #2.
  • the PDCCH-Config corresponding to TRP#1 and TRP#2 are different.
  • TRP#1 and TRP#2 correspond to different DCI search spaces or time-frequency resources.
  • BWP-DownlinkDedicated1 and BWP-DownlinkDedicated2 configured in the ServingCellConfig cell correspond to TRP#1 and TRP#2, respectively, that is, PDCCH-Config1 and PDCCH-Config2 correspond to TRP#1 and TRP#2, respectively.
  • BWP-DownlinkDedicated1 or PDCCH-Config1 corresponds to TRP#1
  • BWP-DownlinkDedicated2 or PDCCH-Config2 corresponds to TRP#2
  • BWP-DownlinkDedicated2 or PDCCH-Config2 corresponds to TRP#1
  • BWP-DownlinkDedicated1 or PDCCH-Config1 corresponds to TRP #2, this is not limited.
  • TRP#1 and TRP#2 can perform data transmission with the terminal device based on the respective PDCCH-Config.
  • BWP-DownlinkDedicated2 is configured in the ServingCellConfig cell, or two BWP-DownlinkDedicated cells (such as BWP-DownlinkDedicated1 and BWP-DownlinkDedicated2) are configured in the ServingCellConfig cell, which can instruct the terminal device to transmit at this time
  • the scenario is the transmission of two transceiver points in a serving cell (TRP#1 and TRP#2 are two transceiver points in a serving cell).
  • the terminal device after receiving the configuration of the serving cell including BWP-DownlinkDedicated2, the terminal device can learn that the network device has configured multi-transmission point transmission for the serving cell.
  • any cell #A may be configured to include N sets of PDCCH configurations
  • the methods of a serving cell fall into the protection scope of the embodiments of the present application.
  • the cell #A may also be configured as a serving cell including N sets of PDCCH configurations based on the similar manner as described above.
  • Cell #A is configured as N co-frequency cells, each co-frequency cell includes a set of configuration parameters related to the downlink control channel, and each co-frequency cell corresponds to a TRP.
  • the cell #A is configured as two co-frequency serving cells, and these two serving cells respectively correspond to TRP#1 and TRP#2 as an example for description.
  • the two co-frequency serving cells are recorded as cell #A1 and cell #A2.
  • the RRC message uses a multi-level cell structure.
  • the following multi-level cell structure is still used as an example for illustration: CellGroupConfig ⁇ SpCellConfig/SCellConfig ⁇ ServingCellConfig ⁇ BWP-DownlinkDedicated ⁇ PDCCH-Config.
  • two cell groups can be configured for the terminal device.
  • two sets of CellGroupConfig can be configured, and the two sets of CellGroupConfig are configurations corresponding to cell #A1 and cell #A2, respectively.
  • the two sets of CellGroupConfig correspond to TRP#1 and TRP#2, respectively.
  • this implementation may be adopted. This implementation can also be applied to any architecture shown in Figures 4-7, which is not limited.
  • each set of CellGroupConfig includes a set of PDCCH-Config (the PDCCH-Config may be included in the lower-level cells of the CellGroupConfig), which are distinguished as PDCCH-Config1 and PDCCH-Config2 respectively.
  • PDCCH-Config1 and PDCCH-Config2 respectively correspond to TRP#1 and TRP#2, in other words, the PDCCH-Config corresponding to TRP#1 and TRP#2 are different.
  • TRP#1 and TRP#2 correspond to different DCI search spaces or time-frequency resources.
  • the network device sends a configuration message to the terminal device.
  • the configuration message includes two sets of configuration parameters.
  • the two sets of configuration parameters may be two sets of CellGroupConfig, or the two sets of configuration parameters may be two sets of PDCCH-Config.
  • cell #A provides two sets of ServingCellConfig, that is, a cell group configuration (CellGroupConfig) includes two sets of ServingCellConfig. Recorded as ServingCellConfig1, ServingCellConfig2.
  • ServingCellConfig1 and ServingCellConfig2 are the configurations of the corresponding cell #A1 and cell #A2, respectively.
  • the ServingCellConfig1 and ServingCellConfig2 respectively correspond to TRP#1 and TRP#2.
  • this implementation manner may be adopted for the single-cell-like architecture shown in FIGS. 5 and 7 and the carrier-like aggregation architecture shown in FIG. 6, this implementation manner may be adopted. This implementation manner can also be applied to the multi-connection-like architecture shown in FIG. 4, which is not limited.
  • the cell indexes (such as ServCellIndex) corresponding to the two sets of ServingCellConfig may be the same or different, and the uplink configuration (such as UplinkConfig) may be the same or different, that is, the cell indexes and uplink configurations corresponding to TRP#1 and TRP#2 may be the same or different.
  • each set of ServingCellConfig includes a set of PDCCH-Config, which is denoted as PDCCH-Config1 and PDCCH-Config2 for distinction.
  • PDCCH-Config1 and PDCCH-Config2 respectively correspond to TRP#1 and TRP#2, in other words, the PDCCH-Config corresponding to TRP#1 and TRP#2 are different.
  • TRP#1 and TRP#2 correspond to different DCI search spaces or time-frequency resources.
  • the network device sends a configuration message to the terminal device.
  • the configuration message includes two sets of configuration parameters.
  • the two sets of configuration parameters may be two sets of ServingCellConfig, or the two sets of configuration parameters may be two sets of ServingCellConfig, or the two sets of configuration parameters It can be two sets of PDCCH-Config.
  • two ServingCellConfig cells are included in the SpCellConfig cell, which are distinguished as ServingCellConfig1 and ServingCellConfig2 respectively.
  • a set of SpCellConfig is provided for cell #A, and the set of SpCellConfig includes two sets of ServingCellConfig, and each set of ServingCellConfig includes a set of PDCCH-Config.
  • TRP#1 and TRP#2 can perform data transmission with the terminal device based on the respective PDCCH-Config.
  • any cell #A can be configured as N co-frequency servings
  • the cell method falls within the protection scope of the embodiments of the present application.
  • the cell #A can also be configured into N co-frequency serving cells based on the similar manner to the above.
  • the method of configuring the serving cell supporting multi-transmission point transmission into two co-frequency serving cells makes it possible to reuse the existing DC or CA configuration process or signaling as much as possible, simplifying the protocol design.
  • the embodiments of the present application also provide several methods that enable the terminal device to determine the protocol architecture type.
  • the terminal device can also communicate with the TRP according to the determined protocol architecture type. The details are described below.
  • the terminal device obtains indication information, which is used to indicate the protocol architecture type that the terminal device communicates with N TRPs.
  • the indication information is recorded as indication information #1.
  • the protocol architecture type includes at least one of the following: a multi-connection-like architecture, a carrier-like aggregation architecture, or a single-cell-like architecture.
  • the multi-connection-like architecture may be the architecture shown in FIG. 4, the carrier-like aggregation architecture is the architecture shown in FIG. 6, and the single-cell-like architecture includes the first-type single-cell architecture shown in FIG. 5 and FIG.
  • the protocol architecture type indicated by the indication information #1 includes at least one of the following: multi-connection-like architecture, carrier-like aggregation architecture, first-type single-cell architecture, and second-type single-cell architecture.
  • the protocol architecture type for communicating with N TRPs may be one or more of the protocols defined or specified in advance; or, the protocol architecture type for communicating with N TRPs may also be notified by the network device to the terminal device.
  • the embodiments of the present application are not limited.
  • a possible implementation manner a protocol pre-defined or a protocol architecture type used by the protocol.
  • the protocol predefines/prescribes the use of multi-connection-like architecture; another example, the protocol predefines/prescribes the use of carrier-like aggregation architecture; another example, the protocol predefines/prescribes the use of the first type of single-cell architecture; another example, the protocol predefines/ The second type of single cell architecture is specified.
  • the terminal device obtains the indication information #1. It can be understood that the terminal device determines the protocol architecture type for communicating with N TRPs in the same serving cell according to the protocol pre-defined or protocol provisions.
  • the protocol predefines or the protocol stipulates multiple protocol architecture types to be used.
  • the protocol predefines/prescribes the use of at least two protocol architecture types: multi-connection-like architecture, carrier-like aggregation architecture, first-type single-cell architecture, and second-type single-cell architecture.
  • the terminal device obtains the indication information #1. It can be understood that the terminal device determines the protocol architecture type for communicating with N TRPs in the same serving cell according to the protocol pre-defined or protocol provisions.
  • the network device sends indication information #1 to the terminal device.
  • the terminal device receives the indication information #1, and the terminal device determines the protocol architecture type according to the received indication information #1.
  • the indication information #1 can be explicitly indicated by means of a dedicated cell, or the indication information #1 can also be specified by a specific value and/or a specific configuration method of an existing cell (for example, a cell is configured with multiple copies ) And other implicit instructions.
  • the protocol architecture type can be explicitly indicated in the cell ServingCellConfig through a special cell multiTrpTransType.
  • the terminal device may determine that the protocol architecture type is a certain architecture (eg, multi-connection-like architecture or carrier-like architecture) (Aggregation architecture or first-type single-cell architecture or second-type single-cell architecture).
  • the terminal device can determine that the protocol architecture type is one of the architectures (such as a multi-connection-like architecture); when two copies are configured, the terminal device can determine the protocol
  • the architecture type is another (such as carrier-like aggregation architecture) and so on, in which a certain cell is configured with X shares (X is an integer greater than or equal to 1) and the corresponding architecture type, which can be predetermined and not limited. It should be understood that the naming of the cell is only an exemplary description for ease of understanding, and should not constitute any limitation to this application, the cell may have other names or expressions.
  • the network device sends indication information #1 to the terminal device.
  • the indication information #1 is used to indicate that the protocol architecture type is a multi-connection-like architecture.
  • the cell multiTrpTransType includes information indicating the multi-connection-like architecture; or, the instruction Information #1 is used to indicate that the protocol architecture type is a carrier-like aggregation architecture.
  • the cell multiTrpTransType includes information indicating the carrier-like aggregation architecture; or, the indication information #1 is used to indicate that the protocol architecture type is the first type of single cell Architecture, for example, the cell multiTrpTransType includes information for indicating the first type of single-cell architecture; or, the indication information #1 is used to indicate that the protocol architecture type is the second type of single-cell architecture, for example, the cell multiTrpTransType includes for indicating Information about the second type of single-cell architecture.
  • the network device sends indication information #1 to the terminal device, where the indication information #1 is used to indicate that the protocol architecture type is at least two of the following: a multi-connection-like architecture, a carrier-like aggregation architecture, a first-type single-cell architecture, or a first
  • a second-type single-cell architecture such as a cell multiTrpTransType, includes information indicating at least two types of protocol architectures: a multi-connection-like architecture, a carrier-like aggregation architecture, a first-type single-cell architecture, or a second-type single-cell architecture.
  • the terminal device may determine the protocol architecture type as the multi-connection-like architecture and the second-type single-cell architecture.
  • determining the protocol architecture type may also be referred to as determining the multi-transmission-point transmission type, or may also be referred to as the protocol architecture type used for multi-transmission-point transmission, and the naming is only for convenience. It is understood that the exemplary description should not constitute any limitation to this application. The following are all expressed by determining the type of protocol architecture.
  • the terminal device may also perform corresponding protocol stack configuration according to the determined protocol architecture type. The details are described below.
  • the terminal device may perform corresponding protocol stack configuration according to the determined protocol architecture type.
  • the above-mentioned architectures shown in FIGS. 4 to 7 will be described separately.
  • the terminal device determines that the protocol architecture type is a multi-connection-like architecture.
  • a radio bearer RB of cell #A can be used to configure a PDCP entity for N TRPs (or N links) for each TRP (or each link). Links) generate an RLC entity, a MAC entity, and a HARQ entity.
  • a PDCP entity is jointly generated for N TRPs (or N links), that is to say, N TRPs (or N links) share a PDCP entity; each TRP (or each link) Generate one RLC entity, one MAC entity, and one HARQ entity, that is, N TRPs (or N links) correspond to N RLC entities, N TRPs (or N links) and N MAC entities Correspondingly, N TRPs (or N links) correspond to N HARQ entities. Specifically, refer to the architecture shown in FIG. 4.
  • a radio bearer RB it may be a data radio bearer of a certain service or a signaling radio bearer of a certain service, for example, for emergency services, such as ultra-reliable and low-latency communication (ultra-reliable and lower latency communication (URLLC) service, the above processing is performed on the data radio bearer/signaling radio bearer of the emergency service; or, it may also be a designated data radio bearer/signaling radio bearer. limited. I will not repeat them below.
  • emergency services such as ultra-reliable and low-latency communication (ultra-reliable and lower latency communication (URLLC) service
  • URLLC ultra-reliable and lower latency communication
  • the network device may configure in which cells (or resources of which cells) the logical channel corresponding to the RB can be sent.
  • the configuration mentioned in the embodiment of the present application may use the radio bearer RB of cell #A (ie, serving cell), that is, the network device configures cell #A to be a cell that can send a certain RB (such as a certain RB corresponding to the URLLC service),
  • the RB is the RB configured by the network device and can use the cell #A.
  • one PDCP entity corresponds to N RLC entities to perform data transmission.
  • N RLC entities and N MAC entities correspond to each other for data transfer.
  • N MAC entities correspond to N HARQ entities for data transfer.
  • the MAC entity may correspond to multiple HARQ entities, and each HARQ entity corresponds to a serving cell.
  • the terminal device determines that the protocol architecture type is a carrier-like aggregation architecture.
  • one RB of cell #A can be used for configuration, and one PDCP entity, one RLC entity, and one MAC entity are generated for N TRPs (or N links), and respectively One HARQ entity is generated for each TRP (or each link).
  • the protocol architecture type is carrier-like aggregation architecture
  • one PDCP entity corresponds to one RLC entity for data transfer
  • one RLC entity corresponds to one MAC entity for data transfer
  • One MAC entity corresponds to N HARQ entities for data transfer.
  • the terminal device determines that the protocol architecture type is the first type of single-cell architecture.
  • one RB of cell #A can be used to jointly generate one PDCP entity, one RLC entity, one MAC entity for N TRPs (or N links), and A HARQ entity.
  • one PDCP entity corresponds to one RLC entity for data transfer
  • one RLC entity corresponds to one MAC entity for data transfer
  • One MAC entity corresponds to one HARQ entity for data transfer.
  • the terminal device determines that the protocol architecture type is the second type of single-cell architecture.
  • one RB of cell #A can be used to jointly generate one PDCP entity, one RLC entity, one MAC entity for N TRPs (or N links), and A HARQ entity.
  • one PDCP entity corresponds to one RLC entity for data transfer
  • one RLC entity corresponds to one MAC entity for data transfer
  • One MAC entity corresponds to one HARQ entity for data transfer.
  • the terminal device can determine the protocol architecture type according to the indication information #1.
  • the terminal device may also determine that cell #A is configured with multi-transmission-point transmission based on the determined protocol architecture type.
  • the following describes in detail several methods for determining whether cell #A is configured with multi-transmission point transmission according to the embodiment of the present application.
  • the terminal device can determine whether cell #A is configured with multi-transmission-point transmission by any of the following methods, or determine whether the N sets of configuration parameters are for multi-transmission-point transmission.
  • Method A The terminal device may determine that cell #A is configured with multi-transmission point transmission according to the indication information #1.
  • the terminal device After the terminal device obtains the indication information #1 indicating the protocol architecture type for communicating with N TRPs, it can determine the protocol architecture type according to the indication information #1, or it can determine that the cell #A is configured with multiple Transmit and receive point transmission, or, determine the configuration message or the N sets of configuration parameters are for multiple transmit and receive point transmission.
  • the indication information #1 used to indicate the protocol architecture type for communicating with N TRPs is as described above and will not be repeated here.
  • Method B The network device may also send indication information indicating that cell #A is configured with multi-transmission point transmission to the terminal device. For the sake of distinction, it is indicated as instruction information #2.
  • Method C The terminal device may also determine that cell #A is configured with multi-transmission point transmission according to the configuration information of cell #A.
  • the architecture shown in FIG. 4 can be It is regarded as a modification of the DC architecture. Under this architecture, two MACs or two RLC entities for one RB correspond to two TRPs or two links in the same serving cell respectively.
  • This variant is referred to as intra-cell DC
  • the traditional DC architecture is referred to as ordinary DC. It should be understood that the above nomenclature should not constitute any limitation to this application.
  • you can reuse the common DC process for intra-cell DC configuration that is, reuse the common DC process for the configuration of multiple transceiver points in the same serving cell.
  • the terminal device can be instructed to be configured as intra-cell DC, or it can be indicated that the configuration is for multi-transmission-point transmission, so that the terminal device can distinguish the configuration as intra-cell DC at this time.
  • the instruction may be a display instruction (such as the above method B) or a hidden instruction (such as the above method C). Each is explained below.
  • the above method B indicates that the terminal device is configured to be intra-cell DC, that is, the network device may send indication information #2 to the terminal device to indicate that the intra-cell DC is configured.
  • the indication information #2 may be included in a configuration message sent by the network device to the terminal device, such as RRC Setup (RRCSetup), RRC Recovery (RRCResume), RRC Reestablishment (RRCReestablishment), or RRC Reconfiguration (RRCReconfiguration) and other messages.
  • the indication information #2 may be a binary value. For example, “0” indicates that the intra-cell DC is not configured, that is, ordinary DC, and “1” indicates that the intra-cell DC is configured.
  • the indication information #2 may be a Boolean value, such as “False” indicates that the intra-cell DC is not configured, that is, a normal DC, and “True” indicates that the intra-cell DC is configured.
  • the indication information #2 is in the form of a cell, in other words, whether the configuration is intra-cell DC can be indicated by whether there is a certain cell in the configuration message. For example, if a certain cell is included in the configuration message, it indicates that the intra-cell DC is configured. If the cell is not included in the configuration message, it indicates that the intra-cell DC is not configured, that is, an ordinary DC.
  • the cell may be multiTrpTrans, for example. It should be understood that the naming of the cell is only an exemplary description for ease of understanding, and should not constitute any limitation to this application, the cell may have other names or expressions.
  • the method C implicitly indicates that the terminal device configures intra-cell DC, that is, N sets of configuration parameters included in the configuration message sent to the terminal device through the network device, for example, N sets of CellGroupConfig,
  • the corresponding frequency point information is the same, and the configuration is determined to be intra-cell DC, or it is determined that the configuration is for multi-transmission-point transmission, or the configuration corresponds to N different TRPs or links in cell #A.
  • the frequency point information may include at least one of the following: absoluteFrequencySSB, absoluteFrequencyPointA, frequencyBandList, scs-SpecificCarrierList, and so on.
  • the architecture shown in FIG. 5 can be regarded as a part of the CA architecture
  • N TRPs share a HARQ entity.
  • this variant is recorded as intra-cell CA (intra-cell CA)
  • the traditional CA architecture is recorded as ordinary CA. Understand that the above nomenclature should not constitute any limitation to this application.
  • the intra-cell CA configuration For the first type of single-cell architecture, you can reuse the common CA process for intra-cell CA configuration, that is, reuse the common CA process for the configuration of multiple transceiver points in the same serving cell.
  • the intra-cell CA configuration has only one HARQ configuration or two identical HARQ configurations.
  • N sets of configuration parameters for example, N sets of CellGroupConfig or N sets of ServingCellConfig
  • M sets of PUCCH configurations there are M sets of PUCCH configurations, and M is less than N.
  • TRP#1 and TRP#2 shown in FIG. 5 as an example, TRP#1 and TRP#2 only correspond to one set of PUCCH configurations.
  • the terminal device can be instructed to be configured as intra-cell CA, or the configuration can be indicated as intra-cell CA with sharing HARQ entity, or it can be indicated that the configuration is for multi-transmission point transmission, Therefore, the terminal device can distinguish the configuration at this time as intra-cell CA.
  • the instruction may be a display instruction (such as the above method B) or a hidden instruction (such as the above method C). Each is explained below.
  • the above method B indicates that the terminal device is configured with intra-cell CA, that is, the network device may send indication information #2 to the terminal device to indicate that the intra-cell CA is configured.
  • the indication information #2 may be included in a configuration message sent by the network device to the terminal device, such as RRCSetup, RRCResume, RRCReestablishment, or RRCReconfiguration.
  • the indication information #2 may be a binary value. For example, “0" indicates that the intra-cell CA is not configured, that is, an ordinary CA, and "1" indicates that the intra-cell CA is configured.
  • the indication information #2 may be a Boolean value, such as “False” indicates that the intra-cell CA is not configured, that is, a normal CA, and “True” indicates that the intra-cell CA is configured.
  • the indication information #2 is in the form of a cell, in other words, whether the configuration is intra-cell can be indicated by whether there is a certain cell in the configuration message. For example, if a certain cell is included in the configuration message, it indicates that the intra-cell CA is configured. If the cell is not included in the configuration message, it indicates that the intra-cell CA is not configured, that is, a common CA.
  • the cell may be multiTrpTrans, for example. It should be understood that the naming of the cell is only an exemplary description for ease of understanding, and should not constitute any limitation to this application, the cell may have other names or expressions.
  • the method C implicitly indicates that the terminal device configuration is intra-cell CA, that is, N sets of configuration parameters included in the configuration message sent to the terminal device through the network device, for example, N sets of CellGroupConfig or N sets of ServingCellConfig, corresponding to the same frequency information, determine that the configuration is intra-cell CA, or determine that the configuration is for multi-transmission point transmission, or determine that the configuration corresponds to N different TRPs in cell #A or link.
  • the frequency point information may include at least one of the following: absoluteFrequencySSB, absoluteFrequencyPointA, frequencyBandList, scs-SpecificCarrierList, and so on.
  • the architecture shown in FIG. 6 can be regarded as a part of the CA architecture kind of deformation. Under this architecture, two HARQ entities correspond to two TRPs or links in the same serving cell respectively.
  • this variant is recorded as intra-cell CA (intra-cell), and the traditional CA architecture is recorded as It is an ordinary CA. It should be understood that the above nomenclature should not constitute any limitation to this application.
  • the carrier-like aggregation architecture you can reuse the traditional CA process for intra-cell CA configuration, that is, reuse the traditional CA process for the configuration of multiple transceiver points in the same serving cell.
  • the terminal device can be instructed that the configuration is intra-cell CA, or it can be indicated that the configuration is for multi-transmission-point transmission, so that the terminal device can distinguish the configuration as intra-cell CA at this time.
  • the instruction may be a display instruction (such as the above method B) or a hidden instruction (such as the above method C). Each is explained below.
  • the above method B indicates that the terminal device is configured with intra-cell CA, that is, the network device may send indication information #2 to the terminal device to indicate that the intra-cell CA is configured.
  • the indication information #2 may be included in a configuration message sent by the network device to the terminal device, such as RRCSetup, RRCResume, RRCReestablishment, or RRCReconfiguration.
  • the indication information #2 may be a binary value. For example, “0" indicates that the intra-cell CA is not configured, that is, an ordinary CA, and "1" indicates that the intra-cell CA is configured.
  • the indication information #2 may be a Boolean value, such as “False” indicates that the intra-cell CA is not configured, that is, a normal CA, and “True” indicates that the intra-cell CA is configured.
  • the indication information #2 is in the form of a cell, in other words, whether the configuration is intra-cell can be indicated by whether there is a certain cell in the configuration message. For example, if a certain cell is included in the configuration message, it indicates that the intra-cell CA is configured. If the cell is not included in the configuration message, it indicates that the intra-cell CA is not configured, that is, a common CA.
  • the cell may be multiTrpTrans, for example. It should be understood that the naming of the cell is only an exemplary description for ease of understanding, and should not constitute any limitation to this application, the cell may have other names or expressions.
  • the method C implicitly indicates that the terminal device configuration is intra-cell CA, that is, N sets of configuration parameters included in the configuration message sent to the terminal device through the network device, for example, N sets of CellGroupConfig or N sets of ServingCellConfig, corresponding to the same frequency information, determine that the configuration is intra-cell CA, or determine that the configuration is for multi-transmission point transmission, or determine that the configuration corresponds to N different TRPs in cell #A or link.
  • the frequency point information may include at least one of the following: absoluteFrequencySSB, absoluteFrequencyPointA, frequencyBandList, scs-SpecificCarrierList, and so on.
  • the architecture shown in FIG. 7 can be regarded as one of the CA architecture
  • N TRPs share a HARQ entity.
  • this variant is recorded as intra-cell CA (intra-cell CA)
  • the traditional CA architecture is recorded as ordinary CA. Understand that the above nomenclature should not constitute any limitation to this application.
  • the second type of single-cell architecture you can reuse the traditional CA related processes for intra-cell CA configuration, that is, the traditional CA related processes are used for the configuration of multiple transceiver points in the same serving cell.
  • the intra-cell CA configuration has only one HARQ configuration or two identical HARQ configurations.
  • N sets of PUCCH configurations in N sets of configuration parameters such as N sets of CellGroupConfig or N sets of ServingCellConfig.
  • TRP#1 and TRP#2 shown in FIG. 7 respectively correspond to a set of PUCCH configurations.
  • the terminal device can be indicated to be configured as intra-cell CA, or it can be indicated as intra-cell CA with sharing HARQ entity, or it can be indicated that the configuration is for multi-transmission point transmission, Therefore, the terminal device can distinguish the configuration at this time as intra-cell CA.
  • the instruction may be a display instruction (such as the above method B) or a hidden instruction (such as the above method C). Each is explained below.
  • the above method B indicates that the terminal device is configured with intra-cell CA, that is, the network device may send indication information #2 to the terminal device to indicate that the intra-cell CA is configured.
  • the indication information #2 may be included in a configuration message sent by the network device to the terminal device, such as RRCSetup, RRCResume, RRCReestablishment, or RRCReconfiguration.
  • the indication information #2 may be a binary value. For example, “0" indicates that the intra-cell CA is not configured, that is, an ordinary CA, and "1" indicates that the intra-cell CA is configured.
  • the indication information #2 may be a Boolean value, such as “False” indicates that the intra-cell CA is not configured, that is, a normal CA, and “True” indicates that the intra-cell CA is configured.
  • the indication information #2 is in the form of a cell, in other words, whether the configuration is intra-cell can be indicated by whether there is a certain cell in the configuration message. For example, if a certain cell is included in the configuration message, it indicates that the intra-cell CA is configured. If the cell is not included in the configuration message, it indicates that the intra-cell CA is not configured, that is, a common CA.
  • the cell may be multiTrpTrans, for example. It should be understood that the naming of the cell is only an exemplary description for ease of understanding, and should not constitute any limitation to this application, the cell may have other names or expressions.
  • the method C implicitly indicates that the terminal device configuration is intra-cell CA, that is, N sets of configuration parameters included in the configuration message sent to the terminal device through the network device, for example, N sets of CellGroupConfig or N sets of ServingCellConfig, corresponding to the same frequency information, determine that the configuration is intra-cell CA, or determine that the configuration is for multi-transmission point transmission, or determine that the configuration corresponds to N different TRPs in cell #A or link.
  • the frequency point information may include at least one of the following: absoluteFrequencySSB, absoluteFrequencyPointA, frequencyBandList, scs-SpecificCarrierList, and so on.
  • the terminal device can determine whether the cell #A is configured with multi-transmission point transmission based on the embodiment of the present application, or determine whether the N sets of configuration parameters are for multi-transmission point transmission.
  • the terminal equipment can perform different operations for different TRPs. The following is a detailed description.
  • N sets of configuration parameters related to the downlink control channel correspond to N links of cell #A
  • the N links include a first link and a second link
  • the terminal device may perform beam failure based on the first link Detection and beam failure recovery process; or, the terminal device may perform a random access process based on the first link; or, the terminal device may perform wireless link management RLM based on the first link; or, the terminal device may be based on the first link, respectively
  • the RLM and the second link perform RLM, and when the radio link failure RLF occurs on the first link, the radio resource control RRC re-establishment is triggered.
  • the N links of cell #A can be understood as N TRPs of cell #A, or N channels of cell #A, respectively, and N channels of communication with the terminal device.
  • the first link and the second link can be represented by the first TRP and the second TRP, or the first link can be represented as the link between the terminal device and the first TRP, and the second link can be represented as the terminal The link between the device and the second TRP.
  • the first link may be any one or more of the N links, or may be one or more specified by the network device, or may be one or more specified by the protocol, or , Can also be one or more main links of the N links.
  • the main link is a channel or link for communication between the terminal device and the main TRP (refer to the description in FIGS. 5 to 7 for the main link).
  • the first TRP may be any one of the N TRPs, or may be a TRP designated by the network device, or may be a TRP specified in the protocol, or may be the master of the N TRPs. TRP.
  • the terminal device determines that the TRP sending the DCI is N of cell #A according to the configuration parameters corresponding to the received DCI The method of which TRP or which link in the TRP will not be described in detail.
  • the network device may indicate the first link or the first TRP through an explicit or implicit method.
  • the network device may indicate by sending the identifier of the first link or the identifier of the first TRP, or a protocol agreement.
  • the network device may refer to a certain cell (or a certain cell structure) included in the sent configuration information including N sets of configuration parameters related to the downlink control channel corresponding to cell #A to refer to the first chain Road or first TRP information.
  • N sets of configuration parameters related to the downlink control channel corresponding to cell #A to refer to the first chain Road or first TRP information.
  • the second link may be any one or more of the N links that are different from the first link.
  • the second TRP may be any one or more of the N TRPs different from the first TRP.
  • the method for the terminal device to determine each link (such as the Zth link) or each TRP (such as the Zth TRP), and the method for the network device to indicate each link (such as the Zth link) or each TRP (such as the Zth TRP) For details, please refer to the above descriptions in case 1 to case 6 and will not repeat them.
  • Z can be any value in the range of 1 to N.
  • the terminal device can receive the information of N TRPs or N links from cell #A.
  • the terminal device can perform some operations on only one or part of the TRPs or links.
  • the terminal device may perform operations on only one TRP or one link, or on some TRPs or some links, to avoid performing multiple sets of these processes on a serving cell, simplifying the terminal device Implementation and protocol complexity.
  • the terminal device performs beam failure detection (BFD) and beam failure recovery (BFR) on the TRP or link specified by the network device.
  • BFD beam failure detection
  • BFR beam failure recovery
  • the terminal device performs a random access process on the TRP or link specified by the network device.
  • the terminal device may perform radio link management (radio link management (RLM)) on the TRP or link specified by the network device.
  • RLM radio link management
  • the terminal device may perform RLM based on N TRPs or N links, respectively, and trigger a radio resource control RRC re-establishment when a radio link failure (RLF) occurs in the TRP or link specified by the network device.
  • RLM radio link management
  • the terminal device After a wireless link failure occurs in another TRP, the terminal device sends the wireless link failure report to the TRP designated by the network device or sends the wireless link failure report to the network device, and the TRP or network device designated by the network device performs corresponding processing For example, the TRP designated by the network device or the network device deletes the TRP in which the wireless link fails or reconfigures the TRP in which the wireless link fails.
  • the terminal device performs a beam failure detection and beam failure recovery process on the TRP or link specified in the protocol.
  • the terminal device performs a random access process on the TRP or link specified in the protocol.
  • the terminal device may perform wireless link management on the TRP or link specified in the protocol.
  • the terminal device may perform radio link management based on N TRPs or N links, respectively, and trigger radio resource control RRC re-establishment when a radio link failure occurs in the TRP or link specified in the protocol.
  • the terminal device sends the wireless link failure report to the TRP specified in the protocol or the wireless link failure report to the network device to which the TRP specified in the protocol belongs.
  • the network device to which the TRP belongs performs corresponding processing. For example, the TRP specified in the protocol or the network device to which the TRP specified in the protocol deletes the TRP in which the wireless link fails or reconfigures the TRP in which the wireless link fails.
  • the terminal device performs a beam failure detection and beam failure recovery process on the main TRP or the link.
  • the terminal device performs a random access procedure on the main TRP or link.
  • the terminal device may perform wireless link management on the main TRP or link.
  • the terminal device may perform radio link management based on N TRPs or N links, respectively, and trigger radio resource control RRC re-establishment when a radio link failure RLF occurs in the main TRP or link.
  • the terminal device sends the wireless link failure report to the master TRP or sends the wireless link failure report to the network device to which the master TRP belongs, and the master TRP or the network device to which the master TRP belongs Processing, for example, the master TRP or the network device to which the master TRP belongs deletes the TRP in which the wireless link fails or reconfigures the TRP in which the wireless link fails.
  • the terminal device may perform beam-level RRM measurement on the TRP specified by the network device; or, the terminal device may perform beam-level RRM measurement on the TRP specified in the protocol; or, the terminal device may separately perform Beam level RRM measurement is performed on N TRPs.
  • the terminal device can perform some operations on only one TRP or one link or part of the TRP or link, it should be understood that the above several possible implementations and specific operations are only exemplary Note that this application is not limited to this.
  • the method implemented by the terminal device can also be implemented by components (such as chips or circuits) that can be used for the terminal device
  • the method implemented by the network device can also be implemented by the method that can be used for the network device Components (such as chips or circuits) to achieve.
  • the network device may configure N sets of configuration parameters for the serving cell, or it may be understood that the network device configures a set of configuration parameters for each transceiver point in the serving cell, then each transceiver in the serving cell All points can transmit data with terminal devices based on the configuration parameters configured for them. This can not only avoid the interference problems that may occur when multiple transceiver points in the serving cell communicate with the terminal device using a set of configuration parameters, but also allow the terminal device to communicate with the corresponding transceiver point based on the corresponding configuration parameters according to the actual communication situation. Communication, improve communication efficiency.
  • the communication device 1000 may include a communication unit 1100 and a processing unit 1200.
  • the communication device 1000 may include a communication unit 1100 and a processing unit 1200.
  • the communication apparatus 1000 may implement steps or processes corresponding to the terminal device in the above method embodiment, for example, it may be a terminal device, or a chip or circuit configured in the terminal device.
  • the communication unit 1100 is configured to: receive configuration information of the serving cell, and the configuration information includes N sets of configuration parameters related to the downlink control channel corresponding to the serving cell, where each set of configuration parameters includes the same parameter type , N is an integer greater than or equal to 2; the processing unit 1200 is used to communicate with the serving cell based on N sets of configuration parameters related to the downlink control channel.
  • the communication unit 1100 is further configured to: receive first downlink control information DCI, and the configuration parameter corresponding to the first DCI belongs to one of N sets of configuration parameters related to the downlink control channel; the processing unit 1200 is used to: The first DCI determines the link corresponding to the first DCI.
  • the configuration parameters include at least one of the following: physical downlink control channel PDCCH configuration, cell identification information, cell radio network temporary identification C-RNTI, demodulation reference signal DMRS, beam set information, or beam information.
  • N sets of configuration parameters related to the downlink control channel correspond to N links of the serving cell, and the N links include a first link and a second link
  • the processing unit 1200 is further configured to: based on the first link Perform beam failure detection and beam failure recovery procedures; or, perform random access procedures based on the first link; or, perform radio link management RLM based on the first link; or, respectively based on the first link and the second link
  • the link performs RLM, and when a radio link failure RLF occurs on the first link, the radio resource control RRC re-establishment is triggered; where the first link is the primary link.
  • the communication unit 1100 is further configured to receive N sets of configuration parameters related to the uplink control channel corresponding to the serving cell, N sets of configuration parameters related to the uplink control channel and N sets of configuration parameters related to the downlink control channel One by one.
  • the processing unit 1200 is further configured to: determine a protocol architecture type for communication with the serving cell, where the protocol architecture type includes at least one of the following: a multi-connection-like architecture, a carrier-like aggregation architecture, or a single-cell-like architecture.
  • the communication unit 1100 is further used to: obtain indication information, and the indication information is used to indicate the protocol architecture type for the terminal device to communicate with the serving cell; the processing unit 1200 is specifically used to determine communication with the serving cell according to the indication information The type of protocol architecture.
  • N sets of configuration parameters related to the downlink control channel correspond to N links of the serving cell; the processing unit 1200 is also used to: when the protocol architecture type is a multi-connection-like architecture, the corresponding configuration can use the wireless bearer of the serving cell RB, generate a packet data convergence layer protocol PDCP entity, generate N radio link control RLC entities, generate N media access control MAC entities, and generate N hybrid automatic repeat request HARQ entities, where one PDCP entity is N links are shared, N RLC entities correspond to N links, N MAC entities correspond to N links, N HARQ entities correspond to N links; or, when the protocol architecture type is carrier-like aggregation architecture
  • the corresponding configuration can use the RB of the serving cell to generate one PDCP entity, one RLC entity, and one MAC entity, and generate N HARQ entities, where one PDCP entity is shared by N links and one RLC entity is N Link sharing, one MAC entity is shared by N links, and N HARQ entities correspond to N links; or, when the protocol architecture type is
  • the communication unit 1100 is configured to: communicate with the serving cell based on N sets of configuration parameters related to the uplink control channel corresponding to the serving cell, where N sets of configuration parameters related to the uplink control channel are related to N One set of configuration parameters related to the downlink control channel is associated with each other. N sets of configuration parameters related to the downlink control channel correspond to N links of the serving cell.
  • the N links of the serving cell share one PDCP entity, one RLC entity, and one MAC entity and one HARQ entity, N is an integer greater than or equal to 2.
  • the configuration parameters include at least one of the following: physical downlink control channel PDCCH configuration, cell identification information, cell radio network temporary identification C-RNTI, demodulation reference signal DMRS, beam set information, or beam information.
  • the communication apparatus 1000 may implement steps or processes corresponding to the terminal device in the method 200 according to the embodiment of the present application.
  • the communication apparatus 1000 may include the terminal device in the method 200 in FIG. 9. Method unit.
  • each unit in the communication device 1000 and the other operations and/or functions described above are respectively to implement the corresponding flow of the method 200 in FIG. 9.
  • the communication unit 1100 can be used to perform step 220 in the method 200
  • the processing unit 1200 can be used to perform step 230 in the method 200.
  • the communication unit 1100 in the communication device 1000 may correspond to the transceiver 2020 in the terminal device 2000 shown in FIG. 11, and the processing unit 1200 in the communication device 1000 may This corresponds to the processor 2010 in the terminal device 2000 shown in FIG. 11.
  • the communication unit 1100 in the communication device 1000 may be an input/output interface.
  • the communication apparatus 1000 may implement steps or processes corresponding to the network device in the above method embodiment, for example, it may be a network device, or a chip or circuit configured in the network device; For another example, it may also be a transceiver point, or a chip or circuit disposed in the transceiver point.
  • the processing unit 1200 is configured to: generate configuration information of the serving cell, and the configuration information includes N sets of configuration parameters related to the downlink control channel corresponding to the serving cell, wherein each set of configuration parameters includes the same parameter type, and N is greater than or equal to 2.
  • An integer of; communication unit 1100 is used to: send configuration information of the serving cell.
  • the communication unit 1100 is further configured to: send first downlink control information DCI, and the configuration parameter corresponding to the first DCI belongs to one of N sets of configuration parameters related to the downlink control channel.
  • the configuration parameters include at least one of the following: physical downlink control channel PDCCH configuration, cell identification information, cell radio network temporary identification C-RNTI, demodulation reference signal DMRS, beam set information, or beam information.
  • the communication unit 1100 is further configured to send N sets of configuration parameters related to the uplink control channel corresponding to the serving cell, N sets of configuration parameters related to the uplink control channel and N sets of configuration parameters related to the downlink control channel One by one.
  • the communication unit 1100 is further configured to: send indication information, which is used to indicate a protocol architecture type for communication between the terminal device and the serving cell, where the protocol architecture type includes at least one of the following: multi-connection-like architecture, carrier-like aggregation Architecture, or similar single-cell architecture.
  • the communication unit 1100 is configured to: communicate with the terminal device based on N sets of configuration parameters related to the downlink control channel corresponding to the serving cell, where the N sets of configuration parameters related to the downlink control channel correspond to the service N links of the cell, and the N links of the serving cell share a PDCP entity, an RLC entity, a MAC entity, and a HARQ entity, and N sets of configuration parameters related to the downlink control channel are related to N sets of uplink control channels
  • the configuration parameters are related one by one, N is an integer greater than or equal to 2.
  • the configuration parameters include at least one of the following: physical downlink control channel PDCCH configuration, cell identification information, cell radio network temporary identification C-RNTI, demodulation reference signal DMRS, beam set information, or beam information.
  • the communication apparatus 1000 may implement the steps or processes performed by the network device corresponding to the method 200 according to an embodiment of the present application.
  • the communication apparatus 1000 may include the network device performed by the method 200 in FIG. 9. Method unit.
  • each unit in the communication device 1000 and the other operations and/or functions described above are respectively to implement the corresponding flow of the method 200 in FIG. 9.
  • the communication unit 1100 can be used to perform step 220 in the method 200
  • the processing unit 1200 can be used to perform step 210 and step 230 in the method 200.
  • the communication unit in the communication device 1000 may correspond to the transceiver 3200 in the network device 3000 shown in FIG. 12, and the processing unit 1200 in the communication device 1000 may This corresponds to the processor 3100 in the network device 3000 shown in FIG. 12.
  • the communication unit 1100 in the communication device 1000 may be an input/output interface.
  • FIG. 11 is a schematic structural diagram of a terminal device 2000 provided by an embodiment of the present application.
  • the terminal device 2000 may be applied to the system shown in FIGS. 1 to 8 to perform the functions of the terminal device in the foregoing method embodiments, or to implement the steps or processes performed by the terminal device in the foregoing method embodiments.
  • the terminal device 2000 includes a processor 2010 and a transceiver 2020.
  • the terminal device 2000 further includes a memory 2030.
  • the processor 2010, the transceiver 2002 and the memory 2030 can communicate with each other through an internal connection channel to transfer control and/or data signals.
  • the memory 2030 is used to store a computer program, and the processor 2010 is used from the memory 2030 Call and run the computer program to control the transceiver 2020 to send and receive signals.
  • the terminal device 2000 may further include an antenna 2040 for sending uplink data or uplink control signaling output by the transceiver 2020 through a wireless signal.
  • the processor 2010 and the memory 2030 may be combined into a processing device.
  • the processor 2010 is used to execute the program code stored in the memory 2030 to realize the above-mentioned functions.
  • the memory 2030 may also be integrated in the processor 2010 or independent of the processor 2010.
  • the processor 2010 may correspond to the processing unit in FIG. 10.
  • the above-mentioned transceiver 2020 may correspond to the communication unit in FIG. 10, and may also be referred to as a transceiver unit.
  • the transceiver 2020 may include a receiver (or receiver, receiving circuit) and a transmitter (or transmitter, transmitting circuit). Among them, the receiver is used to receive signals, and the transmitter is used to transmit signals.
  • the terminal device 2000 shown in FIG. 11 can implement various processes involving the terminal device in the method embodiment shown in FIG. 9.
  • the operations and/or functions of each module in the terminal device 2000 are respectively to implement the corresponding processes in the above method embodiments.
  • the above-mentioned processor 2010 may be used to perform the actions described in the foregoing method embodiments that are internally implemented by the terminal device, and the transceiver 2020 may be used to perform the operations described in the foregoing method embodiments by the terminal device to or from the network device. action.
  • the transceiver 2020 may be used to perform the operations described in the foregoing method embodiments by the terminal device to or from the network device. action.
  • the terminal device 2000 may further include a power supply 2050, which is used to provide power to various devices or circuits in the terminal device.
  • a power supply 2050 which is used to provide power to various devices or circuits in the terminal device.
  • the terminal device 2000 may further include one or more of an input unit 2060, a display unit 2070, an audio circuit 2080, a camera 2090, a sensor 2100, etc.
  • the audio circuit It may also include a speaker 2082, a microphone 2084, and so on.
  • FIGS. 1 to 8 are schematic structural diagrams of a network device provided by an embodiment of the present application, for example, may be a schematic structural diagram of a base station.
  • the base station 3000 may be applied to the system shown in FIGS. 1 to 8 to perform the functions of the network device in the above method embodiments, or implement the steps or processes performed by the network devices in the above method embodiments.
  • the base station 3000 may include one or more radio frequency units, such as a remote radio unit (RRU) 3100 and one or more baseband units (BBU) (also called digital units) , Digital, unit, DU) 3200.
  • RRU remote radio unit
  • BBU baseband units
  • the RRU 3100 may be referred to as a transceiver unit, which corresponds to the communication unit 1100 in FIG.
  • the transceiver unit 3100 may also be called a transceiver, a transceiver circuit, or a transceiver, etc., which may include at least one antenna 3101 and a radio frequency unit 3102.
  • the transceiving unit 3100 may include a receiving unit and a transmitting unit, the receiving unit may correspond to a receiver (or receiver, receiving circuit), and the transmitting unit may correspond to a transmitter (or transmitter, transmitting circuit).
  • the RRU 3100 part is mainly used for the transmission and reception of radio frequency signals and the conversion of radio frequency signals and baseband signals, for example, for sending instruction information to terminal devices.
  • the 3200 part of the BBU is mainly used for baseband processing and controlling the base station.
  • the RRU 3100 and the BBU 3200 may be physically arranged together, or may be physically separated, that is, distributed base stations.
  • the BBU 3200 is the control center of the base station, and may also be referred to as a processing unit, which may correspond to the processing unit 1200 in FIG. 10, and is mainly used to complete baseband processing functions, such as channel coding, multiplexing, modulation, spread spectrum, and so on.
  • the BBU processing unit
  • the BBU may be used to control the base station to perform the operation flow on the network device in the above method embodiment, for example, generating the above indication information, or configuring a serving cell, etc.
  • the BBU 3200 may be composed of one or more boards, and multiple boards may jointly support a wireless access network (such as an LTE network) of a single access standard, or may support different access standards respectively. Wireless access network (such as LTE network, 5G network or other networks).
  • the BBU 3200 also includes a memory 3201 and a processor 3202.
  • the memory 3201 is used to store necessary instructions and data.
  • the processor 3202 is used to control the base station to perform necessary actions, for example, to control the base station to perform the operation flow on the network device in the above method embodiment.
  • the memory 3201 and the processor 3202 may serve one or more single boards. In other words, the memory and the processor can be set separately on each board. It is also possible that multiple boards share the same memory and processor. In addition, each board can also be provided with necessary circuits.
  • the base station 3000 shown in FIG. 12 can implement various processes involving network devices in the method embodiment of FIG. 9.
  • the operations and/or functions of each module in the base station 3000 are to implement the corresponding processes in the above method embodiments.
  • the above-mentioned BBU 3200 can be used to perform the actions described in the foregoing method embodiments that are implemented internally by the network device, and the RRU 3100 can be used to perform the actions described in the previous method embodiments that the network device sends to or receives from the terminal device.
  • the RRU 3100 can be used to perform the actions described in the previous method embodiments that the network device sends to or receives from the terminal device.
  • An embodiment of the present application further provides a processing device, including a processor and an interface.
  • the processor may be used to execute the method in the above method embodiment.
  • the above processing device may be a chip.
  • the processing device may be a field programmable gate array (field programmable gate array (FPGA)), an application specific integrated circuit (ASIC), or a system chip (SoC), or It is a central processor (CPU), it can also be a network processor (NP), it can also be a digital signal processing circuit (digital signal processor, DSP), or a microcontroller (micro controller) , MCU), can also be a programmable controller (programmable logic device, PLD) or other integrated chips.
  • FPGA field programmable gate array
  • ASIC application specific integrated circuit
  • SoC system chip
  • CPU central processor
  • NP network processor
  • DSP digital signal processor
  • microcontroller micro controller
  • MCU microcontroller
  • PLD programmable logic device
  • each step of the above method may be completed by an integrated logic circuit of hardware in the processor or instructions in the form of software.
  • the steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied and executed by a hardware processor, or may be executed and completed by a combination of hardware and software modules in the processor.
  • the software module may be located in a mature storage medium in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, and a register.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware. In order to avoid repetition, they are not described in detail here.
  • the processor in the embodiment of the present application may be an integrated circuit chip with signal processing capabilities.
  • the steps of the foregoing method embodiments may be completed by instructions in the form of hardware integrated logic circuits or software in the processor.
  • the aforementioned processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components .
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application may be implemented or executed.
  • the general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied and executed by a hardware decoding processor, or may be executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module may be located in a mature storage medium in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, and a register.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be read-only memory (read-only memory, ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electronically Erasable programmable read only memory (electrically EPROM, EEPROM) or flash memory.
  • Volatile memory can be random access memory (random access memory, RAM), which acts as an external cache.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • double data rate synchronous dynamic random access memory double data SDRAM, DDR SDRAM
  • enhanced synchronous dynamic random access memory enhanced SDRAM, ESDRAM
  • serial link DRAM SLDRAM
  • direct RAMbus RAM direct RAMbus RAM
  • the present application also provides a computer program product, the computer program product includes: computer program code, when the computer program code runs on the computer, the computer is caused to execute the embodiment shown in FIG. 9 The method of any one of the embodiments.
  • the present application also provides a computer-readable medium that stores program codes, and when the program codes are run on a computer, the computer is caused to execute the embodiment shown in FIG. 9 The method of any one of the embodiments.
  • the present application further provides a system, which includes the foregoing one or more terminal devices and one or more network devices.
  • the present application further provides a system, which includes the foregoing multiple TRPs.
  • the computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on the computer, all or part of the processes or functions described in the embodiments of the present application are generated.
  • the computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be from a website site, computer, server or data center Transmission to another website, computer, server or data center via wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device including one or more available medium integrated servers, data centers, and the like.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a high-density digital video disc (DVD)), or a semiconductor medium (for example, a solid state disc, SSD)) etc.
  • a magnetic medium for example, a floppy disk, a hard disk, a magnetic tape
  • an optical medium for example, a high-density digital video disc (DVD)
  • DVD high-density digital video disc
  • SSD solid state disc
  • the network device in each of the above device embodiments corresponds exactly to the network device or terminal device in the terminal device and method embodiments, and the corresponding steps are performed by the corresponding modules or units, for example, the communication unit (transceiver) performs the receiving or The steps of sending, other than sending and receiving, can be executed by the processing unit (processor).
  • the function of the specific unit can refer to the corresponding method embodiment. There may be one or more processors.
  • a component may be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, and/or a computer.
  • the application running on the computing device and the computing device can be components.
  • One or more components can reside in a process and/or thread of execution, and a component can be localized on one computer and/or distributed between two or more computers.
  • these components can execute from various computer readable media having various data structures stored thereon.
  • the component may, for example, be based on a signal having one or more data packets (eg, data from two components that interact with another component between a local system, a distributed system, and/or a network, such as the Internet that interacts with other systems through signals) Communicate through local and/or remote processes.
  • data packets eg, data from two components that interact with another component between a local system, a distributed system, and/or a network, such as the Internet that interacts with other systems through signals
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the unit is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical, or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium.
  • the technical solution of the present application essentially or part of the contribution to the existing technology or part of the technical solution can be embodied in the form of a software product
  • the computer software product is stored in a storage medium, including Several instructions are used to enable a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application.
  • the foregoing storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program codes .

Landscapes

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

Abstract

本申请提供了一种通信方法和通信装置，该方法包括：接收服务小区的配置信息，该配置信息包括N套与下行控制信道相关的配置参数，其中，每套配置参数包括的参数类型相同，N套与下行控制信道相关的配置参数对应于服务小区中的N个收发点的，N为大于或等于2的整数；基于N套与下行控制信道相关的配置参数，与服务小区通信。通过本申请，服务小区中的收发点可以基于与其对应的一套配置参数与终端设备传输数据，提高通信效率。

Description

通信方法和通信装置
本申请要求于2019年01月11日提交中国专利局、申请号为201910028856.2、申请名称为“通信方法和通信装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，并且更具体地，涉及通信方法和通信装置。
背景技术
为提高终端设备的数据传输速率，第三代合作伙伴计划(3rd generation partnership project，3GPP)无线接入网络第一工作组(radio access network working group#1，RAN1)研究支持一个小区内的多收发点传输(multiple transmit receive point transmission，Multi-TRP transmission)机制。
多个收发点(transmission and reception point，TRP)间可以通过理想回传(ideal backhaul)或者非理想回传(non-ideal backhaul)进行通信。
在一个小区内的多收发点传输机制下，终端设备如何与该小区之间通信成为当前亟需解决的问题。
发明内容
本申请提供一种通信方法和通信装置，以期终端设备能够与小区内的多个收发点通信，并尽可能保证通信效率。
第一方面，提供了一种通信方法。该方法可以由终端设备执行，或者，也可以由配置于终端设备中的芯片或电路执行，本申请对此不作限定。
具体地，该方法包括：接收服务小区的配置信息，配置信息包括对应于服务小区的N套与下行控制信道相关的配置参数，其中，每套配置参数包括的参数类型相同，N为大于或等于2的整数；基于N套与下行控制信道相关的配置参数，与所述服务小区通信。
其中，服务小区，可以是网络配置与终端设备进行上下行传输的小区。
其中，终端设备与服务小区通信，也可以理解为，终端设备通过该服务小区(或该服务小区所属的网络设备)分配的传输资源(例如，频域资源，或者说，频谱资源)与服务小区中的收发点进行通信。其中，收发点可以为收发点(transmission and reception point，TRP)，也可以称为接入设备或者传输点，应理解，其命名不应对本申请构成任何限定，本申请并不排除在未来的协议中定义其他名称来表示相同或相似含义的可能。在本申请实施例中，用收发点(TRP)表示。
其中，N套与下行控制信道相关的配置参数，可以理解为，服务小区中包括N个收发点，终端设备可以与该服务小区内的N个收发点通信，该N套与下行控制信道相关的配 置参数对应服务小区中的N个收发点，或者说，每个收发点对应一套与下行控制信道相关的配置参数。每个收发点可以基于其对应的与下行控制信道相关的配置参数与终端设备传输数据。
或者，N套与下行控制信道相关的配置参数，可以理解为，服务小区中包括N个收发点，终端设备与该N个收发点中的每个收发点通信时，可以分别采用对应的一个链路进行通信，终端设备可以与该服务小区内的N个链路通信，该N套与下行控制信道相关的配置参数对应服务小区与终端设备通信的N个链路，或者说，每个链路对应一套与下行控制信道相关的配置参数。每个链路可以基于其对应的与下行控制信道相关的配置参数与终端设备传输数据。
基于上述技术方案，服务小区的配置信息包括N套与下行控制信道相关的配置参数，且每套配置参数包括的参数类型相同，也就是说，每一套配置参数对应服务小区中的一个收发点，或者，也可以理解为，网络设备为服务小区中的每一个收发点配置一套与下行控制信道相关的配置参数。那么服务小区中的每个收发点都可以基于其对应的配置参数(或者为其配置的配置参数，或者，其关联的配置参数)与终端设备传输数据。从而不仅能够避免服务小区中的多个收发点采用一套配置参数与终端设备进行通信可能会导致的干扰问题，而且可以使得终端设备根据实际通信情况，与相应的收发点基于对应的配置参数进行通信，提高通信效率。
结合第一方面，在第一方面的某些实现方式中，方法还包括：接收第一下行控制信息DCI，第一DCI对应的配置参数属于N套与下行控制信道相关的配置参数中的一套；根据第一DCI，确定第一DCI对应的链路。
其中，从服务小区接收第一下行控制信息(downlink control information，DCI)，可以理解为，接收来自服务小区中的一个收发点(或者说该收发点通过其与终端设备之间的链路)发送的DCI。
基于上述技术方案，服务小区中的收发点向终端设备发送DCI时，可以基于该收发点对应的一套配置参数发送该DCI。相应地，终端设备接收到DCI后，也可以根据该套配置参数，确定发送该DCI的收发点或链路，即终端设备能够区分接收到的DCI是来自于哪个收发点或哪个链路的。从而，终端设备也能够向相应的收发点或链路发送上行信息。
结合第一方面，在第一方面的某些实现方式中，配置参数包括以下至少一项：物理下行控制信道PDCCH配置、小区标识信息、小区无线网络临时标识C-RNTI、解调参考信号DMRS、波束集信息、或波束信息。
结合第一方面，在第一方面的某些实现方式中，N套与下行控制信道相关的配置参数对应服务小区的N个链路，N个链路包括第一链路和第二链路，方法还包括：基于第一链路执行波束失败检测和波束失败恢复过程；或者，基于第一链路执行随机接入过程；或者，基于第一链路执行无线链路管理RLM；或者，分别基于第一链路和第二链路执行RLM，且在第一链路发生无线链路失败RLF时，触发无线资源控制RRC重建；其中，第一链路是主链路。
其中，服务小区的N个链路，也可以理解为，服务小区中的N个收发点。
其中，N套与下行控制信道相关的配置参数对应服务小区的N个链路，也可以理解为，N套与下行控制信道相关的配置参数对应服务小区中的N个收发点，即服务小区中的每个 收发点可以基于各自对应的一套配置参数与终端设备传输数据。
基于上述技术方案，终端设备可以仅基于一个链路(例如记作第一链路)或者仅针对一个收发点执行一些操作，避免与一个服务小区内的全部或多个TRP间执行多次这些过程，简化了终端设备的实现和协议复杂度。
结合第一方面，在第一方面的某些实现方式中，方法还包括：接收对应于服务小区的N套与上行控制信道相关的配置参数，N套与上行控制信道相关的配置参数与N套与下行控制信道相关的配置参数一一关联。
基于上述技术方案，N套与下行控制信道相关的配置参数分别与N套与上行控制信道相关的配置参数一一关联，即服务小区中的一个收发点基于与其对应的一套与下行控制信道相关的配置参数发送下行信息时，终端设备也可以基于与该套配置参数对应的一套与上行控制信道相关的配置参数，向该收发点发送上行信息或者上行反馈，使得终端设备与该收发点间能正常、有效地进行通信，且该收发点可以及时接收到与之对应的上行信息，提高鲁棒性且提高终端设备的吞吐量。
结合第一方面，在第一方面的某些实现方式中，方法还包括：确定与服务小区通信的协议架构类型，其中，协议架构类型包括以下至少一项：类多连接架构、类载波聚合架构、或类单小区架构。
其中，类单小区架构可以为第一类单小区架构，也可以为第二类单小区架构，下文实施例中具体描述。应理解，第一类单小区架构、第二类单小区架构的命名不应对本申请构成任何限定。本申请并不排除在未来的协议中定义其他名称来表示相同或相似含义的可能。
结合第一方面，在第一方面的某些实现方式中，方法还包括：获取指示信息，指示信息用于指示终端设备与服务小区通信的协议架构类型；确定与服务小区通信的协议架构类型，包括：根据指示信息确定与服务小区通信的协议架构类型。
结合第一方面，在第一方面的某些实现方式中，N套与下行控制信道相关的配置参数对应服务小区的N个链路；当协议架构类型为类多连接架构时，对应配置可以使用服务小区的无线承载RB，生成一个分组数据汇聚层协议PDCP实体，生成N个无线链路控制RLC实体、生成N个媒体接入控制MAC实体、以及生成N个混合自动重传请求HARQ实体，其中，一个PDCP实体为N个链路共用，N个RLC实体与N个链路对应，N个MAC实体与N个链路对应，N个HARQ实体与N个链路对应；或者，当协议架构类型为类载波聚合架构时，对应配置可以使用服务小区的RB，生成一个PDCP实体、一个RLC实体、以及一个MAC实体，且生成N个HARQ实体，其中，一个PDCP实体为N个链路共用，一个RLC实体为N个链路共用，一个MAC实体为N个链路共用，N个HARQ实体与N个链路对应；或者，当协议架构类型为类单小区架构时，对应配置可以使用服务小区的RB，生成一个PDCP实体、一个RLC实体、一个MAC实体、以及一个HARQ实体，其中，一个PDCP实体为N个链路共用，一个RLC实体为N个链路共用，一个MAC实体为N个链路共用，一个HARQ实体为N个链路共用。
第二方面，提供了一种通信方法。该方法可以由网络设备执行，或者，也可以由配置于网络设备中的芯片或电路执行，本申请对此不作限定。
其中，网络设备可以理解为收发点所属的接入网设备或者理解为控制该收发点的接入 网设备(例如，接入网设备可以是基站，如eNB、gNB、CU或DU等，不做限定)，该收发点所属的服务小区属于该接入网设备。
具体地，该方法包括：生成服务小区的配置信息，配置信息包括对应于服务小区的N套与下行控制信道相关的配置参数，其中，每套配置参数包括的参数类型相同，N为大于或等于2的整数；发送服务小区的配置信息。
其中，服务小区，可以是网络设备配置的与终端设备进行上下行传输的小区。
基于上述技术方案，网络设备可以为服务小区配置N套与下行控制信道相关的配置参数，且每套配置参数包括的参数类型相同，或者，也可以理解为，网络设备为服务小区中的每个收发点配置一套与下行控制信道相关的配置参数，那么服务小区中的每个收发点都可以基于为其配置的配置参数与终端设备传输数据。从而不仅能够避免服务小区中的多个收发点采用一套配置参数与终端设备进行通信可能会导致的干扰问题，而且可以使得终端设备根据实际通信情况，与相应的收发点基于对应的配置参数进行通信，提高通信效率。
结合第二方面，在第二方面的某些实现方式中，方法还包括：发送第一下行控制信息DCI，第一DCI对应的配置参数属于N套与下行控制信道相关的配置参数中的一套。
结合第二方面，在第二方面的某些实现方式中，配置参数包括以下至少一项：物理下行控制信道PDCCH配置、小区标识信息、小区无线网络临时标识C-RNTI、解调参考信号DMRS、波束集信息、或波束信息。
结合第二方面，在第二方面的某些实现方式中，方法还包括：发送对应于服务小区的N套与上行控制信道相关的配置参数，N套与上行控制信道相关的配置参数与N套与下行控制信道相关的配置参数一一关联。
结合第二方面，在第二方面的某些实现方式中，方法还包括：发送指示信息，指示信息用于指示终端设备与服务小区通信的协议架构类型，其中，协议架构类型包括以下至少一项：类多连接架构、类载波聚合架构、或类单小区架构。
第三方面，提供了一种通信方法。该方法可以由终端设备执行，或者，也可以由配置于终端设备中的芯片或电路执行，本申请对此不作限定。
具体地，该方法包括：基于对应于服务小区的N套与上行控制信道相关的配置参数，与服务小区通信，其中，N套与上行控制信道相关的配置参数与N套与下行控制信道相关的配置参数一一关联，N套与下行控制信道相关的配置参数对应服务小区的N个链路，服务小区的N个链路共用一个PDCP实体、一个RLC实体、一个MAC实体、以及一个HARQ实体，N为大于或等于2的整数。
基于上述技术方案，终端设备可以基于N套与上行控制信道相关的配置参数，向该收发点发送上行信息或者上行反馈，使得终端设备与该收发点间能正常、有效地进行通信，且该收发点可以及时接收到与之对应的上行信息，提高鲁棒性且提高终端设备的吞吐量。通过上述方案，终端设备可以不需要为每一个配置的可以使用该服务小区的RB分别生成RLC实体、MAC实体和HARQ实体，从而可以避免占用更多的存储和计算等资源。此外，各个收发点可以直接接收终端设备发送的对应该收发点的HARQ反馈，可以避免HARQ重传不及时和吞吐量下降的问题。此外，通过上述方案，针对网络设备配置的可以使用该服务小区的一个RB，终端设备可以不需要为每一个收发点分别生成一个HARQ实体，从而可以避免占用更多存储和计算等资源。
结合第三方面，在第三方面的某些实现方式中，配置参数包括以下至少一项：物理下行控制信道PDCCH配置、小区标识信息、小区无线网络临时标识C-RNTI、解调参考信号DMRS、波束集信息、或波束信息。
第四方面，提供了一种通信方法。该方法可以由网络设备执行，或者，也可以由配置于网络设备中的芯片或电路执行，本申请对此不作限定。
其中，网络设备可以理解为收发点所属的接入网设备或者理解为控制该收发点的接入网设备(例如，接入网设备可以是基站，如eNB、gNB、CU或DU等，不做限定)，该收发点所属的服务小区属于该接入网设备。
具体地，该方法包括：基于对应于服务小区的N套与下行控制信道相关的配置参数，与终端设备通信，其中，N套与下行控制信道相关的配置参数对应服务小区的N个链路，服务小区的N个链路共用一个PDCP实体、一个RLC实体、一个MAC实体、以及一个HARQ实体，N套与下行控制信道相关的配置参数与N套与上行控制信道相关的配置参数一一关联，N为大于或等于2的整数。
结合第四方面，在第四方面的某些实现方式中，配置参数包括以下至少一项：物理下行控制信道PDCCH配置、小区标识信息、小区无线网络临时标识C-RNTI、解调参考信号DMRS、波束集信息、或波束信息。
第五方面，提供了一种通信装置，包括：通信单元和处理单元，其中，通信单元用于：接收服务小区的配置信息，配置信息包括对应于服务小区的N套与下行控制信道相关的配置参数，其中，每套配置参数包括的参数类型相同，N为大于或等于2的整数；处理单元用于：基于N套与下行控制信道相关的配置参数，与服务小区通信。
其中，该装置可以配置在或本身即为终端设备。
结合第五方面，在第五方面的某些实现方式中，通信单元还用于：接收第一下行控制信息DCI，第一DCI对应的配置参数属于N套与下行控制信道相关的配置参数中的一套；处理单元用于：根据第一DCI，确定第一DCI对应的链路。
结合第五方面，在第五方面的某些实现方式中，配置参数包括以下至少一项：物理下行控制信道PDCCH配置、小区标识信息、小区无线网络临时标识C-RNTI、解调参考信号DMRS、波束集信息、或波束信息。
结合第五方面，在第五方面的某些实现方式中，N套与下行控制信道相关的配置参数对应服务小区的N个链路，N个链路包括第一链路和第二链路，处理单元还用于：基于第一链路执行波束失败检测和波束失败恢复过程；或者，基于第一链路执行随机接入过程；或者，基于第一链路执行无线链路管理RLM；或者，分别基于第一链路和所述第二链路执行RLM，且在第一链路发生无线链路失败RLF时，触发无线资源控制RRC重建；其中，第一链路是主链路。
结合第五方面，在第五方面的某些实现方式中，通信单元还用于：接收对应于服务小区的N套与上行控制信道相关的配置参数，N套与上行控制信道相关的配置参数与N套与下行控制信道相关的配置参数一一关联。
结合第五方面，在第五方面的某些实现方式中，处理单元还用于：确定与服务小区通信的协议架构类型，其中，协议架构类型包括以下至少一项：类多连接架构、类载波聚合架构、或类单小区架构。
结合第五方面，在第五方面的某些实现方式中，通信单元还用于：获取指示信息，指示信息用于指示终端设备与服务小区通信的协议架构类型；处理单元具体用于：根据指示信息确定与服务小区通信的协议架构类型。
结合第五方面，在第五方面的某些实现方式中，N套与下行控制信道相关的配置参数对应服务小区的N个链路；处理单元还用于：当协议架构类型为类多连接架构时，对应配置可以使用服务小区的无线承载RB，生成一个分组数据汇聚层协议PDCP实体，生成N个无线链路控制RLC实体、生成N个媒体接入控制MAC实体、以及生成N个混合自动重传请求HARQ实体，其中，一个PDCP实体为N个链路共用，N个RLC实体与N个链路对应，N个MAC实体与N个链路对应，N个HARQ实体与N个链路对应；或者，当协议架构类型为类载波聚合架构时，对应配置可以使用服务小区的RB，生成一个PDCP实体、一个RLC实体、以及一个MAC实体，且生成N个HARQ实体，其中，一个PDCP实体为N个链路共用，一个RLC实体为N个链路共用，一个MAC实体为N个链路共用，N个HARQ实体与N个链路对应；或者，当协议架构类型为类单小区架构时，对应配置可以使用服务小区的RB，生成一个PDCP实体、一个RLC实体、一个MAC实体、以及一个HARQ实体，其中，一个PDCP实体为N个链路共用，一个RLC实体为N个链路共用，一个MAC实体为N个链路共用，一个HARQ实体为N个链路共用。
其中，该装置中的各单元分别用于执行上述第一方面以及第一方面的各实现方式中的通信方法的各步骤。
在一种设计中，该装置为通信芯片，通信芯片可以包括用于发送信息或数据的输入电路或者接口，以及用于接收信息或数据的输出电路或者接口。
在另一种设计中，所述装置为通信设备，通信设备可以包括用于发送信息或数据的发射机，以及用于接收信息或数据的接收机。
第六方面，提供了一种通信装置，包括：通信单元和处理单元，其中，处理单元用于：生成服务小区的配置信息，配置信息包括对应于服务小区的N套与下行控制信道相关的配置参数，其中，每套配置参数包括的参数类型相同，N为大于或等于2的整数；通信单元用于：发送服务小区的配置信息。
其中，该装置可以配置在或本身即为网络设备执行，或者，基站中的服务小区执行，或者，收发点(例如TRP)执行。
结合第六方面，在第六方面的某些实现方式中，通信单元还用于：发送第一下行控制信息DCI，第一DCI对应的配置参数属于N套与下行控制信道相关的配置参数中的一套。
结合第六方面，在第六方面的某些实现方式中，配置参数包括以下至少一项：物理下行控制信道PDCCH配置、小区标识信息、小区无线网络临时标识C-RNTI、解调参考信号DMRS、波束集信息、或波束信息。
结合第六方面，在第六方面的某些实现方式中，通信单元还用于：发送对应于服务小区的N套与上行控制信道相关的配置参数，N套与上行控制信道相关的配置参数与N套与下行控制信道相关的配置参数一一关联。
结合第六方面，在第六方面的某些实现方式中，通信单元还用于：发送指示信息，指示信息用于指示终端设备与服务小区通信的协议架构类型，其中，协议架构类型包括以下至少一项：类多连接架构、类载波聚合架构、或类单小区架构。
其中，该装置中的各单元分别用于执行上述第二方面以及第二方面的各实现方式中的通信方法的各步骤。
在一种设计中，该通信装置为通信芯片，通信芯片可以包括用于发送信息或数据的输入电路或者接口，以及用于接收信息或数据的输出电路或者接口。
在另一种设计中，所述通信装置为通信设备，通信芯片可以包括用于发送信息或数据的发射机，以及用于接收信息或数据的接收机。
第七方面，提供了一种通信装置。包括：通信单元，其中，通信单元用于：基于对应于服务小区的N套与上行控制信道相关的配置参数，与服务小区通信，其中，N套与上行控制信道相关的配置参数与N套与下行控制信道相关的配置参数一一关联，N套与下行控制信道相关的配置参数对应服务小区的N个链路，服务小区的N个链路共用一个PDCP实体、一个RLC实体、一个MAC实体、以及一个HARQ实体，N为大于或等于2的整数。
其中，该装置可以配置在或本身即为终端设备。
结合第七方面，在第七方面的某些实现方式中，配置参数包括以下至少一项：物理下行控制信道PDCCH配置、小区标识信息、小区无线网络临时标识C-RNTI、解调参考信号DMRS、波束集信息、或波束信息。
第八方面，提供了一种通信装置。包括：通信单元和处理单元，其中，通信单元用于：基于对应于服务小区的N套与下行控制信道相关的配置参数，与终端设备通信，其中，N套与下行控制信道相关的配置参数对应服务小区的N个链路，服务小区的N个链路共用一个PDCP实体、一个RLC实体、一个MAC实体、以及一个HARQ实体，N套与下行控制信道相关的配置参数与N套与上行控制信道相关的配置参数一一关联，N为大于或等于2的整数。
其中，该装置可以配置在或本身即为网络设备执行，或者，基站中的服务小区执行，或者，收发点(例如TRP)执行。
结合第八方面，在第八方面的某些实现方式中，配置参数包括以下至少一项：物理下行控制信道PDCCH配置、小区标识信息、小区无线网络临时标识C-RNTI、解调参考信号DMRS、波束集信息、或波束信息。
第九方面，提供了一种通信设备，包括，处理器，存储器，该存储器用于存储计算机程序，该处理器用于从存储器中调用并运行该计算机程序，使得该通信设备执行第一方面或第三方面及其各种可能实现方式中的通信方法。
可选地，所述处理器为一个或多个，所述存储器为一个或多个。
可选地，所述存储器可以与所述处理器集成在一起，或者所述存储器与处理器分离设置。
可选的，该通信设备还包括，发射机(发射器)和接收机(接收器)。
第十方面，提供了一种通信设备，包括，处理器，存储器，该存储器用于存储计算机程序，该处理器用于从存储器中调用并运行该计算机程序，使得该通信设备执行第二方面或第四方面及其各种实现方式中的通信方法。
可选地，所述处理器为一个或多个，所述存储器为一个或多个。
可选地，所述存储器可以与所述处理器集成在一起，或者所述存储器与处理器分离设 置。
可选地，该通信设备还包括，发射机(发射器)和接收机(接收器)。
第十一方面，提供了一种通信系统，上述第九方面提供的通信设备和/或第十方面提供的通信设备。
在一个可能的设计中，该通信系统还可以包括本申请实施例提供的方案中与通信设备进行交互的其他设备。
第十二方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序(也可以称为代码，或指令)，当所述计算机程序被运行时，使得计算机执行上述第一方面至第四方面中任一种可能实现方式中的方法。
第十三方面，提供了一种计算机可读介质，所述计算机可读介质存储有计算机程序(也可以称为代码，或指令)当其在计算机上运行时，使得计算机执行上述第一方面至第四方面中任一种可能实现方式中的方法。
第十四方面，提供了一种芯片系统，包括存储器和处理器，该存储器用于存储计算机程序，该处理器用于从存储器中调用并运行该计算机程序，使得安装有该芯片系统的通信设备执行上述第一方面至第四方面中任一种可能实现方式中的方法。
其中，该芯片系统可以包括用于发送信息或数据的输入电路或者接口，以及用于接收信息或数据的输出电路或者接口。
第十五方面，提供了一种通信系统，包括多个收发点TRP。
第十六方面，提供了一种通信系统，包括前述的终端设备和基站。
基于本申请实施例，网络设备可以为服务小区配置N套与下行控制信道相关的配置参数，或者，也可以理解为，网络设备为服务小区中的每个收发点配置一套与下行控制信道相关的配置参数，那么服务小区中的每个收发点都可以基于为其配置的配置参数与终端设备传输数据。从而不仅能够避免服务小区中的多个收发点采用一套配置参数与终端设备进行通信可能会导致的干扰问题，而且可以使得终端设备根据实际通信情况，与相应的收发点基于对应的配置参数进行通信，提高通信效率。
附图说明
图1示出了一种网络架构的示意图；
图2示出了双连接的一种协议栈架构的示意图；
图3示出了载波聚合的一种协议栈架构的示意图；
图4至图6示出了三种协议栈架构的示意图；
图7是本申请实施例提出的一种协议栈架构的示意图；
图8是适用于本申请实施例的通信系统的一示意图；
图9是本申请实施例提出的通信方法的一示意性交互图；
图10是本申请的通信装置的一例的示意性框图；
图11是本申请的终端设备的一例的示意性结构图；
图12是本申请的网络设备的一例的示意性结构图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信系统，例如：长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、通用移动通信系统(universal mobile telecommunication system，UMTS)、第五代(5th generation，5G)系统或新无线(new radio，NR)或者其他演进的通信系统等。
本申请实施例中的终端设备也可以称为：用户设备(user equipment，UE)、移动台(mobile station，MS)、移动终端(mobile terminal，MT)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置等。
终端设备可以是一种向用户提供语音/数据连通性的设备，例如，具有无线连接功能的手持式设备、车载设备等。目前，一些终端的举例为：手机(mobile phone)、平板电脑、笔记本电脑、掌上电脑、移动互联网设备(mobile internet device，MID)、可穿戴设备，虚拟现实(virtual reality，VR)设备、增强现实(augmented reality，AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，5G网络中的终端设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端设备等，本申请实施例对此并不限定。
作为示例而非限定，在本申请实施例中，该终端设备还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
此外，在本申请实施例中，终端设备还可以是物联网(internet of things，IoT)系统中的终端设备，IoT是未来信息技术发展的重要组成部分，其主要技术特点是将物品通过通信技术与网络连接，从而实现人机互连，物物互连的智能化网络。
另外，本申请实施例中的网络设备可以是用于与终端设备通信的设备，该网络设备也可以称为接入网设备或无线接入网设备，可以是传输接收点(transmission reception point，TRP)，也可以是全球移动通信(global system for mobile communications，GSM)系统或码分多址(code division multiple access，CDMA)中的基站(base transceiver station，BTS)，也可以是宽带码分多址(wideband code division multiple access，WCDMA)系统中的基站 (NodeB，NB)，还可以是LTE系统中的演进型基站(evolved NodeB，eNB或eNodeB)，还可以是基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved NodeB，或home Node B，HNB)、基带单元(base band unit，BBU)，还可以是云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器，或者该网络设备可以为中继站、接入点、车载设备、可穿戴设备以及5G网络中的网络设备或者未来演进的PLMN网络中的网络设备等，可以是WLAN中的接入点(access point，AP),可以是新型无线系统(new radio，NR)系统中的gNB，本申请实施例并不限定。
在一种网络结构中，网络设备可以包括集中单元(centralized unit，CU)节点、或分布单元(distributed unit，DU)节点、或包括CU节点和DU节点的RAN设备、或者控制面CU节点(CU-CP节点)和用户面CU节点(CU-UP节点)以及DU节点的RAN设备。
网络设备为小区提供服务，终端设备通过网络设备分配的传输资源(例如，频域资源，或者说，频谱资源)与小区或者小区中的收发点进行通信，该小区可以是收发点对应的小区，小区可以属于宏基站(例如，宏eNB或宏gNB等)，也可以属于小小区(small cell)对应的基站，这里的小小区可以包括：城市小区(metro cell)、微小区(micro cell)、微微小区(pico cell)、毫微微小区(femto cell)等，这些小小区具有覆盖范围小、发射功率低的特点，适用于提供高速率的数据传输服务。
图1示出了双连接(dual-connectivity，DC)的一种网络架构的示意图，如图1所示，终端设备可以同时与两个网络设备存在通信连接并可收发数据，可以称之为双连接。该两个网络设备(例如基站)之中，可以有一个网络设备负责与该终端设备交互无线资源控制消息，并负责和核心网控制平面实体交互，那么，该网络设备可以称之为主节点(master node，MN)，例如，主节点可以是MeNB或者MgNB，不限定于此；则另一个网络设备可以称之为辅节点(secondary node，SN)，例如，辅节点可以是SeNB或者SgNB，不限定于此。其中，主节点为控制面锚点，即终端设备与主节点建立RRC连接，且主节点与核心网之间建立控制面连接。在DC中，主节点中的多个服务小区组成主小区组(master cell group，MCG)，包括一个主小区(primary cell，PCell)和可选的一个或多个辅小区(primary cell，PCell)。辅节点中的多个服务小区组成辅小区组(secondary cell group，SCG)，包括一个主辅小区(primary secondary cell，PSCell，或者，也可以称为特殊小区)和可选的一个或多个SCell。服务小区是指网络配置给终端设备进行上下行传输的小区。
类似的，终端设备也可以同时与多个网络设备存在通信连接并可收发数据，可以称之为多连接或者多链接(multi-connectivity，MC)，该多个网络设备之中，可以有一个网络设备负责与该终端设备交互无线资源控制消息，并负责和核心网控制平面实体交互，那么，该网络设备可以称之为MN，则其余的网络设备可以称之为SN。
网络设备和终端设备之间的通信遵循一定的用户面协议栈架构。例如用户面协议栈架构可以包括无线资源控制(radio resource control，RRC)层、分组数据汇聚层协议(packet data convergence protocol，PDCP)层、无线链路控制(radio link control，RLC)层、媒体接入控制(media access control，MAC)层和物理层等协议层的功能。图2示出了DC的一种协议栈架构图。在DC中，对应某无线承载，该两个网络设备共用一个PDCP实体，或者说，该PDCP实体为两个网络设备共同使用，且该两个网络设备有各自对应的RLC 和MAC实体。
应理解，图1是DC的一种网络架构的示意图。为便于理解本申请，下面首先介绍载波聚合的架构。
载波聚合(carrier aggregation，CA)：为了高效地利用零碎的频谱，系统支持不同载波单元之间的聚合。将2个或2个以上的载波聚合在一起以支持更大的传输带宽的技术可以称为载波聚合。
载波聚合技术中，终端设备可以配置多个载波单元(component carrier，CC，或者称，成员载波、组成载波、载波等)，每个CC可以对应于一个独立的小区。可以将一个CC等同于一个小区。例如，主小区对应主CC(或者称，主载波)，可以是为终端进行初始连接建立的小区，或进行RRC连接重建的小区，或是在切换(handover)过程中指定的主小区。辅小区对应辅CC(或者称，辅载波)，可以是在RRC重配置时添加的，用于提供额外的无线资源的小区。
对于处于连接态的终端设备来说，若未配置载波聚合，则该终端设备有一个服务小区；若配置了载波聚合，则该终端设备可以有多个服务小区(serving cell)，可以称为服务小区集合。例如，上文所述的主小区和辅小区组成了该终端设备的服务小区(serving cell)集合。换句话说，配置载波聚合的场景下，服务小区集合包括至少一个主小区和至少一个辅小区。或者说，配置了载波聚合的终端设备可与1个PCell和多个SCell进行数据传输。
图3示出了载波聚合的一种协议栈架构图。图3所示的协议栈架构适用于2个CC做载波聚合的场景。如图3所示，在2个CC进行CA的场景中，对应某无线承载，两个服务小区共用一个PDCP实体、一个RLC实体和一个MAC实体，换句话说，一个PDCP实体、一个RLC实体和一个MAC实体为两个服务小区共用，且两个服务小区有各自对应的独立的混合自动重传请求(hybrid automatic repeat request，HARQ)实体。
上面介绍了DC和CA的网络架构，下面介绍适用于本申请实施例的一个小区内多个收发点(TRP)传输的场景。
下面介绍一个小区内多个收发点传输的场景。以一个小区内的两个收发点(TRP)传输为例，图4至图6示出了三种可能的用户面协议栈架构图，图4至图6所示的协议栈架构均可适用于支持一个小区内多个收发点传输的场景，下面分别介绍。其中，该多个收发点之间可以通过理想回传进行通信，也可以通过非理想回传进行通信，对此，不作限定。
其中，多个收发点，或者，也可以称为多个传输点，即多个TRP，可以理解为地理位置上的一组天线。小区内有多个TRP，可以理解为，小区向终端设备发送下行信息时，可以分别通过该多个TRP将各自的信息发送出去。
假设小区内有N个TRP，其中，N为大于2或等于2的整数。小区的N个TRP可以分别通过一个链路或一个通道与终端设备通信，换句话说，该小区中包括N个链路或者N个通道。小区中的N个TRP，也可以理解为，小区的N个TRP分别与终端设备通信的N个通道。
应理解，图4至图6所示的协议栈架构均可适用于一个小区内两个收发点传输的场景，支持一个小区内多个收发点传输的协议栈架构可类比，不再赘述。
图4所示的协议栈架构类似于DC的协议栈架构，可以将图4所示的协议栈架构称为类双连接架构或者类多连接架构，故在下文实施例中，将图4所示的协议栈架构简称为多 连接架构。其中，当一个小区内有两个TRP时，可以称为类双连接架构；当一个小区内有三个TRP时，可以称为类三连接架构或者称为类多连接架构。应理解，类多连接架构或类双连接架构的命名不应对本申请构成任何限定。本申请并不排除在未来的协议中定义其他名称来表示相同或相似含义的可能。
图4中以两个TRP，分别记为TRP1、TRP2，为例进行说明。
如图4所示，对于同一个无线承载(radio bearer，RB)，网络设备侧的协议栈架构为：TRP1与TRP2共用一个PDCP实体，TRP1和TRP2有各自独立的(physical，PHY)实体、MAC实体、RLC实体，此外TRP1与TRP2有各自的MAC调度器(scheduler)和HARQ实体。本申请实施例中，MAC调度器具有资源分配、调度等功能，可以实现MAC实体的调度功能，MAC调度器可以看成是MAC实体的一部分功能模块，或者说，MAC调度器可以属于MAC实体，不做限定。下文出现MAC调度器的地方不再赘述。可以将具有MAC调度器的TRP看成主TRP，或者说将MAC调度器所属的TRP看成主TRP，或者说将MAC调度器所对应的TRP看成主TRP，或者将具有MAC调度功能的TRP看成主TRP，对此不做限定。终端设备侧的协议栈架构可以与网络设备侧的协议栈架构保持一致，例如，对于网络设备配置的可以使用服务小区的一个RB，网络设备侧包括：一个PDCP实体、两个MAC实体、两个RLC实体时，终端设备侧也包括：一个PDCP实体、两个MAC实体、两个RLC实体，不再赘述。
在图4所示的架构下，TRP1与TRP2可以各自发送下行控制信息(downlink control information，DCI)，独立调度物理下行共享信道(physical downlink shared channel，PDSCH)和物理上行共享信道(physical uplink share channel，PUSCH)。终端设备可以分别给TRP1与TRP2发送相对应的上行控制信息(uplink control information，UCI)。上行控制信息包括但不限于以下至少一种：调度请求(scheduling request，SR)、信道状态信息(channel state information，CSI)和HARQ反馈。例如，如图4中，TRP1可以向终端设备发送DCI、PDSCH，为区分，分别记为DCI1、PDSCH1，终端设备也可以向TRP1发送CSI、SR、HARQ反馈，为区分，分别记为CSI1、SR1、HARQ反馈1；TRP2可以向终端设备发送DCI、PDSCH，为区分，分别记为DCI2、PDSCH2，终端设备也可以向TRP2发送CSI、SR、HARQ反馈，为区分，分别记为CSI2、SR2、HARQ反馈2。
图5所示的协议栈架构类似于单小区通信时的用户面协议栈架构，故在下文实施例中，将类似于图5所示的协议栈架构简称为第一类单小区架构。应理解，第一类单小区架构的命名不应对本申请构成任何限定。本申请并不排除在未来的协议中定义其他名称来表示相同或相似含义的可能。
图5中仍以TRP1、TRP2为例进行说明。
如图5所示，对于同一个RB，网络设备侧的协议栈架构为：TRP1与TRP2共用一个PDCP实体、一个RLC实体、以及一个MAC实体，且TRP1与TRP2共用一个HARQ实体。一种示例，MAC调度器可以位于TRP1，则可以将TRP1看做主TRP，相应地，TRP1与终端设备通信的链路也可以称为主链路，TRP1的MAC调度器同时负责TRP1和TRP2的传输调度。或者，又一种示例，MAC调度器也可以位于TRP2，则可以将TRP2看做主TRP，相应地，TRP2与终端设备通信的链路也可以称为主链路，TRP2的MAC调度器同时负责TRP1和TRP2的传输调度。图5中为便于理解，仅示出一种情况。终端设备侧的 协议栈架构可以与网络设备侧保持一致，不再赘述。
在图5所示的架构下，两个TRP可以各自发送DCI，独立调度PDSCH和PUSCH；终端设备只向TRP1(即主TRP)发送上行控制信息，即终端设备向TRP1发送对应TRP1的上行控制信息和对应TRP2的上行控制信息。上行控制信息包括但不限于：SR、CSI和HARQ反馈。例如，如图5中，TRP1可以向终端设备发送DCI、PDSCH，为区分，分别记为DCI1、PDSCH1，TRP2可以向终端设备发送DCI、PDSCH，为区分，分别记为DCI2、PDSCH2；终端设备也可以向TRP1发送对应TRP1的CSI、SR、HARQ反馈，为区分，分别记为CSI1、SR1、HARQ反馈1，终端设备也可以向TRP1发送对应TRP2的CSI、SR、HARQ反馈，为区分，分别记为CSI2、SR2、HARQ反馈2。
图6所示的协议栈架构类似于CA的协议栈架构，故在下文实施例中，将类似于图6所示的协议栈架构简称为类载波聚合架构。应理解，类载波聚合架构的命名不应对本申请构成任何限定。本申请并不排除在未来的协议中定义其他名称来表示相同或相似含义的可能。
图6中仍以TRP1、TRP2为例进行说明。
如图6所示，对于同一个RB，网络网络设备侧的协议栈架构为：TRP1与TRP2共用一个PDCP实体、一个RLC实体、以及一个MAC实体，且TRP1与TRP2有各自对应的PHY实体、HARQ实体。MAC调度器位于TRP1(TRP1看做主TRP，相应地，TRP1与终端设备通信的链路也可以看做主链路)，TRP1的MAC调度器同时负责TRP1和TRP2的传输调度。终端设备侧的协议栈架构可以与网络设备侧保持一致，不再赘述。图6中，TRP2也可以实现虚拟MAC调度器从而能够及时处理TRP2侧的传输调度，但该虚拟MAC调度器必须在TRP1的MAC调度器的控制下进行工作。TRP1的MAC调度器与TRP2的虚拟MAC调度器属于主、从关系，即将TRP1看做主TRP，TRP2看做辅TRP。
在图6所示的架构下，两个TRP可以各自发送DCI，独立调度PDSCH和PUSCH。终端设备可以分别给两个TRP发送相对应的上行控制信息。上行控制信息包括但不限于：SR、CSI和HARQ反馈。例如，如图6中，TRP1可以向终端设备发送DCI、PDSCH，为区分，分别记为DCI1、PDSCH1，终端设备也可以向TRP1发送CSI、SR、HARQ反馈，为区分，分别记为CSI1、SR1、HARQ反馈1；TRP2可以向终端设备发送DCI、PDSCH，为区分，分别记为DCI2、PDSCH2，终端设备也可以向TRP2发送CSI、SR、HARQ反馈，为区分，分别记为CSI2、SR2、HARQ反馈2。
图4至图6的架构可应用于一个小区内的多收发点传输，本申请提出另一种可应用于一个小区内多收发点传输的架构。本申请提出的协议栈架构类似于单小区通信时的用户面协议栈架构，故在下文实施例中，将本申请提出的协议栈架构简称为第二类单小区架构。应理解，第二类单小区架构的命名不应对本申请构成任何限定。本申请并不排除在未来的协议中定义其他名称来表示相同或相似含义的可能。
下面以TRP1、TRP2为例，结合图7说明本申请提出的协议栈架构。图7所示的协议栈架构可适用于支持一个小区内两个TRP传输的场景，支持一个小区内多个TRP传输的协议栈架构可类比，例如，若需要支持一个小区内三个TRP传输的场景，则对于同一个RB，网络设备侧的协议栈架构为：3个TRP共用一个PDCP实体、一个RLC实体、以及一个MAC实体，且这3个TRP共用一个HARQ实体。终端设备侧的协议栈架构可以与 网络设备侧的协议栈架构保持一致。
如图7所示，对于同一个RB，网络设备侧的协议栈架构为：TRP1与TRP2共用一个PDCP实体、一个RLC实体、以及一个MAC实体，且TRP1与TRP2共用一个HARQ实体。其中，TRP1与TRP2共用一个PDCP实体、一个RLC实体、以及一个MAC实体，也就是说，一个PDCP实体为TRP1与TRP2共用、一个RLC实体为TRP1与TRP2共用、以及一个MAC实体为TRP1与TRP2共用；TRP1与TRP2共用一个HARQ实体，也就是说，对应该RB的唯一一个HARQ实体为TRP1与TRP2共用。
一种示例，MAC调度器位于TRP1，则可以将TRP1看做主TRP，相应地，TRP1与终端设备通信的链路也可以称为主链路，TRP1的MAC调度器同时负责TRP1和TRP2的传输调度。终端设备侧的协议栈架构可以与网络设备侧的协议栈架构保持一致，不再赘述。
图7中，TRP2也可以实现虚拟MAC调度器以及处理TRP2侧的传输调度，但该虚拟MAC调度器需要在TRP1的MAC调度器的控制下进行工作。TRP1的MAC调度器与TRP2的虚拟MAC调度器可以看做是主、从关系，即将TRP1看做主TRP，TRP2看做辅TRP，相应地，TRP1与终端设备通信的链路也可以称为主链路，TRP2与终端设备通信的链路也可以称为辅链路。
在图7所示的架构下，两个TRP可以各自发送DCI，独立调度PDSCH和PUSCH。在本申请实施例提出的协议栈架构中，配有多套PUCCH配置，分别用于终端设备向多个TRP发送相对应的上行控制信息。例如，配有两套PUCCH配置，终端设备可以分别使用对应的PUCCH配置，向TRP1、TRP2发送上行控制信息，即终端设备向TRP1发送对应TRP1的上行控制信息，向TRP2发送对应TRP2的上行控制信息。上行控制信息包括但不限于：SR、CSI和HARQ反馈。例如，如图7中，TRP1可以向终端设备发送DCI、PDSCH，为区分，分别记为DCI1、PDSCH1，TRP2可以向终端设备发送DCI、PDSCH，为区分，分别记为DCI2、PDSCH2；终端设备也可以向TRP1发送对应TRP1的CSI、SR、HARQ反馈，为区分，分别记为CSI1、SR1、HARQ反馈1，终端设备也可以向TRP2发送对应TRP2的CSI、HARQ反馈，为区分，分别记为CSI2、SR2、HARQ反馈2。
本申请实施例提出的协议栈架构，不仅能够减少终端设备存储和计算等资源的浪费，又能避免终端设备的吞吐量下降。图7所示的架构中，针对网络配置的可以使用该服务小区的RB，不需要为每一个收发点分别生成RLC实体、MAC实体和HARQ实体，从而可以避免占用更多的存储和计算等资源。此外，图7所示的架构中，TRP2可以直接接收终端设备发送的对应TRP2的HARQ反馈，可以避免HARQ重传不及时和吞吐量下降的问题。此外，图7所示的架构中，针对网络设备配置的可以使用该服务小区的RB，不需要为每一个收发点分别生成一个HARQ实体，从而可以避免占用更多存储和计算等资源。
关于本申请提出的协议栈架构，下文实施例中具体说明。
需要说明的是，本申请提出的第二类单小区架构和图5所示的第一类单小区架构，可统称为类单小区架构或者类单载波架构，其中，“第一”和“第二”仅是为区分不同的架构所作的命名。应理解，类单小区架构或者类单载波架构的命名不应对本申请构成任何限定。本申请并不排除在未来的协议中定义其他名称来表示相同或相似含义的可能。
图8是能够适用本申请实施例通信方法的系统100的示意图。如图8所示，该通信系统100可以包括至少一个终端设备，如图中所示的终端设备101；该通信系统100还可以 包括至少两个收发点，如图中所示的收发点#1 102和收发点#2 103。收发点#1 102和收发点#2 103可以是同一个小区中的传输节点。
在通信系统100中，收发点#1 102和收发点#2 103彼此之间可通过回程(backhaul)链路通信，该回程链路可以是有线回程链路(例如光纤、铜缆)，也可以是无线回程链路(例如微波)。收发点#1 102和收发点#2 103可以进行相互协同，来为终端设备101提供服务。因此，终端设备101可通过无线链路分别与收发点#1 102和收发点#2 103通信。
按照收发点之间的通信时延分类，可以将回程分为理想回程(ideal backhaul)和非理想回程(non-ideal backhaul)。理想回程下的两传输节点之间，通信时延可以是微秒级别，与NR中毫秒级别的调度相比，可以忽略不计；非理想回程下的两传输节点之间，通信时延可以是毫秒级别，与NR中毫秒级别的调度相比，无法忽略。上文所述的图4至图6所示的协议栈架构，以及本申请提出的如图7所示的协议栈架构，均可应用于通信系统100。
此外，该通信系统100可以是PLMN网络、D2D网络、M2M网络、IoT网络或者其他网络，图8只是举例的简化示意图，网络中还可以包括其他网络设备，图8中未予以画出。
应理解，上述图1至图8仅是示例性说明，不应对本申请构成任何限定。例如，通信系统还可以包括核心网设备，核心网设备可以与多个接入网设备连接，用于控制接入网设备。
为了便于理解本申请实施例，作出以下几点说明。
第一，在本申请实施例中，多处涉及高层参数，该高层参数可以包含在高层信令中。该高层信令例如可以是无线资源控制(radio resource control，RRC)消息，也可以是其他高层信令，本申请对此不做限定。
第二，在本申请实施例中，“用于指示”可以包括用于直接指示和用于间接指示，也可以包括显式指示和隐式指示。将某一信息(如下文所述的配置信息)所指示的信息称为待指示信息，则具体实现过程中，对待指示信息进行指示的方式有很多种，例如但不限于，可以直接指示待指示信息，如待指示信息本身或者该待指示信息的索引等。也可以通过指示其他信息来间接指示待指示信息，其中该其他信息与待指示信息之间存在关联关系。还可以仅仅指示待指示信息的一部分，而待指示信息的其他部分则是已知的或者提前约定的。例如，还可以借助预先约定(例如协议规定)是否存在某个信元来实现对待指示信息的指示，从而在一定程度上降低指示开销。
第三，在本申请实施例中，当描述A与B关联或关联的A与B时，可表示A与B之间具有关联关系。因此，“A与B关联”与“A与B之间具有关联关系”，可以表达相同的含义，或者说，是可替换的。例如，M套与下行控制信道相关的配置参数分别与M套与上行控制信道相关的配置参数一一关联，可表示下行控制信道相关的配置参数与上行控制信道相关的配置参数之间具有关联关系，即每套下行控制信道相关的配置参数关联一套上行控制信道相关的配置参数。为了简洁，这里不再一一举例说明。
第四，在本申请实施例中，多次提及“对应”，例如“对应DCI的PDCCH配置”，其表示的是，网络设备(如TRP所属的网络设备)或者收发点(如TRP)发送该DCI时所基于的PDCCH配置，或者，终端设备在由该PDCCH配置确定的空间/时频资源中检测，进而解析得到该DCI。本申请实施例中，PDCCH是一种信道/承载，DCI是承载在PDCCH 上的信息。例如，终端设备根据网络设备配置的PDCCH配置确定出候选空间/时频资源，终端设备在配置的候选空间/时频资源进行PDCCH检测，检测到PDCCH后，解析该PDCCH，从而得到承载在该PDCCH上的DCI信息。
第五，在下文示出的实施例中第一、第二、第三、第四以及各种数字编号仅为描述方便进行的区分，并不用来限制本申请实施例的范围。例如，区分不同的TRP、或不同的架构等。
第六，在下文示出的实施例中，“预先获取”可包括由网络设备信令指示或者预先定义，例如，协议定义。其中，“预先定义”可以通过在设备(例如，包括终端设备和网络设备)中预先保存相应的代码、表格或其他可用于指示相关信息的方式来实现，本申请对于其具体的实现方式不做限定。
第七，本申请实施例中涉及的“保存”，可以是指的保存在一个或者多个存储器中。所述一个或者多个存储器，可以是单独的设置，也可以是集成在编码器或者译码器，处理器、或通信装置中。所述一个或者多个存储器，也可以是一部分单独设置，一部分集成在译码器、处理器、或通信装置中。存储器的类型可以是任意形式的存储介质，本申请并不对此限定。
第八，本申请实施例中涉及的“协议”可以是指通信领域的标准协议，例如可以包括LTE协议、NR协议以及应用于未来的通信系统中的相关协议，本申请对此不做限定。
第九，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A，B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a、b和c中的至少一项(个)，可以表示：a，或b，或c，或a和b，或a和c，或b和c，或a、b和c，其中a，b，c可以是单个，也可以是多个。
下面将结合附图详细说明本申请提供的各个实施例。
应理解，本申请提供的通信方法可适用于无线通信系统，例如，图8中所示的无线通信系统100。本申请实施例中的终端设备可以同时与一个或多个网络设备通信，例如，本申请实施例中的网络设备可对应于图8中的收发点#1 102和收发点#2 103所属的网络设备(也就是说收发点#1 102和收发点#2 103所属的网络设备是同一个网络设备)，或者，本申请实施例中的网络设备可对应于图8中的收发点#1 102所属的网络设备或收发点#2 103所属的网络设备(也就是说收发点#1 102和收发点#2 103所属的网络设备是不同的网络设备)；本申请实施例中的终端设备可以对应于图8中的终端设备101。本实施例以网络设备对应于图8中的收发点#1 102和收发点#2 103所属的网络设备(也就是说收发点#1 102和收发点#2 103所属的网络设备是同一个网络设备)为例进行说明。
以下，不失一般性，以一个终端设备与一个网络设备之间的交互过程为例详细说明本申请实施例。或者，也可以理解为一个终端设备与一个网络设备中的服务小区进行交互，该终端设备可以为处于无线通信系统中与一个或多个服务小区具有无线连接关系的任意终端设备。或者，也可以理解为一个终端设备与一个服务小区中的多个收发点进行交互，该终端设备可以为处于无线通信系统中与一个或多个收发点具有无线连接关系的任意终 端设备。可以理解的是，处于该无线通信系统中的任意一个终端设备均可以基于相同的技术方案实现无线通信。本申请对此不做限定。
可以理解的，本申请实施例中，终端设备和/或网络设备，或者说，终端设备和/或收发点可以执行本申请实施例中的部分或全部步骤，这些步骤或操作仅是示例，本申请实施例还可以执行其它操作或者各种操作的变形。此外，各个步骤可以按照本申请实施例呈现的不同的顺序来执行，并且有可能并非要执行本申请实施例中的全部操作。
应理解，本申请实施例适用的协议栈架构可以如图4-图7所示，但不仅局限于图4-图7所示的协议栈架构，其他可以实现一个小区内多收发点(如多个TRP)传输的协议栈架构，也可以适用于本申请实施例。
图9是本申请实施例提供的一种通信方法200的示意性交互图。方法200包括：
S210，网络设备为小区#A进行配置。
其中，小区#A(即服务小区的一例)为支持多收发点(TRP)传输的小区，下文为简洁且不失一般性，将支持多收发点传输的小区记为小区#A。
小区#A内包括N个TRP，其中，N为大于或等于2的整数。网络设备为小区#A进行配置，可以理解为，网络设备为该小区#A中的N个TRP进行配置；或者，也可以理解为，网络设备分别为该小区#A中的每个TRP配置一套与下行控制信道相关的配置参数；或者，还可以理解为，网络设备分别为该小区#A中的每个TRP配置一套与下行控制信道相关的配置参数，并配置一套与上行控制信道相关的配置参数。应理解，每套配置参数包括的参数类型相同。下文结合具体配置参数说明。
作为示例而非限定，在本申请中，网络设备可以采用以下任意一种方式，为N个TRP进行配置：
方式1：将小区#A配置成包括N套与下行控制信道相关的配置参数的一个服务小区，该N套与下行控制信道相关的配置参数对应N个TRP，这种方式也可以称为单小区方式配置；
方式2：将小区#A配置成N个同频小区，每个同频小区包括一套与下行控制信道相关的配置参数，每个同频小区对应一个TRP，这种方式也可以称为多小区方式配置。其中，每个同频小区可以对应相同的频点信息和/或相同的小区标识信息。
其中，频点信息可以包括以下至少一项：同步信号块(synchronization signal block，SSB)绝对频率(absoluteFrequencySSB)、PointA绝对频率(absoluteFrequencyPointA)、频率带宽列表(frequencyBandList)、子载波间隔(subcarrier spacing，SCS)特定的载波列表(scs-SpecificCarrierList)等。
其中，小区标识信息可以包括以下至少一种：小区全球标识(cell global identifier，CGI)、物理小区标识(physical cell identifier，PCI)、服务小区索引(如ServCellIndex)、小区组标识(如Cell Group Id)。
关于上述方式1和方式2，以及配置参数，在后面实施例中具体介绍
S220，网络设备向终端设备发送小区#A的配置信息，相应地，终端设备接收网络设备发送的小区#A的配置信息。
其中，配置信息包括对应于该小区#A的N套与下行控制信道相关的配置参数。每套与下行控制信道相关的配置参数包括的参数类型相同，例如，配置参数包括PDCCH配置 时，每套与下行控制信道相关的配置参数中均包括PDCCH配置。
可选地，配置信息还可以包括对应于该小区#A的M套与上行控制信道相关的配置参数，其中，M为大于1或等于1的整数，且，M小于或等于N。
其中，M套与上行控制信道相关的配置参数和M套与下行控制信道相关的配置参数一一关联，分别用于进行上行信息反馈和下行信息接收。
一种可能的实现方式，以图4、图6、或图7所示的协议栈架构为例，M等于N，即配置信息中可以包括N套与上行控制信道相关的配置参数和N套与下行控制信道相关的配置参数，即每个TRP对应一套与上行控制信道相关的配置参数和一套与下行控制信道相关的配置参数。每个TRP基于对应的与下行控制信道相关的配置参数向终端设备发送下行信息，相应地，终端设备也可以基于对应的与上行控制信道相关的配置参数向相应的TRP发送上行信息。
又一种可能的实现方式，以图5所示的协议栈架构为例，M小于N，即配置信息中可以包括M套与上行控制信道相关的配置参数和N套与下行控制信道相关的配置参数，M套与上行控制信道相关的配置参数和N套与下行控制信道相关的配置参数中的M套配置参数对应。即N个TRP中，有M个TRP分别对应一套与上行控制信道相关的配置参数和一套与下行控制信道相关的配置参数，有(N-M)个TRP分别对应一套与下行控制信道相关的配置参数。例如，以图5所示的协议栈架构为例，即配置信息中可以包括一套与上行控制信道相关的配置参数和两套与下行控制信道相关的配置参数。即两个TRP中，有一个TRP(即图5中的TRP1)对应一套与上行控制信道相关的配置参数和一套与下行控制信道相关的配置参数，有一个TRP(即图5中的TRP2)对应一套与下行控制信道相关的配置参数，故终端设备采用与上行控制信道相关的配置参数，向TRP1发送对应TRP1的上行信息和对应TRP2的上行信息。
S230，终端设备基于小区#A的配置信息，与小区#A通信。
也可以理解为，终端设备基于N套与下行控制信道相关的配置参数，与小区#A通信；或者，也可以理解为，终端设备基于N套与下行控制信道相关的配置参数，与小区#A中的N个TRP通信。
终端设备与小区#A通信，可以理解为，终端设备从小区#A接收到来自多个TRP的信息，相应地，多个TRP可以分别向终端设备发送信息。例如，终端设备从该小区#A对应的时频资源上接收到来自该小区#A内的多个TRP的信息。多个TRP的发送的信息可以相同也可以不同。
可选地，配置参数包括以下至少一项：PDCCH配置(如PDCCH config)、小区标识信息、小区无线网络临时标识C-RNTI、解调参考信号DMRS、N个TRP对应的标识(如TRP ID)、波束集信息、或波束信息。
可选地，终端设备从小区#A接收DCI，或者说，终端设备从小区#A所属的网络设备接收DCI，该DCI对应的配置参数属于N套与下行控制信道相关的配置参数中的一套。其中，由于N套与下行控制信道相关的配置参数和N个TRP间存在关联关系，该关联关系是通过显式或隐式的方法表示的。
一种示例，N套与下行控制信道相关的配置参数和N个TRP或N个链路间的关联关系可以通过显式的方法表示。网络设备发送的包括对应于小区#A的N套与下行控制信道 相关的配置参数的配置信息中也可以分别包含每套配置参数关联的TRP或链路信息，那么，终端设备可以基于接收到的该DCI对应的配置参数，确定发送该DCI的TRP或链路是小区#A的N个TRP或N个链路中的哪个TRP或哪个链路。其中，该TRP信息可以是TRP标识(如TRP ID)，或者其他方法(如该TRP信息可以是用于区分、识别TRP的相关参数)，不做限定。该链路信息可以是链路标识(如link ID)，或者其他方法(如该链路信息可以是用于区分、识别链路的相关参数)，不做限定。
另一种示例，N套与下行控制信道相关的配置参数和N个TRP或N个链路间的关联关系可以通过隐示的方法表示。例如，协议约定网络设备发送的对应于小区#A的N套与下行控制信道相关的配置参数中，其中，第一套配置参数关联小区#A内的第一TRP或第一链路(如记作TRP1或链路1)，第二套配置参数关联小区#A内的第二TRP或第二链路(如记作TRP2或链路2)，如此类推，不做赘述。或者，也可以是其他约定准则，不做限定。那么，终端设备可以基于接收到的该DCI对应的配置参数，确定发送该DCI的TRP是小区#A的N个TRP中的哪个TRP或哪个链路。
或者，又一示例，N套与下行控制信道相关的配置参数和N个TRP或N个链路间的关联关系可以通过信元或信元结构表示。例如，网络设备发送的包括对应于小区#A的N套与下行控制信道相关的配置参数的配置信息中可以通过某一信元(或者说某一信元结构)来指示每套配置参数关联的TRP或链路信息，那么，终端设备可以基于接收到的该DCI对应的配置参数，确定发送该DCI的TRP或链路是小区#A的N个TRP或N个链路中的哪个TRP或哪个链路。例如，网络设备发送包括对应于小区#A的N套与下行控制信道相关的配置参数时，其中，第一套配置参数用信元first-config来指代，该信元first-config中包含对应第一套配置参数的相关参数，第一套配置参数对应第一TRP或者第一链路，第二套配置参数用信元second-config来指代，该信元second-config中包含对应第二套配置参数的相关参数，第二套配置参数对应第二TRP或者第二链路，如此类推，不做赘述。或者，信元(或该信元对应的配置参数)与TRP(或链路)间也可以是其他对应关系，本实施例仅是一种举例，实现时，网络设备可以任意实现。应理解，信元first-config、信元second-config仅是一种命名方式，不做限定。
通过本申请实施例，终端设备可以区分接收到的信息(如DCI)是来自哪个TRP的，或者说，可以将每个TRP与终端设备间的传输通道看成一个链路，通过本申请实施例，终端设备可以区分接收到的信息(如DCI)是来自哪个链路的。终端设备若要处理来自多个TRP的信息，则需要区分接收到的信息来自于哪个TRP。例如，对多个TRP对应的PDCCH进行区分以分别接收多个TRP发送的DCI，终端设备确定接收到的DCI分别对应的TRP是哪个。进一步的，终端设备可以根据接收到的DCI从相应的物理下行共享信道(physical downlink share channel，PDSCH)接收下行数据；或者，终端设备可以向确定出的TRP所对应的PUSCH发送上行数据；或者，终端设备可以在确定出的TRP对应的物理上行共享信道(physical uplink share channel，PUSCH)或者物理上行控制信道(physical uplink control channel，PUCCH)上进行上行功率控制等。区分PDCCH或者区分DCI对实现与指定TRP的波束失败恢复等操作也非常关键。因此，通过本申请实施例，可以通过多收发点传输实现数据传输速率提升。
下面结合六种可能的情况具体说明。
情况1：配置参数包括PDCCH配置。
其中，PDCCH配置：可用于配置PDCCH参数，例如，包括控制资源集(control resource set，CORESET)、搜索空间(search space)以及其他可用于盲检PDCCH的参数。PDCCH配置例如可以通过高层参数中的PDCCH配置控制元素(PDCCH-config information element，PDCCH-config IE)配置。
PDCCH配置还可用于确定检测PDCCH的搜索空间/时频资源。不同的PDCCH配置所确定的搜索空间(或者说时频资源)不同。每个PDCCH配置可以包括一个或多个控制资源集以及一个或多个搜索空间。每个控制资源集和每个搜索空间可以进一步通过高层参数来配置。例如，PDCCH-config中可以包含控制资源集控制元素(ControlResourceSet IE)和搜索空间控制元素(SearchSpace IE)，ControlResourceSet IE表示控制资源集相关参数，SearchSpace IE表示搜索空间相关参数。根据ControlResourceSet IE和/或SearchSpace IE，可以确定检测PDCCH的候选空间/时频资源。因此，基于一个PDCCH配置，终端设备可以确定出候选空间/时频资源，终端设备在配置的候选空间/时频资源进行PDCCH检测，检测到PDCCH后，解析该PDCCH，从而得到承载在该PDCCH上的DCI信息。
应理解，上述仅是为便于理解，以PDCCH-config中包含的ControlResourceSet IE和SearchSpace IE为例进行了示例性说明，本申请实施例并未限定于此。
配置信息包括对应于该小区#A的N套与下行控制信道相关的配置参数。在情况1中，配置信息包括N套PDCCH配置，N套PDCCH配置对应N个TRP，即每一套PDCCH配置对应一个TRP。或者说，N套PDCCH配置对应N个链路，即每一套PDCCH配置对应一个链路。
在情况1中，对于终端设备而言，接收到的DCI对应的PDCCH配置可以理解为接收该DCI时所基于的PDCCH配置，或者说，终端设备在由该PDCCH配置确定的空间/时频资源中进行PDCCH检测，检测到PDCCH后，解析该PDCCH，进而得到该DCI；对于网络设备而言，DCI对应的PDCCH配置可以理解为发送该DCI时所基于的PDCCH配置，或者说，网络设备将该DCI承载在该PDCCH配置所对应的信道或者空间/时频资源上。
一种示例，在情况1中，终端设备可以基于该DCI对应的PDCCH配置，确定发送该DCI的TRP或链路。
一种可能的实现方式，N个TRP的N个PDCCH位置以时分多址(time-division multiplexing，TDM)的方式配置在N个不同的时频资源块上，终端设备在哪个时频资源块上监测/接收到DCI，则可以结合第一对应关系确定发送该DCI的TRP或链路。
其中，第一对应关系表示N个PDCCH位置与N个不同的时频资源块之间的对应关系，该第一对应关系可以是网络设备发送给终端设备的，也可以是终端设备预先保存的，也可以是协议约定的，对此，本申请实施例不作限定。
例如，小区#A中包括两个TRP，为区分，分别记为TRP#1、TRP#2。TRP#1和TRP#2的PDCCH位置所在的时频资源块分别记为K1、K2。这样，终端设备就知道从K1接收到的是TRP#1发送的信息，从K2接收到的是TRP#2发送的信息。
又一种可能的实现方式，可以为每套配置参数(如PDCCH配置)关联一个标识(identify，ID)，该标识可以是索引值或者是TRP ID或者其他，不做限定。该标识可以由网络设备发送给终端设备或者协议规定。换句话说，N套配置参数(如N个PDCCH配 置)分别对应一个标识，收发点(如TRP)发送的DCI中可以包含该标识，终端设备可以根据接收到DCI中包含的该标识，结合第二对应关系确定发送该DCI的TRP或链路。
其中，第二对应关系表示N套配置参数(如N个PDCCH配置)与N个不同标识之间的对应关系，该第二对应关系可以是网络设备发送给终端设备的，也可以是终端设备预先保存的，或者协议规定的，对此，本申请实施例不作限定。
例如，小区#A中包括TRP#1、TRP#2。一种示例，TRP#1和TRP#2分别对应的PDCCH配置所关联的标识分别记为index1、index2。这样，终端设备就知道携带index1的信息为TRP#1发送的信息(例如，该信息是DCI)，携带index2的信息为TRP#2发送的信息(例如，该信息是DCI)。
或者，又一种示例，在情况1中，终端设备可以基于接收到的DCI所对应的控制资源集相关参数和/或搜索空间相关参数，确定发送该DCI的TRP或链路。
具体地，配置信息包括对应于该小区#A的N套与下行控制信道相关的配置参数。配置信息包括一套PDCCH配置，该一套PDCCH配置中包含分别对应N个链路(或者说N个TRP)的控制资源集相关参数和搜索空间相关参数，可选地，可以为每个链路(或者说每个TRP)的控制资源集相关参数关联一个标识，也可以为每个链路(或者说每个TRP)的搜索空间相关参数关联一个标识。例如，该一套PDCCH配置中包含N套第一参数，每一套第一参数(如，第一参数包括控制资源集相关参数和/或搜索空间相关参数)分别对应一个TRP(或者一个链路)。也就是说，N套第一参数中，其中任意两套第一参数包含的控制资源集相关参数和搜索空间相关参数中，至少有一个参数不相同，以此来区分不同的TRP(或者链路)。从而终端设备可以基于接收到的DCI所对应的控制资源集相关参数和/或搜索空间相关参数，确定发送该DCI的TRP或链路。
例如，以N＝2，终端设备与服务小区#A内的TRP#1和TRP#2进行通信为例，网络设备提供的配置信息中包括对应于该小区#A的两套与下行控制信道相关的配置参数。该配置信息包括一套PDCCH配置，该一套PDCCH配置中包含分别对应两个链路(或者说两个TRP)的控制资源集相关参数和搜索空间相关参数。假设对应TRP#1的控制资源集相关参数与对应TRP#2的控制资源集相关参数不相同，对应TRP#1的搜索空间相关参数与对应TRP#2的搜索空间相关参数相同；或者，假设对应TRP#1的控制资源集相关参数与对应TRP#2的控制资源集相关参数相同，对应TRP#1的搜索空间相关参数与对应TRP#2的搜索空间相关参数不相同；或者，假设对应TRP#1的控制资源集相关参数与对应TRP#2的控制资源集相关参数不相同，对应TRP#1的搜索空间相关参数与对应TRP#2的搜索空间相关参数不相同。终端设备接收到DCI后，可以结合第三对应关系确定发送该DCI的TRP或链路。
其中，第三对应关系表示N个控制资源集相关参数与N个不同标识(即N个控制资源集相关参数关联的标识)之间的对应关系，和/或，第三对应关系表示N个搜索空间相关参数与N个不同标识(即N个搜索空间相关参数关联的标识)之间的对应关系。该第三对应关系可以是网络设备发送给终端设备的，也可以是终端设备预先保存的，也可以是协议约定的，对此，本申请实施例不作限定。
具体的，其他的用于关联每一套第一参数与TRP(或者链路)的关系的实现方式可参照上述其他可能的实现方式，不再赘述。
对于上述任意一种可能的实现方式，终端设备确定接收到的DCI是来自哪个TRP或链路后，可以进一步进行对应的PDSCH、PUSCH或PUCCH处理。以TRP#1为例，终端设备确定接收到的DCI来自TRP#1后，可以根据该DCI指示PDSCH接收下行数据。或者，终端设备确定接收到的DCI来自TRP#1后，可以向TRP#1对应的PUSCH发送上行数据。或者，终端设备确定接收到的DCI来自TRP#1后，可以在TRP#1对应的上行PUSCH或PUCCH进行上行功率控制等。
TRP#1和TRP#2可能对应不同的HARQ实体，甚至不同的MAC和RLC实体。如果TRP#1和TRP#2对应不同的HARQ实体，则对从PDSCH接收到的下行数据，终端设备递交到对应的HARQ实体去处理。上行方向类似，对发送到TRP所对应的PUSCH的上行数据，终端设备需要从与TRP对应的HARQ实体获取数据。对波束失败检测(beam failure detection，BFD)也是类似，例如，终端设备根据从TRP#1(或者TRP#1所对应的时频资源块K1)接收到的解调参考信号(demodulation reference signal，DMRS)的质量来判断TRP#1是否发生了波束失败。
可选地，在情况1中，配置参数还可以包括其他信息，例如配置参数还可以包括以下至少一项：小区标识信息、小区无线网络临时标识、解调参考信号、TRP的标识、波束信息、或波束集信息等。终端设备确定发送DCI的TRP或链路时，可以基于上述第一对应关系、第二对应关系、或第三对应关系确定，或者，也可以基于其他配置信息与TRP之间的对应关系确定，对此，不作限定。
情况2：配置参数包括小区标识信息。
其中，该小区标识信息，可以是PCI，或者是CGI，或者是服务小区索引，或者是小区组标识，或者，也可以是小区索引标识(Cell Index Flag，CIF)等，对此，本申请实施例不作限定，任何可以通过标识区分不同TRP的方式都落入本申请实施例保护范围。所述小区标识信息可以包含在物理层消息(如DCI)或层2消息(如MAC CE)或RRC消息中(如RRC重配置消息)，不做限定。应理解，小区索引标识(CIF)只是一种可能的示例，也可以用其他名称代替，不作限定。下文以CIF为例进行示例性说明。
小区#A可以配置N个CIF，该N个CIF分别对应N个TRP或N个链路，每个TRP或每个链路对应的CIF可以不相同，CIF用于区分不同的TRP。CIF可以包含在DCI中，或者也可以包含在其他消息中，不作限定。下文以CIF包含在DCI中进行示例性说明。
配置信息包括对应于该小区#A的N套与下行控制信道相关的配置参数。在情况2中，配置信息包括N个CIF，N个CIF对应N个TRP或N个链路，即每一个CIF对应一个TRP或一个链路，每一个CIF分别包含在与之对应的TRP发送的DCI中。
在情况2中，对于终端设备而言，接收到的DCI对应的CIF可以理解为携带在该DCI中的CIF；对于网络设备而言，DCI对应的CIF可以理解为发送该DCI时，携带在该DCI中的CIF。
在情况2中，终端设备可以基于该DCI对应的CIF，确定发送该DCI的TRP或链路。
例如，终端设备可以根据DCI中包含的CIF，以及CIF与TRP或链路之间的第四对应关系，确定发送该DCI的TRP或链路。该第四对应关系可以是网络设备发送给终端设备的，也可以是终端设备预先保存的，也可以是协议规定的，对此，本申请实施例不作限定。
以支持小区#A内的TRP#1和TRP#2传输为例，在情况2中，TRP#1对应的PDCCH配置和TRP#2对应的PDCCH配置可以相同或不同，或者说，TRP#1对应的PDCCH位置和TRP#2对应的PDCCH位置可以相同或不同。例如，终端设备从小区#A的PDCCH时频位置检测到DCI后，根据DCI中携带的CIF来判断该DCI是来自哪个TRP或链路的。
此外，终端设备确定接收到的DCI是来自哪个TRP或链路后，可以进一步进行对应的PDSCH、PUSCH或PUCCH处理。具体地处理过程同上述情况1似，不再赘述。
可选地，在情况2中，配置参数还可以包括其他信息，例如配置参数还可以包括以下至少一项：PDCCH配置、小区无线网络临时标识、解调参考信号、TRP的标识、波束信息、或波束集信息等。终端设备确定发送DCI的TRP或链路时，可以基于上述第四对应关系确定，或者，也可以基于第一对应关系、第二对应关系、或第三对应关系确定，或者，也可以基于其他配置信息与TRP之间的对应关系确定，对此，不作限定。
情况3：配置参数包括小区无线网络临时标识(cell radio network temporary identifier，C-RNTI)。
小区#A可以配置N个不同的C-RNTI来作为扰码序列(scrambling sequence，SS)(或解扰序列(descrambling sequence))，该N个不同的C-RNTI分别对应N个TRP或N个链路。
配置信息包括对应于该小区#A的N套与下行控制信道相关的配置参数。在情况3中，配置信息包括N个C-RNTI，N个C-RNTI对应N个TRP或N个链路，即每一个C-RNTI对应一个TRP或一个链路。每个TRP或每个链路对应的C-RNTI可以不相同。
应理解，C-RNTI是扰码序列(或解扰序列)的一种可能的示例，任何可以通过扰码序列(或解扰序列)区分不同TRP的方式都落入本申请实施例保护范围。例如，情况3中，可以通过配置N个不同的其他种类或其他名称的扰码序列(或解扰序列)来分别对应N个TRP或N个链路，即配置信息包括N个扰码序列(或解扰序列)，该扰码序列(或解扰序列)包括但不局限于C-RNTI。下文以C-RNTI为例进行说明。
在情况3中，对于终端设备而言，接收到的DCI对应的C-RNTI可以理解为获得DCI使用的解扰序列；对于网络设备而言，DCI对应的C-RNTI可以理解为用于对DCI进行加扰的扰码序列。扰码序列一般与解扰序列相同，可以通常称为扰码序列。
在情况3中，终端设备可以基于该DCI对应的C-RNTI，确定发送该DCI的TRP或链路。
例如，终端设备可以根据得到DCI所使用的C-RNTI，以及C-RNTI与TRP或链路之间的第五对应关系，确定发送该DCI的TRP或链路。该第五对应关系可以是网络设备发送给终端设备的，也可以是终端设备预先保存的，也可以是协议规定的，对此，本申请实施例不作限定。
以支持小区#A内的TRP#1和TRP#2传输为例，在情况3中，TRP#1对应的PDCCH配置和TRP#2对应的PDCCH配置可以相同或不同，或者说，TRP#1对应的PDCCH位置和TRP#2对应的PDCCH位置可以相同或不同。例如，配置信息中包括2个SS，如该SS为C-RNTI，这2个C-RNTI分别对应TRP#1和TRP#2，终端设备在小区#A的PDCCH时频位置通过尝试两个不同的SS来检测DCI。检测到DCI后，根据获得该DCI使用的SS来判断该DCI是来自哪个TRP或链路的。
此外，终端设备确定接收到的DCI是来自哪个TRP或链路后，可以进一步进行对应的PDSCH、PUSCH或PUCCH处理。具体地处理过程同上述情况1似，不再赘述。
可选地，在情况3中，配置参数还可以包括其他信息，例如配置参数还可以包括以下至少一项：PDCCH配置、小区标识信息、解调参考信号、TRP的标识、波束信息、或波束集信息等。终端设备确定发送DCI的TRP或链路时，可以基于上述第一对应关系、第二对应关系、第三对应关系、第四对应关系、第五对应关系中的任意一种确定，或者，也可以基于其他配置信息与TRP之间的对应关系确定，对此，不作限定。
情况4：配置参数包括解调参考信号(demodulation reference signal，DMRS)。
其中，DMRS可以承载在物理共享信道中与数据信号一起发送，以用于对物理共享信道中承载的数据信号进行解调。如，在PDSCH中与下行数据一起发送，或者，在PUSCH中与上行数据一起发送。DMRS还可以承载在物理控制信道中与控制信令一起发送，以用于对物理控制信道汇总承载的控制信令进行解调。如，在PDCCH中与下行控制信令一起发送，或者，在PUCCH中与上行控制信令一起发送。
小区#A可以配置N个不同的DMRS，该N个不同的DMRS分别对应N个TRP或N个链路。
配置信息包括对应于该小区#A的N套与下行控制信道相关的配置参数。在情况4中，配置信息包括N个DMRS，N个DMRS对应N个TRP或N个链路，即每一个DMRS对应一个TRP或一个链路。
应理解，DMRS是解调参考信号的一种可能的示例，任何可以通过解调参考信号区分不同TRP的方式都落入本申请实施例保护范围。例如，情况4中，可以通过配置N个不同的其他种类或其他名称的解调参考信号来分别对应N个TRP或N个链路，对此不做限定。下文以DMRS为例进行说明。
在情况4中，对于终端设备而言，接收到的DCI对应的DMRS可以理解为从接收到的DCI所在的时频位置接收DMRS；对于网络设备而言，DCI对应的DMRS可以理解为在发送DCI所对应的空间/时频资源发送DMRS。
在情况4中，终端设备可以基于该DCI对应的DMRS，确定发送该DCI的TRP或链路。
例如，终端设备可以根据接收到的DMRS，以及DMRS与TRP或链路之间的第六对应关系，确定发送该DCI的TRP或链路。该第六对应关系可以是网络设备发送给终端设备的，也可以是终端设备预先保存的，也可以是协议规定的，对此，本申请实施例不作限定。
以支持小区#A内的TRP#1和TRP#2传输为例，在情况4中，TRP#1对应的PDCCH配置和TRP#2对应的PDCCH配置可以相同或不同，或者说，TRP#1对应的PDCCH位置和TRP#2对应的PDCCH位置可以相同或不同。例如，终端设备从小区#A的PDCCH时频位置检测到DCI后，根据接收到该DCI所在时频位置的DMRS信息(比如可以根据DMRS对应的信号质量是否大于预设门限来确定该DMRS信号是否有效)判断该DCI是来自哪个TRP或链路的。
此外，终端设备确定接收到的DCI是来自哪个TRP或链路后，可以进一步进行对应的PDSCH、PUSCH或PUCCH处理。具体地处理过程同上述情况1似，不再赘述。
可选地，在情况4中，配置参数还可以包括其他信息，例如配置参数还可以包括以下至少一项：PDCCH配置、小区标识信息、小区无线网络临时标识、TRP的标识、波束信息、或波束集信息等。终端设备确定发送DCI的TRP或链路时，可以基于上述第一对应关系、第二对应关系、第三对应关系、第四对应关系、第五对应关系、第六对应关系中的任意一种确定，或者，也可以基于其他配置信息与TRP之间的对应关系确定，对此，不作限定。
情况5：配置参数包括TRP的标识。
小区#A可以为N个TRP配置N个标识，该N个标识分别对应N个TRP，该标识用于识别TRP。
配置信息包括对应于该小区#A的N套与下行控制信道相关的配置参数。在情况5中，配置信息包括N个标识，N个标识对应N个TRP，即每一个标识对应一个TRP。例如，标识可以是TRP ID，对此不做限定。下文以TRP ID为例进行说明。
在情况5中，对于终端设备而言，接收到的DCI对应的标识可以理解为接收该DCI时所基于的PDCCH配置所关联的TRP标识；对于网络设备而言，DCI对应的标识可以理解为网络设备在配置PDCCH配置时配置的TRP标识，所述配置的该TRP标识与所述PDCCH配置相关联。
在情况5中，终端设备可以基于该DCI对应的TRP标识，确定发送该DCI的TRP或链路。
例如，终端设备可以根据TRP标识，以及TRP标识与TRP或链路之间的第七对应关系，确定发送该DCI的TRP或链路。该第七对应关系可以是网络设备发送给终端设备的，也可以是终端设备预先保存的，也可以是协议规定的，对此，本申请实施例不作限定。
以支持小区#A内的TRP#1和TRP#2传输为例，在情况5中，TRP#1对应的PDCCH配置和TRP#2对应的PDCCH配置可以相同或不同，或者说，TRP#1对应的PDCCH位置和TRP#2对应的PDCCH位置可以相同或不同。例如，终端设备从小区#A的PDCCH时频位置检测到DCI后，根据接收该DCI时所基于的PDCCH配置所关联的TRP标识来判断该DCI是来自哪个TRP或链路的。
此外，终端设备确定接收到的DCI是来自哪个TRP或链路后，可以进一步进行对应的PDSCH、PUSCH或PUCCH处理。具体地处理过程同上述情况1似，不再赘述。
可选地，在情况5中，配置参数还可以包括其他信息，例如配置参数还可以包括以下至少一项：PDCCH配置、小区标识信息、小区无线网络临时标识、解调参考信号、波束信息、或波束集信息等。终端设备确定发送DCI的TRP或链路时，可以基于上述第一对应关系、第二对应关系、第三对应关系、第四对应关系、第五对应关系、第六对应关系、第七对应关系中的任意一种确定，或者，也可以基于其他配置信息与TRP之间的对应关系确定，对此，不作限定。
情况6：配置参数包括波束信息或波束集信息。
其中，波束在NR协议中的体现可以是空域滤波器(spatial filter)，或者称空间滤波器或空间参数(spatial parameters)。用于发送信号的波束可以称为发射波束(transmission beam，Tx beam)，也可以称为空间发送滤波器(spatial domain transmit filter)或空间发射参数(spatial domain transmit parameter)；用于接收信号的波束可以称为接收波束 (reception beam，Rx beam)，也可以称为空间接收滤波器(spatial domain receive filter)或空间接收参数(spatial domain receive parameter)。
小区#A可以配置N个波束(beam)(或N个波束集)，该N个波束分别对应N个TRP，该波束可以用波束标识(如SSB index或CSI-RS index)来表示；或者，该N个波束集分别对应N个TRP，其中，波束集可以用波束集标识(如beam set index)来表示，不同的波束集中包含的波束个数可以相同或不同，不同的波束集中包含的波束不相同。例如，波束集1中可以包含beam1-4，波束集2中可以包含beam5-8，对此不做限定。
配置信息包括对应于该小区#A的N套与下行控制信道相关的配置参数。在情况6中，配置参数包括波束信息或波束集信息，该波束信息可以包括波束标识，该波束集信息可以包括波束标识和/或波束集标识，不做限定。配置信息包括N个波束(或N个波束集)，N个波束(或N个波束集)对应N个TRP或N个链路，即每一个波束(或每一个波束集)分别对应一个TRP。
在情况6中，对于终端设备而言，接收到的DCI对应的波束(或波束集)可以理解为用于接收该DCI的波束(或接收该DCI的波束所属的波束集)；对于网络设备而言，DCI对应的波束(或波束集)可以理解为发送该DCI的波束(或发送该DCI的波束所属的波束集)。
在情况6中，终端设备可以基于该DCI对应的波束(或波束集)，确定发送该DCI的TRP或链路。
例如，终端设备可以根据接收到DCI的波束(或接收到该DCI的波束所属的波束集)，以及波束(或波束集)与TRP或链路之间的第七对应关系，确定发送该DCI的TRP或链路。该第七对应关系可以是网络设备发送给终端设备的，也可以是终端设备预先保存的，也可以是协议规定的，对此，本申请实施例不作限定。
以支持小区#A内的TRP#1和TRP#2传输为例，在情况6中，TRP#1对应的PDCCH配置和TRP#2对应的PDCCH配置可以相同或不同，或者说，TRP#1对应的PDCCH位置和TRP#2对应的PDCCH位置可以相同或不同。例如，终端设备从小区#A的不同波束(或波束集)检测PDCCH并获得DCI后，根据获得该DCI的波束(或获得该DCI的波束所属的波束集)判断该DCI是来自哪个TRP或链路的。
一种示例，配置信息包括2个波束集，如可以分别记为波束集1和波束集2，波束集1中包含beam1-4，该波束集1对应TRP#1；波束集2中包含beam5-8，该波束集2对应TRP#2。如果终端设备从beam2接收到DCI，则终端设备确定接收到的该DCI是TRP#1发送的，或者，终端设备确定接收到的该DCI是终端设备与TRP#1间的链路发送的。
另一种示例，配置信息包括2个波束，如可以分别记为波束1和波束2，波束1对应TRP#1，波束2对应TRP#2。如果终端设备从波束1接收到DCI，则终端设备确定接收到的该DCI是TRP#1发送的，或者，终端设备确定接收到的该DCI是终端设备与TRP#1间的链路发送的。
此外，终端设备确定接收到的DCI是来自哪个TRP或链路后，可以进一步进行对应的PDSCH、PUSCH或PUCCH处理。具体地处理过程同上述情况1似，不再赘述。
可选地，在情况6中，配置参数还可以包括其他信息，例如配置参数还可以包括以下至少一项：PDCCH配置、小区标识信息、小区无线网络临时标识、解调参考信号、TRP 的标识等。终端设备确定发送DCI的TRP或链路时，可以基于上述第一对应关系、第二对应关系、第三对应关系、第四对应关系、第五对应关系、第六对应关系、第七对应关系中的任意一种确定，或者，也可以基于其他配置信息与TRP之间的对应关系确定，对此，不作限定。
基于上述六种情况，终端设备可以根据以下至少一项：PDCCH配置、小区标识信息、C-RNTI、DMRS、TRP标识、波束信息、或波束集信息，来区分接收到的信息是来自哪个TRP或者是来自哪个链路的，以便进一步进行对应的PDSCH、PUSCH或PUCCH处理，通过一个小区内的多收发点传输实现传输速率的提升。
应理解，上述示例性地介绍了六种可能的情况，本申请实施例并未限定于此。例如，上述六种情况可以单独使用，也可以结合使用。
下面详细介绍上述方式1和方式2。
方式1：单小区方式配置。
以配置参数为PDCCH配置为例，网络设备可以将小区#A配置成包括N套PDCCH配置的一个服务小区，每一套PDCCH配置分别对应一个TRP。
RRC消息采用多级信元结构，即一个信元可能包括一个或多个下一级信元，例如，小区组配置(CellGroupConfig)→特殊小区配置/辅小区配置(SpCellConfig/SCellConfig)→服务小区配置(ServingCellConfig)→带宽部分专用参数(BWP-DownlinkDedicated)→PDCCH-Config。因此，可以在ServingCellConfig信元或者BWP-DownlinkDedicated信元内，包括N个PDCCH-Config信元。下面以小区#A包括两个TRP为例具体说明，为区分，分别记为TRP#1、TRP#2。
一种可能的实现方式，在BWP-DownlinkDedicated信元内包括两个PDCCH-Config信元，为区分，分别记为PDCCH-Config1、PDCCH-Config2。换句话说，对小区#A提供一套ServingCellConfig，即给终端设备配置一套ServingCellConfig，且该套ServingCellConfig中包括两套PDCCH-Config。
其中，该套ServingCellConfig中包含的信息除了PDCCH配置外，其他信息可以同时对应TRP#1和TRP#2。例如，TRP#1和TRP#2对应的小区索引(如ServCellIndex)、上行配置(如UplinkConfig)等可以相同，或者也可以不相同，对此不做限定。
其中，该套ServingCellConfig中的PDCCH-Config1、PDCCH-Config2分别对应TRP#1和TRP#2，换句话说，TRP#1和TRP#2对应的PDCCH-Config不同。例如，TRP#1和TRP#2对应的DCI搜索空间或时频资源不同。
BWP-DownlinkDedicated信元内配置的PDCCH-Config1和PDCCH-Config2分别对应TRP#1和TRP#2(例如，PDCCH-Config1对应TRP#1，PDCCH-Config2对应TRP#2，或者，PDCCH-Config2对应TRP#1，PDCCH-Config1对应TRP#2)。TRP#1和TRP#2可以分别基于各自的PDCCH-Config与终端设备进行数据传输。此外，通过BWP-DownlinkDedicated信元内配置有PDCCH-Config2信元，或者，通过BWP-DownlinkDedicated信元内配置有PDCCH-Config1信元和PDCCH-Config2信元，也可以指示终端设备此时的传输场景为一个服务小区内的两个收发点传输(TRP#1和TRP#2为服务小区内的两个收发点)。相应地，终端设备接收到包括PDCCH-Config2的服务小区配置后可获知网络设备对该服务小区配置了多收发点传输。
在本申请实施例中，多收发点传输用于表示一个小区中的多个TRP与终端设备通信。下文为简洁，不再赘述。
或者，另一种可能的实现方式，在BWP-DownlinkDedicated信元内包括一个PDCCH-Config信元，但是该PDCCH-Config中包含分别对应N个TRP(或者N个链路)的N套第一参数(第一参数如上所述，不再赘述)。换句话说，对小区#A提供一套PDCCH-Config，即给终端设备配置一套PDCCH-Config，且该套PDCCH-Config中包括N套第一参数，第一参数包括第一控制资源集相关参数(如ControlResourceSet)和第一搜索空间相关参数(如SearchSpace)。
下面以N＝2，小区#A包括两个TRP为例具体说明，为区分，分别记为TRP#1、TRP#2。
在BWP-DownlinkDedicated信元内包括一个PDCCH-Config信元，该PDCCH-Config中包含分别对应2个TRP(或者2个链路)的2套第一参数，第一参数包括第一控制资源集相关参数(如ControlResourceSet)和第一搜索空间相关参数(如SearchSpace)，为区分，分别记为ControlResourceSet1、SearchSpace1、ControlResourceSet2、SearchSpace2。
其中，该套PDCCH-Config中的ControlResourceSet1、SearchSpace1对应TRP#1，ControlResourceSet2、SearchSpace2对应TRP#2，换句话说，TRP#1、TRP#2对应一套PDCCH-Config，TRP#1和TRP#2分别对应的PDCCH的候选空间(时频资源)是不同的。例如，TRP#1和TRP#2分别对应的DCI搜索空间和/或时频资源不同。
TRP#1和TRP#2可以分别基于各自的PDCCH的候选空间(时频资源)与终端设备进行数据传输。此外，通过一套PDCCH-Config内配置有两套ControlResourceSet和两套SearchSpace，也可以指示终端设备此时的传输场景为一个服务小区内的两个收发点传输(TRP#1和TRP#2为服务小区内的两个收发点)。相应地，终端设备接收到包括两套ControlResourceSet和两套SearchSpace的PDCCH-Config后可获知网络设备对该服务小区配置了多收发点传输。
又一种可能的实现方式，在ServingCellConfig信元内包括两个BWP-DownlinkDedicated信元，为区分，分别记为BWP-DownlinkDedicated1、BWP-DownlinkDedicated2。换句话说，对小区#A提供一套ServingCellConfig，即给终端设备配置一套ServingCellConfig，且该套ServingCellConfig中包括两套BWP-DownlinkDedicated。每套BWP-DownlinkDedicated中包括一套PDCCH-Config，为区分，分别记为PDCCH-Config1、PDCCH-Config2。
其中，该套ServingCellConfig中包含的信息除了PDCCH配置外，其他信息可以同时对应TRP#1和TRP#2。例如，TRP#1和TRP#2对应的小区索引(如ServCellIndex)可以相同或者不同、上行配置(如UplinkConfig)可以相同或不同，对此不做限定。
其中，该套ServingCellConfig中的BWP-DownlinkDedicated1、BWP-DownlinkDedicated2分别对应TRP#1和TRP#2，即，BWP-DownlinkDedicated1中的PDCCH-Config1、BWP-DownlinkDedicated2中的PDCCH-Config2分别对应TRP#1和TRP#2。换句话说，TRP#1和TRP#2对应的PDCCH-Config不同。例如，TRP#1和TRP#2对应的DCI搜索空间或时频资源不同。
ServingCellConfig信元内配置的BWP-DownlinkDedicated1、BWP-DownlinkDedicated2分别对应TRP#1和TRP#2，即PDCCH-Config1和PDCCH-Config2分别对应TRP#1和 TRP#2。例如，BWP-DownlinkDedicated1或PDCCH-Config1对应TRP#1，BWP-DownlinkDedicated2或PDCCH-Config2对应TRP#2；又如，BWP-DownlinkDedicated2或PDCCH-Config2对应TRP#1，BWP-DownlinkDedicated1或PDCCH-Config1对应TRP#2，对此不做限定。TRP#1和TRP#2可以分别基于各自的PDCCH-Config与终端设备进行数据传输。此外，通过ServingCellConfig信元内配置有BWP-DownlinkDedicated 2，或者，通过ServingCellConfig信元内配置有两个BWP-DownlinkDedicated信元(如BWP-DownlinkDedicated1和BWP-DownlinkDedicated 2)，可以指示终端设备此时的传输场景为一个服务小区内的两个收发点传输(TRP#1和TRP#2为服务小区内的两个收发点)。相应地，终端设备接收到包括BWP-DownlinkDedicated 2的服务小区配置后可获知网络设备对该服务小区配置了多收发点传输。
需要说明的是，上述仅结合RRC消息、以及RRC消息采用的一种多级信元结构进行了示例性说明，本申请并未限定于此，任何可以将小区#A配置成包括N套PDCCH配置的一个服务小区的方式都落入本申请实施例的保护范围。例如，RRC消息采用其它形式的多级信元结构时，也可以基于类似于上述的方式将小区#A配置成包括N套PDCCH配置的一个服务小区。
应理解，上述各个信元的命名不应对本申请构成任何限定。本申请并不排除在未来的协议中定义其他名称来表示相同或相似含义的可能。
基于上述方式1，通过为支持多收发点传输的服务小区配置多个PDCCH配置来进行多收发点传输配置，可以避免冗余信息，既尽量重用了现有信令，又节省了信令开销。
方式2：多小区方式配置。
将小区#A配置成N个同频小区，每个同频小区包括一套与下行控制信道相关的配置参数，每个同频小区对应一个TRP。下面以将小区#A配置成两个同频serving cell，这两个serving cell分别对应TRP#1、TRP#2为例进行说明。为区分，将这两个同频serving cell记为小区#A1、小区#A2。
RRC消息采用多级信元结构，仍以下面这种多级信元结构为例进行示例性说明：CellGroupConfig→SpCellConfig/SCellConfig→ServingCellConfig→BWP-DownlinkDedicated→PDCCH-Config。
一种可能的实现方式，可以为终端设备配置两个小区组(cell group，CG)，换句话说，可以配置两套CellGroupConfig，该两套CellGroupConfig为分别对应小区#A1、小区#A2的配置。换句话说，该两套CellGroupConfig分别对应TRP#1、TRP#2。例如，针对如上述图4所示的类双连接架构，可以采用该实现方式。该实现方式还可以适用于如图4-图7所示的任意一种架构，对此不做限定。
其中，每套CellGroupConfig中包括一套PDCCH-Config(该PDCCH-Config可以包含在CellGroupConfig的下级信元中)，为区分，分别记为PDCCH-Config1、PDCCH-Config2。PDCCH-Config1、PDCCH-Config2分别对应TRP#1和TRP#2，换句话说，TRP#1和TRP#2对应的PDCCH-Config不同。例如，TRP#1和TRP#2对应的DCI搜索空间或时频资源不同。
网络设备向终端设备发送配置消息，该配置消息中包括两套配置参数，该两套配置参数可以为两套CellGroupConfig，或者，该两套配置参数可以为两套PDCCH-Config。
又一种可能的实现方式，为小区#A提供两个服务小区的配置，换句话说，小区#A提供两套ServingCellConfig，即一个小区组配置(CellGroupConfig)中包括两套ServingCellConfig，为区分，分别记为ServingCellConfig1、ServingCellConfig2。ServingCellConfig1、ServingCellConfig2分别为对应小区#A1、小区#A2的配置。换句话说，该ServingCellConfig1、ServingCellConfig2分别对应TRP#1和TRP#2。例如，针对上述如图5和图7所示的类单小区架构，以及如图6所示的类载波聚合架构，可以采用该实现方式。该实现方式还可以适用于如图4所示的类多连接架构，对此不做限定。
其中，该两套ServingCellConfig对应的小区索引(如ServCellIndex)可以相同或不同、上行配置(如UplinkConfig)可以相同或不同，即，TRP#1和TRP#2对应的小区索引、上行配置等可以相同或不同。
其中，每套ServingCellConfig中包括一套PDCCH-Config，为区分，分别记为PDCCH-Config1、PDCCH-Config2。PDCCH-Config1、PDCCH-Config2分别对应TRP#1和TRP#2，换句话说，TRP#1和TRP#2对应的PDCCH-Config不同。例如，TRP#1和TRP#2对应的DCI搜索空间或时频资源不同。
网络设备向终端设备发送配置消息，该配置消息中包括两套配置参数，该两套配置参数可以为两套ServingCellConfig，或者，该两套配置参数可以为两套ServingCellConfig，或者，该两套配置参数可以为两套PDCCH-Config。
该实现方式中，在SpCellConfig信元内包括两个ServingCellConfig信元，为区分，分别记为ServingCellConfig1、ServingCellConfig2。换句话说，对小区#A提供一套SpCellConfig，且该套SpCellConfig中包括两套ServingCellConfig，每套ServingCellConfig中包括一套PDCCH-Config。TRP#1和TRP#2可以分别基于各自的PDCCH-Config与终端设备进行数据传输。
需要说明的是，上述仅结合RRC消息、以及RRC消息采用的一种多级信元结构进行了示例性说明，本申请并未限定于此，任何可以将小区#A配置成N个同频serving cell的方式都落入本申请实施例的保护范围。例如，RRC消息采用其它形式的多级信元结构时，也可以基于类似于上述的方式将小区#A配置成N个同频serving cell。
应理解，上述各个信元的命名不应对本申请构成任何限定。本申请并不排除在未来的协议中定义其他名称来表示相同或相似含义的可能。
基于上述方式2，通过将支持多收发点传输的服务小区配置成两个同频serving cell的方法，使得可以尽可能地重用已有的DC或CA配置流程或信令，简化协议设计。
考虑到终端设备与N个TRP通信的协议架构有多种，本申请实施例还提供了可以使得终端设备确定协议架构类型的几种方式。此外，终端设备也可以根据确定的协议架构类型与TRP进行通信。下面详细说明。
可选地，终端设备获取指示信息，指示信息用于指示终端设备与N个TRP通信的协议架构类型，为区分，将该指示信息记为指示信息#1。其中，协议架构类型包括以下至少一项：类多连接架构、类载波聚合架构、或类单小区架构。
其中，类多连接架构可以为如图4所示的架构，类载波聚合架构即为如图6所示的架构，类单小区架构包括如图5所示的第一类单小区架构和如图7所示的第二类单小区架构。另一种实现方式中，指示信息#1所指示的协议架构类型包括以下至少一项：类多连接架 构、类载波聚合架构、第一类单小区架构、第二类单小区架构。
具体的，与N个TRP通信的协议架构类型，可以是协议预先定义或规定的一种或多种；或者，与N个TRP通信的协议架构类型，也可以是网络设备通知给终端设备的，对此，本申请实施例不作限定。
一种可能的实现方式，协议预先定义或协议规定使用的一种协议架构类型。
例如，协议预先定义/规定使用类多连接架构；又如，协议预先定义/规定使用类载波聚合架构；又如，协议预先定义/规定使用第一类单小区架构；又如，协议预先定义/规定使用第二类单小区架构。此时，终端设备获取指示信息#1，可以理解为，终端设备根据协议预先定义或协议规定，确定与同一个服务小区内的N个TRP通信的协议架构类型。
又一种可能的实现方式，协议预先定义或协议规定使用的多种协议架构类型。
例如，协议预先定义/规定使用以下至少两种协议架构类型：类多连接架构、类载波聚合架构、第一类单小区架构、第二类单小区架构。此时，终端设备获取指示信息#1，可以理解为，终端设备根据协议预先定义或协议规定，确定与同一个服务小区内的N个TRP通信的协议架构类型。
又一种可能的实现方式，网络设备向终端设备发送指示信息#1，相应地，终端设备接收指示信息#1，终端设备根据接收到的指示信息#1确定协议架构类型。
其中，指示信息#1可以通过专门信元的方式显式指示，或者，指示信息#1也可以通过现有信元的特定取值和/或特定配置方式(比如一个信元被配置了多份)等隐式指示。例如，可以在信元ServingCellConfig中通过专门信元multiTrpTransType来显式指示协议架构类型。又如，对于某一信元，当被配置Y份时(Y为大于1或等于1的整数)，终端设备可以确定该协议架构类型为某一种架构(如，类多连接架构或类载波聚合架构或第一类单小区架构或第二类单小区架构)。又如，对于某一信元，当被配置一份时，终端设备可以确定该协议架构类型为其中一种架构(如类多连接架构)；当被配置了两份时，终端设备可以确定协议架构类型为另一种(如类载波聚合架构)等等，其中，某一信元被配置X份(X为大于1或等于1的整数)以及对应的架构类型，可以预先规定，不作限定。应理解，其中，该信元的命名仅是为便于理解作的示例性说明，不应对本申请构成任何限定，该信元可以有其他名称或表达形式。
例如，网络设备向终端设备发送指示信息#1，该指示信息#1用于指示协议架构类型为类多连接架构，如信元multiTrpTransType中包括用于表示类多连接架构的信息；或者，该指示信息#1用于指示协议架构类型为类载波聚合架构，如信元multiTrpTransType中包括用于表示类载波聚合架构的信息；或者，该指示信息#1用于指示协议架构类型为第一类单小区架构，如信元multiTrpTransType中包括用于表示第一类单小区架构的信息；或者，该指示信息#1用于指示协议架构类型为第二类单小区架构，如信元multiTrpTransType中包括用于表示第二类单小区架构的信息。
又如，网络设备向终端设备发送指示信息#1，该指示信息#1用于指示协议架构类型为以下至少两种：类多连接架构、类载波聚合架构、第一类单小区架构、或第二类单小区架构，如信元multiTrpTransType中包括用于表示以下至少两种协议架构类型的信息：类多连接架构、类载波聚合架构、第一类单小区架构、或第二类单小区架构。例如，信元multiTrpTransType中包括用于表示类多连接架构和第二类单小区架构的信息，则终端设备 可以确定协议架构类型为类多连接架构和第二类单小区架构。
需要说明的是，在本申请实施例中，确定协议架构类型，也可以称为确定多收发点传输类型，或者，也可以称为多收发点传输采用的协议架构类型，其命名仅是为便于理解作的示例性说明，不应对本申请构成任何限定。下文均用确定协议架构类型表示。
应理解，上述几种可能的实现方式仅是示例性说明，本申请并未限定于此，任何可以使得终端设备确定协议架构类型的方式都落入本本申请实施例的保护范围。
上面介绍了终端设备确定协议架构类型的几种方式，在本申请实施例中，终端设备也可以根据确定的协议架构类型进行相应的协议栈配置。下面详细说明。
可选地，终端设备可以根据确定的协议架构类型，进行相应的协议栈配置。下面结合上述如图4至图7所示的架构，分别进行说明。
一种可能的实现方式，终端设备确定协议架构类型为类多连接架构。
当协议架构类型为类多连接架构时，针对配置可以使用小区#A的一个无线承载RB，为N个TRP(或N个链路)共同生成一个PDCP实体，且分别为每个TRP(或每个链路)生成一个RLC实体、一个MAC实体、以及一个HARQ实体。其中，为N个TRP(或N个链路)共同生成一个PDCP实体，也就是说，N个TRP(或N个链路)共用一个PDCP实体；分别为每个TRP(或每个链路)生成一个RLC实体、一个MAC实体、以及一个HARQ实体，也就是说，N个TRP(或N个链路)与N个RLC实体对应、N个TRP(或N个链路)与N个MAC实体对应、N个TRP(或N个链路)与N个HARQ实体对应。具体地，参考如图4所示的架构。
可选的，对于一个无线承载RB而言，可以是某种业务的数据无线承载，也可以是某种业务的信令无线承载，例如，针对紧急业务，如超可靠低延迟通信(ultra-reliable and low latency communication，URLLC)业务，对该紧急业务的数据无线承载/信令无线承载进行上述处理；或者，也可以是指定的数据无线承载/信令无线承载，对此，本申请实施例不作限定。下文不再赘述。
此外，对于某一RB，网络设备在对该RB建立逻辑信道时，可以配置该RB对应的逻辑信道能够在哪些小区(或哪些小区的资源)上发送。本申请实施例中提及的配置可以使用小区#A(即服务小区)的无线承载RB，即网络设备将小区#A配置成能发某一RB(如对应URLLC业务的某RB)的小区，也就是说，该RB就是网络设备配置的可以使用小区#A的RB。
其中，一个PDCP实体与N个RLC实体对应进行数据传递。N个RLC实体与N个MAC实体一一对应进行数据传递。N个MAC实体与N个HARQ实体一一对应进行数据传递。当存在多个服务小区时，MAC实体可能对应多个HARQ实体，每一个HARQ实体对应一个服务小区。
又一种可能的实现方式，终端设备确定协议架构类型为类载波聚合架构。
当协议架构类型为类载波聚合架构时，针对配置可以使用小区#A的一个RB，为N个TRP(或N个链路)共同生成一个PDCP实体、一个RLC实体、以及一个MAC实体，且分别为每个TRP(或每个链路)生成一个HARQ实体。具体地，参考如图6所示的架构。
其中，一个PDCP实体与一个RLC实体对应进行数据传递，一个RLC实体与一个 MAC实体对应进行数据传递。一个MAC实体与N个HARQ实体对应进行数据传递。
又一种可能的实现方式，终端设备确定协议架构类型为第一类单小区架构。
当协议架构类型为第一类单小区架构时，针对配置可以使用小区#A的一个RB，为N个TRP(或N个链路)共同生成一个PDCP实体、一个RLC实体、一个MAC实体、以及一个HARQ实体。
其中，一个PDCP实体与一个RLC实体对应进行数据传递，一个RLC实体与一个MAC实体对应进行数据传递。一个MAC实体与一个HARQ实体对应进行数据传递。
又一种可能的实现方式，终端设备确定协议架构类型为第二类单小区架构。
当协议架构类型为第二类单小区架构时，针对配置可以使用小区#A的一个RB，为N个TRP(或N个链路)共同生成一个PDCP实体、一个RLC实体、一个MAC实体、以及一个HARQ实体。
其中，一个PDCP实体与一个RLC实体对应进行数据传递，一个RLC实体与一个MAC实体对应进行数据传递。一个MAC实体与一个HARQ实体对应进行数据传递。
上述介绍了终端设备可以根据指示信息#1确定协议架构类型。在本申请实施例中，终端设备也可以基于上述确定的协议架构类型确定小区#A配置了多收发点传输。下面详细介绍本申请实施例提出的终端设备确定小区#A是否配置了多收发点传输的几种方法。
可选地，终端设备可以通过以下任意一种方法，确定小区#A是否配置了多收发点传输，或者，确定该N套配置参数针对的是否为多收发点传输。
方法A：终端设备可以根据指示信息#1确定小区#A配置了多收发点传输。
终端设备获取到用于指示与N个TRP通信的协议架构类型的指示信息#1后，可以根据该指示信息#1确定协议架构类型，也可以根据该指示信息#1确定小区#A配置了多收发点传输，或者，确定配置消息或者该N套配置参数针对的是多收发点传输。用于指示与N个TRP通信的协议架构类型的指示信息#1，如前所述，不再赘述。
方法B：网络设备也可以向终端设备发送用于指示小区#A配置了多收发点传输的指示信息。为区分，记为指示信息#2。
方法C：终端设备也可以根据小区#A的配置信息确定小区#A配置了多收发点传输。
下面结合上述如图4至图7所示的架构，详细介绍上述方法B和方法C。
针对如图4所示的类多连接架构。
相比于传统DC架构(传统DC中，针对一个RB的两个MAC或两个RLC实体是分别对应两个接入网设备的(如对应MN和SN))，图4所示的该架构可以看作是DC架构的一种变形，由于该架构下，针对一个RB的两个MAC或两个RLC实体是分别对应同一个服务小区内的两个TRP或两个链路的，为区分，将该变形记为小区内的DC(intra-cell DC)，将传统DC架构记为普通DC。应理解，上述命名不应对本申请构成任何限定。针对类多连接架构，可以重用普通DC的相关流程进行intra-cell DC的配置，即重用普通DC的相关流程进行同一个服务小区内多收发点传输的配置。
针对类多连接架构，可以指示终端设备该配置为intra-cell DC，或者，可以指示该配置针对的是多收发点传输，从而使得终端设备能够区分此时的配置为intra-cell DC。其中，该指示可以是显示指示(如上述方法B)，也可以是隐示指示(如上述方法C)。下面分别说明。
一种可能的实现方式，通过上述方法B显示指示终端设备配置的是intra-cell DC，即网络设备可以向终端设备发送指示信息#2，用于指示配置的是intra-cell DC。该指示信息#2可以包括在网络设备发送给终端设备的配置消息，例如RRC建立(RRCSetup)、RRC恢复(RRCResume)、RRC重建立(RRCReestablishment)或RRC重配置(RRCReconfiguration)等消息中。
例如，该指示信息#2为可以是二进制数值，如“0”表示配置的不是intra-cell DC，即是普通DC，“1”表示配置的是intra-cell DC。
又如，该指示信息#2为可以是布尔值，如“False”表示配置的不是intra-cell DC，即是普通DC，“True”表示配置的是intra-cell DC。
又如，该指示信息#2为信元的形式，换句话说，可以通过在配置消息中是否有某一信元的方式来指示配置的是否为intra-cell DC。如，配置消息中包括了某信元，表示配置的是intra-cell DC，配置消息中没有包括该信元，表示配置的不是intra-cell DC，即是普通DC。其中，该信元例如可以是multiTrpTrans。应理解，其中，该信元的命名仅是为便于理解作的示例性说明，不应对本申请构成任何限定，该信元可以有其他名称或表达形式。
又一种可能的实现方式，通过上述方法C隐示指示终端设备配置的是intra-cell DC，即通过网络设备向终端设备发送的配置消息中所包括的N套配置参数，例如N套CellGroupConfig，所对应的频点信息相同，确定该配置为intra-cell DC，或者，确定该配置针对的是多收发点传输，或者，确定该配置对应小区#A内的N个不同TRP或链路。
其中，频点信息可以包括以下至少一项：absoluteFrequencySSB、absoluteFrequencyPointA、frequencyBandList、scs-SpecificCarrierList等。
针对如图5所示的第一类单小区架构。
相比于传统CA架构(以传统2CC CA为例，传统2CC CA架构下，两个HARQ实体是分别对应两个CC/小区的)，图5所示的该架构可以看作是CA架构的一种变形，此架构下，N个TRP共享一个HARQ entity。为区分，将该变形记为小区内的CA(intra-cell CA)，将传统CA架构记为普通CA。理解，上述命名不应对本申请构成任何限定。针对第一类单小区架构，可以重用普通CA的相关流程进行intra-cell CA的配置，即重用普通CA的相关流程进行同一个服务小区内多收发点传输的配置。相比于普通CA，对intra-cell CA的配置只有一个HARQ配置或两个完全一样的HARQ配置。
如前所述，针对第一类单小区架构，N套配置参数中，例如N套CellGroupConfig中或N套ServingCellConfig中，有M套PUCCH配置，M小于N。例如，以图5所示的TRP#1和TRP#2为例，TRP#1和TRP#2仅对应一套PUCCH配置。
针对第一类单小区架构，可以指示终端设备该配置为intra-cell CA，或者，可以指示该配置为intra-cell CA with sharing HARQ entity，或者，可以指示该配置针对的是多收发点传输，从而使得终端设备能够区分此时的配置为intra-cell CA。其中，该指示可以是显示指示(如上述方法B)，也可以是隐示指示(如上述方法C)。下面分别说明。
一种可能的实现方式，通过上述方法B显示指示终端设备配置的是intra-cell CA，即网络设备可以向终端设备发送指示信息#2，用于指示配置的是intra-cell CA。该指示信息#2可以包括在网络设备发送给终端设备的配置消息，例如RRCSetup、RRCResume、RRCReestablishment或RRCReconfiguration等消息中。
例如，该指示信息#2为可以是二进制数值，如“0”表示配置的不是intra-cell CA，即是普通CA，“1”表示配置的是intra-cell CA。
又如，该指示信息#2为可以是布尔值，如“False”表示配置的不是intra-cell CA，即是普通CA，“True”表示配置的是intra-cell CA。
又如，该指示信息#2为信元的形式，换句话说，可以通过在配置消息中是否有某一信元的方式来指示配置的是否为intra-cell CA。如，配置消息中包括了某信元，表示配置的是intra-cell CA，配置消息中没有包括该信元，表示配置的不是intra-cell CA，即是普通CA。其中，该信元例如可以是multiTrpTrans。应理解，其中，该信元的命名仅是为便于理解作的示例性说明，不应对本申请构成任何限定，该信元可以有其他名称或表达形式。
又一种可能的实现方式，通过上述方法C隐示指示终端设备配置的是intra-cell CA，即通过网络设备向终端设备发送的配置消息中所包括的N套配置参数，例如N套CellGroupConfig或N套ServingCellConfig，所对应的频点信息相同，确定该配置为intra-cell CA，或者，确定该配置针对的是多收发点传输，或者，确定该配置对应小区#A内的N个不同TRP或链路。
其中，频点信息可以包括以下至少一项：absoluteFrequencySSB、absoluteFrequencyPointA、frequencyBandList、scs-SpecificCarrierList等。
针对如图6所示的类载波聚合架构。
相比于传统CA架构(以传统2CC CA为例，传统2CC CA架构下，两个HARQ实体是分别对应两个CC/小区的)，图6所示的该架构可以看作是CA架构的一种变形。由于该架构下，两个HARQ实体是分别对应同一个服务小区内的两个TRP或链路的，为区分，将该变形记为小区内的CA(intra-cell CA)，将传统CA架构记为普通CA。应理解，上述命名不应对本申请构成任何限定。针对类载波聚合架构，可以重用传统CA的相关流程进行intra-cell CA的配置，即重用传统CA的相关流程进行同一个服务小区内多收发点传输的配置。
针对类载波聚合架构，可以指示终端设备该配置为intra-cell CA，或者，可以指示该配置针对的是多收发点传输，从而使得终端设备能够区分此时的配置为intra-cell CA。其中，该指示可以是显示指示(如上述方法B)，也可以是隐示指示(如上述方法C)。下面分别说明。
一种可能的实现方式，通过上述方法B显示指示终端设备配置的是intra-cell CA，即网络设备可以向终端设备发送指示信息#2，用于指示配置的是intra-cell CA。该指示信息#2可以包括在网络设备发送给终端设备的配置消息，例如RRCSetup、RRCResume、RRCReestablishment或RRCReconfiguration等消息中。
例如，该指示信息#2为可以是二进制数值，如“0”表示配置的不是intra-cell CA，即是普通CA，“1”表示配置的是intra-cell CA。
又如，该指示信息#2为可以是布尔值，如“False”表示配置的不是intra-cell CA，即是普通CA，“True”表示配置的是intra-cell CA。
又如，该指示信息#2为信元的形式，换句话说，可以通过在配置消息中是否有某一信元的方式来指示配置的是否为intra-cell CA。如，配置消息中包括了某信元，表示配置的是intra-cell CA，配置消息中没有包括该信元，表示配置的不是intra-cell CA，即是普通 CA。其中，该信元例如可以是multiTrpTrans。应理解，其中，该信元的命名仅是为便于理解作的示例性说明，不应对本申请构成任何限定，该信元可以有其他名称或表达形式。
又一种可能的实现方式，通过上述方法C隐示指示终端设备配置的是intra-cell CA，即通过网络设备向终端设备发送的配置消息中所包括的N套配置参数，例如N套CellGroupConfig或N套ServingCellConfig，所对应的频点信息相同，确定该配置为intra-cell CA，或者，确定该配置针对的是多收发点传输，或者，确定该配置对应小区#A内的N个不同TRP或链路。
其中，频点信息可以包括以下至少一项：absoluteFrequencySSB、absoluteFrequencyPointA、frequencyBandList、scs-SpecificCarrierList等。
针对如图7所示的第二类单小区架构。
相比于传统CA架构(以传统2CC CA为例，传统2CC CA架构下，两个HARQ实体是分别对应两个CC/小区的)，图7所示的该架构可以看作是CA架构的一种变形，此架构下，N个TRP共享一个HARQ entity。为区分，将该变形记为小区内的CA(intra-cell CA)，将传统CA架构记为普通CA。理解，上述命名不应对本申请构成任何限定。针对第二类单小区架构，可以重用传统CA的相关流程进行intra-cell CA的配置，即重用传统CA的相关流程进行同一个服务小区内多收发点传输的配置。相比于普通CA，对intra-cell CA的配置只有一个HARQ配置或两个完全一样的HARQ配置。
如前所述，针对第二类单小区架构，N套配置参数中，例如N套CellGroupConfig中，或N套ServingCellConfig中，有N套PUCCH配置。例如，以图7所示的TRP#1和TRP#2为例，TRP#1和TRP#2分别对应一套PUCCH配置。
针对第二类单小区架构，可以指示终端设备该配置为intra-cell CA，或者，可以指示该配置为intra-cell CA with sharing HARQ entity，或者，可以指示该配置针对的是多收发点传输，从而使得终端设备能够区分此时的配置为intra-cell CA。其中，该指示可以是显示指示(如上述方法B)，也可以是隐示指示(如上述方法C)。下面分别说明。
一种可能的实现方式，通过上述方法B显示指示终端设备配置的是intra-cell CA，即网络设备可以向终端设备发送指示信息#2，用于指示配置的是intra-cell CA。该指示信息#2可以包括在网络设备发送给终端设备的配置消息，例如RRCSetup、RRCResume、RRCReestablishment或RRCReconfiguration等消息中。
例如，该指示信息#2为可以是二进制数值，如“0”表示配置的不是intra-cell CA，即是普通CA，“1”表示配置的是intra-cell CA。
又如，该指示信息#2为可以是布尔值，如“False”表示配置的不是intra-cell CA，即是普通CA，“True”表示配置的是intra-cell CA。
又如，该指示信息#2为信元的形式，换句话说，可以通过在配置消息中是否有某一信元的方式来指示配置的是否为intra-cell CA。如，配置消息中包括了某信元，表示配置的是intra-cell CA，配置消息中没有包括该信元，表示配置的不是intra-cell CA，即是普通CA。其中，该信元例如可以是multiTrpTrans。应理解，其中，该信元的命名仅是为便于理解作的示例性说明，不应对本申请构成任何限定，该信元可以有其他名称或表达形式。
又一种可能的实现方式，通过上述方法C隐示指示终端设备配置的是intra-cell CA，即通过网络设备向终端设备发送的配置消息中所包括的N套配置参数，例如N套 CellGroupConfig或N套ServingCellConfig，所对应的频点信息相同，确定该配置为intra-cell CA，或者，确定该配置针对的是多收发点传输，或者，确定该配置对应小区#A内的N个不同TRP或链路。
其中，频点信息可以包括以下至少一项：absoluteFrequencySSB、absoluteFrequencyPointA、frequencyBandList、scs-SpecificCarrierList等。
上文结合不同架构，介绍了终端设备可以基于本申请实施例，确定小区#A是否配置了多收发点传输，或者，确定该N套配置参数针对的是否为多收发点传输。终端设备针对不同的TRP，可以进行不同的操作。下面具体说明。
可选地，N套与下行控制信道相关的配置参数对应小区#A的N个链路，N个链路包括第一链路和第二链路，终端设备可以基于第一链路执行波束失败检测和波束失败恢复过程；或者，终端设备可以基于第一链路执行随机接入过程；或者，终端设备可以基于第一链路执行无线链路管理RLM；或者，终端设备可以分别基于第一链路和第二链路执行RLM，且在第一链路发生无线链路失败RLF时，触发无线资源控制RRC重建。
其中，小区#A的N个链路，可以理解为，小区#A的N个TRP，或者可以理解为小区#A的N个TRP分别与终端设备通信的N个通道。相应地，第一链路和第二链路可以用第一TRP和第二TRP表示，或者第一链路可以表示为终端设备与第一TRP通信的链路，第二链路可以表示为终端设备与第二TRP通信的链路。
其中，第一链路可以是N个链路中的任意一个或多个，或者，可以是网络设备指定的一个链路或多个，或者，可以是协议规定的一个链路或多个，或者，也可以是N个链路中的一个或多个主链路。其中，主链路为终端设备与主TRP通信的通道或链路(关于主链路可参考图5至图7中的描述)。相应地，其中，第一TRP可以是N个TRP中的任意一个，或者，可以是网络设备指定的一个TRP，或者，可以是协议规定的一个TRP，或者，也可以是N个TRP中的主TRP。
终端设备确定第一链路或第一TRP的方法可以参考上述如情况1至情况6中的描述，如终端设备根据接收到的DCI对应的配置参数确定发送该DCI的TRP是小区#A的N个TRP中的哪个TRP或哪个链路的方法，不再赘述。
例如，网络设备可以通过显式或隐式的方法来指示第一链路或者第一TRP。如网络设备可以通过发送第一链路的标识或者第一TRP的标识来进行指示，或者，协议约定。又如，网络设备可以通过发送的包括对应于小区#A的N套与下行控制信道相关的配置参数的配置信息中包含的某一信元(或者说某一信元结构)来指第一链路或者第一TRP信息。具体可以参考情况1至情况6中的描述，不再赘述。
其中，第二链路可以是N个链路中不同于第一链路的任意一个或多个。相应地，第二TRP可以是N个TRP中不同于第一TRP的任意一个或多个。
终端设备确定各个链路(例如第Z链路)或各个TRP(例如第Z TRP)的方法，以及网络设备指示各个链路(例如第Z链路)或各个TRP(例如第Z TRP)的方法，可参考上述如情况1至情况6中的描述，不再赘述。其中Z可以是1至N区间内的任意取值。
对小区#A，终端设备能接收到来自小区#A的N个TRP或N个链路的信息，终端设备可以仅在其中一个或部分TRP或链路上执行一些操作。
基于本申请本实施例，终端设备可以只在一个TRP或一个链路上，或者，在部分TRP 或部分链路上，执行一些操作，避免对一个服务小区执行多套这些过程，简化了终端设备的实现和协议复杂度。
一种可能的实现方式，终端设备在网络设备指定的TRP或链路上执行波束失败检测(beam failure detection，BFD)和波束失败恢复过程(beam failure recovery，BFR)。
又一种可能的实现方式，终端设备在网络设备指定的TRP或链路上执行随机接入过程。
又一种可能的实现方式，终端设备可以在网络设备指定的TRP或链路上执行无线链路管理(radio link management，RLM)。或者，终端设备可以分别基于N个TRP或N个链路执行RLM，并在网络设备指定的TRP或链路发生无线链路失败(radio link failure，RLF)时，触发无线资源控制RRC重建立。在其它TRP发生无线链路失败后，终端设备将无线链路失败报告发送给网络设备指定的TRP或将无线链路失败报告发送给网络设备，由网络设备指定的TRP或网络设备进行相应的处理，例如，网络设备指定的TRP或网络设备将发生无线链路失败的TRP删除或者重配置该无线链路失败的TRP。
又一种可能的实现方式，终端设备在协议规定的TRP或链路上执行波束失败检测和波束失败恢复过程。
又一种可能的实现方式，终端设备在协议规定的TRP或链路上执行随机接入过程。
又一种可能的实现方式，终端设备可以在协议规定的TRP或链路上执行无线链路管理。或者，终端设备可以分别基于N个TRP或N个链路执行无线链路管理，并在协议规定的TRP或链路发生无线链路失败时，触发无线资源控制RRC重建立。在其它TRP发生无线链路失败后，终端设备将无线链路失败报告发送给协议规定的TRP或将无线链路失败报告发送给协议规定的TRP所属的网络设备，由协议规定的TRP或协议规定的TRP所属的网络设备进行相应的处理，例如，协议规定的TRP或协议规定的TRP所属的网络设备将发生无线链路失败的TRP删除或者重配置该无线链路失败的TRP。
又一种可能的实现方式，终端设备在主TRP或链路上执行波束失败检测和波束失败恢复过程。
又一种可能的实现方式，终端设备在主TRP或链路上执行随机接入过程。
又一种可能的实现方式，终端设备可以在主TRP或链路上执行无线链路管理。或者，终端设备可以分别基于N个TRP或N个链路执行无线链路管理，并在主TRP或链路发生无线链路失败RLF时，触发无线资源控制RRC重建立。在其它TRP发生无线链路失败后，终端设备将无线链路失败报告发送给主TRP或将无线链路失败报告发送给主TRP所属的网络设备，由主TRP或主TRP所属的网络设备进行相应的处理，例如，主TRP或主TRP所属的网络设备将发生无线链路失败的TRP删除或者重配置该无线链路失败的TRP。
又一种可能的实现方式，终端设备可以在网络设备指定的TRP上执行波束级别的RRM测量；或者，终端设备可以在协议规定的TRP上执行波束级别的RRM测量；或者，终端设备可以分别在N个TRP上执行波束级别的RRM测量。
以上结合几种可能的实现方式，介绍了终端设备可以只在一个TRP或一个链路或部分TRP或链路上执行一些操作，应理解，上述几种可能的实现方式以及具体操作仅是示例性说明，本申请并未限定于此。
可以理解的是，本申请上述各个实施例中，由终端设备实现的方法也可以由可用于终 端设备的部件(例如芯片或者电路)实现，由网络设备实现的方法也可以由可用于网络设备的部件(例如芯片或者电路)实现。
基于本申请实施例，网络设备可以为服务小区配置N套配置参数，或者，也可以理解为，网络设备为服务小区中的每个收发点配置一套配置参数，那么服务小区中的每个收发点都可以基于为其配置的配置参数与终端设备传输数据。从而不仅能够避免服务小区中的多个收发点采用一套配置参数与终端设备进行通信可能会导致的干扰问题，而且可以使得终端设备根据实际通信情况，与相应的收发点基于对应的配置参数进行通信，提高通信效率。
以上，结合图4至图9详细说明了本申请实施例提供的方法。以下，结合图10至图12详细说明本申请实施例提供的通信装置。
图10是本申请实施例提供的通信装置的示意性框图。如图所示，该通信装置1000可以包括通信单元1100和处理单元1200。
图10是本申请实施例提供的通信装置的示意性框图。如图所示，该通信装置1000可以包括通信单元1100和处理单元1200。
在一种可能的设计中，该通信装置1000可实现对应于上文方法实施例中的终端设备执行的步骤或者流程，例如，可以为终端设备，或者配置于终端设备中的芯片或电路。
一种可能的实现方式，通信单元1100用于：接收服务小区的配置信息，配置信息包括对应于服务小区的N套与下行控制信道相关的配置参数，其中，每套配置参数包括的参数类型相同，N为大于或等于2的整数；处理单元1200用于：基于N套与下行控制信道相关的配置参数，与服务小区通信。
可选地，通信单元1100还用于：接收第一下行控制信息DCI，第一DCI对应的配置参数属于N套与下行控制信道相关的配置参数中的一套；处理单元1200用于：根据第一DCI，确定第一DCI对应的链路。
可选地，配置参数包括以下至少一项：物理下行控制信道PDCCH配置、小区标识信息、小区无线网络临时标识C-RNTI、解调参考信号DMRS、波束集信息、或波束信息。
可选地，N套与下行控制信道相关的配置参数对应服务小区的N个链路，N个链路包括第一链路和第二链路，处理单元1200还用于：基于第一链路执行波束失败检测和波束失败恢复过程；或者，基于第一链路执行随机接入过程；或者，基于第一链路执行无线链路管理RLM；或者，分别基于第一链路和所述第二链路执行RLM，且在第一链路发生无线链路失败RLF时，触发无线资源控制RRC重建；其中，第一链路是主链路。
可选地，通信单元1100还用于：接收对应于服务小区的N套与上行控制信道相关的配置参数，N套与上行控制信道相关的配置参数与N套与下行控制信道相关的配置参数一一关联。
可选地，处理单元1200还用于：确定与服务小区通信的协议架构类型，其中，协议架构类型包括以下至少一项：类多连接架构、类载波聚合架构、或类单小区架构。
可选地，通信单元1100还用于：获取指示信息，获取指示信息，指示信息用于指示终端设备与服务小区通信的协议架构类型；处理单元1200具体用于：根据指示信息确定与服务小区通信的协议架构类型。
可选地，N套与下行控制信道相关的配置参数对应服务小区的N个链路；处理单元 1200还用于：当协议架构类型为类多连接架构时，对应配置可以使用服务小区的无线承载RB，生成一个分组数据汇聚层协议PDCP实体，生成N个无线链路控制RLC实体、生成N个媒体接入控制MAC实体、以及生成N个混合自动重传请求HARQ实体，其中，一个PDCP实体为N个链路共用，N个RLC实体与N个链路对应，N个MAC实体与N个链路对应，N个HARQ实体与N个链路对应；或者，当协议架构类型为类载波聚合架构时，对应配置可以使用服务小区的RB，生成一个PDCP实体、一个RLC实体、以及一个MAC实体，且生成N个HARQ实体，其中，一个PDCP实体为N个链路共用，一个RLC实体为N个链路共用，一个MAC实体为N个链路共用，N个HARQ实体与N个链路对应；或者，当协议架构类型为类单小区架构时，对应配置可以使用服务小区的RB，生成一个PDCP实体、一个RLC实体、一个MAC实体、以及一个HARQ实体，其中，一个PDCP实体为N个链路共用，一个RLC实体为N个链路共用，一个MAC实体为N个链路共用，一个HARQ实体为N个链路共用。
又一种可能的实现方式，通信单元1100用于：基于对应于服务小区的N套与上行控制信道相关的配置参数，与服务小区通信，其中，N套与上行控制信道相关的配置参数与N套与下行控制信道相关的配置参数一一关联，N套与下行控制信道相关的配置参数对应服务小区的N个链路，服务小区的N个链路共用一个PDCP实体、一个RLC实体、一个MAC实体、以及一个HARQ实体，N为大于或等于2的整数。
可选地，配置参数包括以下至少一项：物理下行控制信道PDCCH配置、小区标识信息、小区无线网络临时标识C-RNTI、解调参考信号DMRS、波束集信息、或波束信息。
具体地，该通信装置1000可实现对应于根据本申请实施例的方法200中的终端设备执行的步骤或者流程，该通信装置1000可以包括用于执行图9中的方法200中的终端设备执行的方法的单元。并且，该通信装置1000中的各单元和上述其他操作和/或功能分别为了实现图9中的方法200的相应流程。
其中，当该通信装置1000用于执行图9中的方法200时，通信单元1100可用于执行方法200中的步骤220，处理单元1200可用于执行方法200中的步骤230。
应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
还应理解，该通信装置1000为终端设备时，该通信装置1000中的通信单元1100可对应于图11中示出的终端设备2000中的收发器2020，该通信装置1000中的处理单元1200可对应于图11中示出的终端设备2000中的处理器2010。
还应理解，该通信装置1000为配置于终端设备中的芯片或者电路时，该通信装置1000中的通信单元1100可以为输入/输出接口。
在另一种可能的设计中，该通信装置1000可实现对应于上文方法实施例中的网络设备执行的步骤或者流程，例如，可以为网络设备，或者配置于网络设备中的芯片或电路；又如，也可以为收发点，或者配置于收发点中的芯片或电路。
处理单元1200用于：生成服务小区的配置信息，配置信息包括对应于服务小区的N套与下行控制信道相关的配置参数，其中，每套配置参数包括的参数类型相同，N为大于或等于2的整数；通信单元1100用于：发送服务小区的配置信息。
可选地，通信单元1100还用于：发送第一下行控制信息DCI，第一DCI对应的配置 参数属于N套与下行控制信道相关的配置参数中的一套。
可选地，配置参数包括以下至少一项：物理下行控制信道PDCCH配置、小区标识信息、小区无线网络临时标识C-RNTI、解调参考信号DMRS、波束集信息、或波束信息。
可选地，通信单元1100还用于：发送对应于服务小区的N套与上行控制信道相关的配置参数，N套与上行控制信道相关的配置参数与N套与下行控制信道相关的配置参数一一关联。
可选地，通信单元1100还用于：发送指示信息，指示信息用于指示终端设备与服务小区通信的协议架构类型，其中，协议架构类型包括以下至少一项：类多连接架构、类载波聚合架构、或类单小区架构。
又一种可能的实现方式，通信单元1100用于：基于对应于服务小区的N套与下行控制信道相关的配置参数，与终端设备通信，其中，N套与下行控制信道相关的配置参数对应服务小区的N个链路，服务小区的N个链路共用一个PDCP实体、一个RLC实体、一个MAC实体、以及一个HARQ实体，N套与下行控制信道相关的配置参数与N套与上行控制信道相关的配置参数一一关联，N为大于或等于2的整数。
可选地，配置参数包括以下至少一项：物理下行控制信道PDCCH配置、小区标识信息、小区无线网络临时标识C-RNTI、解调参考信号DMRS、波束集信息、或波束信息。
具体地，该通信装置1000可实现对应于根据本申请实施例的方法200中的网络设备执行的步骤或者流程，该通信装置1000可以包括用于执行图9中的方法200中的网络设备执行的方法的单元。并且，该通信装置1000中的各单元和上述其他操作和/或功能分别为了实现图9中的方法200的相应流程。
其中，当该通信装置1000用于执行图9中的方法200时，通信单元1100可用于执行方法200中的步骤220，处理单元1200可用于执行方法200中的步骤210和步骤230。
应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
还应理解，该通信装置1000为网络设备时，该通信装置1000中的通信单元为可对应于图12中示出的网络设备3000中的收发器3200，该通信装置1000中的处理单元1200可对应于图12中示出的网络设备3000中的处理器3100。
还应理解，该通信装置1000为配置于网络设备中的芯片或者电路时，该通信装置1000中的通信单元1100可以为输入/输出接口。
图11是本申请实施例提供的终端设备2000的结构示意图。该终端设备2000可应用于如图1至图8所示的系统中，执行上述方法实施例中终端设备的功能，或者实现上述方法实施例中终端设备执行的步骤或者流程。
如图所示，该终端设备2000包括处理器2010和收发器2020。可选地，该终端设备2000还包括存储器2030。其中，处理器2010、收发器2002和存储器2030之间可以通过内部连接通路互相通信，传递控制和/或数据信号，该存储器2030用于存储计算机程序，该处理器2010用于从该存储器2030中调用并运行该计算机程序，以控制该收发器2020收发信号。可选地，终端设备2000还可以包括天线2040，用于将收发器2020输出的上行数据或上行控制信令通过无线信号发送出去。
上述处理器2010可以和存储器2030可以合成一个处理装置，处理器2010用于执行 存储器2030中存储的程序代码来实现上述功能。具体实现时，该存储器2030也可以集成在处理器2010中，或者独立于处理器2010。该处理器2010可以与图10中的处理单元对应。
上述收发器2020可以与图10中的通信单元对应，也可以称为收发单元。收发器2020可以包括接收器(或称接收机、接收电路)和发射器(或称发射机、发射电路)。其中，接收器用于接收信号，发射器用于发射信号。
应理解，图11所示的终端设备2000能够实现图9所示方法实施例中涉及终端设备的各个过程。终端设备2000中的各个模块的操作和/或功能，分别为了实现上述方法实施例中的相应流程。具体可参见上述方法实施例中的描述，为避免重复，此处适当省略详述描述。
上述处理器2010可以用于执行前面方法实施例中描述的由终端设备内部实现的动作，而收发器2020可以用于执行前面方法实施例中描述的终端设备向网络设备发送或从网络设备接收的动作。具体请见前面方法实施例中的描述，此处不再赘述。
可选地，上述终端设备2000还可以包括电源2050，用于给终端设备中的各种器件或电路提供电源。
除此之外，为了使得终端设备的功能更加完善，该终端设备2000还可以包括输入单元2060、显示单元2070、音频电路2080、摄像头2090和传感器2100等中的一个或多个，所述音频电路还可以包括扬声器2082、麦克风2084等。
图12是本申请实施例提供的网络设备的结构示意图，例如可以为基站的结构示意图。该基站3000可应用于如图1至图8所示的系统中，执行上述方法实施例中网络设备的功能，或者实现上述方法实施例中网络设备执行的步骤或者流程。
如图所示，该基站3000可以包括一个或多个射频单元，如远端射频单元(remote radio unit，RRU)3100和一个或多个基带单元(baseband unit，BBU)(也可称为数字单元，digital unit，DU)3200。所述RRU 3100可以称为收发单元，与图10中的通信单元1100对应。可选地，该收发单元3100还可以称为收发机、收发电路、或者收发器等等，其可以包括至少一个天线3101和射频单元3102。可选地，收发单元3100可以包括接收单元和发送单元，接收单元可以对应于接收器(或称接收机、接收电路)，发送单元可以对应于发射器(或称发射机、发射电路)。所述RRU 3100部分主要用于射频信号的收发以及射频信号与基带信号的转换，例如用于向终端设备发送指示信息。所述BBU 3200部分主要用于进行基带处理，对基站进行控制等。所述RRU 3100与BBU 3200可以是物理上设置在一起，也可以物理上分离设置的，即分布式基站。
所述BBU 3200为基站的控制中心，也可以称为处理单元，可以与图10中的处理单元1200对应，主要用于完成基带处理功能，如信道编码，复用，调制，扩频等等。例如所述BBU(处理单元)可以用于控制基站执行上述方法实施例中关于网络设备的操作流程，例如，生成上述指示信息，或者配置服务小区等。
在一个示例中，所述BBU 3200可以由一个或多个单板构成，多个单板可以共同支持单一接入制式的无线接入网(如LTE网)，也可以分别支持不同接入制式的无线接入网(如LTE网，5G网或其他网)。所述BBU 3200还包括存储器3201和处理器3202。所述存储器3201用以存储必要的指令和数据。所述处理器3202用于控制基站进行必要的动 作，例如用于控制基站执行上述方法实施例中关于网络设备的操作流程。所述存储器3201和处理器3202可以服务于一个或多个单板。也就是说，可以每个单板上单独设置存储器和处理器。也可以是多个单板共用相同的存储器和处理器。此外每个单板上还可以设置有必要的电路。
应理解，图12所示的基站3000能够实现图9方法实施例中涉及网络设备的各个过程。基站3000中的各个模块的操作和/或功能，分别为了实现上述方法实施例中的相应流程。具体可参见上述方法实施例中的描述，为避免重复，此处适当省略详述描述。
上述BBU 3200可以用于执行前面方法实施例中描述的由网络设备内部实现的动作，而RRU 3100可以用于执行前面方法实施例中描述的网络设备向终端设备发送或从终端设备接收的动作。具体请见前面方法实施例中的描述，此处不再赘述。
本申请实施例还提供了一种处理装置，包括处理器和接口。所述处理器可用于执行上述方法实施例中的方法。
应理解，上述处理装置可以是一个芯片。例如，该处理装置可以是现场可编程门阵列(field programmable gate array，FPGA)，可以是专用集成芯片(application specific integrated circuit，ASIC)，还可以是系统芯片(system on chip，SoC)，还可以是中央处理器(central processor unit，CPU)，还可以是网络处理器(network processor，NP)，还可以是数字信号处理电路(digital signal processor，DSP)，还可以是微控制器(micro controller unit，MCU)，还可以是可编程控制器(programmable logic device，PLD)或其他集成芯片。
在实现过程中，上述方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。
应注意，本申请实施例中的处理器可以是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM， EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
根据本申请实施例提供的方法，本申请还提供一种计算机程序产品，该计算机程序产品包括：计算机程序代码，当该计算机程序代码在计算机上运行时，使得该计算机执行图9所示实施例中任意一个实施例的方法。
根据本申请实施例提供的方法，本申请还提供一种计算机可读介质，该计算机可读介质存储有程序代码，当该程序代码在计算机上运行时，使得该计算机执行图9所示实施例中任意一个实施例的方法。
根据本申请实施例提供的方法，本申请还提供一种系统，其包括前述的一个或多个终端设备以及一个或多个网络设备。
根据本申请实施例提供的方法，本申请还提供一种系统，其包括前述的多个收发点TRP。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disc，SSD))等。
上述各个装置实施例中网络设备与终端设备和方法实施例中的网络设备或终端设备完全对应，由相应的模块或单元执行相应的步骤，例如通信单元(收发器)执行方法实施例中接收或发送的步骤，除发送、接收外的其它步骤可以由处理单元(处理器)执行。具体单元的功能可以参考相应的方法实施例。其中，处理器可以为一个或多个。
在本说明书中使用的术语“部件”、“模块”、“系统”等用于表示计算机相关的实体、硬件、固件、硬件和软件的组合、软件、或执行中的软件。例如，部件可以是但不限于，在处理器上运行的进程、处理器、对象、可执行文件、执行线程、程序和/或计算机。通过图示，在计算设备上运行的应用和计算设备都可以是部件。一个或多个部件可驻留在 进程和/或执行线程中，部件可位于一个计算机上和/或分布在两个或更多个计算机之间。此外，这些部件可从在上面存储有各种数据结构的各种计算机可读介质执行。部件可例如根据具有一个或多个数据分组(例如来自与本地系统、分布式系统和/或网络间的另一部件交互的二个部件的数据，例如通过信号与其它系统交互的互联网)的信号通过本地和/或远程进程来通信。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各种说明性逻辑块(illustrative logical block)和步骤(step)，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (17)

  1. 一种通信方法，其特征在于，包括：
    接收服务小区的配置信息，所述配置信息包括对应于所述服务小区的N套与下行控制信道相关的配置参数，其中，每套配置参数包括的参数类型相同，N为大于或等于2的整数；
    基于所述N套与下行控制信道相关的配置参数，与所述服务小区通信。
  2. 根据权利要求1所述的方法，其特征在于，
    所述配置参数包括以下至少一项：物理下行控制信道PDCCH配置、小区标识信息、小区无线网络临时标识C-RNTI、解调参考信号DMRS、波束集信息、或者波束信息。
  3. 根据权利要求1或2所述的方法，其特征在于，所述N套与下行控制信道相关的配置参数对应所述服务小区的N个链路，所述N个链路包括第一链路和第二链路，
    所述方法还包括：
    基于所述第一链路执行波束失败检测和波束失败恢复过程；或者，
    基于所述第一链路执行随机接入过程；或者，
    基于所述第一链路执行无线链路管理RLM；或者，
    分别基于所述第一链路和所述第二链路执行RLM，且在所述第一链路发生无线链路失败RLF时，触发无线资源控制RRC重建；
    其中，所述第一链路是主链路。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，所述方法还包括：
    接收对应于所述服务小区的N套与上行控制信道相关的配置参数，所述N套与上行控制信道相关的配置参数与所述N套与下行控制信道相关的配置参数一一关联。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，所述方法还包括：
    确定与所述服务小区通信的协议架构类型，
    其中，所述协议架构类型包括以下至少一项：
    类多连接架构、类载波聚合架构、或类单小区架构。
  6. 根据权利要求5所述的方法，其特征在于，所述方法还包括：
    获取指示信息，所述指示信息用于指示终端设备与所述服务小区通信的协议架构类型；
    所述确定与所述服务小区通信的协议架构类型，包括：
    根据所述指示信息确定与所述服务小区通信的协议架构类型。
  7. 根据权利要求5或6所述的方法，其特征在于：所述N套与下行控制信道相关的配置参数对应所述服务小区的N个链路；
    当所述协议架构类型为所述类多连接架构时，对应配置可以使用所述服务小区的无线承载RB，生成一个分组数据汇聚层协议PDCP实体，生成N个无线链路控制RLC实体、生成N个媒体接入控制MAC实体、以及生成N个混合自动重传请求HARQ实体，其中，所述一个PDCP实体为所述N个链路共用，所述N个RLC实体与所述N个链路对应，所述N个MAC实体与所述N个链路对应，所述N个HARQ实体与所述N个链路对应；
    或者，
    当所述协议架构类型为所述类载波聚合架构时，对应配置可以使用所述服务小区的RB，生成一个PDCP实体、一个RLC实体、以及一个MAC实体，且生成N个HARQ实体，其中，所述一个PDCP实体为所述N个链路共用，所述一个RLC实体为所述N个链路共用，所述一个MAC实体为所述N个链路共用，所述N个HARQ实体与所述N个链路对应；
    或者，
    当所述协议架构类型为所述类单小区架构时，对应配置可以使用所述服务小区的RB，生成一个PDCP实体、一个RLC实体、一个MAC实体、以及一个HARQ实体，其中，所述一个PDCP实体为所述N个链路共用，所述一个RLC实体为所述N个链路共用，所述一个MAC实体为所述N个链路共用，所述一个HARQ实体为所述N个链路共用。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，所述方法还包括：
    接收第一下行控制信息DCI，所述第一DCI对应的配置参数属于所述N套与下行控制信道相关的配置参数中的一套；
    根据所述第一DCI，确定所述第一DCI对应的链路。
  9. 一种通信方法，其特征在于，包括：
    生成服务小区的配置信息，所述服务小区的配置信息包括对应于所述服务小区的N套与下行控制信道相关的配置参数，其中，每套配置参数包括的参数类型相同，N为大于或等于2的整数；
    发送所述服务小区的配置信息。
  10. 根据权利要求9所述的方法，其特征在于，
    所述配置参数包括以下至少一项：物理下行控制信道PDCCH配置、小区标识信息、小区无线网络临时标识C-RNTI、解调参考信号DMRS、波束集信息、或波束信息。
  11. 根据权利要求9或10所述的方法，其特征在于，所述方法还包括：
    发送对应于所述服务小区的N套与上行控制信道相关的配置参数，所述N套与上行控制信道相关的配置参数与所述N套与下行控制信道相关的配置参数一一关联。
  12. 根据权利要求9至11中任一项所述的方法，其特征在于，所述方法还包括：
    发送指示信息，所述指示信息用于指示终端设备与所述服务小区通信的协议架构类型，
    其中，所述协议架构类型包括以下至少一项：
    类多连接架构、类载波聚合架构、或类单小区架构。
  13. 根据权利要求9至12中任一项所述的方法，其特征在于，所述方法还包括：
    发送第一下行控制信息DCI，所述第一DCI对应的配置参数属于所述N套与下行控制信道相关的配置参数中的一套。
  14. 一种通信装置，其特征在于，用于实现如权利要求1至8中任意一项所述的方法。
  15. 一种通信装置，其特征在于，用于实现如权利要求9至13中任意一项所述的方法。
  16. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储有计算机程序，当所述计算机程序在计算机上运行时，
    使得所述计算机执行如权利要求1至8中任意一项所述的方法，或者
    使得所述计算机执行如权利要求9至13中任意一项所述的方法。
  17. 一种芯片系统，其特征在于，包括：处理器，用于从存储器中调用并运行计算机程序，
    使得安装有所述芯片系统的通信设备执行如权利要求1至8中任意一项所述的方法；或者
    使得安装有所述芯片系统的通信设备执行如权利要求9至13中任意一项所述的方法。
PCT/CN2020/071007 2019-01-11 2020-01-08 通信方法和通信装置 WO2020143692A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP20738425.6A EP3902149A4 (en) 2019-01-11 2020-01-08 COMMUNICATION METHOD AND APPARATUS
JP2021540208A JP7358481B2 (ja) 2019-01-11 2020-01-08 通信方法および通信装置
US17/371,352 US20210377920A1 (en) 2019-01-11 2021-07-09 Communication Method and Communications Apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910028856.2 2019-01-11
CN201910028856.2A CN111435845B (zh) 2019-01-11 2019-01-11 通信方法和通信装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/371,352 Continuation US20210377920A1 (en) 2019-01-11 2021-07-09 Communication Method and Communications Apparatus

Publications (1)

Publication Number Publication Date
WO2020143692A1 true WO2020143692A1 (zh) 2020-07-16

Family

ID=71521446

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/071007 WO2020143692A1 (zh) 2019-01-11 2020-01-08 通信方法和通信装置

Country Status (5)

Country Link
US (1) US20210377920A1 (zh)
EP (1) EP3902149A4 (zh)
JP (1) JP7358481B2 (zh)
CN (1) CN111435845B (zh)
WO (1) WO2020143692A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022168876A1 (ja) * 2021-02-05 2022-08-11 株式会社Ｎｔｔドコモ 端末、無線通信方法及び基地局
WO2023278588A3 (en) * 2021-06-30 2023-02-09 Ofinno, Llc Determination of connection failure

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11405975B2 (en) * 2019-03-29 2022-08-02 Qualcomm Incorporated Link failure recovery procedure for a primary cell (PCell) and a secondary cell (SCell)
JP7242600B2 (ja) * 2020-03-18 2023-03-20 株式会社東芝 給電装置
CN114258131A (zh) * 2020-09-22 2022-03-29 中国移动通信有限公司研究院 物理上行共享信道的传输方法、接收方法、终端及基站
CN116548038A (zh) * 2020-10-30 2023-08-04 高通股份有限公司 多发送接收点（trp）操作期间的波束恢复
CN115378559A (zh) * 2021-05-18 2022-11-22 上海朗帛通信技术有限公司 一种被用于无线通信的节点中的方法和装置
CN115842703A (zh) * 2021-08-06 2023-03-24 华为技术有限公司 一种数据传输的方法及通信装置
WO2023159492A1 (zh) * 2022-02-25 2023-08-31 Oppo广东移动通信有限公司 无线通信的方法和终端设备
WO2024087211A1 (zh) * 2022-10-28 2024-05-02 北京小米移动软件有限公司 一种传输配置信息的方法、装置及可读存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103974430A (zh) * 2013-02-06 2014-08-06 电信科学技术研究院 一种数据传输方法及装置
CN108713341A (zh) * 2016-03-10 2018-10-26 高通股份有限公司 用于超低延时（ull）和传统传输的资源管理的方法和装置
WO2018204282A1 (en) * 2017-05-03 2018-11-08 Idac Holdings, Inc. Beam-based pdcch transmission in nr

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012173445A2 (ko) * 2011-06-17 2012-12-20 엘지전자 주식회사 무선 접속 시스템에서 데이터 송수신 방법 및 이를 위한 단말
US9674855B2 (en) * 2012-03-29 2017-06-06 Qualcomm Incorporated H-ARQ timing determination under cross-carrier scheduling in LTE
US20180198650A1 (en) 2017-01-06 2018-07-12 Sharp Laboratories Of America, Inc. User equipments, base stations and methods
JP6995880B2 (ja) 2017-04-27 2022-01-17 オッポ広東移動通信有限公司 無線通信方法、端末装置及び送受信ノード
CN109391441B (zh) * 2017-08-11 2020-10-30 电信科学技术研究院 一种控制信息的发送方法、接收方法、基站及终端
US11172485B2 (en) * 2018-07-26 2021-11-09 Qualcomm Incorporated Group-common control information
CN113507747B (zh) * 2018-08-08 2023-09-01 中兴通讯股份有限公司 信息发送和接收方法、设备和存储介质

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103974430A (zh) * 2013-02-06 2014-08-06 电信科学技术研究院 一种数据传输方法及装置
CN108713341A (zh) * 2016-03-10 2018-10-26 高通股份有限公司 用于超低延时（ull）和传统传输的资源管理的方法和装置
WO2018204282A1 (en) * 2017-05-03 2018-11-08 Idac Holdings, Inc. Beam-based pdcch transmission in nr

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
CATT: "Considerations on DL multi-panel and multi-TRP transmission, R1-1712368", 3GPP DRAFT; R1-1712368, 25 August 2017 (2017-08-25), Prague, Czechia, pages 1 - 4, XP051315184 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022168876A1 (ja) * 2021-02-05 2022-08-11 株式会社Ｎｔｔドコモ 端末、無線通信方法及び基地局
WO2023278588A3 (en) * 2021-06-30 2023-02-09 Ofinno, Llc Determination of connection failure

Also Published As

Publication number Publication date
JP7358481B2 (ja) 2023-10-10
CN111435845A (zh) 2020-07-21
CN111435845B (zh) 2023-12-19
EP3902149A4 (en) 2022-05-25
US20210377920A1 (en) 2021-12-02
JP2022517075A (ja) 2022-03-04
EP3902149A1 (en) 2021-10-27

Similar Documents

Publication Publication Date Title
WO2020143692A1 (zh) 通信方法和通信装置
WO2020143828A1 (zh) 资源配置的方法和装置
WO2020164418A1 (zh) 一种测量方法、终端设备及网络设备
WO2021163938A1 (zh) 天线切换方法、终端设备和通信设备
EP3846532A1 (en) Power control method and device
TW202013921A (zh) 發送上行信號的方法和設備
WO2021018283A1 (zh) 通信方法和通信装置
WO2020211096A1 (zh) 无线通信方法、终端设备和网络设备
CN113490278B (zh) 下行信号传输的方法和设备
TW202021390A (zh) 無線通訊的方法、終端設備和網路設備
WO2020156364A1 (zh) 测量方法和通信装置
US20220173847A1 (en) Downlink transmission method and terminal device
WO2021203956A1 (zh) 一种通信方法及装置
US20200374887A1 (en) Channel transmission method and apparatus, and computer storage medium
JP7419553B2 (ja) フィードバックリソース決定方法およびフィードバックリソース決定装置
WO2021212372A1 (zh) 资源分配方法和终端
US20230069425A1 (en) Sidelink resource allocation method and terminal device
WO2023029008A1 (zh) 信息传输方法、设备及存储介质
WO2022067611A1 (zh) 先侦听后传输失败上报的方法、终端设备和网络设备
WO2021196237A1 (zh) 侧行反馈信息处理方法、终端设备和网络设备
WO2021072602A1 (zh) 链路失败检测的方法和装置
WO2021062795A1 (zh) 一种通信方法及装置
WO2023011180A1 (zh) 载波配置方法及通信装置
US20230129834A1 (en) Method for determining antenna panel for transmission, and terminal device
WO2023039811A1 (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: 20738425

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021540208

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020738425

Country of ref document: EP

Effective date: 20210719