[go: up one dir, main page]

WO2018202087A1 - 上行传输资源的调度方法和设备 - Google Patents

上行传输资源的调度方法和设备 Download PDF

Info

Publication number
WO2018202087A1
WO2018202087A1 PCT/CN2018/085482 CN2018085482W WO2018202087A1 WO 2018202087 A1 WO2018202087 A1 WO 2018202087A1 CN 2018085482 W CN2018085482 W CN 2018085482W WO 2018202087 A1 WO2018202087 A1 WO 2018202087A1
Authority
WO
WIPO (PCT)
Prior art keywords
scheduling request
uplink
scheduling
terminal device
type
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2018/085482
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 EP18795055.5A priority Critical patent/EP3614776B1/en
Publication of WO2018202087A1 publication Critical patent/WO2018202087A1/zh
Priority to US16/671,768 priority patent/US11606803B2/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/1221—Wireless traffic scheduling based on age of data to be sent
    • 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
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0278—Traffic management, e.g. flow control or congestion control using buffer status reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/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/535—Allocation or scheduling criteria for wireless resources based on resource usage policies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols
    • 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

Definitions

  • the present application relates to communications technologies, and in particular, to a method and a device for scheduling uplink transmission resources.
  • the uplink scheduling process can be generally divided into the following five steps: scheduling request (SR) sending, and evolved Node B (eNB) allocating uplink resources (Uplink Grant, The UL Grant sends a Buffer State Report (BSR), the terminal transmits a BSR on the resource, the eNB allocates a UL Grant to transmit uplink data, and the terminal transmits uplink data on the resource.
  • SR scheduling request
  • eNB evolved Node B
  • BSR Buffer State Report
  • the terminal transmits a BSR on the resource
  • the eNB allocates a UL Grant to transmit uplink data
  • the terminal transmits uplink data on the resource.
  • the user equipment User Equipment, UE
  • the regular BSR-regular BSR when the BSR trigger condition is met.
  • the logicalChannel-SR-ProhibitTimer does not.
  • the SR is triggered, and the physical layer is sent to send an SR on the available Physical Uplink Control Channel (PUCCH) resource, and the UE sends an SR (1 bit) on the available PUCCH resource, to inform the eNB that the UE has data.
  • the eNB receives the SR sent by the UE, and allocates the uplink resource to the UE to send the BSR. After receiving the allocated uplink resource, the UE sends the BSR to the corresponding resource to inform the eNB.
  • the eNB allocates the resources required for transmitting the uplink data according to the BSR and the eNB's own scheduling algorithm. After receiving the allocated uplink resources, the eNB sends the uplink data on the corresponding resource. To achieve the transmission of uplink data.
  • 5G fifth-generation mobile communication
  • eMBB enhanced mobile broadband
  • mMTC massive machine type communication
  • URLLC Latency Communications
  • sr-prohibitTimer is used to limit the interval between consecutive SR transmissions. During the timer running time, other SRs cannot be sent, resulting in a longer resource scheduling delay. Therefore, the uplink resource scheduling mode in LTE cannot meet the requirements of the 5G network.
  • An embodiment of the present application provides a method and a device for scheduling an uplink transmission resource, which are used to solve the problem that an uplink resource scheduling manner in LTE cannot meet the requirements of a 5G network.
  • a first aspect of the embodiments of the present application provides a method for scheduling an uplink transmission resource, where the method includes:
  • the first scheduling request is determined according to the first indication information that is acquired in advance; the first indication information is used to indicate the type of the logical channel and the scheduling request. Corresponding relationship; the first scheduling request includes a first scheduling request type for indicating uplink scheduling information required by the terminal device;
  • the method further includes:
  • the uplink data includes the first BSR, or the first BSR and data to be sent.
  • the method further includes:
  • the network device receives, by the access network device, the second uplink scheduling information, where the second uplink scheduling information is used to indicate that the access network device is configured to be used by the first BSR according to the terminal device
  • the network device sends the cached second uplink resource of the data to be sent
  • the access network device may also schedule, for the terminal device, the second data to be sent for sending the buffer according to the type of the scheduling request. Upstream resources.
  • the method is determined according to the first indication information that is acquired in advance. Also includes:
  • the first indication information further includes:
  • the sending, by the access network device, the first scheduling request includes:
  • the first logical channel is used to send high priority service data.
  • the duration of the scheduling request prohibition timer of the first logical channel is smaller than the duration of the scheduling request prohibition timer of the other logical channel.
  • the scheduling request prohibiting timer of the first logical channel has a duration of zero.
  • the scheduling request prohibiting timer corresponding to the terminal device is disabled when determining that the first BSR triggers the data to be sent in the first logical channel.
  • the method before the sending the first scheduling request to the access network device, the method further includes:
  • the scheduling request cancellation condition includes any one of the following conditions:
  • the first BSR is carried in a MAC PDU to be sent
  • the uplink resource that the access network device has allocated to the terminal device is sufficient to transmit all data to be sent;
  • the terminal device has received an uplink resource corresponding to the type of the first scheduling request that is allocated by the access network device;
  • the access network device configures the terminal device with an unlicensed uplink resource.
  • a second aspect of the embodiments of the present application provides a method for scheduling an uplink transmission resource, where the method includes:
  • the terminal device Receiving, by the terminal device, a first scheduling request, where the first scheduling request includes a first scheduling request type used to indicate uplink scheduling information required by the terminal device;
  • the method further includes:
  • the terminal device Receiving uplink data sent by the terminal device on the first uplink resource, where the uplink data includes a first BSR, or the first BSR and data.
  • the method further includes:
  • the access network device when the access network device receives the scheduling request that is sent by the terminal device multiple times, the access network device may also schedule, for the terminal device, the data to be sent for sending the buffer according to the type of the scheduling request.
  • the second uplink resource when the access network device receives the scheduling request that is sent by the terminal device multiple times, the access network device may also schedule, for the terminal device, the data to be sent for sending the buffer according to the type of the scheduling request.
  • the second uplink resource when the access network device receives the scheduling request that is sent by the terminal device multiple times, the access network device may also schedule, for the terminal device, the data to be sent for sending the buffer according to the type of the scheduling request.
  • the method before receiving the first scheduling request sent by the terminal device, the method further includes:
  • the first indication information includes:
  • determining the type of the first scheduling request includes:
  • Determining a type of the first scheduling request according to a correspondence between a PUCCH that receives the first scheduling request and a type of a pre-configured scheduling request and a PUCCH;
  • a third aspect of the embodiments of the present application provides a scheduling device for uplink transmission resources, where the device may be a terminal device or a chip in the terminal device.
  • the apparatus can include a processing unit and a transceiver unit.
  • the processing unit may be a processor
  • the transceiver unit may be a transceiver
  • the terminal device may further include a storage unit, the storage unit may be a memory; the storage unit is configured to store an instruction, the processing The unit executes the instructions stored by the storage unit, so that the terminal device performs the scheduling method of the uplink transmission resource provided by the first aspect or the various embodiments of the first aspect.
  • the processing unit may be a processor, the transceiver unit may be an input/output interface, a pin or a circuit, etc.; the processing unit executes instructions stored by the storage unit to make the terminal
  • the device performs the scheduling method of the uplink transmission resource provided by the first aspect or the various implementation manners of the first aspect, where the storage unit may be a storage unit (for example, a register, a cache, etc.) in the chip, or may be in the terminal device.
  • a memory unit for example, a read only memory, a random access memory, etc. located outside the chip.
  • a fourth aspect of the embodiments of the present disclosure provides a scheduling device for uplink transmission resources, where the device may be a network device or a chip in the network device.
  • the apparatus can include a processing unit and a transceiver unit.
  • the processing unit may be a processor, and the transceiver unit may be a transceiver;
  • the network device may further include a storage unit, the storage unit may be a memory; the storage unit is configured to store an instruction, the processing The unit executes the instructions stored by the storage unit, so that the network device performs the scheduling method of the uplink transmission resource provided by the second aspect or the various embodiments of the second aspect.
  • the processing unit may be a processor, the transceiver unit may be an input/output interface, a pin or a circuit, etc.; the processing unit executes instructions stored by the storage unit to make the network
  • the apparatus performs the scheduling method of the uplink transmission resource provided by the second aspect or the various implementation manners of the second aspect, where the storage unit may be a storage unit (for example, a register, a cache, etc.) in the chip, or may be in the network device.
  • a memory unit for example, a read only memory, a random access memory, etc. located outside the chip.
  • a fifth aspect of the embodiments of the present application provides a scheduling apparatus for an uplink transmission resource, where the apparatus includes a processor and a storage medium, where the storage medium stores an instruction, when the instruction is executed by the processor, causing the processor to perform the first aspect Or the scheduling method of the uplink transmission resource provided by the various implementation manners of the first aspect.
  • the device can be a chip or chip system.
  • a sixth aspect of the embodiments of the present application provides a scheduling apparatus for an uplink transmission resource, where the apparatus includes a processor and a storage medium, where the storage medium stores an instruction, when the instruction is executed by the processor, causing the processor to perform the second aspect.
  • the scheduling method of the uplink transmission resource provided by the various implementation manners of the second aspect.
  • the device can be a chip or chip system.
  • a seventh aspect of the embodiments of the present application provides a computer storage medium storing computer executable instructions that, when invoked by a computer, cause the computer to perform various aspects of the first aspect or the first aspect The scheduling method of the uplink transmission resource provided by the embodiment.
  • An eighth aspect of the embodiments of the present application provides a computer storage medium storing computer executable instructions that, when invoked by a computer, cause the computer to perform various aspects of the second aspect or the second aspect The scheduling method of the uplink transmission resource provided by the embodiment.
  • a ninth aspect of the embodiments of the present application provides a program product, the program product comprising a computer program (ie, an execution instruction) stored in a readable storage medium.
  • a computer program ie, an execution instruction
  • At least one processor of the terminal device can read the computer program from a readable storage medium, and the at least one processor executes the computer program to cause the terminal device to implement scheduling of uplink transmission resources provided by the first aspect or various embodiments of the first aspect method.
  • a tenth aspect of the embodiments of the present application provides a program product, the program product comprising a computer program (ie, an execution instruction) stored in a readable storage medium.
  • At least one processor of the access network device can read the computer program from a readable storage medium, the at least one processor executing the computer program causing the access network device to implement the second aspect or the various embodiments of the second aspect A scheduling method for uplink transmission resources.
  • the method and device for scheduling an uplink transmission resource provided by the embodiment of the present disclosure, when the first logical channel of the terminal device has a data to be sent, and the first BSR is triggered, the terminal device determines the first scheduling request according to the first indication information that is acquired in advance.
  • the first indication information is used to indicate a correspondence between the logical channel and the type of the scheduling request, where the first scheduling request includes a first scheduling request type, the terminal device sends a first scheduling request to the access network device, and the terminal device receives the access network.
  • the first uplink scheduling information sent by the device where the uplink scheduling information is used to indicate a first uplink resource used by the terminal device to send uplink data to the access network device.
  • the access network device can distinguish the scheduling request of the service according to the type of the scheduling request, and quickly and reasonably allocate resources for the terminal device.
  • FIG. 1 is a schematic diagram of an application scenario of an uplink transmission resource scheduling method according to an embodiment of the present disclosure
  • FIG. 2 is an interaction flowchart of Embodiment 1 of an uplink transmission resource scheduling method according to an embodiment of the present disclosure
  • FIG. 3 is an interaction flowchart of Embodiment 2 of an uplink transmission resource scheduling method according to an embodiment of the present disclosure
  • FIG. 4 is an interaction flowchart of an example of a method for scheduling an uplink transmission resource according to an embodiment of the present disclosure
  • Figure 5a is a schematic diagram of a BSR format
  • Figure 5b is a schematic diagram of another BSR format
  • FIG. 6 is a schematic structural diagram of Embodiment 1 of a terminal device according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic structural diagram of Embodiment 1 of an access network device according to an embodiment of the present disclosure.
  • the technical solution of the embodiment of the present application can be applied to a 5G communication system or a future communication system, and can also be used in other various wireless communication systems, such as a Global System of Mobile communication (GSM) system, and code division multiple access (CDMA, Code Division Multiple Access system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency division duplex (Freq terminal equipment ncy Division Duplex, FDD) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), and the like.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • LTE Frequency division duplex Frequency division duplex
  • TDD Time Division Duplex
  • UMTS Universal Mobile Telecommunication System
  • FIG. 1 is a schematic diagram of an application scenario of an uplink transmission resource scheduling method according to an embodiment of the present disclosure.
  • an application scenario of the uplink transmission resource scheduling method is applied to a base station and a user equipment (User Equipment)
  • the base station When the base station performs resource scheduling for the UE, the UE may perform scheduling according to the scheme.
  • the base station functions as an access network device and the UE serves as a terminal device.
  • the access network device may also be a base station (Base Transceiver Station, BTS for short) in Global System of Mobile communication (GSM) or Code Division Multiple Access (CDMA).
  • BTS Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • the terminal device may be a wireless terminal or a wired terminal, and the wireless terminal may be a device that provides voice and/or other service data connectivity to the user, a handheld device with wireless connectivity, or other processing device connected to the wireless modem.
  • the wireless terminal can communicate with one or more core networks via a Radio Access Network (RAN), which can be a mobile terminal, such as a mobile phone (or "cellular" phone) and a mobile terminal.
  • RAN Radio Access Network
  • the computer for example, can be a portable, pocket, handheld, computer built-in or in-vehicle mobile device that exchanges language and/or data with the wireless access network.
  • the wireless terminal may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, and a remote terminal.
  • the access terminal, the user terminal (User Terminal), the user agent (User Agent), and the user device (User Device or User Equipment) are not limited herein.
  • FIG. 2 is an interaction flowchart of Embodiment 1 of an uplink transmission resource scheduling method according to an embodiment of the present disclosure. As shown in FIG. 2, the specific implementation steps of the uplink transmission resource scheduling method are as follows:
  • the terminal device determines the first scheduling request according to the first indication information that is acquired in advance.
  • the first indication information is used to indicate a correspondence between the logical channel and the type of the scheduling request; the first scheduling request includes a first scheduling request type for indicating uplink scheduling information required by the terminal device.
  • the terminal device may obtain the relationship between the logical channel and the type of the scheduling request according to the configuration of the access network device or the negotiation with the device side of the access network, or by the provisions in the protocol, and the solution is not limited. .
  • the BSR may be triggered, that is, the first BSR, where the terminal device needs to send a scheduling request to the access network device, so that the access network device schedules the terminal device. Send the resources of the BSR.
  • the terminal device first needs to determine the type of the scheduling request to be sent according to the obtained first indication information and the logical channel of the data buffer. In a specific implementation manner, the type of the scheduling request may be carried in the scheduling request.
  • the method further includes: receiving, by the terminal device, the first indication information sent by the access network device. That is, the first indication information is obtained by the notification of the access network device.
  • S102 The terminal device sends a first scheduling request to the access network device.
  • the terminal device needs to send the first scheduling request to the corresponding resource configured by the access network device, if not Configuration, the terminal device can instruct the lower layer to send directly on the available resources.
  • the access network device receives the first scheduling request sent by the terminal device, and then allocates resources to the terminal device according to the first scheduling request.
  • the terminal device instructs the physical layer to send the first scheduling request to the access network device on a physical uplink control channel (PUCCH) corresponding to the type of the first scheduling request.
  • PUCCH physical uplink control channel
  • the terminal device instructs the physical layer to send the first scheduling request to the access network device on an available PUCCH.
  • the access network device determines a type of the first scheduling request, and schedules, by the terminal device, a first uplink resource for sending uplink data according to the type of the first scheduling request.
  • the access network device can directly allocate resources according to the type of the first scheduling request carried in the first scheduling request, and at least determine the type of the first scheduling request in the following manners:
  • the access network device determines the type of the first scheduling request according to the correspondence between the PUCCH that receives the first scheduling request and the type of the pre-configured scheduling request and the PUCCH.
  • the access network device can determine the type of the first scheduling request by using the received PUCCH channel.
  • the access network device determines the type of the first scheduling request according to the quantity of the first scheduling request received within the preset duration.
  • the scheduling request of different service priorities can be sent in different frequencies or in different numbers. Therefore, the access network device can also determine the type according to the number of scheduling requests received within the preset duration.
  • the access network device may adopt different scheduling modes and allocate corresponding resources for different types of scheduling requests. For example, for a scheduling request with a higher priority, the uplink resource may be separately scheduled. Or, the processing time can be shortened, that is, the resources are preferentially allocated to the scheduling request with high priority and quickly delivered to the terminal device.
  • the terminal device receives the first uplink scheduling information sent by the access network device, where the uplink scheduling information is used to indicate the first uplink resource used by the terminal device to send uplink data to the access network device.
  • the access network device sends the first uplink scheduling information to the terminal device, where the first uplink scheduling information is used to indicate the first uplink resource.
  • the access network device may notify the terminal device of the allocated uplink resource, and the specific notification mode may be carried in the downlink information, or may specifically send the first uplink scheduling request indicating the resource, This program does not limit.
  • the terminal device determines the first scheduling request according to the first indication information acquired in advance, and accesses the access
  • the network device sends a first scheduling request carrying the type information, and the access network device allocates an uplink resource to the terminal device according to the type of the scheduling request, and notifies the terminal device to send the information to the access network device according to the correspondence between the logical channel and the type.
  • the scheduling request carries the type of the scheduling request, and the access network device can distinguish the scheduling request of the service according to the type of the scheduling request, and quickly and reasonably allocate resources for the terminal device.
  • the first indication information sent by the access network device to the terminal device further includes, but is not limited to, at least one of the following:
  • the data that needs to be transmitted to the terminal device has certain attribute information, and the data of the same service group has the same or similar attributes, which may be the service type and the service quality requirement of the service, such as transmission delay and reliability.
  • the terminal device In order for the terminal device to be able to determine the priority of the service or the priority of the logical channel or the logical channel according to the plurality, and then obtain the type of the first scheduling request according to the corresponding relationship described above.
  • the first logical channel is configured to send high priority service data.
  • the type of the scheduling request may be determined according to the service priority.
  • the duration of the scheduling request prohibition timer of the first logical channel may be configured to be smaller than the duration of the scheduling request prohibit timer of the other logical channel.
  • the duration of the scheduling request prohibition timer of the first logical channel may be configured to be zero, so that the first scheduling request can be quickly sent to the access network device.
  • the scheduling request prohibiting timer corresponding to the terminal device determines that the first BSR is triggered to be sent by the first logical channel.
  • the de-enable indication may be the indication information of the first logical channel sent by the access network device to enable the scheduling request prohibition timer; or may be specified in the protocol, and the solution is not limited.
  • FIG. 3 is an interaction flowchart of Embodiment 2 of an uplink transmission resource scheduling method according to an embodiment of the present disclosure. As shown in FIG. 3, on the basis of the foregoing Embodiment 1, after step S104, the following steps may be further included:
  • the terminal device sends uplink data on the first uplink resource.
  • the uplink data includes the first BSR, or the first BSR and the to-be-sent data.
  • the terminal device may perform data transmission on the first uplink resource, that is, the first BSR on the first uplink resource. Send to the access network device.
  • the first BSR and the buffered uplink data may be sent on the first uplink resource at the same time, and the solution is not limited.
  • the access network device schedules, according to the first BSR, a second uplink resource for uploading data for the terminal device.
  • the access network device may further schedule, for the terminal device, the second data for transmitting the data according to the type of the scheduling request.
  • Upstream resources there is no limit to this solution.
  • the access network device sends the second uplink scheduling information to the terminal device, where the second uplink scheduling information is used to indicate the second uplink resource.
  • the second uplink scheduling information is used to indicate that the access network device sends the cache to the access network device according to the type of the first BSR or the first scheduling request configured for the terminal device.
  • the second uplink resource of the data to be sent is used to indicate that the access network device sends the cache to the access network device according to the type of the first BSR or the first scheduling request configured for the terminal device.
  • S108 The terminal device sends the to-be-sent data on the second uplink resource.
  • the access network device After receiving the first BSR sent by the terminal device, the access network device schedules, according to the BSR, a second uplink resource for transmitting data, and notifies the terminal device, so that the terminal device is in the Sending data to be sent on the second uplink resource.
  • the pending scheduling request may be canceled when any of the following conditions are met:
  • the first BSR is carried in one or more Media Access Control Protocol Data Units (MAC PDUs) to be transmitted.
  • MAC PDUs Media Access Control Protocol Data Units
  • Condition 2 The uplink resource that the access network device has allocated to the terminal device is sufficient to transmit all data to be sent.
  • Condition 3 The terminal device has received an uplink resource corresponding to the type of the first scheduling request that is allocated by the access network device.
  • Condition 4 The access network device configures the terminal device with an unlicensed uplink resource.
  • the method for scheduling an uplink transmission resource provided by the foregoing embodiment, the first indication information sent by the access network device to the terminal device, indicating a correspondence between the logical channel and the type of the scheduling request, so that the terminal device reaches the data on the logical channel.
  • the type of the scheduling request is determined, and the scheduling request of the carrying type is sent to the access network device, so that the access network device can distinguish the service type or the priority according to the type of the received scheduling request, and implement fast and reasonable Resource allocation.
  • the access network device is a base station (eNB), and the terminal device is a UE, and the uplink transmission resource scheduling method provided by the embodiment of the present application is provided. Detailed instructions are given.
  • FIG. 4 is an interaction flowchart of an example of an uplink transmission resource scheduling method according to an embodiment of the present disclosure. As shown in FIG. 4, in a specific implementation manner, the uplink resource scheduling method specifically includes the following steps:
  • S201 Send configuration information of the LCH to the UE.
  • the eNB sends configuration information (corresponding to the foregoing first indication information) of a logical channel (LCH) to the UE, where the configuration information of the LCH includes a logical channel (or a logical channel group) and a resource usage attribute ( The numerology), the Scheduling Request (SR) parameter setting, and the BSR parameter configuration; can be notified by means of radio resource control (RRC)/MAC, etc.;
  • RRC radio resource control
  • the SR parameter configuration may include a correspondence between an SR trigger type and a numerology/Transmission Time Interval (TTI), or a correspondence with a service priority or a correspondence with a logical channel priority.
  • TTI Transmission Time Interval
  • the SR parameter configuration may further include an SR related timer, such as a timer that restricts the SR transmission, that is, an sr-ProhibitTimer, or a timer that limits the SR trigger, that is, a logicalChannelSR-ProhibitTimer.
  • an SR related timer such as a timer that restricts the SR transmission, that is, an sr-ProhibitTimer, or a timer that limits the SR trigger, that is, a logicalChannelSR-ProhibitTimer.
  • the SR parameter configuration may further include configuring a LCH to have a fast triggering SR function; that is, when some new SR triggering cases are met, a fast SR triggering may be implemented.
  • the BSR parameter configuration includes: a BSR-related timer, and a correspondence between a logical channel or a logical channel group and a numerology in a BSR reporting process.
  • the UE triggers the BSR, and triggers and determines the SR type according to the SR triggering mechanism and parameters configured by the LCH, and instructs the physical layer to send the SR.
  • the regular BSR when there is data arriving and the regular BSR trigger condition is met, the regular BSR can be triggered; once it is triggered by Ultra-Reliable and Low Latency Communications (URLLC) data (data) With the BSR, the SR can be triggered immediately.
  • URLLC Ultra-Reliable and Low Latency Communications
  • the UE is equipped with two sets of SR triggering mechanisms at the same time. It only needs to configure the LCH of the special function to perform fast triggering and instruct the physical layer to send the SR (this will involve some new trigger cases and short timer values; thus achieving fast triggering). When other logical channels are reported, they can be executed normally.
  • the UE there are two sets of SR triggering mechanisms at the same time to meet the requirements of the UE to send different services. Among them, one set of the two mechanisms is shared by all logical channels, and one set is separately configured for a certain logical channel. , when a logical channel is configured separately, the shared configuration can be ignored;
  • the configuration of the SR trigger enhancement mechanism corresponding to the RB or the logical channel is allocated (for example, the logical channelSR-ProhibitTimer of the per-UE configuration is ignored, or a new one is adopted. SR trigger mechanism, etc.);
  • the UE When the UE receives the RRC reconfiguration message, it first checks the logicalChannel-SR-Triggering-Enhancement-r15 configuration available for the current TTI:
  • the SR triggering enhancement is supported.
  • the logical channel is timely based on the logical channel. Triggering and instructing the physical layer to send the SR on the available PUCCH resources, thereby achieving the purpose of obtaining the UL grant as early as possible;
  • LCH-specific logicalChannelSR-ProhibitTimer For services with higher latency requirements, you can configure the LCH-specific logicalChannelSR-ProhibitTimer to set the timers of these LCHs to be smaller. (In particular, when 5G is introduced into numerologies with different durations of TTIs, for different LCHs, The processing capability is different, and the control capabilities such as timers can be set differently);
  • the BSR is triggered because the URLLC data is sent by the packet, and the logicalChannelSR-ProhibitTimer of the LCH is started.
  • the timer can be started or restarted. Here, only the startup, but not restarting, once the timer If it times out, it can trigger SR;
  • an indication to enable the logicalChannelSR-ProhibitTimer may be added to the LCH configuration, that is, the LCH triggering SR of the URLLC is not restricted by the timer;
  • an indication to enable the logicalChannelSR-ProhibitTimer may be added to the LCH configuration, that is, the LCH triggering the SR of the URLLC is not restricted by the timer; but the triggering of the SR introduces a new trigger case. , statistics due to URLLC business.
  • the method of dividing the SR type may include:
  • the type of business the degree of importance, such as the type of regular BSR triggered by different services
  • the priority of the logical channel is high or low
  • the eNB may configure a correspondence between the SR type and the triggered regular BSR type, or a logical channel or a logical channel group or a logical channel numerology/TTI, etc., and adopts RRC signaling or a MAC control unit (Control Element, CE). Informing the UE of the correspondence, the UE determining the SR type by using the correspondence relationship;
  • the regular BSR types triggered by the different services include:
  • Different BSRs are triggered by different BSR triggering mechanisms. Different BSR triggers are due to data sent in the LCH/LCG bound to the service; or
  • LCH/LCGs with different services are configured with different triggering mechanisms.
  • services that are sensitive to delay requirements such as URLLC
  • /LCG has the function of quickly triggering BSR; if this function is configured, the UE can quickly trigger the regular BSR when the following conditions are met:
  • the uplink buffer of the UE is empty and new data arrives. For example, the UE sends uplink data for the first time.
  • the retxBSR-Timer can be configured, the retxBSR-Timer times out, and any logical channel of any LCG of the UE has data to be transmitted, triggering "Regular" BSR", here, for services with higher latency requirements, RB-specific retxBSR-Timer can be configured (especially when 5G introduces numerologies with different durations of TTIs, the processing capability is different for different RBs, and timing can be Control and other settings are different);
  • the UE has sent the BSR. Before the retxBSR-Timer times out, the data bit or the number of data packets in the buffer reaches a certain threshold (both BSR trigger delay and unnecessary overhead, and the threshold is configured), then the "regular BSR" is triggered. ”
  • the UE has sent the BSR.
  • the data speed of the newly arrived buffer reaches a certain condition (according to the Data speed of the arriving buffer, the amount of data of the subsequent arriving buffer is pre-determined, and the UL is required in advance. Grant), triggers "regular BSR".
  • S203 The UE sends an SR to the eNB, where the SR carries the SR type information.
  • the UE may indicate a lower layer, for example, the physical layer sends an SR on the PUCCH resource.
  • the UE indicates the lower layer after determining the SR type, for example, the physical layer sends the SR on the PUCCH resource corresponding to the SR type;
  • the UE instructs the lower layer to send the SR on the available PUCCH resource, and on which PUCCH resource the SR is last sent, depending on the UE implementation.
  • the specific implementation of this step includes the sending of the SR and the carrying of the SR type information. Specifically:
  • the sr-prohibitTimer is started.
  • the timer is used to limit the interval of two consecutive SR transmissions. That is, during this timer running time, other SRs cannot be sent, but the timer It is a per-UE.
  • the SR is not required to wait for the timer to expire.
  • the UL grant acquisition delay is large, and the per-UE timer setting is unreasonable.
  • Option 1 Configure the UE-specific sr-ProhibitTimer, but the timer does not work for the high priority initiated by the URLLC data LCH.
  • Option 2 Configure the LCH-specific sr-ProhibitTimer. For the LCH/LCG bound to the URLLC data, set the timer to be small.
  • the manner in which the UE carries the SR type when transmitting the SR may include both display and implicit modes.
  • the multi-bit SR displays the indication.
  • the NR may extend the number of SR bits to carry the SR type information.
  • the BSR carried in the multi-bit SR may also be the BSR corresponding to the data to be sent by the UE, or the number of LCGs to be sent by the UE, thereby assisting the eNB to allocate resources for transmitting the BSR, and does not exclude other possible information.
  • the UE determines the SR type, and then sends the information on the corresponding PUCCH resource, and the eNB determines the SR type information by using the PUCCH resource location; for example, the high priority SR can only be on the short duration PUCCH. Send, while the low priority SR can only be sent on the long duration PUCCH.
  • the eNB does not configure the correspondence between the SR type and the PUCCH resource, that is, the PUCCH is transmitted on the different PUCCHs depending on the UE implementation.
  • the UE can distinguish the transmission modes of different SR types. After sending an SR, only The high priority SR triggers, the UE will instruct the lower layer to send, and the eNB recognizes the SR type by receiving the number of SRs.
  • the NR introduces numerology, does not exclude the numerology-specific PUCCH resources, and can limit the maximum SR transmission. The number does not exceed the number of PUCCH resource types.
  • the display + implicit combination is not excluded, that is, the SR sent in the implicit carrying mode is a multi-bit SR.
  • the eNB receives the SR sent by the UE, and determines the first uplink resource according to the SR.
  • the eNB receives and identifies different SR types, and adopts different scheduling modes and allocates corresponding resource types for different SR types, specifically:
  • the UL grant can be separately scheduled, so that after receiving the UL grant, the UE reduces the processing delay of the UE to the UL grant (reusing data of different logical channels).
  • the eNB processing time is reduced, and the UL grant is quickly delivered. For example, when the eNB receives the SR at time n, the eNB can feed back the UL grant at time n+4. For the high-priority SR, the UL grant can be delivered at time n+3.
  • the UL grant (the UL grant format is as shown in the following table) in the above two manners, the eNB may allocate different uplink resource sizes, MCSs, uplink powers, resource usage attributes, numerology/TTI indications, and the like according to different SR types.
  • the resource usage attribute includes a resource period (eg, a period of 1 ms, 2 ms, 5 ms, 1 TTI length, 2 TTI lengths, etc.), and a Transmission Time Interval (TTI) length (eg, 1 ms TTI).
  • a resource period eg, a period of 1 ms, 2 ms, 5 ms, 1 TTI length, 2 TTI lengths, etc.
  • TTI Transmission Time Interval
  • 0.5msTTI TTI length of two orthogonal sub-division modulation (OFDM) symbols, TTI length of one OFDM symbol, etc.
  • subcarrier spacing such as 15KHz, 60KHz, etc.
  • coding mode if used
  • LDPC Low-Density Parity-Check
  • Polarized Polar code etc.
  • multiple access methods such as OFDM, Code Division Multiple Access (Code Division Multiple Access) CDMA), etc., the number of carriers occupied in the frequency domain (such as 12 subcarriers, 15 subcarriers, etc.), whether to perform repeated transmission in the frequency domain (if it also includes the number of repeated transmissions in the frequency domain), whether to perform time domain repeat transmission ( If so, it also includes at least one of the number of times of repeated transmissions in the time domain.
  • the base station processes the SRs as follows:
  • Option 1 The eNB returns the same UL grant resource for multiple SRs of the same UE, and adds indication information to the UL grant.
  • the UE can learn that the eNB allocates the same UL resource according to the indication information.
  • Option 2 The eNB replies with different UL grant resources for multiple SRs of the same UE.
  • S205 The eNB notifies the UE of the first uplink resource.
  • S206 The UE sends a BSR on the first uplink resource.
  • S207 The eNB schedules a second uplink resource for the UE according to the received BSR, and notifies the UE of the second uplink resource.
  • the UE receives the UL grant and sends the uplink data on the corresponding UL grant; the uplink data includes (the BSR corresponding to the different types of SRs, or the uplink data in the LCH/LCG bound thereto).
  • the UL grants that are applied by different types of SRs can be shared or shared.
  • the UL grant of the low-priority type SR application can be exclusive to the LCH/LCG bound by itself or the high-priority SR.
  • the eNB If the first UL grant (the first uplink resource) sends the BSR, the eNB, after receiving the BSR, allocates a corresponding UL grant, and the UL grant can be used to send the uplink data.
  • the UE sends the SR and carries the SR type through the multi-bit display.
  • the multi-bit can also carry the number of LCGs that the UE has data to send, thereby assisting the eNB to allocate a suitable UL grant for the UE to send the BSR.
  • the UE After receiving the UL grant, the UE uses the UL grant according to the logical channel priority procedure LCP, that is, how to multiplex the MAC PDU, where the MAC PDU includes the LCH data to be sent and the MAC CE (BSR);
  • LCP logical channel priority procedure
  • the order between LCH data and BSR can be configured.
  • the UE determines the order of multiplexing to the MAC PDU according to a pre-stored LCH data and MAC CE priority order, and the priority order may be configured by the eNB; the specific configuration manner may be: RRC reconfiguration, MAC CE or other.
  • the possible LCH data and BSR order may be:
  • the BSR format may be (NR design, flexible BSR format, odd-numbered and even-numbered LCG).
  • FIG. 5a is a schematic diagram of a BSR format
  • FIG. 5b is a schematic diagram of another BSR format.
  • Figure 5a shows the NR BSR and Truncated NR BSR MAC control element for even N, that is, the NR BSR and the truncated NR BSR MAC CE when N is even, and the NR BSR and Truncated NR BSR MAC control element for odd N in Figure 5b.
  • Figure 5b that is, a schematic diagram of the NR BSR and the truncated NR BSR MAC CE when N is an odd number.
  • the LCG ID is the logical channel identifier, and the amount of data to be sent by the corresponding LCG can be expressed by the buffer size.
  • BSR transmission (truncate BSR transmission, and LCG ID in BSR are sorted in descending order)
  • the BSRs corresponding to the LCGs that have data to be sent can be reported to the base station; that is, the complete BSR; If the UL grant is insufficient, the BSR is reported to be truncated, and the buffer size of the LCG to be sent is reported as much as possible.
  • the LCGs are sorted according to the priority of the highest LCH in the LCG group. (The LCG IDs reported in the BSR are in descending order.)
  • the NR BSR format is more flexible, and only the LCG buffer size with data to be sent is reported, which is different from the existing LTE fixed BSR format (only one of the short and the long BSR, respectively, and one and four LCGs).
  • S208 The UE sends data to the eNB on the second uplink resource.
  • the padding BSR may be sent by using the remaining resources; if the remaining number of bits is greater than the sum of the BSRs of all the LCGs to be sent and the subheaders corresponding to the BSRs, all data may be The BSR corresponding to the sent LCG is reported to the base station;
  • the BSR is reported to be truncated, and the BSRs of the LCGs to be sent are reported as much as possible, and the LCGs are sorted according to the priority of the highest LCH in the LCG group--the LCG IDs reported in the BSR are in descending order.
  • the data to be sent in the BSR includes data in a Radio Link Control (RLC) entity and a Packet Data Convergence Protocol (PDCP) entity, but does not include an RLC header and a PDCP. Header; wherein, the RLC is located above the MAC layer, and the PDCP is located above the RLC layer;
  • RLC Radio Link Control
  • PDCP Packet Data Convergence Protocol
  • 5G introduces a new layer (for example, SDAP: Service Data Adaptation Protocol) on the PDCP layer for mapping between QoS flow and Data Radio Bearer (DRB).
  • SDAP Service Data Adaptation Protocol
  • DRB Data Radio Bearer
  • the BSR is calculated.
  • PDU Protocol Data Unit
  • the UE distinguishes the type of the pending SR.
  • the UE may adopt different processing modes after identifying different SR types, such as rapidly triggering/sending the SR, and configuring different SR related parameters— —sr-prohibitTimer and logicalChannelSR-ProhibitTimer.
  • the UE can inform the eNB of the SR type information in a display or implicit manner, thereby assisting the eNB to implement the classification type scheduling.
  • the UE can quickly indicate the physical layer Signal SR to the SR that triggers the high-priority LCH data, and assists the eNB to quickly schedule downlink resources by displaying or implicitly carrying the priority information in the process of sending the SR. In this way, the scheduling delay is reduced, and the base station can allocate resources reasonably.
  • the sending SR will be canceled when the sending SR meets any of the following conditions:
  • Option 1 MAC PDU group packet, and carries the corresponding BSR in the PDU packet.
  • Option 2 The upper layer is configured with grant-free resources, and the SR can be cancelled without the first two steps.
  • Option 3 The allocated UL grant is sufficient to send data.
  • the option 2 and option 4 are newly added cases compared to LTE.
  • the grant-free mode in option 2 is equivalent to pre-configuring resources for the UE.
  • the UE has the resource, and as long as there is a data packet to be sent, it can be directly sent. Apply for UL grant by scheduling.
  • the scheduling method of the uplink transmission resources proposed in the embodiments of the present application proposes to distinguish different SR types, such as priorities, and the high priority SRs can be fast.
  • the cancellation of the dispatch request is sent to further save resources.
  • FIG. 6 is a schematic structural diagram of Embodiment 1 of a terminal device according to an embodiment of the present disclosure; as shown in FIG. 6, the terminal device 100 includes:
  • the processing module 101 is configured to determine, according to the first indication information that is acquired in advance, the first scheduling request, when the first logical channel of the terminal device has the data to be sent, and the first indication information is used; the first indication information is used to indicate the logical channel.
  • the first scheduling request includes a first scheduling request type for indicating uplink scheduling information required by the terminal device;
  • the sending module 102 is configured to send the first scheduling request to the access network device.
  • the receiving module 103 is configured to receive first uplink scheduling information that is sent by the access network device, where the uplink scheduling information is used to indicate a first uplink resource used by the terminal device to send uplink data to the access network device. .
  • the terminal device provided in this embodiment is used to perform the technical solution of the terminal device side in any of the foregoing embodiments.
  • the processing module obtains the first BSR according to the foregoing.
  • An indication information determines a first scheduling request, and sends a first scheduling request carrying type information to the access network device, and the access network device allocates an uplink resource to the terminal device according to the type of the scheduling request, and notifies the terminal device, and the processing module according to the logic
  • the mapping between the channel and the type carries the scheduling request when the scheduling request is sent to the access network device.
  • the access network device can distinguish the scheduling request of the service according to the type of the scheduling request, and quickly and reasonably allocate resources for the terminal device.
  • the sending module 102 is further configured to send uplink data on the first uplink resource, where the uplink data includes the first BSR, or the first BSR and data to be sent. .
  • the receiving module 103 is further configured to receive second uplink scheduling information that is sent by the access network device, where the second uplink scheduling information is used to indicate that the access network device is configured according to the first BSR. Transmitting, by the terminal device, a second uplink resource that is to be sent to the access network device to be buffered data to be sent;
  • the sending module 102 is further configured to send data to be sent on the second uplink resource.
  • the receiving module 103 is further configured to receive the first indication information that is sent by the access network device.
  • the first indication information further includes:
  • the sending module 102 is specifically configured to:
  • the first scheduling request is sent to the access network device on an available PUCCH.
  • the first logical channel is used to send high priority service data.
  • the duration of the scheduling request prohibition timer of the first logical channel is smaller than the duration of the scheduling request prohibition timer of the other logical channel.
  • the scheduling request prohibiting timer corresponding to the terminal device is disabled when determining that the first BSR triggers the data to be sent in the first logical channel.
  • processing module 101 is further configured to: when the scheduling request cancellation condition is met, cancel the first scheduling request; and the scheduling request cancellation condition includes any one of the following conditions:
  • the first BSR is carried in a MAC PDU to be sent
  • the uplink resource that the access network device has allocated to the terminal device is sufficient to transmit all data to be sent;
  • the terminal device has received an uplink resource corresponding to the type of the first scheduling request that is allocated by the access network device;
  • the access network device configures the terminal device with an unlicensed uplink resource.
  • the terminal device provided by any of the foregoing embodiments is used to perform the technical solution of the terminal device in any of the foregoing embodiments, and the implementation principle and technical effects are similar, and details are not described herein again.
  • FIG. 7 is a schematic structural diagram of Embodiment 1 of an access network device according to an embodiment of the present disclosure; as shown in FIG. 7, the access network device 200 includes:
  • the receiving module 201 is configured to receive a first scheduling request sent by the terminal device, where the first scheduling request includes a first scheduling request type used to indicate uplink scheduling information required by the terminal device;
  • the processing module 202 is configured to determine a type of the first scheduling request, and schedule, by the terminal device, a first uplink resource for sending uplink data according to the type of the first scheduling request.
  • the sending module 203 is configured to send the first uplink scheduling information to the terminal device, where the first uplink scheduling information is used to indicate the first uplink resource.
  • the access network device provided in this embodiment is used to implement the technical solution of the access network device side in any of the foregoing embodiments.
  • the scheduling request received by the receiving module carries the type of the scheduling request, and the processing module may use the channel according to the scheduling request. Or the quantity or the carried information determines the type of the scheduling request, and then the service scheduling request is differentiated according to the type of the scheduling request, and the resource is scheduled for the terminal device quickly and reasonably.
  • the receiving module 201 is further configured to receive uplink data that is sent by the terminal device on the first uplink resource, where the uplink data includes a first BSR, or the first BSR and data.
  • the processing module 202 is further configured to schedule, according to the first BSR, a second uplink resource for uploading data for the terminal device;
  • the sending module 203 is further configured to send the second uplink scheduling information to the terminal device, where the second uplink scheduling information is used to indicate the second uplink resource;
  • the access network device receives data sent by the terminal device on the second uplink resource.
  • the sending module 203 is further configured to send first indication information to the terminal device, where the first indication information is used to indicate a correspondence between a logical channel and a type of a scheduling request.
  • the first indication information includes:
  • processing module 202 is specifically configured to:
  • Determining a type of the first scheduling request according to a correspondence between a physical downlink control channel PUCCH that receives the first scheduling request and a type of a pre-configured scheduling request and a PUCCH;
  • the access network device provided by any of the foregoing embodiments is used to perform the technical solution of the access network device in any of the foregoing embodiments, and the implementation principle and technical effects are similar, and details are not described herein again.
  • the processing module may be implemented as a processor, the sending module may be implemented as a transmitter, and the receiving module may be time-limited as a receiver.
  • a fifth aspect of the embodiments of the present application provides a terminal device, including: a memory, a processor, a transmitter, a receiver, and a computer program, where the computer program is stored in the memory, and the processor runs the computer program to execute A method for scheduling uplink transmission resources provided by any of the embodiments.
  • the number of processors is at least one, and is used to execute an execution instruction of the memory storage, that is, a computer program.
  • the scheduling method of the uplink transmission resource provided by the foregoing various embodiments is performed by the sending device to perform data interaction with the access network device through the communication interface.
  • the memory may also be integrated in the processor.
  • a sixth aspect of the embodiments of the present application provides an access network device, including: a memory, a processor, a receiver, a transmitter, and a computer program, where the computer program is stored in the memory, and the processor runs the computer The program performs the scheduling method of the uplink transmission resource provided by any of the foregoing embodiments.
  • the number of processors is at least one, and is used to execute an execution instruction of the memory storage, that is, a computer program.
  • the method for scheduling the uplink transmission resource provided by the foregoing various embodiments is performed by the access network device performing the data interaction between the access interface and the terminal device.
  • the memory may also be integrated in the processor.
  • a seventh aspect of the present application provides a storage medium, including: a readable storage medium and a computer program, where the computer program is used to implement a method for scheduling an uplink transmission resource provided by any of the embodiments of the first aspect. Program.
  • the eighth aspect of the embodiments of the present application provides a storage medium, including: a readable storage medium and a computer program, where the computer program is used to implement a scheme of an access network device side in a scheduling method of an uplink transmission resource provided by any of the embodiments. .
  • a ninth aspect of the embodiments of the present application provides a program product, the program product comprising a computer program (ie, an execution instruction) stored in a readable storage medium.
  • a computer program ie, an execution instruction
  • At least one processor of the terminal device can read the computer program from a readable storage medium, and the at least one processor executes the computer program to cause the terminal device to implement the scheduling method of the uplink transmission resource provided by the various embodiments described above.
  • the embodiment of the present application further provides a program product, the program product comprising a computer program (ie, an execution instruction), the computer program being stored in a readable storage medium.
  • a computer program ie, an execution instruction
  • At least one processor of the access network device can read the computer program from a readable storage medium, and the at least one processor executes the computer program such that the access network device implements the scheduling method of the uplink transmission resources provided by the various embodiments described above.
  • the processor may be a central processing unit (English: Central Processing Unit, CPU for short), or may be other general-purpose processors and digital signal processors (English: Digital Signal Processor (DSP), Application Specific Integrated Circuit (ASIC), etc.
  • 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 as a hardware processor, or may be performed by a combination of hardware and software modules in the processor.
  • All or part of the steps of implementing the above method embodiments may be performed by hardware associated with the program instructions.
  • the aforementioned program can be stored in a readable memory.
  • the steps including the foregoing method embodiments are performed; and the foregoing memory (storage medium) includes: read-only memory (English: read-only memory, abbreviation: ROM), RAM, flash memory, hard disk, Solid state drive, magnetic tape (English: magnetic tape), floppy disk (English: floppy disk), optical disc (English: optical disc) and any combination thereof.

Landscapes

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

Abstract

本申请提供一种上行传输资源的调度方法和设备，该方法包括：当终端设备的第一逻辑信道存在待发送数据而触发第一BSR时，终端设备根据预先获取的第一指示信息确定第一调度请求，第一指示信息用于指示逻辑信道与调度请求的类型之间的对应关系，第一调度请求包括第一调度请求类型，终端设备向接入网设备发送第一调度请求；终端设备接收接入网设备发送的第一上行调度信息，上行调度信息用于指示用于终端设备向接入网设备发送上行数据的第一上行资源。接入网设备可以根据调度请求的类型区分业务的调度请求，快速合理的为终端设备调度资源。

Description

上行传输资源的调度方法和设备
本申请要求于2017年05月03日提交中国专利局、申请号为201710307267.9、申请名称为“上行传输资源的调度方法和设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术，尤其涉及一种上行传输资源的调度方法和设备。
背景技术
在长期演进(Long Term Evolution，LTE)技术中，上行调度流程总体可分为下面5个步骤：调度请求(Scheduling Request，SR)发送、基站(evolved Node B，eNB)分配上行资源(Uplink Grant，UL Grant)发送缓存状态报告(Buffer State Report，BSR)、终端在该资源上发送BSR、eNB分配UL Grant用于发送上行数据、终端在该资源上发送上行数据。具体的，当有数据到达时，在满足BSR触发条件时，用户设备(User Equipment，UE)触发常规BSR—regular BSR，UE触发regular BSR后，如果满足SR触发条件，即logicalChannel-SR-ProhibitTimer没有在运行，则触发SR，并指示物理层在可用的物理上行控制信道(Physical Uplink Control Channel，PUCCH)资源上发送SR，UE在可用PUCCH资源上发送SR(1bit)，用于告知eNB UE有数据要发，请求分配发送BSR的上行资源，eNB收到UE发送的SR后，给UE分配上行资源用于发送BSR，UE收到分配的上行资源后，在对应的资源上发送BSR，告知eNB自己有多少数据量待发送，eNB收到UE发送的BSR后，根据BSR以及eNB自身调度算法，分配发送上行数据所需的资源，UE收到分配的上行资源后，在对应的资源上发送上行数据，实现上行数据的传输。
随着移动通信技术的发展，未来的第五代移动通信(5th-Generation，5G)已成为全球研发的热点。3GPP TR 38.913中将5G的应用场景划分成3类：增强移动带宽(enhanced Mobile Broadband，eMBB)、海量机器类通信(massive Machine Type Communications，mMTC)以及低时延高可靠通信(Ultra-Reliable and Low Latency Communications，URLLC)。
5G业务种类繁多，不同业务的需求不同，如URLLC对时延和可靠性要求较高，若按照上述的上行调度方式，其中sr-prohibitTimer是用来限制连续连个SR发送的时间间隔，在此timer运行时间内，是不能发送其他SR，导致资源调度时延较长，因此LTE中上行资源调度的方式不能满足5G网络的要求。
发明内容
本申请实施例提供一种上行传输资源的调度方法和设备，用于解决LTE中上行资源调度的方式不能满足5G网络的要求的问题。
本申请实施例第一方面提供一种上行传输资源的调度方法，所述方法包括：
当终端设备的第一逻辑信道存在待发送数据而触发第一BSR时，根据预先获取的第一指示信息确定第一调度请求；所述第一指示信息用于指示逻辑信道与调度请求的类型之间的对应关系；所述第一调度请求包括用于指示所述终端设备所需的上行调度信息的第一调度请求类型；
向接入网设备发送所述第一调度请求；
接收所述接入网设备发送的第一上行调度信息；所述上行调度信息用于指示用于所述终端设备向所述接入网设备发送上行数据的第一上行资源。
一种具体的实现方式中，所述方法还包括：
在所述第一上行资源上发送上行数据；所述上行数据包括所述第一BSR，或者所述第一BSR和待发送数据。
一种具体的实现方式中，所述方法还包括：
接收所述接入网设备发送的第二上行调度信息；所述第二上行调度信息用于指示所述接入网设备根据所述第一BSR为所述终端设备配置的、向所述接入网设备发送缓存的待发送数据的第二上行资源；
在所述第二上行资源上发送待发送数据。
可选的，在具体实现中，当终端设备向接入网设备多次发送调度请求，接入网设备也可以根据调度请求的类型为该终端设备调度用于发送缓存的待发送数据的第二上行资源。
一种具体的实现方式中，所述当终端设备的第一逻辑信道存在待发送数据而触发第一缓存状态报告BSR时，根据预先获取的第一指示信息确定第一调度请求之前，所述方法还包括：
接收所述接入网设备发送的所述第一指示信息。
一种具体的实现方式中，所述第一指示信息还包括：
逻辑信道与调度请求的类型之间的对应关系；
或者，
逻辑信道与资源使用属性之间的对应关系，以及资源使用属性与调度请求的类型之间的对应关系；
或者，
调度请求的类型与业务组的对应关系，以及逻辑信道与业务优先级的对应关系；
或者，
调度请求的类型与逻辑信道优先级的对应关系。
一种具体的实现方式中，向接入网设备发送所述第一调度请求，包括：
指示物理层在所述第一调度请求的类型对应的物理下行控制信道PUCCH上向所述接入网设备发送所述第一调度请求；
或者，
指示物理层在可用的物理下行控制信道PUCCH上向所述接入网设备发送所述第一调度请求。
一种具体的实现方式中，所述第一逻辑信道用于发送高优先级的业务数据。
一种具体的实现方式中，所述第一逻辑信道的调度请求禁止定时器的时长小于其他逻辑信道的调度请求禁止定时器的时长。例如：所述第一逻辑信道的调度请求禁止定时器的 时长为零。
另一种具体的实现方式中，所述终端设备对应的调度请求禁止定时器在确定所述第一BSR为所述第一逻辑信道存在待发送数据触发时去使能。
一种具体的实现方式中，向接入网设备发送所述第一调度请求之前，所述方法还包括：
检测到满足调度请求取消条件时，将所述第一调度请求取消；所述调度请求取消条件包括以下任一个条件：
所述第一BSR被携带在待发送的MAC PDU中；
所述接入网设备已经分配给所述终端设备的上行资源足够传输所有待发送数据；
所述终端设备已经收到所述接入网设备分配的所述第一调度请求的类型对应的上行资源；
所述接入网设备为所述终端设备配置了免授权的上行资源。
本申请实施例第二方面提供一种上行传输资源的调度方法，所述方法包括：
接收终端设备发送的第一调度请求；所述第一调度请求包括用于指示所述终端设备所需的上行调度信息的第一调度请求类型；
确定所述第一调度请求的类型，并根据所述第一调度请求的类型为所述终端设备调度用于发送上行数据的第一上行资源；
向所述终端设备发送第一上行调度信息，所述第一上行调度信息用于指示所述第一上行资源。
一种具体的实现方式中，所述方法还包括：
接收所述终端设备在所述第一上行资源上发送的上行数据，所述上行数据包括第一BSR，或者所述第一BSR和数据。
一种具体的实现方式中，所述方法还包括：
根据所述第一BSR为所述终端设备调度用于上传数据的第二上行资源；
向所述终端设备发送第二上行调度信息，所述第二上行调度信息用于指示所述第二上行资源；
在所述第二上行资源上接收所述终端设备发送的数据。
可选的，在具体实现中，当接入网设备接收到终端设备多次发送的调度请求，接入网设备也可以根据调度请求的类型为该终端设备调度用于发送缓存的待发送数据的第二上行资源。
一种具体的实现方式中，接收终端设备发送的第一调度请求之前，所述方法还包括：
向所述终端设备发送第一指示信息；所述第一指示信息用于指示逻辑信道与调度请求的类型之间的对应关系。
一种具体的实现方式中，所述第一指示信息包括：
逻辑信道与调度请求的类型之间的对应关系；
或者，
逻辑信道与资源使用属性之间的对应关系，以及资源使用属性与调度请求的类型之间的对应关系；
或者，
调度请求的类型与业务组的对应关系，以及逻辑信道与业务优先级的对应关系；
或者，
调度请求的类型与逻辑信道优先级的对应关系。
一种具体的实现方式中，确定所述第一调度请求的类型，包括：
根据接收所述第一调度请求的PUCCH以及预先配置的调度请求的类型与PUCCH之间的对应关系，确定所述第一调度请求的类型；
或者，
根据预设时长内接收到的第一调度请求的数量确定所述第一调度请求的类型。
本申请实施例第三方面提供一种上行传输资源的调度装置，该装置可以是终端设备，也可以是终端设备内的芯片。该装置可以包括处理单元和收发单元。当该装置是终端设备时，该处理单元可以是处理器，该收发单元可以是收发器；该终端设备还可以包括存储单元，该存储单元可以是存储器；该存储单元用于存储指令，该处理单元执行该存储单元所存储的指令，以使该终端设备执行第一方面或者第一方面的各种实施方式提供的上行传输资源的调度方法。当该装置是终端设备内的芯片时，该处理单元可以是处理器，该收发单元可以是输入/输出接口、管脚或电路等；该处理单元执行存储单元所存储的指令，以使该终端设备执行第一方面或者第一方面的各种实施方式提供的上行传输资源的调度方法，该存储单元可以是该芯片内的存储单元(例如，寄存器、缓存等)，也可以是该终端设备内的位于该芯片外部的存储单元(例如，只读存储器、随机存取存储器等)。
本申请实施例第四方面提供一种上行传输资源的调度装置，该装置可以是网络设备，也可以是网络设备内的芯片。该装置可以包括处理单元和收发单元。当该装置是网络设备时，该处理单元可以是处理器，该收发单元可以是收发器；该网络设备还可以包括存储单元，该存储单元可以是存储器；该存储单元用于存储指令，该处理单元执行该存储单元所存储的指令，以使该网络设备执行第二方面或者第二方面的各种实施方式提供的上行传输资源的调度方法。当该装置是网络设备内的芯片时，该处理单元可以是处理器，该收发单元可以是输入/输出接口、管脚或电路等；该处理单元执行存储单元所存储的指令，以使该网络设备执行第二方面或者第二方面的各种实施方式提供的上行传输资源的调度方法，该存储单元可以是该芯片内的存储单元(例如，寄存器、缓存等)，也可以是该网络设备内的位于该芯片外部的存储单元(例如，只读存储器、随机存取存储器等)。
本申请实施例第五方面提供一种上行传输资源的调度装置，该装置包括处理器和存储介质，该存储介质存储有指令，该指令被该处理器运行时，使得该处理器执行第一方面或者第一方面的各种实施方式提供的上行传输资源的调度方法。该装置可以是芯片或芯片系统。
本申请实施例第六方面提供一种上行传输资源的调度装置，该装置包括处理器和存储介质，该存储介质存储有指令，该指令被该处理器运行时，使得该处理器执行第二方面或者第二方面的各种实施方式提供的上行传输资源的调度方法。该装置可以是芯片或芯片系统。
本申请实施例第七方面提供一种计算机存储介质，该计算机存储介质存储有计算机可执行指令，该计算机可执行指令在被计算机调用时，使该计算机执行第一方面或者第一方面的各种实施方式提供的上行传输资源的调度方法。
本申请实施例第八方面提供一种计算机存储介质，该计算机存储介质存储有计算机可执行指令，该计算机可执行指令在被计算机调用时，使该计算机执行第二方面或者第二方面的各种实施方式提供的上行传输资源的调度方法。
本申请实施例第九方面提供一种程序产品，该程序产品包括计算机程序(即执行指令)，该计算机程序存储在可读存储介质中。终端设备的至少一个处理器可以从可读存储介质读取该计算机程序，至少一个处理器执行该计算机程序使得终端设备实施第一方面或者第一方面的各种实施方式提供的上行传输资源的调度方法。
本申请实施例第十方面提供一种程序产品，该程序产品包括计算机程序(即执行指令)，该计算机程序存储在可读存储介质中。接入网设备的至少一个处理器可以从可读存储介质读取该计算机程序，至少一个处理器执行该计算机程序使得接入网设备实施上述第二方面或者第二方面的各种实施方式提供的上行传输资源的调度方法。
本申请实施例提供的上行传输资源的调度方法和设备，当终端设备的第一逻辑信道存在待发送数据而触发第一BSR时，终端设备根据预先获取的第一指示信息确定第一调度请求，第一指示信息用于指示逻辑信道与调度请求的类型之间的对应关系，第一调度请求包括第一调度请求类型，终端设备向接入网设备发送第一调度请求；终端设备接收接入网设备发送的第一上行调度信息，上行调度信息用于指示用于终端设备向接入网设备发送上行数据的第一上行资源。接入网设备可以根据调度请求的类型区分业务的调度请求，快速合理的为终端设备调度资源。
附图说明
图1为本申请实施例提供的上行传输资源的调度方法的一种应用场景示意图；
图2为本申请实施例提供的上行传输资源的调度方法实施例一的交互流程图；
图3为本申请实施例提供的上行传输资源的调度方法实施例二的交互流程图；
图4为本申请实施例提供的上行传输资源的调度方法一实例的交互流程图；
图5a为一种BSR格式示意图；
图5b为另一种BSR格式示意图；
图6为本申请实施例提供的终端设备实施例一的结构示意图；
图7为本申请实施例提供的接入网设备实施例一的结构示意图。
具体实施方式
本申请实施例的技术方案可以应用5G通信系统或未来的通信系统，也可以用于其他各种无线通信系统，例如：全球移动通讯(Global System of Mobile communication，GSM)系统、码分多址(CDMA，Code Division Multiple Access)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)系统、LTE频分双工(Freq终端设备ncy Division Duplex，FDD)系统、LTE时分双工(Time Division Duplex，TDD)、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)等。
图1为本申请实施例提供的上行传输资源的调度方法的一种应用场景示意图，如图1 所示，该上行传输资源的调度方法的一种应用场景，应用在基站和用户设备(User Equipment，UE)之间，基站为UE进行资源调度时，可根据该方案进行调度。基站作为接入网设备、UE作为终端设备。
在实际应用中，接入网设备还可以是全球移动通讯(Global System of Mobile communication，简称GSM)或码分多址(Code Division Multiple Access，简称CDMA)中的基站(Base Transceiver Station，简称BTS)，也可以是宽带码分多址(Wideband Code Division Multiple Access，简称WCDMA)中的基站(NodeB，简称NB)，还可以是LTE中的演进型基站(Evolutional Node B，简称eNB或eNodeB)，或者中继站或接入点，或者未来5G网络中的基站等，在此并不限定。
终端设备可以是无线终端也可以是有线终端，无线终端可以是指向用户提供语音和/或其他业务数据连通性的设备，具有无线连接功能的手持式设备、或连接到无线调制解调器的其他处理设备。无线终端可以经无线接入网(Radio Access Network，简称RAN)与一个或多个核心网进行通信，无线终端可以是移动终端，如移动电话(或称为“蜂窝”电话)和具有移动终端的计算机，例如，可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置，它们与无线接入网交换语言和/或数据。例如，个人通信业务(Personal Communication Service，简称PCS)电话、无绳电话、会话发起协议(Session Initiation Protocol，简称SIP)话机、无线本地环路(Wireless Local Loop，简称WLL)站、个人数字助理(Personal Digital Assistant，简称PDA)等设备。无线终端也可以称为系统、订户单元(Subscriber Unit)、订户站(Subscriber Station)，移动站(Mobile Station)、移动台(Mobile)、远程站(Remote Station)、远程终端(Remote Terminal)、接入终端(Access Terminal)、用户终端(User Terminal)、用户代理(User Agent)、用户设备(User Device or User Equipment)，在此不作限定。
图2为本申请实施例提供的上行传输资源的调度方法实施例一的交互流程图，如图2所示，该上行传输资源的调度方法的具体实现步骤为：
S101：终端设备的第一逻辑信道存在待发送数据而触发第一BSR时，终端设备根据预先获取的第一指示信息确定第一调度请求。
在本步骤中，第一指示信息用于指示逻辑信道与调度请求的类型之间的对应关系；第一调度请求包括用于指示终端设备所需的上行调度信息的第一调度请求类型。
终端设备可预先根据接入网设备的配置，或者与接入网设备侧的协商，或者通过协议中的规定等方式获取逻辑信道与调度请求的类型之间的关系，对此本方案不做限制。
当有数据到达且需要满足了触发BSR的条件时候，可触发BSR，即上述的第一BSR，此时终端设备需要向接入网设备发送调度请求，以使接入网设备为该终端设备调度发送BSR的资源。在该过程中终端设备首先需要根据得到的第一指示信息以及数据缓存的逻辑信道确定要发送的调度请求的类型。一种具体实现方式中可以将该调度请求的类型携带在调度请求中。
可选的，在步骤S101之前，该方法还包括：终端设备接收所述接入网设备发送的所述第一指示信息。即通过接入网设备的通知获取到上述第一指示信息。
S102：终端设备向接入网设备发送第一调度请求。
在本步骤中，如果接入网设备为该类型的第一调度请求配置了专门的资源，则需要终 端设备将该第一调度请求在接入网设备配置的对应的资源上进行发送，如果没有配置，则终端设备可以指示下层直接在可用的资源上进行发送。
对于接入网设备来说，接入网设备接收终端设备发送的第一调度请求，然后根据该第一调度请求为终端设备分配资源。
可选的，终端设备指示物理层在所述第一调度请求的类型对应的物理下行控制信道(Physical Uplink Control Channel，PUCCH)上向所述接入网设备发送所述第一调度请求。
或者，所述终端设备指示物理层在可用的PUCCH上向所述接入网设备发送所述第一调度请求。
S103：接入网设备确定第一调度请求的类型，并根据第一调度请求的类型为终端设备调度用于发送上行数据的第一上行资源。
在本步骤中，接入网设备可以直接根据第一调度请求中携带的第一调度请求的类型进行资源分配，至少还可以通过以下几种方式确定第一调度请求的类型：
第一种方式，接入网设备根据接收第一调度请求的PUCCH以及预先配置的调度请求的类型与PUCCH之间的对应关系，确定所述第一调度请求的类型。
即接入网设备预先配置的PUCCH与调度请求的关系，即使终端设备发送的第一调度请求中没有携带类型，接入网设备也可以通过接收的PUCCH信道确定出该第一调度请求的类型。
第二种方式，接入网设备根据预设时长内接收到的第一调度请求的数量确定第一调度请求的类型。不同业务优先级的调度请求可以发送的频率或者数量不同，因此接入网设备还可以根据预设时长内接收到的调度请求的数量去确定类型。
接入网设备在确定了调度请求的类型之后，针对不同的调度请求的类型，可采取不同的调度方式以及分配对应的资源，例如：针对优先级比较高的调度请求，可以单独调度上行资源，或者可以缩短处理时间，即优先为优先级高的调度请求分配资源并快速下发给终端设备。
S104：终端设备接收接入网设备发送的第一上行调度信息；上行调度信息用于指示用于所述终端设备向接入网设备发送上行数据的第一上行资源。
在本步骤中，接入网设备向终端设备发送第一上行调度信息，第一上行调度信息用于指示所述第一上行资源。接入网设备在为终端设备分配完资源之后，可以将分配的上行资源通知给终端设备，具体的通知方式可以是携带在下行信息中，也可以专门发送指示资源的第一上行调度请求，对此本方案不做限制。
本实施例提供的上行传输资源的调度方法，当终端设备的第一逻辑信道存在待发送数据而触发第一BSR时，终端设备根据预先获取的第一指示信息确定第一调度请求，向接入网设备发送携带类型信息的第一调度请求，接入网设备根据调度请求的类型为终端设备分配上行资源，并通知该终端设备，根据逻辑信道与类型的对应关系，在给接入网设备发送调度请求时携带调度请求的类型，接入网设备可以根据调度请求的类型区分业务的调度请求，快速合理的为终端设备调度资源。
在上述实施例的基础上，该上行传输资源的调度方法的一种具体实现中，接入网设备为终端设备发送的第一指示信息中还包括但不限于以下至少一项：
逻辑信道与调度请求的类型之间的对应关系；或者，
逻辑信道与资源使用属性之间的对应关系，以及资源使用属性与调度请求的类型之间的对应关系；或者，
调度请求的类型与业务组的对应关系，以及逻辑信道与业务优先级的对应关系；或者，
调度请求的类型与逻辑信道优先级的对应关系。
到达终端设备需要上行传输的数据具有一定的属性信息，同一个业务组的数据具有相同或者相近的属性，可以是业务类型、业务的服务质量需求，如传输时延、可靠性等。以便终端设备能够根据若干能够确定业务优先级或者逻辑信道、或者逻辑信道的优先级，然后根据上述的对应关系得到第一调度请求的类型。
例如一种具体实现方式中，所述第一逻辑信道被配置为用于发送高优先级的业务数据。在该第一逻辑信道被触发BSR之后，可根据业务优先级确定调度请求的类型。
可选的，还可以配置所述第一逻辑信道的调度请求禁止定时器的时长小于其他逻辑信道的调度请求禁止定时器的时长。例如：可将第一逻辑信道的调度请求禁止定时器的时长配置为零，以便第一调度请求能够快速的发送给接入网设备。
可选的，当该调度请求禁止定时器是给每个终端设备分别配置的时，终端设备对应的调度请求禁止定时器在确定所述第一BSR为所述第一逻辑信道存在待发送数据触发时去使能。其含义是：终端设备在发现第一BSR是第一逻辑信道触发时，可对该调度请求禁止定时器去使能，即禁止运行，同时在所述终端的调度请求禁止定时器运行期间，第一逻辑信道的调度请求仍可以发送。该去使能指示可以是接收所述接入网设备发送的第一逻辑信道去使能调度请求禁止定时器的指示信息；也可以是在协议中规定的，对此本方案不做限制。
图3为本申请实施例提供的上行传输资源的调度方法实施例二的交互流程图，如图3所示，在上述实施例一的基础上，步骤S104之后，还可以包括以下步骤：
S105：终端设备在第一上行资源上发送上行数据；上行数据包括第一BSR，或者第一BSR和待发送数据。
在本步骤中，终端设备在根据接入网发送的第一上行调度信息确定了第一上行资源之后，可在第一上行资源上进行数据传输，即在该第一上行资源上将第一BSR发送给接入网设备。也可以同时在该第一上行资源上发送第一BSR和缓存的上行数据，对此本方案不做限制。
S106：接入网设备根据第一BSR为终端设备调度用于上传数据的第二上行资源。
可选的，在另一种实现方式中，当终端设备向接入网设备多次发送该调度请求，则接入网设备还可以根据调度请求的类型为终端设备调度用于传输数据的第二上行资源，对此本方案不做限制。
S107：接入网设备向终端设备发送第二上行调度信息，第二上行调度信息用于指示第二上行资源。
同样的，该第二上行调度信息用于指示所述接入网设备根据所述第一BSR或所述第一调度请求的类型为所述终端设备配置的、向所述接入网设备发送缓存的待发送数据的第二上行资源。
S108：终端设备在第二上行资源上发送待发送数据。
在上述几个步骤中，接入网设备接收到终端设备发送的第一BSR之后，根据该BSR 为终端设备调度用于传输数据的第二上行资源并通知给终端设备，以使终端设备在该第二上行资源上发送待发送数据。
在上述图1或图2实施例的中，针对不同类型的调度请求，在满足以下任一条件时，待定的调度请求可以被取消：
条件一、第一BSR被携带在待发送的一个或者多个媒体接入控制协议数据单元(Media Access Control Protocol Data Unit，MAC PDU)中。
条件二、所述接入网设备已经分配给所述终端设备的上行资源足够传输所有待发送数据。
条件三、所述终端设备已经收到所述接入网设备分配的所述第一调度请求的类型对应的上行资源。
条件四、所述接入网设备为所述终端设备配置了免授权的上行资源。
上述实施例提供的上行传输资源的调度方法，接入网设备发送给终端设备的第一指示信息，指示逻辑信道与调度请求的类型之间的对应关系，以使终端设备在逻辑信道上到达数据触发BSR之后，确定调度请求的类型，再向接入网设备发送携带类型的调度请求，以使接入网设备能够根据接收到的调度请求的类型，区分业务类型或者优先级，实现快速合理的资源分配。
在上述两个实施例的基础上，下面以图1中所示的应用场景，接入网设备为基站(eNB)，终端设备为UE为例，对本申请实施例提供的上行传输资源的调度方法进行详细说明。
图4为本申请实施例提供的上行传输资源的调度方法一实例的交互流程图，如图4所示，在一种具体的实现方式中，该上行资源的调度方法具体包括以下步骤：
S201：向UE发送LCH的配置信息。
在本步骤中，eNB向UE发送逻辑信道(Logical Channel，LCH)的配置信息(相当于前述的第一指示信息)，该LCH的配置信息包括逻辑信道(或者逻辑信道组)与资源使用属性(numerology)的对应关系、调度请求(Scheduling Request，SR)参数设置和BSR参数配置；可以通过无线资源控制(Radio Resource Control，RRC)/MAC等信令方式进行通知；其中：
SR参数配置可包括SR触发类型与numerology/传输时间间隔(Transmission Time Interval，TTI)之间的对应关系，或者与业务优先级的对应关系或者与逻辑信道优先级的对应关系等。
可选地，SR参数配置还可以包括SR相关的定时器timer，如限制SR发送的timer，即sr-ProhibitTimer，或者限制SR触发的timer，即logicalChannelSR-ProhibitTimer。
可选地，SR参数配置还可以包括配置某LCH具有快速触发SR功能；即当满足一些新SR触发case时，可以实现快速SR触发。
BSR参数配置包括：BSR相关定时器，BSR上报过程中逻辑信道或逻辑信道组与numerology的对应关系。
S202：UE触发BSR，并且根据LCH配置的SR触发机制和参数，触发并确定SR类 型，并指示物理层发送SR。
在本步骤中，当有数据到达，满足常规的(regular)BSR触发条件时，可触发regular BSR；一旦是低时延高可靠性(Ultra-Reliable and Low Latency Communications，URLLC)数据(data)触发了BSR，能够立刻触发SR。一种具体的实现方式为：
(一)、SR的快速触发
UE同时配有两套SR触发机制，只需配置特殊功能的LCH执行快速触发和指示物理层发送SR即可(这里会涉及一些新的触发case和短timer值；从而实现快速触发)，而对于其他逻辑信道上报时，可以正常执行。
通过该种配置方式，需要对协议进行较多的变动，只需要小改动。只配置了SR快速触发使能指示的某个逻辑信道，需要执行快速触发SR的操作，其他不用改变。
上述方案(快速触发的流程)的具体实现步骤如下：
1、针对UE来说，可同时具备两套SR触发机制，以满足UE发送不同业务的需求，其中，两套机制中一套是所有逻辑信道共用的，一套是针对某个逻辑信道单独配置的，当某个逻辑信道被单独配置了，那么可忽略共用的配置；
2、在RRC重配置消息中增加某个逻辑信道是否支持SR触发机制增强的信息单元(Information Element，IE)：logicalChannel-SR-Triggering-Enhancement-r15，且该逻辑信道与某一类高优先级业务(URLLC)绑定；
3、在RRC重配添加该资源块(Resource block，RB)时，会分配针对该RB或者逻辑信道对应的SR触发增强机制的配置(如忽略per-UE配置的logicalChannelSR-ProhibitTimer，或者采用新的SR触发机制等)；
4、在UE接收到RRC重配置消息时，会首先检查当前TTI可用的logicalChannel-SR-Triggering-Enhancement-r15配置：
(1)、若logicalChannel-BSR-Triggering-Enhancement-r15配置为true，则支持SR触发增强，当配置了BSR触发增加的逻辑信道中存在可用于发送的高优先级业务时，基于此逻辑信道及时触发并指示物理层在可用的PUCCH资源上发送SR，从而实现尽早获得UL grant的目的；
(2)、否则，按照正常的流程进行。
对于SR快速触发机制的描述如下：
1、针对时延要求较高的业务，可配置LCH-specific的logicalChannelSR-ProhibitTimer,可将这些LCHs的timer设置小些，(特别是5G引入numerologies with different durations of TTIs的情况下，针对不同LCH，其处理能力不同，可将定时器等控制能力设置不同)；
在per-UE配置下，由于URLLC data有包发送而触发了BSR，启动该LCH的logicalChannelSR-ProhibitTimer，与LTE机制中，该timer可启动或重启不同，这里只有启动，但不重启，一旦该timer超时，则可以触发SR；
2、针对时延要求较高的业务，可在LCH配置中增加一个去使能logicalChannelSR-ProhibitTimer的指示，即对URLLC的LCH触发SR不受此timer限制；
3、针对时延要求较高的业务，可在LCH配置中增加一个去使能logicalChannelSR-ProhibitTimer的指示，即对URLLC的LCH触发SR不受此timer限制； 但SR的触发，引入新的触发case，统计由于URLLC业务.
(二)、确定SR的类型
SR类型的划分方法可包括：
业务类型、重要程度来划分，如不同业务触发的regular BSR类型；
逻辑信道优先级高低；
逻辑信道组
逻辑信道的numerology/TTI
其他
具体地，eNB可配置SR类型和触发的regular BSR类型、或者逻辑信道或者逻辑信道组或者逻辑信道的numerology/TTI等之间的对应关系，并通过RRC信令或MAC控制单元(Control Element，CE)将此对应关系告知UE，UE通过此对应关系确定SR类型；
所述不同业务触发的regular BSR类型包括：
不同业务采用相同BSR触发机制触发的不同BSR，不同BSR触发是由于与业务绑定的LCH/LCG中有数据要发送；或者，
不同业务采用不同BSR触发机制触发的不同BSR，具体地，不同业务绑定的LCH/LCG配置了不同的触发机制，如对于时延要求较为敏感的业务，如URLLC，可配置其绑定的LCH/LCG具有快速触发BSR的功能；若配置了该功能，当满足如下条件(case)时，UE可快速触发regular BSR：
(1)、UE的上行缓存(buffer)为空且有新数据到达，例如：UE第一次发送上行数据。
(2)、为了避免UE发送了BSR却一直没有收到UL grant情况，可配置retxBSR-Timer，retxBSR-Timer超时，且UE的任意一个LCG的任意一个逻辑信道有数据可以发送时，触发“Regular BSR”，这里，针对时延要求较高的业务，可配置RB-specific的retxBSR-Timer(特别是5G引入numerologies with different durations of TTIs的情况下，针对不同RB，其处理能力不同，可将定时器等控制能力设置不同)；
(3)、UE已经发送了BSR，retxBSR-Timer超时前，buffer中数据bit或者数据包个数达到某一阈值(兼顾BSR触发时延和不必要的开销，配置阈值)，则触发“regular BSR”
(4)、UE已经发送了BSR，retxBSR-Timer超时前，新到达buffer的Data速度达到某一条件(根据到达buffer的Data速度，预判断后续到达buffer的数据量会很大，需提前申请UL grant)，触发“regular BSR”。
S203：UE向eNB发送SR，该SR携带SR类型信息。
在本步骤的具体实现中，UE可指示下层，比如物理层在PUCCH资源发送SR。
如果eNB为不同SR类型配置了相应的PUCCH资源(一对一)，则UE在确定SR类型后，指示下层，如物理层在SR类型对应的PUCCH资源上发送SR；
否则，若eNB未配置SR类型和PUCCH资源之间的对应关系，则UE指示下层，在可用PUCCH资源上发送SR，至于SR最后在哪个PUCCH资源上发，取决于UE实现。
本步骤的具体实现中包括SR的发送以及SR类型信息的携带，具体的：
(一)、SR的发送
当UE指示下层在可用PUCCH上发送SR时，会启动sr-prohibitTimer，该timer 是用来限制连续2个SR发送时间间隔，即在此timer运行时间内，是不能发送其他SR的，但该timer是per-UE的，对于URLLC来说，一旦SR发送不成功，要等到timer超时才能再请求SR，UL grant获取时延较大，per-UE的timer设置不合理；
鉴于此，考虑针对不同的SR类型，设置不同的sr-prohibitTimer；使得UE可区分不同类型SR的发送，可能的option有：
●Option 1：配置UE-specific sr-ProhibitTimer，但是该timer对于URLLC data LCH发起的高优先级不起作用；
●Option 2：配置LCH-specific sr-ProhibitTimer，对于URLLC data绑定的LCH/LCG该timer设置小；
两个option对比如下表所示：
表1 两种sr-ProhibitTimer设置option对比
Figure PCTCN2018085482-appb-000001
(二)、SR发送携带SR类型信息
UE在发送SR时携带SR类型方式可包括显示和隐式两种方式。
显示携带；
UE确定SR类型后，通过多bit SR显示指示，目前LTE SR中只有1bit，用来指示有无数据待发送，NR中有可能扩展SR bit数，从而携带SR类型信息。可选地，多bit SR中携带的还可能为UE待发送数据对应的BSR，或者UE待发送的LCG个数，从而辅助eNB来分配发送BSR的资源也不排除其他可能的信息
隐式携带
若eNB配置了SR类型和PUCCH资源的对应关系，UE确定SR类型后，在对应的PUCCH资源上发送，eNB通过PUCCH资源位置，确定SR类型信息；比如高优先级SR只能在short duration PUCCH上发送，而低优先级SR只能在long duration PUCCH上发送。
若eNB未配置SR类型和PUCCH资源的对应关系，即不同SR类型在何种PUCCH上发送取决于UE实现，UE确定SR类型后，可区分不同SR类型的发送方式，发过一个SR后，只有高优先级SR触发，UE才会指示下层发送，eNB通过接收到SR个数来识别SR类型。
注：为防止高优先级SR频繁发送SR，可限制收到UL grant之前不同SR类型最大可发送SR个数；(NR引入numerology，不排除有numerology-specific的PUCCH资源，可限制最大SR发送个数不超过可支持PUCCH资源类型个数)；在该方案中，不排除显示+隐式方式结合，即隐式携带方式中所发送的SR为多bit SR。
S204：eNB接收UE发送的SR，并根据SR确定第一上行资源。
在本步骤中，eNB接收并识别不同SR类型，针对不同SR类型，采取不同的调度方式以及分配对应的资源类型，具体地：
●针对高优先级SR，可单独调度UL grant，使得UE收到UL grant后，减小UE对UL grant的处理时延(复用不同逻辑信道的数据)。
●减小eNB处理时间，快速下发UL grant，如eNB在n时刻收到SR，可在n+4时刻反馈UL grant，针对高优先级SR，可在n+3时刻就下发UL grant。
Figure PCTCN2018085482-appb-000002
于上述两种方式中的UL grant(UL grant格式如下表所示)，eNB可根据不同的SR类型，分配不同的上行资源大小、MCS、上行功率、资源使用属性numerology/TTI指示等。
所述资源使用属性(numerology)包括资源周期(如周期为1ms，2ms，5ms，1个TTI长度，2个TTI长度，等)、传输时间间隔(Transmission Time Interval，简称TTI)长度(如1ms TTI，0.5msTTI，2个正交子载波调制(Orthogonal frequency division Modulation，OFDM)符号的TTI长度，1个OFDM符号的TTI长度等)、子载波间隔(如15KHz，60KHz等)，编码方式(如使用Turbo码，还是低密度奇偶校验(Low-Density Parity-Check，简称LDPC)码，还是极化Polar码等)，多址方式(如OFDM，码分多址接入(Code Division Multiple Access，简称CDMA)等)、频域占用的载波个数(如12个子载波，15个子载波等)、是否进行频域重复传输(是的话，还包含频域重复传输次数)，是否进行时域重复传输(是的话，还包含时域重复传输次数)中的至少一个。
表2 UL Grant的PDCCH中的部分IE
Figure PCTCN2018085482-appb-000003
可选地，在一种具体情况中对于eNB而言，如果收到同一个UE的多个SR，基站对该些SR的处理方式如下：
●Case 1：只回复一个SR。
●Case 2：针对每一个SR都进行回复，UE只要收到一个SR就可以，哪个先收到就采用哪个发送BSR。
Figure PCTCN2018085482-appb-000004
Option 1：eNB针对同一个UE的多个SR，回复相同的UL grant资源，在UL grant中增加指示信息，UE根据该指示信息可获知eNB分配的是相同的UL资源。
Figure PCTCN2018085482-appb-000005
Option 2：eNB针对同一UE的多个SR，回复不同的UL grant资源。
S205：eNB将第一上行资源通知给UE。
S206：UE在第一上行资源上发送BSR。
S207：eNB根据收到的BSR为UE调度第二上行资源，并向UE通知该第二上行资源。
在上述两个步骤中，UE接收UL grant，在对应UL grant上发送上行数据；上行数据包括(不同类型SR对应的BSR，或者与其绑定的LCH/LCG中的上行data)。
可选地，不同SR类型申请到的UL grant可以独享也可以共享，即如低优先级类型SR申请的UL grant，可以与自己绑定的LCH/LCG独享，也可以被高优先级SR类型对应的LCH/LCG抢占。
如果第一个UL grant(第一个上行资源)发送了BSR，则eNB在接收到BSR后，会分配对应的UL grant，该UL grant可用来发送上行数据。
在上述实现过程中，应理解：
1)多bit SR可携带待上报数据量的LCG个数
UE发送SR，通过多bit显示携带SR类型，可选地，多bit中也可以携带UE有数据待发送的LCG个数，从而辅助eNB来分配合适大小的UL grant供UE来发送BSR；
UE收到UL grant后，按照逻辑信道优先级过程LCP来使用UL grant，即决定如何复用MAC PDU，MAC PDU中包括待发送LCH data和MAC CE(BSR)；
2)UL grant使用时，LCH data和BSR之间顺序可配置
上述LCP过程中，UE会按照一个预先存储的LCH data和MAC CE优先级顺序来决定复用到MAC PDU的顺序，该优先级顺序可由eNB配置；具体配置方式可为：RRC重配、MAC CE或者其他。
可能的LCH data和BSR顺序可能为：
URLLC BSR>URLLC data>eMBB BSR>eMBB data；或者；
URLLC BSR>eMBB BSR>URLLC data>eMBB data；也不排除其他的；
3)BSR格式可能为(NR设计，灵活BSR format，分奇数和偶数LCG个数两种类型)。图5a为一种BSR格式示意图，图5b为另一种BSR格式示意图。图5a中为NR BSR and Truncated NR BSR MAC control element for even N，即N为偶数时，NR BSR和截断NR BSR MAC CE的示意图、图5b中为NR BSR and Truncated NR BSR MAC control element for odd N，即N为奇数时，NR BSR和截断NR BSR MAC CE的示意图。
注：上图中，LCG ID为逻辑信道标识，对应LCG待发送的数据量多少可用buffer size表示。
4)BSR发送(截断BSR发送，以及BSR中LCG ID按照降序排列)
当UL grant大于所有有数据包待发送的LCG组成的BSR和BSR对应的子头subheader 之和时，可将所有有数据待发送的LCG对应的BSR上报给基站；即完整的BSR；反之；如果UL grant不足，上报截断BSR，尽可能多上报待发送数据的LCG的buffer size，且各LCG按照LCG组中最高LCH的优先级进行排序——(BSR中上报的LCG ID按照降序排列)
特别地，区别于现有LTE固定BSR format(只有short和long BSR两种，分别对应1个和4个LCG)，NR BSR format更加灵活，且只上报有数据待发送的LCG buffer size；
S208：UE在第二上行资源上向eNB发送数据。
当第二上行资源有剩余时，可用剩余资源来发送padding BSR；如果剩余bit数目大于所有有数据包待发送的LCG组成的BSR和BSR对应的子头subheader之和时，可将所有有数据待发送的LCG对应的BSR上报给基站；
否则，上报截断BSR，尽可能多上报待发送数据的LCG组成的BSR，且各LCG按照LCG组中最高LCH的优先级进行排序——(BSR中上报的LCG ID按照降序排列)
上述实施例中，BSR中待发送的数据包括无线链路控制层(Radio Link Control，RLC)实体和分组数据汇聚层(Packet Data Convergence Protocol，PDCP)实体中的数据，但不包括RLC header和PDCP header；其中，RLC位于MAC层之上，PDCP位于RLC层之上；
特殊地，5G在PDCP层之上引入一个新层(例如SDAP:Service Data Adaptation Protocol)，用于QoS flow和数据无线承载DRB(Data Radio Bearer)之间的映射，可选地，在计算BSR待上报数据量时，可考虑此新层中待发送数据量，但不考虑新层协议数据单元PDU(Protocol Data Unit)的header
在上述实施例中，UE区分待定(pending)SR的类型，通过区分SR类型，UE在识别不同SR类型后，可采取不同的处理方式，如快速触发/发送SR；配置不同的SR相关参数——sr-prohibitTimer和logicalChannelSR-ProhibitTimer。并且UE可通过显示或隐式的方式将SR类型信息告知eNB，从而辅助eNB实现区分类型调度。通过该种方式，UE对高优先级LCH data到达触发的SR，可以快速指示物理层Signal SR，并且在发送SR过程中通过显示或隐式携带优先级信息方式，来辅助eNB快速调度下行资源，以此减小调度时延，并且可以是基站合理分配资源。
基于上述实例中，以eNB以及UE为接入网设备和终端设备为例，对实施例二中涉及到的不同类型的待定SR去如何进行取消再次进行说明：
当spending SR满足以下任一个条件时，该spending SR将会被取消：
Option 1：MAC PDU组包，并且在该PDU包中携带对应BSR。
Option 2：上层配置了免授权(grant-free)资源，——SR可以取消，不用前两步。
Option 3：分配的UL grant足够用来发送数据。
Option 4：不同类型的pending SR，只有收到了对应SR类型申请的UL grant，才会取消其pending SR。
所述option 2和option4是相比LTE，新增加的case；option2中的grant-free方式相当 于为UE预配置了资源，UE有了该资源，只要有数据包待发送，可以直接发，无需通过调度方式来申请UL grant。
随着5G技术的飞速发展，5G业务种类繁多，不同业务的需求不同，本申请实施例提出的上行传输资源的调度方法，提出区分不同SR类型，如优先级，对高优先级SR，可以快速指示物理层Signal SR，并且在发送SR过程中通过显示或隐式携带SR类型信息携带给eNB，从而辅助eNB区分不同业务的调度需求；快速且分配合理的UL grant，并且UE可以在满足一定条件下取消调度请求的发送，进一步节省资源。
图6为本申请实施例提供的终端设备实施例一的结构示意图；如图6所示，该终端设备100包括：
处理模块101，用于当终端设备的第一逻辑信道存在待发送数据而触发第一BSR时，根据预先获取的第一指示信息确定第一调度请求；所述第一指示信息用于指示逻辑信道与调度请求的类型之间的对应关系；所述第一调度请求包括用于指示所述终端设备所需的上行调度信息的第一调度请求类型；
发送模块102，用于向接入网设备发送所述第一调度请求；
接收模块103，用于接收所述接入网设备发送的第一上行调度信息；所述上行调度信息用于指示用于所述终端设备向所述接入网设备发送上行数据的第一上行资源。
本实施例提供的终端设备，用于执行前述任一实施例中终端设备侧的技术方案，当终端设备的第一逻辑信道存在待发送数据而触发第一BSR时，处理模块根据预先获取的第一指示信息确定第一调度请求，向接入网设备发送携带类型信息的第一调度请求，接入网设备根据调度请求的类型为终端设备分配上行资源，并通知该终端设备，处理模块根据逻辑信道与类型的对应关系，在给接入网设备发送调度请求时携带调度请求的类型，接入网设备可以根据调度请求的类型区分业务的调度请求，快速合理的为终端设备调度资源。
在终端设备的实施例二中，所述发送模块102还用于在所述第一上行资源上发送上行数据；所述上行数据包括所述第一BSR，或者所述第一BSR和待发送数据。
可选的，所述接收模块103还用于接收所述接入网设备发送的第二上行调度信息；所述第二上行调度信息用于指示所述接入网设备根据所述第一BSR为所述终端设备配置的、向所述接入网设备发送缓存的待发送数据的第二上行资源；
所述发送模块102还用于在所述第二上行资源上发送待发送数据。
可选的，所述接收模块103还用于接收所述接入网设备发送的所述第一指示信息。
可选的，所述第一指示信息还包括：
逻辑信道与调度请求的类型之间的对应关系；
或者，
逻辑信道与资源使用属性之间的对应关系，以及资源使用属性与调度请求的类型之间的对应关系；
或者，
调度请求的类型与业务组的对应关系，以及逻辑信道与业务优先级的对应关系；
或者，
调度请求的类型与逻辑信道优先级的对应关系。
可选的，所述发送模块102具体用于：
在所述第一调度请求的类型对应的PUCCH上向所述接入网设备发送所述第一调度请求；
或者，
在可用的PUCCH上向所述接入网设备发送所述第一调度请求。
可选的，所述第一逻辑信道用于发送高优先级的业务数据。
可选的，所述第一逻辑信道的调度请求禁止定时器的时长小于其他逻辑信道的调度请求禁止定时器的时长。
可选的，所述终端设备对应的调度请求禁止定时器在确定所述第一BSR为所述第一逻辑信道存在待发送数据触发时去使能。
可选的，所述处理模块101还用于检测到满足调度请求取消条件时，将所述第一调度请求取消；所述调度请求取消条件包括以下任一个条件：
所述第一BSR被携带在待发送的MAC PDU中；
所述接入网设备已经分配给所述终端设备的上行资源足够传输所有待发送数据；
所述终端设备已经收到所述接入网设备分配的所述第一调度请求的类型对应的上行资源；
所述接入网设备为所述终端设备配置了免授权的上行资源。
上述任一实施例提供的终端设备，用于执行前述任一实施例中终端设备的技术方案，其实现原理和技术效果类似，在此不再赘述。
图7为本申请实施例提供的接入网设备实施例一的结构示意图；如图7所示，该接入网设备200包括：
接收模块201，用于接收终端设备发送的第一调度请求；所述第一调度请求包括用于指示所述终端设备所需的上行调度信息的第一调度请求类型；
处理模块202，用于确定所述第一调度请求的类型，并根据所述第一调度请求的类型为所述终端设备调度用于发送上行数据的第一上行资源；
发送模块203，用于向所述终端设备发送第一上行调度信息，所述第一上行调度信息用于指示所述第一上行资源。
本实施例提供的接入网设备，用于实现前述任一实施例中接入网设备侧的技术方案，接收模块接收到的调度请求携带调度请求的类型，处理模块可以根据该调度请求的信道或者数量或者携带的信息确定调度请求的类型，再根据调度请求的类型区分业务的调度请求，快速合理的为终端设备调度资源。
可选的，所述接收模块201还用于接收所述终端设备在所述第一上行资源上发送的上行数据，所述上行数据包括第一BSR，或者所述第一BSR和数据。
可选的，所述处理模块202还用于根据所述第一BSR为所述终端设备调度用于上传数据的第二上行资源；
所述发送模块203还用于向所述终端设备发送第二上行调度信息，所述第二上行调度信息用于指示所述第二上行资源；
所述接入网设备在所述第二上行资源上接收所述终端设备发送的数据。
可选的，所述发送模块203还用于向所述终端设备发送第一指示信息；所述第一指示信息用于指示逻辑信道与调度请求的类型之间的对应关系。
可选的，所述第一指示信息包括：
逻辑信道与调度请求的类型之间的对应关系；
或者，
逻辑信道与资源使用属性之间的对应关系，以及资源使用属性与调度请求的类型之间的对应关系；
或者，
调度请求的类型与业务组的对应关系，以及逻辑信道与业务优先级的对应关系；
或者，
调度请求的类型与逻辑信道优先级的对应关系。
可选的，所述处理模块202具体用于：
根据接收所述第一调度请求的物理下行控制信道PUCCH以及预先配置的调度请求的类型与PUCCH之间的对应关系，确定所述第一调度请求的类型；
或者，
根据预设时长内接收到的第一调度请求的数量确定所述第一调度请求的类型。
上述任一实施例提供的接入网设备，用于执行前述任一实施例中接入网设备的技术方案，其实现原理和技术效果类似，在此不再赘述。
应理解，在上述终端设备和接入网设备具体实现中，处理模块可以被具体实现为处理器，发送模块可以被实现为发送器，接收模块可以被时限为接收器。
本申请实施例第五方面提供一种终端设备，包括：存储器、处理器、发送器、接收器以及计算机程序，所述计算机程序存储在所述存储器中，所述处理器运行所述计算机程序执行任一实施例提供的上行传输资源的调度方法。
在上述终端设备的具体实现中，处理器的数量为至少一个，用来执行存储器存储的执行指令，即计算机程序。使得发送设备通过通信接口与接入网设备之间进行数据交互来执行上述的各种实施方式提供的上行传输资源的调度方法，可选的，存储器还可以集成在处理器内部。
本申请实施例第六方面提供一种接入网设备，包括：存储器、处理器、接收器、发送器以及计算机程序，所述计算机程序存储在所述存储器中，所述处理器运行所述计算机程序执行上述任一实施例提供的上行传输资源的调度方法。
在上述接入网设备的具体实现中，处理器的数量为至少一个，用来执行存储器存储的执行指令，即计算机程序。使得接入网设备通过通信接口与终端设备之间进行数据交互，来执行上述的各种实施方式提供的上行传输资源的调度方法，可选的，存储器还可以集成在处理器内部。
本申请实施例第七方面提供一种存储介质，包括：可读存储介质和计算机程序，所述计算机程序用于实现第一方面任一实施例提供的上行传输资源的调度方法中终端设备侧的方案。
本申请实施例第八方面提供一种存储介质，包括：可读存储介质和计算机程序，所述计算机程序用于实现任一实施例提供的上行传输资源的调度方法中接入网设备侧的方案。
本申请实施例第九方面提供一种程序产品，该程序产品包括计算机程序(即执行指令)，该计算机程序存储在可读存储介质中。终端设备的至少一个处理器可以从可读存储 介质读取该计算机程序，至少一个处理器执行该计算机程序使得终端设备实施上述的各种实施方式提供的上行传输资源的调度方法。
本申请实施例还提供一种程序产品，该程序产品包括计算机程序(即执行指令)，该计算机程序存储在可读存储介质中。接入网设备的至少一个处理器可以从可读存储介质读取该计算机程序，至少一个处理器执行该计算机程序使得接入网设备实施上述的各种实施方式提供的上行传输资源的调度方法。
在终端设备或者接入网设备的具体实现中，应理解，处理器可以是中央处理单元(英文：Central Processing Unit，简称：CPU)，还可以是其他通用处理器、数字信号处理器(英文：Digital Signal Processor，简称：DSP)、专用集成电路(英文：Application Specific Integrated Circuit，简称：ASIC)等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
实现上述各方法实施例的全部或部分步骤可以通过程序指令相关的硬件来完成。前述的程序可以存储于一可读取存储器中。该程序在执行时，执行包括上述各方法实施例的步骤；而前述的存储器(存储介质)包括：只读存储器(英文：read-only memory，缩写：ROM)、RAM、快闪存储器、硬盘、固态硬盘、磁带(英文：magnetic tape)、软盘(英文：floppy disk)、光盘(英文：optical disc)及其任意组合。

