Beam measurement report triggering method and user equipment

Abstract

The present invention provides a beam measurement report (BMR) triggering method performed by a user equipment (UE), and a UE. The method comprises: detecting a trigger event triggering a BMR, and counting the number of occurrences of the same trigger event; and triggering the BMR when the number of occurrences of the same trigger event is not less than a number threshold within a given time period.

Description

Method for triggering beam measurement report and user equipment TECHNICAL FIELD

[0001] The present application relates to the technical field of wireless communication, in particular to a method for triggering beam measurement report executed by user equipment and user equipment. BACKGROUND

[0002] With the rapid growth of mobile communication and great progress of technology, the world will move towards a fully interconnected network society, that is, anyone or anything can obtain information and share data at any time and in any place. In 2020, the number of interconnected devices reached 50 billion, of which only about 10 billion may be mobile phones and tablets, and the others are not machines talking to people, but machines talking to each other. Therefore, how to design a system to better support the Internet of Things is a subject that needs in-depth study.

[0003] To this end, at the 3rd Generation Partnership Project (3GPP) RAN #64 plenary meeting held in March 2016, a research topic of new 5G wireless access technology was proposed (see non-patent document: RP-160671 New SID Proposal: Study on New Radio Access Technology). In the description of this work project, the working frequency of the future new communication system can be extended to 100 GHz, and at the same time, at least the enhanced mobile broadband service demand, the communication demand of massive Internet of Things UE, and the service demand of high reliability requirement, etc. The project research work ended in 2018.

[0004] In the research of this topic, it is planned to use beams / beam forming to transmit information, which specifically includes using a relatively thin beam when communicating at high frequencies in order to cope with the characteristics of high-frequency channel fading too fast. However, using a relatively thin beam to transmit information is easily affected by external changes, such as the rotation of a mobile phone, the blocking of other objects, etc.

[0005] In a transmission scenario using beamforming, in order to timely report the beam signal quality and change of the serving cell to the network side, the UE can actively send the signal quality information of the beam to the network side, referred to as beam measurement report. In order to enable the UE to determine the timing of the beam measurement report, a series of beam measurement report triggering events are defined, and when at least one triggering event occurs, the UE can start or trigger the beam measurement report. However, if such beam measurement report is transmitted to the network too frequently, it will cause uplink congestion and waste of uplink resources. In order to avoid this situation, it can be defined that if the UE detects a certain event a number of times reaching or exceeding a given number within a given time period, then the UE is allowed to trigger or start the beam measurement report process. How to implement such a beam measurement report triggering mechanism is a problem to be solved. SUMMARY

[0006] To solve the above problems, the present application provides a method for triggering a beam measurement report executed by a user equipment and a user equipment.

[0007] According to an aspect of the present application, a method for triggering a beam measurement report executed by a user equipment (UE) is provided, comprising: detecting a triggering event of a beam measurement report (BMR) and counting the number of occurrences of the same triggering event; and triggering the BMR when the number of occurrences of the same triggering event within a given time period is not less than a number threshold.

[0008] Optionally, triggering the BMR when the number of occurrences of the same triggering event within a given time period is not less than a number threshold can include any one of the following: when the triggering event is detected, determining whether the number of occurrences of the same triggering event within a first time window ending at the time point when the triggering event is detected is not less than a number threshold, and triggering the BMR when the number of occurrences of the same triggering event within the first time window is not less than a number threshold; when the triggering event is detected, determining whether the number of occurrences of the same triggering event within a second time window defined by a time window timer is not less than a number threshold, and triggering the BMR when the number of occurrences of the same triggering event within the second time window is not less than a number threshold, the time window timer being started when the triggering event is first detected and being reset when it is determined that the number of occurrences of the same triggering event is not less than a number threshold; triggering the BMR when the number of occurrences of the same triggering event detected continuously at a time interval less than a given time length is not less than a number threshold.

[0009] Optionally, at least one of the following is set or performed separately for each candidate beam: the first time window; the second time window and the time window timer; the given time length; the number threshold and the count of the number of occurrences of the same trigger event.

[0010] Optionally, when the trigger event is detected, if the interval between the time point of the current detection of the trigger event and the time point of the previous detection of the same trigger event is less than an indication interval, the current detection of the trigger event is not counted.

[0011] Optionally, the given time length can be an integer multiple of the indication interval.

[0012] Optionally, the indication interval can be set in any of the following ways: the indication interval is an integer multiple of the period of the reference signal of the corresponding candidate beam; the indication interval is the maximum value between an integer multiple of the period of the reference signal of the corresponding candidate beam and a first fixed value.

[0013] Optionally, the first time window and / or the second time window can be set according to a reference period, which is the period of the reference signal corresponding to the respective beam.

[0014] Optionally, the reference period can be determined in any of the following ways: in the case of setting the first time window and / or the second time window for each candidate beam as a measurement object, the reference period is the period of the reference signal of the candidate beam corresponding to the first time window or the second time window; in the case of setting the first time window and / or the second time window for all candidate beams as measurement objects collectively, the reference period is the maximum period among the periods of the reference signals of the all candidate beams, or the maximum period among the periods of the reference signals of the all candidate beams and the period of the reference signal of the current working beam.

