WO2019128308A1 - 一种进行调度请求的方法和设备 - Google Patents

一种进行调度请求的方法和设备 Download PDF

Info

Publication number
WO2019128308A1
WO2019128308A1 PCT/CN2018/104898 CN2018104898W WO2019128308A1 WO 2019128308 A1 WO2019128308 A1 WO 2019128308A1 CN 2018104898 W CN2018104898 W CN 2018104898W WO 2019128308 A1 WO2019128308 A1 WO 2019128308A1
Authority
WO
WIPO (PCT)
Prior art keywords
bwp
random access
change
terminal
changed
Prior art date
Application number
PCT/CN2018/104898
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 KR1020227029997A priority Critical patent/KR102487369B1/ko
Priority to KR1020207021856A priority patent/KR102439712B1/ko
Priority to JP2020535988A priority patent/JP7030996B2/ja
Priority to EP18893567.0A priority patent/EP3735067B1/en
Priority to US16/958,386 priority patent/US11405947B2/en
Publication of WO2019128308A1 publication Critical patent/WO2019128308A1/zh
Priority to US17/839,416 priority patent/US11825480B2/en

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
    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/535—Allocation or scheduling criteria for wireless resources based on resource usage policies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices

Definitions

  • the present application relates to the field of wireless communication technologies, and in particular, to a method and device for performing a scheduling request.
  • the cell bandwidth of the network side is less than or equal to the terminal receiving bandwidth of 20 MHz. Therefore, the network side always allocates the total uplink and downlink bandwidth of the cell to the terminal, and the terminal can have the entire cell bandwidth. Work on.
  • the bandwidth on the network side can be as high as 400 MHz, which is much larger than the receiving capability of the terminal. Therefore, the concept of a BWP (Band Width Part) is introduced, that is, the large bandwidth on the network side is divided into multiple bandwidth parts BWP, one or more BWPs are configured to the terminal, and a partially configured BWP is activated to perform uplink and downlink operations for the terminal.
  • BWP Band Width Part
  • the activated downlink BWP is called active DL BWP
  • the activated uplink BWP is called active UL BWP.
  • the activated downlink BWP is called active DL BWP
  • the activated uplink BWP is called active UL BWP.
  • the inactive BWP cannot perform uplink and downlink signaling and data transmission.
  • the BWP can be changed by using the Downlink Control Information (DCI), and the BWP can be changed separately.
  • DCI Downlink Control Information
  • the 3GPP (3rd Generation Partnership Project) wireless communication system is a scheduling-based system.
  • the base station allocates time-frequency resources required for data transmission to the terminal device, and the terminal performs downlink data reception according to the scheduling command of the base station or Uplink data is sent.
  • the uplink data transmission is scheduled by the base station, and the base station scheduler notifies the terminal through the UL grant (uplink scheduling permission) after determining the uplink resource allocation situation.
  • the basis for the uplink resource allocation by the base station scheduler is the amount of uplink data to be sent by the terminal, that is, the buffer status of the terminal.
  • the buffer is on the terminal side. If the base station wants to know the information, the terminal needs to perform a BSR (Buffer state report) to the base station.
  • BSR Buffer state report
  • the SR scheduling request
  • D-SR the SR
  • RA-SR the SR
  • the present application provides a method and a device for performing a scheduling request, which is to solve the problem that if a network side configuration terminal performs BWP change in the prior art, there is no solution to how the ongoing SR process is handled.
  • a method for performing a scheduling request according to an embodiment of the present application includes:
  • the terminal determines that a BWP change occurs during the execution of the SR reporting process
  • the terminal performs SR according to the SR configuration on the changed BWP.
  • a terminal for performing a scheduling request is provided by an embodiment of the present application, where the terminal includes: a processor, a memory, and a transceiver.
  • the processor is configured to read a program in the memory and perform the following process:
  • the BWP change is determined during the execution of the SR report; the SR is performed according to the SR configuration on the changed BWP.
  • the terminal includes:
  • a change processing module configured to determine that a BWP change occurs during execution of the SR reporting process
  • the reporting processing module is configured to perform SR according to the SR configuration on the changed BWP.
  • a computer storage medium provided by the embodiment of the present application has a computer program stored thereon, and when the program is executed by the processor, the steps of the method for performing the scheduling request are implemented.
  • the terminal determines that a BWP change needs to be generated during the execution of the SR, the terminal performs the SR according to the SR configuration on the changed BWP. Since the terminal can perform SR according to the SR configuration on the changed BWP, a processing manner for the ongoing SR process after the terminal BWP is changed is given; the performance of the system is further improved.
  • FIG. 1 is a schematic flowchart of a method for scheduling a request according to an embodiment of the present application
  • FIG. 2 is a schematic structural diagram of a first terminal according to an embodiment of the present application.
  • FIG. 3 is a schematic structural diagram of a second terminal according to an embodiment of the present application.
  • FIG. 4 is a schematic flowchart of a scheduling request method without a dedicated SR configuration after a dedicated SR configuration change before the change of the embodiment of the present application;
  • FIG. 5 is a schematic flowchart of a scheduling request method with a dedicated SR configuration after a change of a dedicated SR configuration before the change in the embodiment of the present application.
  • the method for scheduling a request in this embodiment of the present application includes:
  • Step 100 The terminal determines that a BWP change occurs during the execution of the SR reporting process.
  • Step 101 The terminal performs SR according to the SR configuration on the changed BWP.
  • the terminal determines that a BWP change needs to be generated during the execution of the SR, the terminal performs the SR according to the SR configuration on the changed BWP. Since the terminal can perform SR according to the SR configuration on the changed BWP, a processing manner for the ongoing SR process after the terminal BWP is changed is given; the performance of the system is further improved.
  • the terminal performs SR according to the SR configuration on the changed BWP.
  • the logical channel that triggers the SR does not have a corresponding dedicated SR configuration on the changed BWP.
  • the logical channel that triggers the SR is changed. There is a corresponding dedicated SR configuration on the BWP. The following is introduced separately.
  • the logical channel that triggers the SR does not have a corresponding dedicated SR configuration on the changed BWP.
  • the terminal performs SR (ie, RA-SR) through a random access procedure.
  • the terminal can perform the SR through the random access procedure in one of the following ways:
  • the terminal If the terminal has at least one SR inhibit timer running, the terminal is on the changed BWP after the target SR prohibit timer (sr-ProhibitTimer) in the running SR inhibit timer expires. Perform SR through the random access procedure and cancel all pending SRs.
  • target SR prohibit timer sr-ProhibitTimer
  • the terminal currently has multiple pending SRs, and each of the suspended SRs has multiple SR-inhibited timers.
  • the target SR prohibits the timer
  • the random access is performed on the changed BWP. The process proceeds to SR.
  • the target SR disable timer here is the first timeout SR disable timer or the last timeout SR disable timer.
  • the terminal may perform the SR through the random access procedure on the changed BWP after the first timeout SR prohibition timer in the running SR prohibition timer expires;
  • the terminal may perform the SR through the random access procedure on the changed BWP after the SR-inhibition timer of the last one of the running SR-inhibition timers expires.
  • the terminal stops all SR prohibit timers, and sets an SR counter corresponding to the SR inhibit timer to a preset value (SR_COUNTER), for example, SR
  • SR_COUNTER a preset value
  • the terminal After receiving the BWP handover command, the terminal stops all currently running SR prohibition timers, performs SR through the random access procedure on the changed BWP, and cancels all suspended SRs, and sets the SR count value. Set to a preset value, such as setting the SR count value to 0.
  • the terminal currently has multiple pending SRs, and each of the suspended SRs has multiple SR-inhibited timers.
  • all running SR-inhibited timers are stopped and changed.
  • the SR is performed through a random access procedure.
  • the terminal After receiving the BWP switching command, the terminal stops all currently executing SR prohibition timers, and sets the SR counter related to the SR prohibition timer to a preset value, and randomly connects the changed BWP. The process proceeds to SR and all pending SRs are cancelled.
  • the terminal currently has multiple pending SRs, and each of the suspended SRs has multiple SR-inhibited timers.
  • the embodiment of the present application stops all running SR-inhibited timers after receiving the BWP switching command, and will
  • the SR prohibition timer-related SR counter is set to a preset value, and the SR is performed by the random access procedure on the changed BWP.
  • the terminal can perform the SR through the random access procedure in one of the following ways:
  • the terminal does not perform the BWP change, and continues to perform the SR through the random access procedure on the BWP before the change, and then performs the BWP change after the random access succeeds.
  • the terminal receives the BWP handover command and does not perform the BWP handover, but continues to perform the SR through the random access procedure on the BWP before the change.
  • the terminal does not perform the BWP change, continues to perform the SR through the random access procedure on the BWP before the change, performs the BWP change after the Nth random access failure, and continues to pass the random access on the changed BWP.
  • the process performs SR, where N is not greater than the maximum number of random access transmissions.
  • the terminal receives the BWP handover command and does not perform the BWP handover, but continues to perform the SR through the random access procedure on the BWP before the change, and performs the BWP change after the Nth random access fails.
  • the value of N can be set as needed. For example, if it is set to 1, the BWP switch is performed as long as the first random access fails after the BWP is changed, and the SR is requested by the dedicated scheduling request resource on the changed BWP. .
  • the terminal immediately stops the SR through the random access procedure on the BWP before the change, and performs the BWP change, and performs the SR through the random access procedure on the changed BWP.
  • the terminal immediately stops the SR through the random access procedure and performs the BWP change, and performs the SR through the random access procedure on the changed BWP.
  • Mode 2 The logical channel that triggers the SR has a corresponding dedicated SR configuration on the changed BWP.
  • the logical channel that triggers the SR has a corresponding dedicated SR configuration on the changed BWP, and the terminal performs the SR through the random access procedure or the SR through the dedicated scheduling request resource.
  • the terminal can request the resource for the SR through the dedicated scheduling in the following manner:
  • the terminal After the SR prohibit timer expires on the logical channel that triggers the SR, if the SR triggered by the logical channel is in the suspended state, the terminal performs the SR by using the dedicated scheduling request resource on the changed BWP.
  • the terminal continues the SR prohibition timer operation, and after the SR prohibition timer corresponding to the logical channel that triggers the SR times out, if the SR triggered by the logical channel is in the suspended state, the changed BWP is The SR is requested by a dedicated scheduling request resource.
  • the terminal may perform the SR through the random access procedure or request the resource through the dedicated scheduling in one of the following ways:
  • the terminal does not perform the BWP change, continues to perform the SR through the random access procedure on the BWP before the change, and performs the BWP handover after the random access succeeds.
  • the terminal receives the BWP handover command and does not perform the BWP handover, but continues to perform the SR through the random access procedure on the BWP before the change.
  • the terminal does not perform the BWP change, continues to perform the SR through the random access procedure on the BWP before the change, performs the BWP handover after the Nth random access failure, and requests the resource through the dedicated scheduling on the changed BWP. Perform SR, where N is not greater than the maximum number of random access transmissions.
  • the terminal receives the BWP handover command and does not perform the BWP handover, but continues to perform the SR through the random access procedure on the BWP before the change, and performs the BWP handover after the Nth random access failure, and after the change.
  • the SR is requested by a dedicated scheduling request resource.
  • the value of N can be set as needed. For example, if it is set to 1, the BWP switch is performed as long as the first random access fails after the BWP is changed, and the SR is requested by the dedicated scheduling request resource on the changed BWP. .
  • the terminal immediately stops the SR through the random access procedure on the BWP before the change, immediately performs the BWP change, and requests the resource to perform the SR through the dedicated scheduling on the changed BWP.
  • the terminal stops receiving the BWP handover command, stops the SR through the random access procedure, and performs the BWP change, and requests the resource to perform the SR on the changed BWP.
  • the terminal does not send a random access problem indication to the upper layer.
  • a terminal is provided in the embodiment of the present application.
  • the principle of solving the problem is similar to the method for scheduling a request in the embodiment of the present application. Therefore, the implementation of the terminal can refer to the implementation of the method. No longer.
  • the first terminal of the embodiment of the present application includes: a processor 200, a memory 201, and a transceiver 202.
  • the processor 200 is responsible for managing the bus architecture and general processing, and the memory 201 can store data used by the processor 200 when performing operations.
  • the transceiver 202 is configured to receive and transmit data under the control of the processor 200.
  • the bus architecture may include any number of interconnected buses and bridges, specifically linked by one or more processors represented by processor 200 and various circuits of memory represented by memory 201.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be further described herein.
  • the bus interface provides an interface.
  • the processor 200 is responsible for managing the bus architecture and general processing, and the memory 201 can store data used by the processor 200 when performing operations.
  • the flow disclosed in the embodiment of the present application may be applied to the processor 200 or implemented by the processor 200.
  • each step of the signal processing flow may be completed by an integrated logic circuit of hardware in the processor 200 or an instruction in the form of software.
  • the processor 200 can be a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or a transistor logic device, and a discrete hardware component, which can be implemented or executed in the embodiment of the present application.
  • a general purpose processor can be a microprocessor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly implemented as a hardware processor, or may be performed by a combination of hardware and software modules in the processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 201, and the processor 200 reads the information in the memory 201 and completes the steps of the signal processing flow in conjunction with its hardware.
  • the processor 200 is configured to read a program in the memory 201 and perform the following processes:
  • the BWP change is determined during the execution of the SR report; the SR is performed according to the SR configuration on the changed BWP.
  • the processor 200 is specifically configured to:
  • the SR is performed through a random access procedure
  • the SR is performed by the random access procedure or the SR is requested by the dedicated scheduling request resource.
  • the logical channel that triggers the SR has a corresponding dedicated SR configuration on the BWP before the change, and the logical channel that triggers the SR does not have a corresponding dedicated SR configuration on the changed BWP.
  • the processor 200 is specifically configured to:
  • the target SR disables the timer as the first timeout SR disable timer or the last timeout SR disable timer.
  • processor 200 is further configured to:
  • the logical channel that triggers the SR does not have a corresponding dedicated SR configuration on the BWP before the change, and the logical channel that triggers the SR does not have a corresponding dedicated SR configuration on the changed BWP.
  • the processor 200 is specifically configured to:
  • the logical channel that triggers the SR has a corresponding dedicated SR configuration on the BWP before the change, and the logical channel that triggers the SR has a corresponding dedicated SR configuration on the changed BWP.
  • the processor 200 is specifically configured to:
  • the SR prohibition timer corresponding to the logical channel that triggers the SR expires, if the SR triggered by the logical channel is in a suspended state, the SR is requested by the dedicated scheduling request resource on the changed BWP.
  • the logical channel that triggers the SR does not have a corresponding dedicated SR configuration on the BWP before the change, and the logical channel that triggers the SR has a corresponding dedicated SR configuration on the changed BWP.
  • the processor 200 is specifically configured to:
  • the dedicated scheduling request resource performs SR, where N is not greater than the maximum number of random access transmissions; or
  • processor 200 is further configured to:
  • the random access problem indication is not sent to the upper layer.
  • the second terminal in this embodiment of the present application includes:
  • the change processing module 300 is configured to determine that a BWP change occurs during the execution of the SR report process
  • the report processing module 301 is configured to perform SR according to the SR configuration on the changed BWP.
  • the report processing module 301 is specifically configured to:
  • the SR is performed through a random access procedure
  • the SR is performed by the random access procedure or the SR is requested by the dedicated scheduling request resource.
  • the logical channel that triggers the SR has a corresponding dedicated SR configuration on the BWP before the change, and the logical channel that triggers the SR does not have a corresponding dedicated SR configuration on the changed BWP.
  • the report processing module 301 is specifically configured to:
  • the target SR disables the timer as the first timeout SR disable timer or the last timeout SR disable timer.
  • reporting processing module 301 is further configured to:
  • the logical channel that triggers the SR does not have a corresponding dedicated SR configuration on the BWP before the change, and the logical channel that triggers the SR does not have a corresponding dedicated SR configuration on the changed BWP.
  • the report processing module 301 is specifically configured to:
  • the logical channel that triggers the SR has a corresponding dedicated SR configuration on the BWP before the change, and the logical channel that triggers the SR has a corresponding dedicated SR configuration on the changed BWP.
  • the report processing module 301 is specifically configured to:
  • the SR prohibition timer corresponding to the logical channel that triggers the SR expires, if the SR triggered by the logical channel is in a suspended state, the SR is requested by the dedicated scheduling request resource on the changed BWP.
  • the logical channel that triggers the SR does not have a corresponding dedicated SR configuration on the BWP before the change, and the logical channel that triggers the SR has a corresponding dedicated SR configuration on the changed BWP.
  • the report processing module 301 is specifically configured to:
  • the dedicated scheduling request resource performs SR, where N is not greater than the maximum number of random access transmissions; or
  • reporting processing module 301 is further configured to:
  • the random access problem indication is not sent to the upper layer.
  • the embodiment of the present application provides a readable storage medium, which is a non-volatile readable storage medium, including program code, when the program code is run on a computing device, the program code is used to And causing the computing device to perform the action of the foregoing terminal to perform a scheduling request.
  • the logical channel 1 of the terminal is a logical channel that triggers the SR, and the dedicated SR configuration corresponding to the logical channel 1 is present on the BWP 1 , and the logical channel 1 has no corresponding dedicated SR configuration on the BWP 2 .
  • the scheduling request method without a dedicated SR configuration after a dedicated SR configuration change before the change of the embodiment of the present application includes:
  • Step 400 The BWP currently activated by the terminal is BWP 1. At this time, there is a regular (cycle) BSR trigger, and according to the SR trigger condition, it is determined that the regular BSR triggers the SR.
  • Step 401 Since the logical channel 1 that triggers the SR has a corresponding dedicated SR configuration on the BWP1, the terminal performs SR on the BWP1 using the dedicated SR resource, and maintains the sr-ProhibitTimer and the SR_COUNTER based on the dedicated SR.
  • Step 402 During the process of executing the SR by the terminal, the network side notifies the terminal to perform the BWP change.
  • Step 403 The terminal changes the activated BWP from BWP 1 to BWP 2.
  • Step 404 Since the logical channel 2 that triggers the SR does not have a dedicated SR configuration on the BWP 2, the terminal needs to perform the RA-SR.
  • the specific behavior of the terminal is:
  • the terminal If the terminal has at least one SR prohibition timer running, the terminal passes the random access procedure on the changed BWP after the target SR prohibition timer expires in the running SR prohibition timer. Perform SR and cancel all pending SRs.
  • the terminal After receiving the BWP handover command, the terminal stops all currently running SR prohibition timers, performs SR on the changed BWP through the random access procedure, and cancels all suspended SRs.
  • the terminal stops all currently executing SR prohibition timers after receiving the BWP switching command, and sets the SR counter related to the SR prohibition timer to a preset value, and passes the changed BWP.
  • the random access procedure performs SR and cancels all pending SRs.
  • Step 500 The terminal currently activates the BWP as BWP 2. At this time, a regular BSR triggers, and according to the SR trigger condition, it is determined that the regular BSR triggers the SR.
  • Step 501 Since the logical channel 1 that triggers the SR does not have a corresponding dedicated SR configuration on the BWP 2, the terminal performs the SR on the BWP 2 using the RA-SR.
  • Step 502 During the process of executing the SR by the terminal, the network side notifies the terminal to perform the BWP change.
  • Step 503 The terminal changes the activated BWP from BWP 2 to BWP 1.
  • Step 504 Since the logical channel 2 that triggers the SR does not have a dedicated SR configuration on the BWP 2, the terminal may perform the RA-SR or perform the SR (ie, D-SR) through the dedicated scheduling request resource.
  • the terminal specific behavior may be any of the following:
  • the terminal does not perform the BWP change, continues to perform the SR through the random access procedure on the BWP before the change, performs the BWP handover after the random access succeeds, or performs the BWP handover after the Nth random access failure, and is changed.
  • the subsequent BWP requests the resource through the dedicated scheduling resource, where N is not greater than the maximum number of random access transmissions.
  • the terminal immediately stops the SR through the random access procedure on the BWP before the change, immediately performs the BWP change, and requests the resource to perform the SR through the dedicated scheduling on the changed BWP.
  • 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Multi-Process Working Machines And Systems (AREA)

