WO2019062422A1 - 调度请求的处理方法及终端设备 - Google Patents

调度请求的处理方法及终端设备 Download PDF

Info

Publication number
WO2019062422A1
WO2019062422A1 PCT/CN2018/102553 CN2018102553W WO2019062422A1 WO 2019062422 A1 WO2019062422 A1 WO 2019062422A1 CN 2018102553 W CN2018102553 W CN 2018102553W WO 2019062422 A1 WO2019062422 A1 WO 2019062422A1
Authority
WO
WIPO (PCT)
Prior art keywords
logical channel
scheduling request
cancellation
status report
cancel
Prior art date
Application number
PCT/CN2018/102553
Other languages
English (en)
French (fr)
Inventor
岳然
杨晓东
Original Assignee
维沃移动通信有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 维沃移动通信有限公司 filed Critical 维沃移动通信有限公司
Priority to US16/652,095 priority Critical patent/US11184912B2/en
Priority to EP18863220.2A priority patent/EP3691390B1/en
Priority to ES18863220T priority patent/ES2944437T3/es
Publication of WO2019062422A1 publication Critical patent/WO2019062422A1/zh

Links

Images

Classifications

    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0278—Traffic management, e.g. flow control or congestion control using buffer status reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0096—Indication of changes in allocation

Definitions

  • the present application relates to the field of communications, and in particular, to a method and a terminal device for processing a scheduling request.
  • the SR Service Request
  • the SR is considered to be in a Pending state before being canceled.
  • the condition that the SR of the Pending state is canceled includes: the assembled MAC PDU (Media Access Control Layer Protocol Data Unit) includes a BSR (Buffer Status Report), and the BSR includes the latest cache status when the BSR is triggered; or The allocated uplink resources are sufficient to transmit all available Pending data.
  • the assembled MAC PDU Media Access Control Layer Protocol Data Unit
  • BSR Buffer Status Report
  • each logical channel can be mapped to 0 to 1 SR, but there is no clear conclusion about the cancellation of the SR at present.
  • LCH1 the eMBB service
  • URLLC ultra-high reliability and low delay
  • SR2 will be cancelled.
  • the UL grant (uplink scheduling grant) for sending the BSR is obtained through SR1, and after the BSR is sent, the uplink data is scheduled to be transmitted. This process results in a large data delay on LCH2.
  • the purpose of the embodiment of the present application is to provide a processing method for a scheduling request and a terminal device, so as to improve the cancellation/cancellation exemption mechanism for the scheduling request SR in the NR system.
  • an embodiment of the present invention provides a processing method for scheduling a request, where the method includes:
  • the embodiment of the present invention further provides a terminal device, where the terminal device includes:
  • a determining module configured to report whether to cancel the triggered scheduling request SR and/or stop the SR prohibiting timer according to the current status of the BSR reporting the status of the BSR.
  • an embodiment of the present invention further provides a terminal device, including a processor, a memory, and a computer program stored on the memory and executable on the processor, where the computer program is used by the processor Steps of implementing the processing method of the scheduling request according to any of the above items at the time of execution
  • the embodiment of the present invention further provides a computer readable storage medium, where the computer readable storage medium stores a computer program, and when the computer program is executed by the processor, implements the scheduling according to any one of the foregoing The steps of the requested processing method.
  • the technical solution improves the cancellation/cancellation exemption mechanism of the scheduling request SR, and in particular, when applied to the NR system, the delay of the delay-sensitive service (such as the URLLC service) can be reduced, thereby improving system performance.
  • FIG. 1 is a flow chart of a method for processing a scheduling request in an embodiment of the present application.
  • FIG. 2 is a flowchart of a method for processing a scheduling request in a specific embodiment 1 of the present application.
  • FIG. 3 is a flowchart of a method for processing a scheduling request in a second embodiment of the present application.
  • FIG. 4 is a flowchart of a method for processing a scheduling request in a third embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of a terminal device in an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of a terminal device in an embodiment of the present application.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • Terminal equipment also known as mobile terminal, access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user Agent or user device.
  • the access terminal may be a cellular phone, a cordless phone, a SIP (Session Initiation Protocol) phone, a WLL (Wireless Local Loop) station, a PDA (Personal Digital Assistant), and a wireless communication.
  • PLMN Public Land Mobile Network
  • the system to which the present application is adapted may be FDD (Frequency Division Duplex), TDD (Time Division Duplex), or a system in which FDD and TDD are used in a duplex mode. Make a limit.
  • FIG. 1 is a flow chart of a method for processing a scheduling request in an embodiment of the present application.
  • the method of FIG. 1 is performed by a terminal device, and may include:
  • Step S101 Determine whether to cancel the triggered scheduling request SR and/or stop the SR prohibiting timer according to the current status of the buffer status report BSR.
  • the current status of the buffer status report BSR may include that the buffer status report BSR has been assembled or the buffer status report BSR has been sent.
  • the Cache Status Report BSR contains the cache status when the BSR was last triggered by the Cache Status Report. When it is determined that the triggered scheduling request SR is canceled, the SR inhibition timer is stopped.
  • the technical solution improves the cancellation/cancellation exemption mechanism of the scheduling request SR, and in particular, when applied to the NR system, the delay of the delay-sensitive service (such as the URLLC service) can be reduced, thereby improving system performance.
  • the delay-sensitive service such as the URLLC service
  • the scheduling request SR corresponding to the resource for assembling or transmitting the buffer status report BSR and/or the stop SR prohibition timing are cancelled.
  • the resources used to assemble or send the buffer status report BSR may include:
  • the resource in which the scheduling request SR is located is a value configuration resource corresponding to the SR configuration
  • the value configuration resource (assuming the subcarrier spacing is 15 kHz) has two SR configurations on the carrier 1, including the SR configuration 1 (eg, corresponding to 1, 3, 5 subframes) and SR configuration 2 (such as corresponding 2, 4, 6 subframes), wherein the value configuration resource corresponding to SR configuration 1 is the value configuration resource of carrier 1; the value configuration resource corresponding to SR configuration 2 is the carrier 2 value configuration resources.
  • the SR configuration 1 corresponds to the triggering of the eMBB service
  • the SR configuration 2 corresponds to the trigger of the URLLC service.
  • the scheduling request SR corresponding to the SR configuration 1 on the carrier 1 is cancelled, that is, the scheduling request SR corresponding to the value configuration resource of the carrier 1; if the URLLC service is sent on the carrier 2, then The scheduling request SR corresponding to the SR configuration 2 on the carrier 1 is cancelled, that is, the scheduling request SR corresponding to the value configuration resource on the carrier 1.
  • the scheduling request SR and/or the stop SR prohibition timer on the resource for assembling or transmitting the buffer status report BSR can be cancelled, which not only improves the scheduling.
  • the cancellation mechanism of the SR is requested, and the delay of the delay-sensitive service (such as the URLLC service) can be reduced, and the system performance is improved.
  • determining whether to cancel the triggered scheduling request SR and/or stopping the SR prohibit timer if the current status of the buffer status report BSR is that the buffer status report BSR has been sent, cancel all triggered scheduling requests SR and / or stop SR prohibit timer.
  • all the scheduling requests SR that are triggered and/or the stop SR prohibition timer can be canceled. Since the scheduling request SR is not required to be sent when the buffer status report BSR has been sent, canceling all the scheduling request SRs that are triggered at this time can avoid unnecessary scheduling request SRs occupying resources, thereby making the cancellation mechanism of the scheduling request SR more perfect.
  • determining whether to cancel the triggered scheduling request SR and/or stopping the SR prohibit timer may also be combined with the current status of the buffer status report BSR and the type of the logical channel used to carry the scheduling request SR. Cancel the scheduling request SR and/or stop the SR prohibit timer.
  • the type of the logical channel is used to indicate whether the logical channel is an SR cancellation exempt logical channel.
  • the type of logical channel may include an SR Cancel Exempt Logical Channel or a Non-SR Cancel Exempt Logical Channel.
  • the SR cancel exempt logical channel is pre-configured by the network side.
  • the network side pre-configures at least one logical channel for the SR cancellation exempt logical channel, the at least one logical channel needs to satisfy at least one of the following conditions:
  • the subcarrier spacing corresponding to the logical channel is greater than a preset threshold.
  • the subcarrier spacing corresponding to the logical channel may be 15 kHz, 60 kHz, 240 kHz, or the like.
  • the service corresponding to the logical channel is a specified low-latency service.
  • low-latency services such as URLLC services are specified.
  • the logical channel performs an independent scheduling request process.
  • determining whether to cancel the triggered scheduling request SR and/or stopping the SR prohibit timer whether the current state of the non-SR cancel exempt logical channel judgment buffer status report BSR is a buffer status report BSR has been assembled; If so, the cancellation SR cancels the scheduling request SR on the logical channel.
  • the scheduling request SR on the cancel SR cancellation exemption logical channel is exempted, compared to the SR cancellation mechanism in the conventional LET system.
  • the technical solution improves the cancellation exemption mechanism of the scheduling request SR, and avoids the situation that the cancellation scheduling request SR cannot be exempted according to the current situation (such as the current channel type or the state of the BSR).
  • the cache status report BSR sent on the non-SR cancel exempt logical channel includes the SR Cancel the cache size on the logical channel. If it is determined that the buffer status report BSR transmitted on the non-SR cancel exempt logical channel does not include the buffer size on the SR cancel exempt logical channel, the cancel SR cancels the scheduling request SR on the logical channel.
  • the non-SR cancel exempt logical channel determination buffer status report BSR is assembled, and the non-SR cancel exemption logical channel transmission buffer status report BSR does not include the SR cancellation exemption cache size on the logical channel, exemption cancellation
  • the SR cancels the exemption of the scheduling request SR on the logical channel, thereby further improving the cancellation exemption mechanism of the scheduling request SR.
  • the scheduling request SR that is exempted from cancellation on the logical channel can be sent, so that the scheduling request SR on the SR cancellation exemption logical channel can continue after the cancellation cancellation. It is sent, thereby not only perfecting the cancellation exemption mechanism of the scheduling request SR.
  • the technical solution can also continue to send the scheduling request SR that is exempted from canceling when the scheduling request SR needs to be sent, thereby reducing the delay and greatly improving the system. performance.
  • determining whether to cancel the triggered scheduling request SR and/or stopping the SR prohibition timer, canceling the exemption logical channel for the SR determining whether the current state of the buffer status report BSR of the SR cancellation exempt logical channel trigger is cached
  • the status report BSR has been assembled or sent, and if so, cancels the SR cancellation exemption scheduling request SR on the logical channel and/or stops the SR inhibit timer. That is, for the SR cancellation exempt logical channel, the scheduling request SR and/or the stop SR prohibition timer on the SR cancellation exemption logical channel are cancelled only when the buffer status report BSR triggered by its own channel is assembled or transmitted.
  • the scheduling request SR on the SR cancellation exempt logical channel and/or the stop SR inhibition timer are cancelled only when the buffer status report BSR triggered by the SR cancellation exemption logical channel itself is assembled or transmitted.
  • the SR cancellation mechanism for canceling the scheduling request SR on the logical channel is more perfect.
  • the scheduling request SR and/or the stop SR prohibition timer on the SR cancellation exempt logical channel can be canceled when all the to-be-sent data on the SR cancellation exemption logical channel has been assembled or transmitted, due to the SR cancellation exemption
  • the scheduling request SR can avoid unnecessary scheduling request SR occupying resources, and the SR cancellation exempt logical channel is improved.
  • the scheduling request on the SR cancels the mechanism.
  • FIG. 2 is a flowchart of a method for processing a scheduling request in a specific embodiment 1 of the present application.
  • the method of FIG. 2 is performed by a terminal device, and may include:
  • Step S201 for the non-SR cancellation exemption logical channel, determining that the buffer status report BSR is assembled.
  • Step S202 determining that the buffer status report BSR sent on the non-SR cancel exempt logical channel does not include the buffer size on the SR cancel exempt logical channel.
  • Step S203 exempting the cancellation of the SR cancellation exemption scheduling request SR on the logical channel.
  • Step S204 When the SR cancels the arrival of the scheduling request resource on the exempt logical channel, the SR cancels the scheduling request SR on the exempt logical channel.
  • the SR cancellation exempt logical channel is pre-configured by the network side.
  • the network side pre-configures at least one logical channel for the SR cancellation exempt logical channel, the at least one logical channel needs to satisfy at least one of the following conditions:
  • the subcarrier spacing corresponding to the logical channel is greater than a preset threshold.
  • the subcarrier spacing corresponding to the logical channel may be 15 kHz, 60 kHz, 240 kHz, or the like.
  • the service corresponding to the logical channel is a specified low-latency service.
  • low-latency services such as URLLC services are specified.
  • the logical channel performs an independent scheduling request process.
  • the first embodiment can cause the buffer status report BSR to be assembled, and the non-SR cancel exempts the buffer status report sent on the logical channel.
  • the BSR does not include the SR cancellation exemption on the logical channel.
  • the cancellation of the SR cancellation exempts the scheduling request SR on the logical channel, thereby further improving the cancellation exemption mechanism of the scheduling request SR.
  • the scheduling request SR of the logical channel can be sent out when the scheduling request resource on the SR cancellation exemption logical channel arrives.
  • the scheduling request resource is sent by the terminal device, so the terminal device needs to send the scheduling request SR. It also enables the SR cancellation exemption scheduling request SR on the logical channel to continue to be transmitted after the cancellation is cancelled, thereby reducing the delay and greatly improving the system performance.
  • FIG. 3 is a flowchart of a method for processing a scheduling request in a second embodiment of the present application.
  • the method of FIG. 3 is performed by a terminal device, and may include:
  • Step S301 determining whether the SR cancels the logical channel triggered buffer status report BSR has been assembled or transmitted. If yes, go to step S302; if no, go to step S303.
  • Step S302 canceling the SR cancellation exemption of the scheduling request SR on the logical channel and stopping the SR prohibition timer.
  • Step S303 the scheduling request SR on the logical channel is not cancelled by the SR cancellation.
  • the SR cancellation exempt logical channel is pre-configured by the network side.
  • the network side pre-configures at least one logical channel for the SR cancellation exempt logical channel, the at least one logical channel needs to satisfy at least one of the following conditions:
  • the subcarrier spacing corresponding to the logical channel is greater than a preset threshold.
  • the subcarrier spacing corresponding to the logical channel may be 15 kHz, 60 kHz, 240 kHz, or the like.
  • the service corresponding to the logical channel is a specified low-latency service.
  • low-latency services such as URLLC services are specified.
  • the logical channel performs an independent scheduling request process.
  • the scheduling request SR on the SR cancellation exemption logical channel is cancelled and the SR inhibition timer is stopped, so that the SR cancellation is exempted.
  • the cancellation mechanism of the scheduling request SR on the logical channel is more perfect, and the buffer status on the other logical channels is reported to report the impact of the current state of the BSR on canceling the SR cancellation exemption scheduling request SR on the logical channel.
  • FIG. 4 is a flowchart of a method for processing a scheduling request in a third embodiment of the present application.
  • the method of FIG. 4 is performed by a terminal device, and may include:
  • step S401 it is determined that the cache status report BSR has been sent.
  • Step S402 cancel all the scheduling requests SR that are triggered and stop the SR prohibition timer.
  • the scheduling request SR when the buffer status report BSR has been transmitted, all the scheduling requests SR that are triggered can be canceled and the SR prohibit timer is stopped. Since the scheduling request SR is not required to be sent when the buffer status report BSR has been sent, canceling all the scheduling request SRs that are triggered at this time can avoid unnecessary scheduling request SRs occupying resources, thereby making the cancellation mechanism of the scheduling request SR more perfect.
  • FIG. 5 is a schematic structural diagram of a terminal device in an embodiment of the present application.
  • the terminal device may include:
  • the first determining module 510 is configured to determine whether to cancel the triggered scheduling request SR and/or stop the SR prohibit timer according to the current status of the buffer status report BSR.
  • the Buffer Status Report BSR contains the cache status when the BSR was last triggered by the Buffer Status Report.
  • the first determining module 510 includes:
  • a first determining unit configured to: if the current status of the buffer status report BSR is that the buffer status report BSR has been assembled or sent, cancel the scheduling request SR corresponding to the resource for assembling or transmitting the buffer status report BSR and/or stop the SR prohibition Timer.
  • the resources include:
  • the SR configures at least one of a value allocation resource corresponding to the logical channel corresponding to the logical channel, a bandwidth partial resource BWP, and a component carrier resource CC.
  • the first determining module 510 includes:
  • the first canceling unit is configured to cancel all the scheduling requests SR that are triggered and/or stop the SR prohibiting timer if the current status of the buffer status report BSR is that the buffer status reports that the BSR has been sent.
  • the foregoing terminal device further includes:
  • a second determining module configured to determine whether to cancel the triggered scheduling request SR and/or stop the SR prohibiting timer according to a type of the logical channel used to carry the scheduling request SR, where the type of the logical channel is used to indicate Whether the logical channel is an SR cancellation exempt logical channel.
  • the first determining module 510 includes:
  • a first determining unit configured to determine, for a non-SR cancel exempt logical channel other than the SR cancel exempt logical channel, whether the current status of the buffer status report BSR is a buffer status report that the BSR has been assembled;
  • the cancellation unit is used to cancel the SR cancellation exemption scheduling request SR on the logical channel if the current status of the buffer status report BSR is that the buffer status report BSR has been assembled.
  • the first determining module 510 further includes:
  • a second determining unit configured to determine, before exempting the scheduling request SR on the SR cancellation exemption logical channel, that the buffer status report BSR sent on the non-SR cancellation exempt logical channel does not include the buffer size on the SR cancellation exemption logical channel.
  • the first determining module 510 further includes:
  • a sending unit configured to send the SR to cancel the scheduling request SR on the logical channel when the SR cancels the scheduling request resource on the logical channel after the SR cancellation cancels the scheduling request SR on the logical channel.
  • the first determining module 510 includes:
  • a second determining unit configured to cancel the exempt logical channel for the SR, and determine whether the current status of the buffer status report BSR of the SR cancellation exempt logical channel trigger is a buffer status report that the BSR has been assembled or sent;
  • a second canceling unit configured to: if the current status of the buffer status report BSR of the SR cancellation exempt logical channel trigger is a buffer status report that the BSR has been assembled or sent, cancel the SR cancellation exemption scheduling request SR on the logical channel and/or stop the SR The timer is disabled.
  • the first determining module 510 further includes:
  • a third determining unit configured to determine that all data to be sent on the SR cancellation exemption logical channel has been assembled or transmitted before canceling the scheduling request SR on the SR cancellation exemption logical channel and/or stopping the SR inhibition timer.
  • the SR cancellation exempt logical channel satisfies at least one of the following conditions:
  • the subcarrier spacing corresponding to the logical channel is greater than a preset threshold
  • the service corresponding to the logical channel is a specified low-latency service
  • the logical channel performs an independent scheduling request process.
  • the terminal device provided by the embodiment of the present application can report whether to cancel the triggered scheduling request SR and/or stop the SR prohibit timer according to the current state of the BSR reporting the BSR. Therefore, the technical solution improves the cancellation/cancellation exemption mechanism of the scheduling request SR, and in particular, when applied to the NR system, the delay of the delay-sensitive service (such as the URLLC service) can be reduced, thereby improving system performance.
  • the delay-sensitive service such as the URLLC service
  • the terminal device provided by the embodiment of the present invention can implement various processes implemented by the terminal device in the method embodiment of FIG. 1 to FIG. 4, and details are not repeatedly described herein.
  • FIG. 6 is a block diagram of a terminal device in accordance with another embodiment of the present invention.
  • the terminal device 600 shown in FIG. 6 includes at least one processor 601, a memory 602, at least one network interface 604, and a user interface 603.
  • the various components in terminal device 600 are coupled together by a bus system 605.
  • the bus system 605 is used to implement connection communication between these components.
  • the bus system 605 includes a power bus, a control bus, and a status signal bus in addition to the data bus.
  • various buses are labeled as bus system 605 in FIG.
  • the user interface 603 may include a display, a keyboard, or a pointing device (eg, a mouse, a trackball, a touchpad, or a touch screen, etc.).
  • a pointing device eg, a mouse, a trackball, a touchpad, or a touch screen, etc.
  • the memory 602 in the embodiments of the present invention may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be a read-only memory (ROM), a programmable read only memory (PROM), an erasable programmable read only memory (Erasable PROM, EPROM), or an electric Erase programmable read only memory (EEPROM) or flash memory.
  • the volatile memory can be a Random Access Memory (RAM) that acts as an external cache.
  • RAM Random Access Memory
  • many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (Synchronous DRAM).
  • the memory 602 of the systems and methods described in the embodiments of the present invention is intended to comprise, without being limited to, these and any other suitable types of memory.
  • memory 602 stores elements, executable modules or data structures, or a subset thereof, or their set of extensions: operating system 6021 and application 6022.
  • the operating system 6021 includes various system programs, such as a framework layer, a core library layer, a driver layer, and the like, for implementing various basic services and processing hardware-based tasks.
  • the application 6022 includes various applications, such as a media player (Media Player), a browser, and the like, for implementing various application services.
  • a program implementing the method of the embodiment of the present invention may be included in the application 6022.
  • the terminal device 600 further includes: a computer program stored on the memory 609 and executable on the processor 610.
  • a computer program stored on the memory 609 and executable on the processor 610.
  • Processor 601 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 601 or an instruction in the form of software.
  • the processor 601 may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a Field Programmable Gate Array (FPGA), or the like. Programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA Field Programmable Gate Array
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present invention may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software modules can be located in a conventional computer readable storage medium of the art, such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the computer readable storage medium is located in a memory 602, and the processor 601 reads the information in the memory 602 and, in conjunction with its hardware, performs the steps of the above method.
  • the computer readable storage medium stores a computer program, and when the computer program is executed by the processor 601, each step of the processing method embodiment of the scheduling request is implemented.
  • the embodiments described in the embodiments of the present invention may be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof.
  • the processing unit can be implemented in one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processing (DSP), Digital Signal Processing Equipment (DSP Device, DSPD), programmable Programmable Logic Device (PLD), Field-Programmable Gate Array (FPGA), general purpose processor, controller, microcontroller, microprocessor, other for performing the functions described herein In an electronic unit or a combination thereof.
  • ASICs Application Specific Integrated Circuits
  • DSP Digital Signal Processing
  • DSP Device Digital Signal Processing Equipment
  • PLD programmable Programmable Logic Device
  • FPGA Field-Programmable Gate Array
  • the technology described in the embodiments of the present invention may be implemented by a module (for example, a process, a function, and the like) that performs the functions described in the embodiments of the present invention.
  • the software code can be stored in memory and executed by the processor.
  • the memory can be implemented in the processor or external to the processor.
  • the cache status report BSR includes a cache status when the cache status report BSR is triggered last time.
  • the buffer status report BSR If the current status of the buffer status report BSR is that the buffer status report BSR has been assembled or sent, cancel the scheduling request SR and/or stop SR prohibition timing on the resource for assembling or transmitting the buffer status report BSR. Device.
  • the resources include:
  • the SR configures at least one of a value allocation resource corresponding to the logical channel corresponding to the logical channel, a bandwidth partial resource BWP, and a component carrier resource CC.
  • the type of the logical channel is used to indicate whether the logical channel is an SR cancellation Eliminate logical channels.
  • the buffer status report BSR sent on the non-SR cancel exempt logical channel does not include the cache size on the SR cancel exempt logical channel.
  • the SR cancels the scheduling request SR on the exempt logical channel when the SR cancels the scheduling request resource on the exempt logical channel, the SR cancels the scheduling request SR on the exempt logical channel.
  • Determining the logical channel for the SR cancellation determining whether the current state of the buffer status report BSR of the SR cancellation exempt logical channel trigger is the buffer status report that the BSR has been assembled or sent;
  • the SR cancellation exempt logical channel meets at least one of the following conditions:
  • the subcarrier spacing corresponding to the logical channel is greater than a preset threshold
  • the service corresponding to the logical channel is a specified low-latency service
  • the logical channel performs an independent scheduling request process.
  • the terminal device 600 can implement various processes implemented by the terminal device in the foregoing embodiment. To avoid repetition, details are not described herein again.
  • the terminal device provided by the embodiment of the present application can determine whether to cancel the triggered scheduling request SR and/or stop the SR prohibit timer according to the current state of the buffer status report BSR. Therefore, the technical solution improves the cancellation/cancellation exemption mechanism of the scheduling request SR, and in particular, when applied to the NR system, the delay of the delay-sensitive service (such as the URLLC service) can be reduced, thereby improving system performance.
  • the delay-sensitive service such as the URLLC service
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.
  • a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
  • processors CPUs
  • input/output interfaces network interfaces
  • memory volatile and non-volatile memory
  • the memory may include non-persistent memory, random access memory (RAM), and/or non-volatile memory in a computer readable medium, such as read only memory (ROM) or flash memory.
  • RAM random access memory
  • ROM read only memory
  • Memory is an example of a computer readable medium.
  • Computer readable media includes both permanent and non-persistent, removable and non-removable media.
  • Information storage can be implemented by any method or technology.
  • the information can be computer readable instructions, data structures, modules of programs, or other data.
  • Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory. (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disk read only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, Magnetic tape cartridges, magnetic tape storage or other magnetic storage devices or any other non-transportable media can be used to store information that can be accessed by a computing device.
  • computer readable media does not include temporary storage of computer readable media, such as modulated data signals and carrier waves.
  • embodiments of the present application can be provided as a method, system, or computer program product.
  • the present application can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment in combination of software and hardware.
  • the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Selective Calling Equipment (AREA)

Abstract

公开了一种调度请求的处理方法及终端设备，以完善NR系统中对调度请求SR的取消/取消免除机制，该方法包括：根据缓存状态报告BSR的当前状态，确定是否取消被触发的调度请求SR和/或停止SR禁止计时器。该技术方案完善了调度请求SR的取消/取消免除机制，尤其是应用于NR系统中时，能够降低时延敏感业务(如URLLC业务)的时延，从而提高系统性能。

Description

调度请求的处理方法及终端设备 技术领域
本申请涉及通信领域，尤其涉及一种调度请求的处理方法及终端设备。
背景技术
LTE(Long Term Evolution，长期演进)系统中，一旦SR(Scheduing Request，调度请求)被触发，则认为该SR在被取消前都为待传(即Pending)状态。Pending状态的SR被取消的条件包括：组装的MAC PDU(媒体接入控制层协议数据单元)中包括一个BSR(Buffer Status Report，缓存状态报告)，该BSR包括最新触发BSR时的缓存状态；或，分配的上行资源足够传输所有可用的Pending数据。
在NR(New Radio，新无线)系统中，确认了单个小区的情况下，每个逻辑信道可以映射到0～1个SR，但目前对于SR的取消还没有明确的结论。如果沿用LTE系统中的SR取消策略，则当两个或两个以上的逻辑信道存在时，假设其中一个逻辑信道对应eMBB业务，称为LCH1，另一个逻辑信道对应URLLC(超高可靠及低延时通信)业务，称为LCH2，如果LCH1的优先级低于LCH2，LCH1先触发并发送了SR1，LCH2随后触发了SR2，则SR2为Pending状态。这时，如果收到上行授权，且该授权可以包括最新触发BSR时的缓存状态，那么SR2会被取消。通过SR1获取到发送BSR的UL grant(上行调度授权)，发送BSR后，被调度传输上行数据。该过程导致LCH2上的数据时延较大。
发明内容
本申请实施例的目的是提供一种调度请求的处理方法及终端设备，以完善NR系统中对调度请求SR的取消/取消免除机制。
为解决上述技术问题，本申请实施例是这样实现的：
第一方面，本发明实施例提供了一种调度请求的处理方法，该方法包括：
根据缓存状态报告BSR的当前状态，确定是否取消被触发的调度请求SR和/或停止SR禁止计时器。
第二方面，本发明实施例还提供了一种终端设备，该终端设备包括：
确定模块，用于根据缓存状态报告BSR的当前状态，确定是否取消被触发的调度请求SR和/或停止SR禁止计时器。
第三方面，本发明实施例还提供了一种终端设备，包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如上述任一项所述的调度请求的处理方法的步骤
第四方面，本发明实施例还提供了一种计算机可读存储介质，所述计算机可读存储介质上存储计算机程序，所述计算机程序被处理器执行时实现如上述任一项所述的调度请求的处理方法的步骤。
由以上本申请实施例提供的技术方案可见，本申请实施例方案至少具备如下一种技术效果：
采用本申请实施例提供的技术方案，能够根据缓存状态报告BSR的当前状态确定是否取消被触发的调度请求SR和/或停止SR禁止计时器。因此，该技术方案完善了调度请求SR的取消/取消免除机制，尤其是应用于NR系统中时，能够降低时延敏感业务(如URLLC业务)的时延，从而提高系统性能。
附图说明
为了更清楚地说明本申请实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请中记载的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1是本申请的一个实施例中一种调度请求的处理方法的流程图。
图2是本申请的具体实施例一中的一种调度请求的处理方法的流程图。
图3是本申请的具体实施例二中的一种调度请求的处理方法的流程图。
图4是本申请的具体实施例三中的一种调度请求的处理方法的流程图。
图5是本申请的一个实施例中终端设备的结构示意图。
图6是本申请的一个实施例中终端设备的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请的技术方案，可以应用于各种通信系统，例如：GSM(Global System of Mobile communication,全球移动通讯系统)，CDMA(Code Division Multiple Access，码分多址)系统，WCDMA(Wideband Code Division Multiple Access Wireless，宽带码分多址)，GPRS(General Packet Radio Service，通用分组无线业务)，LTE(Long Term Evolution，长期演进)等。
终端设备，也可称之为移动终端(Mobile Terminal)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、SIP(Session Initiation Protocol，会话启动协议)电话、WLL(Wireless Local Loop，无线本地环路)站、PDA(Personal Digital Assistant，个人数字处理)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，未来5G网络中的终端设备或者未来演进的PLMN(Public Land Mobile Network，公共陆地移动网络)网络中的终端设备。
本申请所适应的系统，可以是FDD(Frequency Division Duplex，频分双工)，TDD(Time Division Duplex，时分双工)或者FDD与TDD两种双工方式聚合使用的系统，本申请对此不做限定。
图1是本申请的一个实施例中一种调度请求的处理方法的流程图。图1的方法由终端设备执行，可包括：
步骤S101，根据缓存状态报告BSR的当前状态，确定是否取消被触发的调度请求SR和/或停止SR禁止计时器。
其中，缓存状态报告BSR的当前状态可包括缓存状态报告BSR已被组装或缓存状态报告BSR已被发送。缓存状态报告BSR包含最近一次触发缓存状态报告BSR时的缓存状态。当确定取消被触发的调度请求SR时，停止SR禁止计时器。
采用本申请实施例提供的技术方案，能够根据缓存状态报告BSR的当前状态，确定是否取消被触发的调度请求SR和/或停止SR禁止计时器。因此，该技术方案完善了调度请求SR的取消/取消免除机制，尤其是应用于NR系统中时，能够降低时延敏感业务(如URLLC业务)的时延，从而提高系统性能。
下面，将结合具体的实施例，对本申请实施例的方法作进一步的描述。
在一个实施例中，若缓存状态报告BSR的当前状态为缓存状态报告BSR已被组装或发送，则取消用于组装或发送缓存状态报告BSR的资源对应的调度请求SR和/或停止SR禁止计时器。
其中，用于组装或发送缓存状态报告BSR的资源可包括：
(1)SR配置对应的数值配置资源、带宽部分资源BWP、成员载波资源CC中的至少一项；或，
(2)SR配置对应的逻辑信道所对应的数值配置资源、带宽部分资源BWP、成员载波资源CC中的至少一项。
举例而言，调度请求SR所在的资源为SR配置对应的数值配置资源，该数值配置资源(假设子载波间隔为15KHZ)在载波1上有两个SR配置，包括SR配置1(如对应1、3、5子帧)和SR配置2(如对应2、4、6子帧)，其中，SR配置1对应的数值配置资源为载波1的数值配置资源；SR配置2对应的数值配置资源为载波2的数值配置资源。SR配置1对应eMBB业务的触发，SR 配置2对应URLLC业务的触发。那么，若eMBB业务在载波1上发送，则取消载波1上的SR配置1所对应的调度请求SR，即载波1的数值配置资源对应的调度请求SR；若URLLC业务在载波2上发送，则取消载波1上的SR配置2所对应的调度请求SR，即载波1上的数值配置资源对应的调度请求SR。
本实施例中，能够在缓存状态报告BSR已被组装或发送时，取消用于组装或发送所述缓存状态报告BSR的资源上的调度请求SR和/或停止SR禁止计时器，不仅完善了调度请求SR的取消机制，且能够降低时延敏感业务(如URLLC业务)的时延，提高了系统性能。
在一个实施例中，确定是否取消被触发的调度请求SR和/或停止SR禁止计时器时，若缓存状态报告BSR的当前状态为缓存状态报告BSR已被发送，则取消被触发的所有调度请求SR和/或停止SR禁止计时器。
本实施例中，能够在缓存状态报告BSR已被发送时，取消被触发的所有调度请求SR和/或停止SR禁止计时器。由于缓存状态报告BSR已被发送时无需再发送调度请求SR，此时取消被触发的所有调度请求SR能够避免不必要的调度请求SR占用资源，进而使得调度请求SR的取消机制更加完善。
在一个实施例中，确定是否取消被触发的调度请求SR和/或停止SR禁止计时器时，还可结合缓存状态报告BSR的当前状态以及用于承载调度请求SR的逻辑信道的类型来确定是否取消调度请求SR和/或停止SR禁止计时器。
其中，逻辑信道的类型用于指示逻辑信道是否为SR取消免除逻辑信道。
逻辑信道的类型可包括SR取消免除逻辑信道或非SR取消免除逻辑信道。
SR取消免除逻辑信道由网络侧预先配置。网络侧预先配置至少一个逻辑信道为SR取消免除逻辑信道时，该至少一个逻辑信道需满足以下条件中的至少一项：
(1)逻辑信道对应的子载波间隔大于预设阈值。
例如，预设阈值为15KHz，则逻辑信道对应的子载波间隔可以是15KHz、60KHz、240KHz等。
(2)逻辑信道对应的业务为指定低时延业务。
其中，指定低时延业务如URLLC业务。
(3)逻辑信道执行独立的调度请求过程。
在一个实施例中，确定是否取消被触发的调度请求SR和/或停止SR禁止计时器时，针对非SR取消免除逻辑信道判断缓存状态报告BSR的当前状态是否为缓存状态报告BSR已被组装；若是，则免除取消SR取消免除逻辑信道上的调度请求SR。
本实施例中，能够针对非SR取消免除逻辑信道判定缓存状态报告BSR被组装时，免除取消SR取消免除逻辑信道上的调度请求SR，相较于传统的LET系统中的SR取消机制而言，该技术方案完善了调度请求SR的取消免除机制，避免了无法根据当前状况(如当前的信道类型或BSR的状态)免除取消调度请求SR的情况。
在一个实施例中，针对非SR取消免除逻辑信道判定缓存状态报告BSR的当前状态为缓存状态报告BSR已被组装之后，还可确定非SR取消免除逻辑信道上发送的缓存状态报告BSR是否包括SR取消免除逻辑信道上的缓存大小。若确定非SR取消免除逻辑信道上发送的缓存状态报告BSR不包括SR取消免除逻辑信道上的缓存大小时，免除取消SR取消免除逻辑信道上的调度请求SR。
本实施例中，能够针对非SR取消免除逻辑信道判定缓存状态报告BSR被组装，且非SR取消免除逻辑信道上发送的缓存状态报告BSR不包括SR取消免除逻辑信道上的缓存大小时，免除取消SR取消免除逻辑信道上的调度请求SR，进而更加完善了调度请求SR的取消免除机制。
基于上述实施例，在免除取消SR取消免除逻辑信道上的调度请求SR之后，当该SR取消免除逻辑信道上的调度请求资源到达时，发送该SR取消免除逻辑信道上的调度请求SR。
本实施例中，能够在SR取消免除逻辑信道上的调度请求资源到达时发送该逻辑信道上的被免除取消的调度请求SR，使得SR取消免除逻辑信道上的调 度请求SR在免除取消之后可继续被发送，从而不仅完善了调度请求SR的取消免除机制。并且，由于调度请求资源的到达使得终端设备需发送调度请求SR，因此该技术方案还能够在需要发送调度请求SR时继续发送被免除取消的调度请求SR，从而减小时延，极大地提高了系统性能。
在一个实施例中，确定是否取消被触发的调度请求SR和/或停止SR禁止计时器时，针对SR取消免除逻辑信道，判断SR取消免除逻辑信道触发的缓存状态报告BSR的当前状态是否为缓存状态报告BSR已被组装或发送，若是，则取消SR取消免除逻辑信道上的调度请求SR和/或停止SR禁止计时器。即，针对SR取消免除逻辑信道，只有在其本身信道所触发的缓存状态报告BSR被组装或发送时，才会取消该SR取消免除逻辑信道上的调度请求SR和/或停止SR禁止计时器。
本实施例中，仅在SR取消免除逻辑信道本身所触发的缓存状态报告BSR被组装或发送时，才会取消该SR取消免除逻辑信道上的调度请求SR和/或停止SR禁止计时器，使得SR取消免除逻辑信道上的调度请求SR的取消机制更加完善。
在一个实施例中，在取消SR取消免除逻辑信道上的调度请求SR和/或停止SR禁止计时器之前，还可确定SR取消免除逻辑信道上的所有待发送数据均已被组装或发送。即，除确定SR取消免除逻辑信道触发的缓存状态报告BSR已被组装或发送之外，若确定SR取消免除逻辑信道上的所有待发送数据均已被组装或发送，也可取消SR取消免除逻辑信道上的调度请求SR和/或停止SR禁止计时器。
本实施例中，能够在SR取消免除逻辑信道上的所有待发送数据均已被组装或发送时取消该SR取消免除逻辑信道上的调度请求SR和/或停止SR禁止计时器，由于SR取消免除逻辑信道上的所有待发送数据均已被组装或发送时已无需再发送调度请求SR，因此这种情况下取消调度请求SR可避免不必要的调度请求SR占用资源，完善了SR取消免除逻辑信道上的调度请求SR的取消 机制。
以下通过几个具体实施例来说明本申请提供的调度请求的处理方法。
实施例一
图2是本申请的具体实施例一中的一种调度请求的处理方法的流程图。图2的方法由终端设备执行，可包括：
步骤S201，针对非SR取消免除逻辑信道，确定缓存状态报告BSR被组装。
步骤S202，确定非SR取消免除逻辑信道上发送的缓存状态报告BSR不包括SR取消免除逻辑信道上的缓存大小。
步骤S203，免除取消SR取消免除逻辑信道上的调度请求SR。
步骤S204，当SR取消免除逻辑信道上的调度请求资源到达时，发送该SR取消免除逻辑信道上的调度请求SR。
本实施例一中，SR取消免除逻辑信道由网络侧预先配置。网络侧预先配置至少一个逻辑信道为SR取消免除逻辑信道时，该至少一个逻辑信道需满足以下条件中的至少一项：
(1)逻辑信道对应的子载波间隔大于预设阈值。
例如，预设阈值为15KHz，则逻辑信道对应的子载波间隔可以是15KHz、60KHz、240KHz等。
(2)逻辑信道对应的业务为指定低时延业务。
其中，指定低时延业务如URLLC业务。
(3)逻辑信道执行独立的调度请求过程。
本实施例一能够在非SR取消免除逻辑信道上发送调度请求SR之后，导致缓存状态报告BSR被组装，且非SR取消免除逻辑信道上发送的缓存状态报告BSR不包括SR取消免除逻辑信道上的缓存大小时，免除取消SR取消免除逻辑信道上的调度请求SR，进而更加完善了调度请求SR的取消免除机制。并且，能够在SR取消免除逻辑信道上的调度请求资源到达时发送该逻辑信道上 的被免除取消的调度请求SR，由于调度请求资源的到达使得终端设备需发送调度请求SR，因此本实施例一还使得SR取消免除逻辑信道上的调度请求SR在免除取消之后可继续被发送，从而减小时延，极大地提高了系统性能。
实施例二
图3是本申请的具体实施例二中的一种调度请求的处理方法的流程图。图3的方法由终端设备执行，可包括：
步骤S301，判断SR取消免除逻辑信道触发的缓存状态报告BSR是否已被组装或发送。若是，则执行步骤S302；若否，则执行步骤S303。
步骤S302，取消SR取消免除逻辑信道上的调度请求SR并停止SR禁止计时器。
步骤S303，不取消SR取消免除逻辑信道上的调度请求SR。
本实施例二中，SR取消免除逻辑信道由网络侧预先配置。网络侧预先配置至少一个逻辑信道为SR取消免除逻辑信道时，该至少一个逻辑信道需满足以下条件中的至少一项：
(1)逻辑信道对应的子载波间隔大于预设阈值。
例如，预设阈值为15KHz，则逻辑信道对应的子载波间隔可以是15KHz、60KHz、240KHz等。
(2)逻辑信道对应的业务为指定低时延业务。
其中，指定低时延业务如URLLC业务。
(3)逻辑信道执行独立的调度请求过程。
本实施例二仅在SR取消免除逻辑信道本身所触发的缓存状态报告BSR被组装或发送时，才会取消该SR取消免除逻辑信道上的调度请求SR并停止SR禁止计时器，使得SR取消免除逻辑信道上的调度请求SR的取消机制更加完善，避免其他逻辑信道上的缓存状态报告BSR的当前状态对是否取消SR取消免除逻辑信道上的调度请求SR的影响。
实施例三
图4是本申请的具体实施例三中的一种调度请求的处理方法的流程图。图4的方法由终端设备执行，可包括：
步骤S401，确定缓存状态报告BSR已被发送。
步骤S402，取消被触发的所有调度请求SR并停止SR禁止计时器。
本实施例三能够在缓存状态报告BSR已被发送时，取消被触发的所有调度请求SR并停止SR禁止计时器。由于缓存状态报告BSR已被发送时无需再发送调度请求SR，此时取消被触发的所有调度请求SR能够避免不必要的调度请求SR占用资源，进而使得调度请求SR的取消机制更加完善。
上述对本说明书特定实施例进行了描述。其它实施例在所附权利要求书的范围内。在一些情况下，在权利要求书中记载的动作或步骤可以按照不同于实施例中的顺序来执行并且仍然可以实现期望的结果。另外，在附图中描绘的过程不一定要求示出的特定顺序或者连续顺序才能实现期望的结果。在某些实施方式中，多任务处理和并行处理也是可以的或者可能是有利的。
图5是本申请的一个实施例中终端设备的结构示意图。请参考图5，终端设备可包括：
第一确定模块510，用于根据缓存状态报告BSR的当前状态，确定是否取消被触发的调度请求SR和/或停止SR禁止计时器。
在一个实施例中，缓存状态报告BSR包含最近一次触发缓存状态报告BSR时的缓存状态。
在一个实施例中，第一确定模块510包括：
第一确定单元，用于若缓存状态报告BSR的当前状态为缓存状态报告BSR已被组装或发送，则取消用于组装或发送缓存状态报告BSR的资源对应的调度请求SR和/或停止SR禁止计时器。
在一个实施例中，资源包括：
SR配置对应的数值配置资源、带宽部分资源BWP、成员载波资源CC中的至少一项；或，
SR配置对应的逻辑信道所对应的数值配置资源、带宽部分资源BWP、成员载波资源CC中的至少一项。
在一个实施例中，第一确定模块510包括：
第一取消单元，用于若缓存状态报告BSR的当前状态为缓存状态报告BSR已被发送，则取消被触发的所有调度请求SR和/或停止SR禁止计时器。
在一个实施例中，上述终端设备还包括：
第二确定模块，用于根据用于承载所述调度请求SR的逻辑信道的类型，确定是否取消被触发的调度请求SR和/或停止SR禁止计时器，所述逻辑信道的类型用于指示所述逻辑信道是否为SR取消免除逻辑信道。
在一个实施例中，第一确定模块510包括：
第一判断单元，用于针对除SR取消免除逻辑信道之外的非SR取消免除逻辑信道，判断缓存状态报告BSR的当前状态是否为缓存状态报告BSR已被组装；
免除取消单元，用于若缓存状态报告BSR的当前状态为缓存状态报告BSR已被组装，则免除取消SR取消免除逻辑信道上的调度请求SR。
在一个实施例中，第一确定模块510还包括：
第二确定单元，用于在免除取消SR取消免除逻辑信道上的调度请求SR之前，确定非SR取消免除逻辑信道上发送的缓存状态报告BSR不包括SR取消免除逻辑信道上的缓存大小。
在一个实施例中，第一确定模块510还包括：
发送单元，用于在免除取消SR取消免除逻辑信道上的调度请求SR之后，当SR取消免除逻辑信道上的调度请求资源到达时，发送SR取消免除逻辑信道上的调度请求SR。
在一个实施例中，第一确定模块510包括：
第二判断单元，用于针对所述SR取消免除逻辑信道，判断SR取消免除逻辑信道触发的缓存状态报告BSR的当前状态是否为缓存状态报告BSR已被 组装或发送；
第二取消单元，用于若SR取消免除逻辑信道触发的缓存状态报告BSR的当前状态为缓存状态报告BSR已被组装或发送，则取消SR取消免除逻辑信道上的调度请求SR和/或停止SR禁止计时器。
在一个实施例中，第一确定模块510还包括：
第三确定单元，用于在取消SR取消免除逻辑信道上的调度请求SR和/或停止SR禁止计时器之前，确定SR取消免除逻辑信道上的所有待发送数据均已被组装或发送。
在一个实施例中，SR取消免除逻辑信道满足以下条件中的至少一项：
逻辑信道对应的子载波间隔大于预设阈值；
逻辑信道对应的业务为指定低时延业务；
逻辑信道执行独立的调度请求过程。
采用本申请实施例提供的终端设备，能够根据缓存状态报告BSR的当前状态，确定是否取消被触发的调度请求SR和/或停止SR禁止计时器。因此，该技术方案完善了调度请求SR的取消/取消免除机制，尤其是应用于NR系统中时，能够降低时延敏感业务(如URLLC业务)的时延，从而提高系统性能。
本发明实施例提供的终端设备能够实现图1至图4的方法实施例中终端设备实现的各个过程，为避免重复，这里不再赘述。
图6是本发明另一个实施例的终端设备的框图。图6所示的终端设备600包括：至少一个处理器601、存储器602、至少一个网络接口604和用户接口603。终端设备600中的各个组件通过总线系统605耦合在一起。可理解，总线系统605用于实现这些组件之间的连接通信。总线系统605除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。但是为了清楚说明起见，在图6中将各种总线都标为总线系统605。
其中，用户接口603可以包括显示器、键盘或者点击设备(例如，鼠标，轨迹球(trackball)、触感板或者触摸屏等。
可以理解，本发明实施例中的存储器602可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double DataRate SDRAM，DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(DirectRambus RAM，DRRAM)。本发明实施例描述的系统和方法的存储器602旨在包括但不限于这些和任意其它适合类型的存储器。
在一些实施方式中，存储器602存储了如下的元素，可执行模块或者数据结构，或者他们的子集，或者他们的扩展集：操作系统6021和应用程序6022。
其中，操作系统6021，包含各种系统程序，例如框架层、核心库层、驱动层等，用于实现各种基础业务以及处理基于硬件的任务。应用程序6022，包含各种应用程序，例如媒体播放器(Media Player)、浏览器(Browser)等，用于实现各种应用业务。实现本发明实施例方法的程序可以包含在应用程序6022中。
在本发明实施例中，终端设备600还包括：存储在存储器上609并可在处理器610上运行的计算机程序，计算机程序被处理器601执行时实现如下步骤：
根据缓存状态报告BSR的当前状态，确定是否取消被触发的调度请求SR和/或停止SR禁止计时器。
上述本发明实施例揭示的方法可以应用于处理器601中，或者由处理器601实现。处理器601可能是一种集成电路芯片，具有信号的处理能力。在实 现过程中，上述方法的各步骤可以通过处理器601中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器601可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本发明实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本发明实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的计算机可读存储介质中。该计算机可读存储介质位于存储器602，处理器601读取存储器602中的信息，结合其硬件完成上述方法的步骤。具体地，该计算机可读存储介质上存储有计算机程序，计算机程序被处理器601执行时实现如上述调度请求的处理方法实施例的各步骤。
可以理解的是，本发明实施例描述的这些实施例可以用硬件、软件、固件、中间件、微码或其组合来实现。对于硬件实现，处理单元可以实现在一个或多个专用集成电路(Application Specific Integrated Circuits，ASIC)、数字信号处理器(Digital Signal Processing，DSP)、数字信号处理设备(DSP Device，DSPD)、可编程逻辑设备(Programmable Logic Device，PLD)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)、通用处理器、控制器、微控制器、微处理器、用于执行本申请所述功能的其它电子单元或其组合中。
对于软件实现，可通过执行本发明实施例所述功能的模块(例如过程、函数等)来实现本发明实施例所述的技术。软件代码可存储在存储器中并通过处理器执行。存储器可以在处理器中或在处理器外部实现。
可选的，所述缓存状态报告BSR包含最近一次触发所述缓存状态报告BSR时的缓存状态。
可选的，计算机程序被处理器601执行时还可实现如下步骤：
若所述缓存状态报告BSR的当前状态为所述缓存状态报告BSR已被组装或发送，则取消用于组装或发送所述缓存状态报告BSR的资源上的调度请求SR和/或停止SR禁止计时器。
可选的，所述资源包括：
SR配置对应的数值配置资源、带宽部分资源BWP、成员载波资源CC中的至少一项；或，
SR配置对应的逻辑信道所对应的数值配置资源、带宽部分资源BWP、成员载波资源CC中的至少一项。
可选的，计算机程序被处理器601执行时还可实现如下步骤：
若所述缓存状态报告BSR的当前状态为所述缓存状态报告BSR已被发送，则取消被触发的所有调度请求SR和/或停止SR禁止计时器
可选的，计算机程序被处理器601执行时还可实现如下步骤：
根据用于承载所述调度请求SR的逻辑信道的类型，确定是否取消被触发的调度请求SR和/或停止SR禁止计时器，所述逻辑信道的类型用于指示所述逻辑信道是否为SR取消免除逻辑信道。
可选的，计算机程序被处理器601执行时还可实现如下步骤：
针对除所述SR取消免除逻辑信道之外的非SR取消免除逻辑信道，判断所述缓存状态报告BSR的当前状态是否为所述缓存状态报告BSR已被组装；
若是，则免除取消所述SR取消免除逻辑信道上的调度请求SR。
可选的，计算机程序被处理器601执行时还可实现如下步骤：
在所述免除取消所述SR取消免除逻辑信道上的调度请求SR之前，确定所述非SR取消免除逻辑信道上发送的缓存状态报告BSR不包括所述SR取消免除逻辑信道上的缓存大小。
可选的，计算机程序被处理器601执行时还可实现如下步骤：
在所述免除取消所述SR取消免除逻辑信道上的调度请求SR之后，当所 述SR取消免除逻辑信道上的调度请求资源到达时，发送所述SR取消免除逻辑信道上的调度请求SR。
可选的，计算机程序被处理器601执行时还可实现如下步骤：
针对所述SR取消免除逻辑信道，判断所述SR取消免除逻辑信道触发的缓存状态报告BSR的当前状态是否为所述缓存状态报告BSR已被组装或发送；
若是，则取消所述SR取消免除逻辑信道上的调度请求SR和/或停止SR禁止计时器。
可选的，计算机程序被处理器601执行时还可实现如下步骤：
在所述取消所述SR取消免除逻辑信道上的调度请求SR和/或停止SR禁止计时器之前，确定所述SR取消免除逻辑信道上的所有待发送数据均已被组装或发送。
可选的，所述SR取消免除逻辑信道满足以下条件中的至少一项：
逻辑信道对应的子载波间隔大于预设阈值；
逻辑信道对应的业务为指定低时延业务；
逻辑信道执行独立的调度请求过程。
终端设备600能够实现前述实施例中终端设备实现的各个过程，为避免重复，这里不再赘述。
采用本申请实施例提供的终端设备，能够根据缓存状态报告BSR的当前状态确定是否取消被触发的调度请求SR和/或停止SR禁止计时器。因此，该技术方案完善了调度请求SR的取消/取消免除机制，尤其是应用于NR系统中时，能够降低时延敏感业务(如URLLC业务)的时延，从而提高系统性能。
本领域内的技术人员应明白，本发明的实施例可提供为方法、系统、或计算机程序产品。因此，本发明可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
在一个典型的配置中，计算设备包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光 盘(DVD)或其他光学存储、磁盒式磁带，磁带磁磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
本领域技术人员应明白，本申请的实施例可提供为方法、系统或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
以上所述仅为本申请的实施例而已，并不用于限制本申请。对于本领域技术人员来说，本申请可以有各种更改和变化。凡在本申请的精神和原理之内所作的任何修改、等同替换、改进等，均应包含在本申请的权利要求范围之内。

Claims (26)

  1. 一种调度请求的处理方法，其特征在于，由终端设备执行，所述方法包括：
    根据缓存状态报告BSR的当前状态，确定是否取消被触发的调度请求SR和/或停止SR禁止计时器。
  2. 根据权利要求1所述的方法，其特征在于，所述缓存状态报告BSR包含最近一次触发所述缓存状态报告BSR时的缓存状态。
  3. 根据权利要求1或2所述的方法，其特征在于，所述确定是否取消被触发的调度请求SR和/或停止SR禁止计时器，包括：
    若所述缓存状态报告BSR的当前状态为所述缓存状态报告BSR已被组装或发送，则取消用于组装或发送所述缓存状态报告BSR的资源对应的调度请求SR和/或停止SR禁止计时器。
  4. 根据权利要求3所述的方法，其特征在于，所述资源包括：
    SR配置对应的数值配置资源、带宽部分资源BWP、成员载波资源CC中的至少一项；或，
    SR配置对应的逻辑信道所对应的数值配置资源、带宽部分资源BWP、成员载波资源CC中的至少一项。
  5. 根据权利要求2所述的方法，其特征在于，所述确定是否取消被触发的调度请求SR和/或停止SR禁止计时器，包括：
    若所述缓存状态报告BSR的当前状态为所述缓存状态报告BSR已被发送，则取消被触发的所有调度请求SR和/或停止SR禁止计时器。
  6. 根据权利要求2所述的方法，其特征在于，还包括：
    根据用于承载所述调度请求SR的逻辑信道的类型，确定是否取消被触发的调度请求SR和/或停止SR禁止计时器，所述逻辑信道的类型用于指示所述逻辑信道是否为SR取消免除逻辑信道。
  7. 根据权利要求6所述的方法，其特征在于，所述确定是否取消被触发 的调度请求SR和/或停止SR禁止计时器，包括：
    针对除所述SR取消免除逻辑信道之外的非SR取消免除逻辑信道，判断所述缓存状态报告BSR的当前状态是否为所述缓存状态报告BSR已被组装；
    若是，则免除取消所述SR取消免除逻辑信道上的调度请求SR。
  8. 根据权利要求7所述的方法，其特征在于，在所述免除取消所述SR取消免除逻辑信道上的调度请求SR之前，还包括：
    确定所述非SR取消免除逻辑信道上发送的缓存状态报告BSR不包括所述SR取消免除逻辑信道上的缓存大小。
  9. 根据权利要求7所述的方法，其特征在于，在所述免除取消所述SR取消免除逻辑信道上的调度请求SR之后，还包括：
    当所述SR取消免除逻辑信道上的调度请求资源到达时，发送所述SR取消免除逻辑信道上的调度请求SR。
  10. 根据权利要求6所述的方法，其特征在于，所述确定是否取消被触发的调度请求SR和/或停止SR禁止计时器，包括：
    针对所述SR取消免除逻辑信道，判断所述SR取消免除逻辑信道触发的缓存状态报告BSR的当前状态是否为所述缓存状态报告BSR已被组装或发送；
    若是，则取消所述SR取消免除逻辑信道上的调度请求SR和/或停止SR禁止计时器。
  11. 根据权利要求10所述的方法，其特征在于，在所述取消所述SR取消免除逻辑信道上的调度请求SR和/或停止SR禁止计时器之前，还包括：
    确定所述SR取消免除逻辑信道上的所有待发送数据均已被组装或发送。
  12. 根据权利要求6-11中任一项所述的方法，其特征在于，所述SR取消免除逻辑信道满足以下条件中的至少一项：
    逻辑信道对应的子载波间隔大于预设阈值；
    逻辑信道对应的业务为指定低时延业务；
    逻辑信道执行独立的调度请求过程。
  13. 一种终端设备，其特征在于，包括：
    第一确定模块，用于根据缓存状态报告BSR的当前状态，确定是否取消被触发的调度请求SR和/或停止SR禁止计时器。
  14. 根据权利要求13所述的终端设备，其特征在于，所述缓存状态报告BSR包含最近一次触发所述缓存状态报告BSR时的缓存状态。
  15. 根据权利要求13或14所述的终端设备，其特征在于，所述第一确定模块包括：
    第一确定单元，用于若所述缓存状态报告BSR的当前状态为所述缓存状态报告BSR已被组装或发送，则取消用于组装或发送所述缓存状态报告BSR的资源对应的调度请求SR和/或停止SR禁止计时器。
  16. 根据权利要求15所述的终端设备，其特征在于，所述资源包括：
    SR配置对应的数值配置资源、带宽部分资源BWP、成员载波资源CC中的至少一项；或，
    SR配置对应的逻辑信道所对应的数值配置资源、带宽部分资源BWP、成员载波资源CC中的至少一项。
  17. 根据权利要求14所述的终端设备，其特征在于，所述第一确定模块包括：
    第一取消单元，用于若所述缓存状态报告BSR的当前状态为所述缓存状态报告BSR已被发送，则取消被触发的所有调度请求SR和/或停止SR禁止计时器。
  18. 根据权利要求14所述的终端设备，其特征在于，还包括：
    第二确定模块，用于根据用于承载所述调度请求SR的逻辑信道的类型，确定是否取消被触发的调度请求SR和/或停止SR禁止计时器，所述逻辑信道的类型用于指示所述逻辑信道是否为SR取消免除逻辑信道。
  19. 根据权利要求18所述的终端设备，其特征在于，所述第一确定模块包括：
    第一判断单元，用于针对除所述SR取消免除逻辑信道之外的非SR取消免除逻辑信道，判断所述缓存状态报告BSR的当前状态是否为所述缓存状态报告BSR已被组装；
    免除取消单元，用于若所述缓存状态报告BSR的当前状态为所述缓存状态报告BSR已被组装，则免除取消所述SR取消免除逻辑信道上的调度请求SR。
  20. 根据权利要求19所述的终端设备，其特征在于，所述第一确定模块还包括：
    第二确定单元，用于在所述免除取消所述SR取消免除逻辑信道上的调度请求SR之前，确定所述非SR取消免除逻辑信道上发送的缓存状态报告BSR不包括所述SR取消免除逻辑信道上的缓存大小。
  21. 根据权利要求19所述的终端设备，其特征在于，所述第一确定模块还包括：
    发送单元，用于在所述免除取消所述SR取消免除逻辑信道上的调度请求SR之后，当所述SR取消免除逻辑信道上的调度请求资源到达时，发送所述SR取消免除逻辑信道上的调度请求SR。
  22. 根据权利要求18所述的终端设备，其特征在于，所述第一确定模块包括：
    第二判断单元，用于针对所述SR取消免除逻辑信道，判断所述SR取消免除逻辑信道触发的缓存状态报告BSR的当前状态是否为所述缓存状态报告BSR已被组装或发送；
    第二取消单元，用于若所述SR取消免除逻辑信道触发的缓存状态报告BSR的当前状态为所述缓存状态报告BSR已被组装或发送，则取消所述SR取消免除逻辑信道上的调度请求SR和/或停止SR禁止计时器。
  23. 根据权利要求22所述的终端设备，其特征在于，所述第一确定模块还包括：
    第三确定单元，用于在所述取消所述SR取消免除逻辑信道上的调度请求SR和/或停止SR禁止计时器之前，确定所述SR取消免除逻辑信道上的所有待发送数据均已被组装或发送。
  24. 根据权利要求18-23中任一项所述的终端设备，其特征在于，所述SR取消免除逻辑信道满足以下条件中的至少一项：
    逻辑信道对应的子载波间隔大于预设阈值；
    逻辑信道对应的业务为指定低时延业务；
    逻辑信道执行独立的调度请求过程。
  25. 一种终端设备，其特征在于，包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如权利要求1至12中任一项所述的调度请求的处理方法的步骤。
  26. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储计算机程序，所述计算机程序被处理器执行时实现如权利要求1至12中任一项所述的调度请求的处理方法的步骤。
PCT/CN2018/102553 2017-09-28 2018-08-27 调度请求的处理方法及终端设备 WO2019062422A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US16/652,095 US11184912B2 (en) 2017-09-28 2018-08-27 Scheduling request processing method and user equipment
EP18863220.2A EP3691390B1 (en) 2017-09-28 2018-08-27 Scheduling request processing method and terminal device
ES18863220T ES2944437T3 (es) 2017-09-28 2018-08-27 Método de procesamiento de solicitud de planificación y dispositivo terminal

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710900929.3A CN109587805B (zh) 2017-09-28 2017-09-28 调度请求的处理方法及终端设备
CN201710900929.3 2017-09-28

Publications (1)

Publication Number Publication Date
WO2019062422A1 true WO2019062422A1 (zh) 2019-04-04

Family

ID=65900512

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/102553 WO2019062422A1 (zh) 2017-09-28 2018-08-27 调度请求的处理方法及终端设备

Country Status (5)

Country Link
US (1) US11184912B2 (zh)
EP (1) EP3691390B1 (zh)
CN (1) CN109587805B (zh)
ES (1) ES2944437T3 (zh)
WO (1) WO2019062422A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019051765A1 (zh) * 2017-09-15 2019-03-21 Oppo广东移动通信有限公司 一种调度请求的配置方法、网络设备及终端设备
CN114026946A (zh) * 2019-06-28 2022-02-08 中兴通讯股份有限公司 针对辅小区的波束故障恢复

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104170491A (zh) * 2012-03-19 2014-11-26 阿尔卡特朗讯 用于配置多个调度请求触发的方法和装置
CN104320857A (zh) * 2009-05-05 2015-01-28 瑞典爱立信有限公司 处理调度请求触发
CN107079469A (zh) * 2014-11-05 2017-08-18 Lg 电子株式会社 在d2d通信系统中取消通过侧链路缓冲器状态报告触发的调度请求的方法及其设备

Family Cites Families (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101771521B (zh) * 2009-01-06 2013-11-06 中兴通讯股份有限公司 一种缓冲区状态报告重传定时器的管理方法
CN102474880B (zh) * 2009-06-29 2016-01-06 瑞典爱立信有限公司 无线通信系统中的方法和布置
KR101164117B1 (ko) * 2009-09-04 2012-07-12 엘지전자 주식회사 무선 통신 시스템상에서 물리 하향 채널의 모니터링 동작을 효율적으로 제어하는 방법
JP2011155335A (ja) * 2010-01-26 2011-08-11 Sharp Corp 通信システム及び移動局装置及び基地局装置及び処理方法
JP2011155334A (ja) * 2010-01-26 2011-08-11 Sharp Corp 通信システム及び移動局装置及び基地局装置及び処理方法
JP2011155336A (ja) * 2010-01-26 2011-08-11 Sharp Corp 通信システム及び移動局装置及び基地局装置及び処理方法
US9065545B2 (en) * 2012-03-12 2015-06-23 Blackberry Limited Handling scheduling request collisions with an ACK/NACK repetition signal
EP2802185B1 (en) * 2013-04-01 2019-11-13 Innovative Sonic Corporation Method and Apparatus for Adding Serving Cells in a Wireless Communication System
US9585134B2 (en) * 2013-12-13 2017-02-28 Sharp Kabushiki Kaisha Systems and methods for multi-connectivity operation
US9756678B2 (en) * 2013-12-13 2017-09-05 Sharp Kabushiki Kaisha Systems and methods for multi-connectivity operation
CN106105306B (zh) * 2014-03-19 2019-12-06 Lg电子株式会社 在无线通信系统中确定缓冲器状态报告的优先级的方法和装置
KR101726705B1 (ko) * 2014-12-01 2017-04-26 아서스테크 컴퓨터 인코포레이션 무선 통신 시스템에서 스케줄링 요청(sr)에 대한 금지 타이머를 처리하기 위한 방법 및 장치
US10142880B2 (en) * 2014-12-03 2018-11-27 Lg Electronics Inc. Method and apparatus for configuring scheduling request prohibit timer for prose priority in wireless communication system
WO2016157809A1 (en) * 2015-03-27 2016-10-06 Sharp Kabushiki Kaisha Systems and methods for a physical uplink control channel on a secondary cell
EP3275266B1 (en) * 2015-03-27 2020-04-29 Sharp Kabushiki Kaisha Systems and methods for a physical uplink control channel on a secondary cell
CN107409394B (zh) * 2015-03-27 2021-10-12 夏普株式会社 辅小区上的物理上行链路控制信道的系统及方法
CN107409412B (zh) * 2015-03-27 2021-06-29 夏普株式会社 用于辅小区上的物理上行控制信道的系统和方法
WO2016182344A1 (en) * 2015-05-12 2016-11-17 Lg Electronics Inc. Method for transmitting a contention-based pusch in a wireless communication system and a device therefor
US10200177B2 (en) * 2015-06-12 2019-02-05 Comcast Cable Communications, Llc Scheduling request on a secondary cell of a wireless device
US9894681B2 (en) * 2015-06-12 2018-02-13 Ofinno Technologies, Llc Uplink scheduling in a wireless device and wireless network
WO2017007148A1 (en) * 2015-07-06 2017-01-12 Lg Electronics Inc. Method for cancelling a buffer status report or a scheduling request in dual connectivity and a device therefor
GB2542172A (en) * 2015-09-10 2017-03-15 Nec Corp Communication system
US10912145B2 (en) * 2016-04-15 2021-02-02 Lg Electronics Inc. Method for performing transmission of a SR bundle in a wireless communication system and a device therefor
CN108811146B (zh) * 2017-05-04 2020-08-28 维沃移动通信有限公司 上行调度请求处理方法及装置
US10524294B2 (en) * 2017-05-04 2019-12-31 Ofinno, Llc Scheduling request transmission

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104320857A (zh) * 2009-05-05 2015-01-28 瑞典爱立信有限公司 处理调度请求触发
CN104170491A (zh) * 2012-03-19 2014-11-26 阿尔卡特朗讯 用于配置多个调度请求触发的方法和装置
CN107079469A (zh) * 2014-11-05 2017-08-18 Lg 电子株式会社 在d2d通信系统中取消通过侧链路缓冲器状态报告触发的调度请求的方法及其设备

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3GPP TSG-RAN WG2 Meeting #99, R2-1708556", SR CONFIGURATION AND TRIGGERING FOR STTI, 25 August 2017 (2017-08-25), XP051318408 *
"3GPP TSG-RAN WG2 Meeting #99, R2-1709416", SR CANCELLATION FOR STTI, 25 August 2017 (2017-08-25), XP051319144 *
See also references of EP3691390A4 *

Also Published As

Publication number Publication date
EP3691390A1 (en) 2020-08-05
US20200305181A1 (en) 2020-09-24
CN109587805A (zh) 2019-04-05
CN109587805B (zh) 2021-02-19
EP3691390A4 (en) 2020-11-04
EP3691390B1 (en) 2023-04-26
US11184912B2 (en) 2021-11-23
ES2944437T3 (es) 2023-06-21

Similar Documents

Publication Publication Date Title
WO2019137481A1 (zh) Harq-ack反馈时间的确定方法和指示方法、终端设备和网络设备
JP2021519045A (ja) アップリンク伝送方法及び装置
WO2019127035A1 (zh) 激活与去激活辅小区的方法和终端设备
US12015559B2 (en) Service processing method, device, chip, and computer program
WO2018233521A1 (zh) 数据传输方法、基站和用户终端
WO2019157754A1 (zh) 上行数据的调度方法和设备
WO2019154265A1 (zh) 数据传输方法和设备
WO2019061982A1 (zh) 用于资源分配的方法、网络设备和通信设备
WO2021023185A1 (zh) 一种接入限制检测方法和装置
WO2019062422A1 (zh) 调度请求的处理方法及终端设备
US11122584B2 (en) Method and device for transmitting uplink data
WO2019157675A1 (zh) 无线通信方法和设备
WO2021026846A1 (zh) 无线通信的方法、终端设备和网络设备
JP2023539320A (ja) ダウンリンク伝送方法および通信装置
CN109327857B (zh) 一种bsr取消方法和用户终端
US11968701B2 (en) Network scheduling in unlicensed spectrums
WO2021004374A1 (zh) 数据发送的方法、数据接收的方法和设备
WO2019075762A1 (zh) 传输调度请求的方法和终端设备
WO2020088520A1 (zh) 上行传输方法和终端设备
WO2020020057A1 (zh) 用于半静态授权上行传输的方法、终端设备和网络侧设备
WO2019076226A1 (zh) 一种多载波中数据传输的方法及装置
WO2019080034A1 (zh) 用于数据传输的方法、终端设备和网络设备
WO2020199004A1 (zh) 通信方法和终端设备
WO2021031128A1 (zh) 传输数据的方法、终端设备和网络设备
WO2021026847A1 (zh) 无线通信的方法和设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18863220

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018863220

Country of ref document: EP

Effective date: 20200428