WO2024067172A1 - 一种数据传输的方法和装置 - Google Patents

一种数据传输的方法和装置 Download PDF

Info

Publication number
WO2024067172A1
WO2024067172A1 PCT/CN2023/119198 CN2023119198W WO2024067172A1 WO 2024067172 A1 WO2024067172 A1 WO 2024067172A1 CN 2023119198 W CN2023119198 W CN 2023119198W WO 2024067172 A1 WO2024067172 A1 WO 2024067172A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
threshold
delay budget
scheduling request
remaining delay
Prior art date
Application number
PCT/CN2023/119198
Other languages
English (en)
French (fr)
Inventor
陈二凯
秦熠
徐瑞
曹佑龙
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2024067172A1 publication Critical patent/WO2024067172A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/02—Selection of wireless resources by user or terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • 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/50—Allocation or scheduling criteria for wireless resources
    • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/543—Allocation or scheduling criteria for wireless resources based on quality criteria based on requested quality, e.g. QoS

Definitions

  • the embodiments of the present application relate to the field of communications, and more specifically, to a method and device for data transmission.
  • the fifth generation (5G) communication system has gradually infiltrated some multimedia services with strong real-time performance and large data capacity requirements, such as video transmission, cloud gaming (CG) and extended reality (XR). These multimedia services usually have strict requirements on the latency of data transmission. Therefore, how to ensure the latency requirement of data transmission is an issue that needs to be considered.
  • CG cloud gaming
  • XR extended reality
  • the embodiments of the present application provide a communication method and a communication device, so as to complete data transmission within the data delay budget, thereby improving communication performance.
  • a communication method is provided, which can be executed by a terminal device, or by a chip or circuit in the terminal device, or by a logic module or software that can implement all or part of the functions of the terminal device. This application does not limit this.
  • the method includes: receiving first configuration information from a network device, the first configuration information is used to configure a first threshold and a second threshold; sending a scheduling request to the network device, the scheduling request is used to request resources for scheduling data, the scheduling request indicates at least one of the relationship between the remaining delay budget of the data and the first threshold or the relationship between the data volume of the data and the second threshold, the remaining delay budget of the data is the upper limit of the remaining time to complete the data transmission.
  • the terminal device when the terminal device is configured with a threshold of the remaining delay budget of the data (first threshold) and the data volume (second threshold), the terminal device can send a scheduling request to the network device indicating the relationship between the remaining delay budget of the data and the first threshold, and/or the relationship between the data volume and the second threshold, so that the network device can schedule resources for transmitting data according to the scheduling request, reduce the delay of data transmission, and thus improve communication performance.
  • first threshold the remaining delay budget of the data
  • second threshold the terminal device can send a scheduling request to the network device indicating the relationship between the remaining delay budget of the data and the first threshold, and/or the relationship between the data volume and the second threshold, so that the network device can schedule resources for transmitting data according to the scheduling request, reduce the delay of data transmission, and thus improve communication performance.
  • the scheduling request indicates one of the following relationships: the data volume of the data is less than the second threshold; the data volume of the data is greater than or equal to the second threshold and the remaining delay budget of the data is greater than or equal to the first threshold; or, the data volume of the data is greater than or equal to the second threshold and the remaining delay budget of the data is less than the first threshold.
  • the network device can know the relationship between the data volume and the second threshold, or the network device can know the relationship between the remaining delay budget of the data and the first threshold and the relationship between the data volume and the second threshold, which can save signaling overhead.
  • the scheduling request indicates one of the following relationships: the remaining delay budget of the data is greater than or equal to the first threshold; the remaining delay budget of the data is less than the first threshold and the data volume of the data is less than the second threshold; or, the remaining delay budget of the data is less than the first threshold and the data volume of the data is greater than or equal to the second threshold.
  • the network device can know the relationship between the remaining delay budget of the data and the first threshold, or the network device can know the relationship between the remaining delay budget of the data and the first threshold and the relationship between the data volume and the second threshold, which can save signaling overhead.
  • the scheduling request indicates one of the following relationships: the remaining delay budget of the data is greater than or equal to the first threshold and the data volume of the data is less than the second threshold; the remaining delay budget of the data is greater than or equal to the first threshold and the data volume of the data is greater than or equal to the second threshold; the remaining delay budget of the data is less than the first threshold and the data volume of the data is less than the second threshold; or the remaining delay budget of the data is less than the first threshold and the data volume of the data is greater than or equal to the second threshold.
  • the network device can know the relationship between the remaining delay budget of the data and the first threshold and the relationship between the data volume and the second threshold, which can save signaling overhead.
  • the scheduling request is carried by a physical uplink control channel PUCCH format 0.
  • scheduling requests indicating different information can be indicated by different sequence cyclic shift values in PUCCH format 0, which can reduce the complexity of network device processing.
  • second configuration information is received from the network device, and the scheduling request is sent to the network device according to the second configuration information.
  • the terminal device can send a scheduling request indicating the relationship between the remaining delay budget of the data and the first threshold, and/or the relationship between the data volume and the second threshold when configured with the second configuration information.
  • a communication method is provided, which can be executed by a network device, or by a chip or circuit in the network device, or by a logic module or software that can implement all or part of the network device functions. This application does not limit this.
  • the method includes: sending first configuration information to a terminal device, the first configuration information is used to configure a first threshold and a second threshold; receiving a scheduling request from the terminal device, the scheduling request is used to request resources for scheduling data, the scheduling request indicates at least one of the relationship between a remaining delay budget of the data and the first threshold or the relationship between a data volume of the data and the second threshold, the remaining delay budget of the data being an upper limit on the remaining time to complete the data transmission.
  • the terminal device can send a scheduling request indicating the relationship between the remaining delay budget of the data and the first threshold value, and/or the relationship between the data volume and the second threshold value to the network device based on the configuration information, so that resources for transmitting data can be scheduled for the terminal device, reducing the delay of data transmission, thereby improving communication performance.
  • the scheduling request indicates one of the following relationships: the data volume of the data is less than the second threshold; the data volume of the data is greater than or equal to the second threshold and the remaining delay budget of the data is greater than or equal to the first threshold; or, the data volume of the data is greater than or equal to the second threshold and the remaining delay budget of the data is less than the first threshold.
  • the network device can obtain the relationship between the data volume and the second threshold, or can obtain the relationship between the remaining delay budget of the data and the first threshold and the relationship between the data volume and the second threshold, while saving signaling overhead.
  • the scheduling request indicates one of the following relationships: the remaining delay budget of the data is greater than or equal to the first threshold; the remaining delay budget of the data is less than the first threshold and the data volume of the data is less than the second threshold; or, the remaining delay budget of the data is less than the first threshold and the data volume of the data is greater than or equal to the second threshold.
  • the network device can obtain the relationship between the remaining delay budget of the data and the first threshold, or can obtain the relationship between the remaining delay budget of the data and the first threshold and the relationship between the data volume and the second threshold, while saving signaling overhead.
  • the scheduling request indicates one of the following relationships: the remaining delay budget of the data is greater than or equal to the first threshold and the data volume of the data is less than the second threshold; the remaining delay budget of the data is greater than or equal to the first threshold and the data volume of the data is greater than or equal to the second threshold; the remaining delay budget of the data is less than the first threshold and the data volume of the data is less than the second threshold; or, the remaining delay budget of the data is less than the first threshold and the data volume of the data is greater than or equal to the second threshold.
  • the network device can know the relationship between the remaining delay budget of the data and the first threshold and the relationship between the data volume and the second threshold, while saving signaling overhead.
  • the scheduling request is carried by physical uplink control channel PUCCH format 0.
  • scheduling requests indicating different information can be indicated by different sequence cyclic shift values in PUCCH format 0, which can reduce the complexity of network device processing.
  • the method further includes: sending second configuration information to the terminal device, the second configuration information configuring the sending of the scheduling request.
  • the terminal device can send a scheduling request indicating the relationship between the remaining delay budget of the data and the first threshold, and/or the relationship between the data volume and the second threshold, so that resources for transmitting data can be scheduled for the terminal device.
  • a communication method is provided, which can be executed by a terminal device, or by a chip or circuit in the terminal device, or by a logic module or software that can implement all or part of the functions of the terminal device. This application does not limit this.
  • the method includes: receiving fourth configuration information from a network device; sending a scheduling request to the network device according to the fourth configuration information, the scheduling request is used to request resources for scheduling data, the scheduling request indicates the ratio of the data volume of the data to the remaining delay budget of the data, and the remaining delay budget of the data is the upper limit of the remaining time to complete the data transmission.
  • the ratio of the amount of data sent to the remaining delay budget of the data (this ratio can be called the demand rate of the data) enables the network device to schedule the resources for transmitting data according to the demand rate of the data, thereby reducing the delay of data transmission and improving the performance of communication.
  • the scheduling request is carried by physical uplink control channel PUCCH format 0.
  • scheduling requests indicating different information can be indicated by different sequence cyclic shift values in PUCCH format 0, which can reduce the complexity of network device processing.
  • the method further includes receiving fifth configuration information from the network device, the fifth configuration information including a required rate list for data, the required rate list for data including at least one value.
  • the scheduling request indicates a value in the required rate list.
  • possible values of the required rate of data are configured through the fifth configuration information, so that the terminal device can choose to send among the configured values, saving signaling overhead.
  • the scheduling request indicates a relationship between a required rate of data and a value in the required rate list.
  • the possible values of the required rate of the data are configured through the fifth configuration information, so that the terminal device can send the required rate of data in relation to the value in the required rate list, thereby saving signaling overhead.
  • a communication method is provided, which can be executed by a network device, or by a chip or circuit in the network device, or by a logic module or software that can implement all or part of the network device functions. This application does not limit this.
  • the method includes: sending fourth configuration information to a terminal device, the fourth configuration information is used to configure the sending of a scheduling request, the scheduling request indicates the ratio of the data volume to the remaining delay budget of the data; receiving a scheduling request from the terminal device, the remaining delay budget of the data is the upper limit of the remaining time to complete the data transmission.
  • the network device can schedule the resources for transmitting data according to the demand rate of the data, reduce the delay of data transmission, and thus improve the performance of communication.
  • the scheduling request is carried by physical uplink control channel PUCCH format 0.
  • the method further includes sending fifth configuration information to the terminal device, the fifth configuration information including a required rate list for data, the required rate list for data including at least one value.
  • the scheduling request indicates a value in the required rate list.
  • possible values of the required rate of data are configured through the fifth configuration information, so that the terminal device can choose to send among the configured values, saving signaling overhead.
  • the scheduling request indicates a relationship between a required rate of data and a value in the required rate list.
  • the possible values of the required rate of the data are configured through the fifth configuration information, so that the terminal device can send the required rate of data in relation to the value in the required rate list, thereby saving signaling overhead.
  • a communication device which may be a terminal device, or a chip or circuit in a terminal device, or a logic module or software that can implement all or part of the functions of the terminal device, which is not limited in the present application.
  • the device includes an interface unit, which is used to receive first configuration information from a network device, and the first configuration information is used to configure a first threshold and a second threshold; the interface unit is also used to send a scheduling request to the network device, and the scheduling request is used to request resources for scheduling data, and the scheduling request indicates at least one of the relationship between the remaining delay budget of the data and the first threshold or the relationship between the data volume of the data and the second threshold, and the remaining delay budget of the data is the upper limit of the remaining time to complete the data transmission.
  • the scheduling request indicates one of the following relationships: the data volume of the data is less than the second threshold; the data volume of the data is greater than or equal to the second threshold and the remaining delay budget of the data is greater than or equal to the first threshold; or, the data volume of the data is greater than or equal to the second threshold and the remaining delay budget of the data is less than the first threshold.
  • the scheduling request indicates one of the following relationships: the remaining delay budget of the data is greater than or equal to the first threshold; the remaining delay budget of the data is less than the first threshold and the data volume of the data is less than the second threshold; or, the remaining delay budget of the data is less than the first threshold and the data volume of the data is greater than or equal to the second threshold.
  • the scheduling request indicates one of the following relationships: the remaining delay budget of the data is greater than or equal to the first threshold and the data volume of the data is less than the second threshold; the remaining delay budget of the data is greater than or equal to the first threshold and the data volume of the data is greater than or equal to the second threshold; the remaining delay budget of the data is less than the first threshold and the data volume of the data is less than the second threshold; or, the remaining delay budget of the data is less than the first threshold and the data volume of the data is greater than or equal to the second threshold.
  • the scheduling request is carried by physical uplink control channel PUCCH format 0.
  • the interface unit is also used to receive second configuration information from the network device; the communication device also includes a processing unit, which is used to control the device to send the scheduling request to the network device according to the second configuration information.
  • a communication device which may be a network device, or a chip or circuit in a network device, or a logic module or software that can implement all or part of the functions of the network device, which is not limited in the present application.
  • the communication device includes an interface unit, which is used to send first configuration information to a terminal device, and the first configuration information is used to configure a first threshold and a second threshold; the interface unit is also used to receive a scheduling request from the terminal device, and the scheduling request is used to request resources for scheduling data, and the scheduling request indicates at least one of the relationship between the remaining delay budget of the data and the first threshold or the relationship between the data volume of the data and the second threshold, and the remaining delay budget of the data is the upper limit of the remaining time to complete the data transmission.
  • the scheduling request indicates one of the following relationships: the data volume of the data is less than the second threshold; the data volume of the data is greater than or equal to the second threshold and the remaining delay budget of the data is greater than or equal to the first threshold; or, the data volume of the data is greater than or equal to the second threshold and the remaining delay budget of the data is less than the first threshold.
  • the scheduling request indicates one of the following relationships: the remaining delay budget of the data is greater than or equal to the first threshold; the remaining delay budget of the data is less than the first threshold and the data volume of the data is less than the second threshold; or, the remaining delay budget of the data is less than the first threshold and the data volume of the data is greater than or equal to the second threshold.
  • the scheduling request indicates one of the following relationships: the remaining delay budget of the data is greater than or equal to the first threshold and the data volume of the data is less than the second threshold; the remaining delay budget of the data is greater than or equal to the first threshold and the data volume of the data is greater than or equal to the second threshold; the remaining delay budget of the data is less than the first threshold and the data volume of the data is less than the second threshold; or, the remaining delay budget of the data is less than the first threshold and the data volume of the data is greater than or equal to the second threshold.
  • the scheduling request is carried by physical uplink control channel PUCCH format 0.
  • the interface unit is further used to send second configuration information to the terminal device, and the second configuration information configures the sending of the scheduling request.
  • a communication device which may be a terminal device, or a chip or circuit in the terminal device, or a logic module or software that can implement all or part of the functions of the terminal device, which is not limited in the present application.
  • the communication device includes an interface unit and a processing unit, the interface unit is used to receive fourth configuration information from a network device; the processing unit is used to control the device to send a scheduling request to the network device according to the fourth configuration information, the scheduling request is used to request resources for scheduling data, the scheduling request indicates the ratio of the data volume of the data to the remaining delay budget of the data, and the remaining delay budget of the data is the upper limit of the remaining time to complete the data transmission.
  • the scheduling request is carried by physical uplink control channel PUCCH format 0.
  • the interface unit is further used to receive fifth configuration information from the network device, the fifth configuration information including a required rate list for data, and the required rate list for data includes at least one value.
  • the scheduling request indicates a value in the required rate list.
  • the scheduling request indicates a relationship between a required rate of data and a value in the required rate list.
  • a communication device which may be a network device, or a chip or circuit in a network device, or a logic module or software that can implement all or part of the functions of the network device, which is not limited in the present application.
  • the device includes an interface unit, which is used to send fourth configuration information to the terminal device, and the fourth configuration information is used to configure the sending of a scheduling request, and the scheduling request indicates the ratio of the data volume to the remaining delay budget of the data; the interface unit is also used to receive a scheduling request from the terminal device, and the remaining delay budget of the data is the upper limit of the remaining time to complete the data transmission.
  • the scheduling request is carried by physical uplink control channel PUCCH format 0.
  • the interface unit is further used to send fifth configuration information to the terminal device, the fifth configuration information including a required rate list for data, and the required rate list for data includes at least one value.
  • the scheduling request indicates a value in the demand rate list.
  • the scheduling request indicates a relationship between a required rate of data and a value in the required rate list.
  • a communication device comprising a processor, the processor being coupled to a memory, and being configured to execute instructions in the memory to implement any of the first to fourth aspects, and any possible implementation of the first to fourth aspects.
  • the device further comprises a memory, and the memory and the processor may be deployed separately or centrally.
  • the device further comprises a communication interface, and the processor is coupled to the communication interface.
  • the communication interface may be a transceiver, or an input/output interface.
  • the device is a terminal device or a network device, or a chip configured in the terminal device or the network device, and can also be a logic module or software that can realize all or part of the functions of the terminal device or the network device.
  • the communication interface can be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit on the chip or the chip system.
  • the processor can also be embodied as a processing circuit or a logic circuit.
  • the transceiver may be a transceiver circuit.
  • the input/output interface may be an input/output circuit.
  • the processor can be one or more chips
  • the input circuit can be an input pin
  • the output circuit can be an output pin
  • the processing circuit can be a transistor, a gate circuit, a trigger, and various logic circuits.
  • the input signal received by the input circuit can be but not limited to being received and input by the receiver, and the signal output by the output circuit can be but not limited to being output to the transmitter and transmitted by the transmitter, and the input circuit and the output circuit can be the same circuit, which is used as an input circuit and an output circuit at different times.
  • the embodiment of the present application does not limit the specific implementation of the processor and various circuits.
  • a communication device which includes a logic circuit and an input/output interface, wherein the logic circuit is used to couple with the input/output interface and transmit data through the input/output interface to execute any aspect of the first to fourth aspects above, and a method in any possible implementation of the first to fourth aspects.
  • the device is a terminal device or a network device, or a chip configured in the terminal device or the network device, and may also be a logic module or software that can realize all or part of the functions of the terminal device or the network device.
  • the communication interface may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit on the chip or the chip system.
  • the processor may also be embodied as a processing circuit or a logic circuit.
  • the present application provides a chip system, comprising: a processor, the processor being used to execute the computer program or instructions in the memory, so that the chip system implements the method in the above-mentioned first to fourth aspects and any possible implementation method of the first to fourth aspects.
  • the present application provides a chip system, comprising: a terminal device and a network device, the terminal device being used to execute the method in the above-mentioned first aspect or third aspect and any possible implementation of the first aspect or third aspect; the network device being used to execute the method in the above-mentioned second aspect or fourth aspect and any possible implementation of the second aspect or fourth aspect.
  • a computer-readable storage medium which stores a computer program (also referred to as code, or instructions).
  • a computer program also referred to as code, or instructions.
  • a computer program product which includes: a computer program (also referred to as code, or instruction), which, when executed, enables a computer to execute any aspect of the first to fourth aspects above, and a method in any possible implementation of the first to fourth aspects.
  • a computer program also referred to as code, or instruction
  • the beneficial effects brought about by the above-mentioned fifth to fourteenth aspects can refer to the description of the beneficial effects in the first to fourth aspects, and will not be repeated here.
  • FIG1 is a schematic diagram of a system architecture applicable to the present application.
  • FIG. 2 is an interactive flow chart of a method for scheduling data.
  • FIG3 is a schematic diagram of scheduling data under uplink and downlink time slot configuration.
  • FIG4 is an interactive flow chart of a communication method provided in an embodiment of the present application.
  • FIG5 is an interactive flow chart of another communication method provided in an embodiment of the present application.
  • FIG. 6 is a schematic diagram of a communication device provided in an embodiment of the present application.
  • FIG. 7 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application.
  • FIG8 is a schematic diagram of the structure of another communication device provided in an embodiment of the present application.
  • FIG. 9 is a schematic diagram of the structure of another communication device provided in an embodiment of the present application.
  • FIG1 is a schematic diagram of a system architecture applicable to the present application.
  • the communication system 100 shown in FIG1 includes a network device 10 and at least one terminal device, such as a terminal device 20 and a terminal device 21.
  • the terminal device 20 and the terminal device 21 can send uplink data/signals/information to the network device 10; the network device 10 can send downlink data/signals/information to at least one of the terminal device 20 and the terminal device 21.
  • the terminal device 20 can also transmit data/signals/information with the terminal device 21.
  • FIG1 is only a simplified schematic diagram for ease of understanding, and the communication system 100 may also include other network devices or other terminal devices, which are not shown in FIG1 .
  • the above-mentioned network architecture applied to the embodiment of the present application is only an example, and the network architecture applicable to the embodiment of the present application is not limited to this. Any network architecture that can realize the functions of the above-mentioned devices is applicable to the embodiment of the present application.
  • LTE long term evolution
  • FDD frequency division duplex
  • TDD LTE time division duplex
  • UMTS universal mobile telecommunication system
  • 5G fifth generation
  • NR new radio
  • the technical solution provided in the present application can also be applied to machine type communication (MTC), long term evolution-machine (LTE-M), device-to-device (D2D) network, machine-to-machine (M2M) network, Internet of Things (IoT) network or other networks.
  • IoT network can include vehicle networking, for example.
  • vehicle to X, V2X, X can represent anything
  • the V2X can include: vehicle to vehicle (V2V) communication, vehicle to infrastructure (V2I) communication, vehicle to pedestrian (V2P) communication or vehicle to network (V2N) communication, etc.
  • the terminal device in the embodiment of the present application may be a wireless terminal device capable of receiving network device scheduling and indication information.
  • the terminal device may be a device that provides voice and/or data connectivity to a user, or a handheld device with a wireless connection function, or other processing devices connected to a wireless modem.
  • Terminal equipment may also be called terminal, access terminal, user unit, user equipment (UE), user station, mobile Mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication device, user agent or user device.
  • Terminal device is a device that includes wireless communication function (providing voice/data connectivity to the user). For example, a handheld device with wireless connection function, or a vehicle-mounted device, etc.
  • the terminal in the embodiments of the present application can be a mobile phone, a tablet computer (pad), a computer with wireless transceiver function, a train, an airplane, a mobile Internet device (MID), a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control (such as a robot, etc.), a wireless terminal in the Internet of Vehicles (such as an on-board device, a whole vehicle device, an on-board module, a vehicle, etc.), a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a wireless communication device (such as a cellular phone, a wireless communication device ...
  • MID mobile Internet device
  • PDA personal digital assistant
  • handheld devices with wireless communication functions computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminals in 5G networks or terminals in future evolution networks, etc.
  • vehicle-mounted devices wearable devices
  • terminals in 5G networks or terminals in future evolution networks etc.
  • all or part of the functions of the terminal device in this application can also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (such as a cloud platform).
  • wearable devices can also be called wearable smart devices, which are a general term for the intelligent design and development of wearable devices for daily wear using wearable technology, such as glasses, gloves, watches, clothing and shoes.
  • Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothes or accessories.
  • Wearable devices are not only hardware devices, but also realize powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-sized, and independent of smartphones to achieve complete or partial functions, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.
  • the network device in the embodiments of the present application may be a device in a wireless network.
  • the network device may be a device deployed in a wireless access network to provide wireless communication functions for a terminal device.
  • the network device may be a radio access network (RAN) node that connects a terminal device to a wireless network, and may also be referred to as an access network device.
  • RAN radio access network
  • the network equipment includes but is not limited to: evolved Node B (eNB), radio network controller (RNC), Node B (NB), base station controller (BSC), base transceiver station (BTS), home evolved Node B (HeNB, or home Node B, HNB), baseband unit (BBU), server, wearable device, vehicle-mounted equipment, access point (AP) in WIFI system, wireless relay node, wireless backhaul node, transmission point (TP) or transmission and reception point (TRP), etc., and can also be 5G, such as gNB in NR system, or transmission point (TRP or TP), one or a group of (including multiple antenna panels) antenna panels of a base station in 5G system, or, it can also be a network node constituting a gNB or a transmission point, such as a baseband unit (BBU), or a distributed unit (DU), etc.
  • eNB evolved Node B
  • RNC radio network controller
  • NB Node B
  • BSC base station controller
  • BTS base
  • the base station can be a macro base station, a micro base station, a pico base station, a small station, a relay station or a balloon station, etc. It can be understood that all or part of the functions of the network device in this application can also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (such as a cloud platform).
  • the gNB may include a centralized unit (CU) and a DU.
  • the gNB may also include an active antenna unit (AAU).
  • the CU implements some of the gNB functions, and the DU implements some of the gNB functions.
  • the CU is responsible for processing non-real-time protocols and services, and implements the functions of the radio resource control (RRC) and packet data convergence protocol (PDCP) layers.
  • the DU is responsible for processing physical layer protocols and real-time services, and implements the functions of the radio link control (RLC), media access control (MAC) and physical (PHY) layers.
  • the AAU implements some physical layer processing functions, RF processing and related functions of active antennas.
  • the RRC layer information is generated by the CU and will eventually be encapsulated by the PHY layer of the DU to become PHY layer information, or converted from PHY layer information. Therefore, in this architecture, high-level signaling such as RRC layer signaling can also be considered to be sent by the DU, or by the DU+AAU.
  • the network device may be a device including one or more of a CU node, a DU node, and an AAU node.
  • the CU may be classified as a network device in an access network (radio access network, RAN), or the CU may be classified as a network device in a core network (CN), and this application does not limit this.
  • the technologies related to multimedia services are constantly improving and perfecting.
  • these services have strict requirements on network latency.
  • the sampling rate of tactile information should be no less than 1kHz, and the transmission delay requirement for each sample should reach 5ms.
  • the data delay budget can be determined based on the transmission delay requirements of the service.
  • Fig. 2 is an interactive flow chart of a method for scheduling data.
  • the method 200 shown in Fig. 2 may include the following steps.
  • the terminal device sends a scheduling request (SR) to the network device, and the scheduling request is used to request resources for scheduling data.
  • SR scheduling request
  • the network device receives the scheduling request from the terminal device.
  • the terminal device when the terminal device needs to send uplink data, it sends the scheduling request to the network device to request resources for sending the uplink data.
  • the scheduling request may be carried by a physical uplink control channel (PUCCH).
  • the scheduling request may include 1 bit of information for informing the network device whether there is uplink data transmission.
  • the sending period and sending offset (such as time slot offset) of the scheduling request of different logical channels may be the same or different. Different logical channels may be configured separately.
  • the scheduling request can be carried in PUCCH format 0 or PUCCH format 1.
  • PUCCH format 0 can also be used to send ACK/NACK (acknowledgement/negative acknowledgment) feedback of hybrid automatic repeat request (HARQ).
  • the information sent by PUCCH format 0 can include 1 bit or 2 bits (when the corresponding scheduled physical downlink shared channel (PDSCH) includes 2 codewords).
  • PUCCH format 0 can occupy one resource block in the frequency domain and 1-2 symbols in the time domain.
  • PUCCH format 0 can be generated based on a ZC (Zadoff-Chu) sequence.
  • the information carried by the ZC sequence can be indicated by the value of the final sequence cyclic shift.
  • the value of the final sequence cyclic shift can be determined based on the value of the sequence cyclic shift m cs .
  • m cs corresponding to a certain HARQ-ACK information may be determined through the correspondence between the HARQ-ACK information and the sequence cyclic shift of PUCCH format 0.
  • the correspondence between the value of the HARQ-ACK information bit (ie, the HARQ-ACK value) and the sequence cyclic shift of PUCCH format 0 may be as shown in Table 1, that is, m cs corresponding to the HARQ-ACK value may be determined according to the correspondence shown in Table 1.
  • the correspondence between the value of the HARQ-ACK information bit and the sequence cyclic shift of PUCCH format 0 may be as shown in Table 2, that is, m cs corresponding to the HARQ-ACK value may be determined according to the correspondence shown in Table 2.
  • PUCCH format 0 can also carry SR, that is, HARQ-ACK information and scheduling request SR are multiplexed. In other words, SR and HARQ-ACK information can be sent at the same time.
  • the SR is a positive request (i.e., informing the network device that there is data transmission), and the terminal device can also indicate the HARQ-ACK information and the positive SR by cyclic shift.
  • the corresponding relationship between the values of the HARQ-ACK information bit and the forward SR and the sequence cyclic shift of the PUCCH format 0 may be as shown in Table 4.
  • the value of the forward SR is not shown in Table 3 and Table 4 because the forward SR is implicitly indicated and does not actually occupy information bits. That is, when the value of m cs is the value in Table 3 and Table 4, the HARQ-ACK value indicates the forward SR in addition to the HARQ-ACK information.
  • the network device sends scheduling information to the terminal device.
  • the terminal device receives the scheduling information from the network device.
  • the network device in response to the SR sent by the terminal device, sends scheduling information to the terminal device.
  • the scheduling information may include physical uplink shared channel (PUSCH) resource information.
  • PUSCH physical uplink shared channel
  • the scheduling information may be carried by a physical downlink control channel (PDCCH), for example, by sending the scheduling information to the terminal device via downlink control information (DCI) format 0_0 or 0_1.
  • PDCCH physical downlink control channel
  • DCI downlink control information
  • the network device Since the network device does not know the amount of uplink data that the terminal device is about to send, the network device can schedule the terminal device according to a smaller, fixed data amount.
  • the terminal device may continue to send SR.
  • the terminal device sends data to the network device.
  • the network device receives data from the terminal device.
  • the terminal device after receiving the scheduling information from the network device, the terminal device sends data to the network device based on the scheduling information.
  • the scheduling information allocated by the network device may include PUSCH resource information, and the terminal device may send data on the PUSCH resource.
  • the data may include buffer status report (BSR) information, which is used to inform the network device how much data needs to be sent. For example, if the BSR is greater than 0, the network device can continue to schedule the terminal device. That is, the network device can continue to send scheduling information to the terminal device through the PDCCH, so that the terminal device continues to transmit data on the PUSCH resources indicated by the scheduling information.
  • BSR buffer status report
  • the network device can only receive the SR in the uplink time slot due to the ratio and order of the number of uplink time slots and downlink time slots.
  • the time when the terminal device data arrives or the time when the terminal device obtains the data may be earlier than the time corresponding to the uplink time slot. If the data scheduling scheme in method 200 is adopted, the network device may not be able to perceive the exact time when the terminal device obtains the data. In the case where the network device cannot perceive the exact time when the terminal device obtains the data, the scheduling time of the data at the air interface may exceed the delay budget of the data.
  • the TDD time slot configuration is DDDSU
  • the network device uses the SR sending time as the data acquisition time
  • the error can reach 5 time slots compared with the actual data acquisition time. If the system uses 15kHz sub-carrier spacing (SCS), 1 time slot is 1ms, that is, the error can reach 5ms.
  • the TDD time slot configuration is DDDDD DDSUU
  • the network device uses the SR sending time as the data acquisition time
  • the error can reach 9 time slots compared with the actual data acquisition time. If each time slot is 1ms, the error can reach 9ms.
  • D is a downlink time slot
  • U is an uplink time slot
  • S represents a special time slot (special), which may include symbols for uplink transmission and symbols for downlink transmission.
  • the data delay budget is 15ms (1 time slot is 1ms) and the actual data acquisition time is the end time of the first uplink time slot
  • the data may be invalid after the end of the fourth uplink time slot shown in Figure 3. If the network device uses the end time of the second uplink time slot in which the SR is sent as the data acquisition time, the network device will complete the scheduled transmission of the data within 15ms after the second uplink time slot according to the data delay budget, and the data transmitted after the fourth uplink time slot may be invalid.
  • the delay budget of data may be a packet delay budget (PDB).
  • PDB may refer to the maximum value of the transmission delay allowed for a data packet during transmission between a user plane function (UPF) network element and a terminal device.
  • UPF user plane function
  • the PDB in the embodiment of the present application may also be the maximum value of the transmission delay allowed for data transmission between a network device (eg, a base station) and a terminal device.
  • a network device eg, a base station
  • the moment of acquiring data can be understood as the moment when the terminal device acquires the data.
  • the moment of acquiring data can be understood as the moment when the data is delivered to/arrives at a certain protocol layer (such as the MAC layer, the RLC layer, or the PDCP layer, etc.).
  • the moment of acquiring data is the moment when the MAC entity or the RLC entity or the PDCP entity obtains the data.
  • the moment of acquiring data can be expressed as the time slot number or the subframe number or the frame number when the MAC entity or the RLC entity or the PDCP entity obtains the data.
  • the moment of acquiring data can also be understood as the moment when the terminal device is ready to send the data, and the present application does not impose any restrictions on this.
  • the network device's scheduling of the terminal device may have a large delay, or the network device may not be able to complete the data transmission within the data delay budget.
  • the embodiments of the present application provide a communication method and a communication device, so as to reduce the delay of data transmission of a terminal device, complete the data transmission within the data delay budget, and thus improve the communication performance.
  • Figure 4 is a schematic flow chart of a communication method provided by an embodiment of the present application.
  • the interaction flow chart in the present application uses a network device and a terminal device as an example to illustrate the corresponding method, but the present application does not limit the execution subject of the interaction diagram.
  • the network device in the figure may also be a chip, a chip system, or a processor that supports the network device to implement the corresponding method, or a logic module or software that can implement all or part of the functions of the network device;
  • the terminal device in the figure may also be a chip, a chip system, or a processor that supports the terminal device to implement the corresponding method, or a logic module or software that can implement all or part of the functions of the terminal device.
  • the method may include at least the following steps.
  • the network device sends first configuration information to the terminal device.
  • the terminal device receives the first configuration information from the network device.
  • the first configuration information can be used to configure a first threshold and a second threshold.
  • the first threshold can be a threshold of a remaining delay budget of the data or a threshold of a cache duration of the data;
  • the second threshold can be a threshold of a data volume or a threshold of a cache size of a terminal device.
  • the remaining delay budget of the data may refer to the upper limit of the remaining time to complete the data transmission.
  • the remaining delay budget of the data is related to the delay budget of the data and the cache duration of the data.
  • the cache duration of the data may refer to the time between the acquisition time of the data and the transmission time of the data.
  • the transmission time of the data may be the time when the scheduling request is sent.
  • the remaining delay budget of the data may be the difference between the delay budget of the data and the cache duration.
  • the sending time of the scheduling request is understood as the triggering time of the scheduling request or the actual sending time of the scheduling request.
  • the triggering time of the scheduling request may be before the actual sending time of the scheduling request.
  • the time interval between the triggering time of the scheduling request and the actual sending time may be very small, for example, less than 1 millisecond (ms), and this application does not limit this.
  • the number and arrangement order of uplink time units (e.g., time slots) and downlink time units (e.g., time slots) can be preconfigured, so the terminal device can determine the time to send the scheduling request before sending the scheduling request.
  • the TDD time slot configuration is DDDSU
  • the data acquisition time is the end time of the first uplink time slot, and the terminal device can determine to send the scheduling request in the next uplink time slot.
  • the time unit may be a time slot, a frame, a subframe, a time domain symbol, etc., without limitation.
  • the remaining delay budget of the data and the cache duration of the data can be replaced with each other, that is, when the delay budget of the data is known, the cache duration of the data can be determined according to the remaining delay budget of the data, or the remaining delay budget of the data can be determined according to the cache duration of the data.
  • the delay budget of the data is 20ms
  • the acquisition time of the data is 3ms
  • the start time of the uplink time slot for sending the scheduling request is 8ms, that is, the cache duration of the data is 5ms.
  • the delay budget of the data and the cache duration of the data it can be determined that the remaining delay budget of the data is 15ms.
  • the data volume of the data can also be replaced by the cache size of the terminal device.
  • the data volume of the data can be 1000 bytes, which can also be said that the cache size of the terminal device is 1000 bytes.
  • the following mainly uses the first threshold as the remaining delay budget threshold of the data and the second threshold as the data volume threshold as an example to illustrate the method of the embodiment of the present application, but this does not constitute a limitation of the present application.
  • the first configuration information may be a field in scheduling request configuration (SchedulingRequestToAddMod) information or scheduling request resource configuration (SchedulingRequestResourceConfig) information.
  • the first configuration information may include a remaining-Threshold field indicating the first threshold and a BufferSize-Threshold field indicating the second threshold:
  • ms1 1 millisecond (ms)
  • Byte1000 1000 bytes (Byte), and so on.
  • ms1 1 millisecond (ms)
  • Byte1000 1000 bytes (Byte)
  • the terminal device sends a scheduling request to the network device.
  • the network device receives the scheduling request from the terminal device.
  • the scheduling request may be used to request resources for scheduling data.
  • the scheduling request may indicate at least one of a size relationship between a remaining delay budget of the data and the first threshold, or a size relationship between a data volume of the data and the second threshold.
  • the terminal device determines the acquisition time of the data and the data volume of the data.
  • the terminal device may determine the remaining delay budget of the data according to the delay budget of the data and the sending time of the scheduling request.
  • the terminal device determines the size relationship between the remaining delay budget of the data and the first threshold according to the first threshold.
  • the terminal device determines the size relationship between the data volume of the data and the second threshold according to the second threshold.
  • the scheduling request may be carried on a PUCCH.
  • the scheduling request may include information (for convenience of description, recorded as first information) indicating at least one of a relationship between a remaining delay budget of the data and the first threshold, or a relationship between a data volume of the data and the second threshold.
  • the first information may be 2-bit information, and the value and meaning of the 2-bit information may be pre-configured by the protocol.
  • the value and meaning of the 2-bit information may be as shown in any one of Tables 5 to 8.
  • the terminal device may first determine the amount of data. If there is no data or the cache of the terminal device is empty, the value of the 2-bit information may be "00"; if the amount of data is less than the second threshold, the value of the 2-bit information may be "01". When the terminal device determines that the amount of data is greater than or equal to the second threshold, the terminal device may determine the remaining delay budget of the data. If the remaining delay budget of the data is greater than or equal to the first threshold, the value of the 2-bit information may be "10"; if the remaining delay budget of the data is less than the first threshold, the value of the 2-bit information may be "11".
  • the terminal device may first determine whether there is data or whether the buffer of the terminal device is empty. If there is no data or the buffer of the terminal device is empty, the value of the 2-bit information may be "00". When the terminal device determines that there is data or the buffer of the terminal device is not empty, the terminal device may determine the remaining delay budget of the data. If the remaining delay budget of the data is greater than or equal to the first If the remaining delay budget of the data is less than the first threshold, the value of the 2-bit information can be "01". If the terminal device determines that the remaining delay budget of the data is less than the first threshold, the terminal device can determine the amount of data. If the amount of data is less than the second threshold, the value of the 2-bit information can be "10"; if the amount of data is greater than or equal to the second threshold, the value of the 2-bit information can be "11".
  • the terminal device can determine the remaining delay budget of the data and the amount of the data according to Table 7.
  • the terminal device determines the value of the bit information according to the relationship between the remaining delay budget of the data and the first threshold, and the relationship between the amount of the data and the second threshold.
  • the terminal device can determine the remaining delay budget of the data and the data volume of the data. And according to the remaining delay budget of the data being the first value or the second value in the remaining delay budget list, and the data volume of the data being the first value or the second value in the data volume list, the value of the 2-bit information is determined. Among them, the remaining delay budget list and the data volume list can be configured by the network device (refer to the description of the third configuration).
  • Tables 5 to 8 are only examples and do not constitute a limitation of the present application.
  • the meanings represented by the bit information can be replaced with each other.
  • the information used in the scheduling request to indicate at least one of the relationship between the remaining delay budget of the data and the first threshold, or the relationship between the amount of data and the second threshold can be greater than 2 bits, and the bit information greater than 2 bits can indicate any combination of the meanings in Tables 5 to 8; for another example, any one or two bit values in Tables 5 to 8 may not indicate any meaning, or the meaning indicated by the bit information is retained.
  • the scheduling request is carried by PUCCH format 0
  • the information in the scheduling request for indicating at least one of the relationship between the remaining delay budget of the data and the first threshold, or the relationship between the amount of data and the second threshold includes 2 bits
  • the correspondence between the value of the 2-bit information and the value of the sequence cyclic shift can be as shown in Table 9.
  • the sequence cyclic shift value of the PUCCH format 0 is 5.
  • bit information values and sequence cyclic shift values are only examples, and the corresponding relationship between the bit information values and the sequence cyclic shift values is also only an example.
  • the difference between the m cs values corresponding to the bit information ⁇ 0,0 ⁇ , ⁇ 0,1 ⁇ , ⁇ 1,1 ⁇ , ⁇ 1,0 ⁇ can be 3.
  • the value of m cs can also be 0, 3, 6, 9 or 2, 4, 7, 11.
  • the terminal device when the terminal device is configured with a threshold value (first threshold value) of the remaining delay budget of the data and the data volume (second threshold value), the terminal device can send a scheduling request indicating the size relationship between the remaining delay budget of the data and the first threshold value, and/or the size relationship between the data volume of the data and the second threshold value to the network device, so that the network device can schedule the network device according to the scheduling request. It can improve the communication performance by utilizing the resources for transmitting data at a high speed and reducing the delay of data transmission.
  • the method 400 may further include S430, the network device sends second configuration information to the terminal device.
  • the terminal device receives the second configuration information from the network device.
  • the second configuration information may be used to configure the sending of the scheduling request.
  • the second configuration information may be another field in the SchedulingRequestToAddMod information, such as an enhanced-SR field.
  • the enhanced-sr field can be used to configure the sending of a scheduling request. For example, when the enhanced-sr field is configured to be true (or other agreed values), it indicates that a scheduling request is configured for at least one of the relationship between the remaining delay budget for the terminal device to send indication data and the first threshold, or the relationship between the amount of data and the second threshold.
  • the scheduling request may not indicate at least one of the relationship between the remaining delay budget of the data and the first threshold, or the relationship between the amount of data and the second threshold.
  • the scheduling request may refer to the prior art.
  • the method 400 may further include S440, the network device sends third configuration information to the terminal device.
  • the terminal device receives the third configuration information from the network device.
  • the third configuration information is used to configure a remaining delay budget list and a data volume list.
  • the remaining delay budget list may include at least one value of the remaining delay budget of the data; and the data volume list may include at least one value of the data volume of the data.
  • the third configuration information may be a remaining delay list (sr-RemainingPDBList) field and a buffer size (sr-BufferSizeList) field in the SchedulingRequestToAddMod information.
  • sr-RemainingPDBList and sr-BufferSizeList can be configured with at least one value and at most four values.
  • the range of each value in sr-RemainingPDBList is greater than or equal to 0 and less than or equal to 128; the range of each value in sr-BufferSizeList is greater than or equal to 1000 and less than or equal to 1000.
  • the terminal device when different configuration information (for example, first configuration information, second configuration information and third configuration information) are different elements in the same configuration (for example, SchedulingRequestToAddMod), the terminal device can obtain different configuration information by receiving one configuration, or the terminal device can obtain different configuration information by receiving different configurations respectively, and there is no limitation on this.
  • different configuration information for example, first configuration information, second configuration information and third configuration information
  • SchedulingRequestToAddMod when different configuration information (for example, first configuration information, second configuration information and third configuration information) are different elements in the same configuration (for example, SchedulingRequestToAddMod), the terminal device can obtain different configuration information by receiving one configuration, or the terminal device can obtain different configuration information by receiving different configurations respectively, and there is no limitation on this.
  • the method 400 further includes:
  • the network device sends scheduling information to the terminal device.
  • the terminal device receives the scheduling information from the network device.
  • the scheduling information may be used for data scheduling.
  • the network device may determine the scheduling information based on the scheduling request.
  • the scheduling information may include PUSCH resource information.
  • the scheduling information may be carried on the PDCCH.
  • DCI format 0_0 or 0_1 may be used to send the PUSCH resource information to the PDCCH.
  • the terminal device sends scheduling information.
  • the terminal device may continue to send a scheduling request to the network device.
  • the method 400 further includes:
  • the terminal device sends data to the network device.
  • the network device receives data from the terminal device.
  • the data is carried on a PUSCH resource, and the PUSCH resource is indicated by the PUSCH resource indication information.
  • the data may also include BSR information, and the BSR information is used to inform the network device how much data is still to be sent. For example, if the BSR is greater than 0, the network device may continue to configure resources for transmitting data for the terminal device, so that the terminal device continues to transmit the remaining data on the configured resources.
  • Fig. 5 is a schematic flow chart of another communication method provided in an embodiment of the present application. The method includes at least the following steps.
  • S510 The network device sends fourth configuration information to the terminal device.
  • the terminal device receives the fourth configuration information from the network device.
  • the fourth configuration information may be used to configure the sending of the scheduling request, wherein the scheduling request indicates the ratio of the amount of data to the remaining delay budget of the data, wherein the ratio of the amount of data to the remaining delay budget of the data may also be referred to as the required rate of the data.
  • the fifth configuration information may be a field in SchedulingRequestToAddMod information, such as an enhanced-SR (enhanced-sr) field.
  • SchedulingRequestToAddMod information such as an enhanced-SR (enhanced-sr) field.
  • the enhanced-sr field may be used to configure the sending of a scheduling request. For example, when the enhanced-sr field is configured to true (or other agreed values), it indicates that the required rate for the terminal device to send data is configured.
  • the scheduling request may not indicate the required rate of the data.
  • the terminal device sends a scheduling request to the network device.
  • the network device receives the scheduling request from the terminal device.
  • the scheduling request may be used to request resources for scheduling data.
  • the scheduling request may indicate a ratio of the amount of data to the remaining delay budget of the data.
  • the ratio of the amount of data to the remaining delay budget of the data is referred to as the required rate of the data.
  • the terminal device after the terminal device acquires the data, it can determine the acquisition time of the data and the data volume of the data.
  • the terminal device determines the remaining delay budget of the data according to the delay budget of the data and the sending time of the scheduling request.
  • the terminal device determines the required rate of the data according to the data volume and the remaining delay budget of the data.
  • the scheduling request may be carried on a PUCCH, for example, may be carried by PUCCH format 0 or PUCCH format 1.
  • the scheduling request may include information (referred to as second information) for indicating a required rate of data.
  • the second information may be 2-bit information, and the value and meaning of the 2-bit information may be pre-configured by the protocol.
  • the value and meaning of the 2-bit information may be as shown in any one of Table 10 and Table 11.
  • the terminal device can determine the value of the 2-bit information indicating the required rate of the data in the scheduling request according to the required rate of the data and Table 10. For example, if the terminal device determines that the required rate of the data is the first value in the required rate list, then the 2-bit information The value of is "00".
  • the terminal device can determine the value of the 2-bit information indicating the required rate of the data in the scheduling request according to the required rate of the data and Table 11. For example, if the terminal device determines that the required rate of the data is R1, R1 is greater than the first value in the required rate list and less than the second value in the required rate list, then the value of the 2-bit information is "01".
  • the required rate list can refer to the description of the fourth configuration.
  • the values and meanings of the bit information in Tables 10 and 11 are only examples, and the present application does not limit this.
  • the information indicating the required rate of data can be greater than 2 bits, that is, the network device can indicate more required rate values or ranges of required rate values.
  • the scheduling request is carried by PUCCH format 0, and the information in the scheduling request for indicating the required data rate includes 2 bits, the correspondence between the value of the 2-bit information and the value of the sequence cyclic shift can be referred to Table 9 and will not be repeated here.
  • the method 500 further includes S530, the network device sends fifth configuration information to the terminal device.
  • the terminal device receives the fifth configuration information from the network device.
  • the fifth configuration information can be used to configure at least one required rate.
  • the fifth configuration information is a field in the SchedulingRequestToAddMod information, such as a required data rate list (RequiredDataRateList) field.
  • the RequiredDataRateList field is configured with at least one value, and each value in the at least one value may represent a required rate.
  • RequiredDataRateList The number of required rate values configured by RequiredDataRateList and the range of each value can be predefined.
  • the predefined example of RequiredDataRateList is as follows:
  • RequiredDataRateList can be configured with at least one value and at most four values. The range of each value is greater than or equal to 0 and less than or equal to 102400. The above values are only examples. RequiredDataRateList can also be configured with other quantities and ranges of values without restriction.
  • the fourth configuration information configures N values
  • the number of bits included in the information indicating the required data rate is ceil(log2(N)), where ceil represents a ceiling function and N is a positive integer.
  • the terminal device when different configuration information (for example, the fourth configuration information, the fifth configuration information) are different elements in the same configuration (for example, SchedulingRequestToAddMod), the terminal device can obtain different configuration information by receiving one configuration, that is, S510 and S530 can be executed simultaneously, or the terminal device can obtain different configuration information by receiving different configurations respectively, that is, steps S510 and S530 can be executed separately, and there is no limitation on this.
  • different configuration information for example, the fourth configuration information, the fifth configuration information
  • the terminal device when different configuration information (for example, the fourth configuration information, the fifth configuration information) are different elements in the same configuration (for example, SchedulingRequestToAddMod)
  • the terminal device can obtain different configuration information by receiving one configuration, that is, S510 and S530 can be executed simultaneously, or the terminal device can obtain different configuration information by receiving different configurations respectively, that is, steps S510 and S530 can be executed separately, and there is no limitation on this.
  • the method 500 further includes S540, the network device sends scheduling information to the terminal device, where the scheduling information is used for scheduling the data.
  • the terminal device receives the scheduling information from the network device.
  • the method 500 further includes S550, the terminal device sends data to the network device.
  • the network device receives data from the terminal device.
  • At least one in the embodiments of the present application may refer to one or more; “plurality” may refer to two or more.
  • the character “/” generally indicates that the objects associated before and after are in an "or” relationship.
  • the following at least one (item) or similar expressions refer to any combination of these items, including any combination of a single (item) or plural (items).
  • At least one (item) of a, b, or c can represent: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c can be single or multiple.
  • each network element such as a transmitting end device or a receiving end device, includes a hardware structure and/or software module corresponding to the execution of each function in order to realize the above functions.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.
  • the embodiment of the present application can divide the functional modules of the transmitting end device or the receiving end device according to the above method example.
  • each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module.
  • the above integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. There may be other division methods in actual implementation. The following is an example of dividing each functional module corresponding to each function.
  • FIG6 is a schematic block diagram of a communication device provided in an embodiment of the present application.
  • the communication device 600 shown in FIG6 includes an interface unit 610, and optionally, the communication device also includes a processing unit 620.
  • the interface unit 610 can communicate with the outside, and the processing unit 620 is used to perform data processing.
  • the interface unit 610 can also be called a communication interface, a transceiver unit, or a communication unit.
  • the communication device 600 may further include a storage unit, which may be used to store instructions and/or data, and the processing unit 620 may read the instructions and/or data in the storage unit.
  • a storage unit which may be used to store instructions and/or data
  • the processing unit 620 may read the instructions and/or data in the storage unit.
  • the communication apparatus 600 may be used to execute the actions performed by the terminal device in the above method embodiment.
  • the communication device 600 may be a terminal device
  • the interface unit 610 is used to perform the receiving or sending operations of the terminal device in the above method embodiment
  • the processing unit 620 is used to perform the internal processing operations of the terminal device in the above method embodiment.
  • the communication device 600 may be a component configured in a terminal device, for example, a chip in the terminal device.
  • the interface unit 610 may be an interface circuit, a pin, etc.
  • the interface circuit may include an input circuit and an output circuit
  • the processing unit 620 may include a processing circuit.
  • the interface unit 610 is used to receive first configuration information from a network device, and the first configuration information is used to configure a first threshold and a second threshold; the interface unit 610 is also used to send a scheduling request to the network device, and the scheduling request is used to request resources for scheduling data, and the scheduling request indicates at least one of the relationship between the remaining delay budget of the data and the first threshold or the relationship between the data volume of the data and the second threshold, and the remaining delay budget of the data is the upper limit of the remaining time to complete the data transmission.
  • the scheduling request indicates one of the following relationships: the data volume of the data is less than the second threshold; the data volume of the data is greater than or equal to the second threshold and the remaining delay budget of the data is greater than or equal to the first threshold; or, the data volume of the data is greater than or equal to the second threshold and the remaining delay budget of the data is less than the first threshold.
  • the scheduling request indicates one of the following relationships: the remaining delay budget of the data is greater than or equal to the first threshold; the remaining delay budget of the data is less than the first threshold and the data volume of the data is less than the second threshold; or, the remaining delay budget of the data is less than the first threshold and the data volume of the data is greater than or equal to the second threshold.
  • the scheduling request indicates one of the following relationships: the remaining delay budget of the data is greater than or equal to the first threshold and the data volume of the data is less than the second threshold; the remaining delay budget of the data is greater than or equal to the first threshold and the data volume of the data is greater than or equal to the second threshold; the remaining delay budget of the data is less than the first threshold and the data volume of the data is less than the second threshold; or, the remaining delay budget of the data is less than the first threshold and the data volume of the data is greater than or equal to the second threshold.
  • the scheduling request is carried by physical uplink control channel PUCCH format 0.
  • the interface unit 610 is further configured to receive second configuration information from the network device; and the processing unit is configured to control the communication apparatus 600 to send the scheduling request to the network device according to the second configuration information.
  • the communication apparatus 600 may be used to execute the actions performed by the network device in the above method embodiments.
  • the communication device 600 may be a network device
  • the interface unit 610 is used to perform the receiving or sending operations of the network device in the above method embodiment
  • the processing unit 620 is used to perform the internal processing operations of the network device in the above method embodiment.
  • the communication device 600 may be a component configured in a network device, for example, a chip in the network device.
  • the interface unit 610 may be an interface circuit, a pin, etc.
  • the interface circuit may include an input circuit and an output circuit
  • the processing unit 620 may include a processing circuit.
  • the interface unit is used to send first configuration information to a terminal device, and the first configuration information is used to configure a first threshold and a second threshold; the interface unit is also used to receive a scheduling request from the terminal device, and the scheduling request is used to request resources for scheduling data, and the scheduling request indicates at least one of the relationship between a remaining delay budget for the data and the first threshold or the relationship between a data volume of the data and the second threshold, and the remaining delay budget for the data is an upper limit on the remaining time to complete the data transmission.
  • the size relationship indicated by the scheduling request can refer to the first possible design mentioned above and will not be elaborated on.
  • the scheduling request is carried by physical uplink control channel PUCCH format 0.
  • the interface unit 610 is further used to send second configuration information to the terminal device, where the second configuration information configures the sending of the scheduling request.
  • the embodiment of the present application further provides a communication device 700.
  • the communication device 700 includes a processor 710, the processor 710 is coupled to a memory 720, the memory 720 is used to store computer programs or instructions or and/or data, and the processor 710 is used to execute the computer programs or instructions and/or data stored in the memory 720, so that the method in the above method embodiment is executed.
  • the communication device 700 includes one or more processors 710.
  • the communication device 700 may further include a memory 720 .
  • the communication device 700 may include one or more memories 720 .
  • the memory 720 may be integrated with the processor 710 or provided separately.
  • the communication device 700 may further include a transceiver 730 and/or a communication interface, and the transceiver 730 and/or the communication interface are used to receive and/or send signals.
  • the processor 710 is used to control the transceiver 730 and/or the communication interface to receive and/or send signals.
  • the device for implementing the receiving function in the transceiver 730 may be regarded as a receiving module, and the device for implementing the sending function in the transceiver 730 may be regarded as a sending module, that is, the transceiver 730 includes a receiver and a transmitter.
  • a transceiver may sometimes be referred to as a transceiver, a transceiver module, or a transceiver circuit, etc.
  • a receiver may sometimes be referred to as a receiver, a receiving module, or a receiving circuit, etc.
  • a transmitter may sometimes be referred to as a transmitter, a transmitter, a transmitting module, or a transmitting circuit, etc.
  • the communication device 700 is used to implement the operations performed by the terminal device in the above method embodiment.
  • the processor 710 is used to implement the operations performed by the terminal device in the above method embodiment
  • the transceiver 730 is used to implement the receiving or sending operations (such as operations S410 to S460, or operations S510 to S550) performed by the terminal device in the above method embodiment.
  • the communication device 700 is used to implement the operations performed by the network device in the above method embodiment.
  • the processor 710 is used to implement the operations performed by the network device in the above method embodiment
  • the transceiver 730 is used to implement the receiving or sending operations (such as operations S410 to S460 or operations S510 to S550) performed by the network device in the above method embodiment.
  • FIG8 shows a simplified schematic diagram of the structure of a communication device.
  • the communication device 800 includes a processor, a memory, a radio frequency circuit, an antenna, and an input/output device.
  • the processor is mainly used to process the communication protocol and communication data, and to control the communication device 800, execute software programs, process the data of software programs, etc.
  • the memory is mainly used to store software programs and data.
  • the RF circuit is mainly used for the conversion between baseband signals and RF signals and the processing of RF signals.
  • the antenna is mainly used to send and receive RF signals in the form of electromagnetic waves.
  • Input and output devices such as touch screens, display screens, keyboards, etc., are mainly used to receive data input by users and output data to users.
  • the processor When data needs to be sent, the processor performs baseband processing on the data to be sent, and then outputs the baseband signal to the RF circuit.
  • the RF circuit performs RF processing on the baseband signal and then sends the RF signal outward in the form of electromagnetic waves through the antenna.
  • the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor.
  • the processor converts the baseband signal into data and processes the data.
  • only one memory and processor are shown in FIG8. In actual products, there may be one or more processors and one or more memories.
  • the memory may also be referred to as a storage medium or a storage device, etc.
  • the memory may be set independently of the processor or integrated with the processor, and the embodiments of the present application do not limit this.
  • the antenna and the radio frequency circuit with transceiver functions may be regarded as the transceiver unit of the communication device 800
  • the processor with processing function may be regarded as the processing unit of the communication device 800 .
  • the communication device 800 includes a transceiver unit 810 and a processing unit 820.
  • the transceiver unit 810 may also be referred to as a transceiver, a transceiver, a transceiver device or a transceiver circuit, etc.
  • the processing unit 820 may also be referred to as a processor, a processing board, a processing module, a processing device, etc.
  • the device used to implement the receiving function in the transceiver unit 810 can be regarded as a receiving unit, and the device used to implement the sending function in the transceiver unit 810 can be regarded as a sending unit, that is, the transceiver unit 810 includes a receiving unit and a sending unit.
  • the receiving unit may also be sometimes called a receiver, a receiver, a receiving device, or a receiving circuit, etc.
  • the sending unit may also be sometimes called a transmitter, a transmitter, a transmitting device, or a transmitting circuit, etc.
  • processing unit 820 and the transceiver unit 810 are used to perform operations of the terminal device.
  • the transceiver unit 810 is used to perform, for example, the transceiver operation in the operations of S410 to S460 , or the transceiver operation in the operations of S510 to S550 .
  • processing unit 820 and the transceiver unit 810 are used to perform operations of the network device.
  • the transceiver unit 810 is used to perform, for example, the transceiver operation in the operations of S410 to S460 , or the transceiver operation in the operations of S510 to S550 .
  • FIG8 is merely an example and not a limitation, and the communication device 800 including the transceiver unit and the processing unit may not rely on the structure shown in FIG8 .
  • the chip When the communication device 800 is a chip, the chip includes a transceiver unit and a processing unit, wherein the transceiver unit may be an input/output circuit or a communication interface; and the processing unit may be a processor or a microprocessor or an integrated circuit integrated on the chip.
  • the embodiment of the present application further provides a communication device 900 .
  • the communication device 900 includes a logic circuit 910 and an input/output interface 920 .
  • the logic circuit 910 can be a processing circuit in the communication device 900.
  • the logic circuit 910 can be coupled to the storage unit and call the instructions in the storage unit so that the communication device 900 can implement the methods and functions of each embodiment of the present application.
  • the input/output interface 920 can be an input/output circuit in the communication device 900, outputting information processed by the communication device 900, or inputting data or signaling information to be processed into the communication device 900 for processing.
  • the communication device 900 is used to implement the operations performed by the terminal device in the above various method embodiments.
  • the logic circuit 910 is used to implement the processing-related operations performed by the terminal device in the above method embodiment.
  • the input/output interface 920 is used to implement the sending and/or receiving-related operations performed by the terminal device in the above method embodiment.
  • the operations performed by the logic circuit 910 can be specifically referred to in the above description of the processing unit 620, and the operations performed by the input/output interface 920 can be referred to in the above description of the interface unit 610, which will not be repeated here.
  • the communication device 900 is used to implement the operations performed by the network device in the above method embodiments.
  • the logic circuit 910 is used to implement the processing-related operations performed by the network device in the above method embodiment, such as the processing-related operations performed by the network device in the method embodiment, and the input/output interface 920 is used to implement the sending and/or receiving-related operations performed by the network device in the above method embodiment.
  • the operations performed by the logic circuit 910 can be specifically referred to in the above description of the processing unit 620.
  • the operations performed by the input/output interface 920 can be referred to in the above description of the transceiver unit 610, which will not be repeated here.
  • the above communication device may be one or more chips.
  • the communication device may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), It can also be a system on chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD) or other integrated chips.
  • FPGA field programmable gate array
  • ASIC application specific integrated circuit
  • SoC system on chip
  • CPU central processor unit
  • NP network processor
  • DSP digital signal processor
  • MCU microcontroller unit
  • PLD programmable logic device
  • each step of the above method can be completed by an integrated logic circuit of hardware in a processor or an instruction in the form of software.
  • the steps of the method disclosed in conjunction with the embodiment of the present application can be directly embodied as a hardware processor for execution, or a combination of hardware and software modules in a processor for execution.
  • the software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc.
  • the storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the above method in conjunction with its hardware. To avoid repetition, it is not described in detail here.
  • the processor in the embodiment of the present application can be an integrated circuit chip with signal processing capabilities.
  • each step of the above method embodiment can be completed by an integrated logic circuit of hardware in the processor or an instruction in the form of software.
  • the above processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • FPGA field programmable gate array
  • the methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc.
  • the steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor can be combined and performed.
  • the software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc.
  • the storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories.
  • the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory.
  • the volatile memory can be a random access memory (RAM), which is used as an external cache.
  • RAM random access memory
  • SRAM static RAM
  • DRAM dynamic RAM
  • SDRAM synchronous DRAM
  • DDR SDRAM double data rate SDRAM
  • ESDRAM enhanced SDRAM
  • SLDRAM synchlink DRAM
  • DR RAM direct rambus RAM
  • the present application also provides a computer-readable medium, which stores a program code, and when the program code is run on a computer, the computer executes the method shown in the method embodiment.
  • the computer program when executed by a computer, the computer can implement the method executed by the terminal device in the above method embodiment, or the method executed by the network device.
  • An embodiment of the present application also provides a computer program product comprising instructions, which, when executed by a computer, enables the computer to implement the method executed by a terminal device or a method executed by a network device in the above method embodiment.
  • the computer program product includes one or more computer instructions.
  • the computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer instructions can be transmitted from one website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center.
  • the computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated.
  • the available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a high-density digital video disk (digital video disk)), a computer, a server or a data center, or a computer. video disc (DVD)), or semiconductor media (for example, solid state drive (SSD)), etc.
  • a magnetic medium e.g., a floppy disk, a hard disk, a tape
  • an optical medium e.g., a high-density digital video disk (digital video disk)
  • a computer e.g., a server or a data center, or a computer.
  • video disc (DVD) digital versatile disc
  • SSD solid state drive
  • the terminal devices and network devices in the above-mentioned various device embodiments correspond to the terminal devices and network devices in the method embodiments, and the corresponding modules or units perform the corresponding steps.
  • the communication unit transmits the steps of receiving or sending in the method embodiment, and other steps except sending and receiving can be performed by the processing unit (processor).
  • the functions of the specific units can refer to the corresponding method embodiments.
  • the processor can be one or more.
  • a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program and/or a computer.
  • applications running on a computing device and a computing device can be components.
  • One or more components may reside in a process and/or an execution thread, and a component may be located on a computer and/or distributed between two or more computers.
  • these components may be executed from various computer-readable media having various data structures stored thereon.
  • Components may, for example, communicate through local and/or remote processes according to signals having one or more data packets (e.g., data from two components interacting with another component between a local system, a distributed system and/or a network, such as the Internet interacting with other systems through signals).
  • signals having one or more data packets (e.g., data from two components interacting with another component between a local system, a distributed system and/or a network, such as the Internet interacting with other systems through signals).
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed.
  • Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art.
  • the computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk, and other media that can store program codes.