Abstract

本申请实施例涉及一种进行调度请求的方法和设备，用以解决现有技术中存在的如果网络侧配置终端进行BWP变更，对于正在进行的SR过程如何处理目前还没有解决方案的问题。本申请实施例终端在执行SR过程中若确定需要发生BWP变更，则根据变更后的BWP上的SR配置进行SR。由于终端能够根据变更后的BWP上的SR配置进行SR，从而给出了终端BWP变更后对于正在进行的SR过程的一种处理方式；进一步提高了系统的性能。

Description

一种进行调度请求的方法和设备
本申请要求在2017年12月28日提交中国专利局、申请号为201711466570.X、发明名称为“一种进行调度请求的方法和设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及无线通信技术领域，特别涉及一种进行调度请求的方法和设备。
背景技术
在传统LTE(Long Term Evolution，长期演进)系统中，网络侧角度的小区带宽小于或等于终端接收带宽20MHz，因此网络侧总是将小区的上下行总带宽配置给终端，终端可以在整个小区带宽上工作。在NR(New Radio，新空口)系统中，网络侧带宽可以高达400MHz，远远大于终端的接收能力。因此，引入BWP(Band Width Part，频带宽度)的概念，即将网络侧的大带宽划分为多个带宽部分BWP，将一个或多个BWP配置给终端，并激活部分配置的BWP为终端进行上下行传输，激活的下行BWP称为active DL BWP，激活的上行BWP称为active UL BWP。在R15版本中，对终端来说，一个时刻只允许激活一个DL BWP和一个UL BWP，非激活的BWP不能进行上下行信令和数据传输。
网络侧给终端配置多个BWP后，可以使用物理层信令DCI(Downlink Control Information，下行控制信息)变更激活BWP，上下行激活BWP可以分别变更。
3GPP(3rd Generation Partnership Project，第三代移动通信标准化组织)无线通信系统是基于调度的系统，由基站为终端设备分配数据传输所需的时频资源，终端根据基站的调度命令进行下行数据接收或者上行数据发送。上行数据传输是由基站调度的，基站调度器确定上行资源分配情况之后会通过UL grant(上行调度许可)通知终端。基站调度器进行上行资源分配的依据是终端要发送的上行数据量，即终端的缓存状态。该缓存在终端侧，基站要想获知该信息，就需要终端向基站进行BSR(Buffer state report，缓存状态上报)。
触发SR(scheduling request，调度请求)后，发送SR的方式有两种，即：通过专用调度请求资源发送SR(D-SR)和通过随机接入过程来进行SR(RA-SR)。
当终端执行SR过程中，如果网络侧配置终端进行BWP变更，对于正在进行的SR过程如何处理目前还没有解决方案。
发明内容
本申请提供一种进行调度请求的方法和设备，用以解决现有技术中存在的如果网络侧配置终端进行BWP变更，对于正在进行的SR过程如何处理目前还没有解决方案的问题。
本申请实施例提供的一种进行调度请求的方法，该方法包括：
终端在执行SR上报过程中确定发生BWP变更；
所述终端根据变更后的BWP上的SR配置进行SR。
本申请实施例提供的一种进行调度请求的终端，该终端包括：处理器、存储器和收发机。
所述处理器，用于读取存储器中的程序并执行下列过程：
在执行SR上报过程中确定发生BWP变更；根据变更后的BWP上的SR配置进行SR。
本申请实施例提供的另一种进行调度请求的终端，该终端包括：
变更处理模块，用于在执行SR上报过程中确定发生BWP变更；
上报处理模块，用于根据变更后的BWP上的SR配置进行SR。
本申请实施例提供的一种计算机存储介质，其上存储有计算机程序，该程序被处理器执行时实现上述进行调度请求的方法的步骤。
本申请实施例终端在执行SR过程中若确定需要发生BWP变更，则根据变更后的BWP上的SR配置进行SR。由于终端能够根据变更后的BWP上的SR配置进行SR，从而给出了终端BWP变更后对于正在进行的SR过程的一种处理方式；进一步提高了系统的性能。
附图说明
为了更清楚地说明本申请实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简要介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域的普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1为本申请实施例进行调度请求的方法流程示意图；
图2为本申请实施例第一种终端的结构示意图；
图3为本申请实施例第二种终端的结构示意图；
图4为本申请实施例变更前有专用SR配置变更后没有专用SR配置的调度请求方法流程示意图；
图5为本申请实施例变更前没有专用SR配置变更后有专用SR配置的调度请求方法流程示意图。
具体实施方式
以下，对本申请实施例中的部分用语进行解释说明，以便于本领域技术人员理解。
(1)本申请实施例中，名词“网络”和“系统”经常交替使用，但本领域的技术人员可以理解其含义。
(2)本申请实施例中术语“多个”是指两个或两个以上，其它量词与之类似。
(3)“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。
为了使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请作进一步地详细描述，显然，所描述的实施例仅仅是本申请一部份实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其它实施例，都属于本申请保护的范围。
如图1所述，本申请实施例进行调度请求的方法包括：
步骤100、终端在执行SR上报过程中确定发生BWP变更；
步骤101、所述终端根据变更后的BWP上的SR配置进行SR。
本申请实施例终端在执行SR过程中若确定需要发生BWP变更，则根据变更后的BWP上的SR配置进行SR。由于终端能够根据变更后的BWP上的SR配置进行SR，从而给出了终端BWP变更后对于正在进行的SR过程的一种处理方式；进一步提高了系统的性能。
本申请实施例终端根据变更后的BWP上的SR配置进行SR分为：1、触发SR的逻辑信道在变更后的BWP上没有对应的专用SR配置；2、触发SR的逻辑信道在变更后的BWP上有对应的专用SR配置。下面分别进行介绍。
方式1、触发SR的逻辑信道在变更后的BWP上没有对应的专用SR配置。
具体的，若触发SR的逻辑信道在变更后的BWP上没有对应的专用SR配置，则所述终端通过随机接入过程进行SR(即RA-SR)。
针对方式1，又可以分为两种情况：
情况1、触发SR的逻辑信道在变更前的BWP上有对应的专用SR配置，且触发SR的逻辑信道在变更后的BWP上没有对应的专用SR配置；
情况2、触发SR的逻辑信道在变更前的BWP上没有对应的专用SR配置，且触发SR的逻辑信道在变更后的BWP上也没有对应的专用SR配置。
下面分别进行说明。
情况1、触发SR的逻辑信道在变更前的BWP上有对应的专用SR配置，且触发SR 的逻辑信道在变更后的BWP上没有对应的专用SR配置。
对于情况1，终端可以按照下列方式中的一种通过随机接入过程进行SR：
1、如果所述终端有至少一个SR禁止定时器正在运行，则所述终端在正在运行的SR禁止定时器中的目标SR禁止定时器(sr-ProhibitTimer)到时后，在变更后的BWP上通过随机接入过程进行SR，并取消所有挂起的SR。
有可能终端当前有多个挂起的SR，每个挂起的SR有多个SR禁止定时器，本申请实施例在目标SR禁止定时器到时后，在变更后的BWP上通过随机接入过程进行SR。
可选的，这里的目标SR禁止定时器为第一个超时的SR禁止定时器或最后一个超时的SR禁止定时器。
比如所述终端可以在正在运行的SR禁止定时器中的第一个超时的SR禁止定时器到时后，在变更后的BWP上通过随机接入过程进行SR；
还比如所述终端可以在正在运行的SR禁止定时器中的最后一个超时的SR禁止定时器到时后，在变更后的BWP上通过随机接入过程进行SR。
可选的，所述如果有正在运行的SR禁止定时器，所述终端停止所有SR禁止定时器，并将所述SR禁止定时器对应的SR计数器置为预设值(SR_COUNTER)，比如将SR计数值设置为0。
2、所述终端在接收到BWP切换命令后立刻停止当前正在运行的所有SR禁止定时器，在变更后的BWP上通过随机接入过程进行SR，并且取消所有挂起的SR，将SR计数值设置为预设值，比如将SR计数值设置为0。
有可能终端当前有多个挂起的SR，每个挂起的SR有多个SR禁止定时器，本申请实施例在接收到BWP切换命令后停止所有正在运行的SR禁止定时器，并在变更后的BWP上通过随机接入过程进行SR。
3、终端在接收到BWP切换命令后立刻停止当前正在运行的所有SR禁止定时器，并将与所述SR禁止定时器相关的SR计数器设置为预设值，在变更后的BWP上通过随机接入过程进行SR，并且取消所有挂起的SR。
有可能终端当前有多个挂起的SR，每个挂起的SR有多个SR禁止定时器，本申请实施例在接收到BWP切换命令后停止所有正在运行的SR禁止定时器，并将与所述SR禁止定时器相关的SR计数器设置为预设值，在变更后的BWP上通过随机接入过程进行SR。
情况2、触发SR的逻辑信道在变更前的BWP上没有对应的专用SR配置，且触发SR的逻辑信道在变更后的BWP上也没有对应的专用SR配置。
对于情况2，终端可以按照下列方式中的一种通过随机接入过程进行SR：
1、所述终端不执行BWP变更，继续在变更前的BWP上通过随机接入过程进行SR，随机接入成功后再执行BWP变更。
本申请实施例终端收到BWP切换命令并不进行BWP切换，而是继续在变更前的BWP上通过随机接入过程进行SR。
2、所述终端不执行BWP变更，继续在变更前的BWP上通过随机接入过程进行SR，当第N次随机接入失败后进行BWP变更，并在变更后的BWP上继续通过随机接入过程进行SR，其中N不大于随机接入最大传输次数。
本申请实施例终端收到BWP切换命令并不进行BWP切换，而是继续在变更前的BWP上通过随机接入过程进行SR，当第N次随机接入失败后进行BWP变更。
这里N的值可以根据需要进行设定，比如可以设置为1，则只要BWP变更后的第1次随机接入失败，就进行BWP切换，并在变更后的BWP上通过专用调度请求资源进行SR。
3、所述终端在变更前的BWP上立刻停止通过随机接入过程进行SR，并执行BWP变更，并在变更后的BWP上通过随机接入过程进行SR。
本申请实施例终端收到BWP切换命令立刻停止通过随机接入过程进行SR，并执行BWP变更，并在变更后的BWP上通过随机接入过程进行SR。
方式2、触发SR的逻辑信道在变更后的BWP上有对应的专用SR配置。
具体的，触发SR的逻辑信道在变更后的BWP上有对应的专用SR配置，则所述终端通过随机接入过程进行SR或通过专用调度请求资源进行SR。
对于方式2，又可以分为两种情况：
情况1、触发SR的逻辑信道在变更前的BWP上有对应的专用SR配置，且触发SR的逻辑信道在变更后的BWP上有对应的专用SR配置。
情况2、触发SR的逻辑信道在变更前的BWP上没有对应的专用SR配置，且触发SR的逻辑信道在变更后的BWP上有对应的专用SR配置。
下面分别进行说明。
情况1、触发SR的逻辑信道在变更前的BWP上有对应的专用SR配置，且触发SR的逻辑信道在变更后的BWP上有对应的专用SR配置。
对于情况1，终端可以按照下列方式通过专用调度请求资源进行SR：
所述终端在触发SR的逻辑信道对应的SR禁止定时器超时后，如果所述逻辑信道触发的SR处于挂起状态，则在变更后的BWP上通过专用调度请求资源进行SR。
这里情况终端在BWP变更后会继续SR禁止定时器运行，并在触发SR的逻辑信道对 应的SR禁止定时器超时后，如果所述逻辑信道触发的SR处于挂起状态，则在变更后的BWP上通过专用调度请求资源进行SR。
情况2、触发SR的逻辑信道在变更前的BWP上没有对应的专用SR配置，且触发SR的逻辑信道在变更后的BWP上有对应的专用SR配置。
对于情况2，终端可以按照下列方式中的一种通过随机接入过程进行SR或通过专用调度请求资源进行SR：
1、所述终端不执行BWP变更，继续在变更前的BWP上通过随机接入过程进行SR，随机接入成功再执行BWP切换。
本申请实施例终端收到BWP切换命令并不进行BWP切换，而是继续在变更前的BWP上通过随机接入过程进行SR。
2、所述终端不执行BWP变更，继续在变更前的BWP上通过随机接入过程进行SR，当第N次随机接入失败后进行BWP切换，并在变更后的BWP上通过专用调度请求资源进行SR，其中N不大于随机接入最大传输次数。
本申请实施例终端收到BWP切换命令并不进行BWP切换，而是继续在变更前的BWP上通过随机接入过程进行SR，当第N次随机接入失败后进行BWP切换，并在变更后的BWP上通过专用调度请求资源进行SR。
这里N的值可以根据需要进行设定，比如可以设置为1，则只要BWP变更后的第1次随机接入失败，就进行BWP切换，并在变更后的BWP上通过专用调度请求资源进行SR。
3、所述终端在变更前的BWP上立刻停止通过随机接入过程进行SR，立刻执行BWP变更，并在变更后的BWP上通过专用调度请求资源进行SR。
本申请实施例终端收到BWP切换命令立刻停止通过随机接入过程进行SR，并执行BWP变更，并在变更后的BWP上通过专用调度请求资源进行SR。
可选的，在随机接入失败的次数等于随机接入最大传输次数后，所述终端不向高层发送随机接入问题指示。
基于同一发明构思，本申请实施例中还提供了一种终端，由于该终端解决问题的原理与本申请实施例进行调度请求的方法相似，因此该终端的实施可以参见方法的实施，重复之处不再赘述。
如图2所述，本申请实施例第一种终端包括：处理器200、存储器201和收发机202。
处理器200负责管理总线架构和通常的处理，存储器201可以存储处理器200在执行操作时所使用的数据。收发机202用于在处理器200的控制下接收和发送数据。
总线架构可以包括任意数量的互联的总线和桥，具体由处理器200代表的一个或多个处理器和存储器201代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。处理器200负责管理总线架构和通常的处理，存储器201可以存储处理器200在执行操作时所使用的数据。
本申请实施例揭示的流程，可以应用于处理器200中，或者由处理器200实现。在实现过程中，信号处理流程的各步骤可以通过处理器200中的硬件的集成逻辑电路或者软件形式的指令完成。处理器200可以是通用处理器、数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器201，处理器200读取存储器201中的信息，结合其硬件完成信号处理流程的步骤。
其中，处理器200，用于读取存储器201中的程序并执行下列过程：
在执行SR上报过程中确定发生BWP变更；根据变更后的BWP上的SR配置进行SR。
可选的，所述处理器200具体用于：
若触发SR的逻辑信道在变更后的BWP上没有对应的专用SR配置，则通过随机接入过程进行SR；或
若触发SR的逻辑信道在变更后的BWP上有对应的专用SR配置，则通过随机接入过程进行SR或通过专用调度请求资源进行SR。
可选的，所述触发SR的逻辑信道在变更前的BWP上有对应的专用SR配置，且触发SR的逻辑信道在变更后的BWP上没有对应的专用SR配置；
所述处理器200具体用于：
如果有至少一个SR禁止定时器正在运行，则在正在运行的SR禁止定时器中的目标SR禁止定时器到时后，在变更后的BWP上通过随机接入过程进行SR，并取消所有挂起的SR；或
在接收到BWP切换命令后立刻停止当前正在运行的所有SR禁止定时器，在变更后的BWP上通过随机接入过程进行SR，并且取消所有挂起的SR；或
在接收到BWP切换命令后立刻停止当前正在运行的所有SR禁止定时器，并将与所述 SR禁止定时器相关的SR计数器设置为预设值，在变更后的BWP上通过随机接入过程进行SR，并且取消所有挂起的SR。
可选的，如果目标SR禁止定时器为第一个超时的SR禁止定时器或最后一个超时的SR禁止定时器。
可选的，所述处理器200还用于：
如果有正在运行的SR禁止定时器，停止所有SR禁止定时器，并将所述SR禁止定时器对应的SR计数器置为预设值。
可选的，所述触发SR的逻辑信道在变更前的BWP上没有对应的专用SR配置，且触发SR的逻辑信道在变更后的BWP上也没有对应的专用SR配置；
所述处理器200具体用于：
不执行BWP变更，继续在变更前的BWP上通过随机接入过程进行SR，随机接入成功后再执行BWP变更或当第N次随机接入失败后进行BWP变更，并在变更后的BWP上继续通过随机接入过程进行SR，其中N不大于随机接入最大传输次数；或
在变更前的BWP上立刻停止通过随机接入过程进行SR，并执行BWP变更，并在变更后的BWP上通过随机接入过程进行SR。
可选的，所述触发SR的逻辑信道在变更前的BWP上有对应的专用SR配置，且触发SR的逻辑信道在变更后的BWP上有对应的专用SR配置；
所述处理器200具体用于：
在触发SR的逻辑信道对应的SR禁止定时器超时后，如果所述逻辑信道触发的SR处于挂起状态，则在变更后的BWP上通过专用调度请求资源进行SR。
可选的，所述触发SR的逻辑信道在变更前的BWP上没有对应的专用SR配置，且触发SR的逻辑信道在变更后的BWP上有对应的专用SR配置；
所述处理器200具体用于：
不执行BWP变更，继续在变更前的BWP上通过随机接入过程进行SR，随机接入成功再执行BWP切换或者当第N次随机接入失败后进行BWP切换，并在变更后的BWP上通过专用调度请求资源进行SR，其中N不大于随机接入最大传输次数；或
在变更前的BWP上立刻停止通过随机接入过程进行SR，立刻执行BWP变更，并在变更后的BWP上通过专用调度请求资源进行SR。
可选的，所述处理器200还用于：
在随机接入失败的次数等于随机接入最大传输次数后，不向高层发送随机接入问题指示。
如图3所述，本申请实施例第二种终端包括：
变更处理模块300，用于在执行SR上报过程中确定发生BWP变更；
上报处理模块301，用于根据变更后的BWP上的SR配置进行SR。
可选的，所述上报处理模块301具体用于：
若触发SR的逻辑信道在变更后的BWP上没有对应的专用SR配置，则通过随机接入过程进行SR；或
若触发SR的逻辑信道在变更后的BWP上有对应的专用SR配置，则通过随机接入过程进行SR或通过专用调度请求资源进行SR。
可选的，所述触发SR的逻辑信道在变更前的BWP上有对应的专用SR配置，且触发SR的逻辑信道在变更后的BWP上没有对应的专用SR配置；
所述上报处理模块301具体用于：
如果有至少一个SR禁止定时器正在运行，则在正在运行的SR禁止定时器中的目标SR禁止定时器到时后，在变更后的BWP上通过随机接入过程进行SR，并取消所有挂起的SR；或
在接收到BWP切换命令后立刻停止当前正在运行的所有SR禁止定时器，在变更后的BWP上通过随机接入过程进行SR，并且取消所有挂起的SR；或
在接收到BWP切换命令后立刻停止当前正在运行的所有SR禁止定时器，并将与所述SR禁止定时器相关的SR计数器设置为预设值，在变更后的BWP上通过随机接入过程进行SR，并且取消所有挂起的SR。
可选的，如果目标SR禁止定时器为第一个超时的SR禁止定时器或最后一个超时的SR禁止定时器。
可选的，所述上报处理模块301还用于：
如果有正在运行的SR禁止定时器，停止所有SR禁止定时器，并将所述SR禁止定时器对应的SR计数器置为预设值。
可选的，所述触发SR的逻辑信道在变更前的BWP上没有对应的专用SR配置，且触发SR的逻辑信道在变更后的BWP上也没有对应的专用SR配置；
所述上报处理模块301具体用于：
不执行BWP变更，继续在变更前的BWP上通过随机接入过程进行SR，随机接入成功后再执行BWP变更或当第N次随机接入失败后进行BWP变更，并在变更后的BWP上继续通过随机接入过程进行SR，其中N不大于随机接入最大传输次数；或
在变更前的BWP上立刻停止通过随机接入过程进行SR，并执行BWP变更，并在变 更后的BWP上通过随机接入过程进行SR。
可选的，所述触发SR的逻辑信道在变更前的BWP上有对应的专用SR配置，且触发SR的逻辑信道在变更后的BWP上有对应的专用SR配置；
所述上报处理模块301具体用于：
在触发SR的逻辑信道对应的SR禁止定时器超时后，如果所述逻辑信道触发的SR处于挂起状态，则在变更后的BWP上通过专用调度请求资源进行SR。
可选的，所述触发SR的逻辑信道在变更前的BWP上没有对应的专用SR配置，且触发SR的逻辑信道在变更后的BWP上有对应的专用SR配置；
所述上报处理模块301具体用于：
不执行BWP变更，继续在变更前的BWP上通过随机接入过程进行SR，随机接入成功再执行BWP切换或者当第N次随机接入失败后进行BWP切换，并在变更后的BWP上通过专用调度请求资源进行SR，其中N不大于随机接入最大传输次数；或
在变更前的BWP上立刻停止通过随机接入过程进行SR，立刻执行BWP变更，并在变更后的BWP上通过专用调度请求资源进行SR。
可选的，所述上报处理模块301还用于：
在随机接入失败的次数等于随机接入最大传输次数后，不向高层发送随机接入问题指示。
本申请实施例提供一种可读存储介质，所述可读存储介质为非易失性可读存储介质，包括程序代码，当所述程序代码在计算设备上运行时，所述程序代码用于使所述计算设备执行上述终端进行调度请求的动作。
下面列举几个例子对本申请的方案进行说明。
假设终端支持BWP 1和BWP 2，终端的逻辑信道1为触发SR的逻辑信道，在BWP1上有逻辑信道1对应的专用SR配置，在BWP2上逻辑信道1没有对应的专用SR配置。
实施例1、如图4所述，本申请实施例变更前有专用SR配置变更后没有专用SR配置的调度请求方法包括：
步骤400、终端当前激活的BWP为BWP 1，此时有regular(周期)BSR触发，根据SR触发条件，判断regular BSR会触发SR。
步骤401、由于触发SR的逻辑信道1在BWP1上有对应的专用SR配置，因此终端在BWP1上使用专用SR资源进行SR，并基于专用SR维护sr-ProhibitTimer和SR_COUNTER。
步骤402、在终端执行SR的过程中，网络侧通知终端进行BWP变更。
步骤403、终端将激活BWP由BWP 1变更到BWP 2。
步骤404、由于触发SR的逻辑信道2在BWP 2上没有专用SR配置，因此终端需要进行RA-SR。
可选的，终端具体的行为为：
1、如果所述终端有至少一个SR禁止定时器正在运行，则所述终端在正在运行的SR禁止定时器中的目标SR禁止定时器到时后，在变更后的BWP上通过随机接入过程进行SR，并取消所有挂起的SR。
2、所述终端在接收到BWP切换命令后立刻停止当前正在运行的所有SR禁止定时器，在变更后的BWP上通过随机接入过程进行SR，并且取消所有挂起的SR。
3、所述终端在接收到BWP切换命令后立刻停止当前正在运行的所有SR禁止定时器，并将与所述SR禁止定时器相关的SR计数器设置为预设值，在变更后的BWP上通过随机接入过程进行SR，并且取消所有挂起的SR。
实施例2、如图5所述，本申请实施例变更前没有专用SR配置变更后有专用SR配置的调度请求方法包括：
步骤500、终端当前激活BWP为BWP 2，此时有regular BSR触发，根据SR触发条件，判断regular BSR会触发SR。
步骤501、由于触发SR的逻辑信道1在BWP 2上没有对应的专用SR配置，因此终端在BWP 2上使用RA-SR进行SR。
步骤502、在终端执行SR的过程中，网络侧通知终端进行BWP变更。
步骤503、终端将激活BWP由BWP 2变更到BWP 1。
步骤504、由于触发SR的逻辑信道2在BWP 2上没有专用SR配置，因此终端可以进行RA-SR或通过专用调度请求资源进行SR(即D-SR)。
可选的，终端具体的行为可以是如下任何一种：
1、所述终端不执行BWP变更，继续在变更前的BWP上通过随机接入过程进行SR，随机接入成功再执行BWP切换或者当第N次随机接入失败后进行BWP切换，并在变更后的BWP上通过专用调度请求资源进行SR，其中N不大于随机接入最大传输次数。
2、所述终端在变更前的BWP上立刻停止通过随机接入过程进行SR，立刻执行BWP变更，并在变更后的BWP上通过专用调度请求资源进行SR。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程 序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本申请的优选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例作出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本申请范围的所有变更和修改。
显然，本领域的技术人员可以对本申请实施例进行各种改动和变型而不脱离本申请实施例的精神和范围。这样，倘若本申请实施例的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (20)

  1. 一种进行调度请求的方法，其特征在于，该方法包括：
    终端在执行调度请求SR上报过程中确定发生频带宽度BWP变更；
    所述终端根据变更后的BWP上的SR配置进行SR。
  2. 如权利要求1所述的方法，其特征在于，所述终端根据变更后的BWP上的SR配置进行SR，包括：
    若触发SR的逻辑信道在变更后的BWP上没有对应的专用SR配置，则所述终端通过随机接入过程进行SR；或
    若触发SR的逻辑信道在变更后的BWP上有对应的专用SR配置，则所述终端通过随机接入过程进行SR或通过专用调度请求资源进行SR。
  3. 如权利要求2所述的方法，其特征在于，若触发SR的逻辑信道在变更前的BWP上有对应的专用SR配置，且触发SR的逻辑信道在变更后的BWP上没有对应的专用SR配置，则所述终端通过随机接入过程进行SR，包括：
    如果所述终端有至少一个SR禁止定时器正在运行，则所述终端在正在运行的SR禁止定时器中的目标SR禁止定时器到时后，在变更后的BWP上通过随机接入过程进行SR，并取消所有挂起的SR；或
    所述终端在接收到BWP切换命令后立刻停止当前正在运行的所有SR禁止定时器，在变更后的BWP上通过随机接入过程进行SR，并且取消所有挂起的SR；或
    所述终端在接收到BWP切换命令后立刻停止当前正在运行的所有SR禁止定时器，并将与所述SR禁止定时器相关的SR计数器设置为预设值，在变更后的BWP上通过随机接入过程进行SR，并且取消所有挂起的SR。
  4. 如权利要求3所述的方法，其特征在于，如果目标SR禁止定时器为第一个超时的SR禁止定时器或最后一个超时的SR禁止定时器。
  5. 如权利要求3所述的方法，其特征在于，所述终端在取消所有挂起的SR之后，还包括：
    如果有正在运行的SR禁止定时器，所述终端停止所有SR禁止定时器，并将所述SR禁止定时器对应的SR计数器置为预设值。
  6. 如权利要求2所述的方法，其特征在于，若触发SR的逻辑信道在变更前的BWP上没有对应的专用SR配置，且触发SR的逻辑信道在变更后的BWP上也没有对应的专用SR配置，则所述终端通过随机接入过程进行SR，包括：
    所述终端不执行BWP变更，继续在变更前的BWP上通过随机接入过程进行SR，随机接入成功后再执行BWP变更或当第N次随机接入失败后进行BWP变更，并在变更后的BWP上继续通过随机接入过程进行SR，其中N不大于随机接入最大传输次数；或
    所述终端在变更前的BWP上立刻停止通过随机接入过程进行SR，并执行BWP变更，并在变更后的BWP上通过随机接入过程进行SR。
  7. 如权利要求2所述的方法，其特征在于，若触发SR的逻辑信道在变更前的BWP上有对应的专用SR配置，且触发SR的逻辑信道在变更后的BWP上有对应的专用SR配置，则所述终端通过专用调度请求资源进行SR，包括：
    所述终端在触发SR的逻辑信道对应的SR禁止定时器超时后，如果所述逻辑信道触发的SR处于挂起状态，则在变更后的BWP上通过专用调度请求资源进行SR。
  8. 如权利要求2所述的方法，其特征在于，若触发SR的逻辑信道在变更前的BWP上没有对应的专用SR配置，且触发SR的逻辑信道在变更后的BWP上有对应的专用SR配置，则所述终端通过随机接入过程进行SR或通过专用调度请求资源进行SR，包括：
    所述终端不执行BWP变更，继续在变更前的BWP上通过随机接入过程进行SR，随机接入成功再执行BWP切换或者当第N次随机接入失败后进行BWP切换，并在变更后的BWP上通过专用调度请求资源进行SR，其中N不大于随机接入最大传输次数；或
    所述终端在变更前的BWP上立刻停止通过随机接入过程进行SR，立刻执行BWP变更，并在变更后的BWP上通过专用调度请求资源进行SR。
  9. 如权利要求1～8任一所述的方法，其特征在于，该方法还包括：
    所述终端在随机接入失败的次数等于随机接入最大传输次数后，不向高层发送随机接入问题指示。
  10. 一种进行调度请求的终端，其特征在于，该终端包括：处理器、存储器和收发机；
    所述处理器，用于读取存储器中的程序并执行下列过程：
    在执行SR上报过程中确定发生BWP变更；根据变更后的BWP上的SR配置进行SR。
  11. 如权利要求10所述的终端，其特征在于，所述处理器具体用于：
    若触发SR的逻辑信道在变更后的BWP上没有对应的专用SR配置，则通过随机接入过程进行SR；或
    若触发SR的逻辑信道在变更后的BWP上有对应的专用SR配置，则通过随机接入过程进行SR或通过专用调度请求资源进行SR。
  12. 如权利要求11所述的终端，其特征在于，所述触发SR的逻辑信道在变更前的BWP上有对应的专用SR配置，且触发SR的逻辑信道在变更后的BWP上没有对应的专 用SR配置；
    所述处理器具体用于：
    如果有至少一个SR禁止定时器正在运行，则在正在运行的SR禁止定时器中的目标SR禁止定时器到时后，在变更后的BWP上通过随机接入过程进行SR，并取消所有挂起的SR；或
    在接收到BWP切换命令后立刻停止当前正在运行的所有SR禁止定时器，在变更后的BWP上通过随机接入过程进行SR，并且取消所有挂起的SR；或
    在接收到BWP切换命令后立刻停止当前正在运行的所有SR禁止定时器，并将与所述SR禁止定时器相关的SR计数器设置为预设值，在变更后的BWP上通过随机接入过程进行SR，并且取消所有挂起的SR。
  13. 如权利要求11所述的终端，其特征在于，如果目标SR禁止定时器为第一个超时的SR禁止定时器或最后一个超时的SR禁止定时器。
  14. 如权利要求11所述的终端，其特征在于，所述处理器还用于：
    如果有正在运行的SR禁止定时器，停止所有SR禁止定时器，并将所述SR禁止定时器对应的SR计数器置为预设值。
  15. 如权利要求11所述的终端，其特征在于，所述触发SR的逻辑信道在变更前的BWP上没有对应的专用SR配置，且触发SR的逻辑信道在变更后的BWP上也没有对应的专用SR配置；
    所述处理器具体用于：
    不执行BWP变更，继续在变更前的BWP上通过随机接入过程进行SR，随机接入成功后再执行BWP变更或当第N次随机接入失败后进行BWP变更，并在变更后的BWP上继续通过随机接入过程进行SR，其中N不大于随机接入最大传输次数；或
    在变更前的BWP上立刻停止通过随机接入过程进行SR，并执行BWP变更，并在变更后的BWP上通过随机接入过程进行SR。
  16. 如权利要求11所述的终端，其特征在于，所述触发SR的逻辑信道在变更前的BWP上有对应的专用SR配置，且触发SR的逻辑信道在变更后的BWP上有对应的专用SR配置；
    所述处理器具体用于：
    在触发SR的逻辑信道对应的SR禁止定时器超时后，如果所述逻辑信道触发的SR处于挂起状态，则在变更后的BWP上通过专用调度请求资源进行SR。
  17. 如权利要求11所述的终端，其特征在于，所述触发SR的逻辑信道在变更前的 BWP上没有对应的专用SR配置，且触发SR的逻辑信道在变更后的BWP上有对应的专用SR配置；
    所述处理器具体用于：
    不执行BWP变更，继续在变更前的BWP上通过随机接入过程进行SR，随机接入成功再执行BWP切换或者当第N次随机接入失败后进行BWP切换，并在变更后的BWP上通过专用调度请求资源进行SR，其中N不大于随机接入最大传输次数；或
    在变更前的BWP上立刻停止通过随机接入过程进行SR，立刻执行BWP变更，并在变更后的BWP上通过专用调度请求资源进行SR。
  18. 如权利要求10～17任一所述的终端，其特征在于，所述处理器还用于：
    在随机接入失败的次数等于随机接入最大传输次数后，不向高层发送随机接入问题指示。
  19. 一种进行调度请求的终端，其特征在于，该终端包括：
    变更处理模块，用于在执行SR上报过程中确定发生BWP变更；
    上报处理模块，用于根据变更后的BWP上的SR配置进行SR。
  20. 一种计算机存储介质，其上存储有计算机程序，其特征在于，该程序被处理器执行时实现如权利要求1～9任一所述方法的步骤。
