WO2018137665A1 - 处理调度请求的方法和装置 - Google Patents

处理调度请求的方法和装置 Download PDF

Info

Publication number
WO2018137665A1
WO2018137665A1 PCT/CN2018/074031 CN2018074031W WO2018137665A1 WO 2018137665 A1 WO2018137665 A1 WO 2018137665A1 CN 2018074031 W CN2018074031 W CN 2018074031W WO 2018137665 A1 WO2018137665 A1 WO 2018137665A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
timer
terminal device
triggering
sending
Prior art date
Application number
PCT/CN2018/074031
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 EP18744458.3A priority Critical patent/EP3565357B1/en
Publication of WO2018137665A1 publication Critical patent/WO2018137665A1/zh
Priority to US16/522,335 priority patent/US11134507B2/en

Links

Images

Classifications

    • 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/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H04W72/566—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient
    • H04W72/569—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient of the traffic information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
    • 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

Definitions

  • the present application relates to the field of communications and, more particularly, to a method and apparatus for processing scheduling requests in the field of communications.
  • a scheduling request is a method in which a user equipment (UE) applies for resources to a network device for new data transmission. If the connected UE does not have an uplink grant and has an SR resource, the SR is sent first, requesting allocation of a small amount of resources.
  • the SR belongs to the information of the physical layer.
  • the UE does not need radio bearer (RB) resources to transmit the SR itself, and can be transmitted through a physical uplink control channel (PUCCH).
  • RB resource may be allocated to the UE through the downlink control information (DCI), but the RB may not be allocated every time.
  • DCI downlink control information
  • the UE sends the SR signal, but the network side does not decode it. After the UE sends the SR signal, do not expect the network device to allocate RB resources at a certain time. In many cases, the UE needs to send the SR application multiple times in order to obtain the uplink RB resources. Since the period of the SR transmission is generally short, in order to prevent the UE from transmitting an unnecessary SR, a prohibition timer (sr-Prohibit Timer) is introduced, which is used to monitor the SR signal transmitted in the PUCCH, when the timer is running, The SR cannot be sent. The SR can be sent only after the timer expires. After the maximum number of transmissions (dsr-Trans Max) is reached, the SR resources are released and the scheduling mode is obtained by using the contention method of the random competition access procedure. This greatly reduces the load on the PUCCH.
  • dsr-Trans Max the maximum number of transmissions
  • the SR When the UE triggers an SR, the SR is in the "Pending" state, which means that the UE is ready but has not sent the SR to the network device. However, when the UE has assembled a medium access control protocol data unit (MAC PDU), and the PDU contains the most recently triggered buffer status report (BSR) control unit, or uplink The authorized resources can accommodate all the data to be transmitted, then the SR in the "Pending" state will be canceled and the timer will be stopped.
  • MAC PDU medium access control protocol data unit
  • BSR buffer status report
  • enhanced mobile broadband (eMBB) services such as video
  • ultra reliable and low latency communication (ultra reliable and low latency communication, URLLC) services such as drone control
  • massive reliable and low latency communication (mMTC) services such as meter reading.
  • the parameter configuration can also be called “numerology” because the resource parameter configuration of different services is different.
  • the cyclic prefix (CP) length and transmission time interval of different service configurations (transmission time) The interval, TTI, and subcarrier spacing are different. Therefore, services in different areas have different requirements for delays in transmitting service data.
  • the uplink transmission delay requirement for the URLLC service is 0.5 ms
  • the uplink transmission delay requirement for the eMBB service is 4 ms.
  • the present application provides a method and apparatus for processing a scheduling request, which can increase the chances of a high-priority service triggering scheduling request and/or a transmitted scheduling request, and reduce the transmission delay of high-priority service data, and the user experience is good.
  • a method for processing a scheduling request includes: determining, by a terminal device, that a condition for triggering a first service scheduling request SR is satisfied; and determining, by the terminal device, an uplink resource of the first service; Whether the priority of the service is higher than the priority of the second service that has triggered or sent the scheduling request SR; when the terminal device determines that the priority of the first service is higher than the priority of the second service, triggering and/or sending The SR of the first service.
  • the method for processing the scheduling request provided by the first aspect determines that the priority of the first service that needs to request the uplink resource is higher than the priority of the second service that has triggered or sent the scheduling request SR.
  • the SR that is triggered or sent by the first service with a higher priority is not affected by the second service triggered by the lower priority and/or the SR that is sent, that is, is sent according to the original period, so that the number can be increased.
  • the triggering or sending opportunity of the SR of a service improves the reliability of the SR triggered or sent by the first service, reduces the delay value, and improves the user experience.
  • the method further includes: when the uplink resource of the SR of the first service is different from the uplink resource of the SR of the second service, the terminal device triggers without interference or Sending the SR of the first service and the SR of the second service.
  • the first timer of the SR corresponding to the first service controls triggering or sending of the SR of the first service, where the first timer expires before the first timer expires
  • the terminal device does not trigger or send the SR of the first service.
  • the second timer of the SR corresponding to the second service controls triggering or sending of the SR of the second service, where the second timer expires before the second timer expires
  • the terminal device does not trigger or does not send the SR of the second service.
  • the method further includes: before the terminal device obtains the scheduling authorization, the terminal device calculates the number of times of sending the SR of the first service from zero until the maximum transmission is accumulated. frequency.
  • the method further includes: when the uplink resource of the SR of the first service is the same as the uplink resource of the SR of the second service, the terminal device only triggers or sends the The SR of a service does not trigger or send the SR of the second service.
  • the method further includes: the terminal device sets a duration value of the first timer associated with the SR of the first service to zero; or the terminal device does not set The first timer associated with the SR of the first service.
  • the first timer of the SR corresponding to the first service controls triggering or sending of the SR of the first service, and the second timing of the SR corresponding to the second service
  • the triggering or sending of the SR of the second service is performed, and the duration value of the first timer is smaller than the duration value of the second timer.
  • the method further includes: the terminal device stops the second timer; the terminal device sets the duration value of the second timer to a duration value of the first timer And restart the second timer.
  • the method further includes: stopping, by the terminal device, the second timer, and associating the triggering or sending of the SR of the second service with the first timer.
  • the method further includes: stopping, by the terminal device, a second timer associated with the SR of the second service, modifying a duration value of the second timer, and the After the SR of a service is related, the second timer is restarted.
  • the duration value of the timer associated with the SR of the first service is smaller than the duration value of the timer associated with the SR of the second service.
  • a second aspect provides a method for processing a scheduling request, where the method includes: determining, by a terminal device, that a condition for triggering a first service scheduling request SR is satisfied; and determining, by the terminal device, whether a priority of the first service is higher than triggered or Sending a priority of the second service of the scheduling request SR; when the terminal device determines that the priority of the first service is lower than the priority of the second service, before the timer associated with the SR of the second service times out The terminal device does not trigger and/or does not send the SR of the first service.
  • the terminal device determines, according to the priority condition of the service, that the priority of the first service that needs to request the uplink resource is lower than the second service that has triggered and/or sent the scheduling request SR Priority, when the timer associated with the SR of the second service times out, the first service with lower priority does not trigger and/or does not send the SR, so that it can be related to the SR of the second service.
  • the associated timer is used to control the triggering and/or sending of the SR of the first service, so that the triggering or sending opportunity of the SR of the first service can be increased, the reliability of the SR triggered or sent by the first service is improved, and the user is improved.
  • Experience is used to control the triggering and/or sending of the SR of the first service, so that the triggering or sending opportunity of the SR of the first service can be increased, the reliability of the SR triggered or sent by the first service is improved, and the user is improved.
  • the duration value of the timer associated with the SR of the second service is smaller than the duration value of the timer associated with the SR of the first service.
  • the third aspect provides a method for processing a scheduling request, where the method includes: determining, by the terminal device, that a condition for triggering the first service scheduling request SR is satisfied; and determining, by the terminal device, an uplink resource and an used resource of the scheduling request SR of the first service Whether the uplink resources of the SR that triggers or sends the second service are the same; when the terminal device determines that the uplink resource of the SR of the first service is different from the uplink resource of the SR of the second service, the terminal device triggers independently of each other. / or send the SR of the first service and the SR of the second service.
  • the method for processing a scheduling request provided by the third aspect before the first service requests the uplink resource, when the second service exists, the uplink resource is also requested, and the SR corresponding to the second service is triggered or sent, when
  • the terminal device may determine that the uplink resource of the SR for transmitting the first service and the uplink resource of the SR for transmitting the first service are different, and the sending and/or triggering of the SR of the first service and the SR of the second service may be mutually Independence, that is, mutual interference.
  • the efficiency of sending or triggering the SR of the first service and the SR of the second service can be improved to ensure the reliability of the SR.
  • the first timer of the SR corresponding to the first service controls triggering or sending of the SR of the first service, where the first timer expires before the first timer expires
  • the terminal device does not trigger or send the SR of the first service.
  • the second timer of the SR corresponding to the second service controls triggering or sending of the SR of the second service, where the second timer expires before the second timer expires
  • the terminal device does not trigger or does not send the SR of the second service.
  • the method further includes: before the terminal device obtains the scheduling authorization, the terminal device calculates the number of times the SR of the first service is sent from zero until the maximum transmission is accumulated. frequency.
  • the method further includes: when the terminal device determines that the uplink resource of the SR request of the first service is the same as the uplink resource of the SR request of the second service, and the first When the priority of the service is lower than the priority of the second service, the terminal device does not trigger and/or does not send the SR of the first service before the timer associated with the SR of the second service times out.
  • a fourth aspect provides a method for processing a scheduling request, the method comprising: determining, by a terminal device, a service that needs to be sent;
  • the terminal device When the terminal device sends data of the service through a non-scheduled resource or a contention resource, the terminal device does not cancel the scheduling request suspended for the service.
  • the method for processing a scheduling request provided by the fourth aspect, when the terminal device determines the service to be sent, the non-scheduled resource for transmitting the data of the first service is also acquired, and at this time, the first service is sent by using the non-scheduled resource.
  • the data does not stop triggering and/or transmitting the SR of the first service or the SR of the second service. In this way, it can be ensured that the data of the service can be effectively transmitted to the network device, that is, when the data of the service is sent by using the non-scheduled resource, the dedicated scheduling resource is also requested at the same time. Increased reliability of transmitting service data.
  • the method further includes: after the terminal device successfully sends the data of the service by using the non-scheduled resource or the contention resource, canceling the triggering or sending of the SR of the service.
  • the method further includes: when the terminal device acquires a sending resource for sending data of a service with a lower priority than the service, canceling triggering and/or sending the service SR; the terminal device transmits data of the service using a transmission resource of data of a service having a lower priority than the service.
  • the method further includes: sending, by using the non-scheduled resource, the priority order of the data of the service: a buffer status report BSR including the data volume of the service, and the data of the service.
  • a buffer status report BSR including the data volume of the service and the data of the service.
  • Semi-persistent scheduling SPS acknowledgment > BSR of a data amount including a service having a lower priority than the service > Data of a service having a lower priority than the service.
  • an apparatus for processing a scheduling request comprising a processor and a memory for supporting the apparatus to perform a corresponding function in the above method.
  • the processor and the memory are coupled by communication, the memory storing a program for invoking the program to implement the method of processing a scheduling request in the first aspect and various implementations thereof.
  • an apparatus for processing a scheduling request comprising a processing module and a storage module, configured to support a device to perform the functions of the first aspect or any of the possible implementations of the first aspect.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware, and the hardware or software includes one or more modules corresponding to the above functions.
  • an apparatus for processing a scheduling request comprising a processor and a memory for supporting the apparatus to perform a corresponding function in the above method.
  • the processor and the memory are coupled by communication, the memory storing a program for invoking the program to implement the method of processing a scheduling request in the second aspect and various implementations thereof.
  • an apparatus for processing a scheduling request including a processing module and a storage module, for supporting a device to perform the functions in any of the second aspect or the second aspect of the second aspect.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware, and the hardware or software includes one or more modules corresponding to the above functions.
  • an apparatus for processing a scheduling request comprising a processor and a memory for supporting the apparatus to perform a corresponding function of the above method.
  • the processor and the memory are communicatively coupled, the memory storing a program for invoking the program to implement the method of processing a scheduling request in the third aspect and various implementations thereof.
  • a tenth aspect provides an apparatus for processing a scheduling request, including a processing module and a storage module, for supporting a device to perform the functions in any of the foregoing third aspect or any possible implementation of the third aspect.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware, and the hardware or software includes one or more modules corresponding to the above functions.
  • an apparatus for processing a scheduling request comprising a processor and a memory for supporting the apparatus to perform a corresponding function in the above method.
  • the processor and the memory are connected by communication, the memory storing a program for calling the program to implement the method for processing a scheduling request in the fourth aspect and various implementations thereof.
  • an apparatus for processing a scheduling request comprising a processing module and a storage module for supporting a device to perform the functions of the apparatus in any of the possible implementations of the fourth aspect or the fourth aspect.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware, and the hardware or software includes one or more modules corresponding to the above functions.
  • a thirteenth aspect a computer readable medium for storing a computer program, the computer program comprising instructions for performing the method of any of the first aspect or the first aspect of the first aspect.
  • a computer readable medium for storing a computer program comprising instructions for performing the method of any of the above-described second aspect or any of the possible implementations of the second aspect.
  • a computer readable medium for storing a computer program comprising instructions for performing the method of any of the above-described third or third possible implementations.
  • a computer readable medium for storing a computer program comprising instructions for performing the method of any of the above-described fourth or fourth possible implementations.
  • FIG. 1 is a schematic flowchart of a scheduling request method according to an embodiment of the present application.
  • FIG. 2 is a schematic flowchart of two kinds of SR transmissions when the available time-frequency resources of the SR of the URLLC and the available time-frequency resources of the eMBB are different from each other in an embodiment of the present application.
  • FIG. 3 is a schematic flowchart of two SR transmissions when the available time-frequency resources of the SR of the URLLC and the available time-frequency resources of the SR of the eMBB are the same in an embodiment of the present application.
  • FIG. 4 is a schematic flowchart of a method for processing a scheduling request according to another embodiment of the present application.
  • FIG. 5 is a schematic flowchart of a method for processing a scheduling request according to still another embodiment of the present application.
  • FIG. 6 is a schematic flowchart of a method for processing a scheduling request according to still another embodiment of the present application.
  • FIG. 7 is a schematic block diagram of an apparatus for processing a scheduling request according to an embodiment of the present application.
  • FIG. 8 is a schematic block diagram of an apparatus for processing a scheduling request according to another embodiment of the present application.
  • FIG. 9 is a schematic block diagram of an apparatus for processing a scheduling request according to an embodiment of the present application.
  • FIG. 10 is a schematic block diagram of an apparatus for processing a scheduling request according to another embodiment of the present application.
  • FIG. 11 is a schematic block diagram of an apparatus for processing a scheduling request according to an embodiment of the present application.
  • FIG. 12 is a schematic block diagram of an apparatus for processing a scheduling request according to another embodiment of the present application.
  • FIG. 13 is a schematic block diagram of an apparatus for processing a scheduling request according to an embodiment of the present application.
  • FIG. 14 is a schematic block diagram of an apparatus for processing a scheduling request according to another embodiment of the present application.
  • an LTE system for example, an LTE system, an LTE frequency division duplex (FDD) system, an LTE time division duplex (TDD) system, and a universal mobile.
  • Universal mobile telecommunication system UMTS
  • WiMAX worldwide interoperability for microwave access
  • PLMN public land mobile network
  • D2D device to device
  • M2M machine to machine
  • the device for processing the scheduling request may be a terminal device, and the terminal device may also be referred to as a user equipment, a mobile station, an MS, a mobile terminal, etc., and the terminal device
  • the radio access network (RAN) can communicate with one or more core network devices, for example, the terminal device can be a mobile phone (or "cellular" phone), a computer with communication function, etc., for example
  • the terminal device can also be a portable, pocket-sized, handheld, computer-integrated or in-vehicle mobile device.
  • the network device may be a device for communicating with the terminal device, and the network device may be an evolved base station (eNB or eNodeB) or an access point in an LTE system, or an in-vehicle device or a wearable device.
  • eNB evolved base station
  • eNodeB evolved base station
  • LTE Long Term Evolution
  • FIG. 1 shows a schematic diagram of a scheduling method 100 according to an embodiment of the present application.
  • the method 100 can be performed by a terminal device. As shown in FIG. 1, the method 100 includes:
  • the terminal device determines that a condition for triggering the first service scheduling request SR is satisfied.
  • the terminal device determines whether a priority of the first service is higher than a priority of a second service that has triggered or sent the scheduling request SR.
  • the terminal device determines that the priority of the first service that needs to request the uplink resource is higher than that of the second service that has triggered or sent the scheduling request SR according to the priority of the service.
  • the first service triggered by the higher priority and/or the transmitted SR is not affected by the second service with the lower priority or the transmitted SR, that is, it is sent according to the original period, so that it can be increased.
  • the triggering or sending opportunity of the SR of the first service improves the reliability of the SR triggered or sent by the first service, reduces the delay value, and improves the user experience.
  • the terminal device when the terminal device has the uplink data of the first service to be transmitted, when the terminal device does not send the uplink resource of the uplink data, it is determined that the condition for triggering the first service scheduling request SR is satisfied.
  • the terminal device sends an uplink resource to the network device by using the SR to request the RB resource to transmit the uplink data, and requests the uplink resource of the data of the first service.
  • the terminal device determines whether the priority of the first service is higher than the priority of the second service that has triggered or sent the scheduling request SR. That is, before the first service requests the uplink resource, when the second service is requested, the uplink resource is also requested, and the terminal device has triggered or sent the SR corresponding to the second service, and the terminal device determines the first service.
  • the terminal device determines that the priority of the first service is higher than the priority of the second service, after determining that the condition for triggering the first service scheduling request SR is satisfied, the terminal is triggered and/or sent.
  • the first service triggers and/or sends the SR that is not triggered by the second service and/or sent by the SR. influences. According to the original trigger and / or the cycle of sending SR.
  • the triggering and/or sending of the SR of the first service may be controlled by a timer, which is used to limit the sending of the SR.
  • a timer which is used to limit the sending of the SR.
  • the timer is not triggered and/or before the timer expires.
  • the SR of the first service is not sent, and the SR of the first service may be triggered and/or sent after the timer expires.
  • the triggering and/or transmission of the SR of the first service may also be independent of the timer.
  • the embodiments of the present application are not limited herein.
  • first service and the second service are merely for indicating two different priority services, and should not impose any limitation on the embodiments of the present application.
  • the method 100 may further include:
  • the terminal device When the uplink resource of the SR of the first service is different from the uplink resource of the SR of the second service, the terminal device triggers and/or transmits the SR of the first service and the SR of the second service independently of each other.
  • the sending and/or triggering of the SR of the first service and the SR of the second service may be mutually Independent, that is, mutual interference. It should be understood that when the resource for sending the SR of the first service and the SR resource for sending the first service are different, the triggering and/or sending period of the SR of the first service and the SR of the second service may be the same, The embodiments of the present application are not limited herein.
  • the first service is a URLLC service
  • the second service is an eMBB service.
  • each parallelogram is a periodic point
  • the interval between adjacent two periodic points is 2ms, which is an available time-frequency resource. All parallelograms are combined into another set of available time-frequency resources.
  • Each small rectangle is a periodic point, which is an available time-frequency resource. The interval between two adjacent periodic points is 3ms. All small rectangles are combined into a set of available time-frequency resources.
  • the SR of the eMBB is sent using a rectangular time-frequency resource.
  • the SR triggered by the URLLC is sent using the time-frequency resource of the parallelogram. Since the two sets of resources are different, the period of triggering or sending may be the same or different. It should be understood that the SR triggered by the URLLC may also be sent by using the time-frequency resource of the rectangle. The eMBB triggered SR is sent using the time-frequency resource of the parallelogram.
  • the embodiments of the present application are not limited herein.
  • the triggering and/or sending of the SR of the first service may be controlled by a first timer, where the first timer corresponds to the SR of the first service.
  • the first timer is used to limit the triggering or sending of the SR.
  • the terminal device does not trigger or send the SR of the first service before the first timer expires. After the first timer expires, the SR of the first service can be triggered or sent.
  • the triggering and/or sending of the SR of the second service may be controlled by a second timer, where the second timer corresponds to the SR of the second service.
  • the second timer is used to limit the triggering or sending of the SR.
  • the terminal device does not trigger or send the SR of the second service before the second timer expires. After the second timer expires, the SR of the second service can be triggered or sent.
  • triggering and/or sending of the SR of the first service may also be unaffected by the corresponding timer.
  • the embodiments of the present application are not limited herein.
  • the method 100 may further include:
  • the terminal device When the uplink resource of the SR of the first service is the same as the uplink resource of the SR of the second service, the terminal device only triggers and/or sends the SR of the first service, and does not trigger and/or does not send the second.
  • Business SR When the uplink resource of the SR of the first service is the same as the uplink resource of the SR of the second service, the terminal device only triggers and/or sends the SR of the first service, and does not trigger and/or does not send the second.
  • Business SR When the uplink resource of the SR of the first service is the same as the uplink resource of the SR of the second service, the terminal device only triggers and/or sends the SR of the first service, and does not trigger and/or does not send the second.
  • the resource for sending the SR of the first service is the same as the SR resource for sending the first service, since the priority of the first service is higher than the priority of the second service, / or send the SR of the first service, and the SR of the second service is no longer triggered and/or sent.
  • the SR of the second service may also be triggered and/or sent.
  • the sending time of the SR of the second service is related to the first service.
  • the sending time of the SR may be different, that is, sent in different subframes. For the case where only the first service exists, the SR sending moment of the first service may be calculated by formula (1):
  • n f is the current system frame number, and the range is 0 to 1023.
  • n s is the current slot number, the range is 0 to 19, N OFFSET, SR is the subframe offset, and SR PERIODICITY is the transmission period of the SR.
  • the SR of the first service can be calculated.
  • SR PERIODICITY ⁇ TTI. Since the TTIs of different services are different, even the resources of the SR transmitting the first service and the SR transmitting the first service are transmitted. The resources are the same, and the transmission time of the SR of the first service and the transmission time of the SR of the second service are also different.
  • the SR of the first service may further include indication information for indicating the first service, where the second The SR of the service may further include indication information for indicating the second service.
  • the SR since the SR does not include information related to the service, it only informs the network device that the terminal device has data to be transmitted, and the network device needs to allocate resources.
  • the SR does not include the amount of data of the service, the type of the service, or The TTI, CP, and other information of the resources required by the service. Therefore, when the network device receives an SR, it does not know which type of resource the SR requests, and therefore does not know which type of resource is scheduled for the terminal device.
  • the SR transmitting the two services when the uplink resource of the SR of the first service is the same as the uplink resource of the SR of the second service, the network device receives two SRs on the same resource.
  • the SR of the first service may further include indication information for indicating the first service
  • the SR of the second service may further include indication information for indicating the second service. It is used by the network device to identify the SRs corresponding to different services, so that different resources can be allocated to different services according to different services, so that the service data can be transmitted faster and the user experience can be improved.
  • the method 100 may further include:
  • the terminal device sets a duration value of the first timer related to the SR of the first service to zero;
  • the terminal device does not set a first timer related to the SR of the first service.
  • the triggering and/or sending of the SR of the first service may not be affected by the first timer, that is, the SR of the first service may be related to The duration value of the first timer is set to zero, or the first timer associated with the SR of the first service is not set.
  • the triggering and/or sending of the SR of the first service is performed according to the period of the original SR resource of the first service, which may increase the chance of triggering and/or sending the SR of the high priority service, and improve the high priority.
  • the reliability of data transmission of the service improves the user experience.
  • the first timer of the SR corresponding to the first service controls triggering or sending of the SR of the first service
  • the second timer of the SR corresponding to the second service controls the The triggering or sending of the SR of the second service.
  • the first timer of the SR corresponding to the first service is started.
  • the duration of the first timer is less than the duration of the second timer associated with the SR of the second service.
  • the triggering and/or sending opportunity of the SR of the first service needs to be increased. Since the sending period of the SR configured by the system is short, in order to avoid excessive Sending an SR, the first timer of the SR corresponding to the first service may be started, used to control triggering and/or sending of the SR of the first service, and because the priority of the first service is high and the second The priority of the service. Therefore, the triggering and/or sending opportunity of the SR of the first service should be more than the triggering and/or sending opportunity of the SR of the second service, and the triggering and/or sending of the SR of the second service is affected. The second timer is controlled. Therefore, the duration of the first timer should be less than the duration of the second timer associated with the SR of the second service.
  • the method 100 may further include:
  • the terminal device stops the second timer
  • the terminal device sets the duration value of the second timer to the duration value of the first timer, and restarts the second timer.
  • the terminal device may set the duration value of the second timer to the duration value of the first timer. That is, the first timer and the second timer are both started, and the durations of the two timers are the same, so that the SR of the first service and the SR of the second service can be triggered according to the duration value of the timer. And/or sending, thereby increasing the SR of the first service and the SR triggering and/or sending the SR of the second service, and improving the reliability of data transmission of the two services.
  • triggering and/or sending of the SR of the first service may be controlled according to the duration value of the first timer, and may not be affected by the first timer.
  • the implementation of the present application is not limited herein.
  • the triggering and/or sending of the SR of the first service may be affected by the first timer related to the first service, and the SR triggering and/or sending the SR of the second service may be affected by the second
  • the impact of the second timer is related to the service.
  • the duration of the first timing is less than the duration of the second timer, or the triggering and/or sending of the SR of the first service may not be the first.
  • the effect of the timer, the SR triggering and/or sending the SR of the second service may be affected by the second timer.
  • the first service is a URLLC service
  • the second service is an eMBB service.
  • the available time-frequency resources of the SR of the URLLC of the embodiment of the present application are the same as the available time-frequency resources of the eMBB, and the SR of the eMBB is The transmission is affected by the timer, and the SRLC of the URLLC is not affected by the timer.
  • each small rectangle in FIG. 3 is a periodic point, which is an available time-frequency resource, and all the small rectangles are combined into a set of available uplink resources.
  • the resource period of the SR carrying the eMBB is 3 ms
  • the forbidden duration value set by the timer is the resource period of the SR of 3 eMBBs, that is, the resource period of the SRs of the three eMBBs may be sent once
  • the time of T0 is assumed to be the SR of the eMBB.
  • the first cycle point of the resource the terminal device triggers the SR of the eMBB at time T0.
  • the SR of the eMBB can only be sent at the time of T0+9ms, that is, at the fourth cycle point and the Seven cycle points are transmitted, and at time T0+3ms (second cycle point), T0+6ms time (second cycle point), T0+12ms time (fifth cycle point), T0+15ms time (first Six cycle points) cannot be sent. It is assumed that the terminal device triggers the SR of the eMBB at the time of T0+1ms.
  • the terminal device can only send the SR of the eMBB after the time T0+10ms, that is, only when the timer expires, but Since there is no time-frequency resource available for the SR of the eMBB at the time T0+10ms, it can only be sent until T0+12ms (the fifth cycle point).
  • the terminal device triggers the SR of the URLLC
  • the T0 time is a cycle point of the resource of the URL of the URLLC
  • the terminal device triggers the SR of the URLLC
  • the SR of the URLLC may be sent at each cycle point. From the time T0, for example, within 9ms.
  • the SR of the URLLC can be sent at time T0 (first cycle point), T0+3ms time (second cycle point), T0+6ms (third cycle point), and T0+9ms (fourth cycle point).
  • the SR of the URLLC can be sent four times, and from the time of T0, within 9ms, and the SR of the eMBB can only be sent once due to the limitation of the timer.
  • the terminal device triggers the SR of the URLLC at time T0+1ms
  • the terminal device can be at T0+3ms (second cycle point) time, T0+6ms (third cycle point) and T0+9ms (fourth cycle) Point), from the time T1, in the same time, for example, within 9ms
  • the SR of the URLLC can be sent three times, and the SR of the eMBB can only be sent once.
  • the SR opportunity triggered or sent by the high-priority URLLC is increased, thereby reducing the waiting time for obtaining the resources required for sending the URLLC service data, ensuring the reliability of the URLLC service data transmission, and improving the user experience.
  • the method 100 may further include:
  • the terminal device stops the second timer, and associates triggering or sending of the SR of the second service with the first timer.
  • the second timer may be stopped, that is, only one duration A shorter first value is used to control SR triggering and/or transmission of both services.
  • the SR of the first service and the SR of the second service may be triggered and/or sent according to the duration value of the first timer, thereby increasing the SR of the first service and the SR trigger of the second service or
  • the opportunity to send SRs improves the reliability of data transmission for both services.
  • triggering and/or sending of the SR of the first service may be controlled according to the duration value of the first timer, and may not be affected by the first timer.
  • the implementation of the present application is not limited herein.
  • the method 100 may further include:
  • the terminal device stops the second timer related to the SR of the second service, and restarts the second timer after modifying the duration value of the second timer to be related to the SR of the first service.
  • the terminal device may stop the second timer, set the duration value of the second timer to be related to the first service with a higher priority, and restart the second timer, that is, the duration of the second timer.
  • the value is set to be shorter, so that the second service can trigger and/or send the SR according to the second timer duration value with the shorter duration value, and the triggering and/or sending opportunity of the SR of the second service can be increased. Improve the reliability of data transmission of the second service.
  • triggering and/or sending of the SR of the first service may be controlled according to the duration value of the second timer, and may not be affected by the second timer.
  • the implementation of the present application is not limited herein.
  • the terminal device calculates the number of times of sending the SR of the first service from zero until the maximum number of transmissions is accumulated.
  • the terminal device After the terminal device triggers and/or sends the SR of the second service, the terminal device starts a timer corresponding to the SR of the second service, and before the scheduling authorization is obtained, the terminal device triggers or The SR of the first service is sent. Or, after the terminal device triggers or sends the SR of the first service, the terminal device starts a timer corresponding to the SR of the first service, and the terminal device triggers or sends the first service before obtaining the scheduling authorization. SR. At this time, there are two ways to count the cumulative number of SRs sent by the first service. One is that when the terminal device ignores the timer, the number of SRs of the first service is calculated from zero until the system stipulates The maximum number of transmissions.
  • the terminal device releases the time-frequency resource of the SR that carries the first service, and requests the resource by initiating a contention random access procedure.
  • the counting method of the cumulative number of SRs of the first service is the basis of the number of SRs triggered or sent in the second service before the timer is stopped.
  • the device continues to accumulate the maximum number of transmissions specified by the system. If the network device does not request the resources scheduled by the network device, the terminal device releases the resources of the SR that carries the first service, and initiates the contention of the random access. Process to request resources.
  • the foregoing first service and the second service are only used to indicate that the priorities of the two services are different, and the first embodiment of the application may also be restricted.
  • the priority of the first service may also be
  • the priority of the second service may be more than two types of services. As long as the delay requirements of the services are different, or the reliability requirements are different, the technical solution of the embodiment of the present application may be used. This is not a limitation.
  • the present application may be implemented according to other sequences, for example, delay values of different services, reliability order, and the like. There are no restrictions here.
  • the terminal device determines that the priority of the first service that needs to request the uplink resource is higher than the priority of the second service that has triggered or sent the scheduling request SR according to the priority of the service.
  • the SR that is triggered or sent by the first service with a higher priority may not be affected by the timer corresponding to the second service with the lower priority, or may be according to the timing related to the SR of the first service.
  • Controlling to trigger and/or send, and the second service may also trigger and/or send the SR of the first service according to the duration value of the first timer, so that the SR of the first service may be increased.
  • the SR triggering or sending opportunity of the second service improves the reliability of the trigger or the sending SR, reduces the delay value, and improves the user experience.
  • FIG. 4 is a schematic flowchart of a method 200 for processing a scheduling request according to an embodiment of the present application.
  • the method 200 may be performed by a terminal device, where the method 200 includes :
  • the terminal device determines that a condition for triggering the first service scheduling request SR is satisfied.
  • S220 The terminal device determines whether the priority of the first service is higher than a priority of the second service that has triggered or sent the scheduling request SR.
  • the terminal device when the terminal device determines that the priority of the first service is lower than the priority of the second service, the terminal device does not trigger and/or does not before the timer associated with the SR of the second service times out. Send the SR of the first service.
  • the terminal device determines, according to the priority condition of the service, that the priority of the first service that needs to request the uplink resource is lower than the second that has been triggered and/or has sent the scheduling request SR.
  • the priority of the service before the timer associated with the SR of the second service times out, the first service with a lower priority does not trigger and/or does not send the SR, and thus, according to the second service
  • the SR-related timer is used to control the triggering and/or sending of the SR of the first service, so that the triggering or sending opportunity of the SR of the first service may be increased, and the reliability of the SR triggered or sent by the first service may be improved. Improve the user experience.
  • the terminal device when the terminal device has the uplink data of the first service to be transmitted, when the terminal device does not send the uplink resource of the uplink data, it is determined that the condition for triggering the first service scheduling request SR is satisfied.
  • the terminal device sends an uplink resource to the network device by using the SR to request the RB resource to transmit the uplink data, and requests the uplink resource of the data of the first service.
  • the terminal device determines whether the priority of the first service is higher than the priority of the second service that has triggered and/or sent the scheduling request SR. That is, before the first service requests the uplink resource, if the second service is requested, the uplink resource is also requested, and the SR corresponding to the second service is triggered or sent, and the terminal device determines the priority of the first service.
  • the relationship between the priority of the second service and the priority of the second service can be differentiated according to the priorities of different services.
  • the terminal device determines that the priority of the first service is lower than the priority of the second service, before the timer associated with the SR of the second service times out, the first priority is lower.
  • the service does not trigger and/or does not send the SR, such that the triggering or sending of the SR of the first service can be controlled according to a timer associated with the SR of the second service.
  • the triggering and/or sending of the SR of the second service may be controlled by the timer, which is used to limit the sending of the SR.
  • the timer is running, the timer is not triggered before the timer expires. / or sending the SR of the second service, after the timer expires, the SR of the second service can be triggered and/or sent.
  • the triggering and/or transmission of the SR of the second service may also be independent of the timer.
  • the embodiments of the present application are not limited herein.
  • first service and the second service are merely for indicating two different priority services, and should not impose any limitation on the embodiments of the present application.
  • the duration value of the timer associated with the SR of the second service is smaller than the duration value of the timer associated with the SR of the first service.
  • the SR of the first service is When the SR of the second service is affected by the timer, the duration of the timer associated with the SR of the second service is smaller than the duration of the timer associated with the SR of the first service, so that the same
  • the triggering and/or sending opportunity of the SR of the second service is more than the SR triggering and/or sending opportunity of the first service, and the SR triggering or sending opportunity of the second service may be increased to improve the triggering and / / Send the reliability of the SR of the second service to improve the user experience.
  • FIG. 5 is a schematic flowchart of a method 300 for processing a scheduling request according to an embodiment of the present application.
  • the method 300 may be performed by a terminal device, where the method 300 includes :
  • the terminal device determines that a condition for triggering the first service scheduling request SR is satisfied.
  • the terminal device determines whether the uplink resource of the scheduling request SR of the first service is the same as the uplink resource of the SR that is used to trigger or send the second service;
  • the terminal device when the terminal device determines that the uplink resource of the SR of the first service is different from the uplink resource of the SR of the second service, the terminal device triggers or sends the SR of the first service and the second service independently of each other. SR.
  • the method for processing a scheduling request provided by the embodiment of the present application before the first service requests the uplink resource, if the second service is requested, the uplink resource is also requested, and the SR corresponding to the second service is triggered or sent.
  • the terminal device may determine that the uplink resource of the SR for transmitting the first service and the uplink resource of the SR for transmitting the first service are different, and the sending and/or triggering of the SR of the first service and the SR of the second service may be They are independent of each other, that is, they do not interfere with each other.
  • the efficiency of sending or triggering the SR of the first service and the SR of the second service can be improved to ensure the reliability of the SR.
  • the triggering and/or sending of the SR of the first service may be controlled by a first timer, where the first timer corresponds to the SR of the first service.
  • the first timer is used to limit the triggering or sending of the SR.
  • the terminal device does not trigger or send the SR of the first service before the first timer expires. After the first timer expires, the SR of the first service can be triggered or sent.
  • the triggering and/or sending of the SR of the second service may be controlled by a second timer, where the second timer corresponds to the SR of the second service.
  • the second timer is used to limit the triggering or sending of the SR.
  • the terminal device does not trigger or send the SR of the second service before the second timer expires. After the second timer expires, the SR of the second service can be triggered or sent.
  • triggering and/or sending of the SR of the first service may also be unaffected by the corresponding timer.
  • the embodiments of the present application are not limited herein.
  • the method 300 may further include:
  • the terminal device determines that the uplink resource of the SR request of the first service is the same as the uplink resource of the SR request of the second service, and the priority of the first service is lower than the priority of the second service, Before the SR associated timer of the second service times out, the terminal device does not trigger and/or does not send the SR of the first service.
  • the terminal device determines that the uplink resource of the SR request of the first service is the same as the uplink resource of the SR request of the second service, and the priority of the first service is lower than the priority of the second service
  • the first service with lower priority does not trigger and/or does not send the SR, and may be controlled according to a timer associated with the SR of the second service.
  • the triggering and/or sending of the SR of the first service may increase the triggering and/or sending opportunity of the SR of the first service, improve the reliability of the SR triggered and/or sent by the first service, and improve the user experience.
  • the triggering and/or non-transmission of the SR of the second service may be controlled by a timer associated with the SR of the second service, the timer is used to limit the sending of the SR, when the timer is running, Before the timer expires, the SR of the second service is not triggered and/or sent, and the SR of the second service may be triggered and/or sent after the timer expires.
  • the triggering and/or transmission of the SR of the second service may also be independent of the timer.
  • the embodiments of the present application are not limited herein.
  • the sending period of the SR of the first service and the SR of the second service may be the same,
  • the embodiments of the present application are not limited herein.
  • FIG. 6 is a schematic flowchart of a method 400 for processing a scheduling request according to an embodiment of the present application.
  • the method 400 may be performed by a terminal device, where the method 400 includes :
  • the terminal device determines that the condition for triggering the first service scheduling request SR is satisfied.
  • the terminal device determines the service to be sent, that is, when the condition for triggering the first service scheduling request SR is satisfied, the non-scheduled resource for transmitting the data of the first service is also acquired, and at this time, the non-scheduled resource is utilized.
  • the scheduling resource sends the data of the first service
  • the terminal device does not stop triggering and/or sending the SR of the first service or the SR of the second service. In this way, it can be ensured that the data of the service can be effectively transmitted to the network device, that is, when the data of the service is transmitted by using the non-scheduled resource, the dedicated scheduling resource is also requested at the same time. Increased reliability of transmitting service data.
  • the method 400 may further include:
  • the terminal device After the terminal device successfully transmits the data of the service by using the non-scheduled resource or the contention resource, the triggering and/or sending of the SR of the service is cancelled.
  • the terminal device when the data of the service is sent by using the non-scheduled resource, in order to ensure that the data can be successfully sent, the terminal device does not stop triggering and/or sending the SR trigger or transmission of the service, but when determining to use the When the non-scheduled resource successfully sends the data of the service, the triggering and/or sending of the SR of the service is cancelled.
  • the network device may be configured to send the first indication information, for example, the first indication information may be that the network device determines to successfully send the data of the first service or the data of the second service by using the non-scheduled resource, to the The terminal device sends an acknowledgement message, for example, an ACK (Acknowledgement).
  • the terminal device stops triggering or sending the SR of the service. In this way, the accuracy of data transmission can be ensured, and the triggering or sending of redundant SRs can be avoided, the waste of resources and the increase of interactive signaling are avoided, and the user experience is better.
  • the network device may also notify the terminal device whether to allow the SR to be sent after the data or the BSR of the service is sent by using the non-scheduled resource, which is not limited herein.
  • the terminal device when the SR has been sent to the most limited number of times, or the network device has scheduled resources for the terminal device according to the SR, the terminal device also cancels triggering and/or transmitting the SR.
  • the embodiments of the present application are not limited herein.
  • the method 400 further includes:
  • the terminal device When the terminal device acquires a transmission resource for transmitting data of a service having a lower priority than the service, canceling the SR that triggers and/or transmits the service;
  • the terminal device transmits data of the service using a transmission resource of data of a service having a lower priority than the service.
  • the data of the different service may be sent according to the priority order of the different services, that is, the first service is sent first.
  • the data of the service since the data of the service already has the transmitted resource, at this time, the terminal device determines to cancel the trigger and/or the SR that sends the service, so that unnecessary triggering or sending of the SR can be reduced, and signaling is reduced. Interaction, saving resources and improving user experience.
  • the priority order of the data that is sent by the terminal device by using the non-scheduled resource is: a buffer status report BSR including the data volume of the service, a data of the service, and a semi-persistent scheduling SPS confirmation.
  • the data of the service when the data of the service is transmitted by using the non-scheduled resource, the data may be sent in the order of priority of the service, that is, the data of the high priority service is sent first.
  • the BSR of the high-priority service can be preferentially sent.
  • the BSR can carry more information than the SR.
  • the network device After receiving the SR sent by the terminal device, the network device only knows the terminal. The device has data transmission, and does not know how much data needs to be transmitted.
  • the network device first allocates a small amount of uplink authorization to the terminal device, and the terminal device sends the BSR, and therefore, the terminal After the device obtains the resource for sending the service, if the resource cannot be saved, the data is first placed in the BSR, and the BSR containing the service data is sent preferentially, and then the service data is sent. Therefore, for the case where only one type of service exists, it is sent in the order of BSR ⁇ the data of the first service ⁇ semi-persistent scheduling (SPS), and the semi-persistent scheduling is a network device.
  • SPS semi-persistent scheduling
  • the physical downlink control channel indicates the current scheduling information of the terminal device, and after the terminal device identifies the SPS, the current scheduling information is saved, and the fixed periodicity is the same.
  • the transmission or reception of data of the service is performed on the time-frequency resource, and the SPS transmission can fully utilize the characteristics of the periodic arrival of the data packet, and the one-time authorization and periodic use can effectively save the PDCCH resource used by the LTE system for scheduling indication.
  • the BSR ⁇ the first service data ⁇ SPS confirmation ⁇ the lower priority than the first service may be reported according to the buffer status including the data volume of the first service.
  • the BSR ⁇ is transmitted in the order of the service data having a lower priority than the first service.
  • the priority order of the URLLC service is higher than the priority of the eMBB service, and the data of the BSR ⁇ URLLC service including the URLLC service data amount is used.
  • SPS confirmation Sequential transmission of the number of BSR ⁇ eMBB services including the amount of eMBB service data.
  • the transmission may be performed according to the foregoing sending order, which is not limited herein.
  • the terminal device needs to trigger the BSR, that is, the BSR needs to be sent.
  • the transmission of the plurality of service data may be performed in the order of priority according to the order of the foregoing, and the implementation of the present application is not limited herein.
  • the terminal device when the data of the service is sent by using the non-scheduled resource, the terminal device does not stop triggering or sending the SR of the service, but determines that the data transmission of the service is successful. Then, the SR that triggers or sends the first service is stopped, and the related data of the high-priority service is preferentially transmitted according to the priority order of the service, and the transmission delay of the data of the high-priority service is reduced. To improve the user experience.
  • FIG. 7 shows a schematic block diagram of an apparatus 500 for processing a scheduling request, the apparatus 500 for processing a scheduling request including a processor 510 and a memory 520 storing a program for execution by the processor 510, in accordance with an embodiment of the present application:
  • the processor 510 is configured to determine that a condition for triggering a scheduling request of the first service is satisfied
  • the processor 510 is further configured to determine whether a priority of the first service is higher than a priority of the second service that has triggered or sent the scheduling request SR;
  • processor 510 determines that the priority of the first service is higher than the priority of the second service, triggering and/or transmitting the scheduling request SR of the first service.
  • the device for processing the scheduling request provided by the embodiment of the present application can determine that the priority of the first service that needs to request the uplink resource is higher than the priority of the second service that has triggered or sent the scheduling request SR according to the priority of the service.
  • the first service triggered by the higher priority and/or the transmitted SR is not affected by the second service triggered by the lower priority and/or the SR sent, that is, according to the original cycle, so that The triggering and/or sending opportunity of the SR of the first service is increased, the reliability of the SR triggered or sent by the first service is improved, the delay value is reduced, and the user experience is improved.
  • the various components in the apparatus 500 that process the scheduling request communicate with each other via a communication connection, i.e., between the processor 510 and the memory 520 via internal connection paths, to communicate control and/or data signals.
  • a communication connection i.e., between the processor 510 and the memory 520 via internal connection paths.
  • the processor may be an integrated circuit chip with signal processing capabilities.
  • each step of the foregoing method embodiment may be completed by an integrated logic circuit of hardware in a processor or an instruction in a form of software.
  • the above processor 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.
  • 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 application 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 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, and the processor reads the information in the memory and combines the hardware to complete the steps of the above method.
  • the processor 510 is further configured to: when the uplink resource of the SR of the first service is different from the uplink resource of the SR of the second service, the processor 510 is further configured to: The ground triggers or sends the SR of the first service and the SR of the second service.
  • the first timer of the SR corresponding to the first service controls triggering or sending of the SR of the first service, where the processor 510 further before the first timer expires. Used to: SR that does not trigger or not send the first service.
  • the second timer of the SR corresponding to the second service controls triggering or sending of the SR of the second service, where the processor 510 further before the second timer expires. Used to: SR that does not trigger or not send the second service.
  • the processor 510 is further configured to: before the device that processes the scheduling request obtains the scheduling authorization, the device that processes the scheduling request calculates the number of times of sending the SR of the first service from zero, Until the maximum number of transmissions is accumulated.
  • the processor 510 is further configured to: when the uplink resource of the SR of the first service is the same as the uplink resource of the SR of the second service, triggering or sending only the SR of the first service The SR of the second service is no longer triggered or sent.
  • the processor 510 is further configured to: set a duration value of the first timer associated with the SR of the first service to zero; or not set an SR related to the first service. The first timer of the union.
  • the processor 510 is further configured to: control, by the first timer of the SR corresponding to the first service, triggering or sending the SR of the first service, and corresponding to the SR of the second service.
  • the second timer controls the triggering or sending of the SR of the second service, and the duration value of the first timer is smaller than the duration value of the second timer associated with the SR of the second service.
  • the processor 510 is further configured to: stop the second timer; set a duration value of the second timer to a duration value of the first timer, and restart the second timer. Device.
  • the processor 510 is further configured to: stop the second timer, and associate the triggering or sending of the SR of the second service with the first timer.
  • the processor 510 is further configured to: stop a second timer associated with the SR of the second service, and modify a duration value of the second timer and an SR of the first service. After the correlation, the second timer is restarted.
  • a duration value of a timer associated with the SR of the first service is smaller than a duration value of a timer related to the SR of the second service.
  • the processor 510 can implement the module implementation, and the memory 520 can be implemented by the storage module.
  • the apparatus 600 for processing a scheduling request may include a processing module 610 and a storage module 620.
  • the apparatus 500 for processing a scheduling request shown in FIG. 7 or the apparatus 600 for processing a scheduling request shown in FIG. 8 can implement the various processes implemented in the foregoing embodiments of FIG. 1 to FIG. 3 and the various embodiments of the method 100, in order to avoid Repeat, no longer repeat them here.
  • FIG. 9 shows a schematic block diagram of an apparatus 700 for processing a scheduling request in accordance with an embodiment of the present application.
  • apparatus 700 for processing a scheduling request includes a processor 710 and a memory 720 that stores programs for execution by the processor 710:
  • the processor 710 is configured to determine that a condition for triggering a scheduling request of the first service is met
  • the processor 710 is further configured to determine whether a priority of the first service is higher than a priority of the second service that has triggered and/or sent the scheduling request SR;
  • the processor 710 is further configured to: when determining that the priority of the first service is lower than the priority of the second service, do not trigger and/or not send before the timer associated with the SR of the second service times out The SR of the first service.
  • the device for processing the scheduling request provided by the embodiment of the present application can determine that the priority of the first service that needs to request the uplink resource is lower than the second service that has been triggered and/or has sent the scheduling request SR according to the priority of the service.
  • Priority when the timer associated with the SR of the second service times out, the first service with a lower priority does not trigger and/or does not send the SR, and thus, according to the SR with the second service
  • the associated timer is used to control the triggering or sending of the SR of the first service, so that the triggering and/or sending opportunity of the SR of the first service can be increased, and the reliability of the SR triggered or sent by the first service is improved, and the reliability is improved. user experience.
  • the various components in the device 700 that process the scheduling request communicate with each other via a communication connection, i.e., between the processor 710 and the memory 720, via an internal connection path, to communicate control and/or data signals.
  • a communication connection i.e., between the processor 710 and the memory 720, via an internal connection path, to communicate control and/or data signals.
  • the processor may be an integrated circuit chip with signal processing capabilities.
  • each step of the foregoing method embodiment may be completed by an integrated logic circuit of hardware in a processor or an instruction in a form of software.
  • the above processor 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.
  • 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 application 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 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, and the processor reads the information in the memory and combines the hardware to complete the steps of the above method.
  • the duration value of the timer associated with the SR of the second service is smaller than the duration value of the timer associated with the SR of the first service.
  • the processor 710 may implement a module implementation, and the memory 720 may be implemented by a storage module.
  • the apparatus 800 for processing a scheduling request may include a processing module 810 and a storage module 820.
  • the apparatus 700 for processing a scheduling request shown in FIG. 9 or the apparatus 800 for processing a scheduling request shown in FIG. 10 can implement the various processes implemented in the foregoing embodiments of FIG. 2 to FIG. 4 and the various embodiments of the method 200, in order to avoid Repeat, no longer repeat them here.
  • FIG. 11 shows a schematic block diagram of an apparatus 900 for processing a scheduling request in accordance with an embodiment of the present application.
  • apparatus 900 for processing a scheduling request includes a processor 910 and a memory 920 that stores programs for execution by the processor 910:
  • the processor 910 is configured to determine that a condition for triggering a scheduling request of the first service is met
  • the processor 910 is further configured to determine whether an uplink resource of the scheduling request SR of the first service is the same as an uplink resource of an SR that is used to trigger and/or send the second service;
  • the processor 910 is further configured to trigger and/or send the SR of the first service and the second independently of each other when determining that the uplink resource of the SR of the first service is different from the uplink resource of the SR of the second service.
  • Business SR is further configured to trigger and/or send the SR of the first service and the second independently of each other when determining that the uplink resource of the SR of the first service is different from the uplink resource of the SR of the second service.
  • the device for processing the scheduling request requests the uplink resource when the first service requests the uplink resource, and the SR corresponding to the second service is triggered and/or sent.
  • the device that processes the scheduling request determines that the uplink resource of the SR for transmitting the first service and the uplink resource of the SR for transmitting the first service are different, the SR of the first service and the SR of the second service are sent.
  • And/or triggers can be independent of each other, ie without interference.
  • the efficiency of sending and/or triggering of the SR of the first service and the SR of the second service may be improved to ensure the reliability of the SR.
  • the various components in the device 900 that process the scheduling request communicate with each other via a communication connection, i.e., between the processor 910 and the memory 920, through an internal connection path, and communicate control and/or data signals.
  • a communication connection i.e., between the processor 910 and the memory 920, through an internal connection path, and communicate control and/or data signals.
  • the processor may be an integrated circuit chip with signal processing capabilities.
  • each step of the foregoing method embodiment may be completed by an integrated logic circuit of hardware in a processor or an instruction in a form of software.
  • the above processor 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.
  • 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 application 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 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, and the processor reads the information in the memory and combines the hardware to complete the steps of the above method.
  • the first timer of the SR corresponding to the first service controls triggering or sending of the SR of the first service, where the processor 710 further before the first timer expires. Used to: SR that does not trigger and/or does not send the first service.
  • the second timer of the SR corresponding to the second service controls triggering or sending of the SR of the second service, where the processor 710 further before the second timer expires. Used to: SR that does not trigger or not send the second service.
  • the processor 710 is further configured to: before the device that processes the scheduling request obtains the scheduling authorization, the device that processes the scheduling request calculates the number of times the SR of the first service is sent from zero. Until the maximum number of transmissions is accumulated.
  • a duration value of a timer associated with the SR of the second service is smaller than a duration value of a timer associated with the SR of the first service.
  • the processor 910 may be implemented by a processing module
  • the memory 920 may be implemented by a storage module.
  • the terminal device 1100 can include a processing module 1110 and a storage module 1120.
  • the apparatus 900 for processing a scheduling request shown in FIG. 11 or the apparatus 1100 for processing a scheduling request shown in FIG. 12 can implement the various processes implemented in the foregoing embodiments of FIG. 2 to FIG. 5 and the various embodiments of the method 300, in order to avoid Repeat, no longer repeat them here.
  • FIG. 13 shows a schematic block diagram of an apparatus 1200 for processing a scheduling request in accordance with an embodiment of the present application.
  • apparatus 1200 for processing a scheduling request includes a processor 1210 and a memory 1220 that stores programs for execution by the processor 1210:
  • the processor 1210 is configured to determine that a condition for triggering the first service scheduling request SR is satisfied
  • the processor 1210 is further configured to: when the data of the first service is sent by using a non-scheduled resource or a contention resource, triggering and/or transmitting the scheduling request SR suspended for the first service is not cancelled.
  • the apparatus for processing a scheduling request provided by the embodiment of the present application does not stop triggering and/or transmitting the SR of the service when the data of the service is sent by using the non-scheduled resource, but only after determining that the data transmission of the service is successful.
  • the scheduling request SR that is suspended for the service is cancelled, the reliability of the service data transmission is ensured, and the user experience is improved.
  • the various components in the device 1200 that handles the scheduling request communicate with each other via a communication connection, i.e., between the processor 1210 and the memory 1220, via an internal connection path, and communicate control and/or data signals.
  • a communication connection i.e., between the processor 1210 and the memory 1220, via an internal connection path, and communicate control and/or data signals.
  • the processor may be an integrated circuit chip with signal processing capabilities.
  • each step of the foregoing method embodiment may be completed by an integrated logic circuit of hardware in a processor or an instruction in a form of software.
  • the above processor 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.
  • 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 application 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 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, and the processor reads the information in the memory and combines the hardware to complete the steps of the above method.
  • the processor 1210 is further configured to: after the data of the service is successfully sent by using the non-scheduled resource or the contention resource, cancel the scheduling request SR that is suspended for the service.
  • the processor 1210 is further configured to: when acquiring a sending resource for sending data of a service with a lower priority than the service, canceling a scheduling request SR that is suspended for the service .
  • the data of the service is transmitted using a transmission resource of data of a service having a lower priority than the service.
  • the processor 1210 is further configured to: use the non-scheduled resource to send the data of the service in a priority order: a buffer status report BSR including the data quantity of the service.
  • the data of the service > semi-persistent scheduling SPS acknowledgment > the data of the BSR whose data amount of the service having a lower priority than the service is lower than the priority of the service.
  • the processor 1210 may implement a module implementation, and the memory 1220 may be implemented by a storage module.
  • the terminal device 1300 can include a processing module 1310 and a storage module 1320.
  • the terminal device 1200 shown in FIG. 13 or the terminal device 1300 shown in FIG. 14 can implement the various processes implemented in the foregoing embodiments in the embodiment shown in FIG. 6 and in the method 400. To avoid repetition, details are not described herein again.
  • the embodiment of the present application further provides a computer readable medium for storing computer program code, the computer program comprising instructions for executing the method for processing a scheduling request of the various embodiments of the present application described above.
  • the readable medium may be a read-only memory (ROM) or a random access memory (RAM), which is not limited in this embodiment of the present application.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
  • the technical solution of the present application which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

