Method executed by user equipment, and user equipment

Abstract

The present invention provides a method executed by a user equipment (UE), and a UE. The method comprises: when a scheduling request is triggered, a UE determines a trigger cause of the scheduling request; when determining that the trigger cause of the scheduling request is for transmitting a beam measurement report, the UE sends the scheduling request over a pre-configured resource, and then cancels the scheduling request; and when determining that the trigger cause of the scheduling request is not for transmitting a beam measurement report, the UE sends the scheduling request over a pre-configured resource, starts a timer sr-ProhibitTimer, and updates the value of a counter SR_COUNTER. Thus, the transmission efficiency of triggered beam measurement reports can be ensured, thereby improving the utilization efficiency of communication resources.

Description

Method performed by user equipment and user equipment TECHNICAL FIELD

[0001] The present application relates to the technical field of wireless communication, in particular to a method performed by user equipment and user equipment. BACKGROUND

[0002] With the rapid growth of mobile communication and great progress in 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 were mobile phones and tablets, and the others were 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 64th plenary meeting of the 3rd Generation Partnership Project (3GPP) RAN 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 least the enhanced mobile broadband service requirements, massive Internet of Things UE communication requirements, and high reliability service requirements will be met. 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 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, and the like.

[0005] In the transmission scenario using beam forming, in order to timely report the beam signal quality and changes of the serving cell to the network side, the UE can actively send the beam signal quality information to the network side, referred to as beam measurement report. If such a beam measurement report is transmitted to the network too frequently, it will cause uplink congestion and waste of uplink resources. Therefore, for the triggered beam measurement report, how to ensure its transmission efficiency is a problem to be solved. SUMMARY

[0006] To address the aforementioned problems, this invention provides a method and a user equipment executed by a user equipment, which can ensure transmission efficiency based on triggered beam measurement reports, thereby improving the utilization efficiency of communication resources.

[0007] According to one aspect of this disclosure, a method performed by a user equipment is provided, comprising: when a scheduling request is triggered, the UE determines the triggering reason of the scheduling request; if the UE determines that the triggering reason of the scheduling request is to transmit a beam measurement report, the UE sends the scheduling request on a pre-configured resource and then cancels the scheduling request; if the UE determines that the triggering reason of the scheduling request is not to transmit a beam measurement report, the UE sends the scheduling request on a pre-configured resource, starts a timer sr-ProhibitTimer, and updates the value of a counter SR_COUNTER.

[0008] Furthermore, according to 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 above-described method.

[0009] Invention Effects

[0010] According to the present invention, the transmission efficiency of triggered beam measurement reports can be guaranteed, thereby improving the utilization efficiency of communication resources. Attached Figure Description

[0011] 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:

[0012] Figure 1 is a flowchart illustrating a method performed by a user equipment (UE) according to Embodiment 1 of the present invention.

[0013] Figure 2 is a block diagram schematically illustrating the user equipment involved in the present invention. Detailed Implementation

[0014] 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.

[0015] 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.

[0016] UE User Equipment

[0017] RLF Radio Link Failure

[0018] NR New Radio

[0019] LTE Long Term Evolution

[0020] eLTE Enhaced Long Term Evolution

[0021] MAC Medium Access Control (layer)

[0022] MAC CE MAC Control Element

[0023] PHY physical layer

[0024] PDCCH Physical Downlink Control Channel

[0025] RRC Radio Resource Control (layer)

[0026] MAC Medium Access Control (layer)

[0027] PHY physical layer

[0028] PDCCH Physical Downlink Control Channel

[0029] PUSCH Physical Uplink Shared Channel

[0030] PDSCH Physical Downlink Shared Channel

[0031] RA Random Access

[0032] PRACH Physical Random Access Channel

[0033] SSB Synchronization Signal Block

[0034] CSI-RS Channel State Information Reference signal

[0035] TCI Transmission Configuration Indicator

[0036] RSRP Reference Signal Received Power