PCT/CN2018/104898 2017-12-28 2018-09-10 一种进行调度请求的方法和设备 WO2019128308A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
KR1020227029997A KR102487369B1 (ko) 2017-12-28 2018-09-10 스케줄링 요청을 수행하기 위한 방법 및 장치
KR1020207021856A KR102439712B1 (ko) 2017-12-28 2018-09-10 스케줄링 요청을 수행하기 위한 방법 및 장치
JP2020535988A JP7030996B2 (ja) 2017-12-28 2018-09-10 スケジューリング要求を行う方法および装置
EP18893567.0A EP3735067B1 (en) 2017-12-28 2018-09-10 Method and apparatus for performing scheduling request
US16/958,386 US11405947B2 (en) 2017-12-28 2018-09-10 Method and terminal for performing scheduling request
US17/839,416 US11825480B2 (en) 2017-12-28 2022-06-13 Method and terminal for performing scheduling request

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711466570.X 2017-12-28
CN201711466570.XA CN109982430B (zh) 2017-12-28 2017-12-28 一种进行调度请求的方法和设备

Related Child Applications (2)

Application Number Title Priority Date Filing Date
US16/958,386 A-371-Of-International US11405947B2 (en) 2017-12-28 2018-09-10 Method and terminal for performing scheduling request
US17/839,416 Continuation US11825480B2 (en) 2017-12-28 2022-06-13 Method and terminal for performing scheduling request

