WO2018202022A1 - 用于传输缓存状态报告的方法和装置 - Google Patents

用于传输缓存状态报告的方法和装置 Download PDF

Info

Publication number
WO2018202022A1
WO2018202022A1 PCT/CN2018/085189 CN2018085189W WO2018202022A1 WO 2018202022 A1 WO2018202022 A1 WO 2018202022A1 CN 2018085189 W CN2018085189 W CN 2018085189W WO 2018202022 A1 WO2018202022 A1 WO 2018202022A1
Authority
WO
WIPO (PCT)
Prior art keywords
numerology
logical channel
channel group
terminal device
target
Prior art date
Application number
PCT/CN2018/085189
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 WO2018202022A1 publication Critical patent/WO2018202022A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0278—Traffic management, e.g. flow control or congestion control using buffer status reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control

Definitions

  • the present application relates to the field of communications and, more particularly, to methods and apparatus for transmitting buffer status reports.
  • the same LCH supports only one numerology (Numerology).
  • the base station allocates a logical channel group (LCG) to which the logical channel (LCH) belongs, and one LCG may include one or more LCHs.
  • the terminal may request an uplink transmission resource by sending a Buffer Status Report (BSR) to the base station, where the buffered data amount may be reported in units of LCG.
  • BSR Buffer Status Report
  • Future wireless communication systems can support multiple scenarios and different types of services, such as Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC), and ultra-reliable low-latency communication (Ultra) Reliable-Low Latency Communication, URLLC), and more.
  • eMBB Enhanced Mobile Broadband
  • mMTC Massive Machine Type Communication
  • Ultra Ultra-reliable low-latency Communication
  • URLLC Ultra-reliable-Low Latency Communication
  • Different service types have different requirements for transmission capabilities. For example, URLLC pays more attention to delay and eMBB pays more attention to bandwidth.
  • the system can configure multiple numerologies for the same logical channel (LCH) to support the transmission needs of different service scenarios. In this way, the technical solution for requesting uplink transmission resources in LTE will no longer be applicable to future wireless communication systems.
  • LCH logical channel
  • the present application provides a method for transmitting a buffer status report, which can be applied to report the amount of buffered data of a logical channel supporting multiple numerology.
  • the first aspect provides a method for transmitting a buffer status report, including: determining, by the terminal device, a target logical channel group to which the first logical channel belongs according to a numerology attribute corresponding to each logical channel group in the at least one logical channel group, The first logical channel supports at least one numerology, each numerology includes at least one physical transmission parameter; the terminal device sends a buffer status report to the network device, where the buffer status report includes at least one logical channel belonging to the target logical channel group The at least one logical channel includes the first logical channel.
  • the terminal device determines, according to a numerology attribute corresponding to each logical channel group in the at least one logical channel group, a target logical channel group to which the first logical channel belongs, including: the terminal The device determines a numerology attribute requirement of the first logical channel; the terminal device determines the target logical channel group according to a numerology attribute requirement of the first logical channel and a numerology attribute corresponding to each logical channel group in the at least one logical channel group.
  • the terminal device determines, by the terminal device, the logical channel group that meets the minimum numerology attribute requirement of the first logical channel of the at least one logical channel group as The target logical channel group.
  • the numerology attribute requirement of the first logical channel may include: the value of the first physical transmission parameter is equal to a preset threshold.
  • the numerology attribute corresponding to each logical channel group in the at least one logical channel group may include: a value of the first physical transmission parameter corresponding to each logical channel group.
  • the terminal device may determine, as the target logical channel group, the logical channel group corresponding to the first physical transmission parameter in the at least one logical channel group to be equal to the preset threshold.
  • the terminal device may determine a candidate logical channel group randomly selected from the at least one candidate logical channel group as the target logical channel group.
  • the terminal device determines, as the target logical channel group, the logical channel group that meets the minimum requirement of the numerology attribute of the first logical channel in the at least one logical channel group, where the terminal device determines the target TTI length,
  • the target TTI length is a maximum value of at least one candidate TTI length
  • the numerology attribute corresponding to the at least one logical channel group includes the at least one candidate TTI length
  • each candidate TTI length in the at least one candidate TTI length is less than Or equal to the maximum TTI length of the first logical channel.
  • the terminal device determines, as the target logical channel group, the logical channel group that meets the minimum numerology attribute requirement of the first logical channel in the at least one logical channel group, where the terminal device determines the target SCS, where The target SCS is a minimum value in the at least one candidate SCS, the numerology attribute corresponding to the at least one logical channel group includes the at least one candidate SCS, and each candidate SCS in the at least one candidate SCS is less than or equal to the first logic The minimum SCS of the channel.
  • the terminal device stores a logical channel group attribute table, where the entry in the logical channel group attribute table includes a logical channel group identifier and a numerology attribute corresponding to the logical channel group identifier; the terminal device is configured according to the first logical channel
  • the numerology attribute requirement and the numerology attribute corresponding to each logical channel group in the at least one logical channel group determine the target logical channel group to which the first logical channel belongs, including: the terminal device requires the numerology attribute of the first logical channel by using Querying the logical channel group attribute table to determine a target logical channel group that satisfies the requirement of the numerology attribute of the first logical channel.
  • the terminal device according to a numerology attribute requirement of the first logical channel, and each logical channel in the at least one logical channel group Determining, by the numerology attribute of the group, the target logical channel group to which the first logical channel belongs, the method includes: the terminal device, the logical channel group corresponding to the value of the first physical transmission parameter in the at least one logical channel group being equal to the preset threshold Determined as the target logical channel group.
  • the method further includes: the terminal device receiving the first indication information from the network device, where the first indication information indicates a numerology attribute corresponding to each logical channel group in the at least one logical channel group.
  • the terminal device receives the first indication information from the network device, where the terminal device receives the RRC signaling from the network device, where the RRC signaling includes the first indication information.
  • a method for transmitting a buffer status report including: determining, by a terminal device, a target numerology from at least one numerology supported by a first logical channel, wherein each of the at least one numerology includes at least one a physical transmission parameter; the terminal device sends a buffer status report to the network device, where the buffer status report includes an amount of data to be sent of the at least one logical channel corresponding to the target numerology, wherein the at least one logical channel includes the first logical channel.
  • the terminal device determines the target numerology from the at least one numerology supported by the first logical channel, including: the terminal device according to the parameter set numerology attribute requirement of the first logical channel, The target numerology is determined in at least one of the numerology supported by the first logical channel.
  • the terminal device determines the target numerology from the at least one numerology supported by the first logical channel according to the numerology attribute requirement of the first logical channel, including: the terminal device satisfies the at least one numerology to the minimum
  • the numerology attribute of a logical channel's numerology attribute is determined as the target numerology.
  • the numerology attribute requirement of the first logical channel includes: the value of the first physical transmission parameter is equal to a preset threshold.
  • each of the at least one numerology includes a value of the first physical transmission parameter.
  • the terminal device determines, according to the numerology attribute requirement of the first logical channel, the target numerology from the at least one numerology supported by the first logical channel, where the terminal device includes the first physics included in the at least one numerology
  • the value of the transmission parameter is equal to the numerology of the preset threshold determined as the target numerology.
  • the terminal device may A candidate numerology randomly selected from a candidate numerology is determined as the target numerology.
  • the terminal device determines, as the target numerology, the numerology of the at least one numerology that satisfies the numerology attribute requirement of the first logical channel, the terminal device determines the target numerology from the at least one numerology,
  • the numerology is a numerology having a maximum value of a TTI length included in at least one candidate numerology, the at least one numerology includes the at least one candidate numerology, and each candidate numerology in the at least one candidate numerology includes a value of a TTI length less than or Equal to the maximum TTI length of the first logical channel.
  • an apparatus for transmitting a buffer status report for performing the method of any of the above aspects or any possible implementation of any of the aspects.
  • the apparatus comprises means for performing the method of any of the above-described aspects or any of the possible implementations of any of the aspects.
  • another apparatus for transmitting a buffer status report comprising: a memory and a processor for storing instructions for executing instructions stored by the memory, and when the processor executes the The execution of the memory causes the processor to perform the method of any aspect or any of the possible implementations of any aspect.
  • a computer readable medium for storing a computer program comprising instructions for performing the method of any of the aspects or any of the possible implementations of any aspect.
  • the numerology attribute corresponding to the LCG may include a numerology corresponding to the LCG or at least one physical transmission parameter value corresponding to the LCG.
  • the numerology attribute corresponding to the LCG may include a TTI length.
  • the numerology attribute requirement of the logical channel may be used to select an LCG to which the LCH belongs, or to buffer data of the LCH.
  • the physical transmission parameters associated with the LCH when performing BSR reporting may be configured, or the rules for selecting the LCG by the LCH may be configured.
  • the numerology attribute requirement of the LCH or the LCG may include: the value of one or more physical transmission parameters satisfying certain conditions.
  • the numerology attribute requirement of the LCH or the LCG may include at least one of the following: a value of the first physical transmission parameter is equal to a preset threshold, a TTI length is less than or equal to a maximum TTI duration, and an SCS is greater than or equal to Minimum SCS (minimum SCS).
  • the minimum numerology attribute requirement that satisfies the LCH or the LCG may refer to at least one of the following: the value of the corresponding physical transmission parameter is equal to a preset threshold, and the maximum TTI length less than or equal to the maximum TTI duration is greater than or Equal to the maximum SCS of the minimum SCS.
  • the physical transmission parameter value may refer to a value of a physical transmission parameter
  • the plurality of physical transmission parameter values may refer to a value of each of a plurality of different physical transmission parameters.
  • the physical transmission parameter herein may be a physical transmission parameter included in the numerology.
  • the network device may send the second indication information to the terminal device, and the terminal device receives the second indication information sent by the network device, where the second indication information is used by the second device.
  • the network device Indicates the numerology attribute requirement of the first logical channel.
  • the numerology attribute corresponding to the logical channel group may be predefined, or the network device is configured through RRC signaling.
  • the buffer status report includes a logical channel group identification field and a buffer size field, where the logical channel group identification field is used to carry identification information of a logical channel group, the cache size field The amount of data to be transmitted used to carry at least one logical channel belonging to the logical channel group.
  • the buffer status report includes N cache size fields corresponding to the N logical channel groups, where a buffer size field corresponding to a certain logical channel group is used to carry at least one logical channel belonging to the logical channel group.
  • the amount of data sent, N is an integer greater than or equal to 1.
  • the cache status report may include: a numerology identifier field and a cache size field, where the numerology identifier field is used to carry a number of a numerology, and the cache size field is used to carry at least one logic corresponding to the numerology The amount of data to be sent for the channel.
  • the cache status report may not include an LCG identification field.
  • the cache status report includes N cache size fields corresponding to the N numerology, where a buffer size field corresponding to a certain numerology is used to carry at least one logical channel belonging to the numerology to be sent.
  • the amount of data, N is an integer greater than or equal to 1.
  • the network device may receive a buffer status report from the terminal device, and allocate an uplink transmission resource according to the cached status report associated numerology.
  • the network device may allocate the uplink transmission resource according to the numerology attribute corresponding to the logical channel group.
  • the network device may allocate the uplink transmission according to the value of the at least one physical transmission parameter included in the target numerology. Resources.
  • the network device may allocate an uplink transmission resource for the amount of data to be sent according to the numerology or the LCG corresponding to the field occupied by the BSR.
  • the network device sends the first indication information to the terminal device, and the terminal device receives the first indication information that is sent by the network device, where the first indication information is used to indicate each logical channel in the at least one logical channel group.
  • the corresponding numerology attribute of the group is used to indicate each logical channel in the at least one logical channel group.
  • the network device sends the second indication information to the terminal device, and the terminal device receives the second indication information from the network device, where the second indication information is used to indicate the numerology attribute requirement corresponding to the logical channel.
  • the network device sends the third indication information to the terminal device, and the terminal device receives the third indication information from the network device, where the third indication information is used to indicate the BSR corresponding to each of the plurality of numerologies. Retransmission timer.
  • different numerologies correspond to different BSR retransmission timers.
  • the terminal device sends a buffer status report to the network device, and starts a BSR retransmission timer corresponding to the numerology associated with the cache status report.
  • the terminal device sends a buffer status report to the network device, and starts a BSR retransmission timer corresponding to each numerology associated with the cache status report.
  • the terminal device does not receive an uplink grant for allocating an uplink transmission resource corresponding to the numerology from the network device, and the terminal device The retransmission request corresponds to the BSR of the uplink transmission resource of the numerology, and restarts the BSR retransmission timer corresponding to the first numerology.
  • the terminal device if the terminal device receives the UL Grant for allocating the uplink transmission resource corresponding to the numerology, the terminal device stops the BSR corresponding to the numerology if the BSR retransmission timer corresponding to the numerology does not expire. Retransmission timer.
  • the BSR retransmission timers corresponding to different numerologies are independent of each other.
  • the terminal device may trigger or send a BSR associated with the second numerology.
  • the terminal device determines the target cache status report from the multiple cache status reports according to the multiple cache status report associated numerology; the terminal device Send the target cache status report.
  • the terminal device optionally, if the terminal device simultaneously triggers the first cache status report and the second cache status report, and the first cache status report and the second cache status report request are associated with the same numerology, the terminal device revokes One of the cache status reports.
  • the terminal device ie, MAC entity
  • the terminal device can only send at most one BSR associated with the same numerology within each scheduling interval (ie, each TTI).
  • each MAC PDU may include a BSR associated with a different numerology. That is, multiple MAC PDUs may include multiple BSRs, and any two of the multiple BSRs associate different numerologies.
  • the terminal device may be in the transmission time interval.
  • the first MAC PDU includes the first cache status report
  • the second cache status report is included in the second MAC PDU in the current transmission time interval.
  • the sent cache status report may be selected according to the priority of the reported LCH in the cache status report.
  • the first buffer status report includes the amount of data to be sent belonging to the at least one first logical channel of the first logical channel group
  • the second buffer status report includes at least the second logical channel group
  • the amount of data to be sent of the second logical channel, the first buffer status report and the second buffer status report are associated with the same numerology, and the highest priority of the at least one second logical channel is higher than the corresponding one of the at least one first logical channel The highest priority, you can undo the first cache status report.
  • the numerology associated with the cache status report may be determined according to a numerology attribute corresponding to the first logical channel group in the cache status report.
  • the terminal device may determine the target logical channel from the at least one logical channel according to the priority corresponding to each logical channel in the at least one logical channel reported by the BSR; and the numerology according to the target logical channel.
  • the attribute requirements determine the numerology associated with the cache status report.
  • the terminal device determines an uplink transmission resource that is matched by the BSR, and sends the BSR on the uplink transmission resource that is matched by the BSR.
  • the terminal device may determine, according to the numerology attribute requirement corresponding to the first logical channel group in the buffer status report, the uplink transmission resource that matches the buffer status report.
  • the terminal device may determine, as the uplink transmission resource that the BSR matches, the uplink transmission resource that meets the minimum requirement of the numerology attribute corresponding to the first logical channel group.
  • the numerology attribute corresponding to the first logical channel group includes a value of the first physical transmission parameter corresponding to the first logical channel, and the first physical transmission parameter corresponding to the matched uplink transmission resource.
  • the value is equal to the value of the first physical transmission parameter corresponding to the first logical channel.
  • the method further includes: if the cache status report includes the a quantity of data to be transmitted of at least one logical channel of the first logical channel group, the terminal device determining a target logical channel from the at least one logical channel according to a priority corresponding to each logical channel of the at least one logical channel; the terminal device Determining a numerology attribute requirement of the first logical channel group according to a numerology attribute requirement of the target logical channel.
  • the terminal device sends a buffer status report to the network device; if the retransmission timer corresponding to the buffer status report does not time out, and the terminal device finds an available uplink transmission resource for transmitting the scheduling request, The terminal device sends a scheduling request to the network device on the available uplink transmission resource, where the end time of the available uplink transmission resource is earlier than the end time of the uplink transmission resource occupied by the buffer status report.
  • FIG. 1 is a schematic structural diagram of a wireless communication system to which the present application is applied.
  • FIG. 2 is a schematic diagram of channel mapping corresponding to a communication interface between the terminal device and the network device in FIG. 1.
  • FIG. 3 is a schematic diagram of a radio interface protocol stack of the terminal device and the network device in FIG. 1.
  • FIG. 4 is a schematic diagram of a hardware architecture of a terminal according to an embodiment of the present disclosure.
  • FIG. 5 is a schematic diagram of a hardware architecture of a base station according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic flowchart of a method for transmitting a buffer status report according to an embodiment of the present application.
  • FIG. 7 is a schematic diagram of a format of a buffer status report in an embodiment of the present application.
  • FIG. 8 is a schematic diagram of another format example of a cache status report in the embodiment of the present application.
  • FIG. 9 is a schematic flowchart of another method for transmitting a buffer status report according to an embodiment of the present application.
  • FIG. 10 is a schematic diagram of another format example of a cache status report according to an embodiment of the present invention.
  • FIG. 11 is a schematic diagram of a format example of third indication information in a method for transmitting a buffer status report according to an embodiment of the present invention.
  • FIG. 12 is a schematic diagram of another format example of third indication information in a method for transmitting a buffer status report according to an embodiment of the present invention.
  • FIG. 13 is a schematic flowchart of another method for transmitting a buffer status report according to an embodiment of the present invention.
  • FIG. 14 is a schematic diagram of transmission resources in a method for transmitting a scheduling request according to an embodiment of the present invention.
  • FIG. 15 is a schematic block diagram of a wireless communication system, a terminal device, and a network device according to an embodiment of the present invention.
  • FIG. 16 is a schematic structural diagram of an apparatus according to an embodiment of the present invention.
  • FIG. 1 shows a wireless communication system to which the present application relates.
  • the wireless communication system can work in a high frequency band, is not limited to a Long Term Evolution (LTE) system, and can be a fifth generation mobile communication (5th generation, 5G) system, a new air interface (NR). System, machine to machine (Machine to Machine, M2M) system.
  • LTE Long Term Evolution
  • 5G fifth generation mobile communication
  • NR new air interface
  • M2M machine to machine
  • the wireless communication system 100 can include one or more network devices 101, one or more terminal devices 103, and a core network 115. among them:
  • the network device 101 may be a base station, and the base station may be used to communicate with one or more terminal devices, or may be used to communicate with one or more base stations having partial terminal functions (such as a macro base station and a micro base station, such as an access point). , the communication between).
  • the base station may be a Base Transceiver Station (BTS) in a Time Division Synchronous Code Division Multiple Access (TD-SCDMA) system, or may be an evolved base station in an LTE system (Evolutional Node B). , eNB), and base stations in 5G systems, new air interface (NR) systems.
  • the base station may also be an Access Point (AP), a TransNode (Trans TRP), a Central Unit (CU), or other network entity, and may include some or all of the functions of the above network entities. .
  • the terminal device 103 can be distributed throughout the wireless communication system 100, either stationary or mobile.
  • the terminal device 103 may be a mobile device, a mobile station, a mobile unit, an M2M terminal, a wireless unit, a remote unit, a user agent, a mobile client, and the like.
  • network device 101 can be used to communicate with terminal device 103 over wireless interface 105 under the control of a network device controller (not shown).
  • the network device controller may be part of the core network 115 or may be integrated into the network device 101.
  • the network device 101 can be configured to transmit control information or user data to the core network 115 through a blackhaul interface 113 (such as an S1 interface).
  • the network device 101 and the network device 101 can also communicate with each other directly or indirectly through a blackhaul interface 111 (such as an X2 interface).
  • FIG. 2 shows a channel map corresponding to the wireless interface 105 of FIG. 1 (ie, the wireless interface between the terminal device 103 and the network device 101).
  • the interface between the radio interface protocol layers shown in FIG. 3 can be expressed as a channel, and specifically includes: a logical channel, a transport channel, and a physical channel. among them:
  • Logical channel The logical channel describes the type of information, that is, what information is transmitted.
  • the interface between the Media Access Control (MAC) layer and the Radio Link Control (RLC) layer is a logical channel.
  • the MAC layer provides services to the RLC layer through logical channels.
  • logical channels are divided into two categories: logical control channels and logical traffic channels.
  • the logical control channel is used for transmitting control plane information, and may include: a paging control channel (Paging Control Channel, PCCH), a common control channel (CCCH), and a dedicated control channel (Dedicated Control Channel, DCCH).
  • the logical service channel is used for transmitting user plane information, and may include: a Dedicated Traffic Channel (DTCH), a Multi-broadcast Traffic Channel (MTCH), and the like.
  • Transport channel The transport channel describes the way information is transmitted, that is, how information is transmitted.
  • the interface between the Physical Layer (PHY) and the Medium Access Control (MAC) layer is a transport channel.
  • the PHY layer provides services to the MAC layer through the transport channel.
  • the transport channel can typically be classified according to the manner in which the signal is transmitted over the radio interface, such as channel coding strategy, modulation method, and antenna mapping.
  • the transport channel may include: a downlink shared channel (DLSCH), a broadcast channel (BCH), a multicast channel (MCH), and a paging channel (Paging Channel, PCH). , Uplink Shared Channel (ULSCH), Random Access Channel (RACH), and the like.
  • DLSCH downlink shared channel
  • BCH broadcast channel
  • MCH multicast channel
  • PCH paging channel
  • ULSCH Uplink Shared Channel
  • RACH Random Access Channel
  • the physical channel corresponds to a resource element (Resource Element, RE) set that carries high-level information.
  • the basic entities that make up a physical channel are Resource Units (REs) and Resource Blocks (RBs).
  • the physical channel may include: a Physical Downlink Control Channel (PDCCH), a Physical Downlink Shared Channel (PDSCH), a Physical Broadcast Channel (PBCH), and a PMCH (Physical Broadcast Channel).
  • Physical Multicast Channel Physical Multicast Channel
  • Physical Hybrid ARQ Indicator Channel PHICH
  • Physical Control Format Indicator Channel PCFICH
  • Physical Uplink Control Channel PUCCH
  • PUSCH Physical uplink shared channel
  • PRACH Physical Random Access Channel
  • the wireless communication system 100 shown in FIG. 1 is only for the purpose of more clearly explaining the technical solutions of the present application, and does not constitute a limitation of the present application. Those skilled in the art may know that with the evolution of the network architecture and new The appearance of the business scenario, the technical solution provided by the present application is equally applicable to similar technical problems.
  • the terminal 200 may include: one or more terminal processors 201, a memory 202, a communication interface 203, a receiver 205, a transmitter 206, a coupler 207, an antenna 208, a user interface 202, and an input and output module. (including audio input and output module 210, key input module 211, display 212, etc.). These components can be connected by bus 204 or other means, and FIG. 4 is exemplified by a bus connection. among them:
  • Communication interface 203 can be used by terminal 200 to communicate with other communication devices, such as network devices.
  • the network device may be the network device 300 shown in FIG. 5.
  • the communication interface 203 may be a Long Term Evolution (LTE) (4G) communication interface, or may be a 5G or a future communication interface of a new air interface.
  • LTE Long Term Evolution
  • 5G Fifth Generation
  • the terminal 200 may be configured with a wired communication interface 203, such as a Local Access Network (LAN) interface.
  • LAN Local Access Network
  • Transmitter 206 can be used to perform transmission processing, such as signal modulation, on signals output by terminal processor 201.
  • Receiver 205 can be used to perform reception processing, such as signal demodulation, on the mobile communication signals received by antenna 208.
  • transmitter 206 and receiver 205 can be viewed as a wireless modem.
  • the number of the transmitter 206 and the receiver 205 may each be one or more.
  • the antenna 208 can be used to convert electromagnetic energy in a transmission line into electromagnetic waves in free space, or to convert electromagnetic waves in free space into electromagnetic energy in a transmission line.
  • the coupler 207 is configured to divide the mobile communication signal received by the antenna 208 into multiple channels and distribute it to a plurality of receivers 205.
  • the terminal 200 may also include other communication components such as a GPS module, a Bluetooth module, a Wireless Fidelity (Wi-Fi) module, and the like. Not limited to the above-described wireless communication signals, the terminal 200 can also support other wireless communication signals such as satellite signals, short-wave signals, and the like. Not limited to wireless communication, the terminal 200 may also be configured with a wired network interface (such as a LAN interface) to support wired communication.
  • a wired network interface such as a LAN interface
  • the input and output module can be used to implement the interaction between the terminal 200 and the user/external environment, and can include the audio input and output module 210, the key input module 211, the display 212, and the like. Specifically, the input and output module may further include: a camera, a touch screen, a sensor, and the like. The input and output modules communicate with the terminal processor 201 through the user interface 209.
  • Memory 202 is coupled to terminal processor 201 for storing various software programs and/or sets of instructions.
  • memory 202 can include high speed random access memory, and can also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid state storage devices.
  • the memory 202 can store an operating system (hereinafter referred to as a system) such as an embedded operating system such as ANDROID, IOS, WINDOWS, or LINUX.
  • the memory 202 can also store a network communication program that can be used to communicate with one or more additional devices, one or more terminal devices, one or more network devices.
  • the memory 202 can also store a user interface program, which can realistically display the content of the application through a graphical operation interface, and receive user control operations on the application through input controls such as menus, dialog boxes, and keys. .
  • the memory 202 may be used to store an implementation program of the resource allocation method provided by one or more embodiments of the present application on the terminal 200 side.
  • the resource allocation method provided by one or more embodiments of the present application please refer to the subsequent embodiments.
  • Terminal processor 201 can be used to read and execute computer readable instructions. Specifically, the terminal processor 201 can be used to invoke a program stored in the memory 212, such as an implementation program of the resource allocation method provided by one or more embodiments of the present application on the terminal 200 side, and execute instructions included in the program.
  • a program stored in the memory 212 such as an implementation program of the resource allocation method provided by one or more embodiments of the present application on the terminal 200 side, and execute instructions included in the program.
  • the terminal 200 can be the terminal device 103 in the wireless communication system 100 shown in FIG. 7, and can be implemented as a mobile device, a mobile station, a mobile unit, a wireless unit, a remote unit, and a user. Proxy, mobile client and more.
  • the terminal 200 shown in FIG. 4 is only one implementation of the embodiment of the present application. In an actual application, the terminal 200 may further include more or less components, which are not limited herein.
  • network device 300 can include one or more network device processors 301, memory 302, communication interface 303, transmitter 305, receiver 306, coupler 307, and antenna 308. These components can be connected via bus 304 or other types, and FIG. 5 is exemplified by a bus connection. among them:
  • Communication interface 303 can be used by network device 300 to communicate with other communication devices, such as terminal devices or other network devices.
  • the terminal device may be the terminal 200 shown in FIG. 4.
  • the communication interface 303 may be a Long Term Evolution (LTE) (4G) communication interface, or may be a 5G or a future communication interface of a new air interface.
  • LTE Long Term Evolution
  • the network device 300 may also be configured with a wired communication interface 303 to support wired communication.
  • the backhaul link between one network device 300 and other network devices 300 may be a wired communication connection.
  • Transmitter 305 can be used to perform transmission processing, such as signal modulation, on signals output by network device processor 301.
  • Receiver 306 can be used to perform reception processing on the mobile communication signals received by antenna 308. For example, signal demodulation.
  • transmitter 305 and receiver 306 can be viewed as a wireless modem. In the network device 300, the number of the transmitter 305 and the receiver 306 may each be one or more.
  • the antenna 308 can be used to convert electromagnetic energy in a transmission line into electromagnetic waves in free space, or to convert electromagnetic waves in free space into electromagnetic energy in a transmission line.
  • Coupler 307 can be used to divide the mobile pass signal into multiple channels and distribute it to multiple receivers 306.
  • Memory 302 is coupled to network device processor 301 for storing various software programs and/or sets of instructions.
  • memory 302 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid state storage devices.
  • the memory 302 can store an operating system (hereinafter referred to as a system) such as an embedded operating system such as uCOS, VxWorks, or RTLinux.
  • the memory 302 can also store a network communication program that can be used to communicate with one or more additional devices, one or more terminal devices, one or more network devices.
  • the network device processor 301 can be used to perform wireless channel management, implement call and communication link establishment and teardown, and provide cell handover control and the like for users in the control area.
  • the network device processor 301 may include: an Administration Module/Communication Module (AM/CM) (a center for voice exchange and information exchange), and a Basic Module (BM) (for Complete call processing, signaling processing, radio resource management, radio link management and circuit maintenance functions), code conversion and sub-multiplexer (TCSM) (for multiplexing demultiplexing and code conversion functions) )and many more.
  • AM/CM Administration Module/Communication Module
  • BM Basic Module
  • TCSM code conversion and sub-multiplexer
  • the network device processor 301 can be used to read and execute computer readable instructions. Specifically, the network device processor 301 can be used to invoke a program stored in the memory 302, such as a resource allocation method provided by one or more embodiments of the present application, on the network device 300 side, and execute instructions included in the program. .
  • the network device 300 can be the base station 101 in the wireless communication system 100 shown in FIG. 7, and can be implemented as a base transceiver station, a wireless transceiver, a basic service set (BSS), and an extended service set (ESS). NodeB, eNodeB, access point or TRP, etc.
  • the network device 300 shown in FIG. 5 is only one implementation of the embodiment of the present application. In actual applications, the network device 300 may further include more or fewer components, which are not limited herein.
  • the network device 101 and the terminal device 103 can support simultaneous transmission of multiple services (uplink transmission or downlink transmission), and allocate logical channels (Logical, Channel, LCH) for multiple services at the MAC layer.
  • the LCH may support one or more numerologies, where the numerology may include one or more physical transmission parameters. Table 1 shows nine different examples of numerology that the LCH may support, where each numerology includes the following physical transmission parameters: Subcarrier Spacing (SCS), Symbol Length, Normal Cyclic Prefix (Normal CP) ), Normal Max BW, Max FFT size, Minimum Scheduling Interval in symbols, Minimum Scheduling Interval in Slots And the minimum scheduling interval in milliseconds.
  • SCS Subcarrier Spacing
  • Normal Cyclic Prefix Normal CP
  • Max BW Normal Max BW
  • Max FFT size Minimum Scheduling Interval in symbols
  • Minimum Scheduling Interval in Slots And the minimum scheduling interval in milliseconds.
  • different numerologies may include at least one physical transmission parameter with different values.
  • the subcarrier spacing, symbol length, regular cyclic prefix, and regular maximum bandwidth of numerology 1 are different from numerology2.
  • different numerologies may also include one or more physical transmission parameters with the same value.
  • the maximum FFT size and minimum scheduling interval of the numerology 1 are the same as the numerology 2.
  • different numerologies may not include physical transmission parameters with the same value, but this application does not limit this.
  • the total number of numerologies in the application may be more or less, and the number of physical transmission parameters included in the numerology may be more or less.
  • each numerology may include only a minimum scheduling interval. Different numerologies may refer to different minimum scheduling intervals, but the application is not limited thereto.
  • the minimum scheduling interval of the numerology may specifically refer to a minimum transmission time interval (TTI) corresponding to the numerology, and the TTI length in the following may refer to a minimum scheduling interval, but the application is not limited thereto.
  • TTI transmission time interval
  • the network device may be requested to allocate an uplink transmission resource corresponding to a certain numerology attribute.
  • the present application provides a method for transmitting a buffer status report, which can configure a numerology attribute corresponding to a logical channel group, and determine a target logical channel group to which the logical channel belongs according to a numerology attribute corresponding to the logical channel group.
  • FIG. 6 illustrates a method 400 for transmitting a buffer status report provided by the present application.
  • the network device sends first indication information to the terminal device, where the first indication information indicates a numerology attribute corresponding to each LCG in the at least one LCG.
  • the terminal device may receive the first indication information from the network device, and determine a numerology attribute corresponding to each LCG in the at least one LCG according to the first indication information.
  • the numerology attribute corresponding to the LCG may include a numerology corresponding to the LCG or at least one physical transmission parameter value corresponding to the LCG.
  • number attribute corresponding to LCG may also be referred to as "physical transmission attribute corresponding to LCG”, or may have other names, which is not limited in this application.
  • the physical transmission parameter value may refer to the value of the physical transmission parameter, and accordingly, the plurality of physical transmission parameter values may refer to the value of each of the plurality of different physical transmission parameters.
  • the physical transmission parameter herein may be a physical transmission parameter included in the numerology, but the application is not limited thereto.
  • a parameter set (numerology) attribute can be configured for the LCG.
  • the numerology attribute may be specifically a numerology or multiple numerologies, or may be one or more physical transmission parameters included in the numerology.
  • one LCG may correspond to one or more physical transmission parameter values.
  • the numerology attribute of the LCG may be specifically a TTI length, and correspondingly, each LCG may correspond to a TTI length value. For example, suppose there are three optional LCGs: LCG 1, LCG 2, and LCG 3.
  • the TTI length of LCG 1 is 4 ms
  • the length of TTI corresponding to LCG 2 is 1 ms
  • the length of TTI corresponding to LCG 3 is equal to 2 ms
  • different LCGs may correspond to different TTI length values, but the application is not limited thereto.
  • the numerology attribute is specifically one or more numerology
  • the TTI length in Table 2 may be replaced with a numerology number, but this application does not limit this.
  • the numerology attribute corresponding to the LCG may be constant or may be dynamically changed.
  • the network device may determine a numerology attribute corresponding to the LCG according to the current network status and/or historical statistic information, where the current network status may include current resource utilization information, and the historical statistic information may include a data transmission delay of a certain LCH or LCG. , etc., this application does not limit this.
  • the network device may determine, according to the capabilities of the terminal device, such as the support capability of the numerology, including but not limited to the maximum bandwidth, the subcarrier spacing, and the like, or the registration information of the user, such as the service type registered by the terminal,
  • the numerology attribute is configured to one or more LCHs, but the embodiment of the present invention is not limited thereto.
  • the network device may configure the numerology attribute of the LCG by using the first indication information, that is, the correspondence between the LCG and the physical transmission parameter value or the numerology.
  • the first indication information may indicate a numerology attribute of some or all of the plurality of candidate LCGs, but the application is not limited thereto.
  • the network device may send the first indication information to the terminal device by using terminal device specific signaling.
  • the network device may also multicast or broadcast the first indication information, which is not limited in this application.
  • the network device may configure a numerology attribute corresponding to each LCG in the at least one LCG by radio resource control (RRC) signaling, that is, the first indication information may include an RRC message sent by the network device.
  • RRC radio resource control
  • the first indication information may include the identifier information of the numerology corresponding to the LCG, or the first indication information may also include the value of the one or more physical transmission parameters corresponding to the LCG, but the application is not limited thereto.
  • the terminal device may further store a numerology attribute corresponding to each LCG in the at least one LCG, but the application is not limited thereto.
  • the terminal device may determine, according to the numerology attribute corresponding to each LCG in the at least one LCG, the LCG to which the LCH belongs, that is, the target LCG.
  • the at least one LCG may be specifically a plurality of LCGs.
  • the terminal device may determine the LCG to which the LCH belongs according to the numerology attribute corresponding to each LCG of the multiple LCGs.
  • the LCH can support multiple numerologies.
  • the LCG to which the LCH belongs may be determined according to the multiple numerology supported by the LCH and the numerology attribute corresponding to each LCG in the at least one LCG, but the application is not limited thereto.
  • the numerology attribute of the LCH (also referred to as the numerology attribute of the LCH) can be configured.
  • the numerology attribute of the LCH can be used to select the LCG to which the LCH belongs or to report the cached data of the LCH.
  • the LCG to which the LCH belongs may be determined according to the numerology attribute requirement of the LCH and the numerology attribute corresponding to each LCG in the at least one LCG.
  • the numerology attribute requirement of the LCH may be pre-configured or pre-defined by the network device.
  • the network device may send second indication information to the terminal device, where the second indication information indicates a numerology attribute requirement of one or more LCHs, corresponding
  • the terminal device may determine the numerology attribute requirement of the one or more LCHs according to the second indication information received from the network device, and select the LCG to which the LCH belongs according to the method, but the application is not limited thereto.
  • the numerology attribute requirement may include: the value of the one or more physical transmission parameters meets a certain condition, and the numerology attribute associated with the LCH when the BSR is reported may be configured.
  • the numerology attribute corresponding to the LCG may include a TTI length (or a minimum scheduling interval), and the numerology attribute requirement may include: the TTI length is equal to a certain selection threshold, for example, as shown in Table 3, the TTI of the LCH 1 The length selection threshold is 2 ms, and the TTI selection length of LCH 2 and LCH 3 is 1 ms. It should be understood that Table 3 exemplarily shows the TTI length selection thresholds corresponding to three LCHs. Alternatively, the present application may be for each LCH.
  • the corresponding numerology attribute requirement is configured, but the application is not limited thereto.
  • the LCG whose corresponding TTI length is equal to the TTI length selection threshold of the LCH may be determined as the LCG to which the LCH belongs.
  • the LCG that satisfies the requirement of the numerology attribute of the LCH may be determined as the LCG to which the LCH belongs, and the LCG that satisfies the requirement of the numerology attribute of the LCH may also be the LCG that satisfies the numerology attribute requirement of the LCH to a minimum.
  • Table 2 and Table 3 it can be concluded that the LCG to which LCH 1 belongs is LCG 3, and the LCG to which LCH 2 and LCH 3 belong is LCG 2, but the present application is not limited thereto.
  • the numerology attribute requirement of the LCH may include: the TTI length is less than or equal to the maximum TTI duration of the LCH (maximum TTI duration).
  • the maximum TTI length may be a maximum TTI length or a certain larger TTI length included in the multiple numerology supported by the LCH, or may be an additionally defined parameter, which may be pre-configured or pre-configured by the network device. Definitions, this application does not limit this. For example, as shown in Table 4, the maximum TTI length corresponding to LCH 1 is 4 ms, the maximum TTI length corresponding to LCH 2 is 2 ms, and the maximum TTI length corresponding to LCH 3 is 1 ms.
  • the LCG to which the LCH belongs may be determined according to the maximum TTI length corresponding to the LCH.
  • the LCG corresponding to the maximum TTI length of the TTI length corresponding to the at least one LCG that is less than or equal to the maximum TTI length corresponding to the LCH may be determined as the LCG to which the LCH belongs, that is, from the at least one Determining a target TTI length in the TTI length corresponding to the LCG, where the target TTI length is a maximum value of the at least one candidate TTI length, where the TTI length corresponding to the at least one LCG may include the at least one candidate TTI length, and the at least one candidate
  • the TTI length may be less than or equal to the maximum TTI length corresponding to the LCH, but the application is not limited thereto.
  • the numerology attribute corresponding to the LCG may include the SCS
  • the numerology attribute requirement of the LCH may include: the SCS is greater than or equal to the minimum SCS (Minimum SCS) corresponding to the LCH.
  • the minimum SCS may be the minimum SCS or a certain smaller SCS included in the multiple numerology supported by the LCH, or may be an additional defined parameter, which may be pre-configured or pre-defined by the network device. There is no limit to this.
  • the LCG to which the LCH belongs may be determined according to the minimum SCS corresponding to the LCH.
  • the LCG corresponding to the smallest SCS of the SCS corresponding to the at least one LCG that is greater than or equal to the minimum SCS corresponding to the LCH may be determined as the LCG to which the LCH belongs, that is, may correspond to the at least one LCG. Determining a target SCS in the SCS, where the target SCS is a minimum value in the at least one candidate SCS, where the SCS corresponding to the at least one LCG may include the at least one candidate SCS, and the at least one candidate SCS may be greater than or equal to the corresponding LCH Minimum SCS, but the application is not limited to this.
  • the rules for selecting the LCG for the LCH may be predefined or may be pre-configured by the network device.
  • the network device may indicate to select an LCG that meets the minimum numerology attribute requirement of the LCH for a certain LCH, for example, indicating that the LCG corresponding to the maximum TTI duration less than or equal to the maximun TTI duration is selected, or the selection is greater than or equal to the Minimum.
  • the LCG corresponding to the smallest SCS of the SCS is not limited to this application.
  • number attribute requirement of LCH may also be referred to as "physical transmission parameter requirement of LCH” or “transmission requirement of LCH”, or may have other names, which is not limited in this application. .
  • the terminal device sends a BSR to the network device, where the BSR includes the amount of data to be sent of the at least one LCH that belongs to the target LCG.
  • the amount of buffered data may still be in the unit of the LCG. Accordingly, the amount of buffered data reported by the BSR may be equal to the sum of the amount of data to be sent of the logical channel belonging to the target LCG, that is, the BSR may report that the target LCG is selected. The amount of cached data for one or more LCHs.
  • the BSR may be a short format BSR.
  • the BSR may include an LCG identification (LCG ID) field and a buffer size (Buffer Size) field, where the LCG identification field carries identification information of the target LCG, and the cache size field carries the target LCG.
  • LCG ID LCG identification
  • Buffer Size buffer size
  • the BSR may be a long format BSR.
  • the BSR may include N cache size fields corresponding to the N LCGs, where the buffer size field corresponding to the target LCG is used to carry data to be sent of at least one logical channel belonging to the target LCG.
  • Quantity, N is an integer greater than or equal to 1.
  • the terminal device may determine a buffer size field corresponding to the target LCG, and carry the sum of the amount of data to be sent of the logical channel belonging to the target LCG in the corresponding buffer size field, but the application is not limited thereto.
  • the network device may allocate an uplink transmission resource to the terminal device according to the BSR.
  • the numerology attribute corresponding to the uplink transmission resource requested by the BSR may be determined according to the information of the LCG included in the BSR, and optionally, corresponding Resource allocation operation. For example, if the BSR includes the identifier information of the LCG 1, the network device may determine, according to the table 2, the uplink transmission resource whose TTI length is equal to 4, and allocate the corresponding uplink transmission resource with the TTI length equal to 4.
  • this application is not limited to this.
  • S440 may not be executed in some cases. For example, if there is no available uplink transmission resource, the network device may not allocate the uplink transmission resource for the terminal device, but the application is not limited thereto.
  • the LCG to which the LCH belongs may be directly configured for the LCH supporting a single numerology; for the LCH supporting multiple numerologies, the LCG to which the LCH belongs may be pre-configured, but the BSR is selected when the BSR is reported. LCG.
  • the present application by configuring the corresponding numerology attribute for the LCG and selecting the LCG to which the LCH belongs according to the numerology attribute corresponding to the LCG, it is possible to implement the reporting of the buffered data amount of the LCH supporting the multiple numerology, which is advantageous for improving the data transmission performance. Meet the needs of different businesses.
  • the present application provides another method for transmitting a buffer status report.
  • the target numerology may be selected from a plurality of numerologies supported by the LCH, and the identification information of the target numerology is included in the BSR.
  • the BSR may not include the LCG information, and accordingly, the terminal device may not need to select the LCG to which the LCH belongs.
  • FIG. 9 illustrates another method 500 for transmitting a buffer status report provided by the present application.
  • the network device sends second indication information to the terminal device, where the second indication information indicates a numerology attribute requirement corresponding to the LCH (for example, the first LCH).
  • the second indication information may be used to indicate a numerology attribute requirement corresponding to one or more LCHs.
  • the numerology attribute requirement of the LCH can be used to select a numerology for reporting the BSR for the LCH.
  • the terminal device may receive the second indication information from the network device, and determine the numerology attribute requirement corresponding to the LCH according to the second indication information.
  • the network device may send the second indication information to the terminal device by using terminal device specific signaling.
  • the network device may also multicast or broadcast the second indication information, which is not limited in this application.
  • the network device may configure the numerology attribute requirement corresponding to the LCH by using Radio Resource Control (RRC) signaling, that is, the second indication information may be included in the RRC signaling sent by the network device, but The application is not limited to this.
  • RRC Radio Resource Control
  • the terminal device may further store a numerology attribute requirement corresponding to the LCH, but the application is not limited thereto.
  • the numerology attribute requirement of the LCH may also be predefined.
  • S510 may not be performed, but the application is not limited thereto.
  • the terminal device may determine the target numerology from the at least one numerology supported by the LCH according to the numerology attribute requirement of the LCH.
  • the LCH can support multiple numerologies.
  • the terminal device may determine the target numerology corresponding to the LCH, that is, the numerology for reporting the BSR, according to the value of the physical transmission parameter included in the plurality of numerologies supported by the LCH and the numerology attribute requirement of the LCH, but the application is not limited thereto.
  • the numerology attribute requirement may include: the value of one or more physical transmission parameters satisfying certain conditions.
  • the numerology may include a TTI length (or a minimum transmission interval), and the numerology attribute requirement may include: the TTI length is equal to a certain selection threshold, for example, as shown in Table 3.
  • the numerology including the TTI length value equal to the TTI length selection threshold of the LCH may be determined as the target numerology corresponding to the LCH.
  • the numerology that satisfies the requirement of the numerology attribute of the LCH may be determined as the target numerology corresponding to the LCH, and the numerology that satisfies the requirement of the numerology attribute of the LCH may also satisfy the requirement of the numerology attribute of the LCH to a minimum. Numerology, but the application is not limited to this.
  • the numerology attribute requirement of the LCH may include: the TTI length is less than or equal to the maximum TTI duration of the LCH (maximum TTI duration).
  • the maximum TTI length may be pre-configured or pre-defined by the network device, which is not limited in this application.
  • the numerology to which the maximum TTI length of the TTI length of the at least one numerology supported by the LCH is less than or equal to the maximum TTI length corresponding to the LCH may be determined as the target numerology corresponding to the LCH, that is, Determining a target TTI length from a TTI length included in the at least one numerology, the target TTI length being a maximum of at least one candidate TTI length, wherein the at least one numerology may include the at least one candidate TTI length, and the at least A candidate TTI length may be less than or equal to a maximum TTI length corresponding to the LCH, but the application is not limited thereto.
  • the numerology may include an SCS
  • the numerology attribute requirement of the LCH may include: the SCS is greater than or equal to the minimum SCS (Minimum SCS) corresponding to the LCH.
  • the minimum SCS may be pre-configured or pre-defined by the network device, which is not limited in this application.
  • the target SCS corresponding to the LCH may be determined according to the minimum SCS corresponding to the LCH.
  • the numerology to which the smallest SCS of the SCS included in the at least one numerology is greater than or equal to the minimum SCS corresponding to the LCH may be determined as the target numerology corresponding to the LCH, that is, may be included from the at least one numerology.
  • Determining a target SCS in the SCS where the target SCS is a minimum value in the at least one candidate SCS, wherein the at least one numerology may include the at least one candidate SCS, and the at least one SCS may be greater than or equal to a minimum SCS corresponding to the LCH, but This application is not limited to this.
  • the rule for selecting the numerology for the LCH may be predefined or may be pre-configured by the network device.
  • the network device may indicate that a certain numerology that meets the requirements of the numerology attribute of the LCH is selected for a certain LCH, for example, indicating that the numerology of the maximum TTI duration less than or equal to the maximun TTI duration is selected, or that the selection is greater than or equal to the Minimum SCS.
  • the numerology to which the minimum SCS belongs is not limited to this application.
  • the terminal device sends a BSR to the network device, where the BSR includes an amount of data to be sent corresponding to at least one LCH of the target numerology.
  • the amount of cached data can be counted in units of numerology.
  • the amount of buffered data reported by the BSR can be equal to the sum of the amount of data to be sent of the LCH corresponding to the target numerology, that is, the BSR can report that the target is selected.
  • the BSR may include a numerology ID field and a Buffer Size field, where the numerology identifier field carries the identification information of the target numerology.
  • the buffer size field carries an amount of data to be transmitted corresponding to at least one LCH of the target numerology.
  • the BSR may include N cache size fields corresponding to the N numerologies, where the buffer size field corresponding to the target numerology is used to carry data to be sent corresponding to at least one LCH of the target numerology.
  • Quantity N is an integer greater than or equal to 1.
  • the terminal device may determine a buffer size field corresponding to the target numerology, and carry the sum of the amount of data to be sent corresponding to the logical channel of the target numerology in the corresponding buffer size field, but the application is not limited thereto.
  • the network device may allocate an uplink transmission resource to the terminal device according to the BSR.
  • the numerology attribute corresponding to the uplink transmission resource requested by the BSR may be determined according to the information of the numerology included in the BSR, and optionally, the corresponding Resource allocation operation. For example, if the BSR includes the number of the numerology 1, the network device may allocate the uplink transmission resource corresponding to the numerology 1 to the terminal device, or may assign the corresponding one or more physical transmission parameters of the terminal device to be equal to the numerology 1
  • the uplink transmission resource of the value of the same physical transmission parameter for example, allocates an uplink transmission resource whose corresponding TTI length is equal to the TTI length in numerology 1, but the application is not limited thereto.
  • S540 may not be performed in some cases. For example, if there is no available uplink transmission resource, the network device may not allocate the uplink transmission resource for the terminal device, but the application is not limited thereto.
  • the cached data of the LCH supporting the multiple numerology can be implemented.
  • the amount of reporting is conducive to improving data transmission performance.
  • the terminal device starts/restarts the retransmission timer (retxBSR-Timer) after transmitting the BSR, and restarts the retxBSR-Timer after receiving the UL grant, that is, after obtaining the uplink transmission resource.
  • retxBSR-Timer the retransmission timer
  • the UL grant is not received when the retxBSR-Timer times out, and any LCG belonging to the LCG has data to be sent
  • a new BSR may be triggered, where the newly triggered BSR belongs to a regular BSR (regular BSR); if retxBSR- The timer does not time out.
  • the new BSR is triggered only if the data of the LCH is reached and the priority is higher than any LCH included in the LCG of the current BSR.
  • the BSR regular BSR
  • the received UL Grant may be used only for allocating uplink transmission resources requested by some BSRs, and the uplink transmission resources correspond to some Specific numerology or physical transfer parameter values.
  • the uplink transmission resources requested by some BSRs may not be allocated, thereby reducing system performance.
  • the present application provides a method for transmitting a buffer status report, which can be configured with a BSR retransmission timer retxBSR-Timer for each type of numerology (or physical transmission parameter value) supported by the terminal device; correspondingly, the terminal device can
  • the retxBSR-Timer of the numerology manages the retransmission of the BSR.
  • the retxBSR-Timer corresponding to the numerology is restarted only when the UL grant corresponding to the numerology of the BSR request is received.
  • the network may send the third indication information to the terminal device, where the third indication information is used to indicate a BSR retransmission timer corresponding to each of the plurality of numerologies.
  • the length of the BSR retransmission timers of the different numerologies may be the same or different, which is not limited in this application.
  • the network device may send the third indication information to the terminal device by using RRC signaling, but the application is not limited thereto.
  • the third indication information may include a numerology identifier field and a corresponding retxBSR-Timer duration, where the numerology identifier field may be used to carry the identifier information of the numerology, and the corresponding retxBSR-Timer duration may be used.
  • the duration of the BSR retransmission timer corresponding to the numerology is carried, but the application is not limited thereto.
  • the third indication information may include a physical transmission parameter field and a corresponding retxBSR-Timer duration field.
  • the third indication information may be used to indicate different values of one or more physical transmission parameters (ie, different The numerology attribute) corresponds to the BSR retransmission timer.
  • the third indication information may include a TTI length and a corresponding BSR retransmission timer duration, but the application is not limited thereto.
  • the terminal device may receive the third indication information from the network device.
  • the terminal device may determine, according to the third indication information, a BSR retransmission timer corresponding to each of the plurality of numerologies.
  • the terminal device may send a first BSR to the network device, and may start a BSR retransmission timer corresponding to the numerology attribute associated with the first BSR.
  • the numerology attribute of the BSR association may be the numerology corresponding to the transmission resource requested by the BSR, but the embodiment of the present invention is not limited thereto.
  • the first BSR may be a short-form BSR, such as the BSR shown in FIG. 7 or FIG. 10, and correspondingly, the first BSR may be associated with a numerology, for example, the first numerology, and the terminal device may start the first numerology.
  • Corresponding BSR retransmission timer may be Alternatively, the first BSR may be a long format BSR, and correspondingly, the first BSR may be associated with one or more numerologies, for example, at least one numerology including a first numerology, and the terminal device may start each of the at least one numerology
  • the BSR retransmission timer corresponding to the numerology, but the embodiment of the present invention is not limited thereto.
  • the terminal device waits for the UL Grant for the numerology, and may not trigger or send the BSR associated with the numerology.
  • the BSR retransmission timer corresponding to the numerology may be stopped or restarted.
  • the terminal device may trigger or send the BSR associated with the numerology again if necessary.
  • the terminal device may trigger or send a BSR associated with another numerology regardless of whether the BSR retransmission timer corresponding to a numerology expires.
  • the terminal device may retransmit the first BSR or retransmit the buffer data corresponding to the first numerology, and may restart the BSR retransmission timer corresponding to the first numerology.
  • the terminal device may send the second BSR to the network device, where the second BSR request corresponds to the uplink transmission resource of the second numerology, that is, the second BSR is associated with the second numerology, but the application is not limited thereto. .
  • the terminal device may trigger the reporting of the BSR by the priority of any LCH that belongs to the corresponding LCG in the sent BSR.
  • the technical solution provided by the present application by configuring different retransmission timers for requesting BSRs corresponding to resources of different numerologies, is advantageous for facilitating timely response to different LCH requirements for resources of different numerologies, thereby improving data transmission performance.
  • each terminal device can only transmit at most one BSR in one TTI.
  • a terminal device triggers multiple BSRs at the same time, if a BSR is included in a Media Access Control (MAC) Protocol Data Unit (PDU) to be transmitted, the other BSR triggered by the terminal device is revoked.
  • MAC Media Access Control
  • PDU Protocol Data Unit
  • the present application provides a method for transmitting a buffer status report. If a terminal device triggers multiple BSRs at the same time, the BSR that is actually sent may be determined according to the numerology attribute associated with the multiple BSRs.
  • the terminal device can trigger the first BSR and the second BSR at the same time, if the first BSR and the second BSR request the uplink transmission resource of the same numerology, that is, the first BSR and the second BSR are associated with each other.
  • the terminal device can revoke one of the first BSR and the second BSR, for example, the terminal device can cancel the first BSR.
  • the terminal device ie, MAC entity
  • the terminal device can only send at most one BSR associated with the same numerology within each scheduling interval (ie, each TTI).
  • each MAC entity can only send at most one BSR associated with the same numerology within each scheduling interval (ie, each TTI).
  • the BSR is associated with multiple numerologies, for example, the long-form BSR shown in FIG. 8
  • the plurality of numerologies associated with the first BSR and the plurality of numerologies associated with the second BSR have an intersection, that is, the first BSR
  • the first BSR and the second BSR may be considered to be associated with the same numerology, but the application is not limited thereto.
  • the terminal device can determine the numerology attribute of the BSR association in various manners.
  • the numerology attribute corresponding to the LCG may be configured, and the terminal device may determine the numerology attribute of the BSR according to the numerology attribute corresponding to the LCG corresponding to the BSR, where the LCG corresponding to the BSR may be based on the LCG included in the BSR.
  • Relevant information is determined.
  • the information about the LCG included in the BSR may be specifically the LCG identifier included in the BSR.
  • the information about the LCG included in the BSR may be specifically the field of the Buffer Size reported by the BSR. Not limited to this.
  • the LCG to which the LCH belongs may also be directly set, for example, the network device is pre-configured or pre-defined.
  • the numerology attribute of the LCG can depend on the numerology of the LCH it reports.
  • the BSR of the LCG reports the amount of data to be sent of the multiple LCHs, that is, the Buffer Size corresponding to the LCG is the sum of the data volumes of the multiple LCHs to be sent
  • the numerology attribute of the LCG may depend on the report.
  • the Buffer Size corresponding to the LCG 1 in the BSR includes the amount of data to be sent of LCH 1 and LCH 2, as shown in the example in Table 5.
  • the TTI length corresponding to LCG 1 may be equal to the maximum TTI duration of the LCH, that is, 4 ms, but the application is not limited thereto.
  • the terminal device may report the numerology attribute corresponding to the LCG in the BSR, so that the network device allocates resources according to the numerology attribute reported in the BSR.
  • a field may be added in the BSR to include the TTI length corresponding to the LCG 1, but the application is not limited thereto.
  • the terminal device may select the transmitted BSR from among a plurality of BSRs that are triggered by the same numerology.
  • the terminal device may randomly select the transmitted BSR.
  • the terminal device may select a priority according to the LCH included in the LCG corresponding to the multiple BSRs.
  • the terminal device may select a BSR of the LCG corresponding to the high priority LCH to transmit.
  • the multiple BSRs are long-form BSRs, and there is an intersection between the numerology attributes of the multiple BSRs, the LCH with the highest priority among the LCHs reported by the same numerology may be selected from the multiple BSRs.
  • the corresponding BSR is sent.
  • both BSR 1 and BSR 2 contain the Buffer Size of LCG 3, assuming that the Buffer Size of LCG 3 in BSR 1 is the amount of data to be transmitted of LCH 3, and the amount of LCG 3 in BSR 2
  • the Buffer Size is the amount of data to be sent of the LCH 1.
  • the priority of the LCH 1 is higher than the priority of the LCH 3.
  • the terminal device can select the BSR 2 to transmit, but the application is not limited thereto.
  • Logical channel group Buffer size LCG 1 X1 LCG 3 X2 LCG 4 X3
  • Logical channel group Buffer size LCG 2 X4 LCG 3 X2 LCG 5 X5
  • each MAC PDU may include a BSR associated with a different numerology. That is, multiple MAC PDUs may include multiple BSRs, and any two of the multiple BSRs associate different numerologies, but the application is not limited thereto.
  • the BSRs may be sent, so that the network device can allocate resources corresponding to the numerology.
  • the terminal device may simultaneously send in the scheduling interval.
  • the second BSR and the third BSR may include the second BSR in the first MAC PDU in the scheduling interval, and include the third BSR in the second MAC PDU in the scheduling interval, but the application is not limited thereto.
  • the method for transmitting a buffer status report provided by the present application when the terminal device triggers multiple BSRs at the same time, determines the BSR to be transmitted according to the numerology attribute associated with the triggered multiple BSRs, which is beneficial to improving data transmission performance. Meet different business needs.
  • the present application also provides a method for selecting an uplink transmission resource, in which the terminal device can determine an uplink transmission resource that matches the BSR according to the numerology attribute associated with the BSR.
  • FIG. 13 illustrates another method 600 for transmitting a buffer status report provided by the present application.
  • the terminal device determines an uplink transmission resource that matches the BSR, where the BSR includes the to-be-sent data amount of the at least one LCH that belongs to the LCG.
  • the uplink transmission resource matched by the BSR may be determined according to the numerology attribute of the BSR association.
  • the uplink transmission resource matched by the BSR may be determined according to a requirement of a numerology attribute corresponding to the LCG included in the BSR.
  • the numerology attribute of the BSR association may be determined according to a numerology attribute requirement corresponding to the LCG included in the BSR.
  • the uplink transmission resource that matches the BSR may be an uplink transmission resource whose corresponding numerology matches the numerology attribute of the LCG.
  • the terminal device may determine, as the uplink transmission resource that matches the requirement of the numerology attribute corresponding to the LCG, the uplink transmission resource that matches the BSR.
  • the LCG's numerology attribute requirement can be used to determine the uplink transmission resources that match the BSR.
  • the numerology attribute requirement corresponding to the LCG may be specifically the numerology attribute corresponding to the LCG in the foregoing embodiment.
  • the terminal device may also depend on the numerology attribute requirement of the LCH corresponding to the Buffer Size of the LCG included in the BSR. For example, if the BSR includes the amount of data to be sent of the at least one LCH belonging to the LCG, the terminal device may The numerology attribute of the LCH having the highest priority in one LCH is determined to be the numerology attribute requirement of the LCG, but the application is not limited thereto.
  • the numerology attribute requirement corresponding to the LCG may also be an additional defined parameter, which may be pre-configured or pre-defined by the network device.
  • the terminal device may receive the fourth indication information sent by the network device, and the fourth indication information may be used to indicate The numerology attribute corresponding to the LCG is required to be, and the application is not limited thereto.
  • the value of the numerology attribute of the LCG may be specifically that the value of the physical transmission parameter is equal to a certain selection threshold, that is, the numerology attribute of the LCG may be specifically the numerology attribute corresponding to the LCG described above.
  • the uplink transmission resource with the same numerology attribute and the same numerology attribute as the LCG may be determined as the uplink transmission resource that matches the BSR.
  • the corresponding first physical transmission parameter (for example, TTI length) may be used.
  • the uplink transmission resource whose value is equal to the value of the first physical transmission parameter corresponding to the LCG is determined to be the uplink transmission resource matched by the BSR of the LCG.
  • the uplink transmission resources currently available to the terminal device are as shown in Table 8.
  • the length of the TTI corresponding to the uplink transmission resource allocated by the UL Grant 1 is 4 ms
  • the length of the TTI corresponding to the uplink transmission resource allocated by the UL Grant 2 is 2 ms.
  • the length of the TTI corresponding to the LCG is as shown in Table 9.
  • the uplink transmission resource that meets the minimum requirement of the numerology attribute corresponding to the LCG may be determined as the uplink transmission resource of the BSR matching of the LCG.
  • the numerology attribute requirement corresponding to the LCG may include: less than or equal to the maximum TTI length corresponding to the LCG, or greater than or equal to the minimum SCS corresponding to the LCG.
  • the meaning of the minimum satisfaction may be referred to the description of the above embodiment. Narration.
  • the numerology attribute requirement of the LCG can be as shown in Table 10. In this case, since there is no corresponding transmission resource with a TTI length less than or equal to 1 in the currently available uplink transmission resource, the BSR of the LCG 2 has no available resources.
  • the BSR may not be sent, which may introduce a transmission delay.
  • the numerology attribute of the uplink transmission resource used in the BSR transmission may not be constrained, that is, the BSR may transmit the uplink transmission resource in any numerology attribute. In this case, the BSR matches the uplink transmission resource.
  • the selection may not depend on the numerology attribute of the uplink transmission resource. For example, the uplink transmission resource matched by the BSR may be arbitrarily selected.
  • the LTG corresponding to the TTI duration is 2 ms
  • the BSR of the LCG may be sent on the resource, but the embodiment of the present invention is not limited thereto.
  • the terminal device sends the BSR on the matched uplink transmission resource.
  • the network device receives the BSR, and optionally allocates an uplink transmission resource to the terminal device.
  • the network device may allocate an uplink transmission resource to the terminal device according to the numerology attribute corresponding to the uplink transmission resource occupied by the BSR. For example, the network device may allocate a resource whose corresponding numerology is the same as the uplink transmission resource occupied by the BSR. In this case, optionally, the BSR may not include information about the LCG corresponding to the Buffer Size.
  • the BSR may determine an LCG corresponding to the Buffer Size included in the BSR, and allocate an uplink transmission resource to the terminal device according to the numerology attribute requirement of the LCG or the numerology attribute corresponding to the LCG, and the application does not do this. limited.
  • the method for transmitting a buffer status report is beneficial to improving system performance by determining an uplink transmission resource that matches a BSR and transmitting the BSR on an uplink transmission resource that matches the BSR.
  • the application also provides a method for transmitting a scheduling request (SR).
  • SR scheduling request
  • the terminal device if the terminal device sends the BSR and finds available resources for transmitting the SR, and the SR can be received before the BSR, the terminal device can send the SR, so that the network device receives the request of the terminal device as soon as possible. It is advantageous for the network device to perform resource scheduling earlier and the terminal device to perform data transmission earlier.
  • the terminal device may send a BSR to the network device, if the BSR retransmission timer corresponding to the BSR does not time out, and the terminal device finds an available uplink transmission resource for transmitting the SR, where the available uplink transmission resource ends.
  • the terminal device may send the SR to the network device on the available uplink transmission resource.
  • the network device can receive the SR sent by the terminal device, and allocate a transmission resource to the terminal device according to the SR.
  • the slot length corresponding to numerology 1 is 0.5 ms
  • the slot length corresponding to numerology 2 is 0.125 ms.
  • the terminal device sends a BSR on the uplink transmission resource corresponding to the numerology 1.
  • the BSR can be received by the network device at t0+0.5 ms.
  • the terminal device After transmitting the BSR, the terminal device discovers an uplink transmission resource corresponding to the numerology that can be used to transmit the SR, and the starting time of the uplink transmission resource is t0+0.125 ms.
  • the terminal device sends the SR at t0+0.125ms, according to the slot length corresponding to the numerology 2, the SR can be received by the network device at t0+0.25ms, that is, the SR can be received by the network device before the BSR. At this time, the terminal device may send the SR to the network device at t0+0.125 ms, but the embodiment of the present invention is not limited thereto.
  • the network device may receive the BSR associated with the same numerology.
  • the time interval between the SR and the BSR is less than a preset time period.
  • the network device can discard the BSR and not respond to the BSR. In this way, the network device can respond to only one resource allocation request for the same numerology sent by the terminal device within the preset time period.
  • the preset time period may be the duration of the BSR retransmission timer corresponding to the numerology, or may also be an SR sending period, which is not limited in this application.
  • any two of the first indication information, the second indication information, the third indication information, and the fourth indication information in the present application may be sent simultaneously or separately, which is not limited by the embodiment of the present invention.
  • FIG. 15 shows a wireless communication system and an apparatus for transmitting a BSR provided by the present application.
  • the wireless communication system 10 includes a device 700 for transmitting a BSR and a device 800 for transmitting a BSR.
  • the device 700 may be the terminal device 200 in the embodiment of FIG. 4
  • the device 800 may be the network device 300 in the embodiment of FIG. 5
  • the wireless communication system 10 may be the wireless communication system 100 described in FIG. Embodiments of the invention are not limited thereto.
  • device 700 can include a processing unit 710 and a communication unit 720.
  • the processing unit 710 is configured to determine, according to a parameter set numerology attribute corresponding to each logical channel group in the at least one logical channel group, a target logical channel group to which the first logical channel belongs, where the first logical channel supports at least one Numerology, each numerology includes at least one physical transmission parameter.
  • the communication unit 720 is configured to send a buffer status report to the network device, where the buffer status report includes an amount of data to be sent that belongs to at least one logical channel of the target logical channel group, where the at least one logical channel includes the first logical channel.
  • the processing unit 710 is configured to determine a target numerology from at least one parameter set numerology supported by the first logical channel, where each numerology of the at least one numerology includes at least one physical transmission parameter.
  • the communication unit 720 is configured to send a buffer status report to the network device, where the buffer status report includes an amount of data to be sent of the at least one logical channel corresponding to the target numerology, wherein the at least one logical channel includes the first logical channel.
  • Apparatus 800 can include a processing unit 810 and a communication unit 820.
  • the processing unit 810 is configured to determine a parameter set numerology attribute corresponding to each logical channel group in the at least one logical channel group.
  • the communication unit 820 is configured to send the first indication information to the terminal device, where the first indication information is used to indicate a numerology attribute corresponding to each logical channel group in the at least one logical channel group.
  • the processing unit 810 is configured to determine a parameter set numerology attribute requirement corresponding to the first logical channel
  • the communication unit 820 is configured to send the second indication information to the terminal device, where the second indication information is used to indicate a numerology attribute requirement corresponding to the first logical channel, where a numerology attribute of the first logical channel is required for the terminal device to be from the first Determining a target numerology in at least one parameter set numerology supported by a logical channel, each numerology in the at least one numerology including at least one physical transmission parameter.
  • the apparatus 700 and apparatus 800 herein are embodied in the form of functional units.
  • the device 700 may be specifically the terminal device in the foregoing method embodiment, and the device 700 may be used to perform various processes and/or steps corresponding to the terminal device in the foregoing method embodiment.
  • the device 800 may be specifically the network device in the foregoing method embodiment, and the device 800 may be used to perform various processes and/or steps corresponding to the network device in the foregoing method embodiments. To avoid repetition, details are not described herein again.
  • unit may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor for executing one or more software or firmware programs (eg, a shared processor). , a proprietary processor or group processor, etc.) and memory, merge logic, and/or other suitable components that support the described functionality.
  • ASIC application specific integrated circuit
  • processors for executing one or more software or firmware programs (eg, a shared processor). , a proprietary processor or group processor, etc.) and memory, merge logic, and/or other suitable components that support the described functionality.
  • device 90 can include a processor 901 and one or more interfaces 902 coupled to processor 901. among them:
  • the processor 901 can be used to read and execute computer readable instructions.
  • the processor 901 may mainly include a controller, an operator, and a register.
  • the controller is mainly responsible for instruction decoding, and sends a control signal for the operation corresponding to the instruction.
  • the operator is mainly responsible for performing fixed-point or floating-point arithmetic operations, shift operations, and logic operations, as well as performing address operations and conversions.
  • the register is mainly responsible for saving the register operands and intermediate operation results temporarily stored during the execution of the instruction.
  • the hardware architecture of the processor 901 may be an Application Specific Integrated Circuits (ASIC) architecture, a MIPS architecture, an ARM architecture, or an NP architecture.
  • the processor 901 can be single core or multi-core.
  • the interface 902 can be used to input data to be processed to the processor 901, and can output the processing result of the processor 901 to the outside.
  • the interface 902 can be a General Purpose Input Output (GPIO) interface, and can be connected to multiple peripheral devices (such as a display (LCD), a camera, a radio frequency module, etc.).
  • GPIO General Purpose Input Output
  • the interface 902 may also include a plurality of independent interfaces, such as an Ethernet interface, an LCD interface, a Camera interface, etc., responsible for communication between different peripheral devices and the processor 901, respectively.
  • the processor 901 can be used to invoke an implementation program of the resource allocation method provided by one or more embodiments of the present application on the terminal side from the memory, and execute the instructions included in the program.
  • the interface 902 can be used to output the execution result of the processor 901.
  • the interface 902 can be specifically used to output the resource allocation result of the processor 901.
  • processor 901 and the interface 902 can be implemented by using a hardware design or a software design, and can also be implemented by a combination of software and hardware, which is not limited herein.
  • the processor may be a central processing unit (CPU), which may also be other general purpose processors, digital uplink signal processors (DSPs), application specific integrated circuits (ASICs). , off-the-shelf programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the memory can include read only memory and random access memory and provides instructions and data to the processor.
  • a portion of the memory may also include a non-volatile random access memory.
  • the memory can also store information of the device type.
  • the processor can be used to execute instructions stored in the memory, and when the processor executes the instructions, the processor can perform the steps corresponding to the terminal device in the above method embodiments.
  • each step of the above method may be completed by an integrated logic circuit of hardware in a processor or an instruction in a form of software.
  • the steps of the method disclosed in connection with the present application may be directly embodied by hardware processor execution or by a combination of hardware and software modules in a processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in a memory, and the processor executes instructions in the memory, in combination with hardware to perform the steps of the above method. To avoid repetition, it will not be described in detail here.
  • system and “network” are used interchangeably herein.
  • the term “and/or” in this context is merely an association describing the associated object, indicating that there may be three relationships, for example, A and / or B, which may indicate that A exists separately, and both A and B exist, respectively. B these three situations.
  • the character "/" in this article generally indicates that the contextual object is an "or" relationship.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention 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 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 transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).

