WO2022083726A1 - 触发边链路pre-emptive缓存状态报告方法、中继设备及介质 - Google Patents

触发边链路pre-emptive缓存状态报告方法、中继设备及介质 Download PDF

Info

Publication number
WO2022083726A1
WO2022083726A1 PCT/CN2021/125586 CN2021125586W WO2022083726A1 WO 2022083726 A1 WO2022083726 A1 WO 2022083726A1 CN 2021125586 W CN2021125586 W CN 2021125586W WO 2022083726 A1 WO2022083726 A1 WO 2022083726A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
emptive
side link
status report
control information
Prior art date
Application number
PCT/CN2021/125586
Other languages
English (en)
French (fr)
Inventor
刘星
Original Assignee
展讯通信（上海）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 展讯通信（上海）有限公司 filed Critical 展讯通信（上海）有限公司
Priority to EP21882140.3A priority Critical patent/EP4236442A4/en
Priority to US18/032,989 priority patent/US20230397229A1/en
Publication of WO2022083726A1 publication Critical patent/WO2022083726A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/25—Control channels or signalling for resource management between terminals via a wireless link, e.g. sidelink
    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1854—Scheduling and prioritising arrangements
    • 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/0205—Traffic management, e.g. flow control or congestion control at the air interface
    • 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/04—Error control
    • 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/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H04W72/566—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient
    • H04W72/569—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient of the traffic information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/04—Terminal devices adapted for relaying to or from another terminal or user