Landscapes

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

Abstract

一种数据传输的方法和装置，该方法包括：接收来自网络设备的第一配置信息，该第一配置信息用于配置第一阈值和第二阈值；向该网络设备发送调度请求，该调度请求用于请求调度数据的资源，该调度请求指示该数据的剩余时延预算与该第一阈值的大小关系或该数据的数据量与该第二阈值的大小关系中的至少一种，该数据的剩余时延预算为完成该数据传输的剩余时长的上限。本申请提供的方案能够使得网络设备确定数据的剩余时延预算以及数据的数据量，以期在数据的时延预算内完成数据的传输，从而提高通信的性能。

Description

一种数据传输的方法和装置
本申请要求于2022年09月29日提交中国专利局、申请号为202211199834.0、发明名称为“一种数据传输的方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信领域，并且，更具体地，涉及一种数据传输的方法和装置。
背景技术
随着通信的发展，第五代(5th generation，5G)通信系统逐渐渗入一些实时性强、数据容量要求大的多媒体业务，例如视频传输、云游戏(cloud gaming，CG)和扩展现实(extended reality，XR)等。这些多媒体业务通常对数据传输的时延要求比较严格。因此如何保证数据传输的时延需求是需要考虑的问题。
发明内容
本申请实施例提供一种通信方法和通信装置，以期在数据的时延预算内完成数据的传输，从而提高通信的性能。
第一方面，提供了一种通信方法，该方法可以由终端设备执行，或者，也可以由终端设备中的芯片或电路执行，或者，还可以由能实现全部或部分终端设备功能的逻辑模块或软件执行。本申请对此不作限定。
该方法包括：接收来自网络设备的第一配置信息，该第一配置信息用于配置第一阈值和第二阈值；向该网络设备发送调度请求，该调度请求用于请求调度数据的资源，该调度请求指示该数据的剩余时延预算与该第一阈值的大小关系或该数据的数据量与该第二阈值的大小关系中的至少一种，该数据的剩余时延预算为完成该数据传输的剩余时长的上限。
基于上述方案，在终端设备被配置了数据的剩余时延预算的阈值(第一阈值)以及数据的数据量(第二阈值)的情况下，终端设备可以向网络设备发送指示数据的剩余时延预算与该第一阈值的大小关系，和/或数据的数据量与该第二阈值的大小关系的调度请求，使得网络设备可以根据该调度请求调度传输数据的资源，减少数据传输的时延，从而提高通信的性能。
结合第一方面，在第一方面的某些实现方式中，该调度请求指示以下关系中的一个：该数据的数据量小于该第二阈值；该数据的数据量大于或等于该第二阈值且该数据的剩余时延预算大于或等于该第一阈值；或，该数据的数据量大于或等于该第二阈值且该数据的剩余时延预算小于该第一阈值。
基于上述方案，通过调度请求指示以上关系中的任一个，可以使得网络设备获知数据的数据量与第二阈值的大小关系，或者，可以使得网络设备获知数据的剩余时延预算和第一阈值的大小关系以及数据的数据量与第二阈值的大小关系，可以节约信令开销。
结合第一方面，在第一方面的某些实现方式中，该调度请求指示以下关系中的一个：该数据的剩余时延预算大于或等于该第一阈值；该数据的剩余时延预算小于该第一阈值且该数据的数据量小于该第二阈值；或，该数据的剩余时延预算小于该第一阈值且该数据的数据量大于或等于该第二阈值。
基于上述方案，通过调度请求指示以上关系中的任一个，可以使得网络设备获知数据的剩余时延预算与第一阈值的大小关系，或者，可以使得网络设备获知数据的剩余时延预算和第一阈值的大小关系以及数据的数据量与第二阈值的大小关系，可以节约信令开销。
结合第一方面，在第一方面的某些实现方式中，该调度请求指示以下关系中的一个：该数据的剩余时延预算大于或等于该第一阈值且该数据的数据量小于该第二阈值；该数据的剩余时延预算大于或等于该第一阈值且该数据的数据量大于或等于该第二阈值；该数据的剩余时延预算小于该第一阈值且该数据的数据量小于该第二阈值；或，该数据的剩余时延预算小于该第一阈值且该数据的数据量大于 或等于该第二阈值。
基于上述方案，通过调度请求指示以上关系中的任一个，可以使得网络设备获知数据的剩余时延预算和第一阈值的大小关系以及数据的数据量与第二阈值的大小关系，可以节约信令开销。
结合第一方面，在第一方面的某些实现方式中，该调度请求由物理上行控制信道PUCCH格式0承载。
基于上述方案，指示不同信息的调度请求可以通过PUCCH格式0中不同的序列循环移位的取值指示，可以降低网络设备处理的复杂度。
结合第一方面，在第一方面的某些实现方式中，接收来自该网络设备的第二配置信息，根据该第二配置信息向该网络设备发送该调度请求。
基于上述方案，终端设备可以在被配置了该第二配置信息的情况下，发送指示数据的剩余时延预算与该第一阈值的大小关系，和/或数据的数据量与该第二阈值的大小关系的调度请求。
第二方面，提供了一种通信方法，该方法可以由网络设备执行，或者，也可以由网络设备中的芯片或电路执行，或者，还可以由能实现全部或部分网络设备功能的逻辑模块或软件执行。本申请对此不作限定。
该方法包括：向终端设备发送第一配置信息，该第一配置信息用于配置第一阈值和第二阈值；接收来自该终端设备的调度请求，该调度请求用于请求调度数据的资源，该调度请求指示该数据的剩余时延预算与该第一阈值的大小关系或该数据的数据量与该第二阈值的大小关系中的至少一种，该数据的剩余时延预算为完成该数据传输的剩余时长的上限。
基于上述方案，通过向终端设备发送用于配置数据的剩余时延预算的阈值(第一阈值)以及数据的数据量(第二阈值)的配置信息，可以使得终端设备基于该配置信息向网络设备发送指示数据的剩余时延预算与该第一阈值的大小关系，和/或数据的数据量与该第二阈值的大小关系的调度请求，从而可以为该终端设备调度传输数据的资源，减少数据传输的时延，从而提高通信的性能。
结合第二方面，在第二方面的某些实现方式中，该调度请求指示以下关系中的一个：该数据的数据量小于该第二阈值；该数据的数据量大于或等于该第二阈值且该数据的剩余时延预算大于或等于该第一阈值；或，该数据的数据量大于或等于该第二阈值且该数据的剩余时延预算小于该第一阈值。
基于上述方案，通过调度请求指示以上关系中的任一个，网络设备可以获知数据的数据量与第二阈值的大小关系，或者，可以获知数据的剩余时延预算和第一阈值的大小关系以及数据的数据量与第二阈值的大小关系，同时可以节约信令开销。
结合第二方面，在第二方面的某些实现方式中，该调度请求指示以下关系中的一个：该数据的剩余时延预算大于或等于该第一阈值；该数据的剩余时延预算小于该第一阈值且该数据的数据量小于该第二阈值；或，该数据的剩余时延预算小于该第一阈值且该数据的数据量大于或等于该第二阈值。
基于上述方案，通过调度请求指示以上关系中的任一个，网络设备可以获知数据的剩余时延预算与第一阈值的大小关系，或者，可以获知数据的剩余时延预算和第一阈值的大小关系以及数据的数据量与第二阈值的大小关系，同时可以节约信令开销。
结合第二方面，在第二方面的某些实现方式中，该调度请求指示以下关系中的一个：该数据的剩余时延预算大于或等于该第一阈值且该数据的数据量小于该第二阈值；该数据的剩余时延预算大于或等于该第一阈值且该数据的数据量大于或等于该第二阈值；该数据的剩余时延预算小于该第一阈值且该数据的数据量小于该第二阈值；或，该数据的剩余时延预算小于该第一阈值且该数据的数据量大于或等于该第二阈值。
基于上述方案，通过调度请求指示以上关系中的任一个，网络设备可以获知数据的剩余时延预算和第一阈值的大小关系以及数据的数据量与第二阈值的大小关系，同时可以节约信令开销。
结合第二方面，在第二方面的某些实现方式中，该调度请求由物理上行控制信道PUCCH格式0承载。
基于上述方案，指示不同信息的调度请求可以通过PUCCH格式0中不同的序列循环移位的取值指示，可以降低网络设备处理的复杂度。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：向该终端设备发送第二配置信息，该第二配置信息配置该调度请求的发送。
基于上述方案，通过向终端设备发送该第二配置信息，可以使得终端设备发送指示数据的剩余时延预算与该第一阈值的大小关系，和/或数据的数据量与该第二阈值的大小关系的调度请求，从而可以为终端设备调度传输数据的资源。
第三方面，提供了一种通信方法，该方法可以由终端设备执行，或者，也可以由终端设备中的芯片或电路执行，或者，还可以由能实现全部或部分终端设备功能的逻辑模块或软件执行。本申请对此不作限定。
该方法包括：接收来自网络设备的第四配置信息；根据该第四配置信息向该网络设备发送调度请求，该调度请求用于请求调度数据的资源，该调度请求指示该数据的数据量与该数据的剩余时延预算的比值，该数据的剩余时延预算为完成该数据传输的剩余时长的上限。
基于上述方案，在终端设备被配置了该第四配置信息的情况下，发送该数据的数据量与该数据的剩余时延预算的比值(该比值可称为数据的需求速率)，使得网络设备可以根据该数据的需求速率调度传输数据的资源，减少数据传输的时延，从而提高通信的性能。
结合第三方面，在第三方面的某些实现方式中，该调度请求由物理上行控制信道PUCCH格式0承载。
基于上述方案，指示不同信息的调度请求可以通过PUCCH格式0中不同的序列循环移位的取值指示，可以降低网络设备处理的复杂度。
结合第三方面，在第三方面的某些实现方式中，该方法还包括接收来自网络设备的第五配置信息，该第五配置信息包括数据的需求速率列表，该数据的需求速率列表包括至少一个值。
结合第三方面，在第三方面的某些实现方式中，该调度请求指示该需求速率列表中的一个值。
基于上述方案，通过第五配置信息配置数据的需求速率的可能的取值，使得终端设备可以在配置的值中选择发送，节约信令开销。
结合第三方面，在第三方面的某些实现方式中，该调度请求指示数据的需求速率与该需求速率列表中的值的大小关系。
基于上述方案，通过第五配置信息配置数据的需求速率的可能的取值，使得终端设备可以发送数据的需求速率与需求速率列表中的值的大小关系，节约信令开销。
第四方面，提供了一种通信方法，该方法可以由网络设备执行，或者，也可以由网络设备中的芯片或电路执行，或者，还可以由能实现全部或部分网络设备功能的逻辑模块或软件执行。本申请对此不作限定。
该方法包括：向终端设备发送第四配置信息，该第四配置信息用于配置调度请求的发送，该调度请求指示数据的数据量与数据的剩余时延预算的比值；接收来自终端设备的调度请求，该数据的剩余时延预算为完成该数据传输的剩余时长的上限。
基于上述方案，通过向终端设备发送该第四配置信息，以及接收来自终端设备的数据的数据量与该数据的剩余时延预算的比值(该比值可称为数据的需求速率)，使得网络设备可以根据该数据的需求速率调度传输数据的资源，减少数据传输的时延，从而提高通信的性能。
结合第四方面，在第四方面的某些实现方式中，该调度请求由物理上行控制信道PUCCH格式0承载。
结合第四方面，在第四方面的某些实现方式中，该方法还包括向终端设备发送第五配置信息，该第五配置信息包括数据的需求速率列表，该数据的需求速率列表包括至少一个值。
结合第四方面，在第四方面的某些实现方式中，该调度请求指示该需求速率列表中的一个值。
基于上述方案，通过第五配置信息配置数据的需求速率的可能的取值，使得终端设备可以在配置的值中选择发送，节约信令开销。
结合第四方面，在第四方面的某些实现方式中，该调度请求指示数据的需求速率与该需求速率列表中的值的大小关系。
基于上述方案，通过第五配置信息配置数据的需求速率的可能的取值，使得终端设备可以发送数据的需求速率与需求速率列表中的值的大小关系，节约信令开销。
第五方面，提供了一种通信装置，该通信装置可以为终端设备，或终端设备中的芯片或电路，或能实现全部或部分终端设备功能的逻辑模块或软件，本申请对此不作限定。
该装置包括接口单元，该接口单元用于接收来自网络设备的第一配置信息，该第一配置信息用于配置第一阈值和第二阈值；该接口单元还用于向该网络设备发送调度请求，该调度请求用于请求调度数据的资源，该调度请求指示该数据的剩余时延预算与该第一阈值的大小关系或该数据的数据量与该第二阈值的大小关系中的至少一种，该数据的剩余时延预算为完成该数据传输的剩余时长的上限。
结合第五方面，在第五方面的某些实现方式中，该调度请求指示以下关系中的一个：该数据的数据量小于该第二阈值；该数据的数据量大于或等于该第二阈值且该数据的剩余时延预算大于或等于该第一阈值；或，该数据的数据量大于或等于该第二阈值且该数据的剩余时延预算小于该第一阈值。
结合第五方面，在第五方面的某些实现方式中，该调度请求指示以下关系中的一个：该数据的剩余时延预算大于或等于该第一阈值；该数据的剩余时延预算小于该第一阈值且该数据的数据量小于该第二阈值；或，该数据的剩余时延预算小于该第一阈值且该数据的数据量大于或等于该第二阈值。
结合第五方面，在第五方面的某些实现方式中，该调度请求指示以下关系中的一个：该数据的剩余时延预算大于或等于该第一阈值且该数据的数据量小于该第二阈值；该数据的剩余时延预算大于或等于该第一阈值且该数据的数据量大于或等于该第二阈值；该数据的剩余时延预算小于该第一阈值且该数据的数据量小于该第二阈值；或，该数据的剩余时延预算小于该第一阈值且该数据的数据量大于或等于该第二阈值。
结合第五方面，在第五方面的某些实现方式中，该调度请求由物理上行控制信道PUCCH格式0承载。
结合第五方面，在第五方面的某些实现方式中，该接口单元还用于接收来自该网络设备的第二配置信息；该通信装置还包括处理单元，该处理单元用于控制所述装置根据该第二配置信息向该网络设备发送该调度请求。
第六方面，提供了一种通信装置，该通信装置可以为网络设备，或网络设备中的芯片或电路，或能实现全部或部分网络设备功能的逻辑模块或软件，本申请对此不作限定。
该通信装置包括接口单元，该接口单元用于向终端设备发送第一配置信息，该第一配置信息用于配置第一阈值和第二阈值；该接口单元还用于接收来自该终端设备的调度请求，该调度请求用于请求调度数据的资源，该调度请求指示该数据的剩余时延预算与该第一阈值的大小关系或该数据的数据量与该第二阈值的大小关系中的至少一种，该数据的剩余时延预算为完成该数据传输的剩余时长的上限。
结合第六方面，在第六方面的某些实现方式中，该调度请求指示以下关系中的一个：该数据的数据量小于该第二阈值；该数据的数据量大于或等于该第二阈值且该数据的剩余时延预算大于或等于该第一阈值；或，该数据的数据量大于或等于该第二阈值且该数据的剩余时延预算小于该第一阈值。
结合第六方面，在第六方面的某些实现方式中，该调度请求指示以下关系中的一个：该数据的剩余时延预算大于或等于该第一阈值；该数据的剩余时延预算小于该第一阈值且该数据的数据量小于该第二阈值；或，该数据的剩余时延预算小于该第一阈值且该数据的数据量大于或等于该第二阈值。
结合第六方面，在第六方面的某些实现方式中，该调度请求指示以下关系中的一个：该数据的剩余时延预算大于或等于该第一阈值且该数据的数据量小于该第二阈值；该数据的剩余时延预算大于或等于该第一阈值且该数据的数据量大于或等于该第二阈值；该数据的剩余时延预算小于该第一阈值且该数据的数据量小于该第二阈值；或，该数据的剩余时延预算小于该第一阈值且该数据的数据量大于或等于该第二阈值。
结合第六方面，在第六方面的某些实现方式中，该调度请求由物理上行控制信道PUCCH格式0承载。
结合第六方面，在第六方面的某些实现方式中，该接口单元还用于向该终端设备发送第二配置信息，该第二配置信息配置该调度请求的发送。
第七方面，提供了一种通信装置，该通信装置可以为终端设备，或终端设备中的芯片或电路，或能实现全部或部分终端设备功能的逻辑模块或软件，本申请对此不作限定。
该通信装置包括接口单元和处理单元，该接口单元用于接收来自网络设备的第四配置信息；该处理单元用于控制所述装置根据该第四配置信息向该网络设备发送调度请求，该调度请求用于请求调度数据的资源，该调度请求指示该数据的数据量与该数据的剩余时延预算的比值，该数据的剩余时延预算为完成该数据传输的剩余时长的上限。
结合第七方面，在第七方面的某些实现方式中，该调度请求由物理上行控制信道PUCCH格式0承载。
结合第七方面，在第七方面的某些实现方式中，该接口单元还用于接收来自网络设备的第五配置信息，该第五配置信息包括数据的需求速率列表，该数据的需求速率列表包括至少一个值。
结合第七方面，在第七方面的某些实现方式中，该调度请求指示该需求速率列表中的一个值。
结合第七方面，在第七方面的某些实现方式中，该调度请求指示数据的需求速率与该需求速率列表中的值的大小关系。
第八方面，提供了一种通信装置，该通信装置可以为网络设备，或网络设备中的芯片或电路，或能实现全部或部分网络设备功能的逻辑模块或软件，本申请对此不作限定。
该装置包括接口单元，该接口单元用于向终端设备发送第四配置信息，该第四配置信息用于配置调度请求的发送，该调度请求指示数据的数据量与数据的剩余时延预算的比值；该接口单元还用于接收来自终端设备的调度请求，该数据的剩余时延预算为完成该数据传输的剩余时长的上限。
结合第八方面，在第八方面的某些实现方式中，该调度请求由物理上行控制信道PUCCH格式0承载。
结合第八方面，在第八方面的某些实现方式中，该接口单元还用于向终端设备发送第五配置信息，该第五配置信息包括数据的需求速率列表，该数据的需求速率列表包括至少一个值。
结合第八方面，在第八方面的某些实现方式中，该调度请求指示该需求速率列表中的一个值。
结合第八方面，在第八方面的某些实现方式中，该调度请求指示数据的需求速率与该需求速率列表中的值的大小关系。
第九方面，提供一种通信装置，该装置包括处理器，该处理器与存储器耦合，可用于执行存储器中的指令，以实现上述第一方面至第四方面中的任一方面，以及第一方面至第四方面中任一种可能实现方式中的方法。可选地，该装置还包括存储器，该存储器与处理器可能是分离部署的，也可能是集中部署的。可选地，该装置还包括通信接口，处理器与通信接口耦合。
在一种实现方式中，该通信接口可以是收发器，或，输入/输出接口。
在另一种实现方式中，该装置为终端设备或网络设备，或配置于终端设备或网络设备中的芯片，还可以是能实现全部或部分终端设备或网络设备功能的逻辑模块或软件。当该装置为芯片时，该通信接口可以是该芯片或芯片系统上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。该处理器也可以体现为处理电路或逻辑电路。
可选地，该收发器可以为收发电路。可选地，所述输入/输出接口可以为输入/输出电路。
在具体实现过程中，上述处理器可以为一个或多个芯片，输入电路可以为输入管脚，输出电路可以为输出管脚，处理电路可以为晶体管、门电路、触发器和各种逻辑电路等。输入电路所接收的输入的信号可以是但不限于接收器接收并输入的，输出电路所输出的信号可以是但不限于输出给发射器并由发射器发射的，且输入电路和输出电路可以是同一电路，该电路在不同的时刻分别用作输入电路和输出电路。本申请实施例对处理器及各种电路的具体实现方式不做限定。
第十方面，提供一种通信装置，该装置包括逻辑电路和输入/输出接口，该逻辑电路用于与输入/输出接口耦合，通过该输入/输出接口传输数据，以执行上述第一方面至第四方面中的任一方面，以及第一方面至第四方面中任一种可能实现方式中的方法。
在一种实现方式中，该装置为终端设备或网络设备，或配置于终端设备或网络设备中的芯片，还可以是能实现全部或部分终端设备或网络设备功能的逻辑模块或软件。当该装置为芯片时，该通信接口可以是该芯片或芯片系统上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。该处理器也可以体现为处理电路或逻辑电路。
第十一方面，本申请提供了一种芯片系统，包括：处理器，该处理器用于执行该存储器中的计算机程序或指令，使得该芯片系统实现上述第一方面至第四方面以及第一方面至第四方面中任一种可能实现方式中的方法。
第十二方面，本申请提供了一种芯片系统，包括：终端设备和网络设备，该终端设备用于执行上述第一方面或第三方面以及第一方面或第三方面中任一种可能实现方式中的方法；该网络设备用于执行上述第二方面或第四方面以及第二方面或第四方面中任一种可能实现方式中的方法。
第十三方面，提供了一种计算机可读存储介质，该计算机可读存储介质存储有计算机程序(也可以称为代码，或指令)当其在计算机上运行时，使得计算机执行上述第一方面至第四方面中的任一方面，以及第一方面至第四方面中任一种可能实现方式中的方法。
第十四方面，提供了一种计算机程序产品，该计算机程序产品包括：计算机程序(也可以称为代码，或指令)，当该计算机程序被运行时，使得计算机执行上述第一方面至第四方面中的任一方面，以及第一方面至第四方面中任一种可能实现方式中的方法。
上述第五方面至第十四方面带来的有益效果可以参考第一方面至第四方面中有益效果的描述，此处不再赘述。
附图说明
图1是本申请适用的一种系统架构的示意图。
图2是一种调度数据的方法的交互流程图。
图3是一种上下行时隙配置下调度数据的示意图。
图4是本申请实施例提供的一种通信方法的交互流程图。
图5是本申请实施例提供的另一种通信方法的交互流程图。
图6是本申请实施例提供的一种通信装置的示意图。
图7是本申请实施例提供的一种通信装置的结构示意图。
图8是本申请实施例提供的另一种通信装置的结构示意图。
图9是本申请实施例提供的又一种通信装置的结构示意图。
具体实施方式
下面将结合附图，对本申请实施例中的技术方案进行描述。
图1示出了本申请适用的一种系统架构的示意图。图1示出的通信系统100包括网络设备10和至少一个终端设备，例如终端设备20、终端设备21。在该通信系统中，终端设备20和终端设备21可以向网络设备10发送上行数据/信号/信息；网络设备10可以向终端设备20和终端设备21中的至少一个发送下行数据/信号/信息。此外，终端设备20也可以与终端设备21之间传输数据/信号/信息。
应理解，图1仅为便于理解而示例的简化示意图，该通信系统100中还可以包括其他网络设备或者还可以包括其他终端设备，图1中未予以画出。
上述应用于本申请实施例的网络架构仅是一种举例说明，适用本申请实施例的网络架构并不局限于此，任何能够实现上述各个设备的功能的网络架构都适用于本申请实施例。
本申请实施例的技术方案可以应用于各种通信系统，例如：长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、通用移动通信系统(universal mobile telecommunication system，UMTS)、第五代(5th generation，5G)系统或新无线(new radio，NR)或者其他演进的通信系统等。
本申请提供的技术方案还可以应用于未来的通信系统，如第六代移动通信系统等。本申请对此不作限定。
本申请提供的技术方案还可以应用于机器类通信(machine type communication，MTC)、机器间通信长期演进技术(long term evolution-machine，LTE-M)、设备到设备(device-to device，D2D)网络、机器到机器(machine to machine，M2M)网络、物联网(internet of things，IoT)网络或者其他网络。其中，IoT网络例如可以包括车联网。其中，车联网系统中的通信方式统称为车到其他设备(vehicle to X，V2X，X可以代表任何事物)，例如，该V2X可以包括：车辆到车辆(vehicle to vehicle，V2V)通信，车辆与基础设施(vehicle to infrastructure，V2I)通信、车辆与行人之间的通信(vehicle to pedestrian，V2P)或车辆与网络(vehicle to network，V2N)通信等。
本申请实施例中的终端设备可以是能够接收网络设备调度和指示信息的无线终端设备。终端设备可以是指向用户提供语音和/或数据连通性的设备，或具有无线连接功能的手持式设备、或连接到无线调制解调器的其他处理设备。
终端设备也可以称为终端、接入终端、用户单元、用户设备(user equipment，UE)、用户站、移 动站、移动台、远方站、远程终端、移动设备、用户终端、无线通信设备、用户代理或用户装置。终端设备是包括无线通信功能(向用户提供语音/数据连通性)的设备。例如，具有无线连接功能的手持式设备、或车载设备等。本申请的实施例中的终端可以是手机(mobile phone)、平板电脑(pad)、带无线收发功能的电脑、列车、飞机、移动互联网设备(mobile internet device，MID)、虚拟现实(virtual reality，VR)终端、增强现实(augmented reality，AR)终端、工业控制(industrial control)中的无线终端(例如机器人等)、车联网中的无线终端(例如车载设备、整车设备、车载模块、车辆等)、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，5G网络中的终端或者未来演进网络中的终端等。可以理解，本申请中的终端设备的全部或部分功能也可以通过在硬件上运行的软件功能来实现，或者通过平台(例如云平台)上实例化的虚拟化功能来实现。
其中，可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
本申请实施例中的网络设备可以是无线网络中的设备。例如，网络设备可以是部署在无线接入网中为终端设备提供无线通信功能的设备。例如，网络设备可以为将终端设备接入到无线网络的无线接入网(radio access network，RAN)节点，又可以称为接入网设备。
该网络设备包括但不限于：演进型节点B(evolved Node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(home evolved NodeB，HeNB，或home Node B，HNB)、基带单元(baseBand unit，BBU)、服务器、可穿戴设备、车载设备，WIFI系统中的接入点(access point，AP)、无线中继节点、无线回传节点、传输点(transmission point，TP)或者发送接收点(transmission and reception point，TRP)等，还可以为5G，如NR系统中的gNB，或传输点(TRP或TP)，5G系统中的基站的一个或一组(包括多个天线面板)天线面板，或者，还可以为构成gNB或传输点的网络节点，如基带单元(BBU)，或分布式单元(distributed unit，DU)等。其中，基站可以是宏基站、微基站、微微基站、小站、中继站或气球站等。可以理解，本申请中的网络设备的全部或部分功能也可以通过在硬件上运行的软件功能来实现，或者通过平台(例如云平台)上实例化的虚拟化功能来实现。
在一些部署中，gNB可以包括集中式单元(centralized unit，CU)和DU。gNB还可以包括有源天线单元(active antenna unit，AAU)。CU实现gNB的部分功能，DU实现gNB的部分功能。比如，CU负责处理非实时协议和服务，实现无线资源控制(radio resource control，RRC)，分组数据汇聚层协议(packet data convergence protocol，PDCP)层的功能。DU负责处理物理层协议和实时服务，实现无线链路控制(radio link control，RLC)层、媒体接入控制(media access control，MAC)层和物理(physical，PHY)层的功能。AAU实现部分物理层处理功能、射频处理及有源天线的相关功能。RRC层的信息由CU生成，最终会经过DU的PHY层封装变成PHY层信息，或者，由PHY层的信息转变而来。因而，在这种架构下，高层信令如RRC层信令，也可以认为是由DU发送的，或者，由DU+AAU发送的。可以理解的是，网络设备可以为包括CU节点、DU节点、AAU节点中一项或多项的设备。此外，可以将CU划分为接入网(radio access network，RAN)中的网络设备，也可以将CU划分为核心网(core network，CN)中的网络设备，本申请对此不做限定。
如今，多媒体业务(例如CG和XR业务)的相关技术不断进步和完善，为了增强视觉效果和互动体验感，这类业务对网络的时延需求较严格。例如，在远程遥控系统中，为了保证触觉和远程操作的高保真性，触觉信息的采样率应不低于1kHz，每个样本的传输时延需求达到5ms。在传输时延需求日 益严格的一些多媒体业务中，在时延预算内完成数据的传输是需要考虑的问题。其中，数据的时延预算可以基于业务的传输时延需求确定。
图2是一种调度数据的方法的交互流程图。图2所示的方法200可以包括如下步骤。
S210，终端设备向网络设备发送调度请求(scheduling request，SR)，该调度请求用于请求调度数据的资源。
相应地，网络设备接收来自终端设备的该调度请求。
示例性地，当终端设备需要发送上行数据时，向网络设备发送该调度请求，以请求发送该上行数据的资源。
该调度请求可以由物理上行控制信道(physical uplink control channel,PUCCH)承载。例如，调度请求可以包括1比特(bit)信息，用于告知网络设备是否有上行数据传输。
其中，不同逻辑信道(logical channel，LCH)的调度请求的发送周期和发送偏移(例如时隙偏移)等可以相同，也可以不相同。并且不同逻辑信道可以单独配置。
示例性地，调度请求可以承载于PUCCH格式(format)0或者PUCCH format 1。
其中，PUCCH format 0还可以用于发送混合自动重传请求(hybrid automatic repeat request，HARQ)的ACK/NACK(acknowledgement/negative acknowledgement)反馈。PUCCH format 0发送的信息可以包括1比特或者2比特(对应调度的物理下行共享信道(physical downlink shared channel，PDSCH)包括2个码字时)。PUCCH format 0在频域上可以占用一个资源块，时域上可以占用1-2个符号。
PUCCH format 0可以基于ZC(Zadoff-Chu)序列产生。ZC序列承载的信息可以通过最终序列循环移位的取值指示。最终序列循环移位的取值可以基于序列循环移位的取值mcs确定。
示例地，当发送的信息为HARQ-ACK信息时，可通过HARQ-ACK信息和PUCCH format 0的序列循环移位的对应关系确定某一HARQ-ACK信息对应的mcs。
当发送的HARQ-ACK信息为1比特时，HARQ-ACK信息比特的值(即HARQ-ACK值)与PUCCH format 0的序列循环移位的对应关系可以如表1所示，即可根据表1所示的对应关系确定HARQ-ACK值对应的mcs。
表1
当发送的HARQ-ACK信息为2比特时，HARQ-ACK信息比特的值与PUCCH format 0的序列循环移位的对应关系可以如表2所示，即可根据表2所示的对应关系确定HARQ-ACK值对应的mcs。
表2
以表2为例，当HARQ-ACK值为{0,1}时，可以确定mcs＝3；进一步可基于mcs＝3确定承载该HARQ-ACK值的PUCCH format 0的最终序列循环移位的取值。
PUCCH format 0也可以携带SR，即HARQ-ACK信息和调度请求SR复用。或者说，SR和HARQ-ACK信息可以同时发送。当HARQ-ACK信息和SR复用时，该SR为正向(positive)请求(即告知网络设备有数据传输)，终端设备也可以通过循环移位的方式指示HARQ-ACK信息和该正向SR。
当发送的HARQ-ACK信息和正向SR为1比特时，HARQ-ACK信息比特和正向SR的值与PUCCH format 0的序列循环移位的对应关系可以如表3所示。
表3
当发送的HARQ-ACK信息比特和正向SR为2比特时，HARQ-ACK信息比特和正向SR的值与PUCCH格式0的序列循环移位的对应关系可以如表4所示。
表4

表3和表4中没有示出正向SR的值，是因为正向SR是隐式指示的，实际不占用信息比特。即mcs的取值为表3和表4中的值时，HARQ-ACK值除了指示HARQ-ACK信息之外，还指示了正向SR。
需要说明的是，由于HARQ-ACK信息，或HARQ-ACK信息和正向SR的发送资源是网络设备配置的，因此网络设备在识别出mcs＝3或9时，可以确定是基于表2解读2比特指示的HARQ-ACK信息，还是基于表3解读1比特指示的HARQ-ACK信息和正向SR。
以表4为例，当HARQ-ACK值为{0,1}时，基于表4可以确定mcs＝4；进一步可基于mcs＝4确定承载该HARQ-ACK信息和正向SR的PUCCH format 0序列的最终序列循环移位的取值。
S220，网络设备向终端设备发送调度信息。
相应地，终端设备接收来自网络设备的该调度信息。
示例性地，响应于终端设备发送的SR，网络设备向终端设备发送调度信息。该调度信息可以包括物理上行共享信道(physical uplink shared channel，PUSCH)资源信息。
该调度信息可以由物理下行控制信道(physical downlink control channel,PDCCH)承载。例如通过下行控制信息(downlink control information，DCI)格式(format)0_0或0_1向终端设备发送调度信息。
由于网络设备不知道终端设备即将发送的上行数据的数据量大小，因此网络设备可以按照一个较小的、固定的数据量对该终端设备进行调度。
可选地，如果终端设备没有接收到来自网络设备的调度信息，终端设备还可以继续发送SR。
S230，终端设备向网络设备发送数据。
相应地，网络设备接收来自终端设备的数据。
示例性地，终端设备接收到来自网络设备的调度信息后，基于调度信息向网络设备发送数据。例如，网络设备分配的调度信息可以包括PUSCH资源信息，终端设备可以在该PUSCH资源上发送数据。
其中，数据可以包括缓存状态报告(buffer status report，BSR)信息，BSR用来告知网络设备还有多少数据需要发送。例如，如果BSR大于0，网络设备可以继续调度该终端设备。即网络设备可继续通过PDCCH向该终端设备发送调度信息，以使该终端设备在调度信息指示的PUSCH资源上继续传输数据。
在时分双工(time division duplex，TDD)系统中，受限于上行时隙和下行时隙的数量比例和先后顺序，网络设备在上行时隙才能收到SR。而终端设备数据到达的时刻或者说终端设备获取数据的时刻可能早于该上行时隙对应的时刻。如果采用方法200中调度数据的方案，网络设备可能无法感知终端设备获取数据的准确时刻。在网络设备无法感知终端设备获取数据的准确时刻的情况下，数据在空口的调度时间有可能超过数据的时延预算。
举例来说，如图3所示，在TDD的时隙配置为DDDSU的情况下，如果网络设备以SR的发送时刻作为数据的获取时刻，则与实际数据的获取时刻相比，误差可达5个时隙。如果系统采用15kHz子载波间隔(sub-carrier spacing，SCS)，1个时隙为1ms，即误差可达5ms。在TDD的时隙配置为DDDDD DDSUU的情况下，如果网络设备以SR的发送时刻作为数据的获取时刻，则与实际数据的获取时刻相比，误差可达9个时隙。如果每个时隙为1ms，即误差可达9ms。
其中，D为下行时隙，U为上行时隙，S表示特殊时隙(special)，该特殊时隙可以包括用于上行传输的符号和用于下行传输的符号。
以TDD的时隙配置为DDDSU为例，假设数据的时延预算为15ms(1个时隙为1ms)、实际数据的获取时刻为第一个上行时隙的结束时刻，则数据可能在图3所示的第四个上行时隙结束后无效。如果网络设备以发送SR的第二个上行时隙的结束时刻作为数据的获取时刻，则网络设备会根据数据的时延预算在第二个上行时隙后的15ms内完成数据的调度传输，而在第四个上行时隙后传输的数据可能无效。
需要说明的是，在本申请实施例中，数据的时延预算可以为数据包时延预算(packet delay budget，PDB)。PDB可以指一个数据包在用户面功能(user plane function，UPF)网元和终端设备之间传输的过程中所允许的传输时延的最大值。换言之，如果一个数据包在UPF和终端设备之间传输的传输时延超过PDB，则该数据包对于接收端而言可能是无用的。
本申请实施例中的PDB还可以是数据在网络设备(例如基站)和终端设备之间传输所允许的传输时延的最大值。
在本申请实施例中，数据的获取时刻可以理解为终端设备获取到数据的时刻。获取到数据的时刻可以理解为数据递交至/到达某协议层(例如MAC层、RLC层或PDCP层等)的时刻。例如，数据的获取时刻为MAC实体或RLC实体或PDCP实体获得数据的时刻。或者，数据的获取时刻可表示为MAC实体或RLC实体或PDCP实体获得数据的时隙编号或子帧编号或帧编号。数据的获取时刻也可以理解终端设备做好发送该数据的准备的时刻，本申请对此不做限制。
综上，若未知终端设备的数据获取情况(例如，数据的获取时刻、数据量)，网络设备对终端设备的调度可能会有较大时延，或者，网络设备可能无法在数据的时延预算内完成数据的传输。
有鉴于此，本申请实施例提供一种通信方法和通信装置，以期减小终端设备数据传输的时延，在数据的时延预算内完成数据的传输，从而提高通信的性能。
图4是本申请实施例提供的一种通信方法的示意性流程图。本申请中的交互流程图以网络设备和终端设备作为该交互示意的执行主体为例来示意相应的方法，但本申请并不限制交互示意的执行主体。例如，图中的网络设备也可以是支持该网络设备实现相应方法的芯片、芯片系统、或处理器，还可以是能实现全部或部分网络设备功能的逻辑模块或软件；图中的终端设备也可以是支持该终端设备实现相应方法的芯片、芯片系统、或处理器，还可以是能实现全部或部分终端设备功能的逻辑模块或软件。该方法至少可以包括以下几个步骤。
S410，网络设备向终端设备发送第一配置信息。
相应地，终端设备接收来自网络设备的该第一配置信息。
该第一配置信息可以用于配置第一阈值和第二阈值。该第一阈值可以是数据的剩余时延预算的阈值或数据的缓存时长的阈值；该第二阈值可以是数据的数据量的阈值或终端设备的缓存大小的阈值。
其中，数据的剩余时延预算可以指完成数据传输的剩余时长的上限。数据的剩余时延预算与数据的时延预算以及数据的缓存时长相关。数据的缓存时长可以指数据的获取时刻与数据的发送时刻之间的时长。数据的发送时刻可以是发送调度请求的时刻。具体地，数据的剩余时延预算可以为数据的时延预算与缓存时长的差。
需要说明的是，调度请求的发送时刻理解为调度请求的触发时刻或调度请求的实际发送时刻。调度请求的触发时刻可以在调度请求的实际发送时刻之前。调度请求的触发时刻和实际发送时刻之间的时间间隔可以很小，例如可以小于1毫秒(ms)，本申请对此不做限制。
还需要说明的是，在TDD系统中，上行时间单元(例如时隙)和下行时间单元(例如时隙)的数量和排列顺序可以预先配置，因此终端设备在发送调度请求前，可以确定发送调度请求的时刻。如图3中所示，当TDD的时隙配置为DDDSU时，数据的获取时刻为第一个上行时隙的结束时刻，终端设备可以确定在下一个上行时隙发送调度请求。
本申请中，时间单元可以是时隙、帧、子帧、时域符号等，对此不做限制。
可以理解，数据的剩余时延预算和数据的缓存时长可以相互替换，即在已知数据的时延预算的情况下，可以根据数据的剩余时延预算确定数据的缓存时长，或者，可以根据数据的缓存时长确定数据的剩余时延预算。例如，数据的时延预算为20ms，数据的获取时刻为第3ms，用于发送调度请求的上行时隙的起始时刻为第8ms，即数据的缓存时长为5ms，根据数据的时延预算以及数据的缓存时长可以确定数据的剩余时延预算为15ms。
数据的数据量也可以替换为终端设备的缓存大小。例如，数据的数据量可以为1000字节(Byte)，也可以说终端设备的缓存大小为1000字节。
以下主要以该第一阈值为数据的剩余时延预算阈值，该第二阈值为数据的数据量的阈值为例说明本申请实施例的方法，但这并不构成对本申请的限定。
示例性地，该第一配置信息可以是调度请求配置(SchedulingRequestToAddMod)信息或调度请求资源配置(SchedulingRequestResourceConfig)信息中的字段。
以该第一配置信息为SchedulingRequestToAddMod中的字段为例，该第一配置信息可以包括表示该第一阈值的remaining-Threshold字段和表示该第二阈值的BufferSize-Threshold字段：

其中，ms1表示1毫秒(ms)，Byte1000表示1000字节(Byte)，依次类推。应理解，上述第一阈值和第二阈值的取值仅为示例，第一阈值和第二阈值的大小可根据实际情况配置，对此不予限制。
S420，终端设备向网络设备发送调度请求。
相应地，网络设备接收来自终端设备的该调度请求。
该调度请求可以用于请求调度数据的资源。该调度请求可以指示数据的剩余时延预算与该第一阈值的大小关系，或数据的数据量与该第二阈值的大小关系中的至少一种。
示例性地，终端设备获取数据后，确定数据的获取时刻以及数据的数据量。终端设备可以根据数据的时延预算以及调度请求的发送时刻确定该数据的剩余时延预算。终端设备根据该第一阈值确定该数据的剩余时延预算与该第一阈值的大小关系。终端设备可以根据该第二阈值确定数据的数据量与该第二阈值的大小关系。
该调度请求可以承载于PUCCH。例如，可以由PUCCH格式0或PUCCH格式1承载。该调度请求可以包括用于指示数据的剩余时延预算与该第一阈值的大小关系，或数据的数据量与该第二阈值的大小关系中的至少一种的信息(为了方便描述，记为第一信息)。
该第一信息可以为2比特信息，该2bit信息的取值和含义可以是协议预先配置的。该2bit信息的取值和含义可以如表5至表8中的任一个所示。
表5
示例性地，依据表5，终端设备可以先确定数据的数据量，如果没有数据，或终端设备的缓存为空，则该2比特信息取值可以为“00”；如果数据的数据量小于第二阈值，则该2比特信息的取值可以为“01”。在终端设备确定数据的数据量大于或等于第二阈值的情况下，终端设备可以确定数据的剩余时延预算。如果数据的剩余时延预算大于或等于第一阈值，则该2比特信息的取值可以为“10”；如果数据的剩余时延预算小于第一阈值，则该2比特信息的取值可以为“11”。
表6
示例性地，依据表6，终端设备可以先确定是否有数据或终端设备的缓存是否为空，如果没有数据，或终端设备的缓存为空，则该2比特信息取值可以为“00”。在终端设备确定有数据或终端设备的缓存不为空的情况下，终端设备可以确定数据的剩余时延预算。如果数据的剩余时延预算大于或等于第一 阈值，则该2比特信息的取值可以为“01”。在终端设备确定数据的剩余时延预算小于第一阈值的情况下，终端设备可以确定数据的数据量。如果数据的数据量小于第二阈值，则该2比特信息的取值可以为“10”；如果数据的数据量大于或等于第二阈值，则该2比特信息的取值可以为“11”。
表7
示例性地，依据表7，终端设备可以确定数据的剩余时延预算以及数据的数据量。终端设备根据数据的剩余时延预算与第一阈值的大小关系，以及数据的数据量与第二阈值的大小关系，确定比特信息的取值。
表8
示例性地，依据表8，终端设备可以确定数据的剩余时延预算以及数据的数据量。并根据该数据的剩余时延预算为剩余时延预算列表中的第一值或第二值，以及该数据的数据量为数据量列表中的第一值或第二值，确定该2比特信息的取值。其中，剩余时延预算列表以及数据量列表可以由网络设备配置(参考第三配置的描述)。
可以理解，表5至表8仅为示例，不构成对本申请的限定。例如，表5至表8中，比特信息所表示的含义可以相互替换。再如，该调度请求中用于指示数据的剩余时延预算与该第一阈值的大小关系，或数据的数据量与该第二阈值的大小关系中的至少一种的信息可以大于2比特，该大于2比特的比特信息可以指示表5至表8中含义的任意组合；又如，表5至表8中的任一或两个比特取值可以不指示任何含义，或者说比特信息指示的含义保留。
进一步地，当该调度请求由PUCCH格式0承载，该调度请求中用于指示数据的剩余时延预算与该第一阈值的大小关系，或数据的数据量与该第二阈值的大小关系中的至少一种的信息包括2比特时，该2比特信息的取值与序列循环移位的取值的对应关系可以如表9中所示。
表9
例如，当比特信息的取值为{0,1}时，该PUCCH格式0的序列循环移位的取值为5。网络设备可以基于mcs＝5解读数据的剩余时延预算与该第一阈值的大小关系，和/或数据的数据量与该第二阈值的大小关系。
应理解，上述比特信息的取值和序列循环移位的取值仅为示例，比特信息的取值和序列循环移位的取值之间的对应关系也仅为示例。该比特信息{0,0}，{0,1}，{1,1}，{1,0}对应的mcs取值差值可以为3。该mcs的取值还可以为0，3，6，9或者2，4，7，11。
基于上述方案，在终端设备被配置了数据的剩余时延预算的阈值(第一阈值)以及数据的数据量(第二阈值)的情况下，终端设备可以向网络设备发送指示数据的剩余时延预算与该第一阈值的大小关系，和/或数据的数据量与该第二阈值的大小关系的调度请求，使得网络设备可以根据该调度请求调 度传输数据的资源，减少数据传输的时延，从而提高通信的性能。
可选地，该方法400还可以包括S430，网络设备向终端设备发送第二配置信息。
相应地，终端设备接收来自网络设备的该第二配置信息。
该第二配置信息可以用于配置该调度请求的发送。示例性地，该第二配置信息可以为SchedulingRequestToAddMod信息中的另一个字段，例如增强SR(enhanced-sr)字段。
即该enhanced-sr字段可用于配置调度请求的发送。例如，当enhanced-sr字段配置为true(或其他约定好的值)时，表示配置了终端设备发送指示数据的剩余时延预算和第一阈值的大小关系，或数据的数据量与第二阈值的大小关系中的至少一种的调度请求。
应理解，上述配置信息以及字段的名称仅为示例，本申请对此不做限制。
包括enhanced-sr字段的配置示例如下：
可选地，若enhanced-sr字段配置为false，则调度请求可以不指示数据的剩余时延预算与该第一阈值的大小关系，或数据的数据量与该第二阈值的大小关系中的至少一种。这种情况下，调度请求可以参考现有技术。
可选地，该方法400还可以包括S440，网络设备向终端设备发送第三配置信息。
相应地，终端设备接收来自网络设备的该第三配置信息。
该第三配置信息用于配置剩余时延预算列表和数据量列表。该剩余时延预算列表可以包括数据的剩余时延预算的至少一个值；该数据量列表可以包括数据的数据量的至少一个值。
示例性地，该第三配置信息可以为SchedulingRequestToAddMod信息中的剩余时延列表(sr-RemainingPDBList)字段和缓存大小(sr-BufferSizeList)字段。
其中，sr-RemainingPDBList和sr-BufferSizeList最少可以配置一个值，最多可以配置4个值。sr-RemainingPDBList中每个值的范围为大于或等于0，且小于或等于128；sr-BufferSizeList中每个值的范围为大于或等于1000，且小于或等于1000。
本申请中，当不同的配置信息(例如，第一配置信息，第二配置信息以及第三配置信息)为是同一个配置(例如，SchedulingRequestToAddMod)中的不同信元时，终端设备可通过接收一个配置获取不同的配置信息，或者，终端设备可通过接收不同的配置分别获取不同的配置信息，对此不予限制。
可选地，方法400还包括：
S450，网络设备向终端设备发送调度信息。
相应地，终端设备接收来自网络设备的该调度信息。
该调度信息可以用于数据的调度。示例性地，网络设备可以基于该调度请求确定该调度信息。该调度信息可以包括PUSCH资源信息。调度信息可以承载于PDCCH。例如通过DCI格式0_0或0_1向 终端设备发送调度信息。
可选地，若终端设备未收到该调度信息，该终端设备还可以继续向网络设备发送调度请求。
可选地，方法400还包括：
S460，终端设备向网络设备发送数据。
相应地，网络设备接收来自该终端设备的数据。
示例性地，该数据承载于PUSCH资源上，PUSCH资源由该PUSCH资源指示信息指示。数据还可以包括BSR信息，BSR信息用于告知网络设备还有多少数据需要发送。例如，如果BSR大于0，网络设备可以继续为终端设备配置传输数据的资源，以使终端设备在配置的资源上继续传输剩余数据。
图5是本申请实施例提供的另一种通信方法的示意性流程图。该方法至少包括以下几个步骤。
S510，网络设备向终端设备发送第四配置信息。
相应地，终端设备接收来自网络设备的该第四配置信息。
该第四配置信息可以用于配置该调度请求的发送，该调度请求指示数据的数据量与数据的剩余时延预算的比值。其中，数据量与数据的剩余时延预算的比值也可以称为数据的需求速率。
示例性地，该第五配置信息可以为SchedulingRequestToAddMod信息中的一个字段，例如增强SR(enhanced-sr)字段。
该enhanced-sr字段可用于配置调度请求的发送。例如，当enhanced-sr字段配置为true(或其他约定好的值)时，表示配置了终端设备发送数据的需求速率。
应理解，上述配置信息以及字段的名称仅为示例，本申请对此不做限制。
包括enhanced-sr字段的配置的示例如下：
可选地，若enhanced-sr字段配置为false，则调度请求可以不指示数据的需求速率。
S520，终端设备向网络设备发送调度请求。
相应地，网络设备接收来自终端设备的该调度请求。
该调度请求可以用于请求调度数据的资源。该调度请求可以指示数据的数据量与数据的剩余时延预算的比值。以下为了方便描述，将数据的数据量与数据的剩余时延预算的比值称为数据的需求速率。
示例性地，终端设备获取数据后，可以确定数据的获取时刻以及数据的数据量。终端设备根据数据的时延预算以及调度请求的发送时刻确定该数据的剩余时延预算。终端设备根据数据的数据量以及数据的剩余时延预算确定数据的需求速率。
该调度请求可以承载于PUCCH。例如，可以由PUCCH格式0或PUCCH格式1承载。该调度请求可以包括用于指示数据的需求速率的信息(记为第二信息)。
该第二信息可以为2比特信息，该2bit信息的取值和含义可以是协议预先配置的。该2bit信息的取值和含义可以如表10和表11中的任一个所示。
表10
终端设备可以根据数据的需求速率以及表10，确定该调度请求中指示数据的需求速率的2比特信息的取值。例如，若终端设备确定数据的需求速率为该需求速率列表中的第一个值，则该2比特信息 的取值为“00”。
表11
终端设备可以根据数据的需求速率以及表11，确定该调度请求中指示数据的需求速率的2比特信息的取值。例如，若终端设备确定数据的需求速率为R1，R1大于需求速率列表中的第一个值且小于需求速率列表中的第二个值，则该2比特信息的取值为“01”。
其中，需求速率列表可以参考第四配置的描述。
应理解，表10和表11中的比特信息的取值和含义仅为示例，本申请对此不做限制。其中，指示数据的需求速率的信息可以大于2比特，即网络设备可以指示更多需求速率的取值或需求速率取值的范围。
进一步地，当该调度请求由PUCCH格式0承载，该调度请求中用于指示数据的需求速率的信息包括2比特时，该2比特信息的取值与序列循环移位的取值的对应关系可以参考表9，不再赘述。
可选地，方法500还包括S530，网络设备向终端设备发送第五配置信息。
相应地，终端设备接收来自网络设备的该第五配置信息。该第五配置信息可以用于配置至少一个需求速率。
示例性地，第五配置信息为SchedulingRequestToAddMod信息中的一个字段，例如需求速率列表(RequiredDataRateList)字段。
该RequiredDataRateList字段配置至少一个值，该至少一个值中的每个值可以表示一种需求速率。
RequiredDataRateList配置的需求速率的值的数量以及每个值的取值范围可以预定义，RequiredDataRateList的预定义示例如下：
其中，RequiredDataRateList最少可以配置一个值，最多可以配置4个值。每个值的范围为大于或等于0，且小于或等于102400。以上取值仅为示例，RequiredDataRateList还可以配置其他数量和范围的值，对此不做限制。
可以理解，如果第四配置信息配置N个值，则指示数据的需求速率的信息包括的比特数为ceil(log2(N))。其中，ceil表示上取整函数，N为正整数。
本申请中，当不同的配置信息(例如，第四配置信息，第五配置信息)为是同一个配置(例如，SchedulingRequestToAddMod)中的不同信元时，终端设备可通过接收一个配置获取不同的配置信息，即S510和S530可以同时执行，或者，终端设备可通过接收不同的配置分别获取不同的配置信息，即步骤S510和S530可以分别执行，对此不予限制。
可选地，方法500还包括S540，网络设备向终端设备发送调度信息，该调度信息用于该数据的调度。
相应地，终端设备接收来自网络设备的该调度信息。
该步骤可以参考S450的描述。
可选地，方法500还包括S550，终端设备向网络设备发送数据。
相应地，网络设备接收来自该终端设备的数据。
该步骤可以参考S460的描述。
上述流程图中虚线步骤为可选地步骤，且各步骤的先后顺序依照方法的内在逻辑确定，上述流程图中所示的序号仅为示例，不对本申请步骤的先后顺序造成限制。
还应理解，本申请实施例提供的方法可以单独使用，也可以结合使用，本申请对此不做限制。本申请实施例提供的各种实施方式可以单独使用，也可以结合使用，本申请对此不做限制。本申请实施例提供的各种示例可以单独使用，也可以结合使用，本申请对此不做限制。
本申请实施例中的术语“至少一个”可以指一个或者多个；“多个”可以指两个或两个以上。字符“/”一般表示前后关联对象是一种“或”的关系。以下至少一个(项)或其类似表达，是指的这些项中的任意组合，包括单个(项)或复数个(项)的任意组合。a，b，或c中的至少一个(项)，可以表示：a，b，c，a-b，a-c，b-c，或a-b-c，其中a，b，c可以是单个，也可以是多个。
上文结合附图描述了本申请实施例的方法实施例，下面描述本申请实施例的装置实施例。可以理解，方法实施例的描述与装置实施例的描述可以相互对应，因此，未描述的部分可以参见前面方法实施例。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，各个网元，例如发射端设备或者接收端设备，为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对发射端设备或者接收端设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。下面以采用对应各个功能划分各个功能模块为例进行说明。
图6是本申请实施例提供的通信装置的示意性框图。图6所示的通信装置600包括接口单元610，可选地，该通信装置还包括处理单元620。接口单元610可以与外部进行通信，处理单元620用于进行数据处理。接口单元610还可以称为通信接口、收发单元或通信单元。
可选地，该通信装置600还可以包括存储单元，该存储单元可以用于存储指令或者和/或数据，处理单元620可以读取存储单元中的指令或者和/或数据。
在一种设计中，通信装置600可以用于执行上文方法实施例中终端设备所执行的动作。
可选地，该通信装置600可以为终端设备，接口单元610用于执行上文方法实施例中终端设备的接收或发送的操作，处理单元620用于执行上文方法实施例中终端设备内部处理的操作。
可选地，该通信装置600可以为配置在终端设备中的部件，例如，终端设备中的芯片。这种情况下，接口单元610可以为接口电路、管脚等。具体地，接口电路可以包括输入电路和输出电路，处理单元620可以包括处理电路。
一种可能的实现方式中，该接口单元610用于接收来自网络设备的第一配置信息，该第一配置信息用于配置第一阈值和第二阈值；该接口单元610还用于向该网络设备发送调度请求，该调度请求用于请求调度数据的资源，该调度请求指示该数据的剩余时延预算与该第一阈值的大小关系或该数据的数据量与该第二阈值的大小关系中的至少一种，该数据的剩余时延预算为完成该数据传输的剩余时长的上限。
一种可能的实现方式中，该调度请求指示以下关系中的一个：该数据的数据量小于该第二阈值；该数据的数据量大于或等于该第二阈值且该数据的剩余时延预算大于或等于该第一阈值；或，该数据的数据量大于或等于该第二阈值且该数据的剩余时延预算小于该第一阈值。
一种可能的实现方式中，该调度请求指示以下关系中的一个：该数据的剩余时延预算大于或等于该第一阈值；该数据的剩余时延预算小于该第一阈值且该数据的数据量小于该第二阈值；或，该数据的剩余时延预算小于该第一阈值且该数据的数据量大于或等于该第二阈值。
一种可能的实现方式中，该调度请求指示以下关系中的一个：该数据的剩余时延预算大于或等于该第一阈值且该数据的数据量小于该第二阈值；该数据的剩余时延预算大于或等于该第一阈值且该数据的数据量大于或等于该第二阈值；该数据的剩余时延预算小于该第一阈值且该数据的数据量小于该第二阈值；或，该数据的剩余时延预算小于该第一阈值且该数据的数据量大于或等于该第二阈值。
一种可能的实现方式中，该调度请求由物理上行控制信道PUCCH格式0承载。
一种可能的实现方式中，该接口单元610还用于接收来自该网络设备的第二配置信息；该处理单元用于控制该通信装置600根据该第二配置信息向该网络设备发送该调度请求。
在一种设计中，通信装置600可以用于执行上文方法实施例中网络设备所执行的动作。
可选地，该通信装置600可以为网络设备，接口单元610用于执行上文方法实施例中网络设备的接收或发送的操作，处理单元620用于执行上文方法实施例中网络设备内部处理的操作。
可选地，该通信装置600可以为配置在网络设备中的部件，例如，网络设备中的芯片。这种情况下，接口单元610可以为接口电路、管脚等。具体地，接口电路可以包括输入电路和输出电路，处理单元620可以包括处理电路。
一种可能的实现方式中，该接口单元用于向终端设备发送第一配置信息，该第一配置信息用于配置第一阈值和第二阈值；该接口单元还用于接收来自该终端设备的调度请求，该调度请求用于请求调度数据的资源，该调度请求指示该数据的剩余时延预算与该第一阈值的大小关系或该数据的数据量与该第二阈值的大小关系中的至少一种，该数据的剩余时延预算为完成该数据传输的剩余时长的上限。
该调度请求指示的大小关系可以参考上述第一种可能的设计，不再赘述。
一种可能的实现方式中，该调度请求由物理上行控制信道PUCCH格式0承载。
一种可能的实现方式中，该接口单元610还用于向该终端设备发送第二配置信息，该第二配置信息配置该调度请求的发送。
如图7所示，本申请实施例还提供一种通信装置700。该通信装置700包括处理器710，处理器710与存储器720耦合，存储器720用于存储计算机程序或指令或者和/或数据，处理器710用于执行存储器720存储的计算机程序或指令和/或者数据，使得上文方法实施例中的方法被执行。
可选地，该通信装置700包括的处理器710为一个或多个。
可选地，如图7所示，该通信装置700还可以包括存储器720。
可选地，该通信装置700包括的存储器720可以为一个或多个。
可选地，该存储器720可以与该处理器710集成在一起，或者分离设置。
可选地，如图7所示，该通信装置700还可以包括收发器730和/或通信接口，收发器730和/或通信接口用于信号的接收和/或发送。例如，处理器710用于控制收发器730和/或通信接口进行信号的接收和/或发送。
可选地，可以将收发器730中用于实现接收功能的器件视为接收模块，将收发器730中用于实现发送功能的器件视为发送模块，即收发器730包括接收器和发送器。收发器有时也可以称为收发机、收发模块、或收发电路等。接收器有时也可以称为接收机、接收模块、或接收电路等。发送器有时也可以称为发射机、发射器、发射模块或者发射电路等。
作为一种方案，该通信装置700用于实现上文方法实施例中由终端设备执行的操作。例如，处理器710用于实现上文方法实施例中由终端设备内部执行的操作，收发器730用于实现上文方法实施例中由终端设备执行的接收或发送的操作(例如S410至S460的操作，或者，S510至S550的操作)。
作为一种方案，该通信装置700用于实现上文方法实施例中由网络设备执行的操作。例如，处理器710用于实现上文方法实施例中由网络设备内部执行的操作，收发器730用于实现上文方法实施例中由网络设备执行的接收或发送的操作(例如S410至S460的操作或者，S510至S550的操作)。
图8示出了一种简化的通信装置的结构示意图。如图8所示，该通信装置800包括处理器、存储器、射频电路、天线以及输入输出装置。处理器主要用于对通信协议以及通信数据进行处理，以及对通信装置800进行控制，执行软件程序，处理软件程序的数据等。存储器主要用于存储软件程序和数 据。射频电路主要用于基带信号与射频信号的转换以及对射频信号的处理。天线主要用于收发电磁波形式的射频信号。输入输出装置，例如触摸屏、显示屏，键盘等主要用于接收用户输入的数据以及对用户输出数据。
当需要发送数据时，处理器对待发送的数据进行基带处理后，输出基带信号至射频电路，射频电路将基带信号进行射频处理后将射频信号通过天线以电磁波的形式向外发送。当有数据发送到通信装置800时，射频电路通过天线接收到射频信号，将射频信号转换为基带信号，并将基带信号输出至处理器，处理器将基带信号转换为数据并对该数据进行处理。为便于说明，图8中仅示出了一个存储器和处理器，在实际的产品中，可以存在一个或多个处理器和一个或多个存储器。存储器也可以称为存储介质或者存储设备等。存储器可以是独立于处理器设置，也可以是与处理器集成在一起，本申请实施例对此不做限制。
在本申请实施例中，可以将具有收发功能的天线和射频电路视为该通信装置800的收发单元，将具有处理功能的处理器视为通信装置800的处理单元。
如图8所示，该通信装置800包括收发单元810和处理单元820。收发单元810也可以称为收发器、收发机、收发装置或收发电路等。处理单元820也可以称为处理器，处理单板，处理模块、处理装置等。
可选地，可以将收发单元810中用于实现接收功能的器件视为接收单元，将收发单元810中用于实现发送功能的器件视为发送单元，即收发单元810包括接收单元和发送单元。接收单元有时也可以称为接收机、接收器、接收装置或接收电路等。发送单元有时也可以称为发射机、发射器、发射装置或发射电路等。
一种实现方式中，处理单元820和收发单元810用于执行终端设备的操作。
示例性地，收发单元810用于执行例如S410至S460的操作中的收发操作，或者，S510至S550的操作中的收发操作。
另一种实现方式中，处理单元820和收发单元810用于执行网络设备的操作。
示例性地，收发单元810用于执行例如S410至S460的操作中的收发操作，或者，S510至S550的操作中的收发操作。
应理解，图8仅为示例而非限定，上述包括收发单元和处理单元的通信装置800可以不依赖于图8所示的结构。
当该通信装置800为芯片时，该芯片包括收发单元和处理单元。其中，收发单元可以是输入输出电路或通信接口；处理单元可以为该芯片上集成的处理器或者微处理器或者集成电路。
如图9，本申请实施例还提供了一种通信装置900。该通信装置900包括逻辑电路910以及输入/输出接口(input/output interface)920。
其中，逻辑电路910可以为通信装置900中的处理电路。逻辑电路910可以耦合连接存储单元，调用存储单元中的指令，使得通信装置900可以实现本申请各实施例的方法和功能。输入/输出接口920，可以为通信装置900中的输入输出电路，将通信装置900处理好的信息输出，或将待处理的数据或信令信息输入通信装置900进行处理。
作为一种方案，该通信装置900用于实现上文各个方法实施例中由终端设备执行的操作。
例如，逻辑电路910用于实现上文方法实施例中由终端设备执行的处理相关的操作。输入/输出接口920用于实现上文方法实施例中由终端设备执行的发送和/或接收相关的操作。逻辑电路910执行的操作具体可以参见上文对处理单元620的说明，输入/输出接口920执行的操作可以参见上文对接口单元610的说明，这里不再赘述。
作为另一种方案，该通信装置900用于实现上文各个方法实施例中由网络设备执行的操作。
例如，逻辑电路910用于实现上文方法实施例中由网络设备执行的处理相关的操作，如，方法实施例中的网络设备执行的处理相关的操作，输入/输出接口920用于实现上文方法实施例中由网络设备执行的发送和/或接收相关的操作。逻辑电路910执行的操作具体可以参见上文对处理单元620的说明。输入/输出接口920执行的操作可以参见上文对收发单元610的说明，这里不再赘述。
应理解，上述通信装置可以是一个或多个芯片。例如，该通信装置可以是现场可编程门阵列(field programmable gate array，FPGA)，可以是专用集成芯片(application specific integrated circuit，ASIC)， 还可以是系统芯片(system on chip，SoC)，还可以是中央处理器(central processor unit，CPU)，还可以是网络处理器(network processor，NP)，还可以是数字信号处理电路(digital signal processor，DSP)，还可以是微控制器(micro controller unit，MCU)，还可以是可编程控制器(programmable logic device，PLD)或其他集成芯片。
在实现过程中，上述方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。
应注意，本申请实施例中的处理器可以是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
根据本申请实施例提供的方法，本申请还提供一种计算机可读介质，该计算机可读介质存储有程序代码，当该程序代码在计算机上运行时，使得该计算机执行方法实施例所示的方法。例如，该计算机程序被计算机执行时，使得该计算机可以实现上述方法实施例中由终端设备执行的方法，或由网络设备执行的方法。
本申请实施例还提供一种包含指令的计算机程序产品，该指令被计算机执行时使得该计算机实现上述方法实施例中由终端设备执行的方法，或由网络设备执行的方法。
上述提供的任一种通信装置中相关内容的解释及有益效果均可参考上文提供的对应的方法实施例，此处不再赘述。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital  video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state drive，SSD))等。
上述各个装置实施例中的终端设备，网络设备与方法实施例中的终端设备，网络设备对应，由相应的模块或单元执行相应的步骤，例如通信单元(收发器)执行方法实施例中接收或发送的步骤，除发送、接收外的其它步骤可以由处理单元(处理器)执行。具体单元的功能可以参考相应的方法实施例。其中，处理器可以为一个或多个。
在本说明书中使用的术语“部件”、“模块”、“系统”等用于表示计算机相关的实体、硬件、固件、硬件和软件的组合、软件、或执行中的软件。例如，部件可以是但不限于，在处理器上运行的进程、处理器、对象、可执行文件、执行线程、程序和/或计算机。通过图示，在计算设备上运行的应用和计算设备都可以是部件。一个或多个部件可驻留在进程和/或执行线程中，部件可位于一个计算机上和/或分布在两个或更多个计算机之间。此外，这些部件可从在上面存储有各种数据结构的各种计算机可读介质执行。部件可例如根据具有一个或多个数据分组(例如来自与本地系统、分布式系统和/或网络间的另一部件交互的二个部件的数据，例如通过信号与其它系统交互的互联网)的信号通过本地和/或远程进程来通信。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (31)

  1. 一种通信方法，其特征在于，包括：
    接收来自网络设备的第一配置信息，所述第一配置信息用于配置第一阈值和第二阈值；
    向所述网络设备发送调度请求，所述调度请求用于请求调度数据的资源，所述调度请求指示所述数据的剩余时延预算与所述第一阈值的大小关系或所述数据的数据量与所述第二阈值的大小关系中的至少一种，所述数据的剩余时延预算为完成所述数据传输的剩余时长的上限。
  2. 根据权利要求1所述的方法，其特征在于，所述调度请求指示以下关系中的一个：
    所述数据的数据量小于所述第二阈值；
    所述数据的数据量大于或等于所述第二阈值且所述数据的剩余时延预算大于或等于所述第一阈值；或，
    所述数据的数据量大于或等于所述第二阈值且所述数据的剩余时延预算小于所述第一阈值。
  3. 根据权利要求1所述的方法，其特征在于，所述调度请求指示以下关系中的一个：
    所述数据的剩余时延预算大于或等于所述第一阈值；
    所述数据的剩余时延预算小于所述第一阈值且所述数据的数据量小于所述第二阈值；或，
    所述数据的剩余时延预算小于所述第一阈值且所述数据的数据量大于或等于所述第二阈值。
  4. 根据权利要求1所述的方法，其特征在于，所述调度请求指示以下关系中的一个：
    所述数据的剩余时延预算大于或等于所述第一阈值且所述数据的数据量小于所述第二阈值；
    所述数据的剩余时延预算大于或等于所述第一阈值且所述数据的数据量大于或等于所述第二阈值；
    所述数据的剩余时延预算小于所述第一阈值且所述数据的数据量小于所述第二阈值；或，
    所述数据的剩余时延预算小于所述第一阈值且所述数据的数据量大于或等于所述第二阈值。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，所述调度请求由物理上行控制信道PUCCH格式0承载。
  6. 根据权利要求1至5中任一项所述的方法，其特征在于，所述方法还包括：
    接收来自所述网络设备的第二配置信息，
    所述向所述网络设备发送调度请求包括：
    根据所述第二配置信息向所述网络设备发送所述调度请求。
  7. 一种通信方法，其特征在于，包括：
    向终端设备发送第一配置信息，所述第一配置信息用于配置第一阈值和第二阈值；
    接收来自所述终端设备的调度请求，所述调度请求用于请求调度数据的资源，所述调度请求指示所述数据的剩余时延预算与所述第一阈值的大小关系或所述数据的数据量与所述第二阈值的大小关系中的至少一种，所述数据的剩余时延预算为完成所述数据传输的剩余时长的上限。
  8. 根据权利要求7所述的方法，其特征在于，所述调度请求指示以下关系中的一个：
    所述数据的数据量小于所述第二阈值；
    所述数据的数据量大于或等于所述第二阈值且所述数据的剩余时延预算大于或等于所述第一阈值；或，
    所述数据的数据量大于或等于所述第二阈值且所述数据的剩余时延预算小于所述第一阈值。
  9. 根据权利要求7所述的方法，其特征在于，所述调度请求指示以下关系中的一个：
    所述数据的剩余时延预算大于或等于所述第一阈值；
    所述数据的剩余时延预算小于所述第一阈值且所述数据的数据量小于所述第二阈值；或，
    所述数据的剩余时延预算小于所述第一阈值且所述数据的数据量大于或等于所述第二阈值。
  10. 根据权利要求7所述的方法，其特征在于，所述调度请求指示以下关系中的一个：
    所述数据的剩余时延预算大于或等于所述第一阈值且所述数据的数据量小于所述第二阈值；
    所述数据的剩余时延预算大于或等于所述第一阈值且所述数据的数据量大于或等于所述第二阈值；
    所述数据的剩余时延预算小于所述第一阈值且所述数据的数据量小于所述第二阈值；或，
    所述数据的剩余时延预算小于所述第一阈值且所述数据的数据量大于或等于所述第二阈值。
  11. 根据权利要求7至10中任一项所述的方法，其特征在于，所述调度请求由物理上行控制信道PUCCH格式0承载。
  12. 根据权利要求7至11中任一项所述的方法，其特征在于，所述方法还包括：
    向所述终端设备发送第二配置信息，所述第二配置信息配置所述调度请求的发送。
  13. 一种通信装置，其特征在于，所述装置包括接口单元，
    所述接口单元用于，接收来自网络设备的第一配置信息，所述第一配置信息用于配置第一阈值和第二阈值；
    所述接口单元还用于，向所述网络设备发送调度请求，所述调度请求用于请求调度数据的资源，所述调度请求指示所述数据的剩余时延预算与所述第一阈值的大小关系或所述数据的数据量与所述第二阈值的大小关系中的至少一种，所述数据的剩余时延预算为完成所述数据传输的剩余时长的上限。
  14. 根据权利要求13所述的装置，其特征在于，所述调度请求指示以下关系中的一个：
    所述数据的数据量小于所述第二阈值；
    所述数据的数据量大于或等于所述第二阈值且所述数据的剩余时延预算大于或等于所述第一阈值；或，
    所述数据的数据量大于或等于所述第二阈值且所述数据的剩余时延预算小于所述第一阈值。
  15. 根据权利要求13所述的装置，其特征在于，所述调度请求指示以下关系中的一个：
    所述数据的剩余时延预算大于或等于所述第一阈值；
    所述数据的剩余时延预算小于所述第一阈值且所述数据的数据量小于所述第二阈值；或，
    所述数据的剩余时延预算小于所述第一阈值且所述数据的数据量大于或等于所述第二阈值。
  16. 根据权利要求13所述的装置，其特征在于，所述调度请求指示以下关系中的一个：
    所述数据的剩余时延预算大于或等于所述第一阈值且所述数据的数据量小于所述第二阈值；
    所述数据的剩余时延预算大于或等于所述第一阈值且所述数据的数据量大于或等于所述第二阈值；
    所述数据的剩余时延预算小于所述第一阈值且所述数据的数据量小于所述第二阈值；或，
    所述数据的剩余时延预算小于所述第一阈值且所述数据的数据量大于或等于所述第二阈值。
  17. 根据权利要求13至16中任一项所述的装置，其特征在于，所述调度请求由物理上行控制信道PUCCH格式0承载。
  18. 根据权利要求13至17中任一项所述的装置，其特征在于，所述接口单元还用于，接收来自所述网络设备的第二配置信息，
    所述装置还包括处理单元，所述处理单元用于：
    根据所述第二配置信息控制所述装置向所述网络设备发送所述调度请求。
  19. 一种通信装置，其特征在于，所述装置包括接口单元，
    所述接口单元用于，向终端设备发送第一配置信息，所述第一配置信息用于配置第一阈值和第二阈值；
    所述接口单元还用于，接收来自所述终端设备的调度请求，所述调度请求用于请求调度数据的资源，所述调度请求指示所述数据的剩余时延预算与所述第一阈值的大小关系或所述数据的数据量与所述第二阈值的大小关系中的至少一种，所述数据的剩余时延预算为完成所述数据传输的剩余时长的上限。
  20. 根据权利要求19所述的装置，其特征在于，所述调度请求指示以下关系中的一个：
    所述数据的数据量小于所述第二阈值；
    所述数据的数据量大于或等于所述第二阈值且所述数据的剩余时延预算大于或等于所述第一阈值；或，
    所述数据的数据量大于或等于所述第二阈值且所述数据的剩余时延预算小于所述第一阈值。
  21. 根据权利要求19所述的装置，其特征在于，所述调度请求指示以下关系中的一个：
    所述数据的剩余时延预算大于或等于所述第一阈值；
    所述数据的剩余时延预算小于所述第一阈值且所述数据的数据量小于所述第二阈值；或，
    所述数据的剩余时延预算小于所述第一阈值且所述数据的数据量大于或等于所述第二阈值。
  22. 根据权利要求19所述的装置，其特征在于，所述调度请求指示以下关系中的一个：
    所述数据的剩余时延预算大于或等于所述第一阈值且所述数据的数据量小于所述第二阈值；
    所述数据的剩余时延预算大于或等于所述第一阈值且所述数据的数据量大于或等于所述第二阈值；
    所述数据的剩余时延预算小于所述第一阈值且所述数据的数据量小于所述第二阈值；或，
    所述数据的剩余时延预算小于所述第一阈值且所述数据的数据量大于或等于所述第二阈值。
  23. 根据权利要求19至22中任一项所述的装置，其特征在于，所述调度请求由物理上行控制信道PUCCH格式0承载。
  24. 根据权利要求19至23中任一项所述的装置，其特征在于，所述接口单元还用于：
    向所述终端设备发送第二配置信息，所述第二配置信息配置所述调度请求的发送。
  25. 一种通信装置，其特征在于，所述装置包括用于执行如权利要求1至6中任一项方法的单元。
  26. 一种通信装置，其特征在于，所述装置包括用于执行如权利要求7至12中任一项方法的单元。
  27. 一种通信装置，其特征在于，所述装置包括处理器，所述处理器与存储器耦合，所述存储器存储有指令，所述指令被所述处理器运行时，使得所述装置执行如权利要求1至6中任一项所述的方法。
  28. 一种通信装置，其特征在于，所述装置包括处理器，所述处理器与存储器耦合，所述存储器存储有指令，所述指令被所述处理器运行时，使得所述装置执行如权利要求7至12中任一项所述的方法。
  29. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质用于存储计算机程序，当所述计算机程序在计算机上运行时，使得所述计算机执行如权利要求1至6中任一项所述的方法，或执行如权利要求7至12中任一项所述的方法。
  30. 一种计算机程序产品，其特征在于，所述计算机程序产品包括：计算机程序代码，当所述计算机程序代码被运行时，实现如权利要求1至6中任一项所述的方法，或执行如权利要求7至12中任一项所述的方法。
  31. 一种通信系统，其特征在于，包括如权利要求13至18中任一项所述的装置和如权利要求19至24中任一项所述的装置。