Publications (1)

Publication Number Publication Date
WO2019128308A1 true WO2019128308A1 (zh) 2019-07-04

Family

ID=67065028

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/104898 WO2019128308A1 (zh) 2017-12-28 2018-09-10 一种进行调度请求的方法和设备

Country Status (7)

Country Link
US (2) US11405947B2 (zh)
EP (1) EP3735067B1 (zh)
JP (1) JP7030996B2 (zh)
KR (2) KR102439712B1 (zh)
CN (1) CN109982430B (zh)
TW (1) TWI743399B (zh)
WO (1) WO2019128308A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11533772B2 (en) * 2018-11-26 2022-12-20 Qualcomm Incorporated Techniques for configuring bandwidth parts for multiple-subscription communication devices
CN111818658B (zh) * 2019-07-11 2023-05-26 维沃移动通信有限公司 调度请求发送方法、调度请求接收方法、终端和网络设备
CN112584539B (zh) * 2019-09-30 2023-01-13 华为技术有限公司 一种随机接入方法及装置
CN112954771B (zh) * 2021-02-19 2023-04-14 Oppo广东移动通信有限公司 一种接入控制方法及终端、存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101841919A (zh) * 2009-03-18 2010-09-22 大唐移动通信设备有限公司 一种资源分配方法及装置
CN103535099A (zh) * 2012-05-09 2014-01-22 华为技术有限公司 上行信道资源配置方法和设备

