WO2019062641A1

WO2019062641A1 - Wireless communication method and device

Info

Publication number: WO2019062641A1
Application number: PCT/CN2018/106738
Authority: WO
Inventors: 张崇铭; 山田升平; 刘仁茂
Original assignee: 夏普株式会社; 张崇铭
Priority date: 2017-09-27
Filing date: 2018-09-20
Publication date: 2019-04-04
Also published as: CN109561511A

Abstract

The present invention provides a method executed by a user equipment, comprising: triggering buffer status reports (BSRs); determining, on the basis of the type of a configured uplink grant and/or whether activation is performed, whether the triggered BSRs should be cancelled; and if a BSR that is triggered but not cancelled is present, determining, at least on the basis of the type of the configured uplink grant and/or whether the activation is performed, whether to trigger a scheduling request (SR). In addition, the present invention also provides a corresponding user equipment.

Description

Wireless communication method and device

Technical field

The present disclosure relates to the field of wireless communication technologies, and in particular, to a method performed by a user equipment and a corresponding device.

Background technique

With the rapid growth of mobile communications and the tremendous advances in technology, the world will move toward a fully interconnected network society where anyone or anything can access information and share data anytime and anywhere. It is estimated that by 2020, the number of connected devices will reach 50 billion, of which only about 10 billion may be mobile phones and tablets, while others are not machines that talk to people, but machines that talk to each other. Therefore, how to design a system to better support the Internet of Everything is a topic that needs in-depth study.

To this end, the research topic of the new 5G wireless access technology was proposed at the 3rd Generation Partnership Project (3GPP) RAN#64 plenary meeting held in March 2016 (see Non-Patent Document: RP-160671 New SID Proposal: Study on New Radio Access Technology). In the description of this work item, the working frequency band of the new communication system can be extended to 100 GHz, and at the same time, it will meet at least the demand for enhanced mobile broadband services, the communication requirements of massive IoT terminals, and the business requirements for high reliability requirements. The research work of the project will end in 2018.

In the future access technology, in order to support high-reliability and low-latency service transmission, the base station may allocate the configured uplink resource to the UE before the service arrives, and may wait for dynamic resource scheduling once the uplink service data arrives. Instead, the data is sent directly on the pre-configured uplink resources. In order to improve the capacity of the user and improve the utilization of the resources, the pre-configured resources can be shared by multiple UEs, that is, the base station can allocate the resources to multiple UEs at the same time. It can be considered that a certain user monopolizes the resource at a certain moment. However, there may be a conflicting situation where at some point there are at least two UEs transmitting data on the resource, resulting in a signal collision. In the case of such a collision, the base station may correctly receive data of one of the UEs, or the data of both UEs may not be correctly received.

Summary of the invention

Therefore, there is a need to improve the reliability of data transmission on the configuration resources and avoid data loss.

In order to solve the above problems, the present disclosure provides a method performed by a user equipment, comprising: triggering a buffer status report BSR; determining whether a triggered BSR should be canceled based on a type of configured uplink grant and/or whether to activate; and when present When the BSR is triggered and not canceled, it is determined whether to trigger the scheduling request SR based on at least the type of the configured uplink grant and/or whether it is activated.

In one embodiment, the method further includes receiving information of a type carrying the configured uplink grant. The type of the configured uplink grant may include a first type of uplink grant and a second type of uplink grant. For example, the first type of uplink grant and the second type of uplink grant may include:

- the first type of uplink grant is based on the uplink grant configured by the conflicting uplink resource, and the second type of uplink grant is based on the uplink grant configured by the non-conflicting uplink resource; or

- the first type of uplink grant is based on the uplink grant configured by the unscheduled uplink resource, and the second type of uplink grant is based on the uplink grant configured by the semi-statically scheduled uplink resource; or