[0015] Optionally, the first time window and / or the second time window can be determined in one of the following ways: the first time window and / or the second time window is a given integer multiple of the reference period; the first time window and / or the second time window is the maximum value between a given integer multiple of the reference period and a second fixed value; the first time window and / or the second time window is a given integer multiple of the reference period, and the given integer multiple is the sum of the number threshold and an offset value, wherein the value of the given integer multiple is not less than the number threshold.

[0016] Furthermore, according to another aspect of the present invention, a user equipment is provided, comprising: a processor; and a memory storing instructions that, when executed by the processor, cause the user equipment to perform the method described above.

[0017] Invention Effects

[0018] According to the present invention, it is possible to avoid transmitting to the network too frequently, thereby avoiding uplink congestion and waste of uplink resources. Attached Figure Description

[0019] The above and other features of the present invention will become more apparent from the following detailed description taken in conjunction with the accompanying drawings, wherein:

[0020] Figure 1 is a flowchart illustrating a method for triggering beam measurement reports performed by a user equipment (UE) according to an embodiment of the present invention.

[0021] Figure 2 is a flowchart illustrating the method for triggering beam measurement reports performed by a user equipment (UE) according to Embodiment 1 of the present invention.

[0022] Figure 3 is a flowchart illustrating the method for triggering beam measurement reports performed by a user equipment (UE) according to Embodiment 2 of the present invention.

[0023] Figure 4 is a flowchart illustrating the method for triggering beam measurement reports performed by a user equipment (UE) according to Embodiment 3 of the present invention.

[0024] Figure 5 is a block diagram schematically illustrating the user equipment involved in this invention. Detailed Implementation

[0025] The present invention will now be described in detail with reference to the accompanying drawings and specific embodiments. It should be noted that the present invention should not be limited to the specific embodiments described below. Furthermore, for the sake of simplicity, detailed descriptions of well-known technologies not directly related to the present invention have been omitted to prevent confusion in understanding the present invention.

[0026] Before proceeding with the detailed description, the following explanation is provided for several terms used in this invention. Unless otherwise specified, the terms used in this invention shall have the meanings described below.

[0027] UE User Equipment

[0028] RLF Radio Link Failure

[0029] NR New Radio - Next-Generation Wireless Technology

[0030] LTE Long Term Evolution technology

[0031] eLTE Enhanced Long Term Evolution

[0032] MAC Medium Access Control

[0033] MAC CE MAC Control Element

[0034] PHY physical layer

[0035] PDCCH Physical Downlink Control Channel

[0036] RRC Radio Resource Control

[0037] MAC Medium Access Control

[0038] PHY physical layer

[0039] PDCCH Physical Downlink Control Channel

[0040] PUSCH Physical Uplink Shared Channel

[0041] PDSCH Physical Downlink Shared Channel

[0042] RA Random Access

[0043] PRACH Physical Random Access Channel

[0044] SSB Synchronization Signal Block

[0045] CSI-RS Channel State Information Reference signal

[0046] TCI Transmission Configuration Indicator

[0047] RSRP Reference Signal Received Power

[0048] Serving Cell: a PCell, a PSCell, or an SCell, which can be a PCell, a PSCell, or an SCell

[0049] SpCell: Special Cell, which can be a PCell or a PSCell.

[0050] PCell: Primary Cell

[0051] PSCell: Primary SCG Cell

[0052] SCell: Secondary Cell

[0053] SCG: Secondary Cell Group

[0054] C-RNTI: Cell RNTI

[0055] RNTI: Radio Network Temporary Identifier

[0056] HARQ: Hybrid Automatic Repeat Request

[0057] SINR: Signal to Noise and Interference Ratio

[0058] TRP: Transmit / Receive Point

[0059] UL-CCCH: Uplink Common Control Channel

[0060] UCI: Uplink Control Information

[0061] MCG: Master Cell Group

[0062] SCG: Secondary Cell Group

[0063] SR: Scheduling Request

[0064] PHR: Power Heardroom Report

[0065] BSR: Buffer Status Report

[0066] ACTIVE time

[0067] Non-ACTIVE time

[0068] DCI: Downlink Control Information

[0069] The following describes in detail a plurality of embodiments according to the present application, taking the NR mobile communication system and its subsequent evolution versions as an example application environment, and taking the base station and UE device supporting NR as an example. However, it should be pointed out that the present application is not limited to the following embodiments, but can be applied to more other wireless communication systems, such as eLTE communication systems, and can be applied to other base stations and UE devices, such as eLTE supporting base stations and UE devices.

[0070] Since the serving cell can include a primary cell and a secondary cell, the serving cell mentioned in the following can be a primary cell or a secondary cell if not specially stated.

