WO2022083541A1 - 电子设备、通信方法和存储介质 - Google Patents

电子设备、通信方法和存储介质 Download PDF

Info

Publication number
WO2022083541A1
WO2022083541A1 PCT/CN2021/124388 CN2021124388W WO2022083541A1 WO 2022083541 A1 WO2022083541 A1 WO 2022083541A1 CN 2021124388 W CN2021124388 W CN 2021124388W WO 2022083541 A1 WO2022083541 A1 WO 2022083541A1
Authority
WO
WIPO (PCT)
Prior art keywords
channel
base station
electronic device
pusch
pdsch
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2021/124388
Other languages
English (en)
French (fr)
Inventor
曹建飞
刘敏
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Sony Group Corp
Original Assignee
Sony Group Corp
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 Sony Group Corp filed Critical Sony Group Corp
Priority to EP21881957.1A priority Critical patent/EP4207908A4/en
Priority to US18/247,274 priority patent/US20230412231A1/en
Priority to JP2023524832A priority patent/JP2023547416A/ja
Priority to CN202180071344.XA priority patent/CN116420408A/zh
Priority to KR1020237011958A priority patent/KR20230092890A/ko
Publication of WO2022083541A1 publication Critical patent/WO2022083541A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • 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/0613—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission
    • H04B7/0615—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission of weighted versions of same signal
    • H04B7/0619—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission of weighted versions of same signal using feedback from receiving side
    • H04B7/0636—Feedback format
    • H04B7/0639—Using selective indices, e.g. of a codebook, e.g. pre-distortion matrix index [PMI] or for beam selection
    • 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/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
    • H04B7/06952—Selecting one or more beams from a plurality of beams, e.g. beam training, management or sweeping
    • 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/0014—Three-dimensional division
    • H04L5/0023—Time-frequency-space
    • 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/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
    • H04B7/06952—Selecting one or more beams from a plurality of beams, e.g. beam training, management or sweeping
    • H04B7/0696—Determining beam pairs
    • H04B7/06962—Simultaneous selection of transmit [Tx] and receive [Rx] beams at both sides of a link
    • 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
    • H04B7/06952—Selecting one or more beams from a plurality of beams, e.g. beam training, management or sweeping
    • H04B7/06968—Selecting one or more beams from a plurality of beams, e.g. beam training, management or sweeping using quasi-colocation [QCL] between signals
    • 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
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0044—Allocation of payload; Allocation of data channels, e.g. PDSCH or PUSCH
    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0457—Variable allocation of band or rate
    • 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
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1273—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of downlink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H04W72/231—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the layers above the physical layer, e.g. RRC or MAC-CE signalling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H04W72/232—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the physical layer, e.g. DCI signalling
    • 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) or DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A) or DMT the frequencies being arranged in component carriers