The first type of uplink grant is an uplink grant message configured based on the conflicting, unscheduled uplink resource; the second type of uplink grant is an uplink grant configured based on the non-conflicting, semi-statically scheduled uplink resource; or

The first type of uplink grant is based on the uplink grant configured by the non-conflicting, unscheduled uplink resource; the second type of uplink grant is the uplink grant configured by the conflicting, semi-statically scheduled uplink resource.

In one embodiment, it may also be determined whether the triggered BSR should be cancelled based on whether there is an available uplink resource. For example, when there is a dynamically scheduled uplink grant, the triggered BSR is cancelled.

In an embodiment, whether to trigger the scheduling request SR may also be determined based on whether there is an available uplink resource. For example, when there is a dynamically scheduled uplink grant, the scheduling request SR is not triggered.

In one embodiment, it may also be determined whether the scheduling request SR is triggered based on whether the logical channel scheduling request timer is running.

In one embodiment, after the scheduling request SR is triggered, if the hybrid automatic repeat request HARQ feedback is received before the physical uplink control channel PUCCH resource for transmitting the SR arrives, the SR is cancelled.

In one embodiment, the buffer status report BSR is triggered when the same MAC PDU is transmitted on the configured uplink resource to the maximum number of times.

In accordance with another aspect of the present disclosure, a user device is provided that includes a processor and a memory. An instruction is stored on the memory that, when executed by the processor, causes the user device to perform a method performed by the user device in accordance with the above.

DRAWINGS

The above and other features of the present disclosure will become more apparent from the following detailed description in conjunction with the appended claims.

FIG. 1 is a flow chart illustrating a method performed by a user equipment in accordance with one embodiment of the present disclosure.

2 is a block diagram showing a user equipment in accordance with one embodiment of the present disclosure.

Detailed ways

The present disclosure is described in detail below in conjunction with the drawings and specific embodiments. It should be noted that the present disclosure should not be limited to the specific embodiments described below. In addition, the detailed description of known techniques that are not directly related to the present disclosure are omitted for the sake of brevity to prevent confusion of the understanding of the present disclosure.

The embodiments of the present disclosure are specifically described below with the LTE mobile communication system and its subsequent evolved versions as example application environments. However, it should be noted that the present disclosure is not limited to the following embodiments, but can be applied to more other wireless communication systems, such as future 5G cellular communication systems, and can be applied to other base stations and terminal devices, for example, supporting eMTC, Base stations and terminal devices such as MMTC.

Prior to the detailed description, several terms mentioned in the present disclosure are explained as follows. Unless otherwise indicated, the terms referred to in this disclosure have the following meanings.

UE User Equipment User Equipment

MAC Medium Access Control Media Access Control

RRC Radio Resource Control

BSR Buffer Status Report Cache Status Report

SR Scheduling Request Scheduling Request

TTI Transmission time Inteval transmission time interval

Slot time slot

Subframe subframe

PUCCH Physical Uplink Control CHannel Physical Uplink Control Channel

PDCCH Physical Downlink Control Cannel Physical Downlink Control Channel

PUSCH Physical Uplink Shared Channel Physical Uplink Shared Channel

DCI Downlink Control Information Downlink Control Information

UL grant upstream authorization

RNTI Radio Network Tempory Identity

HARQ Hybrid Automatic Retransmission request

PDU Packet Data Unit

During uplink data transmission, the UE usually obtains uplink resources for transmitting uplink data in a scheduled manner. For example, the base station allocates available uplink resources to the UE, and related information (such as time, frequency, starting position, subframe number, and the like) of the uplink resource may be included in the DCI, and the DCI is carried/carryed by the PDCCH. After receiving the PDCCH of the DCI carrying the uplink resource allocation information sent to the UE, the UE may consider that an uplink grant (UL grant) is received. That is, an uplink resource that is scheduled to be granted or authorized for use by the UE is received. It can be considered that the UE receives the uplink resource, that is, receives the uplink resource available to the UE. Therefore, in the following, the uplink grant can be replaced with the uplink resource unless otherwise specified. In addition, the UE transmitting data on the uplink grant means that the UE transmits data on the uplink resource that is authorized to be used.