[0071] Beamforming can be used in combination with carrier aggregation (CA) technology. The base station can configure multiple carriers for the UE, and different carriers can correspond to different serving cells. Among the multiple cells configured for the UE, at least one primary cell (Pcell) and one or several secondary cells (Scell) are included. Both the primary cell and the secondary cell can use beamforming technology. Correspondingly, by measuring the configured beams of each serving cell, the UE can report the beam quality of each cell.

[0072] A UE working in dual connection (DC) mode is configured with MCG and SCG, where the primary cell of MCG is referred to as Pcell, and the primary cell of SCG is referred to as PScell, and Pcell and PScell are usually referred to as SPcell.

[0073] Triggering of beam measurement and beam measurement report

[0074] A UE can be configured with one or more serving cells, each of which can be configured with at least one SSB or CSI-RS. According to the indication of the network side or the base station side, in the case where the UE is configured with a serving cell, for example, the serving cell is SPCell or is in an active state Scell, at least one SSB or CSI-RS corresponding to the beam can be referred to as the serving beam of the serving cell, or the current working beam, while other non-serving beams or non-working beams can be considered as candidate beams of the serving cell. Whether it is a serving beam or a candidate beam, it is the object of UE measurement, which is essentially to measure the SSB or CSI-RS corresponding to the beam.

[0075] The UE measures the configured SSB or CSI-RS, and takes the measured L1-RSRP (Layer one-RSRP) value as the measurement quantity of the corresponding beam, and can also take the measured L1-SINR as the measurement quantity. Whether it is L1-RSRP or L1-SINR can be regarded as the measurement result of beam measurement, and then according to the measurement result, the UE can judge whether one or more of the following events has occurred. In the case where the UE judges that one or more of the following events has occurred, the UE can trigger or start the process or flow of sending the beam measurement result to the network side or the base station. Therefore, the following events can be considered as the triggering event of sending the beam measurement report.

[0076] Event 1: the quality of the current serving beam is lower than a pre-set threshold. The quality of the beam can be characterized by a measurement quantity or a measurement result, and the current beam can refer to the beam currently used for transmission, also called the working beam. When the measurement result of the current beam is lower than the pre-set threshold, it can be considered that event 1 has occurred. The number of current serving beams is not limited to one, and in the case of only one serving beam, the measurement quantity of the serving beam is used to characterize the measurement result, which is compared with the pre-set threshold to determine whether event 1 has occurred. If the number of current serving beams is more than one, a measurement result can be obtained based on the measurement results of the serving beams, which is compared with the pre-set threshold. The comparison can be an average or a weighted average of the measurement results of the multiple serving beams, or a final result can be obtained by filtering through a specific algorithm, which is not limited here.

[0077] Event 2: at least one new beam has a measurement value, such as L1-RSRP, higher than the measurement value of the current working beam by an offset value, and the offset value is not less than a pre-set threshold. The new beam refers to a beam different from the current working beam for transmission, which can be considered as a candidate beam. When at least one new beam satisfying the above condition occurs, it can be considered that event 2 has occurred.

[0078] Event 3: at least one new beam has a measurement value higher than a pre-set threshold, at which time it can be considered that event 3 has occurred.

[0079] Event 4: the quality of the current beam is lower than the pre-set threshold 1 and the quality of at least one new beam is higher than the pre-set threshold 2, at which time it can be considered that event 4 has occurred.

[0080] In addition to the above four events, there can be other triggering events, which are not defined here. That is, all events that can cause the UE to trigger the BMR transmission process can be referred to as triggering events of BMR.

[0081] Considering the change of signal quality, once the above events occur, the UE starts or triggers the beam measurement report process, which can result in frequent reporting. Moreover, the above events can occur once and not again, so the beam measurement report can not provide much reference value to the network side. Therefore, the beam measurement report needs to be managed to avoid meaningless reporting as much as possible.

[0082] It can be considered that when the UE detects an event, the UE detects an instance of the event. Taking event 2 as an example, when the UE detects or determines that there is a new beam, the measurement value of the new beam, for example, L1-RSRP, is higher than the measurement value of the current working beam by an offset value, and the offset value is not lower than a pre-configured threshold, it can be considered that the UE detects an instance of event 2. It can be defined that if the UE detects that the number of instances of a certain event reaches or exceeds a predetermined number within a predetermined time period, the UE triggers or initiates a beam measurement report procedure.

[0083] The pre-configured thresholds in the above events can be different, respectively used for determination of the corresponding events.

[0084] In the above events, the current beam can refer to the beam currently used for transmission, also known as the working beam or serving beam.

[0085] Beam measurement report (BMR) procedure

[0086] In the case of determining the occurrence of any triggering event, the UE can send information containing beam measurement results to the network side or base station. According to the configuration of the UE, the UE can use mode A or mode B to perform the beam measurement report procedure.

[0087] Mode A (mode A) includes at least the following three steps:

[0088] Step A.1 sends resource request information / signal to the base station on the pre-configured PUCCH channel, and the requested resource is used for transmitting BMR;

