WO2019028861A1 - 波束失败事件的触发条件的配置方法、装置和通信系统 - Google Patents

波束失败事件的触发条件的配置方法、装置和通信系统 Download PDF

Info

Publication number
WO2019028861A1
WO2019028861A1 PCT/CN2017/097174 CN2017097174W WO2019028861A1 WO 2019028861 A1 WO2019028861 A1 WO 2019028861A1 CN 2017097174 W CN2017097174 W CN 2017097174W WO 2019028861 A1 WO2019028861 A1 WO 2019028861A1
Authority
WO
WIPO (PCT)
Prior art keywords
failure event
beam failure
trigger condition
user equipment
dci
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/CN2017/097174
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.)
Fujitsu Ltd
Original Assignee
Fujitsu Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Fujitsu Ltd filed Critical Fujitsu Ltd
Priority to JP2019571432A priority Critical patent/JP7099481B2/ja
Priority to PCT/CN2017/097174 priority patent/WO2019028861A1/zh
Priority to EP17920832.7A priority patent/EP3668231A4/en
Priority to CN201780091647.1A priority patent/CN110710311B/zh
Publication of WO2019028861A1 publication Critical patent/WO2019028861A1/zh
Priority to US16/729,913 priority patent/US11272487B2/en
Anticipated expiration legal-status Critical
Priority to US17/583,302 priority patent/US11606781B2/en
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/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/06964—Re-selection of one or more beams after beam failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B1/00—Details of transmission systems, not covered by a single one of groups H04B3/00 - H04B13/00; Details of transmission systems not characterised by the medium used for transmission
    • H04B1/74—Details of transmission systems, not covered by a single one of groups H04B3/00 - H04B13/00; Details of transmission systems not characterised by the medium used for transmission for increasing reliability, e.g. using redundant or spare channels or apparatus
    • 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/0617—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 for beam forming
    • 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/0621—Feedback content
    • H04B7/0626—Channel coefficients, e.g. channel state information [CSI]
    • 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/0621—Feedback content
    • H04B7/063—Parameters other than those covered in groups H04B7/0623 - H04B7/0634, e.g. channel matrix rank or transmit mode selection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/08—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the receiving station
    • H04B7/0868—Hybrid systems, i.e. switching and combining
    • H04B7/088—Hybrid systems, i.e. switching and combining using beam selection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • 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
    • 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/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/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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/542—Allocation or scheduling criteria for wireless resources based on quality criteria using measured or perceived quality
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition

Definitions

  • the present invention relates to the field of communications, and in particular, to a method, an apparatus, and a communication system for configuring a trigger condition of a beam failure event.
  • MIMO Multiple-Input Multiple-Output
  • NR new radio
  • a beam recovery mechanism when the UE detects that the control channel (eg, NR-Physical Downlink Control Channel) fails to transmit, the uplink request signal may be sent to notify the network device (for example, a base station, such as gNB) of the current link transmission. Failure, and the network device can then select a new service beam for the UE to resume transmission.
  • the control channel eg, NR-Physical Downlink Control Channel
  • the inventor has found that in order to support flexible transmission of Downlink Control Information (DCI), for example, one DCI is transmitted in one or more control resource sets, it is necessary to configure a trigger condition for reporting a beam failure event.
  • DCI Downlink Control Information
  • an embodiment of the present invention provides a configuration side of a trigger condition of a beam failure event. Law, device and communication system.
  • a method for configuring a trigger condition of a beam failure event includes:
  • the network device configures one or more control channel monitoring groups for the user equipment, so that the user equipment reports a beam failure event for the transmission failure monitoring group when detecting that the beam corresponding to the monitoring group fails to transmit;
  • Each monitoring group corresponds to one or more downlink control information (DCI).
  • DCI downlink control information
  • a method for triggering a beam failure event includes:
  • the user equipment determines, according to the configuration of the network device, whether the trigger condition of the beam failure event is met
  • the user equipment performs reporting of a beam failure event when the trigger condition of the beam failure event is met.
  • a method for configuring a trigger condition of a beam failure event includes:
  • the network device configures a trigger condition of the one or more beam failure events for the user equipment, so that the user equipment performs the reporting of the beam failure event when the trigger condition is met.
  • a device for configuring a trigger condition of a beam failure event includes:
  • a configuration unit configured to configure one or more control channel monitoring groups for the user equipment, so that the user equipment reports a beam failure event for the monitoring group of the transmission failure when detecting that the beam corresponding to the monitoring group fails to transmit;
  • Each monitoring group corresponds to one or more downlink control information (DCI).
  • DCI downlink control information
  • a triggering device for a beam failure event includes:
  • Determining a unit determining, according to a configuration of the network device, whether a trigger condition of the beam failure event is met;
  • the reporting unit performs reporting of the beam failure event when the trigger condition of the beam failure event is met.
  • a configuration apparatus for a trigger condition of a beam failure event includes:
  • a configuration unit configured to configure a trigger condition of the one or more beam failure events for the user equipment, so that the user equipment performs the reporting of the beam failure event when the trigger condition is met.
  • a network device wherein the network device comprises the apparatus of the foregoing fourth or sixth aspect.
  • a terminal device wherein the terminal device comprises the apparatus of the aforementioned fifth aspect.
  • a communication system wherein the communication system comprises the network device of the aforementioned seventh aspect and the terminal device of the foregoing eighth aspect.
  • the beneficial effects of the embodiments of the present invention are: by configuring the triggering conditions of the beam failure event in units of DCI content, the beam failure detection and reporting in more complex scenarios can be supported.
  • one DCI is transmitted in multiple control resources.
  • the scenario for example, a scene in which a control resource set transmits multiple DCIs, and the like.
  • FIG. 1 is a schematic diagram of a communication system according to an embodiment of the present invention.
  • FIG. 2 is a schematic diagram of a configuration method of a trigger condition of a beam failure event of Embodiment 1;
  • FIG. 3 is a schematic diagram of a method for configuring a trigger condition of a beam failure event of Embodiment 2;
  • 5 is a schematic diagram of mapping of multiple DCI messages in CORESET
  • FIG. 6 is a schematic diagram of a method for triggering a beam failure event of Embodiment 3;
  • FIG. 7 is a schematic diagram of a configuration apparatus of a trigger condition of a beam failure event of Embodiment 4.
  • FIG. 8 is a schematic diagram of a configuration apparatus of a trigger condition of a beam failure event of Embodiment 5;
  • FIG. 9 is a schematic diagram of a triggering device for a beam failure event of Embodiment 6;
  • Figure 10 is a schematic diagram of a network device of Embodiment 7.
  • Figure 11 is a schematic diagram of a terminal device of Embodiment 8.
  • the terms “first”, “second”, etc. are used to distinguish different elements from the title, but do not indicate the spatial arrangement or chronological order of the elements, and these elements should not be used by these terms. Limited.
  • the term “and/or” includes any and all combinations of one or more of the associated listed terms.
  • the terms “comprising,” “comprising,” “having,” or “an” are used to distinguish different elements from the title, but do not indicate the spatial arrangement or chronological order of the elements, and these elements should not be used by these terms. Limited.
  • the term “and/or” includes any and all combinations of one or more of the associated listed terms.
  • the term "communication network” or “wireless communication network” may refer to a network that conforms to any communication standard such as NR (New Radio), Long Term Evolution (LTE), enhanced. Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA, Wideband Code Division Multiple Access), High Speed Packet Access (HSPA), and the like.
  • NR New Radio
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution-A
  • LTE-Advanced LTE-Advanced
  • WCDMA Wideband Code Division Multiple Access
  • High Speed Packet Access High Speed Packet Access
  • the communication between the devices in the communication system may be performed according to any phase of the communication protocol, and may include, but is not limited to, the following communication protocols: 1G (Generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, and the future. 5G, New Radio (NR), etc., and/or other communication protocols currently known or to be developed in the future.
  • 1G Geneeration
  • 2G 2.5G, 2.75G
  • 5G New Radio
  • NR New Radio
  • the term "network device” refers to, for example, a device in a communication system that accesses a terminal device to a communication network and provides a service for the terminal device.
  • the network device may include, but is not limited to, a device: a base station (BS, a base station), an access point (AP, an Access Point), a transmission and reception point (TRP), a broadcast transmitter, and a mobility management entity (MME, Mobile). Management Entity), gateway, server, Radio Network Controller (RNC), Base Station Controller (BSC), and so on.
  • BS base station
  • AP access point
  • TRP transmission and reception point
  • MME mobility management entity
  • Management Entity gateway
  • server Radio Network Controller
  • BSC Base Station Controller
  • the base station may include, but is not limited to, a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), and a 5G base station (gNB), and the like, and may further include a Remote Radio Head (RRH). , Remote Radio Unit (RRU), relay or low power node (eg femto, pico, etc.).
  • RRH Remote Radio Head
  • RRU Remote Radio Unit
  • base station may include some or all of their functions, and each base station may provide communication coverage for a particular geographic area.
  • the term "cell” can refer to a base station and/or its coverage area, depending on the context in which the term is used.
  • the term "user equipment” (UE) or “Terminal Equipment” (TE) refers to, for example, a device that accesses a communication network through a network device and receives a network service.
  • the user equipment may be fixed or mobile, and may also be referred to as a mobile station (MS, Mobile Station), a terminal, a subscriber station (SS, Subscriber Station), an access terminal (AT, Access Terminal), a station, and the like.
  • the user equipment may include, but is not limited to, a cellular phone (Cellular Phone), a personal digital assistant (PDA, Personal Digital Assistant), a wireless modem, a wireless communication device, a handheld device, a machine type communication device, a laptop computer, Cordless phones, smart phones, smart watches, digital cameras, and more.
  • a cellular phone Cellular Phone
  • PDA Personal Digital Assistant
  • wireless modem Wireless Fidelity
  • a wireless communication device a handheld device
  • a machine type communication device a laptop computer
  • Cordless phones smart phones, smart watches, digital cameras, and more.
  • the user equipment may also be a machine or device that performs monitoring or measurement, and may include, but is not limited to, machine type communication (MTC, Machine Type). Communication) terminal, vehicle communication terminal, device to device (D2D, Device to Device) terminal, machine to machine (M2M, Machine to Machine) terminal, and the like.
  • MTC machine type communication
  • Communication vehicle communication terminal
  • D2D Device to Device
  • M2M Machine to Machine
  • FIG. 1 is a schematic diagram of a communication system according to an embodiment of the present invention, schematically illustrating a case where a user equipment and a network device are taken as an example.
  • the communication system 100 may include a network device 101 and a terminal device 102 (for simplicity)
  • Figure 1 shows only one terminal device as an example).
  • an existing service or a service that can be implemented in the future can be performed between the network device 101 and the terminal device 102.
  • these services include, but are not limited to, enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and high reliability low latency communication (URLLC, Ultra-Reliable and Low- Latency Communication), and more.
  • eMBB enhanced mobile broadband
  • mMTC massive machine type communication
  • URLLC Ultra-Reliable and Low- Latency Communication
  • CSI-RS channel state information-reference signal
  • the NR-PDCCH beam failure means that the RSRP XOR of the CSI-RS with the same beam as the NR-PDCCH is below a certain threshold.
  • one or more CSI-RS resource configurations can be configured for the UE for measurement of [RSRP XOR SINR].
  • the UE may assume that the CSI-RS is a non-zero transmit power CSI-RS.
  • Parameters configured for each CSI-RS resource through high layer signaling include: resource configuration, period, antenna port, transmission power, pseudo random sequence generator parameters, Quasi-Co-Location (QCL) parameters, and the like.
  • the large-scale attribute of a channel transmitting a symbol on one antenna port can be inferred from a channel transmitting a symbol on another antenna port, the two antenna ports are referred to as quasi co-location.
  • the large scale attributes herein include one or more of delay spread, Doppler spread, Doppler shift, average gain, and average delay.
  • large-scale attributes may also include spatial channel characteristics, ie, beam-related information.
  • the configuration of the current standard for the NR-PDCCH control resource set is: the high-level parameter provides the starting position of the Orthogonal Frequency Division Multiplexing (OFDM) symbol [pdcch_StartSymbol]; The number of consecutive OFDM symbols provided by the parameter [pdcch_NumSymbol]; the set of resource blocks provided by the higher layer parameters [pdcch_RBSet]; the control channel element (CCE) provided by the higher layer parameters to the resource element group (Resource Element) Group, REG) mapping [pdcch_mapping]; the size of the REG bundle in the case where the CCE to REG adopts the interleaving mapping provided by the upper layer parameter [REG_bundle]; the QCL[QCL-ConfigId] of the antenna port provided by the upper layer parameter.
  • OFDM Orthogonal Frequency Division Multiplexing
  • the configuration of the CORESET will include the ID (ID) of the QCL of the antenna port, ie QCL-ConfigId, which is directly derived from the QCL parameter in the CSI-RS configuration.
  • ID the ID of the QCL of the antenna port
  • QCL-ConfigId the QCL parameter in the CSI-RS configuration
  • CORESET corresponds to one QCL configuration, that is, corresponding to one or a group of beams and beam pairs;
  • Each search space in the CORESET can correspond to a QCL configuration, that is, corresponding to one or a group of beams and beam pairs;
  • Each PDCCH candidate in the CORESET may correspond to one QCL configuration, that is, corresponding to one or a group of beams and beam pairs;
  • Each PDCCH candidate set in the CORESET may correspond to one QCL configuration, that is, corresponding to one or a group of beams and beam pairs;
  • Each REG bundle in CORESET can correspond to a QCL configuration, that is, corresponding to one or a group of beams and beam pairs.
  • the trigger condition of the beam failure event needs to be configured.
  • This embodiment provides a method for configuring a trigger condition of a beam failure event, and the method is applied to a network device of a communication system, such as a gNB defined by the NR standard.
  • 2 is a schematic diagram of the method, as shown in FIG. 2, the method includes:
  • Step 201 The network device configures one or more control channel monitoring groups for the user equipment, so that the user equipment reports a beam failure event for the monitoring group of the transmission failure when detecting that the beam corresponding to the monitoring group fails to transmit.
  • control channel is, for example, an NR-PDCCH defined by the NR standard
  • the network device configures a control channel monitoring group for the user equipment, so that the user equipment performs beam failure reporting in the range of the monitoring group.
  • each monitoring group corresponds to one or more DCIs, and each DCI uses one or more beams.
  • the user equipment detects that the beam corresponding to a certain monitoring group fails to transmit, it reports to the monitoring group.
  • a beam failure event such as sending a beam failure recovery request to a network device, for the network device to redistribute the beam for it.
  • one DCI refers to one downlink control information in the transmission, for example, it may correspond to a DCI format. From the perspective of physical transmission resources, a DCI can also be a PDCCH candidate or a candidate set.
  • each monitoring group includes an identifier of all quasi co-locations corresponding to one or more DCIs, that is, a QCL-ConfigId in the foregoing CORESET configuration.
  • the beam failure event for the monitoring group is reported when the user equipment detects that the beam used by the DCI corresponding to the ID of all the QCLs included in a certain monitoring group fails to be transmitted.
  • the same monitoring group includes IDs of all QCLs corresponding to a plurality of DCIs
  • the plurality of DCIs use the same beam. That is, the present embodiment is applicable to the case where the quasi-co-location identifiers of multiple DCIs corresponding to the same monitoring group are the same, that is, the case where multiple DCIs corresponding to the same monitoring group use the same beam.
  • each monitoring group includes an identifier of a physical resource corresponding to the DCI, such as an identifier of the control resource set, an identifier of the search space, and/or an identifier of the control channel candidate set.
  • the indication granularity of the QCL of the antenna port in the CORESET is a PDCCH candidate set.
  • the identifier of the physical resource may include the identifiers and corresponding identifiers of all the control resource sets in which the DCI is located. The identifier of the PDCCH candidate set.
  • the beam failure event for the monitoring group is reported.
  • the network device In addition to the configuration of the CORESET, the network device additionally configures, for the user equipment, a control channel monitoring group for triggering the user equipment to perform beam failure event reporting, and the user equipment detects the beam corresponding to the monitoring group. If the transmission fails, the beam failure event is reported, and the detection and reporting of the beam failure in a scenario where one DCI is transmitted in multiple CORESETs or in a CORESET transmission of multiple DCIs is solved, and the detection accuracy is higher. It does not consume too much resources.
  • This embodiment provides a method for configuring a trigger condition of a beam failure event, and the method is also applied to a network device of a communication system, such as a gNB defined by the NR standard.
  • 3 is a schematic diagram of the method, as shown in FIG. 3, the method includes:
  • Step 301 The network device configures a trigger condition of the one or more beam failure events for the user equipment, so that the user equipment performs the reporting of the beam failure event when the trigger condition is met.
  • the network device is configured to configure a control channel monitoring group for the user equipment in the first embodiment.
  • the network device directly configures a trigger condition of the beam failure event for the user equipment, and the user equipment only needs to detect whether the user equipment meets the requirements. The trigger condition, if satisfied, reports the beam failure event.
  • the trigger condition may be any one or more of the following:
  • the trigger condition is configured in units of control resource sets, and all the beams used by all DCIs included in a certain control resource set or all control resource sets or some control resource sets are transmitted. When it fails, the corresponding beam failure event is reported.
  • the control resource set in the trigger condition may also be a physical resource such as a search space, a control channel candidate set, or the like.
  • the network device In addition to the configuration of the CORESET, the network device additionally configures, for the user equipment, a trigger condition for triggering the user equipment to report the beam failure event, and performs the beam when the user equipment detects that the trigger condition is met.
  • the reporting of the failure event thereby providing another solution for triggering the beam failure event reporting for a scenario in which one DCI transmits multiple CORESETs or one multiple CORESET transmits multiple DCIs.
  • Figure 4 shows the mapping of a single DCI message, as shown in Figure 4, in this example, there is only one DCI message, namely DCI 1, the DCI 1 can be transmitted in a CORESET, as shown in Figure 4 (a) As shown, it can also be transmitted in multiple CORESETs, as shown in (b) and (c) of FIG. 4, and the DCI 1 can use one beam, as shown in FIG. 4(b), and can also be used.
  • the beams are shown in (a) and (c) of Figure 4.
  • (a) and (c) in Fig. 4 show the case where two beams are used for each DCI, but the present embodiment is not limited thereto, and the number of beams used for each DCI can also be specified according to standards.
  • Figure 5 shows the mapping of multiple DCI messages, as shown in Figure 5, in this example, there are two DCIs.
  • Messages namely DCI 1 and DCI 2, where DCI 1 can be transmitted in one CORESET, as shown in (a), (b), (d) and (e) of Figure 5, and within multiple CORESETs.
  • the transmission is as shown in (c), (f) and (g) of FIG.
  • DCI 2 can be transmitted in a CORESET, as shown in (a), (b), (c), (d) and (e) of Figure 5, and can also be transmitted in multiple CORESETs. 5 (f) and (g) are shown.
  • each CORESET can transmit a DCI, as shown in (a), (b) and (c) of Figure 5, and can also transmit multiple DCIs, as shown in Figure 5 (d) of CORESET 3, (e) CORESET 3, (f) CORESET 2 and CORESET 3, and (g) CORESET 3.
  • the DCI 1 and the DCI 2 can use one beam, as shown in (a) of FIG. 5, DCI 1 of (c) of FIG. 5, and (d) of FIG. 5, and multiple beams can also be used, as shown in FIG. 5.
  • FIG. 5 show the case where two beams are used for each DCI.
  • this embodiment is not limited thereto, and the number of beams used by each DCI may also be specified according to standards.
  • Embodiment 1 or Embodiment 2 can be used regardless of the mapping manner of DCI in FIG. 4 or the mapping manner of DCI in FIG. 5 or other DCI mapping manners according to the mapping manner of DCI in FIG. 4 and FIG. 5.
  • the configuration of the trigger condition for the beam failure event can be used regardless of the mapping manner of DCI in FIG. 4 or the mapping manner of DCI in FIG. 5 or other DCI mapping manners according to the mapping manner of DCI in FIG. 4 and FIG. 5.
  • the control channel monitoring group is configured for the user equipment by using the method of Embodiment 1, where each monitoring group includes an ID of a QCL corresponding to one or more DCIs or a physical resource identifier corresponding to one DCI, whereby the user equipment can know each monitoring group.
  • the corresponding beam when it is detected that all the beams corresponding to a certain monitoring group fail to transmit, report the beam failure event for the monitoring group.
  • the triggering condition of the beam failure event is configured for the user equipment by using the method of Embodiment 2, where the trigger condition includes a CORESET reported by the beam failure event, whereby the user equipment can detect the beam used by all DCIs included in the CORESET.
  • the report of the beam failure event is performed when all transmissions fail.
  • the configuration method of Embodiment 2 and the configuration method of Embodiment 1 can be used in combination, as long as the configurations of the two are not conflicted.
  • the present embodiment provides a method for triggering a beam failure event, which is applied to a terminal device of a communication system, such as a UE defined by the NR standard, which is a UE-side processing corresponding to the method of Embodiment 1 or Embodiment 2.
  • a terminal device of a communication system such as a UE defined by the NR standard, which is a UE-side processing corresponding to the method of Embodiment 1 or Embodiment 2.
  • Figure 6 is a schematic representation of the method Figure, as shown in Figure 6, the method includes:
  • Step 601 The user equipment determines, according to the configuration of the network device, whether a trigger condition of the beam failure event is met.
  • Step 602 Perform a report of the beam failure event when the trigger condition of the beam failure event is met.
  • the configuration of the network device is: one or more control channel monitoring groups, each monitoring group corresponding to one or more DCIs, and the user equipment fails to detect that the beam corresponding to the monitoring group fails to be transmitted. At the time, the beam failure event for the monitoring group that failed the transmission is reported.
  • the related content of the control channel monitoring group has been described in Embodiment 1, and the content thereof is incorporated herein, and details are not described herein again.
  • the configuration of the network device is: a trigger condition of one or more beam failure events, and the user equipment performs reporting of the beam failure event when detecting that the trigger condition is met.
  • the related content of the trigger condition has been described in Embodiment 2, and the content thereof is incorporated herein, and details are not described herein again.
  • the network device additionally configures, for the user equipment, a control channel monitoring group for triggering the user equipment to perform beam failure event reporting, or configured for the user equipment to trigger the user equipment.
  • the triggering condition of the beam failure event is reported, and the user equipment fails to report the beam failure event in the case that the beam corresponding to the monitoring group fails to be transmitted or the detection of the trigger condition is met, and the solution is solved regardless of a DCI.
  • Multiple CORESET transmissions, or a CORESET transmission of multiple DCIs in the scenario of beam failure detection and reporting the detection accuracy is higher, and does not consume too much resources.
  • the embodiment provides a configuration device for triggering a beam failure event, and the device is configured in a network device.
  • the principle of the device is similar to the method of the first embodiment, and the specific implementation may refer to the method of the first embodiment. The implementation of the same content will not be repeated.
  • FIG. 7 is a schematic diagram of a configuration apparatus for triggering a beam failure event according to the embodiment.
  • the apparatus 700 includes: a configuration unit 701 configured to configure one or more control channel monitoring groups for the user equipment. When detecting that the beam corresponding to the monitoring group fails to transmit, the user equipment reports a beam failure event for the monitoring group that fails to transmit; wherein each monitoring group corresponds to one or more DCIs.
  • one DCI corresponds to one DCI format, or one DCI corresponds to one control channel candidate, or one DCI corresponds to one control channel candidate set.
  • each monitoring group includes: an identifier of all quasi co-locations corresponding to one or more DCIs, and the quasi co-location IDs of the plurality of DCIs are configured the same.
  • each monitoring group includes: an identifier of a physical resource corresponding to a DCI.
  • the identifier of the physical resource herein may include, for example, an identifier of the control resource set, an identifier of the search space, and/or an identifier of the control channel candidate set, and the like.
  • the network device in addition to the configuration of the CORESET, the network device additionally configures, for the user equipment, a control channel monitoring group for triggering the user equipment to report the beam failure event, and the user equipment detects the beam corresponding to the monitoring group. If the transmission fails, the beam failure event is reported, and the detection and reporting of the beam failure in a scenario where one DCI is transmitted in multiple CORESETs or in a CORESET transmission of multiple DCIs is solved, and the detection accuracy is higher. It does not consume too much resources.
  • the embodiment provides a configuration device for triggering a beam failure event, and the device is configured on a network device.
  • the principle of the device is similar to the method of the second embodiment, and the specific implementation may refer to the method of the second embodiment. The implementation of the same content will not be repeated.
  • FIG. 8 is a schematic diagram of a configuration apparatus for triggering a beam failure event according to the embodiment.
  • the apparatus 800 includes: a configuration unit 801 configured to configure a trigger condition of one or more beam failure events for a user equipment, The user equipment performs the reporting of the beam failure event when the trigger condition is met.
  • the trigger condition is any one or more of the following:
  • the network device In addition to the configuration of the CORESET, the network device additionally configures, for the user equipment, a trigger condition for triggering the user equipment to report the beam failure event, and performs the beam if the user equipment detects that the trigger condition is met.
  • the reporting of the failure event thereby providing another solution for triggering the beam failure event reporting for a scenario in which one DCI transmits multiple CORESETs or one multiple CORESET transmits multiple DCIs.
  • the present embodiment provides a triggering device for a beam failure event.
  • the principle of the device is similar to that of the third embodiment.
  • the specific implementation may refer to the implementation of the method in Embodiment 3. Description.
  • FIG. 9 is a schematic diagram of a triggering device for a beam failure event according to the embodiment.
  • the device 900 includes: a determining unit 901 and a reporting unit 902, where the determining unit 901 determines whether a beam failure event is satisfied according to a configuration of the network device.
  • the triggering condition is that the reporting unit 902 performs the reporting of the beam failure event if the trigger condition of the beam failure event is met.
  • the configuration of the network device is: one or more control channel monitoring groups, each monitoring group corresponding to one or more DCIs, and the user equipment fails to detect that the beam corresponding to the monitoring group fails to be transmitted. At the time, the beam failure event for the monitoring group that failed the transmission is reported.
  • the configuration of the network device is: a trigger condition of one or more beam failure events, and the user equipment performs reporting of the beam failure event when detecting that the trigger condition is met.
  • the network device additionally configures, for the user equipment, a control channel monitoring group for triggering the user equipment to perform beam failure event reporting, or configured for the user equipment to trigger the user equipment.
  • the triggering condition of the beam failure event is reported, and the user equipment fails to report the beam failure event in the case that the beam corresponding to the monitoring group fails to be transmitted or the detection of the trigger condition is met, and the solution is solved regardless of a DCI.
  • Multiple CORESET transmissions, or a CORESET transmission of multiple DCIs in the scenario of beam failure detection and reporting the detection accuracy is higher, and does not consume too much resources.
  • the embodiment provides a network device, where the network device includes a configuration device for triggering a beam failure event according to Embodiment 4 or Embodiment 5.
  • FIG. 10 is a schematic diagram of a network device according to an embodiment of the present invention.
  • network device 1000 can include a processor 1010 and a memory 1020; memory 1020 is coupled to processor 1010.
  • the memory 1020 can store various data; in addition, a program 1030 for information processing is stored, and the program 1030 is executed under the control of the processor 1010 to receive various information transmitted by the terminal device and transmit various information to the terminal device. .
  • the functionality of the configuration device of the triggering condition of the beam failure event can be integrated into In the central processor 1010.
  • the processor 1010 may be configured to: configure one or more control channel monitoring groups for the user equipment, so that the user equipment reports the monitoring for the transmission failure when detecting that the beam corresponding to the monitoring group fails to transmit.
  • the processor 1010 may be configured to: configure a trigger condition of the one or more beam failure events for the user equipment, so that the user equipment performs the reporting of the beam failure event when the trigger condition is met.
  • the configuration device of the trigger condition of the beam failure event may be configured separately from the processor 1010 , for example, the configuration device that can trigger the trigger condition of the beam failure event is configured as a chip connected to the processor 1010 , and the processor 1010 is configured by the processor 1010 .
  • the function of the configuration device that controls the triggering condition of the beam failure event is configured separately from the processor 1010 , for example, the configuration device that can trigger the trigger condition of the beam failure event is configured as a chip connected to the processor 1010 , and the processor 1010 is configured by the processor 1010 .
  • the function of the configuration device that controls the triggering condition of the beam failure event is configured separately from the processor 1010 , for example, the configuration device that can trigger the trigger condition of the beam failure event is configured as a chip connected to the processor 1010 , and the processor 1010 is configured by the processor 1010 .
  • the network device 1000 may further include: a transceiver 1040, an antenna 1050, and the like; wherein the functions of the foregoing components are similar to the prior art, and details are not described herein again. It should be noted that the network device 1000 does not necessarily have to include all the components shown in FIG. 10; in addition, the network device 1000 may further include components not shown in FIG. 10, and reference may be made to the prior art.
  • the user equipment in addition to the configuration of the CORESET, is additionally configured with a control channel monitoring group for triggering the user equipment to perform the beam failure event reporting, or configured for the user equipment to trigger the user equipment to perform the beam.
  • the triggering condition of the failure event is reported, and the user equipment fails to report the beam failure event in the case that the beam corresponding to the monitoring group fails to be transmitted or the detection of the trigger condition is met, thereby solving the problem that no more than one DCI is present.
  • the transmission within the CORESET is also the detection and reporting of the beam failure in the scenario where the CORESET transmits multiple DCIs. The detection accuracy is higher and does not consume too much resources.
  • the embodiment provides a terminal device, which includes the data transmission device as described in Embodiment 6.
  • FIG. 11 is a schematic diagram showing the system configuration of the terminal device 1100 according to the embodiment of the present invention.
  • the terminal device 1100 can include a processor 1110 and a memory 1120; the memory 1120 is coupled to the processor 1110.
  • the figure is exemplary; other types of structures may be used in addition to or in place of the structure to implement telecommunications functions or other functions.
  • the functionality of the triggering device of the beam failure event may be integrated into the processor 1110 in.
  • the processor 1110 may be configured to: determine whether the trigger condition of the beam failure event is met according to the configuration of the network device; and perform the reporting of the beam failure event if the trigger condition of the beam failure event is met.
  • the triggering device of the beam failure event may be configured separately from the processor 1110.
  • the trigger device of the beam failure event may be configured as a chip connected to the processor 1110, and the beam failure is implemented by the control of the processor 1110. The function of the trigger device of the event.
  • the terminal device 1100 may further include: a communication module 1130, an input unit 1140, a display 1150, and a power supply 1160. It should be noted that the terminal device 1100 does not necessarily have to include all the components shown in FIG. 11; in addition, the terminal device 1100 may further include components not shown in FIG. 11, and reference may be made to the related art.
  • processor 1110 also sometimes referred to as a controller or operational control, may include a microprocessor or other processor device and/or logic device that receives input and controls various components of terminal device 1100. operating.
  • the memory 1120 can be, for example, one or more of a buffer, a flash memory, a hard drive, a removable medium, a volatile memory, a non-volatile memory, or other suitable device.
  • Various data can be stored, and programs for executing related information can be stored.
  • the processor 1110 can execute the program stored by the memory 1120 to implement information storage or processing and the like.
  • the functions of other components are similar to those of the existing ones and will not be described here.
  • the various components of terminal device 1100 may be implemented by special purpose hardware, firmware, software or a combination thereof without departing from the scope of the invention.
  • the terminal device of the present embodiment detects that the beam corresponding to the control channel monitoring group configured by the network device fails to transmit, or detects that the trigger condition of the beam failure event is met, the beam failure event is reported.
  • the detection and reporting of beam failure in a scenario in which a DCI is transmitted in multiple CORESETs or in a CORESET transmission of multiple DCIs is solved, and the detection accuracy is higher and does not consume too much resources.
  • the embodiment provides a communication system, including the network device as described in Embodiment 7, and the terminal device as described in Embodiment 8.
  • the above apparatus and method of the present invention may be implemented by hardware or by hardware in combination with software.
  • the present invention relates to a computer readable program that, when executed by a logic component, enables the logic component to implement the apparatus or components described above, or to cause the logic component to implement the various methods described above Or steps.
  • the present invention also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, or the like.
  • the method/apparatus described in connection with the embodiments of the invention may be embodied directly in hardware, a software module executed by a processor, or a combination of both.
  • one or more of the functional block diagrams shown in FIG. 7 and/or one or more combinations of functional block diagrams may correspond to individual software modules of a computer program flow, or to individual hardware modules.
  • These software modules may correspond to the respective steps shown in FIG. 2, respectively.
  • These hardware modules can be implemented, for example, by curing these software modules using a Field Programmable Gate Array (FPGA).
  • FPGA Field Programmable Gate Array
  • the software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.
  • a storage medium can be coupled to the processor to enable the processor to read information from, and write information to, the storage medium; or the storage medium can be an integral part of the processor.
  • the processor and the storage medium can be located in an ASIC.
  • the software module can be stored in the memory of the mobile terminal or in a memory card that can be inserted into the mobile terminal.
  • the software module can be stored in the MEGA-SIM card or a large-capacity flash memory device.
  • One or more of the functional blocks described in the figures and/or one or more combinations of functional blocks may be implemented as a general purpose processor, digital signal processor (DSP) for performing the functions described herein.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • One or more of the functional blocks described with respect to the figures and/or one or more combinations of functional blocks may also be implemented as a combination of computing devices, eg, a combination of a DSP and a microprocessor, multiple microprocessors One or more microprocessors in conjunction with DSP communication or any other such configuration.

