WO2018201929A1 - Method and apparatus for processing scheduling requests - Google Patents

Abstract

Provided in the present disclosure is a method performed by a user equipment (UE), comprising triggering transmission of a buffer status report (BSR). The method further comprises: if there is no uplink resource for transmitting the BSR, the transmission of a corresponding scheduling request (SR) is triggered according to the type of the SR configured for the UE. The SR comprises at least an SR corresponding to a first numerology/transmission time interval type and an SR corresponding to a second numerology/transmission time interval type. Further provided in the present disclosure are the UE and a base station.

Description

Method and apparatus for processing scheduling requests Technical field

The present disclosure relates to the field of wireless communication technologies. More specifically, the present disclosure relates to methods and corresponding devices for processing scheduling requests.

Background technique

In March 2016, at the RAN#71 plenary session of the 3rd Generation Partnership Project (3GPP), a new research project on 5G technical standards was proposed (see Non-patent literature: RP-160671: New SID Proposal: Study on New Radio Access Technology), and approved. The goal of the research project is to develop a new wireless (New Radio: NR) access technology to meet all 5G application scenarios, requirements and deployment environments. NR mainly has three application scenarios: Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC) and Ultra reliable and low latency communications (URLLC).

In order to meet the low latency requirements of the URLLC, the "numerology/transmission time interval type" of the logical channel is determined in the Scheduling Request (SR) at the 3GPP RAN2 #97bis conference held in March 2017. At present, there are mainly two methods for distinguishing "numerology/transmission time interval type" in SR: (1) SR carries multi-bit information; (2) configures multiple SRs, and different SRs correspond to different "numerology/transmission time intervals" Types of".

Summary of the invention

However, the problems involved in triggering, transmitting, and canceling different SRs need to be addressed.

According to an aspect of the present disclosure, there is provided a method performed by a user equipment UE, comprising: triggering transmission of a buffer status report BSR; if there is no uplink resource for transmitting a BSR, requesting an SR according to a scheduling request configured for the UE Type to trigger the sending of the corresponding SR. The SR includes at least an SR corresponding to the first numerology/transmission time interval type and an SR corresponding to the second numerology/transmission time interval type.

In one embodiment, SRs corresponding to different numerology/transmission time interval types share a logical channel SR disable timer. Triggering the transmission of the corresponding SR includes: if the logical channel SR prohibits the timer from running, if the BSR is not triggered by the logical channel having the first condition, the data is transmittable and the BSR is satisfied The transmission of the SR corresponding to the first numerology/transmission time interval type is triggered when the logical channel of the two conditions is triggered by data transmission.

In one embodiment, SRs corresponding to different numerology/transmission time interval types have respective logical channel SR inhibit timers. Triggering the transmission of the corresponding SR includes: if the logical channel SR prohibiting timer corresponding to the first numerology/transmission time interval type is not running, if the BSR is not data transmitted by the logical channel satisfying the first condition, And triggering and the BSR is triggered by the fact that the logical channel satisfying the second condition has data transmittable, triggering the transmission of the SR corresponding to the first numerology/transmission time interval type.

In one embodiment, the method further comprises transmitting the corresponding SR according to the type of the SR. For example, the SR corresponding to the first numerology/transmission time interval type may be transmitted through a PUCCH corresponding to the first numerology/transmission time interval type and a PUCCH corresponding to the second numerology/transmission time interval type, and The PUCCH corresponding to the second numerology/transmission time interval type transmits an SR corresponding to the second numerology/transmission time interval type. Alternatively, the SR corresponding to the first numerology/transmission time interval type may be transmitted through the PUCCH corresponding to the first numerology/transmission time interval type, and the PUCCH corresponding to the first numerology/transmission time interval type The PU corresponding to the second numerology/transmission time interval type is transmitted with the PUCCH corresponding to the second numerology/transmission time interval type. Alternatively, the SR corresponding to the first numerology/transmission time interval type may be transmitted through the PUCCH corresponding to the first numerology/transmission time interval type, and the PUCCH corresponding to the second numerology/transmission time interval type To send an SR corresponding to the second numerology/transmission time interval type.

In one embodiment, the UE transmits to the base station an SR corresponding to the second numerology/transmission time interval type and BSR information corresponding to the first numerology/transmission time interval type, the BSR information including the latest cache status information. The method further includes canceling other SRs corresponding to the first numerology/transmission time interval type if the resource used to transmit the BSR information is a UE-specific resource.

In an embodiment, the method further includes: if the resource for transmitting the BSR information is not a UE-specific resource, receiving, from the base station, an uplink allocation message corresponding to a second numerology/transmission time interval type; and generating and The most recent BSR information corresponding to the numerology/transmission time interval type, and cancels other SRs corresponding to the first numerology/transmission time interval type.

In one embodiment, the UE transmits an SR corresponding to the first numerology/transmission time interval type to the base station. The method further includes: receiving, from the base station, an uplink assignment message corresponding to the first numerology/transmission time interval type; and transmitting, to the base station, BSR information corresponding to the first numerology/transmission time interval type, and canceling with the first numerology/ Other SRs corresponding to the transmission time interval type.

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(a) is a flow chart illustrating a method performed by a user equipment in accordance with one embodiment of the present disclosure.