Definitions

  • the present invention relates to the technical field of wireless communication, and in particular, to a method, a relay device and a medium for triggering a side link pre-emptive buffer status report.
  • the thing-thing-direct connection communication technology or the side link communication technology is different from the traditional wireless cellular network communication.
  • a traditional cellular network user equipment communicates with base station equipment.
  • the link between user equipment and base station equipment is called uplink (Uplink, UL) or downlink (Downlink, DL), and the interface is It is called the Uu interface
  • the user equipment communicates directly with the user equipment, the link between the user equipment and the user equipment is called a sidelink (SL), and the interface is called PC5 interface.
  • IAB Integrated Access Backhaul
  • the uplink resources of the user equipment are also allocated by the IAB node, and the uplink resources of the IAB node are allocated by the base station. Therefore, the user equipment needs to send the BSR request resource to the IAB node, and the IAB node needs to send the BSR request resource to the base station, resulting in additional transmission delay.
  • the pre-emptive BSR mechanism is introduced into the IAB architecture.
  • the IAB node receives the BSR from the user equipment, or when allocating uplink transmission resources to the user equipment, it triggers the sending of a pre-emptive BSR to the base station, that is, it tells the base station in advance that although the data has not been received, it is expected How much data will need to be sent so that the base station can schedule resources in advance.
  • BSR indicates the size information of the existing data
  • the pre-emptive BSR indicates the size information of the predicted data to be received.
  • the transmission resources of the user equipment are not allocated by the IAB node, but are grabbed by the user equipment from the shared resource pool through a preemption mechanism. Therefore, the pre-emptive BSR trigger conditions introduced in the existing IAB architecture cannot be applied in the sidelink relay structure.
  • the embodiment of the present invention solves the technical problem that the pre-emptive BSR trigger cannot be used in the side link relay structure.
  • an embodiment of the present invention provides a method for triggering a side link pre-emptive cache status report, including: receiving side link control information and/or data sent by a user equipment; link control information and/or data, to determine whether there is an expectation of receiving data in the future; after determining that there is an expectation of receiving data in the future, trigger a pre-emptive cache status report; wherein, the side link control information is used to indicate the data.
  • the determining whether there is an expectation of receiving data in the future according to the data sent by the user equipment includes: when decoding the data fails, determining that there is an expectation of receiving data in the future; When decoding fails, HARQ NACK is fed back to the user equipment to determine that there is an expectation of receiving data in the future; or, the side link control information also indicates that there are subsequent unsent resources, and it is determined that there is an expectation of receiving data in the future.
  • determining that there is an expectation of receiving data in the future includes: when the decoding of the data fails for the first time, determining that there is an expectation of receiving data in the future.
  • feeding back a HARQ NACK to the user equipment when decoding the data fails, and determining that there is an expectation of receiving data in the future includes: when decoding the data for the first time fails, reporting to the user equipment.
  • the device feeds back a HARQ NACK to determine that there is an expectation of receiving data in the future.
  • triggering a pre-emptive cache status report including any one of the following: obtaining the first priority of the side link control information, and the pre-empty data sent last time. - the second priority of the emptive buffer status report; when the first priority is higher than the second priority, trigger a pre-emptive buffer status report; obtain the first data amount indicated by the side link control information , and the second data volume indicated by the pre-emptive cache status report sent last time; when the first data volume is greater than the second data volume, trigger the pre-emptive cache status report; obtain the third data volume of the data The amount of data, and the second amount of data indicated by the pre-emptive cache status report sent last time; when the third amount of data is greater than the second amount of data, a pre-emptive cache status report is triggered.
  • the method further includes: generating a current pre-emptive cache status report.
  • the generating the current pre-emptive buffer status report includes: if decoding the data fails, the current pre-emptive buffer status report includes the first priority of the side link control information.
  • the generating the current pre-emptive buffer status report includes: if the data decoding fails, feeding back a HARQ NACK to the user equipment, the current pre-emptive buffer status report includes the side link.
  • the first priority of control information is: if the data decoding fails, feeding back a HARQ NACK to the user equipment, the current pre-emptive buffer status report includes the side link. The first priority of control information.
  • the generating a current pre-emptive cache status report includes: if the data is successfully decoded, and the side link control information also indicates that there are subsequent unsent resources, the current pre-emptive cache The status report includes the first priority of the side link control information; or, if the data is successfully decoded and the side link control information also indicates that there are subsequent unsent resources, the current pre-emptive The buffer status report does not include the first priority of the currently received side link control information.
  • the generating the current pre-emptive cache status report includes: the current pre-emptive cache status report includes the first data amount indicated by the side link control information; or, the current pre-emptive cache The status report includes a third amount of the data.
  • an embodiment of the present invention further provides a relay device, including: a receiving unit, configured to receive side link control information and/or data sent by user equipment; The side link control information and/or data sent by the device determines whether there is an expectation of receiving data in the future; the triggering unit is used to trigger a pre-emptive cache status report after determining that there is an expectation of receiving data in the future; wherein, the edge Link control information is used to indicate the data.
  • An embodiment of the present invention further provides a computer-readable storage medium, where the computer-readable storage medium is a non-volatile storage medium or a non-transitory storage medium, on which a computer program is stored, and the computer program is executed by a processor At runtime, any one of the above-mentioned steps of triggering the method for reporting the pre-emptive cache status of the side link is executed.
  • An embodiment of the present invention further provides another relay device, including a memory and a processor, where the memory stores a computer program that can be run on the processor, and the processor executes the above-mentioned computer program when the processor runs the computer program. Any of the steps of the method for triggering the pre-emptive cache status report of the side link.
  • a pre-emptive buffer status report is triggered, so as to trigger the pre-emptive buffer status report in the side link relay.
  • the air interface resources of the relay device can be fully utilized. Reduce the power consumption of relay equipment.
  • the air interface resources of the relay device can also be fully utilized, and the power consumption of the relay device can be reduced.
  • FIG. 1 is a flowchart of a method for triggering a side link pre-emptive cache status report in an embodiment of the present invention
  • FIG. 2 is a schematic structural diagram of a relay device in an embodiment of the present invention.
  • Fig. 3 is a kind of existing IAB structural representation
  • FIG. 5 is a schematic diagram of an existing side link relay structure.
  • FIG. 4 a schematic diagram of an existing conventional relay structure is given.
  • the base station and the relay device communicate through the uplink and downlink, and the relay device and the user equipment communicate through the uplink and downlink.
  • FIG. 5 a schematic diagram of an existing side link relay structure is given. The difference from FIG. 4 is that, in FIG. 5 , the relay device and the user equipment communicate through a side link (SL).
  • SL side link
  • the transmission resources of the user equipment are not allocated by the IAB node (relay device), but are grabbed by the user equipment from the shared resource pool through a preemption mechanism. Therefore, the pre-emptive BSR trigger condition introduced in the existing IAB architecture cannot be used in the side link relay structure. In other words, in the existing side link relay structure, pre-emptive BSR cannot be triggered, resulting in transmission delay.
  • a pre-emptive cache status report is triggered to realize the pre-emptive cache status report in the side link relay. trigger.
  • An embodiment of the present invention provides a triggering method for triggering a pre-emptive cache status report. Referring to FIG. 1 , the following will describe in detail through specific steps.
  • the triggering method for triggering the pre-emptive cache status report provided by the following steps S101 to S103 may be executed by a chip (such as a baseband chip) with a data processing function in the relay device, or by a relay device including It is executed by a chip module of a chip with data processing functions (such as a baseband chip).
  • a chip such as a baseband chip
  • a relay device including It is executed by a chip module of a chip with data processing functions (such as a baseband chip).
  • Step S101 receiving side link control information and/or data sent by a user equipment.
  • the relay device can receive side link control information (Sidelink Control Information, SCI) sent by the user equipment; the relay device can also receive data sent by the user equipment, and the data sent by the user equipment can be uplink data or other data; the relay device can also receive side link control information sent by the user equipment and data sent by the user equipment.
  • SCI Sidelink Control Information
  • the relay device when the relay device receives the side link control information sent by the user equipment and the data sent by the user equipment, the side link control information is used to indicate the data, for example, the side link control information indicates the data The time-frequency resource location, the modulation and coding method used, etc.
  • the relay device can correctly decode the data according to the side link control information.
  • Step S102 according to the side link control information and/or data sent by the user equipment, determine whether there is an expectation of receiving data in the future.
  • the relay device may determine whether there is an expectation to receive data in the future according to the received side link control information and/or data.
  • the expectation of receiving data in the future means that the relay device can expect whether the user equipment will continue to send data in a subsequent period of time.
  • the relay device when the relay device receives the data sent by the user equipment, it can decode the data. If it is detected that the data fails to be decoded, the user equipment will probably re-send the data that failed to be decoded to the relay device. At this time, the relay device can determine that there is an expectation of receiving data in the future.
  • the relay device when the relay device receives data sent by the user equipment, it decodes the data. If it is detected that the data decoding fails, a Hybrid Automatic Repeat request (HARQ) NACK can be fed back to the user equipment. After receiving the HARQ NACK fed back by the relay device, the user equipment will re-send the data that fails to decode to the relay device with a high probability. At this time, the relay device can determine that there is an expectation of receiving data in the future.
  • HARQ Hybrid Automatic Repeat request
  • the relay device when it is detected that the decoding of the data fails for the first time, and the HARQ NACK is fed back to the user equipment, it can be determined that there is an expectation of receiving data in the future. That is to say, if the relay device fails to decode the data, but it is not the first time that the decoding fails, although the relay device may still need to feed back the HARQ NACK to the user equipment, the relay device may determine that there is no expectation of receiving data in the future.
  • the relay device can also determine that there is an expectation of receiving data in the future.
  • the relay device receives the side link control information sent by the user equipment. If the side link control information indicates that there is a reserved resource location for data transmission, at this time, the relay device can determine that there is a reserved resource location for data transmission. The expectation of receiving data in the future.
  • the relay device receives the side link control information and data sent by the user equipment. If the data is successfully decoded and the side link control information indicates that there is a reserved resource location for data transmission, this , the relay device can determine that there is an expectation of receiving data in the future.
  • Step S103 triggering a pre-emptive cache status report after it is determined that there is an expectation of receiving data in the future.
  • the relay device after the relay device determines that there is an expectation of receiving data in the future, it can trigger a pre-emptive buffer status report, generate a pre-emptive buffer status report, and send it to the base station.
  • the relay device receives the side link control information and/or data sent by the user equipment. After determining that there is an expectation of receiving data in the future, the relay device may first obtain the priority corresponding to the currently received side link control information and the priority of the pre-emptive buffer status report sent last time.
  • the priority corresponding to the currently received side link control information is abbreviated as the first priority
  • the priority of the pre-emptive cache status report sent last time is abbreviated as the second priority. priority.
  • the relay device may compare the first priority with the second priority, and if the first priority is higher than the second priority, trigger a pre-emptive cache status report; If it is not higher than the second priority, the pre-emptive cache status report will not be triggered.
  • the air interface resources of the relay device can be fully utilized and the intermediate following the power consumption of the device.
  • the pre-emptive cache status report can also be triggered.
  • frequent triggering of the pre-emptive cache status report will cause the relay device to occupy more air interface resources and consume more power. In practical applications, it can be determined whether to compare the priorities according to specific application requirements.
  • the relay device may acquire the first data indicated by the currently received side link control information amount, and the second amount of data indicated by the pre-emptive buffer status report sent last time. When the first data amount is greater than the second data amount, a pre-emptive cache status report is triggered.
  • the relay device can obtain the third data amount of the currently received data, and the last The second amount of data indicated by the sent pre-emptive cache status report.
  • the relay device may compare the second data amount with the third data amount, and when the third data amount is greater than the second data amount, trigger a pre-emptive cache status report.
  • the air interface resources of the relay device can also be fully utilized to reduce the power consumption of the relay device.
  • a pre-emptive cache status report may also be triggered.
  • frequent triggering of the pre-emptive cache status report will cause the relay device to occupy more air interface resources and consume more power.
  • whether to compare the amount of data can be determined according to specific application requirements.
  • the current pre-emptive cache status report may be generated.
  • the generation of the current pre-emptive cache status report may include the priority of the currently received side link control information information, that is, including the first priority of the currently received side link control information.
  • the generated current pre-emptive buffer status report may include the currently received The priority information of the side link control information, that is, including the first priority of the currently received side link control information.
  • the generated current pre-emptive buffer status report may also include the first priority of the currently received side link control information.
  • the current pre-emptive cache status report generated by the relay device may not include the currently received side link control information. the first priority.
  • the pre-emptive cache status report is triggered by the currently received side link control information also indicating that there are subsequent unsent resources, then in the generated current pre-emptive cache status report, The first priority of the currently received sidelink control information may also be included.
  • the current pre-emptive buffer status report generated by the relay device may also not include the first priority of the currently received side link control information.
  • the first priority may occupy 8 bits, and the values of some or all of the 8 bits are used to represent the first priority.
  • the current pre-emptive buffer status report may also include the first amount of data indicated by the current side link control information.
  • the first amount of data may occupy 8 bits, and the values of some or all of the 8 bits are used to represent the first amount of data.
  • the current pre-emptive cache status report may also include a third data amount of current data.
  • the third data amount may occupy 8 bits, and some or all of the bit values in the 8 bits are used to represent the third data amount.
  • the number of bits occupied by the first data amount may also be greater than 8 bits, for example, 16 bits or more.
  • the number of bits occupied by the third data amount may also be greater than 8 bits, for example, 16 bits or more.
  • the pre-emptive cache status report is triggered, so as to realize the triggering of the pre-emptive cache status report in the side link relay.
  • an embodiment of the present invention further provides a relay device 20, including: a receiving unit 201, a determining unit 202, and a triggering unit 203, wherein:
  • a receiving unit 201 adapted to receive side link control information and/or data sent by the user equipment
  • a determination unit 202 adapted to determine whether there is an expectation of receiving data in the future according to the side link control information and/or data sent by the user equipment;
  • the triggering unit 203 is adapted to trigger a pre-emptive buffer status report after it is determined that there is an expectation of receiving data in the future; wherein, the side link control information is used to indicate the data.
  • each module/unit included in each device and product described in the above embodiments it may be a software module/unit, a hardware module/unit, or a part of a software module/unit, a part of which is a software module/unit. is a hardware module/unit.
  • each module/unit included therein may be implemented by hardware such as circuits, or at least some modules/units may be implemented by a software program.
  • Running on the processor integrated inside the chip the remaining (if any) part of the modules/units can be implemented by hardware such as circuits; for each device and product applied to or integrated in the chip module, the modules/units contained therein can be They are all implemented by hardware such as circuits, and different modules/units can be located in the same component of the chip module (such as chips, circuit modules, etc.) or in different components, or at least some of the modules/units can be implemented by software programs.
  • the software program runs on the processor integrated inside the chip module, and the remaining (if any) part of the modules/units can be implemented by hardware such as circuits; for each device and product applied to or integrated in the terminal, each module contained in it
  • the units/units may all be implemented in hardware such as circuits, and different modules/units may be located in the same component (eg, chip, circuit module, etc.) or in different components in the terminal, or at least some of the modules/units may be implemented in the form of software programs Realization, the software program runs on the processor integrated inside the terminal, and the remaining (if any) part of the modules/units can be implemented in hardware such as circuits.
  • An embodiment of the present invention further provides a computer-readable storage medium, where the computer-readable storage medium is a non-volatile storage medium or a non-transitory storage medium, on which a computer program is stored, and the computer program is executed by a processor At runtime, the steps of the method for triggering a pre-emptive cache status report of a side link provided by any of the foregoing embodiments are executed.
  • An embodiment of the present invention further provides another relay device, including a memory and a processor, where the memory stores a computer program that can be run on the processor, and the processor executes the above-mentioned computer program when the processor runs the computer program.
  • the steps of triggering the method for reporting the pre-emptive buffer status of a side link provided by any one of the embodiments.