Landscapes

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

Abstract

本申请提供了一种处理调度请求的方法和装置，该方法包括：终端设备确定触发第一业务调度请求SR的条件满足；该终端设备确定该第一业务的优先级是否高于已触发或已发送调度请求SR的第二业务的优先级；当该终端设备确定该第一业务的优先级高于该第二业务的优先级时，触发和/或发送该第一业务的SR。本申请提供的处理调度请求的方法，能根据业务的优先级情况，优先级较高的第一业务触发或者发送的SR不受该优先级较低的第二业务触发或者发送的SR的影响，可以增加该第一业务的SR的触发或者发送机会，提高该第一业务触发或者发送的SR的可靠性，提高用户体验。

Description

处理调度请求的方法和装置
本申请要求于2017年1月26日提交中国专利局、申请号为201710057477.7、申请名称为“调度请求的方法和终端设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，并且更具体地，涉及通信领域中一种处理调度请求的方法和装置。
背景技术
在长期演进(long term evolution，LTE)系统，调度请求(scheduling request，SR)是用户设备(User Equipment，UE)向网络设备申请资源用于新数据传输的一种方式。若连接态UE在没有上行授权时且有SR资源时，先发送SR，请求分配少量资源。SR属于物理层的信息，UE发送SR这个动作的本身不需要无线承载(radio bearer，RB)资源，可以通过物理上行链路控制信道(physical uplink control channel，PUCCH)传输。网络设备成功解码到某个UE的SR信号之后，可能会通过下行控制消息(downlink control information，DCI)给该UE分配RB资源，但不能保证网侧每次都会分配RB。有些时候虽然UE发送了SR信号，但网侧并没有解码到。UE发出了SR信号后，不要期望网络设备一定会在接下来的某个时刻分配RB资源，很多时候，UE为了得到上行RB资源，是需要多次发送SR申请的。由于SR发送的周期一般很短，为了避免UE发送不必要的SR，引入禁止定时器(sr-Prohibit Timer)，该定时器用于监视在PUCCH中传输的SR信号，当该定时器正在运行时，是不能发送SR的，只有等该定时器超时了才能继续发送SR，直到达到最大发送次数(dsr-Trans Max)之后，会释放SR资源，采用随机竞争接入过程的竞争方式来获取调度机会。这样大大降低了PUCCH上的负载。
当UE触发了一个SR时，该SR就处于“Pending”态，意思就是UE准备但还没有向网络设备发送SR。但是，当UE已经组装了一个媒体接入控制协议数据单元(medium access control protocol data unit，MAC PDU)，并且该PDU包含了最近触发的缓存状态报告(buffer status report，BSR)控制单元，或者上行授权提供的资源可以容纳所有待传的数据，那么处于“Pending”态的SR就会被取消，同时禁止定时器也会停止。
随着智能终端(smart phone)和设备智能业务的广泛应用，未来主要有三大类业务：超宽带(enhanced mobile broadband，eMBB)业务，比如视频；低时延高可靠(ultra reliable and low latency communication,URLLC)业务，比如无人机的控制；海量机器类通信(massive machine type Communication，mMTC)业务，比如抄表。对于不同领域的业务，由于使用发送不同业务的资源参数配置不同，该参数配置也可以称为“numerology”，例如，不同业务配置的循环前缀(cyclic prefix，CP)长度、传输时间间隔(transmission time  interval，TTI)和子载波间隔不同，因此，不同领域的业务会对传输业务数据的时延有着不同的要求。按照下一代无线通信的时延要求，对于URLLC业务的上行发送时延需求0.5ms，对于eMBB业务的上行发送时延需求是4ms。
目前，只有一个禁止定时器控制所有业务的SR发送，无法实现不同业务的差异化需求。
发明内容
本申请提供一种处理调度请求的方法和装置，能够增加高优先级的业务触发调度请求和/或发送的调度请求的机会，减少高优先级业务数据的发送时延，用户体验好。
第一方面，提供了一种处理调度请求的方法，该方法包括：终端设备确定触发第一业务调度请求SR的条件满足；终端设备请求第一业务的上行资源；当该终端设备确定该第一业务的优先级是否高于已触发或已发送调度请求SR的第二业务的优先级；该终端设备确定该第一业务的优先级高于该第二业务的优先级时，触发和/或发送该第一业务的SR。
第一方面提供的处理调度请求的方法，能根据业务的优先级情况，当确定当前需要请求上行资源的第一业务的优先级高于已触发或已发送调度请求SR的第二业务的优先级时，优先级较高的第一业务触发或者发送的SR不受该优先级较低的第二业务触发和/或发送的SR的影响，即按照原有的周期发送，这样，可以增加该第一业务的SR的触发或者发送机会，提高该第一业务触发或者发送的SR的可靠性，减小时延值，提高用户体验。
在第一方面的一种可能的实现方式中，该方法还包括：当该第一业务的SR的上行资源与该第二业务的SR的上行资源不同时，该终端设备互不干涉地触发或发送该第一业务的SR和该第二业务的SR。
在第一方面的一种可能的实现方式中，对应于该第一业务的SR的第一定时器控制该第一业务的SR的触发或者发送，其中，在该第一定时器超时前，该终端设备不触发或者不发送该第一业务的SR。
在第一方面的一种可能的实现方式中，对应于该第二业务的SR的第二定时器控制该第二业务的SR的触发或者发送，其中，在该第二定时器超时前，该终端设备不触发或者不发送该第二业务的SR。
在第一方面的一种可能的实现方式中，该方法还包括：在该终端设备获得调度授权前，该终端设备从零开始计算该第一业务的该SR的发送次数，直到累积到最大发送次数。
在第一方面的一种可能的实现方式中，该方法还包括：当该第一业务的SR的上行资源与该第二业务的SR的上行资源相同时，该终端设备只触发或发送该第一业务的SR，不再触发或不发送该第二业务的SR。
在第一方面的一种可能的实现方式中，该方法还包括：该终端设备将与该第一业务的SR相关联的第一定时器的时长值设置为零；或该终端设备不设置与该第一业务的SR相关联的第一定时器。
在第一方面的一种可能的实现方式中，对应于该第一业务的SR的第一定时器控制该第一业务的SR的触发或者发送，对应于该第二业务的SR的第二定时器控制该第二业务的SR的触发或者发送，该第一定时器的时长值小于该第二定时器的时长值。
在第一方面的一种可能的实现方式中，该方法还包括：该终端设备停止该第二定时器；该终端设备将该第二定时器的时长值设置为该第一定时器的时长值，并重启该第二定时器。
在第一方面的一种可能的实现方式中，该方法还包括：该终端设备停止该第二定时器，并将该第二业务的SR的触发或发送与该第一定时器关联。
在第一方面的一种可能的实现方式中，该方法还包括：该终端设备停止与该第二业务的SR相关联的第二定时器，在修改该第二定时器的时长值与该第一业务的SR相关后，重启该第二定时器。
在第一方面的一种可能的实现方式中，其特征在于，与该第一业务的SR相关联的定时器的时长值小于与该第二业务的SR相关的定时器的时长值。
第二方面，提供了一种处理调度请求的方法，该方法包括：终端设备确定触发第一业务调度请求SR的条件满足；该终端设备确定该第一业务的优先级是否高于已触发或已发送调度请求SR的第二业务的优先级；当该终端设备确定该第一业务的优先级低于该第二业务的优先级时，在与该第二业务的SR相关联的定时器超时前，该终端设备不触发和/或不发送该第一业务的SR。
第二方面提供的处理调度请求的方法，终端设备根据业务的优先级情况，当确定当前需要请求上行资源的第一业务的优先级低于已触发和/或已发送调度请求SR的第二业务的优先级时，在与该第二业务的SR相关联的定时器超时前，优先级较低的第一业务不触发和/或者不发送SR，这样，可以根据与该第二业务的SR相关联的定时器来控制该第一业务的SR的触发和/或发送，从而可以增加该第一业务的SR的触发或者发送机会，提高该第一业务触发或者发送的SR的可靠性，提高用户体验。
在第二方面的一种可能的实现方式中，其特征在于，与该第二业务的SR相关联的定时器的时长值小于与该第一业务的SR相关联的定时器的时长值。
第三方面，提供了一种处理调度请求的方法，该方法包括：终端设备确定触发第一业务调度请求SR的条件满足；该终端设备确定该第一业务的调度请求SR的上行资源与已用于触发或发送第二业务的SR的上行资源是否相同；当该终端设备确定该第一业务的SR的上行资源与该第二业务的SR的上行资源不同时，该终端设备相互独立地触发和/或发送该第一业务的SR和该第二业务的SR。
第三方面提供的处理调度请求的方法，在第一业务请求上行资源之前，当存在第二业务也请求上行资源，并且已经触发或者发送了与该第二业务对应的SR，这时，当该终端设备会确定用于发送第一业务的SR的上行资源和用于发送第一业务的SR的上行资源不相同时，第一业务的SR和第二业务的SR的发送和/或触发可以相互独立，即互不干涉。可以提高该第一业务的SR和第二业务的SR的发送或者触发的效率，确保SR的可靠性。
在第三方面的一种可能的实现方式中，对应于该第一业务的SR的第一定时器控制该第一业务的SR的触发或者发送，其中，在该第一定时器超时前，该终端设备不触发或者不发送该第一业务的SR。
在第三方面的一种可能的实现方式中，对应于该第二业务的SR的第二定时器控制该第二业务的SR的触发或者发送，其中，在该第二定时器超时前，该终端设备不触发或者不发送该第二业务的SR。
在第三方面的一种可能的实现方式中，该方法还包括：在该终端设备获得调度授权前，该终端设备从零开始计算该第一业务的该SR的发送次数，直到累积到最大发送次数。
在第三方面的一种可能的实现方式中，该方法还包括：当该终端设备确定该第一业务的SR请求的上行资源与该第二业务的SR请求的上行资源相同，并且该第一业务的优先级低于该第二业务的优先级时，在与该第二业务的SR相关联的定时器超时前，该终端设备不触发和/或不发送该第一业务的SR。
第四方面，提供了一种处理调度请求的方法，该方法包括：终端设备确定需要发送的业务；
当该终端设备通过非调度资源或者竞争资源发送该业务的数据时，该终端设备不取消为该业务挂起的调度请求。
第四方面提供的处理调度请求的方法，终端设备确定需要发送的业务时，还获取了用于发送该第业务的数据的非调度资源，此时，在利用该非调度资源发送该第一业务的数据时，该终端设备并不停止触发和/或发送该第一业务的SR或该第二业务的SR。这样，可以确保该业务的数据可以有效的传输到网络设备，即在利用非调度资源发送业务的数据时，还同时请求专用的调度资源。增加了传输业务数据的可靠性。
在第四方面的一种可能的实现方式中，该方法还包括：该终端设备利用该非调度资源或者竞争资源成功发送该业务的数据后，取消该业务的SR的触发或发送。
在第四方面的一种可能的实现方式中，该方法还包括：当该终端设备获取用于发送比该业务的优先级低的业务的数据的发送资源时，取消触发和/或发送该业务的SR；该终端设备利用比该业务的优先级低的业务的数据的发送资源发送该业务的数据。
在第四方面的一种可能的实现方式中，该方法还包括：利用该非调度资源发送该业务的数据的优先级顺序为：包含该业务的数据量的缓存状态报告BSR>该业务的数据>半静态调度SPS确认>包含比该业务的优先级低的业务的数据量的BSR>比该业务的优先级低的业务的数据。
第五方面，提供了一种处理调度请求的装置，包括处理器和存储器，用于支持该装置执行上述方法中相应的功能。该处理器和该存储器通过通信连接，该存储器存储程序，该处理器用于调用该程序实现上述第一方面及其各种实现方式中的处理调度请求的方法。
第六方面，提供了一种处理调度请求的装置，包括处理模块和存储模块，用于支持装置执行上述第一方面或第一方面的任意可能的实现方式中的功能。功能可以通过硬件实现，也可以通过硬件执行相应的软件实现，硬件或软件包括一个或者多个与上述功能相对应的模块。
第七方面，提供了一种处理调度请求的装置，包括处理器和存储器，用于支持该装置执行上述方法中相应的功能。该处理器和该存储器通过通信连接，该存储器存储程序，该处理器用于调用该程序实现上述第二方面及其各种实现方式中的处理调度请求的方法。
第八方面，提供了一种处理调度请求的装置，包括处理模块和存储模块，用于支持装置执行上述第二方面或第二方面的任意可能的实现方式中的功能。功能可以通过硬件实现，也可以通过硬件执行相应的软件实现，硬件或软件包括一个或者多个与上述功能相对应的模块。
第九方面，提供了一种处理调度请求的装置，包括处理器和存储器，用于支持该装置 执行上述方法中相应的功能。该处理器和该存储器通过通信连接，该存储器存储程序，该处理器用于调用该程序实现上述第三方面及其各种实现方式中的处理调度请求的方法。
第十方面，提供了一种处理调度请求的装置，包括处理模块和存储模块，用于支持装置执行上述第三方面或第三方面的任意可能的实现方式中的功能。功能可以通过硬件实现，也可以通过硬件执行相应的软件实现，硬件或软件包括一个或者多个与上述功能相对应的模块。
第十一方面，提供了一种处理调度请求的装置，包括处理器和存储器，用于支持该装置执行上述方法中相应的功能。该处理器和该存储器通过通信连接，该存储器存储程序，该处理器用于调用该程序实现上述第四方面及其各种实现方式中的处理调度请求的方法。
第十二方面，提供了一种处理调度请求的装置，包括处理模块和存储模块，用于支持装置执行上述第四方面或第四方面的任意可能的实现方式中的装置的功能。功能可以通过硬件实现，也可以通过硬件执行相应的软件实现，硬件或软件包括一个或者多个与上述功能相对应的模块。
第十三方面，提供了一种计算机可读介质，用于存储计算机程序，该计算机程序包括用于执行上述第一方面或第一方面的任一种可能的实现方式的方法的指令。
第十四方面，提供了一种计算机可读介质，用于存储计算机程序，该计算机程序包括用于执行上述第二方面或第二方面的任一种可能的实现方式的方法的指令。
第十五方面，提供了一种计算机可读介质，用于存储计算机程序，该计算机程序包括用于执行上述第三方面或第三方面的任一种可能的实现方式的方法的指令。
第十六方面，提供了一种计算机可读介质，用于存储计算机程序，该计算机程序包括用于执行上述第四方面或第四方面的任一种可能的实现方式的方法的指令。
附图说明
图1是本申请一个实施例的调度请求方法的示意性流程图。
图2是本申请一个实施例的URLLC的SR的可用时频资源和eMBB的SR可用时频资源不相同时两种SR发送的示意性流程图。
图3是本申请一个实施例的URLLC的SR的可用时频资源和eMBB的SR可用时频资源相同时两种SR发送的示意性流程图。
图4是本申请另一个实施例的处理调度请求的方法的示意性流程图。
图5是本申请又一个实施例的处理调度请求的方法的示意性流程图。
图6是本申请又一个实施例的处理调度请求的方法的示意性流程图。
图7是本申请一个实施例的处理调度请求的装置的示意性框图。
图8是本申请另一个实施例的处理调度请求的装置的示意性框图。
图9是本申请一个实施例的处理调度请求的装置的示意性框图。
图10是本申请另一个实施例的处理调度请求的装置的示意性框图。
图11是本申请一个实施例的处理调度请求的装置的示意性框图。
图12是本申请另一个实施例的处理调度请求的装置的示意性框图。
图13是本申请一个实施例的处理调度请求的装置的示意性框图。
图14是本申请另一个实施例的处理调度请求的装置的示意性框图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
应理解，本申请的技术方案可以应用于各种通信系统，例如：LTE系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)系统、通用移动通信系统(universal mobile telecommunication system，UMTS)、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)通信系统、公共陆地移动网络(public land mobile network，PLMN)系统、设备对设备(device to device，D2D)网络系统或者机器对机器(machine to machine，M2M)网络系统以及未来的5G通信系统等。
还应理解，在本申请实施例中，处理调度请求的装置可以是终端设备，终端设备也可称之为用户设备、移动台mobile station，MS)、移动终端(mobile terminal)等，该终端设备可以经无线接入网(radio access network，RAN)与一个或多个核心网设备进行通信，例如，终端设备可以是移动电话(或称为“蜂窝”电话)、具有通信功能的计算机等，例如，终端设备还可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置。
还应理解，网络设备可以是用于与终端设备通信的设备，网络设备可以是LTE系统中的演进型基站(evolutional Node B，eNB或eNodeB)或接入点，或者车载设备、可穿戴设备，未来5G网络中的网络设备或者未来演进的PLMN中的网络设备。本申请实施例在此不作限制。
由于目前SR的发送机制中，只有一个定时器控制所有类型的业务触发的SR的发送，无法满足不同业务请求调度授权的可靠性、时延性需求的差异化需求，例如，对于URLLC业务的上行发送时延需求为0.5ms，而对于eMBB业务的上行发送时延需求为4ms，此时还是利用一个定时器来控制这两种业务触发的SR的发送，会无法满足URLLC业务的上行发送时延要求，导致URLLC业务的数据传输时延增长，用户体验不好。
基于目前的SR发送的机制不能实现不同业务时延的差异化需求的问题，本申请实施例提供了一种处理调度请求的方法，图1示出了根据本申请实施例的调度方法100的示意性流程图，该方法100可以由终端设备来执行，如图1所示，该方法100包括：
S110，终端设备确定触发第一业务调度请求SR的条件满足；
S120，该终端设备确定该第一业务的优先级是否高于已触发或已发送调度请求SR的第二业务的优先级；
S130，当该终端设备确定该第一业务的优先级高于该第二业务的优先级时，触发和/或发送该第一业务的调度请求SR。
本申请实施例提供的处理调度请求的方法，终端设备根据业务的优先级情况，当确定当前需要请求上行资源的第一业务的优先级高于已触发或已发送调度请求SR的第二业务的优先级时，优先级较高的第一业务触发和/或发送的SR不受该优先级较低的第二业务触发或者发送的SR的影响，即按照原有的周期发送，这样，可以增加该第一业务的SR的触发或者发送机会，提高该第一业务触发或者发送的SR的可靠性，减小时延值，提高用户体验。
具体而言，在S110中，当终端设备有第一业务的上行数据要传输时，当该终端设备没有发送该上行数据的上行资源，即确定触发该第一业务调度请求SR的条件满足。该终 端设备会通过SR告诉网络设备自己需要RB资源来传输上行数据，来请求发送该第一业务的数据的上行资源。
在S120中，该终端设备确定该第一业务的优先级是否高于已触发或已发送调度请求SR的第二业务的优先级。即在第一业务请求上行资源之前，当存在第二业务也请求上行资源，并且该终端设备已经触发或者发送了与该第二业务对应的SR，这时，该终端设备会判断该第一业务的优先级与该第二业务的优先级的高低关系，这样可以根据不同业务的优先级来区别对待与不同业务对应的SR，可以满足不同业务的差异化需求。
在S130中，当该终端设备确定该第一业务的优先级高于该第二业务的优先级时，在确定触发该第一业务调度请求SR的条件满足后，会触发和/或发送该第一业务的调度请求SR，即该第一业务的优先级高于该第二业务的优先级时，该第一业务触发和/或发送SR不受该第二业务的触发和/或发送的SR影响。按照原有触发和/或发送SR的周期进行。
应理解，该第一业务的SR的触发和/或发送可以受定时器的控制，该定时器用于限制SR的发送，当该定时器正在运行时，在该定时器超时前，不触发和/或不发送第一业务的SR，在该定时器超时后，才可以触发和/或发送该第一业务的SR。该第一业务的SR的触发和/或发送也可以不受定时器的控制。本申请实施例在此不作限制。
应理解，该第一业务和该第二业务仅仅是为了表示两种不同优先级的业务，而不应对本申请的实施例造成任何限制。
可选的，作为一个实施例，该方法100还可以包括：
当该第一业务的SR的上行资源与该第二业务的SR的上行资源不同时，该终端设备相互独立的地触发和/或发送该第一业务的SR和该第二业务的SR。
具体而言，当用于发送第一业务的SR的上行资源和用于发送第一业务的SR的上行资源不同时，第一业务的SR和第二业务的SR的发送和/或触发可以相互独立，即互不干涉。应理解，在用于发送第一业务的SR的资源和用于发送第一业务的SR资源不同时，该第一业务的SR和第二业务的SR的触发和/或发送周期可以相同，也可以不同，本申请实施例在此不作限制。
以第一业务为URLLC业务，以第二业务为eMBB业务为例进行说明，图2是本申请一个实施例的URLLC的SR的上行资源和eMBB的SR的上行资源不相同时两种SR触发或发送的示意性流程图。图2中每个平行四边形为一个周期点，相邻两个周期点之间的时间间隔为2ms，都为一个可用的时频资源，所有平行四边形组合起来为另一套可用的时频资源。每个小矩形为一个周期点，都为一个可用的时频资源，相邻两个周期点之间的时间间隔为3ms，所有小矩形组合起来为一套可用的时频资源。该eMBB的SR使用矩形这套时频资源来发送。该URLLC触发的SR使用平行四边形这套时频资源来发送。由于两套资源不同，因此，触发或者发送的周期可以相同，也可以不同，应理解，该URLLC触发的SR也可以使用矩形这套时频资源来发送。该eMBB触发的SR使用平行四边形这套时频资源来发送。本申请实施例在此不作限制。
可选的，该第一业务的SR的触发和/或发送可以受第一定时器的控制，该第一定时器与该第一业务的SR对应。例如，该第一定时器用于限制SR的触发或发送，当该第一定时器正在运行时，在该第一定时器超时前，该终端设备不触发或不发送第一业务的SR，在该第一定时器超时后，才可以触发或者发送该第一业务的SR。
可选的，该第二业务的SR的触发和/或发送可以受第二定时器的控制，该第二定时器与该第二业务的SR对应。例如，该第二定时器用于限制SR的触发或发送，当该第二定时器正在运行时，在该第二定时器超时前，该终端设备不触发或不发送第二业务的SR，在该第二定时器超时后，才可以触发或者发送该第二业务的SR。
应理解，该第一业务的SR的触发和/或发送，或者，该第二业务的SR的触发和/或发送，也可以不受对应的定时器的影响。本申请实施例在此不作限制。
可选的，作为一个实施例，该方法100还可以包括：
当该第一业务的SR的上行资源与该第二业务的SR的上行资源相同时，该终端设备只触发和/或发送该第一业务的SR，不再触发和/或不发送该第二业务的SR。
具体而言，当用于发送第一业务的SR的资源和用于发送第一业务的SR资源相同时由于该第一业务的优先级高于该第二业务的优先级，因此，会触发和/或发送该第一业务的SR，并且，不再触发和/或不发送该第二业务的SR。这样，可以节省资源。应理解，在这种情况下，也可以触发和/或发送该第二业务的SR，由于第二业务与第一业务的优先级不同，因此，第二业务的SR的发送时刻与第一业务的SR的发送时刻可以是不同的，即在不同的子帧上发送，对于只存在第一业务的情况，该第一业务的SR发送时刻可以由公式(1)来计算：
Figure PCTCN2018074031-appb-000001
公式(1)中，n f是当前的系统帧号，范围是0～1023。n s是当前的时隙号，范围是0～19，N OFFSET，SR为子帧偏移，SR PERIODICITY为SR的传输周期，通过公式(1)，便可以计算出该第一业务的SR的发送时刻，对于存在两种或者两种以上的业务，可以由SR PERIODICITY×TTI来确定，由于不同种业务的TTI是不一样的，即使发送第一业务的SR的资源和发送第一业务的SR资源相同，第一业务的SR的发送时刻和第二业务的SR的发送时刻也是不同的。
可选的，当该第一业务的SR的上行资源与该第二业务的SR的上行资源相同时，该第一业务的SR还可以包括用于指示该第一业务的指示信息，该第二业务的SR还可以包括用于指示该第二业务的指示信息。
具体而言，由于SR不包括与该业务相关的信息，只是通知网络设备该终端设备有数据需要发送，需要网络设备给分配资源，SR不包括该业务的数据量有多少、该业务的类型或者该业务需要的资源的TTI、CP等信息，因此，当网络设备接收到一个SR后，并不知道SR请求的是那种类型的资源，因此就不知道给该终端设备调度那种类型的资源，对于发送两种业务的SR的情况，当该第一业务的SR的上行资源与该第二业务的SR的上行资源相同时，即网络设备会在同一资源上接收到两个SR，这种情况下，该第一业务的SR还可以包括用于指示该第一业务的指示信息，该第二业务的SR还可以包括用于指示该第二业务的指示信息。用于网络设备识别不同业务对应的SR，从而可以根据业务的不同给不同业务分配不同资源，这样，可以更快的进行业务数据的传输，提高用户体验。
可选的，作为一个实施例，该方法100还可以包括：
该终端设备将与该第一业务的SR相关的第一定时器的时长值设置为零；或
该终端设备不设置与该第一业务的SR相关的第一定时器。
具体而言，由于该第一业务的优先级较高，因此，该第一业务的SR的触发和/或发送 可以不受第一定时器的影响，即可以将与该第一业务的SR相关的第一定时器的时长值设置为零，或者不设置与该第一业务的SR相关的第一定时器。这样，最终该第一业务的SR的触发和/或发送是按照原有的第一业务的SR资源的周期去发送，可以增加高优先级业务触发和/或发送SR的机会，提高高优先级业务的数据发送的可靠性，提高用户体验。
可选的，作为一个实施例，对应于该第一业务的SR的第一定时器控制该第一业务的SR的触发或者发送，对应于该第二业务的SR的第二定时器控制该第二业务的SR的触发或者发送。在该终端设备发送该第一业务的SR后，启动对应于该第一业务的SR的第一定时器。其中该第一定时器的时长值小于与该第二业务的SR相关的第二定时器的时长值。
具体而言，由于第一业务的优先级较高，因此，需要增加该第一业务的SR的触发和/或发送机会，由于系统配置的SR的发送周期较短，因此，为了避免过多的发送SR，可以启动对应于该第一业务的SR的第一定时器，用来控制该第一业务的SR的触发和/或发送，并且，由于该第一业务的优先级高与该第二业务的优先级，因此，该第一业务的SR的触发和/或发送机会应该比该第二业务的SR的触发和/或发送机会多，而第二业务的SR的触发和/或发送受到该第二定时器的控制，因此，该第一定时器的时长值应小于与该第二业务的SR相关的第二定时器的时长值。
可选的，作为一个实施例，该方法100还可以包括：
该终端设备停止该第二定时器；
该终端设备将该第二定时器的时长值设置为该第一定时器的时长值，并重启该第二定时器。
具体而言，由于该第一定时器的时长值小于与该第二定时器的时长值，因此，该终端设备可以将该第二定时器的时长值设置为该第一定时器的时长值。即该第一定时器和该第二定时器都启动，并且两个定时器的时长相同，这样，该第一业务的SR和该第二业务的SR便可以根据该定时器的时长值进行触发和/或发送，从而增加该第一业务的SR和该第二业务的SR触发和/或发送SR的机会，提高这两种业务的数据发送的可靠性。
应理解，该第一业务的SR的触发和/或发送可以根据该第一定时器的时长值来控制，也可以不受该第一定时器的影响，本申请实施在此不作限制。
可选的，该第一业务的SR的触发和/发送可以受与该第一业务相关的该第一定时器的影响，该第二业务的SR触发和/或发送SR可以受与该第二业务相关的该第二定时器的影响，此时，该第一定时的时长值小于该第二定器的时长值，或者，该第一业务的SR的触发和/或发送可以不受第一定时器的影响，该第二业务的SR触发和/或发送SR可以受第二定时器的影响，
以第一业务为URLLC业务，第二业务为eMBB业务为例进行说明，图3是本申请一个实施例的URLLC的SR的可用时频资源和eMBB的SR可用时频资源相同，eMBB的SR的发送受定时器的影响，URLLC的SR的不受定时器影响时两种SR发送的示意流程图。如图3所示，图3中每个小矩形为一个周期点，都为一个可用的时频资源，所有小矩形组合起来为一套可用的上行资源。假设承载该eMBB的SR的资源周期3ms，而该定时器设置的禁止时长值为3个eMBB的SR的资源周期，即3个eMBB的SR的资源周期可以发一次，假设T0时刻为eMBB的SR的资源的第一个周期点，在T0时刻终端设备触发了eMBB的SR，由于该定时器的控制，该eMBB的SR只能在T0+9ms的时刻发送，即 在第四个周期点和第七个周期点发送，而在T0+3ms时刻(第二个周期点)、T0+6ms时刻(第二个周期点)、T0+12ms时刻(第五个周期点)、T0+15ms时刻(第六个周期点)不能发送。假设在T0+1ms时刻终端设备触发了eMBB的SR，由于该定时器的控制，该终端设备只能在T0+10ms时刻后发送该eMBB的SR，即只有当该定时器超时了才可以，但是由于T0+10ms时刻并没有可用于eMBB的SR的时频资源，因此，只能等到T0+12ms(第五个周期点)才可以发送。
当该终端设备触发了URLLC的SR时，假设T0时刻为URLLC的SR的资源的一个周期点，在T0时刻终端设备触发了URLLC的SR，则URLLC的SR可以在每个周期点上发送。从T0时刻算起，例如在9ms的时间内。URLLC的SR可以在T0时刻(第一个周期点)、T0+3ms时刻(第二个周期点)、T0+6ms(第三个周期点)和T0+9ms(第四个周期点)时刻发送，即URLLC的SR可以发送四次，而从T0时刻算起，在9ms的时间内，而eMBB的SR由于受到定时器的限制，只能发送一次。假设在T0+1ms时刻终端设备触发了URLLC的SR，该终端设备可以在T0+3ms(第二个周期点)时刻、T0+6ms(第三个周期点)和T0+9ms(第四个周期点)，从T1时刻算起，在相同的时间内，例如在9ms的时间内，URLLC的SR可以发送三次，而eMBB的SR同样只能发送一次。这样，增加了高优先级的URLLC触发或者发送的SR机会，从而减少了获取发送URLLC业务数据需要的资源的等待时间，确保URLLC业务数据传输的可靠性，提高用户体验。
可选的，作为一个实施例，该方法100还可以包括：
该终端设备停止该第二定时器，并将该第二业务的SR的触发或发送与该第一定时器关联。
具体而言，由于该第一定时器的时长值小于与该第二定时器的时长值，因此，在该终端设备启动该第一定时器后，可以停止该第二定时器，即只有一个时长值较短的第一禁定时来控制这两种业务的SR触发和/或发送。这样，该第一业务的SR和该第二业务的SR便可以根据该第一定时器的时长值进行触发和/或发送，从而增加该第一业务的SR和该第二业务的SR触发或发送SR的机会，提高这两种业务的数据发送的可靠性。
应理解，该第一业务的SR的触发和/或发送可以根据该第一定时器的时长值来控制，也可以不受该第一定时器的影响，本申请实施在此不作限制。
可选的，作为一个实施例，该方法100还可以包括：
该终端设备停止与该第二业务的SR相关的第二定时器，在修改该第二定时器的时长值与所述第一业务的SR相关后，重启该第二定时器。
具体而言，在第二业务的SR根据与该第二业务的SR相关的第二定时器触发和/或发送时，如果有优先级较高的第一业务的SR在触发和/或发送，该终端设备可以停止该第二定时器，并将该第二定时器的时长值设置为与优先级较高的第一业务相关，并重启该第二定时器，即将该第二定时器的时长值设置的更短，这样，该第二业务可以根据该时长值较短的第二定时器时长值来触发和/或发送SR，可以增加该第二业务的SR的触发和/或发送机会，提高第二业务的数据发送的可靠性。
应理解，该第一业务的SR的触发和/或发送可以根据该第二定时器的时长值来控制，也可以不受该第二定时器的影响，本申请实施在此不作限制。
可选的，在该终端设备获得调度授权前，该终端设备从零开始计算该第一业务的SR 的发送次数，直到累积到最大发送次数。
具体而言，在终端设备将该第二业务的SR触发和/或发送后，该终端设备启动了与该第二业务的SR对应的定时器，而在没有获得调度授权前，终端设备触发或者发送了第一业务的SR。或者，在终端设备将该第一业务的SR触发或发送后，该终端设备启动了与该第一业务的SR对应的定时器，而没有获得调度授权前，终端设备触发或者发送了第一业务的SR。此时，该第一业务的SR发送的累积次数的计数方式有两种，一种是终端设备忽略定时器时，从零开始计算该第一业务的SR的发送次数，直到累积到系统规定的最大发送次数，如果此时还没有请求到网络设备给该终端设备调度的资源，该终端设备便释放承载该第一业务的SR的时频资源，通过发起竞争随机接入过程来请求资源。另一种是当该终端设备停止定时器，此时，该第一业务的SR的累积发送次数的计数方法是在该定时器停止前，在该第二业务触发或者发送的SR的次数的基础上，继续累积到系统规定的最大发送次数，如果此时还没有请求到网络设备给该终端设备调度的资源，该终端设备便释放承载该第一业务的SR的资源，通过发起竞争随机接入过程来请求资源。
还应理解，上述的该第一业务和该第二业务仅是为了表明两种业务的优先级不同，而不应对本申请的实施例造成任何限制，例如，该第一业务的优先级也可以高于该第二业务的优先级，也可以有超过两种业务，只要这些业务的时延要求不同，或者可靠性需求不同，都可按利用本申请实施例的技术方案，本申请实施例在此不作限制。
还应理解，除了根据不用业务的优先高低顺序来判断那种或者哪些业务不受该定时器控制外，还可以根据其他顺序，例如，不同业务的时延值、可靠性顺序等，本申请实施在此不作限制。
因此，本申请实施例的调度请求方法，终端设备根据业务的优先级情况，当确定当前需要请求上行资源的第一业务的优先级高于已触发或已发送调度请求SR的第二业务的优先级时，优先级较高的第一业务触发或者发送的SR可以不受与该优先级较低的第二业务对应的定时器的影响，或者可以按照与该第一业务的SR相关的定时的控制来触发和/或发送，并且，该第二业务也可以按照该第一定时器的是时长值去触发和/或发送该第一业务的SR，这样，可以增加该第一业务的SR和该第二业务的SR触发或者发送机会，提高该触发或者发送SR的可靠性，减小时延值，提高用户体验。
本申请实施例还提供了一种处理调度请求的方法200，图4示出了本申请实施例的处理调度请求的方法200示意性流程图，该方法200可以由终端设备执行，该方法200包括：
S210，终端设备确定触发第一业务调度请求SR的条件满足；
S220，该终端设备确定该第一业务的优先级是否高于已触发或已发送调度请求SR的第二业务的优先级；
S230，当该终端设备确定该第一业务的优先级低于该第二业务的优先级时，在与该第二业务的SR相关联的定时器超时前，该终端设备不触发和/或不发送该第一业务的SR。
本申请实施例提供的处理调度请求的方法，终端设备根据业务的优先级情况，当确定当前需要请求上行资源的第一业务的优先级低于已触发和/或已发送调度请求SR的第二业务的优先级时，在与该第二业务的SR相关联的定时器超时前，优先级较低的第一业务不触发和/或不发送的SR，这样，可以根据与该第二业务的SR相关联的定时器来控制该第一业务的SR的触发和/或发送，从而可以增加该第一业务的SR的触发或者发送机会， 提高该第一业务触发或者发送的SR的可靠性，提高用户体验。
具体而言，在S210中，当终端设备有第一业务的上行数据要传输时，当该终端设备没有发送该上行数据的上行资源，即确定触发第一业务调度请求SR的条件满足。该终端设备会通过SR告诉网络设备自己需要RB资源来传输上行数据，来请求发送该第一业务的数据的上行资源。
在S220中，该终端设备确定该第一业务的优先级是否高于已触发和/或已发送调度请求SR的第二业务的优先级。即在第一业务请求上行资源之前，如果存在第二业务也请求上行资源，并且已经触发或者发送了与该第二业务对应的SR，这时，该终端设备会判断该第一业务的优先级与该第二业务的优先级的高低关系，这样可以根据不同业务的优先级来区别对待与不同业务对应的SR，可以满足不同业务的差异化需求。
在S230中，当该终端设备确定该第一业务的优先级低于该第二业务的优先级时，在与该第二业务的SR相关联的定时器超时前，优先级较低的第一业务不触发和/或不发送的SR，这样，可以根据与该第二业务的SR相关联的定时器来控制该第一业务的SR的触发或者发送。
应理解，该第二业务的SR的触发和/或发送可以受该定时器的控制，该定时器用于限制SR的发送，当该定时器正在运行时，在该定时器超时前，不触发和/或发送第二业务的SR，在该定时器超时后，才可以触发和/或发送该第二业务的SR。该第二业务的SR的触发和/或发送也可以不受定时器的控制。本申请实施例在此不作限制。
应理解，该第一业务和该第二业务仅仅是为了表示两种不同优先级的业务，而不应对本申请的实施例造成任何限制。
可选的，与该第二业务的SR相关联的定时器的时长值小于与该第一业务的SR相关联的定时器的时长值。
具体而言，由于该第二业务的优先级高于该第一业务的优先级，因此，为了增加该第一业务触发或者发送该第一业务的SR的机会，在该第一业务的SR和该第二业务的SR均受定时器影响的时候，与该第二业务的SR相关联的定时器的时长值小于与该第一业务的SR相关联的定时器的时长值，这样，在相同的时间内，该第二业务的SR的触发和/或发送的机会比第一业务的SR触发和/或发送的机会多，可以增加该第二业务的SR触发或者发送机会，提高该触发和/或发送第二业务的SR的可靠性，提高用户体验。
本申请实施例还提供了一种处理调度请求的方法300，图5示出了本申请实施例的处理调度请求的方法300示意性流程图，该方法300可以由终端设备执行，该方法300包括：
S310，终端设备确定触发第一业务调度请求SR的条件满足；
S320，该终端设备确定该第一业务的调度请求SR的上行资源与已用于触发或发送第二业务的SR的上行资源是否相同；
S330，当该终端设备确定该第一业务的SR的上行资源与该第二业务的SR的上行资源不同时，该终端设备相互独立地触发或发送该第一业务的SR和该第二业务的SR。
本申请实施例提供的处理调度请求的方法，在第一业务请求上行资源之前，如果存在第二业务也请求上行资源，并且已经触发或者发送了与该第二业务对应的SR，这时，当该终端设备会确定用于发送第一业务的SR的上行资源和用于发送第一业务的SR的上行资源不相同时，第一业务的SR和第二业务的SR的发送和/或触发可以相互独立，即互不 干涉。可以提高该第一业务的SR和第二业务的SR的发送或者触发的效率，确保SR的可靠性。
可选的，该第一业务的SR的触发和/或发送可以受第一定时器的控制，该第一定时器与该第一业务的SR对应。例如，该第一定时器用于限制SR的触发或发送，当该第一定时器正在运行时，在该第一定时器超时前，该终端设备不触发或不发送第一业务的SR，在该第一定时器超时后，才可以触发或发送该第一业务的SR。
可选的，该第二业务的SR的触发和/或发送可以受第二定时器的控制，该第二定时器与该第二业务的SR对应。例如，该第二定时器用于限制SR的触发或发送，当该第二定时器正在运行时，在该第二定时器超时前，该终端设备不触发或不发送第二业务的SR，在该第二定时器超时后，才可以触发或发送该第二业务的SR。
应理解，该第一业务的SR的触发和/或发送，或者，该第二业务的SR的触发和/或发送，也可以不受对应的定时器的影响。本申请实施例在此不作限制。
可选的，作为一个实施例，该方法300还可以包括：
当该终端设备确定该第一业务的SR请求的上行资源与该第二业务的SR请求的上行资源相同，并且该第一业务的优先级低于该第二业务的优先级时，在与该第二业务的SR相关联的定时器超时前，该终端设备不触发和/或不发送该第一业务的SR。
具体而言，当该终端设备确定该第一业务的SR请求的上行资源与该第二业务的SR请求的上行资源相同，并且该第一业务的优先级低于该第二业务的优先级时，在与该第二业务的SR相关联的定时器超时前，优先级较低的第一业务不触发和/或不发送SR，可以根据与该第二业务的SR相关联的定时器来控制该第一业务的SR的触发和/或发送，从而可以增加该第一业务的SR的触发和/或发送机会，提高该第一业务触发和/或发送的SR的可靠性，提高用户体验。
应理解，该第二业务的SR的触发和/或不发送可以受与该第二业务的SR相关联的定时器的控制，该定时器用于限制SR的发送，当该定时器正在运行时，在该定时器超时前，不触发和/或发送第二业务的SR，在该定时器超时后，才可以触发和/或发送该第二业务的SR。该第二业务的SR的触发和/或发送也可以不受定时器的控制。本申请实施例在此不作限制。
还应理解，在用于发送第一业务的SR的上行资源和用于发送第一业务的SR的上行资源不同时，该第一业务的SR和第二业务的SR的发送周期可以相同，也可以不同，本申请实施例在此不作限制。
本申请实施例还提供了一种处理调度请求的方法400，图6示出了本申请实施例的处理调度请求的方法400示意性流程图，该方法400可以由终端设备执行，该方法400包括：
S410，终端设备确定触发第一业务调度请求SR的条件满足；
S420，当该终端设备通过非调度资源或者竞争资源发送该第一业务的数据时，该终端设备不取消该第一业务的调度请求SR的触发和/或发送。
具体而言，终端设备确定需要发送的业务时，即确定触发第一业务调度请求SR的条件满足时，还获取了用于发送该第业务的数据的非调度资源，此时，在利用该非调度资源发送该第一业务的数据时，该终端设备并不停止触发和/或发送该第一业务的SR或该第二业务的SR。这样，可以确保该业务的数据可以有效的传输到网络设备，即在利用非调度 资源发送业务的数据时，还同时请求专用的调度资源。增加了传输业务数据的可靠性。
可选的，作为一个实施例，该方法400还可以包括：
当该终端设备利用该非调度资源或者竞争资源成功发送该业务的数据后，取消该业务的SR的触发和/或发送。
具体而言，由于在利用该非调度资源发送该业务的数据时，为了确保数据可以成功发送，该终端设备并不停止触发和/或发送该业务的SR触发或者发送，而是当确定利用该非调度资源成功发送该业务的数据时，才取消该业务的SR的触发和/或发送。例如，可以是接收到该网络设备发送第一指示信息，例如，该第一指示信息可以是该网络设备确定利用该非调度资源成功发送第一业务的数据或该第二业务的数据，向该终端设备发送一个确认信息，例如，可以是ACK(Acknowledgement)，此时，该终端设备会相应的停止该业务的SR的触发或发送。这样，既可以确保数据发送的准确性，又可以避免多余的SR的触发或发送，避免了资源的浪费和交互信令的增加，用户体验更好。
应理解，该网络设备还可以通过静态或者动态指示告知该终端设备在利用非调度资源在发送业务的数据或者BSR后是否允许发送SR，本申请实施例在此不作限制。
还应理解，当该SR已经发送到最限制次数，或者该网络设备已经根据该SR给该终端设备调度了资源时，该终端设备也会取消触发和/或发送该SR。本申请实施例在此不作限制。
可选的，作为一个实施例，该方法400还包括：
当该终端设备获取用于发送比该业务的优先级低的业务的数据的发送资源时，取消触发和/或发送该业务的SR；
该终端设备利用比该业务的优先级低的业务的数据的发送资源发送该业务的数据。
具体而言，当该终端设备获取了用于发送该业务的或者比该业务的优先级低的业务数据的资源后，可以按照不同业务的优先级顺序来发送不同业务的数据，即先发送该业务的数据，由于该业务的数据已经具有发送的资源了，此时，该终端设备确定取消触发和/或发送该业务的SR，这样，可以减少不必要的SR的触发或发送，减少信令交互，节约资源，提高用户体验。
可选的，作为一个实施例，在该终端设备利用非调度资源发送该业务的数据的优先级顺序为：包含该业务的数据量的缓存状态报告BSR>该业务的数据>半静态调度SPS确认>包含比该业务的优先级低的业务的数据量的BSR>比该业务的优先级低的业务的数据。
具体而言，在利用非调度资源发送业务的数据时，可以按照业务的优先级的顺序来发发送，即高优先级的业务的数据先发送。在按照业务的优先级顺序来发送不同业务的数据时，可以优先发送高优先级业务的BSR，BSR可以携带比SR更多的信息，网络设备接收到终端设备发送的SR后，只知道该终端设备有数据传输，并不知道具体有多少数据需要传输，因此，一般情况下，网络设备会先给该终端设备分配少量的上行链路授权，用于该终端设备发送该BSR，因此，在终端设备获取发送业务的资源后，如果该资源放不下需要传输的数据时，会先将该数据的数据量放入BSR中，优先发送包含该业务数据量的BSR，再发送该业务数据。因此，对于只存在该一种业务的情况，会按照包含该业务数据量的BSR→该第业务的数据→半静态调度(semi-persistent scheduling，SPS)确认的顺序发送，半静态调度是网络设备在初始的调度过程中，通过物理下行链路控制信道(physical  downlink control channel，PDCCH)指示终端设备当前的调度信息，终端设备识别是SPS后，保存当前的调度信息，每隔固定的周期在相同的时频资源上进行该业务的数据的发送或者接收，使用SPS传输可以充分利用数据包周期性到达的特点，一次授权，周期使用，可以有效地节省LTE系统用于调度指示的PDCCH资源。对于存在多种不用优先级的业务，可以按照包含该第一业务的数据量的缓存状态报告BSR→该第一业务的数据→SPS确认→包含比该第一业务的优先级低的业务数据量的BSR→比该第一业务的优先级低的业务数据的顺序发送。例如，以第一业务为URLLC业务为例，以第二业务为eMBB业务为例，URLLC业务的优先级顺序高于eMBB业务的优先级，会按照包含URLLC业务数据量的BSR→URLLC业务的数据→SPS确认→包含eMBB业务数据量的BSR→eMBB业务的数这样的顺序发送。
应理解，对于利用调度资源发送业务的数据时，也可以按照上述的发送顺序来进行发送，本申请实施例在此不作限制。
还应理解，无论对于利用调度资源发送业务数据或者利用非调度资源发送业务数据，如果新的数据包到达无线链路控制层radio link control，RLC)/分组数据汇聚协议(packet data convergence protocol)，只要新到达的数据造成的缓冲寄存器(buffer)的数据量大于一定门限值，终端设备就需要触发BSR，即需要发送BSR。
还应理解，对于多种业务，也可以按照优先级的顺序，按照上述顺序进行多种业务数据的发送，本申请实施在此不作限制。
还应理解，除了根据不用业务的优先级顺序发送不同业务的数据之外，还可以根据其他顺序，例如，不同业务的时延值、可靠性顺序等，本申请实施在此不作限制。
还应理解，在本申请的实施例中，上述各过程和各步骤序号的大小并不意味着执行顺序的先后，各过程的执行顺序应该以其功能和内在的逻辑而定，而不应对本申请的实施例的实施过程造成任何限制。
因此，本申请实施例提供的处理调度请求的方法，在利用非调度资源发送业务的数据时，该终端设备并不停止触发或发送该第业务的SR，而是当确定该业务的数据传输成功后，才停止触发或发送该第业务的SR，并且只要获取到资源，会按照业务的优先级顺序，优先发送高优先级的业务的相关数据，减少了高优先级业务的数据的发送时延，提高用户体验。
下面将对本申请实施例的处理调度请求的装置进行详细描述。
图7示出了根据本申请一个实施例的处理调度请求的装置500的示意性框图，该处理调度请求的装置500包括处理器510和存储用于该处理器510执行的程序的存储器520：
该处理器510，用于确定触发第一业务的调度请求的条件满足；
该处理器510还用于确定该第一业务的优先级是否高于已触发或已发送调度请求SR的第二业务的优先级；
如果该处理器510确定该第一业务的优先级高于该第二业务的优先级时，触发和/或发送该第一业务的调度请求SR。
本申请实施例提供的处理调度请求的装置，能够根据业务的优先级情况，当确定当前需要请求上行资源的第一业务的优先级高于已触发或已发送调度请求SR的第二业务的优先级时，优先级较高的第一业务触发和/或发送的SR不受该优先级较低的第二业务触发和 /或发送的SR的影响，即按照原有的周期发送，这样，可以增加该第一业务的SR的触发和/或发送机会，提高该第一业务触发或者发送的SR的可靠性，减小时延值，提高用户体验。
处理调度请求的装置500中的各个组件通过通信连接，即处理器510和存储器520之间通过内部连接通路互相通信，传递控制和/或数据信号。应注意，本申请上述方法实施例可以应用于处理器中，或者由处理器实现。处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可选的，作为一个实施例，该处理器510还用于：当该第一业务的SR的上行资源与该第二业务的SR的上行资源不同时，该处理器510还用于：相互独立的地触发或发送该第一业务的SR和该第二业务的SR。
可选的，作为一个实施例，对应于该第一业务的SR的第一定时器控制该第一业务的SR的触发或者发送，其中，在该第一定时器超时前，该处理器510还用于：不触发或不发送该第一业务的SR。
可选的，作为一个实施例，对应于该第二业务的SR的第二定时器控制该第二业务的SR的触发或者发送，其中，在该第二定时器超时前，该处理器510还用于：不触发或不发送该第二业务的SR。
可选的，作为一个实施例，该处理器510还用于：在该处理调度请求的装置获得调度授权前，该处理调度请求的装置从零开始计算该第一业务的该SR的发送次数，直到累积到最大发送次数。
可选的，作为一个实施例，该处理器510还用于：当该第一业务的SR的上行资源与该第二业务的SR的上行资源相同时，只触发或发送该第一业务的SR，不再触发或不发送该第二业务的SR。
可选的，作为一个实施例，该处理器510还用于：将与该第一业务的SR相关联的第一定时器的时长值设置为零；或不设置与该第一业务的SR相关联的第一定时器。
可选的，作为一个实施例，该处理器510还用于：对应于该第一业务的SR的第一定时器控制该第一业务的SR的触发或者发送，对应于该第二业务的SR的第二定时器控制该第二业务的SR的触发或者发送，该第一定时器的时长值小于与该第二业务的SR相关联的第二定时器的时长值。
可选的，作为一个实施例，该处理器510还用于：停止该第二定时器；将该第二定时 器的时长值设置为该第一定时器的时长值，并重启该第二定时器。
可选的，作为一个实施例，该处理器510还用于：停止该第二定时器，并将该第二业务的SR的触发或发送与该第一定时器关联。
可选的，作为一个实施例，该处理器510还用于：停止与该第二业务的SR相关联的第二定时器，在修改该第二定时器的时长值与该第一业务的SR相关后，重启该第二定时器。
可选的，作为一个实施例，与该第一业务的SR相关联的定时器的时长值小于与该第二业务的SR相关的定时器的时长值。
应注意，本申请实施例中，处理器510可以处理模块由实现，存储器520可以由存储模块实现。如图8所示，处理调度请求的装置600可以包括处理模块610和存储模块620。
图7所示的处理调度请求的装置500或图8所示的处理调度请求的装置600能够实现前述图1至图3的实施例中以及方法100中各个实施例所实现的各个过程，为避免重复，这里不再赘述。
图9示出了本申请一个实施例的处理调度请求的装置700的示意性框图。如图9所示，处理调度请求的装置700包括处理器710和存储用于该处理器710执行的程序的存储器720：
处理器710，用于确定触发第一业务的调度请求的条件满足；
该处理器710还用于确定该第一业务的优先级是否高于已触发和/或已发送调度请求SR的第二业务的优先级；
该处理器710还用于当确定该第一业务的优先级低于该第二业务的优先级时，在与该第二业务的SR相关联的定时器超时前，不触发和/或不发送该第一业务的SR。
本申请实施例提供的处理调度请求的装置，能够根据业务的优先级情况，当确定当前需要请求上行资源的第一业务的优先级低于已触发和/或已发送调度请求SR的第二业务的优先级时，在与该第二业务的SR相关联的定时器超时前，优先级较低的第一业务不触发和/或不发送的SR，这样，可以根据与该第二业务的SR相关联的定时器来控制该第一业务的SR的触发或者发送，从而可以增加该第一业务的SR的触发和/或发送机会，提高该第一业务触发或者发送的SR的可靠性，提高用户体验。
处理调度请求的装置700中的各个组件通过通信连接，即处理器710和存储器720之间通过内部连接通路互相通信，传递控制和/或数据信号。应注意，本申请上述方法实施例可以应用于处理器中，或者由处理器实现。处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本 领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可选的，作为一个实施例，其特征在于，与该第二业务的SR相关联的定时器的时长值小于与该第一业务的SR相关联的定时器的时长值。
应注意，本申请实施例中，处理器710可以处理模块由实现，存储器720可以由存储模块实现。如图10所示，处理调度请求的装置800可以包括处理模块810和存储模块820。
图9所示的处理调度请求的装置700或图10所示的处理调度请求的装置800能够实现前述图2至图4的实施例中以及方法200中各个实施例所实现的各个过程，为避免重复，这里不再赘述。
图11示出了本申请一个实施例的处理调度请求的装置900的示意性框图。如图11所示，处理调度请求的装置900包括处理器910和存储用于该处理器910执行的程序的存储器920：
该处理器910，用于确定触发第一业务的调度请求的条件满足；
该处理器910还用于确定该第一业务的调度请求SR的上行资源与已用于触发和/或发送第二业务的SR的上行资源是否相同；
该处理器910还用于当确定该第一业务的SR的上行资源与该第二业务的SR的上行资源不同时，相互独立的地触发和/或发送该第一业务的SR和该第二业务的SR。
本申请实施例提供的处理调度请求的装置，在第一业务请求上行资源之前，当存在第二业务也请求上行资源，并且已经触发和/或发送了与该第二业务对应的SR，这时，当该处理调度请求的装置会确定用于发送第一业务的SR的上行资源和用于发送第一业务的SR的上行资源不相同时，第一业务的SR和第二业务的SR的发送和/或触发可以相互独立，即互不干涉。可以提高该第一业务的SR和第二业务的SR的发送和/或触发的效率，确保SR的可靠性。
处理调度请求的装置900中的各个组件通过通信连接，即处理器910和存储器920之间通过内部连接通路互相通信，传递控制和/或数据信号。应注意，本申请上述方法实施例可以应用于处理器中，或者由处理器实现。处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可选的，作为一个实施例，对应于该第一业务的SR的第一定时器控制该第一业务的SR的触发或者发送，其中，在该第一定时器超时前，该处理器710还用于：不触发和/或 不发送该第一业务的SR。
可选的，作为一个实施例，对应于该第二业务的SR的第二定时器控制该第二业务的SR的触发或者发送，其中，在该第二定时器超时前，该处理器710还用于：不触发或不发送该第二业务的SR。
可选的，作为一个实施例，该处理器710还用于：在该处理调度请求的装置获得调度授权前，该处理调度请求的装置从零开始计算该第一业务的该SR的发送次数，直到累积到最大发送次数。
可选的，作为一个实施例，与该第二业务的SR相关联的定时器的时长值小于与该第一业务的SR相关联的定时器的时长值。
应注意，本申请实施例中，处理器910可以处理模块由实现，存储器920可以由存储模块实现。如图12所示，终端设1100可以包括处理模块1110和存储模块1120。
图11所示的处理调度请求的装置900或图12所示的处理调度请求的装置1100能够实现前述图2至图5的实施例中以及方法300中各个实施例所实现的各个过程，为避免重复，这里不再赘述。
图13示出了本申请一个实施例的处理调度请求的装置1200的示意性框图。如图13所示，处理调度请求的装置1200包括处理器1210和存储用于该处理器1210执行的程序的存储器1220：
该处理器1210，用于确定触发第一业务调度请求SR的条件满足；
该处理器1210还用于当通过非调度资源或者竞争资源发送所述第一业务的数据时，不取消为所述第一业务挂起的调度请求SR的触发和/或发送。
本申请实施例提供的处理调度请求的装置，在利用非调度资源发送业务的数据时，并不停止触发和/或发送该第业务的SR，而是当确定该业务的数据传输成功后，才取消为所述业务挂起的调度请求SR，确保了该业务数据发送的可靠性，提高用户体验。
处理调度请求的装置1200中的各个组件通过通信连接，即处理器1210和存储器1220之间通过内部连接通路互相通信，传递控制和/或数据信号。应注意，本申请上述方法实施例可以应用于处理器中，或者由处理器实现。处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可选的，作为一个实施例，该处理器1210还用于：当利用所述非调度资源或者竞争资源成功发送所述业务的数据后，取消为所述业务挂起的调度请求SR。
可选的，作为一个实施例，该处理器1210还用于：当获取用于发送比所述业务的优先级低的业务的数据的发送资源时，取消为所述业务挂起的调度请求SR。利用比所述业务的优先级低的业务的数据的发送资源发送所述业务的数据。
可选的，作为一个实施例，该处理器1210还用于：利用所述非调度资源发送所述业务的数据的优先级顺序为：包含所述业务的数据量的缓存状态报告BSR>所述业务的数据>半静态调度SPS确认>包含比所述业务的优先级低的业务的数据量的BSR>比所述业务的优先级低的业务的数据。
应注意，本申请实施例中，处理器1210可以处理模块由实现，存储器1220可以由存储模块实现。如图14所示，终端设1300可以包括处理模块1310和存储模块1320。
图13所示的终端设备1200或图14所示的终端设备1300能够实现前述图6所示的实施例中以及方法400中各个实施例所实现的各个过程，为避免重复，这里不再赘述。
本申请实施例还提供了一种计算机可读介质，用于存储计算机程序代码，该计算机程序包括用于执行上述的本申请各个实施例的处理调度请求的方法的指令。该可读介质可以是只读存储器(read-only memory，ROM)或随机存取存储器(random access memory，RAM)，本申请实施例对此不做限制。
应理解，本文中术语“和/或”以及“A或B中的至少一种”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现 有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (17)

  1. 一种处理调度请求的方法，其特征在于，包括：
    终端设备确定触发第一业务调度请求SR的条件满足；
    所述终端设备确定所述第一业务的优先级是否高于已触发或已发送SR的第二业务的优先级；
    当所述终端设备确定所述第一业务的优先级高于所述第二业务的优先级时，触发和/或发送所述第一业务的SR。
  2. 根据权利要求1所述的方法，其特征在于，当所述第一业务的SR的上行资源与所述第二业务的SR的上行资源不同时，所述方法还包括：
    所述终端设备相互独立地触发或发送所述第一业务的SR和所述第二业务的SR。
  3. 根据权利要求1或2所述的方法，其特征在于，对应于所述第一业务的SR的第一定时器控制所述第一业务的SR的触发或者发送，其中，在所述第一定时器超时前，所述终端设备不触发或者不发送所述第一业务的SR。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，对应于所述第二业务的SR的第二定时器控制所述第二业务的SR的触发或者发送，其中，在所述第二定时器超时前，所述终端设备不触发或者不发送所述第二业务的SR。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，所述方法还包括：
    在所述终端设备获得调度授权前，所述终端设备从零开始计算所述第一业务的所述SR的发送次数，直到累积到最大发送次数。
  6. 根据权利要求1所述的方法，其特征在于，当所述第一业务的SR的上行资源与所述第二业务的SR的上行资源相同时，所述方法还包括：
    所述终端设备只触发或发送所述第一业务的SR，不触发和/或不发送所述第二业务的SR。
  7. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述终端设备将与所述第一业务的SR相关联的第一定时器的时长值设置为零；或
    所述终端设备不设置与所述第一业务的SR相关联的第一定时器。
  8. 根据权利要求1至5中任一项所述的方法，其特征在于：对应于所述第一业务的SR的第一定时器控制所述第一业务的SR的触发或者发送，对应于所述第二业务的SR的第二定时器控制所述第二业务的SR的触发或者发送，所述第一定时器的时长值小于所述第二定时器的时长值。
  9. 根据权利要求8所述的方法，其特征在于，所述方法还包括：
    所述终端设备停止所述第二定时器；
    所述终端设备将所述第二定时器的时长值设置为所述第一定时器的时长值，并重启所述第二定时器。
  10. 根据权利要求8所述的方法，其特征在于，所述方法还包括：
    所述终端设备停止所述第二定时器，并将所述第二业务的SR的触发和/或发送与所述第一定时器关联。
  11. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述终端设备停止与所述第二业务的SR相关联的第二定时器，在修改所述第二定时器的时长值与所述第一业务的SR相关后，重启所述第二定时器。
  12. 一种处理调度请求的方法，其特征在于，包括：
    终端设备确定触发第一业务调度请求SR的条件满足；
    所述终端设备在所述第一业务的SR的上行资源与已用于触发和/或发送第二业务的SR的上行资源不同时，相互独立地触发和/或发送所述第一业务的SR和所述第二业务的SR。
  13. 根据权利要求12所述的方法，其特征在于，对应于所述第一业务的SR的第一定时器控制所述第一业务的SR的触发或者发送，其中，在所述第一定时器超时前，所述终端设备不触发或者不发送所述第一业务的SR。
  14. 根据权利要求12或13所述的方法，其特征在于，对应于所述第二业务的SR的第二定时器控制所述第二业务的SR的触发或者发送，其中，在所述第二定时器超时前，所述终端设备不触发或者不发送所述第二业务的SR。
  15. 根据权利要求12至14中任一项所述的方法，其特征在于，所述方法还包括：
    在所述终端设备获得调度授权前，所述终端设备从零开始计算所述第一业务的所述SR的发送次数，直到累积到最大发送次数。
  16. 一种处理调度请求的装置，其特征在于，包括处理器和存储用于所述处理器执行的程序的存储器，所述处理器用于执行权利要求1至15中任一项所述的方法。
  17. 一种计算机可读存储介质，用于存储计算机程序，其特征在于，所述计算机程序用于执行根据权利要求1至15中任一项所述的方法的指令。