Landscapes

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

Abstract

本申请提供了一种用于传输缓存状态报告BSR的方法和装置，能够适用于支持多numerology的逻辑信道的缓存数据量上报，有利于提高数据传输性能并且满足不同业务的需求。所述方法包括：终端设备根据至少一个逻辑信道组中每个逻辑信道组对应的参数集numerology属性，确定第一逻辑信道所属的目标逻辑信道组，其中，所述第一逻辑信道支持至少一个numerology，每个numerology包括至少一个物理传输参数；所述终端设备向网络设备发送缓存状态报告，所述缓存状态报告包含属于所述目标逻辑信道组的至少一个逻辑信道的待发送数据量，所述至少一个逻辑信道包括所述第一逻辑信道。

Description

用于传输缓存状态报告的方法和装置
本申请要求于2017年05月05日提交中国专利局、申请号为201710314142.9、发明名称为“用于传输缓存状态报告的方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，并且更具体地，涉及用于传输缓存状态报告的方法和装置。
背景技术
在长期演进(Long Term Evolution，LTE)***中，同一个LCH仅支持一个numerology(Numerology)。基站为终端分配逻辑信道(Logic Channel，LCH)所属的逻辑信道组(Logic Channel Group，LCG)，其中，一个LCG可以包括一个或多个LCH。终端可以通过向基站发送缓存状态报告(Buffer Status Report，BSR)请求上行传输资源，其中，缓存数据量可以以LCG为单位进行上报。
未来的无线通信***可以支持多种场景和不同的业务类型，例如增强移动带宽(Enhanced Mobile Broadband，eMBB)、大规模机器类型通信(Massive Machine Type Communication，mMTC)和超可靠低时延通信(Ultra Reliable-Low Latency Communication，URLLC)，等等。不同业务类型对传输能力有不同的要求，例如URLLC更关注时延而eMBB更关注带宽。为了满足不同的业务需求，***可以为同一个逻辑信道(Logic Channel，LCH)配置多个numerology，以支持不同业务场景的传输需求。这样，LTE中请求上行传输资源的技术方案将不再适用于未来的无线通信***。
发明内容
本申请提供一种用于传输缓存状态报告的方法，能够适用于支持多numerology的逻辑信道的缓存数据量的上报。
第一方面，提供了一种用于传输缓存状态报告的方法，包括：终端设备根据至少一个逻辑信道组中每个逻辑信道组对应的numerology属性，确定第一逻辑信道所属的目标逻辑信道组，其中，该第一逻辑信道支持至少一个numerology，每个numerology包括至少一个物理传输参数；该终端设备向网络设备发送缓存状态报告，该缓存状态报告包含属于该目标逻辑信道组的至少一个逻辑信道的待发送数据量，该至少一个逻辑信道包括该第一逻辑信道。
在第一方面的第一种可能的实现方式中，该终端设备根据至少一个逻辑信道组中每个逻辑信道组对应的numerology属性，确定第一逻辑信道所属的目标逻辑信道组，包括：该终端设备确定该第一逻辑信道的numerology属性要求；该终端设备根据该第一逻辑信道的numerology属性要求以及该至少一个逻辑信道组中每个逻辑信道组对应的 numerology属性，确定该目标逻辑信道组。
结合第一方面的上述可能的实现方式，在第一方面的第二种可能的实现方式中，该终端设备根据该第一逻辑信道的numerology属性要求以及该至少一个逻辑信道组中每个逻辑信道组对应的numerology属性，确定第一逻辑信道所属的目标逻辑信道组，包括：该终端设备将该至少一个逻辑信道组中最低限度地满足该第一逻辑信道的numerology属性要求的逻辑信道组确定为该目标逻辑信道组。
可选地，该第一逻辑信道的numerology属性要求可以包括：第一物理传输参数的值等于预设阈值。
可选地，该至少一个逻辑信道组中每个逻辑信道组对应的numerology属性可以包括：该每个逻辑信道组对应的该第一物理传输参数的值。
可选地，该终端设备可以将该至少一个逻辑信道组中对应的该第一物理传输参数的值等于该预设阈值的逻辑信道组确定为该目标逻辑信道组。
可选地，若该至少一个逻辑信道组中包括至少一个候选逻辑信道组，该至少一个候选逻辑信道组中每个候选逻辑信道组对应的该第一物理传输参数的值等于该预设阈值，该终端设备可以将从该至少一个候选逻辑信道组中随机选择的候选逻辑信道组确定为该目标逻辑信道组。
可选地，该终端设备将该至少一个逻辑信道组中最低限度地满足该第一逻辑信道的numerology属性要求的逻辑信道组确定为该目标逻辑信道组，包括：该终端设备确定目标TTI长度，其中，该目标TTI长度为至少一个候选TTI长度中的最大值，该至少一个逻辑信道组对应的numerology属性包括该至少一个候选TTI长度，并且该至少一个候选TTI长度中的每个候选TTI长度小于或等于该第一逻辑信道的最大TTI长度。
可选地，该终端设备将该至少一个逻辑信道组中最低限度地满足该第一逻辑信道的numerology属性要求的逻辑信道组确定为该目标逻辑信道组，包括：该终端设备确定目标SCS，其中，该目标SCS为至少一个候选SCS中的最小值，该至少一个逻辑信道组对应的numerology属性包括该至少一个候选SCS，并且该至少一个候选SCS中的每个候选SCS小于或等于该第一逻辑信道的最小SCS。
可选地，该终端设备存储有逻辑信道组属性表，该逻辑信道组属性表中的表项包含逻辑信道组标识和该逻辑信道组标识对应的numerology属性；该终端设备根据该第一逻辑信道的numerology属性要求以及该至少一个逻辑信道组中每个逻辑信道组对应的numerology属性，确定第一逻辑信道所属的目标逻辑信道组，包括：该终端设备通过利用该第一逻辑信道的numerology属性要求查询该逻辑信道组属性表，确定满足该第一逻辑信道的numerology属性要求的目标逻辑信道组。
结合第一方面的上述可能的实现方式，在第一方面的第三种可能的实现方式中，该终端设备根据该第一逻辑信道的numerology属性要求以及该至少一个逻辑信道组中每个逻辑信道组对应的numerology属性，确定第一逻辑信道所属的目标逻辑信道组，包括：该终端设备将该至少一个逻辑信道组中对应的该第一物理传输参数的值等于该预设阈值的逻辑信道组确定为该目标逻辑信道组。
结合第一方面的上述可能的实现方式，在第一方面的第四种可能的实现方式中，在该终端设备根据至少一个逻辑信道组中每个逻辑信道组对应的numerology属性，确定第一 逻辑信道所属的目标逻辑信道组之前，该方法还包括：该终端设备从该网络设备接收第一指示信息，该第一指示信息指示该至少一个逻辑信道组中每个逻辑信道组对应的numerology属性。
可选地，该终端设备从该网络设备接收第一指示信息，包括：该终端设备从该网络设备接收RRC信令，该RRC信令包含该第一指示信息。
第二方面，提供了另一种用于传输缓存状态报告的方法，包括：终端设备从第一逻辑信道支持的至少一个numerology中确定目标numerology，其中，该至少一个numerology中的每个包括至少一个物理传输参数；该终端设备向网络设备发送缓存状态报告，该缓存状态报告包括该目标numerology对应的至少一个逻辑信道的待发送数据量，其中，该至少一个逻辑信道包括该第一逻辑信道。
在第二方面的第一种可能的实现方式中，该终端设备从第一逻辑信道支持的至少一个numerology中确定目标numerology，包括：该终端设备根据第一逻辑信道的参数集numerology属性要求，从第一逻辑信道支持的至少一个numerology中确定目标numerology。
可选地，该终端设备根据第一逻辑信道的numerology属性要求，从该第一逻辑信道支持的至少一个numerology中确定目标numerology，包括：该终端设备将该至少一个numerology中最低限度地满足该第一逻辑信道的numerology属性要求的numerology确定为该目标numerology。
可选地，该第一逻辑信道的numerology属性要求包括：第一物理传输参数的值等于预设阈值。
可选地，该至少一个numerology中的每个numerology包括该第一物理传输参数的值。
可选地，该终端设备根据第一逻辑信道的numerology属性要求，从该第一逻辑信道支持的至少一个numerology中确定目标numerology，包括：该终端设备将该至少一个numerology中包括的该第一物理传输参数的值等于该预设阈值的numerology确定为该目标numerology。
可选地，若该至少一个numerology中包括至少一个候选numerology，该至少一个候选numerology中每个候选numerology包括的该第一物理传输参数的值等于该预设阈值，该终端设备可以将从该至少一个候选numerology中随机选择的候选numerology确定为该目标numerology。
可选地，该终端设备将该至少一个numerology中最低限度地满足该第一逻辑信道的numerology属性要求的numerology确定为该目标numerology，包括：该终端设备从该至少一个numerology中确定该目标numerology，其中，该numerology为至少一个候选numerology中包括的TTI长度的值最大的numerology，该至少一个numerology包括该至少一个候选numerology，并且该至少一个候选numerology中每个候选numerology包括的TTI长度的值小于或等于该第一逻辑信道的最大TTI长度。
第三方面，提供了一种用于传输缓存状态报告的装置，用于执行上述任意方面或任意方面的任意可能的实现方式中的方法。
具体地，该装置包括用于执行上述任意方面或任意方面的任意可能的实现方式中的方法的单元。
第四方面，提供了另一种用于传输缓存状态报告的装置，包括：存储器和处理器，该存储器用于存储指令，该处理器用于执行该存储器存储的指令，并且当该处理器执行该存储器存储的指令时，该执行使得该处理器执行任意方面或任意方面的任意可能的实现方式中的方法。
第五方面，提供了一种计算机可读介质，用于存储计算机程序，该计算机程序包括用于执行任意方面或任意方面的任意可能的实现方式中的方法的指令。
在本申请中，可选地，LCG对应的numerology属性可以包括LCG对应的numerology或者LCG对应的至少一个物理传输参数值。
在本申请中，可选地，LCG对应的numerology属性可以包括TTI长度。
在本申请中，可选地，逻辑信道的numerology属性要求可以用于选择该LCH所属的LCG，或者用于上报该LCH的缓存数据。
在本申请中，可选地，可以配置LCH在进行BSR上报时关联的物理传输参数，或者可以配置LCH选择LCG的规则。
在本申请中，可选地，LCH或LCG的numerology属性要求可以包括：一个或多个物理传输参数的值满足一定条件。
可选地，LCH或LCG的numerology属性要求可以包括下列中的至少一种：第一物理传输参数的值等于预设阈值，TTI长度小于或等于最大TTI长度(maximum TTI duration)，SCS大于或等于最小SCS(minimum SCS)。
可选地，最低限度地满足LCH或LCG的numerology属性要求可以指下列中的至少一种：对应的物理传输参数的值等于预设阈值，小于或等于maximum TTI duration的最大的TTI长度，大于或等于minimum SCS的最大的SCS。
在本申请中，可选地，物理传输参数值可以指物理传输参数的值，多个物理传输参数值可以指多个不同的物理传输参数中每个物理传输参数的值。这里的物理传输参数可以是numerology中包括的物理传输参数。
在本发明实施例的某些方面，可选地，网络设备可以向该终端设备发送第二指示信息，相应地，终端设备接收网络设备发送的第二指示信息，其中，该第二指示信息用于指示第一逻辑信道的numerology属性要求。
在本发明实施例的某些方面，可选地，逻辑信道组对应的numerology属性可以是预先定义的，或者是网络设备通过RRC信令配置的。
在本发明实施例的某些方面，可选地，缓存状态报告包括逻辑信道组标识字段和缓存大小字段，其中，该逻辑信道组标识字段用于承载逻辑信道组的标识信息，该缓存大小字段用于承载属于该逻辑信道组的至少一个逻辑信道的待发送数据量。
可选地，缓存状态报告包括与N个逻辑信道组对应的N个缓存大小字段，其中，与某个逻辑信道组对应的缓存大小字段用于承载属于该逻辑信道组的至少一个逻辑信道的待发送数据量，N为大于或等于1的整数。
在本申请中，可选地，缓存状态报告可以包括：numerology标识字段和缓存大小字段，其中，该numerology标识字段用于承载numerology的编号，该缓存大小字段用于承载该numerology对应的至少一个逻辑信道的待发送数据量。
在本申请中，可选地，缓存状态报告可以不包含LCG标识字段。
在本申请中，可选地，缓存状态报告包括与N个numerology对应的N个缓存大小字段，其中，与某个numerology对应的缓存大小字段用于承载属于该numerology的至少一个逻辑信道的待发送数据量，N为大于或等于1的整数。
在本申请中，可选地，网络设备可以从该终端设备接收缓存状态报告，并根据该缓存状态报告关联的numerology，分配上行传输资源。
在本申请中，可选地，如果缓存状态报告可以包含属于逻辑信道组的至少一个逻辑信道的待发送数据量，则该网络设备可以根据该逻辑信道组对应的numerology属性，分配上行传输资源。
在本申请中，可选地，如果缓存状态报告包含参数集numerology对应的至少一个逻辑信道的待发送数据量，则网络设备可以根据该目标numerology包括的至少一个物理传输参数的值，分配上行传输资源。
在本申请中，可选地，网络设备可以根据待发送数据量在BSR中占用的字段所对应的numerology或LCG，为该待发送数据量分配上行传输资源。
在本申请中，可选地，网络设备向终端设备发送第一指示信息，终端设备接收网络设备发送的第一指示信息，该第一指示信息用于指示至少一个逻辑信道组中每个逻辑信道组对应的numerology属性。
在本申请中，可选地，网络设备向终端设备发送第二指示信息，终端设备从网络设备接收第二指示信息，该第二指示信息用于指示逻辑信道对应的numerology属性要求。
在本申请中，可选地，网络设备向终端设备发送第三指示信息，终端设备从网络设备接收第三指示信息，该第三指示信息用于指示与多个numerology中每个numerology对应的BSR重传定时器。
在本申请中，可选地，不同的numerology对应不同的BSR重传定时器。
在本申请中，可选地，终端设备向该网络设备发送缓存状态报告，并启动该缓存状态报告关联的numerology对应的BSR重传定时器。
在本申请中，可选地，终端设备向该网络设备发送缓存状态报告，并启动该缓存状态报告关联的每个numerology对应的BSR重传定时器。
在本申请中，可选地，若在numerology对应的BSR重传定时器超时时，该终端设备未从该网络设备收到用于分配对应于该numerology的上行传输资源的上行授权，该终端设备重传请求对应于该numerology的上行传输资源的BSR，并重启该第一numerology对应的BSR重传定时器。
在本申请中，可选地，若在numerology对应的BSR重传定时器未超时时，终端设备接收到用于分配对应于该numerology的上行传输资源的UL Grant，终端设备停止该numerology对应的BSR重传定时器。
在本申请中，可选地，不同的numerology对应的BSR重传定时器之间相互独立。
在本申请中，可选地，在第一numerology对应的BSR重传定时器未超时时，该终端设备可以触发或发送关联第二numerology的BSR。
在本申请中，可选地，若终端设备同时触发多个缓存状态报告，该终端设备根据该多个缓存状态报告关联的numerology，从该多个缓存状态报告中确定目标缓存状态报告；终端设备发送该目标缓存状态报告。
在本申请中，可选地，若终端设备同时触发第一缓存状态报告和第二缓存状态报告，并且该第一缓存状态报告和该第二缓存状态报告请求关联相同的numerology，该终端设备撤销其中的一个缓存状态报告。
在本申请中，可选地，对于关联同一numerology的多个BSR，如果一个MAC PDU已经包含了某个BSR，则撤销已经触发的其他BSR。
在本申请中，可选地，终端设备(即MAC entity)在每个调度间隔(即每个TTI)内至多只能发送一个关联同一numerology的BSR。
在本申请中，可选地，如果一个调度间隔支持发送多个MAC PDU，则每个MAC PDU可以包含一个关联不同numerology的BSR。也就是说，多个MAC PDU可以包含多个BSR，并且该多个BSR中任意两个BSR关联不同的numerology。
在本申请中，可选地，若某个传输时间间隔支持传输多个MAC PDU，并且第一缓存状态报告和第二缓存状态报告关联不同的numerology，该终端设备可以在该传输时间间隔中的第一MAC PDU中包含该第一缓存状态报告，并在该当前传输时间间隔中的第二MAC PDU中包含该第二缓存状态报告。
在本申请中，可选地，可以根据缓存状态报告上报的LCH的优先级，选择发送的缓存状态报告。
在本申请中，可选地，若第一缓存状态报告包含属于第一逻辑信道组的至少一个第一逻辑信道的待发送数据量，并且第二缓存状态报告包含属于第二逻辑信道组的至少一个第二逻辑信道的待发送数据量，第一缓存状态报告和第二缓存状态报告关联相同的numerology，该至少一个第二逻辑信道对应的最高优先级高于该至少一个第一逻辑信道对应的最高优先级，则可以撤销第一缓存状态报告。
在本申请中，可选地，可以根据缓存状态报告中的第一逻辑信道组所对应的numerology属性，确定该缓存状态报告关联的numerology。
在本申请中，可选地，终端设备可以根据BSR上报的至少一个逻辑信道中每个逻辑信道对应的优先级，从该至少一个逻辑信道中确定目标逻辑信道；并且根据该目标逻辑信道的numerology属性要求，确定缓存状态报告关联的numerology。
在本申请中，可选地，终端设备确定BSR匹配的上行传输资源，并在该BSR匹配的上行传输资源上发送该BSR。
在本申请中，可选地，终端设备可以根据缓存状态报告中的第一逻辑信道组对应的numerology属性要求，确定与缓存状态报告匹配的上行传输资源。
在本申请中，可选地，终端设备可以将最低限度地满足第一逻辑信道组对应的numerology属性要求的上行传输资源确定为BSR匹配的上行传输资源。
在本申请中，可选地，该第一逻辑信道组对应的numerology属性要求包括该第一逻辑信道对应的第一物理传输参数的值；该匹配的上行传输资源对应的该第一物理传输参数的值等于该第一逻辑信道对应的第一物理传输参数的值。
在本申请中，可选地，在该终端设备根据第一逻辑信道组对应的numerology属性要求，确定与缓存状态报告匹配的上行传输资源之前，该方法还包括：若该缓存状态报告包含属于该第一逻辑信道组的至少一个逻辑信道的待发送数据量，该终端设备根据该至少一个逻辑信道中每个逻辑信道对应的优先级，从该至少一个逻辑信道中确定目标逻辑信道； 该终端设备根据该目标逻辑信道的numerology属性要求，确定该第一逻辑信道组的numerology属性要求。
在本申请中，可选地，终端设备向网络设备发送缓存状态报告；若该缓存状态报告对应的重传定时器未超时，并且终端设备发现用于传输调度请求的可用的上行传输资源，该终端设备在该可用的上行传输资源上向该网络设备发送调度请求，其中，该可用的上行传输资源的结束时刻早于该缓存状态报告占用的上行传输资源的结束时刻。
附图说明
图1为本申请应用的无线通信***的架构示意图。
图2为图1中的终端设备与网络设备之间的通信接口对应的信道映射示意图。
图3为图1中的终端设备和网络设备的无线接口协议栈的示意图。
图4为本申请实施例提供的终端的硬件架构示意图。
图5为本申请实施例提供的基站的硬件架构示意图。
图6为本申请实施例提供的用于传输缓存状态报告的方法的示意性流程图。
图7为本申请实施例中的缓存状态报告的格式示例示意图。
图8为本申请实施例中的缓存状态报告的另一格式示例的示意图。
图9为本申请实施例提供的另一用于传输缓存状态报告的方法的示意性流程图。
图10为本发明实施例提供的缓存状态报告的另一格式示例的示意图。
图11为本发明实施例提供的用于传输缓存状态报告的方法中第三指示信息的格式示例的示意图。
图12为本发明实施例提供的用于传输缓存状态报告的方法中第三指示信息的另一格式示例的示意图。
图13为本发明实施例提供的另一用于传输缓存状态报告的方法的示意性流程图。
图14为本发明实施例提供的用于传输调度请求的方法中的传输资源示意图。
图15为本发明实施例提供的无线通信***、终端设备和网络设备的示意性框图。
图16为本发明实施例提供的装置的结构示意图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
图1示出了本申请涉及的无线通信***。所述无线通信***可以工作在高频频段上，不限于长期演进(Long Term Evolution，LTE)***，还可以是未来演进的第五代移动通信(the 5th Generation，5G)***、新空口(NR)***，机器与机器通信(Machine to Machine，M2M)***等。如图1所示，无线通信***100可以包括：一个或多个网络设备101，一个或多个终端设备103，以及核心网115。其中：
网络设备101可以为基站，基站可以用于与一个或多个终端设备进行通信，也可以用于与一个或多个具有部分终端功能的基站进行通信(比如宏基站与微基站，如接入点，之间的通信)。基站可以是时分同步码分多址(Time Division Synchronous Code Division Multiple Access，TD-SCDMA)***中的基站收发台(Base Transceiver Station，BTS)，也可以是LTE***中的演进型基站(Evolutional Node B，eNB)，以及5G***、新空口 (NR)***中的基站。另外，基站也可以为接入点(Access Point，AP)、传输节点(Trans TRP)、中心单元(Central Unit，CU)或其他网络实体，并且可以包括以上网络实体的功能中的一些或所有功能。
终端设备103可以分布在整个无线通信***100中，可以是静止的，也可以是移动的。在本申请的一些实施例中，终端设备103可以是移动设备、移动台(mobile station)、移动单元(mobile unit)、M2M终端、无线单元，远程单元、用户代理、移动客户端等等。
具体的，网络设备101可用于在网络设备控制器(未示出)的控制下，通过无线接口105与终端设备103通信。在一些实施例中，所述网络设备控制器可以是核心网115的一部分，也可以集成到网络设备101中。具体的，网络设备101可用于通过回程(blackhaul)接口113(如S1接口)向核心网115传输控制信息或者用户数据。具体的，网络设备101与网络设备101之间也可以通过回程(blackhaul)接口111(如X2接口)，直接地或者间接地，相互通信。
图2示出了图1中的无线接口105(即终端设备103和网络设备101之间的无线接口)对应的信道映射图。图3所示的无线接口协议层之间的接口可表达为信道，具体可包括：逻辑信道、传输信道和物理信道。其中：
(1)逻辑信道：逻辑信道描述了信息的类型，即定义了传输的是什么信息。媒体接入控制(Media Access Control，MAC)层与无线链路控制(Radio Link Control，RLC)层之间的接口为逻辑信道。MAC层通过逻辑信道为RLC层提供服务。
如图2所示，逻辑信道分为2类：逻辑控制信道和逻辑业务信道。其中，逻辑控制信道用于传输控制面信息，可以包括：寻呼控制信道(Paging Control Channel，PCCH)、公共控制信道(Common Control Channel，CCCH)、专用控制信道(Dedicated Control Channel，DCCH)。逻辑业务信道用于传输用户面信息，可以包括：专用业务信道(Dedicated Traffic Channel，DTCH)、多播业务信道(Multi-broadcast Traffic Channel，MTCH)，等等。
(2)传输信道：传输信道描述的是信息的传输方式，即定义了信息是如何传输的。物理层(Physical Layer，PHY)和媒体接入控制(MAC)层之间的接口为传输信道。PHY层通过传输信道为MAC层提供服务。传输信道通常可以根据在无线接口上传输信号的方式，如信道编码策略、调制方法和天线映射方式，进行分类。
如图2所示，传输信道可以包括：下行共享信道(Downlink Shared Channel，DLSCH)、广播信道(Broadcast Channel，BCH)、多播信道(Multicast Channel，MCH)、寻呼信道(Paging Channel，PCH)、上行共享信道(Uplink Shared Channel，ULSCH)、随机接入信道(Random Access Channel，RACH)，等等。
(3)物理信道：由物理层用于具体信号的传输。物理信道和承载高层信息的资源单元(Resource Element，RE)集合相对应。组成物理信道的基本实体是资源单元(RE)和资源块(Resource Block，RB)。
如图2所示，物理信道可以包括：物理下行控制信道(Physical Downlink Control Channel，PDCCH)、物理下行共享信道(Physical Downlink Shared Channel，PDSCH)、物理广播信道(Physical Broadcast Channel，PBCH)、PMCH(Physical Multicast Channel，物理多播信)、物理HARQ指示信道(Physical Hybrid ARQ Indicator Channel，PHICH)、 物理控制格式指示信道(Physical Control Format Indicator Channel，PCFICH)、物理上行控制信道(Physical Uplink Control Channel，PUCCH)、物理上行共享信道(Physical Uplink Shared Channel，PUSCH)、物理随机接入信道(Physical Random Access Channel，PRACH)。
需要说明的是，图1示出的无线通信***100仅仅是为了更加清楚的说明本申请的技术方案，并不构成对本申请的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请提供的技术方案对于类似的技术问题，同样适用。
参考图4，图4示出了本申请的一些实施例提供的终端200。如图4所示，终端200可包括：一个或多个终端处理器201、存储器202、通信接口203、接收器205、发射器206、耦合器207、天线208、用户接口202，以及输入输出模块(包括音频输入输出模块210、按键输入模块211以及显示器212等)。这些部件可通过总线204或者其他方式连接，图4以通过总线连接为例。其中：
通信接口203可用于终端200与其他通信设备，例如网络设备，进行通信。具体的，所述网络设备可以是图5所示的网络设备300。具体的，通信接口203可以是长期演进(LTE)(4G)通信接口，也可以是5G或者未来新空口的通信接口。不限于无线通信接口，终端200还可以配置有有线的通信接口203，例如局域接入网(Local Access Network，LAN)接口。
发射器206可用于对终端处理器201输出的信号进行发射处理，例如信号调制。接收器205可用于对天线208接收的移动通信信号进行接收处理，例如信号解调。在本申请的一些实施例中，发射器206和接收器205可看作一个无线调制解调器。在终端200中，发射器206和接收器205的数量均可以是一个或者多个。天线208可用于将传输线中的电磁能转换成自由空间中的电磁波，或者将自由空间中的电磁波转换成传输线中的电磁能。耦合器207用于将天线208接收到的移动通信信号分成多路，分配给多个的接收器205。
除了图4所示的发射器206和接收器205，终端200还可包括其他通信部件，例如GPS模块、蓝牙(Bluetooth)模块、无线高保真(Wireless Fidelity，Wi-Fi)模块等。不限于上述表述的无线通信信号，终端200还可以支持其他无线通信信号，例如卫星信号、短波信号等等。不限于无线通信，终端200还可以配置有有线网络接口(如LAN接口)来支持有线通信。
所述输入输出模块可用于实现终端200和用户/外部环境之间的交互，可主要包括包括音频输入输出模块210、按键输入模块211以及显示器212等。具体的，所述输入输出模块还可包括：摄像头、触摸屏以及传感器等等。其中，所述输入输出模块均通过用户接口209与终端处理器201进行通信。
存储器202与终端处理器201耦合，用于存储各种软件程序和/或多组指令。具体的，存储器202可包括高速随机存取的存储器，并且也可包括非易失性存储器，例如一个或多个磁盘存储设备、闪存设备或其他非易失性固态存储设备。存储器202可以存储操作***(下述简称***)，例如ANDROID，IOS，WINDOWS，或者LINUX等嵌入式操作***。存储器202还可以存储网络通信程序，该网络通信程序可用于与一个或多个附加设备，一个或多个终端设备，一个或多个网络设备进行通信。存储器202还可以存储用户接口程序，该用户接口程序可以通过图形化的操作界面将应用程序的内容形象逼真的显示出来，并通过菜单、对话框以及按键等输入控件接收用户对应用程序的控制操作。
在本申请的一些实施例中，存储器202可用于存储本申请的一个或多个实施例提供的资源分配方法在终端200侧的实现程序。关于本申请的一个或多个实施例提供的资源分配方法的实现，请参考后续实施例。
终端处理器201可用于读取和执行计算机可读指令。具体的，终端处理器201可用于调用存储于存储器212中的程序，例如本申请的一个或多个实施例提供的资源分配方法在终端200侧的实现程序，并执行该程序包含的指令。
可以理解的，终端200可以是图7示出的无线通信***100中的终端设备103，可实施为移动设备，移动台(mobile station)，移动单元(mobile unit)，无线单元，远程单元，用户代理，移动客户端等等。
需要说明的，图4所示的终端200仅仅是本申请实施例的一种实现方式，实际应用中，终端200还可以包括更多或更少的部件，这里不作限制。
参考图5，图5示出了本申请的一些实施例提供的网络设备300。如图5所示，网络设备300可包括：一个或多个网络设备处理器301、存储器302、通信接口303、发射器305、接收器306、耦合器307和天线308。这些部件可通过总线304或者其他式连接，图5以通过总线连接为例。其中：
通信接口303可用于网络设备300与其他通信设备，例如终端设备或其他网络设备，进行通信。具体的，所述终端设备可以是图4所示的终端200。具体的，通信接口303通信接口203可以是长期演进(LTE)(4G)通信接口，也可以是5G或者未来新空口的通信接口。不限于无线通信接口，网络设备300还可以配置有有线的通信接口303来支持有线通信，例如一个网络设备300与其他网络设备300之间的回程链接可以是有线通信连接。
发射器305可用于对网络设备处理器301输出的信号进行发射处理，例如信号调制。接收器306可用于对天线308接收的移动通信信号进行接收处理。例如信号解调。在本申请的一些实施例中，发射器305和接收器306可看作一个无线调制解调器。在网络设备300中，发射器305和接收器306的数量均可以是一个或者多个。天线308可用于将传输线中的电磁能转换成自由空间中的电磁波，或者将自由空间中的电磁波转换成传输线中的电磁能。耦合器307可用于将移动通信号分成多路，分配给多个的接收器306。
存储器302与网络设备处理器301耦合，用于存储各种软件程序和/或多组指令。具体的，存储器302可包括高速随机存取的存储器，并且也可包括非易失性存储器，例如一个或多个磁盘存储设备、闪存设备或其他非易失性固态存储设备。存储器302可以存储操作***(下述简称***)，例如uCOS、VxWorks、RTLinux等嵌入式操作***。存储器302还可以存储网络通信程序，该网络通信程序可用于与一个或多个附加设备，一个或多个终端设备，一个或多个网络设备进行通信。
网络设备处理器301可用于进行无线信道管理、实施呼叫和通信链路的建立和拆除，并为本控制区内的用户提供小区切换控制等。具体的，网络设备处理器301可包括：管理/通信模块(Administration Module/Communication Module，AM/CM)(用于话路交换和信息交换的中心)、基本模块(Basic Module，BM)(用于完成呼叫处理、信令处理、无线资源管理、无线链路的管理和电路维护功能)、码变换及子复用单元(Transcoder and SubMultiplexer，TCSM)(用于完成复用解复用及码变换功能)等等。
本申请实施例中，网络设备处理器301可用于读取和执行计算机可读指令。具体的， 网络设备处理器301可用于调用存储于存储器302中的程序，例如本申请的一个或多个实施例提供的资源分配方法在网络设备300侧的实现程序，并执行该程序包含的指令。
可以理解的，网络设备300可以是图7示出的无线通信***100中的基站101，可实施为基站收发台，无线收发器，一个基本服务集(BSS)，一个扩展服务集(ESS)，NodeB，eNodeB，接入点或TRP等等。
需要说明的，图5所示的网络设备300仅仅是本申请实施例的一种实现方式，实际应用中，网络设备300还可以包括更多或更少的部件，这里不作限制。
本申请中，网络设备101和终端设备103之间可以支持多业务的同时传输(上行传输或下行传输)，在MAC层为多个业务分别分配逻辑信道(Logical，Channel，LCH)。LCH可以支持一个或多个参数集(numerology)，其中，numerology可以包括一个或多个物理传输参数。表1示出了LCH可能支持的九种不同的numerology示例，其中，每个numerology包括以下物理传输参数：子载波间隔(Subcarrier Spacing，SCS)、符号长度(Symbol duration)、常规循环前缀(Normal CP)、常规最大带宽(Normal max BW)、最大快速傅里叶变换大小(Max FFT size)、以符号为单位的最小调度间隔(Minimum Scheduling Interval)、以时隙(slot)为单位的最小调度间隔和以毫秒为单位的最小调度间隔。可选地，不同的numerology可以包括至少一个数值不同的物理传输参数，例如，numerology 1的子载波间隔、符号长度、常规循环前缀和常规最大带宽均不同于numerology2。可选地，不同的numerology中也可以包括一个或多个数值相同的物理传输参数，例如，numerology 1的最大FFT大小和最小调度间隔与numerology 2相同。可选地，不同的numerology也可以不包括数值相同的物理传输参数，但本申请对此不做限定。
可选地，本申请中的numerology的总个数可以更多或更少，numerology包括的物理传输参数的个数可以更多或更少，例如，每个numerology可以仅包括最小调度间隔，此时，不同的numerology可以指不同的最小调度间隔，但本申请不限于此。应理解，在本申请中，numerology的最小调度间隔可以具体指numerology对应的最小传输时间间隔(Transmission Time Interval，TTI)，下文中的TTI长度可以指最小调度间隔，但本申请不限于此。
表1 numerology的物理传输参数配置
Figure PCTCN2018085189-appb-000001
Figure PCTCN2018085189-appb-000002
这样，当LCH支持多个numerology时，终端设备如何向网络设备请求上行传输资源是本领域尚未解决的技术问题。
在本申请中，可以请求网络设备分配对应于某种numerology属性的上行传输资源。
本申请提供了一种用于传输缓存状态报告的方法，可以配置逻辑信道组对应的numerology属性，并且根据逻辑信道组对应的numerology属性，确定逻辑信道所属的目标逻辑信道组。
图6示出了本申请提供的用于传输缓存状态报告的方法400。
S410，网络设备向终端设备发送第一指示信息，该第一指示信息指示至少一个LCG中每个LCG对应的numerology属性。
相应地，终端设备可以从网络设备接收第一指示信息，并根据第一指示信息确定该至少一个LCG中每个LCG对应的numerology属性。
可选地，LCG对应的numerology属性可以包括LCG对应的numerology或者LCG对应的至少一个物理传输参数值。
应理解，在本申请中，术语“LCG对应的numerology属性”也可以称为“LCG对应的物理传输属性”，或者也可以具有其他名称，本申请对该名称不做限定。
还应理解，在本申请中，物理传输参数值可以指物理传输参数的值，相应地，多个物理传输参数值可以指多个不同的物理传输参数中每个物理传输参数的值。这里的物理传输参数可以是numerology中包括的物理传输参数，但本申请不限于此。
在本申请中，可以为LCG配置参数集(numerology)属性。可选地，该numerology属性可以具体为一个numerology或多个numerology，或者也可以是numerology中包括的一个或多个物理传输参数，相应地，一个LCG可以对应于一个或多个物理传输参数值。作为一个可选例子，LCG的numerology属性可以具体为TTI长度，相应地，每个LCG可以对应于一个TTI长度值。例如，假设有三个可选的LCG：LCG 1、LCG 2和LCG 3，如表2所示，LCG 1对应的TTI长度为4ms，LCG 2对应的TTI长度为1ms，LCG 3对应的TTI长度等于2ms，这里不同的LCG可以对应于不同的TTI长度值，但本申请不限于此。再例如，如果该numerology属性具体为一个或多个numerology，此时，可以将表2中的TTI长度替换为numerology编号，但本申请对此不做限定。
可选地，LCG对应的numerology属性可以是不变的，或者也可以是动态变化的。例如，网络设备可以根据当前网络状态和/或历史统计信息，确定LCG对应的numerology属性，该当前网络状态可以包括当前的资源利用信息，历史统计信息可以包括某个LCH或LCG的数据传输时延，等等，本申请对此不做限定。
可选地，网络设备可以根据终端设备的能力(例如对numerology的支持能力，包含但不限于最大带宽，子载波间隔等)或者用户的注册信息(例如终端注册的业务类型)确定终端设备支持的numerology属性，并配置给一个或多个LCH，但本发明实施例不限于此。
在本申请中，网络设备可以通过第一指示信息配置LCG的numerology属性，即指示LCG与物理传输参数值或numerology之间的对应关系。可选地，第一指示信息可以指示多个候选的LCG中的部分或全部LCG的numerology属性，但本申请不限于此。
可选地，网络设备可以通过终端设备专有信令向终端设备发送该第一指示信息。或者，网络设备也可以组播或者广播该第一指示信息，本申请对此不做限定。作为一个可选例子，网络设备可以通过无线资源控制(Radio Resource Control，RRC)信令配置该至少一个LCG中每个LCG对应的numerology属性，即第一指示信息可以包含在网络设备发送的RRC信令中，但本申请不限于此。
可选地，该第一指示信息可以包括LCG对应的numerology的标识信息，或者该第一指示信息也可以包括LCG对应的一个或多个物理传输参数的值，但本申请不限于此。
可选地，终端设备还可以存储该至少一个LCG中每个LCG对应的numerology属性，但本申请不限于此。
表2 LCG的numerology属性
逻辑信道组 TTI长度(ms)
LCG 1 4
LCG 2 1
LCG 3 2
S420，在属于某个LCH(例如第一LCH)的上行数据到达时，终端设备可以根据至少一个LCG中每个LCG对应的numerology属性，确定该LCH所属的LCG，即目标LCG。
可选地，该至少一个LCG可以具体为多个LCG。终端设备可以根据该多个LCG中每个LCG对应的numerology属性，确定LCH所属的LCG。
该LCH可以支持多个numerology。可选地，可以根据该LCH支持的多个numerology以及至少一个LCG中每个LCG对应的numerology属性，确定该LCH所属的LCG，但本申请不限于此。
作为一个例子，可以配置LCH的numerology属性要求(也可以称为LCH的numerology属性)，LCH的numerology属性要求可以用于选择该LCH所属的LCG，或者用于上报该LCH的缓存数据。此时，可以根据LCH的numerology属性要求以及至少一个LCG中每个LCG对应的numerology属性，确定该LCH所属的LCG。可选地，LCH的numerology属性要求可以由网络设备预先配置或者预先定义，例如，网络设备可以向终端设备发送第二指示信息，该第二指示信息指示一个或多个LCH的numerology属性要求，相应地，终端设备可以根据从网络设备接收的该第二指示信息，确定该一个或多个LCH的numerology 属性要求，并据此选择该LCH所属的LCG，但本申请不限于此。
可选地，该numerology属性要求可以包括：一个或多个物理传输参数的值满足一定条件，此时，可以配置LCH在进行BSR上报时关联的numerology属性。作为一个可选例子，LCG对应的numerology属性可以包括TTI长度(或最小调度间隔)，并且该numerology属性要求可以包括：TTI长度等于某个选择门限，例如，如表3所示，LCH 1的TTI长度选择门限为2ms，LCH 2和LCH 3的TTI选择长度为1ms，应理解，表3示例性地示出了三个LCH对应的TTI长度选择门限，可选地，本申请可以为每个LCH配置对应的numerology属性要求，但本申请不限于此。此时，可选地，可以将对应的TTI长度等于该LCH的TTI长度选择门限的LCG确定为该LCH所属的LCG。此时，可以将恰好满足该LCH的numerology属性要求的LCG确定为该LCH所属的LCG，而该恰好满足该LCH的numerology属性要求的LCG也可以是最低限度地满足该LCH的numerology属性要求的LCG。通过比较表2和表3可以得出，LCH 1所属的LCG为LCG 3，LCH 2和LCH 3所属的LCG为LCG 2，但本申请不限于此。
表3 LCH对应的numerology属性要求示例
逻辑信道 TTI长度选择门限(ms)
LCH 1 2
LCH 2 1
LCH 3 1
作为另一个可选例子，LCH的numerology属性要求可以包括：TTI长度小于或等于LCH对应的最大TTI长度(maximum TTI duration)。可选地，该最大TTI长度可以是该LCH支持的多个numerology中包括的最大TTI长度或某个较大的TTI长度，或者也可以是额外定义的参数，具体可以由网络设备预先配置或者预先定义，本申请对此不做限定。例如，如表4所示，LCH 1对应的最大TTI长度为4ms，LCH 2对应的最大TTI长度为2ms，LCH 3对应的最大TTI长度为1ms。此时，可以根据LCH对应的最大TTI长度，确定该LCH所属的LCG。可选地，可以将该至少一个LCG对应的TTI长度中小于或等于LCH对应的最大TTI长度的最大的TTI长度所对应的LCG确定为该LCH所属的LCG，也就是说，可以从该至少一个LCG对应的TTI长度中确定目标TTI长度，该目标TTI长度是至少一个候选TTI长度中的最大值，其中，该至少一个LCG对应的TTI长度可以包括该至少一个候选TTI长度，并且该至少一个候选TTI长度可以小于或等于该LCH对应的最大TTI长度，但本申请不限于此。通过比较表2和表4可以得出，LCH 1所属的LCG为LCG 1，LCH 2所属的LCG为LCG 3，LCH 3所属的LCG为LCG 2。
表4 LCH对应的numerology属性要求示例
Figure PCTCN2018085189-appb-000003
Figure PCTCN2018085189-appb-000004
作为另一个可选例子，LCG对应的numerology属性可以包括SCS，并且LCH的numerology属性要求可以包括：SCS大于或等于LCH对应的最小SCS(Minimum SCS)。可选地，该最小SCS可以是该LCH支持的多个numerology中包括的最小SCS或某个较小的SCS，也可以是额外定义的参数，具体可以由网络设备预先配置或者预先定义，本申请对此不做限定。此时，可以根据LCH对应的最小SCS，确定该LCH所属的LCG。可选地，可以将该至少一个LCG对应的SCS中大于或等于LCH对应的最小SCS的最小的SCS所对应的LCG确定为该LCH所属的LCG，也就是说，可以从该至少一个LCG对应的SCS中确定目标SCS，该目标SCS是至少一个候选SCS中的最小值，其中，该至少一个LCG对应的SCS可以包括该至少一个候选SCS，并且该至少一个候选SCS可以大于或等于该LCH对应的最小SCS，但本申请不限于此。
可选地，为LCH选择LCG的规则可以预先定义，或者也可以由网络设备预先配置。例如，网络设备可以指示为某个LCH选择最低限度地满足该LCH的numerology属性要求的LCG，例如，指示选择小于或等于maximun TTI duration的最大的TTI duration所对应的LCG，或者选择大于或等于Minimum SCS的最小的SCS所对应的LCG，本申请不限于此。
应理解，在本申请中，术语“LCH的numerology属性要求”也可以称为“LCH的物理传输参数要求”或“LCH的传输要求”，或者也可以具有其他名称，本申请对此不做限定。
S430，终端设备向网络设备发送BSR，该BSR包含属于该目标LCG的至少一个LCH的待发送数据量。
在BSR中，缓存数据量可以仍以LCG为单位，相应地，该BSR上报的缓存数据量可以等于属于该目标LCG的逻辑信道的待发送数据量之和，即BSR可以上报选择了该目标LCG的一个或多个LCH的缓存数据量。
作为一个可选实施例，在本申请中，该BSR可以为短格式BSR。例如，如图7所示，BSR可以包括LCG标识(LCG ID)字段和缓存大小(Buffer Size)字段，其中，该LCG标识字段承载该目标LCG的标识信息，该缓存大小字段承载属于该目标LCG的至少一个逻辑信道的待发送数据量。
作为另一个可选实施例，该BSR可以为长格式BSR。例如，如图8所示，BSR可以包括与N个LCG对应的N个缓存大小字段，其中，与该目标LCG对应的缓存大小字段用于承载属于该目标LCG的至少一个逻辑信道的待发送数据量，N为大于或等于1的整数。此时，终端设备可以确定该目标LCG对应的缓存大小字段，并在该对应的缓存大小字段中承载属于该目标LCG的逻辑信道的待发送数据量之和，但本申请不限于此。
S440，网络设备在接收到该BSR之后，可以根据该BSR，为终端设备分配上行传输资源。
可选地，当网络设备从终端设备接收到该BSR之后，可以根据该BSR包含的LCG 的信息，确定该BSR所请求的上行传输资源对应的numerology属性，并可选地可以据此进行相应的资源分配操作。例如，如果该BSR包含LCG 1的标识信息，则网络设备可以根据表2确定该BSR请求对应的TTI长度等于4的上行传输资源，并为该终端设备分配对应的TTI长度等于4的上行传输资源，但本申请不限于此。
可选地，在某些情况下也可以不执行S440。例如，若当前没有可用的上行传输资源，则网络设备可以不为终端设备分配上行传输资源，但本申请不限于此。
在本申请中，可选地，对于支持单个numerology的LCH，可以直接配置LCH所属的LCG；对于支持多numerology的LCH，可以不用预先配置其所属的LCG，而是在上报BSR时选择其所属的LCG。
这样，在本申请中，通过为LCG配置对应的numerology属性，并且根据LCG对应的numerology属性选择LCH所属的LCG，能够实现支持多numerology的LCH的缓存数据量的上报，有利于提高数据传输性能并满足不同业务的需求。
本申请提供了另一种用于传输缓存状态报告的方法，可以从LCH支持的多个numerology中选择目标numerology，并在BSR中包含该目标numerology的标识信息。此时，BSR中可以不包含LCG信息，相应地，终端设备可以无需选择LCH所属的LCG。
图9示出了本申请提供的另一种用于传输缓存状态报告的方法500。
S510，网络设备向终端设备发送第二指示信息，该第二指示信息指示LCH(例如第一LCH)对应的numerology属性要求。
可选地，该第二指示信息可以用于指示一个或多个LCH对应的numerology属性要求。LCH的numerology属性要求可以用于为该LCH选择用于上报BSR的numerology。相应地，终端设备可以从网络设备接收第二指示信息，并根据第二指示信息，确定该LCH对应的numerology属性要求。
可选地，网络设备可以通过终端设备专有信令向终端设备发送该第二指示信息。或者，网络设备也可以组播或者广播该第二指示信息，本申请对此不做限定。作为一个可选例子，网络设备可以通过无线资源控制(Radio Resource Control，RRC)信令配置该LCH对应的numerology属性要求，即第二指示信息可以包含在网络设备发送的RRC信令中，但本申请不限于此。
可选地，终端设备还可以存储该LCH对应的numerology属性要求，但本申请不限于此。
可选地，LCH的numerology属性要求可也以预先定义，此时，也可以不执行S510，但本申请不限于此。
S520，在属于LCH(例如第一LCH)的上行数据到达时，终端设备可以根据该LCH的numerology属性要求，从该LCH支持的至少一个numerology中确定目标numerology。
可选地，该LCH可以支持多个numerology。终端设备可以根据该LCH支持的多个numerology包括的物理传输参数的值以及该LCH的numerology属性要求，确定该LCH对应的目标numerology，即用于上报BSR的numerology，但本申请不限于此。
可选地，该numerology属性要求可以包括：一个或多个物理传输参数的值满足一定条件。作为一个可选例子，numerology可以包括TTI长度(或最小传输间隔)，并且该numerology属性要求可以包括：TTI长度等于某个选择门限，例如，如表3所示。此时， 可选地，可以将包括的TTI长度值等于该LCH的TTI长度选择门限的numerology确定为该LCH对应的目标numerology。此时，可以将恰好满足该LCH的numerology属性要求的numerology确定为该LCH对应的目标numerology，而该恰好满足该LCH的numerology属性要求的numerology也可以是最低限度地满足该LCH的numerology属性要求的numerology，但本申请不限于此。
作为另一个可选例子，LCH的numerology属性要求可以包括：TTI长度小于或等于LCH对应的最大TTI长度(maximum TTI duration)。可选地，该最大TTI长度可以由网络设备预先配置或者预先定义，本申请对此不做限定。此时，可选地，可以将LCH支持的至少一个numerology包括的TTI长度中小于或等于该LCH对应的最大TTI长度的最大的TTI长度所属的numerology确定为该LCH对应的目标numerology，也就是说，可以从该至少一个numerology包括的TTI长度中确定目标TTI长度，该目标TTI长度是至少一个候选TTI长度中的最大值，其中，该至少一个numerology可以包括该至少一个候选TTI长度，并且该至少一个候选TTI长度可以小于或等于该LCH对应的最大TTI长度，但本申请不限于此。
作为另一个可选例子，numerology可以包括SCS，并且LCH的numerology属性要求可以包括：SCS大于或等于LCH对应的最小SCS(Minimum SCS)。可选地，该最小SCS可以由网络设备预先配置或者预先定义，本申请对此不做限定。此时，可以根据LCH对应的最小SCS，确定该LCH对应的目标SCS。可选地，可以将该至少一个numerology包括的SCS中大于或等于LCH对应的最小SCS的最小的SCS所属的numerology确定为该LCH对应的目标numerology，也就是说，可以从该至少一个numerology包括的SCS中确定目标SCS，该目标SCS是至少一个候选SCS中的最小值，其中，该至少一个numerology可以包括该至少一个候选SCS，并且该至少一个SCS可以大于或等于该LCH对应的最小SCS，但本申请不限于此。
可选地，为LCH选择numerology的规则可以预先定义，或者也可以由网络设备预先配置。例如，网络设备可以指示为某个LCH选择最低限度地满足该LCH的numerology属性要求的numerology，例如，指示选择小于或等于maximun TTI duration的最大TTI duration所属的numerology，或者选择大于或等于Minimum SCS的最小SCS所属的numerology，本申请不限于此。
S530，终端设备向网络设备发送BSR，该BSR包含对应于该目标numerology的至少一个LCH的待发送数据量。
在BSR中，缓存数据量可以以numerology为单位进行统计，相应地，该BSR上报的缓存数据量可以等于对应于该目标numerology的LCH的待发送数据量之和，即BSR可以上报选择了该目标numerology的一个或多个LCH的缓存数据量。
作为一个可选实施例，在本申请中，如图10所示，BSR可以包括numerology标识(numerology ID)字段和缓存大小(Buffer Size)字段，其中，该numerology标识字段承载该目标numerology的标识信息，该缓存大小字段承载对应于该目标numerology的至少一个LCH的待发送数据量。
作为另一个可选实施例，BSR可以包括与N个numerology对应的N个缓存大小字段，其中，与该目标numerology对应的缓存大小字段用于承载对应于该目标numerology的至 少一个LCH的待发送数据量，N为大于或等于1的整数。此时，终端设备可以确定该目标numerology对应的缓存大小字段，并在该对应的缓存大小字段中承载对应于该目标numerology的逻辑信道的待发送数据量之和，但本申请不限于此。
S540，网络设备在接收到该BSR之后，可以根据该BSR，为终端设备分配上行传输资源。
可选地，当网络设备从终端设备接收到该BSR之后，可以根据该BSR包含的numerology的信息，确定该BSR所请求的上行传输资源对应的numerology属性，并可选地可以据此进行相应的资源分配操作。例如，如果该BSR包含numerology 1的编号，则网络设备可以为该终端设备分配对应于numerology 1的上行传输资源，或者可以为终端设备分配对应的一个或多个物理传输参数的值等于该numerology 1中的相同物理传输参数的值的上行传输资源，例如分配对应的TTI长度等于numerology 1中的TTI长度的上行传输资源，但本申请不限于此。
可选地，在某些情况下也可以不执行S540。例如，若当前没有可用的上行传输资源，则网络设备可以不为终端设备分配上行传输资源，但本申请不限于此。
这样，在本申请中，通过为LCH配置numerology属性要求，并且根据LCH的numerology属性要求，从该LCH支持的多个numerology中选择用于上报BSR的numerology，能够实现支持多numerology的LCH的缓存数据量的上报，有利于提高数据传输性能。
在现有技术中，终端设备在发送BSR后启动/重启重传定时器(retxBSR-Timer)，并且在收到UL grant之后，即在获得了上行传输资源后，重启retxBSR-Timer。如果在retxBSR-Timer超时时未收到UL grant，并且属于LCG的任意一个LCG有数据待发送，则可以触发新的BSR，其中，该新触发的BSR属于常规BSR(regular BSR)；如果retxBSR-Timer未超时，只有在某个LCH有数据到达且优先级高于当前BSR的LCG包括的任意LCH，才会触发新的BSR，否则不会触发BSR(regular BSR)。这样，如果不同的BSR用于请求对应于不同numerology或物理传输参数值的上行传输资源，则收到的UL Grant可能只用于分配部分BSR请求的上行传输资源，该上行传输资源对应于某个特定numerology或物理传输参数值。此时，如果仍采用现有技术的方案，可能会使得部分BSR请求的上行传输资源一直得不到分配，从而降低***性能。
本申请提供了一种用于传输缓存状态报告的方法，可以为终端设备支持的每种numerology(或物理传输参数值)配置一个BSR重传定时器retxBSR-Timer；相应地，终端设备可以根据各个numerology的retxBSR-Timer来管理BSR的重传，只有当收到BSR请求的numerology对应的UL grant时，才重启对应numerology的retxBSR-Timer。
具体地，网可以络设备向终端设备发送第三指示信息，该第三指示信息用于指示该多个numerology中每个numerology对应的BSR重传定时器。
可选地，不同numerology对应的BSR重传定时器时长可以相同或不同，本申请对此不做限定。
可选地，该网络设备可以通过RRC信令向该终端设备发送该第三指示信息，但本申请不限于此。
作为一个例子，如图11所示，该第三指示信息可以包括numerology标识字段和对应 的retxBSR-Timer时长，其中，numerology标识字段可以用于承载numerology的标识信息，对应的retxBSR-Timer时长可以用于承载该numerology对应的BSR重传定时器的时长，但本申请不限于此。
作为另一个例子，该第三指示信息可以包括物理传输参数字段和对应的retxBSR-Timer时长字段，此时，该第三指示信息可以用于指示一个或多个物理传输参数的不同数值(即不同的numerology属性)对应的BSR重传定时器。例如，如图12所示，第三指示信息可以包括TTI长度和对应的BSR重传定时器时长，但本申请不限于此。
终端设备可以从网络设备接收该第三指示信息。该终端设备可以根据该第三指示信息，确定与该多个numerology中每个numerology对应的BSR重传定时器。
作为一个例子，该终端设备可以向该网络设备发送第一BSR，并且可以启动该第一BSR关联的numerology属性对应的BSR重传定时器。
可选地，BSR关联的numerology属性可以指BSR请求的传输资源对应的numerology，但本发明实施例不限于此。
可选地，该第一BSR可以为短格式BSR，例如图7或图10所示的BSR，相应地，该第一BSR可以关联一个numerology，例如第一numerology，则终端设备可以启动第一numerology对应的BSR重传定时器。或者，该第一BSR可以为长格式BSR，相应地，该第一BSR可以关联一个或多个numerology，例如包括第一numerology在内的至少一个numerology，终端设备可以启动该至少一个numerology中每个numerology对应的BSR重传定时器，但本发明实施例不限于此。
可选地，在某个numerology对应的BSR重传定时器未超时时，终端设备等待针对该numerology的UL Grant，并且可以不再触发或发送关联该numerology的BSR。
可选地，如果收到针对某个numerology的UL grant，则可以停止或重启该numerology对应的BSR重传定时器。此时，可选地，如果有需要，终端设备可以再次触发或发送关联该numerology的BSR。
可选地，无论某个numerology对应的BSR重传定时器是否超时，终端设备都可以触发或发送关联另一个numerology的BSR。
可选地，若在该第一numerology对应的BSR重传定时器超时时，该终端设备未从该网络设备收到用于分配对应于该第一numerology的上行传输资源的UL Grant，即未收到针对该第一numerology的UL Grant，则该终端设备可以重传该第一BSR或者重传该第一numerology对应的缓存数据量，并且可以重启该第一numerology对应的BSR重传定时器。
可选地，在该第一numerology对应的BSR重传定时器未超时时，如果有属于某个LCH的数据到达并且需要请求对应于第二numerology的上行传输资源，无论是否收到针对该第一numerology的UL Grant，都可以触发新的BSR。此时，可选地，该终端设备可以向该网络设备发送第二BSR，该第二BSR请求对应于第二numerology的上行传输资源，即第二BSR关联第二numerology，但本申请不限于此。
在本申请中，可选地，如果终端设备已经发送了一个BSR，并且正在等待网络设备发送的上行授权(UL grant)，此时有更高优先级的数据需要传输，该数据所属的LCH高于属于该已发送的BSR中对应的LCG的任意LCH的优先级，则终端设备可以触发BSR的上报。
这样，本申请提供的技术方案，通过为请求对应于不同numerology的资源的BSR配置不同的重传定时器，有利于有利于及时响应不同LCH对不同numerology的资源的需求，从而提高数据传输性能。
在现有技术中，每个终端设备在一个TTI中最多只能传输一个BSR。当终端设备同时触发了多个BSR时，如果待传输的媒体访问控制(Media Access Control，MAC)协议数据单元(Protocol Data Unit，PDU)中包含了某个BSR，则撤销终端设备触发的其他BSR。由于不同的BSR可能用于请求对应于不同numerology的传输资源，一个TTI中仅发送一个BSR可能会导致有些BSR请求的传输资源在很长时间内都无法得到分配，从而影响数据传输效率和用户体验。
本申请提供了一种用于传输缓存状态报告的方法，如果终端设备同时触发了多个BSR，则可以根据该多个BSR关联的numerology属性，确定实际发送的BSR。
可选地，终端设备可以同时触发第一BSR和第二BSR，若该第一BSR和该第二BSR请求对应相同的numerology的上行传输资源，即该第一BSR和该第二BSR关联相同的numerology，则该终端设备可以撤销该第一BSR和该第二BSR中的一个，例如该终端设备可以撤销(cancel)第一BSR。
这样，对于关联同一numerology的多个BSR，即请求对应于同一numerology的上行传输资源的多个BSR，如果一个MAC PDU已经包含了某个BSR，则撤销已经触发的其他BSR。
这样，终端设备(即MAC实体，MAC entity)在每个调度间隔(即每个TTI)内至多只能发送一个关联同一numerology的BSR。
可选地，如果终端设备有多套MAC entitiy，则每个MAC entity在每个调度间隔(即每个TTI)内至多只能发送一个关联同一numerology的BSR。
可选地，在BSR关联多个numerology的情况下，例如图8所示的长格式BSR，则如果第一BSR关联的多个numerology和第二BSR关联的多个numerology存在交集，即第一BSR关联的多个numerology中的部分或全部numerology与第二BSR关联的numerology属性相同，则可以认为该第一BSR和该第二BSR关联相同的numerology，但本申请不限于此。
在本申请中，终端设备可以通过多种方式确定BSR关联的numerology属性。可选地，可以配置LCG对应的numerology属性，相应地，终端设备可以根据BSR对应的LCG所对应的numerology属性，确定该BSR关联的numerology属性，其中，BSR对应的LCG可以根据BSR中包含的LCG相关信息确定。对于短格式BSR，该BSR中包含的LCG相关信息可以具体为BSR中包含的LCG标识，对于长格式BSR，该BSR中包含的LCG相关信息可以具体为BSR上报的Buffer Size所在字段，但本申请不限于此。
可选地，也可以直接设置LCH所属的LCG，例如网络设备预先配置或者预先定义。此时，LCG的numerology属性可以依赖于其上报的LCH的numerology。可选地，当该LCG的BSR上报多个LCH的待发送数据量时，即该LCG对应的Buffer Size为多个LCH的待发送数据量之和，则该LCG的numerology属性可以依赖于其上报的LCH中具有最高优先级的LCH的numerology。例如，BSR中与LCG 1对应的Buffer Size包含LCH 1和LCH 2的待发送数据量，如表5所示的例子，第三列的数值越小，对应的优先级越高， 则LCH 1的优先级高于LCH 2的优先级。LCG 1对应的TTI长度可以等于LCH的maximum TTI duration，即4ms，但本申请不限于此。
表5 LCH的配置示例
逻辑信道LCH maximum TTI duration(ms) 优先级
LCH 1 4 1
LCH 2 2 2
LCH 3 1 3
此时，可选地，终端设备可以在BSR中上报该LCG对应的numerology属性，以使得网络设备根据该BSR中上报的numerology属性分配资源。例如，可以在BSR中新增字段，以包含LCG 1对应的TTI长度，但本申请不限于此。
在本申请中，该终端设备可以通过多种方法从触发的关联同一numerology的多个BSR中选择发送的BSR。可选地，该终端设备可以随机选择发送的BSR。或者，该终端设备可以根据该多个BSR对应的LCG中包含的LCH的优先级选择，例如，终端设备可以选择高优先级LCH对应的LCG的BSR进行发送。可选地，如果该多个BSR为长格式BSR，并且该多个BSR关联的numerology属性之间存在交集，则可以从多个BSR中选择该相同的numerology上报的LCH中具有最高优先级的LCH所对应的BSR进行发送。如表6和表7所示的例子，BSR 1和BSR 2均包含LCG 3的Buffer Size，假设BSR 1中的LCG 3的Buffer Size为LCH 3的待发送数据量，BSR 2中的LCG 3的Buffer Size为LCH 1的待发送数据量，根据表5可以得出LCH 1的优先级高于LCH 3的优先级，则终端设备可以选择BSR 2进行发送，但本申请不限于此。
表6 BSR 1
逻辑信道组 Buffer size
LCG 1 X1
LCG 3 X2
LCG 4 X3
表7 BSR 2
逻辑信道组 Buffer size
LCG 2 X4
LCG 3 X2
LCG 5 X5
可选的，如果一个调度间隔支持发送多个MAC PDU，则每个MAC PDU可以包含一个关联不同numerology的BSR。也就是说，多个MAC PDU可以包含多个BSR，并且该 多个BSR中任意两个BSR关联不同的numerology，但本申请不限于此。
可选地，如果终端设备同时触发了多个关联不同numerology的BSR，则这些BSR都可以进行发送，以便网络设备可以分配对应numerology的资源。
这样，如果一个调度间隔(即当前调度间隔)支持传输多个MAC PDU，并且第三BSR和该第二BSR请求对应不同的numerology的上行传输资源，则该终端设备可以在该调度间隔中同时发送该第二BSR和该第三BSR。例如，该终端设备可以在该调度间隔中的第一MAC PDU中包含该第二BSR，并在该调度间隔中的第二MAC PDU中包含第三BSR，但本申请不限于此。
因此，本申请提供的用于传输缓存状态报告的方法，当终端设备同时触发多个BSR时，通过根据触发的多个BSR所关联的numerology属性，确定发送的BSR，有利于提高数据传输性能，满足不同业务需求。
本申请还提供了一种选择上行传输资源的方法，在该方法中，终端设备可以根据BSR关联的numerology属性，确定与该BSR匹配的上行传输资源。
图13示出了本申请提供的另一种用于传输缓存状态报告的方法600。
S610，终端设备确定与BSR匹配的上行传输资源，其中，该BSR包含属于该LCG的至少一个LCH的待发送数据量。
可选地，可以根据BSR关联的numerology属性，确定该BSR匹配的上行传输资源。
可选地，可以根据BSR包括的LCG对应的numerology属性要求，确定该BSR匹配的上行传输资源。
可选地，BSR关联的numerology属性可以根据该BSR包括的LCG所对应的numerology属性要求来确定。
可选地，与该BSR匹配的上行传输资源可以是对应的numerology与该LCG的numerology属性匹配的上行传输资源。
作为一个可选例子，终端设备可以将最低限度地满足该LCG对应的numerology属性要求的上行传输资源确定为与该BSR匹配的上行传输资源。
LCG的numerology属性要求可以用于确定与BSR匹配的上行传输资源。可选地，LCG对应的numerology属性要求可以具体为上述实施例中的LCG对应的numerology属性。或者，也可以依赖于该BSR中包含的该LCG的Buffer Size对应的LCH的numerology属性要求，例如，若该BSR包含属于该LCG的至少一个LCH的待发送数据量，该终端设备可以将该至少一个LCH中具有最高优先级的LCH的numerology属性要求确定为该LCG的numerology属性要求，但本申请不限于此。或者，LCG对应的numerology属性要求也可以是额外定义的参数，具体可以由网络设备预先配置或者预先定义，例如终端设备可以接收网络设备发送的第四指示信息，该第四指示信息可以用于指示该LCG对应的numerology属性要求，本申请不限于此。
作为一个可选例子，LCG对应的numerology属性要求可以具体为物理传输参数的值等于某个选择门限，即LCG对应的numerology属性要求可以具体为上文所述的LCG对应的numerology属性。此时，可以将对应的numerology属性与LCG对应的numerology属性相同的上行传输资源确定为与BSR匹配的上行传输资源，作为一个可选例子，可以将对应的第一物理传输参数(例如TTI长度)的值等于LCG对应的第一物理传输参数的 值的上行传输资源确定为LCG的BSR匹配的上行传输资源。例如，终端设备当前可用的上行传输资源如表8所示，其中UL Grant 1分配的上行传输资源对应的TTI长度为4ms，UL Grant 2分配的上行传输资源对应的TTI长度为2ms。LCG对应的TTI长度如表9所示，通过比较表8和表9的前两列，可以确定LCG 1的BSR匹配的上行传输资源为UL Grant1分配的上行传输资源，由于当前可用的上行传输资源中不存在TTI长度等于1的传输资源，LCG 2的BSR无匹配的上行传输资源，LCG 3的BSR匹配的上行传输资源为UL Grant2分配的上行传输资源，但本申请不限于此。
表8 UL Grant分配的上行传输资源对应的numerology属性
可用的上行传输资源 numerology属性/TTI duration(ms)
UL Grant 1 4
UL Grant 2 2
表9 LCG对应的numerology属性要求以及选择的上行传输资源
逻辑信道组 LCG要求/TTI duration(ms) 匹配的上行传输资源
LCG 1 4 UL Grant 1
LCG 2 1 无资源可用
LCG 3 2 UL Grant 2
作为另一个可选例子，可以将最低限度地满足LCG对应的numerology属性要求的上行传输资源确定为该LCG的BSR匹配的上行传输资源。LCG对应的numerology属性要求可以包括：小于或等于LCG对应的最大TTI长度，或者大于或等于LCG对应的最小SCS，最低限度地满足的含义可以参见上文实施例的描述，为了简洁，这里不再赘述。例如，LCG对应的numerology属性要求可以如表10所示，此时，由于当前可用的上行传输资源中不存在对应的TTI长度小于或等于1的传输资源，LCG 2的BSR无可用资源。
表10 LCG对应的numerology属性要求以及选择的上行传输资源
Figure PCTCN2018085189-appb-000005
可选地，若根据numerology属性找不到与BSR匹配的可用上行传输资源，可以不发送该BSR，这样可能会引入传输时延。作为另一个可选实施例，在本申请中，可以不约束BSR传输时使用的上行传输资源的numerology属性，即BSR可在任意numerology属性的上行传输资源传输，此时，BSR匹配的上行传输资源的选择可以不依赖于上行传输资源的 numerology属性，例如，BSR匹配的上行传输资源是可以任意选择的。例如，虽然LCG对应TTI duration为2ms，但当UL grant分配的是具有1ms的TTI duration的资源时，该LCG的BSR可以在该资源上发送，但本发明实施例不限于此。
S620，终端设备在该匹配的上行传输资源上发送该BSR。
S630，网络设备接收该BSR，并可选地为终端设备分配上行传输资源。
可选地，该网络设备可以根据该BSR占用的上行传输资源对应的numerology属性，为终端设备分配上行传输资源。例如，该网络设备可以分配对应的numerology与该BSR占用的而上行传输资源相同的资源。此时，可选地，该BSR可以不包含Buffer Size对应的LCG的信息。
可选地，该BSR可以确定该BSR中包含的Buffer Size对应的LCG，并根据该LCG对应的numerology属性要求或者该LCG对应的numerology属性，为终端设备分配上行传输资源，本申请对此不做限定。
因此，本申请提供的用于传输缓存状态报告的方法，通过确定与BSR匹配的上行传输资源，并在与该BSR匹配的上行传输资源上传输该BSR，有利于提高***性能。
本申请还提供了一种传输调度请求(Scheduling Request，SR)的方法。在该方法中，如果终端设备发送了BSR，发现用于传输SR的可用资源，并且SR能够先于BSR被接收，则终端设备可以发送SR，以使得网络设备尽早地收到终端设备的请求，有利于网络设备更早地进行资源调度并且终端设备更早地进行数据传输。
具体地，终端设备可以向网络设备发送BSR，若该BSR对应的BSR重传定时器未超时，并且终端设备发现用于传输SR的可用的上行传输资源，其中，该可用的上行传输资源的结束时刻早于该BSR占用的上行传输资源的结束时刻，则该终端设备可以在该可用的上行传输资源上向该网络设备发送SR。相应地，网络设备可以接收终端设备发送的SR，并根据该SR，为终端设备分配传输资源。
作为一个例子，如图14所示，numerology 1对应的slot长度为0.5ms，numerology 2对应的slot长度为0.125ms。在t0时刻，终端设备在对应于numerology 1的上行传输资源上发送了BSR，根据numerology 1对应的slot长度，该BSR可以于t0+0.5ms被网络设备接收完毕。在发送该BSR之后，终端设备发现了可用于传输SR的对应于numerology的上行传输资源，该上行传输资源的起始时刻为t0+0.125ms。如果该终端设备在t0+0.125ms发送SR，根据numerology 2对应的slot长度，该SR可以在t0+0.25ms被网络设备接收完毕，即该SR可以先于该BSR被网络设备接收到。此时，该终端设备可以在t0+0.125ms向网络设备发送SR，但本发明实施例不限于此。
在本申请中，在收到SR后，网络设备可能会收到关联同一numerology的BSR，此时，可选地，如果该SR和BSR之间的时间间隔小于某个预设时间段，则该网络设备可以舍弃该BSR，不对该BSR进行响应。这样，该网络设备可以在该预设时间段内仅响应终端设备发送的针对同一numerology的一次资源分配请求。可选地，该预设时间段可以为该numerology对应的BSR重传定时器的时长，或者也可以为SR发送周期，本申请对此不做限定。
应理解，本申请中的第一指示信息、第二指示信息、第三指示信息和第四指示信息中的任意两个指示信息可以同时发送或者分别发送，本发明实施例对此不做限定。
还应理解，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请的实施过程构成任何限定。
还应理解，上文给出的例子是为了帮助本领域技术人员更好地理解本申请，而非要限制本申请的范围。本领域技术人员根据所给出的上述示例，显然可以进行各种等价的修改或变化，这样的修改或变化也落入本申请的范围内。
图15示出了本申请提供的无线通信***以及用于传输BSR的装置。无线通信***10包括：用于传输BSR的装置700和用于传输BSR的装置800。其中，可选地，装置700可以为图4实施例中的终端设备200，装置800可以为图5实施例中的网络设备300，无线通信***10可以是图1描述的无线通信***100，但本发明实施例不限于此。
如图15所示，装置700可以包括处理单元710和通信单元720。
作为一个例子，处理单元710用于根据至少一个逻辑信道组中每个逻辑信道组对应的参数集numerology属性，确定第一逻辑信道所属的目标逻辑信道组，其中，该第一逻辑信道支持至少一个numerology，每个numerology包括至少一个物理传输参数。通信单元720用于向网络设备发送缓存状态报告，该缓存状态报告包含属于该目标逻辑信道组的至少一个逻辑信道的待发送数据量，该至少一个逻辑信道包括该第一逻辑信道。
作为另一个例子，处理单元710用于从该第一逻辑信道支持的至少一个参数集numerology中确定目标numerology，其中，该至少一个numerology中的每个numerology包括至少一个物理传输参数。通信单元720用于向网络设备发送缓存状态报告，该缓存状态报告包括该目标numerology对应的至少一个逻辑信道的待发送数据量，其中，该至少一个逻辑信道包括该第一逻辑信道。
装置800可以包括处理单元810和通信单元820。
作为一个例子，处理单元810用于确定至少一个逻辑信道组中每个逻辑信道组对应的参数集numerology属性。通信单元820用于向终端设备发送第一指示信息，该第一指示信息用于指示该至少一个逻辑信道组中每个逻辑信道组对应的numerology属性。
作为另一个例子，处理单元810用于确定第一逻辑信道对应的参数集numerology属性要求；
通信单元820用于向终端设备发送第二指示信息，该第二指示信息用于指示该第一逻辑信道对应的numerology属性要求，该第一逻辑信道的numerology属性要求用于该终端设备从该第一逻辑信道支持的至少一个参数集numerology中确定目标numerology，该至少一个numerology中的每个numerology包括至少一个物理传输参数。
应理解，这里的装置700和装置800以功能单元的形式体现。在一个可选例子中，本领域技术人员可以理解，装置700可以具体为上述方法实施例中的终端设备，装置700可以用于执行上述方法实施例中与终端设备对应的各个流程和/或步骤，装置800可以具体为上述方法实施例中的网络设备，装置800可以用于执行上述方法实施例中与网络设备对应的各个流程和/或步骤，为避免重复，在此不再赘述。
还应理解，在本申请中，术语“单元”可以指应用特有集成电路(Application Specific Integrated Circuit，ASIC)、电子电路、用于执行一个或多个软件或固件程序的处理器(例如共享处理器、专有处理器或组处理器等)和存储器、合并逻辑电路和/或其它支持所描述的功能的合适组件。
图16为本申请提供的一种装置的结构示意图。如图16所示，装置90可包括：处理器901以及耦合于处理器901的一个或多个接口902。其中：
处理器901可用于读取和执行计算机可读指令。具体实现中，处理器901可主要包括控制器、运算器和寄存器。其中，控制器主要负责指令译码，并为指令对应的操作发出控制信号。运算器主要负责执行定点或浮点算数运算操作、移位操作以及逻辑操作等，也可以执行地址运算和转换。寄存器主要负责保存指令执行过程中临时存放的寄存器操作数和中间操作结果等。具体实现中，处理器901的硬件架构可以是专用集成电路(Application Specific Integrated Circuits,ASIC)架构、MIPS架构、ARM架构或者NP架构等等。处理器901可以是单核的，也可以是多核的。
接口902可用于输入待处理的数据至处理器901，并且可以向外输出处理器901的处理结果。具体实现中，接口902可以是通用输入输出(General Purpose Input Output，GPIO)接口，可以和多个***设备(如显示器(LCD)、摄像头、射频模块等等)连接。接口902还可以包括多个独立的接口，例如以太网接口、LCD接口、Camera接口等，分别负责不同***设备和处理器901之间的通信。
本申请中，处理器901可用于从存储器中调用本申请的一个或多个实施例提供的资源分配方法在终端侧的实现程序，并执行该程序包含的指令。接口902可用于输出处理器901的执行结果。本申请中，接口902可具体用于输出处理器901的资源分配结果。关于本申请的一个或多个实施例提供的资源分配方法可参考前述各个实施例，这里不再赘述。
需要说明的，处理器901、接口902各自对应的功能既可以通过硬件设计实现，也可以通过软件设计来实现，还可以通过软硬件结合的方式来实现，这里不作限制。
应理解，在本申请中，该处理器可以是中央处理单元(Central Processing Unit，CPU)，该处理器还可以是其他通用处理器、数字上行信号处理器(DSP)、专用集成电路(ASIC)、现成可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
存储器可以包括只读存储器和随机存取存储器，并向处理器提供指令和数据。存储器的一部分还可以包括非易失性随机存取存储器。例如，存储器还可以存储设备类型的信息。该处理器可以用于执行存储器中存储的指令，并且该处理器执行该指令时，该处理器可以执行上述方法实施例中与终端设备对应的各个步骤。
在实现过程中，上述方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器执行存储器中的指令，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。
应理解，上文的描述着重于强调各个实施例之间的不同之处，未提到的相同或相似之处可以互相参考，为了简洁，这里不再赘述。
此外，本文中术语“***”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表 示前后关联对象是一种“或”的关系。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的***、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的***、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个***，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本发明各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (28)

  1. 一种用于传输缓存状态报告的方法，其特征在于，包括：
    终端设备根据至少一个逻辑信道组中每个逻辑信道组对应的参数集numerology属性，确定第一逻辑信道所属的目标逻辑信道组，其中，所述第一逻辑信道支持至少一个numerology，每个numerology包括至少一个物理传输参数；
    所述终端设备向网络设备发送缓存状态报告，所述缓存状态报告包含属于所述目标逻辑信道组的至少一个逻辑信道的待发送数据量，所述至少一个逻辑信道包括所述第一逻辑信道。
  2. 根据权利要求1所述的方法，其特征在于，所述终端设备根据至少一个逻辑信道组中每个逻辑信道组对应的numerology属性，确定第一逻辑信道所属的目标逻辑信道组，包括：
    所述终端设备确定所述第一逻辑信道的numerology属性要求；
    所述终端设备根据所述第一逻辑信道的numerology属性要求以及所述至少一个逻辑信道组中每个逻辑信道组对应的numerology属性，确定所述目标逻辑信道组。
  3. 根据权利要求2所述的方法，其特征在于，所述终端设备根据所述第一逻辑信道的numerology属性要求以及所述至少一个逻辑信道组中每个逻辑信道组对应的numerology属性，确定所述目标逻辑信道组，包括：
    所述终端设备将所述至少一个逻辑信道组中最低限度地满足所述第一逻辑信道的numerology属性要求的逻辑信道组确定为所述目标逻辑信道组。
  4. 根据权利要求2或3所述的方法，其特征在于，所述第一逻辑信道的numerology属性要求包括：第一物理传输参数的值等于预设阈值，所述至少一个逻辑信道组中每个逻辑信道组对应的numerology属性包括：所述每个逻辑信道组对应的所述第一物理传输参数的值；
    所述终端设备根据所述第一逻辑信道的numerology属性要求以及所述至少一个逻辑信道组中每个逻辑信道组对应的numerology属性，确定所述目标逻辑信道组，包括：
    所述终端设备将所述至少一个逻辑信道组中对应的所述第一物理传输参数的值等于所述预设阈值的逻辑信道组确定为所述目标逻辑信道组。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，在所述终端设备根据至少一个逻辑信道组中每个逻辑信道组对应的numerology属性，确定第一逻辑信道所属的目标逻辑信道组之前，所述方法还包括：
    所述终端设备从所述网络设备接收第一指示信息，所述第一指示信息指示所述至少一个逻辑信道组中每个逻辑信道组对应的numerology属性。
  6. 一种用于传输缓存状态报告的方法，其特征在于，包括：
    终端设备从所述第一逻辑信道支持的至少一个参数集numerology中确定目标numerology，其中，所述至少一个numerology中的每个numerology包括至少一个物理传输参数；
    所述终端设备向网络设备发送缓存状态报告，所述缓存状态报告包括所述目标 numerology对应的至少一个逻辑信道的待发送数据量，其中，所述至少一个逻辑信道包括所述第一逻辑信道。
  7. 根据权利要求6所述的方法，其特征在于，所述终端设备从所述第一逻辑信道支持的至少一个numerology中确定目标numerology，包括：
    所述终端设备根据第一逻辑信道的numerology属性要求，从所述第一逻辑信道支持的至少一个numerology中确定目标numerology。
  8. 根据权利要求7所述的方法，其特征在于，所述终端设备根据第一逻辑信道的numerology属性要求，从所述第一逻辑信道支持的至少一个numerology中确定目标numerology，包括：
    所述终端设备将所述至少一个numerology中最低限度地满足所述第一逻辑信道的numerology属性要求的numerology确定为所述目标numerology。
  9. 根据权利要求7或8所述的方法，其特征在于，所述第一逻辑信道的numerology属性要求包括：第一物理传输参数的值等于预设阈值，所述至少一个numerology中的每个numerology包括所述第一物理传输参数的值；
    所述终端设备根据第一逻辑信道的numerology属性要求，从所述第一逻辑信道支持的至少一个numerology中确定目标numerology，包括：
    所述终端设备将所述至少一个numerology中包括的所述第一物理传输参数的值等于所述预设阈值的numerology确定为所述目标numerology。
  10. 根据权利要求6至9中任一项所述的方法，其特征在于，所述缓存状态报告包括：numerology标识字段和缓存大小字段，其中，所述numerology标识字段用于承载所述目标numerology的编号，所述缓存大小字段用于承载所述目标numerology对应的至少一个逻辑信道的待发送数据量。
  11. 一种用于传输缓存状态报告的方法，其特征在于，包括：
    网络设备确定至少一个逻辑信道组中每个逻辑信道组对应的参数集numerology属性；
    所述网络设备向终端设备发送第一指示信息，所述第一指示信息用于指示所述至少一个逻辑信道组中每个逻辑信道组对应的numerology属性。
  12. 根据权利要求11所述的方法，其特征在于，所述方法还包括：
    所述网络设备从所述终端设备接收缓存状态报告，所述缓存状态报告包含属于第一逻辑信道组的至少一个逻辑信道的待发送数据量；
    所述网络设备根据所述第一逻辑信道组对应的numerology属性，为所述终端设备分配上行传输资源。
  13. 一种用于传输缓存状态报告的方法，其特征在于，包括：
    网络设备确定第一逻辑信道对应的参数集numerology属性要求；
    所述网络设备向终端设备发送第二指示信息，所述第二指示信息用于指示所述第一逻辑信道对应的numerology属性要求，所述第一逻辑信道的numerology属性要求用于所述终端设备从所述第一逻辑信道支持的至少一个参数集numerology中确定目标numerology，所述至少一个numerology中的每个numerology包括至少一个物理传输参数。
  14. 根据权利要求13所述的方法，其特征在于，所述方法还包括：
    所述网络设备从所述终端设备接收缓存状态报告，所述缓存状态报告包含所述目标参 数集numerology对应的至少一个逻辑信道的待发送数据量，其中，所述至少一个逻辑信道包括所述第一逻辑信道；
    所述网络设备根据所述目标numerology包括的至少一个物理传输参数的值，为所述终端设备分配上行传输资源。
  15. 一种用于传输缓存状态报告的装置，其特征在于，包括：
    处理单元，用于根据至少一个逻辑信道组中每个逻辑信道组对应的参数集numerology属性，确定第一逻辑信道所属的目标逻辑信道组，其中，所述第一逻辑信道支持至少一个numerology，每个numerology包括至少一个物理传输参数；
    通信单元，用于向网络设备发送缓存状态报告，所述缓存状态报告包含属于所述目标逻辑信道组的至少一个逻辑信道的待发送数据量，所述至少一个逻辑信道包括所述第一逻辑信道。
  16. 根据权利要求15所述的装置，其特征在于，所述处理单元具体用于：
    确定所述第一逻辑信道的numerology属性要求；
    根据所述第一逻辑信道的numerology属性要求以及所述至少一个逻辑信道组中每个逻辑信道组对应的numerology属性，确定所述目标逻辑信道组。
  17. 根据权利要求16所述的装置，其特征在于，所述处理单元具体用于：
    将所述至少一个逻辑信道组中最低限度地满足所述第一逻辑信道的numerology属性要求的逻辑信道组确定为所述目标逻辑信道组。
  18. 根据权利要求16或17所述的装置，其特征在于，所述第一逻辑信道的numerology属性要求包括：第一物理传输参数的值等于预设阈值，所述至少一个逻辑信道组中每个逻辑信道组对应的numerology属性包括：所述每个逻辑信道组对应的所述第一物理传输参数的值；
    所述处理单元具体用于：将所述至少一个逻辑信道组中对应的所述第一物理传输参数的值等于所述预设阈值的逻辑信道组确定为所述目标逻辑信道组。
  19. 根据权利要求15至18中任一项所述的装置，其特征在于，所述通信单元还用于：在所述处理单元根据至少一个逻辑信道组中每个逻辑信道组对应的numerology属性，确定第一逻辑信道所属的目标逻辑信道组之前，从所述网络设备接收第一指示信息，所述第一指示信息指示所述至少一个逻辑信道组中每个逻辑信道组对应的numerology属性。
  20. 一种用于传输缓存状态报告的装置，其特征在于，包括：
    处理单元，用于从所述第一逻辑信道支持的至少一个参数集numerology中确定目标numerology，其中，所述至少一个numerology中的每个numerology包括至少一个物理传输参数；
    通信单元，用于向网络设备发送缓存状态报告，所述缓存状态报告包括所述目标numerology对应的至少一个逻辑信道的待发送数据量，其中，所述至少一个逻辑信道包括所述第一逻辑信道。
  21. 根据权利要求20所述的装置，其特征在于，所述处理单元具体用于：根据第一逻辑信道的numerology属性要求，从所述第一逻辑信道支持的至少一个numerology中确定目标numerology。
  22. 根据权利要求21所述的装置，其特征在于，所述处理单元具体用于：
    将所述至少一个numerology中最低限度地满足所述第一逻辑信道的numerology属性要求的numerology确定为所述目标numerology。
  23. 根据权利要求21或22所述的装置，其特征在于，所述第一逻辑信道的numerology属性要求包括：第一物理传输参数的值等于预设阈值，所述至少一个numerology中的每个numerology包括所述第一物理传输参数的值；
    所述处理单元具体用于：
    将所述至少一个numerology中包括的所述第一物理传输参数的值等于所述预设阈值的numerology确定为所述目标numerology。
  24. 根据权利要求20至23中任一项所述的装置，其特征在于，所述缓存状态报告包括：numerology标识字段和缓存大小字段，其中，所述numerology标识字段用于承载所述目标numerology的编号，所述缓存大小字段用于承载所述目标numerology对应的至少一个逻辑信道的待发送数据量。
  25. 一种用于传输缓存状态报告的装置，其特征在于，包括：
    处理单元，用于确定至少一个逻辑信道组中每个逻辑信道组对应的参数集numerology属性；
    通信单元，用于向终端设备发送第一指示信息，所述第一指示信息用于指示所述至少一个逻辑信道组中每个逻辑信道组对应的numerology属性。
  26. 根据权利要求25所述的装置，其特征在于，所述通信单元还用于从所述终端设备接收缓存状态报告，所述缓存状态报告包含属于第一逻辑信道组的至少一个逻辑信道的待发送数据量；
    所述处理单元还用于根据所述第一逻辑信道组对应的numerology属性，为所述终端设备分配上行传输资源。
  27. 一种用于传输缓存状态报告的装置，其特征在于，包括：
    处理单元，用于确定第一逻辑信道对应的参数集numerology属性要求；
    通信单元，用于向终端设备发送第二指示信息，所述第二指示信息用于指示所述第一逻辑信道对应的numerology属性要求，所述第一逻辑信道的numerology属性要求用于所述终端设备从所述第一逻辑信道支持的至少一个参数集numerology中确定目标numerology，所述至少一个numerology中的每个numerology包括至少一个物理传输参数。
  28. 根据权利要求27所述的装置，其特征在于，所述通信单元还用于从所述终端设备接收缓存状态报告，所述缓存状态报告包含所述目标参数集numerology对应的至少一个逻辑信道的待发送数据量，其中，所述至少一个逻辑信道包括所述第一逻辑信道；
    所述处理单元还用于根据所述目标numerology包括的至少一个物理传输参数的值，为所述终端设备分配上行传输资源。