Claims (35)

  1. 一种上行传输资源的调度方法，其特征在于，所述方法包括：
    当终端设备的第一逻辑信道存在待发送数据而触发第一缓存状态报告BSR时，根据预先获取的第一指示信息确定第一调度请求；所述第一指示信息用于指示逻辑信道与调度请求的类型之间的对应关系；所述第一调度请求包括用于指示所述终端设备所需的上行调度信息的第一调度请求类型；
    向接入网设备发送所述第一调度请求；
    接收所述接入网设备发送的第一上行调度信息；所述上行调度信息用于指示用于所述终端设备向所述接入网设备发送上行数据的第一上行资源。
  2. 据权利要求1所述的方法，其特征在于，所述方法还包括：
    在所述第一上行资源上发送上行数据；所述上行数据包括所述第一BSR，或者所述第一BSR和待发送数据。
  3. 根据权利要求2所述的方法，其特征在于，所述方法还包括：
    接收所述接入网设备发送的第二上行调度信息；所述第二上行调度信息用于指示所述接入网设备根据所述第一BSR为所述终端设备配置的、向所述接入网设备发送缓存的待发送数据的第二上行资源；
    在所述第二上行资源上发送待发送数据。
  4. 根据权利要求1至3任一项所述的方法，其特征在于，所述当终端设备的第一逻辑信道存在待发送数据而触发第一缓存状态报告BSR时，根据预先获取的第一指示信息确定第一调度请求之前，所述方法还包括：
    接收所述接入网设备发送的所述第一指示信息。
  5. 根据权利要求1至4任一项所述的方法，其特征在于，所述第一指示信息还包括：
    逻辑信道与调度请求的类型之间的对应关系；
    或者，
    逻辑信道与资源使用属性之间的对应关系，以及资源使用属性与调度请求的类型之间的对应关系；
    或者，
    调度请求的类型与业务组的对应关系，以及逻辑信道与业务优先级的对应关系；
    或者，
    调度请求的类型与逻辑信道优先级的对应关系。
  6. 根据权利要求1至5任一项所述的方法，其特征在于，向接入网设备发送所述第一调度请求，包括：
    指示物理层在所述第一调度请求的类型对应的物理下行控制信道PUCCH上向所述接入网设备发送所述第一调度请求；
    或者，
    指示物理层在可用的PUCCH上向所述接入网设备发送所述第一调度请求。
  7. 根据权利要求1至6任一项所述的方法，其特征在于，所述第一逻辑信道用于发送高优先级的业务数据。
  8. 根据权利要求7所述的方法，其特征在于，所述第一逻辑信道的调度请求禁止定时器的时长小于其他逻辑信道的调度请求禁止定时器的时长。
  9. 根据权利要求7所述的方法，其特征在于，所述终端设备对应的调度请求禁止定时器在确定所述第一BSR为所述第一逻辑信道存在待发送数据触发时去使能。
  10. 根据权利要求1至9任一项所述的方法，其特征在于，向接入网设备发送所述第一调度请求之前，所述方法还包括：
    检测到满足调度请求取消条件时，将所述第一调度请求取消；所述调度请求取消条件包括以下任一个条件：
    所述第一BSR被携带在待发送的媒体接入控制协议数据单元MAC PDU中；
    所述接入网设备已经分配给所述终端设备的上行资源足够传输所有待发送数据；
    所述终端设备已经收到所述接入网设备分配的所述第一调度请求的类型对应的上行资源；
    所述接入网设备为所述终端设备配置了免授权的上行资源。
  11. 一种上行传输资源的调度方法，其特征在于，所述方法包括：
    接收终端设备发送的第一调度请求；所述第一调度请求包括用于指示所述终端设备所需的上行调度信息的第一调度请求类型；
    确定所述第一调度请求的类型，并根据所述第一调度请求的类型为所述终端设备调度用于发送上行数据的第一上行资源；
    向所述终端设备发送第一上行调度信息，所述第一上行调度信息用于指示所述第一上行资源。
  12. 根据权利要求11所述的方法，其特征在于，所述方法还包括：
    接收所述终端设备在所述第一上行资源上发送的上行数据，所述上行数据包括第一缓存状态报告BSR，或者所述第一BSR和数据。
  13. 根据权利要求12所述的方法，其特征在于，所述方法还包括：
    根据所述第一BSR为所述终端设备调度用于上传数据的第二上行资源；
    向所述终端设备发送第二上行调度信息，所述第二上行调度信息用于指示所述第二上行资源；
    在所述第二上行资源上接收所述终端设备发送的数据。
  14. 根据权利要求11至13任一项所述的方法，其特征在于，接收终端设备发送的第一调度请求之前，所述方法还包括：
    向所述终端设备发送第一指示信息；所述第一指示信息用于指示逻辑信道与调度请求的类型之间的对应关系。
  15. 根据权利要求14所述的方法，其特征在于，所述第一指示信息包括：
    逻辑信道与调度请求的类型之间的对应关系；
    或者，
    逻辑信道与资源使用属性之间的对应关系，以及资源使用属性与调度请求的类型之间的对应关系；
    或者，
    调度请求的类型与业务组的对应关系，以及逻辑信道与业务优先级的对应关系；
    或者，
    调度请求的类型与逻辑信道优先级的对应关系。
  16. 根据权利要求11至15任一项所述的方法，其特征在于，确定所述第一调度请求的类型，包括：
    根据接收所述第一调度请求的物理下行控制信道PUCCH以及预先配置的调度请求的类型与PUCCH之间的对应关系，确定所述第一调度请求的类型；
    或者，
    根据预设时长内接收到的第一调度请求的数量确定所述第一调度请求的类型。
  17. 一种上行传输资源的调度装置，其特征在于，所述装置包括：
    处理模块，用于当终端设备的第一逻辑信道存在待发送数据而触发第一缓存状态报告BSR时，根据预先获取的第一指示信息确定第一调度请求；所述第一指示信息用于指示逻辑信道与调度请求的类型之间的对应关系；所述第一调度请求包括用于指示所述终端设备所需的上行调度信息的第一调度请求类型；
    发送模块，用于向接入网设备发送所述第一调度请求；
    接收模块，用于接收所述接入网设备发送的第一上行调度信息；所述上行调度信息用于指示用于所述终端设备向所述接入网设备发送上行数据的第一上行资源。
  18. 据权利要求17所述的装置，其特征在于，所述发送模块还用于在所述第一上行资源上发送上行数据；所述上行数据包括所述第一BSR，或者所述第一BSR和待发送数据。
  19. 根据权利要求18所述的装置，其特征在于，所述接收模块还用于接收所述接入网设备发送的第二上行调度信息；所述第二上行调度信息用于指示所述接入网设备根据所述第一BSR为所述终端设备配置的、向所述接入网设备发送缓存的待发送数据的第二上行资源；
    所述发送模块还用于在所述第二上行资源上发送待发送数据。
  20. 根据权利要求17至19任一项所述的装置，其特征在于，所述接收模块还用于接收所述接入网设备发送的所述第一指示信息。
  21. 根据权利要求17至20任一项所述的装置，其特征在于，所述第一指示信息还包括：
    逻辑信道与调度请求的类型之间的对应关系；
    或者，
    逻辑信道与资源使用属性之间的对应关系，以及资源使用属性与调度请求的类型之间的对应关系；
    或者，
    调度请求的类型与业务组的对应关系，以及逻辑信道与业务优先级的对应关系；
    或者，
    调度请求的类型与逻辑信道优先级的对应关系。
  22. 根据权利要求17至21任一项所述的装置，其特征在于，所述发送模块具体用于：
    在所述第一调度请求的类型对应的物理下行控制信道PUCCH上向所述接入网设备发送所述第一调度请求；
    或者，
    在可用的PUCCH上向所述接入网设备发送所述第一调度请求。
  23. 根据权利要求17至11任一项所述的装置，其特征在于，所述第一逻辑信道用于发送高优先级的业务数据。
  24. 根据权利要求17至23任一项所述的装置，其特征在于，所述处理模块还用于检测到满足调度请求取消条件时，将所述第一调度请求取消；所述调度请求取消条件包括以下任一个条件：
    所述第一BSR被携带在待发送的媒体接入控制协议数据单元MAC PDU中；
    所述接入网设备已经分配给所述终端设备的上行资源足够传输所述待发送数据；
    所述终端设备已经收到所述接入网设备分配的所述第一调度请求的类型对应的上行资源；
    所述接入网设备为所述终端设备配置了免授权的上行资源。
  25. 一种上行传输资源的调度装置，其特征在于，所述装置包括：
    接收模块，用于接收终端设备发送的第一调度请求；所述第一调度请求包括用于指示所述终端设备所需的上行调度信息的第一调度请求类型；
    处理模块，用于确定所述第一调度请求的类型，并根据所述第一调度请求的类型为所述终端设备调度用于发送上行数据的第一上行资源；
    发送模块，用于向所述终端设备发送第一上行调度信息，所述第一上行调度信息用于指示所述第一上行资源。
  26. 根据权利要求25所述的装置，其特征在于，所述接收模块还用于接收所述终端设备在所述第一上行资源上发送的上行数据，所述上行数据包括第一缓存状态报告BSR，或者所述第一BSR和数据。
  27. 根据权利要求26所述的装置，其特征在于，所述处理模块还用于根据所述第一BSR为所述终端设备调度用于上传数据的第二上行资源；
    所述发送模块还用于向所述终端设备发送第二上行调度信息，所述第二上行调度信息用于指示所述第二上行资源；
    所述接入网设备在所述第二上行资源上接收所述终端设备发送的数据。
  28. 根据权利要求25至27任一项所述的装置，其特征在于，所述发送模块还用于向所述终端设备发送第一指示信息；所述第一指示信息用于指示逻辑信道与调度请求的类型之间的对应关系。
  29. 根据权利要求28所述的装置，其特征在于，所述第一指示信息包括：
    逻辑信道与调度请求的类型之间的对应关系；
    或者，
    逻辑信道与资源使用属性之间的对应关系，以及资源使用属性与调度请求的类型之间的对应关系；
    或者，
    调度请求的类型与业务组的对应关系，以及逻辑信道与业务优先级的对应关系；
    或者，
    调度请求的类型与逻辑信道优先级的对应关系。
  30. 根据权利要求25至29任一项所述的装置，其特征在于，所述处理模块具体用于：
    根据接收所述第一调度请求的物理下行控制信道PUCCH以及预先配置的调度请求的类型与PUCCH之间的对应关系，确定所述第一调度请求的类型；
    或者，
    根据预设时长内接收到的第一调度请求的数量确定所述第一调度请求的类型。
  31. 一种终端设备，其特征在于，包括：存储器、处理器、发送器、接收器以及计算机程序，所述计算机程序存储在所述存储器中，所述处理器运行所述计算机程序执行权利要求1至10任一项所述的上行传输资源的调度方法。
  32. 一种接入网设备，其特征在于，包括：存储器、处理器、接收器、发送器以及计算机程序，所述计算机程序存储在所述存储器中，所述处理器运行所述计算机程序执行权利要求11至16任一项所述的上行传输资源的调度方法。
  33. 一种计算机程序产品，其特征在于，该计算机程序产品包括：计算机程序代码，当该计算机程序代码被通信设备运行时，使得所述通信设备执行权利要求1至16中任一项所述的方法。
  34. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有计算机指令，所述计算机指令使得通信设备执行权利要求1至16中任一项所述的方法。
  35. 一种上行传输资源的调度装置，其特征在于，所述装置包括处理器和存储介质，所述存储介质存储有指令，所述指令被所述处理器运行时，使得所述处理器执行根据权利要求1至16中任一项所述的方法。