The uplink resource related information that is available to the UE is carried in the DCI, and is dynamically sent by the base station to the UE. This manner may be referred to as dynamic scheduling. In this manner, each time the UE has an uplink data transmission, the UE needs to receive the DCI carrying the uplink resource allocation information, and the DCI is dynamically sent by the base station to the UE.

In addition to dynamic scheduling, the base station can allocate available uplink resources to the UE in other manners. For example, the base station carries the uplink resources allocated by the UE in the RRC signaling, and such resources are usually periodic. If there is uplink data transmission, the UE can use the resource in each cycle. The uplink resources allocated in this manner may be referred to as configured uplink resources or configured uplink grants. That is, the base station configures the uplink resource that can be used to the UE, or authorizes the UE to use the configured uplink resource.

FIG. 1 is a flow chart showing a method 10 performed by a user equipment UE, in accordance with one embodiment of the present disclosure.

In step S110, the buffer status report BSR is triggered. The BSR is a way for the UE to report the state of the cache. For example, a BSR is usually triggered in the following three cases.

- When the UE has no uplink data transmission, if there is uplink data from any logical channel, the BSR is triggered;

- when the UE has uplink data transmission, when a new data arrives and the logical channel from which the data originated has a higher priority than the logical channel from which the currently transmitted data originates, the BSR is triggered;

- A BSR report is generated periodically, controlled by a timer.

Alternatively, the reason why the BSR is triggered may be that the UE transmits the MAC PDU on the configured uplink grant, and when the number of transmissions or the number of retransmissions of the same MAC PDU reaches or exceeds the maximum number of times, the indication or report transmission is abnormal or The transmission on the configured uplink authorization is abnormal. Preferably, the UE may transmit the MAC PDU on the uplink grant of the type of the first type. When the number of transmissions or the number of retransmissions of the same MAC PDU reaches or exceeds the maximum number of times, the indication or report is configured as the first type. The transmission is abnormal on the upstream grant. Here, the configured first type of uplink grant is preferably an unscheduled uplink grant or a conflict-based uplink grant. The exception may be indicated or reported to the MAC entity by the UE's HARQ entity or HARQ process. The report or the indicated anomaly will trigger the BSR.

In step S120, it is determined whether the triggered BSR should be canceled based on the type of the configured uplink grant and/or whether it is activated. In the present application, the configured uplink grant and dynamic scheduling are different when the radio resource is allocated to the UE once per TTI. For example, the configured uplink grants are typically repeated in cycles, which may be based on grant free or self scheduling, or semi persistent scheduling.

The so-called uplink resource based on the non-scheduled configuration may be configured to configure related information such as a period in which the uplink resource occurs and/or a start time-frequency resource in the RRC message received by the UE. Once the UE is configured with such resources, the UE may be allowed to use the configured resources without waiting for the dynamic scheduling indication of the base station or the signaling activation/deactivation of the physical layer when there is uplink data arrival. That is, the UE may use the configured uplink grant to transmit the PUSCH without receiving any PDCCH carrying the DCI of the scheduled uplink resource or without receiving any PDCCH carrying the DCI that allows the configured uplink resource information. By "no scheduling" herein is meant that the UE does not need to wait for scheduling or scheduling indications or usage indications of the base station. From the perspective of the UE, it may be a resource that the UE schedules itself. Therefore, an uplink resource based on a non-scheduled configuration may also be referred to as an uplink resource based on a self-scheduling configuration. Alternatively, the uplink resource based on the non-scheduled configuration may also be referred to as an uplink resource based on a persistent shceduling configuration or an uplink based on a persistent shceduling configuration, as compared with the semi-static-based scheduling described below. Resources. These names can be replaced with those based on no scheduling below, and therefore will not be described again.