PCT/CN2018/085189 2017-05-05 2018-04-28 用于传输缓存状态报告的方法和装置 WO2018202022A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710314142.9 2017-05-05
CN201710314142.9A CN108810975B (zh) 2017-05-05 2017-05-05 用于传输缓存状态报告的方法和装置

Publications (1)

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

Family

ID=64016412

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/085189 WO2018202022A1 (zh) 2017-05-05 2018-04-28 用于传输缓存状态报告的方法和装置

Country Status (2)

Country Link
CN (1) CN108810975B (zh)
WO (1) WO2018202022A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020199004A1 (zh) * 2019-03-29 2020-10-08 Oppo广东移动通信有限公司 通信方法和终端设备
JP2022537898A (ja) * 2019-05-29 2022-08-31 オッポ広東移動通信有限公司 情報伝送方法及び端末機器
EP4154652A4 (en) * 2020-05-21 2024-01-17 Nokia Technologies Oy PLANNING REQUIREMENTS MANAGEMENT
CN116939855A (zh) * 2022-04-08 2023-10-24 华为技术有限公司 一种通信方法和通信装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009096847A1 (en) * 2008-01-30 2009-08-06 Telefonaktiebolaget L M Ericsson (Publ) Method and arrangement in a telecommunication system
US20100232376A1 (en) * 2009-03-16 2010-09-16 Chih-Hsiang Wu Method and related communication device for radio link control reconfiguration in a wireless communications system
CN102291760A (zh) * 2010-06-21 2011-12-21 电信科学技术研究院 一种上报和确认缓存状态信息的方法、***及设备
CN102595599A (zh) * 2011-01-17 2012-07-18 华为技术有限公司 长期演进***中演进基站进行调度的方法、基站及***
CN104219738A (zh) * 2013-05-29 2014-12-17 华为技术有限公司 非连续接收参数配置方法及装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2079202A1 (en) * 2008-01-08 2009-07-15 NEC Corporation Method for optimizing the triggering of the transmission of buffer status reporting (BSR) information
CN106535246B (zh) * 2015-09-11 2021-03-16 中兴通讯股份有限公司 一种缓冲区状态报告的上报方法、装置及***

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009096847A1 (en) * 2008-01-30 2009-08-06 Telefonaktiebolaget L M Ericsson (Publ) Method and arrangement in a telecommunication system
US20100232376A1 (en) * 2009-03-16 2010-09-16 Chih-Hsiang Wu Method and related communication device for radio link control reconfiguration in a wireless communications system
CN102291760A (zh) * 2010-06-21 2011-12-21 电信科学技术研究院 一种上报和确认缓存状态信息的方法、***及设备
CN102595599A (zh) * 2011-01-17 2012-07-18 华为技术有限公司 长期演进***中演进基站进行调度的方法、基站及***
CN104219738A (zh) * 2013-05-29 2014-12-17 华为技术有限公司 非连续接收参数配置方法及装置