[0037] Serving Cell: a PCell, a PSCell, or an SCell; the serving cell can be a PCell, PSCell, or SCell.

[0038] SpCell: Special Cell, which can be either PCell or PSCell.

[0039] PCell: Primary Cell

[0040] PSCell: Primary SCG Cell

[0041] SCell: Secondary Cell

[0042] SCG: Secondary Cell Group

[0043] C-RNTI: Cell RNTI, Cell RNTI

[0044] RNTI: Radio Network Temporary Identifier

[0045] HARQ: Hybrid Automatic Repeat Request.

[0046] SINR: Signal to Noise and Interference Ratio.

[0047] TRP: Transmit / Receive Point

[0048] UL-CCCH: Uplink Common Control Channel

[0049] UCI: Uplink Control Information

[0050] MCG: Master Cell Group

[0051] SCG: Secondary Cell Group

[0052] SR: Scheduling Request

[0053] PHR: Power Heardroom Report

[0054] BSR: Buffer Status Report

[0055] ACTIVE time: Active period

[0056] Non-ACTIVE time: Non-active period

[0057] DCI: Downlink Control Information

[0058] The following describes in detail a plurality of embodiments according to the present application, taking as an example application environment a NR mobile communication system and its subsequent evolved versions, and taking as an example a base station and a UE device supporting NR. However, it needs to 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.

[0059] Since a 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.

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

[0061] A UE operating in dual connection (DC) mode is configured with MCG and SCG, where 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.

[0062] Beam measurement and triggering of beam measurement reporting

[0063] A UE can be configured with one or more serving cells, and each serving cell can be configured with at least one SSB or CSI-RS. According to the instructions from the network side or the base station side, in the case where the UE is configured to provide services for a serving cell, for example, the serving cell is a Spcell or an activated 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.

[0064] The UE measures the configured SSB or CSI-RS, and the measured L1-RSRP (Layer one-RSRP) value is used as the measurement quantity of the corresponding beam, and the measured L1-SINR can also be used as the measurement quantity. Both L1-RSRP and L1-SINR can be regarded as the measurement result of beam measurement. Then, according to the measurement result, 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 start a process or flow to send the beam measurement result to the network side or the base station. Therefore, the following events can be considered as triggering events for sending beam measurement reports.

[0065] Event 1: the quality of the current serving beam is lower than a pre-defined threshold. The quality of the beam can be characterized by a measurement quantity or a measurement result, and the current beam can be the beam currently used for transmission, also called the working beam. When the measurement result of the current beam is lower than the pre-defined threshold, it can be considered that event 1 occurs. The number of current serving beams is not limited to one. 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-defined threshold to determine whether event 1 occurs. 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 pre-defined threshold can be compared with the final result obtained by averaging or weighted averaging of the measurement results of the multiple serving beams, or the final result can be obtained by filtering through a specific algorithm, which is not limited here.

[0066] Event 2: at least one new beam has a measurement value, for example, 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-defined 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 occurs.

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

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

[0069] 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 BMR.

[0070] In the procedure that the UE sends the information containing the beam measurement result to the network side or the base station, the information containing the beam measurement result is referred to as a beam measurement report (BMR) or a layer 1 measurement report. Such a report can be generated when the UE detects that the trigger event occurs, or is generated when the UE determines that the trigger event occurs, or is generated when the UE obtains the resource for transmitting the BMR. The procedure of sending the report can also be referred to as reporting the beam measurement report to the network side or the base station. Therefore, when the UE detects at least one of the above-mentioned events in a certain serving cell, it can be considered that a beam measurement report is triggered (a BMR is triggered). In the BMR, the event information triggering the BMR can be included, such as an event identifier, and the information of the beam in the corresponding event can also be included, such as at least one new beam if event 2 occurs. For example, the identifier information of the new beam and the measurement result can also be included.

[0071] The preset thresholds in the above-mentioned events can be different and are respectively used for determining the corresponding events.