PCT/CN2018/085482 2017-05-03 2018-05-03 上行传输资源的调度方法和设备 Ceased WO2018202087A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP18795055.5A EP3614776B1 (en) 2017-05-03 2018-05-03 Uplink transmission resource scheduling method and device
US16/671,768 US11606803B2 (en) 2017-05-03 2019-11-01 Resource allocation and scheduling using a buffer status report (BSR)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710307267.9A CN108811099B (zh) 2017-05-03 2017-05-03 上行传输资源的调度方法和设备
CN201710307267.9 2017-05-03

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/671,768 Continuation US11606803B2 (en) 2017-05-03 2019-11-01 Resource allocation and scheduling using a buffer status report (BSR)

Publications (1)

Publication Number Publication Date
WO2018202087A1 true WO2018202087A1 (zh) 2018-11-08

Family

ID=64015774

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/085482 Ceased WO2018202087A1 (zh) 2017-05-03 2018-05-03 上行传输资源的调度方法和设备

Country Status (4)

Country Link
US (1) US11606803B2 (zh)
EP (1) EP3614776B1 (zh)
CN (1) CN108811099B (zh)
WO (1) WO2018202087A1 (zh)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111800866A (zh) * 2019-08-15 2020-10-20 维沃移动通信有限公司 资源请求方法、资源分配方法、装置、设备及介质
WO2020220954A1 (zh) * 2019-04-28 2020-11-05 华为技术有限公司 一种确定调度优先级的方法及装置
US11039463B2 (en) * 2017-05-19 2021-06-15 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Method for uplink control information transmission, terminal device and access network device
CN114616912A (zh) * 2020-01-15 2022-06-10 Oppo广东移动通信有限公司 数据传输方法、设备及存储介质
CN114640906A (zh) * 2020-11-28 2022-06-17 华为技术有限公司 传输调度的方法、装置、计算设备和存储介质
CN114765894A (zh) * 2021-01-12 2022-07-19 大唐移动通信设备有限公司 数据传输方法、装置、网络设备、终端及存储介质