Definitions

  • the present disclosure relates to an electronic device, a communication method, and a storage medium, and more particularly, the present disclosure relates to an electronic device, a communication method, and a storage medium for beam sharing operations between different physical channels in a wireless communication system.
  • the base station uses different mechanisms to indicate to the UE the beams determined for the control channel and the data channel.
  • beams used for downlink or uplink control channels can be indicated using a medium access control (MAC) control element (CE)
  • MAC medium access control
  • DCI downlink control information
  • the base station may need to reselect the transmission beam and indicate the updated beam for the data channel, eg, by sending DCI.
  • the update of the beam used for the control channel needs to be done by sending the MAC CE, which is not so fast.
  • beam updates for control channels and data channels need to be indicated separately, even if they have the same beam direction, which may introduce redundant signaling burden.
  • the present disclosure provides aspects related to enabling beam sharing over various transmission channels between a base station and a UE.
  • the needs described above may be met by applying one or more aspects of the present disclosure.
  • an electronic device on the side of a base station including a processing circuit configured to: determine a first beam used for a first transmission channel between the base station and a UE; the UE sends dynamic signaling containing beam indication information about the first beam, so that the beam used for the first transmission channel is updated to the first beam; and if the update of the beam used for the first transmission channel is successful , updating the beam used for the second transmission channel and/or the reference signal between the base station and the UE to the first beam.
  • an electronic device on the UE side including a processing circuit configured to: receive dynamic signaling including beam indication information about a first beam from a base station, and the first beam is determined for the first transmission channel between the UE and the base station; updating the beam for the first transmission channel to the first beam; and if the update of the beam for the first transmission channel is successful, updating the beam for the first transmission channel
  • the beam used for the second transmission channel and/or the reference signal between the UE and the base station is updated to the first beam.
  • a communication method comprising: determining a first beam for a first transmission channel between the base station and a UE; sending beam indication information including the first beam to the UE dynamic signaling, so that the beam used for the first transmission channel is updated to the first beam; and if the update of the beam used for the first transmission channel is successful, the beam used for the first transmission channel will be used for the communication between the base station and the UE.
  • the beam of the second transmission channel and/or the reference signal in between is updated to the first beam.
  • a communication method comprising: receiving, from a base station, dynamic signaling including beam indication information about a first beam determined for communication between the UE and the base station a first transmission channel; updating the beam used for the first transmission channel to a first beam; and if the update of the beam used for the first transmission channel is successful, The beam of the second transmission channel and/or the reference signal is updated to the first beam.
  • a non-transitory computer-readable storage medium storing executable instructions that, when executed, implement any one of the above communication methods.
  • Figure 1 schematically shows beams available to a base station and a UE
  • FIG. 2 shows a schematic diagram of beam sharing according to the first embodiment
  • FIG. 3 is a schematic configuration diagram illustrating a TCI state
  • Figure 4 illustrates a MAC CE for activating the TCI state for a data channel
  • FIG. 6 shows a schematic diagram of beam sharing according to the second embodiment
  • FIG. 7A and 7B show schematic diagrams of beam sharing according to a third embodiment
  • FIG. 8 is a schematic diagram illustrating a configuration of PUCCH spatial relationship information
  • FIG. 9 shows a schematic diagram of beam sharing according to a fourth embodiment
  • Figure 10 shows a MAC CE for activating the TCI state for a control channel
  • FIG. 11 shows a schematic diagram of beam sharing according to the fifth embodiment
  • Figure 12 shows a MAC CE for activating PUCCH spatial relationship information for a control channel
  • 13A and 13B illustrate an electronic device on the base station side and a communication method thereof according to an embodiment
  • 14A and 14B illustrate an electronic device on the UE side and a communication method thereof according to an embodiment
  • FIG. 15 illustrates a first example of a schematic configuration of a base station according to the present disclosure
  • FIG. 16 illustrates a second example of a schematic configuration of a base station according to the present disclosure
  • FIG. 17 illustrates a schematic configuration example of a smartphone according to the present disclosure
  • FIG. 18 illustrates a schematic configuration example of a car navigation apparatus according to the present disclosure.
  • both the base station and the UE can apply massive antenna technology such as Massive MIMO (Massive MIMO).
  • Massive MIMO massive MIMO
  • both the base station and the UE have many antennas, such as dozens, hundreds or even thousands of antennas.
  • a three-layer mapping relationship is generally defined around the antenna, so that it can successfully undertake the channel model and communication standards.
  • the bottom layer is the most basic physical unit - the antenna, which can also be called the antenna array element.
  • Each antenna element radiates electromagnetic waves according to their respective amplitude parameters and phase parameters.
  • the antenna elements are arranged into one or more antenna arrays in the form of a matrix.
  • An antenna array can be composed of an entire row, an entire column, multiple rows, and multiple columns of antenna array elements.
  • each antenna array actually constitutes a Transceiver Unit (TXRU).
  • TXRU Transceiver Unit
  • Each TXRU can be configured independently. By configuring the amplitude parameters and/or phase parameters of the antenna elements constituting the TXRU, the adjustment of the antenna pattern of the TXRU is realized, and the electromagnetic wave radiation emitted by all the antenna elements in the antenna array forms a narrower beam pointing to a specific spatial direction, That is, beamforming is realized.
  • the TXRU and its antenna elements can be configured in various correspondences, thereby changing the beamforming capabilities and characteristics.
  • a single TXRU can only contain a single row or single column of antenna elements, the so-called one-dimensional TXRU.
  • the TXRU can only adjust the beam direction in one dimension; a single TXRU can also contain multiple rows or multiple columns
  • the antenna array element, the so-called two-dimensional TXRU, at this time, the TXRU can adjust the beam direction in two dimensions, horizontal and vertical.
  • a row of antenna array elements can form multiple TXRUs, but the configuration method can be a partial connection method, that is, each TXRU only uses part of the antenna array elements to form beams; it can also be a fully connected method, that is , each TXRU can adjust all antenna elements to form beams.
  • one or more TXRUs constitute the antenna ports (Antenna Ports) seen at the system level through logical mapping.
  • the TXRU and the antenna port are equivalent.
  • two or more TXRUs may collectively form an antenna port.
  • Antenna ports can be characterized by reference signals. There is a one-to-one correspondence between antenna ports and their reference signals, and different antenna ports are used to transmit different reference signals.
  • the reference signals include, for example, a synchronization signal block (SSB), a channel state information reference signal (CSI-RS), a sounding reference signal (SRS), and the like.
  • a quasi-co-located (QCL) relationship may exist between different antenna ports.
  • Two antenna ports are considered quasi-co-located if the large-scale properties of the channel carrying the symbols on one antenna port can be inferred from the channel carrying the symbols on the other antenna port.
  • the channel large-scale property parameters estimated from the signal at antenna port A are also suitable for the signal at antenna port B when, for example, a QCL relationship is satisfied between antenna port A and antenna port B.
  • the large-scale properties include at least one of the following: delay spread, Doppler spread, Doppler shift, average gain, average delay, and spatial reception parameters.
  • antenna port A and antenna port B have a QCL relationship with respect to spatial reception parameters, the receiving end can use the same spatial reception parameters to realize the reception of signals on these two antenna ports.
  • the term "spatial reception parameters" includes beamforming parameters for receiving electromagnetic wave radiation signals formed into beams from a particular spatial direction.
  • the beamforming parameters may include, for example, phase parameters and/or amplitude parameters of antenna elements of the antenna array. According to the corresponding beamforming parameters, the electromagnetic wave radiation emitted by the antenna element is combined into a desired beam in space.
  • An antenna array configured with specific spatial reception parameters can achieve optimal reception of beam signals from corresponding spatial directions.
  • Spatial receive parameters can be embodied as spatial domain receive filters. It should be understood that in this disclosure, “spatial reception parameter” may be used interchangeably with the "receive beam” it forms.
  • the term “spatial transmit parameters” includes beamforming parameters used to form transmit beams directed towards a particular spatial direction.
  • the spatial transmit parameters can be embodied as spatial domain transmit filters. Also, in this disclosure, "spatial transmit parameter” may be used interchangeably with the "transmit beam” it forms.
  • the radiated energy can be mainly concentrated in a specific direction to combat path loss.
  • the base station and UE need to have the ability to form many beams directed at different points, and select a transmit beam or a receive beam from among these beams that matches the channel direction as closely as possible before using the beams for transmit and receive, i.e., in On the transmitter side, the transmit beam is aligned with the channel launch angle, and on the receiver side, the receive beam is aligned with the channel arrival angle.
  • the base station and the UE can perform beam selection through beam training.
  • Beam training generally includes processes such as beam measurement, beam reporting, and beam indication.
  • the base station 1000 may use n t_DL (n t_DL ⁇ 1) downlink transmit beams with different directions, and the UE 1004 may use n r_DL (n r_DL ⁇ 1) downlink receive beams with different directions.
  • the base station 1000 may also use n r_UL (n r_UL ⁇ ) uplink receive beams with different directions, and the UE 1004 may also use nt_UL (n t_UL ⁇ 1) uplink transmit beams with different directions.
  • the number of uplink receive beams and downlink transmit beams 1002 of the base station 1000 and the coverage of each beam are the same, the number of uplink transmit beams and downlink receive beams 1006 of the UE 1004 and the coverage of each beam are the same, It should be understood, however, that this is only an example, and the number and coverage of beams used by the base station and the UE may vary.
  • the base station 1000 and the UE 1004 traverse all transmit beam-receive beam combinations by scanning beams. Taking the downlink beam scan as an example, first, the base station 1000 sends n r_DL downlink reference signals to the UE 1004 through each of its nt_DL transmit beams according to the downlink scan period.
  • the nt_DL transmit beams may be from the base station 1000 beamforming codebook. In this way, the nt_DL transmit beams of the base station 1000 transmit nt_DL ⁇ nr_DL downlink reference signals to the UE 1004 in sequence.
  • Reference signal resources that can be utilized by the base station 1000 include, for example, non-zero power CSI-RS (NZP-CSI-RS) resources or SSB resources.
  • the UE 1004 receives each transmit beam separately through its nr_DL receive beams 1006 and measures the beam signal. For example, the UE 1004 may measure nt_DL downlink reference signals carried in each transmit beam, ie, measure nt_DL ⁇ nr_DL downlink reference signals in total. For example, UE 1004 may measure reference signal received power (L1-RSRP), reference signal received quality (L1-RSRQ), signal-to-interference-plus-noise ratio (L1-SINR), etc. of the physical layer (L1).
  • L1-RSRP reference signal received power
  • L1-RSRQ reference signal received quality
  • L1-SINR signal-to-interference-plus-noise ratio
  • the UE 1004 reports the beam measurement result to the base station 1000 .
  • the UE 1004 may be configured to report only a portion of the transmit beams (eg, only Nr ⁇ n t_DL , Nr is preconfigured by the base station 1000 ) beam measurement results and associated reference signal identification information, such as CSI - RS resource indicator CRI or SSB resource indicator SSBRI). Due to the correspondence between reference signals and transmit and receive beams, each reference signal represents a pair of transmit beam-receive beam.
  • the base station 1000 can select the best transmit beam from the transmit beams reported by the UE 1004 for downlink transmission with the UE 1004.
  • the base station 1000 may select the transmit beam corresponding to the reference signal with the best measurement result as the best transmit beam, and the transmit beam direction generally best matches the channel direction and corresponds to the corresponding spatial transmit parameter.
  • the base station 1000 instructs the UE 1004 the reference signal corresponding to the optimal transmit beam, so that the UE 1004 can determine the receive beam corresponding to the reference signal as the best transmit beam during the beam scanning process Best receive beam for beam matching. This receive beam achieves the best reception for the best transmit beam and its direction generally best matches the channel direction. After that, the base station 1000 and the UE 1004 can use the determined optimal transmit beam and optimal receive beam for downlink transmission.
  • UE 1004 sends nr_UL uplink reference signals to base station 1000 through each of its nt_UL transmit beams.
  • the base station 1000 has a total of n t_UL ⁇ n r_UL uplink reference signals through its n r_UL receive beams.
  • the base station 1000 measures the n t_UL ⁇ n r_UL uplink reference signals, such as measuring L1-RSRP, L1-RSRQ, L1-SINR, etc., so as to determine the optimal uplink transmit beam of the UE 1004 and the optimal uplink transmission beam of the base station 1000 The best upstream receive beam for transmit beam matching.
  • the base station 1000 indicates the corresponding reference signal to the UE 1004, so that the UE 1004 can use the determined optimal transmit beam for uplink transmission.
  • the existing transmit beam-receive beam pair may no longer be adapted to the radio channel direction.
  • the above beam training process can be repeated to update the transmit beam-receive beam pair.
  • the base station 1000 may send the DCI indicating the selected beam to the UE 1004 through the Physical Downlink Control Channel (PDCCH), thereby The UE 1004 may adjust (or update) the downlink receive beam for PDSCH or the uplink transmit beam for PUSCH.
  • PDSCH Physical Downlink Shared Channel
  • PUSCH Physical Uplink Shared Channel
  • the base station 1000 can send a MAC CE indicating the selected beam to the UE 1004 through the PDSCH, so that the UE 1004 can update the downlink receive beam for the PDCCH Or the uplink transmit beam for PUCCH.
  • a MAC CE indicating the selected beam to the UE 1004 through the PDSCH, so that the UE 1004 can update the downlink receive beam for the PDCCH Or the uplink transmit beam for PUCCH.
  • the spatial position relationship of the UE relative to the base station is certain. That is, in many scenarios, the state of the data channel is similar to that of the control channel, so its beam may also be suitable for the control channel, and vice versa.
  • the beam used for the uplink channel can also be used for the downlink channel.
  • the UE uses the spatial reception parameter corresponding to the downlink receive beam to determine the spatial transmission parameter corresponding to the uplink transmit beam. , or vice versa; at the same time, the base station uses the spatial transmit parameters corresponding to the downlink transmit beams to determine the spatial receive parameters corresponding to the uplink receive beams, or vice versa.
  • beam sharing refers to the transmission of two or more channels or signals using the same beam or beams that are symmetrical for both uplink and downlink.
  • FIG. 2 illustrates a schematic diagram of beam sharing according to the first embodiment.
  • the first embodiment relates to DCI-based downlink beam indication.
  • DCI is carried by PDCCH, which contains information such as DCI format identifier, carrier indicator, bandwidth part (BWP) indicator, etc., and also contains time-frequency resource information (such as frequency domain resource allocation field, time domain resource allocation field, etc.) allocated to PDSCH ).
  • PDCCH contains information such as DCI format identifier, carrier indicator, bandwidth part (BWP) indicator, etc., and also contains time-frequency resource information (such as frequency domain resource allocation field, time domain resource allocation field, etc.) allocated to PDSCH ).
  • the PDCCH carrying DCI itself occupies a control resource set (for example, CORESET #0 illustrated in Figure 2), and the beam used for the PDCCH is activated by the base station using the MAC CE in the unit of CORESET, and the following embodiments will introduce the control channel beam indication details. As shown in FIG.
  • the PDCCH (CORESET#0) that schedules the PDSCH uses beam Beam#0.
  • the base station beam and UE beam used for transmission of a certain channel are sometimes collectively referred to as the beam used for the channel.
  • the downlink receive beams for receiving the PDCCH are all represented by Beam#0, the pair of transmit and receive beams are matched to each other and are characterized by the same reference signal (ie, the reference signal associated with Beam#0).
  • the DCI may also include information of beams scheduled for PDSCH.
  • the beams scheduled for use with the PDSCH may be determined through the beam scanning process described above in order to adapt to the current wireless channel environment.
  • beam indication for PDSCH can be achieved by setting a Transmission Configuration Indication (TCI) state in the DCI.
  • TCI Transmission Configuration Indication
  • FIG. 3 is a configuration diagram illustrating a TCI state.
  • TCI states are identified by TCI state IDs.
  • Each TCI state contains parameters for configuring a quasi-co-located (QCL) relationship between one or two downlink reference signals and the DMRS ports of the PDCCH or PDSCH.
  • QCL quasi-co-located
  • the first downlink reference signal this quasi-co-location relationship is configured by the RRC layer parameter qcl-Type1.
  • the quasi-co-location relationship is configured by optional qcl-Type2.
  • the qcl-Type1 or qcl-Type2 parameter includes the following information:
  • Serving Cell Index (ServCellIndex), which represents the applicable serving cell
  • BWP-Id Bandwidth Part ID
  • reference Signal which represents the reference signal resource providing QCL information, including the NZP-CSI-RS resource identified by NZP-CSI-RS-ResoureId and the SSB resource identified by SSB-Index;
  • the type of QCL involved in the TCI state qcl-Type can include the following options: – "typeA”: on ⁇ Doppler shift, Doppler spread, average delay, delay spread ⁇ ; – “typeB”: on ⁇ Doppler shift, Doppler spread ⁇ ; – “typeC”: on ⁇ Doppler shift, average delay ⁇ ; – “typeD”: on ⁇ spatial reception parameters ⁇ .
  • each TCI state is generally allowed to contain only one QCL hypothesis of type "typeD”.
  • the base station may send a MAC CE to the UE through the PDSCH to activate up to 8 TCI states in the TCI state pool configured for the UE.
  • FIG. 4 illustrates the format of the MAC CE (excluding the header) for activating the TCI state.
  • the "CORESET Pool ID” field indicates the CORESET pool where the PDCCH is located, which occupies 1 bit;
  • the "Serving Cell ID” indicates the serving cell to which the MAC CE is applicable, which occupies 5 bits;
  • BWP ID Indicates the part of the downlink bandwidth applicable to the MAC CE, which occupies 2 bits;
  • T i represents the activation information of the configured TCI state pool, which occupies 1 bit. If it is set to 1, it means that the corresponding TCI state is Activated, otherwise it indicates that the corresponding TCI state is not activated.
  • the base station can indicate the beam scheduled for PDSCH by specifying a TCI status in the DCI.
  • FIG. 5 illustrates DCI formats that can be used to specify TCI states, such as DCI formats 1_1 or 1_2 specified by 3GPP R16.
  • DCI may also include an identification field of TCI state, which occupies 3 bits to indicate that at most 8 TCI states are activated one of.
  • the UE On the UE side, when such DCI is received on the PDCCH, the UE extracts the identification field of the TCI state from it, finds the corresponding TCI state, and makes the following QCL assumptions: the antenna port of the reference signal listed in the TCI state is the same as the There is a QCL relationship with respect to the spatial reception parameters for the antenna ports of the transport channel or reference signal indicated by the TCI state, so that the spatial reception parameters (ie, beams) used for the former will be available for the latter.
  • the spatial reception parameters ie, beams
  • the base station determines that the beam scheduled for PDSCH is Beam#1, which may be the beam with the best transmission performance in the beam scan.
  • the base station may indicate a TCI state in the DCI, where the TCI state contains QCL information on the reference signal associated with Beam#1.
  • the UE On the UE side, the UE firstly uses the beam Beam#0 (downlink receive beam) corresponding to CORESET#0 to blindly detect the PDCCH in order to receive the DCI carried in it. If the DCI is successfully received, the UE extracts various scheduling information on the PDSCH, such as time-frequency resource information and the like. In particular, the UE can find the TCI status indicated in the DCI and understand that the beam indicated by this TCI status (ie Beam#1) should be used as the beam to receive the scheduled PDSCH, ie, the same as the reference signal contained in the TCI status Associated downlink receive beams.
  • the base station does not know whether the transmitted DCI has been successfully received by the UE, and thus does not know whether the UE has updated the beam for receiving the PDSCH.
  • the UE may use an implicit way to feed back whether the UE has received the DCI and whether the beam used for the PDSCH has been successfully updated.
  • the base station uses the downlink transmit beam of Beam#1 to transmit the PDSCH, and the UE uses the downlink receive beam of Beam#1 to receive and decode the PDSCH. If decoding is correct, positive feedback (ACK) is sent to the base station through PUCCH, otherwise negative feedback (NACK) is sent. In response to receiving the ACK, the base station will know that the UE has updated the PDSCH's beam to Beam#1 and the reliability of Beam#1 is verified.
  • ACK positive feedback
  • NACK negative feedback
  • the base station and the UE may share the beam for the PDSCH to other channels. This is because the successful transmission of PDSCH indicates that its beam is of the best quality in terms of timeliness. Therefore, according to the first embodiment of the present disclosure, the base station and the UE may, for example, update the beam Beam#0 that schedules the PDCCH (CORESET#0) of the PDSCH to Beam#1.
  • the beam update of the PDCCH can be performed spontaneously on the base station and the UE side, that is, the UE performs the update of the downlink receive beam of the PDCCH after a certain time interval after the PDSCH is correctly decoded. After a certain time interval after the ACK, the update of the downlink transmit beam of the PDCCH is performed, thereby omitting the signaling overhead and time delay dedicated to the beam update of the PDCCH.
  • the base station uses CORESET#0 to schedule PDSCH again, the base station will be able to use the updated Beam#1 to send the PDCCH carrying the DCI, and the UE will be able to use the updated Beam#1 to receive the DCI.
  • the UE will send a NACK to the base station, so that both the base station and the UE can know that the downlink data transmission is unsuccessful, and the reason may be the scheduled Beam# 1
  • the quality has deteriorated or has been blocked to a certain extent, i.e. the reliability of Beam#1 has not been verified. Therefore, the base station and the UE do not update the beam of the PDCCH temporarily.
  • the base station may perform rescheduling of the PDSCH content, that is, using Beam#0 again to send another DCI, this DCI including the reallocated time-frequency resources and beams.
  • this DCI including the reallocated time-frequency resources and beams.
  • the beam indicated in the DCI may be the previous beam Beam#1, or may be a new beam. The subsequent process is similar to that described above, and will not be repeated here. If the rescheduled PDSCH is decoded correctly, the base station and UE can still update the beam used for the PDCCH to the beam indicated in the DCI.
  • the beam of the PDCCH can follow the beam of the PDSCH, thereby realizing beam sharing between the two channels.
  • DCI-based PDSCH scheduling is described above as an example, DCI can also trigger or schedule downlink reference signals, such as CSI-RS, etc. Therefore, the first embodiment can also implement PDCCH and downlink reference signals The principle of beam sharing between them is similar and will not be repeated here.
  • FIG. 6 shows a schematic diagram of beam sharing according to the second embodiment.
  • the second embodiment relates to DCI based uplink beam indication.
  • the UE may request the base station to schedule resources for PUSCH transmission by sending a scheduling request (SR) or a buffer status report (BSR) to the base station.
  • SR scheduling request
  • BSR buffer status report
  • the base station may allocate time-frequency resources according to the amount of data to be transmitted by the UE, and determine the beam for the PUSCH. For example, the beams scheduled for use by the PUSCH may be determined through the beam scanning process described above in order to adapt to the current wireless channel environment.
  • the base station may schedule the PUSCH by sending DCI, and the available DCI here may be, for example, DCI format 0_1.
  • the DCI contains information such as a DCI format identifier, a carrier indicator, a bandwidth part (BWP) indicator, etc., and also contains time-frequency resource information (such as a frequency-domain resource assignment field, a time-domain resource allocation field, etc.) allocated to the PUSCH assignment field) and beam information.
  • the PDCCH carrying DCI itself occupies one control resource set (eg CORESET #0 illustrated in FIG. 6 ), assuming that the beam activated for the PDCCH on CORESET #0 is Beam #0.
  • the base station may determine a beam for PUSCH, such as Beam#1 shown in FIG. 6, through, for example, the beam scanning procedure described above, which may be the beam with the best transmission performance during the beam scanning procedure.
  • the base station may indicate a TCI state in the DCI, which contains QCL information about the reference signal associated with Beam#1, and send the DCI to the UE using Beam#0 (downlink transmit beam).
  • the UE On the UE side, the UE firstly uses the beam Beam#0 (downlink receive beam) corresponding to CORESET#0 to blindly detect the PDCCH in order to receive the DCI carried in it. If the DCI is successfully received, the UE extracts various scheduling information on the PUSCH, such as time-frequency resource information and the like. In particular, the UE can find the TCI status indicated in the DCI and understand that the beam indicated by this TCI status (ie Beam#1) should be used as the beam for transmitting the scheduled PUSCH, ie, in conjunction with the reference signal contained in the TCI status The associated upstream transmit beam.
  • the beam Beam#0 downlink receive beam
  • the UE extracts various scheduling information on the PUSCH, such as time-frequency resource information and the like.
  • the UE can find the TCI status indicated in the DCI and understand that the beam indicated by this TCI status (ie Beam#1) should be used as the beam for transmitting the scheduled PUSCH, ie, in conjunction
  • the UE does not need to perform HARQ feedback on the reception of the DCI, but directly transmits the PUSCH by using the uplink transmit beam of Beam #1 on the time-frequency resources scheduled by the DCI.
  • the base station uses the uplink receive beam of Beam#1 to receive and decode the PUSCH.
  • the base station does not send explicit HARQ feedback for PUSCH to the UE.
  • the base station will continue to schedule the next PUSCH of the UE to implicitly confirm that the PUSCH has been successfully received this time.
  • the next PUSCH scheduling can be performed through the PDCCH on the original CORESET#0, and the DCI used to schedule the next PUSCH is still transmitted through Beam#0 at this time.
  • the next PUSCH scheduling may also be performed through PDCCHs on other CORESETs, and at this time, the DCI for scheduling the next PUSCH scheduling may be transmitted through the beam associated with the corresponding CORESET.
  • the DCI used to schedule the next PUSCH needs to include the same HARQ process ID and the reversed New Data Indicator (NDI) field. For example, if the value assigned to this PUSCH is '0', Then the next PUSCH should be assigned '1', so the UE will know that the previous PUSCH transmission has been correctly received and decoded, and can use the same HARQ process for new uplink data transmission.
  • NDI New Data Indicator
  • both the base station and the UE can confirm that the PUSCH transmission using the updated beam Beam#1 in FIG. 6 is successful, that is, the beam update of the PUSCH on both the base station and the UE side has been completed, and The reliability of Beam#1 is proven.
  • the base station and the UE may share the beam used for the PUSCH to other channels, because the successful transmission of the PUSCH indicates that the beam has the best quality in terms of timeliness. Therefore, according to the second embodiment of the present disclosure, the base station and the UE may, for example, update the beam Beam#0 that schedules the PDCCH (CORESET#0) of the PUSCH to Beam#1.
  • the symmetry of the uplink and downlink channels of PUSCH and PDCCH is considered here, that is, the UE can use the uplink transmit beam of PUSCH as the downlink receive beam of PDCCH, and the base station can use the uplink receive beam of PUSCH as the downlink transmit beam of PDCCH.
  • the beam update of the PDCCH can be performed autonomously at the base station and the UE side, thereby omitting the signaling overhead and delay dedicated to the beam update of the PDCCH.
  • the base station uses CORESET#0 to schedule the PUSCH again, the base station will be able to use the updated Beam#1 to send the PDCCH carrying the DCI, and the UE will be able to use the updated Beam#1 to receive the DCI.
  • the base station may reschedule the PUSCH as an implicit negative feedback.
  • the base station uses Beam#0 to send another DCI again.
  • This DCI contains the reallocated time-frequency resources and beams.
  • the beam indicated in the DCI can be the previous beam Beam#1, or it can be new beam.
  • the same HARQ process ID and non-inverted NDI are included in the DCI of the rescheduled PUSCH to command the UE to perform data retransmission. At this point, both the base station and the UE know that the previous uplink data transmission was unsuccessful.
  • the reason may be that the quality of the scheduled Beam#1 has deteriorated or been blocked to a certain extent, that is, the reliability of the Beam#1 has not been verified. Therefore, the base station and the UE do not update the beam of the PDCCH temporarily.
  • the base station and UE can still update the beam used for the PDCCH to the beam indicated in the DCI.
  • spatial relation information can also be used to indicate the beam used for PUSCH. Similar to the TCI state, the spatial relationship information also includes identification information of the reference signal with which the indicated transport channel (or reference signal) should have a QCL relationship, such as SSB_Index, NZP-CSI-RS-ResourceId or SRS-ResourceId, etc. Spatial relationship information and TCI state are qualitatively and functionally identical and can be used interchangeably where applicable.
  • the beam of the PDCCH can follow the beam of the PUSCH, thereby realizing beam sharing between the two channels.
  • the DCI-based PUSCH scheduling is described above as an example, the DCI can also trigger or schedule uplink reference signals, such as SRS, etc. Therefore, the first embodiment can also realize the connection between the PDCCH and the uplink reference signal.
  • the beam sharing principle is similar and will not be repeated here.
  • the DCI involved in the first and second embodiments above has the function of data scheduling. However, other formats of DCI may not perform any data scheduling, but only play a signaling role.
  • the third embodiment of the present disclosure will ignore data scheduling of DCI, and instead use dynamic signaling of DCI to implement beam indication.
  • FIG. 7A shows a schematic diagram of an example of beam sharing according to the third embodiment.
  • the base station may transmit DCI over the PDCCH on CORESET #0 to indicate a beam for the PDCCH on another CORESET (eg, CORESET #1 illustrated in FIG. 7A ). It is assumed that the beam activated for the PDCCH on CORESET#0 is Beam#0.
  • the base station may determine the beam used for the PDCCH on CORESET #1 through, for example, the beam scanning process described above, such as Beam #1 shown in FIG. 7A, which may be the one with the best transmission performance in the beam scanning beam.
  • the base station may include in the DCI a TCI state that includes QCL information about the reference signal associated with Beam#1.
  • the identification information of CORESET#1 may also be included in the DCI, so that the UE knows that Beam#1 is indicated to this CORESET.
  • the UE On the UE side, the UE firstly uses the beam Beam#0 (downlink receive beam) corresponding to CORESET#0 to blindly detect the PDCCH in order to receive the DCI carried in it. If the DCI is successfully received, the UE finds the TCI status contained therein and understands that the beam indicated by the TCI status (ie Beam#1) should be used as the beam to receive the PDCCH on CORESET#1.
  • Beam#0 downlink receive beam
  • the UE finds the TCI status contained therein and understands that the beam indicated by the TCI status (ie Beam#1) should be used as the beam to receive the PDCCH on CORESET#1.
  • the UE uses a HARQ mechanism to inform the base station whether the DCI is correctly received. In one example, if the UE decodes the DCI correctly, an ACK is sent to the base station, otherwise a NACK is sent to the base station. In another example, the UE only sends a NACK to the base station when the DCI is not correctly decoded, and does not send feedback to the base station when the DCI is correctly decoded. If the base station does not receive a NACK within a certain time interval after sending the DCI, Then the base station confirms that the DCI has been correctly received.
  • both the base station and the UE can know that the beam indication undertaken by the DCI has succeeded, thereby completing the beam update of the PDCCH on CORESET#1. That is, the base station updates the downlink transmit beam of CORESET#1 to Beam#1 (downlink transmit beam), and the UE updates the downlink receive beam of CORESET#1 to Beam#1 (downlink receive beam).
  • the base station and the UE in response to the completion of the beam update of the PDCCH, can realize beam sharing between the PDCCH and its scheduled PDSCH. Specifically, as shown in FIG. 7A, the base station and the UE may adjust the beam for PDSCH to Beam#1. In this way, the beam of the PDSCH can follow the beam of the PDCCH. It should be understood that, in addition to the PDSCH, the third embodiment can also implement beam sharing between the PDCCH and downlink reference signals such as CSI-RS, and the principles are similar, which will not be repeated here.
  • FIG. 7B shows a schematic diagram of another example of beam sharing according to the third embodiment.
  • the base station may transmit DCI through the PDCCH on CORESET #0 to indicate the beam used for the PUCCH. It is assumed that the beam activated for the PDCCH on CORESET#0 is Beam#0.
  • the base station may determine a beam for PUCCH through, for example, the beam scanning process described above, such as Beam #1 shown in FIG. 7B , which may be the beam with the best transmission performance in the beam scanning.
  • the base station may include the PUCCH spatial relationship information with beam indication function in the DCI.
  • FIG. 8 shows a schematic diagram of the configuration of PUCCH spatial relationship information.
  • the PUCCH spatial relationship information is identified by the PUCCH spatial relationship information ID (PUCCH-SpatialRelationInfoId), which includes reference signal resources associated with Beam#1, such as NZP-CSI-RS-ResoureId identified by NZP- CSI-RS resource, SSB resource identified by SSB-Index, and SRS resource jointly identified by SRS-ResourceId and BWP-Id.
  • PUCCH-SpatialRelationInfoId PUCCH spatial relationship information ID
  • the UE shall transmit the PUCCH using the spatial reception parameters for receiving the SSB or NZP-CSI-RS. If the SRS is configured in the PUCCH spatial relationship information, the UE shall transmit the PUCCH using the spatial transmission parameters used to transmit the SRS.
  • the DCI may further include identification information of the PUCCH resource, so that the UE knows that Beam#1 is indicated to this PUCCH resource.
  • the UE On the UE side, the UE firstly uses the beam Beam#0 (downlink receive beam) corresponding to CORESET#0 to blindly detect the PDCCH in order to receive the DCI carried in it. If the DCI is successfully received, the UE finds the included PUCCH spatial relationship information from it, and understands that the beam indicated by the PUCCH spatial relationship information (ie, Beam#1) should be used as the beam for transmitting PUCCH.
  • Beam#0 downlink receive beam
  • Beam#1 downlink receive beam
  • the UE uses the HARQ mechanism to inform the base station whether the DCI is correctly received. In one example, if the UE decodes the DCI correctly, an ACK is sent to the base station, otherwise a NACK is sent to the base station. In another example, the UE only sends a NACK to the base station when the DCI is not correctly decoded, and does not send feedback to the base station when the DCI is correctly decoded, if the base station does not receive a NACK within a certain time interval after sending the DCI , the base station confirms that the DCI has been correctly received.
  • the UE since the HARQ feedback is transmitted through the PUCCH or PUSCH, it may be considered that the UE uses the beam (Beam #1) indicated in the DCI to transmit the PUCCH or PUSCH, so as to verify the reliability of the beam.
  • Beam #1 the beam indicated in the DCI
  • both the base station and the UE can know that the beam indication undertaken by the DCI has succeeded, thereby completing the beam update of the corresponding PUCCH. That is, the base station updates the uplink receive beam of the PUCCH to Beam#1 (uplink receive beam), and the UE updates the uplink transmit beam of CORESET#1 to Beam#1 (uplink transmit beam).
  • the base station and the UE in response to the completion of the beam update of the PUCCH, can realize beam sharing between the PUCCH and the PUSCH in the same uplink direction. Specifically, as shown in FIG. 7B, the base station and the UE may adjust the beam for PUSCH to Beam#1. In this way, the beam of the PUSCH can follow the beam of the PUCCH.
  • the above-mentioned TCI status can also be used to indicate the beam used for PUSCH. Spatial relationship information and TCI status may be used interchangeably where applicable.
  • the beam of the uplink reference signal such as the SRS can also be updated with the beam of the PUCCH to realize beam sharing between them.
  • the principle is similar, and details are not repeated here.
  • the fourth embodiment of the present disclosure relates to beam sharing between control channels and downlink channels/reference signals based on MAC CE indication.
  • the base station configures a TCI state pool for the UE through RRC signaling, wherein the TCI state pool is configured in units of BWP, including at most M (M is configured by the base station, eg, 64 or 128) TCI states.
  • the base station may determine a TCI state associated with the beam from a configured TCI state pool, and send a MAC including identification information of the TCI state to the UE through the PDSCH CE.
  • FIG 10 shows the format of a MAC CE for TCI state activation of PDCCH (excluding header).
  • Server Cell ID indicates the serving cell to which the MAC CE is applicable, which occupies 5 bits
  • CORESET ID indicates the CORESET where the PDCCH is located, which occupies 4 bits
  • TCI Status ID indicates the same The TCI status associated with the beam determined for the PDCCH occupies 7 bits.
  • FIG. 9 shows a schematic diagram of beam sharing according to the fourth embodiment.
  • the pool of TCI states configured for the UE in BWP A of component carrier CC1 is illustrated in Figure 9, where the black balls represent exemplary TCI states.
  • the base station can activate or update the beam for the PDCCH on CORESET#X by indicating the TCI status 54 in the MAC CE.
  • the UE may feed back an ACK to the base station and update the beam used for CORESET #X to the beam indicated in TCI state 54, i.e., the beam that will be used to receive PDCCH on CORESET #X.
  • the downlink receive beam is updated to the beam associated with the reference signal contained in the TCI state 54 .
  • the UE can update the PDSCH beam scheduled by the PDCCH to the beam indicated in the TCI state 54, and correspondingly, the base station updates the PDSCH transmission beam (downlink transmission beam) to the PDCCH transmission beam.
  • the base station and the UE synchronize the beam shared between the PDCCH and the PDSCH.
  • the above MAC CE can also be used to implement beam sharing between the PDCCH on CORESET#Y and its scheduled periodic/semi-static downlink reference signal (eg P/SP CSI-RS), or on CORESET#Y Beam sharing between the PDCCH and its scheduled aperiodic downlink reference signals (such as AP CSI-RS).
  • periodic/semi-static downlink reference signal eg P/SP CSI-RS
  • CORESET#Y Beam sharing between the PDCCH and its scheduled aperiodic downlink reference signals such as AP CSI-RS.
  • the MAC CE may also activate TCI state 18, thereby implementing CORESET#Z in another BWP of CC 1 (eg BWP B shown in Figure 9) and its scheduled PDSCH and/or CSI - Beam sharing between RSs, or enabling beam sharing between CORESET#A in another CC (eg CC 2 shown in Figure 9) and its scheduled PDSCH and/or CSI-RS.
  • CC Component Carrier
  • the UE may be preconfigured with a list of CORESETs associated with them. For example, the base station may pre-configure the association between TCI state 18 and CORESET#Z, CORESET#A, so that the UE can understand the beam indication purpose of MAC CE, even if CORESET#Z, CORESET#A belong to different BWPs or CCs.
  • the fifth embodiment of the present disclosure relates to beam sharing between MAC CE based control channels and uplink channels/reference signals.
  • FIG. 11 shows a schematic diagram of beam sharing according to the fifth embodiment.
  • the base station may indicate TCI status 54 in the MAC CE to activate the PDCCH on CORESET#X.
  • the UE may feed back an ACK to the base station and update the beam of CORESET #X to the beam indicated in TCI state 54.
  • the UE can update the beam (uplink transmit beam) of the PUSCH scheduled by the PDCCH to the beam indicated in the TCI state 54, and the base station also updates the beam for transmitting PUSCH (uplink receive beam) to the beam for transmitting PDCCH.
  • the base station and the UE synchronize the beam shared between the PDCCH and the PDSCH.
  • the above-mentioned MAC CE can also be used to realize beam sharing between the PDCCH (CORESET#X) and its scheduled aperiodic uplink reference signal (for example, AP SRS).
  • the PDCCH CORESET#X
  • its scheduled aperiodic uplink reference signal for example, AP SRS
  • FIG. 12 shows the format (excluding the header) of a MAC CE for TCI state activation of PUCCH.
  • R represents a reserved field, which occupies 1 bit
  • Server cell ID represents a serving cell to which the MAC CE is applicable, which occupies 4 bits
  • BWP ID represents the location where the PUCCH resource is located CORESET, which occupies 3 bits
  • PUCCH resource ID indicates the PUCCH resource
  • the base station can activate or update the beam for PUCCH on PUCCH resource #Y by indicating TCI status 54 in the MAC CE.
  • the base station and UE can update the beam that is also the PUSCH in the uplink direction to the beam indicated in the MAC CE, thereby realizing beam sharing between PUCCH and PUSCH.
  • PUCCH resource #Y PUCCH resource #Y
  • periodic/semi-static uplink reference signals eg P/SP SRS
  • the MAC CE may also activate the TCI state 18, thereby enabling PUCCH resource #Z in another BWP of CC 1 (eg, BWP B shown in Figure 11) with its scheduled PUSCH and/or Beam sharing between SRSs, or enabling beam sharing between CORESET#A in another CC (eg, CC 2 shown in Figure 11 ) and its scheduled PUSCH and/or SRS.
  • the UE may be pre-configured with a list of CORESET and/or PUCCH resources associated therewith. For example, the base station may pre-configure the association between TCI state 18 and PUCCH resource #Z, CORESET #A, so that the UE can understand the purpose of beam indication of MAC CE.
  • the above first to fifth embodiments have described examples of beam sharing according to the present disclosure.
  • the present disclosure aims to realize beam sharing between various transmission channels and reference signals, and is not limited to the sharing combination in the above embodiments.
  • the above-mentioned two or more channels or reference signals of a shared beam refer to channels or signals within the same transmission reception point (TRP).
  • FIG. 13A is a block diagram illustrating an electronic device 1000 according to the present disclosure.
  • the electronic device 1000 may be a base station device or a component thereof.
  • electronic device 1000 includes processing circuit 1001 .
  • the processing circuit 1001 includes at least a beam determining unit 1002 , a beam indicating unit 1003 and a beam updating unit 1004 .
  • the processing circuit 1001 may be configured to perform the communication method shown in FIG. 13B.
  • the beam determination unit 1002 in the processing circuit 1001 is configured to determine the first beam used for the first transmission channel between the base station and the UE, ie to perform step S1001 in FIG. 13B .
  • the beam determination unit 1002 may, for example, select a beam with the best transmission quality from a set of candidate beams as the first beam through a beam scanning process.
  • the beam indication unit 1003 is configured to send dynamic signaling including beam indication information about the first beam to the UE, so that the beam used for the first transmission channel is updated to the first beam, that is, the steps in FIG. 13B are performed S1002.
  • the beam indication unit 1003 can send beam indication information through MAC CE or DCI.
  • the beam indication information may be TCI status or spatial relationship information associated with the first beam determined by the beam determination unit 1002 .
  • the UE may use the beam indication information to update the beam used for the first transport channel.
  • the beam update unit 1004 is configured to update the beam used for the second transmission channel and/or the reference signal between the base station and the UE to the first beam if the update of the beam used for the first transmission channel is successful, that is Step S1003 in FIG. 13B is performed.
  • the beam update unit 1004 may perform beam update of the second transmission channel or reference signal when receiving explicit positive feedback from the UE for the dynamic signaling sent by the beam indicating unit 1003 or not receiving explicit negative feedback.
  • the beam update unit 1003 may perform beam update of the second transmission channel or the reference signal when the transmission of the first transmission channel using the first beam is successful.
  • the electronic device 1000 may also include, for example, a communication unit 1005 and a memory 1006 .
  • the communication unit 1005 may be configured to communicate with a UE device (eg, the electronic device 2000 to be described below) under the control of the processing circuit 1001 .
  • the communication unit 1005 may be implemented as a transmitter or transceiver, including communication components such as antenna arrays and/or radio frequency links.
  • the communication unit 1005 is drawn with a dashed line, as it can also be located outside the electronic device 1000 .
  • Electronic device 1000 may also include memory 1006 .
  • the memory 1006 may store various data and instructions, programs and data for the operation of the electronic device 1000, various data generated by the processing circuit 1001, data received by the communication unit 1005, and the like.
  • FIG. 14A is a block diagram illustrating an electronic device 2000 according to the present disclosure.
  • the electronic device 2000 may be a UE device or a component thereof.
  • electronic device 2000 includes processing circuit 2001 .
  • the processing circuit 2001 at least includes a beam indication receiving unit 2002 and a beam updating unit 2003 .
  • the processing circuit 2001 may be configured to perform the communication method shown in FIG. 14B.
  • the beam indication receiving unit 2002 of the processing circuit 2001 is configured to receive dynamic signaling including beam indication information about the first beam from the base station, ie to execute step S2001 in FIG. 14B .
  • the first beam is determined for the first transmission channel between the UE and the base station.
  • the dynamic signaling can be DCI or MAC CE, and includes identification information of TCI status or spatial relationship information as beam indication information.
  • the beam update unit 2003 is configured to update the beam used for the first transmission channel to the first beam indicated by the beam indication information, that is, to perform step S2002 in FIG. 14B .
  • the beam update unit 2003 is further configured to update the beam used for the second transmission channel and/or the reference signal between the UE and the base station to the first beam, That is, step S2002 in FIG. 14B is executed.
  • the beam update unit 2003 may perform beam update of the second transmission channel or reference signal when dynamic signaling is successfully received.
  • the beam update unit 2003 may perform beam update of the second transmission channel or the reference signal when the transmission of the first transmission channel using the first beam is successful.
  • the electronic device 2000 may also include, for example, a communication unit 2005 and a memory 2006 .
  • the communication unit 2005 may be configured to communicate with the base station under the control of the processing circuit 2001 .
  • the communication unit 2005 may be implemented as a transmitter or transceiver, including communication components such as antenna arrays and/or radio frequency links.
  • the communication unit 2005 is drawn with a dashed line, as it can also be located outside the electronic device 2000.
  • Electronic device 2000 may also include memory 2006 .
  • the memory 2006 may store various data and instructions, such as programs and data for the operation of the electronic device 2000, various data generated by the processing circuit 2001, various control signaling or service data to be sent by the communication unit 2005, and the like.
  • the memory 2006 is drawn with a dashed line, as it can also be located within the processing circuit 2001 or outside the electronic device 2000.
  • the units of the electronic devices 1000 and 2000 described in the above embodiments are only logical modules divided according to specific functions implemented by them, rather than being used to limit specific implementations.
  • the above units may be implemented as independent physical entities, or may also be implemented by a single entity (eg, a processor (CPU or DSP, etc.), an integrated circuit, etc.).
  • An electronic device on a base station side comprising: a processing circuit configured to: determine a first beam used for a first transmission channel between the base station and a UE; send information to the UE that includes information about the first beam dynamic signaling of beam indication information for the first transmission channel, so that the beam used for the first transmission channel is updated to the first beam; and if the update of the beam used for the first transmission channel is successful, The beam of the second transmission channel and/or the reference signal between the UEs is updated to the first beam.
  • the dynamic signaling is downlink control information (DCI)
  • DCI downlink control information
  • the first transmission channel is a physical downlink shared channel (PDSCH) or a physical uplink data channel (PUSCH)
  • PUSCH physical uplink data channel
  • the second transport channel is a physical downlink control channel (PDCCH) that schedules the PDSCH or PUSCH.
  • the dynamic signaling includes downlink control information (DCI), and wherein the first transmission channel is a physical downlink control channel (PDCCH) or a physical uplink control channel (PUCCH) , the second transmission channel is a physical downlink shared channel (PDSCH) or a physical uplink data channel (PUSCH).
  • DCI downlink control information
  • the first transmission channel is a physical downlink control channel (PDCCH) or a physical uplink control channel (PUCCH)
  • the second transmission channel is a physical downlink shared channel (PDSCH) or a physical uplink data channel (PUSCH).
  • the dynamic signaling includes a medium access control (MAC) control element (CE), and wherein the first transport channel is a physical downlink control channel (PDCCH), and the first transmission channel is a physical downlink control channel (PDCCH).
  • the second transport channel is the Physical Downlink Shared Channel (PDSCH) scheduled by the PDCCH.
  • the dynamic signaling is a medium access control (MAC) control element (CE)
  • the first transport channel is a physical uplink control channel (PUCCH)
  • the first transmission channel is a physical uplink control channel (PUCCH).
  • the second transport channel is the Physical Uplink Data Channel (PUSCH).
  • processing circuit is further configured to: use the first beam to send the PDSCH or receive the PUSCH; in the case of successful transmission of the PDSCH or PUSCH, Confirm that the update of the beam for the first transmission channel was successful.
  • the first transmission channel includes one of the following: a plurality of transmission channels in a same bandwidth part (BWP), a plurality of transmission channels in a same component carrier (CC) ) multiple transport channels within different BWPs, or multiple transport channels within different CCs.
  • BWP bandwidth part
  • CC component carrier
  • the beam indication information includes transmission configuration indicator (TCI) status or spatial relationship information.
  • TCI transmission configuration indicator
  • An electronic device on the UE side comprising: a processing circuit configured to: receive dynamic signaling including beam indication information about a first beam from a base station, the first beam is determined for the UE and the the first transmission channel between the base stations; updating the beam used for the first transmission channel to the first beam; and if the update of the beam used for the first transmission channel is successful, changing the beam used for the UE and the The beam of the second transmission channel and/or the reference signal between the base stations is updated to the first beam.
  • the dynamic signaling is downlink control information (DCI)
  • DCI downlink control information
  • the first transmission channel is a physical downlink shared channel (PDSCH) or a physical uplink data channel (PUSCH)
  • PUSCH physical uplink data channel
  • the second transport channel is a physical downlink control channel (PDCCH) that schedules the PDSCH or PUSCH.
  • the dynamic signaling is downlink control information (DCI)
  • DCI downlink control information
  • the first transmission channel is a physical downlink control channel (PDCCH) or a physical uplink control channel (PUCCH)
  • the second transmission channel is a physical downlink shared channel (PDSCH) or a physical uplink data channel (PUSCH).
  • the electronic device wherein the dynamic signaling is a medium access control (MAC) control element (CE), and wherein the first transport channel is a physical downlink control channel (PDCCH), and the first transport channel is a physical downlink control channel (PDCCH).
  • the second transport channel is the Physical Downlink Shared Channel (PDSCH) scheduled by the PDCCH.
  • the electronic device wherein the dynamic signaling is a medium access control (MAC) control element (CE), and wherein the first transport channel is a physical uplink control channel (PUCCH), and the first transmission channel is a physical uplink control channel (PUCCH).
  • the second transport channel is the Physical Uplink Data Channel (PUSCH).
  • processing circuit is further configured to: receive the PDSCH or send the PUSCH by using the first beam; in the case that the transmission of the PDSCH or the PUSCH is successful, Confirm that the update of the beam for the first transmission channel was successful.
  • the first transmission channel includes one of the following: multiple transmission channels in the same bandwidth part (BWP), multiple transmission channels in the same component carrier (CC) ) multiple transport channels within different BWPs, or multiple transport channels within different CCs.
  • BWP bandwidth part
  • CC component carrier
  • a communication method comprising: determining a first beam for a first transmission channel between the base station and a UE; sending dynamic signaling including beam indication information about the first beam to the UE, to causing the beam for the first transport channel to be updated to be the first beam; and if the update of the beam for the first transport channel is successful, to be used for the second transport channel between the base station and the UE and/or the beam of the reference signal is updated to the first beam.
  • a communication method comprising: receiving dynamic signaling including beam indication information about a first beam from a base station, the first beam being determined for a first transmission channel between the UE and the base station; updating the beam used for the first transmission channel to the first beam; and if the update of the beam used for the first transmission channel is successful, will be used for the second transmission channel between the UE and the base station and/or Or the beam of the reference signal is updated to the first beam.
  • a non-transitory computer-readable storage medium storing executable instructions which, when executed, implement the communication method as described in 18) or 19).
  • the electronic device 1000 may be implemented as or installed in various base stations, and the electronic device 2000 may be implemented as or installed in various user equipments.
  • Communication methods according to embodiments of the present disclosure may be implemented by various base stations or user equipment; methods and operations according to embodiments of the present disclosure may be embodied as computer-executable instructions, stored in non-transitory computer-readable storage media, and Can be performed by various base stations or user equipment to implement one or more of the functions described above.
  • Techniques according to embodiments of the present disclosure can be made into various computer program products that are used in various base stations or user equipment to implement one or more of the functions described above.
  • the base station used in this disclosure is not limited to the above two kinds of nodes, but serves as an example of a control device on the network side, and has the full breadth of its usual meaning.
  • the base stations mentioned in this disclosure can be implemented as any type of base stations, preferably, such as macro gNB and ng-eNB as defined in the 5G NR standard of 3GPP.
  • a gNB may be a gNB covering a smaller cell than a macro cell, such as pico gNBs, micro gNBs, and home (femto) gNBs.
  • the base station may be implemented as any other type of base station, such as NodeB, eNodeB, and base transceiver station (BTS).
  • the base station may also include a subject configured to control wireless communications and one or more remote radio heads (RRHs), wireless relay stations, drone towers, control nodes in automated factories, etc., located at a different location than the subject.
  • RRHs remote radio heads
  • the term "UE” has the full breadth of its usual meaning, including various terminal devices or in-vehicle devices that communicate with a base station.
  • the UE may be implemented as a mobile terminal such as a smart phone, a tablet personal computer (PC), a notebook PC, a portable game terminal, a portable/dongle type mobile router, and a digital camera or a vehicle-mounted terminal such as a car navigation device.
  • the UE may also be implemented as a terminal performing machine-to-machine (M2M) communication (also known as a machine type communication (MTC) terminal), a drone, sensors and actuators in automated factories, and the like.
  • M2M machine-to-machine
  • MTC machine type communication
  • the user equipment may be a wireless communication module (such as an integrated circuit module comprising a single die) mounted on each of the aforementioned terminals.
  • the base station may be implemented as a gNB 1400.
  • gNB 1400 includes multiple antennas 1410 and base station equipment 1420.
  • the base station apparatus 1420 and each antenna 1410 may be connected to each other via an RF cable.
  • the gNB 1400 (or the base station device 1420) here may correspond to the electronic device 1000 described above.
  • Antenna 1410 includes multiple antenna elements, such as multiple antenna arrays for massive MIMO.
  • the antennas 1410 may, for example, be arranged in an antenna array matrix and used for the base station apparatus 1420 to transmit and receive wireless signals.
  • multiple antennas 1410 may be compatible with multiple frequency bands used by gNB 1400.
  • the base station apparatus 1420 includes a controller 1421 , a memory 1422 , a network interface 1423 , and a wireless communication interface 1425 .
  • the controller 1421 may be, for example, a CPU or a DSP, and operates various functions of a higher layer of the base station apparatus 1420 .
  • the controller 1421 may include the processing circuit 1001 described above, perform the communication method described in FIG. 13B , or control various components of the electronic device 1000 .
  • the controller 1421 generates data packets from the data in the signal processed by the wireless communication interface 1425, and communicates the generated packets via the network interface 1423.
  • the controller 1421 may bundle data from a plurality of baseband processors to generate a bundled packet, and deliver the generated bundled packet.
  • the controller 1421 may have logical functions to perform controls such as radio resource control, radio bearer control, mobility management, admission control, and scheduling. This control can be performed in conjunction with nearby gNB or core network nodes.
  • the memory 1422 includes RAM and ROM, and stores programs executed by the controller 1421 and various types of control data such as a terminal list, transmission power data, and scheduling data.
  • the network interface 1423 is a communication interface for connecting the base station apparatus 1420 to the core network 1424 (eg, a 5G core network).
  • the controller 1421 may communicate with core network nodes or further gNBs via the network interface 1423 .
  • gNB 1400 and core network nodes or other gNBs may be connected to each other through logical interfaces such as NG interface and Xn interface.
  • the network interface 1423 may also be a wired communication interface or a wireless communication interface for wireless backhaul. If the network interface 1423 is a wireless communication interface, the network interface 1423 may use a higher frequency band for wireless communication than the frequency band used by the wireless communication interface 1425 .
  • Wireless communication interface 1425 supports any cellular communication scheme, such as 5G NR, and provides wireless connectivity to terminals located in the cell of gNB 1400 via antenna 1410.
  • the wireless communication interface 1425 may generally include, for example, a baseband (BB) processor 1426 and RF circuitry 1427 .
  • the BB processor 1426 may perform, for example, encoding/decoding, modulation/demodulation, and multiplexing/demultiplexing, and perform various types of signals of various layers (eg, physical layer, MAC layer, RLC layer, PDCP layer, SDAP layer) deal with.
  • the BB processor 1426 may have some or all of the above-described logical functions.
  • the BB processor 1426 may be a memory storing a communication control program, or a module including a processor and associated circuitry configured to execute the program.
  • the update procedure may cause the functionality of the BB processor 1426 to change.
  • the module may be a card or blade that is inserted into a slot of the base station device 1420. Alternatively, the module can also be a chip mounted on a card or blade.
  • the RF circuit 1427 may include, for example, a mixer, a filter, and an amplifier, and transmit and receive wireless signals via the antenna 1410 .
  • FIG. 15 shows an example in which one RF circuit 1427 is connected to one antenna 1410 , the present disclosure is not limited to this illustration, but one RF circuit 1427 may connect a plurality of antennas 1410 at the same time.
  • the wireless communication interface 1425 may include multiple BB processors 1426 .
  • multiple BB processors 1426 may be compatible with multiple frequency bands used by gNB 1400.
  • the wireless communication interface 1425 may include a plurality of RF circuits 1427 .
  • multiple RF circuits 1427 may be compatible with multiple antenna elements.
  • FIG. 15 shows an example in which the wireless communication interface 1425 includes multiple BB processors 1426 and multiple RF circuits 1427 , the wireless communication interface 1425 may also include a single BB processor 1426 or a single RF circuit 1427 .
  • gNB 1400 In the gNB 1400 shown in FIG. 15 , one or more units included in the processing circuit 1001 described with reference to FIG. 13A may be implemented in the wireless communication interface 1425. Alternatively, at least some of these components may be implemented in the controller 1421 .
  • gNB 1400 includes a portion (eg, BB processor 1426) or the entirety of wireless communication interface 1425, and/or a module including controller 1421, and one or more components may be implemented in the module.
  • the module may store and execute a program for allowing the processor to function as one or more components (in other words, a program for allowing the processor to perform the operations of the one or more components).
  • a program for allowing a processor to function as one or more components may be installed in gNB 1400, and wireless communication interface 1425 (eg, BB processor 1426) and/or controller 1421 may execute the program.
  • the gNB 1400, the base station apparatus 1420, or a module may be provided as an apparatus including one or more components, and a program for allowing a processor to function as the one or more components may be provided.
  • a readable medium in which the program is recorded may be provided.
  • FIG. 16 is a block diagram showing a second example of a schematic configuration of a base station to which the technology of the present disclosure can be applied.
  • the base station is shown as gNB 1530.
  • gNB 1530 includes multiple antennas 1540, base station equipment 1550 and RRH 1560.
  • the RRH 1560 and each antenna 1540 may be connected to each other via an RF cable.
  • the base station apparatus 1550 and the RRH 1560 may be connected to each other via a high-speed line such as an optical fiber cable.
  • the gNB 1530 (or the base station device 1550) here may correspond to the electronic device 1000 described above.
  • Antenna 1540 includes multiple antenna elements, such as multiple antenna arrays for massive MIMO.
  • the antennas 1540 may be arranged in an antenna array matrix, for example, and used for the base station apparatus 1550 to transmit and receive wireless signals.
  • multiple antennas 1540 may be compatible with multiple frequency bands used by gNB 1530.
  • the base station apparatus 1550 includes a controller 1551 , a memory 1552 , a network interface 1553 , a wireless communication interface 1555 , and a connection interface 1557 .
  • the controller 1551 , the memory 1552 and the network interface 1553 are the same as the controller 1421 , the memory 1422 and the network interface 1423 described with reference to FIG. 15 .
  • Wireless communication interface 1555 supports any cellular communication scheme, such as 5G NR, and provides wireless communication via RRH 1560 and antenna 1540 to terminals located in a sector corresponding to RRH 1560.
  • Wireless communication interface 1555 may generally include, for example, BB processor 1556 .
  • the BB processor 1556 is the same as the BB processor 1426 described with reference to FIG. 15, except that the BB processor 1556 is connected to the RF circuit 1564 of the RRH 1560 via the connection interface 1557.
  • the wireless communication interface 1555 may include a plurality of BB processors 1556.
  • multiple BB processors 1556 may be compatible with multiple frequency bands used by gNB 1530.
  • FIG. 16 shows an example in which the wireless communication interface 1555 includes multiple BB processors 1556
  • the wireless communication interface 1555 may include a single BB processor 1556 .
  • connection interface 1557 is an interface for connecting the base station apparatus 1550 (the wireless communication interface 1555 ) to the RRH 1560.
  • the connection interface 1557 may also be a communication module for communication in the above-mentioned high-speed line connecting the base station device 1550 (the wireless communication interface 1555) to the RRH 1560.
  • RRH 1560 includes connection interface 1561 and wireless communication interface 1563.
  • connection interface 1561 is an interface for connecting the RRH 1560 (the wireless communication interface 1563 ) to the base station apparatus 1550.
  • the connection interface 1561 may also be a communication module for communication in the above-mentioned high-speed line.
  • the wireless communication interface 1563 transmits and receives wireless signals via the antenna 1540 .
  • Wireless communication interface 1563 may typically include RF circuitry 1564, for example.
  • RF circuitry 1564 may include, for example, mixers, filters, and amplifiers, and transmit and receive wireless signals via antenna 1540 .
  • FIG. 16 shows an example in which one RF circuit 1564 is connected to one antenna 1540 , the present disclosure is not limited to this illustration, but one RF circuit 1564 may connect multiple antennas 1540 at the same time.
  • the wireless communication interface 1563 may include a plurality of RF circuits 1564 .
  • multiple RF circuits 1564 may support multiple antenna elements.
  • FIG. 16 shows an example in which the wireless communication interface 1563 includes multiple RF circuits 1564 , the wireless communication interface 1563 may include a single RF circuit 1564 .
  • gNB 1500 one or more units included in the processing circuit 1001 described with reference to FIG. 13A may be implemented in the wireless communication interface 1525. Alternatively, at least some of these components may be implemented in the controller 1521 .
  • gNB 1500 includes a portion (eg, BB processor 1526) or the entirety of wireless communication interface 1525, and/or a module including controller 1521, and one or more components may be implemented in the module.
  • the module may store and execute a program for allowing the processor to function as one or more components (in other words, a program for allowing the processor to perform the operations of the one or more components).
  • a program for allowing a processor to function as one or more components may be installed in gNB 1500, and wireless communication interface 1525 (eg, BB processor 1526) and/or controller 1521 may execute the program.
  • the gNB 1500, the base station apparatus 1520, or a module may be provided as an apparatus including one or more components, and a program for allowing a processor to function as the one or more components may be provided.
  • a readable medium in which the program is recorded may be provided.
  • FIG. 17 is a block diagram showing an example of a schematic configuration of a smartphone 1600 to which the techniques of the present disclosure may be applied.
  • the smartphone 1600 may be implemented as the electronic device 2000 described with reference to FIG. 14A.
  • Smartphone 1600 includes processor 1601, memory 1602, storage device 1603, external connection interface 1604, camera device 1606, sensor 1607, microphone 1608, input device 1609, display device 1610, speaker 1611, wireless communication interface 1612, one or more Antenna switch 1615 , one or more antennas 1616 , bus 1617 , battery 1618 , and auxiliary controller 1619 .
  • the processor 1601 may be, for example, a CPU or a system on a chip (SoC), and controls the functions of the application layer and further layers of the smartphone 1600.
  • the processor 1601 may include or function as the processing circuit 2001 described with reference to FIG. 14A.
  • the memory 1602 includes RAM and ROM, and stores data and programs executed by the processor 1601 .
  • the storage device 1603 may include storage media such as semiconductor memories and hard disks.
  • the external connection interface 1604 is an interface for connecting an external device such as a memory card and a Universal Serial Bus (USB) device to the smartphone 1600 .
  • USB Universal Serial Bus
  • the camera 1606 includes an image sensor such as a charge coupled device (CCD) and a complementary metal oxide semiconductor (CMOS), and generates a captured image.
  • Sensors 1607 may include a set of sensors such as measurement sensors, gyroscope sensors, geomagnetic sensors, and acceleration sensors.
  • the microphone 1608 converts the sound input to the smartphone 1600 into an audio signal.
  • the input device 1609 includes, for example, a touch sensor, a keypad, a keyboard, buttons, or switches configured to detect a touch on the screen of the display device 1610, and receives operations or information input from a user.
  • the display device 1610 includes a screen such as a liquid crystal display (LCD) and an organic light emitting diode (OLED) display, and displays an output image of the smartphone 1600 .
  • the speaker 1611 converts the audio signal output from the smartphone 1600 into sound.
  • the wireless communication interface 1612 supports any cellular communication scheme (such as 4G LTE or 5G NR, etc.), and performs wireless communication.
  • Wireless communication interface 1612 may typically include, for example, BB processor 1613 and RF circuitry 1614.
  • the BB processor 1613 can perform, for example, encoding/decoding, modulation/demodulation, and multiplexing/demultiplexing, and perform various types of signal processing for wireless communication.
  • the RF circuit 1614 may include, for example, mixers, filters, and amplifiers, and transmit and receive wireless signals via the antenna 1616 .
  • the wireless communication interface 1612 may be a chip module on which the BB processor 1613 and the RF circuit 1614 are integrated. As shown in FIG.
  • the wireless communication interface 1612 may include a plurality of BB processors 1613 and a plurality of RF circuits 1614 .
  • FIG. 17 shows an example in which the wireless communication interface 1612 includes multiple BB processors 1613 and multiple RF circuits 1614
  • the wireless communication interface 1612 may include a single BB processor 1613 or a single RF circuit 1614 .
  • the wireless communication interface 1612 may support additional types of wireless communication schemes, such as short-range wireless communication schemes, near field communication schemes, and wireless local area network (LAN) schemes.
  • the wireless communication interface 1612 may include the BB processor 1613 and the RF circuit 1614 for each wireless communication scheme.
  • Each of the antenna switches 1615 switches the connection destination of the antenna 1616 among a plurality of circuits included in the wireless communication interface 1612 (eg, circuits for different wireless communication schemes).
  • Antenna 1616 includes multiple antenna elements, such as multiple antenna arrays for massive MIMO. Antennas 1616 may be arranged, for example, in an antenna array matrix, and used for wireless communication interface 1612 to transmit and receive wireless signals. Smartphone 1600 may include one or more antenna panels (not shown).
  • the smartphone 1600 may include an antenna 1616 for each wireless communication scheme.
  • the antenna switch 1615 can be omitted from the configuration of the smartphone 1600 .
  • the bus 1617 connects the processor 1601, the memory 1602, the storage device 1603, the external connection interface 1604, the camera device 1606, the sensor 1607, the microphone 1608, the input device 1609, the display device 1610, the speaker 1611, the wireless communication interface 1612, and the auxiliary controller 1619 to each other connect.
  • the battery 1618 provides power to the various blocks of the smartphone 1600 shown in FIG. 17 via feeders, which are partially shown in phantom in the figure.
  • the auxiliary controller 1619 operates the minimum necessary functions of the smartphone 1600, eg, in sleep mode.
  • one or more components included in the processing circuit 2001 described with reference to FIG. 14A may be implemented in the wireless communication interface 1612 .
  • at least some of these components may be implemented in processor 1601 or auxiliary controller 1619 .
  • smartphone 1600 includes a portion (eg, BB processor 1613 ) or the entirety of wireless communication interface 1612, and/or a module including processor 1601 and/or auxiliary controller 1619, and one or more components may be implemented in this module.
  • the module may store and execute a program that allows the processor to function as one or more components (in other words, a program for allowing the processor to perform the operations of the one or more components).
  • a program for allowing a processor to function as one or more components may be installed in smartphone 1600, and wireless communication interface 1612 (eg, BB processor 1613), processor 1601 and/or auxiliary
  • the controller 1619 can execute the program.
  • the smartphone 1600 or a module may be provided as an apparatus including one or more components, and a program for allowing a processor to function as the one or more components may be provided.
  • a readable medium in which the program is recorded may be provided.
  • FIG. 18 is a block diagram showing an example of a schematic configuration of a car navigation apparatus 1720 to which the technology of the present disclosure can be applied.
  • the car navigation device 1720 may be implemented as the electronic device 2000 described with reference to FIG. 14A .
  • the car navigation device 1720 includes a processor 1721, a memory 1722, a global positioning system (GPS) module 1724, a sensor 1725, a data interface 1726, a content player 1727, a storage medium interface 1728, an input device 1729, a display device 1730, a speaker 1731, a wireless A communication interface 1733 , one or more antenna switches 1736 , one or more antennas 1737 , and a battery 1738 .
  • GPS global positioning system
  • the processor 1721 may be, for example, a CPU or a SoC, and controls the navigation function and other functions of the car navigation device 1720 .
  • the memory 1722 includes RAM and ROM, and stores data and programs executed by the processor 1721 .
  • the GPS module 1724 measures the position (such as latitude, longitude, and altitude) of the car navigation device 1720 using GPS signals received from GPS satellites.
  • Sensors 1725 may include a set of sensors, such as gyroscope sensors, geomagnetic sensors, and air pressure sensors.
  • the data interface 1726 is connected to, for example, the in-vehicle network 1741 via a terminal not shown, and acquires data generated by the vehicle, such as vehicle speed data.
  • the content player 1727 reproduces content stored in storage media such as CDs and DVDs, which are inserted into the storage media interface 1728 .
  • the input device 1729 includes, for example, a touch sensor, a button, or a switch configured to detect a touch on the screen of the display device 1730, and receives operations or information input from a user.
  • the display device 1730 includes a screen such as an LCD or OLED display, and displays images or reproduced content of a navigation function.
  • the speaker 1731 outputs the sound of the navigation function or the reproduced content.
  • the wireless communication interface 1733 supports any cellular communication scheme, such as 4G LTE or 5G NR, and performs wireless communication.
  • Wireless communication interface 1733 may generally include, for example, BB processor 1734 and RF circuitry 1735.
  • the BB processor 1734 may perform, for example, encoding/decoding, modulation/demodulation, and multiplexing/demultiplexing, and perform various types of signal processing for wireless communication.
  • the RF circuit 1735 may include, for example, a mixer, a filter, and an amplifier, and transmit and receive wireless signals via the antenna 1737 .
  • the wireless communication interface 1733 can also be a chip module on which the BB processor 1734 and the RF circuit 1735 are integrated. As shown in FIG.
  • the wireless communication interface 1733 may include a plurality of BB processors 1734 and a plurality of RF circuits 1735 .
  • FIG. 18 shows an example in which the wireless communication interface 1733 includes multiple BB processors 1734 and multiple RF circuits 1735
  • the wireless communication interface 1733 may include a single BB processor 1734 or a single RF circuit 1735 .
  • the wireless communication interface 1733 may support another type of wireless communication scheme, such as a short-range wireless communication scheme, a near field communication scheme, and a wireless LAN scheme.
  • the wireless communication interface 1733 may include the BB processor 1734 and the RF circuit 1735 for each wireless communication scheme.
  • Each of the antenna switches 1736 switches the connection destination of the antenna 1737 among a plurality of circuits included in the wireless communication interface 1733, such as circuits for different wireless communication schemes.
  • Antenna 1737 includes multiple antenna elements, such as multiple antenna arrays for massive MIMO.
  • the antennas 1737 may be arranged, for example, in an antenna array matrix, and are used for the wireless communication interface 1733 to transmit and receive wireless signals.
  • the car navigation device 1720 may include an antenna 1737 for each wireless communication scheme.
  • the antenna switch 1736 may be omitted from the configuration of the car navigation apparatus 1720 .
  • the battery 1738 provides power to the various blocks of the car navigation device 1720 shown in FIG. 18 via feeders, which are partially shown as dashed lines in the figure.
  • the battery 1738 accumulates power supplied from the vehicle.
  • car navigation device 1720 shown in FIG. 18 , one or more components included in the processing circuit 2001 described with reference to FIG. 14A may be implemented in the wireless communication interface 1733 . Alternatively, at least some of these components may be implemented in the processor 1721 . As one example, car navigation device 1720 includes a portion (eg, BB processor 1734) or the entirety of wireless communication interface 1733, and/or a module including processor 1721, and one or more components may be implemented in the module. In this case, the module may store and execute a program that allows the processor to function as one or more components (in other words, a program for allowing the processor to perform the operations of the one or more components).
  • BB processor 1734 BB processor 1734
  • the module may store and execute a program that allows the processor to function as one or more components (in other words, a program for allowing the processor to perform the operations of the one or more components).
  • a program for allowing the processor to function as one or more components may be installed in the car navigation device 1720, and the wireless communication interface 1733 (eg, the BB processor 1734) and/or the processor 1721 may be installed Execute the program.
  • the car navigation device 1720 or a module may be provided, and a program for allowing a processor to function as the one or more components may be provided.
  • a readable medium in which the program is recorded may be provided.
  • the communication unit 2005 of FIG. 14A may be implemented in the wireless communication interface 1933 (eg, the RF circuit 1935 ).
  • the techniques of the present disclosure may also be implemented as an in-vehicle system (or vehicle) 1740 that includes one or more blocks of a car navigation device 1720 , an in-vehicle network 1741 , and a vehicle module 1742 .
  • the vehicle module 1742 generates vehicle data such as vehicle speed, engine speed, and fault information, and outputs the generated data to the in-vehicle network 1741 .
  • a plurality of functions included in one unit in the above embodiments may be implemented by separate devices.
  • multiple functions implemented by multiple units in the above embodiments may be implemented by separate devices, respectively.
  • one of the above functions may be implemented by multiple units. Needless to say, such a configuration is included in the technical scope of the present disclosure.
  • the steps described in the flowcharts include not only processing performed in time series in the stated order, but also processing performed in parallel or individually rather than necessarily in time series. Furthermore, even in the steps processed in time series, needless to say, the order can be appropriately changed.

Landscapes

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

Abstract

本公开涉及无线通信系统中的电子设备、通信方法和存储介质。一种基站侧的电子设备包括处理电路，处理电路被配置为：确定用于所述基站与UE之间的第一传输信道的第一波束；向所述UE发送包含关于第一波束的波束指示信息的动态信令，以使得用于第一传输信道的波束被更新为第一波束；以及在用于第一传输信道的波束的更新成功的情况下，将用于所述基站与所述UE之间的第二传输信道和/或参考信号的波束更新为第一波束。

Description

电子设备、通信方法和存储介质 技术领域
本公开涉及电子设备、通信方法和存储介质，更具体地，本公开涉及用于无线通信系统中的不同物理信道之间的波束共用操作的电子设备、通信方法和存储介质。
背景技术
当前的无线通信系统中广泛使用大规模天线技术，其中基站和用户设备(UE)均具有多个天线，可以通过波束赋形(beamforming)形成具有较窄的指向性的空间波束，以在特定的方向上提供较强的功率覆盖，从而对抗高频信道中存在的较大的路径损耗。具有不同发射方向的波束集合被用于实现小区覆盖。为了提高波束信号的接收质量，基站和UE需要选择出尽可能与信道方向匹配的波束。典型地，基站和UE可以通过波束训练来选择和管理波束。
根据5G新无线电(5G NR)的标准R16，基站采用不同的机制将针对控制信道和数据信道确定的波束指示给UE。具体而言，用于下行或上行的控制信道的波束可以使用介质接入控制(MAC)控制元素(CE)来指示，而用于下行或上行的数据信道的波束可以使用下行控制信息(DCI)来指示。这种波束指示差异主要出于以下考虑：相比于控制信道，数据信道的传输对于可靠性要求更高、对于波束方向更敏感，所以需要更为灵活和动态的指示机制。
当无线信道环境发生变化时，基站可能需要重新选择传输波束，并例如通过发送DCI来指示更新的用于数据信道的波束。然而，用于控制信道的波束的更新需要通过发送MAC CE，相比没有那么快速。此外，控制信道和数据信道的波束更新需要分开指示，即使它们具有相同的波束方向，这可能带来多余的信令负担。
因此，对于两个或更多个不同信道适用相同波束的应用场景，可能存在实现波束共用的波束指示和更新机制的需求。然而，现有技术中尚没有涉及波束共用的高效方法。
发明内容
本公开提供了多个方面，涉及在基站和UE之间的各种传输信道上实现波束共用。通过应用本公开的一个或多个方面，可以满足上面所述的需求。
在下文中给出了关于本公开的简要概述，以便提供关于本公开的一些方面的基本理解。但是，应当理解，这个概述并不是关于本公开的穷举性概述。它并不是意图用来确定本公开的关键性部分或重要部分，也不是意图用来限定本公开的范围。其目的仅仅是以简化的形式给出关于本公开的某些概念，以此作为稍后给出的更详细描述的前序。
根据本公开的一个方面，提供了一种基站侧的电子设备，包括处理电路，该处理电路被配置为：确定用于所述基站与UE之间的第一传输信道的第一波束；向所述UE发送包含关于第一波束的波束指示信息的动态信令，以使得用于第一传输信道的波束被更新为第一波束；以及在用于第一传输信道的波束的更新成功的情况下，将用于所述基站与所述UE之间的第二传输信道和/或参考信号的波束更新为第一波束。
根据本公开的一个方面，提供了一种UE侧的电子设备，包括处理电路，该处理电路被配置为：从基站接收包含关于第一波束的波束指示信息的动态信令，第一波束被确定用于所述UE与所述基站之间的第一传输信道；将用于第一传输信道的波束更新为第一波束；以及在用于第一传输信道的波束的更新成功的情况下，将用于所述UE与所述基站之间的第二传输信道和/或参考信号的波束更新为第一波束。
根据本公开的一个方面，提供了一种通信方法，包括：确定用于所述基站与UE之间的第一传输信道的第一波束；向所述UE发送包含关于第一波束的波束指示信息的动态信令，以使得用于第一传输信道的波束被更新为第一波束；以及在用于第一传输信道的波束的更新成功的情况下，将用于所述基站与所述UE之间的第二传输信道和/或参考信号的波束更新为第一波束。
根据本公开的一个方面，提供了一种通信方法，包括：从基站接收包含关于第一波束的波束指示信息的动态信令，第一波束被确定用于所述UE与所述基站之间的第一传输信道；将用于第一传输信道的波束更新为第一波束；以及在用于第一传 输信道的波束的更新成功的情况下，将用于所述UE与所述基站之间的第二传输信道和/或参考信号的波束更新为第一波束。
根据本公开的一个方面，提供了一种存储有可执行指令的非暂时性计算机可读存储介质，所述可执行指令当被执行时实现上面的任一个通信方法。
附图说明
本公开可以通过参考下文中结合附图所给出的详细描述而得到更好的理解，其中在所有附图中使用了相同或相似的附图标记来表示相同或者相似的要素。所有附图连同下面的详细说明一起包含在本说明书中并形成说明书的一部分，用来进一步举例说明本公开的实施例和解释本公开的原理和优点。其中：
图1示意性地示出了基站和UE可使用的波束；
图2示出了根据第一实施例的波束共用的示意图；
图3是例示了TCI状态的配置示意图；
图4例示了用于为数据信道激活TCI状态的MAC CE；
图5例示了用于调度数据信道的DCI；
图6示出了根据第二实施例的波束共用的示意图；
图7A和7B示出了根据第三实施例的波束共用的示意图；
图8是例示了PUCCH空间关系信息的配置示意图；
图9示出了根据第四实施例的波束共用的示意图；
图10示出了用于为控制信道激活TCI状态的MAC CE；
图11示出了根据第五实施例的波束共用的示意图；
图12示出了用于为控制信道激活PUCCH空间关系信息的MAC CE；
图13A和13B例示了根据实施例的基站侧的电子设备及其通信方法；
图14A和14B例示了根据实施例的UE侧的电子设备及其通信方法；
图15例示了根据本公开的基站的示意性配置的第一示例；
图16例示了根据本公开的基站的示意性配置的第二示例；
图17例示了根据本公开的智能电话的示意性配置示例；
图18例示了根据本公开的汽车导航设备的示意性配置示例。
通过参照附图阅读以下详细描述，本公开的特征和方面将得到清楚的理解。
具体实施方式
在下文中将参照附图来详细描述本公开的各种示例性实施例。为了清楚和简明起见，在本说明书中并未描述实施例的所有特征。然而应注意，在实现本公开的实施例时可以根据特定需求做出很多特定于实现方式的设置，以便实现开发人员的具体目标，例如，符合与设备及业务相关的限制条件，并且这些限制条件可能会随着实现方式的不同而有所改变。
此外，还应注意，为了避免因不必要的细节而模糊了本公开，在附图中仅仅示出了与至少根据本公开的技术方案密切相关的处理步骤和/或设备结构，而省略了与本公开关系不大的其他细节。
为了方便解释本公开的技术方案，下面将在5G NR的背景下描述本公开的各个方面。但是应注意，这不是对本公开的应用范围的限制，本公开的一个或多个方面还可以被应用于例如4G LTE/LTE-A等已经普遍使用的无线通信系统，或者将来发展的各种无线通信系统。下面的描述中提及的架构、实体、功能、过程等并非局限于NR通信系统中的那些，而可以在其它的通信标准中找到对应。
【概述】
在诸如5G NR之类的无线通信系统中，基站和UE都可以应用诸如大规模MIMO(Massive MIMO)的大规模天线技术。为了支持MIMO技术的应用，基站和UE均具有许多天线，例如几十根、几百根甚至上千根。对于天线模型，一般围绕天线定义了三层的映射关系，使其能够顺利承接信道模型和通信标准。
最底层是最基本的物理单元——天线，也可以称为天线阵元。每个天线阵元按 照各自的幅度参数和相位参数辐射电磁波。
天线阵元按照矩阵的形式被布置成一个或多个天线阵列。一个天线阵列可以由整行、整列、多行、多列的天线阵元构成。在这一层上，每个天线阵列实际上构成一个收发单元(Transceiver Unit，TXRU)。每一个TXRU都可以独立配置。通过配置组成该TXRU的天线阵元的幅度参数和/或相位参数，实现对该TXRU天线图样的调整，天线阵列内的所有天线阵元发射的电磁波辐射形成指向特定空间方向的较窄的波束，即，实现波束赋形。
TXRU与其天线阵元可以配置成多种对应关系，从而改变波束赋形的能力和特性。从TXRU的角度看，单个TXRU可以仅包含单行或单列天线阵元，即所谓的一维TXRU，此时，TXRU仅能在一个维度上调整波束的方向；单个TXRU也可以包含多行或多列天线阵元，即所谓的二维TXRU，此时TXRU能够在水平和垂直两个维度上调整波束的方向。从天线阵元的角度看，例如一列天线阵元可以构成多个TXRU，但是构成方式可以是部分连接方式，即，每个TXRU只使用部分天线阵元形成波束；也可以是全连接方式，即，每个TXRU都可以对所有天线阵元进行调整以形成波束。
最后，一个或多个TXRU通过逻辑映射构成系统层面上看到的天线端口(Antenna Ports)。当TXRU与天线端口之间采用一一映射的关系时，TXRU与天线端口是等价的。当然，取决于系统配置，两个或多个TXRU可以共同构成一个天线端口。
天线端口可以由参考信号表征。天线端口与其参考信号之间存在一一对应的关系，不同的天线端口用于传输不同的参考信号。参考信号例如包括：同步信号块(SSB)、信道状态信息参考信号(CSI-RS)、探测参考信号(SRS)等等。
在不同的天线端口之间可以存在准共址(quasi-co-located，QCL)的关系。如果运送一个天线端口上的符号的信道的大尺度性质可以从运送另一个天线端口上的符号的信道推断出，则认为这两个天线端口是准共址的。这意味着，当例如天线端口A和天线端口B之间满足QCL关系时，从天线端口A上的信号估计得到的信道大尺度性质参数同样适合于天线端口B上的信号。大尺度性质包括以下至少之一：时延扩展、多普勒扩展、多普勒频移、平均增益、平均延迟和空间接收参数等。特 别而言，如果天线端口A和天线端口B具有关于空间接收参数的QCL关系，则接收端可以使用相同的空间接收参数来实现这两个天线端口上的信号的接收。
如本公开中所使用的，术语“空间接收参数”包括用于接收来自特定空间方向的被形成为波束的电磁波辐射信号的波束赋形参数。波束赋形参数例如可以包括天线阵列的天线阵元的相位参数和/或幅度参数。根据对应的波束赋形参数，由天线阵元发射的电磁波辐射在空间中组合成希望的波束。通过特定空间接收参数配置的天线阵列可以对来自于对应的空间方向的波束信号实现最佳接收。空间接收参数可以体现为空间域接收滤波器。应理解的是，在本公开中，“空间接收参数”可以与它所形成的“接收波束”互换地使用。类似地，术语“空间发射参数”包括用于形成指向特定空间方向的发射波束的波束赋形参数。空间发射参数可以体现为空间域发射滤波器。同样，在本公开中，“空间发射参数”可以与它所形成的“发射波束”互换地使用。
通过采用波束赋形，辐射能量可以主要集中于特定的方向上，以对抗路径损耗。为了实现完全覆盖，基站和UE需要具备形成许多指向不同的波束的能力，并且在使用波束进行发射和接收之前从这些波束当中选择尽可能地与信道方向匹配的发射波束或接收波束，即，在发射端，发射波束对准信道发射角，在接收端，接收波束对准信道到达角。
基站和UE可以通过波束训练来进行波束选择。波束训练一般包括波束测量、波束上报、波束指示等过程。
下面参照图1来简单描述无线通信系统中的波束训练过程。如图1中所示，基站1000可使用方向不同的n t_DL个(n t_DL≥1)下行发射波束，UE 1004可使用方向不同的n r_DL个(n r_DL≥1)下行接收波束。类似地，基站1000还可使用方向不同的n r_UL个(n r_UL≥)上行接收波束，UE 1004还可使用方向不同的n t_UL个(n t_UL≥1)上行发射波束。虽然在图1中，基站1000的上行接收波束与下行发射波束1002的个数以及各波束的覆盖范围相同，UE 1004的上行发射波束与下行接收波束1006的个数以及各波束的覆盖范围相同，但是应当理解，这仅仅是示例性的，基站和UE所使用的波束的数量和覆盖范围可以是各种各样的。
基站1000和UE 1004通过扫描波束的方式遍历所有的发射波束-接收波束组合。以下行波束扫描为例，首先，基站1000按照下行扫描周期通过其n t_DL个发射波束 中的每个发射波束向UE 1004发送n r_DL个下行参考信号。这n t_DL个发射波束可以来自基站1000的波束赋形码本。以这种方式，基站1000的n t_DL个发射波束依次向UE 1004发送n t_DL×n r_DL个下行参考信号。基站1000可以利用的参考信号资源例如包括非零功率的CSI-RS(NZP-CSI-RS)资源或SSB资源。
UE 1004通过其n r_DL个接收波束1006分别接收每个发射波束，并对波束信号进行测量。例如，UE 1004可以测量每个发射波束中携带的n t_DL个下行参考信号，即共测量n t_DL×n r_DL个下行参考信号。例如，UE 1004可以测量物理层(L1)的参考信号接收功率(L1-RSRP)、参考信号接收质量(L1-RSRQ)、信号与干扰加噪声比(L1-SINR)等。
然后，UE 1004将波束测量结果上报给基站1000。为了减少上报的数据量，UE1004可以被配置为仅上报一部分发射波束(例如，仅Nr<n t_DL个，Nr由基站1000预先配置)波束的测量结果以及相关联的参考信号的标识信息，诸如CSI-RS资源指示符CRI或SSB资源指示符SSBRI)。由于参考信号与发射波束和接收波束之间的对应关系，每个参考信号代表一对发射波束-接收波束。
基于所上报的波束测量结果，基站1000可以从UE 1004上报的发射波束中选择最佳发射波束以用于与UE 1004的下行传输。在一个例子中，基站1000可以选择与测量结果最好的参考信号对应的发射波束作为最佳发射波束，该发射波束的方向一般最匹配信道方向，并且对应于相应的空间发射参数。
为了便于UE 1004进行波束接收，基站1000将与最佳发射波束相对应的参考信号指示给UE 1004，由此UE 1004可以确定在波束扫描过程中与该参考信号对应的接收波束作为与最佳发射波束匹配的最佳接收波束。该接收波束实现了对于最佳发射波束的最佳接收并且其方向一般最匹配信道方向。之后，基站1000和UE 1004将可以使用所确定的最佳发射波束和最佳接收波束进行下行传输。
类似地，在上行波束扫描过程中，UE 1004通过其n t_UL个发射波束中的每个发射波束向基站1000发送n r_UL个上行参考信号。以这种方式，基站1000通过其n r_UL个接收波束共n t_UL×n r_UL个上行参考信号。基站1000对这n t_UL×n r_UL个上行参考信号进行测量，例如测量L1-RSRP、L 1-RSRQ、L1-SINR等，从而确定UE 1004的最佳上行发射波束和基站1000的与最佳上行发射波束匹配的最佳上行接收波束。基站1000 将对应的参考信号指示给UE 1004，使得UE 1004可以利用所确定的最佳发射波束来进行上行传输。
当例如由于UE 1004发生移动，导致无线信道环境发生变化时，现有的发射波束-接收波束对可能不再适配无线信道方向。此时，可以重复上述波束训练过程，以更新发射波束-接收波束对。
取决于传输信道是控制信道还是数据信道，可以采用不同的波束指示机制。对于诸如物理下行共享信道(PDSCH)或物理上行共享信道(PUSCH)之类的数据信道，基站1000可以通过物理下行控制信道(PDCCH)向UE 1004发送用于指示所选择的波束的DCI，由此UE 1004可以调整(或者说更新)用于PDSCH的下行接收波束或用于PUSCH的上行发射波束。而对于诸如PDCCH或物理上行控制信道(PUCCH)之类的控制信道，基站1000可以通过PDSCH向UE 1004发送用于指示所选择的波束的MAC CE，以便于UE 1004更新用于PDCCH的下行接收波束或用于PUCCH的上行发射波束。
然而，尽管传输信道不同，UE相对于基站的空间位置关系是一定的。也就是说，在很多场景下，数据信道的状态类似于控制信道的状态，因此其波束也可能适用于控制信道，反之亦然。另外，考虑到上下行信道之间的对称性，用于上行信道的波束也可以用于下行信道，例如，UE利用与下行接收波束对应的空间接收参数来确定与上行发射波束对应的空间发射参数，或者反过来；同时基站利用与下行发射波束对应的空间发射参数来确定与上行接收波束对应的空间接收参数，或者反过来。
基于这些考虑，可以设想在不同的信道之间实现波束共用。如本公开中使用的，“波束共用”是指两个或更多个信道或信号的传输使用相同的波束或上下行对称的波束。通过实现波束共用，可以缩减波束选择和指示的信令过程，提高波束管理的效率。
为了对本公开的透彻理解，下面将详细介绍根据本公开的实施例。
【第一实施例】
图2例示了根据第一实施例的波束共用的示意图。第一实施例涉及基于DCI的下行波束指示。
当基站有数据要发送给UE时，基站可以通过发送DCI来调度PDSCH。DCI由PDCCH承载，其中包含诸如DCI格式标识符、载波指示符、带宽部分(BWP)指示符等，并且还包含分配给PDSCH的时频资源信息(诸如频域资源分派字段、时域资源分派字段)。承载DCI的PDCCH本身占用一个控制资源集(例如，图2中例示的CORESET#0)，并且用于PDCCH的波束是以CORESET为单位、由基站使用MAC CE激活的，后面的实施例会介绍控制信道的波束指示细节。如图2中所示，假设调度PDSCH的PDCCH(CORESET#0)使用波束Beam#0。在本公开中，为了便于说明，有时候将用于某个信道传输的基站波束和UE波束统称为用于该信道的波束，例如，图2中基站用于发送PDCCH的下行发射波束和UE用于接收PDCCH的下行接收波束都用Beam#0表示，这对发射波束和接收波束相互匹配，并且由同一个参考信号(即，与Beam#0相关联的参考信号)表征。
另外，DCI中还可以包含为PDSCH调度的波束的信息。例如，调度给PDSCH使用的波束可以通过上面所述的波束扫描过程确定，以便适配当前的无线信道环境。典型地，针对PDSCH的波束指示可以通过在DCI中设置传输配置指示(TCI)状态来实现。
这里简单介绍诸如PDSCH或PUSCH之类的数据信道的波束指示过程。首先，基站可以通过无线电资源控制(RRC)信令为UE预先配置包括最多M个(例如，64个或128个)TCI状态的TCI状态池。图3是例示了TCI状态的配置示意图。如图3中所示，TCI状态由TCI状态ID标识。每个TCI状态包含用于配置一个或两个下行参考信号与PDCCH或PDSCH的DMRS端口之间的准共址(QCL)关系的参数。对于第一个下行参考信号，这种准共址关系由RRC层参数qcl-Type1配置。如果还有第二个下行参考信号，则准共址关系由可选的qcl-Type2配置。如图3中所示，qcl-Type1或qcl-Type2参数包括以下信息：
–服务小区索引(ServCellIndex)，其代表适用的服务小区；
–带宽部分ID(BWP-Id)，其代表适用的下行带宽部分；
–参考信号(referenceSignal)，其代表提供QCL信息的参考信号资源，包括由NZP-CSI-RS-ResoureId标识的NZP-CSI-RS资源和由SSB-Index标识的SSB资源；
–QCL类型(qcl-Type)，其代表与所列出的下行参考信号对应的准共址类型。取 决于需要推断的无线信道的大尺度性质，TCI状态所涉及的QCL类型qcl-Type可以包括以下选项：–“typeA”：关于{多普勒频移，多普勒扩展，平均延迟，延迟扩展}；–“typeB”：关于{多普勒频移，多普勒扩展}；–“typeC”：关于{多普勒频移，平均延迟}；–“typeD”：关于{空间接收参数}。为了避免歧义，每个TCI状态一般仅允许包含一个“typeD”类型的QCL假设。
随后，基站可以通过PDSCH向UE发送MAC CE，以激活为UE配置的TCI状态池中的至多8个TCI状态。图4例示了用于激活TCI状态的MAC CE的格式(不包括头部)。如图4中所示，“CORESET池ID”字段表示PDCCH所在的CORESET池，其占用1个比特；“服务小区ID”表示该MAC CE适用的服务小区，其占用5个比特；“BWP ID”表示该MAC CE适用的下行带宽部分，其占用2个比特；“T i”表示所配置的TCI状态池的激活信息，其占用1个比特，如果被设置为1，则表示对应的TCI状态被激活，否则表示对应的TCI状态不被激活。
最后，基站可以通过在DCI中指定一个TCI状态，以指示为PDSCH调度的波束。
图5例示了可用于指定TCI状态的DCI格式，诸如由3GPP R16规定的DCI格式1_1或1_2。如图5中所示，除了关于DCI格式、分量载波、BWP、时频资源等信息以外，DCI还可以包含TCI状态的标识字段，其占用3比特，以便指示所激活的至多8个TCI状态中的一个。在UE侧，当在PDCCH上接收到这种DCI时，UE从中提取TCI状态的标识字段，找到对应的TCI状态，并做出如下QCL假设：TCI状态中列出的参考信号的天线端口与该TCI状态所指示的传输信道或参考信号的天线端口存在关于空间接收参数的QCL关系，从而用于前者的空间接收参数(即，波束)将可用于后者。
现在回到图2，假设基站确定为PDSCH调度的波束是Beam#1，该Beam#1可以是在波束扫描中具有最佳传输表现的波束。基站可以在DCI中指示一个TCI状态，其中该TCI状态包含关于与Beam#1相关联的参考信号的QCL信息。
在UE侧，UE首先利用与CORESET#0对应的波束Beam#0(下行接收波束)来盲检PDCCH，以便接收其中承载的DCI。如果成功接收到该DCI，UE从中提取出关于PDSCH的各种调度信息，诸如时频资源信息等。特别地，UE可以找到DCI中指示的TCI状态，并理解应该将该TCI状态所指示的波束(即Beam#1)用作接收被调度的PDSCH的波束，即，与TCI状态中包含的参考信号相关联的下行接收波束。
需要注意的是，一般不存在对于DCI的HARQ反馈机制。也就是说，基站不知道所发送的DCI是否已被UE成功接收，从而不知道UE是否已经更新用于接收PDSCH的波束。
对此，UE可以采用一种隐式的方式来反馈UE是否已接收到DCI并且用于PDSCH的波束是否已经更新成功。具体而言，在DCI调度的时频资源上，基站利用Beam#1的下行发射波束来发送PDSCH，而UE利用Beam#1的下行接收波束来接收PDSCH，并对其进行解码。如果解码正确，则通过PUCCH向基站发送肯定反馈(ACK)，否则发送否定反馈(NACK)。响应于接收到ACK，基站将知道UE已经将PDSCH的波束更新为Beam#1，并且Beam#1的可靠性得到验证。
接下来，响应于确定PDSCH的波束更新完成，基站和UE可以将用于PDSCH的波束共用给其它信道。这是因为，PDSCH的传输成功表明其波束从时效性来说是质量最好的。因此，根据本公开的第一实施例，基站和UE可以例如将调度该PDSCH的PDCCH(CORESET#0)的波束Beam#0更新为Beam#1。
根据第一实施例，PDCCH的波束更新可以在基站和UE侧自发进行，即，UE在正确解码出PDSCH后经过一定的时间间隔，执行PDCCH的下行接收波束的更新，基站在接收到对于PDSCH的ACK后经过一定的时间间隔，执行PDCCH的下行发射波束的更新，从而省略了专门用于PDCCH的波束更新的信令开销和时延。
随后，如果基站再次利用CORESET#0调度PDSCH，则基站将可以利用更新的Beam#1来发送承载DCI的PDCCH，而UE将可以利用更新的Beam#1来接收DCI。
另一方面，如果图2中所示的PDSCH未被成功解码，则UE将向基站发送NACK，由此基站和UE都可以知道该次下行数据传输没有成功，原因有可能是所调度的Beam#1质量变差或受到了一定程度的阻挡，即Beam#1的可靠性没有经过验证。因此，基站和UE暂时不更新PDCCH的波束。
基站接收到对于PDSCH的NACK后，可以执行该PDSCH内容的重新调度，即，再次利用Beam#0发送另一个DCI，这个DCI包含重新分配的时频资源和波束。这里，取决于基站侧的调度策略，DCI中指示的波束可以是之前的波束Beam#1，也可以是新的波束。接下来的过程如上面所述的类似，这里不再赘述。如果重新调度PDSCH被正确解码，则基站和UE仍然可以将用于PDCCH的波束更新为DCI中指示的波束。
根据第一实施例，可以实现PDCCH的波束对PDSCH的波束跟随，从而实现这两种信道之间的波束共用。应理解，虽然上面是以基于DCI的PDSCH调度为例进行描述的，但是DCI还可以触发或者说调度下行参考信号，诸如CSI-RS等，因此，第一实施例还可以实现PDCCH与下行参考信号之间的波束共用，原理类似，这里不再赘述。
【第二实施例】
图6示出了根据第二实施例的波束共用的示意图。第二实施例涉及基于DCI的上行波束指示。
当UE有数据要发送给基站时，UE可以通过向基站发送调度请求(SR)或缓冲状态报告(BSR)来请求基站调度用于传输PUSCH的资源。基站可以根据UE要传输的数据量来分配时频资源，并且确定用于PUSCH的波束。例如，调度给PUSCH使用的波束可以通过上面所述的波束扫描过程确定，以便适配当前的无线信道环境。
基站可以通过发送DCI来调度PUSCH，这里可用的DCI可以是例如DCI格式0_1。如图5中所示，DCI包含诸如DCI格式标识符、载波指示符、带宽部分(BWP)指示符等，并且还包含分配给PUSCH的时频资源信息(诸如频域资源分派字段、时域资源分派字段)和波束信息。承载DCI的PDCCH本身占用一个控制资源集(例如，图6中例示的CORESET#0)，假设为CORESET#0上的PDCCH激活的波束是Beam#0。
基站可以通过例如上面所述的波束扫描过程来确定用于PUSCH的波束，诸如图6中所示的Beam#1，Beam#1可以是在波束扫描过程中具有最佳传输表现的波束。基站可以在DCI中指示一个TCI状态，该TCI状态中包含关于与Beam#1相关联的参考信号的QCL信息，并利用Beam#0(下行发射波束)将该DCI发送给UE。
在UE侧，UE首先利用与CORESET#0对应的波束Beam#0(下行接收波束)来盲检PDCCH，以便接收其中承载的DCI。如果成功接收到该DCI，UE从中提取出关于PUSCH的各种调度信息，诸如时频资源信息等。特别地，UE可以找到DCI中指示的TCI状态，并理解应将该TCI状态所指示的波束(即Beam#1)用作发射被调度的PUSCH的波束，即，与TCI状态中包含的参考信号相关联的上行发射波束。
UE无需对DCI的接收进行HARQ反馈，而是直接在DCI调度的时频资源上，利用Beam#1的上行发射波束来发送PUSCH。基站利用Beam#1的上行接收波束来接收PUSCH，并对其进行解码。
不同于PDSCH传输的是，基站不会给UE发送对于PUSCH的显式的HARQ反馈。相反，如果本次PUSCH的解码正确，基站会继续进行该UE的下一次PUSCH调度，来隐式地确认本次PUSCH已被成功接收。下一次PUSCH调度可以通过原来的CORESET#0上的PDCCH来进行，此时用于调度下一次PUSCH的DCI仍然通过Beam#0来传输。可替代地，下一次PUSCH调度也可以通过其它CORESET上的PDCCH来进行，此时用于调度下一次PUSCH调度的DCI可以通过与相应CORESET相关联的波束来传输。但是无论哪种情况，用于调度下一次PUSCH的DCI中需要包括相同的HARQ进程ID以及反转的新数据指示符(NDI)字段，例如，如果为本次PUSCH赋予的值是‘0’，则下一次PUSCH应赋予‘1’，由此UE将知道之前的PUSCH传输已被正确接收和解码，可以利用相同的HARQ进程进行新的上行数据传输。
通过这种隐式的方式，基站和UE可以都确认图6中利用更新的波束Beam#1进行的PUSCH传输是成功的，也就是说，基站和UE侧的PUSCH的波束更新都已完成，并且Beam#1的可靠性得到验证。
接下来，响应于确定PUSCH的波束更新完成，基站和UE可以将用于PUSCH的波束共用给其它信道，这是因为，PUSCH的传输成功表明其波束从时效性来说是质量最好的。因此，根据本公开的第二实施例，基站和UE可以例如将调度该PUSCH的PDCCH(CORESET#0)的波束Beam#0更新为Beam#1。这里考虑到了PUSCH和PDCCH的上下行信道的对称性，即，UE可以将PUSCH的上行发射波束用作PDCCH的下行接收波束，基站可以将PUSCH的上行接收波束用作PDCCH的下行发射波束。
根据第二实施例，PDCCH的波束更新可以在基站和UE侧自发进行，从而省略了专门用于PDCCH的波束更新的信令开销和时延。
随后，如果基站再次利用CORESET#0调度PUSCH，则基站将可以利用更新的Beam#1来发送承载DCI的PDCCH，而UE将可以利用更新的Beam#1来接收DCI。
另一方面，如果图6中所示的PUSCH未被成功接收，则基站可以重新调度PUSCH，以此作为隐式的否定反馈。基站再次利用Beam#0发送另一个DCI，这个DCI包含重新分配的时频资源和波束，这里，取决于基站侧的调度策略，DCI中指示的波束可以是之前的波束Beam#1，也可以是新的波束。此外，重新调度PUSCH的DCI中包含相同的HARQ进程ID和不反转的NDI，以命令UE执行数据重传。此时，基站和UE都知道先前的上行数据传输没有成功，原因有可能是所调度的Beam#1质量变差或受到了一定程度的阻挡，即Beam#1的可靠性没有经过验证。因此，基站和UE暂时不更新PDCCH的波束。
接下来的过程如上面所述的类似，这里不再赘述。如果重新调度PUSCH被正确解码，则基站和UE仍然可以将用于PDCCH的波束更新为DCI中指示的波束。
应注意，除了上面提到的TCI状态，还可以用空间关系信息(Spatial Relation Info)来指示用于PUSCH的波束。类似于TCI状态，空间关系信息中也包含所指示的传输信道(或参考信号)应与之具有QCL关系的参考信号的标识信息，诸如SSB_Index、NZP-CSI-RS-ResourceId或SRS-ResourceId等。空间关系信息和TCI状态从性质和功能上看是一样的，在适用的场景下可以互换地使用。
根据第二实施例，可以实现PDCCH的波束对PUSCH的波束跟随，从而实现这两种信道之间的波束共用。应理解，虽然上面是以基于DCI的PUSCH调度为例进行描述的，但是DCI还可以触发或者说调度上行参考信号，诸如SRS等，因此，第一实施例还可以实现PDCCH与上行参考信号之间的波束共用，原理类似，这里不再赘述。
【第三实施例】
上面的第一实施例和第二实施例中涉及的DCI具有数据调度的功能。但是其它格式的DCI可以不做任何数据调度，而仅仅起到信令的作用。本公开的第三实施例将忽略DCI的数据调度，而是使用DCI的动态信令来实现波束指示。
图7A示出了根据第三实施例的波束共用的示例的示意图。如图7A中所示，基站可以通过CORESET#0上的PDCCH发送DCI，来指示用于另一个CORESET(例如，图7A中例示的CORESET#1)上的PDCCH的波束。假设为CORESET#0上的PDCCH激活的波束是Beam#0。
基站可以通过例如上面所述的波束扫描过程来确定用于CORESET#1上的 PDCCH的波束，例如图7A中所示的Beam#1，Beam#1可以是在波束扫描中具有最佳传输表现的波束。基站可以在DCI中包含一个TCI状态，该TCI状态中包含关于与Beam#1相关联的参考信号的QCL信息。优选地，DCI中还可以包括CORESET#1的标识信息，以便于UE知道Beam#1是被指示给这个CORESET。
在UE侧，UE首先利用与CORESET#0对应的波束Beam#0(下行接收波束)来盲检PDCCH，以便接收其中承载的DCI。如果成功接收到该DCI，UE从中找到所包含的TCI状态，并理解应将该TCI状态所指示的波束(即Beam#1)用作接收CORESET#1上的PDCCH的波束。
但是需要考虑一个问题，对于一般的DCI不存在差错保护，即，如果UE漏检或者检测DCI失败，那么UE将不知道该DCI的内容。如果UE对于DCI的传输成功与否不进行反馈，则基站不知道该DCI是否被正确接收。这样可能导致基站和UE没有同步好该DCI中的波束更新信息，可能出现后续的发射波束与接收波束不匹配，造成控制信道的波束紊乱。
因此，这里设计了一种保护机制。对于根据第三实施例使用的DCI，UE使用HARQ机制来告知基站该DCI是否被正确接收。在一个例子中，如果UE正确解码DCI，则向基站发送ACK，否则向基站发送NACK。在另一个例子中，UE仅在未正确解码DCI时向基站发送NACK，而在正确解码DCI时，不向基站发送反馈，如果基站在发送完DCI后过去一定的时间间隔内未接收到NACK，则基站确认DCI已被正确接收。
通过对于DCI的反馈，基站和UE都可以知道DCI承担的波束指示已经成功，从而完成CORESET#1上的PDCCH的波束更新。即，基站将CORESET#1的下行发射波束更新为Beam#1(下行发射波束)，并且UE将CORESET#1的下行接收波束更新为Beam#1(下行接收波束)。
根据第三实施例，响应于PDCCH的波束更新完成，基站和UE可以实现该PDCCH与其调度的PDSCH之间的波束共用。具体而言，如图7A中所示，基站和UE可以将用于PDSCH的波束调整为Beam#1。由此可以实现PDSCH的波束对PDCCH的波束跟随。应理解，除了PDSCH以外，第三实施例还可以实现PDCCH与诸如CSI-RS等下行参考信号之间的波束共用，原理类似，这里不再赘述。
图7B示出了根据第三实施例的波束共用的另一个示例的示意图。如图7B中所示，基站可以通过CORESET#0上的PDCCH发送DCI，来指示用于PUCCH的波束。假设为CORESET#0上的PDCCH激活的波束是Beam#0。
基站可以通过例如上面所述的波束扫描过程来确定用于PUCCH的波束，例如图7B中所示的Beam#1，Beam#1可以是在波束扫描中具有最佳传输表现的波束。
基站可以在DCI中包含具有波束指示功能的PUCCH空间关系信息。图8示出了PUCCH空间关系信息的配置示意图。如图8中所示，PUCCH空间关系信息由PUCCH空间关系信息ID(PUCCH-SpatialRelationInfoId)标识，其中包括与Beam#1相关联的参考信号资源，诸如由NZP-CSI-RS-ResoureId标识的NZP-CSI-RS资源、由SSB-Index标识的SSB资源、以及由SRS-ResourceId和BWP-Id共同标识的SRS资源。如果PUCCH空间关系信息中配置的是SSB或NZP-CSI-RS，则UE应当利用用于接收该SSB或NZP-CSI-RS的空间接收参数来发送PUCCH。如果PUCCH空间关系信息中配置的是SRS，则UE应当利用用于发送该SRS的空间发射参数来发送PUCCH。
优选地，DCI中还可以包括PUCCH资源的标识信息，以便于UE知道Beam#1是被指示给这个PUCCH资源。
在UE侧，UE首先利用与CORESET#0对应的波束Beam#0(下行接收波束)来盲检PDCCH，以便接收其中承载的DCI。如果成功接收到该DCI，UE从中找到所包含的PUCCH空间关系信息，并理解应将该PUCCH空间关系信息所指示的波束(即Beam#1)用作发送PUCCH的波束。
同样地，UE使用HARQ机制来告知基站该DCI是否被正确接收。在一个例子中，如果UE正确解码DCI，则向基站发送ACK，否则向基站发送NACK。在另一个例子中，UE仅在未正确解码DCI时向基站发送NACK，而在正确解码DCI时，不向基站发送反馈，如果在基站在发送完DCI后过去一定的时间间隔内未接收到NACK，则基站确认DCI已被正确接收。优选地，由于HARQ反馈是通过PUCCH或PUSCH传输的，则可以考虑UE使用DCI中指示的波束(Beam#1)来发送PUCCH或PUSCH，从而验证该波束的可靠性。
通过对于DCI的反馈，基站和UE都可以知道DCI承担的波束指示已经成功， 从而完成相应PUCCH的波束更新。即，基站将PUCCH的上行接收波束更新为Beam#1(上行接收波束)，并且UE将CORESET#1的上行发射波束更新为Beam#1(上行发射波束)。
根据第三实施例，响应于PUCCH的波束更新完成，基站和UE可以实现该PUCCH与同为上行方向的PUSCH之间的波束共用。具体而言，如图7B中所示，基站和UE可以将用于PUSCH的波束调整为Beam#1。由此可以实现PUSCH的波束对PUCCH的波束跟随。
应注意，除了上面提到的PUCCH空间关系信息，还可以用上面提到的TCI状态来指示用于PUSCH的波束。空间关系信息和TCI状态在适用的场景下可以互换地使用。
应理解，根据第三实施例，还可以用PUCCH的波束来更新诸如SRS等上行参考信号的波束，以实现它们之间的波束共用，原理类似，这里不再赘述。
【第四实施例】
本公开的第四实施例涉及基于MAC CE指示的控制信道与下行信道/参考信号之间的波束共用。
对于诸如PDCCH或PUCCH之类的控制信道，可以通过RRC配置加MAC CE激活的方式来指示其波束。具体而言，基站通过RRC信令为UE配置一个TCI状态池，其中TCI状态池是以BWP为单位配置的，包括至多M个(M由基站配置，例如64或128)TCI状态。
当例如通过波束扫描过程确定了用于控制信道的波束时，基站可以从配置的TCI状态池中确定与该波束相关联的TCI状态，并通过PDSCH向UE发送包括该TCI状态的标识信息的MAC CE。
图10示出了用于PDCCH的TCI状态激活的MAC CE的格式(不包括头部)。如图10中所示，“服务小区ID”表示该MAC CE适用的服务小区，其占用5个比特；“CORESET ID”表示PDCCH所在的CORESET，其占用4个比特；“TCI状态ID”表示与为PDCCH确定的波束相关联的TCI状态，其占用7个比特。
图9示出了根据第四实施例的波束共用的示意图。在图9中例示了在分量载波CC 1的BWP A中为UE配置的TCI状态池，其中的黑色球代表示例性的TCI状态。 假设基站可以通过在MAC CE中指示TCI状态54，来为CORESET#X上的PDCCH激活或者说更新波束。响应于在PDSCH上正确接收该MAC CE，UE可以向基站反馈ACK，并且将用于CORESET#X的波束更新为TCI状态54中指示的波束，即，将用于接收CORESET#X上的PDCCH的下行接收波束更新为与TCI状态54中包含的参考信号相关联的波束。
根据第四实施例，UE可以将该PDCCH调度的PDSCH的波束更新为TCI状态54中指示的波束，对应地，基站将发送PDSCH的波束(下行发射波束)更新为用于发送PDCCH的波束。由此，基站和UE同步了实现PDCCH与PDSCH之间共用的波束。
类似地，上述MAC CE还可以用于实现CORESET#Y上的PDCCH与它所调度的周期性/半静态下行参考信号(例如P/SP CSI-RS)之间的波束共用，或者CORESET#Y上的PDCCH与它所调度的非周期性下行参考信号(例如AP CSI-RS)之间的波束共用。
另外，根据第四实施例，还可以通过上面的过程实现跨BWP、甚至跨分量载波(Component Carrier，CC)的波束共用。如图9中所示，MAC CE还可以激活TCI状态18，从而实现CC 1的另一个BWP(例如图9中所示的BWP B)中的CORESET#Z与它所调度的PDSCH和/或CSI-RS之间的波束共用，或者实现另一个CC(例如图9中所示的CC 2)中的CORESET#A与它所调度的PDSCH和/或CSI-RS之间的波束共用。
为了实现同一个TCI状态指示两个或更多个CORESET(它们可以在同一个BWP内、跨BWP或跨CC)，可以将与其相关联的CORESET的列表预先配置给UE。例如，基站可以预先配置TCI状态18与CORESET#Z、CORESET#A之间的关联，以便于UE理解MAC CE的波束指示目的，即使CORESET#Z、CORESET#A属于不同的BWP或CC。
【第五实施例】
本公开的第五实施例涉及基于MAC CE的控制信道与上行信道/参考信号之间的波束共用。
图11示出了根据第五实施例的波束共用的示意图。类似于参照图9描述的第四 实施例，基站可以在MAC CE中指示TCI状态54以激活CORESET#X上的PDCCH。响应于在PDSCH上正确接收该MAC CE，UE可以向基站反馈ACK，并且将CORESET#X的波束更新为TCI状态54中指示的波束。此外，UE可以将该PDCCH调度的PUSCH的波束(上行发射波束)更新为TCI状态54中指示的波束，基站也将发送PUSCH的波束(上行接收波束)更新为用于发送PDCCH的波束。由此，基站和UE同步了实现PDCCH与PDSCH之间共用的波束。
类似地，上述MAC CE还可以用于实现PDCCH(CORESET#X)与它所调度的非周期性上行参考信号(例如AP SRS)之间的波束共用。
此外，还可以通过MAC CE来指示用于PUCCH的波束。图12示出了用于PUCCH的TCI状态激活的MAC CE的格式(不包括头部)。如图12中所示，“R”表示预留字段，其占用1个比特；“服务小区ID”表示该MAC CE适用的服务小区，其占用4个比特；“BWP ID”表示PUCCH资源所在的CORESET，其占用3个比特；“PUCCH资源ID”表示PUCCH资源；“S i”表示为该PUCCH资源配置的PUCCH_SpatialRelationInfoId＝i+1的PUCCH空间关系信息的激活状态，其被设置为“1”是表示被激活，而被设置为“0”是表示不被激活。
如图11中所示，假设基站可以通过在MAC CE中指示TCI状态54，来为PUCCH资源#Y上的PUCCH激活或者说更新波束。当用于PUCCH的波束更新完成后，基站和UE可将同为上行方向上的PUSCH的波束更新为MAC CE中指示的波束，从而实现PUCCH与PUSCH之间的波束共用。
类似地，通过MAC CE中的TCI状态54，还可以实现PUCCH(PUCCH资源#Y)与周期性/半静态上行参考信号(例如P/SP SRS)之间的波束共用。
另外，根据第四实施例，还可以通过上面的过程实现跨BWP、甚至跨CC的波束共用。如图11中所示，MAC CE还可以激活TCI状态18，从而实现CC 1的另一个BWP(例如图11中所示的BWP B)中的PUCCH资源#Z与它所调度的PUSCH和/或SRS之间的波束共用，或者实现另一个CC(例如图11中所示的CC 2)中的CORESET#A与它所调度的PUSCH和/或SRS之间的波束共用。
为了实现同一个TCI状态指示两个或更多个控制信道(它们可以在同一个BWP内、跨BWP或跨CC)，可以将与其相关联的CORESET和/或PUCCH资源 的列表预先配置给UE。例如，基站可以预先配置TCI状态18与PUCCH资源#Z、CORESET#A之间的关联，以便于UE理解MAC CE的波束指示目的。
上面的第一至第五实施例已经描述了根据本公开的波束共用的示例。但是应理解，本公开旨在实现各种传输信道和参考信号之间的波束共用，不限于上述实施例中的共用组合。应注意，上面所述的共用波束的两个或更多个信道或参考信号是指同一个传输接收点(TRP)内的信道或信号。
【电子设备和通信方法】
接下来描述可以实施本公开的电子设备和通信方法。
图13A是例示了根据本公开的电子设备1000的框图。电子设备1000可以是基站设备或其部件。
如图13A中所示，电子设备1000包括处理电路1001。处理电路1001至少包括波束确定单元1002、波束指示单元1003和波束更新单元1004。处理电路1001可被配置为执行图13B中所示的通信方法。
处理电路1001中的波束确定单元1002被配置为确定用于基站与UE之间的第一传输信道的第一波束，即执行图13B中的步骤S1001。波束确定单元1002可以例如通过波束扫描过程从一组候选波束中选择出具有最佳传输质量的波束作为第一波束。
波束指示单元1003被配置为向所述UE发送包含关于第一波束的波束指示信息的动态信令，以使得用于第一传输信道的波束被更新为第一波束，即执行图13B中的步骤S1002。波束指示单元1003可以通过MAC CE或DCI发送波束指示信息。取决于第一传输信道是上行信道还是下行信道，波束指示信息可以是与波束确定单元1002确定的第一波束相关联的TCI状态或者空间关系信息。UE可以利用波束指示信息来更新用于第一传输信道的波束。
波束更新单元1004被配置为在用于第一传输信道的波束的更新成功的情况下，将用于基站与UE之间的第二传输信道和/或参考信号的波束更新为第一波束，即执行图13B中的步骤S1003。波束更新单元1004可以在从UE接收到对于波束指示单元1003发送的动态信令的显式肯定反馈或未接收到显式否定反馈时执行第二传输信道或参考信号的波束更新。可替代地，波束更新单元1003可以在第一传输信道利用第一波束的传输成功时执行第二传输信道或参考信号的波束更新。
电子设备1000还可以包括例如通信单元1005和存储器1006。
通信单元1005可以被配置为在处理电路1001的控制下与UE设备(例如下面将描述的电子设备2000)进行通信。在一个示例中，通信单元1005可以被实现为发射机或收发机，包括天线阵列和/或射频链路等通信部件。通信单元1005用虚线绘出，因为它还可以位于电子设备1000外。
电子设备1000还可以包括存储器1006。存储器1006可以存储各种数据和指令、用于电子设备1000操作的程序和数据、由处理电路1001产生的各种数据、由通信单元1005接收的数据等。
图14A是例示了根据本公开的电子设备2000的框图。电子设备2000可以是UE设备或其部件。
如图14A中所示，电子设备2000包括处理电路2001。处理电路2001至少包括波束指示接收单元2002和波束更新单元2003。处理电路2001可被配置为执行图14B中所示的通信方法。
处理电路2001的波束指示接收单元2002被配置为从基站接收包含关于第一波束的波束指示信息的动态信令即执行图14B中的步骤S2001。第一波束被确定用于UE与基站之间的第一传输信道。动态信令可以是DCI或MAC CE，并包括TCI状态或空间关系信息的标识信息作为波束指示信息。
波束更新单元2003被配置为将用于第一传输信道的波束更新为由波束指示信息指示的第一波束，即执行图14B中的步骤S2002。
在用于第一传输信道的波束的更新成功的情况下，波束更新单元2003还被配置为将用于UE与基站之间的第二传输信道和/或参考信号的波束更新为第一波束，即执行图14B中的步骤S2002。在一个示例中，波束更新单元2003可以在成功接收到动态信令时执行第二传输信道或参考信号的波束更新。可替代地，波束更新单元2003可以在第一传输信道利用第一波束的传输成功时执行第二传输信道或参考信号的波束更新。
电子设备2000还可以包括例如通信单元2005和存储器2006。
通信单元2005可以被配置为在处理电路2001的控制下与基站进行通信。在一个示例中，通信单元2005可以被实现为发射机或收发机，包括天线阵列和/或射频链路等通信部件。通信单元2005用虚线绘出，因为它还可以位于电子设备2000外。
电子设备2000还可以包括存储器2006。存储器2006可以存储各种数据和指令，例如用于电子设备2000操作的程序和数据、由处理电路2001产生的各种数据、将由通信单元2005发送的各种控制信令或业务数据等。存储器2006用虚线绘出，因为它还可以位于处理电路2001内或者位于电子设备2000外。
上面已经详细描述了本公开的实施例的各个方面，但是应注意，上面为了描述了所示出的天线阵列的结构、布置、类型、数量等，端口，参考信号，通信设备，通信方法等等，都不是为了将本公开的方面限制到这些具体的示例。
应当理解，上述各实施例中描述的电子设备1000、2000的各个单元仅是根据其所实现的具体功能划分的逻辑模块，而不是用于限制具体的实现方式。在实际实现时，上述各单元可被实现为独立的物理实体，或者也可以由单个实体(例如，处理器(CPU或DSP等)、集成电路等)来实现。
【本公开的示例性实现】
根据本公开的实施例，可以想到各种实现本公开的概念的实现方式，包括但不限于：
1)、一种基站侧的电子设备，包括：处理电路，被配置为：确定用于所述基站与UE之间的第一传输信道的第一波束；向所述UE发送包含关于第一波束的波束指示信息的动态信令，以使得用于第一传输信道的波束被更新为第一波束；以及在用于第一传输信道的波束的更新成功的情况下，将用于所述基站与所述UE之间的第二传输信道和/或参考信号的波束更新为第一波束。
2)、如1)所述的电子设备，其中，所述动态信令是下行控制信息(DCI)，并且其中，第一传输信道是物理下行共享信道(PDSCH)或物理上行数据信道(PUSCH)，第二传输信道是调度所述PDSCH或PUSCH的物理下行控制信道(PDCCH)。
3)、如1)所述的电子设备，其中，所述动态信令包括下行控制信息(DCI)，并且其中，第一传输信道是物理下行控制信道(PDCCH)或物理上行控制信道(PUCCH)，第二传输信道是物理下行共享信道(PDSCH)或物理上行数据信道(PUSCH)。
4)、如1)所述的电子设备，其中，所述动态信令包括介质接入控制(MAC)控制元素(CE)，并且其中，第一传输信道是物理下行控制信道(PDCCH)，第二传输信道是由该PDCCH调度的物理下行共享信道(PDSCH)。
5)、如1)所述的电子设备，其中，所述动态信令是介质接入控制(MAC)控制元素(CE)，并且其中，第一传输信道是物理上行控制信道(PUCCH)，第二传输信道是物理上行数据信道(PUSCH)。
6)、如2)所述的电子设备，其中，所述处理电路进一步被配置为：利用第一波束发送所述PDSCH或接收所述PUSCH；在所述PDSCH或PUSCH的传输成功的情况下，确认用于第一传输信道的波束的更新成功。
7)、如3)-5)中任一项所述的电子设备，其中，所述处理电路进一步被配置为：在从所述UE接收到对于所述动态信令的肯定反馈(ACK)或未接收到对于所述动态信令的否定反馈(NACK)的情况下，确认用于第一传输信道的波束的更新成功。
8)、如4)或5)所述的电子设备，其中，所述第一传输信道包括以下之一：在同一个带宽部分(BWP)内的多个传输信道、在同一个分量载波(CC)的不同BWP内的多个传输信道、或者在不同CC内的多个传输信道。
9)、如1)所述的电子设备，其中，所述波束指示信息包括传输配置指示符(TCI)状态或空间关系信息。
10)、一种UE侧的电子设备，包括：处理电路，被配置为：从基站接收包含关于第一波束的波束指示信息的动态信令，第一波束被确定用于所述UE与所述基站之间的第一传输信道；将用于第一传输信道的波束更新为第一波束；以及在用于第一传输信道的波束的更新成功的情况下，将用于所述UE与所述基站之间的第二传输信道和/或参考信号的波束更新为第一波束。
11)、如10)所述的电子设备，其中，所述动态信令是下行控制信息(DCI)，并且其中，第一传输信道是物理下行共享信道(PDSCH)或物理上行数据信道(PUSCH)，第二传输信道是调度所述PDSCH或PUSCH的物理下行控制信道(PDCCH)。
12)、如10)所述的电子设备，其中，所述动态信令是下行控制信息(DCI)，并且其中，第一传输信道是物理下行控制信道(PDCCH)或物理上行控制信道(PUCCH)，第二传输信道是物理下行共享信道(PDSCH)或物理上行数据信道(PUSCH)。
13)、如10)所述的电子设备，其中，所述动态信令是介质接入控制(MAC)控制元素(CE)，并且其中，第一传输信道是物理下行控制信道(PDCCH)，第二传输信道是由该PDCCH调度的物理下行共享信道(PDSCH)。
14)、如10)所述的电子设备，其中，所述动态信令是介质接入控制(MAC)控制元素(CE)，并且其中，第一传输信道是物理上行控制信道(PUCCH)，第二传输信道是物理上行数据信道(PUSCH)。
15)、如11)所述的电子设备，其中，所述处理电路进一步被配置为：利用第一波束接收所述PDSCH或发送所述PUSCH；在所述PDSCH或PUSCH的传输成功的情况下，确认用于第一传输信道的波束的更新成功。
16)、如12)-14)中任一项所述的电子设备，其中，所述处理电路进一步被配置为：在成功接收所述动态信令的情况下，确认用于第一传输信道的波束的更新成功，并向所述基站发送对于所述动态信令的肯定反馈(ACK)或不发送对于所述动态信令的否定反馈(NACK)。
17)、如13)或14)所述的电子设备，其中，所述第一传输信道包括以下之一：在同一个带宽部分(BWP)内的多个传输信道、在同一个分量载波(CC)的不同BWP内的多个传输信道、或者在不同CC内的多个传输信道。
18)、一种通信方法，包括：确定用于所述基站与UE之间的第一传输信道的第一波束；向所述UE发送包含关于第一波束的波束指示信息的动态信令，以使得用于第一传输信道的波束被更新为第一波束；以及在用于第一传输信道的波束的更新成功的情况下，将用于所述基站与所述UE之间的第二传输信道和/或参考信号的波束更新为第一波束。
19)、一种通信方法，包括：从基站接收包含关于第一波束的波束指示信息的动态信令，第一波束被确定用于所述UE与所述基站之间的第一传输信道；将用于 第一传输信道的波束更新为第一波束；以及在用于第一传输信道的波束的更新成功的情况下，将用于所述UE与所述基站之间的第二传输信道和/或参考信号的波束更新为第一波束。
20)、一种存储有可执行指令的非暂时性计算机可读存储介质，所述可执行指令当被执行时实现如18)或19)所述的通信方法。
【本公开的应用实例】
本公开中描述的技术能够应用于各种产品。
例如，根据本公开的实施例的电子设备1000可以被实现为各种基站或者安装在基站中，电子设备2000可以被实现为各种用户设备或被安装在各种用户设备中。
根据本公开的实施例的通信方法可以由各种基站或用户设备实现；根据本公开的实施例的方法和操作可以体现为计算机可执行指令，存储在非暂时性计算机可读存储介质中，并可以由各种基站或用户设备执行以实现上面所述的一个或多个功能。
根据本公开的实施例的技术可以制成各个计算机程序产品，被用于各种基站或用户设备以实现上面所述的一个或多个功能。
应注意，本公开中所使用的术语“基站”不仅限于上面这两种节点，而是作为网络侧的控制设备的示例，并具有其通常含义的全部广度。本公开中所说的基站可以被实现为任何类型的基站，优选地，诸如3GPP的5G NR标准中定义的宏gNB和ng-eNB。gNB可以是覆盖比宏小区小的小区的gNB，诸如微微gNB、微gNB和家庭(毫微微)gNB。代替地，基站可以被实现为任何其他类型的基站，诸如NodeB、eNodeB和基站收发台(BTS)。基站还可以包括：被配置为控制无线通信的主体以及设置在与主体不同的地方的一个或多个远程无线头端(RRH)、无线中继站、无人机塔台、自动化工厂中的控制节点等。
另外，在本公开中，术语“UE”具有其通常含义的全部广度，包括与基站通信的各种终端设备或车载设备。UE可以被实现为移动终端(诸如智能电话、平板个人计算机(PC)、笔记本式PC、便携式游戏终端、便携式/加密狗型移动路由器和数字摄像装置)或者车载终端(诸如汽车导航设备)。UE还可以被实现为执行机器对机器(M2M)通信的终端(也称为机器类型通信(MTC)终端)、无人机、自动化工 厂中的传感器和执行器等。此外，用户设备可以为安装在上述终端中的每个终端上的无线通信模块(诸如包括单个晶片的集成电路模块)。
下面简单介绍可以应用本公开的技术的基站和UE的应用示例。
基站的第一应用示例
图15是示出可以应用本公开内容的技术的基站的示意性配置的第一示例的框图。在图15中，基站可以实现为gNB 1400。gNB 1400包括多个天线1410以及基站设备1420。基站设备1420和每个天线1410可以经由RF线缆彼此连接。在一种实现方式中，此处的gNB 1400(或基站设备1420)可以对应于上述电子设备1000。
天线1410包括多个天线元件，诸如用于大规模MIMO的多个天线阵列。天线1410例如可以被布置成天线阵列矩阵，并且用于基站设备1420发送和接收无线信号。例如，多个天线1410可以与gNB 1400使用的多个频段兼容。
基站设备1420包括控制器1421、存储器1422、网络接口1423以及无线通信接口1425。
控制器1421可以为例如CPU或DSP，并且操作基站设备1420的较高层的各种功能。例如，控制器1421可以包括上面所述的处理电路1001，执行图13B中描述的通信方法，或者控制电子设备1000的各个部件。例如，控制器1421根据由无线通信接口1425处理的信号中的数据来生成数据分组，并经由网络接口1423来传递所生成的分组。控制器1421可以对来自多个基带处理器的数据进行捆绑以生成捆绑分组，并传递所生成的捆绑分组。控制器1421可以具有执行如下控制的逻辑功能：该控制诸如为无线资源控制、无线承载控制、移动性管理、接纳控制和调度。该控制可以结合附近的gNB或核心网节点来执行。存储器1422包括RAM和ROM，并且存储由控制器1421执行的程序和各种类型的控制数据(诸如终端列表、传输功率数据以及调度数据)。
网络接口1423为用于将基站设备1420连接至核心网1424(例如，5G核心网)的通信接口。控制器1421可以经由网络接口1423而与核心网节点或另外的gNB进行通信。在此情况下，gNB 1400与核心网节点或其他gNB可以通过逻辑接口(诸如NG接口和Xn接口)而彼此连接。网络接口1423还可以为有线通信接口或用于无线回程线路的无线通信接口。如果网络接口1423为无线通信接口，则与由无线通信接口1425 使用的频段相比，网络接口1423可以使用较高频段用于无线通信。
无线通信接口1425支持任何蜂窝通信方案(诸如5G NR)，并且经由天线1410来提供到位于gNB 1400的小区中的终端的无线连接。无线通信接口1425通常可以包括例如基带(BB)处理器1426和RF电路1427。BB处理器1426可以执行例如编码/解码、调制/解调以及复用/解复用，并且执行各层(例如物理层、MAC层、RLC层、PDCP层、SDAP层)的各种类型的信号处理。代替控制器1421，BB处理器1426可以具有上述逻辑功能的一部分或全部。BB处理器1426可以为存储通信控制程序的存储器，或者为包括被配置为执行程序的处理器和相关电路的模块。更新程序可以使BB处理器1426的功能改变。该模块可以为插入到基站设备1420的槽中的卡或刀片。可替代地，该模块也可以为安装在卡或刀片上的芯片。同时，RF电路1427可以包括例如混频器、滤波器和放大器，并且经由天线1410来传送和接收无线信号。虽然图15示出一个RF电路1427与一根天线1410连接的示例，但是本公开并不限于该图示，而是一个RF电路1427可以同时连接多根天线1410。
如图15所示，无线通信接口1425可以包括多个BB处理器1426。例如，多个BB处理器1426可以与gNB 1400使用的多个频段兼容。如图15所示，无线通信接口1425可以包括多个RF电路1427。例如，多个RF电路1427可以与多个天线元件兼容。虽然图15示出其中无线通信接口1425包括多个BB处理器1426和多个RF电路1427的示例，但是无线通信接口1425也可以包括单个BB处理器1426或单个RF电路1427。
在图15中示出的gNB 1400中，参照图13A描述的处理电路1001中包括的一个或多个单元可被实现在无线通信接口1425中。可替代地，这些组件中的至少一部分可被实现在控制器1421中。例如，gNB 1400包含无线通信接口1425的一部分(例如，BB处理器1426)或者整体，和/或包括控制器1421的模块，并且一个或多个组件可被实现在模块中。在这种情况下，模块可以存储用于允许处理器起一个或多个组件的作用的程序(换言之，用于允许处理器执行一个或多个组件的操作的程序)，并且可以执行该程序。作为另一个示例，用于允许处理器起一个或多个组件的作用的程序可被安装在gNB 1400中，并且无线通信接口1425(例如，BB处理器1426)和/或控制器1421可以执行该程序。如上所述，作为包括一个或多个组件的装置，gNB 1400、基站设备1420或模块可被提供，并且用于允许处理器起一个或多个 组件的作用的程序可被提供。另外，将程序记录在其中的可读介质可被提供。
基站的第二应用示例
图16是示出可以应用本公开的技术的基站的示意性配置的第二示例的框图。在图16中，基站被示出为gNB 1530。gNB 1530包括多个天线1540、基站设备1550和RRH 1560。RRH 1560和每个天线1540可以经由RF线缆而彼此连接。基站设备1550和RRH 1560可以经由诸如光纤线缆的高速线路而彼此连接。在一种实现方式中，此处的gNB 1530(或基站设备1550)可以对应于上述电子设备1000。
天线1540包括多个天线元件，诸如用于大规模MIMO的多个天线阵列。天线1540例如可以被布置成天线阵列矩阵，并且用于基站设备1550发送和接收无线信号。例如，多个天线1540可以与gNB 1530使用的多个频段兼容。
基站设备1550包括控制器1551、存储器1552、网络接口1553、无线通信接口1555以及连接接口1557。控制器1551、存储器1552和网络接口1553与参照图15描述的控制器1421、存储器1422和网络接口1423相同。
无线通信接口1555支持任何蜂窝通信方案(诸如5G NR)，并且经由RRH 1560和天线1540来提供到位于与RRH 1560对应的扇区中的终端的无线通信。无线通信接口1555通常可以包括例如BB处理器1556。除了BB处理器1556经由连接接口1557连接到RRH 1560的RF电路1564之外，BB处理器1556与参照图15描述的BB处理器1426相同。如图16所示，无线通信接口1555可以包括多个BB处理器1556。例如，多个BB处理器1556可以与gNB 1530使用的多个频段兼容。虽然图16示出其中无线通信接口1555包括多个BB处理器1556的示例，但是无线通信接口1555也可以包括单个BB处理器1556。
连接接口1557为用于将基站设备1550(无线通信接口1555)连接至RRH 1560的接口。连接接口1557还可以为用于将基站设备1550(无线通信接口1555)连接至RRH 1560的上述高速线路中的通信的通信模块。
RRH 1560包括连接接口1561和无线通信接口1563。
连接接口1561为用于将RRH 1560(无线通信接口1563)连接至基站设备1550的接口。连接接口1561还可以为用于上述高速线路中的通信的通信模块。
无线通信接口1563经由天线1540来传送和接收无线信号。无线通信接口1563通常可以包括例如RF电路1564。RF电路1564可以包括例如混频器、滤波器和放大器，并且经由天线1540来传送和接收无线信号。虽然图16示出一个RF电路1564与一根天线1540连接的示例，但是本公开并不限于该图示，而是一个RF电路1564可以同时连接多根天线1540。
如图16所示，无线通信接口1563可以包括多个RF电路1564。例如，多个RF电路1564可以支持多个天线元件。虽然图16示出其中无线通信接口1563包括多个RF电路1564的示例，但是无线通信接口1563也可以包括单个RF电路1564。
在图16中示出的gNB 1500中，参照图13A描述的处理电路1001中包括的一个或多个单元可被实现在无线通信接口1525中。可替代地，这些组件中的至少一部分可被实现在控制器1521中。例如，gNB 1500包含无线通信接口1525的一部分(例如，BB处理器1526)或者整体，和/或包括控制器1521的模块，并且一个或多个组件可被实现在模块中。在这种情况下，模块可以存储用于允许处理器起一个或多个组件的作用的程序(换言之，用于允许处理器执行一个或多个组件的操作的程序)，并且可以执行该程序。作为另一个示例，用于允许处理器起一个或多个组件的作用的程序可被安装在gNB 1500中，并且无线通信接口1525(例如，BB处理器1526)和/或控制器1521可以执行该程序。如上所述，作为包括一个或多个组件的装置，gNB 1500、基站设备1520或模块可被提供，并且用于允许处理器起一个或多个组件的作用的程序可被提供。另外，将程序记录在其中的可读介质可被提供。
用户设备的第一应用示例
图17是示出可以应用本公开内容的技术的智能电话1600的示意性配置的示例的框图。在一个示例中，智能电话1600可以被实现为参照图14A描述的电子设备2000。
智能电话1600包括处理器1601、存储器1602、存储装置1603、外部连接接口1604、摄像装置1606、传感器1607、麦克风1608、输入装置1609、显示装置1610、扬声器1611、无线通信接口1612、一个或多个天线开关1615、一个或多个天线1616、总线1617、电池1618以及辅助控制器1619。
处理器1601可以为例如CPU或片上系统(SoC)，并且控制智能电话1600的应 用层和另外层的功能。处理器1601可以包括或充当参照图14A描述的处理电路2001。存储器1602包括RAM和ROM，并且存储数据和由处理器1601执行的程序。存储装置1603可以包括存储介质，诸如半导体存储器和硬盘。外部连接接口1604为用于将外部装置(诸如存储卡和通用串行总线(USB)装置)连接至智能电话1600的接口。
摄像装置1606包括图像传感器(诸如电荷耦合器件(CCD)和互补金属氧化物半导体(CMOS))，并且生成捕获图像。传感器1607可以包括一组传感器，诸如测量传感器、陀螺仪传感器、地磁传感器和加速度传感器。麦克风1608将输入到智能电话1600的声音转换为音频信号。输入装置1609包括例如被配置为检测显示装置1610的屏幕上的触摸的触摸传感器、小键盘、键盘、按钮或开关，并且接收从用户输入的操作或信息。显示装置1610包括屏幕(诸如液晶显示器(LCD)和有机发光二极管(OLED)显示器)，并且显示智能电话1600的输出图像。扬声器1611将从智能电话1600输出的音频信号转换为声音。
无线通信接口1612支持任何蜂窝通信方案(诸如4G LTE或5G NR等等)，并且执行无线通信。无线通信接口1612通常可以包括例如BB处理器1613和RF电路1614。BB处理器1613可以执行例如编码/解码、调制/解调以及复用/解复用，并且执行用于无线通信的各种类型的信号处理。同时，RF电路1614可以包括例如混频器、滤波器和放大器，并且经由天线1616来传送和接收无线信号。无线通信接口1612可以为其上集成有BB处理器1613和RF电路1614的一个芯片模块。如图17所示，无线通信接口1612可以包括多个BB处理器1613和多个RF电路1614。虽然图17示出其中无线通信接口1612包括多个BB处理器1613和多个RF电路1614的示例，但是无线通信接口1612也可以包括单个BB处理器1613或单个RF电路1614。
此外，除了蜂窝通信方案之外，无线通信接口1612可以支持另外类型的无线通信方案，诸如短距离无线通信方案、近场通信方案和无线局域网(LAN)方案。在此情况下，无线通信接口1612可以包括针对每种无线通信方案的BB处理器1613和RF电路1614。
天线开关1615中的每一个在包括在无线通信接口1612中的多个电路(例如用于不同的无线通信方案的电路)之间切换天线1616的连接目的地。
天线1616包括多个天线元件，诸如用于大规模MIMO的多个天线阵列。天线 1616例如可以被布置成天线阵列矩阵，并且用于无线通信接口1612传送和接收无线信号。智能电话1600可以包括一个或多个天线面板(未示出)。
此外，智能电话1600可以包括针对每种无线通信方案的天线1616。在此情况下，天线开关1615可以从智能电话1600的配置中省略。
总线1617将处理器1601、存储器1602、存储装置1603、外部连接接口1604、摄像装置1606、传感器1607、麦克风1608、输入装置1609、显示装置1610、扬声器1611、无线通信接口1612以及辅助控制器1619彼此连接。电池1618经由馈线向图17所示的智能电话1600的各个块提供电力，馈线在图中被部分地示为虚线。辅助控制器1619例如在睡眠模式下操作智能电话1600的最小必需功能。
在图17中示出的智能电话1600中，参照图14A描述的处理电路2001中包括的一个或多个组件可被实现在无线通信接口1612中。可替代地，这些组件中的至少一部分可被实现在处理器1601或者辅助控制器1619中。作为一个示例，智能电话1600包含无线通信接口1612的一部分(例如，BB处理器1613)或者整体，和/或包括处理器1601和/或辅助控制器1619的模块，并且一个或多个组件可被实现在该模块中。在这种情况下，该模块可以存储允许处理起一个或多个组件的作用的程序(换言之，用于允许处理器执行一个或多个组件的操作的程序)，并且可以执行该程序。作为另一个示例，用于允许处理器起一个或多个组件的作用的程序可被安装在智能电话1600中，并且无线通信接口1612(例如，BB处理器1613)、处理器1601和/或辅助控制器1619可以执行该程序。如上所述，作为包括一个或多个组件的装置，智能电话1600或者模块可被提供，并且用于允许处理器起一个或多个组件的作用的程序可被提供。另外，将程序记录在其中的可读介质可被提供。
用户设备的第二应用示例
图18是示出可以应用本公开的技术的汽车导航设备1720的示意性配置的示例的框图。汽车导航设备1720可以被实现为参照图14A描述的电子设备2000。汽车导航设备1720包括处理器1721、存储器1722、全球定位系统(GPS)模块1724、传感器1725、数据接口1726、内容播放器1727、存储介质接口1728、输入装置1729、显示装置1730、扬声器1731、无线通信接口1733、一个或多个天线开关1736、一个或多个天线1737以及电池1738。
处理器1721可以为例如CPU或SoC，并且控制汽车导航设备1720的导航功能和另外的功能。存储器1722包括RAM和ROM，并且存储数据和由处理器1721执行的程序。
GPS模块1724使用从GPS卫星接收的GPS信号来测量汽车导航设备1720的位置(诸如纬度、经度和高度)。传感器1725可以包括一组传感器，诸如陀螺仪传感器、地磁传感器和空气压力传感器。数据接口1726经由未示出的终端而连接到例如车载网络1741，并且获取由车辆生成的数据(诸如车速数据)。
内容播放器1727再现存储在存储介质(诸如CD和DVD)中的内容，该存储介质被插入到存储介质接口1728中。输入装置1729包括例如被配置为检测显示装置1730的屏幕上的触摸的触摸传感器、按钮或开关，并且接收从用户输入的操作或信息。显示装置1730包括诸如LCD或OLED显示器的屏幕，并且显示导航功能的图像或再现的内容。扬声器1731输出导航功能的声音或再现的内容。
无线通信接口1733支持任何蜂窝通信方案(诸如4G LTE或5G NR)，并且执行无线通信。无线通信接口1733通常可以包括例如BB处理器1734和RF电路1735。BB处理器1734可以执行例如编码/解码、调制/解调以及复用/解复用，并且执行用于无线通信的各种类型的信号处理。同时，RF电路1735可以包括例如混频器、滤波器和放大器，并且经由天线1737来传送和接收无线信号。无线通信接口1733还可以为其上集成有BB处理器1734和RF电路1735的一个芯片模块。如图18所示，无线通信接口1733可以包括多个BB处理器1734和多个RF电路1735。虽然图18示出其中无线通信接口1733包括多个BB处理器1734和多个RF电路1735的示例，但是无线通信接口1733也可以包括单个BB处理器1734或单个RF电路1735。
此外，除了蜂窝通信方案之外，无线通信接口1733可以支持另外类型的无线通信方案，诸如短距离无线通信方案、近场通信方案和无线LAN方案。在此情况下，针对每种无线通信方案，无线通信接口1733可以包括BB处理器1734和RF电路1735。
天线开关1736中的每一个在包括在无线通信接口1733中的多个电路(诸如用于不同的无线通信方案的电路)之间切换天线1737的连接目的地。
天线1737包括多个天线元件，诸如用于大规模MIMO的多个天线阵列。天线 1737例如可以被布置成天线阵列矩阵，并且用于无线通信接口1733传送和接收无线信号。
此外，汽车导航设备1720可以包括针对每种无线通信方案的天线1737。在此情况下，天线开关1736可以从汽车导航设备1720的配置中省略。
电池1738经由馈线向图18所示的汽车导航设备1720的各个块提供电力，馈线在图中被部分地示为虚线。电池1738累积从车辆提供的电力。
在图18中示出的汽车导航装置1720中，参照图14A描述的处理电路2001中包括的一个或多个组件可被实现在无线通信接口1733中。可替代地，这些组件中的至少一部分可被实现在处理器1721中。作为一个示例，汽车导航装置1720包含无线通信接口1733的一部分(例如，BB处理器1734)或者整体，和/或包括处理器1721的模块，并且一个或多个组件可被实现在该模块中。在这种情况下，该模块可以存储允许处理起一个或多个组件的作用的程序(换言之，用于允许处理器执行一个或多个组件的操作的程序)，并且可以执行该程序。作为另一个示例，用于允许处理器起一个或多个组件的作用的程序可被安装在汽车导航装置1720中，并且无线通信接口1733(例如，BB处理器1734)和/或处理器1721可以执行该程序。如上所述，作为包括一个或多个组件的装置，汽车导航装置1720或者模块可被提供，并且用于允许处理器起一个或多个组件的作用的程序可被提供。另外，将程序记录在其中的可读介质可被提供。
另外，在图18中示出的汽车导航装置1720中，例如，图14A的通信单元2005可被实现在无线通信接口1933(例如，RF电路1935)中。
本公开的技术也可以被实现为包括汽车导航设备1720、车载网络1741以及车辆模块1742中的一个或多个块的车载系统(或车辆)1740。车辆模块1742生成车辆数据(诸如车速、发动机速度和故障信息)，并且将所生成的数据输出至车载网络1741。
以上参照附图描述了本公开的示例性实施例，但是本公开当然不限于以上示例。本领域技术人员可在所附权利要求的范围内得到各种变更和修改，并且应理解这些变更和修改自然将落入本公开的技术范围内。
例如，在以上实施例中包括在一个单元中的多个功能可以由分开的装置来实现。替选地，在以上实施例中由多个单元实现的多个功能可分别由分开的装置来实现。另 外，以上功能之一可由多个单元来实现。无需说，这样的配置包括在本公开的技术范围内。
在该说明书中，流程图中所描述的步骤不仅包括以所述顺序按时间序列执行的处理，而且包括并行地或单独地而不是必须按时间序列执行的处理。此外，甚至在按时间序列处理的步骤中，无需说，也可以适当地改变该顺序。
虽然已经详细说明了本公开及其优点，但是应当理解在不脱离由所附的权利要求所限定的本公开的精神和范围的情况下可以进行各种改变、替代和变换。而且，本公开实施例的术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。