Landscapes

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

Abstract

一种触发边链路pre-emptive缓存状态报告方法、中继设备及介质，所述方法包括：接收用户设备发送的边链路控制信息和/或数据；根据所述用户设备发送的边链路控制信息和/或数据，确定是否存在未来接收数据的预期；在确定存在未来接收数据的预期后，触发pre-emptive缓存状态报告。上述方案能够实现在边链路中继结构中使用pre-emptive BSR触发。

Description

触发边链路pre-emptive缓存状态报告方法、中继设备及介质
本申请要求于2020年10月22日提交中国专利局、申请号为202011140334.0、发明名称为“触发边链路pre-emptive缓存状态报告方法、中继设备及介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及无线通信技术领域，尤其涉及一种触发边链路pre-emptive缓存状态报告方法、中继设备及介质。
背景技术
物物直连通信技术或边链路通信技术(Sidelink，SL)与传统无线蜂窝网络通信不同。在传统的蜂窝网络中，用户设备和基站设备进行通信，此时用户设备和基站设备之间的链路被称为上行链路(Uplink，UL)或下行链路(Downlink，DL)，接口被称为Uu接口，而在物物直连通信中，用户设备直接和用户设备进行通信，用户设备和用户设备之间的链路称为直连链路(sidelink，SL)，接口被称为PC5接口。
在LTE和NR中，为了获取上行传输资源，用户设备在满足条件时需要向基站反馈缓存状态报告(BSR)，用于指示具体的待传输数据的数据量。在NR中，还引入了集成接入回传(Integrated Access Backhaul，IAB)技术，其具体架构如图3所示。IAB架构的特点是IAB节点和基站之间、IAB节点和用户设备之间，采用的都是NR Uu(Uu特指基站和用户设备之间直接连接时的接口)的传输机制。IAB节点能够起到中继作用。
由于IAB节点和用户设备之间仍旧采用Uu传输机制，在IAB架构中，用户设备的上行资源也由IAB节点分配，IAB节点的上行资源由基站分配。因此，用户设备需要向IAB节点发送BSR请求资源，而IAB节点需要向基站发送BSR请求资源，导致额外的传输时延。
为了降低传输时延，IAB架构中引入了pre-emptive BSR机制。IAB节点在收到来自用户设备的BSR的时候，或者在向用户设备分配上行传输资源的时候，就触发向基站发送pre-emptive BSR，也就是提前告诉基站，虽然数据还没有收到，但预计将会有多少数据需要发送，以便基站提前调度资源。此处BSR指示的是已经存在的数据的大小信息，而pre-emptive BSR指示的是预测的将要收到的数据的大小信息。
然而，在边链路中继结构中，用户设备的发送资源不是由IAB节点分配的，而是由用户设备通过抢占机制从共享的资源池里面抢来的。因此，现有IAB架构中引入的pre-emptive BSR触发条件无法在sidelink中继结构中应用。
发明内容
本发明实施例解决的是在边链路中继结构中无法使用pre-emptive BSR触发的技术问题。
为解决上述技术问题，本发明实施例提供一种触发边链路pre-emptive缓存状态报告方法，包括：接收用户设备发送的边链路控制信息和/或数据；根据所述用户设备发送的边链路控制信息和/或数据，确定是否存在未来接收数据的预期；在确定存在未来接收数据的预期后，触发pre-emptive缓存状态报告；其中，所述边链路控制信息用于指示所述数据。
可选的，所述根据所述用户设备发送的数据，确定是否存在未来 接收数据的预期，包括：在对所述数据解码失败时，确定存在未来接收数据的预期；或，在对所述数据解码失败时，向所述用户设备反馈HARQ NACK，确定存在未来接收数据的预期；或，在所述边链路控制信息还指示后续存在未发送的资源，确定存在未来接收数据的预期。
可选的，所述在对所述数据解码失败时，确定存在未来接收数据的预期，包括：在对所述数据第一次解码失败时，确定存在未来接收数据的预期。
可选的，所述在对所述数据解码失败时，向所述用户设备反馈HARQ NACK，确定存在未来接收数据的预期，包括：在对所述数据第一次解码失败时，向所述用户设备反馈HARQ NACK，确定存在未来接收数据的预期。
可选的，所述在确定存在未来接收数据的预期后，触发pre-emptive缓存状态报告，包括以下任一种：获取所述边链路控制信息的第一优先级，以及上一次发送的pre-emptive缓存状态报告的第二优先级；当所述第一优先级高于所述第二优先级时，触发pre-emptive缓存状态报告；获取所述边链路控制信息指示的第一数据量，以及上一次发送的pre-emptive缓存状态报告指示的第二数据量；当所述第一数据量大于所述第二数据量时，触发pre-emptive缓存状态报告；获取所述数据的第三数据量，以及上一次发送的pre-emptive缓存状态报告指示的第二数据量；当所述第三数据量大于所述第二数据量时，触发pre-emptive缓存状态报告。
可选的，在触发pre-emptive缓存状态报告之后，还包括：生成当前pre-emptive缓存状态报告。
可选的，所述生成当前pre-emptive缓存状态报告，包括：若对所述数据解码失败，则所述当前pre-emptive缓存状态报告包括所述边链路控制信息的第一优先级。
可选的，所述生成当前pre-emptive缓存状态报告，包括：若对所述数据解码失败，向所述用户设备反馈HARQ NACK，则所述当前pre-emptive缓存状态报告包括所述边链路控制信息的第一优先级。
可选的，所述生成当前pre-emptive缓存状态报告，包括：若对所述数据解码成功，且所述边链路控制信息还指示后续存在未发送的资源，则所述当前pre-emptive缓存状态报告包括所述边链路控制信息的第一优先级；或，若对所述数据解码成功，且所述边链路控制信息还指示后续存在未发送的资源，则所述当前pre-emptive缓存状态报告不包括所述当前接收到的边链路控制信息的第一优先级。
可选的，所述生成当前pre-emptive缓存状态报告，包括：所述当前pre-emptive缓存状态报告包括所述边链路控制信息指示的第一数据量；或，所述当前pre-emptive缓存状态报告包括所述数据的第三数据量。
为解决上述技术问题，本发明实施例还提供了一种中继设备，包括：接收单元，用于接收用户设备发送的边链路控制信息和/或数据；确定单元，用于根据所述用户设备发送的边链路控制信息和/或数据，确定是否存在未来接收数据的预期；触发单元，用于在确定存在未来接收数据的预期后，触发pre-emptive缓存状态报告；其中，所述边链路控制信息用于指示所述数据。
本发明实施例还提供了一种计算机可读存储介质，所述计算机可读存储介质为非易失性存储介质或非瞬态存储介质，其上存储有计算机程序，所述计算机程序被处理器运行时执行上述任一种所述的触发边链路pre-emptive缓存状态报告方法的步骤。
本发明实施例还提供了另一种中继设备，包括存储器和处理器，所述存储器上存储有可在所述处理器上运行的计算机程序，所述处理器运行所述计算机程序时执行上述任一种所述的触发边链路pre-emptive缓存状态报告方法的步骤。
与现有技术相比，本发明实施例的技术方案具有以下有益效果：
在接收到用户设备发送的数据后，若确定存在未来接收数据的预期，则触发pre-emptive缓存状态报告，实现在边链路中继中pre-emptive缓存状态报告的触发。
进一步，通过获取边链路控制信息对应的优先级，并在当前接收到的边链路控制信息的优先级较高时才触发pre-emptive缓存状态报告，可以充分利用中继设备的空口资源，减少中继设备的功耗。
此外，通过比较指示的数据量，在当前需要发送的数量较大时触发pre-emptive缓存状态报告，也可以充分利用中继设备的空口资源，减少中继设备的功耗。
附图说明
图1是本发明实施例中的一种触发边链路pre-emptive缓存状态报告方法的流程图；
图2是本发明实施例中的一种中继设备的结构示意图；
图3是现有的一种IAB结构示意图；
图4是现有的一种传统中继结构示意图；
图5是现有的一种边链路中继结构示意图。
具体实施方式
参照图4，给出了现有的一种传统中继结构示意图。基站与中继设备之间通过上下行链路进行通信，中继设备与用户设备之间通过上下行链路进行通信。而在图5中，则给出了现有的一种边链路中继结构示意图。与图4所不同的是，图5中，中继设备与用户设备之间通过边链路(SL)进行通信。
在边链路中继结构中，用户设备的发送资源不是由IAB节点(中继设备)分配的，而是由用户设备通过抢占机制从共享的资源池里面抢来的。因此，现有IAB架构中引入的pre-emptive BSR触发条件无法在边链路中继结构中使用。换言之，在现有的边链路中继结构中，无法触发pre-emptive BSR，导致传输时延产生。
在本发明实施例中，在接收到用户设备发送的数据后，若确定存在未来接收数据的预期，则触发pre-emptive缓存状态报告，实现在边链路中继中pre-emptive缓存状态报告的触发。
为使本发明的上述目的、特征和有益效果能够更为明显易懂，下面结合附图对本发明的具体实施例做详细的说明。
本发明实施例提供了一种触发pre-emptive缓存状态报告触发方法，参照图1，以下通过具体步骤进行详细说明。
在具体实施中，下述步骤S101～步骤S103所提供的触发pre-emptive缓存状态报告触发方法可以由中继设备中具有数据处理功能的芯片(如基带芯片)执行，或者由中继设备中包含有数据处理功能的芯片(如基带芯片)的芯片模组执行。
步骤S101，接收用户设备发送的边链路控制信息和/或数据。
在具体实施中，中继设备可以接收用户设备发送的边链路控制信息(Sidelink Control Information，SCI)；中继设备也可以接收用户设备发送的数据，用户设备发送的数据可以为上行数据或其他数据；中继设备还可以接收用户设备发送的边链路控制信息以及该用户设备发送的数据。
在具体实施中，当中继设备接收到用户设备发送的边链路控制信息以及该用户设备发送的数据时，该边链路控制信息用于指示该数据，例如，该边链路控制信息指示数据所在的时频资源位置、所使用的调制编码方式等。中继设备根据该边链路控制信息，能够正确解码该数据。
步骤S102，根据所述用户设备发送的边链路控制信息和/或数据，确定是否存在未来接收数据的预期。
在具体实施中，中继设备在接收到用户设备发送的边链路控制信息和/或数据后，可以根据接收到的边链路控制信息和/或数据来确定是否存在未来接收数据的预期。存在未来接收数据的预期，是指中继设备能够预期用户设备在后续的一段时间之内是否会继续发送数据。
在本发明实施例中，中继设备接收到用户设备发送的数据时，可以对该数据进行解码。若检测到对该数据解码失败，则用户设备大概率会重新向中继设备发送解码失败的数据。此时，中继设备可以判定存在未来接收数据的预期。
在本发明一实施例中，当检测到对接收到的数据第一次解码失败时，即可确定存在未来接收数据的预期。在本发明另一实施例中，当对接收到的数据连续N次解码失败时，确定存在未来接收数据的预期，N≥2。
在本发明另一实施例中，中继设备接收到用户设备发送的数据时，对该数据进行解码。若检测到对该数据解码失败，可以向用户设备反馈混合自动重传请求(Hybrid Automatic Repeat reQuest，HARQ)NACK。用户设备在接收到中继设备反馈的HARQ NACK之后，大概率会重新向中继设备发送解码失败的数据。此时，中继设备可以判定存在未来接收数据的预期。
在本发明又一实施例中，当检测到对数据第一次解码失败时，向用户设备反馈HARQ NACK时，即可确定存在未来接收数据的预期。也就是说，若中继设备数据解码失败，但不是第一次解码失败，虽然中继设备仍可能需要向用户设备反馈HARQ NACK，但是中继设备可能判定未来并不存在接收数据的预期。
可以理解的是，若中继设备对数据解码失败，且该数据不是第一次传输，则中继设备也可以判定未来存在接收数据的预期。
在本发明实施例中，中继设备接收到用户设备发送的边链路控制信息，若该边链路控制信息指示存在预留的资源位置用于数据传输，此时，中继设备可以判定存在未来接收数据的预期。
在本发明实施例中，中继设备接收到用户设备发送的边链路控制信息和数据，若该数据解码成功，且该边链路控制信息指示存在预留的资源位置用于数据传输，此时，中继设备可以判定存在未来接收数据的预期。
步骤S103，在确定存在未来接收数据的预期后，触发pre-emptive缓存状态报告。
在具体实施中，在中继设备确定存在未来接收数据的预期后，可以触发pre-emptive缓存状态报告，生成pre-emptive缓存状态报告并发送至基站。
在具体实施中，中继设备接收到用户设备发送的边链路控制信息和/或数据。中继设备在确定存在未来接收数据的预期后，可以先获取当前接收到的边链路控制信息对应的优先级，以及上一次发送的pre-emptive缓存状态报告的优先级。在本发明实施例中，为简便描述，将当前接收到的边链路控制信息对应的优先级简称为第一优先级，将上一次发送的pre-emptive缓存状态报告的优先级简称为第二优先级。
在本发明实施例中，中继设备可以对第一优先级与第二优先级进行比较，若第一优先级高于第二优先级，则触发pre-emptive缓存状态报告；若第一优先级不高于第二优先级，则不触发pre-emptive缓存状态报告。
通过获取边链路控制信息对应的优先级，并在当前接收到的边链路控制信息的优先级较高时才触发pre-emptive缓存状态报告，可以充分利用中继设备的空口资源，减少中继设备的功耗。
可以理解的是，若第一优先级不高于第二优先级，也可以触发pre-emptive缓存状态报告。但是，频繁触发pre-emptive缓存状态报 告会导致中继设备的空口资源占用较多，功耗较大。在实际应用中，可以根据具体的应用需求来确定是否进行优先级的比较。
在具体实施中，中继设备接收到用户设备发送的边链路控制信息和/或数据，并确定存在未来接收数据的预期后，可以获取当前接收到的边链路控制信息指示的第一数据量，以及上一次发送的pre-emptive缓存状态报告指示的第二数据量。当第一数据量大于第二数据量时，触发pre-emptive缓存状态报告。
在具体实施中，中继设备接收到用户设备发送的边链路控制信息和/或数据，并确定存在未来接收数据的预期后，可以获取当前接收到的数据的第三数据量，以及上一次发送的pre-emptive缓存状态报告指示的第二数据量。中继设备可以对第二数据量与第三数据量进行比较，当第三数据量大于第二数据量时，触发pre-emptive缓存状态报告。
通过比较数据量的大小，在当前需要发送的数量较大时触发pre-emptive缓存状态报告，也可以充分利用中继设备的空口资源，减少中继设备的功耗。
可以理解的是，若第一数据量不大于第二数据量，也可以触发pre-emptive缓存状态报告。但是，频繁触发pre-emptive缓存状态报告会导致中继设备的空口资源占用较多，功耗较大。在实际应用中，可以根据具体的应用需求来确定是否进行数据量的比较。
在具体实施中，在触发pre-emptive缓存状态报告之后，可以生成当前pre-emptive缓存状态报告。
在具体实施中，当pre-emptive缓存状态报告为中继设备对数据未解码成功触发的，则在生成当前pre-emptive缓存状态报告中，可以包括当前接收到的边链路控制信息的优先级信息，也即包括当前接收到的边链路控制信息的第一优先级。
在具体实施中，当pre-emptive缓存状态报告为中继设备对数据 未解码成功且向用户设备反馈HARQ NACK触发的，则在生成的当前pre-emptive缓存状态报告中，可以包括当前接收到的边链路控制信息的优先级信息，也即包括当前接收到的边链路控制信息的第一优先级。
在本发明实施例中，若pre-emptive缓存状态报告为中继设备对当前接收到的数据解码成功，且所述当前接收到的边链路控制信息还指示后续存在未发送的资源触发的，则在生成的当前pre-emptive缓存状态报告中，也可以包括当前接收到的边链路控制信息的第一优先级。
在具体应用中可知，若pre-emptive缓存状态报告为中继设备对当前接收到的数据解码成功，且当前接收到的边链路控制信息还指示后续存在未发送的资源触发的，由于未发送的资源对应数据的优先级未知，因此，为减少当前pre-emptive缓存状态报告的长度，中继设备生成的当前pre-emptive缓存状态报告也可以不包括所述当前接收到的边链路控制信息的第一优先级。
在本发明实施例中，若pre-emptive缓存状态报告为所述当前接收到的边链路控制信息还指示后续存在未发送的资源触发的，则在生成的当前pre-emptive缓存状态报告中，也可以包括当前接收到的边链路控制信息的第一优先级。
在具体应用中可知，若pre-emptive缓存状态报告为当前接收到的边链路控制信息还指示后续存在未发送的资源触发的，由于未发送的资源对应数据的优先级未知，因此，为减少当前pre-emptive缓存状态报告的长度，中继设备生成的当前pre-emptive缓存状态报告也可以不包括所述当前接收到的边链路控制信息的第一优先级。
在具体实施中，第一优先级可以占用8个比特，8个比特中的部分或全部比特取值用于表征第一优先级。
在具体实施中，当前pre-emptive缓存状态报告也可以包括当前 边链路控制信息指示的第一数据量。
在本发明实施例中，第一数据量可以占用8个比特，8个比特中的部分或全部比特取值用于表征第一数据量。
在具体实施中，当前pre-emptive缓存状态报告也可以包括当前数据的第三数据量。
在本发明实施例中，第三数据量可以占用8个比特，8个比特中的部分或全部比特取值用于表征第三数据量。
可以理解的是，第一数据量所占用的比特数量也可以大于8比特，例如16比特或更多。第三数据量所占用的比特数量也可以大于8比特，例如16比特或更多。
由上可见，在接收到用户设备发送的数据后，若确定存在未来接收数据的预期，则触发pre-emptive缓存状态报告，实现在边链路中继中pre-emptive缓存状态报告的触发。
参照图2，本发明实施例还提供了一种中继设备20，包括：接收单元201、确定单元202以及触发单元203，其中：
接收单元201，适于接收用户设备发送的边链路控制信息和/或数据；
确定单元202，适于根据所述用户设备发送的边链路控制信息和/或数据，确定是否存在未来接收数据的预期；
触发单元203，适于在确定存在未来接收数据的预期后，触发pre-emptive缓存状态报告；其中，所述边链路控制信息用于指示所述数据。
在具体实施中，上述的接收单元201、确定单元202以及触发单元203的具体执行流程可以参照上述实施例中提供的步骤S101～步骤S103，本发明实施例此处不做赘述。
在具体实施中，关于上述实施例中描述的各个装置、产品包含的 各个模块/单元，其可以是软件模块/单元，也可以是硬件模块/单元，或者也可以部分是软件模块/单元，部分是硬件模块/单元。
例如，对于应用于或集成于芯片的各个装置、产品，其包含的各个模块/单元可以都采用电路等硬件的方式实现，或者，至少部分模块/单元可以采用软件程序的方式实现，该软件程序运行于芯片内部集成的处理器，剩余的(如果有)部分模块/单元可以采用电路等硬件方式实现；对于应用于或集成于芯片模组的各个装置、产品，其包含的各个模块/单元可以都采用电路等硬件的方式实现，不同的模块/单元可以位于芯片模组的同一组件(例如芯片、电路模块等)或者不同组件中，或者，至少部分模块/单元可以采用软件程序的方式实现，该软件程序运行于芯片模组内部集成的处理器，剩余的(如果有)部分模块/单元可以采用电路等硬件方式实现；对于应用于或集成于终端的各个装置、产品，其包含的各个模块/单元可以都采用电路等硬件的方式实现，不同的模块/单元可以位于终端内同一组件(例如，芯片、电路模块等)或者不同组件中，或者，至少部分模块/单元可以采用软件程序的方式实现，该软件程序运行于终端内部集成的处理器，剩余的(如果有)部分模块/单元可以采用电路等硬件方式实现。本发明实施例还提供了一种计算机可读存储介质，所述计算机可读存储介质为非易失性存储介质或非瞬态存储介质，其上存储有计算机程序，所述计算机程序被处理器运行时执行上述任一实施例提供的触发边链路pre-emptive缓存状态报告方法的步骤。
本发明实施例还提供了另一种中继设备，包括存储器和处理器，所述存储器上存储有可在所述处理器上运行的计算机程序，所述处理器运行所述计算机程序时执行上述任一实施例提供的触发边链路pre-emptive缓存状态报告方法的步骤。
本领域普通技术人员可以理解上述实施例的各种方法中的全部或部分步骤是可以通过程序来指示相关的硬件来完成，该程序可以存储于一计算机可读存储介质中，存储介质可以包括：ROM、RAM、 磁盘或光盘等。
虽然本发明披露如上，但本发明并非限定于此。任何本领域技术人员，在不脱离本发明的精神和范围内，均可作各种更动与修改，因此本发明的保护范围应当以权利要求所限定的范围为准。