Families Citing this family (29)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11219052B2 (en) * 2017-05-05 2022-01-04 Telefonaktiebolaget Lm Ericsson (Publ) SR-BSR and resource management
EP3666016B1 (en) * 2017-08-07 2021-06-23 Telefonaktiebolaget LM Ericsson (publ) Dual strategy for short physical uplink control channel (spucch) utilization
CN109392009A (zh) * 2017-08-11 2019-02-26 华为技术有限公司 数据传输方法、设备和通信系统
KR20200053513A (ko) * 2017-09-21 2020-05-18 광동 오포 모바일 텔레커뮤니케이션즈 코포레이션 리미티드 정보 전송 방법 및 기기
EP3711426A1 (en) 2017-11-14 2020-09-23 IDAC Holdings, Inc. Supplementary uplink transmissions in wireless systems
US20210345302A1 (en) * 2018-11-01 2021-11-04 Sony Corporation Telecommunications apparatus and methods
WO2020113433A1 (zh) * 2018-12-04 2020-06-11 Oppo广东移动通信有限公司 一种处理调度请求的方法及装置、终端
CN111294936B (zh) 2018-12-06 2023-04-14 大唐移动通信设备有限公司 一种传输方法及终端
CN111356172B (zh) * 2018-12-20 2022-04-12 华为技术有限公司 通信方法、装置、终端、网络设备及存储介质
CN111432432B (zh) * 2019-01-10 2022-04-22 华为技术有限公司 数据传输方法和设备
WO2020197482A1 (en) * 2019-03-28 2020-10-01 Telefonaktiebolaget Lm Ericsson (Publ) User equipment, radio network node and methods performed therein for handling communication
WO2020193012A1 (en) * 2019-03-28 2020-10-01 Sony Corporation Communications device, infrastructure equipment and methods
CN112242877B (zh) * 2019-07-16 2023-06-06 华为技术有限公司 数据传输方法、装置及系统
CN111836381B (zh) * 2019-08-16 2023-09-08 维沃移动通信有限公司 传输方法、配置pucch的方法和设备
CN112449434B (zh) * 2019-08-28 2025-04-08 中国移动通信有限公司研究院 一种信息传输方法、装置和计算机可读存储介质
CN114364040B (zh) * 2019-10-30 2024-03-22 Oppo广东移动通信有限公司 无线通信方法和终端设备
US11540166B2 (en) * 2019-12-05 2022-12-27 Qualcomm Incorporated Procedures for managing quality of service flows
WO2022006915A1 (zh) * 2020-07-10 2022-01-13 Oppo广东移动通信有限公司 上行数据传输方法、装置、终端及存储介质
CN115918219B (zh) * 2020-08-24 2024-11-19 Oppo广东移动通信有限公司 信息传输方法、装置、设备及存储介质
CN114375047A (zh) * 2020-10-15 2022-04-19 大唐移动通信设备有限公司 资源调度方法、系统、设备及存储介质
CN114828272B (zh) * 2021-01-28 2025-08-29 大唐移动通信设备有限公司 一种信息传输方法及装置
WO2023283793A1 (zh) * 2021-07-12 2023-01-19 Oppo广东移动通信有限公司 传输资源的请求方法、装置、设备及存储介质
CN114710837B (zh) * 2022-04-25 2024-12-27 中国联合网络通信集团有限公司 一种上行资源块分配方法、感知终端和接入网设备
WO2024031396A1 (zh) * 2022-08-09 2024-02-15 北京小米移动软件有限公司 逻辑信道的调度方法、装置、通信设备及存储介质
CN115426319B (zh) * 2022-08-30 2024-09-06 商飞智能技术有限公司 一种网络资源调度系统
WO2024065109A1 (zh) * 2022-09-26 2024-04-04 北京小米移动软件有限公司 信息传输控制方法、装置、通信设备及存储介质
CN118158819A (zh) * 2022-12-05 2024-06-07 维沃移动通信有限公司 资源分配方法、装置、终端及网络侧设备
CN118785231A (zh) * 2023-04-04 2024-10-15 维沃移动通信有限公司 时延信息报告调度请求sr的发送方法及装置
WO2025018605A1 (en) * 2023-07-18 2025-01-23 Lg Electronics Inc. Method and apparatus for transmitting protocol data unit based on maximum size of control element in wireless communication system

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 大唐移动通信设备有限公司 长期演进系统中资源调度方法、系统及设备
CN102316582A (zh) * 2010-07-06 2012-01-11 中兴通讯股份有限公司 一种上行资源分配方法及系统
US20140204800A1 (en) * 2011-11-04 2014-07-24 Fujitsu Limited Buffer status indication in wireless communication
WO2016186698A1 (en) * 2015-05-21 2016-11-24 Intel IP Corporation Non-contention based low latency scheduling request transmission

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101778418B (zh) * 2009-01-13 2014-03-19 中兴通讯股份有限公司 无线网络中触发或上报调度请求的方法和设备
CA2766903C (en) * 2009-06-29 2018-05-01 Telefonaktiebolaget L M Ericsson (Publ) Method and arrangement in a wireless communication system
CN102685895B (zh) * 2011-03-11 2015-02-04 华为技术有限公司 一种上行数据的调度方法、系统及装置
CN111314955B (zh) * 2013-05-10 2023-04-18 寰发股份有限公司 具有基站之间载波聚合的无线网络中调度请求给多个调度器的增强机制
SG11201606699XA (en) * 2014-02-13 2016-09-29 Lg Electronics Inc Method for transmitting/receiving synchronization signal for d2d communication in wireless communication system, and apparatus therefor
US10098122B2 (en) * 2014-05-15 2018-10-09 Telefonaktiebolaget Lm Ericsson (Publ) System and method for resource allocation for device-to-device communications
US20150341938A1 (en) * 2014-05-22 2015-11-26 Qualcomm Incorporated Uplink operation for rlc communications
CN106162911B (zh) * 2015-04-17 2021-12-07 索尼公司 用于无线通信的电子设备和方法
US10701692B2 (en) * 2015-08-10 2020-06-30 Qualcomm Incorporated Techniques for managing uplink transmissions in a shared radio frequency spectrum band and a dedicated radio frequency spectrum band
US20180152860A1 (en) * 2016-11-28 2018-05-31 Qualcomm Incorporated Buffer status report triggering
US10912110B2 (en) * 2017-03-24 2021-02-02 Sharp Kabushiki Kaisha Systems and methods for an enhanced scheduling request for 5G NR

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 大唐移动通信设备有限公司 长期演进系统中资源调度方法、系统及设备
CN102316582A (zh) * 2010-07-06 2012-01-11 中兴通讯股份有限公司 一种上行资源分配方法及系统
US20140204800A1 (en) * 2011-11-04 2014-07-24 Fujitsu Limited Buffer status indication in wireless communication
WO2016186698A1 (en) * 2015-05-21 2016-11-24 Intel IP Corporation Non-contention based low latency scheduling request transmission