[0089] Step A.2 monitors the downlink PDCCH to receive scheduling information from the base station or the network side, and such scheduling information can be included in DCI. The scheduling information can be specific information indicating the PUSCH / PUCCH resource used for transmitting BMR. The base station can schedule a PUSCH / PUCCH resource in the DCI for transmitting BMR;

[0090] Step A.3 transmits the beam measurement report on the resource obtained in step A.2.

[0091] Mode B (mode B) includes at least the following two steps:

[0092] Step B.1 sends indication information to the base station on the pre-configured PUCCH channel, indicating / notifying the base station or the network side that the UE is ready to transmit BMR, which can be referred to as indicating or notifying the transmission of BMR;

[0093] Step B.2: UE sends the beam measurement report on the pre-configured uplink resource, which can be a pre-configured PUSCH or PUCCH.

[0094] Based on the indication information or the notification information in step B.1, the base station can receive the beam measurement report on the resource in step B.2.

[0095] It can be seen that when determining that any triggering event occurs, the UE can at least perform step A.1 of mode A or step B.1 of mode B.

[0096] The transmitted BMR can be contained in the uplink control information (UCI) transmission, and can also be contained in a MAC CE and transmitted.

[0097] For the sake of simplicity, in this document, “a triggering event occurs” can be mutually replaced with “a BMR is triggered”, “a triggering event occurs” can also be mutually replaced with “a procedure of sending a BMR containing beam measurement results to the network side or the base station is started”, and “a BMR is triggered” can be mutually replaced with “a procedure of sending a BMR containing beam measurement results to the network side or the base station is started”, and “a BMR is triggered” can be mutually replaced with “a beam measurement report procedure is started”.

[0098] According to the purpose or use of the beam measurement, the UE can perform different types of beam measurement:

[0099] If the purpose of the beam measurement is to perform beam switching or beam switching, for example, to select a potential beam as a serving beam from candidate beams of a serving cell, to select a beam with the best or most suitable signal quality, and to timely switch the serving beam to a candidate beam in the case of poor service quality of the current serving beam level, the beam measurement performed for such a purpose can be referred to as serving cell beam measurement;

[0100] If the purpose of the beam measurement is to perform serving cell switching or handover, for example, by measuring the beams of one or more candidate cells (referred to as candidate cells for short) belonging to a target cell for switching, in the case of poor service beam quality of the current serving cell, and there is no suitable candidate beam belonging to the current serving cell for switching, a suitable candidate cell can be selected from the candidate cells to perform cell switching; for example, in order to perform uplink synchronization on the candidate cell as soon as possible, obtain the time advance value, and shorten the switching completion time, a PRACH signal needs to be sent in the direction of the suitable beam of the candidate cell, and the beams of the candidate cells need to be measured, and the beam measurement performed for such a purpose can be referred to as candidate cell beam measurement.

[0101] In addition, the beam measurement can also be classified according to the type of the beam measured by the UE. If the beam as the measurement object is a candidate beam of the serving cell, such beam measurement can be referred to as the beam measurement of the serving cell; if the beam as the measurement object is a beam of a candidate cell, which is a cell different from the serving cell, such beam measurement can be referred to as the beam measurement of the candidate cell.

[0102] The UE can determine whether a beam is a candidate beam of the serving cell or a beam of the candidate cell through the received configuration information. For the serving cell for which the beam measurement needs to be performed, the corresponding cell configuration information can contain the configuration information of the SSB or CSI-RS corresponding to the candidate beam. After receiving such cell configuration information, the UE can determine and perform the beam measurement of the serving cell. In the configuration information of the candidate cell, if the SSB or CSI-RS corresponding to one or several beams is contained, the beams are the beams of the candidate cell, and the measurement performed for the beams is the beam measurement of the candidate cell.

[0103] The scheme is described herein taking the beam measurement of the serving cell as an example, but the scheme herein can also be applicable to the beam measurement of the candidate cell. In the beam measurement of the serving cell, the new beam refers to the configured candidate beam, which is different from the current serving beam of the serving cell; in the beam measurement of the candidate cell, the new beam refers to the beam of the candidate cell, and one candidate cell can be configured with one or more beams, which can also be referred to as candidate beams relative to the working beam of the serving cell. The so-called new beam can also refer to a different beam compared with the previously reported candidate beam.

[0104] The scheme herein is described in detail taking the trigger event 2 as an example to determine the trigger or start of the beam measurement report, but the scheme herein can also be applicable to other trigger events,

[0105] The following first refers to FIG. 1 to describe the outline of the method of triggering the beam measurement report of the present application.

[0106] FIG. 1 is a flowchart showing the method of triggering the beam measurement report performed by the user equipment UE involved in the embodiment of the present application.

[0107] As shown in FIG. 1, in S101, the user equipment detects a triggering event triggering a beam measurement report (BMR), and counts the number of occurrences of the same triggering event. The counting of the same triggering event can be implemented by using a counter corresponding to each event. For example, if event 2 is detected, the counter corresponding to event 2 is incremented, and if event 3 is detected, the counter corresponding to event 3 is incremented.