[0072] In the above-mentioned events, the current beam can refer to the beam currently used for transmission, also called the working beam or the serving beam.

[0073] Beam measurement report procedure

[0074] In the case of determining that any trigger event occurs, the UE can send information containing the beam measurement result to the network side or the base station. According to the configuration of the UE, the UE can adopt mode A or mode B to perform the beam measurement report procedure.

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

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

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

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

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

[0080] Step B.1: sending an indication information to the base station on a pre-configured PUCCH channel, indicating / informing the base station or network side that the UE is ready to perform the transmission of BMR, which can be simply referred to as indicating or informing the transmission of BMR;

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

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

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

[0084] For simplicity of description, in this document, “occurrence of a trigger event” can be mutually replaced with “triggering a BMR”, “occurrence of a trigger event” can also be mutually replaced with “starting a process of sending a beam measurement result to the network side or the base station”, and “triggering a BMR” can be mutually replaced with “starting a process of sending a beam measurement result to the network side or the base station”, and “triggering a BMR” can be mutually replaced with “starting a beam measurement report process”.

[0085] Discontinue Reception (DRX)

[0086] Discontinue Reception (DRX) refers to when the UE's traffic is not busy, the UE can not continuously monitor the PDCCH (PDCCH monitoring), but periodically wakes up and continuously monitors 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 the PDCCH until the next wake-up time.

[0087] The DRX mode in this document refers to a UE that is configured with a DRX function, or is configured with DRX related parameters, or refers to a UE that performs DRX operation. The Non-DRX mode in this document refers to a UE that is not configured with a DRX function or is not configured with DRX related parameters, or refers to a UE that does not perform DRX operation.

[0088] A UE in DRX mode periodically monitors PDCCH, where the period is the DRX cycle. When the UE wakes up to monitor PDCCH according to the DRX cycle, the UE starts a timer drx-onDurationTimer, during which the UE monitors PDCCH. By "monitoring PDCCH", it is meant that the UE receives PDCCH at all times when PDCCH can occur, and detects whether the PDCCH is scrambled by the UE's C-RNTI, i.e. whether the PDCCH is addressed to the UE's C-RNTI (PDCCH addressed to the C-RNTI). If so, the UE decodes the PDCCH to obtain the information indicated therein.

[0089] A UE in DRX mode can be in ACTIVE time or Non-ACTIVE time. Non-ACTIVE time in this context is the time period when the UE is not in ACTIVE time, or the time that is not part of ACTIVE time.

[0090] ACTIVE time refers to the time when the UE is in one of the following cases when the UE is configured with DRX cycle:

[0091] - the timer drx-onDurationTimer, drx-InactivityTimer or drx-RetransmissionTimerDL or drx-RetransmissionTimerUL or ra-ContentionResolutionTimer is running;

[0092] - when a scheduling request sent on PUCCH is pending

[0093] - 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.

[0094] The solution in this context can also be used in the following scenarios:

[0095] In any of the following cases, the UE can consider that no DRX is used, or is in non-DRX mode operation:

[0096] - no DRX parameters are configured or

[0097] - is configured with DRX parameters and a timer drx-InactivityTimer or drx-RetransmissionTimerDL or drx-RetransmissionTimerUL or ra-ContentionResolutionTimer is running, or

[0098] - is configured with DRX parameters and a scheduling request transmitted on PUCCH is pending, or

[0099] - is configured with DRX parameters and in a random access procedure, if the transmitted preamble sequence is not selected from contention-based random access preamble sequences, has not received a PDCCH with a C-RNTI targeting the UE after successfully receiving a RAR.

[0100] Except for the above cases, the UE can be considered to be in DRX or in DRX mode operation.

[0101] Depending on the purpose or use of the beam measurement, the UE can perform different types of beam measurement:

[0102] If the purpose of the beam measurement is to perform beam switching or beam change, e.g., to select a potential beam from candidate beams of a serving cell as a serving beam, to select a beam with the best or most suitable signal quality, to timely switch the serving beam to a candidate beam in case of a degradation of the serving beam level quality of service, the beam measurement for such a purpose can be referred to as a beam measurement of the serving cell;

[0103] If the purpose of the beam measurement is to perform a handover or switch of the serving cell, e.g., to select a suitable candidate cell from one or more candidate cells (for short, candidate cells) belonging to a handover target cell by measuring beams of the candidate cells in case of a degradation of the serving beam quality of the current serving cell and no suitable candidate beam belonging to the current serving cell is available for handover, to perform a cell handover, or to transmit a PRACH signal in a suitable beam direction of a candidate cell in order to perform uplink synchronization on the candidate cell as early as possible, to obtain a time advance value and to shorten the handover completion time, the beam measurement for such a purpose can be referred to as a beam measurement of the candidate cell.

[0104] 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.

[0105] 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 include 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 more beams is included, the beams are the beams of the candidate cell, and the measurement performed for the beams is the beam measurement of the candidate cell.

[0106] In this paper, the beam measurement of the serving cell is taken as an example to describe the scheme, but the scheme in this paper can also be applied to the beam measurement of the candidate cell.

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

[0108] Embodiment One

[0109] This embodiment gives a method performed by a UE, and Fig. 1 is a flow chart showing a method performed by a user equipment UE according to Embodiment 1 of the present application, as shown in Fig. 1, the method comprises steps S101, S102 and S103.

[0110] In step S101, the UE determines the trigger cause of the scheduling request when the scheduling request is triggered. In step S102, the UE transmits the scheduling request on the pre-configured resource in the case where it is determined that the trigger cause of the scheduling request is to transmit the beam measurement report, and then cancels the scheduling request. In step S103, the UE transmits the scheduling request on the pre-configured resource in the case where it is determined that the trigger cause of the scheduling request is not to transmit the beam measurement report, starts a timer sr-ProhibitTimer, and updates the value of a counter SR_COUNTER.

[0111] According to the above method, the transmission efficiency of the triggered beam measurement report can be ensured, thereby improving the utilization efficiency of the communication resources.

[0112] Hereinafter, the method performed by the UE of this embodiment will be described in detail.

[0113] For a pending scheduling request, the UE determines its trigger cause, and performs corresponding operation according to its determined trigger cause. Here, a pending scheduling request can be that when a scheduling request is triggered, the scheduling request is considered as pending until it is cancelled.

[0114] In one case, the UE determines that the cause of triggering the scheduling request is for beam measurement reporting, for example, the cause of triggering the scheduling request is to request resource from the network side or base station for transmitting beam measurement report; or for example, the cause of triggering the scheduling request is to inform or indicate the network side or base station that the UE is ready to transmit beam measurement report, all of which can 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 transmit the scheduling request on a pre-configured resource, and then cancel the triggered scheduling request. Preferably, the pre-configured resource is a PUCCH resource. And preferably, after the instruction of transmitting the scheduling request is completed, the UE does not need to start a timer, or update the value of a counter, etc., but directly cancels the triggered scheduling request.

[0115] Preferably, the MAC layer determines that the cause of triggering the scheduling request is based on the indication information of the lower layer (e.g. physical layer), the physical layer can instruct the MAC to trigger the scheduling request, and the MAC layer can determine that the cause of triggering the scheduling request is for beam measurement reporting based on such indication information, only in the case that the physical layer instructs the MAC to transmit the scheduling request only when any triggering event occurs. Preferably, the physical layer can also indicate the cause of triggering the scheduling request when instructing the MAC to trigger the scheduling request, and in the case that the cause is for beam measurement reporting, the MAC layer can perform the foregoing operation.