Claims (20)

  1. 一种基站侧的电子设备，包括：
    处理电路，被配置为：
    确定用于所述基站与UE之间的第一传输信道的第一波束；
    向所述UE发送包含关于第一波束的波束指示信息的动态信令，以使得用于第一传输信道的波束被更新为第一波束；以及
    在用于第一传输信道的波束的更新成功的情况下，将用于所述基站与所述UE之间的第二传输信道和/或参考信号的波束更新为第一波束。
  2. 如权利要求1所述的电子设备，其中，所述动态信令包括下行控制信息(DCI)，并且
    其中，第一传输信道是物理下行共享信道(PDSCH)或物理上行数据信道(PUSCH)，第二传输信道是调度所述PDSCH或PUSCH的物理下行控制信道(PDCCH)。
  3. 如权利要求1所述的电子设备，其中，所述动态信令包括下行控制信息(DCI)，并且
    其中，第一传输信道是物理下行控制信道(PDCCH)或物理上行控制信道(PUCCH)，第二传输信道是物理下行共享信道(PDSCH)或物理上行数据信道(PUSCH)。
  4. 如权利要求1所述的电子设备，其中，所述动态信令包括介质接入控制(MAC)控制元素(CE)，并且
    其中，第一传输信道是物理下行控制信道(PDCCH)，第二传输信道是由该PDCCH调度的物理下行共享信道(PDSCH)。
  5. 如权利要求1所述的电子设备，其中，所述动态信令包括介质接入控制(MAC)控制元素(CE)，并且
    其中，第一传输信道是物理上行控制信道(PUCCH)，第二传输信道是物理上 行数据信道(PUSCH)。
  6. 如权利要求2所述的电子设备，其中，所述处理电路进一步被配置为：
    利用第一波束发送所述PDSCH或接收所述PUSCH；
    在所述PDSCH或PUSCH的传输成功的情况下，确认用于第一传输信道的波束的更新成功。
  7. 如权利要求3-5中任一项所述的电子设备，其中，所述处理电路进一步被配置为：
    在从所述UE接收到对于所述动态信令的肯定反馈(ACK)或未接收到对于所述动态信令的否定反馈(NACK)的情况下，确认用于第一传输信道的波束的更新成功。
  8. 如权利要求4或5所述的电子设备，其中，所述第一传输信道包括以下之一：在同一个带宽部分(BWP)内的多个传输信道、在同一个分量载波(CC)的不同BWP内的多个传输信道、或者在不同CC内的多个传输信道。
  9. 如权利要求1所述的电子设备，其中，所述波束指示信息包括传输配置指示符(TCI)状态或空间关系信息。
  10. 一种UE侧的电子设备，包括：
    处理电路，被配置为：
    从基站接收包含关于第一波束的波束指示信息的动态信令，第一波束被确定用于所述UE与所述基站之间的第一传输信道；
    将用于第一传输信道的波束更新为第一波束；以及
    在用于第一传输信道的波束的更新成功的情况下，将用于所述UE与所述基站之间的第二传输信道和/或参考信号的波束更新为第一波束。
  11. 如权利要求10所述的电子设备，其中，所述动态信令是下行控制信息(DCI)，并且
    其中，第一传输信道是物理下行共享信道(PDSCH)或物理上行数据信道 (PUSCH)，第二传输信道是调度所述PDSCH或PUSCH的物理下行控制信道(PDCCH)。
  12. 如权利要求10所述的电子设备，其中，所述动态信令是下行控制信息(DCI)，并且
    其中，第一传输信道是物理下行控制信道(PDCCH)或物理上行控制信道(PUCCH)，第二传输信道是物理下行共享信道(PDSCH)或物理上行数据信道(PUSCH)。
  13. 如权利要求10所述的电子设备，其中，所述动态信令是介质接入控制(MAC)控制元素(CE)，并且
    其中，第一传输信道是物理下行控制信道(PDCCH)，第二传输信道是由该PDCCH调度的物理下行共享信道(PDSCH)。
  14. 如权利要求10所述的电子设备，其中，所述动态信令是介质接入控制(MAC)控制元素(CE)，并且
    其中，第一传输信道是物理上行控制信道(PUCCH)，第二传输信道是物理上行数据信道(PUSCH)。
  15. 如权利要求11所述的电子设备，其中，所述处理电路进一步被配置为：
    利用第一波束接收所述PDSCH或发送所述PUSCH；
    在所述PDSCH或PUSCH的传输成功的情况下，确认用于第一传输信道的波束的更新成功。
  16. 如权利要求12-14中任一项所述的电子设备，其中，所述处理电路进一步被配置为：
    在成功接收所述动态信令的情况下，确认用于第一传输信道的波束的更新成功，并向所述基站发送对于所述动态信令的肯定反馈(ACK)或不发送对于所述动态信令的否定反馈(NACK)。
  17. 如权利要求13或14所述的电子设备，其中，所述第一传输信道包括以下之一：在同一个带宽部分(BWP)内的多个传输信道、在同一个分量载波(CC)的不同BWP内的多个传输信道、或者在不同CC内的多个传输信道。
  18. 一种通信方法，包括：
    确定用于所述基站与UE之间的第一传输信道的第一波束；
    向所述UE发送包含关于第一波束的波束指示信息的动态信令，以使得用于第一传输信道的波束被更新为第一波束；以及
    在用于第一传输信道的波束的更新成功的情况下，将用于所述基站与所述UE之间的第二传输信道和/或参考信号的波束更新为第一波束。
  19. 一种通信方法，包括：
    从基站接收包含关于第一波束的波束指示信息的动态信令，第一波束被确定用于所述UE与所述基站之间的第一传输信道；
    将用于第一传输信道的波束更新为第一波束；以及
    在用于第一传输信道的波束的更新成功的情况下，将用于所述UE与所述基站之间的第二传输信道和/或参考信号的波束更新为第一波束。
  20. 一种存储有可执行指令的非暂时性计算机可读存储介质，所述可执行指令当被执行时实现如权利要求18或19所述的通信方法。