Claims (13)

  1. 一种触发边链路pre-emptive缓存状态报告方法，其特征在于，包括：
    接收用户设备发送的边链路控制信息和/或数据；
    根据所述用户设备发送的边链路控制信息和/或数据，确定是否存在未来接收数据的预期；
    在确定存在未来接收数据的预期后，触发pre-emptive缓存状态报告；其中，所述边链路控制信息用于指示所述数据。
  2. 如权利要求1所述的触发边链路pre-emptive缓存状态报告方法，其特征在于，所述根据所述用户设备发送的边链路控制信息和/或数据，确定是否存在未来接收数据的预期，包括：
    在对所述数据解码失败时，确定存在未来接收数据的预期；或，在对所述数据解码失败时，向所述用户设备反馈HARQ NACK，确定存在未来接收数据的预期；或，在所述边链路控制信息指示后续存在未发送的资源时，确定存在未来接收数据的预期。
  3. 如权利要求2所述的触发边链路pre-emptive缓存状态报告方法，其特征在于，所述在对所述数据解码失败时，确定存在未来接收数据的预期，包括：
    在对所述数据第一次解码失败时，确定存在未来接收数据的预期。
  4. 如权利要求2所述的触发边链路pre-emptive缓存状态报告方法，其特征在于，所述在对所述数据解码失败时，向所述用户设备反馈HARQ NACK，确定存在未来接收数据的预期，包括：
    在对所述数据第一次解码失败时，向所述用户设备反馈HARQ NACK，确定存在未来接收数据的预期。
  5. 如权利要求2～4任一项所述的触发边链路pre-emptive缓存状态报 告方法，其特征在于，所述在确定存在未来接收数据的预期后，触发pre-emptive缓存状态报告，包括以下任一种：
    获取所述边链路控制信息的第一优先级，以及上一次发送的pre-emptive缓存状态报告的第二优先级；当所述第一优先级高于所述第二优先级时，触发pre-emptive缓存状态报告；
    获取所述边链路控制信息指示的第一数据量，以及上一次发送的pre-emptive缓存状态报告指示的第二数据量；当所述第一数据量大于所述第二数据量时，触发pre-emptive缓存状态报告；
    获取所述数据的第三数据量，以及上一次发送的pre-emptive缓存状态报告指示的第二数据量；当所述第三数据量大于所述第二数据量时，触发pre-emptive缓存状态报告。
  6. 如权利要求5所述的触发边链路pre-emptive缓存状态报告方法，其特征在于，在触发pre-emptive缓存状态报告之后，还包括：
    生成当前pre-emptive缓存状态报告。
  7. 如权利要求6所述的触发边链路pre-emptive缓存状态报告方法，其特征在于，所述生成当前pre-emptive缓存状态报告，包括：
    若对所述数据解码失败，则所述当前pre-emptive缓存状态报告包括所述边链路控制信息的第一优先级。
  8. 如权利要求6所述的触发边链路pre-emptive缓存状态报告方法，其特征在于，所述生成当前pre-emptive缓存状态报告，包括：
    若对所述数据解码失败，向所述用户设备反馈HARQ NACK，则所述当前pre-emptive缓存状态报告包括所述边链路控制信息的第一优先级。
  9. 如权利要求6所述的触发边链路pre-emptive缓存状态报告方法，其特征在于，所述生成当前pre-emptive缓存状态报告，包括：
    若对所述数据解码成功，且所述边链路控制信息还指示后续存在未发 送的资源，则所述当前pre-emptive缓存状态报告包括所述边链路控制信息的第一优先级；
    或，若对所述数据解码成功，且所述边链路控制信息还指示后续存在未发送的资源，则所述当前pre-emptive缓存状态报告不包括所述当前接收到的边链路控制信息的第一优先级。
  10. 如权利要求6所述的触发边链路pre-emptive缓存状态报告方法，其特征在于，所述生成当前pre-emptive缓存状态报告，包括：
    所述当前pre-emptive缓存状态报告包括所述边链路控制信息指示的第一数据量；
    或，所述当前pre-emptive缓存状态报告包括所述数据的第三数据量。
  11. 一种中继设备，其特征在于，包括：
    接收单元，用于接收用户设备发送的边链路控制信息和/或数据；
    确定单元，用于根据所述用户设备发送的边链路控制信息和/或数据，确定是否存在未来接收数据的预期；
    触发单元，用于在确定存在未来接收数据的预期后，触发pre-emptive缓存状态报告；其中，所述边链路控制信息用于指示所述数据。
  12. 一种计算机可读存储介质，所述计算机可读存储介质为非易失性存储介质或非瞬态存储介质，其上存储有计算机程序，其特征在于，所述计算机程序被处理器运行时执行权利要求1～10任一项所述的触发边链路pre-emptive缓存状态报告方法的步骤。
  13. 一种中继设备，包括存储器和处理器，所述存储器上存储有可在所述处理器上运行的计算机程序，其特征在于，所述处理器运行所述计算机程序时执行权利要求1～10任一项所述的触发边链路pre-emptive缓存状态报告方法的步骤。
