[go: up one dir, main page]

WO2018028269A1 - 一种资源调度方法和装置 - Google Patents

一种资源调度方法和装置 Download PDF

Info

Publication number
WO2018028269A1
WO2018028269A1 PCT/CN2017/085524 CN2017085524W WO2018028269A1 WO 2018028269 A1 WO2018028269 A1 WO 2018028269A1 CN 2017085524 W CN2017085524 W CN 2017085524W WO 2018028269 A1 WO2018028269 A1 WO 2018028269A1
Authority
WO
WIPO (PCT)
Prior art keywords
resource
service
terminal
scheduling request
resource scheduling
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2017/085524
Other languages
English (en)
French (fr)
Inventor
徐小英
郑潇潇
曾清海
徐敏
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to EP17838401.2A priority Critical patent/EP3471484A4/en
Publication of WO2018028269A1 publication Critical patent/WO2018028269A1/zh
Priority to US16/252,534 priority patent/US20190159236A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/121—Wireless traffic scheduling for groups of terminals or users
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • 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/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • 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/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • 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
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/115—Grant-free or autonomous transmission

Definitions

  • the present invention relates to the field of communications, and in particular, to a resource scheduling method and apparatus.
  • Next Generation Mobile Network such as the future 5G mobile communication system
  • MBB Mobile Broad Band
  • eMBB enhanced MBB
  • mMTC massive machine type communication
  • URLLC Ultra Reliable and Low Latency Communications
  • eMBB evolved MBB
  • mMTC massive machine type communication
  • URLLC Ultra Reliable and Low Latency Communications
  • the eMBB service requires the network to provide high bandwidth and low latency
  • the mMTC service is not sensitive to delay, but the network needs to provide a large number of connections
  • the URLLC service requires the network to provide extremely high reliability and Very low end-to-end delay.
  • the uplink transmission delay requirement for the URLLC service is 0.5 ms.
  • the scheduling request is first sent on the physical uplink control channel (PUCCH).
  • PUCCH physical uplink control channel
  • Request, SR requesting the base station to allocate a small amount of resources
  • BSR Buffer Status Report
  • the BSR includes the logical channel and the requested data buffer amount, and the base station according to the priority of the logical channel in the BSR
  • the requested data buffer is used to allocate the uplink grant, and the UE sends the data after obtaining the uplink grant.
  • TTI Transmission Time Interval
  • the scheduling request process of the SR+BSR takes about 15 ms. If the TTI is reduced to 0.1 ms, the delay is about 2 ms without retransmission, so the transmission delay requirement of the future service cannot be met.
  • the embodiment of the invention provides a resource scheduling method and device, so as to reduce the transmission delay of the resource scheduling to meet the transmission delay requirement of the future service.
  • a resource scheduling method including:
  • the terminal determines that the service to be carried satisfies the trigger condition for sending the resource scheduling request
  • the terminal sends a resource scheduling request to the base station, where the resource scheduling request is used to request the base station to allocate an uplink resource to the terminal, where the resource scheduling request includes a priority indication, a scheduling-free sending indication, and a scheduling-free sending failure indication of the service. At least one of a semi-static resource request and a data cache amount indication.
  • the terminal determines that the service to be carried meets the triggering condition of the resource scheduling, including:
  • the terminal determines that the resource scheduling request is satisfied when the data buffering amount is empty and new data of the service arrives. Trigger condition; or
  • the terminal determines that the service data volume of the service is greater than a preset second threshold, determining, by the terminal, that a trigger condition that satisfies the resource scheduling request is met; or
  • the resource scheduling request is sent to the base station, so that the triggering condition of the resource scheduling request can be flexibly set according to the actual situation, thereby satisfying the delay requirement of various services.
  • the semi-static resource request includes service bearer information or a semi-static resource request indication for indicating that the base station allocates a semi-static resource.
  • the scheduling-free sending indication includes resource information used to indicate that the terminal performs unscheduled transmission.
  • the method before the terminal determines that the service to be carried needs to meet the trigger condition for sending the resource scheduling request, the method further includes:
  • the terminal determines that the data of the service carries a logical channel or a specified slice or a designated IP flow configured on the network side.
  • a resource scheduling method including:
  • the base station receives the resource scheduling request sent by the terminal, where the resource scheduling request is used to request the base station to allocate an uplink resource to the terminal, where the resource scheduling request includes the priority indication, the scheduling-free sending indication, and the scheduling-free sending failure of the service. At least one of an indication, a semi-static resource request, and a data cache amount indication;
  • the base station allocates an uplink resource to the terminal according to the resource scheduling request.
  • the semi-static resource request includes a service bearer information or a semi-static resource request indication for indicating that the base station allocates a semi-static resource.
  • the base station allocates uplink resources to the terminal according to the resource scheduling request, including:
  • the base station allocates a corresponding uplink authorization to the terminal according to the scheduling-free sending indication or the scheduling-free sending failure indication or the data buffering quantity indication in the resource scheduling request;
  • the base station determines a delay of the uplink grant based on a priority indication in the resource scheduling request.
  • the base station can allocate appropriate uplink resources for different services according to various information of services carried in the scheduling request sent by the terminal, improve resource utilization, and flexibly schedule resources.
  • the base station allocates uplink resources to the terminal according to the resource scheduling request, including:
  • the base station When the base station determines that the service bearer information in the resource scheduling request meets a preset condition, the base station allocates a semi-static resource to the terminal; or
  • the base station determines that the resource scheduling request includes a semi-static resource request indication that indicates that the base station allocates a semi-static resource
  • the base station allocates a semi-static resource to the terminal.
  • the base station can allocate the service bearer information or the indication of the semi-static resource to the requesting base station carried in the scheduling request sent by the terminal, and allocate the semi-static resource to the terminal, so that the terminal can allocate the resource scheduling request to make the base station allocate multiple times.
  • Semi-static resources are used, saving scheduling overhead.
  • the method further includes:
  • the base station When the base station detects that the terminal service bearer information does not meet the preset condition, the base station actively releases the semi-static resource or notifies the terminal to release the semi-static resource.
  • a third aspect provides a resource scheduling apparatus, which is applied to a terminal, and includes:
  • a processing unit configured to determine that a service that needs to be carried meets a trigger condition for sending a resource scheduling request
  • a sending unit configured to send a resource scheduling request to the base station, where the resource scheduling request is used to request the base station to allocate an uplink resource to the terminal, where the resource scheduling request includes a priority indication of the service, an unscheduled sending indication, and a At least one of scheduling a transmission failure indication, a semi-static resource request, and a data buffer amount indication.
  • the processing unit when the processing unit determines that the service to be carried needs to meet the triggering condition of the resource scheduling, the processing unit is specifically configured to:
  • the semi-static resource request includes a service bearer information or a semi-static resource request indication for indicating that the base station allocates a semi-static resource.
  • the scheduling-free sending indication includes resource information for instructing the terminal to perform unscheduled transmission.
  • the processing unit is further configured to:
  • Determining that the data of the service carries a logical channel or a specified slice or a designated IP flow configured on the network side.
  • a resource scheduling apparatus including:
  • a receiving unit configured to receive a resource scheduling request sent by the terminal, where the resource scheduling request is used to request the base station to allocate an uplink resource to the terminal, where the resource scheduling request includes a priority indication of the service, an unscheduled sending indication, At least one of a schedule-free transmission failure indication, a semi-static resource request, and a data buffer amount indication;
  • a processing unit configured to allocate an uplink resource to the terminal according to the resource scheduling request.
  • the semi-static resource request includes a service bearer information or a semi-static resource request indication for indicating that the base station allocates a semi-static resource.
  • the processing unit when the processing unit allocates an uplink resource to the terminal based on the resource scheduling request, the processing unit is specifically configured to:
  • the processing unit when the processing unit allocates an uplink resource to the terminal based on the resource scheduling request, the processing unit is specifically configured to:
  • the terminal When the service bearer information in the resource scheduling request meets a preset condition, the terminal is allocated a semi-static resource; or
  • the semi-static resource is allocated to the terminal.
  • the processing unit is further configured to:
  • the base station After the semi-static resource is allocated to the terminal, when the terminal service bearer information does not meet the preset condition, the base station actively releases the semi-static resource or notifies the terminal to release the semi-static resource.
  • a terminal comprising a processor, a memory, and a transmitter, wherein the memory stores a computer readable program, and the processor controls the transmitting by running a program in the memory
  • the resource scheduling method involved in the first aspect is implemented.
  • a network device in a sixth aspect, includes a processor, a memory, and a receiver, wherein the memory stores a computer readable program, and the processor controls the location by running a program in the memory The receiver implements the resource scheduling method involved in the second aspect.
  • the present application provides a computer storage medium for storing computer software instructions for use in the terminal of the first aspect and the second aspect, comprising a program designed to perform the above aspects.
  • the present application provides a computer storage medium for storing computer software instructions for use in the base station of the first aspect and the second aspect, comprising a program designed to perform the above aspects.
  • the terminal when the terminal determines that the service to be carried needs to meet the triggering condition of the resource scheduling request, the terminal sends a resource scheduling request to the base station, so that the base station allocates the uplink resource to the terminal flexibly according to the resource scheduling request sent by the terminal.
  • the resource scheduling method in the prior art can send a resource scheduling request at a time to obtain a suitable scheduling resource, so that the resource utilization rate is high, and the transmission delay of various future services can be satisfied.
  • FIG. 1 is an architecture diagram of an LTE system
  • FIG. 2 is a flowchart of a resource scheduling method according to an embodiment of the present invention.
  • FIG. 3 is a schematic structural diagram of a resource scheduling apparatus according to an embodiment of the present invention.
  • FIG. 4 is a schematic structural diagram of a terminal device according to an embodiment of the present invention.
  • FIG. 5 is a schematic structural diagram of a resource scheduling apparatus according to an embodiment of the present invention.
  • FIG. 6 is a schematic structural diagram of a network device according to an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a terminal according to an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of a base station according to an embodiment of the present invention.
  • a terminal may be referred to as a user equipment (English: User Equipment, abbreviated as: UE), a mobile station (English: Mobile Station, abbreviated as: MS), or a mobile terminal (Mobile Terminal).
  • the terminal may communicate with one or more core network devices via a radio access network (English: Radio Access Network, RAN for short), for example, the terminal may be a mobile phone (or "cellular" phone) or have The computer or the like of the mobile terminal, for example, the terminal may also be a portable, pocket, handheld, computer built-in or in-vehicle mobile device that exchanges voice and/or data with the wireless access network.
  • a base station which may be referred to as a radio access network (RAN) device, is a device that accesses a terminal to a wireless network, including but not limited to: an evolved node. B (evolved Node B, eNB), radio network controller (RNC), Node B (Node B, NB), Base Station Controller (BSC), Base Transceiver Station (BTS) ), a home base station (for example, Home evolved NodeB, or Home Node B, HNB), a BaseBand Unit (BBU), a WIFI Access Point (AP), and the like.
  • RAN radio access network
  • FIG. 1 shows the architecture of the LTE system.
  • the LTE system includes a base station 110, a core network (CN) device 120, and a terminal 130.
  • the terminal 130 accesses the wireless network through the base station 110, and the terminal 130 communicates with the external network through the CN device 120.
  • the information exchange between the base stations 110 is possible.
  • an interface between the base stations is called an X2 interface, and the base stations 110 can perform information interaction through the X2 interface.
  • LTE Long Term Evolution
  • the interface between the base station 110 and the terminal 130 is referred to as a Uu interface, which is also referred to as an air interface, and the base station 110 and the terminal 130 pass through. Air interface for communication.
  • the interface between the base station 110 and the CN device 120 is referred to as an S1 interface, and the base station 110 and the CN device 120 communicate through the S1 interface.
  • the CN device 120 may include a Mobility Management Entity (MME) and a Serving Gateway (Serving Gateway). S-GW), the user plane information interaction is implemented between the base station 110 and the S-GW, and the control plane information interaction is implemented between the base station 110 and the MME, which is not described in detail in this embodiment of the present invention.
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • the embodiment of the invention provides a resource scheduling method and device, so as to reduce the transmission delay of the resource scheduling to meet the transmission delay requirement of the future service.
  • the method and the device are based on the same inventive concept. Since the principles of the method and the device for solving the problem are similar, the implementation of the device and the method can be referred to each other, and the repeated description is not repeated.
  • an embodiment of the present invention provides a resource scheduling method, where the specific process includes the following steps:
  • Step 21 The terminal determines that the service to be carried satisfies the trigger condition for sending the resource scheduling request.
  • the method further needs to configure the application mode of the resource scheduling request, which specifically includes the following two methods:
  • the first mode when the terminal determines that the data of the service is carried in a pre-agreed logical channel or slice or IP flow, it can further determine whether the service meets a trigger condition for sending a resource scheduling request.
  • the second mode when the terminal determines that the data of the service is carried in a logical channel or a slice or an IP flow configured on the network side, the terminal can further determine whether the service meets a trigger condition for sending a resource scheduling request.
  • the network side configuration may also be terminal granularity, and the logical channel or slice or IP flow configured on the network side may be configured to the terminal through dedicated or public signaling.
  • the terminal determines that the service to be carried meets the trigger condition of the resource scheduling, and includes any one of the following situations:
  • the terminal determines a trigger condition that satisfies the resource scheduling request when the data buffer amount is empty and new data of the service arrives.
  • the terminal carries a trigger condition that satisfies the resource scheduling request when the data of the service on the channel or the slice or the IP flow whose priority indicates that the preset condition is met is reached.
  • the terminal determines that the service data in the service indicates that the service data amount of the service on the channel or the slice or the IP flow that meets the preset condition is greater than the preset first threshold, and determines that the resource scheduling request is satisfied. Trigger condition.
  • the fourth scenario when the terminal determines that the service data volume of the service is greater than a preset second threshold, the terminal determines a trigger condition that satisfies the resource scheduling request.
  • the fifth scenario when the terminal determines that the service data volume of the unscheduled service in the service is greater than a preset third threshold, determining that the trigger condition of the resource scheduling request is met.
  • the priority includes multiple levels, for example, the priority has a high priority and a low priority, the high priority priority indication is represented by 1, and the low priority priority indication is represented by 0.
  • the priority indication in the second case or the third case described above satisfies the case where the preset condition refers to a case where the priority is indicated as 1 high priority.
  • the scheduling-free service in the embodiment of the present invention does not need to allocate resources before the data is sent, and the terminal acquires one or a group of resources pre-configured by the network when the terminal is in the connected state, and directly uses the network configuration when the service data needs to be sent.
  • the one or a group of resources the terminal acquires the unscheduled resource indicated in the broadcast message when the terminal is idle, and directly uses the unscheduled resource when the service data needs to be sent.
  • the sixth situation when the terminal determines that the data buffer quantity of the scheduling-based service in the service is greater than a preset third threshold, determining that the trigger condition of the resource scheduling request is met.
  • the seventh situation when the terminal determines that the number of failed transmissions of the unscheduled service in the service is greater than a preset fourth threshold, determining that the trigger condition of the resource scheduling request is met.
  • Step 22 The terminal sends a resource scheduling request to the base station, where the resource scheduling request is used to request the base station to allocate an uplink resource to the terminal, where the resource scheduling request includes at least the priority indication, the scheduling-free sending indication, and the Scheduling any one of a transmission failure indication, a semi-static resource request, and a data buffer amount indication.
  • the semi-static resource request includes a service bearer information or a semi-static resource request indication for indicating that the base station allocates a semi-static resource.
  • the data buffer quantity indicates whether the data buffer quantity used to describe the service is higher/lower than a certain threshold.
  • the scheduling-free sending indication includes resource information used to instruct the terminal to perform scheduling-free transmission.
  • the resource scheduling request includes any one or any combination of a schedule-free sending indication, a schedule-free sending failure indication, and a data buffering quantity indication, and a priority indication of the service, At this time, the resource scheduling request is used to request the base station to allocate an uplink grant resource to the terminal.
  • the resource scheduling request includes any one or combination of the priority indication, the data cache amount indication, and the semi-static resource request of the service, where the resource is The scheduling request is used to request the base station to allocate uplink semi-static resources to the terminal.
  • each of the above indications is characterized by one bit.
  • a bit of 1 in the priority indication of the service indicates that the service contains a high priority; a bit of 0 indicates that the service with a high priority is not included.
  • the service bearer is a high priority bearer, and the service may be a corresponding one IP stream.
  • a bit of 1 indicates that the traffic on the high priority slice is included.
  • different slices may be characterized by using different physical layer frame structures or Transmission Time Intervals (TTIs).
  • TTIs Transmission Time Intervals
  • One bit in the schedule-free sending indication indicates that the service contains grant free; the bit is 0 indicates that the unscheduled service is not included.
  • a bit in the data buffer indication indicates that the data exchange amount of the service is greater than a certain threshold; a bit of 0 indicates that the data exchange amount of the service is below a certain threshold.
  • the priority indication of the service is indicated by 2 bits
  • the unscheduled transmission indication is indicated by 2 bits.
  • One bit indicates whether there is a service of a high priority logical channel, a slice or an IP stream, and one bit is used to indicate whether there is a service of a low priority logical channel, slice or IP stream.
  • One bit indicates that there is no scheduling service, and one bit indicates that there is a scheduling based service.
  • Step 23 The base station allocates an uplink resource to the terminal according to the resource scheduling request.
  • the base station allocates uplink resources to the terminal based on the resource scheduling request, in a possible implementation manner:
  • the base station allocates a corresponding uplink grant to the terminal according to the schedule-free sending indication or the schedule-free sending failure indication or the data buffering quantity indication in the resource scheduling request; for example, the resource scheduling request includes a data buffering quantity indication
  • the resource scheduling request includes a data buffering quantity indication
  • the A authorization is assigned, and when the threshold is higher than a certain threshold, the B authorization is allocated.
  • a authorization is sufficient for the terminal to send a BSR/Power Head Romm (PHR) +1 Small Transport Block (TB) size or A authorization enough for the terminal to send 1 small transport block size, where a small transmission
  • the block size can be pre-agreed or network configured.
  • B authorizes data sufficient for the terminal to transmit 1 large transport block size, where a large transport block size can be pre-agreed or network configured.
  • the scheduling-free sending indication in the scheduling request includes resource information for instructing UE1 to perform unscheduled transmission, that is,
  • the primary carrier indicates the frequency and resources of the UE1 to perform unscheduled transmission, so that the base station can determine, according to this information, whether multiple UEs simultaneously transmit data in the same resource of one carrier frequency.
  • the base station determines that there are other UEs transmitting data on the same resource as the UE1, the base station performs resource allocation and scheduling on the UE1 or other UEs to improve the efficiency of resource transmission.
  • the base station correctly receives data of one UE in multiple UEs, scheduling or continuing to use the unscheduled manner for resource allocation and scheduling for other UEs; if the data of any one UE is not correctly received, The UE1 and/or other UEs are scheduled or continue to use the unscheduled manner for resource allocation and scheduling.
  • the UE sends the resource scheduling request on the primary carrier of the licensed spectrum, and directly transmits data in the unscheduled manner on the secondary carrier of the unlicensed spectrum, so that the base station can determine whether there is a resource conflict and perform resource allocation and scheduling.
  • the resource scheduling request may be sent simultaneously with the data.
  • the base station determines whether the data of the UE is received, and determines whether there is a conflict between multiple UEs.
  • the resource scheduling is performed.
  • the request may also be sent before the data is sent.
  • the base station waits for a period of time to determine whether the data of the UE is received. The period may be a period of one or more LBTs.
  • the resource scheduling request may also be sent after the data is sent.
  • the base station determines whether the resource scheduling request is in the resource scheduling request.
  • the data of the UE is received before.
  • the UE works in a Standalone scenario, and after the LBT, allows a fixed time when the resource is used to transmit data (for example, the first time slot or the last time slot before data transmission, or a pre-configured segment)
  • the resource scheduling request is sent in a pre-configured resource and a frequency point.
  • the scheduling-free sending indication in the resource scheduling request includes resource information used to indicate that the UE performs scheduling-free transmission, and the resource information may be selected by the UE.
  • the resource information or the number of the non-scheduled resource facilitates the base station to determine whether a resource conflict occurs and allocates resources and schedules, and reduces the data transmission delay of the unlicensed spectrum and increases the spectrum utilization rate.
  • the UE can occupy the spectrum for 10 ms for data transmission according to the WLAN, it can be specified that the resource is not sent by using the pre-configured resource at a certain time of 10 ms, but the resource scheduling request is sent, so that multiple UEs simultaneously preempt After the resource is received, the data scheduling request is not sent at the same time but the non-conflicting resource is used to ensure that the network can receive the relevant resource scheduling request.
  • the scheduling-free sending indication may further include: an SR, a BSR, a pre-configured dedicated resource sending related data transmission request information, a UE ID, a quantity of data to be sent, and the like, and the resource occupied by the resource scheduling request is sent.
  • the frequency point is configured independently for each UE, so as to ensure that the UEs do not conflict or reduce the probability of collision.
  • the resource indication information can be simultaneously sent at a certain fixed time (the base station is pre-configured by the system message or other means), so that the resource indication information is The indicated uplink resources will not conflict.
  • the base station can ensure that the base station receives the scheduling-free transmission indication, thereby performing resource allocation and scheduling of the data transmission, for example, the base station according to the unscheduled transmission indication
  • the SR allocates an authorization resource to the UE, and the UE sends data according to the authorized resource after the LBT; if there is no collision or the base station correctly receives data of one UE, after the data transmission of the UE, the base station does not need to perform resource allocation of the data transmission. Scheduling, only need to send ACK/NACK response according to demand.
  • the Standalone scenario refers to a scenario where the base station or the access point of the 3GPP and the WLAN station use the same spectrum resource (the same frequency point or frequency band, unlicensed spectrum), and the base station only works in the same spectrum as the WLAN, that is, the scenario
  • the cell controlled by the base station does not work on the frequency point where only the 3GPP cell is separately arranged.
  • the cell controlled by the base station is the primary cell, and needs to send system information and control channels of other upper and lower sub-rows, including the feedback channel after the UE receives the downlink data.
  • the data request and the like that need to be sent when the UE performs uplink scheduling need to be sent in the cell.
  • Such systems are all sent according to the TDD mode, that is, the uplink data or the downlink data can only be sent in the specified subframe.
  • the base station determines a delay of the uplink authorization based on a priority indication in the resource scheduling request. For example, for a high-priority service, the base station allocates an uplink grant after receiving the N subframe or symbol after the resource scheduling request, and allocates an uplink for the low-priority service after receiving the M subframe or symbol after the resource scheduling request.
  • the N, M value may be a network configuration or a protocol convention, where M is greater than or equal to the value of N, and M and N are integers.
  • the base station allocates an uplink resource to the terminal based on the resource scheduling request
  • the terminal is the terminal.
  • a semi-static resource is allocated.
  • the temporary identifier of the wireless network used by the semi-static resource usage period and semi-persistent scheduling is pre-agreed.
  • the resource scheduling request may further include a priority indication of the service and a data buffer indication. Determining the delay of the semi-static resource based on the priority indication, the higher the priority, the smaller the delay; determining the size of the semi-static resource based on the data buffer indication.
  • the base station determines that the resource scheduling request includes a semi-static resource request indication that indicates that the base station allocates a semi-static resource. , allocating semi-static resources to the terminal. At this time, the temporary identifier of the wireless network used by the semi-static resource usage period and semi-persistent scheduling is pre-agreed.
  • the resource scheduling request may further include a priority indication of the service and a data buffer indication. Determining the delay of the semi-static resource based on the priority indication, the higher the priority, the smaller the delay; determining the size of the semi-static resource based on the data buffer indication.
  • the method further includes:
  • the base station When the base station detects that the terminal service bearer information does not meet the preset condition, the base station actively releases the semi-static resource or notifies the terminal to release the semi-static resource.
  • the base station may actively release the semi-static resource or notify the terminal to release the semi-static resource when the service sent by the terminal does not belong to the specified logical channel, slice, or IP flow.
  • the terminal cannot initiate the resource scheduling request for requesting the semi-static resource for a period of time after releasing the semi-static resource.
  • the base station sends a release indication to the terminal, and after receiving the release indication, the terminal starts a timer, and cannot initiate a resource scheduling request for requesting the semi-static resource before the timer expires. Even if a resource scheduling request for requesting a semi-static resource is initiated, the base station does not allocate a semi-static resource to the terminal.
  • the base station does not release the semi-static resource resources through explicit signaling, which is generally implicit release, that is, the terminal and the base station do not have the semi-static resources for a certain period of time. Implicit release when data is transmitted.
  • the usage period or number of semi-static resources may be default or pre-configured on the network side, and the semi-static resources are uplink and/or downlink resources.
  • the semi-static resource period is 1 TTI, the terminal can use the static resource continuously.
  • the terminal sends the indication information of the resource to the terminal, where the indication information is used to indicate the type of the resource, the size of the corresponding time-frequency resource block, and the frequency band and frequency to which the resource belongs.
  • Point or resource pool ID In one design, a resource with low latency and high reliability is supported in a resource pool, supporting high-rate and large-bandwidth resources in a resource pool, and supporting resources sent by non-emergency packet services in a resource pool.
  • FIG. 3 is a schematic structural diagram of the device 300 according to the embodiment of the present invention. As shown in FIG. 3, the device 300 includes a sending unit 301 and a processing unit 302.
  • the processing unit 302 is configured to determine that the service that needs to be carried meets the trigger condition that is sent by the resource scheduling request.
  • the sending unit 301 is configured to send a resource scheduling request to the base station, where the resource scheduling request is used to request the base station to allocate an uplink resource to the terminal, where the resource scheduling request includes a priority indication of the service, and a scheduling-free sending At least one of an indication, a schedule-free transmission failure indication, a semi-static resource request, and a data buffer amount indication.
  • the processing unit 302 is specifically configured to: when determining that the service to be carried needs to meet the triggering condition of the resource scheduling:
  • the semi-static resource request includes a service bearer information or a semi-static resource request indication for indicating that the base station allocates a semi-static resource.
  • the scheduling-free sending indication includes resource information used to indicate that the terminal performs unscheduled transmission.
  • the processing unit 302 is further configured to: before determining that the service to be carried meets the trigger condition for sending the resource scheduling request, determine that the data of the service is carried in a pre-agreed logical channel or a specified slice or specified IP flow; or, determining that the data of the service carries a logical channel or a specified slice or a designated IP flow configured on the network side.
  • each unit in the above device 300 is only a division of a logical function, and the actual implementation may be integrated into one physical entity in whole or in part, or may be physically separated.
  • each of the above units may be a separately set processing element, or may be implemented in one chip of the terminal, or may be stored in a storage element of the base station in the form of program code, and is called by a processing element of the terminal. And perform the functions of each unit above.
  • the individual units can be integrated or implemented independently.
  • the processing elements described herein can be an integrated circuit chip with signal processing capabilities.
  • each step of the above method or each of the above units may be completed by an integrated logic circuit of hardware in the processor element or an instruction in a form of software.
  • the processing element may be a general-purpose processor, such as a central processing unit (CPU), or may be one or more integrated circuits configured to implement the above method, for example, one or more specific integrated circuits (Application Specific) Integrated Circuit (ASIC), or one or more microprocessors (DSP), or one or more Field Programmable Gate Arrays (FPGAs) Wait.
  • CPU central processing unit
  • ASIC Application Specific
  • DSP microprocessors
  • FPGAs Field Programmable Gate Arrays
  • FIG. 4 is a schematic structural diagram of the device 400 according to an embodiment of the present invention, as shown in FIG. 400 includes a processor 401, a memory 402, a transmitter 403, and program code for carrying out the inventive arrangements is stored in memory 402 and controlled by processor 401 for execution.
  • the program stored in the memory 402 is used by the instruction processor 401 to perform a resource scheduling method, including: determining that a service to be carried satisfies a trigger condition for sending a resource scheduling request; and transmitting, by the transmitter 403, a resource scheduling request to the base station, where the resource scheduling request is used by the The requesting base station allocates an uplink resource to the terminal, where the resource scheduling request includes at least one of a priority indication, a schedule-free sending indication, a schedule-free sending failure indication, a semi-static resource request, and a data buffering quantity indication of the service. .
  • the processor 401 when the determining that the service to be carried needs to meet the triggering condition of the resource scheduling, the processor 401 is specifically configured to:
  • the semi-static resource request includes a service bearer information or a semi-static resource request indication for indicating that the base station allocates a semi-static resource.
  • the scheduling-free sending indication includes resource information used to indicate that the terminal performs unscheduled transmission.
  • the processor 401 is further configured to: before determining that the service to be carried meets the trigger condition for sending the resource scheduling request, determine that the data of the service is carried in a pre-agreed logical channel or a specified slice or specified IP flow; or, determining that the data of the service carries a logical channel or a specified slice or a designated IP flow configured on the network side.
  • the device 400 of the embodiment may be used to implement all the functions of the terminal in the foregoing method embodiments.
  • reference may be made to the description of the method for performing the terminal in the foregoing method embodiment, and details are not described herein again.
  • the embodiment of the present invention provides a resource device 500, where the device 500 is applied to a base station
  • FIG. 5 is a structure of the device 500 according to an embodiment of the present invention.
  • the apparatus 500 includes a receiving unit 501 and a processing unit 502.
  • the receiving unit 501 is configured to receive a resource scheduling request sent by the terminal, where the resource scheduling request is used for the request.
  • the base station allocates an uplink resource to the terminal, where the resource scheduling request includes at least one of a priority indication, a schedule-free transmission indication, a schedule-free transmission failure indication, a semi-static resource request, and a data buffer indication.
  • the processing unit 502 is configured to allocate an uplink resource to the terminal according to the resource scheduling request.
  • the semi-static resource request includes a service bearer information or a semi-static resource request indication for indicating that the base station allocates a semi-static resource.
  • the processing unit 502 is specifically configured to:
  • the processing unit 502 is specifically configured to:
  • the terminal When the service bearer information in the resource scheduling request meets a preset condition, the terminal is allocated a semi-static resource; or
  • the semi-static resource is allocated to the terminal.
  • the processing unit 502 is further configured to: after the semi-static resource is allocated to the terminal, when the terminal service bearer information does not meet the preset condition, the base station actively releases the semi-static resource or Notifying the terminal to release the semi-static resource.
  • each unit in the above apparatus 500 is only a division of a logical function, and the actual implementation may be integrated into one physical entity in whole or in part, or may be physically separated.
  • each of the above units may be a separate processing element, or may be integrated in a chip of the base station, or may be stored in a storage element of the base station in the form of a program code, and is called by a processing element of the base station. And perform the functions of each unit above.
  • the individual units can be integrated or implemented independently.
  • the processing elements described herein can be an integrated circuit chip with signal processing capabilities.
  • each step of the above method or each of the above units may be completed by an integrated logic circuit of hardware in the processor element or an instruction in a form of software.
  • the processing element may be a general-purpose processor, such as a central processing unit (CPU), or may be one or more integrated circuits configured to implement the above method, for example, one or more specific integrated circuits (Application Specific) Integrated Circuit (ASIC), or one or more digital singal processors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs).
  • ASIC Application Specific
  • DSPs digital singal processors
  • FPGAs Field Programmable Gate Arrays
  • FIG. 6 is a schematic structural diagram of a device 600 according to an embodiment of the present invention.
  • 600 includes a processor 601, a memory 602, a receiver 603, and program code for carrying out the inventive arrangements is stored in the memory 602 and controlled by the processor 601 for execution.
  • the program stored in the memory 602 is used by the instruction processor 601 to perform a resource scheduling method, including: receiving, by the receiver 603, a resource scheduling request sent by the terminal, where the resource scheduling request is used to request the base station to allocate an uplink resource to the terminal,
  • the resource scheduling request includes a priority indication of the service, a scheduling exemption sending indication, and a scheduling free transmission loss. At least one of a defeat indication, a semi-static resource request, and a data buffer amount indication; assigning an uplink resource to the terminal based on the resource scheduling request.
  • the semi-static resource request includes a service bearer information or a semi-static resource request indication for indicating that the base station allocates a semi-static resource.
  • the processor 601 when the processor allocates an uplink resource to the terminal, the processor 601 is specifically configured to: perform a scheduling-free sending indication or a scheduling-free sending failure indication or a data cache according to the resource scheduling request.
  • the quantity indication, the terminal is allocated a corresponding uplink authorization; and the time delay of the uplink authorization is determined based on the priority indication in the resource scheduling request.
  • the processor 601 when the processor allocates an uplink resource to the terminal, the processor 601 is specifically configured to: when the service bearer information in the resource scheduling request meets a preset condition, the terminal is And assigning a semi-static resource to the terminal when determining that the resource scheduling request includes a semi-static resource request indication that indicates that the base station allocates a semi-static resource.
  • the processor 601 is further configured to: after the semi-static resource is allocated to the terminal, when the terminal service bearer information does not meet the preset condition, the base station actively releases the semi-static resource or Notifying the terminal to release the semi-static resource.
  • the processor involved in the foregoing apparatus 400 and apparatus 600 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or an application-specific integrated circuit (ASIC). Or an integrated circuit for controlling the execution of the program of the present invention.
  • One or more memories included in the computer system which may be read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM) or Other types of dynamic storage devices that store information and instructions may also be disk storage. These memories are connected to the processor via a bus.
  • the receiver and transmitter can perform their functions through a transceiver, which can be a physical module capable of transceiving functions to communicate with other devices or communication networks.
  • a memory such as a RAM, holds an operating system and a program for executing the inventive scheme.
  • the operating system is a program that controls the running of other programs and manages system resources.
  • These memories, transmitters and receivers can be connected to the processor via a bus or can also be connected to the processor via dedicated connection lines.
  • the code corresponding to the method shown below is solidified into the chip, so that the chip can perform the method shown in FIG. 2 while it is running.
  • FIG. 7 is a schematic structural diagram of a terminal according to an embodiment of the present invention.
  • the terminal includes a processor 710, a storage component 720, and a transceiver 730.
  • the transceiver 730 can be coupled to an antenna.
  • the transceiver 730 receives the information transmitted by the base station through the antenna, and transmits the information to the processor 710 for processing.
  • the processor 710 processes the data of the terminal and transmits it to the base station through the transceiver 730.
  • the storage element 720 is configured to store program code for implementing the foregoing method embodiments, or the units of the embodiment shown in FIG. 3, and the processor 710 calls the program code to perform the operations of the foregoing method embodiments to implement the various modes shown in FIG. unit.
  • the storage element 720 is configured to store program code that instructs the processor 710 to execute a resource scheduling method.
  • the processor 710 is configured to invoke a program code stored in the storage element 720, and perform: determining And the resource-scheduling request is sent to the base station, where the resource scheduling request is used to request the base station to allocate an uplink resource to the terminal, where the resource scheduling request includes the priority indication of the service, and the At least one of a scheduling transmission indication, a schedule-free transmission failure indication, a semi-static resource request, and a data buffer amount indication.
  • Some or all of the above units may also be implemented by being embedded in a chip of the terminal in the form of a Field Programmable Gate Array (FPGA). And they can be implemented separately or integrated.
  • FPGA Field Programmable Gate Array
  • the processing elements herein are the same as described above, and may be a general purpose processor, such as a Central Processing Unit (CPU), or may be one or more integrated circuits configured to implement the above method, for example: one or more specific An Application Specific Integrated Circuit (ASIC), or one or more digital singnal processors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs).
  • the storage element can be a storage device or a collective name for a plurality of storage elements.
  • a plurality of interfaces may be disposed on the processor for respectively connecting peripheral devices or interface circuits connected to the peripheral devices.
  • peripheral devices for example, an interface for connecting a display screen, an interface for connecting to a camera, an interface for connecting an audio processing element, and the like.
  • FIG. 8 is a schematic structural diagram of a base station according to an embodiment of the present invention.
  • the base station includes an antenna 810, a radio frequency device 820, and a baseband device 830.
  • the antenna 810 is connected to the radio frequency device 820.
  • the radio frequency device 820 receives the information transmitted by the terminal through the antenna 810, and transmits the information sent by the terminal to the baseband device 830 for processing.
  • the baseband device 830 processes the information of the terminal and sends it to the radio frequency device 820.
  • the radio frequency device 820 processes the information of the terminal and sends it to the terminal via the antenna 810.
  • the above device 500 can be located in the baseband device 830, including the processing component 831 and the storage component 832.
  • the baseband device 830 may, for example, comprise at least one baseband board having a plurality of chips disposed thereon, as shown in FIG. 8, one of which is, for example, a processing component 831, coupled to the storage component 832 to invoke a program in the storage component 832 The operations shown in the above method embodiments are performed.
  • the baseband device 830 can also include an interface 833 for interacting with the radio frequency device 820, such as a common public radio interface (CPRI).
  • CPRI common public radio interface
  • the processing unit 502 in FIG. 5 above may be implemented in one chip of the baseband device 830, the receiving unit 501 is implemented by another chip of the baseband device 830, or they may be integrated together through one chip of the baseband device 830. Or, their functions are stored in the storage element of the baseband device 830 in the form of program code, and are implemented by one processing element of the baseband device 830. The implementation of other units is similar.
  • the processing elements herein are the same as described above, and may be a general purpose processor, such as a Central Processing Unit (CPU), or may be one or more integrated circuits configured to implement the above method, for example: one or more specific An Application Specific Integrated Circuit (ASIC), or one or more digital singnal processors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs).
  • CPU Central Processing Unit
  • ASIC Application Specific Integrated Circuit
  • DSPs digital singnal processors
  • FPGAs Field Programmable Gate Arrays
  • the storage element can be a memory or a collective name for a plurality of storage elements.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

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