[0116] In another case, the UE determines that the cause of triggering the scheduling request is not for beam measurement reporting, for example, the cause of triggering the scheduling request is that there is a triggered BSR, or DSR, or PHR, which can be considered as the cause of triggering the scheduling request is not for beam measurement reporting, then in these cases the MAC entity or MAC layer of the UE can instruct the physical layer to transmit the scheduling request on a pre-configured resource, start a timer sr-ProhibitTimer, and update the value of a counter SR_COUNTER, for example, increment the value of the counter SR_COUNTER by 1. Preferably, the pre-configured resource is a PUCCH resource.

[0117] In particular, for different modes of transmitting BMR, one possible implementation can be:

[0118] In case the UE determines that the cause of triggering the scheduling request is for beam measurement reporting, the UE can have the following operations based on the configured transmission mode of BMR:

[0119] - If it is determined that the UE is configured with mode A of transmission, 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 mode A at the physical layer or MAC layer, 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.

[0120] - If it is determined that the UE is configured with mode B of transmission, 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, after indicating the completion 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.

[0121] Embodiment two

[0122] When the UE determines the resource for transmitting BMR, for example, the UE receives the scheduling information in step A.2, or obtains the pre-configured resource in step B.2, if the event triggering the BMR no longer exists, then how the UE generates the content of the BMR for transmission is a problem to be solved.

[0123] Generally, for example, event 2 occurs, triggering the UE to perform BMR, then when generating the BMR, if event 2 still exists, then the UE will report the new beam meeting the condition in the BMR, for example, report the identification information of the beam, and can also include information corresponding to event 2 in the BMR, indicating that event 2 has occurred.

[0124] However, if the event 2 does not exist when the BMR is generated, one possible way is that the UE can include at least the link quality of the current serving beam, for example, the measurement value of L1-RSRP of the serving beam, and preferably, other information corresponding to the serving beam, in the BMR.

[0125] Another possible way is to predefine a reporting format or reporting type, and in the above case, i.e., the triggering event does not exist, the UE always adopts the specific type of reporting or the fixed format of reporting to be included in the BMR. Preferably, a specific code (for example, 001 or 000) can be used in the BMR to represent the specific format or the specific type of reporting, and preferably, the content of the reporting is the related information of the serving beam, for example, the link quality.

[0126] Another possible way is that in the above case, i.e., the triggering event does not exist, the UE includes the default BMR in the generated BMR.

[0127] Another possible way is that the UE indicates the non-existence of the triggering event in the generated BMR, for example, sets the indication information to indicate that the event no longer occurs, corresponding to the event 2.

[0128] Another possible way is that in the above case, i.e., the triggering event does not exist, the UE does not generate the BMR.

[0129] It should be noted that the aforementioned "the triggering event does not exist" means that the event triggering the UE to perform A.1 or B.1 does not exist, and there is no other triggering event 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 the event 2, but when the UE obtains the resource for transmitting the BMR, the event 2 does not exist, but other events, for example, the event 1 or the event 3, occur and exist, and here it can be considered that the event 1 or the event 3 is valid, so the UE needs to generate the BMR based on the valid event existing at that time when generating the BMR and transmit the BMR.

[0130] The embodiment can be combined with the first embodiment to determine the generated BMR after the scheduling request is sent. The embodiment can also be implemented alone to determine the generated BMR.

[0131] Embodiment Three

[0132] A UE can be configured with DRX parameters. In case the UE is configured with DRX parameters, the UE can be in an ACTIVE TIME and a NON-ACTIVE TIME. In the NON-ACTIVE TIME, the UE will not monitor the PDCCH for downlink. For a UE configured with DRX parameters, the UE can be considered as not employing DRX when it is in the ACTIVE TIME of DRX; the UE can be considered as employing DRX when it is in the NON-ACTIVE TIME of DRX.

[0133] If the UE sends a scheduling request for BMR at the end of the ACTIVE TIME, or sends a resource request for BMR (e.g. step A.1), or sends a notification for BMR (e.g. step B.1), and the UE enters the NON-ACTIVE TIME directly, it can cause the UE to miss the necessary downlink scheduling.