PCT/CN2021/125586 2020-10-22 2021-10-22 触发边链路pre-emptive缓存状态报告方法、中继设备及介质 WO2022083726A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP21882140.3A EP4236442A4 (en) 2020-10-22 2021-10-22 METHOD FOR TRIGGING A PREVENTIVE SIDELINK CACHE STATUS REPORT AND RELAY DEVICE AND MEDIUM
US18/032,989 US20230397229A1 (en) 2020-10-22 2021-10-22 Method for triggering sidelink pre-emptive buffer status report, relay device and medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011140334.0A CN114390586A (zh) 2020-10-22 2020-10-22 触发边链路pre-emptive缓存状态报告方法、中继设备及介质
CN202011140334.0 2020-10-22

Publications (1)

Publication Number Publication Date
WO2022083726A1 true WO2022083726A1 (zh) 2022-04-28

Family

ID=81194867

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/125586 WO2022083726A1 (zh) 2020-10-22 2021-10-22 触发边链路pre-emptive缓存状态报告方法、中继设备及介质

Country Status (4)

Country Link
US (1) US20230397229A1 (zh)
EP (1) EP4236442A4 (zh)
CN (1) CN114390586A (zh)
WO (1) WO2022083726A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101686565A (zh) * 2008-09-22 2010-03-31 宏达国际电子股份有限公司 改善暂存器状态触发机制的方法及其相关通讯装置
US20190334663A1 (en) * 2015-06-26 2019-10-31 Intel IP Corporation Transmission toggle uplink compensation
CN111107654A (zh) * 2018-11-02 2020-05-05 维沃移动通信有限公司 上行传输方法和终端设备

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2562220A (en) * 2017-05-05 2018-11-14 Tcl Communication Ltd Methods and devices associated with direct communications in a radio access network
CN113923711B (zh) * 2020-07-09 2024-10-18 大唐移动通信设备有限公司 缓冲区状态报告的上报方法、装置及中继终端

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101686565A (zh) * 2008-09-22 2010-03-31 宏达国际电子股份有限公司 改善暂存器状态触发机制的方法及其相关通讯装置
US20190334663A1 (en) * 2015-06-26 2019-10-31 Intel IP Corporation Transmission toggle uplink compensation
CN111107654A (zh) * 2018-11-02 2020-05-05 维沃移动通信有限公司 上行传输方法和终端设备

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
CATT: "Pre-emptive BSR", 3GPP DRAFT; R2-1912124, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Chongqing, P. R. China; 20191014 - 20191018, 3 October 2019 (2019-10-03), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051790177 *
HUAWEI, HISILICON: "Clarification of BSR and Pre-emptive BSR", 3GPP DRAFT; R2-2003018, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. electronic; 20200420 - 20200430, 10 April 2020 (2020-04-10), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051871138 *
See also references of EP4236442A4