Non-Patent Citations (1)

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

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11039463B2 (en) * 2017-05-19 2021-06-15 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Method for uplink control information transmission, terminal device and access network device
WO2020220954A1 (zh) * 2019-04-28 2020-11-05 华为技术有限公司 一种确定调度优先级的方法及装置
CN111800866A (zh) * 2019-08-15 2020-10-20 维沃移动通信有限公司 资源请求方法、资源分配方法、装置、设备及介质
CN111800866B (zh) * 2019-08-15 2023-09-19 维沃移动通信有限公司 资源请求方法、资源分配方法、装置、设备及介质
CN114616912A (zh) * 2020-01-15 2022-06-10 Oppo广东移动通信有限公司 数据传输方法、设备及存储介质
CN114640906A (zh) * 2020-11-28 2022-06-17 华为技术有限公司 传输调度的方法、装置、计算设备和存储介质
CN114640906B (zh) * 2020-11-28 2023-07-18 华为技术有限公司 传输调度的方法、装置、计算设备和存储介质
CN114765894A (zh) * 2021-01-12 2022-07-19 大唐移动通信设备有限公司 数据传输方法、装置、网络设备、终端及存储介质

Also Published As

Publication number Publication date
CN108811099A (zh) 2018-11-13
US20200068600A1 (en) 2020-02-27
CN108811099B (zh) 2024-07-23
EP3614776A4 (en) 2020-04-08
EP3614776B1 (en) 2023-12-13
US11606803B2 (en) 2023-03-14
EP3614776A1 (en) 2020-02-26