Landscapes

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

Abstract

一种波束失败事件的触发条件的配置方法、装置和通信系统，该方法包括：网络设备为用户设备配置一个或多个控制信道监测组，以便所述用户设备在检测到所述监测组所对应的波束均传输失败时，上报针对传输失败的监测组的波束失败事件；其中，每个监测组对应一个或多个下行控制信息(DCI)。通过针对DCI对波束失败事件的触发条件进行配置，可以支持更多复杂场景下的波束失败检测和上报，例如，一个DCI在多个控制资源集中传输的场景，再例如，一个控制资源集传输多个DCI的场景，等。

Description

波束失败事件的触发条件的配置方法、装置和通信系统 技术领域
本发明涉及通信领域，特别涉及一种波束失败事件的触发条件的配置方法、装置和通信系统。
背景技术
大规模多输入多输出(Multiple-Input Multiple-Output，MIMO)技术是新无线(New radio，NR)系统的关键技术，包括6GHz以下及6GHz以上频段的研究。随着频段的增加，传输中产生的衰落和损耗也会相应增大，波束成型技术由于可以有效补偿衰落而成为大规模MIMO技术中的关键技术。
在大规模MIMO技术的研究中，为提高传输的可靠性，允许使用同时为物理信道(广播信道，数据信道，控制信道等)发送多个波束的波束成型技术。然而，在多波束的波束成型技术下，由于高频段的传输特性、移动台(User Equipment，UE)的旋转以及障碍物的遮挡等，仍然存在传输失败的情况。在这种情况下，通过调整服务波束，有可能可以在物理层(层1)和介质访问控制(Media Access Control，MAC)层(层2)解决传输失败的问题，因而，NR系统中引入了波束恢复机制：即当UE检测到控制信道(例如NR-PDCCH，NR-Physical Downlink Control Channel)传输失败的情况下，可以通过发送上行请求信号通知网络设备(例如基站，如gNB)当前链路传输失败，进而网络设备就可以相应地为UE选择新的服务波束以恢复传输。
应该注意，上面对技术背景的介绍只是为了方便对本发明的技术方案进行清楚、完整的说明，并方便本领域技术人员的理解而阐述的。不能仅仅因为这些方案在本发明的背景技术部分进行了阐述而认为上述技术方案为本领域技术人员所公知。
发明内容
发明人发现，为了支持下行控制信息(Downlink Control Information，DCI)的灵活传输，例如，一个DCI在一个或多个控制资源集里传输，需要为波束失败事件上报的触发条件进行配置。
为了解决上述问题，本发明实施例提供一种波束失败事件的触发条件的配置方 法、装置和通信系统。
根据本发明实施例的第一方面，提供了一种波束失败事件的触发条件的配置方法，其中，所述方法包括：
网络设备为用户设备配置一个或多个控制信道监测组，以便所述用户设备在检测到所述监测组所对应的波束均传输失败时，上报针对传输失败的监测组的波束失败事件；其中，每个监测组对应一个或多个下行控制信息(DCI)。
根据本发明实施例的第二方面，提供了一种波束失败事件的触发方法，其中，所述方法包括：
用户设备根据网络设备的配置确定是否满足波束失败事件的触发条件；
所述用户设备在满足波束失败事件的触发条件的情况下，进行波束失败事件的上报。
根据本发明实施例的第三方面，提供了一种波束失败事件的触发条件的配置方法，其中，所述方法包括：
网络设备为用户设备配置一个或多个波束失败事件的触发条件，以便所述用户设备在满足所述触发条件时，进行波束失败事件的上报。
根据本发明实施例的第四方面，提供了一种波束失败事件的触发条件的配置装置，其中，所述装置包括：
配置单元，其为用户设备配置一个或多个控制信道监测组，以便所述用户设备在检测到所述监测组所对应的波束均传输失败时，上报针对传输失败的监测组的波束失败事件；其中，每个监测组对应一个或多个下行控制信息(DCI)。
根据本发明实施例的第五方面，提供了一种波束失败事件的触发装置，其中，所述装置包括：
确定单元，其根据网络设备的配置确定是否满足波束失败事件的触发条件；
上报单元，其在满足波束失败事件的触发条件的情况下，进行波束失败事件的上报。
根据本发明实施例的第六方面，提供了波束失败事件的触发条件的配置装置，其中，所述装置包括：
配置单元，其为用户设备配置一个或多个波束失败事件的触发条件，以便所述用户设备在满足所述触发条件时，进行波束失败事件的上报。
根据本发明实施例的第七方面，提供了一种网络设备，其中，所述网络设备包括前述第四方面或第六方面所述的装置。
根据本发明实施例的第八方面，提供了一种终端设备，其中，所述终端设备包括前述第五方面所述的装置。
根据本发明实施例的第九方面，提供了一种通信系统，其中，所述通信系统包括前述第七方面所述的网络设备和前述第八方面所述的终端设备。
本发明实施例的有益效果在于：通过以DCI内容为单位对波束失败事件的触发条件进行配置，可以支持更多复杂场景下的波束失败检测和上报，例如，一个DCI在多个控制资源集中传输的场景，再例如，一个控制资源集传输多个DCI的场景，等。
参照后文的说明和附图，详细公开了本发明的特定实施方式，指明了本发明的原理可以被采用的方式。应该理解，本发明的实施方式在范围上并不因而受到限制。在所附权利要求的条款的范围内，本发明的实施方式包括许多改变、修改和等同。
针对一种实施方式描述和/或示出的特征可以以相同或类似的方式在一个或更多个其它实施方式中使用，与其它实施方式中的特征相组合，或替代其它实施方式中的特征。
应该强调，术语“包括/包含”在本文使用时指特征、整件、步骤或组件的存在，但并不排除一个或更多个其它特征、整件、步骤或组件的存在或附加。
附图说明
在本发明实施例的一个附图或一种实施方式中描述的元素和特征可以与一个或更多个其它附图或实施方式中示出的元素和特征相结合。此外，在附图中，类似的标号表示几个附图中对应的部件，并可用于指示多于一种实施方式中使用的对应部件。
所包括的附图用来提供对本发明实施例的进一步的理解，其构成了说明书的一部分，用于例示本发明的实施方式，并与文字描述一起来阐释本发明的原理。显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。在附图中：
图1是本发明实施例的通信系统的示意图；
图2是实施例1的波束失败事件的触发条件的配置方法的示意图；
图3是实施例2的波束失败事件的触发条件的配置方法的示意图；
图4是单DCI消息在CORESET中的映射示意图；
图5是多DCI消息在CORESET中的映射示意图；
图6是实施例3的波束失败事件的触发方法的示意图；
图7是实施例4的波束失败事件的触发条件的配置装置的示意图；
图8是实施例5的波束失败事件的触发条件的配置装置的示意图；
图9是实施例6的波束失败事件的触发装置的示意图；
图10是实施例7的网络设备的示意图；
图11是实施例8的终端设备的示意图。
具体实施方式
参照附图，通过下面的说明书，本发明的前述以及其它特征将变得明显。在说明书和附图中，具体公开了本发明的特定实施方式，其表明了其中可以采用本发明的原则的部分实施方式，应了解的是，本发明不限于所描述的实施方式，相反，本发明包括落入所附权利要求的范围内的全部修改、变型以及等同物。下面结合附图对本发明的各种实施方式进行说明。这些实施方式只是示例性的，不是对本发明的限制。
在本发明实施例中，术语“第一”、“第二”等用于对不同元素从称谓上进行区分，但并不表示这些元素的空间排列或时间顺序等，这些元素不应被这些术语所限制。术语“和/或”包括相关联列出的术语的一种或多个中的任何一个和所有组合。术语“包含”、“包括”、“具有”等是指所陈述的特征、元素、元件或组件的存在，但并不排除存在或添加一个或多个其他特征、元素、元件或组件。
在本发明实施例中，单数形式“一”、“该”等包括复数形式，应广义地理解为“一种”或“一类”而并不是限定为“一个”的含义；此外术语“所述”应理解为既包括单数形式也包括复数形式，除非上下文另外明确指出。此外术语“根据”应理解为“至少部分根据……”，术语“基于”应理解为“至少部分基于……”，除非上下文另外明确指出。
在本发明实施例中，术语“通信网络”或“无线通信网络”可以指符合如下任意通信标准的网络，例如新无线(NR，New Radio)、长期演进(LTE，Long Term Evolution)、增强的长期演进(LTE-A，LTE-Advanced)、宽带码分多址接入(WCDMA， Wideband Code Division Multiple Access)、高速报文接入(HSPA，High-Speed Packet Access)等等。
并且，通信系统中设备之间的通信可以根据任意阶段的通信协议进行，例如可以包括但不限于如下通信协议：1G(Generation)、2G、2.5G、2.75G、3G、4G、4.5G以及未来的5G、新无线(NR，New Radio)等等，和/或其他目前已知或未来将被开发的通信协议。
在本发明实施例中，术语“网络设备”例如是指通信系统中将终端设备接入通信网络并为该终端设备提供服务的设备。网络设备可以包括但不限于如下设备：基站(BS，Base Station)、接入点(AP、Access Point)、发送接收点(TRP，Transmission Reception Point)、广播发射机、移动管理实体(MME、Mobile Management Entity)、网关、服务器、无线网络控制器(RNC，Radio Network Controller)、基站控制器(BSC，Base Station Controller)等等。
其中，基站可以包括但不限于：节点B(NodeB或NB)、演进节点B(eNodeB或eNB)以及5G基站(gNB)，等等，此外还可包括远端无线头(RRH，Remote Radio Head)、远端无线单元(RRU，Remote Radio Unit)、中继(relay)或者低功率节点(例如femto、pico等等)。并且术语“基站”可以包括它们的一些或所有功能，每个基站可以对特定的地理区域提供通信覆盖。术语“小区”可以指的是基站和/或其覆盖区域，这取决于使用该术语的上下文。
在本发明实施例中，术语“用户设备”(UE，User Equipment)或者“终端设备”(TE，Terminal Equipment)例如是指通过网络设备接入通信网络并接收网络服务的设备。用户设备可以是固定的或移动的，并且也可以称为移动台(MS，Mobile Station)、终端、用户台(SS，Subscriber Station)、接入终端(AT，Access Terminal)、站，等等。
其中，用户设备可以包括但不限于如下设备：蜂窝电话(Cellular Phone)、个人数字助理(PDA，Personal Digital Assistant)、无线调制解调器、无线通信设备、手持设备、机器型通信设备、膝上型计算机、无绳电话、智能手机、智能手表、数字相机，等等。
再例如，在物联网(IoT，Internet of Things)等场景下，用户设备还可以是进行监控或测量的机器或装置，例如可以包括但不限于：机器类通信(MTC，Machine Type  Communication)终端、车载通信终端、设备到设备(D2D，Device to Device)终端、机器到机器(M2M，Machine to Machine)终端，等等。
以下通过示例对本发明实施例的场景进行说明，但本发明不限于此。
图1是本发明实施例的通信系统的示意图，示意性说明了以用户设备和网络设备为例的情况，如图1所示，通信系统100可以包括网络设备101和终端设备102(为简单起见，图1仅以一个终端设备为例进行说明)。
在本发明实施例中，网络设备101和终端设备102之间可以进行现有的业务或者未来可实施的业务。例如，这些业务包括但不限于：增强的移动宽带(eMBB，enhanced Mobile Broadband)、大规模机器类型通信(mMTC，massive Machine Type Communication)和高可靠低时延通信(URLLC，Ultra-Reliable and Low-Latency Communication)，等等。
在当前第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)的讨论中，已经明确使用信道状态信息参考信号(channel state information-reference signal，CSI-RS)来检测NR-PDCCH的波束失败事件以及识别新的候选波束和/或收发波束对，NR-PDCCH的波束失败也就意味着与该NR-PDCCH采用相同波束的CSI-RS的RSRP异或SINR低于某个门限值。在当前标准中定义为：可以为UE配置一个或多个CSI-RS资源配置用于[RSRP异或SINR]的测量。UE可以假设该CSI-RS是非零发送功率的CSI-RS。通过高层信令为每个CSI-RS资源配置的参数包括：资源配置、周期、天线端口、传输功率、伪随机序列发生器参数、准共址(Quasi-Co-Location，QCL)参数等。
这里，如果传送一个天线端口上的符号的信道的大尺度属性可以从传送另一个天线端口上的符号的信道推断出来，则这两个天线端口被称为准共址。这里的大尺度属性包括延迟扩展、多普勒扩展、多普勒频移、平均增益以及平均延迟中的一个或多个。此外，在某些场景下，大尺度属性还可以包括空间信道特性，即波束相关信息。
此外，当前标准对NR-PDCCH的控制资源集(COntrol REsource SET，CORESET)的配置为：高层参数提供正交频分复用(Orthogonal Frequency Division Multiplexing，OFDM)符号的起始位置[pdcch_StartSymbol]；高层参数提供的连续OFDM符号数[pdcch_NumSymbol]；高层参数提供的资源块的集合[pdcch_RBSet]；高层参数提供的控制信道单元(Control Channel Element，CCE)到资源粒子组(Resource Element  Group，REG)的映射[pdcch_mapping]；高层参数提供的在CCE到REG采用交织映射的情况下REG束的大小[REG_bundle]；高层参数提供的天线端口的QCL[QCL-ConfigId]等。
此处，CORESET的配置会包含天线端口的QCL的标识(ID)，即QCL-ConfigId，该参数直接来源于CSI-RS配置中的QCL参数。目前，关于CORESET中的天线端口的QCL的指示粒度有多种提议，包括：
CORESET整个对应一个QCL配置，即对应一个或一组波束、波束对；
CORESET中的每个搜索空间(search space)都可以分别对应一个QCL配置，即对应一个或一组波束、波束对；
CORESET中的每个PDCCH候选(candidate)都可以分别对应一个QCL配置，即对应一个或一组波束、波束对；
CORESET中的每个PDCCH候选(candidate)集合都可以分别对应一个QCL配置，即对应一个或一组波束、波束对；
CORESET中的每个REG束(bundle)都可以分别对应一个QCL配置，即对应一个或一组波束、波束对。
然而，不管采用哪种指示粒度，为了支持控制信息(DCI)的灵活传输，如一个DCI在一个或多个CORSET里传输，都需要为波束失败事件的触发条件进行配置。
下面结合附图和具体实施方式对本发明实施例的波束失败事件的触发条件的配置方法、装置和系统进行说明。
实施例1
本实施例提供了一种波束失败事件的触发条件的配置方法，该方法应用于通信系统的网络设备，例如NR标准定义的gNB等。图2是该方法的示意图，如图2所示，该方法包括：
步骤201：网络设备为用户设备配置一个或多个控制信道监测组，以便所述用户设备在检测到所述监测组所对应的波束均传输失败时，上报针对传输失败的监测组的波束失败事件。
在本实施例中，控制信道例如为NR标准定义的NR-PDCCH，网络设备通过为用户设备配置控制信道监测组，以便用户设备在该监测组的范围内进行波束失败的上报。
在本实施例中，每个监测组对应一个或多个DCI，每个DCI使用一个或多个波束，当用户设备检测到某个监测组所对应的波束均传输失败时，上报针对该监测组的波束失败事件，例如向网络设备发送波束失败恢复请求，以便网络设备为其重新分配波束。
在本实施例中，一个DCI是指传输中的一个下行控制信息，例如，其可以对应一种DCI格式(DCI format)。从物理传输资源上来看，一个DCI也可以是一个PDCCH candidate或者candidate集合。
在本实施例中一个实施方式中，每个监测组包括一个或多个DCI所对应的所有准共址的标识，也即前述CORESET配置中的QCL-ConfigId。由于QCL的ID对波束进行了指示，当用户设备检测到某个监测组所包含的所有QCL的ID对应的DCI所使用的波束均传输失败时，上报针对该监测组的波束失败事件。在本实施方式中，对于同一个监测组包含多个DCI所对应的所有QCL的ID的情况，该多个DCI使用相同的波束。也即本实施方式适用于同一个监测组对应的多个DCI的准共址标识配置相同的情况，即同一个监测组对应的多个DCI使用相同的波束的情况。
在本实施例的另一个实施方式中，每个监测组包括一个DCI所对应的物理资源的标识，例如控制资源集的标识、搜索空间的标识、和/或控制信道候选集合的标识等。例如，CORESET中的天线端口的QCL的指示粒度为PDCCH候选集合，当一个DCI在多个控制资源集上传输时，该物理资源的标识可以包括该DCI所处的所有控制资源集的标识及相应的PDCCH候选集合的标识。
由于该物理资源的标识与DCI对应，当用户设备检测到某个监测组所包含的物理资源的标识对应的DCI所使用的波束均传输失败时，上报针对该监测组的波束失败事件。
通过本实施例的方法，在CORESET的配置之外，网络设备还额外为用户设备配置用于触发用户设备进行波束失败事件上报的控制信道监测组，在用户设备检测到该监测组所对应的波束均传输失败的情况下进行波束失败事件的上报，解决了无论一个DCI在多个CORESET内传输，还是一个CORESET传输多个DCI的场景下的波束失败的检测和上报，检测的准确性更高，且不会耗费太多的资源。
实施例2
本实施例提供了一种波束失败事件的触发条件的配置方法，该方法也应用于通信系统的网络设备，例如NR标准定义的gNB等。图3是该方法的示意图，如图3所示，该方法包括：
步骤301：网络设备为用户设备配置一个或多个波束失败事件的触发条件，以便所述用户设备在满足所述触发条件时，进行波束失败事件的上报。
在本实施例中，与实施例1中网络设备为用户设备配置控制信道监测组不同，在本实施例中，网络设备直接为用户设备配置波束失败事件的触发条件，用户设备只需要检测是否满足该触发条件，在满足的情况下，进行波束失败事件的上报。
在本实施例中，该触发条件可以是以下任意一种或多种：
任意一个控制资源集所包含的所有DCI所使用的全部波束传输失败；
所有控制资源集所包含的所有DCI所使用的全部波束传输失败；以及
预先定义的控制资源集的集合所包含的所有DCI所使用的全部波束传输失败。
也就是说，本实施例是以控制资源集为单位进行触发条件的配置，当某个控制资源集或者所有控制资源集或某几个控制资源集所包含的所有DCI所使用的全部波束均传输失败时，进行相应的波束失败事件的上报。此外，触发条件中的控制资源集也可以是搜索空间，控制信道候选集合等物理资源。
通过本实施例的方法，在CORESET的配置之外，网络设备还额外为用户设备配置用于触发用户设备进行波束失败事件上报的触发条件，在用户设备检测到满足该触发条件的情况下进行波束失败事件的上报，由此，为一个DCI在多个CORESET内传输或者一个多个CORESET传输多个DCI的场景提供了另一种触发波束失败事件上报的解决方案。
图4示出了单DCI消息的映射情况，如图4所示，在该示例中，只有一个DCI消息，也即DCI 1，该DCI 1可以在一个CORESET内传输，如图4中(a)所示，也可以在多个CORESET内传输，如图4中(b)和(c)所示，并且，该DCI 1可以使用一个波束，如图4中(b)所示，也可以使用多个波束，如图4中(a)和(c)所示。图4中的(a)和(c)示出了每个DCI使用两个波束的情况，但本实施例并不以此作为限制，每个DCI所使用的波束的数量也可以根据标准规定。
图5示出了多DCI消息的映射情况，如图5所示，在该示例中，共有两个DCI 消息，也即DCI 1和DCI 2，其中DCI 1既能在一个CORESET内传输，如图5中(a)、(b)、(d)和(e)所示，也能在多个CORESET内传输，如图5中(c)、(f)和(g)所示。同理，DCI 2既能在一个CORESET内传输，如图5中(a)、(b)、(c)、(d)和(e)所示，也能在多个CORESET内传输，如图5中(f)和(g)所示。此外，每个CORESET可以传输一个DCI，如图5中(a)、(b)和(c)所示，也可以传输多个DCI，如图5中(d)的CORESET 3、(e)的CORESET 3、(f)的CORESET 2和CORESET 3以及(g)的CORESET 3所示。并且，该DCI 1和DCI 2可以使用一个波束，如图5中(a)、图5中(c)的DCI 1、图5中(d)所示，也可以使用多个波束，如图5中(b)、图5中(c)的DCI 2、图5中(e)、图5中(f)以及图5中(g)所示。图5中的(b)、图5中(c)的DCI 2、图5中(e)、图5中(f)以及图5中(g)示出了每个DCI使用两个波束的情况，但本实施例并不以此作为限制，每个DCI所使用的波束的数量也可以根据标准规定。
无论是图4中DCI的映射方式还是图5中DCI的映射方式，或者根据图4和图5的DCI的映射方式演变的其他DCI的映射方式，都可以使用实施例1或者实施例2的方法进行波束失败事件的触发条件的配置。
通过实施例1的方法为用户设备配置控制信道监测组，每个监测组包含对应一个或多个DCI的QCL的ID或者对应一个DCI的物理资源标识，由此，用户设备可以知道每个监测组对应的波束，当检测到某个监测组对应的波束全部传输失败时，进行针对该监测组的波束失败事件的上报。
通过实施例2的方法为用户设备配置波束失败事件的触发条件，该触发条件包含了进行波束失败事件上报的CORESET，由此，用户设备可以在检测到该CORESET所包含的所有DCI所使用的波束全部传输失败时进行波束失败事件的上报。
在本发明实施例中，实施例2的配置方法和实施例1的配置方法可以结合使用，只要保证两者的配置不冲突即可。
实施例3
本实施例提供了一种波束失败事件的触发方法，该方法应用于通信系统的终端设备，例如NR标准定义的UE等，其是与实施例1或者实施例2的方法对应的UE侧的处理，其中与实施例1和实施例2相同的内容不再重复说明。图6是该方法的示意 图，如图6所示，该方法包括：
步骤601：用户设备根据网络设备的配置确定是否满足波束失败事件的触发条件；
步骤602：在满足波束失败事件的触发条件的情况下，进行波束失败事件的上报。
在一个实施方式中，网络设备的配置为：一个或多个控制信道监测组，每个监测组对应一个或多个DCI，所述用户设备在检测到所述监测组所对应的波束均传输失败时，上报针对传输失败的监测组的波束失败事件。关于该控制信道监测组的相关内容，已经在实施例1中做了说明，其内容被合并于此，此处不再赘述。
在另一个实施方式中，网络设备的配置为：一个或多个波束失败事件的触发条件，所述用户设备在检测到满足所述触发条件时，进行波束失败事件的上报。关于该触发条件的相关内容，已经在实施例2中做了说明，其内容被合并于此，此处不再赘述。
通过本实施例的方法，在CORESET的配置之外，网络设备还额外为用户设备配置了用于触发用户设备进行波束失败事件上报的控制信道监测组，或者为用户设备配置用于触发用户设备进行波束失败事件上报的触发条件，用户设备在检测到该监测组所对应的波束均传输失败的情况下或者在检测到满足该触发条件的情况下进行波束失败事件的上报，解决了无论一个DCI在多个CORESET内传输，还是一个CORESET传输多个DCI的场景下的波束失败的检测和上报，检测的准确性更高，且不会耗费太多的资源。
实施例4
本实施例提供了一种波束失败事件的触发条件的配置装置，该装置配置于网络设备，由于该装置解决问题的原理与实施例1的方法类似，其具体的实施可以参照实施例1的方法的实施，内容相同之处不再重复说明。
图7是本实施例的波束失败事件的触发条件的配置装置的示意图，如图7所示，该装置700包括：配置单元701，其为用户设备配置一个或多个控制信道监测组，以便所述用户设备在检测到所述监测组所对应的波束均传输失败时，上报针对传输失败的监测组的波束失败事件；其中，每个监测组对应一个或多个DCI。
在本实施例中，一个所述DCI对应一种DCI格式，或者一个所述DCI对应一个控制信道候选，或者一个所述DCI对应一个控制信道候选的集合。
在一个实施方式中，每个监测组包括：一个或多个DCI所对应的所有准共址的标识，所述多个DCI的准共址标识配置相同。
在另一个实施方式中，每个监测组包括：一个DCI所对应的物理资源的标识。这里的物理资源的标识例如可以包括：控制资源集的标识、搜索空间的标识、和/或控制信道候选集合的标识等。
通过本实施例的装置，在CORESET的配置之外，网络设备还额外为用户设备配置用于触发用户设备进行波束失败事件上报的控制信道监测组，在用户设备检测到该监测组所对应的波束均传输失败的情况下进行波束失败事件的上报，解决了无论一个DCI在多个CORESET内传输，还是一个CORESET传输多个DCI的场景下的波束失败的检测和上报，检测的准确性更高，且不会耗费太多的资源。
实施例5
本实施例提供了一种波束失败事件的触发条件的配置装置，该装置配置于网络设备，由于该装置解决问题的原理与实施例2的方法类似，其具体的实施可以参照实施例2的方法的实施，内容相同之处不再重复说明。
图8是本实施例的波束失败事件的触发条件的配置装置的示意图，如图8所示，该装置800包括：配置单元801，其为用户设备配置一个或多个波束失败事件的触发条件，以便所述用户设备在满足所述触发条件时，进行波束失败事件的上报。
在本实施例中，触发条件为以下任意一种或多种：
任意一个控制资源集所包含的所有DCI所使用的全部波束传输失败；
所有控制资源集所包含的所有DCI所使用的全部波束传输失败；以及
预先定义的控制资源集的集合所包含的所有DCI所使用的全部波束传输失败。
通过本实施例的装置，在CORESET的配置之外，网络设备还额外为用户设备配置用于触发用户设备进行波束失败事件上报的触发条件，在用户设备检测到满足该触发条件的情况下进行波束失败事件的上报，由此，为一个DCI在多个CORESET内传输或者一个多个CORESET传输多个DCI的场景提供了另一种触发波束失败事件上报的解决方案。
实施例6
本实施例提供了一种波束失败事件的触发装置，由于该装置解决问题的原理与实施例3的方法类似，其具体的实施可以参照实施例3的方法的实施，内容相同之处不再重复说明。
图9是本实施例的波束失败事件的触发装置的示意图，如图9所示，该装置900包括：确定单元901和上报单元902，该确定单元901根据网络设备的配置确定是否满足波束失败事件的触发条件；该上报单元902在满足波束失败事件的触发条件的情况下，进行波束失败事件的上报。
在一个实施方式中，网络设备的配置为：一个或多个控制信道监测组，每个监测组对应一个或多个DCI，所述用户设备在检测到所述监测组所对应的波束均传输失败时，上报针对传输失败的监测组的波束失败事件。
在另一个实施方式中，网络设备的配置为：一个或多个波束失败事件的触发条件，所述用户设备在检测到满足所述触发条件时，进行波束失败事件的上报。
通过本实施例的装置，在CORESET的配置之外，网络设备还额外为用户设备配置了用于触发用户设备进行波束失败事件上报的控制信道监测组，或者为用户设备配置用于触发用户设备进行波束失败事件上报的触发条件，用户设备在检测到该监测组所对应的波束均传输失败的情况下或者在检测到满足该触发条件的情况下进行波束失败事件的上报，解决了无论一个DCI在多个CORESET内传输，还是一个CORESET传输多个DCI的场景下的波束失败的检测和上报，检测的准确性更高，且不会耗费太多的资源。
实施例7
本实施例提供了一种网络设备，该网络设备包括如实施例4或实施例5所述的波束失败事件的触发条件的配置装置。
图10是本发明实施例的网络设备的示意图。如图10所示，网络设备1000可以包括：处理器(processor)1010和存储器1020；存储器1020耦合到处理器1010。其中该存储器1020可存储各种数据；此外还存储信息处理的程序1030，并且在处理器1010的控制下执行该程序1030，以接收终端设备发送的各种信息、并且向终端设备发送各种信息。
在一个实施方式中，波束失败事件的触发条件的配置装置的功能可以被集成到中 央处理器1010中。例如，处理器1010可以被配置为：为用户设备配置一个或多个控制信道监测组，以便所述用户设备在检测到所述监测组所对应的波束均传输失败时，上报针对传输失败的监测组的波束失败事件，其中，每个监测组对应一个或多个DCI。再例如，处理器1010可以被配置为：为用户设备配置一个或多个波束失败事件的触发条件，以便所述用户设备在满足所述触发条件时，进行波束失败事件的上报。
在另一个实施方式中，波束失败事件的触发条件的配置装置可以与处理器1010分开配置，例如可以将波束失败事件的触发条件的配置装置配置为与处理器1010连接的芯片，通过处理器1010的控制来实现波束失败事件的触发条件的配置装置的功能。
此外，如图10所示，网络设备1000还可以包括：收发机1040和天线1050等；其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，网络设备1000也并不是必须要包括图10中所示的所有部件；此外，网络设备1000还可以包括图10中没有示出的部件，可以参考现有技术。
通过本实施例的网络设备，在CORESET的配置之外，还额外为用户设备配置了用于触发用户设备进行波束失败事件上报的控制信道监测组，或者为用户设备配置用于触发用户设备进行波束失败事件上报的触发条件，用户设备在检测到该监测组所对应的波束均传输失败的情况下或者在检测到满足该触发条件的情况下进行波束失败事件的上报，解决了无论一个DCI在多个CORESET内传输，还是一个CORESET传输多个DCI的场景下的波束失败的检测和上报，检测的准确性更高，且不会耗费太多的资源。
实施例8
本实施例提供了一种终端设备，该终端设备包括如实施例6所述的数据传输装置。
图11是本发明实施例的终端设备1100的系统构成的示意图。如图11所示，该终端设备1100可以包括处理器1110和存储器1120；存储器1120耦合到处理器1110。值得注意的是，该图是示例性的；还可以使用其他类型的结构，来补充或代替该结构，以实现电信功能或其他功能。
在一个实施方式中，波束失败事件的触发装置的功能可以被集成到处理器1110 中。其中，处理器1110可以被配置为：根据网络设备的配置确定是否满足波束失败事件的触发条件；在满足波束失败事件的触发条件的情况下，进行波束失败事件的上报。
在另一个实施方式中，波束失败事件的触发装置可以与处理器1110分开配置，例如可以将波束失败事件的触发装置配置为与处理器1110连接的芯片，通过处理器1110的控制来实现波束失败事件的触发装置的功能。
如图11所示，该终端设备1100还可以包括：通信模块1130、输入单元1140、显示器1150、电源1160。值得注意的是，终端设备1100也并不是必须要包括图11中所示的所有部件；此外，终端设备1100还可以包括图11中没有示出的部件，可以参考现有技术。
如图11所示，处理器1110有时也称为控制器或操作控件，可以包括微处理器或其他处理器装置和/或逻辑装置，该处理器1110接收输入并控制终端设备1100的各个部件的操作。
其中，存储器1120，例如可以是缓存器、闪存、硬驱、可移动介质、易失性存储器、非易失性存储器或其它合适装置中的一种或更多种。可储存各种数据，此外还可存储执行有关信息的程序。并且处理器1110可执行该存储器1120存储的该程序，以实现信息存储或处理等。其他部件的功能与现有类似，此处不再赘述。终端设备1100的各部件可以通过专用硬件、固件、软件或其结合来实现，而不偏离本发明的范围。
通过本实施例的终端设备，在检测到网络设备配置的控制信道监测组所对应的波束均传输失败的情况下或者在检测到满足波束失败事件的触发条件的情况下进行波束失败事件的上报，解决了无论一个DCI在多个CORESET内传输，还是一个CORESET传输多个DCI的场景下的波束失败的检测和上报，检测的准确性更高，且不会耗费太多的资源。
实施例9
本实施例提供一种通信系统，包括如实施例7所述的网络设备以及如实施例8所述的终端设备。
本发明以上的装置和方法可以由硬件实现，也可以由硬件结合软件实现。本发明涉及这样的计算机可读程序，当该程序被逻辑部件所执行时，能够使该逻辑部件实现上文所述的装置或构成部件，或使该逻辑部件实现上文所述的各种方法或步骤。本发明还涉及用于存储以上程序的存储介质，如硬盘、磁盘、光盘、DVD、flash存储器等。
结合本发明实施例描述的方法/装置可直接体现为硬件、由处理器执行的软件模块或二者组合。例如，图7中所示的功能框图中的一个或多个和/或功能框图的一个或多个组合，既可以对应于计算机程序流程的各个软件模块，亦可以对应于各个硬件模块。这些软件模块，可以分别对应于图2所示的各个步骤。这些硬件模块例如可利用现场可编程门阵列(FPGA)将这些软件模块固化而实现。
软件模块可以位于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动磁盘、CD-ROM或者本领域已知的任何其它形式的存储介质。可以将一种存储介质耦接至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息；或者该存储介质可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。该软件模块可以存储在移动终端的存储器中，也可以存储在可插入移动终端的存储卡中。例如，若设备(如移动终端)采用的是较大容量的MEGA-SIM卡或者大容量的闪存装置，则该软件模块可存储在该MEGA-SIM卡或者大容量的闪存装置中。
针对附图中描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，可以实现为用于执行本发明所描述功能的通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其它可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件或者其任意适当组合。针对附图描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，还可以实现为计算设备的组合，例如，DSP和微处理器的组合、多个微处理器、与DSP通信结合的一个或多个微处理器或者任何其它这种配置。
以上结合具体的实施方式对本发明进行了描述，但本领域技术人员应该清楚，这些描述都是示例性的，并不是对本发明保护范围的限制。本领域技术人员可以根据本发明的精神和原理对本发明做出各种变型和修改，这些变型和修改也在本发明的范围内。