[0134] Therefore, to solve such problems, a possible solution can be:

[0135] When the UE sends a resource request for BMR, or after, the UE can be considered as in the ACTIVE TIME. Such a resource request can be included in the Uplink control Information (UCI), preferably transmitted on PUCCH, e.g. step A.1; or the UE sends a request signal on a resource for BMR resource request, and at the time of sending or after, the UE can be considered as in the ACTIVE TIME, preferably such a resource for BMR resource request is a pre-configured PUCCH resource.

[0136] When the UE sends a notification for BMR, or after, the UE can be considered as in the ACTIVE TIME. Such a notification can be included in the Uplink control Information (UCI), preferably transmitted on PUCCH, e.g. step B.1; or the UE sends a notification signal on a resource for BMR, and at the time of sending or after, the UE can be considered as in the ACTIVE TIME, preferably such a resource for BMR is a pre-configured PUCCH resource.

[0137] When the UE sends a BMR, or after, 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.

[0138] Embodiment four

[0139] Considering that the UE is configured with DRX, it is desirable that the UE saves power by reducing downlink monitoring in non-busy period. To avoid frequent reporting of BMR when the UE is configured with DRX, a feasible way can be:

[0140] When any of the preceding trigger 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 non-active period of DRX, the UE can cancel the triggered BMR, i.e. step A.1 or B.1 is not performed.

[0141] Another feasible way can be:

[0142] When any of the preceding trigger 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 active period of DRX, the UE can perform the operation of step A.1 or B.1.

[0143] Another feasible way can be:

[0144] 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 non-active period of DRX, the UE can cancel the triggered scheduling request.

[0145] Another feasible way can be:

[0146] 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 active period of DRX, the UE can indicate the lower layer to send the scheduling request.

[0147] Preferably, the above operation can also be performed when a specific triggering event occurs, for example, when event 4 occurs, or event 5 occurs, or event 6 occurs, or when there is a BMR or a scheduling request triggered by a specific triggering event, for example:

[0148] When a scheduling request is triggered due to a BMR, and the BMR is triggered or initiated due to the occurrence of triggering event X, if the UE determines that the UE is in DRX or in DRX mode operation or in the non-active period of DRX at this time, the UE can cancel the triggered scheduling request.

[0149] When a scheduling request is triggered due to a BMR, and the BMR is triggered or initiated due to the occurrence of triggering event Y, if the UE determines that the UE is in DRX or in DRX mode operation or in the non-active period of DRX at this time, the UE can instruct the lower layer to send the scheduling request.

[0150] When triggering event X occurs, or the UE triggers or initiates a BMR due to the occurrence of triggering event X, if the UE determines that the UE is in DRX or in DRX mode operation or in the non-active period of DRX at this time, the UE can cancel the triggered BMR, i.e. not perform step A.1 or B.1.

[0151] When triggering 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 DRX mode operation or in the non-active period of DRX at this time, the UE can perform step A.1 or B.1.

[0152] The present embodiment can be used in combination with embodiments one to three, or can be used alone, for processing BMR in the case of DRX.

[0153] [Modified example]

[0154] Fig. 2 is a block diagram schematically showing a user equipment device to which the present application relates.

[0155] As shown in FIG. 2, the user equipment 200 includes at least a processor 201 and a memory 202. The processor 201 can include, for example, a microprocessor, a microcontroller, an embedded processor, etc. The memory 202 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 storage media. The memory 202 stores program instructions. The instructions, when executed by the processor 201, can perform one or several steps in the processing method of the UE of the present disclosure.

[0156] 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.

[0157] The 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" here can be a computer system embedded in the device, which 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.

[0158] The various features or functional modules of the device used in the above embodiments can be implemented or executed by a circuit (for example, a single-chip or multi-chip integrated circuit). The circuit designed to perform the functions described in this 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 of the above devices. The general-purpose processor can be a microprocessor, or any existing processor, controller, microcontroller, or state machine. The above circuit can be a digital circuit or an analog circuit. In the case of new integrated circuit technology replacing existing integrated circuit technology due to the advancement of semiconductor technology, one or more embodiments of the present application can also be implemented using these new integrated circuit technologies.