FIG. 1(b) is a flow chart showing a method performed by a base station according to an embodiment of the present disclosure.

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

2(b) is a block diagram showing a base station according to an embodiment of the present disclosure.

3-4 illustrate a flow diagram of an SR triggering process in accordance with one embodiment of the present disclosure.

5-7 illustrate schematic flow diagrams of an SR transmission process in accordance with one embodiment of the present disclosure.

8-9 show schematic flow diagrams of an SR cancellation process in accordance with one embodiment of the present disclosure.

detailed description

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, detailed descriptions of well-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.

Some of the terms referred to in the present disclosure are described below, and the terms referred to in the present disclosure are defined herein unless otherwise specified. The terms or cells given in the present disclosure may adopt different naming methods in NR, LTE, and eLTE, but uniform terminology or cells are used in the present disclosure, and may be replaced by corresponding systems when applied to a specific system. The term or cell, the value of the cell is the value specified in the corresponding system.

RRC: Radio resource control.

PDCP: Packet Data Convergence Protocol. In the present disclosure, the PDCP may represent an NRPDCP entity or a PDCP entity of LTE or eLTE, unless otherwise specified.

RLC: Wireless Link Control. In the present disclosure, the RLC may represent an NR RLC entity or an RLC entity of LTE or eLTE, unless otherwise specified.

MAC: Media Access Control. In the present disclosure, the MAC may represent an NR MAC entity or a MAC entity of LTE or eLTE, unless otherwise specified.

PDU: Protocol data unit.

BSR: Cache status report. The information for providing the serving base station with the amount of data to be transmitted of the uplink buffer corresponding to the associated MAC entity, that is, the data to be transmitted in the PDCP and the RLC entity.

logicalChannelGroup: A logical channel group identifier used to map a logical channel to a logical channel group for BSR reporting.

periodicBSR-Timer: Timer used for BSR reporting. When the buffer status report process determines that at least one BSR is triggered and is not cancelled, if the MAC entity has an uplink resource for new transmission and the generated BSR is not a truncated BSR (Trancated BSR) in the current TTI, the periodicBSR-Timer is started or restarted. . When the timer expires, the regular BSR is triggered.

retxBSR-Timer: Timer for BSR reporting. When the buffer status reporting process determines that at least one BSR is triggered and is not cancelled, if the MAC entity has an uplink resource for new transmission at the current TTI, the retxBSR-Timer is started or restarted. The retxBSR-Timer is restarted when the MAC entity receives an allocation indication for a new data transmission of any UL-SCH. The regular BSR is triggered when the timer expires and any of the logical channels of any of the logical channel groups LCG of the MAC entity have transmittable data.

logicalChannelSR-ProhibitTimer: Logical channel SR disable timer, a timer configured for a logical channel, when the BSR is triggered by the logical channel configured with the logicalChannelSR-ProhibitTimer, the logicalChannelSR-ProhibitTimer is started or restarted. The logicalChannelSR-ProhibitTimer is stopped when the BSR is not triggered by the logical channel on which the logicalChannelSR-ProhibitTimer is configured and the logicalChannelSR-ProhibitTimer is currently running.

logicalChannelSR-Mask cell: When the uplink allocation is configured, it is used to control the SR channel triggering mechanism based on the logical channel.

sr-prohibitTimer: SR disable timer, a timer for the scheduling request SR transmitted on the PUCCH. The timer is started when the SR is transmitted; the SR cannot be transmitted during the operation of the timer.

SR_COUNTER: A variable used to count the number of SRs sent. The initial value is 0, which is incremented by 1 each time the SR is sent.

dsr-TransMax: Used to define the maximum number of SR transmissions, that is, the number of times the SR can be sent cannot exceed the value defined by dsr-TransMax minus 1.

Numerology: In this disclosure, it is called numerology, a sub-carrier spacing (SCS) and a cyclic prefix CP overhead definition.

TTI: Transmission time interval. The present disclosure refers to a TTI with a transmission time interval of 1 ms as a normal TTI, and a TTI with a transmission time interval of less than 1 ms as a short TTI. The TTIs corresponding to different transmission time intervals may also be named separately, corresponding to different types of TTIs.

Slot duration: The time slot duration, corresponding to different types of TTI and/or different numerology and/or different subcarrier space SCS. Different types of TTIs correspond to different time slots durations.

In the following embodiments, the UE is configured with two types of SRs (for example, an SR corresponding to a short TTI and an SR corresponding to a normal TTI) as an example. Those skilled in the art can understand that the above embodiments can be extended to scenarios in which the UE is configured with more types of SRs, for example, more different types of TTIs define more different types of SRs. Furthermore, the embodiments described herein may also be applied to scenarios in which all TTIs with TTI values less than the normal TTI are defined as short TTIs.

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

