Execution method of user equipment, and user equipment
By sending scheduling requests and canceling triggered scheduling requests on pre-configured resources using the user equipment and adopting a transmission process of mode A or mode B, the problem of extended uplink synchronization time and resource waste caused by beam measurement reports is solved, and efficient beam measurement report transmission is achieved.
Patent Information
- Application Number
- PCT/CN2025/106454
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2024-07-01
- Filing Date
- 2025-07-01
- Publication Date
- 2026-01-08
AI Technical Summary
In beamforming scenarios, frequent beam measurement reports lead to prolonged uplink synchronization time and wasted resources, making it a challenge to improve the transmission efficiency of beam measurement reports.
When the user equipment determines that the scheduling request is triggered for beam measurement report transmission, it instructs the user equipment to send the scheduling request on the pre-configured resources and cancels the triggered scheduling request under specific conditions. The transmission process adopts mode A or mode B, which includes receiving resource request and resource scheduling information, and sending beam measurement report on the pre-configured resources.
This effectively avoids uplink congestion and resource waste caused by beam measurement reports, ensuring the transmission efficiency of beam measurement reports.
Smart Images

Figure CN2025106454_08012026_PF_FP_ABST
Abstract
Description
Method for execution of user equipment and user equipment TECHNICAL FIELD
[0001] The present application relates to the technical field of wireless communication, in particular to a method for execution of user equipment and user equipment. BACKGROUND
[0002] When a UE in RRC connected state moves from the coverage area of one cell to the coverage area of another cell, in order to ensure the continuity of service, the base station or the network side usually instructs the UE to perform cell switching (Cell Switch / Cell Handover) operation. The switching in the prior art is triggered by RRC signaling, that is, when the UE receives an RRC reconfiguration message (hereinafter referred to as a layer 3 handover command) carrying a synchronization identifier, it will synchronize to the target cell specified in the message. The time from receiving the layer 3 handover command to completing synchronization with the target cell is called handover delay. In the handover delay, the time for the UE to initiate random access in the target cell to obtain uplink synchronization accounts for a large proportion of the handover delay.
[0003] In order to shorten the time of uplink synchronization, a feasible method is to configure one or more candidate cells for the UE at the base station or network side before instructing the UE to perform cell switching. Before performing the switching operation, the UE can perform uplink synchronization on the candidate cell or cells in advance to obtain the uplink synchronization transmission time advance. In the scenario where the candidate cell adopts beam forming, in order to ensure the success of uplink synchronization, the UE can measure the beams of the candidate cell and send the signal quality information of the measured beams (referred to as beam measurement report) to the network side or the base station. Based on such a report, the base station can instruct the UE to perform uplink synchronization in the appropriate beam direction of the candidate cell, thereby improving the success rate of uplink synchronization. However, if such a beam measurement report is transmitted to the network too frequently, it will cause uplink congestion and waste of uplink resources. Therefore, how to ensure the transmission efficiency of the triggered beam measurement report is a problem to be solved. SUMMARY
[0004] In order to solve the above problems, the present application provides a method for execution of user equipment and user equipment.
[0005] According to one aspect of the present application, a method for execution of user equipment is provided, wherein for a pending scheduling request, in the case where the user equipment determines that the trigger cause of the scheduling request is for transmission of a beam measurement report, the user equipment instructs to send the scheduling request on a pre-configured resource, and cancels the triggered scheduling request.
[0006] In the method for performing the user equipment, preferably, the user equipment adopts a first mode or a second mode to perform the transmission procedure of the beam measurement report, the first mode comprises: step one, the user equipment sends resource request information or a signal to the base station; step two, the user equipment receives scheduling information from the base station or the network side for scheduling resources for transmitting the beam measurement report; and step three, the user equipment sends the beam measurement report on the resources obtained in step two. The second mode comprises: step one, the user equipment sends indication information to the base station to indicate or inform the base station or the network side of the transmission of the beam measurement report; and step two, the user equipment sends the beam measurement report on the pre-configured resources.
[0007] In the method for performing the user equipment, preferably, in the case where the user equipment is configured with the first mode for transmitting the beam measurement report, after the user equipment indicates to send the scheduling request on the pre-configured resources, a timer is started, the value of a counter is updated, and when the scheduling information is received, the triggered scheduling request is cancelled. In the case where the user equipment is configured with the second mode for transmitting the beam measurement report, after the user equipment indicates to send the scheduling request on the pre-configured resources, the triggered scheduling request is directly cancelled.
[0008] In the method for performing the user equipment, preferably, in the case where the trigger event for triggering the transmission of the beam measurement report does not exist when the user equipment generates the beam measurement report, the user equipment selects one candidate beam from all candidate beams for reporting, or adopts a specific type of report or a fixed format of report, or reports a default beam transmission report, or indicates that the trigger event does not exist, or does not generate the beam transmission report.
[0009] In the method for performing the user equipment, preferably, in the case where the user equipment is configured with discontinuous reception, when or after the user equipment sends resource request information for transmitting the beam measurement report in the first mode, it is considered that the user equipment is in an active period of discontinuous reception, and when or after the user equipment sends information indication for informing the transmission of the beam measurement report in the second mode, it is considered that the user equipment is in an active period of discontinuous reception.
[0010] In the method for performing the user equipment, preferably, in the case where the user equipment is in an inactive period of discontinuous reception, the user equipment cancels the triggered beam measurement report, and in the case where the user equipment is in an active period of discontinuous reception, the user equipment performs the transmission procedure of the triggered beam measurement report.
[0011] According to another aspect of the present invention, a user equipment is provided, comprising: a processor; and a memory storing instructions, wherein the instructions, when executed by the processor, perform the execution method of the user equipment described in any of the preceding aspects.
[0012] Invention Effects
[0013] According to the present invention, uplink congestion and waste of uplink resources caused by beam measurement report transmission can be avoided, and the transmission efficiency of triggered beam measurement reports can be guaranteed. Attached Figure Description
[0014] 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:
[0015] Figure 1 is a flowchart illustrating the transmission process of the beam measurement report in Mode A of this invention.
[0016] Figure 2 is a flowchart illustrating the transmission process of the beam measurement report in Mode B of this invention.
[0017] Figure 3 is a block diagram schematically illustrating the user equipment involved in the present invention. Detailed Implementation
[0018] 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.
[0019] Before proceeding with the detailed description, the following explanation is provided for several terms mentioned in this invention. Unless otherwise specified, the terms used in this invention shall have the meanings described below.
[0020] UE User Equipment
[0021] RLF Radio Link Failure
[0022] NR New Radio: Next-Generation Wireless Technology
[0023] LTE Long Term Evolution technology
[0024] eLTE Enhanced Long Term Evolution (LTE)
[0025] MAC Medium Access Control
[0026] MAC CE MAC Control Element
[0027] PHY physical layer
[0028] PDCCH Physical Downlink Control Channel
[0029] RRC Radio Resource Control
[0030] MAC Medium Access Control
[0031] PHY physical layer
[0032] PDCCH Physical Downlink Control Channel
[0033] PUSCH Physical Uplink Shared Channel
[0034] PDSCH Physical Downlink Shared Channel
[0035] RA Random Access
[0036] PRACH Physical Random Access Channel
[0037] SSB Synchronization Signal Block
[0038] CSI-RS Channel State Information Reference signal
[0039] TCI Transmission Configuration Indicator
[0040] RSRP Reference Signal Received Power
[0041] Serving Cell: a PCell, a PSCell, or an SCell, the serving cell can be a PCell, a PSCell or an SCell
[0042] SpCell: Special Cell, the special cell can be a PCell or a PSCell.
[0043] PCell: Primary Cell, the primary cell
[0044] PSCell: Primary SCG Cell, the primary SCG cell
[0045] SCell: Secondary Cell, the secondary cell
[0046] SCG: Secondary Cell Group, the secondary cell group
[0047] C-RNTI: Cell RNTI, the cell RNTI
[0048] RNTI: Radio Network Temporary Identifier, the radio network temporary identifier
[0049] HARQ: Hybrid Automatic Repeat Request, the hybrid automatic repeat request
[0050] SINR: Signal to Noise and Interference Ratio, the signal to noise and interference ratio
[0051] TRP: Transmit / Receive Point, the transmit / receive point
[0052] UL-CCCH: Uplink Common Control Channel, the uplink common control channel
[0053] UCI: Uplink Control Information, the uplink control information
[0054] MCG: Master Cell Group, the master cell group
[0055] SCG: Secondary Cell Group, the secondary cell group
[0056] SR: Scheduling Request, scheduling request
[0057] PHR: Power Heardroom Report, power headroom report
[0058] BSR: Buffer Status Report, buffer status report
[0059] ACTIVE time: active period
[0060] Non-ACTIVE time: inactive period
[0061] DCI: Downlink Control Information, downlink control information
[0062] 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 stations and UE devices 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.
[0063] 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 is a primary cell (Pcell) and one or several are secondary cells (Scell). 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.
[0064] The UE working in the dual connection (DC) mode is configured with MCG and SCG, wherein the primary cell of the MCG is referred to as Pcell, and the primary cell of the SCG is referred to as PScell, and Pcell and PScell are usually referred to as SPcell.
[0065] The following describes some technical means and technical terms involved in the present application in detail.
[0066] LTM (Layer 1 / Layer 2-triggered mobility, L1 / L2 triggered mobility)
[0067] LTM refers to the mobility operation of UE upon receiving the Layer 1 / Layer 2 signaling. Here the Layer 1 / Layer 2 signaling refers to the signaling for cell switching, in which the information of target cell is carried or indicated. The UE realizes the change of serving cell by applying or executing the configuration information of target cell.
[0068] Here the target cell refers to the cell that will replace the current serving cell to provide service for UE. The serving cell that provides service for UE before receiving the switching signaling can be called source cell. That is, after receiving the switching signaling, the UE will switch from the source cell to the target cell, and the target cell will continue to provide service for UE. The movement of UE leads to the change of serving cell (switch), which is triggered by the command or information indication of L1 or L2.
[0069] The switching and cell change involved in this article are mainly the LTM triggered switching and cell change described above.
[0070] LTM candidate cell
[0071] Before performing LTM, the UE will be configured with one or more candidate cells, which are called LTM candidate cells, one of which will become the target cell of LTM switching. The base station provides the UE with the configuration information of these candidate cells, which can be in the form of cell group configuration information, and numbers or sequences the candidate cells, each number or sequence corresponds to a candidate cell, or can determine the configuration information of a candidate cell. The configuration information can at least include the identification information of each candidate cell, such as the physical cell ID (PCID) or cell ID, and can also include the information of one or more SSBs or CSI-RSs for measuring the beams of the cell.
[0072] The beams of LTM candidate cells can be regarded as candidate beams for LTM. The UE can measure the candidate beams of LTM candidate cells configured by the UE according to the indication of the network side or base station side. In fact, the essence is to measure the SSBs or CSI-RSs corresponding to these beams.
[0073] The UE can measure the SSB or CSI-RS corresponding to the configured candidate beam, and take the measured L1-RSRP (Layer one-RSRP) value as the measurement quantity of the corresponding beam, or take the measured L1-SINR as the measurement quantity. Both L1-RSRP and L1-SINR can be regarded as the measurement result of the beam measurement.
[0074] The UE can also 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 to be served by a serving cell, for example, the serving cell is a Spcell or an Scell in an active state, at least one beam corresponding to the SSB or CSI-RS can be referred to as a serving beam of the serving cell, or a current working beam. By measuring the SSB or CSI-RS corresponding to the serving beam, the UE can take the measured L1-RSRP (Layer one-RSRP) value as the measurement quantity of the corresponding beam, or take the measured L1-SINR as the measurement quantity.
[0075] According to the beam measurement results of the serving cell and the candidate cell, the UE can determine whether one or more of the following events has occurred. In the case where the UE determines that one or more of the following events has occurred, the UE can trigger or initiate a process or flow of sending the beam measurement result to the network side or the base station. Therefore, the following events can be regarded as triggering events for sending the beam measurement report.
[0076] Event 1: The quality of the serving beam of the current serving cell is lower than a predetermined threshold.
[0077] The quality of the beam can be represented by the measurement quantity or result of the beam, and the current beam can refer to the beam currently used for transmission, also known as the working beam. When the measurement result of the current beam is lower than the predetermined threshold, it can be considered that event 1 has occurred. The number of current serving beams is not limited to one. In the case where there is only one serving beam, the measurement quantity of the serving beam is used to represent the measurement result, which is compared with the predetermined 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. The final result can be obtained by averaging or weighted averaging of the measurement results of the multiple serving beams, or by filtering through a specific algorithm, which is not limited here.
[0078] Event 2: There is at least one candidate cell, and at least one beam of the candidate cell (referred to as a candidate beam) has a measurement value, such as L1-RSRP, which is higher than the measurement value of the current working beam by an offset value, preferably, the offset value is a pre-configuration. When there is at least one candidate beam that meets the above condition, it is considered that event 2 occurs.
[0079] Event 3: There is at least one candidate cell, and at least one beam of the candidate cell has a measurement value higher than a pre-configured threshold, which can be an absolute value, at this time it is considered that event 3 occurs.
[0080] Event 4: The quality (or measurement result) of the current serving beam is lower than a pre-configured threshold 1, and at least one candidate cell has at least one beam whose quality (or measurement result) is higher than a pre-configured threshold 2, at this time it is considered that event 4 occurs.
[0081] 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 the triggering event of the BMR.
[0082] In the process of sending the beam measurement result to the network side or base station by the UE, the information containing the beam measurement result is referred to as the beam measurement report (BMR), or the layer 1 measurement report. Such a report can be generated when the above triggering event is detected, or when the above triggering event is determined, or when the UE obtains the resource for transmitting the BMR. The process of sending the report can also be referred to as reporting the beam measurement report to the network side or base station, so when the UE detects at least one of the above events in a certain serving cell, it is considered that a beam measurement report is triggered (trigger a BMR). The BMR can contain event information of triggering the BMR, such as event identification, and can also contain information of the candidate beam in the corresponding event, such as if event 2 occurs, at least one candidate beam information, such as identification information for the candidate beam, and the measurement result of the corresponding beam, can be contained in the corresponding report.
[0083] The pre-configured threshold in the above event can be different for each event.
[0084] Beam measurement report process
[0085] Upon determining that any triggering event occurs, the UE can send a beam measurement report containing the beam measurement results to the network side or the base station. Depending on the configuration of the UE, the UE can adopt mode A or mode B to perform the beam measurement report procedure.
[0086] As shown in FIG. 1, mode A contains at least three steps, and mode B contains at least two steps, as shown in FIG. 2. The specific steps are described as follows.
[0087] Mode A contains at least the following three steps:
[0088] Step A.1: The user equipment sends resource request information or a signal to the base station. Specifically, the UE sends the resource request information / signal to the base station on a pre-configured PUCCH channel, and the requested resource is used for transmitting the BMR;
[0089] Step A.2: The user equipment receives scheduling information from the base station or the network side for scheduling the resource for transmitting the beam measurement report. Specifically, the UE listens to the downlink PDCCH and receives the scheduling information from the base station or the network side. Such scheduling information can be contained in the DCI, and the scheduling information can specifically be related information indicating the PUSCH / PUCCH resource for transmitting the BMR. The base station can schedule a PUSCH / PUCCH resource in the DCI for transmitting the BMR;
[0090] Step A.3: The user equipment sends the beam measurement report on the resource obtained in step A.2. Specifically, the UE sends the beam measurement report on the resource obtained in step A.2.
[0091] Mode B contains at least the following two steps:
[0092] Step B.1: The user equipment sends indication information to the base station, indicating or notifying the base station or the network side of the transmission of the beam measurement report. Specifically, the UE sends the indication information to the base station on a pre-configured PUCCH channel, indicating / notifying the base station or the network side that the UE is ready to transmit the BMR, which can be referred to as indicating or notifying the transmission of the BMR;
[0093] Step B.2: The user equipment sends the beam measurement report on a pre-configured resource. Specifically, the UE sends the beam measurement report on a pre-configured uplink resource, which can be a pre-configured PUSCH or a 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 any of the triggering events as described above is determined to occur, the UE can perform at least step A.1 of Mode A or step B.1 of Mode B.
[0096] For simplicity of illustration, in this document, “a triggering event occurs” can be used interchangeably with “a BMR is triggered”, “a triggering event occurs” can also be used interchangeably with “a procedure of sending beam measurement results to the network side or base station is initiated”, and “a BMR is triggered” can be used interchangeably with “a procedure of sending beam measurement results to the network side or base station is initiated”, and “a BMR is triggered” can be used interchangeably with “a beam measurement reporting procedure is initiated”.
[0097] Discontinue Reception (DRX)
[0098] Discontinue Reception (DRX) means that when the UE’s traffic is not busy, the UE can not continuously monitor PDCCH (PDCCH monitoring), but periodically wakes up to continuously monitor for a period of time, and if no scheduling for the UE is received in this period of time, the UE will no longer monitor PDCCH until the next wake-up time.
[0099] DRX mode in this document means that the UE is configured with DRX function, or is configured with DRX related parameters, or means that the UE is operating in DRX. Non-DRX mode in this document means that the UE is not configured with DRX function or is not configured with DRX related parameters, or means that the UE is not operating in DRX.
[0100] When the UE is in DRX mode, it periodically monitors PDCCH, and the period is DRX cycle. When the UE wakes up to monitor PDCCH according to the DRX cycle, the UE starts a timer drx-onDurationTimer, and during the running of this timer, the UE monitors PDCCH. “Monitoring PDCCH” here means that PDCCH is received at all possible times of PDCCH, and it is detected whether the PDCCH is scrambled by the C-RNTI of the UE, i.e. whether the PDCCH is addressed to the C-RNTI of the UE (PDCCH addressed to the C-RNTI). If so, the PDCCH is decoded to obtain the information indicated therein.
[0101] A UE in DRX mode can be in an ACTIVE time or a Non-ACTIVE time. Non-ACTIVE time herein refers to a time period when the UE is not in an ACTIVE time, or a time that is not part of an ACTIVE time.
[0102] ACTIVE time refers to the time when:
[0103] - a timer drx-onDurationTimer, drx-InactivityTimer or drx-RetransmissionTimerDL or drx-RetransmissionTimerUL or ra-ContentionResolutionTimer is running; or
[0104] - a scheduling request transmitted on PUCCH is pending; or
[0105] - in a random access procedure, if the transmitted preamble sequence is not selected from the contention based random access preamble sequences, and after successfully receiving a RAR, a PDCCH addressed to the UE's C-RNTI has not been received.
[0106] The solution herein can also be used in the following scenarios:
[0107] In any of the following cases, the UE can consider no DRX is used, or is in non-DRX mode operation:
[0108] - not configured with DRX parameters; or
[0109] - configured with DRX parameters and a timer drx-InactivityTimer or drx-RetransmissionTimerDL or drx-RetransmissionTimerUL or ra-ContentionResolutionTimer is running; or
[0110] - configured with DRX parameters and a scheduling request transmitted on PUCCH is pending; or
[0111] - configured with DRX parameters and in a random access procedure, if the transmitted preamble sequence is not selected from the contention-based random access preamble sequences, and after successfully receiving a RAR, no PDCCH addressed to the UE's C-RNTI has been received.
[0112] In addition to the above cases, it can be considered that the UE is in DRX or in DRX mode operation.
[0113] Depending on the purpose or use of the beam measurement, the UE can perform different types of beam measurement:
[0114] If the purpose of the beam measurement is to perform beam switching or beam change, for example, to select a potential beam as a serving beam from the candidate beams of the serving cell, to select the beam with the best or most suitable signal quality, to timely switch the serving beam to a candidate beam in the case of a deterioration of the 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;
[0115] If the purpose of the beam measurement is to perform serving cell switching or handover, for example, to select a suitable candidate cell from one or more candidate cells (referred to as candidate cells for short) belonging to the target cell of the handover, in the case of a deterioration of the service beam quality of the current serving cell, and there is no suitable candidate beam belonging to the current serving cell for switching, the cell can be switched; for example, to send a PRACH signal in the direction of a suitable beam of a candidate cell in order to perform uplink synchronization on the candidate cell as soon as possible, obtain the value of the time advance, and shorten the time to complete the handover, 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.
[0116] In addition, the beam measurement can also be classified according to the type of beam measured by the UE. If the beam measured as an object is a candidate beam of the serving cell, such a beam measurement can be referred to as serving cell beam measurement; if the beam measured as an object is a beam of a candidate cell, which is a cell different from the serving cell, such a beam measurement can be referred to as candidate cell beam measurement.
[0117] The UE can determine whether a beam is a candidate beam of a serving cell or a beam of a candidate cell through the received configuration information. For a serving cell that needs to perform beam measurement, the corresponding cell configuration information can contain the configuration information of SSB or CSI-RS corresponding to the candidate beams. After receiving such cell configuration information, the UE can determine and perform beam measurement of the serving cell. In the configuration information of a candidate cell, if SSB or CSI-RS corresponding to one or several beams are contained, the beams are beams of the candidate cell, and the measurement performed on the beams is beam measurement of the candidate cell.
[0118] The scheme is described herein by taking beam measurement of a candidate cell as an example, but the scheme herein can also be applicable to beam measurement of a serving cell.
[0119] Hereinafter, several embodiments of the present application are described in detail with reference to the accompanying drawings.
[0120] Embodiment One
[0121] For a pending scheduling request, the UE determines the cause of triggering the scheduling request, and performs corresponding operation according to the determined cause. Here, the pending scheduling request can be: when a scheduling request is triggered, the scheduling request is considered to be pending until it is cancelled.
[0122] In one case, the UE determines that the cause of triggering the scheduling request is to perform beam measurement reporting, for example, the cause of triggering the scheduling request is to request resources from the network side or the base station for transmitting beam measurement reporting; for another example, the cause of triggering the scheduling request is to inform or instruct the network side or the base station that the UE is ready to send beam measurement reporting, which can all be considered as triggering a scheduling request for beam measurement reporting. Then in this case, the MAC entity or MAC layer of the UE can instruct the physical layer to send 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, after instructing to send the scheduling request is completed, the UE does not need to start a timer, does not need to update the value of the counter, etc., but directly cancels the triggered scheduling request.
[0123] Preferably, the MAC layer determines the trigger of the scheduling request is based on an indication from the lower layer (e.g. physical layer), which can indicate the MAC to trigger the scheduling request, and the MAC layer can determine the trigger of the scheduling request is for beam measurement reporting based on such indication from the physical layer, which can only indicate the MAC to trigger the scheduling request if any of the trigger events is determined to have occurred. Preferably, the physical layer can also indicate the reason of the trigger of the scheduling request at the same time of indicating the MAC to trigger the scheduling request, and the MAC layer can perform the above-mentioned operations if the reason of the trigger of the scheduling request is for beam measurement reporting.
[0124] In another case, the UE determines the trigger of the scheduling request is not for beam measurement reporting, e.g. the trigger of the scheduling request is due to a triggered BSR, or DSR, or PHR, which can be considered as the trigger of the scheduling request is not for beam measurement reporting, then in these cases, the MAC entity or layer of the UE can instruct the physical layer to transmit the scheduling request on a pre-configured resource, start the timer sr-ProhibitTimer, and increment the value of the counter SR_COUNTER by 1. Preferably, the pre-configured resource is a PUCCH resource.
[0125] In particular, for different modes of transmission of BMR, one possible implementation can be:
[0126] In case the UE determines the trigger of the scheduling request is for beam measurement reporting, the UE can have the following operations based on the transmission mode of the configured BMR:
[0127] - If the UE determines the UE is configured with mode A of transmission, in this case, the MAC entity or layer of the UE can instruct the physical layer to transmit the scheduling request on a pre-configured resource, start the timer sr-ProhibitTimer, and update the value of the counter SR_COUNTER, e.g. increment the value of the counter SR_COUNTER by 1. Preferably, the pre-configured resource is a PUCCH resource; upon reception of the DCI containing the scheduling or indication of the transmission of BMR in step A.2 of mode A, the UE can cancel the triggered scheduling request, and preferably stop the running timer sr-ProhibitTimer, and optionally reset the value of the counter SR_COUNTER to the initial value, e.g. zero.
[0128] - If it is determined that the UE is configured with mode B transmission, the UE can cancel the triggered scheduling request. Preferably, the pre-configured resource is PUCCH resource. And preferably, after the indication of the completion of the scheduling request, the UE does not need to start the timer, or update the counter value, etc., but directly cancels the triggered scheduling request.
[0129] Embodiment two
[0130] When the UE determines the resource for transmitting the BMR, for example, the UE receives the scheduling information in step A.2, or acquires the pre-configured resource in step B.2, if the event triggering the BMR no longer exists, how the UE generates the content of the BMR for transmission is a problem to be solved.
[0131] Generally, for example, event 2 occurs, triggering the UE to perform the BMR, then when generating the BMR, if event 2 still exists, the UE will report the candidate beams that meet the conditions in the BMR, for example, report the identification information of the beam, and also the identification information of the candidate cell to which the beam belongs, and also can contain information corresponding to event 2 in the BMR, indicating that event 2 has occurred.
[0132] But if event 2 no longer exists when generating the BMR, then one possible way is that the UE can at least contain the information of a candidate beam in the BMR, the selection of this candidate beam can be that the UE selects the candidate beam ranked first from all candidate beams according to the measurement results from high to low, or selects the candidate beams ranked in the top three, and reports their information and measurement results.
[0133] Another possible way is to predefine a reporting format or reporting type, and in the above case, i.e., when the triggering event no longer exists, the UE always uses this specific type of report or this fixed format report and contains it in the BMR. Preferably, a specific code (e.g., 001 or 000) can be used in the BMR to indicate this specific format or this specific type of report, and preferably, the content of the report is the relevant information of the candidate beam with the best measurement result, such as the corresponding identification information and measurement result.
[0134] Another possible way is that in the above case, i.e., when the triggering event no longer exists, the UE contains a default BMR in the generated BMR.
[0135] Another possible way is that the UE indicates the absence of the triggering event in the generated BMR, for example, sets the indication information to indicate that the event no longer occurs corresponding to event 2.
[0136] Another possible way is that in the above case, i.e. the triggering event no longer exists, the UE does not generate the BMR, and the UE can discard the given resource for transmitting the BMR in this case and give up transmission.
[0137] It should be noted that the aforementioned "the triggering event no longer exists" means that the event triggering the UE to perform A.1 or B.1 no longer exists, and no other triggering event exists when the BMR is generated. For example, taking the aforementioned event 2 as an example, the UE can perform A.1 or B.1 due to the occurrence of event 2, but when the UE obtains the resource for transmitting the BMR, event 2 no longer exists, but other events occur or exist, such as event 1 or event 3 occurs and exists, which can be considered as event 1 or event 3 is valid, and then the UE needs to generate the BMR based on the valid event existing at that time when generating the BMR and transmit it.
[0138] The embodiment can be combined with the first embodiment to determine the generated BMR after sending the scheduling request. The embodiment can also be implemented alone to determine the generated BMR.
[0139] Embodiment three
[0140] The UE can be configured with DRX parameters. In the case of being configured with DRX parameters, the UE can be in an active period / active time (ACTIVE time) and a non-active period / non-active time (Non-ACTIVE time). In the non-active period, the UE will not listen to the downlink PDCCH. For the UE configured with DRX parameters, when it is in the active period of DRX, it can be considered that the UE does not use DRX; when it is in the non-active period of DRX, it can be considered that the UE uses DRX.
[0141] In the case that the UE sends a scheduling request for BMR at the end of the active period, or sends a resource request for BMR (for example, step A.1), or sends notification information of the BMR (for example, step B.1), if the UE directly enters the non-active period, it can cause the UE to miss the necessary downlink scheduling.
[0142] Therefore, in order to solve such a problem, a possible solution can be:
[0143] When the UE sends a resource request for BMR, or after that, the UE can be considered in active period, such resource request can be contained in Uplink control Information (UCI), preferably the resource request is transmitted on PUCCH, e.g. step A.1; or the UE sends a request signal on a resource for BMR resource request, then at the time of sending or after that, the UE can be considered in active period, preferably the resource for BMR resource request is pre-configured PUCCH resource.
[0144] When the UE sends a information indication for notification of BMR transmission, or after that, the UE can be considered in active period, such information indication can be contained in Uplink control Information (UCI), preferably the information indication is transmitted on PUCCH, e.g. step B.1; or the UE sends an indication signal on a resource for notification of BMR, then at the time of sending or after that, the UE can be considered in active period, preferably the resource for information indication for notification of BMR transmission is pre-configured PUCCH resource.
[0145] When the UE sends a BMR, or after that, e.g. step A.3 or B.2 is performed, the UE can be considered in active period, the sent BMR can be contained in Uplink control Information (UCI), preferably the UCI or the BMR is transmitted on PUCCH or PUSCH.
[0146] Another possible way can also be when the UE sends a scheduling request on PUCCH, if the UE determines that the scheduling request is not triggered by BMR, or is not triggered by beam measurement report, e.g. the reason for triggering the scheduling request is that there is triggered BSR, or DSR, or PHR, which can be considered as the reason for triggering is not for beam measurement report, then the UE can be considered in active period; on the contrary, if the UE determines that the scheduling request is triggered by BMR, or is triggered by beam measurement report, then the UE can be considered in inactive period, and optionally the triggered BMR is cancelled when the UE enters inactive period.
[0147] Embodiment four
[0148] Considering that the UE is configured with DRX, it is expected that the UE saves power by reducing downlink monitoring during non-busy period. In order to avoid frequent reporting of BMR when the UE is configured with DRX, one possible way is that:
[0149] When any of the aforementioned triggering events occurs, or when the UE is triggered with a BMR, if the UE determines that the UE is configured with DRX or in DRX mode operation, or in the non-active period of DRX, the UE can cancel the triggered BMR, for example, can not perform step A.1 or B.1, or cancel the scheduling request triggered by the BMR at the same time.
[0150] Another possible way is that:
[0151] When any of the aforementioned triggering events occurs, or when the UE is triggered with a BMR, if the UE determines that the UE is not configured with DRX or in non-DRX mode operation, or in the active period of DRX, the UE can trigger a BMR, for example, can perform the operation of step A.1 or B.1, and further trigger a scheduling request.
[0152] Another possible way is that:
[0153] When a scheduling request is triggered due to BMR, if the UE determines that the UE is configured with DRX or in DRX mode operation, or in the non-active period of DRX, the UE can cancel the triggered scheduling request.
[0154] Another possible way is that:
[0155] When a scheduling request is triggered due to BMR, if the UE determines that the UE is not configured with DRX or in non-DRX mode operation, or in the active period of DRX, the UE can instruct the lower layer to send the scheduling request.
[0156] Preferably, the above operations can also be performed when a specific triggering event occurs, for example, when event 2 or event 3 occurs, or when there is a BMR or scheduling request triggered by a specific triggering event, for example:
[0157] When a scheduling request is triggered due to a BMR, and the BMR is triggered or initiated due to the occurrence of trigger event X, if the UE determines that the UE is in DRX or in inDRX mode operation or in the non-active period of DRX at this time, the UE can cancel the triggered scheduling request, for example, can not perform step A.1 or B.1, or cancel the scheduling request triggered by the BMR at the same time.
[0158] When a scheduling request is triggered due to a BMR, and the BMR is triggered or initiated due to the occurrence of trigger event Y, if the UE determines that the UE is in DRX or in inDRX mode operation or in the non-active period of DRX at this time, the UE can instruct the lower layer to send a scheduling request.
[0159] When trigger event X occurs, or the UE triggers or initiates a BMR due to the occurrence of trigger event X, if the UE determines that the UE is in DRX or in inDRX mode operation or in the non-active period of DRX at this time, the UE can cancel the triggered BMR, for example, can not perform step A.1 or B.1, or cancel the scheduling request triggered by the BMR at the same time.
[0160] When trigger event Y occurs, or the UE triggers or initiates a BMR due to the occurrence of event Y, if the UE determines that the UE is in DRX or in inDRX mode operation or in the non-active period of DRX at this time, the UE can trigger a BMR, for example, can perform step A.1 or B.1, and can further trigger a scheduling request.
[0161] The embodiment can be used in combination with embodiments one to three, or can be used alone, and is used for processing BMR in the case of using DRX.
[0162] [Modified example]
[0163] Fig. 3 is a block diagram schematically showing a user equipment device related to the present application.
[0164] As shown in FIG. 3, the user equipment 300 at least includes a processor 301 and a memory 302. The processor 301 can include, for example, a microprocessor, a microcontroller, an embedded processor, etc. The memory 302 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 302 stores program instructions. The instructions, when executed by the processor 301, can perform one or several steps in the processing method of the UE of the present disclosure.
[0165] The method and the related device of the present disclosure have been described above in connection with the preferred embodiments. It can be understood by those skilled in the art that the method shown above is only exemplary, and the embodiments described above can be combined with each other without contradiction. The method of the present disclosure is not limited to the steps and the order shown above.
[0166] In the embodiments of the present disclosure, in the case of containing multiple operations, the embodiments of the present disclosure exemplarily list the execution order of each operation, and the embodiments obtained by changing the execution order of each operation are also within the protection scope of the present disclosure. In addition, in the case of containing multiple judgment conditions, the embodiments obtained by changing the execution order of each judgment condition are also within the protection scope of the present disclosure. In addition, in the present disclosure, if not specifically stated, the meaning of the field defined in one embodiment can also be applied to the corresponding field involved in other embodiments. In addition, in the embodiments of the present disclosure, “if”, “when”, “if…”, “when…”, “in the case of…”, “satisfy” or “satisfy the condition” can be replaced by “in the case of…”.
[0167] The user equipment shown above can include more modules, for example, modules that can be developed or will be developed in the future, which can be used for base stations, MMEs, or UEs, etc. The various identifiers shown above are only exemplary and not restrictive, and the present disclosure is not limited to the specific information elements as examples of these identifiers. Those skilled in the art can make many changes and modifications according to the teachings of the embodiments shown.
[0168] It should be understood that the above embodiments of the present disclosure can be realized by software, hardware, or a combination of software and hardware. For example, various components inside the base station and the user equipment in the above embodiments can be realized by various devices, including but not limited to: analog circuit devices, digital circuit devices, digital signal processing (DSP) circuits, programmable processors, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), programmable logic devices (CPLDs), etc.
[0169] Further, a program running on the device according to the present application can be a program for causing a computer to implement the functions of the embodiments of the present application by controlling a central processing unit (CPU). The program or information processed by the program can be temporarily stored in a volatile memory (e.g., a random access memory (RAM)), a hard disk drive (HDD), a non-volatile memory (e.g., a flash memory), or other memory systems. Further, the program can be transmitted, distributed, and downloaded in the form of a signal over the Internet.
[0170] A program 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 program recorded on the recording medium and execute the program. The so-called "computer system" herein can be a computer system embedded in the device and can include an operating system or hardware (e.g., 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.
[0171] 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.
[0172] Further, 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.
[0173] 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 without departing 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 having the same effect described in the above-described embodiments can be substituted for each other.
Claims
1. An execution method of a user equipment, wherein, in a case that a pending scheduling request is determined by the user equipment that a triggering cause of the scheduling request is for transmission of a beam measurement report, the user equipment indicates to send the scheduling request on a pre-configured resource and cancels the triggered scheduling request.
2. The execution method of the user equipment according to claim 1, wherein, the user equipment performs a transmission procedure of the beam measurement report in a first mode or a second mode, the first mode comprises: step one, the user equipment sends resource request information or a signal to a base station; step two, the user equipment receives scheduling information from the base station or a network side that schedules a resource for transmission of the beam measurement report; and step three, the user equipment sends the beam measurement report on the resource obtained in the step two, the second mode comprises: step one, the user equipment sends indication information to the base station to indicate or inform the base station or the network side of the transmission of the beam measurement report; and step two, the user equipment sends the beam measurement report on a pre-configured resource.
3. The execution method of the user equipment according to claim 2, wherein, in a case that the user equipment is configured with the first mode for transmission of the beam measurement report, after the user equipment indicates to send the scheduling request on the pre-configured resource, a timer is started, a value of a counter is updated, and the triggered scheduling request is cancelled upon receiving the scheduling information, in a case that the user equipment is configured with the second mode for transmission of the beam measurement report, after the user equipment indicates to send the scheduling request on the pre-configured resource, the triggered scheduling request is directly cancelled.
4. The execution method of the user equipment according to any one of claims 1 to 3, wherein, in a case that a triggering event for triggering transmission of the beam measurement report does not exist when the user equipment generates the beam measurement report, the user equipment selects one candidate beam for reporting from all candidate beams, or uses a specific type of report or a fixed format of report, or reports a default beam transmission report, or indicates that the triggering event does not exist, or does not generate the beam transmission report.
5. The execution method of the user equipment according to claim 2 or 3, wherein, in a case that the user equipment is configured with discontinuous reception, in the first mode, after the user equipment sends resource request information for transmission of the beam measurement report, it is considered that the user equipment is in an active period of discontinuous reception, in the second mode, after the user equipment sends information indication for informing the transmission of the beam measurement report, it is considered that the user equipment is in the active period of discontinuous reception.
6. The execution method of the user equipment according to any one of claims 1 to 3, wherein, in a case that the user equipment is in an inactive period of discontinuous reception, the user equipment cancels the triggered beam measurement report. In a case that the user equipment is in an active period of discontinuous reception, the user equipment performs a transmission procedure of the triggered beam measurement report.
7. A user equipment comprising: a processor; and a memory storing instructions, wherein the instructions, when executed by the processor, perform the execution method of the user equipment according to any one of claims 1 to 6.
Citation Information
Patent Citations
Method and user equipment for executing beam recovery, and method and base station for supporting same
CN110447295A
Beam recovery procedure using a second component carrier
CN111316700A
Methods and apparatuses for scheduling request resource prioritization for beam failure recovery
CN114097286A
Methods of latency reduction for positioning-specific measurement reporting
US20230388085A1