PCT/CN2021/124388 2020-10-22 2021-10-18 电子设备、通信方法和存储介质 Ceased WO2022083541A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
EP21881957.1A EP4207908A4 (en) 2020-10-22 2021-10-18 ELECTRONIC DEVICE, COMMUNICATION METHOD AND STORAGE MEDIUM
US18/247,274 US20230412231A1 (en) 2020-10-22 2021-10-18 Electronic device, communication method and storage medium
JP2023524832A JP2023547416A (ja) 2020-10-22 2021-10-18 電子機器、通信方法、及び記憶媒体
CN202180071344.XA CN116420408A (zh) 2020-10-22 2021-10-18 电子设备、通信方法和存储介质
KR1020237011958A KR20230092890A (ko) 2020-10-22 2021-10-18 전자 디바이스, 통신 방법 및 저장 매체

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011141631.7 2020-10-22
CN202011141631.7A CN114390696A (zh) 2020-10-22 2020-10-22 电子设备、通信方法和存储介质

Publications (1)

Publication Number Publication Date
WO2022083541A1 true WO2022083541A1 (zh) 2022-04-28

Family

ID=81194833

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/124388 Ceased WO2022083541A1 (zh) 2020-10-22 2021-10-18 电子设备、通信方法和存储介质

Country Status (6)