The so-called uplink resource based on the semi-persistent scheduling may be related information, such as time, frequency or period, configured in the RRC message received by the UE. After the UE is configured with such a resource, the resource cannot be directly used, but needs to wait until receiving the activation signaling of the physical layer (for example, the PDCCH scrambled with a specific RNTI), and is allowed to use; and the resource is activated. After that, the configured resources may be periodically used to transmit data, and the PUSCH is transmitted until a deactivation or release signaling is received, or a message for releasing the configured resource is received. During the activation of the resource, the network side does not need to send the PDCCH again or multiple times to instruct the UE to use the resource for transmission, and the configured resource may be considered to be in an active state at this time. In addition, when the UE receives the deactivation or release signaling sent by the physical layer from the base station, such signaling may be a PDCCH scrambled with a specific RNTI, and there may be an indication of release or deactivation in the DCI included in the PDCCH. Used to indicate the release or deactivation of the configured resource. After receiving the information, the UE does not continue to use the configured resources until the signaling including the activation information is received again.

The uplink resources granted to the UE may be based on no scheduling or based on semi-static scheduling. Therefore, it can be considered that the uplink grant configured to the UE can be based on no scheduling or based on semi-persistent scheduling.

In addition, the configured uplink resources can also be conflict-based or non-conflicting based.

The conflict-based uplink resource may be that the configured uplink resource may be shared by multiple UEs, or may be that the configured uplink resource may be in conflict with other users. Therefore, there is a problem or process of contention resolution. Therefore, the uplink resource can be regarded as contention based or contention resolution based uplink resource.

The non-conflicting uplink resource may be that the configured uplink resource may be regarded as a certain UE exclusive, or that the UE does not exist to collide with other users on the configured uplink resource at any time. Therefore, there is no problem or process of contention resolution. Therefore, the resource can be considered to be based on contention free based or non-contention resolution based uplink resources. These names can be replaced with conflict-based ones below, so they are not described again.

The uplink resources granted to the UE may be conflict based or non-conflicting based. Therefore, it can be considered that the uplink grant configured to the UE can be conflict based or non-conflicting based.

Therefore, the configured uplink grants received by the UE can be classified into at least two different types according to the type of the corresponding uplink resource, for example:

The first type is based on conflict and the second type is based on non-conflict; or

The first type is based on no scheduling, and the second type is based on semi-static scheduling; or

The first type is unscheduled and based on conflicts, the second type is semi-statically scheduled and based on non-conflicting; or

The first type is unscheduled and based on non-conflicting, the second type is semi-statically scheduled and conflict based.

Although the uplink grants may be of different types, in general, the configured uplink grants received by the UE include only one of them. That is, the configured uplink grant of the UE may be of the first type, and may also be of the second type. If the configured uplink grant received by the UE has both the first type and the second type, the UE needs to distinguish the logical channel or the logical channel group corresponding to the different uplink grants.

The manner in which the UE obtains the type of the configured uplink grant may include:

- receiving, after or after configuring the uplink grant, the UE receives information about the type of the configured uplink grant, the information may be included in the RRC signaling, indicating explicitly or implicitly that the configured uplink grant belongs to the first type. Still the second type; or

- When the UE receives the configuration of the uplink grant, if the network side does not indicate any type of information, the uplink grant that the UE can configure by default belongs to the first type/second type.

The UE receives the physical resource information (for example, time or frequency, etc.) corresponding to the configured uplink grant, and the physical resource may be pre-configured to be of the first type or the second type, or may be broadcast or unicast (proprietary signaling) The manner of notifying the UE of the configured physical resource type, the UE determines the type of the configured uplink authorization according to the type of the physical resource.