At step 110, the buffer status is triggered to report the transmission of the BSR. Specifically, in LTE Release 14, the BSR report can be controlled by configuring the timers periodicBSR-Timer, retxBSR-Timer, and logicalChannelSR-ProhibitTimer and by configuring a logicalChannelGroup for each logical channel. The logicalChannelGroup is used to assign a logical channel group LCG to the logical channel, where the logicalChannelGroup is an optional configuration parameter. In addition, in LTE Release 14, three BSRs are defined according to different events that trigger the BSR: a regular BSR, an inserted BSR, and a periodic BSR. For example, in an embodiment of the present disclosure, a regular BSR may be a BSR triggered by the following events:

(1) The uplink buffer of the UE is empty and new data arrives. When all the logical channels of all the LCGs have no transmittable uplink data, the RLC entity or the PDCP entity of any logical channel of any LCG has uplink data that can be sent, triggering the regular BSR reporting.

(2) High priority data arrives. When the RLC entity or the PDCP entity of any logical channel of any LCG has uplink data that can be transmitted and the priority of the logical channel is higher than any of the logical channels of any of the LCGs that have data transmittable, triggering the routine The BSR is reported.

(3) The retxBSR-Timer expires and any of the logical channels of any LCG can transmit data, triggering the regular BSR reporting.

(4) "Medical and/or transmission time interval type" (denoted as "numerology/TTI type" or numerology with any logical channel (and/or any logical channel of any LCG) that can transmit data /Transmission Time Interval Type) Different logical channels (and/or any logical channel of any LCG) have transmittable data that triggers regular BSR reporting.

(5) Logic with a smaller "numerology/TTI type" of any logical channel (and/or any logical channel of any LCG) that can transmit data (in other words, smaller TTI or larger SCS) The channel (and/or any logical channel of any LCG) has transmittable data that triggers regular BSR reporting.

(6) Logic having a larger "numerology/TTI type" of any logical channel (and/or any logical channel of any LCG) that can transmit data (in other words, a larger TTI or a smaller SCS) The channel (and/or any logical channel of any LCG) has transmittable data that triggers regular BSR reporting.

(7) Any logical channel and/or any logical channel of any LCG has data to transmit.

(8) A logical channel having a different QoS flow (higher priority and/or lower) than any current logical channel (and/or any logical channel of any LCG) that can transmit data (and / or any logical channel of any LCG) can send data, triggering regular BSR reporting.

(9) When the data exceeding the set threshold is not sent within the specified time, the regular BSR is reported.

Of course, in the present disclosure, the BSR may also be a BSR triggered by other events not listed in events (1)-(9). The present disclosure is also applicable to a scenario in which the BSRs triggered by the above events (1) to (9) are defined as different types of BSRs (for example, the different types of BSRs have different formats or correspond to different TTI types).

In step 120, if there is no uplink resource for transmitting the BSR, according to the characteristics of the data to be sent in the PDCP and/or the RLC or the event that triggers the BSR or the characteristic of the logical channel that has data to be transmitted or the logic that can be sent. The type of numerology/transmission time interval supported by the channel and the type of scheduling request SR configured for the UE trigger the transmission of the corresponding SR. In this embodiment, the SR includes at least an SR corresponding to the first numerology/transmission time interval type and an SR corresponding to the second numerology/transmission time interval type. In the following, the triggering of the SR is described in detail by several specific examples.

Example 1

In this example, SRs corresponding to different numerology/transmission time interval types share a logical channel SR disable timer logicalChannelSR-ProhibitTimer. In other words, if the timer logicalChannelSR-ProhibitTimer is running, then any type of SR cannot be sent.

FIG. 3 shows a flow chart of the SR triggering process in this example.

In step 30l, if at least one BSR is triggered and not cancelled, the MAC entity does not allocate an uplink resource for the new transmission for the current TTI. If the BSR is a regular BSR and the timer logicalChannelSR-ProhibitTimer is not running, then step 302 is performed.

In step 302, if an uplink grant (UL Grant) is not configured and the regular BSR is not triggered by the logical channel having the first condition, the data is transmittable and the regular BSR is data transmittable by the logical channel satisfying the second condition. If triggered, step 303 is performed. Otherwise, step 304 is performed. The first condition is that the upper layer establishes a logical channel SR mask for the logical channel, and the second condition is that the upper layer establishes an allowed TTI type for the logical channel and the short TTI is one of the allowed TTI types or is included in the allowed In the TTI type.

At step 303, an SR corresponding to the short TTI is triggered.

At step 304, if the uplink assignment is not configured or the regular BSR is not triggered by the logical channel having the first condition met, the step 305 is performed.

In step 305, the SR corresponding to the normal TTI is triggered.

It should be noted that, preferably, the uplink allocation in step 302 is an uplink allocation corresponding to any type of TTI. Optionally, the uplink allocation in step 302 is an uplink allocation corresponding to the short TTI.

Example 2