[0108] In S103, it is determined whether the number of occurrences of the same triggering event in a given time period is not less than a number threshold. Here, the given time period can be a first time window and a second time window described later. In addition, in Embodiment 3 described later, the period during which the same triggering event is detected M times continuously at a time interval less than a given time length can also be regarded as the given time period here.

[0109] When the determination in S103 is yes, in S105, the BMR is triggered.

[0110] Therefore, since the BMR is not triggered every time the triggering event is detected, but the BMR is triggered when the number of occurrences of the same triggering event in a given time period is not less than a number threshold, the BMR can be avoided from being triggered frequently.

[0111] Hereinafter, embodiments of the present application will be described in detail with reference to the accompanying drawings.

[0112] Embodiment 1

[0113] FIG. 2 is a flowchart showing a method of triggering a beam measurement report performed by a user equipment (UE) according to Embodiment 1 of the present application.

[0114] As shown in FIG. 2, in S201, a triggering event is detected.

[0115] When the triggering event is detected, in S203, it is determined whether the number of occurrences of the same triggering event in a first time window ending at the time point at which the triggering event is detected is not less than a number threshold. For example, if event 2 is detected, it is determined whether the number of occurrences of event 2 in the past first time window ending at the time point at which event 2 is detected is not less than a number threshold.

[0116] When it is determined that the number of occurrences of the same triggering event in the first time window is not less than the number threshold, in S205, the BMR is triggered.

[0117] Hereinafter, specific descriptions will be made more specifically.

[0118] For example, when UE detects or determines that there is a new beam (e.g. beam X, which is not the current serving beam), and the measurement value (e.g. L1-RSRP) is higher than the measurement value of the current serving beam by an offset value, and the offset value is not less than a pre-configured threshold, then it can be considered that UE detects an instance of Event 2, or UE determines that an instance of Event 2 occurs.

[0119] In one case, UE detects or determines the occurrence of the instance at the physical layer, UE evaluates the number of occurrences of the same instance within a period of time. Preferably, here the "same instance" refers to the instance for the same event (i.e. both are instances of Event 2) and the same beam (i.e. both are instances for beam X). The length of the period of time to be evaluated is T_time_window, UE can evaluate from the beginning of the last period of time with length T_time_window, or evaluate from the time point of detecting or determining the current instance to the end of the period of time (When an instance for Event 2 for new beam X is reported / detected, UE evaluates over the last T_time_window period):

[0120] - When UE determines that the number of occurrences of the same instance within the period of time is equal to or greater than a pre-configured number of occurrences value, then UE can determine to trigger or initiate the beam measurement reporting procedure;

[0121] - When UE determines that the number of occurrences of the same instance within the period of time is less than (or does not exceed) the pre-configured number of occurrences value, then UE does not trigger or initiate the beam measurement reporting procedure.

[0122] Here the "pre-configured number of occurrences value" can be configured by the base station or network side through the RRC reconfiguration message, and is preferably an integer value, which can be 1, or 2 or other.

[0123] Embodiment 2

[0124] Embodiment 2 provides another implementation method.

[0125] Figure 3 is a flow chart showing the method of triggering the beam measurement reporting performed by the user equipment UE according to Embodiment 2 of the present application.

[0126] As shown in Figure 3, at S301, a triggering event is detected.

[0127] When a trigger event is detected, at S303, it is determined whether a time window timer (Timer_window timer described later) for the detected trigger event is running. The time window timer is set for each event. If the corresponding time window timer is not running, at S305, the time window timer is started. That is, the time window timer is started when a certain trigger event is detected for the first time. For example, when event 2 is detected, if the time window timer for event 2 is not running, the event 2 detected this time is the event 2 detected for the first time, and the time window timer needs to be started. If the time window timer for event 2 is running, the event 2 detected this time is not the event 2 detected for the first time.

[0128] If the time window timer is running or the time window timer is started at S305, at S307, the detection of the trigger event is counted, and it is determined whether the number of occurrences of the same trigger event within a second time window defined by the time window timer is not less than a number threshold. The operation of S307 can also be performed before S305, or in parallel with S305.

[0129] When the determination result in S307 is yes, at S309, the BMR is triggered.

[0130] In addition, at S311, the time window timer is reset. S311 can be performed before S309, or in parallel with S309.

[0131] The following is a more specific description.

[0132] The UE detects or determines the occurrence of the instance at the physical layer, and indicates the occurrence or appearance of the instance to the upper layer, such as the MAC layer. Accordingly, when the MAC layer receives the instance indication, the UE can perform the following operations:

[0133] - If the timer Timer_window is not running, the UE can start the timer Timer_window;

[0134] - The UE sets the value of the corresponding counter COUNT to increase by 1, for example, the original value of COUNT is 0, and after receiving the indication of the aforementioned instance, the value of COUNT is set to 0+1, that is, the value of COUNT is changed, and the changed value is 1;

[0135] - The UE determines whether the value of COUNT is equal to or greater than a preconfigured number / quantity value:

[0136] When the UE determines that the COUNT value is equal to or greater than the preconfigured number of times / values, the UE can determine to trigger or initiate the beam measurement reporting procedure, and optionally, the UE can stop running the timer Timer_window, or reset the timer Timer_window.

[0137] When the UE determines that the COUNT value is less than (or not more than) the preconfigured number of times / values, the UE does not trigger or initiate the beam measurement reporting procedure.

[0138]

[0139] In addition to the above operations, when the timer Timer_window expires or after the BMR containing the beam related information is sent, the UE can also reset the COUNT value to the initial value, for example, zero.

[0140] Preferably, the timer Timer_window is associated with the detected beam, or is managed based on the beam. For example, if the new beam detected by the UE is X, the timer Timer_window-1 associated with the beam X is started. If the new beam detected by the UE is Y, although the Timer_window-1 is running, the UE considers that the Timer_window associated with the beam Y is not running, and starts the associated timer Timer_window-2 for the beam Y.

[0141] Similarly, the counter COUNT is also associated with the detected beam, or is managed based on the beam. It can be considered that there are corresponding or associated counters for the beam X and the beam Y, for example, COUNT-1 is associated with the beam X, and COUNT-2 is associated with the beam Y. For the beam X detected in the instance, only the value change or reset of the counter COUNT-1 associated with the beam X is affected, and the value change or reset of the counter COUNT-2 associated with the beam Y is not affected.

[0142] Embodiment 3

[0143] Embodiment 3 provides another implementation method.

[0144] In embodiment 3, the BMR is triggered when the number of occurrences of the same trigger event detected continuously at a time interval less than the given time length is not less than the number threshold. Here, if the number threshold is M, the period during which M times of the same trigger event are continuously detected at a time interval less than the given time length can also be regarded as the above-mentioned given time period. ​

[0145] FIG. 4 is a flow chart showing a method of triggering a beam measurement report performed by a user equipment (UE) according to an embodiment of the present application.

[0146] S401, a triggering event is detected.

[0147] When the triggering event is detected, a detection interval timer (Timer_detection, to be described later) for the triggering event is started or restarted at S403. Also, a counter for the corresponding triggering event is incremented at S405. For example, when event 2 is detected, if the detection interval timer for event 2 is not in a running state, the detection interval timer is started and the counter for event 2 is incremented. When event 2 is detected, if the detection interval timer for event 2 is in a running state, it is restarted and the counter for event 2 is incremented.

[0148] After the counter is incremented, it is determined whether the value of the corresponding counter is not less than a threshold number at S407. If the determination result at S407 is YES, a BMR is triggered at S409.

[0149] Further, after the detection interval timer is started, it is determined whether the detection interval timer has expired at S411. When the detection interval timer has expired, the counter corresponding to the detection interval timer is reset at S413. For example, if the timer Timer_detection corresponding to event 2 has expired, the counter corresponding to event 2 is reset.

[0150] In the present embodiment, the timer Timer_detection is used to monitor the time interval between the present detected triggering event and the last detected triggering event. If no next same event is detected during the period from when the timer Timer_detection is started to expiration, the corresponding counter is reset. That is, if the time interval between two detected same triggering events is less than a given time length defined by the timer Timer_detection, the two detected same triggering events are regarded as continuously occurring, and if the time interval is not less than the given time length defined by the timer Timer_detection, the two detected same triggering events are not regarded as continuously occurring.

[0151] This will be described in more detail below.

[0152] The UE detects or determines the occurrence of the instance at a physical layer and indicates the occurrence or appearance of the instance to an upper layer, for example, a MAC layer. Accordingly, when the instance indication is received at the MAC layer, the UE can perform the following operations:

[0153] - start or restart a timer Timer_detection;

[0154] - the UE sets the value of the corresponding counter COUNT to increase by 1, for example, the value of COUNT is originally 0, then after receiving the indication of the foregoing example, the value of COUNT is set to 0+1, that is, the value of COUNT is changed, and the changed value is 1;

[0155] - the UE determines whether the value of COUNT is equal to or greater than a pre-configured number of times / values:

[0156] When the UE determines that the value of COUNT is equal to or greater than the pre-configured number of times / values, the UE can determine to trigger or start the beam measurement reporting procedure;

[0157] When the UE determines that the value of COUNT is less than (or does not exceed) the pre-configured number of times / values

[0158] , the UE does not trigger or start the beam measurement reporting procedure.

[0159] In addition to the above operations, when the timer Timer_detection expires or after the BMR containing the beam-related information is sent, the UE can also reset the value of COUNT to an initial value, for example, the initial value is zero.

[0160] Preferably, the timer Timer_detection is associated with the detected beam or is managed based on the beam. For example, in the case of a new beam X detected by the UE, a timer Timer_detection-1 associated with the beam X is started. If a new beam Y is detected by the UE, although the timer Timer_detection-1 is running, the UE considers that the timer Timer_detection associated with the beam Y is not running, and starts the timer Timer_detection-2 associated with the beam Y.