Country Link
US (1) US20230412231A1 (zh)
EP (1) EP4207908A4 (zh)
JP (1) JP2023547416A (zh)
KR (1) KR20230092890A (zh)
CN (2) CN114390696A (zh)
WO (1) WO2022083541A1 (zh)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI807458B (zh) * 2020-10-23 2023-07-01 瑞典商Lm艾瑞克生(Publ)電話公司 用於啟用正交振幅調變模式之方法及相關之使用者設備
US20240121797A1 (en) * 2021-03-11 2024-04-11 Lenovo (Beijing) Limited Method and apparatus for monitoring downlink control information
WO2023004663A1 (en) * 2021-07-29 2023-02-02 Qualcomm Incorporated Quasi co-location information for 3d beamforming in holographic multiple-input multiple-output systems
US12537659B2 (en) * 2022-08-19 2026-01-27 Qualcomm Incorporated Mapping of time and frequency resources to beams of a network node
WO2025099860A1 (ja) * 2023-11-08 2025-05-15 株式会社Ｎｔｔドコモ 端末、無線通信方法及び基地局
WO2025191860A1 (ja) * 2024-03-15 2025-09-18 株式会社Ｎｔｔドコモ 端末

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110120862A (zh) * 2018-02-06 2019-08-13 英特尔Ip公司 用于波束管理的装置和方法
CN110809901A (zh) * 2018-02-14 2020-02-18 Oppo广东移动通信有限公司 物理上行共享信道传输方法和终端设备
WO2020036433A1 (ko) * 2018-08-17 2020-02-20 삼성전자 주식회사 무선 통신 시스템에서의 빔 정보 설정 및 지시 방법 및 장치
WO2020132191A1 (en) * 2018-12-20 2020-06-25 Qualcomm Incorporated Quasi co-location reset for a user equipment supporting a single active transmission configuration indication state
WO2020132198A1 (en) * 2018-12-20 2020-06-25 Qualcomm Incorporated Transmission configuration indication determination for a shared data channel

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9900891B1 (en) * 2016-12-20 2018-02-20 Qualcomm Incorporated Fallback beam selection procedure during failure of beam change instruction reception
US10602520B2 (en) * 2017-03-24 2020-03-24 Qualcomm Incorporated Multi-link control beam switching
US10849152B2 (en) * 2018-01-09 2020-11-24 Apple Inc. Beam management for carrier aggregation (CA)
US11272576B2 (en) * 2018-02-15 2022-03-08 Apple Inc. Hierarchical beamforming structure and transmission of beam indication to improve device mobility and reduce network traffic overhead in new radio (NR)
US11109380B2 (en) * 2018-04-05 2021-08-31 Qualcomm Incorporated Uplink control channel beam switch procedure
US11757517B2 (en) * 2019-02-22 2023-09-12 Beijing Xiaomi Mobile Software Co., Ltd. Data transmission method and apparatus, and storage medium

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110120862A (zh) * 2018-02-06 2019-08-13 英特尔Ip公司 用于波束管理的装置和方法
CN110809901A (zh) * 2018-02-14 2020-02-18 Oppo广东移动通信有限公司 物理上行共享信道传输方法和终端设备
WO2020036433A1 (ko) * 2018-08-17 2020-02-20 삼성전자 주식회사 무선 통신 시스템에서의 빔 정보 설정 및 지시 방법 및 장치
WO2020132191A1 (en) * 2018-12-20 2020-06-25 Qualcomm Incorporated Quasi co-location reset for a user equipment supporting a single active transmission configuration indication state
WO2020132198A1 (en) * 2018-12-20 2020-06-25 Qualcomm Incorporated Transmission configuration indication determination for a shared data channel

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "On common beam for PDSCH and PDCCH", 3GPP TSG_RAN\WG1_RL1; R1-1718746, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), SOPHIA-ANTIPOLIS CEDEX ; FRANCE, 3 October 2017 (2017-10-03), Prague, Czech Republic; 20171009 - 20171013, XP051353234 *
See also references of EP4207908A4 *