Family Cites Families (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10511379B2 (en) * 2010-05-02 2019-12-17 Viasat, Inc. Flexible beamforming for satellite communications
US9654998B2 (en) * 2013-01-02 2017-05-16 Lg Electronics Inc. Method for measuring interference in wireless communication system, and apparatus therefor
KR20150020018A (ko) * 2013-08-14 2015-02-25 삼성전자주식회사 이동 통신 시스템에서 복수의 캐리어를 이용하는 데이터 송수신 방법 및 장치
JP6230516B2 (ja) * 2014-10-08 2017-11-15 シャープ株式会社 基地局装置、移動局装置、及び処理方法
KR101726705B1 (ko) * 2014-12-01 2017-04-26 아서스테크 컴퓨터 인코포레이션 무선 통신 시스템에서 스케줄링 요청(sr)에 대한 금지 타이머를 처리하기 위한 방법 및 장치
CN106507491B (zh) * 2015-09-08 2019-11-12 华为技术有限公司 并行发送数据的站点调度方法、装置、设备及系统
EP3342236B1 (en) 2015-11-16 2020-05-27 Samsung Electronics Co., Ltd. Transmission and reception of repeated scheduling requests
CN117241380A (zh) * 2017-04-01 2023-12-15 华为技术有限公司 一种上行传输方法及装置
KR20200015752A (ko) * 2017-06-15 2020-02-12 콘비다 와이어리스, 엘엘씨 스케줄링 요청들, 상태 보고들, 및 논리 채널 우선순위화
US12010754B2 (en) * 2017-08-10 2024-06-11 Interdigital Patent Holdings, Inc. Enhanced connected mode DRX procedures for NR
CN107396386B (zh) * 2017-08-30 2021-05-18 宇龙计算机通信科技(深圳)有限公司 信道检测方法及信道检测设备
WO2019062867A1 (en) * 2017-09-28 2019-04-04 Telefonaktiebolaget Lm Ericsson (Publ) BANDWIDTH PARTS SWITCHING IN A WIRELESS COMMUNICATION NETWORK
EP3685619A4 (en) * 2017-09-28 2021-04-07 Samsung Electronics Co., Ltd. METHOD AND NETWORK NODE FOR PERFORMING DATA TRANSMISSION AND MEASUREMENTS ON MULTIPLE PARTS OF BANDWIDTH
CN113473637B (zh) * 2017-09-29 2022-05-13 华为技术有限公司 一种调度请求配置方法、发送方法以及对应装置
EP3611866A1 (en) * 2017-10-26 2020-02-19 Ofinno, LLC Reference signal received power report
US10887903B2 (en) * 2017-10-26 2021-01-05 Ofinno, Llc Wireless device processes with bandwidth part switching
US11496937B2 (en) * 2017-11-24 2022-11-08 FG Innovation Company Limited Methods and related devices for handling random access procedure in bandwidth part switching operation
US10736137B2 (en) * 2017-11-24 2020-08-04 FG Innovation Company Limited Methods and devices for adaptive scheduling request procedure
WO2019123009A1 (en) * 2017-12-20 2019-06-27 Lenovo (Singapore) Pte. Ltd. Random-access procedure for scheduling request

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101841919A (zh) * 2009-03-18 2010-09-22 大唐移动通信设备有限公司 一种资源分配方法及装置
CN103535099A (zh) * 2012-05-09 2014-01-22 华为技术有限公司 上行信道资源配置方法和设备

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
CATT.: "R2-1710296 SR Configuration, Mapping and Transmission for CA and BWPs Cases", 3GPP TSG-RAN WG2 #99BIS, 13 October 2017 (2017-10-13), XP051342344 *
CATT: "R2-1710295 Further Details on the SR Procedure", 3GPP TSG-RAN WG2 #99BIS, 13 October 2017 (2017-10-13), XP051342343 *
See also references of EP3735067A4

Also Published As

Publication number Publication date
CN109982430B (zh) 2021-07-13
KR102487369B1 (ko) 2023-01-10
JP2021508208A (ja) 2021-02-25
KR102439712B1 (ko) 2022-09-01
TWI743399B (zh) 2021-10-21
TW201931914A (zh) 2019-08-01
EP3735067A1 (en) 2020-11-04
US11405947B2 (en) 2022-08-02
JP7030996B2 (ja) 2022-03-07
US20220312461A1 (en) 2022-09-29
EP3735067A4 (en) 2021-01-06
KR20200100825A (ko) 2020-08-26
CN109982430A (zh) 2019-07-05
KR20220123760A (ko) 2022-09-08
US20210058957A1 (en) 2021-02-25
EP3735067B1 (en) 2023-02-22
US11825480B2 (en) 2023-11-21

Similar Documents

Publication Publication Date Title
WO2019128308A1 (zh) 一种进行调度请求的方法和设备
RU2682011C1 (ru) Устройство и способ деактивации для вторичной соты и система связи
WO2020192213A1 (zh) 共享信道占用时间的方法和设备
US11166263B2 (en) Selective reallocation of previously allocated radio resources
EP3668223B1 (en) Random access resource processing method and device
JP7354114B2 (ja) 帯域幅パートのメンテナンスのための方法および装置
US10349409B2 (en) Method and system for transmission schedule instruction for allocating resources in an unlicensed spectrum
US11444678B2 (en) Method for indicating beam failure recovery, device, and storage medium
US20220353899A1 (en) User equipment, base station, and method thereof
US11350438B2 (en) Method for configuring scheduling request, terminal device, and computer storage medium
US12016049B2 (en) User equipment, base station, and method thereof
WO2012092762A1 (zh) 一种终端物理层资源分配方法及系统
US10440694B2 (en) MAC control element uplink configuration method and device and communications system
RU2020128270A (ru) Способ связи и устройство

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: 18893567

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020535988

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20207021856

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2018893567

Country of ref document: EP

Effective date: 20200728