Also Published As

Publication number Publication date
CN108810975A (zh) 2018-11-13
CN108810975B (zh) 2020-09-08

Similar Documents

Publication Publication Date Title
WO2020088688A1 (zh) 资源配置方法及装置
US10075378B2 (en) Electronic apparatus, a central node apparatus and a network side apparatus, a transmission method and a configuration method
WO2018202022A1 (zh) 用于传输缓存状态报告的方法和装置
US11968682B2 (en) Uplink dynamic grant-free transmission method and apparatus
WO2020221093A1 (zh) 搜索空间的监测、配置方法及装置
US11317425B2 (en) Data transmission method, related device, and system
WO2020094025A1 (zh) 一种上行控制信息的传输方法及装置
EP3595383B1 (en) Resource mapping method, network device and terminal device
WO2018228537A1 (zh) 信息发送、接收方法及装置
WO2020259254A1 (zh) 搜索空间的监测方法及装置
US11405961B2 (en) Wireless communication method and apparatus
WO2020143490A1 (zh) 通信方法及装置
US20190124705A1 (en) Identifier management method, apparatus, and system
WO2019158039A1 (zh) 通信方法和通信装置
WO2023097810A1 (zh) 无线通信方法、终端和网络设备
EP4152815A1 (en) Communication method and communication device
TW202019214A (zh) Pdcch的監聽方法、裝置、設備及系統
JP2018537907A (ja) スケジューリング情報送信方法および装置
WO2024082813A1 (zh) Harq进程的分配方法、装置、基站及存储介质
WO2018170877A1 (zh) 信息发送方法、装置、终端、接入网设备及***
WO2017205999A1 (zh) 一种数据传输的方法、设备和***
CN116156653A (zh) 一种通信方法及通信装置
WO2020094080A1 (zh) 数据接收和发送的方法、设备及***
WO2021134447A1 (zh) 一种通信方法及装置
WO2024067186A1 (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: 18794810

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18794810

Country of ref document: EP

Kind code of ref document: A1