CN108810925A - Method and apparatus for handling scheduling request - Google Patents
Method and apparatus for handling scheduling request Download PDFInfo
- Publication number
- CN108810925A CN108810925A CN201710310255.1A CN201710310255A CN108810925A CN 108810925 A CN108810925 A CN 108810925A CN 201710310255 A CN201710310255 A CN 201710310255A CN 108810925 A CN108810925 A CN 108810925A
- Authority
- CN
- China
- Prior art keywords
- fate
- time interval
- transmission time
- type
- interval type
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/02—Arrangements for optimising operational condition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/12—Wireless traffic scheduling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
- H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Present disclose provides a kind of methods executed by user equipment (UE), include the transmission of triggering buffer status report BSR.This method further includes：If there is no the ascending resource for sending BSR, then the transmission of corresponding SR is triggered according to the type of the scheduling request SR configured for UE.The SR includes at least SR corresponding with the first fate/Transmission Time Interval type and SR corresponding with the second fate/Transmission Time Interval type.The disclosure additionally provides a kind of user equipment and base station.
Description
Technical field
This disclosure relates to wireless communication technology field.More specifically, this disclosure relates to the method for being used to handle scheduling request
With corresponding equipment.
Background technology
In March, 2016, in third generation partner program (3GPP) RAN#71 plenary session, it is proposed that one about 5G skills
The new research project of art standard is (referring to non-patent literature：RP-160671：New SID Proposal：Study on New
Radio Access Technology), and it is granted.The purpose of the research project is to develop a new wireless (New
Radio：NR) access technology is to meet all application scenarios, demand and the deployed environment of 5G.Mainly there are three application scenarios by NR：
Mobile broadband communication (the Enhanced mobile broadband of enhancing：EMBB), large-scale machines class communicates (massive
Machine type communication：MMTC) and super reliable low latency communicates (Ultra reliable and low
latency communications：URLLC).
To meet requirements of the URLLC to low latency, reached in the RAN2#97bis meeting of 3GPP that in March, 2017 holds
At " fate/Transmission Time Interval type " for distinguishing logic channel in scheduling request (Scheduling Request, SR).Mesh
It is preceding that there are mainly two types of the methods that " fate/Transmission Time Interval type " is distinguished in SR：(1) more bit informations are carried in SR；(2)
Multiple SR are configured, different SR is corresponded to different " fate/Transmission Time Interval type ".
Invention content
However, the problem that the triggering of difference SR urgently to be resolved hurrily, transmission and cancellation are involved.
According to one aspect of the disclosure, a kind of method executed by user equipment (UE) is provided, including：Triggering caching shape
State reports the transmission of BSR；If there is no the ascending resource for sending BSR, then according to the scheduling request SR for being UE configurations
Type triggers the transmission of corresponding SR.The SR include at least SR corresponding with the first fate/Transmission Time Interval type with
And SR corresponding with the second fate/Transmission Time Interval type.
In one embodiment, believe from the shared logic of different fates/corresponding SR of Transmission Time Interval type
Road SR forbids timer.The transmission for triggering corresponding SR includes：The case where the logic channel SR forbids timer not running
Under, if the BSR is not to have data transmittable and trigger and the BSR is by full by the logic channel for meeting first condition
The logic channel of sufficient second condition has data to can be transmitted and trigger, then triggers opposite with the first fate/Transmission Time Interval type
The transmission of the SR answered.
In one embodiment, there is respective logic from different fates/corresponding SR of Transmission Time Interval type
Channel SR forbids timer.The transmission for triggering corresponding SR includes：Corresponding with the first fate/Transmission Time Interval type
In the case that logic channel SR forbids timer not running, if the BSR is had by the logic channel for meeting first condition
Data are transmittable and trigger and the BSR is has data transmittable and trigger by the logic channel for meeting second condition, then touch
The transmission of hair SR corresponding with the first fate/Transmission Time Interval type.
In one embodiment, this method further includes that corresponding SR is sent according to the type of SR.For example, can by with
First fate/corresponding PUCCH of Transmission Time Interval type and corresponding with the second fate/Transmission Time Interval type
PUCCH sends SR corresponding with the first fate/Transmission Time Interval type, and by with the second fate/transmission time
The corresponding PUCCH of interval type sends SR corresponding with the second fate/Transmission Time Interval type.It is alternatively possible to
It is sent and the first fate/Transmission Time Interval type by PUCCH corresponding with the first fate/Transmission Time Interval type
Corresponding SR, and by PUCCH corresponding with the first fate/Transmission Time Interval type and with the second fate/transmission
The corresponding PUCCH of time interval type sends SR corresponding with the second fate/Transmission Time Interval type.Alternatively,
It can be sent and the first fate/Transmission Time Interval by PUCCH corresponding with the first fate/Transmission Time Interval type
The corresponding SR of type, and sent and the second life by PUCCH corresponding with the second fate/Transmission Time Interval type
Reason/corresponding the SR of Transmission Time Interval type.
In one embodiment, UE to base station send SR corresponding with the second fate/Transmission Time Interval type and
BSR information corresponding with the first fate/Transmission Time Interval type, the BSR information include newest buffer status information.
This method further includes：If being UE private resources for sending the resource of the BSR information, cancel and the first fate/transmission
The corresponding other SR of time interval type.
In one embodiment, this method further includes：If not being the special moneys of UE for sending the resource of the BSR information
Source then receives uplink assignment message corresponding with the second fate/Transmission Time Interval type from base station；And it generates and first
The corresponding newest BSR information of fate/Transmission Time Interval type, and cancel and the first fate/Transmission Time Interval class
The corresponding other SR of type.
In one embodiment, UE sends SR corresponding with the first fate/Transmission Time Interval type to base station.The party
Method further includes：Uplink assignment message corresponding with the first fate/Transmission Time Interval type is received from base station；And to base station
BSR information corresponding with the first fate/Transmission Time Interval type is sent, and is cancelled between the first fate/transmission time
Every the corresponding other SR of type.
Description of the drawings
By the detailed description below in conjunction with attached drawing, above and other feature of the disclosure will become more apparent,
In：
Fig. 1 (a) is the flow chart for showing the method executed by user equipment according to an embodiment of the present disclosure.
Fig. 1 (b) is the flow chart for showing the method executed by base station according to an embodiment of the present disclosure.
Fig. 2 (a) is the block diagram for showing the user equipment according to an embodiment of the present disclosure.
Fig. 2 (b) is the block diagram for showing the base station according to an embodiment of the present disclosure.
Fig. 3-4 shows the flow diagram of the SR trigger process according to an embodiment of the present disclosure.
Fig. 5-7 shows the schematic flow diagram of the SR transmission process according to an embodiment of the present disclosure.
Fig. 8-9 shows the schematic flow diagram for cancelling process according to the SR of an embodiment of the present disclosure.
Specific implementation mode
The disclosure is described in detail with reference to the accompanying drawings and detailed description.It should be noted that the disclosure does not answer office
It is limited to specific implementation mode described below.In addition, for simplicity pair public affairs not being directly linked with the disclosure are omitted
The detailed description for knowing technology, to prevent understanding of this disclosure from causing to obscure.
Be described below this disclosure relates to part term, if not otherwise specified, this disclosure relates to term use it is fixed herein
Justice.The term or cell that the disclosure provides may use different naming methods in NR, LTE and eLTE, but be adopted in the disclosure
The term or cell used in corresponding system is could alternatively be when being applied to specific system with unified term or cell,
The value of cell is using value specified in correspondence system.
RRC：Wireless heterogeneous networks.
PDCP：Packet Data Convergence Protocol.In the disclosure, if not otherwise specified, PDCP can indicate NRPDCP entities
Or the PDCP entities of LTE or eLTE.
RLC：Radio link controls.In the disclosure, if not otherwise specified, RLC can indicate NR RLC entities or LTE or
The RLC entities of eLTE.
MAC：Media access control.In the disclosure, if not otherwise specified, MAC can indicate NR MAC entities or LTE or
The MAC entity of eLTE.
PDU：Protocol Data Unit.
BSR：Buffer status report.It is waited for for providing the associated corresponding upper row buffer of MAC entity to serving BS
The information of transmitted data amount, i.e. data to be sent in PDCP and RLC entities.
LogicalChannelGroup cells：Logic channel group identification is used for mapping logical channels to for BSR
The logic channel group of report.
periodicBSR-Timer：Timer for BSR reports.When buffer status report process determines at least one
A BSR is triggered and is not cancelled, if in current TTI, MAC entity have ascending resource carry out newly transmit and generate BSR not
It is to block BSR (Trancated BSR) entirely, then starts or restart periodicBSR-Timer.When the timer expires,
Trigger routine BSR.
retxBSR-Timer：Timer for BSR reports.When buffer status report process determines at least one BSR
It is triggered and is not cancelled, if in current TTI, MAC entity has ascending resource newly to be transmitted, then starts or restart
retxBSR-Timer.When MAC entity receives the distribution instruction for new data transmission of arbitrary UL-SCH, restart
retxBSR-Timer.When the timer expire and any logic channel of any logic channel group LCG of MAC entity have can
When transmission data, routine BSR is triggered.
logicalChannelSR-ProhibitTimer：Logic channel SR forbids timer, matches for some logic channel
The timer set, when BSR is that had and can be sent out by the logic channel for being configured with the logicalChannelSR-ProhibitTimer
Data-triggered is sent, then starts or restart logicalChannelSR-ProhibitTimer.When BSR is not described by being configured with
The logic channel of logicalChannelSR-ProhibitTimer have transmittable data-triggered and it is current have be currently running
LogicalChannelSR-ProhibitTimer then stops logicalChannelSR-ProhibitTimer.
LogicalChannelSR-Mask cells：When being configured with uplink assignment, the SR for controlling logic-based channel is touched
Hair mechanism.
sr-prohibitTimer：SR forbids timer, the timer of the scheduling request SR for being transmitted on PUCCH.
When sending SR, start the timer；During the timer is run, SR cannot be sent.
SR_COUNTER：Variable for counting the SR numbers sent, initial value 0 send SR and all increase by 1 every time.
dsr-TransMax：Maximum times for defining SR transmission, i.e. the transmittable number of SR is no more than dsr-
The value that TransMax is defined subtracts 1.
Numerology：In the disclosure be known as fate, a fate by sub-carrier space (sub-carrier spacing,
SCS it) is defined with cyclic prefix CP overhead.
TTI：Transmission Time Interval.The TTI that Transmission Time Interval is 1ms is known as normal TTI by the disclosure, between transmission time
Every being known as short TTI less than the TTI of 1ms；The TTI of the different Transmission Time Intervals of correspondence can also be named respectively, corresponding inhomogeneity
The TTI of type.
Slot duration：Time slot duration, corresponding different types of TTI and/or different fates and/or different
Sub-carrier space SCS.Different types of TTI corresponds to different time slot durations.
In following examples, two kinds of SR is configured with (such as corresponding to the SR of short TTI and corresponding to just with UE
The SR of normal TTI) for be described.It is configured with more it will be understood by those skilled in the art that above-described embodiment can expand to UE
The scene of a plurality of types of SR, such as more different types of more different types of SR of TTI definition.In addition, described herein
Embodiment can also be applied to the scene that the TTI by all TTI values less than normal TTI is defined as short TTI.
Fig. 1 a are the flow charts for showing the method 10a executed by user equipment according to an embodiment of the present disclosure.
In step 110, the transmission of triggering buffer status report BSR.Specifically, in LTE versions 14, it can pass through and configure
Timer periodicBSR-Timer, retxBSR-Timer and logicalChannelSR-ProhibitTimer and pass through
LogicalChannelGroup is configured for each logic channel to control BSR reports.LogicalChannelGroup is for being
Logical channel assignment logic channel group LCG, wherein logicalChannelGroup are optional configuration parameters.In addition, in LTE
In version 14, according to the different event of triggering BSR, three kinds of BSR are defined：Conventional BSR, it is inserted into BSR and period BSR.For example,
In embodiment of the disclosure, conventional BSR can be the BSR triggered by following event：
(1) the uplink buffer area of UE is empty and has new data arrival.When all logic channels of all LCG all can not sent out
When the upstream data sent, the RLC entities or PDCP entities of any logic channel of any LCG have upstream data transmittable, trigger
Conventional BSR is reported.
(2) high-priority data reaches.When the RLC entities or PDCP entities of any logic channel of any LCG have uplink
Data are transmittable and any logic channel for having had a transmittable data of any LCG of priority ratio of the logic channel it is excellent
First grade is high, and triggering routine BSR is reported.
(3) retxBSR-Timer expires and any logic channel of any LCG has transmittable data, triggers on routine BSR
Report.
(4) have and current any logic channel (and/or any logic channel of any LCG) for there are a transmittable data
" fate and/or Transmission Time Interval type " (is denoted as " numerology/TTI types " or fate/Transmission Time Interval type)
Different logic channels (and/or any logic channel of any LCG) has transmittable data, triggering routine BSR to report.
(5) have and current any logic channel (and/or any logic channel of any LCG) for there are a transmittable data
" numerology/TTI types " smaller (in other words, TTI smallers or SCS biggers) logic channel (and/or any LCG appoint
One logic channel) there are transmittable data, triggering routine BSR to report.
(6) have and current any logic channel (and/or any logic channel of any LCG) for there are a transmittable data
" numerology/TTI types " bigger (in other words, TTI biggers or SCS smallers) logic channel (and/or any LCG appoint
One logic channel) there are transmittable data, triggering routine BSR to report.
(7) any logic channel of any logic channel and/or any LCG have data transmittable.
(8) have and current any logic channel (and/or any logic channel of any LCG) for there are a transmittable data
Logic channel (and/or any logic letter of any LCG of QoS flow (QoS flow) different (priority higher and/or lower)
Road) there are transmittable data, triggering routine BSR to report.
(9) when the data more than given threshold are not sent before the deadline, triggering routine BSR is reported.
Certainly, in the disclosure, BSR can also be to be triggered by other events that do not listed in event (1)~(9)
BSR.The disclosure can also be applied to by the BSR that above-mentioned event (1)~(9) are triggered be defined as different types of BSR (for example,
The different types of BSR has different format or corresponding different TTI types) scene.
In step 120, if there is no the ascending resource for sending BSR, then according to be sent in PDCP and/or RLC
The characteristics of data, triggers the event of BSR or has the characteristics of data transmissible logic channel or have the transmissible logic letter of data
The fate that road is supported/Transmission Time Interval type and trigger corresponding SR's for the type of the UE scheduling request SR configured
It sends.In this embodiment, which includes at least SR corresponding with the first fate/Transmission Time Interval type and with second
Fate/corresponding the SR of Transmission Time Interval type.In the following, the triggering of SR is described in detail by several specific examples.
Example 1
In this example, prohibit from the shared logic channel SR of different fates/corresponding SR of Transmission Time Interval type
Only timer logicalChannelSR-ProhibitTimer.In other words, if the timer
LogicalChannelSR-ProhibitTimer is currently running, then any type of SR cannot be sent.
Fig. 3 shows the flow diagram of the SR trigger process in this example.
In step 301, if at least one BSR is triggered and is not cancelled, for current TTI, MAC entity does not have to be new
Transmission distribution ascending resource.If BSR is a routine BSR and timer logicalChannelSR-ProhibitTimer
Not running thens follow the steps 302.
In step 302, if it is not by meeting first to distribute (UL Grant) and the routine BSR without collocating uplink
The logic channel of part has data transmittable and trigger and the routine BSR has data can by the logic channel for meeting second condition
It sends and triggers, then follow the steps 303.Otherwise, step 304 is executed.Wherein, it is that the logic channel is built that first condition, which is upper layer,
Logic channel SR masking is stood, second condition is that upper layer is that establish the TTI types of permission and short TTI be fair to the logic channel
Perhaps one of TTI types or included in the TTI types of permission.
In step 303, SR corresponding with short TTI is triggered.
In step 304, if the distribution of no collocating uplink or the routine BSR are not by meeting patrolling for the above first condition
Collecting channel has data to can be transmitted and trigger, and thens follow the steps 305.
In step 305, the corresponding SR of normal TTI are triggered.
It should be noted that preferably, uplink assignment described in step 302 is the corresponding uplink assignments of any type TTI.It is standby
Choosing, uplink assignment described in step 302 is the corresponding uplink assignments of short TTI.
Example 2
In this example, different types of SR corresponding from different fates/Transmission Time Interval type has respective
Timer logicalChannelSR-ProhibitTimer.In other words, if because of the logic channel for supporting some type of TTI
There are data transmittable and triggers BSR and SR associated timer logicalChannelSR- corresponding with the type TTI
ProhibitTimer is currently running, then the SR of corresponding types cannot be sent.
Fig. 4 shows the flow diagram of the SR trigger process in this example.
(can be normal for current TTI if at least one BSR is triggered and is not cancelled in step 401
TTI or short TTI) without distributing ascending resource for new transmission.If the BSR is a routine BSR, 402 are thened follow the steps.
In step 402, if no collocating uplink distributes and the routine BSR is believed by meeting the logic of first condition
Road has data transmittable and trigger and the routine BSR is had data can be transmitted by the logic channel for meeting second condition and touched
Hair, thens follow the steps 403.Otherwise, step 404 is executed.Wherein, it is that the logic channel establishes logic that first condition, which is upper layer,
Channel SR maskings, second condition are that upper layer is that the logic channel establishes the TTI types of permission and short TTI is allowed TTI
One of type or included in the TTI types of permission.
In step 403, if first timer logicalChannelSR-ProhibitTimer corresponding with short TTI
Not running then triggers SR corresponding with short TTI.
In step 404, if second timer logicalChannelSR- corresponding with normal TTI
ProhibitTimer not running, thens follow the steps 405.
In step 405, if the distribution of no collocating uplink or the routine BSR are not by meeting patrolling for the above first condition
Collecting channel has data to can be transmitted and trigger, and thens follow the steps 406.
In step 406, the SR of normal TTI is triggered.
It should be noted that the execution sequence of Rule of judgment can be interchanged in above-mentioned steps 402 and 403；Above-mentioned steps 404
With 405 in Rule of judgment execution sequence can be interchanged.Preferably, uplink assignment described in step 402 is that any type TTI is corresponded to
Uplink assignment.Alternative, uplink assignment described in step 402 is the corresponding uplink assignments of short TTI.
Fig. 1 a are returned to, this method 10a further includes optionally step 130.In step 130, phase is sent according to the type of SR
The SR answered.In the following, the transmission of SR is described in detail by several specific examples.
Example 1
In this example, and the corresponding SR of short TTI can (can in Physical Uplink Control Channel PUCCH corresponding with short TTI
Be denoted as sPUCCH) and PUCCH corresponding with normal TTI on send, and SR corresponding with normal TTI can with normal TTI pairs
It is sent on the PUCCH answered.
Fig. 5 shows the schematic flow diagram of the SR transmission process in this example.
In step 501, if there is any SR (and normal TTI corresponding SR or corresponding with short TTI SR) is to be sent, for
Each normal TTI or short TTI, if current normal TTI or short TTI do not have Uplink Shared Channel UL-SCH resources to can be used for passing
It is defeated, then follow the steps 502.
In step 502, if SR to be sent is SR corresponding with normal TTI and in the arbitrary normal TTI for being configured with SR
The effective PUCCH resource that not can be used for sending SR, thens follow the steps 503.Otherwise, step 504 is executed.
In step 503, random access procedure is executed in defined cell (such as SpCell) and is cancelled and normal TTI pairs
All SR to be sent answered.Optionally, all to be sent SR corresponding with short TTI can be cancelled.
In step 504, if not can be used for sending in the arbitrary TTI (normal TTI and/or short TTI) for being configured with SR
Effective PUCCH resource of SR, thens follow the steps 505.Otherwise, step 506 is executed.
In step 505, random access procedure is executed in defined cell (such as SpCell) and is cancelled all to be sent
SR。
In step 506, if MAC entity has in current short TTI and at least one can be used for sending the corresponding SR's of short TTI
Effective PUCCH resource and the current short TTI are not the part and timer sr- that measurement interval or Sindlink have found interval
ProhibitTimer not running (or the associated sr-prohibitTimer not running of the corresponding SR of short TTI), thens follow the steps
507.Otherwise, step 510 is executed.
In step 507, if first SR_COUNTER < dsr-TransMax corresponding with short TTI, thens follow the steps
508.Otherwise, step 509 is executed.
In step 508, the first SR_COUNTER values increase by 1, and instruction physical layer is configured with corresponding short TTI SR's described
SR corresponding with short TTI is sent in effective PUCCH resource, starts timer sr-ProhibitTimer, or is started and TTI pairs short
Answer the associated first timer sr-ProhibitTimer of SR.
In step 509, if first SR_COUNTER >=dsr-TransMax corresponding with short TTI, can provide
Cell (such as SpCell) on execute random access procedure and cancel all to be sent SRs corresponding with short TTI.Optionally, may be used
To cancel all to be sent SRs corresponding with normal TTI.Optionally, RRC can be notified to discharge the first of all serving cells
PUCCH (PUCCH corresponding with short TTI).
In step 510, if MAC entity has at least one transmission SR that can be used for (with normal TTI in current normal TTI
Corresponding SR and/or SR corresponding with short TTI) effective PUCCH resource and the current normal TTI be not measurement interval or
Sindlink find interval a part and timer sr-prohibitTimer not running (or SR corresponding with normal TTI close
The sr-prohibitTimer not running of connection), then follow the steps 511.
In step 511, if twoth SR_COUNTER < dsr-TransMax corresponding with normal TTI, thens follow the steps
512.Otherwise, step 513 is executed.
In step 512, the 2nd SR_COUNTER values increase by 1, and instruction physical layer is configured with effective PUCCH resource described
Send SR on (correspond to normal TTI SR and/or short TTI SR), the SR be SR corresponding with normal TTI or with it is TTI pairs short
The SR answered starts timer sr-ProhibitTimer, or starts the associated second timers of SR corresponding with normal TTI
sr-ProhibitTimer.Optionally, first judge whether to configure short TTI before sending the corresponding SR of short TTI corresponding effectively
PUCCH resource, if it is, not sending the corresponding SR of short TTI and not executing other operations in step 512.
In step 513, if twoth SR_COUNTER >=dsr-TransMax corresponding with normal TTI, can advise
Random access procedure is executed in fixed cell (such as SpCell) and cancels all to be sent SRs corresponding with normal TTI.It is optional
, all to be sent SR corresponding with short TTI can also be cancelled.Optionally, RRC can be notified to discharge the of all serving cells
Two PUCCH (PUCCH corresponding with normal TTI).
It should be noted that step 502 and 503 is optional, if not executing step 502 and 503, if meeting step
Rapid 501 condition executes step 504.
Example 2
In this example, it can be sent on PUCCH corresponding with normal TTI or short TTI with the corresponding SR of normal TTI,
And it can be sent on PUCCH corresponding with short TTI with the corresponding SR of short TTI.
Fig. 6 shows the schematic flow diagram of the SR transmission process in this example.
In step 601, if there is any SR (and normal TTI corresponding SR or corresponding with short TTI SR) is to be sent, to every
A normal TTI or short TTI are thened follow the steps if current normal TTI or short TTI do not have UL-SCH resources to can be used for transmitting
602。
In step 602, if SR to be sent is SR corresponding with short TTI and does not have in the arbitrary short TTI for being configured with SR
The effective PUCCH resource that can be used for sending SR, thens follow the steps 603.Otherwise, step 604 is executed.
In step 603, random access procedure is executed in defined cell (such as SpCell) and is cancelled corresponding with short TTI
All SR to be sent.Optionally, all to be sent SR corresponding with normal TTI can be cancelled.
In step 604, if not can be used for sending effective PUCCH resource of SR in the arbitrary TTI for being configured with SR,
Execute step 605.Otherwise, step 606 is executed.
In step 605, random access procedure is executed in defined cell (such as SpCell) and is cancelled all to be sent
SR。
In step 606, if having in current short TTI it is at least one can be used for sending SR (SR corresponding with normal TTI or
SR corresponding with short TTI) effective PUCCH resource and the current short TTI be not that measurement interval or Sindlink have found interval
A part and timer sr-prohibitTimer not running (or SR associated sr- corresponding with short TTI
ProhibitTimer not running), then follow the steps 607.Otherwise, step 610 is executed.
In step 607, if first SR_COUNTER < dsr-TransMax corresponding with short TTI, step 608 is executed.
Otherwise, step 609 is executed.
In step 608, the first SR_COUNTER values increase by 1, and instruction physical layer is corresponding in the short TTI for being configured with SR
Send SR in effective PUCCH resource, the SR is and corresponding SR or corresponding with the normal TTI SR of short TTI to start timer
Sr-ProhibitTimer, or start SR associated first timer sr-ProhibitTimer corresponding with short TTI.Optionally,
First judge whether to configure the corresponding effective PUCCH resources of normal TTI before sending the corresponding SR of normal TTI, if it is, not
It sends the corresponding SR of normal TTI and does not execute other operations in step 608.
In step 609, if first SR_COUNTER >=dsr-TransMax corresponding with short TTI, can provide
Cell (such as SpCell) on execute random access procedure and cancel all to be sent SRs corresponding with short TTI.Optionally, also
All to be sent SR corresponding with normal TTI can be cancelled.Optionally, RRC can be notified to discharge the first of all serving cells
PUCCH (PUCCH corresponding with short TTI).
In step 610, at least one it can be used for sending having for the corresponding SR of normal TTI if had in current normal TTI
Effect PUCCH resource and the current normal TTI are not the part and timer sr- that measurement interval or Sindlink have found interval
ProhibitTimer not running (or the associated sr-prohibitTimer not running of SR corresponding with normal TTI), then execute step
Rapid 611.
In step 611, if twoth SR_COUNTER < dsr-TransMax corresponding with normal TTI, thens follow the steps
612.Otherwise, step 613 is executed.
In step 612, the 2nd SR_COUNTER values increase by 1, and instruction physical layer is configured with corresponding normal TTI SR described
Effective PUCCH resource on send SR corresponding with normal TTI, start timer sr-ProhibitTimer, or start and just
The associated second timer sr-ProhibitTimer of the normal corresponding SR of TTI.
In step 613, if twoth SR_COUNTER >=dsr-TransMax corresponding with normal TTI, can advise
Random access procedure is executed in fixed cell (such as SpCell) and cancels all to be sent SRs corresponding with normal TTI.It is optional
, all to be sent SR corresponding with short TTI can be cancelled.Optionally, RRC can be notified to discharge the second of all serving cells
PUCCH (PUCCH corresponding with normal TTI).
It should be noted that step 602 and 603 is optional, if not executing step 602 and 603, if meeting step
Rapid 601 condition executes step 604.
Example 3
In this example, it is sent on PUCCH corresponding with short TTI with the corresponding SR of short TTI, it is corresponding with normal TTI
SR is sent on PUCCH corresponding with normal TTI.For example, it is assumed that sometime or time slot duration trigger it is TTI pairs short
The SR answered, and the corresponding effective PUCCH of normal TTI can use moment effective PUCCH corresponding prior to short TTI, then short TTI is corresponding
SR is not sent on the corresponding effective PUCCH of normal TTI, but waits for the corresponding effective PUCCH of short TTI.
Fig. 7 shows the schematic flow diagram of the SR transmission process in this example.
In step 701, if there is any SR (and normal TTI corresponding SR or corresponding with short TTI SR) is to be sent, to every
A normal TTI or short TTI are thened follow the steps if current normal TTI or short TTI do not have UL-SCH resources to can be used for transmitting
702。
In step 702, if SR to be sent is SR corresponding with short TTI, if do not had in the arbitrary short TTI for being configured with SR
There is the effective PUCCH resource that can be used for sending SR, thens follow the steps 703.Otherwise, step 704 is executed.
In step 703, random access procedure is executed in defined cell (such as SpCell) and is cancelled corresponding with short TTI
All SR to be sent.Optionally, all to be sent SR corresponding with normal TTI can be cancelled.
In step 704, if SR to be sent is SR corresponding with normal TTI, if in the arbitrary normal TTI for being configured with SR
The effective PUCCH resource that not can be used for sending SR inside, thens follow the steps 705.Otherwise, step 706 is executed.
In step 705, random access procedure is executed in defined cell (such as SpCell) and is cancelled and normal TTI pairs
All SR to be sent answered.Optionally, all to be sent SR corresponding with short TTI can be cancelled.
In step 706, at least one it can be used for sending the effective of the corresponding SR of short TTI if had in current short TTI
PUCCH resource and the current short TTI are not the part and timer sr- that measurement interval or Sindlink have found interval
ProhibitTimer not running (or the associated sr-prohibitTimer not running of SR corresponding with short TTI), thens follow the steps
707.Otherwise, step 710 is executed.
In step 707, if first SR_COUNTER < dsr-TransMax corresponding with short TTI, thens follow the steps
708.Otherwise, step 709 is executed.
In step 708, the first SR_COUNTER values increase by 1, and instruction physical layer is configured with corresponding short TTI SR's described
SR corresponding with short TTI is sent in effective PUCCH resource, starts timer sr-ProhibitTimer, or is started and TTI pairs short
The associated first timer sr-ProhibitTimer of SR answered.
In step 709, if first SR_COUNTER >=dsr-TransMax corresponding with short TTI, can provide
Cell (such as SpCell) on execute random access procedure and cancel all to be sent SRs corresponding with short TTI.Optionally, may be used
To cancel all to be sent SRs corresponding with normal TTI.Optionally, RRC can be notified to discharge the first of all serving cells
PUCCH (PUCCH corresponding with short TTI).
In step 710, at least one it can be used for sending having for the corresponding SR of normal TTI if had in current normal TTI
Effect PUCCH resource and the current normal TTI are not the part and timer sr- that measurement interval or Sindlink have found interval
ProhibitTimer not running (or the associated sr-prohibitTimer not running of SR corresponding with normal TTI), then execute
Step 711.
In step 711, if twoth SR_COUNTER < dsr-TransMax corresponding with normal TTI, thens follow the steps
712.Otherwise, step 713 is executed.
In step 712, the 2nd SR_COUNTER values increase by 1, and instruction physical layer is configured with corresponding normal TTI SR described
Effective PUCCH resource on send the corresponding SR of normal TTI, start timer sr-ProhibitTimer, or start with it is normal
TTI corresponds to the associated second timer sr-ProhibitTimer of SR.
In step 713, if twoth SR_COUNTER >=dsr-TransMax corresponding with normal TTI, can advise
Random access procedure is executed in fixed cell (such as SpCell) and cancels the corresponding all SR to be sent of normal TTI.Optionally,
All to be sent SR corresponding with short TTI can be cancelled.Optionally, RRC can be notified to discharge the second of all serving cells
PUCCH (PUCCH corresponding with normal TTI).
It should be noted that alternative, step 702~705 could alternatively be：If in the arbitrary TTI for being configured with SR
The effective PUCCH resource that not can be used for sending SR, then execute random access procedure in defined cell (such as SpCell)
And cancel all SR to be sent.Otherwise, step 706 is executed.
Example 4
In this example, TTI pairs short if be configured with simultaneously and short TTI corresponding SR and SR corresponding with normal TTI
The SR answered is formerly sent on effective PUCCH；For example, it is assumed that sometime or time slot duration triggers short TTI and corresponds to
SR, and the normal corresponding effective PUCCH of TTI can use moment effective PUCCH corresponding prior to short TTI, then the corresponding SR of short TTI
It is sent on the corresponding effective PUCCH of normal TTI.If being configured with SR corresponding with normal TTI, SR corresponding with normal TTI
It is sent on PUCCH corresponding with normal TTI.
Fig. 1 a are returned to, this method 10a further includes optionally step 140.In step 140, cancel corresponding with specific type
Other SR.In the following, the cancellation of SR is described in detail by several specific examples.
Example 1
Fig. 8 shows that the SR in this example cancels the schematic flow diagram of process.
In step 801, user equipment (UE) sends SR to base station, and is sent and SR associated " fate/TTI types " to base station
The buffer status of the corresponding relevant PDCP and RLC entities data to be sent of logic channel indicates information.The buffer status indicates
Information can be indicated with a MAC PDU, and can be defined as a kind of new BSR types.For example, the buffer status indicates information
Buffer status when can include the BSR up-to-date events generation of triggering new type.
The BSR of above-mentioned new type is related to fate/Transmission Time Interval type, can only include to be closed with certain type TTI
The buffer state of connection or support certain type TTI logic channel data to be sent or support the logic channel of certain type TTI
Data to be sent in corresponding RLC and PDCP entities, for example, in TTI (being denoted as TTI1) associated buffer area of Class1
In the data to be sent of the logic channel of data or support TTI1 or the corresponding RLC and PDCP entities of logic channel of support TTI1
Data to be sent can only be sent in the uplink assignment that TTI is TTI1 or can only be with the data in the associated buffer areas of TTI1
TTI is sent in the uplink assignment no more than TTI1.
If the uplink assignment for sending buffer status instruction information is based on non-competing resource, i.e., the described resource is
User equipment specific resource, then when MAC layer generates newest buffer status instruction letter associated with some fate/TTI types
When breath, cancels all to be sent SRs corresponding with the fate/TTI types and stop corresponding sr-ProhibitTimer.If
The uplink assignment for sending buffer status instruction information is resource competition-based, then the buffer status indicates information
In comprising can distinguish different UE UE mark, for example, C-RNTI.
In step 802, user equipment (UE) receives the uplink assignment from base station, which is associated with above-mentioned SR
Fate/corresponding the uplink assignment of TTI types.If the resource for sending buffer status instruction information in step 801 is based on competition
, then when the MAC layer generation newest buffer status with fate/TTI type associations indicates information, it can cancel and be somebody's turn to do
The corresponding all SR to be sent of fate/TTI types and the corresponding sr-ProhibitTimer of stopping.If the uplink assignment is
Uplink assignment corresponding with normal TTI, thens follow the steps 803.
In step 803, user equipment (UE) sends buffer status instruction information or BSR to base station.When MAC layer generates and the life
When the newest buffer status instruction information of reason/TTI type associations, cancels all SRs corresponding with the fate/TTI types and stop
Only corresponding sr-ProhibitTimer.If the BSR sent to base station caches shape when including the up-to-date event generation of triggering BSR
State then cancels all SR to be sent and stops all sr-ProhibitTimer.
Example 2
Fig. 9 shows that the SR in this example cancels the schematic flow diagram of process.
In step 901, user equipment (UE) sends the SR of the first kind to base station.
In step 902, user equipment (UE) receives the uplink assignment of the first kind from base station, the first kind it is upper
Row distribution can correspond to " fate/Transmission Time Interval type " associated with the SR of the first kind.
In step 903, user equipment (UE) sends buffer status to base station and indicates information.The buffer status indicates that information is available
One MAC PDU is indicated, and can be defined as a kind of new BSR types.The buffer status indicates that information includes described in triggering
Buffer status when the BSR up-to-date events of new type occur.The BSR of new type is related to fate/Transmission Time Interval type,
Can only include with the associated buffer states of certain type TTI, for example, can only be with the data in the associated buffer areas of TTI1
TTI is to be sent in the uplink assignment of TTI1 or can only be not more than the upper of TTI1 in TTI with the data in the associated buffer areas of TTI1
It is sent in row distribution.Refer to when MAC layer generates the newest buffer status with some fate/Transmission Time Interval type association
When showing information, cancels all to be sent SRs corresponding with the fate/Transmission Time Interval type and stop corresponding sr-
ProhibitTimer。
Fig. 1 (b) is the flow chart for showing the method 10b executed by base station according to an embodiment of the present disclosure.
In step 150, the SR of the first kind is received from user equipment (UE).
In step 160, the uplink assignment of the first kind is sent to user equipment (UE), the uplink assignment of the first kind can be with
Corresponding to " fate/Transmission Time Interval type " associated with the SR of the first kind.
In step 170, from user equipment (UE) order caching status indication information.Buffer status instruction information can use one
MAC PDU are indicated, and can be defined as a kind of new BSR types.The buffer status indicates that information includes to trigger the new class
Buffer status when the BSR up-to-date events of type occur.The BSR of new type can be related to fate/Transmission Time Interval type,
Can only include and the associated buffer states of certain type TTI.
Fig. 2 a are the block diagrams for showing the user equipment 20a according to an embodiment of the present disclosure.As shown in Figure 2 a, the user
Equipment 20a includes processor 210a and memory 220a.Processor 210a for example may include microprocessor, microcontroller, embedding
Enter formula processor etc..Memory 220a for example may include volatile memory (such as random access memory ram), hard drive
Device (HDD), nonvolatile memory (such as flash memory) or other memories.Have program stored therein finger on memory 220a
It enables.The instruction can execute the above-mentioned side of disclosure detailed description executed by user equipment when being run by processor 210a
Method.
Fig. 2 b are the block diagrams for showing the base station 20b according to an embodiment of the present disclosure.As shown in Figure 2 b, base station 20b
Including processor 210b and memory 220b.Processor 210b for example may include microprocessor, microcontroller, embedded processing
Device etc..Memory 220b for example may include volatile memory (such as random access memory ram), hard disk drive (HDD),
Nonvolatile memory (such as flash memory) or other memories.Have program stored therein instruction on memory 220b.The instruction
When being run by processor 210b, the above method of disclosure detailed description executed by base station can be executed.
The program operated in equipment according to the present invention can make calculating by controlling central processing unit (CPU)
Machine realizes the program of the embodiment of the present invention function.The program or the information handled by the program can be temporarily stored in volatibility
Memory (such as random access memory ram), hard disk drive (HDD), nonvolatile memory (such as flash memory) or its
In his storage system.
It can be recorded on a computer readable recording medium for realizing the program of various embodiments of the present invention function.It can lead to
Crossing makes computer system read the program being recorded in the recording medium and executes these programs to realize corresponding function.This
So-called " computer system " at place can be built-in the computer system in the equipment, may include operating system or hardware
(such as peripheral equipment)." computer readable recording medium storing program for performing " can be semiconductor recording medium, optical record medium, magnetic recording Jie
Matter, the in short-term recording medium of dynamic memory program or any other computer-readable recording medium.
It can be by circuit (for example, monolithic or more with the various feature or function modules of equipment in the above-described embodiments
Piece integrated circuit) it realizes or executes.The circuit for being designed to carry out this specification described function may include general place
Reason device, digital signal processor (DSP), application-specific integrated circuit (ASIC), field programmable gate array (FPGA) or other can compile
The arbitrary combination of journey logical device, discrete door or transistor logic, discrete hardware component or above-mentioned device.General procedure
Device can be microprocessor, can also be any existing processor, controller, microcontroller or state machine.Foregoing circuit can
Can also be analog circuit to be digital circuit.Occur the new of the existing integrated circuit of replacement because of the progress of semiconductor technology
Integrated circuit technique in the case of, one or more embodiments of the invention can also use these new integrated circuit techniques
To realize.
In addition, the invention is not limited in above-described embodiments.Although it have been described that the various examples of the embodiment, but
The present invention is not limited thereto.Fixation or non-mobile electronic equipment mounted on indoor or outdoors may be used as terminal device or logical
Equipment is believed, such as AV equipment, cooking apparatus, cleaning equipment, air-conditioning, office equipment, automatic vending machine and other household electrical appliance
Deng.
As above, the embodiment of the present invention is described in detail by reference to attached drawing.But specific structure not office
It is limited to above-described embodiment, the present invention also includes any design change without departing from present subject matter.Furthermore it is possible in claim
In the range of the present invention is variously changed, it is obtained by being appropriately combined technological means disclosed in different embodiments
Embodiment is also included in the technical scope of the present invention.In addition, the component with same effect described in above-described embodiment
It can be substituted for each other.
Claims (10)
1. a kind of method executed by user equipment (UE), including：
Trigger the transmission of buffer status report BSR；
If there is no the ascending resource for sending BSR, then phase is triggered according to the type of the scheduling request SR configured for UE
The transmission of the SR answered；
Wherein, the SR include at least SR corresponding with the first fate/Transmission Time Interval type and with the second fate/biography
The defeated corresponding SR of time interval type.
2. according to the method described in claim 1, wherein, being total to from different fates/corresponding SR of Transmission Time Interval type
It enjoys a logic channel SR and forbids timer；And
The transmission of the corresponding SR of the triggering includes：In the case where the logic channel SR forbids timer not running, if
The BSR is not to have data transmittable and trigger and the BSR is by meeting second by the logic channel for meeting first condition
The logic channel of condition has data to can be transmitted and trigger, then triggers SR corresponding with the first fate/Transmission Time Interval type
Transmission.
3. according to the method described in claim 1, wherein, having from the corresponding SR of different fates/Transmission Time Interval type
There is respective logic channel SR to forbid timer；And
The transmission of the corresponding SR of the triggering includes：In logic channel corresponding with the first fate/Transmission Time Interval type
In the case that SR forbids timer not running, if the BSR is not to have data that can send out by the logic channel for meeting first condition
It send and triggers and the BSR is has data transmittable and trigger, then triggering and first by the logic channel for meeting second condition
The transmission of fate/corresponding SR of Transmission Time Interval type.
4. according to the method described in claim 1, further including：Corresponding SR is sent according to the type of SR.
5. according to the method described in claim 4, wherein, corresponding SR is sent according to the type of SR includes：By with first
Fate/corresponding PUCCH of Transmission Time Interval type and PUCCH corresponding with the second fate/Transmission Time Interval type
Send SR corresponding with the first fate/Transmission Time Interval type, and by with the second fate/Transmission Time Interval class
The corresponding PUCCH of type sends SR corresponding with the second fate/Transmission Time Interval type.
6. according to the method described in claim 4, wherein, corresponding SR is sent according to the type of SR includes：By with first
Fate/corresponding PUCCH of Transmission Time Interval type is corresponding with the first fate/Transmission Time Interval type to send
SR, and by PUCCH corresponding with the first fate/Transmission Time Interval type and with the second fate/Transmission Time Interval
The corresponding PUCCH of type sends SR corresponding with the second fate/Transmission Time Interval type.
7. according to the method described in claim 4, wherein, corresponding SR is sent according to the type of SR includes：By with first
Fate/corresponding PUCCH of Transmission Time Interval type is corresponding with the first fate/Transmission Time Interval type to send
SR, and sent and the second fate/transmission time by PUCCH corresponding with the second fate/Transmission Time Interval type
The corresponding SR of interval type.
8. according to the method described in claim 4, wherein, the UE is sent and the second fate/Transmission Time Interval class to base station
The corresponding SR of type and BSR information corresponding with the first fate/Transmission Time Interval type, the BSR information include most
New buffer status information；And the method further includes：If being the special moneys of UE for sending the resource of the BSR information
Other SRs corresponding with the first fate/Transmission Time Interval type are then cancelled in source.
9. according to the method described in claim 8, wherein, the method further includes：
If not being UE private resources for sending the resource of the BSR information, when being received from base station with the second fate/transmission
Between the corresponding uplink assignment message of interval type；And
Corresponding with the first fate/Transmission Time Interval type newest BSR information is generated, and cancel and the first fate/
The corresponding other SR of Transmission Time Interval type.
10. according to the method described in claim 4, wherein, the UE is sent and the first fate/Transmission Time Interval class to base station
The corresponding SR of type；And the method further includes：
Uplink assignment message corresponding with the first fate/Transmission Time Interval type is received from base station；And
Corresponding with the first fate/Transmission Time Interval type BSR information is sent to base station, and cancel and the first fate/
The corresponding other SR of Transmission Time Interval type.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710310255.1A CN108810925A (en) | 2017-05-04 | 2017-05-04 | Method and apparatus for handling scheduling request |
| PCT/CN2018/084228 WO2018201929A1 (en) | 2017-05-04 | 2018-04-24 | Method and apparatus for processing scheduling requests |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710310255.1A CN108810925A (en) | 2017-05-04 | 2017-05-04 | Method and apparatus for handling scheduling request |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN108810925A true CN108810925A (en) | 2018-11-13 |
Family
ID=64015793
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710310255.1A Pending CN108810925A (en) | 2017-05-04 | 2017-05-04 | Method and apparatus for handling scheduling request |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN108810925A (en) |
| WO (1) | WO2018201929A1 (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2020147813A1 (en) * | 2019-01-18 | 2020-07-23 | 维沃移动通信有限公司 | Information sending method, data sending method, terminal configuration method, and device |
| CN113015211A (en) * | 2019-12-20 | 2021-06-22 | 大唐移动通信设备有限公司 | Data transmission scheduling method and terminal |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113498040B (en) * | 2020-04-08 | 2023-12-05 | 大唐移动通信设备有限公司 | Method and device for stopping sending scheduling request |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101778418B (en) * | 2009-01-13 | 2014-03-19 | 中兴通讯股份有限公司 | Method and device for triggering or reporting scheduling request in wireless network |
| KR101623977B1 (en) * | 2009-10-09 | 2016-05-24 | 삼성전자주식회사 | Device and method for transmitting scheduling request in wireless communication system |
| EP2829136A4 (en) * | 2012-03-19 | 2016-01-13 | Alcatel Lucent | Method and apparatus for configuring a plurality of scheduling request triggers |
| US9907056B2 (en) * | 2014-08-06 | 2018-02-27 | Futurewei Technologies, Inc. | System and method for allocating resources for device-to-device communications |
-
2017
- 2017-05-04 CN CN201710310255.1A patent/CN108810925A/en active Pending
-
2018
- 2018-04-24 WO PCT/CN2018/084228 patent/WO2018201929A1/en active Application Filing
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2020147813A1 (en) * | 2019-01-18 | 2020-07-23 | 维沃移动通信有限公司 | Information sending method, data sending method, terminal configuration method, and device |
| CN113015211A (en) * | 2019-12-20 | 2021-06-22 | 大唐移动通信设备有限公司 | Data transmission scheduling method and terminal |
| CN113015211B (en) * | 2019-12-20 | 2022-08-19 | 大唐移动通信设备有限公司 | Data transmission scheduling method and terminal |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2018201929A1 (en) | 2018-11-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP7318089B2 (en) | Wireless communication system and method | |
| ES2747827T3 (en) | Conditional use of uplink radio resources in a cellular network | |
| KR102202334B1 (en) | Method for transmitting a scheduling request in a wireless communication system and apparatus therefor | |
| ES2717429T3 (en) | Planning request procedure for D2D communication | |
| TWI413431B (en) | Method and apparatus for power headroom reporting | |
| US10555208B2 (en) | Method for performing a buffer status reporting in a wireless communication system and device therefor | |
| KR20220100948A (en) | Method for low-tier inter-cell mobility management | |
| BR112018001646B1 (en) | METHOD AND APPARATUS OF WIRELESS COMMUNICATION BY A MACHINE-TYPE COMMUNICATION USER EQUIPMENT AND COMPUTER READABLE MEMORY | |
| JP2014512782A (en) | Data transmission method and transmission resource allocation method and apparatus | |
| CN109561511A (en) | Wireless communications method and equipment | |
| CN106576314A (en) | Transmission timing control for D2D communication | |
| US20240292402A1 (en) | User equipment, base station and related method | |
| KR20100119765A (en) | Shared resource allocation | |
| TWI843743B (en) | Feedback prioritization for wireless communications | |
| WO2020034904A1 (en) | Control method for user equipment, control method for base station, and user equipment | |
| CN110740522B (en) | Resource selection method, base station and terminal | |
| CN109963337A (en) | Wireless communications method and equipment | |
| RU2764284C2 (en) | Method and device in radio communication network | |
| CN108810925A (en) | Method and apparatus for handling scheduling request | |
| US20240373432A1 (en) | Method and device for reporting uplink control information, storage medium, and user equipment | |
| WO2021063307A1 (en) | Method executed by user device and user device | |
| CN109804709A (en) | Wireless communication device | |
| WO2021063305A1 (en) | Method executed by user equipment, and user equipment | |
| WO2020222215A1 (en) | Transmission prioritisation | |
| JP2024514516A (en) | Prioritization of logical channels within configuration permissions |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| WD01 | Invention patent application deemed withdrawn after publication | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20181113 |