Claims (10)

  1. 一种波束失败事件的触发条件的配置装置，其中，所述装置包括：
    配置单元，其为用户设备配置一个或多个控制信道监测组，以便所述用户设备在检测到所述监测组所对应的波束均传输失败时，上报针对传输失败的监测组的波束失败事件；
    其中，每个监测组对应一个或多个下行控制信息(DCI)。
  2. 根据权利要求1所述的装置，其中，每个监测组包括：一个或多个DCI所对应的所有准共址的标识，所述多个DCI的准共址标识配置相同。
  3. 根据权利要求1所述的装置，其中，每个监测组包括：一个DCI所对应的物理资源的标识。
  4. 根据权利要求3所述的装置，其中，所述物理资源的标识包括：控制资源集的标识、搜索空间的标识、和/或控制信道候选集合的标识。
  5. 根据权利要求1所述的装置，其中，一个所述DCI对应一种DCI格式，或者一个所述DCI对应一个控制信道候选，或者一个所述DCI对应一个控制信道候选的集合。
  6. 一种波束失败事件的触发条件的配置装置，其中，所述装置包括：
    配置单元，其为用户设备配置一个或多个波束失败事件的触发条件，以便所述用户设备在满足所述触发条件时，进行波束失败事件的上报。
  7. 根据权利要求6所述的装置，其中，所述触发条件为以下任意一种或多种：
    任意一个控制资源集所包含的所有DCI所使用的全部波束传输失败；
    所有控制资源集所包含的所有DCI所使用的全部波束传输失败；以及
    预先定义的控制资源集的集合所包含的所有DCI所使用的全部波束传输失败。
  8. 一种波束失败事件的触发装置，其中，所述装置包括：
    确定单元，其根据网络设备的配置确定是否满足波束失败事件的触发条件；
    上报单元，其在满足波束失败事件的触发条件的情况下，进行波束失败事件的上报。
  9. 根据权利要求8所述的装置，其中，所述网络设备的配置为：一个或多个控制信道监测组，每个监测组对应一个或多个DCI，所述用户设备在检测到所述监测组 所对应的波束均传输失败时，上报针对传输失败的监测组的波束失败事件。
  10. 根据权利要求8所述的装置，其中，所述网络设备的配置为：一个或多个波束失败事件的触发条件，所述用户设备在检测到满足所述触发条件时，进行波束失败事件的上报。