In this example, different types of SRs corresponding to different numerology/transmission time interval types have respective timers logicalChannelSR-ProhibitTimer. In other words, if the BSR is triggered because the logical channel supporting a certain type of TTI has data transmittable and the timer logicalChannelSR-ProhibitTimer associated with the SR corresponding to the type TTI is running, the SR of the corresponding type cannot be transmitted.

Figure 4 shows a flow diagram of the SR triggering process in this example.

In step 401, if at least one BSR is triggered and not cancelled, no uplink resource is allocated for the new transmission for the current TTI (which may be a normal TTI or a short TTI). If the BSR is a regular BSR, step 402 is performed.

At step 402, if the uplink assignment is not configured and the regular BSR is not triggered by the logical channel having the first condition that the data is transmittable and the regular BSR is triggered by the logical channel satisfying the second condition, the data is Go to step 403. Otherwise, step 404 is performed. The first condition is that the upper layer establishes a logical channel SR mask for the logical channel, and the second condition is that the upper layer establishes an allowed TTI type for the logical channel and the short TTI is one of the allowed TTI types or is included in the allowed In the TTI type.

At step 403, if the first timer logicalChannelSR-ProhibitTimer corresponding to the short TTI is not running, the SR corresponding to the short TTI is triggered.

At step 404, if the second timer logicalChannelSR-ProhibitTimer corresponding to the normal TTI is not running, step 405 is performed.

At step 405, if the uplink assignment is not configured or the regular BSR is not triggered by the logical channel having the first condition met, the step 406 is performed.

At step 406, the SR of the normal TTI is triggered.

It should be noted that the execution order of the determination conditions in the above steps 402 and 403 may be interchanged; the execution order of the determination conditions in the above steps 404 and 405 may be interchanged. Preferably, the uplink allocation in step 402 is an uplink allocation corresponding to any type of TTI. Optionally, the uplink allocation in step 402 is an uplink allocation corresponding to the short TTI.

Returning to Figure 1a, the method 10a optionally further includes a step 130. At step 130, the corresponding SR is transmitted according to the type of SR. In the following, the transmission of the SR is described in detail by several specific examples.

Example 1

In this example, the SR corresponding to the short TTI may be sent on the physical uplink control channel PUCCH (which may be denoted as sPUCCH) corresponding to the short TTI and the PUCCH corresponding to the normal TTI, and the SR corresponding to the normal TTI may be in the normal state. Transmitted on the PUCCH corresponding to the TTI.

FIG. 5 shows a schematic flow chart of the SR transmission process in this example.

In step 501, if any SR (SR corresponding to the normal TTI or SR corresponding to the short TTI) is to be transmitted, for each normal TTI or short TTI, if the current normal TTI or short TTI does not have the uplink shared channel UL-SCH The resource is available for transmission, and step 502 is performed.

In step 502, if the SR to be transmitted is an SR corresponding to the normal TTI and there is no valid PUCCH resource available for transmitting the SR in any normal TTI in which the SR is configured, step 503 is performed. Otherwise, step 504 is performed.

At step 503, a random access procedure is performed on a specified cell (e.g., SpCell) and all pending SRs corresponding to the normal TTI are cancelled. Optionally, all the to-be-sent SRs corresponding to the short TTI may be cancelled.

At step 504, if there are no valid PUCCH resources available for transmitting the SR within any TTI (normal TTI and/or short TTI) in which the SR is configured, then step 505 is performed. Otherwise, step 506 is performed.

At step 505, a random access procedure is performed on the specified cell (e.g., SpCell) and all pending SRs are cancelled.

At step 506, if the MAC entity has at least one valid PUCCH resource available for transmitting the SR corresponding to the short TTI within the current short TTI and the current short TTI is not part of the measurement interval or Sindlink discovery interval and the timer sr-prohibitTimer is not running (or the sr-prohibitTimer associated with the SR corresponding to the short TTI is not running), then step 507 is performed. Otherwise, step 510 is performed.

At step 507, if the first SR_COUNTER<dsr-TransMax corresponding to the short TTI, step 508 is performed. Otherwise, step 509 is performed.

In step 508, the first SR_COUNTER value is incremented by 1, indicating that the physical layer sends the SR corresponding to the short TTI on the valid PUCCH resource configured with the corresponding short TTI SR, starts the timer sr-ProhibitTimer, or starts the SR corresponding to the short TTI. The associated first timer sr-ProhibitTimer.

In step 509, if the first SR_COUNTER>=dsr-TransMax corresponding to the short TTI, the random access procedure may be performed on the specified cell (eg, SpCell) and all pending SRs corresponding to the short TTI may be cancelled. Optionally, all the to-be-sent SRs corresponding to the normal TTI may be cancelled. Optionally, the RRC may be notified to release the first PUCCH (PUCCH corresponding to the short TTI) of all serving cells.

At step 510, if the MAC entity has at least one valid PUCCH resource available for transmitting an SR (SR corresponding to a normal TTI and/or an SR corresponding to a short TTI) within the current normal TTI and the current normal TTI is not a measurement interval or If Sindlink finds a part of the interval and the timer sr-prohibitTimer is not running (or the sr-prohibitTimer associated with the SR corresponding to the normal TTI is not running), step 511 is performed.