PCT/CN2018/074031 2017-01-26 2018-01-24 处理调度请求的方法和装置 WO2018137665A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP18744458.3A EP3565357B1 (en) 2017-01-26 2018-01-24 Method and device for processing scheduling request
US16/522,335 US11134507B2 (en) 2017-01-26 2019-07-25 Method and apparatus for processing scheduling request

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710057477.7 2017-01-26
CN201710057477.7A CN108366430B (zh) 2017-01-26 2017-01-26 调度请求的方法和终端设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/522,335 Continuation US11134507B2 (en) 2017-01-26 2019-07-25 Method and apparatus for processing scheduling request

Publications (1)

Publication Number Publication Date
WO2018137665A1 true WO2018137665A1 (zh) 2018-08-02

Family

ID=62979089

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/074031 WO2018137665A1 (zh) 2017-01-26 2018-01-24 处理调度请求的方法和装置

Country Status (4)

Country Link
US (1) US11134507B2 (zh)
EP (1) EP3565357B1 (zh)
CN (1) CN108366430B (zh)
WO (1) WO2018137665A1 (zh)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020087509A1 (zh) * 2018-11-02 2020-05-07 Oppo广东移动通信有限公司 无线通信方法、终端设备和网络设备
CN111181693B (zh) * 2018-11-09 2021-08-31 华为技术有限公司 发送数据的方法、发送数据的装置、以及终端设备
US20220095334A1 (en) * 2019-01-21 2022-03-24 Ntt Docomo, Inc. User terminal and radio communication method
CN111865508B (zh) * 2019-04-30 2021-08-20 华为技术有限公司 一种通信方法及通信装置
CN113498040B (zh) * 2020-04-08 2023-12-05 大唐移动通信设备有限公司 一种停止发送调度请求的方法及装置
CN115623603B (zh) * 2020-11-26 2024-02-23 紫光展锐(重庆)科技有限公司 数据传输方法及系统、终端及存储介质
CN117675124A (zh) * 2022-08-09 2024-03-08 华为技术有限公司 一种通信方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101980575A (zh) * 2010-10-14 2011-02-23 华为技术有限公司 随机接入的处理方法和终端
CN104170491A (zh) * 2012-03-19 2014-11-26 阿尔卡特朗讯 用于配置多个调度请求触发的方法和装置
US20150223235A1 (en) * 2012-09-28 2015-08-06 Lg Electronics Inc. Uplink transmission method and uplink transmission device
WO2016165387A1 (zh) * 2015-09-18 2016-10-20 中兴通讯股份有限公司 调度控制方法、通信节点和计算机存储介质