PCT/CN2017/097174 2017-08-11 2017-08-11 波束失败事件的触发条件的配置方法、装置和通信系统 Ceased WO2019028861A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
JP2019571432A JP7099481B2 (ja) 2017-08-11 2017-08-11 ビーム失敗イベントのトリガー条件の設定方法、装置及び通信システム
PCT/CN2017/097174 WO2019028861A1 (zh) 2017-08-11 2017-08-11 波束失败事件的触发条件的配置方法、装置和通信系统
EP17920832.7A EP3668231A4 (en) 2017-08-11 2017-08-11 METHOD AND APPARATUS FOR CONFIGURING A TRIPPING STATE FOR A WAVE BEAM FAILURE EVENT AND COMMUNICATION SYSTEM
CN201780091647.1A CN110710311B (zh) 2017-08-11 2017-08-11 波束失败事件的触发条件的配置方法、装置和通信系统
US16/729,913 US11272487B2 (en) 2017-08-11 2019-12-30 Method and apparatus for configuring a triggering condition of a beam failure event and a communication system
US17/583,302 US11606781B2 (en) 2017-08-11 2022-01-25 Method and apparatus for configuring a triggering condition of a beam failure event and a communication system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/097174 WO2019028861A1 (zh) 2017-08-11 2017-08-11 波束失败事件的触发条件的配置方法、装置和通信系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/729,913 Continuation US11272487B2 (en) 2017-08-11 2019-12-30 Method and apparatus for configuring a triggering condition of a beam failure event and a communication system