[0159] 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. Stationary 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.

[0160] 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. Further, components having the same effects described in the above-described embodiments can be substituted for each other.

Claims

1.A method performed by a user equipment (UE), comprising: determining a cause of a scheduling request triggered by the UE when the scheduling request is triggered; transmitting the scheduling request on a pre-configured resource and then cancelling the scheduling request if the cause of the scheduling request is determined to be for transmission of a beam measurement report; transmitting the scheduling request on a pre-configured resource, starting a timer sr-ProhibitTimer and updating a value of a counter SR_COUNTER if the cause of the scheduling request is determined to be not for transmission of a beam measurement report. 2.The method of claim 1, wherein, determining a configured mode of transmission of a beam measurement report if the cause of the scheduling request is determined to be for transmission of a beam measurement report, the configured mode of transmission of a beam measurement report includes mode A and mode B, mode A includes at least: a step of transmitting resource request information for transmission of a beam measurement report to a base station; a step of receiving scheduling information for scheduling a resource for transmission of a beam measurement report from the base station; a step of transmitting a beam measurement report on the resource based on the scheduling information, mode B includes at least: a step of transmitting indication information for indicating transmission of a beam measurement report to the base station; a step of transmitting a beam measurement report on a pre-configured uplink resource. 3.The method of claim 2, wherein, transmitting the scheduling request on a pre-configured resource, starting a timer sr-ProhibitTimer and updating a value of a counter SR_COUNTER if the configured mode of transmission of a beam measurement report is determined to be mode A, and cancelling the scheduling request if the scheduling information is received. 4.The method of claim 2, wherein, transmitting the scheduling request on a pre-configured resource and then cancelling the scheduling request if the configured mode of transmission of a beam measurement report is determined to be mode B. 5.The method of claim 1, wherein, the UE determines the cause of the scheduling request based on indication information from a lower layer. 6.The method of claim 1, wherein, if the triggering event for transmission of a beam measurement report does not exist when a resource for transmission of a beam measurement report is determined, the UE performs any one of the following: including at least a link quality of a current working beam in a beam measurement report if the triggering event is that a measurement value of at least one new beam is higher than a measurement value of the current working beam by an offset value not lower than a pre-configured threshold; adopting a pre-defined reporting format or reporting type in a beam measurement report; including a default beam measurement report in a generated beam measurement report; indicating non-existence of the triggering event in a generated beam measurement report; not generating a beam measurement report; generating a beam measurement report based on a currently existing valid event if there is another event or another event exists. 7.The method of claim 1, wherein, The UE is considered to be in an active period when any of the following operations is performed by the UE in a case where the UE is configured with discontinuous reception (DRX): transmitting resource request information for transmission of a beam measurement report; transmitting indication information for indicating transmission of a beam measurement report; transmitting a beam measurement report. 8.The method of claim 1, wherein, the UE is triggered for a beam measurement report, in a case where it is determined that the UE is in DRX or in a DRX operation mode or in a non-active period of DRX at this time, the triggered beam measurement report is cancelled; in a case where it is determined that the UE is not in DRX or in a non-DRX operation mode or in an active period of DRX at this time, resource request information for transmission of a beam measurement report or indication information for indicating transmission of a beam measurement report is transmitted to the base station. 9.The method of claim 1, wherein, the UE is triggered for a scheduling request due to a beam measurement report, in a case where it is determined that the UE is in DRX or in a DRX operation mode or in a non-active period of DRX at this time, the triggered scheduling request is cancelled; in a case where it is determined that the UE is not in DRX or in a non-DRX operation mode or in an active period of DRX at this time, the triggered scheduling request is transmitted. 10.A user equipment 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