Also Published As

Publication number Publication date
KR20230092890A (ko) 2023-06-26
JP2023547416A (ja) 2023-11-10
US20230412231A1 (en) 2023-12-21
EP4207908A1 (en) 2023-07-05
EP4207908A4 (en) 2024-02-28
CN114390696A (zh) 2022-04-22
CN116420408A (zh) 2023-07-11

Similar Documents

Publication Publication Date Title
US12308902B2 (en) Electronic device, communication method and storage medium
US12301310B2 (en) Electronic device, communication method and storage medium
EP3768026A1 (en) Electronic device and method for wireless communication, and computer-readable storage medium
CN113382449A (zh) 用于无线通信的电子设备和方法、计算机可读存储介质
EP4207908A1 (en) Electronic device, communication method and storage medium
WO2019142512A1 (ja) 通信装置及び通信方法
US12289761B2 (en) Electronic device and method for wireless communication, and computer-readable storage medium
CN113453271A (zh) 用于无线通信的电子设备和方法、计算机可读存储介质
WO2021036875A1 (zh) 电子设备、通信方法和存储介质
US20240040556A1 (en) Electronic device and method for wireless communication, and computer-readable storage medium
WO2022083525A1 (zh) 用于无线通信的电子设备和方法、计算机可读存储介质
WO2023134528A1 (zh) 用于无线通信的电子设备和方法、计算机可读存储介质
US20240178887A1 (en) Electronic device, communication method, storage medium and computer program product
US12526810B2 (en) Electronic device, wireless communication method and computer-readable storage medium
WO2023056922A1 (zh) 电子设备、通信方法和计算机程序产品
CN116489780A (zh) 电子设备、通信方法和计算机程序产品
US20250203348A1 (en) User equipment, electronic device, wireless communication method, and storage medium
US20250350437A1 (en) Method for indicating tci states and related device

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021881957

Country of ref document: EP

Effective date: 20230331

WWE Wipo information: entry into national phase

Ref document number: 2023524832

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE

WWW Wipo information: withdrawn in national office

Ref document number: 2021881957

Country of ref document: EP