Publications (1)

Publication Number Publication Date
WO2019028861A1 true WO2019028861A1 (zh) 2019-02-14

Family

ID=65272908

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/097174 Ceased WO2019028861A1 (zh) 2017-08-11 2017-08-11 波束失败事件的触发条件的配置方法、装置和通信系统

Country Status (5)

Country Link
US (2) US11272487B2 (zh)
EP (1) EP3668231A4 (zh)
JP (1) JP7099481B2 (zh)
CN (1) CN110710311B (zh)
WO (1) WO2019028861A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210289414A1 (en) * 2018-11-29 2021-09-16 Huawei Technologies Co., Ltd. Information transmission method and apparatus

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019028861A1 (zh) * 2017-08-11 2019-02-14 富士通株式会社 波束失败事件的触发条件的配置方法、装置和通信系统
US11259306B2 (en) * 2018-01-12 2022-02-22 Nokia Technologies Oy Utilizing interference measurements in beam recovery procedure
WO2019166016A1 (en) * 2018-03-02 2019-09-06 FG Innovation Company Limited Scell selection for beam failure recovry
DE112019003523T5 (de) * 2018-08-08 2021-05-27 Lg Electronics Inc. Verfahren zum Senden oder Empfangen von Kanalzustandsinformationen für eine Vielzahl von Basisstationen in einem drahtlosen Kommunikationssystem, und Gerät dafür
CN117354930A (zh) * 2020-05-11 2024-01-05 富士通株式会社 波束管理装置
EP4233463A4 (en) * 2020-10-22 2024-07-31 Nokia Technologies Oy ERROR RECORDING
US12495458B2 (en) * 2022-03-30 2025-12-09 Qualcomm Incorporated Multi-path beam failure reporting techniques

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104885377A (zh) * 2012-12-21 2015-09-02 三星电子株式会社 在无线通信系统中通过波束成形发送和接收控制信道的方法和装置
WO2017024516A1 (en) * 2015-08-11 2017-02-16 Telefonaktiebolaget Lm Ericsson (Publ) Recovery from beam failure

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3100488B1 (en) * 2015-02-13 2021-10-27 MediaTek Singapore Pte. Ltd. Handling of intermittent disconnection in a millimeter wave (mmw) system
KR102015207B1 (ko) * 2015-04-21 2019-08-27 텔레호낙티에볼라게트 엘엠 에릭슨(피유비엘) 무선 링크 품질을 모니터링하기 위한 방법 및 장치
US10630410B2 (en) * 2016-05-13 2020-04-21 Telefonaktiebolaget Lm Ericsson (Publ) Network architecture, methods, and devices for a wireless communications network
US10367677B2 (en) * 2016-05-13 2019-07-30 Telefonaktiebolaget Lm Ericsson (Publ) Network architecture, methods, and devices for a wireless communications network
IL264604B1 (en) * 2016-08-10 2026-04-01 Idac Holdings Inc Methods and system for efficient power saving in wireless networks
US11082286B2 (en) * 2017-01-06 2021-08-03 Sony Corporation Beam failure recovery
US10542445B2 (en) * 2017-02-06 2020-01-21 Lg Electronics Inc. Method and device for performing radio link monitoring by user equipment in wireless communication system
US10547429B2 (en) * 2017-02-09 2020-01-28 Qualcomm Incorporated Search candidates in multi-link control channel
CN110622460B (zh) * 2017-03-15 2022-04-29 Lg电子株式会社 在无线通信系统中发送或接收信号的方法和用于其的设备
US11139881B2 (en) * 2017-03-23 2021-10-05 Ntt Docomo, Inc. User terminal and radio communication method
GB2560770A (en) * 2017-03-24 2018-09-26 Nec Corp Communication system
US10602520B2 (en) * 2017-03-24 2020-03-24 Qualcomm Incorporated Multi-link control beam switching
US10374679B2 (en) * 2017-03-31 2019-08-06 Qualcomm Incorporated Dynamic overriding of control beam monitoring configuration
US10952273B2 (en) * 2017-08-10 2021-03-16 At&T Intellectual Property I, L.P. Detecting and correcting radio link failures based on different usage scenarios
US10555359B2 (en) * 2017-08-11 2020-02-04 Futurewei Technologies, Inc. System and method for beam failure recovery
WO2019028861A1 (zh) * 2017-08-11 2019-02-14 富士通株式会社 波束失败事件的触发条件的配置方法、装置和通信系统
CN114666904B (zh) * 2017-08-11 2026-02-13 华为技术有限公司 通信方法及装置

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104885377A (zh) * 2012-12-21 2015-09-02 三星电子株式会社 在无线通信系统中通过波束成形发送和接收控制信道的方法和装置
WO2017024516A1 (en) * 2015-08-11 2017-02-16 Telefonaktiebolaget Lm Ericsson (Publ) Recovery from beam failure

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
FUJITSU: "Discussion on Beam Failure Recovery Procedure", 3GPP TSG RAN WG1 NR AD-HOC#2 R1-1710236, 16 June 2017 (2017-06-16), XP051304268 *
SAMSUNG: "Multibeam Transmission for PDCCH", 3GPP TSG RAN WG1 NR AD-HOCTT2 R1-1710695, 16 June 2017 (2017-06-16), XP051304343 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210289414A1 (en) * 2018-11-29 2021-09-16 Huawei Technologies Co., Ltd. Information transmission method and apparatus
US12457653B2 (en) * 2018-11-29 2025-10-28 Huawei Technologies Co., Ltd. Information transmission method and apparatus