[0161] Similarly, the counter COUNT is also associated with the detected beam or is managed based on the beam. It can be considered that there are corresponding or associated counters for the beam X and the beam Y, for example, COUNT-1 is associated with the beam X and COUNT-2 is associated with the beam Y. For the beam X in the detected instance, only the value of the counter COUNT-1 associated with the beam X is changed or reset, and the value of the counter COUNT-2 associated with the beam Y is not changed or reset.

[0162] The length of T_time_window can be determined according to the periodicity of the reference signal (e.g., SSB or CSI-RS) corresponding to the beam X. For example, if the periodicity of the reference signal corresponding to the beam X is T_period, the length of T_time_window can be set as a multiple of T_period, e.g., T_time_window = N x T_period, and preferably N is an integer. In addition, in the case of a pre-configured number of times / quantity of values equal to M, N is greater than or equal to M, or N is not less than M, or the value of N is at least M. In this way, it can be ensured that there are M instances that can be detected within the length of T_time_window. Alternatively, the length of T_time_window can be equal to the larger value between N x T_period and a fixed value, e.g., 10 ms or 20 ms, i.e., T_time_window = max{20 ms, N x T_period}, which takes into account the evaluation capability of the UE, i.e., the UE needs at least 20 ms to perform the evaluation once. The base station can configure the periodicity of the reference signal corresponding to the beam when configuring the reference signal for the UE, so that the UE can determine the value of T_period. For the value of N, one way is that the UE can calculate N by the formula N = M + offset when the base station configures M for the UE, wherein offset can be a default value, e.g., always equal to 1, or also be configured. Another possible implementation is to directly indicate the value of N in the configuration information.

[0163] In the foregoing scheme, the running length of the timer Timer_window can be determined according to the periodicity of the reference signal corresponding to the beam X, and the specific method can adopt the scheme for determining the length of T_time_window.

[0164] In the foregoing solutions, the value of the running time of the timer Timer detection can be determined according to the periodicity of the reference signal corresponding to the beam X. For example, the indication interval between two instances can be T interval, where the length of T interval can be at least equal to a multiple of T period, for example, T interval = P*T period. Alternatively, the minimum value of the length of T interval is the maximum value between N*T period and a fixed value (e.g., 10 ms), for example, T interval = max{10 ms, P*T period}. In actual applications, the length of T interval can be greater than or equal to the minimum value of the length of T interval described above. Then the running time of the timer Timer detection can be equal to a multiple of T interval, for example, the running time of the timer Timer detection can be equal to 1 times T interval (1*T interval), or 2 times T interval (2*T interval), and so on.

[0165] In the foregoing solutions, T time_window, the timer Timer window, and the timer Timer detection can be associated with a specific beam, so when their lengths are calculated according to the reference signal of the beam, the beam used is the specific beam to which they are associated. Therefore, for beams with different reference signal periods, the calculated lengths are different.

[0166] Another possible implementation is to use a common length for the lengths of T time_window, the timer Timer window, and the timer Timer detection. That is, the lengths of T time_window or the timer Timer window or the timer Timer detection corresponding to the beam X or the beam Y are all the same.

[0167] Such a common length can be determined according to the maximum reference signal period among all candidate beams that the UE needs to measure in the serving cell configured for the UE. For example, the candidate beams that the UE needs to measure are beam X, Y, and Z, where the reference signal corresponding to the beam Z has the maximum period of 10 ms, and the reference signals corresponding to the beam X and the beam Y both have a period of 5 ms. Then, according to the foregoing method, the lengths of T time_window, the timer Timer window, and the timer Timer detection can be determined according to the beam Z.

[0168] Alternatively, the periodicity of the reference signal of the current active beam can also be considered. That is, the maximum periodicity of the reference signal of the current active beam and all the candidate beams that the UE is configured to measure is considered to determine the time duration. For example, the UE is configured to measure beams X, Y, Z and the current active beam is W, where the periodicity of the reference signal of beam W is 10 ms and the periodicity of the reference signal of beams X, Y and Z is 5 ms. Then, the time duration of T_time_window, Timer_window and Timer_detection can be determined according to beam W based on the above method. For another example, among beams X, Y, Z and W, the periodicity of the reference signal of beam X is the maximum. Then, the time duration of T_time_window, Timer_window and Timer_detection can be determined according to beam W based on the above method.

[0169] On the basis of the above embodiments, when the UE determines to trigger or initiate the beam measurement reporting procedure, one or more of the following operations are performed:

[0170] - The MAC entity or layer of the UE can instruct the physical layer to transmit a scheduling request on a pre-configured resource, and then cancel the triggered scheduling request. Preferably, the pre-configured resource is a PUCCH resource. Preferably, the triggered scheduling request is cancelled after the instruction to transmit the scheduling request is completed.

[0171] - The physical layer of the UE can instruct the upper layer (e.g. the MAC layer above the physical layer) to trigger a scheduling request. The MAC layer can determine that the scheduling request is triggered for beam measurement reporting based on the instruction information, provided that the physical layer only instructs the MAC layer to transmit the scheduling request when any of the triggering events occurs. Preferably, the physical layer can also instruct the MAC layer of the reason for triggering the scheduling request at the same time as instructing the MAC layer to trigger the scheduling request. When the reason is for beam measurement reporting, the MAC layer can perform the above operations.