The UE receives the information of the physical resource corresponding to the configured uplink grant. If the physical resource information includes information specific to the uplink resource of the certain type, the UE may determine the type of the uplink grant. For example, the information of the first type of uplink resource includes time, frequency, and scrambling code, and the information of the second type of uplink resource includes only time and frequency. The first type of uplink resource is compared with the second type of uplink resource, and the scrambling code is its unique information. If the configured uplink resource information of the UE includes the scrambling code information, the UE may determine that the type of the uplink grant configured by the UE is the first type; otherwise, if the configured uplink resource information received by the UE does not include the scrambling code information Then, the UE can determine that the type of the uplink grant configured is the second type.

Alternatively, for the above-mentioned semi-static scheduling-based type, the configured uplink grant may also be in two states: one is an active state, and the other is a deactivated state (or a release state), and the UE is only authorized in the uplink. In the active state, data transmission on the configured uplink resources is allowed. For example, there may be two types of configured uplink grants, the first type is based on no scheduling, and the second type is based on semi-static scheduling. Further, the second type may have two states, an active state and a deactivated state.

Alternatively, the UE may receive status information regarding the configured uplink grants while receiving the configured uplink grants or after. For example, the UE may first receive information about the configured uplink grant, and then receive information that activates the uplink grant (eg, the DCI indication carried by the PDCCH scrambled by the specific RNTI is activated). Then, the configured uplink grant is inactive before the activation information is received. After receiving the activation information, the configured uplink authorization is in the active state. If the UE then receives information to deactivate the uplink grant (eg, the DCI indication release carried by the PDCCH scrambled by the particular C-RNTI), then the uplink grant is in a deactivated state.

Alternatively, when the UE receives the configured uplink grant, the uplink grant is in an active/deactivated state by default. When the information about the deactivation/activation of the uplink grant is received next, the uplink grant is in a deactivated/activated state.

Next, how to determine whether the triggered BSR should be canceled based on the type and/or activation of the configured uplink grant is described in detail.

Method 1: Determine whether to cancel the triggered according to the type of the configured uplink authorization. BSR

First, determine if there is a configured upstream authorization. If it does not exist, there is no need to cancel the triggered BSR (or BSR called reservation trigger). Conversely, if it exists, it is further determined which type of configured uplink grant is. If the type of the configured uplink grant is the first type, the triggered BSR does not need to be canceled. If the type of the configured uplink grant is the second type, the triggered BSR is canceled.

The process may be described as: determining whether there is an uplink grant configured as the first type, and if there is an uplink grant configured as the first type, the triggered BSR does not need to be canceled; if not configured as the first type of uplink grant , then cancel the triggered BSR. Here, "not configured as the first type of uplink grant" means that the UE is configured with an uplink grant but the type of the uplink grant of the configuration is the second type. For the case where the UE is not configured with any type of uplink grant, the triggered BSR does not need to be cancelled.

Alternatively, it can be determined whether there is an uplink grant configured as the second type. If there is an uplink grant configured as the second type, the triggered BSR is cancelled. If the BSR is not configured as the second type of uplink grant, the triggered BSR does not need to be canceled. Here, "not configured as the second type of uplink grant" may mean that the UE is not configured with any type of uplink grant or that the UE is configured with an uplink grant but the type of the uplink grant of the configuration is the first type.

Manner 2: Determine whether it is necessary to cancel the triggered according to whether the configured uplink authorization is activated. BSR

First, determine if there is an upstream authorization configured. If not, the triggered BSR does not need to be cancelled. If so, it is further determined whether the configured uplink authorization is activated. If the configured uplink grant is in the inactive/deactivated state, the triggered BSR does not need to be canceled. If the configured uplink authorization is active, the triggered BSR is canceled.

The above process can also be described as determining whether there is a configured uplink grant and is in an active state. If there is a configured uplink authorization and is in the active state, the triggered BSR is canceled. If there is no configured uplink authorization, the triggered BSR does not need to be cancelled. If the uplink grant is configured but the uplink grant is inactive, the triggered BSR does not need to be cancelled.