PCT/CN2023/119198 2022-09-29 2023-09-15 一种数据传输的方法和装置 WO2024067172A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211199834.0A CN117793932A (zh) 2022-09-29 2022-09-29 一种数据传输的方法和装置
CN202211199834.0 2022-09-29

Publications (1)

Publication Number Publication Date
WO2024067172A1 true WO2024067172A1 (zh) 2024-04-04

Family

ID=90384104

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/119198 WO2024067172A1 (zh) 2022-09-29 2023-09-15 一种数据传输的方法和装置

Country Status (2)

Country Link
CN (1) CN117793932A (zh)
WO (1) WO2024067172A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106304377A (zh) * 2015-06-04 2017-01-04 电信科学技术研究院 一种进行调度的方法和设备
CN109156025A (zh) * 2017-04-27 2019-01-04 北京小米移动软件有限公司 上行资源获取方法、装置及计算机可读存储介质
CN112996115A (zh) * 2019-12-18 2021-06-18 大唐移动通信设备有限公司 一种上行资源分配的方法及装置
WO2022061774A1 (zh) * 2020-09-25 2022-03-31 Oppo广东移动通信有限公司 无线通信方法和终端

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106304377A (zh) * 2015-06-04 2017-01-04 电信科学技术研究院 一种进行调度的方法和设备
CN109156025A (zh) * 2017-04-27 2019-01-04 北京小米移动软件有限公司 上行资源获取方法、装置及计算机可读存储介质
CN112996115A (zh) * 2019-12-18 2021-06-18 大唐移动通信设备有限公司 一种上行资源分配的方法及装置
WO2022061774A1 (zh) * 2020-09-25 2022-03-31 Oppo广东移动通信有限公司 无线通信方法和终端