Also Published As

Publication number Publication date
EP4236442A1 (en) 2023-08-30
EP4236442A4 (en) 2024-04-03
US20230397229A1 (en) 2023-12-07
CN114390586A (zh) 2022-04-22

Similar Documents

Publication Publication Date Title
WO2020029886A1 (zh) 反馈信息的传输方法和装置
US9379850B2 (en) Controlling retransmissions
US20090103440A1 (en) Collision avoidance for uplink VoIP transmission
CN110495114A (zh) 用于码块分组的方法和设备
US20110010598A1 (en) User Specific Load Balancing
CN110830177B (zh) 一种混合自动重传请求传输方法和装置
CN112911713B (zh) 一种上行控制信道的配置方法和设备
WO2018010497A1 (zh) 一种混合自动重传请求进程处理方法、设备及通信系统
CN111436094A (zh) 通信方法及装置
WO2020244599A1 (zh) 一种反馈指示方法及通信装置
US20230337211A1 (en) Sps harq-ack processing method and apparatus, device, and readable storage medium
TW202241171A (zh) 用於重傳之混成自動重複請求確認(harq-ack)碼簿之指示技術
CN112910610B (zh) 一种混合自动重传请求应答方法和设备
WO2022083726A1 (zh) 触发边链路pre-emptive缓存状态报告方法、中继设备及介质
JP7462749B2 (ja) アップリンクデータ伝送方法及びアップリンクデータ伝送装置
WO2017185991A1 (zh) 数据传输方法和装置
US12120686B2 (en) Service conflict processing method, user terminal and computer readable storage medium
WO2022000318A1 (en) Harq feedback transmission method, base station and user equipment
US20180359727A1 (en) Wireless communication apparatus, wireless communication method, and computer readable medium
WO2019095971A1 (zh) 一种通信方法及设备
CN115333680B (zh) 信息传输方法、装置、终端和存储介质
WO2022152324A1 (zh) 一种指示tci状态的方法、装置、芯片和电子设备
US11121804B2 (en) Base station, radio terminal, radio communication system, radio communication control method, and program
CN112369089B (zh) 支持多个活动带宽部分的harq解决方案
WO2018082073A1 (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: 21882140

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 18032989

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2021882140

Country of ref document: EP

Effective date: 20230522