The above process can also be described as determining whether there is a configured uplink grant and is in an inactive state. If there is a configured uplink authorization and is inactive, the triggered BSR does not need to be canceled. If the uplink authorization is not configured, the triggered BSR does not need to be cancelled. If there is a configured uplink grant but the uplink grant is not in an inactive state (ie, in an active state), the triggered BSR is cancelled.

Manner 3: Determine according to the type of the configured uplink authorization and whether the uplink authorization is activated. Whether to cancel the triggered BSR

For example, if the type of the configured uplink grant is the second type, it may further be determined whether the uplink grant configured as the second type is activated (or is in an active state). specifically:

- if the uplink grant configured as the second type is not activated or is in the deactivated state, the triggered BSR does not need to be cancelled;

- If the uplink grant configured as the second type is activated or is active, the triggered BSR is cancelled.

The above process may be described as determining whether there is an uplink grant of the second type configured to be in an active state. If there is, cancel the triggered BSR. If there is a second type of uplink grant but the uplink grant is not in an active state (or is in a deactivated state), the triggered BSR does not need to be cancelled.

Method 4: further determining whether the cancellation needs to be triggered based on the dynamically scheduled uplink resources BSR

The difference between the fourth mode and the mode one to the third mode is that, when determining whether the triggered BSR needs to be canceled, in addition to the type and/or the activation state of the configured uplink grant, the uplink resource based on the dynamic scheduling needs to be determined (that is, whether it is required to determine whether There are available upstream resources). Preferably, it is determined whether there is an available uplink resource at the current time or the current transmission unit (for example, time slot/TTI/subframe). The available uplink resources include the configured uplink grant and the dynamically scheduled uplink grant. The available uplink resources also include uplink resources that are currently available or available in the future. If there are available uplink resources, you can cancel the BSR. Otherwise, the BSR is not cancelled.

For example, when the BSR is triggered, it is determined whether there is an available uplink resource (including a configured uplink grant or a dynamically scheduled uplink grant) in the current transport unit (eg, slot/TTI/subframe) MAC entity. If no uplink resources are available (ie, there is no configured uplink grant and there is no dynamically scheduled uplink grant), the triggered BSR is not cancelled. If there is a dynamically scheduled uplink grant, the triggered BSR is cancelled. If there is a configured uplink authorization, determine whether to cancel the triggered BSR according to the mode 1 to mode 3.

Returning to FIG. 1, in step S130, when there is a BSR that is triggered and not cancelled, it is determined whether to trigger the scheduling request SR based on at least the type of the configured uplink grant and/or whether it is activated.

For example, when there is a BSR that is triggered and not cancelled, it is determined whether there is a configured uplink authorization. If there is no configured upstream authorization, the SR is triggered. If there is a configured uplink authorization, the type of the configured uplink authorization can be further determined. The SR is triggered if the configured uplink grant is the first type of uplink grant. If the configured uplink grant is the second type of uplink grant, the SR is not triggered.

In addition, if the configured uplink grant is the second type of uplink grant, the status of the configured second type of uplink grant may be further determined. If the configured second type of uplink grant is active, the SR is not triggered. If the configured second type of uplink grant is inactive, the SR is triggered.

The foregoing process may be described as: when there is a BSR that is triggered and not cancelled, it is determined whether there is an uplink grant configured as the first type. If there is an uplink grant configured as the first type, the SR is triggered. If there is a configured uplink grant but the uplink grant is a second type of uplink grant, the SR is not triggered. If there is no configured upstream authorization, the SR is triggered.

The foregoing process may also be described as: when there is a BSR that is triggered and not cancelled, it is determined whether there is an uplink grant configured as the second type. If there is an uplink grant configured as the second type, the SR is not triggered. The SR is triggered if there is a configured uplink grant but the uplink grant is the first type of uplink grant. If there is no configured upstream authorization, the SR is triggered.