Family Cites Families (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE3340052A1 (de) * 1983-11-05 1985-05-15 Simprop electronic Walter Claas GmbH & Co, 4834 Harsewinkel Verfahren und schaltung zur erzeugung und uebertragung einer vielzahl von ausgangssignalen
EP0671860A1 (en) * 1994-03-04 1995-09-13 ALCATEL BELL Naamloze Vennootschap FIFO buffer arrangement with delayed push-out
RU2417524C2 (ru) * 2006-06-22 2011-04-27 Самсунг Электроникс Ко., Лтд. Способ передачи запроса диспетчеризации в системе мобильной связи и терминальное устройство для этого
CN101330313A (zh) * 2007-06-19 2008-12-24 中兴通讯股份有限公司 一种lte系统中上行调度请求的方法
US20090046641A1 (en) * 2007-08-13 2009-02-19 Interdigital Patent Holdings, Inc. Long term evolution medium access control procedures
CN101686551B (zh) * 2008-09-22 2011-09-28 电信科学技术研究院 基于优先级管理的通信控制方法及装置
CN101938403B (zh) * 2009-06-30 2012-02-22 中国电信股份有限公司 多用户多业务的服务质量的保证方法和业务接入控制点
EP2462776B1 (en) * 2009-08-07 2018-10-31 HMD global Oy Operation in case of radio link failure
CN102111892B (zh) * 2009-12-24 2014-02-12 普天信息技术研究院有限公司 一种用户设备上报调度请求信息的方法
US20120289183A1 (en) * 2011-05-13 2012-11-15 Kundan Tiwari Methods for requesting emergency bearer services for low priority devices, and apparatuses using the same
GB2493239B (en) * 2011-07-29 2015-11-25 Sca Ipla Holdings Inc Communications terminal and method
EP2739099B1 (en) * 2011-07-29 2019-09-25 NEC Corporation Wireless station, wireless terminal, and time alignment timer control method in wireless communication system
EP2608567A1 (en) * 2011-12-13 2013-06-26 Panasonic Corporation Device triggering and congestion control
WO2013129861A1 (ko) * 2012-02-28 2013-09-06 엘지전자 주식회사 무선 통신 시스템에서의 서비스 기간 설정 방법 및 이를 위한 장치
WO2013134952A1 (zh) * 2012-03-16 2013-09-19 华为技术有限公司 调度请求资源配置方法、设备及系统
WO2013139299A1 (en) * 2012-03-23 2013-09-26 Mediatek Inc. Methods and apparatus of allocating scheduling request resources in mobile communication networks
CN103024001B (zh) * 2012-11-30 2018-07-31 中兴通讯股份有限公司 一种业务调度方法与装置及融合设备
CA2905351A1 (en) * 2013-03-11 2014-10-09 Micro Macro Assets Llc System and method for providing sales and marketing acceleration and effectiveness
MX355829B (es) * 2013-03-29 2018-05-02 Huawei Tech Co Ltd Método para controlar la solicitud de recursos de otorgamiento de enlace ascendente, equipo de usuario, y estación base.
GB2513312B (en) * 2013-04-22 2020-01-29 Sony Corp Communications system for transmitting and receiving data
CN104378830B (zh) * 2013-08-15 2018-07-20 普天信息技术有限公司 调度请求资源的分配方法和系统
US9949271B2 (en) * 2014-03-06 2018-04-17 Mediatek Inc. Smart congestion control for RRC idle mode in LTE systems
JP6422992B2 (ja) * 2014-03-19 2018-11-14 エルジー エレクトロニクス インコーポレイティド 無線通信システムにおけるバッファ状態報告の優先順位を決める方法及び装置
CN105992373B (zh) * 2015-01-30 2020-09-15 中兴通讯股份有限公司 数据传输方法、装置、基站及用户设备
US10582522B2 (en) * 2015-09-04 2020-03-03 Lg Electronics Inc. Data transmission and reception method and device of terminal in wireless communication system
US10524294B2 (en) * 2017-05-04 2019-12-31 Ofinno, Llc Scheduling request transmission

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101980575A (zh) * 2010-10-14 2011-02-23 华为技术有限公司 随机接入的处理方法和终端
CN104170491A (zh) * 2012-03-19 2014-11-26 阿尔卡特朗讯 用于配置多个调度请求触发的方法和装置
US20150223235A1 (en) * 2012-09-28 2015-08-06 Lg Electronics Inc. Uplink transmission method and uplink transmission device
WO2016165387A1 (zh) * 2015-09-18 2016-10-20 中兴通讯股份有限公司 调度控制方法、通信节点和计算机存储介质

Also Published As

Publication number Publication date
EP3565357A4 (en) 2020-01-01
CN108366430B (zh) 2023-10-03
US20190349961A1 (en) 2019-11-14
CN108366430A (zh) 2018-08-03
EP3565357A1 (en) 2019-11-06
US11134507B2 (en) 2021-09-28
EP3565357B1 (en) 2021-11-03

Similar Documents

Publication Publication Date Title
WO2018137665A1 (zh) 处理调度请求的方法和装置
US11606803B2 (en) Resource allocation and scheduling using a buffer status report (BSR)
CN107548159B (zh) 处理上行链路传输的装置及方法
US20240224113A1 (en) Scheduling request processing method and terminal device
US11589384B2 (en) Data transmission method, terminal device, and network device
EP2364053B1 (en) Method and related device for synchronizing semi-persistent scheduling data delivery and semi-persistent scheduling resource arrival in a wireless communication system
EP2169871B1 (en) Method and apparatus of handling a timer for triggering buffer status report
CA2775952C (en) A method and apparatus to control scheduling
TWI488526B (zh) 無線通信系統中的方法及配置
WO2018170655A1 (zh) 传输数据的方法、终端设备和网络设备
CN113661672A (zh) 用于操作无线通信系统中的配置授权定时器的方法和设备
CN113825189B (zh) 一种切换控制方法及通信装置
CN113647182B (zh) 无线通信的方法和设备
KR20230087486A (ko) 소량 데이터 송신 또는 수신을 위한 방법 및 장치
WO2017049425A1 (zh) 上行数据的传输方法和用户设备
CN116134876A (zh) 用于数据传输的方法及设备
CN113647171B (zh) 无线通信的方法和设备
CN110087322B (zh) 一种调度请求方法、终端、资源分配方法及基站
WO2019157998A1 (zh) 一种传输信息的方法和装置
WO2018000247A1 (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: 18744458

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

Country of ref document: EP

Effective date: 20190731