Similar Documents

Publication Publication Date Title
US11606803B2 (en) Resource allocation and scheduling using a buffer status report (BSR)
US11405921B2 (en) Communication method, terminal, and base station
US12185161B2 (en) Scheduling request processing method and terminal device
CN108781465B (zh) 信道接入优先级类别选择
JP2025128227A (ja) 異なる信頼度を有するデータを転送するための方法、システム、およびデバイス
EP3122103B1 (en) Terminal device, base station device, notification system, notification method, and integrated circuit
EP3633892B1 (en) Data transmission method and device, and communication system
CN111264080A (zh) 在无线通信系统中触发发送载波选择的方法和设备
CN118828983A (zh) 用于无线系统中的逻辑信道优先级排序和业务成形的方法
CN109586854B (zh) 数据传输方法及装置
US11134507B2 (en) Method and apparatus for processing scheduling request
EP3119148A1 (en) Terminal device, base station device, communication system, resource management method, and accumulation circuit
CN110583084B (zh) 无线电网络中的方法和装置
KR20180077270A (ko) 피드백을 송수신하는 방법 및 장치
CN113661672A (zh) 用于操作无线通信系统中的配置授权定时器的方法和设备
CN110839284A (zh) 一种调度请求资源确定及配置方法、设备及装置
CN110741674A (zh) 无线通信系统中用于触发缓冲区状态报告的方法和用于该方法的装置
CN114009122A (zh) 用于多个配置授权的方法、通信装置和基础设施设备
CN110447262B (zh) 用于发送分组数据单元的装置和方法
TWI602447B (zh) 回報緩衝區狀態報告的裝置及方法
CN108924877B (zh) 信息的处理方法和设备
CN106488577B (zh) 传输信息的方法和用户设备
CN115314172A (zh) 一种上行控制信息uci发送方法及通信装置
WO2022207903A1 (en) Logical channel priotization within configured grants
WO2025231769A1 (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: 18795055

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

Country of ref document: EP

Effective date: 20191122