The foregoing process may also be described as: when there is a BSR that is triggered and not cancelled, it is determined whether there is an uplink grant configured as the second type. If there is an uplink grant configured as the second type and the uplink grant is in the active state, the SR is not triggered. The SR is triggered if there is an uplink grant configured as the second type and the uplink grant is in an inactive state. The SR is triggered if there is a configured uplink grant but the uplink grant is the first type of uplink grant. If there is no configured upstream authorization, the SR is triggered.

The foregoing process may also be described as: when there is a BSR that is triggered and not cancelled, it is determined whether there is an uplink grant configured as the first type. If there is an uplink grant configured as the first type, the SR is triggered. If there is no configured uplink grant, or if the uplink grant is configured as the second type and the second type of uplink grant is in the active state, the SR is not triggered. The SR is triggered if there is an uplink grant configured as the second type and the uplink grant of the second type is in an inactive state.

Alternatively, when there is a BSR that is triggered and not cancelled, it may further determine whether the MAC entity has available uplink resources, and thereby decide whether to trigger the SR. Here, the available uplink resources include the configuration resources described above, and may also include dynamically scheduled uplink resources. That is, in addition to determining whether there is a configuration resource available in the above manner, it is also necessary to determine whether there is a dynamic scheduling resource available in the current transmission unit (eg, slot/TTI/subframe). If there is a dynamic scheduling resource available, the SR is not triggered. If there is no available dynamic scheduling resource, it is further determined whether there is an available configuration uplink authorization. Preferably, the process may include: determining whether there is available uplink resources (including configured uplink grants or dynamically scheduled uplink grants) in the current transport unit MAC entity when there is a triggered and uncancelled BSR. If no uplink resources are available (ie, there is no configured uplink grant and there is no dynamically scheduled uplink grant), the SR is triggered. If there is a dynamically scheduled uplink grant, the SR is not triggered. If there is a configured uplink grant, you can determine whether you need to cancel the triggered BSR according to the method described above.

Alternatively, when there is a BSR that is triggered and not cancelled, it may further be determined whether the logical channel scheduling request timer is running, and thereby determining whether to trigger the SR. The logical channel scheduling request timer is a timer that is started when a scheduling request is sent. Therefore, new scheduling requests are not allowed to be sent during the running of this timer. That is, when there is a BSR that is triggered and not canceled, if the timer is still running, the scheduling request is not triggered.

Alternatively, an SR that is triggered in accordance with the manner described above is also proposed. In particular, the BSR that is triggered when the configured uplink grant is the first type does not need to cancel and further trigger the SR. Specifically, after the SR is triggered, if the HARQ feedback is received before or when the valid PUCCH resource for transmitting the SR has not arrived, the SR is cancelled. Preferably, the HARQ feedback is feedback for a specific MAC PDU, which may be the MAC PDU transmitted on the configured uplink grant, preferably the MAC PDU is transmitted on the uplink grant configured as the first type, and may also be It is a MAC PDU belonging to the logical channel corresponding to the BSR that triggers the SR. Further, the SR may be cancelled when the information fed back by the HARQ is ACK.

FIG. 2 is a block diagram showing user equipment 20 in accordance with one embodiment of the present disclosure. As shown in FIG. 2, the user equipment 20 includes a processor 210 and a memory 220. Processor 210 can include, for example, a microprocessor, a microcontroller, an embedded processor, and the like. The memory 220 may include, for example, a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a nonvolatile memory (such as a flash memory), or other memory. Program instructions are stored on the memory 220. The instructions, when executed by the processor 210, can perform the above-described methods (e.g., the method illustrated in Figure 1) performed by the user equipment as described in detail in this disclosure.

The program running on the device according to the present disclosure may be a program that causes a computer to implement the functions of the embodiments of the present disclosure by controlling a central processing unit (CPU). The program or information processed by the program may 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 system.