[0172] - The UE can have the following operations based on the transmission mode of the configured BMR:

[0173] If it is determined that the UE is configured with the transmission mode A, in this case, the MAC entity or MAC layer of the UE can instruct the physical layer to transmit the scheduling request on the pre-configured resource, start the timer sr-ProhibitTimer, and update the value of the counter SR_COUNTER, for example, increment the value of the counter SR_COUNTER by 1. Preferably, the pre-configured resource is a PUCCH resource; upon receiving the DCI containing the scheduling or indication of BMR transmission information in step A.2 of the mode A, the triggered scheduling request is cancelled, and preferably, the running timer sr-ProhibitTimer is stopped, and optionally, the value of the counter SR_COUNTER is reset to the initial value, for example, zero;

[0174] If it is determined that the UE is configured with the transmission mode B, then the UE can transmit the scheduling request on the pre-configured resource, and then cancel the triggered scheduling request. Preferably, the pre-configured resource is a PUCCH resource. And preferably, upon completion of the indication of transmitting the scheduling request, the UE does not need to start the timer, does not need to update the value of the counter, etc., but directly cancels the triggered scheduling request.

[0175] [Modified example]

[0176] Fig. 5 is a block diagram schematically showing a user equipment according to the present application.

[0177] As shown in Fig. 5, the user equipment 500 includes at least a processor 501 and a memory 502. The processor 501 can include, for example, a microprocessor, a microcontroller, an embedded processor, etc. The memory 502 can include, for example, a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a non-volatile memory (such as a flash memory), or other memory systems, etc. The memory 502 stores program instructions. The instructions, when executed by the processor 501, can perform one or several steps in the processing method of the UE of the present disclosure.

[0178] The program running on the device according to the present application can be a program that controls a central processing unit (CPU) to enable a computer to implement the functions of the embodiments of the present application. The program or information processed by the program can be temporarily stored in a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a non-volatile memory (such as a flash memory), or other memory systems.

[0179] The programs for implementing the functions of the embodiments of the present application can be recorded on a computer-readable recording medium. The corresponding functions can be implemented by causing a computer system to read the programs recorded on the recording medium and execute the programs. The so-called "computer system" herein can be a computer system embedded in the device and can include an operating system or hardware such as a peripheral device. The "computer-readable recording medium" can be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a short-time dynamic storage program recording medium, or any other computer-readable recording medium.

[0180] The various features or function modules of the device used in the above-described embodiments can be implemented or executed by a circuit (e.g., a single-chip or multi-chip integrated circuit). The circuit designed to perform the functions described in the specification can include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gates or transistor logic, discrete hardware components, or any combination thereof. The general-purpose processor can be a microprocessor, but can also be any existing processor, controller, microcontroller, or state machine. The above-described circuit can be a digital circuit, but can also be an analog circuit. In the event that new integrated circuit technologies emerge as a result of advances in semiconductor technology, one or more embodiments of the present application can also be implemented using these new integrated circuit technologies.

[0181] Furthermore, the present application is not limited to the above-described embodiments. Although various examples of the embodiments have been described, the present application is not limited thereto. Fixed or non-mobile electronic devices installed indoors or outdoors can be used as UE devices or communication devices, such as AV devices, kitchen devices, cleaning devices, air conditioners, office devices, vending machines, and other home appliances.

[0182] As described above, the embodiments of the present application have been described in detail with reference to the accompanying drawings. However, the specific configuration is not limited to the above-described embodiments, and the present application includes any design modification that does not deviate from the gist of the present application. In addition, various modifications can be made to the present application within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in the different embodiments are also included in the technical scope of the present application. Furthermore, components described in the above-described embodiments that have the same effect can be substituted for each other.

Claims

1.A method for triggering beam measurement reporting performed by a user equipment (UE), comprising: determining that one event instance occurs and performing the following operations if a layer 1 reference signal received power (L1-RSRP) of a first reference signal is greater than a L1-RSRP of a second reference signal: starting a timer associated with the first reference signal if the timer is not started; setting a value of a counter COUNT associated with the first reference signal to be increased by 1; determining whether the value of the COUNT is equal to or greater than a preconfigured number value; in a case where the UE determines that the value of the COUNT is equal to or greater than the preconfigured number value, sending a report indication on a PUCCH channel, and sending a report on a PUSCH channel, the report including a layer 1 reference signal received power. 2.The method of claim 1, further comprising: in a case where the UE is configured with a mode A transmission mode, sending the report on a PUSCH indicated by one downlink control information (DCI). in a case where the UE is configured with a mode B transmission mode, sending the report on a PUSCH configured by a network side. 3.A user equipment (UE), comprising: a processor; and a memory storing instructions, wherein the instructions, when executed by the processor, perform the method of any one of claims 1 to 9. ​

Images