In step 511, if the second SR_COUNTER<dsr-TransMax corresponding to the normal TTI, step 512 is performed. Otherwise, step 513 is performed.

In step 512, the second SR_COUNTER value is incremented by 1, indicating that the physical layer sends an SR on the configured valid PUCCH resource (corresponding to a normal TTI SR and/or a short TTI SR), the SR being an SR corresponding to a normal TTI or The SR corresponding to the short TTI starts the timer sr-ProhibitTimer or starts the second timer sr-ProhibitTimer associated with the SR corresponding to the normal TTI. Optionally, before the SR corresponding to the short TTI is sent, it is determined whether the valid PUCCH resource corresponding to the short TTI is configured, and if yes, the SR corresponding to the short TTI is not sent, and other operations in step 512 are not performed.

In step 513, if the second SR_COUNTER>=dsr-TransMax corresponding to the normal TTI, the random access procedure may be performed on the specified cell (eg, SpCell) and all the to-be-sent SRs corresponding to the normal TTI may be cancelled. Optionally, all the to-be-sent SRs corresponding to the short TTI may also be cancelled. Optionally, the RRC may be notified to release the second PUCCH (PUCCH corresponding to the normal TTI) of all serving cells.

It should be noted that steps 502 and 503 are optional. If steps 502 and 503 are not performed, if the condition of step 501 is satisfied, step 504 is performed.

Example 2

In this example, the SR corresponding to the normal TTI may be transmitted on the PUCCH corresponding to the normal TTI or the short TTI, and the SR corresponding to the short TTI may be transmitted on the PUCCH corresponding to the short TTI.

Fig. 6 shows a schematic flow chart of the SR transmission process in this example.

In step 601, if any SR (SR corresponding to the normal TTI or SR corresponding to the short TTI) is to be sent, for each normal TTI or short TTI, if the current normal TTI or short TTI has no UL-SCH resources available, If the transmission is performed, step 602 is performed.

In step 602, if the SR to be transmitted is an SR corresponding to the short TTI and there is no valid PUCCH resource available for transmitting the SR within any short TTI in which the SR is configured, step 603 is performed. Otherwise, step 604 is performed.

At step 603, a random access procedure is performed on a specified cell (e.g., SpCell) and all pending SRs corresponding to the short TTI are cancelled. Optionally, all the to-be-sent SRs corresponding to the normal TTI may be cancelled.

At step 604, if there is no valid PUCCH resource available for transmitting the SR within any TTI in which the SR is configured, then step 605 is performed. Otherwise, step 606 is performed.

At step 605, a random access procedure is performed on the specified cell (e.g., SpCell) and all pending SRs are cancelled.

At step 606, if there is at least one valid PUCCH resource available for transmitting an SR (SR corresponding to a normal TTI or an SR corresponding to a short TTI) within the current short TTI and the current short TTI is not a measurement interval or a Sindlink discovery interval If a part of the timer sr-prohibitTimer is not running (or the sr-prohibitTimer associated with the SR corresponding to the short TTI is not running), step 607 is performed. Otherwise, step 610 is performed.

At step 607, if the first SR_COUNTER<dsr-TransMax corresponding to the short TTI, step 608 is performed. Otherwise, step 609 is performed.

In step 608, the first SR_COUNTER value is incremented by 1, indicating that the physical layer sends an SR on the valid PUCCH resource corresponding to the short TTI configured with the SR, where the SR is an SR corresponding to the short TTI or an SR corresponding to the normal TTI. The timer sr-ProhibitTimer is started, or the first timer sr-ProhibitTimer associated with the SR corresponding to the short TTI is started. Optionally, before the SR corresponding to the normal TTI is sent, it is determined whether the valid PUCCH resource corresponding to the normal TTI is configured. If yes, the SR corresponding to the normal TTI is not sent and the other operations in step 608 are not performed.

In step 609, if the first SR_COUNTER>=dsr-TransMax corresponding to the short TTI, the random access procedure may be performed on the specified cell (eg, SpCell) and all the to-be-sent SRs corresponding to the short TTI may be cancelled. Optionally, all the to-be-sent SRs corresponding to the normal TTI may also be cancelled. Optionally, the RRC may be notified to release the first PUCCH (PUCCH corresponding to the short TTI) of all serving cells.