Abstract

本发明公开了一种资源调度方法和装置，以降低资源调度的发送时延满足未来业务的发送时延需求。该方法为，终端确定需要承载的业务满足资源调度请求发送的触发条件时，向基站发送资源调度请求，所述资源调度请求用于请求基站为终端分配上行资源，所述资源调度请求中包括所述业务的优先级指示、免调度发送指示、免调度发送失败指示、半静态资源请求和数据缓存量指示中的至少一个；所述基站基于所述资源调度请求为所述终端分配上行资源，这种资源调度方式，能够降低业务的发送时延。

Description

一种资源调度方法和装置
本申请要求在2016年8月11日提交中国专利局、申请号为201610665452.0、发明名称为“一种资源调度方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信领域，尤其涉及一种资源调度方法和装置。
背景技术
下一代移动网络(Next Generation Mobile Network，NGMN)，如未来的5G移动通信系统除了需要支持传统的移动宽带(Mobile Broad Band，MBB)业务外，还需要支持各种需求不一的使用业务，NGMN将未来业务粗分为增强的MBB(evolved MBB，eMBB)业务，大连接机器通信(massive Machine Type Communication，mMTC)业务和高可靠低时延(Ultra Reliable and Low Latency Communications，URLLC)业务。这些业务对网络提出了不同的需求，如eMBB业务需要网络提供高带宽低时延；mMTC业务对时延不敏感，但需要网络提供超大数量的连接；URLLC业务需要网络提供极高的可靠性及极低的端到端时延，按照下一代无线通信的时延要求，对于URLLC业务的上行发送时延需求是0.5ms。
目前长期演进(Long Term Evolution，LTE)系统中，终端(User Equipment，UE)处于连接态没有上行授权时，先在物理上行链路控制信道(Physical Uplink Control Channel，PUCCH)上发送调度请求(scheduling Request，SR)，请求基站分配少量资源，获得上行授权后发送缓存状态报告(Buffer Status Report，BSR)，BSR中包含逻辑信道和请求的数据缓存量，基站根据BSR中的逻辑信道的优先级和请求的数据缓存量来分配上行授权，UE在获得上行授权后再发送数据。按照目前的1ms TTI(Transmission Time Interval)，SR+BSR的调度请求过程约需要15ms。若TTI减低到0.1ms，在没有重传的情况下送时延大约2ms，因此无法满足未来业务的发送时延需求。
发明内容
本发明实施例提供一种资源调度方法和装置，以降低资源调度的发送时延满足未来业务的发送时延需求。
本发明实施例提供的具体技术方案如下：
第一方面，提供一种资源调度方法，包括：
终端确定需要承载的业务满足资源调度请求发送的触发条件；
所述终端向基站发送资源调度请求，所述资源调度请求用于请求基站为终端分配上行资源，所述资源调度请求中包括所述业务的优先级指示、免调度发送指示、免调度发送失败指示、半静态资源请求和数据缓存量指示中的至少一个。
结合第一方面，一种可能的设计中，终端确定需要承载的业务满足资源调度的触发条件，包括：
所述终端在数据缓存量为空且有所述业务的新数据到达时，确定满足资源调度请求的 触发条件；或
所述终端承载在优先级指示满足预设条件的信道或切片或IP流上的所述业务的数据到达时，确定满足资源调度请求的触发条件；或
所述终端确定所述业务中承载在优先级指示满足预设条件的信道或切片或IP流上的业务的业务数据量大于预设的第一门限时，确定满足资源调度请求的触发条件；或
所述终端确定所述业务的业务数据量大于预设的第二门限时，确定满足资源调度请求的触发条件；或
所述终端确定所述业务中的免调度业务的业务数据量大于预设的第三门限时，确定满足资源调度请求的触发条件；或
所述终端确定所述业务中的基于调度的业务的数据缓存量大于预设的第三门限时，确定满足资源调度请求的触发条件；或
所述终端确定所述业务中免调度业务的发送失败次数大于预设的第四门限时，确定满足资源调度请求的触发条件。
这种设计中，当终端满足所述资源调度请求的触发条件时，向基站发送所述资源调度请求，这样可以根据实际情形灵活设置资源调度请求的触发条件，从而满足各种业务的时延需求。
结合第一方面，一种可能的设计中，所述半静态资源请求中包括用于指示基站分配半静态资源的业务承载信息或半静态资源请求指示。
结合第一方面，一种可能的设计中，所述免调度发送指示包括用于指示所述终端进行免调度发送的资源信息。
结合第一方面，一种可能的设计中，终端确定需要承载的业务满足资源调度请求发送的触发条件之前，所述方法还包括：
所述终端确定所述业务的数据承载在预先约定的逻辑信道或指定的切片或指定的IP流；或
所述终端确定所述业务的数据承载在网络侧配置的逻辑信道或指定的切片或指定的IP流。
第二方面，提供一种资源调度方法，包括：
基站接收终端发送的资源调度请求，所述资源调度请求用于请求基站为所述终端分配上行资源，所述资源调度请求中包括所述业务的优先级指示、免调度发送指示、免调度发送失败指示、半静态资源请求和数据缓存量指示中至少一个；
所述基站基于所述资源调度请求为所述终端分配上行资源。
结合第二方面，一种可能的设计中，所述半静态资源请求中包括用于指示基站分配半静态资源的业务承载信息或半静态资源请求指示。
结合第二方面，一种可能的设计中，所述基站基于所述资源调度请求为所述终端分配上行资源，包括：
所述基站基于所述资源调度请求中的免调度发送指示或免调度发送失败指示或数据缓存量指示，为所述终端分配相应的上行授权；
所述基站基于所述资源调度请求中的优先级指示，确定所述上行授权的时延。
这种设计中，基站能够根据终端发送的调度请求中携带的业务的各种信息，针对不同业务分配合适的上行资源，提高资源利用率，并且灵活调度资源。
结合第二方面，一种可能的设计中，所述基站基于所述资源调度请求为所述终端分配上行资源，包括：
所述基站确定所述资源调度请求中的业务承载信息满足预设条件时，为所述终端分配半静态资源；或
所述基站确定所述资源调度请求中包括指示基站分配半静态资源的半静态资源请求指示时，为所述终端分配半静态资源。
这种设计中，基站能够终端发送的调度请求中携带的请求基站分配半静态资源的业务承载信息或指示，为终端分配半静态资源，这样终端能够通过发送一次资源调度请求，使基站分配多次使用的半静态资源，从而节省调度开销。
结合第二方面，一种可能的设计中，所述基站为所述终端分配半静态资源之后，所述方法还包括：
所述基站检测到所述终端业务承载信息不满足预设条件时，所述基站主动释放所述半静态资源或通知所述终端释放所述半静态资源。
这种设计中，当终端后续发送的业务不满足预设的半静态资源的承载条件时，释放半静态资源，提高资源利用率。
第三方面，提供一种资源调度装置，应用于终端，包括：
处理单元，用于确定需要承载的业务满足资源调度请求发送的触发条件；
发送单元，用于向基站发送资源调度请求，所述资源调度请求用于请求基站为所述终端分配上行资源，所述资源调度请求中包括所述业务的优先级指示、免调度发送指示、免调度发送失败指示、半静态资源请求和数据缓存量指示中的至少一个。
结合第三方面，一种可能的设计中，所述处理单元在确定需要承载的业务满足资源调度的触发条件时，具体用于：
在数据缓存量为空且有所述业务的新数据到达时，确定满足资源调度请求的触发条件；或
承载在优先级指示满足预设条件的信道或切片或IP流上的所述业务的数据到达时，确定满足资源调度请求的触发条件；或
确定所述业务中承载在优先级指示满足预设条件的信道或切片或IP流上的业务的业务数据量大于预设的第一门限时，确定满足资源调度请求的触发条件；或
确定所述业务的业务数据量大于预设的第二门限时，确定满足资源调度请求的触发条件；或
确定所述业务中的免调度业务的业务数据量大于预设的第三门限时，确定满足资源调度请求的触发条件；或
确定所述业务中的基于调度的业务的数据缓存量大于预设的第三门限时，确定满足资源调度请求的触发条件；或
确定所述业务中免调度业务的发送失败次数大于预设的第四门限时，确定满足资源调度请求的触发条件。
结合第三方面，一种可能的设计中，所述半静态资源请求中包括用于指示基站分配半静态资源的业务承载信息或半静态资源请求指示。
结合第三方面，一种可能的设计中，所述免调度发送指示包括用于指示所述终端进行免调度发送的资源信息。
结合第三方面，一种可能的设计中，所述处理单元，还用于：
在确定需要承载的业务满足资源调度请求发送的触发条件之前，确定所述业务的数据承载在预先约定的逻辑信道或指定的切片或指定的IP流；或
确定所述业务的数据承载在网络侧配置的逻辑信道或指定的切片或指定的IP流。
第四方面，提供一种资源调度装置，包括：
接收单元，用于接收终端发送的资源调度请求，所述资源调度请求用于请求基站为所述终端分配上行资源，所述资源调度请求中包括所述业务的优先级指示、免调度发送指示、免调度发送失败指示、半静态资源请求和数据缓存量指示中至少一个；
处理单元，用于基于所述资源调度请求为所述终端分配上行资源。
结合第四方面，一种可能的设计中，所述半静态资源请求中包括用于指示基站分配半静态资源的业务承载信息或半静态资源请求指示。
结合第四方面，一种可能的设计中，所述处理单元在基于所述资源调度请求为所述终端分配上行资源时，具体用于：
基于所述资源调度请求中的免调度发送指示或免调度发送失败指示或数据缓存量指示，为所述终端分配相应的上行授权；
基于所述资源调度请求中的优先级指示，确定所述上行授权的时延。
结合第四方面，一种可能的设计中，所述处理单元在基于所述资源调度请求为所述终端分配上行资源时，具体用于：
确定所述资源调度请求中的业务承载信息满足预设条件时，为所述终端分配半静态资源；或
确定所述资源调度请求中包括指示基站分配半静态资源的半静态资源请求指示时，为所述终端分配半静态资源。
结合第四方面，一种可能的设计中，所述处理单元，还用于：
为所述终端分配半静态资源之后，检测到所述终端业务承载信息不满足预设条件时，所述基站主动释放所述半静态资源或通知所述终端释放所述半静态资源。
第五方面，提供一种终端，该终端包括处理器、存储器、发射器，其中，所述存储器中存有计算机可读程序，所述处理器通过运行所述存储器中的程序，控制所述发射器，实现第一方面涉及的资源调度方法。
第六方面，提供一种网络设备，该网络设备包括处理器、存储器、接收器，其中，所述存储器中存有计算机可读程序，所述处理器通过运行所述存储器中的程序，控制所述接收器，实现第二方面涉及的资源调度方法。
第七方面，本申请提供一种计算机存储介质，用于储存为上述第一方面、第二方面所述的终端所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
第八方面，本申请提供一种计算机存储介质，用于储存为上述第一方面、第二方面所述的基站所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
可见，在以上各个方面，终端确定需要承载的业务满足资源调度请求发送的触发条件时，向基站发送资源调度请求，从而使基站基于终端发送的资源调度请求灵活的为终端分配上行资源，相比于现有技术中的资源调度方法，能够一次发送资源调度请求获得合适调度资源，使得资源利用率高，而且能够满足各种未来业务的传输时延。
附图说明
图1为LTE系统架构图；
图2为本发明实施例中的资源调度方法流程图；
图3为本发明实施例中的一种资源调度装置结构示意图；
图4为本发明实施例中的终端设备结构示意图；
图5为本发明实施例中的一种资源调度装置结构示意图；
图6为本发明实施例中的网络设备结构示意图；
图7为本发明实施例中的终端结构示意图；
图8为本发明实施例中的基站结构示意图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本发明一部分实施例，并不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
应理解，在本发明实施例中，终端(Terminal)可以称之为用户设备(英文：User Equipment，简称：UE)、移动台(英文：Mobile Station，简称：MS)或移动终端(Mobile Terminal)等，该终端可以经无线接入网(英文：Radio Access Network，简称：RAN)与一个或多个核心网设备进行通信，例如，终端可以是移动电话(或称为“蜂窝”电话)或具有移动终端的计算机等，例如，终端还可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置，它们与无线接入网交换语音和/或数据。
应理解，在本发明实施例中，基站又可以称之为无线接入网(Radio Access Network，RAN)设备，是一种将终端接入到无线网络的设备，包括但不限于：演进型节点B(evolved Node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、基站控制器(Base Station Controller，BSC)、基站收发台(Base Transceiver Station,BTS)、家庭基站(例如，Home evolved NodeB，或Home Node B，HNB)、基带单元(BaseBand Unit，BBU)、WIFI接入点(Access Point，AP)等。
还应理解，本发明实施例中提供的技术方案，可以应用于各种通信系统，例如：全球移动通信系统(英文：Global System of Mobile communication，简称：GSM，)，码分多址(英文：Code Division Multiple Access，简称：CDMA)系统，宽带码分多址(英文：Wideband Code Division Multiple Access Wireless，简称：WCDMA)系统，通用分组无线业务(英文：General Packet Radio Service，简称：GPRS)系统，长期演进(英文：Long Term Evolution，简称：LTE)系统、未来演进系统，如5G系统。
本发明实施例中以应用到LTE系统为例来说明。如图1所示为LTE系统架构图。LTE系统包括：基站110、核心网(Core Network，CN)设备120和终端130，终端130通过基站110接入无线网络，且通过CN设备120实现终端130与外部网络的通信。该系统中，基站110之间可以进行信息交互，例如在长期演进(Long Term Evolution，LTE)系统中，基站之间的接口称为X2接口，且基站110之间可以通过X2接口进行信息交互。此外，基站110与终端130之间的接口称为Uu口，又称之为空口，基站110与终端130之间通过 空口进行通信。基站110与CN设备120之间的接口称为S1接口，基站110与CN设备120通过S1接口进行通信，CN设备120可以包括移动性管理实体(Mobility Management Entity，MME)和服务网关(Serving Gateway，S-GW)，基站110与S-GW之间实现用户面信息交互，基站110与MME之间实现控制面信息交互，本发明实施例在此不再详述。
本发明实施例提供一种资源调度方法和装置，以降低资源调度的发送时延满足未来业务的发送时延需求。其中，方法和装置是基于同一发明构思的，由于方法及装置解决问题的原理相似，因此装置与方法的实施可以相互参见，重复之处不再赘述。
基于图1所示的网络架构，参阅图2所示，本发明实施例提供一种资源调度方法，具体流程包括如下步骤：
步骤21：终端确定需要承载的业务满足资源调度请求发送的触发条件。
进一步的，终端确定需要承载的业务满足资源调度请求发送的触发条件之前，所述方法还需要配置资源调度请求的应用方式，具体包括以下两种方式：
第一种方式：所述终端确定所述业务的数据承载在预先约定的逻辑信道或切片或IP流时，才能进一步确定所述业务是否满足资源调度请求发送的触发条件。
第二种方式：所述终端确定所述业务的数据承载在网络侧配置的逻辑信道或切片或IP流时，才能进一步确定所述业务是否满足资源调度请求发送的触发条件。此时，网络侧配置也可以是终端粒度的，网络侧配置的逻辑信道或切片或IP流可通过专用或公共信令配置给终端。
具体的，终端确定需要承载的业务满足资源调度的触发条件，包括以下情形中的任意一种情形：
第一种情形：所述终端在数据缓存量为空且有所述业务的新数据到达时，确定满足资源调度请求的触发条件。
第二种情形：所述终端承载在优先级指示满足预设条件的信道或切片或IP流上的所述业务的数据到达时，确定满足资源调度请求的触发条件。
第三种情形：所述终端确定所述业务中承载在优先级指示满足预设条件的信道或切片或IP流上的业务的业务数据量大于预设的第一门限时，确定满足资源调度请求的触发条件。
第四种情形：所述终端确定所述业务的业务数据量大于预设的第二门限时，确定满足资源调度请求的触发条件。
第五种情形：所述终端确定所述业务中的免调度业务的业务数据量大于预设的第三门限时，确定满足资源调度请求的触发条件。
需要说明的是，优先级包括多个级别，例如优先级存在高优先级和低优先级这两种情形，高优先级的优先级指示用1表示，低优先级的优先级指示用0表示，上述第二种情形或第三种情形中的优先级指示满足预设条件指的是优先级指示为1的高优先级的情形。
需要说明的是，本发明实施例中的免调度业务在发送数据之前无需网络分配资源，终端在连接态时获取网络预先配置的一个或一组资源，在需要发送业务数据时，直接使用网络配置的该一个或一组资源；终端在空闲态时获取广播消息中指示的免调度资源，在需要发送业务数据时，直接使用该免调度资源。
第六种情形：所述终端确定所述业务中的基于调度的业务的数据缓存量大于预设的第三门限时，确定满足资源调度请求的触发条件。
第七种情形：所述终端确定所述业务中免调度业务的发送失败次数大于预设的第四门限时，确定满足资源调度请求的触发条件。
步骤22：所述终端向基站发送资源调度请求，所述资源调度请求用于请求基站为终端分配上行资源，所述资源调度请求中至少包括所述业务的优先级指示、免调度发送指示、免调度发送失败指示、半静态资源请求和数据缓存量指示中的任意一个。
其中，所述半静态资源请求中包括用于指示基站分配半静态资源的业务承载信息或半静态资源请求指示。
其中，数据缓存量指示用于描述所述业务的数据缓存量是否高于/低于一定门限。
其中，所述免调度发送指示包括用于指示所述终端进行免调度发送的资源信息。
可选的，一种可能的实施方式中，所述资源调度请求中包括免调度发送指示、免调度发送失败指示和数据缓存量指示中的任意一个或任意组合以及所述业务的优先级指示，此时，所述资源调度请求用于请求基站为终端分配上行授权资源。
可选的，另一种可能的实施方式中，所述资源调度请求中包括所述业务的优先级指示、数据缓存量指示中的任意一个或组合以及半静态资源请求，此时，所述资源调度请求用于请求基站为终端分配上行半静态资源。
此外，上述每个指示用一个比特来表征。业务的优先级指示中一个比特为1表示包含高优先级的业务；比特为0表示不包含高有优先级的业务。可选的，该业务承载为高优先级承载，该业务可以是对应一个IP流。一个比特为1表示包含高优先级切片(slice)上的业务。可选的，不同的slice可表征采用不同的物理层帧结构或者传输时间间隔(Transmission Time Interval，TTI)。免调度发送指示中一个比特为1表示包含免调度(grant free)的业务；比特为0表示不包含免调度的业务。数据缓存量指示中一个比特为1表示所述业务的数据换存量大于一定门限；比特为0表示所述业务的数据换存量低于一定门限。
举例，用2个比特指示业务的优先级指示，用2个比特指示免调度发送指示。一个比特指示是否有高优先级逻辑信道、切片或者IP流的业务，一个比特用于指示是否有低优先级逻辑信道、切片或者IP流的业务。一个比特指示有免调度的业务，一个比特指示有基于调度的业务。
步骤23：所述基站基于所述资源调度请求为所述终端分配上行资源。
具体的，所述基站基于所述资源调度请求为所述终端分配上行资源时，一种可能的实施方式中：
所述基站基于所述资源调度请求中的免调度发送指示或免调度发送失败指示或数据缓存量指示，为所述终端分配相应的上行授权；例如，所述资源调度请求中包括数据缓存量指示，当业务的数据缓存量低于一定门限时分配A授权，高于一定门限时分配B授权。比如，A授权足以终端发送一个BSR/剩余功率(Power Head Romm，PHR)+1个小传输块(Transport Block，TB)大小或A授权足以终端发送1个小传输块大小,其中，一个小传输块大小可以是预先约定或网络配置的。B授权足以终端发送1个大传输块大小的数据，其中，一个大传输块大小可以是预先约定或网络配置的。
例如，在辅载波上引入非授权(unlicensed)频谱进行主载波辅助辅载波的发送时，当UE1在辅载波采用免调度方式直接发送数据时，需要在主载波上发送资源调度请求，所述资源调度请求中的免调度发送指示包括用于指示UE1进行免调度发送的资源信息，即在 主载波上指示UE1进行免调度发送的频点以及资源，便于基站能够根据这个信息确定是否有多个UE同时在一个载频的同一个资源发送数据。当基站确定存在其他UE与所述UE1同时在一个资源上发送数据时，基站对所述UE1或其他UE进行资源分配与调度，提高资源发送的效率。可选的，若基站在多个UE中正确接收到一个UE的数据，则对其他UE采用调度或继续采用免调度的方式进行资源分配与调度；若没有正确接收到任何一个UE的数据，则对UE1和/或其他UE采用调度或继续采用免调度的方式进行资源分配与调度。
此时，UE在授权频谱的主载波上发送所述资源调度请求，在非授权频谱的辅载波上采用免调度方式直接发送数据，便于基站确定是否存在资源冲突并进行资源分配与调度。所述资源调度请求可以与数据同时发送，此时当基站收到这个资源调度请求时同时判断是否收到所述UE的数据，确定是否有多个UE的冲突；可选的，所述资源调度请求也可以在数据发送之前发送，此时，当基站收到这个资源调度请求后，等待一段时间确定是否会收到所述UE的数据。这段时间可以是一个或多个LBT的周期；可选的，所述资源调度请求也可以在数据发送之后发送，此时，当基站收到这个资源调度请求之后，判断是否在这个资源调度请求前收到所述UE的数据。
例如，UE工作在Standalone场景下，在LBT后，允许占用资源发送数据的这段时间内的固定时刻(例如，数据发送前的第一个时隙或最后一个时隙，或预配置的某段时间)，在预配置的资源和频点发送所述资源调度请求，所述资源调度请求中的免调度发送指示包括用于指示UE进行免调度发送的资源信息，所述资源信息可以是UE选用的资源信息或免调度资源的编号，便于基站确定是否发生资源冲突并进行资源分配与调度，同时减少非授权频谱的数据传输时延，加大其频谱利用率。比如UE按照WLAN规定可以占用频谱10ms用于数据发送，则可以规定在这10ms的某一规定时刻，使用预配置的资源不发送数据，而是发送所述资源调度请求，这样多个UE同时抢占到资源后，在同一时刻不发送数据而是采用不冲突的资源发送资源调度请求，保证网络能收到相关资源调度请求。
可选的，所述免调度发送指示中还可以包括SR、BSR、预配置的专用资源发送相关数传请求信息、UE ID、需要发送的数据量等，发送该资源调度请求所占用的资源和频点是每个UE独立配置，尽量保证UE之间不会冲突或降低冲突概率。这样当两个或多个UE在LBT后同时使用相同免调度资源发送数据时，可以保证在某一固定时刻(基站通过系统消息或其他途径预先配置)同时发送资源指示信息，使资源指示信息中指示的上行资源不会发生冲突。
当有两个UE同时采用相同免调度资源发送数据时，数据发送产生冲突时，可以保证基站收到免调度发送指示，从而进行数据传输的资源分配与调度，例如基站根据免调度发送指示中的SR，给UE分配授权资源，UE根据授权资源在LBT后发送数据；如果没有冲突或基站正确接收一个UE的数据，则在该UE的数据传输后，基站不需要再进行数据传输的资源分配与调度，只需要根据需求发送ACK/NACK响应。
需要说明的是，Standalone场景是指3GPP的基站或接入点和WLAN的站点使用同一频谱资源(相同频点或频段，unlicensed频谱)，同时该基站只工作在与WLAN同频谱的场景，即该基站控制的小区都没有在只有单独布置3GPP小区的频点上工作，该基站控制的小区是主小区，需要发送系统信息以及其他上下子行的控制信道，包括UE接收下行数据后的反馈信道，UE进行上行调度时需要发送的数据请求等都需要在该小区发送，这样的系统都是按照TDD模式发送，即只能在规定的子帧发送上行数据或下行数据。
所述基站基于所述资源调度请求为所述终端分配上行资源时，一种可能的实施方式中：所述基站基于所述资源调度请求中的优先级指示，确定所述上行授权的时延。比如，针对高优先级的业务，基站在收到资源调度请求后的N子帧或符号后分配上行授权，针对低优先级业务，在收到资源调度请求后的M子帧或符号后分配上行授权，N、M值可以是网络配置或协议约定，其中M大于等于N值，M和N为整数。
所述基站基于所述资源调度请求为所述终端分配上行资源时，一种可能的实施方式中：所述基站确定所述资源调度请求中的业务承载信息满足预设条件时，为所述终端分配半静态资源，此时，所述半静态资源的使用周期、半静态调度使用的无线网络临时标识为预先约定好的。可选的，所述资源调度请求中还可以包括业务的优先级指示和数据缓存量指示。所述基站基于所述优先级指示确定所述半静态资源的时延，优先级越高时延越小；基于所述数据缓存量指示确定半静态资源的大小。
所述基站基于所述资源调度请求为所述终端分配上行资源时，一种可能的实施方式中：所述基站确定所述资源调度请求中包括指示基站分配半静态资源的半静态资源请求指示时，为所述终端分配半静态资源。此时，所述半静态资源的使用周期、半静态调度使用的无线网络临时标识为预先约定好的。可选的，所述资源调度请求中还可以包括业务的优先级指示和数据缓存量指示。所述基站基于所述优先级指示确定所述半静态资源的时延，优先级越高时延越小；基于所述数据缓存量指示确定半静态资源的大小。
具体的，所述基站为所述终端分配半静态资源之后，所述方法还包括：
所述基站检测到所述终端业务承载信息不满足预设条件时，所述基站主动释放所述半静态资源或通知所述终端释放所述半静态资源。
基站为所述终端分配半静态资源之后，当终端后续发送的业务不是属于承载在指定的逻辑信道、切片或IP流时，基站可以基站主动释放半静态资源或通知终端释放半静态资源。
具体的，对于基站主动释放半静态资源的，终端在释放半静态资源后的一段时间内都不能发起请求半静态资源的资源调度请求。
具体的，对于基站通知终端释放半静态资源的，基站向终端发送释放指示，终端在收到释放指示后，启动一个定时器，在定时器超时前不能发起请求半静态资源的资源调度请求。即使发起了请求半静态资源的资源调度请求，基站也不给终端分配半静态资源。
此外，终端在基站分配半静态资源后，一般来说，基站不会通过显式信令释放该半静态资源资源，一般是隐式释放，即在终端和基站在该半静态资源上一段时间没有数据传输时，进行隐式释放的。
半静态资源的使用周期或次数可以是默认的或网络侧预先配置的，半静态资源是上行和/或下行资源。半静态资源周期为1个TTI时，相当于终端可以连续使用该静态资源。
可选的，所述基站为终端分配上行资源之后，向终端发送所述资源的指示信息，所述指示信息用于指示资源的类型，对应的时频资源块的大小，资源所属的频带、频点或资源池标识。一种设计中，针对低时延高可靠的资源在一个资源池，支持高速率大带宽的资源在一个资源池，支持非紧急的小包业务发送的资源在一个资源池。
应理解，以上实施例虽然以LTE系统为例，但是其可以用于其它通信系统中，且该通信系统支持基站之间的信息交互。
基于上述实施例提供的资源调度方法，请参见图3所示，本发明实施例提供一种资源 装置300，该装置300应用于终端，图3所示为本发明实施例提供的装置300的结构示意图，如图3所示，该装置300包括发送单元301和处理单元302。
所述处理单元302，用于确定需要承载的业务满足资源调度请求发送的触发条件。
所述发送单元301，用于向基站发送资源调度请求，所述资源调度请求用于请求基站为所述终端分配上行资源，所述资源调度请求中包括所述业务的优先级指示、免调度发送指示、免调度发送失败指示、半静态资源请求和数据缓存量指示中的至少一个。
可选的，所述处理单元302在确定需要承载的业务满足资源调度的触发条件时，具体用于：
在数据缓存量为空且有所述业务的新数据到达时，确定满足资源调度请求的触发条件；或
承载在优先级指示满足预设条件的信道或切片或IP流上的所述业务的数据到达时，确定满足资源调度请求的触发条件；或
确定所述业务中承载在优先级指示满足预设条件的信道或切片或IP流上的业务的业务数据量大于预设的第一门限时，确定满足资源调度请求的触发条件；或
确定所述业务的业务数据量大于预设的第二门限时，确定满足资源调度请求的触发条件；或
确定所述业务中的免调度业务的业务数据量大于预设的第三门限时，确定满足资源调度请求的触发条件；或
确定所述业务中的基于调度的业务的数据缓存量大于预设的第三门限时，确定满足资源调度请求的触发条件；或
确定所述业务中免调度业务的发送失败次数大于预设的第四门限时，确定满足资源调度请求的触发条件。
可选的，所述半静态资源请求中包括用于指示基站分配半静态资源的业务承载信息或半静态资源请求指示。
可选的，所述免调度发送指示包括用于指示所述终端进行免调度发送的资源信息。
可选的，所述处理单元302，还用于：在确定需要承载的业务满足资源调度请求发送的触发条件之前，确定所述业务的数据承载在预先约定的逻辑信道或指定的切片或指定的IP流；或，确定所述业务的数据承载在网络侧配置的逻辑信道或指定的切片或指定的IP流。
应理解以上装置300中的各个单元的划分仅仅是一种逻辑功能的划分，实际实现时可以全部或部分集成到一个物理实体上，也可以物理上分开。例如，以上各个单元可以为单独设立的处理元件，也可以集成在终端的某一个芯片中实现，此外，也可以以程序代码的形式存储于基站的存储元件中，由终端的某一个处理元件调用并执行以上各个单元的功能。此外各个单元可以集成在一起，也可以独立实现。这里所述的处理元件可以是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤或以上各个单元可以通过处理器元件中的硬件的集成逻辑电路或者软件形式的指令完成。该处理元件可以是通用处理器，例如中央处理器(Central Processing Unit，CPU)，还可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个特定集成电路(Application Specific Integrated Circuit，ASIC)，或，一个或多个微处理器(digital singnal processor，DSP)，或，一个或者多个现场可编程门阵列(Field Programmable Gate Array，FPGA) 等。
需要说明的是，本发明实施例中的装置300的各个单元的功能实现以及交互方式可以进一步参照相关方法实施例的描述，在此不再赘述。
本发明实施例还提供一种设备400，该设备400可以为终端，或位于终端上的其他设备，图4所示为本发明实施例提供的设备400的结构示意图，如图4所示，设备400包括处理器401，存储器402、发射器403，执行本发明方案的程序代码保存在存储器402中，并由处理器401来控制执行。
存储器402中存储的程序用于指令处理器401执行资源调度方法，包括：确定需要承载的业务满足资源调度请求发送的触发条件；通过发射器403向基站发送资源调度请求，所述资源调度请求用于请求基站为所述终端分配上行资源，所述资源调度请求中包括所述业务的优先级指示、免调度发送指示、免调度发送失败指示、半静态资源请求和数据缓存量指示中的至少一个。
可选的，所述处理器401在确定需要承载的业务满足资源调度的触发条件时，具体用于：
在数据缓存量为空且有所述业务的新数据到达时，确定满足资源调度请求的触发条件；或
承载在优先级指示满足预设条件的信道或切片或IP流上的所述业务的数据到达时，确定满足资源调度请求的触发条件；或
确定所述业务中承载在优先级指示满足预设条件的信道或切片或IP流上的业务的业务数据量大于预设的第一门限时，确定满足资源调度请求的触发条件；或
确定所述业务的业务数据量大于预设的第二门限时，确定满足资源调度请求的触发条件；或
确定所述业务中的免调度业务的业务数据量大于预设的第三门限时，确定满足资源调度请求的触发条件；或
确定所述业务中的基于调度的业务的数据缓存量大于预设的第三门限时，确定满足资源调度请求的触发条件；或
确定所述业务中免调度业务的发送失败次数大于预设的第四门限时，确定满足资源调度请求的触发条件。
可选的，所述半静态资源请求中包括用于指示基站分配半静态资源的业务承载信息或半静态资源请求指示。
可选的，所述免调度发送指示包括用于指示所述终端进行免调度发送的资源信息。
可选的，所述处理器401，还用于：在确定需要承载的业务满足资源调度请求发送的触发条件之前，确定所述业务的数据承载在预先约定的逻辑信道或指定的切片或指定的IP流；或，确定所述业务的数据承载在网络侧配置的逻辑信道或指定的切片或指定的IP流。
可以理解的是，本实施例的设备400可用于实现上述方法实施例中涉及终端的所有功能，其具体实现过程可以参照上述方法实施例终端执行方法的相关描述，此处不再赘述。
基于上述实施例提供的资源调度方法，请参见图5所示，本发明实施例提供一种资源装置500，该装置500应用于基站，图5所示为本发明实施例提供的装置500的结构示意图，如图5所示，该装置500包括接收单元501和处理单元502。
所述接收单元501，用于接收终端发送的资源调度请求，所述资源调度请求用于请求 基站为所述终端分配上行资源，所述资源调度请求中包括所述业务的优先级指示、免调度发送指示、免调度发送失败指示、半静态资源请求和数据缓存量指示中至少一个。
所述处理单元502，用于基于所述资源调度请求为所述终端分配上行资源。
可选的，所述半静态资源请求中包括用于指示基站分配半静态资源的业务承载信息或半静态资源请求指示。
可选的，所述处理单元502在基于所述资源调度请求为所述终端分配上行资源时，具体用于：
基于所述资源调度请求中的免调度发送指示或免调度发送失败指示或数据缓存量指示，为所述终端分配相应的上行授权；
基于所述资源调度请求中的优先级指示，确定所述上行授权的时延。
可选的，所述处理单元502在基于所述资源调度请求为所述终端分配上行资源时，具体用于：
确定所述资源调度请求中的业务承载信息满足预设条件时，为所述终端分配半静态资源；或
确定所述资源调度请求中包括指示基站分配半静态资源的半静态资源请求指示时，为所述终端分配半静态资源。
可选的，所述处理单元502，还用于：为所述终端分配半静态资源之后，检测到所述终端业务承载信息不满足预设条件时，所述基站主动释放所述半静态资源或通知所述终端释放所述半静态资源。
应理解以上装置500中的各个单元的划分仅仅是一种逻辑功能的划分，实际实现时可以全部或部分集成到一个物理实体上，也可以物理上分开。例如，以上各个单元可以为单独设立的处理元件，也可以集成在基站的某一个芯片中实现，此外，也可以以程序代码的形式存储于基站的存储元件中，由基站的某一个处理元件调用并执行以上各个单元的功能。此外各个单元可以集成在一起，也可以独立实现。这里所述的处理元件可以是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤或以上各个单元可以通过处理器元件中的硬件的集成逻辑电路或者软件形式的指令完成。该处理元件可以是通用处理器，例如中央处理器(Central Processing Unit，CPU)，还可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个特定集成电路(Application Specific Integrated Circuit，ASIC)，或，一个或多个微处理器(digital singnal processor，DSP)，或，一个或者多个现场可编程门阵列(Field Programmable Gate Array，FPGA)等。
需要说明的是，本发明实施例中的装置500的各个单元的功能实现以及交互方式可以进一步参照相关方法实施例的描述，在此不再赘述。
本发明实施例还提供一种设备600，该设备600可以为基站，或位于基站上的其他设备，图6所示为本发明实施例提供的设备600的结构示意图，如图6所示，设备600包括处理器601，存储器602、接收器603，执行本发明方案的程序代码保存在存储器602中，并由处理器601来控制执行。
存储器602中存储的程序用于指令处理器601执行资源调度方法，包括：通过接收器603接收终端发送的资源调度请求，所述资源调度请求用于请求基站为所述终端分配上行资源，所述资源调度请求中包括所述业务的优先级指示、免调度发送指示、免调度发送失 败指示、半静态资源请求和数据缓存量指示中至少一个；基于所述资源调度请求为所述终端分配上行资源。
可选的，所述半静态资源请求中包括用于指示基站分配半静态资源的业务承载信息或半静态资源请求指示。
可选的，所述处理器601在基于所述资源调度请求为所述终端分配上行资源时，具体用于：基于所述资源调度请求中的免调度发送指示或免调度发送失败指示或数据缓存量指示，为所述终端分配相应的上行授权；基于所述资源调度请求中的优先级指示，确定所述上行授权的时延。
可选的，所述处理器601在基于所述资源调度请求为所述终端分配上行资源时，具体用于：确定所述资源调度请求中的业务承载信息满足预设条件时，为所述终端分配半静态资源；或，确定所述资源调度请求中包括指示基站分配半静态资源的半静态资源请求指示时，为所述终端分配半静态资源。
可选的，所述处理器601，还用于：为所述终端分配半静态资源之后，检测到所述终端业务承载信息不满足预设条件时，所述基站主动释放所述半静态资源或通知所述终端释放所述半静态资源。
可以理解的是，本发明实施例上述设备400和设备600中涉及的处理器可以是一个通用中央处理器(CPU)，微处理器，特定应用集成电路application-specific integrated circuit(ASIC)，或一个或多个用于控制本发明方案程序执行的集成电路。计算机系统中包括的一个或多个存储器，可以是只读存储器read-only memory(ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器random access memory(RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是磁盘存储器。这些存储器通过总线与处理器相连接。
接收器和发射器可以通过收发器实现其功能，所述收发器可以是能够实现收发功能的实体模块，以便与其他设备或通信网络通信。
存储器，如RAM，保存有操作系统和执行本发明方案的程序。操作系统是用于控制其他程序运行，管理系统资源的程序。
这些存储器、发射器和接收器可以通过总线与处理器相连接，或者也可以通过专门的连接线分别与处理器连接。
通过对处理器进行设计编程，将下面所示的方法所对应的代码固化到芯片内，从而使芯片在运行时能够执行图2所示的方法。
请参见图7，图7为本发明实施例提供的一种终端的结构示意图。如图7所示，该终端包括：处理器710、存储元件720、收发装置730。收发装置730可以与天线连接。在下行方向上，收发装置730通过天线接收基站发送的信息，并将信息发送给处理器710进行处理。在上行方向上，处理器710对终端的数据进行处理，并通过收发装置730发送给基站。
该存储元件720用于存储实现以上方法实施例，或者图3所示实施例各个单元的程序代码，处理器710调用该程序代码，执行以上方法实施例的操作，以实现图3所示的各个单元。
例如，所述存储元件720，用于存储指令处理器710执行资源调度方法的程序代码。
所述处理器710，用于调用所述存储元件720中存储的程序代码，执行：确定需要承 载的业务满足资源调度请求发送的触发条件；向基站发送资源调度请求，所述资源调度请求用于请求基站为终端分配上行资源，所述资源调度请求中包括所述业务的优先级指示、免调度发送指示、免调度发送失败指示、半静态资源请求和数据缓存量指示中的至少一个。
以上各个单元的部分或全部也可以通过现场可编程门阵列(Field Programmable Gate Array，FPGA)的形式内嵌于该终端的某一个芯片上来实现。且它们可以单独实现，也可以集成在一起。
这里的处理元件同以上描述，可以是通用处理器，例如中央处理器(Central Processing Unit，CPU)，还可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个特定集成电路(Application Specific Integrated Circuit，ASIC)，或，一个或多个微处理器(digital singnal processor，DSP)，或，一个或者多个现场可编程门阵列(Field Programmable Gate Array，FPGA)等。存储元件可以是一个存储装置，也可以是多个存储元件的统称。
另外，该处理器上可以设置多个接口，分别用于连接外围设备或与外围设备连接的接口电路。例如，用于连接显示屏的接口，用于连接摄像头的接口，用于连接音频处理元件的接口等。
请参见图8，图8为本发明实施例提供的一种基站的结构示意图。如图8所示，该基站包括：天线810、射频装置820、基带装置830。天线810与射频装置820连接。在上行方向上，射频装置820通过天线810接收终端发送的信息，将终端发送的信息发送给基带装置830进行处理。在下行方向上，基带装置830对终端的信息进行处理，并发送给射频装置820，射频装置820对终端的信息进行处理后经过天线810发送给终端。
以上装置500可以位于基带装置830，包括处理元件831和存储元件832。基带装置830例如可以包括至少一个基带板，该基带板上设置有多个芯片，如图8所示，其中一个芯片例如为处理元件831，与存储元件832连接，以调用存储元件832中的程序，执行以上方法实施例中所示的操作。该基带装置830还可以包括接口833，用于与射频装置820交互信息，该接口例如为通用公共无线接口(common public radio interface，CPRI)。
再如，以上图5中的处理单元502可以通过基带装置830的一个芯片中实现，接收单元501通过基带装置830的另一个芯片实现，或者，将它们集成在一起，通过基带装置830的一个芯片实现；或者，将它们的功能通过程序代码的形式存储于基带装置830的存储元件中，通过基带装置830的一个处理元件调度实现。其它单元的实现与之类似。
这里的处理元件同以上描述，可以是通用处理器，例如中央处理器(Central Processing Unit，CPU)，还可以是被配置成实施以上方法的一个或多个集成电路，例如：一个或多个特定集成电路(Application Specific Integrated Circuit，ASIC)，或，一个或多个微处理器(digital singnal processor，DSP)，或，一个或者多个现场可编程门阵列(Field Programmable Gate Array，FPGA)等。
存储元件可以是一个存储器，也可以是多个存储元件的统称。
本领域内的技术人员应明白，本发明的实施例可提供为方法、系统、或计算机程序产品。因此，本发明可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本发明的优选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例作出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本发明范围的所有变更和修改。
显然，本领域的技术人员可以对本发明实施例进行各种改动和变型而不脱离本发明实施例的精神和范围。这样，倘若本发明实施例的这些修改和变型属于本发明权利要求及其等同技术的范围之内，则本发明也意图包含这些改动和变型在内。

Claims (20)

  1. 一种资源调度方法，其特征在于，包括：
    终端确定需要承载的业务满足资源调度请求发送的触发条件；
    所述终端向基站发送资源调度请求，所述资源调度请求用于请求基站为终端分配上行资源，所述资源调度请求中包括所述业务的优先级指示、免调度发送指示、免调度发送失败指示、半静态资源请求和数据缓存量指示中的至少一个。
  2. 如权利要求1所述的方法，其特征在于，终端确定需要承载的业务满足资源调度的触发条件，包括：
    所述终端在数据缓存量为空且有所述业务的新数据到达时，确定满足资源调度请求的触发条件；或
    所述终端承载在优先级指示满足预设条件的信道或切片或IP流上的所述业务的数据到达时，确定满足资源调度请求的触发条件；或
    所述终端确定所述业务中承载在优先级指示满足预设条件的信道或切片或IP流上的业务的业务数据量大于预设的第一门限时，确定满足资源调度请求的触发条件；或
    所述终端确定所述业务的业务数据量大于预设的第二门限时，确定满足资源调度请求的触发条件；或
    所述终端确定所述业务中的免调度业务的业务数据量大于预设的第三门限时，确定满足资源调度请求的触发条件；或
    所述终端确定所述业务中的基于调度的业务的数据缓存量大于预设的第三门限时，确定满足资源调度请求的触发条件；或
    所述终端确定所述业务中免调度业务的发送失败次数大于预设的第四门限时，确定满足资源调度请求的触发条件。
  3. 如权利要求1所述的方法，其特征在于，所述半静态资源请求中包括用于指示基站分配半静态资源的业务承载信息或半静态资源请求指示。
  4. 如权利要求1所述的方法，其特征在于，所述免调度发送指示包括用于指示所述终端进行免调度发送的资源信息。
  5. 如权利要求1所述的方法，其特征在于，终端确定需要承载的业务满足资源调度请求发送的触发条件之前，所述方法还包括：
    所述终端确定所述业务的数据承载在预先约定的逻辑信道或指定的切片或指定的IP流；或
    所述终端确定所述业务的数据承载在网络侧配置的逻辑信道或指定的切片或指定的IP流。
  6. 一种资源调度方法，其特征在于，包括：
    基站接收终端发送的资源调度请求，所述资源调度请求用于请求基站为所述终端分配上行资源，所述资源调度请求中包括所述业务的优先级指示、免调度发送指示、免调度发送失败指示、半静态资源请求和数据缓存量指示中至少一个；
    所述基站基于所述资源调度请求为所述终端分配上行资源。
  7. 如权利要求6所述的方法，其特征在于，所述半静态资源请求中包括用于指示基 站分配半静态资源的业务承载信息或半静态资源请求指示。
  8. 如权利要求6所述的方法，其特征在于，所述基站基于所述资源调度请求为所述终端分配上行资源，包括：
    所述基站基于所述资源调度请求中的免调度发送指示或免调度发送失败指示或数据缓存量指示，为所述终端分配相应的上行授权；
    所述基站基于所述资源调度请求中的优先级指示，确定所述上行授权的时延。
  9. 如权利要求7所述的方法，其特征在于，所述基站基于所述资源调度请求为所述终端分配上行资源，包括：
    所述基站确定所述资源调度请求中的业务承载信息满足预设条件时，为所述终端分配半静态资源；或
    所述基站确定所述资源调度请求中包括指示基站分配半静态资源的半静态资源请求指示时，为所述终端分配半静态资源。
  10. 如权利要求8所述的方法，其特征在于，所述基站为所述终端分配半静态资源之后，所述方法还包括：
    所述基站检测到所述终端业务承载信息不满足预设条件时，所述基站主动释放所述半静态资源或通知所述终端释放所述半静态资源。
  11. 一种资源调度装置，应用于终端，其特征在于，包括：
    处理单元，用于确定需要承载的业务满足资源调度请求发送的触发条件；
    发送单元，用于向基站发送资源调度请求，所述资源调度请求用于请求基站为所述终端分配上行资源，所述资源调度请求中包括所述业务的优先级指示、免调度发送指示、免调度发送失败指示、半静态资源请求和数据缓存量指示中的至少一个。
  12. 如权利要求11所述的装置，其特征在于，所述处理单元在确定需要承载的业务满足资源调度的触发条件时，具体用于：
    在数据缓存量为空且有所述业务的新数据到达时，确定满足资源调度请求的触发条件；或
    承载在优先级指示满足预设条件的信道或切片或IP流上的所述业务的数据到达时，确定满足资源调度请求的触发条件；或
    确定所述业务中承载在优先级指示满足预设条件的信道或切片或IP流上的业务的业务数据量大于预设的第一门限时，确定满足资源调度请求的触发条件；或
    确定所述业务的业务数据量大于预设的第二门限时，确定满足资源调度请求的触发条件；或
    确定所述业务中的免调度业务的业务数据量大于预设的第三门限时，确定满足资源调度请求的触发条件；或
    确定所述业务中的基于调度的业务的数据缓存量大于预设的第三门限时，确定满足资源调度请求的触发条件；或
    确定所述业务中免调度业务的发送失败次数大于预设的第四门限时，确定满足资源调度请求的触发条件。
  13. 如权利要求11所述的装置，其特征在于，所述半静态资源请求中包括用于指示基站分配半静态资源的业务承载信息或半静态资源请求指示。
  14. 如权利要求11所述的装置，其特征在于，所述免调度发送指示包括用于指示所 述终端进行免调度发送的资源信息。
  15. 如权利要求11所述的装置，其特征在于，所述处理单元，还用于：
    在确定需要承载的业务满足资源调度请求发送的触发条件之前，确定所述业务的数据承载在预先约定的逻辑信道或指定的切片或指定的IP流；或
    确定所述业务的数据承载在网络侧配置的逻辑信道或指定的切片或指定的IP流。
  16. 一种资源调度装置，其特征在于，包括：
    接收单元，用于接收终端发送的资源调度请求，所述资源调度请求用于请求基站为所述终端分配上行资源，所述资源调度请求中包括所述业务的优先级指示、免调度发送指示、免调度发送失败指示、半静态资源请求和数据缓存量指示中至少一个；
    处理单元，用于基于所述资源调度请求为所述终端分配上行资源。
  17. 如权利要求16所述的装置，其特征在于，所述半静态资源请求中包括用于指示基站分配半静态资源的业务承载信息或半静态资源请求指示。
  18. 如权利要求16所述的装置，其特征在于，所述处理单元在基于所述资源调度请求为所述终端分配上行资源时，具体用于：
    基于所述资源调度请求中的免调度发送指示或免调度发送失败指示或数据缓存量指示，为所述终端分配相应的上行授权；
    基于所述资源调度请求中的优先级指示，确定所述上行授权的时延。
  19. 如权利要求17所述的装置，其特征在于，所述处理单元在基于所述资源调度请求为所述终端分配上行资源时，具体用于：
    确定所述资源调度请求中的业务承载信息满足预设条件时，为所述终端分配半静态资源；或
    确定所述资源调度请求中包括指示基站分配半静态资源的半静态资源请求指示时，为所述终端分配半静态资源。
  20. 如权利要求18所述的装置，其特征在于，所述处理单元，还用于：
    为所述终端分配半静态资源之后，检测到所述终端业务承载信息不满足预设条件时，所述基站主动释放所述半静态资源或通知所述终端释放所述半静态资源。
PCT/CN2017/085524 2016-08-11 2017-05-23 一种资源调度方法和装置 Ceased WO2018028269A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP17838401.2A EP3471484A4 (en) 2016-08-11 2017-05-23 RESOURCE PLANNING PROCESS AND DEVICE
US16/252,534 US20190159236A1 (en) 2016-08-11 2019-01-18 Resource scheduling method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610665452.0 2016-08-11
CN201610665452.0A CN107734703B (zh) 2016-08-11 2016-08-11 一种资源调度方法和装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/252,534 Continuation US20190159236A1 (en) 2016-08-11 2019-01-18 Resource scheduling method and apparatus

Publications (1)

Publication Number Publication Date
WO2018028269A1 true WO2018028269A1 (zh) 2018-02-15

Family

ID=61161624

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/085524 Ceased WO2018028269A1 (zh) 2016-08-11 2017-05-23 一种资源调度方法和装置

Country Status (4)

Country Link
US (1) US20190159236A1 (zh)
EP (1) EP3471484A4 (zh)
CN (1) CN107734703B (zh)
WO (1) WO2018028269A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020064220A1 (en) * 2018-09-27 2020-04-02 Sony Corporation Communications device, infrastructure equipment and methods
CN113490281A (zh) * 2021-07-20 2021-10-08 上海中兴易联通讯股份有限公司 一种用于5g nr系统调度优化的方法和装置
US12025601B2 (en) 2020-10-28 2024-07-02 Freshair Sensor Llc Integrated monitoring and analysis systems and methods

Families Citing this family (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3769577B1 (en) * 2018-03-20 2025-02-26 Nokia Technologies OY Determining the mbb ue to puncture to accommodate urllc traffic
CN111373808A (zh) * 2018-05-10 2020-07-03 Oppo广东移动通信有限公司 通信方法和终端设备
CN110557839A (zh) * 2018-05-30 2019-12-10 中国移动通信有限公司研究院 调度请求的处理方法、配置方法、终端及网络侧设备
CN110636533B (zh) * 2018-06-21 2021-05-18 维沃移动通信有限公司 一种调度传输方法及终端
CN110536426B (zh) * 2018-08-10 2023-04-07 中兴通讯股份有限公司 一种信息指示方法、装置及计算机可读存储介质
CN110933742B (zh) * 2018-09-20 2021-08-13 华为技术有限公司 调度方法、设备与计算机可读存储介质
CN111182628B (zh) * 2018-11-09 2023-05-12 中国移动通信有限公司研究院 一种资源调度方法及装置、设备、存储介质
KR102815879B1 (ko) * 2019-03-28 2025-06-02 주식회사 아이티엘 무선통신 시스템에서 복수 개의 사전 구성 자원을 지원하는 방법 및 장치
US12238580B2 (en) * 2019-06-19 2025-02-25 Qualcomm Incorporated System and method for flow control and acknowledgement transmission
EP4498749A3 (en) * 2019-11-07 2025-04-16 ZTE Corporation System and method for power efficient establishment of uplink and downlink communications in wireless communication networks
CN112996115B (zh) * 2019-12-18 2023-04-07 大唐移动通信设备有限公司 一种上行资源分配的方法及装置
US11696305B2 (en) * 2020-06-18 2023-07-04 Qualcomm Incorporated Scheduling uplink transmissions using relay devices
CN112272108B (zh) * 2020-10-14 2022-09-27 中国联合网络通信集团有限公司 一种调度方法和装置
CN112333826B (zh) * 2020-11-05 2023-08-11 中国联合网络通信集团有限公司 一种业务接纳方法及装置
CN114641060A (zh) * 2020-12-15 2022-06-17 中国联合网络通信集团有限公司 时钟同步方法、装置、系统及存储介质
WO2022151213A1 (zh) * 2021-01-14 2022-07-21 捷开通讯(深圳)有限公司 一种上行传输方法、通信设备及可读存储介质
CN113316230B (zh) * 2021-05-07 2022-07-19 浙江大华技术股份有限公司 一种发送数据任务调度方法、装置、电子设备及存储介质
CN113453235B (zh) * 2021-06-09 2022-11-22 中国联合网络通信集团有限公司 无线资源的分配方法及装置
CN113260067B (zh) * 2021-07-07 2021-09-28 深圳市光联世纪信息科技有限公司 基于sd-wan的服务级别协议sla的业务承载方法、系统及设备
CN114501396B (zh) * 2022-03-28 2022-10-14 深圳市科思科技股份有限公司 数据传输方法、装置及设备
WO2024064169A1 (en) * 2022-09-23 2024-03-28 Apple Inc. Resource allocation for low latency wireless communication

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101695194A (zh) * 2009-10-22 2010-04-14 普天信息技术研究院有限公司 一种lte系统半静态调度中上行逻辑信道的复用方法
CN101873704A (zh) * 2009-04-24 2010-10-27 大唐移动通信设备有限公司 长期演进系统中资源调度方法、系统及设备
CN102036404A (zh) * 2010-12-24 2011-04-27 华为技术有限公司 一种数据发送方法和用户设备
EP2667674A1 (en) * 2011-01-20 2013-11-27 Huawei Technologies Co., Ltd. Method, user equipment and communication system for processing resource requests

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE602004012862T2 (de) * 2004-10-01 2009-04-09 Matsushita Electric Industrial Co., Ltd., Kadoma-shi Dienstgüte-bewusste Ablaufsteuerung für Aufwärtsübertragungen über zugeordneten Kanälen
KR101367476B1 (ko) * 2007-08-13 2014-02-25 엘지전자 주식회사 무선통신 시스템에서 데이터 수신방법
ES2553410T3 (es) * 2007-08-13 2015-12-09 Optis Cellular Technology, Llc Procedimiento para transmitir paquetes de tipo VoIP
EP3104653B1 (en) * 2011-09-30 2018-03-14 Nokia Solutions and Networks Oy Packet scheduling in communications
EP2888906B1 (en) * 2012-08-23 2021-03-31 Interdigital Patent Holdings, Inc. Operating with multiple schedulers in a wireless system
US10028302B2 (en) * 2013-03-08 2018-07-17 Huawei Technologies Co., Ltd. System and method for uplink grant-free transmission scheme
EP3048847B1 (en) * 2015-01-26 2019-11-20 Panasonic Intellectual Property Corporation of America Improved scheduling request procedure
JP6783755B2 (ja) * 2015-05-15 2020-11-11 京セラ株式会社 無線端末、基地局、及びプロセッサ
CN105188150B (zh) * 2015-08-12 2019-06-18 中国电子科技集团公司第七研究所 降低lte上行数据传输延时的方法和系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101873704A (zh) * 2009-04-24 2010-10-27 大唐移动通信设备有限公司 长期演进系统中资源调度方法、系统及设备
CN101695194A (zh) * 2009-10-22 2010-04-14 普天信息技术研究院有限公司 一种lte系统半静态调度中上行逻辑信道的复用方法
CN102036404A (zh) * 2010-12-24 2011-04-27 华为技术有限公司 一种数据发送方法和用户设备
EP2667674A1 (en) * 2011-01-20 2013-11-27 Huawei Technologies Co., Ltd. Method, user equipment and communication system for processing resource requests

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3471484A4 *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020064220A1 (en) * 2018-09-27 2020-04-02 Sony Corporation Communications device, infrastructure equipment and methods
CN112640352A (zh) * 2018-09-27 2021-04-09 索尼公司 通信装置、基础设施设备和方法
US11991119B2 (en) 2018-09-27 2024-05-21 Sony Corporation Communications device, infrastructure equipment and methods
CN112640352B (zh) * 2018-09-27 2024-11-26 索尼公司 通信装置、基础设施设备和方法
US12025601B2 (en) 2020-10-28 2024-07-02 Freshair Sensor Llc Integrated monitoring and analysis systems and methods
CN113490281A (zh) * 2021-07-20 2021-10-08 上海中兴易联通讯股份有限公司 一种用于5g nr系统调度优化的方法和装置

Also Published As

Publication number Publication date
CN107734703A (zh) 2018-02-23
US20190159236A1 (en) 2019-05-23
CN107734703B (zh) 2020-11-17
EP3471484A1 (en) 2019-04-17
EP3471484A4 (en) 2019-05-22

Similar Documents

Publication Publication Date Title
CN107734703B (zh) 一种资源调度方法和装置
KR102270541B1 (ko) 무선 통신 시스템에서 통신 방법 및 장치
CN108781465B (zh) 信道接入优先级类别选择
EP3324566B1 (en) Electronic equipment in wireless communication system
US10098122B2 (en) System and method for resource allocation for device-to-device communications
CN108292980B (zh) 业务传输的方法和装置
CN111034318B (zh) 与无线通信网络中的缓冲区状态报告相关的方法和装置
US10764881B2 (en) Resource management method and related device
CN114342535B (zh) 上行信号的发送和接收方法以及装置
WO2019157945A1 (zh) 一种用于上行授权的方法及装置
CN108370589A (zh) 用于分布式非调度传输的网络辅助
CN108347784A (zh) 一种资源调度方法以及无线接入网设备和终端设备
CN106992846A (zh) 一种数据发送方法、数据接收方法和装置
WO2018141244A1 (zh) 一种资源调度方法、装置及系统
CN114073159A (zh) 信号发送和接收方法以及装置
WO2019028792A1 (zh) 一种配置资源的方法及设备
JP2023514730A (ja) フィードバックリソース決定方法およびフィードバックリソース決定装置
CN114073157A (zh) 信道接入优先级的选择
EP4418786A1 (en) Data transmission method and communication device
CN107534984A (zh) 一种分量载波组的配置方法及设备
WO2023138622A1 (zh) 资源配置方法与装置、网络设备和终端设备
WO2021026841A1 (zh) 调度请求传输的方法和设备
JP7544828B2 (ja) 情報処理方法及び装置
WO2023070375A1 (zh) 资源指示的方法、终端设备和网络设备
US20230353292A1 (en) Wireless communication method and device

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2017838401

Country of ref document: EP

Effective date: 20190114

NENP Non-entry into the national phase

Ref country code: DE