A program for realizing the functions of the embodiments of the present disclosure may be recorded on a computer readable recording medium. The corresponding functions can be realized by causing a computer system to read programs recorded on the recording medium and execute the programs. The so-called "computer system" herein may be a computer system embedded in the device, and may include an operating system or hardware (such as a peripheral device). The "computer readable recording medium" may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a recording medium of a short-term dynamic storage program, or any other recording medium readable by a computer.

The various features or functional blocks of the apparatus used in the above embodiments may be implemented or executed by circuitry (e.g., monolithic or multi-chip integrated circuits). Circuitry designed to perform the functions described in this specification can include general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, discrete Gate or transistor logic, discrete hardware components, or any combination of the two. A general purpose processor may be a microprocessor or any existing processor, controller, microcontroller, or state machine. The above circuit may be a digital circuit or an analog circuit. One or more embodiments of the present disclosure may also be implemented using these new integrated circuit technologies in the context of new integrated circuit technologies that replace existing integrated circuits due to advances in semiconductor technology.

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

As above, the embodiments of the present disclosure have been described in detail with reference to the accompanying drawings. However, the specific structure is not limited to the above embodiments, and the present disclosure also includes any design changes that do not deviate from the gist of the present disclosure. In addition, various modifications of the present disclosure are possible within the scope of the claims, and the embodiments obtained by appropriately combining the technical means disclosed in the different embodiments are also included in the technical scope of the present disclosure. Further, the components having the same effects described in the above embodiments may be substituted for each other.

Claims

A method performed by a user equipment, comprising:

Triggering a buffer status report BSR;

Determining whether the triggered BSR should be canceled based on the type and/or activation of the configured uplink grant;

When there is a BSR that is triggered and not cancelled, it is determined whether to trigger the scheduling request SR based on at least the type of the configured uplink grant and/or whether it is activated.
The method of claim 1, further comprising receiving information of a type of the uplink grant carrying the configuration, wherein the configured type of uplink grant comprises a first type of uplink grant and a second type of uplink grant, The first type of uplink grant and the second type of uplink grant include:

The first type of uplink grant is based on the uplink grant configured by the conflicting uplink resource, and the second type of uplink grant is based on the uplink grant configured by the non-conflicting uplink resource; or

The first type of uplink grant is based on the uplink grant configured by the unscheduled uplink resource, and the second type of uplink grant is based on the uplink grant configured by the semi-statically scheduled uplink resource; or

The first type of uplink grant is an uplink grant message configured based on the conflicting, unscheduled uplink resource; the second type of uplink grant is an uplink grant configured based on the non-conflicting, semi-statically scheduled uplink resource; or

The first type of uplink grant is based on the uplink grant configured by the non-conflicting, non-scheduled uplink resource; the second type of uplink grant is the uplink grant configured by the conflicting, semi-statically scheduled uplink resource.
The method of claim 1, wherein the triggered BSR should be cancelled based on whether there is an available uplink resource.
The method of claim 3 wherein the triggered BSR is cancelled when there is a dynamically scheduled uplink grant.
The method of claim 1, wherein determining whether to trigger the scheduling request SR is further based on whether there is an available uplink resource.
The method of claim 5, wherein the scheduling request SR is not triggered when there is a dynamically scheduled uplink grant.
The method of claim 1 wherein determining whether to trigger the scheduling request SR is further based on whether the logical channel scheduling request timer is running.
The method according to claim 1, wherein, after triggering the scheduling request SR, if hybrid automatic repeat request HARQ feedback is received before the physical uplink control channel PUCCH resource for transmitting the SR arrives, canceling Said SR.
The method of claim 1, wherein the buffer status report BSR is triggered when the same MAC PDU is transmitted on the configured uplink resource for a maximum number of times.
A user equipment comprising:

Processor;

a memory on which an instruction is stored;

Wherein the instructions, when executed by the processor, cause the user equipment to perform the method of any of claims 1-9.