Also Published As

Publication number Publication date
US11272487B2 (en) 2022-03-08
US11606781B2 (en) 2023-03-14
EP3668231A1 (en) 2020-06-17
CN110710311A (zh) 2020-01-17
JP2020526954A (ja) 2020-08-31
EP3668231A4 (en) 2021-02-17
JP7099481B2 (ja) 2022-07-12
CN110710311B (zh) 2023-05-23
US20200137750A1 (en) 2020-04-30
US20220149913A1 (en) 2022-05-12

Similar Documents

Publication Publication Date Title
US12120774B2 (en) Radio resource control procedures for machine learning
CN111512587B (zh) 配置信息的接收和发送方法、装置及通信系统
US11606781B2 (en) Method and apparatus for configuring a triggering condition of a beam failure event and a communication system
US11082864B2 (en) Method for transmitting and receiving signal by means of beam in wireless communication system, and apparatus for said method
US20210266130A1 (en) Data Transmission Method and Apparatus
JP7040617B2 (ja) シグナリング指示及び受信方法、装置及び通信システム
KR20230113297A (ko) 셀룰러 네트워크들에서 협력 머신 러닝을 위한 모델 발견 및 선택
JP2018514998A (ja) ワイヤレス通信ネットワークにおけるリレー接続を管理するためのシステム、方法、および装置
KR102594392B1 (ko) 다운링크 신호 모니터링 및 전송 방법, 및 파라미터 구성 방법 및 장치
CN113163430A (zh) 用于蜂窝通信网络中的休眠带宽部分的波束故障检测
JP2020503803A (ja) 通信方法、ネットワークデバイス、および端末デバイス
US11516811B2 (en) Control information transmission method and device
WO2018227441A1 (zh) 波束失败恢复请求的传输资源配置装置、波束失败请求的响应装置、方法及通信系统
WO2022151110A1 (zh) 波束失败信息的生成和上报方法以及装置
CN112567839A (zh) 评估无线链路质量的方法、参数配置方法、装置和系统
CN119096478A (zh) 使用混合基于人工智能（ai）的和非基于ai的技术进行波束选择的方法
WO2019136677A1 (zh) 信号接收装置及方法、通信系统
CN117223322A (zh) 连接模式移动性期间优选小区上的服务连续性
US11272434B2 (en) Narrow beam related search information
JP2024514131A (ja) 処理能力が制約されたシナリオにおいてマルチｒｔｔ測位を改善するためにｐｒｓとｓｒｓとの関連付けを定義すること
KR20210132149A (ko) 빔 실패 회복 방법 및 디바이스 및 통신 시스템
CN110121855B (zh) 信息配置装置、监测装置、方法及通信系统
WO2024164186A1 (zh) 信息收发方法与装置
CN117917178A (zh) 利用上行链路天线面板选择的波束故障恢复
CN119631463A (zh) 使用系统间移交报告的回退指示来增强移动性鲁棒性优化

Legal Events

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

Ref document number: 17920832

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019571432

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2017920832

Country of ref document: EP

Effective date: 20200311