Also Published As

Publication number Publication date
CN117793932A (zh) 2024-03-29

Similar Documents

Publication Publication Date Title
WO2021180098A1 (zh) 无线通信方法和通信装置
WO2020191781A1 (zh) 一种数据传输方法及装置
WO2021031202A1 (zh) 数据传输的方法和装置
WO2019029463A1 (zh) 一种接收控制信息、发送控制信息的方法及设备
WO2021027551A1 (zh) 一种通信方法及装置
WO2021081696A1 (zh) 传输数据的方法和通信装置
WO2021027806A1 (zh) 信息传输的方法和装置
KR102298616B1 (ko) 비-트리거-기반 레인징을 위한 절전
WO2020199034A1 (zh) 用于中继通信的方法和装置
KR20240003733A (ko) 무선 네트워킹 시스템들에 대한 향상된 어드레스 변경
WO2024067172A1 (zh) 一种数据传输的方法和装置
WO2021249218A1 (zh) 数据传输方法和装置
WO2022077351A1 (zh) 通信方法和通信装置
WO2021027904A1 (zh) 无线通信的方法和装置以及通信设备
WO2021000954A1 (zh) 一种数据传输方法及通信装置
WO2024007814A1 (zh) 数据的传输方法和装置
JP7440641B2 (ja) プライマリセルクロスキャリアスケジューリングの管理
WO2020147768A1 (zh) 处理数据的方法和处理数据的装置
WO2020097920A1 (zh) 参数重配的方法和装置
WO2021088062A1 (zh) 一种通信方法及装置
WO2021056585A1 (zh) 一种混合自动重传请求反馈方法及装置
WO2020164148A1 (zh) 一种数据传输方法和设备
WO2020088538A1 (zh) 一种通信方法及装置
WO2024067171A1 (zh) 一种通信方法和装置
WO2023231636A1 (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: 23870406

Country of ref document: EP

Kind code of ref document: A1