At step 610, if there is at least one valid PUCCH resource available for transmitting the SR corresponding to the normal TTI within the current normal TTI and the current normal TTI is not part of the measurement interval or Sindlink discovery interval and the timer sr-prohibitTimer is not running (or If the sr-prohibitTimer associated with the SR corresponding to the normal TTI is not running, step 611 is performed.

In step 611, if the second SR_COUNTER<dsr-TransMax corresponding to the normal TTI, step 612 is performed. Otherwise, step 613 is performed.

In step 612, the second SR_COUNTER value is incremented by 1, indicating that the physical layer sends the SR corresponding to the normal TTI on the valid PUCCH resource configured with the corresponding normal TTI SR, starts the timer sr-ProhibitTimer, or starts the corresponding TTI. The second timer associated with the SR is the sr-ProhibitTimer.

In step 613, if the second SR_COUNTER>=dsr-TransMax corresponding to the normal TTI, the random access procedure may be performed on the specified cell (eg, SpCell) and all the to-be-transmitted SRs corresponding to the normal TTI may be cancelled. Optionally, all the to-be-sent SRs corresponding to the short TTI may be cancelled. Optionally, the RRC may be notified to release the second PUCCH (PUCCH corresponding to the normal TTI) of all serving cells.

It should be noted that steps 602 and 603 are optional. If steps 602 and 603 are not performed, if the condition of step 601 is satisfied, step 604 is performed.

Example 3

In this example, the SR corresponding to the short TTI is transmitted on the PUCCH corresponding to the short TTI, and the SR corresponding to the normal TTI is transmitted on the PUCCH corresponding to the normal TTI. For example, if the SR corresponding to the short TTI is triggered at a certain time or the duration of the time slot, and the available PUCCH corresponding to the normal TTI is earlier than the effective PUCCH corresponding to the short TTI, the SR corresponding to the short TTI is not valid for the normal TTI. Transmitted on the PUCCH, but waits for a valid PUCCH corresponding to the short TTI.

Fig. 7 shows a schematic flow chart of the SR transmission process in this example.

In step 701, if any SR (SR corresponding to the normal TTI or SR corresponding to the short TTI) is to be sent, for each normal TTI or short TTI, if the current normal TTI or short TTI has no UL-SCH resources available, If the transmission is performed, step 702 is performed.

In step 702, if the SR to be transmitted is an SR corresponding to the short TTI, if there is no valid PUCCH resource available for transmitting the SR in any short TTI in which the SR is configured, step 703 is performed. Otherwise, step 704 is performed.

At step 703, a random access procedure is performed on a specified cell (e.g., SpCell) and all pending SRs corresponding to the short TTI are cancelled. Optionally, all the to-be-sent SRs corresponding to the normal TTI may be cancelled.

In step 704, if the SR to be transmitted is an SR corresponding to the normal TTI, if there is no valid PUCCH resource available for transmitting the SR in any normal TTI in which the SR is configured, step 705 is performed. Otherwise, step 706 is performed.

At step 705, a random access procedure is performed on a specified cell (e.g., SpCell) and all pending SRs corresponding to the normal TTI are cancelled. Optionally, all the to-be-sent SRs corresponding to the short TTI may be cancelled.

At step 706, if there is at least one valid PUCCH resource available for transmitting the SR corresponding to the short TTI within the current short TTI and the current short TTI is not part of the measurement interval or Sindlink discovery interval and the timer sr-prohibitTimer is not running (or If the sr-prohibitTimer associated with the SR corresponding to the short TTI is not running, step 707 is performed. Otherwise, step 710 is performed.

At step 707, if the first SR_COUNTER<dsr-TransMax corresponding to the short TTI, step 708 is performed. Otherwise, step 709 is performed.

In step 708, the first SR_COUNTER value is incremented by 1, indicating that the physical layer sends an SR corresponding to the short TTI on the valid PUCCH resource configured with the corresponding short TTI SR, starts the timer sr-ProhibitTimer, or starts corresponding to the short TTI. The first timer associated with the SR is the sr-ProhibitTimer.

In step 709, if the first SR_COUNTER>=dsr-TransMax corresponding to the short TTI, the random access procedure may be performed on the specified cell (eg, SpCell) and all the to-be-transmitted SRs corresponding to the short TTI may be cancelled. Optionally, all the to-be-sent SRs corresponding to the normal TTI may be cancelled. Optionally, the RRC may be notified to release the first PUCCH (PUCCH corresponding to the short TTI) of all serving cells.

At step 710, if there is at least one valid PUCCH resource available for transmitting the SR corresponding to the normal TTI within the current normal TTI and the current normal TTI is not part of the measurement interval or Sindlink discovery interval and the timer sr-prohibitTimer is not running (or If the sr-prohibitTimer associated with the SR corresponding to the normal TTI is not running, step 711 is performed.

At step 711, if the second SR_COUNTER<dsr-TransMax corresponding to the normal TTI, step 712 is performed. Otherwise, step 713 is performed.

In step 712, the value of the second SR_COUNTER is increased by 1, indicating that the physical layer sends the SR corresponding to the normal TTI on the valid PUCCH resource configured with the corresponding normal TTI SR, starts the timer sr-ProhibitTimer, or initiates association with the SR corresponding to the normal TTI. The second timer sr-ProhibitTimer.

In step 713, if the second SR_COUNTER>=dsr-TransMax corresponding to the normal TTI, the random access procedure may be performed on the specified cell (for example, the SpCell) and all the to-be-transmitted SRs corresponding to the normal TTI may be cancelled. Optionally, all the to-be-sent SRs corresponding to the short TTI may be cancelled. Optionally, the RRC may be notified to release the second PUCCH (PUCCH corresponding to the normal TTI) of all serving cells.

It should be noted that, alternatively, steps 702-705 may be replaced by: if there is no valid PUCCH resource available for transmitting the SR in any TTI configured with the SR, performing random access on a specified cell (eg, SpCell) Process and cancel all pending SRs. Otherwise, step 706 is performed.

Example 4

In this example, if the SR corresponding to the short TTI and the SR corresponding to the normal TTI are configured at the same time, the SR corresponding to the short TTI is sent on the previously valid PUCCH; for example, it is assumed that the duration is triggered at a certain time or time slot. The SR corresponding to the short TTI, and the available PUCCH corresponding to the normal TTI precedes the valid PUCCH corresponding to the short TTI, and the SR corresponding to the short TTI is sent on the valid PUCCH corresponding to the normal TTI. If the SR corresponding to the normal TTI is configured, the SR corresponding to the normal TTI is transmitted on the PUCCH corresponding to the normal TTI.

Returning to Figure 1a, the method 10a optionally further includes a step 140. At step 140, other SRs corresponding to a particular type are cancelled. In the following, the cancellation of the SR is described in detail by several specific examples.

Example 1

Figure 8 shows a schematic flow chart of the SR cancellation process in this example.

In step 801, the user equipment UE sends an SR to the base station, and sends, to the base station, the PDCP related to the logical channel and the buffer status indication information of the RLC entity to be transmitted corresponding to the "numerology/TTI type" associated with the SR. The cache status indication information may be represented by one MAC PDU and may be defined as a new BSR type. For example, the cache status indication information may include a cache status when a new type of BSR latest event is triggered.

The new type of BSR is related to the numerology/transmission time interval type, and may include only the buffer status associated with a certain type of TTI or the data to be transmitted of a logical channel supporting a certain type of TTI or the RLC corresponding to a logical channel supporting a certain type of TTI. And the data to be transmitted in the PDCP entity, for example, the data in the buffer area associated with the type 1 TTI (denoted as TTI1) or the data to be transmitted of the logical channel supporting TTI1 or the RLC and PDCP entities corresponding to the logical channel supporting TTI1. The data to be transmitted can only be sent on the uplink allocation with TTI TTI1 or the data in the buffer associated with TTI1 can only be sent on the uplink allocation with TTI not greater than TTI1.

If the uplink allocation for transmitting the buffer status indication information is based on a non-contention resource, that is, the resource is a user equipment specific resource, when the MAC layer generates the latest buffer status indication information associated with a certain numerology/TTI type , cancel all the SRs to be sent corresponding to the numerology/TTI type and stop the corresponding sr-ProhibitTimer. If the uplink allocation for sending the buffer status indication information is a contention-based resource, the buffer status indication information includes a UE identifier that can distinguish different UEs, for example, a C-RNTI.

In step 802, the user equipment UE receives an uplink allocation from the base station, and the uplink allocation is an uplink allocation corresponding to the numerology/TTI type associated with the SR. If the resource for sending the buffer status indication information in step 801 is contention-based, when the MAC layer generates the latest cache status indication information associated with the numerology/TTI type, all the to-be-corresponding to the numerology/TTI type may be cancelled. Send the SR and stop the corresponding sr-ProhibitTimer. If the uplink allocation is an uplink allocation corresponding to a normal TTI, step 803 is performed.

In step 803, the user equipment UE sends the buffer status indication information or the BSR to the base station. When the MAC layer generates the latest cache status indication information associated with the numerology/TTI type, all SRs corresponding to the numerology/TTI type are canceled and the corresponding sr-ProhibitTimer is stopped. If the BSR sent to the base station contains the buffer status when the latest event triggering the BSR occurs, all the pending SRs are canceled and all sr-ProhibitTimers are stopped.

Example 2

Figure 9 shows a schematic flow chart of the SR cancellation process in this example.

In step 901, the user equipment UE sends a first type of SR to the base station.

At step 902, the user equipment UE receives a first type of uplink assignment from the base station, the first type of uplink assignment may correspond to a "numerology/transmission time interval type" associated with the first type of SR.

In step 903, the user equipment UE sends the buffer status indication information to the base station. The cache status indication information may be represented by one MAC PDU and may be defined as a new BSR type. The cache status indication information includes a buffer status when a new event of the new type BSR is triggered. The new type of BSR is related to the numerology/transmission time interval type, which may only contain the buffer status associated with a certain type of TTI. For example, the data in the buffer associated with TTI1 can only be sent on the uplink allocation with TTI TTI1 or The data in the buffer associated with TTI1 can only be sent on the upstream allocation where the TTI is not greater than TTI1. When the MAC layer generates the latest cache status indication information associated with a certain numerology/transmission time interval type, all the to-be-sent SRs corresponding to the numerology/transmission time interval type are cancelled and the corresponding sr-ProhibitTimer is stopped.

FIG. 1(b) is a flow chart showing a method 10b performed by a base station in accordance with an embodiment of the present disclosure.

At step 150, a first type of SR is received from the user equipment UE.

At step 160, a first type of uplink assignment is transmitted to the user equipment UE, the first type of uplink assignment may correspond to a "numerology/transmission time interval type" associated with the first type of SR.

At step 170, the cache status indication information is received from the user equipment UE. The cache status indication information may be represented by one MAC PDU and may be defined as a new BSR type. The cache status indication information includes a buffer status when a new event of the new type BSR is triggered. A new type of BSR may be associated with a numerology/transmission time interval type, which may only contain the state of the buffer associated with a certain type of TTI.

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

Figure 2b is a block diagram showing a base station 20b in accordance with one embodiment of the present disclosure. As shown in Figure 2b, the base station 20b includes a processor 210b and a memory 220b. Processor 210b can include, for example, a microprocessor, a microcontroller, an embedded processor, and the like. The memory 220b 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 220b. The instructions, when executed by the processor 210b, can perform the above-described methods performed by the base station as described in detail in this disclosure.

The program running on the device according to the present invention may be a program that causes a computer to implement the functions of the embodiments of the present invention 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 invention can 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 above. 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 invention may also be implemented using these new integrated circuit technologies in the context of new integrated circuit technologies that have replaced existing integrated circuits due to advances in semiconductor technology.

Further, the present invention is not limited to the above embodiment. Although various examples of the embodiment have been described, the invention 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 invention 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 invention also includes any design modifications not departing from the gist of the present invention. In addition, various modifications may be made to the invention 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 invention. Further, the components having the same effects described in the above embodiments may be substituted for each other.

Claims (10)

A method performed by a user equipment UE, comprising: Triggering the buffer status report to send the BSR; If there is no uplink resource for sending the BSR, triggering the sending of the corresponding SR according to the type of the scheduling request SR configured for the UE; The SR includes at least an SR corresponding to the first numerology/transmission time interval type and an SR corresponding to the second numerology/transmission time interval type. The method of claim 1 wherein the SRs corresponding to different numerology/transmission time interval types share a logical channel SR disable timer; The triggering the sending of the corresponding SR includes: if the logical channel SR prohibits the timer from running, if the BSR is not triggered by the logical channel that satisfies the first condition, and the BSR is triggered by The logical channel satisfying the second condition has data transmitable and triggered, and triggers transmission of the SR corresponding to the first numerology/transmission time interval type. The method of claim 1 wherein the SRs corresponding to different numerology/transmission time interval types have respective logical channel SR inhibit timers; The triggering the sending of the corresponding SR includes: if the logical channel SR prohibiting timer corresponding to the first numerology/transmission time interval type is not running, if the BSR is not data by the logical channel satisfying the first condition The transmission may be triggered and the BSR is triggered by the logical channel satisfying the second condition that the data is transmittable, triggering the transmission of the SR corresponding to the first numerology/transmission time interval type. The method of claim 1, further comprising transmitting the corresponding SR according to the type of the SR. The method of claim 4, wherein transmitting the corresponding SR according to the type of the SR comprises: a PUCCH corresponding to the first numerology/transmission time interval type and a PUCCH corresponding to the second numerology/transmission time interval type The SR corresponding to the first numerology/transmission time interval type is transmitted, and the SR corresponding to the second numerology/transmission time interval type is transmitted through the PUCCH corresponding to the second numerology/transmission time interval type. The method of claim 4, wherein transmitting the corresponding SR according to the type of the SR comprises: transmitting, by the PUCCH corresponding to the first numerology/transmission time interval type, corresponding to the first numerology/transmission time interval type SR, and transmitting an SR corresponding to the second numerology/transmission time interval type by a PUCCH corresponding to the first numerology/transmission time interval type and a PUCCH corresponding to the second numerology/transmission time interval type. The method of claim 4, wherein transmitting the corresponding SR according to the type of the SR comprises: transmitting, by the PUCCH corresponding to the first numerology/transmission time interval type, corresponding to the first numerology/transmission time interval type SR, and transmitting an SR corresponding to the second numerology/transmission time interval type by a PUCCH corresponding to the second numerology/transmission time interval type. The method according to claim 4, wherein said UE transmits to said base station an SR corresponding to a second numerology/transmission time interval type and BSR information corresponding to a first numerology/transmission time interval type, said BSR information The latest cache status information is included; and the method further includes canceling other SRs corresponding to the first numerology/transmission time interval type if the resource used to transmit the BSR information is a UE-specific resource. The method of claim 8 wherein the method further comprises: If the resource for transmitting the BSR information is not a UE-specific resource, receiving, from the base station, an uplink allocation message corresponding to the second numerology/transmission time interval type; The latest BSR information corresponding to the first numerology/transmission time interval type is generated, and other SRs corresponding to the first numerology/transmission time interval type are canceled. The method of claim 4, wherein the UE transmits an SR corresponding to a first numerology/transmission time interval type to a base station; and the method further comprises: Receiving, from the base station, an uplink assignment message corresponding to the first numerology/transmission time interval type; The BSR information corresponding to the first numerology/transmission time interval type is transmitted to the base station, and other SRs corresponding to the first numerology/transmission time interval type are canceled.

Images