Buffer status report processing method, apparatus, terminal, and storage medium
By processing cache status reports according to different bearer modes in multi-path scenarios, the problems of cache status reports processing efficiency and quality in the prior art are solved, and more efficient data transmission is achieved.
Patent Information
- Application Number
- PCT/CN2024/092766
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-19
- Filing Date
- 2024-05-13
- Publication Date
- 2024-11-28
AI Technical Summary
In multipath scenarios, the prior art fails to effectively process cache status reporting (BSR), resulting in limited data transmission efficiency and quality.
Provide a cache status report processing method, by determining the end-to-end bearer mode between the remote device and the network side device, respectively, the cache status report between the terminal and the network side device and the cache status report between the terminal and the terminal is respectively processed. , including determining the corresponding BSR-related information according to different bearer modes in the case of multipath transmission.
Improve data transmission performance, ensuring that the processing of cache status reports in multi-path scenarios can be accurately processed according to different bearer modes, thereby improving transmission efficiency and quality.
Smart Images

Figure CN2024092766_28112024_PF_FP_ABST
Abstract
Description
Cache status report processing method, device, terminal and storage medium
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims priority to the Chinese patent application filed with the China Patent Office on May 19, 2023, with application number 202310577655.4 and titled “A cache status report processing method, device, terminal and storage medium”, the entire contents of which are incorporated by reference into this application. Technical Field
[0003] The present application belongs to the field of communication technology, and specifically relates to a cache status report processing method, device, terminal and storage medium. Background Art
[0004] Relay technology in wireless communication systems adds one or more relay nodes between the base station and the terminal. These nodes forward wireless signals once or multiple times, meaning that wireless signals must traverse multiple hops before reaching the terminal. Wireless relay technology not only expands cell coverage and addresses coverage blind spots, but also increases cell capacity through spatial resource reuse. For indoor coverage, relay technology can also help overcome penetration loss and improve indoor coverage quality.
[0005] Taking a simple two-hop relay as an example, wireless relay splits a base station-terminal link into two links: base station-relay station and relay station-terminal. This allows one low-quality link to be replaced with two high-quality links, achieving higher link capacity and better coverage. Currently, LTE supports UE-to-network relay, where one end of the relay is connected to the UE and the other end is connected to the network. The UE connected to the relay is called the remote UE (or remote UE).
[0006] Based on the above technologies, a multi-path scenario has emerged. For the sidelink (SL) relay architecture, multi-path means that the remote UE establishes both an indirect path and a direct path, as shown in Figures 1 to 3. The direct path refers to the wireless link established between the remote UE (or primary UE) and the base station through its own Uu air interface; the indirect path refers to the wireless link established between the remote UE (or primary UE) and the base station through the Uu air interface of the relay UE (or secondary UE) and the relay UE (or secondary UE). In Figures 1 to 3, CP represents the control plane, and UP represents the user plane.
[0007] The Buffer Status Report (BSR) process is used to provide the network device with information about the amount of data stored in the UE's uplink buffer that needs to be sent, allowing the network to allocate resources to the UE, thereby further improving transmission efficiency and quality. However, in the aforementioned multipath scenario, related technologies do not provide a specific BSR processing method.
[0008] Summary of the Invention
[0009] The embodiments of the present application provide a buffer status report processing method, device, terminal and storage medium, and provide a BSR processing method in a multipath scenario.
[0010] In a first aspect, a cache status report processing method is provided, comprising:
[0011] When the remote device is configured for multipath transmission, the remote device determines, according to a configuration mode of an end-to-end bearer between the remote device and the network-side device, information related to a first BSR and information related to a second BSR of the remote device, or determines information related to the first BSR of the remote device;
[0012] Among them, the first BSR is the cache status report of the first communication interface, the second BSR is the cache status report of the second communication interface, the first communication interface is the communication interface between the terminal and the network side device, and the second communication interface is the communication interface between the terminals.
[0013] In a second aspect, a cache status report processing method is provided, including:
[0014] When the remote device is configured for multipath transmission and an ideal backhaul or non-standard connection is established between the remote device and the relay device, the relay device determines, based on an end-to-end bearer configuration mode between the remote device and the network-side device, relevant information about a third BSR of the relay device;
[0015] When the remote device is configured for multipath transmission and a non-ideal backhaul or a standard connection is used between the remote device and the relay device, the relay device determines, according to a radio link control protocol RLC entity of the first communication interface of the relay device, relevant information of the third BSR;
[0016] The third BSR is a buffer status report of the first communication interface, and the first communication interface is a communication interface between the terminal and the network side device.
[0017] According to a third aspect, a cache status report processing device is provided, comprising:
[0018] a first processing module, configured to, when the remote device is configured for multipath transmission, determine, based on a configuration mode of an end-to-end bearer between the remote device and the network-side device, information related to a first BSR and information related to a second BSR of the remote device, or determine information related to the first BSR of the remote device;
[0019] Among them, the first BSR is the cache status report of the first communication interface, the second BSR is the cache status report of the second communication interface, the first communication interface is the communication interface between the terminal and the network side device, and the second communication interface is the communication interface between the terminals.
[0020] In a fourth aspect, a cache status report processing device is provided, comprising at least one of the following modules:
[0021] a second processing module, configured to determine, when the remote device is configured for multipath transmission and an ideal backhaul or non-standard connection is established between the remote device and the relay device, relevant information of a third BSR of the relay device according to a configuration mode of an end-to-end bearer between the remote device and the network-side device;
[0022] a third processing module, configured to determine, according to a radio link control protocol RLC entity of the first communication interface of the relay device, relevant information of the third BSR when the remote device is configured for multipath transmission and a non-ideal backhaul or a standard connection is used between the remote device and the relay device;
[0023] The third BSR is a buffer status report of the first communication interface, and the first communication interface is a communication interface between the terminal and the network side device.
[0024] In a fifth aspect, a terminal is provided, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect or the second aspect are implemented.
[0025] In a sixth aspect, a terminal is provided, comprising a processor and a communication interface;
[0026] The processor is configured to: when the remote device is configured for multipath transmission, determine, based on the configuration mode of the end-to-end bearer between the remote device and the network-side device, relevant information of a first BSR and relevant information of a second BSR of the remote device, or determine relevant information of the first BSR of the remote device; wherein the first BSR is a buffer status report of a first communication interface, the second BSR is a buffer status report of a second communication interface, the first communication interface is a communication interface between a terminal and a network-side device, and the second communication interface is a communication interface between terminals;
[0027] or,
[0028] The processor is configured to: when a remote device is configured for multipath transmission and an ideal backhaul or non-standard connection is established between the remote device and the relay device, determine, based on a configuration mode of an end-to-end bearer between the remote device and the network-side device, relevant information of a third BSR of the relay device; wherein the third BSR is a buffer status report of the first communication interface, and the first communication interface is a communication interface between the terminal and the network-side device;
[0029] or,
[0030] The processor is used to: when the remote device is configured for multipath transmission and the remote device and the relay device have a non-ideal backhaul or a standard connection, determine the relevant information of the third BSR according to the radio link control protocol RLC entity of the first communication interface of the relay device.
[0031] In the seventh aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented.
[0032] In an eighth aspect, a wireless communication system is provided, comprising: a remote device and a relay device, wherein the remote device can be used to execute the steps of the method described in the first aspect, and the relay device can be used to execute the steps of the method described in the second aspect.
[0033] In the ninth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the method described in the first aspect, or to implement the method described in the second aspect.
[0034] In a tenth aspect, a computer program / program product is provided, wherein the computer program / program product is stored in a storage medium, and the program / program product is executed by at least one processor to implement the steps of the method described in the first aspect or the second aspect.
[0035] In an eleventh aspect, an embodiment of the present application provides a cache status report processing device, which is used to execute the steps of the cache status report processing method as described in the first aspect or the second aspect.
[0036] In an embodiment of the present application, when the remote device is configured for multi-path transmission, the remote device can determine the relevant information of the first BSR and the relevant information of the second BSR of the remote device based on the configuration mode of the end-to-end bearer between the remote device and the network side device, wherein the first BSR is a cache status report of the first communication interface, the second BSR is a cache status report of the second communication interface, the first communication interface is the communication interface between the terminal and the network side device, and the second communication interface is the communication interface between the terminal and the terminal.
[0037] It can be seen that in an embodiment of the present application, if the remote device is configured for multi-path transmission, the remote device can use a corresponding method to determine the relevant information of the BSR of the communication interface between the terminal and the terminal, and at least one of the relevant information of the BSR of the communication interface between the terminal and the network side device under different end-to-end bearing modes between the remote device and the network side device, that is, determine the relevant information of the corresponding BSR based on different end-to-end bearing modes. It can be seen that the embodiment of the present application provides a method for processing BSR in a multi-path scenario. BRIEF DESCRIPTION OF THE DRAWINGS
[0038] FIG1 is a schematic diagram of a multipath scenario based on the SL Relay architecture in the related art;
[0039] FIG2 is a second schematic diagram of a multipath scenario based on the SL Relay architecture in the related art;
[0040] FIG3 is a third schematic diagram of a multipath scenario based on the SL Relay architecture in the related art;
[0041] FIG4 is a block diagram of a wireless communication system applicable to embodiments of the present application;
[0042] FIG5 is a schematic diagram of a UE-to-Network Relay scenario in an embodiment of the present application;
[0043] FIG6 is a schematic diagram of direct loading in an embodiment of the present application;
[0044] FIG7 is a schematic diagram of a non-straight load-bearing system according to an embodiment of the present application;
[0045] FIG8 is a schematic diagram of a separate load in an embodiment of the present application;
[0046] FIG9 is a flowchart of a cache status report processing method according to an embodiment of the present application;
[0047] FIG10 is a flowchart of another cache status report processing method in an embodiment of the present application;
[0048] FIG11 is a structural block diagram of a cache status report processing device according to an embodiment of the present application;
[0049] FIG12 is a structural block diagram of another cache status report processing device in an embodiment of the present application;
[0050] FIG13 is a structural block diagram of a communication device in an embodiment of the present application;
[0051] FIG14 is a structural block diagram of a terminal in an embodiment of the present application. Specific embodiments
[0052] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.
[0053] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.
[0054] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.
[0055] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the technology described can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) systems. th Generation, 6G) communication system.
[0056] FIG4 shows a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device (Wearable Device), an aircraft (flight vehicle), a vehicle user equipment (VUE), a ship-borne device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), a game console, a personal computer (PC), a teller machine, or a self-service machine, or other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, vehicle-mounted controller, vehicle-mounted module, vehicle-mounted component, vehicle-mounted chip or vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application.
[0057] The network-side device 12 may include an access network device or a core network device, wherein the access network device may also be referred to as a radio access network (RAN) device, a radio access network function, or a radio access network unit. The access network device may include a base station, a wireless local area network (WLAN) access point (AS), or a wireless fidelity (WiFi) node. Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.
[0058] First, to facilitate understanding of the cache status report processing method of the embodiment of the present application, the following related technologies are introduced:
[0059] 1. Typical Scenarios of the SL Relay Mechanism
[0060] NR supports the UE-to-Network Relay mechanism, a typical scenario of which is shown in Figure 5. In this UE-to-Network scenario, a remote UE needs to transmit data to the network. If coverage is poor, a relay UE can be found to relay the data. The Uu interface connects the relay UE to the base station, while the sidelink (i.e., PC5) interface connects the relay UE to the remote UE. Generally speaking, the relay UE is open and can serve any remote UE.
[0061] 2. Multiple paths have the following bearer types:
[0062] The first type is direct bearer. As shown in Figure 6, in the Remote UE multi-path architecture, if an end-to-end radio bearer (E2E RB) between the Remote UE and the gNB is transmitted only through the direct path between the Remote UE and the gNB, then the bearer is a direct bearer.
[0063] The second type is an indirect bearer. As shown in Figure 7, in the Remote UE multi-path architecture, if an end-to-end bearer between the Remote UE and the gNB is transmitted only through the indirect path between the Remote UE, the Relay UE, and the gNB, then the bearer is an indirect bearer.
[0064] The third type is split bearer. As shown in Figure 8, in the Remote UE multi-path architecture, if an end-to-end bearer between the Remote UE and the gNB can be transmitted through both the direct path between the Remote UE and the gNB and the indirect path between the Remote UE, the Relay UE, and the gNB, then the bearer is a split bearer.
[0065] 6 to 8, SDAP stands for Service Data Adaptation Protocol; PDCP stands for Packet Data Convergence Protocol;
[0066] RLC stands for Radio Link Control Protocol; MAC stands for Medium Access Control; PHY stands for Physical Layer; SRAP stands for Sidelink Relay Adaptation Protocol; and Inter-UE interface stands for the interface between UEs.
[0067] The cache status report processing method provided in the embodiment of the present application is described in detail below with reference to some embodiments and application scenarios in conjunction with the accompanying drawings.
[0068] In a first aspect, an embodiment of the present application provides a method for processing a cache status report. As shown in FIG9 , the method may include the following steps:
[0069] Step 901: When the remote device is configured for multi-path transmission, the remote device determines the relevant information of the first BSR and the relevant information of the second BSR of the remote device according to the configuration mode of the end-to-end bearer between the remote device and the network side device, or determines the relevant information of the first BSR of the remote device.
[0070] In an embodiment of the present application, multipath transmission may refer to a direct path and an indirect path established between a remote device and a network side device, wherein the direct path is a wireless link established between the remote device and the network side device, and the indirect path is a wireless link established between the remote device and the network side device through a relay device.
[0071] Among them, the first BSR is the cache status report of the first communication interface, the second BSR is the cache status report of the second communication interface, the first communication interface is the communication interface between the terminal and the network side device, and the second communication interface is the communication interface between the terminals.
[0072] It can be seen that the first BSR is a buffer status report of the first communication interface of the remote device in the direct path, and the second BSR is a buffer status report of the second communication interface of the remote device in the indirect path.
[0073] In addition, when the remote device is configured for multi-path transmission, the remote device selects how to transmit data via a direct path and an indirect path based on its configured bearer type (i.e., the end-to-end bearer configuration mode). That is, the end-to-end bearer configuration mode determines how the remote device transmits data on a direct path and an indirect path. Different end-to-end configuration modes result in different data transmission methods on the direct path and the indirect path. Correspondingly, in different end-to-end configuration modes, the remote device's first BSR corresponding to the direct path and the relevant information of the second BSR corresponding to the indirect path are different. Therefore, the relevant information of the corresponding first BSR and the relevant information of the second BSR can be determined in different end-to-end configuration modes, thereby further improving the data transmission performance of the remote device.
[0074] Optionally, the first communication interface may be a Uu interface, and the second communication interface may be a PC5 interface.
[0075] Optionally, the BSR related information may include at least one of a trigger condition and a buffer size.
[0076] It can be seen from the above step 901 that in an embodiment of the present application, if the remote device is configured for multi-path transmission, the remote device can use a corresponding method to determine the relevant information of the BSR of the communication interface between the terminal and the terminal, and at least one of the relevant information of the BSR of the communication interface between the terminal and the network side device under different end-to-end bearing modes between the remote device and the network side device, that is, determine the corresponding BSR related information based on different end-to-end bearing modes. It can be seen that the embodiment of the present application provides a method for processing BSR in a multi-path scenario.
[0077] Optionally, step 901, "the remote device determining, according to a configuration mode of an end-to-end bearer between the remote device and the network-side device, relevant information about a first BSR and relevant information about a second BSR of the remote device," includes the following steps A-1:
[0078] Step A-1: When the remote device and the relay device are connected through the second communication interface and the remote device is configured as a network-side device scheduling mode, the remote device determines the triggering condition and first cache amount of the first BSR of the remote device and the triggering condition and second cache amount of the second BSR according to the configuration mode of the end-to-end bearer between the remote device and the network-side device.
[0079] Among them, if the remote device and the relay device are connected through the second communication interface, and the remote device is configured as the network side device scheduling mode (i.e., SL RA mode 1), the remote device needs to report the data cache that it needs to transmit on the second communication interface, and the network side device dynamically schedules the resources of the second communication interface. In this case, the remote device is involved in both the first BSR reporting and the second BSR reporting.
[0080] Optionally, when multiple end-to-end bearers exist between the remote device and the network-side device, one end-to-end bearer corresponds to one Packet Data Convergence Protocol (PDCP) entity; in step A-1, “the remote device configures, according to a configuration mode of the end-to-end bearer between the remote device and the network-side device, a triggering condition for a first BSR and a first buffer amount, and a triggering condition for a second BSR and a second buffer amount” includes at least one of the following items B-1 to B-8:
[0081] Item B-1: When the end-to-end bearer corresponding to the target PDCP entity is configured as a direct bearer, the remote device counts the arrival of the first data into the triggering condition of the first BSR, and counts the first data into the first cache amount, wherein the first data includes the data to be transmitted in the protocol data unit PDU corresponding to the service data unit SDU of the target PDCP entity, and the data in the control PDU of the target PDCP entity, and the target PDCP entity is one of the PDCP entities of the remote device.
[0082] Among them, for direct bearer, the data of the bearer is completely transmitted through a direct connection path between the remote device and the network side device. Therefore, if the end-to-end bearer corresponding to the target PDCP entity of the remote device is configured as direct bearer, then in item B-1, the arrival of the first data only needs to be counted in the triggering condition of the first BSR, and the first data only needs to be counted in the first cache amount of the first BSR.
[0083] In addition, the data to be transmitted includes data to be initially transmitted and data to be retransmitted.
[0084] In addition, the data to be transmitted in a PDCP entity includes the data to be transmitted in the PDU corresponding to the PDCP SDU and the data in the control PDU of the PDCP entity. The data in the SDU is the original data received, and the data in the PDU corresponding to the SDU is the data after processing the data in the SDU.
[0085] It should also be noted that in the embodiment of the present application, "counting the arrival of the first data as a triggering condition for the first BSR" means counting the arrival of the first data as a trigger for the first BSR, or classifying the arrival of the first data as a triggering condition for the first BSR. This can also be understood as meaning that the triggering condition for the first BSR includes the arrival of the first data, but whether the arrival of the first data can trigger the reporting of the first BSR depends on the actual reporting configuration. Similarly, other similar descriptions hereinbelow should be understood in accordance with the explanations herein.
[0086] In addition, in the embodiment of the present application, "the first data is counted in the first cache amount" can also be understood as: the first cache amount includes the amount of the first data. Similarly, other similar descriptions in the following text can be understood according to the explanation here.
[0087] Item B-2: When the end-to-end bearer corresponding to the target PDCP entity is configured as a non-direct bearer, the remote device counts the arrival of the first data into the triggering condition of the second BSR, and counts the first data into the second cache amount.
[0088] Among them, for non-direct bearer, the data of the bearer is completely transmitted through the non-direct path between the remote device-relay device-network side device. Therefore, if the end-to-end bearer corresponding to the target PDCP entity of the remote device is configured as a non-direct bearer, in item B-2, the arrival of the first data only needs to be counted in the triggering condition of the second BSR, and the second data only needs to be counted in the second cache amount of the second BSR.
[0089] Item B-3: When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, duplicate transmission is activated, and the primary path is a direct RLC bearer, the remote device counts the arrival of the first data into the triggering condition of the first BSR, and counts the first data into the first cache amount, counts the arrival of the second data into the triggering condition of the second BSR, and counts the second data into the second cache amount, or the remote device counts the arrival of the second data into the triggering condition of the first BSR, and counts the second data into the first cache amount, counts the arrival of the first data into the triggering condition of the second BSR, and counts the first data into the second cache amount, wherein the second data includes the data to be transmitted in the PDU corresponding to the SDU of the target PDCP entity.
[0090] Item B-4: When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, duplicate transmission is activated, and the primary path is a non-direct RLC bearer, the remote device counts the arrival of the first data into the triggering condition of the first BSR, and counts the first data into the first cache amount, counts the arrival of the second data into the triggering condition of the second BSR, and counts the second data into the second cache amount, or, the remote device counts the arrival of the second data into the triggering condition of the first BSR, and counts the second data into the first cache amount, counts the arrival of the first data into the triggering condition of the second BSR, and counts the first data into the second cache amount.
[0091] In items B-3 and B-4, for separated bearers with activated copy transmission, the data of the bearer will be copied and transmitted simultaneously through the direct RLC bearer and the indirect RLC bearer, that is, the remote device's E2E RB has two copies of data, one is directly transmitted to the network side device through the first communication interface, and the other is transmitted to the relay device through the second communication interface and then to the network side device through the first communication interface of the relay device.
[0092] Therefore, if the end-to-end bearer corresponding to the target PDCP entity of the remote device is configured as a separate bearer and duplicate transmission is activated, the data to be transmitted (i.e., the second data) in the PDU corresponding to the SDU of the target PDCP entity needs to be copied twice, so as to be transmitted simultaneously through the direct RLC bearer and the indirect RLC bearer. However, it should be noted that the data in the control PDU of the target PDCP entity (i.e., the part of the first data other than the second data) is only sent once, i.e., it does not participate in duplicate transmission. Therefore, the data in the control PDU of the target PDCP entity can be transmitted only on the primary path or only on the secondary path, wherein, if the RLC direct path is the primary path, the direct RLC bearer is the secondary path and the RLC indirect RLC bearer is the secondary path, and if the indirect RLC bearer is the primary path and the direct RLC bearer is the primary path, the direct RLC bearer is the secondary path. It can be seen that the data in the control PDU of the target PDCP entity can be transmitted on one of the direct bearer and the indirect bearer.
[0093] That is, if the end-to-end bearer corresponding to the target PDCP entity of the remote device is configured as a separate bearer and the copy transmission is activated, regardless of whether the main path is a direct RLC bearer or an indirect RLC bearer, the arrival of the data to be transmitted (i.e., the second data) in the PDU corresponding to the SDU of the target PDCP entity needs to be included in the triggering conditions of the first BSR and the triggering conditions of the second BSR (i.e., the arrival of the second data can affect the triggering of the first BSR and the triggering of the second BSR, that is, the arrival of the second data jointly affects the first BSR and the second BSR), and the second data needs to be included in the first cache amount and the second cache amount; and the data in the control PDU of the target PDCP entity (i.e., the part of the first data other than the second data) is included in the triggering conditions of the first BSR or the triggering conditions of the second BSR, and the data in the control PDU of the target PDCP entity is included in the first cache amount or the second cache amount.
[0094] In this way, it can be obtained that: if the end-to-end bearer corresponding to the target PDCP entity of the remote device is configured as a separate bearer, and the duplicate transmission is activated, and the main path is a direct RLC bearer or an indirect RLC bearer, then the arrival and data volume of the first data are included in the triggering condition and the first cache amount of the first BSR, and the arrival and data volume of the second data are included in the triggering condition and the second cache amount of the second BSR, or, the arrival and data volume of the first data are included in the triggering condition and the second cache amount of the second BSR, and the arrival and data volume of the second data are included in the triggering condition and the first cache amount of the first BSR.
[0095] It should also be noted that, as shown in Figure 8, for split bearers, the data of the PDCP entity of the remote device (i.e., Remote UE) can be transmitted to the network side device (e.g., gNB) through the RLC entity of the first communication interface (e.g., Uu interface), or can be transmitted to the network side device through the RLC entity of the second communication interface (e.g., PC5 interface) and the relay device (i.e., Relay UE). Under split bearers, the bearer on the radio link between the RLC entity of the first communication interface and the network side device is called a direct RLC bearer; the bearer on the radio link between the RLC entity of the second communication interface and the relay device is called an indirect RLC bearer. It is understandable that under other communication protocols, the RLC entity can also be replaced by other entities used to transmit data of the PDCP entity under other communication protocols.
[0096] Item B-5: When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, and duplicate transmission is not activated, and the primary path is a direct RLC bearer, and the data volume of the third data is less than the first threshold, the remote device counts the arrival of the first data into the triggering condition of the first BSR, and counts the first data into the first cache volume, wherein the third data includes fourth data, data to be initially transmitted in the non-directly connected layer 2 entity of the remote device, and data to be initially transmitted in the radio link control protocol RLC entity of the first communication interface of the remote device, and the fourth data includes at least one of data to be initially transmitted in the PDU corresponding to the SDU of the target PDCP entity, data to be retransmitted, and data in the control PDU of the target PDCP entity.
[0097] Item B-6: When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, duplicate transmission is not activated, the primary path is a direct RLC bearer, and the data volume of the third data is greater than or equal to the first threshold, the remote device performs one of the following items B-6-1 to B-6-3:
[0098] Item B-6-1: Count the arrival of the first data into the triggering condition of the first BSR and count the first data into the first buffer size; count the arrival of the second data into the triggering condition of the second BSR and count the second data into the second buffer size;
[0099] Item B-6-2: Count the arrival of the second data into the triggering condition of the first BSR, and count the second data into the first buffer size; count the arrival of the first data into the triggering condition of the second BSR, and count the first data into the second buffer size;
[0100] Item B-6-3: The remote device counts the arrival of the first data into the triggering conditions of the first BSR and the triggering conditions of the second BSR, and counts the first data into the first cache amount and the second cache amount.
[0101] In items B-5 to B-6, for separated bearers, where duplicate transmission is not activated and the primary path is a direct RLC bearer, the data of the bearer will be transmitted on the configured primary path, i.e., the direct RLC bearer, when the amount of buffered data to be transmitted is less than the corresponding threshold. When the amount of buffered data to be transmitted is greater than or equal to the corresponding threshold, the data can be transmitted on any path, i.e., a direct RLC bearer or an indirect RLC bearer.
[0102] Therefore, in the case of item B-5, the arrival and data amount of the first data only need to be counted in the triggering condition of the first BSR and the first buffer amount; while in the case of item B-6, transmission can be carried out on any path. Therefore, the data to be transmitted in the PDU corresponding to the SDU of the target PDCP entity (for example, data D1) and the data in the control PDU of the target PDCP entity (for example, data D2) can be transmitted on any path, and multiple combinations can be obtained:
[0103] Combination 1: Direct RLC bearer: D1+D2 (i.e., first data), indirect RLC bearer: D1 (i.e., second data);
[0104] Combination 2: Direct RLC bearer: D1 (i.e., second data), indirect RLC bearer: D1+D2 (i.e., first data);
[0105] Combination three: direct RLC bearer: D1+D2 (ie, first data), indirect RLC bearer: D1+D2 (ie, first data).
[0106] Therefore, based on combination one, we can get item B-6-1 mentioned above; based on combination two, we can get item B-6-2 mentioned above; and based on combination three, we can get item B-6-3 mentioned above.
[0107] Item B-7: When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, and duplicate transmission is not activated, and the primary path is a non-direct RLC bearer, and the data volume of the third data is less than the second threshold, the remote device counts the arrival of the first data into the triggering condition of the second BSR, and counts the first data into the second cache volume.
[0108] Item B-8: When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, duplicate transmission is not activated, the primary path is a non-direct RLC bearer, and the data volume of the third data is greater than or equal to the second threshold, the remote device performs one of the following items B-8-1 to B-8-3:
[0109] Item B-8-1: Count the arrival of the first data into the triggering condition of the first BSR and count the first data into the first buffer size; count the arrival of the second data into the triggering condition of the second BSR and count the second data into the second buffer size;
[0110] Item B-8-2: The remote device counts the arrival of the second data into the triggering condition of the first BSR and adds the second data to the first cache amount, and counts the arrival of the first data into the triggering condition of the second BSR and adds the first data to the second cache amount;
[0111] Item B-8-3: The remote device counts the arrival of the first data into the triggering conditions of the first BSR and the triggering conditions of the second BSR, and counts the first data into the first cache amount and the second cache amount.
[0112] In items B-7 to B-8, for a separated bearer, with duplicate transmission not activated and the primary path being a non-direct RLC bearer, the data of the bearer will be transmitted on the configured primary path, i.e., the non-direct RLC bearer, when the amount of buffered data to be transmitted is less than the corresponding threshold. When the amount of buffered data to be transmitted is greater than or equal to the corresponding threshold, the data can be transmitted on any path, i.e., a direct RLC bearer or a non-direct RLC bearer.
[0113] Therefore, in the case of item B-7, the arrival and data amount of the first data only need to be counted in the triggering condition of the second BSR and the second buffer amount; while in the case of item B-8, transmission can be carried out on any path. Therefore, the data to be transmitted in the PDU corresponding to the SDU of the target PDCP entity (for example, data D1) and the data in the control PDU of the target PDCP entity (for example, data D2) can be transmitted on any path, and multiple combinations can be obtained:
[0114] Combination 1: Direct RLC bearer: D1+D2 (i.e., first data), indirect RLC bearer: D1 (i.e., second data);
[0115] Combination 2: Direct RLC bearer: D1 (i.e., second data), indirect RLC bearer: D1+D2 (i.e., first data);
[0116] Combination three: direct RLC bearer: D1+D2 (ie, first data), indirect RLC bearer: D1+D2 (ie, first data).
[0117] Therefore, based on combination one, we can get item B-8-1 mentioned above; based on combination two, we can get item B-8-2 mentioned above; and based on combination three, we can get item B-8-3 mentioned above.
[0118] It should also be noted that if there are multiple PDCP entities on the remote device, each PDCP entity, based on the specific configuration mode of its corresponding end-to-end bearer, selects the corresponding content in items B-1 to B-8 described above to determine in which BSR of the remote device the data arrival and data volume in the PDU corresponding to the SDU of the PDCP entity, and the data arrival and data volume in the control PDU of the PDCP entity, are to be included. For example, if there are three PDCP entities on the remote device, and they meet the requirements of items B-1, B-2, and B-3, respectively, then these three PDCP entities will perform corresponding processing based on items B-1, B-2, and B-3, respectively.
[0119] In addition, the above items B-1 to B-8 are described from the perspective of a single PDCP entity. When the remote device and the relay device are connected via the second communication interface, and the remote device is configured in the network-side device scheduling mode, based on the different configuration modes of the end-to-end bearer corresponding to the PDCP entity of the remote device, it is determined to which BSR of the remote device the data arrival and data volume in the PDU corresponding to the SDU of each PDCP entity, as well as the data arrival and data volume in the control PDU, should be classified. After the classification is completed (i.e., after determining the triggering condition and first buffer volume of the first BSR, and the triggering condition and buffer volume of the second BSR), whether the triggering condition of the first BSR triggers the reporting of the first buffer volume of the first BSR, and whether the triggering condition of the second BSR triggers the reporting of the second buffer volume of the second BSR, can be determined based on relevant technologies and will not be further described here.
[0120] The following describes the overall buffer capacity of the first BSR and the second BSR of the remote device in this case.
[0121] Optionally, the first cache amount includes at least one of the following items C-1 to C-7:
[0122] Item C-1: amount of fifth data, wherein the fifth data includes data to be transmitted in a PDU corresponding to an SDU of the RLC entity of the first communication interface of the remote device, and data in a control PDU of the RLC entity;
[0123] It can be seen from item C-1 that when the remote device and the relay device are connected through the second communication interface and the remote device is configured as the network side device scheduling mode, the first cache amount includes the data to be transmitted in the PDU corresponding to the SDU of the RLC entity of all the first communication interfaces of the remote device and the data in the control PDU of the RLC entity.
[0124] Item C-2: The amount of first data when the end-to-end bearer corresponding to the target PDCP entity is configured as direct bearer, wherein the first data includes the data to be transmitted in the PDU corresponding to the SDU of the target PDCP entity, and the data in the control PDU of the target PDCP entity, and the target PDCP entity is one of the PDCP entities of the remote device.
[0125] In combination with the relevant content of the above-mentioned item B-1, for example, when the above-mentioned target PDCP entity is the first PDCP entity, it can be known from C-2 that when the remote device and the relay device are connected through the second communication interface and the remote device is configured as the network-side device scheduling mode, the first cache amount also includes the data to be transmitted in the PDU corresponding to the SDU of the first PDCP entity and the data amount in the control PDU of the first PDCP entity, wherein the end-to-end bearer corresponding to the first PDCP entity is configured as direct bearer.
[0126] Item C-3: When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, duplicate transmission is activated, and the primary path is a direct RLC bearer, the data volume of the first data or the data volume of the second data, wherein the second data includes the data to be transmitted in the PDU corresponding to the SDU of the target PDCP entity.
[0127] In combination with the relevant content of the aforementioned item B-3, for example, when the above-mentioned target PDCP entity is the second PDCP entity, it can be known from C-3 that when the remote device and the relay device are connected through the second communication interface and the remote device is configured as the network-side device scheduling mode, the first cache amount also includes the data amount of the data to be transmitted in the PDU corresponding to the SDU of the second PDCP entity and the data amount in the control PDU of the second PDCP entity, or the data amount of the data to be transmitted in the PDU corresponding to the SDU of the second PDCP entity, wherein the end-to-end bearer configuration corresponding to the second PDCP entity is: separated bearer, duplicate transmission is activated, and the main path is a direct RLC bearer.
[0128] Item C-4: The data volume of the second data or the data volume of the first data when the end-to-end bearer corresponding to the target PDCP entity is configured as a separated bearer, the duplicate transmission is activated, and the primary path is a non-direct RLC bearer.
[0129] In combination with the relevant content of the above-mentioned item B-4, for example, when the above-mentioned target PDCP entity is the third PDCP entity, it can be known from C-4 that when the remote device and the relay device are connected through the second communication interface and the remote device is configured as the network-side device scheduling mode, the first cache amount also includes the data amount of the to-be-transmitted data in the PDU corresponding to the SDU of the third PDCP entity and the data amount in the control PDU of the third PDCP entity, or the data amount of the to-be-transmitted data in the PDU corresponding to the SDU of the third PDCP entity, wherein the end-to-end bearer configuration corresponding to the third PDCP entity is: separated bearer, duplicate transmission is activated, and the main path is a non-direct RLC bearer.
[0130] Item C-5: The end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, duplicate transmission is not activated, the main path is a direct RLC bearer, and the data volume of the third data is less than the data volume of the first data at the first threshold, wherein the third data includes fourth data, data to be initially transmitted in the non-directly connected layer 2 entity of the remote device, and data to be initially transmitted in the RLC entity of the first communication interface of the remote device, and the fourth data includes at least one of data to be initially transmitted in the PDU corresponding to the SDU of the target PDCP entity, data to be retransmitted, and data in the control PDU of the target PDCP entity.
[0131] Combined with the relevant content of the aforementioned item B-5, for example, when the above-mentioned target PDCP entity is the fourth PDCP entity, it can be known from C-5 that when the remote device and the relay device are connected through the second communication interface and the remote device is configured as the network side device scheduling mode, the first cache amount also includes the data amount of the data to be transmitted in the PDU corresponding to the SDU of the fourth PDCP entity and the data amount in the control PDU of the fourth PDCP entity, wherein the end-to-end bearer configuration corresponding to the fourth PDCP entity is: separated bearer and copy transmission is not activated and the main path is a direct RLC bearer, and at least one of the data to be initially transmitted, the data to be retransmitted, and the data in the control PDU of the fourth PDCP entity in the PDU corresponding to the SDU of the fourth PDCP entity, the data to be initially transmitted in the non-directly connected layer 2 entity of the remote device, and the data to be initially transmitted in the RLC entity of the first communication interface of the remote device, the sum of the three data amounts is less than the first threshold.
[0132] Item C-6: When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer and duplicate transmission is not activated and the main path is a direct RLC bearer, and the data volume of the third data is greater than or equal to the first threshold, the data volume of the first data or the data volume of the second data.
[0133] Combined with the relevant content of item B-6 above, for example, when the target PDCP entity is the fifth PDCP entity, it can be known from C-6 that when the remote device and the relay device are connected through the second communication interface and the remote device is configured as the network side device scheduling mode, the first cache amount also includes the data amount of the data to be transmitted in the PDU corresponding to the SDU of the fifth PDCP entity and the data amount in the control PDU of the fifth PDCP entity, or the data amount of the data to be transmitted in the PDU corresponding to the SDU of the fifth PDCP entity, wherein the end-to-end bearer configuration corresponding to the fifth PDCP entity is: separated bearer and copy transmission is not activated and the main path is a direct RLC bearer, and at least one of the data to be initially transmitted, the data to be retransmitted, and the data in the control PDU of the fifth PDCP entity in the PDU corresponding to the SDU of the fifth PDCP entity, the data to be initially transmitted in the non-directly connected layer 2 entity of the remote device, and the data to be initially transmitted in the RLC entity of the first communication interface of the remote device, the sum of the three data amounts is greater than or equal to the first threshold.
[0134] Item C-7: When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer and duplicate transmission is not activated and the main path is a non-direct RLC bearer, and the data volume of the third data is greater than or equal to the second threshold, the data volume of the second data or the data volume of the first data.
[0135] Combined with the relevant content of item B-8 above, for example, when the target PDCP entity is the sixth PDCP entity, it can be known from C-7 that when the remote device and the relay device are connected through the second communication interface and the remote device is configured as the network side device scheduling mode, the first cache amount also includes the data amount of the data to be transmitted in the PDU corresponding to the SDU of the sixth PDCP entity and the data amount in the control PDU of the sixth PDCP entity, or the data amount of the data to be transmitted in the PDU corresponding to the SDU of the sixth PDCP entity, wherein the end-to-end bearer configuration corresponding to the sixth PDCP entity is: separated bearer and copy transmission is not activated and the main path is a non-direct RLC bearer, and at least one of the data to be initially transmitted, the data to be retransmitted, and the data in the control PDU of the sixth PDCP entity in the PDU corresponding to the SDU of the sixth PDCP entity, the data to be initially transmitted in the non-directly connected layer 2 entity of the remote device, and the data to be initially transmitted in the RLC entity of the first communication interface of the remote device, the sum of the three data amounts is greater than or equal to the second threshold.
[0136] Optionally, the second cache amount includes at least one of the following items E-1 to E-7:
[0137] Item E-1: amount of sixth data, wherein the sixth data includes data to be transmitted in a PDU corresponding to an SDU of the RLC entity of the second communication interface of the remote device, and data in a control PDU of the RLC entity;
[0138] It can be seen from item E-1 that when the remote device and the relay device are connected through the second communication interface and the remote device is configured as the network side device scheduling mode, the second cache amount includes the amount of data to be transmitted in the PDU corresponding to the SDU of the RLC entity of all the second communication interfaces of the remote device and the amount of data in the control PDU of the RLC entity.
[0139] Item E-2: The amount of first data when the end-to-end bearer corresponding to the target PDCP entity is configured as a non-direct bearer, wherein the first data includes the data to be transmitted in the PDU corresponding to the SDU of the target PDCP entity, and the data in the control PDU of the target PDCP entity, and the target PDCP entity is one of the PDCP entities of the remote device.
[0140] In combination with the relevant content of the above-mentioned item B-2, for example, when the above-mentioned target PDCP entity is the seventh PDCP entity, it can be known from E-2 that when the remote device and the relay device are connected through the second communication interface and the remote device is configured as the network-side device scheduling mode, the second cache amount also includes the amount of data to be transmitted in the PDU corresponding to the SDU of the seventh PDCP entity and the amount of data in the control PDU of the seventh PDCP entity, wherein the end-to-end bearer corresponding to the seventh PDCP entity is configured as direct bearer.
[0141] Item E-3: When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, the copy transmission is activated, and the main path is a direct RLC bearer, the data volume of the second data or the data volume of the first data, wherein the second data includes the data to be transmitted in the PDU corresponding to the SDU of the target PDCP entity.
[0142] In combination with the relevant content of the aforementioned item B-3, for example, when the above-mentioned target PDCP entity is the second PDCP entity, it can be known from E-3 that when the remote device and the relay device are connected through the second communication interface and the remote device is configured as the network-side device scheduling mode, the second cache amount also includes the data volume of the data to be transmitted in the PDU corresponding to the SDU of the second PDCP entity and the data volume in the control PDU of the second PDCP entity, or the data volume of the data to be transmitted in the PDU corresponding to the SDU of the second PDCP entity, wherein the end-to-end bearer configuration corresponding to the second PDCP entity is: separated bearer, copy transmission is activated, and the main path is a direct RLC bearer.
[0143] Item E-4: The data volume of the first data or the data volume of the second data when the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, the duplicate transmission is activated, and the primary path is a non-direct RLC bearer.
[0144] In combination with the relevant content of the above-mentioned item B-4, for example, when the above-mentioned target PDCP entity is the third PDCP entity, it can be known from E-4 that when the remote device and the relay device are connected through the second communication interface and the remote device is configured as the network side device scheduling mode, the second cache amount also includes the data amount of the to-be-transmitted data in the PDU corresponding to the SDU of the third PDCP entity and the data amount in the control PDU of the third PDCP entity, or the data amount of the to-be-transmitted data in the PDU corresponding to the SDU of the third PDCP entity, wherein the end-to-end bearer configuration corresponding to the third PDCP entity is: separated bearer, duplicate transmission is activated, and the main path is a non-direct RLC bearer.
[0145] Item E-5: When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer and duplicate transmission is not activated and the main path is a direct RLC bearer, and the data volume of the third data is greater than or equal to the first threshold, the data volume of the second data or the data volume of the first data, wherein the third data includes fourth data, data to be initially transmitted in the non-directly connected layer 2 entity of the remote device, and data to be initially transmitted in the radio link control protocol RLC entity of the first communication interface of the remote device, and the fourth data includes at least one of data to be initially transmitted in the PDU corresponding to the SDU of the target PDCP entity, data to be retransmitted, and data in the control PDU of the target PDCP entity.
[0146] Combined with the relevant content of item B-6 above, for example, when the target PDCP entity is the fifth PDCP entity, it can be known from E-5 that when the remote device and the relay device are connected through the second communication interface and the remote device is configured as the network side device scheduling mode, the second cache amount also includes the data amount of the data to be transmitted in the PDU corresponding to the SDU of the fifth PDCP entity and the data amount in the control PDU of the fifth PDCP entity, or the data amount of the data to be transmitted in the PDU corresponding to the SDU of the fifth PDCP entity, wherein the end-to-end bearer configuration corresponding to the fifth PDCP entity is: separated bearer and copy transmission is not activated and the main path is a direct RLC bearer, and at least one of the data to be initially transmitted, the data to be retransmitted, and the data in the control PDU of the fifth PDCP entity in the PDU corresponding to the SDU of the fifth PDCP entity, the data to be initially transmitted in the non-directly connected layer 2 entity of the remote device, and the data to be initially transmitted in the RLC entity of the first communication interface of the remote device, the sum of the three data amounts is greater than or equal to the first threshold.
[0147] Item E-6: The end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer and duplicate transmission is not activated and the main path is a non-direct RLC bearer, and the data volume of the third data is less than the data volume of the first data at the second threshold.
[0148] Combined with the relevant content of the aforementioned item B-7, for example, when the above-mentioned target PDCP entity is the eighth PDCP entity, it can be known from E-6 that when the remote device and the relay device are connected through the second communication interface and the remote device is configured as the network side device scheduling mode, the second cache amount also includes the data amount of the to-be-transmitted data in the PDU corresponding to the SDU of the eighth PDCP entity and the data amount in the control PDU of the eighth PDCP entity, wherein the end-to-end bearer configuration corresponding to the eighth PDCP entity is: separated bearer and copy transmission is not activated and the main path is a non-direct RLC bearer, and at least one of the to-be-transmitted data, to-be-retransmitted data, and data in the control PDU of the eighth PDCP entity in the PDU corresponding to the SDU of the eighth PDCP entity, the to-be-transmitted data in the non-directly connected layer 2 entity of the remote device, and the to-be-transmitted data in the RLC entity of the first communication interface of the remote device, the sum of the three data amounts is less than the second threshold.
[0149] Item E-7: When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer and duplicate transmission is not activated and the main path is a non-direct RLC bearer, and the data volume of the third data is greater than or equal to the second threshold, the data volume of the first data or the data volume of the second data.
[0150] Combined with the relevant content of item B-8 above, for example, when the target PDCP entity is the sixth PDCP entity, it can be known from E-7 that when the remote device and the relay device are connected through the second communication interface and the remote device is configured as the network side device scheduling mode, the second cache amount also includes the data amount of the to-be-transmitted data in the PDU corresponding to the SDU of the sixth PDCP entity and the data amount in the control PDU of the sixth PDCP entity, or the data amount of the to-be-transmitted data in the PDU corresponding to the SDU of the sixth PDCP entity, wherein the end-to-end bearer configuration corresponding to the sixth PDCP entity is: separated bearer and copy transmission is not activated and the main path is a non-direct RLC bearer, and at least one of the to-be-transmitted data, to-be-retransmitted data, and the data in the control PDU of the sixth PDCP entity in the PDU corresponding to the SDU of the sixth PDCP entity, the to-be-transmitted data in the non-directly connected layer 2 entity of the remote device, and the to-be-transmitted data in the RLC entity of the first communication interface of the remote device, the sum of the three data amounts is greater than or equal to the second threshold.
[0151] Optionally, in step 901, "the remote device determines, according to a configuration mode of an end-to-end bearer between the remote device and the network-side device, relevant information of a first BSR of the remote device" includes the following step F-1:
[0152] Step F-1: In the case where the remote device and the relay device have an ideal backhaul or a non-standard connection, the remote device determines the triggering condition and the third cache amount of the first BSR of the remote device based on the configuration mode of the end-to-end bearer between the remote device and the network side device.
[0153] Among them, ideal backhaul means that the connection between two nodes reaches or is close to the ideal communication state, that is, the communication bandwidth is large enough or infinite, and the communication delay is equal to or close to zero; non-standard connection means that the two nodes are not connected through a standardized interface. Standardized interfaces include Uu interface, PC5 interface, Wi-Fi, Bluetooth, etc. Non-standard interfaces do not require cross-vendor definition and can generally be implemented internally or in a non-standardized manner.
[0154] Among them, in the scenario where the remote device and the relay device are connected through an ideal connection (i.e., ideal backhaul) or a non-standardized interface, the remote device and the relay device are also in the Radio Resource Control (RRC) connected (CONNECTED) state in the multi-path architecture. These two devices also need to report the uplink (UL) BSR to the network side device to facilitate the network side device to schedule their UL data in a timely manner, thereby well supporting the data transmission of the remote device.
[0155] In addition, as mentioned above, for the remote device, when the configuration mode of the end-to-end bearer between it and the network side device is different, the remote device uses the direct path and the non-direct path differently. Therefore, in the case of an ideal backhaul or a non-standard connection between the remote device and the relay device, the remote device can also determine the triggering conditions of the first BSR (i.e., the BSR of the first communication interface) and the third cache amount based on the different configuration modes of the end-to-end bearer.
[0156] Optionally, when multiple end-to-end bearers exist between the remote device and the network-side device, one end-to-end bearer corresponds to one PDCP entity;
[0157] In step F-1 above, the remote device determines, based on the configuration mode of the end-to-end bearer between the remote device and the network-side device, a triggering condition for a first BSR of the remote device and a third buffer amount, including at least one of the following items G-1 to G-7:
[0158] Item G-1: When the end-to-end bearer corresponding to the target PDCP entity is configured as a direct bearer, the remote device counts arrival of first data into a triggering condition of the first BSR, and counts the first data into the third buffer amount, wherein the first data includes data to be transmitted in a PDU corresponding to an SDU of the target PDCP entity and data in a control PDU of the target PDCP entity, and the target PDCP entity is one of the PDCP entities of the remote device;
[0159] Among them, for direct bearer, the data of the bearer is completely transmitted through a direct connection path between the remote device and the network side device. Therefore, if the end-to-end bearer corresponding to the target PDCP entity of the remote device is configured as direct bearer, in item G-1, the arrival of the first data only needs to be counted in the triggering condition of the first BSR, and the first data only needs to be counted in the third cache amount of the first BSR.
[0160] Item G-2: When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, duplicate transmission is activated, and the primary path is a direct RLC bearer, the remote device counts the arrival of the first data into the triggering condition of the first BSR and counts the first data into the third cache amount, or the remote device counts the arrival of the second data into the triggering condition of the first BSR and counts the second data into the third cache amount, wherein the second data includes the data to be transmitted in the PDU corresponding to the SDU of the target PDCP entity.
[0161] Item G-3: When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, duplicate transmission is activated, and the primary path is a non-direct RLC bearer, the remote device counts the arrival of the first data into the triggering condition of the first BSR and counts the first data into the third cache amount, or the remote device counts the arrival of the second data into the triggering condition of the first BSR and counts the second data into the third cache amount.
[0162] In items G-2 and G-3, for separated bearers with activated copy transmission, the data of the bearer will be copied and transmitted simultaneously through the direct RLC bearer and the indirect RLC bearer. That is to say, the remote device's E2E RB has two copies of data, one of which is directly transmitted to the network side device through the first communication interface, and the other is first transmitted to the relay device through the second communication interface and then to the network side device through the first communication interface of the relay device.
[0163] Therefore, if the end-to-end bearer corresponding to the target PDCP entity of the remote device is configured as a separate bearer and duplicate transmission is activated, the data to be transmitted (i.e., the second data) in the PDU corresponding to the SDU of the target PDCP entity needs to be copied twice, so as to be transmitted simultaneously through the direct RLC bearer and the indirect RLC bearer. However, it should be noted that the data in the control PDU of the target PDCP entity (i.e., the part of the first data other than the second data) is only sent once, i.e., it does not participate in duplicate transmission. Therefore, the data in the control PDU of the target PDCP entity can be transmitted only on the primary path or only on the secondary path, wherein, if the direct RLC bearer is the primary path, the direct RLC bearer is the secondary path and the indirect RLC bearer is the secondary path, and if the indirect RLC bearer is the primary path, the direct RLC bearer is the secondary path. Therefore, the data in the control PDU of the target PDCP entity can be transmitted on one of the direct bearer and the indirect bearer.
[0164] That is, if the end-to-end bearer corresponding to the target PDCP entity of the remote device is configured as a separate bearer and the copy transmission is activated, regardless of whether the main path is a direct RLC bearer or an indirect RLC bearer, the arrival of the data to be transmitted (i.e., the second data) in the PDU corresponding to the SDU of the target PDCP entity needs to be counted in the trigger condition of the first BSR and the trigger condition of the third BSR of the first communication interface of the relay device, and the second data needs to be counted in the third cache amount and the fourth cache amount of the third BSR; and the data in the control PDU of the target PDCP entity (i.e., the part of the first data other than the second data) is counted in the trigger condition of the first BSR or the trigger condition of the third BSR, and the data in the control PDU of the target PDCP entity is counted in the third cache amount or the fourth cache amount.
[0165] In this way, we can obtain the following contents of items G-2 to G-3, that is, if the end-to-end bearer corresponding to the target PDCP entity of the remote device is configured as a separate bearer, and the copy transmission is activated, and the main path is a direct RLC bearer or an indirect RLC bearer, then the arrival and data volume of the first data are included in the triggering conditions and the third cache amount of the first BSR, or the arrival and data volume of the second data are included in the triggering conditions and the third cache amount of the first BSR.
[0166] Item G-4: When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, and duplicate transmission is not activated, and the primary path is a direct RLC bearer, and the data volume of the third data is less than a third threshold, the remote device counts the arrival of the first data into the triggering condition of the first BSR, and counts the first data into the third cache volume, wherein the third data includes fourth data, data to be initially transmitted in the non-directly connected layer 2 entity of the remote device, and data to be initially transmitted in the RLC entity of the first communication interface of the remote device, and the fourth data includes at least one of data to be initially transmitted in the PDU corresponding to the SDU of the target PDCP entity, data to be retransmitted, and data in the control PDU of the target PDCP entity.
[0167] Item G-5: When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, and duplicate transmission is not activated, and the primary path is a direct RLC bearer, and the data volume of the third data is greater than or equal to the third threshold, the remote device counts the arrival of the first data into the triggering condition of the first BSR and counts the first data into the third cache volume, or the remote device counts the arrival of the second data into the triggering condition of the first BSR and counts the second data into the third cache volume.
[0168] In items G-4 to G-5, for a separated bearer, with duplicate transmission not activated and the primary path being a direct RLC bearer, the data of the bearer will be transmitted on the configured primary path, i.e., the direct RLC bearer, when the amount of buffered data to be transmitted is less than the corresponding threshold. When the amount of buffered data to be transmitted is greater than or equal to the corresponding threshold, the data can be transmitted on any path, i.e., a direct RLC bearer or an indirect RLC bearer.
[0169] Therefore, in the case of item G-4, the arrival and data amount of the first data only need to be counted in the triggering condition of the first BSR and the third cache amount; while in the case of item G-5, it can be transmitted on any path. Therefore, in the case of item G-5, the arrival and data amount of the first data can be counted in the triggering condition of the first BSR and the third cache amount, or the arrival and data amount of the second data can be counted in the triggering condition of the first BSR and the third cache amount.
[0170] Item G-6: When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, and duplicate transmission is not activated, and the primary path is a non-direct RLC bearer, and the data volume of the third data is greater than or equal to a fourth threshold, the remote device counts the arrival of the first data into the triggering condition of the first BSR and counts the first data into the third cache volume, or the remote device counts the arrival of the second data into the triggering condition of the first BSR and counts the second data into the third cache volume.
[0171] In item G-6, for a split bearer, with duplicate transmission not activated and the primary path being an indirect RLC bearer, the data of the bearer will be transmitted on the configured primary path, i.e., the indirect RLC bearer, when the amount of buffered data to be transmitted is less than the corresponding threshold. When the amount of buffered data to be transmitted is greater than or equal to the corresponding threshold, the data can be transmitted on any path, i.e., a direct RLC bearer or an indirect RLC bearer.
[0172] Therefore, in the case of item G-6, transmission can be carried out on any path, so in the case of item G-6, the arrival and data amount of the first data can be counted in the triggering condition of the first BSR and the third cache amount, or the arrival and data amount of the second data can be counted in the triggering condition of the first BSR and the third cache amount.
[0173] Item G-7: When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer and the copy transmission is not activated, the remote device counts the arrival of the first data into the trigger condition of the first BSR and counts the first data into the third cache amount.
[0174] It can be seen from item G-7 that if the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer and the copy transmission is not activated, it can be considered that both the main path and the auxiliary path can be transmitted. In this way, the arrival and data volume of the first data can be included in the triggering conditions of the first BSR and the third cache amount.
[0175] Furthermore, items G-1 through G-7 above describe, from the perspective of a single PDCP entity, whether the data arrival and amount in the PDU corresponding to the SDU of that PDCP entity, as well as the data arrival and amount in the control PDU, are included in the triggering conditions and third buffer size of the remote device's first BSR, when the remote device and relay device have an ideal backhaul or non-standard connection. The following describes the overall buffer size of the remote device's first BSR in this scenario.
[0176] Optionally, the third cache amount includes at least one of the following items H-1 to H-8:
[0177] Item H-1: amount of fifth data, wherein the fifth data includes data to be transmitted in a PDU corresponding to an SDU of the RLC entity of the first communication interface of the remote device, and data in a control PDU of the RLC entity;
[0178] It can be seen from item H-1 that when the connection between the remote device and the relay device is an ideal backhaul or a non-standard connection, the third cache amount includes the amount of data to be transmitted in the PDU corresponding to the SDU of the RLC entity of all first communication interfaces of the remote device and the amount of data in the control PDU of the RLC entity.
[0179] Item H-2: amount of first data when the end-to-end bearer corresponding to the target PDCP entity is configured as a direct bearer, wherein the first data includes data to be transmitted in a PDU corresponding to an SDU of the target PDCP entity and data in a control PDU of the target PDCP entity, and the target PDCP entity is one of the PDCP entities of the remote device;
[0180] In combination with the relevant content of item G-1 above, for example, when the above-mentioned target PDCP entity is the ninth PDCP entity, it can be known from H-2 that when there is an ideal backhaul or non-standard connection between the remote device and the relay device, the third cache amount also includes the amount of data to be transmitted in the PDU corresponding to the SDU of the ninth PDCP entity and the amount of data in the control PDU of the ninth PDCP entity, wherein the end-to-end bearer configuration corresponding to the ninth PDCP entity is direct bearer.
[0181] Item H-3: When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is activated, and the primary path is a direct RLC bearer, the data volume of the first data or the data volume of the second data, wherein the second data includes the data to be transmitted in the PDU corresponding to the SDU of the target PDCP entity;
[0182] In combination with the relevant content of item G-2 above, for example, when the target PDCP entity is the tenth PDCP entity, it can be known from H-3 that when the connection between the remote device and the relay device is an ideal backhaul or a non-standard connection, the third cache amount also includes the amount of data to be transmitted in the PDU corresponding to the SDU of the tenth PDCP entity and the amount of data in the control PDU of the tenth PDCP entity, or the amount of data to be transmitted in the PDU corresponding to the SDU of the tenth PDCP entity, wherein the end-to-end bearer configuration corresponding to the tenth PDCP entity is: separated bearer, duplicate transmission is activated, and the main path is a direct RLC bearer.
[0183] Item H-4: when the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is activated, and the primary path is an indirect RLC bearer, the data volume of the second data or the data volume of the first data;
[0184] In combination with the relevant content of item G-3 above, for example, when the target PDCP entity is the eleventh PDCP entity, it can be known from H-4 that when the connection between the remote device and the relay device is an ideal backhaul or a non-standard connection, the third cache amount also includes the amount of data to be transmitted in the PDU corresponding to the SDU of the eleventh PDCP entity and the amount of data in the control PDU of the eleventh PDCP entity, or the amount of data to be transmitted in the PDU corresponding to the SDU of the eleventh PDCP entity, wherein the end-to-end bearer configuration corresponding to the eleventh PDCP entity is: separated bearer, duplicate transmission is activated, and the main path is a non-direct RLC bearer.
[0185] Item H-5: when the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer and duplicate transmission is not activated and the primary path is a direct RLC bearer, and the data volume of the third data is less than a third threshold, the data volume of the first data, wherein the third data includes fourth data, data to be initially transmitted in the non-directly connected layer 2 entity of the remote device, and data to be initially transmitted in the RLC entity of the first communication interface of the remote device, and the fourth data includes at least one of data to be initially transmitted in the PDU corresponding to the SDU of the target PDCP entity, data to be retransmitted, and data in the control PDU of the target PDCP entity;
[0186] Combined with the relevant content of item G-4 above, for example, when the target PDCP entity is the twelfth PDCP entity, it can be known from H-5 that when the remote device and the relay device have an ideal backhaul or a non-standard connection, the third cache amount also includes the amount of data to be transmitted in the PDU corresponding to the SDU of the twelfth PDCP entity and the amount of data in the control PDU of the twelfth PDCP entity, wherein the end-to-end bearer configuration corresponding to the twelfth PDCP entity is: separated bearer and copy transmission is not activated and the main path is a direct RLC bearer, and at least one of the data to be initially transmitted, the data to be retransmitted, and the data in the control PDU of the twelfth PDCP entity in the PDU corresponding to the SDU of the twelfth PDCP entity, the data to be initially transmitted in the non-directly connected layer 2 entity of the remote device, and the data to be initially transmitted in the RLC entity of the first communication interface of the remote device, the sum of the three data amounts is less than the third threshold.
[0187] Item H-6: when the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is not activated, the primary path is a direct RLC bearer, and the data volume of the third data is greater than or equal to the third threshold, the data volume of the first data or the data volume of the second data;
[0188] Combined with the relevant content of item G-5 above, for example, when the target PDCP entity is the thirteenth PDCP entity, it can be known from H-6 that when the connection between the remote device and the relay device is an ideal backhaul or a non-standard connection, the third cache amount also includes the data amount of the data to be transmitted in the PDU corresponding to the SDU of the thirteenth PDCP entity and the data amount in the control PDU of the thirteenth PDCP entity, or the data amount of the data to be transmitted in the PDU corresponding to the SDU of the thirteenth PDCP entity, wherein the end-to-end bearer configuration corresponding to the thirteenth PDCP entity is: separated bearer and copy transmission is not activated and the main path is a direct RLC bearer, and at least one of the data to be initially transmitted, the data to be retransmitted, and the data in the control PDU of the thirteenth PDCP entity in the PDU corresponding to the SDU of the thirteenth PDCP entity, the data to be initially transmitted in the non-directly connected layer 2 entity of the remote device, and the data to be initially transmitted in the RLC entity of the first communication interface of the remote device, the sum of the three data amounts is greater than or equal to the third threshold.
[0189] Item H-7: when the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is not activated, the primary path is an indirect RLC bearer, and the data volume of the third data is greater than or equal to a fourth threshold, the data volume of the second data or the data volume of the first data;
[0190] Combined with the relevant content of item G-6 above, for example, when the target PDCP entity is the fourteenth PDCP entity, it can be seen from C-7 that when the connection between the remote device and the relay device is an ideal backhaul or a non-standard connection, the third cache amount also includes the data amount of the data to be transmitted in the PDU corresponding to the SDU of the fourteenth PDCP entity and the data amount in the control PDU of the fourteenth PDCP entity, or the data amount of the data to be transmitted in the PDU corresponding to the SDU of the fourteenth PDCP entity, wherein the end-to-end bearer configuration corresponding to the fourteenth PDCP entity is: separated bearer and copy transmission is not activated and the main path is a non-direct RLC bearer, and at least one of the data to be initially transmitted, the data to be retransmitted, and the data in the control PDU of the fourteenth PDCP entity in the PDU corresponding to the SDU of the fourteenth PDCP entity, the data to be initially transmitted in the non-directly connected layer 2 entity of the remote device, and the data to be initially transmitted in the RLC entity of the first communication interface of the remote device, the sum of the three data amounts is greater than or equal to the fourth threshold.
[0191] Item H-8: The end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, and the data volume of the first data when the copy transmission is not activated.
[0192] In combination with the relevant content of item G-7 above, for example, when the target PDCP entity is the fifteenth PDCP entity, it can be seen from C-7 that when the remote device and the relay device have an ideal backhaul or a non-standard connection, the third cache amount also includes the amount of data to be transmitted in the PDU corresponding to the SDU of the fifteenth PDCP entity and the amount of data in the control PDU of the fifteenth PDCP entity, wherein the end-to-end bearer configuration of the fifteenth PDCP entity is: separate bearer, and copy transmission is not activated.
[0193] In a second aspect, an embodiment of the present application provides a cache status report processing method. As shown in FIG10 , the method may include at least one of the following steps 1001 and 1002:
[0194] Step 1001: When the remote device is configured for multi-path transmission and the remote device and the relay device have an ideal backhaul or a non-standard connection, the relay device determines the relevant information of the third BSR of the relay device based on the configuration mode of the end-to-end bearer between the remote device and the network side device.
[0195] Among them, when the connection between the remote device and the relay device is an ideal backhaul or a non-standard connection, the remote device and the relay device are also in the RRC CONNECTED state in the multi-path architecture. These two devices also need to report uplink (UL) BSR to the network side device to facilitate the network side device to schedule their UL data in a timely manner, thereby well supporting the data transmission of the remote device.
[0196] It should be noted that, in addition to data transferred to the network for the remote device, the relay device may also have its own data sent directly to the network. This data is the data of the traditional first interface, and its first BSR mechanism can fully reuse the existing mechanism, which will not be described in detail. In the embodiment of the present application, the BSR (i.e., the third BSR) related information of the data transferred to the network by the relay device for the remote device needs to be determined according to the configuration mode of the end-to-end bearer between the remote device and the network-side device.
[0197] Step 1002: When the remote device is configured for multi-path transmission and the connection between the remote device and the relay device is a non-ideal backhaul or a standard connection, the relay device determines the relevant information of the third BSR based on the radio link control protocol RLC entity of the first communication interface of the relay device.
[0198] The third BSR is a buffer status report of the first communication interface, and the first communication interface is a communication interface between the terminal and the network side device.
[0199] Furthermore, if the remote device and the relay device have a non-ideal backhaul or standard connection, the relay device is unlikely to obtain timely information about the remote device's PDCP layer data. Therefore, the relay device's third BSR reporting may not take into account the remote device's buffering status as it does in the "ideal backhaul or standard connection" scenario, but may only consider its own buffering status. Therefore, if the remote device is configured for multipath transmission and the remote device and the relay device have a non-ideal backhaul or standard connection, the remote device can determine the relevant information for the third BSR based on the RLC of its own first communication interface.
[0200] It can be seen from steps 1001 and 1002 that in an embodiment of the present application, when the remote device is configured for multi-path transmission, for the relay device, corresponding specific methods for determining the relevant information of the BSR (i.e., the third BSR) of the first communication interface are provided in the case of "an ideal backhaul or a non-standard connection between the remote device and the relay device" and "an ideal backhaul or a non-standard connection between the remote device and the relay device", thereby further improving data transmission performance.
[0201] Optionally, when multiple end-to-end bearers exist between the remote device and the network-side device, one end-to-end bearer corresponds to one Packet Data Convergence Protocol (PDCP) entity;
[0202] In the above step 1001, “the relay device determines, according to the configuration mode of the end-to-end bearer between the remote device and the network-side device, the relevant information of the third BSR of the relay device” includes at least one of the following items I-1 to I-7:
[0203] Item I-1: When the end-to-end bearer corresponding to the target PDCP entity is configured as a non-direct bearer, the relay device counts the arrival of the first data into the trigger condition of the third BSR, and counts the first data into the fourth cache amount of the third BSR, wherein the first data includes the data to be transmitted in the protocol data unit PDU corresponding to the service data unit SDU of the target PDCP entity, and the data in the control PDU of the target PDCP entity, and the target PDCP entity is one of the PDCP entities of the remote device.
[0204] Among them, for non-direct bearer, the data of the bearer is completely transmitted through the non-direct path between the remote device-relay device-network side device. Therefore, if the end-to-end bearer corresponding to the target PDCP entity of the remote device is configured as a non-direct bearer, in item I-1, the arrival of the first data only needs to be counted in the triggering condition of the third BSR, and the second data only needs to be counted in the fourth cache amount of the third BSR.
[0205] Item I-2: When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, duplicate transmission is activated, and the primary path is a direct RLC bearer, the relay device counts the arrival of the second data into the triggering condition of the third BSR and counts the second data into the fourth cache amount, or the relay device counts the arrival of the first data into the triggering condition of the third BSR and counts the first data into the fourth cache amount, wherein the second data includes the data to be transmitted in the PDU corresponding to the SDU of the target PDCP entity.
[0206] Item I-3: When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, the duplicate transmission is activated, and the primary path is a non-direct RLC bearer, the relay device counts the arrival of the second data into the triggering condition of the third BSR and counts the second data into the fourth cache amount, or the relay device counts the arrival of the first data into the triggering condition of the third BSR and counts the first data into the fourth cache amount.
[0207] For items I-2 and I-3, for separated bearers with activated copy transmission, the data of the bearer will be copied and transmitted simultaneously through the direct RLC bearer and the indirect RLC bearer, that is, the remote device's E2E RB has two copies of data, one is directly transmitted to the network side device through the first communication interface, and the other is first transmitted to the relay device through the second communication interface and then to the network side device through the first communication interface of the relay device.
[0208] Therefore, if the end-to-end bearer corresponding to the target PDCP entity of the remote device is configured as a separate bearer and duplicate transmission is activated, the data to be transmitted (i.e., the second data) in the PDU corresponding to the SDU of the target PDCP entity needs to be copied twice, so as to be transmitted simultaneously through the direct RLC bearer and the indirect RLC bearer. However, it should be noted that the data in the control PDU of the target PDCP entity (i.e., the part of the first data other than the second data) is only sent once, i.e., it does not participate in duplicate transmission. Therefore, the data in the control PDU of the target PDCP entity can be transmitted only on the primary path or only on the secondary path, wherein, if the direct RLC bearer is the primary path, the direct RLC bearer is the secondary path and the indirect RLC bearer is the secondary path, and if the indirect RLC bearer is the primary path, the direct RLC bearer is the secondary path. Therefore, the data in the control PDU of the target PDCP entity can be transmitted on one of the direct bearer and the indirect bearer.
[0209] That is, if the end-to-end bearer corresponding to the target PDCP entity of the remote device is configured as a separate bearer and the copy transmission is activated, regardless of whether the main path is a direct RLC bearer or an indirect RLC bearer, the arrival of the data to be transmitted (i.e., the second data) in the PDU corresponding to the SDU of the target PDCP entity needs to be counted in the trigger condition of the first BSR and the trigger condition of the third BSR, and the second data needs to be counted in the third cache amount and the fourth cache amount; and the data in the control PDU of the target PDCP entity (i.e., the part of the first data other than the second data) is counted in the trigger condition of the first BSR or the trigger condition of the third BSR, and the data in the control PDU of the target PDCP entity is counted in the third cache amount or the fourth cache amount.
[0210] In this way, it can be obtained that: when the remote device is configured for multi-path transmission and the remote device and the relay device have an ideal backhaul or a non-standard connection, if the end-to-end bearer corresponding to the target PDCP entity of the remote device is configured as a separate bearer, and the copy transmission is activated, and the main path is a direct RLC bearer or an indirect RLC bearer, then the arrival and data volume of the first data are included in the triggering condition and the third cache amount of the first BSR, and the arrival and data volume of the second data are included in the triggering condition and the fourth cache amount of the third BSR, or, the arrival and data volume of the first data are included in the triggering condition and the fourth cache amount of the third BSR, and the arrival and data volume of the second data are included in the triggering condition and the third cache amount of the first BSR.
[0211] Item I-4: When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, and duplicate transmission is not activated, and the primary path is a direct RLC bearer, and the data volume of the third data is greater than or equal to the third threshold, the relay device counts the arrival of the second data into the triggering condition of the third BSR, and counts the second data into the fourth cache volume, or the relay device counts the arrival of the first data into the triggering condition of the third BSR, and counts the first data into the fourth cache volume, wherein the third data includes the fourth data, the data to be initially transmitted in the non-directly connected layer 2 entity of the remote device, and the data to be initially transmitted in the RLC entity of the first communication interface of the remote device, and the fourth data includes at least one of the data to be initially transmitted in the PDU corresponding to the SDU of the target PDCP entity, the data to be retransmitted, and the data in the control PDU of the target PDCP entity.
[0212] Among them, for the separated bearer, and the copy transmission is not activated, and the main path is a direct RLC bearer, the data of the bearer will be transmitted on the configured main path, that is, the direct RLC bearer, when the amount of cached data to be transmitted is less than the corresponding threshold, and when the amount of cached data to be transmitted is greater than or equal to the corresponding threshold, it can be transmitted on any path, that is, a direct RLC bearer or an indirect RLC bearer, that is: the first data is transmitted on the direct path, and the second data is transmitted on the indirect path, or the first data is transmitted on the indirect path, and the second data is transmitted on the direct path, or the first data is transmitted on both the direct path and the indirect path. Therefore, it can be obtained that in item I-4, the arrival and data amount of the first data can be included in the triggering condition and the fourth cache amount of the third BSR, or the arrival and data amount of the second data can be included in the triggering condition and the fourth cache amount of the third BSR.
[0213] Item I-5: When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, and duplicate transmission is not activated, and the primary path is a non-direct RLC bearer, and the data volume of the third data is less than the fourth threshold, the relay device counts the arrival of the first data into the triggering condition of the third BSR, and counts the first data into the fourth cache volume.
[0214] Item I-6: When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, and duplicate transmission is not activated, and the primary path is a non-direct RLC bearer, and the data volume of the third data is greater than or equal to the fourth threshold, the relay device counts the arrival of the second data in the triggering condition of the third BSR and counts the second data in the fourth cache volume, or the relay device counts the arrival of the first data in the triggering condition of the third BSR and counts the first data in the fourth cache volume.
[0215] For a split bearer with duplicate transmission disabled and an indirect RLC bearer as the primary path, the bearer's data will be transmitted on the configured primary path, i.e., the indirect RLC bearer, when the amount of buffered data to be transmitted is less than a corresponding threshold. When the amount of buffered data to be transmitted is greater than or equal to the corresponding threshold, the bearer's data can be transmitted on either path, i.e., a direct RLC bearer or an indirect RLC bearer. Specifically, the first data may be transmitted on the indirect path, and the second data on the direct path; or the first data may be transmitted on the direct path and the second data on the indirect path; or the first data may be transmitted on both the direct and indirect paths. Therefore, in the case of item I-5, the arrival and data volume of the first data only need to be counted in the triggering condition of the third BSR and the fourth buffer volume. In the case of item I-6, the arrival and data volume of the first data may be counted in the triggering condition of the third BSR and the fourth buffer volume, or the arrival and data volume of the second data may be counted in the triggering condition of the third BSR and the fourth buffer volume.
[0216] Item I-7: When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer and the copy transmission is not activated, the relay device counts the arrival of the first data into the trigger condition of the third BSR and counts the first data into the fourth cache amount.
[0217] It can be seen from item I-7 that if the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer and the copy transmission is not activated, it can be considered that both the main path and the auxiliary path can be transmitted. In this way, the arrival and data volume of the first data can also be included in the triggering conditions of the third BSR and the fourth cache amount.
[0218] Furthermore, items I-1 through I-7 above describe, from the perspective of a single PDCP entity, whether the data arrival and amount in the PDU corresponding to the SDU of that PDCP entity, as well as the data arrival and amount in the control PDU, are included in the triggering conditions and fourth buffer size of the relay device's third BSR, when the remote device and relay device have an ideal backhaul or non-standard connection. The following describes the overall buffer size of the relay device's third BSR in this scenario.
[0219] Optionally, the fourth cache amount is the sum of at least one of the following items J-1 to J-8:
[0220] Item J-1: The data volume of the seventh data, wherein the seventh data includes the data to be transmitted in the PDU corresponding to the SDU of the RLC entity of the first communication interface of the relay device, and the data in the control PDU of the RLC entity.
[0221] It can be seen from item J-1 that when the remote device is configured for multi-path transmission and the remote device and the relay device have an ideal backhaul or a non-standard connection, the fourth cache amount includes the amount of data to be transmitted in the PDU corresponding to the SDU of the RLC entity of all first communication interfaces of the relay device and the amount of data in the control PDU of the RLC entity.
[0222] Item J-2: The amount of first data when the end-to-end bearer corresponding to the target PDCP entity is configured as a non-direct bearer, wherein the first data includes the data to be transmitted in the PDU corresponding to the SDU of the target PDCP entity, and the data in the control PDU of the target PDCP entity, and the target PDCP entity is one of the PDCP entities of the remote device.
[0223] In combination with the relevant content of the above-mentioned item I-1, for example, when the above-mentioned target PDCP entity is the sixteenth PDCP entity, it can be known from J-2 that when the connection between the remote device and the relay device is an ideal backhaul or a non-standard connection, the fourth cache amount also includes the amount of data to be transmitted in the PDU corresponding to the SDU of the sixteenth PDCP entity and the amount of data in the control PDU of the first PDCP entity, wherein the end-to-end bearer configuration corresponding to the sixteenth PDCP entity is a non-direct bearer.
[0224] Item J-3: When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, the copy transmission is activated, and the main path is a direct RLC bearer, the data volume of the second data or the data volume of the first data, wherein the second data includes the data to be transmitted in the PDU corresponding to the SDU of the target PDCP entity.
[0225] Combined with the relevant content of the above-mentioned item I-2, for example, when the above-mentioned target PDCP entity is the tenth PDCP entity, it can be known from J-3 that when the connection between the remote device and the relay device is an ideal backhaul or a non-standard connection, the fourth cache amount also includes the data volume of the data to be transmitted in the PDU corresponding to the SDU of the tenth PDCP entity and the data volume in the control PDU of the tenth PDCP entity, or the data volume of the data to be transmitted in the PDU corresponding to the SDU of the tenth PDCP entity, wherein the end-to-end bearer configuration corresponding to the tenth PDCP entity is: separated bearer, duplicate transmission is activated, and the main path is a direct RLC bearer.
[0226] Item J-4: The data volume of the first data or the data volume of the second data when the end-to-end bearer corresponding to the target PDCP entity is configured as a separated bearer, the duplicate transmission is activated, and the primary path is a non-direct RLC bearer.
[0227] In combination with the relevant content of the above-mentioned item I-3, for example, when the above-mentioned target PDCP entity is the eleventh PDCP entity, it can be known from J-4 that when the connection between the remote device and the relay device is an ideal backhaul or a non-standard connection, the fourth cache amount also includes the data volume of the data to be transmitted in the PDU corresponding to the SDU of the eleventh PDCP entity and the data volume in the control PDU of the eleventh PDCP entity, or the data volume of the data to be transmitted in the PDU corresponding to the SDU of the eleventh PDCP entity, wherein the end-to-end bearer configuration corresponding to the eleventh PDCP entity is: separated bearer, duplicate transmission is activated, and the main path is a non-direct RLC bearer.
[0228] Item J-5: When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer and duplicate transmission is not activated and the main path is a direct RLC bearer, and the data volume of the third data is greater than or equal to the third threshold, the data volume of the second data or the data volume of the first data, wherein the third data includes fourth data, data to be initially transmitted in the non-directly connected layer 2 entity of the remote device, and data to be initially transmitted in the radio link control protocol RLC entity of the first communication interface of the remote device, and the fourth data includes at least one of data to be initially transmitted in the PDU corresponding to the SDU of the target PDCP entity, data to be retransmitted, and data in the control PDU of the target PDCP entity.
[0229] Combined with the relevant content of the above-mentioned item I-4, for example, when the above-mentioned target PDCP entity is the thirteenth PDCP entity, it can be known from J-5 that when the connection between the remote device and the relay device is an ideal backhaul or a non-standard connection, the fourth cache amount also includes the data amount of the data to be transmitted in the PDU corresponding to the SDU of the thirteenth PDCP entity and the data amount in the control PDU of the thirteenth PDCP entity, or the data amount of the data to be transmitted in the PDU corresponding to the SDU of the thirteenth PDCP entity, wherein the end-to-end bearer configuration corresponding to the thirteenth PDCP entity is: separated bearer and no copy transmission is activated and the main path is a direct RLC bearer, and at least one of the data to be initially transmitted, the data to be retransmitted, and the data in the control PDU of the thirteenth PDCP entity in the PDU corresponding to the SDU of the thirteenth PDCP entity, the data to be initially transmitted in the non-directly connected layer 2 entity of the remote device, and the data to be initially transmitted in the RLC entity of the first communication interface of the remote device, the sum of the three data amounts is greater than or equal to the third threshold.
[0230] Item J-6: When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, duplicate transmission is not activated, the main path is a non-direct RLC bearer, and the data volume of the third data is less than the fourth threshold, the data volume of the first data.
[0231] Combined with the relevant content of the aforementioned item I-5, for example, when the above-mentioned target PDCP entity is the seventeenth PDCP entity, it can be known from J-6 that when the connection between the remote device and the relay device is an ideal backhaul or a non-standard connection, the fourth cache amount also includes the amount of data to be transmitted in the PDU corresponding to the SDU of the seventeenth PDCP entity and the amount of data in the control PDU of the seventeenth PDCP entity, wherein the end-to-end bearer configuration corresponding to the seventeenth PDCP entity is: separated bearer and copy transmission is not activated and the main path is a direct RLC bearer, and at least one of the data to be initially transmitted, the data to be retransmitted, and the data in the control PDU of the seventeenth PDCP entity in the PDU corresponding to the SDU of the seventeenth PDCP entity, the data to be initially transmitted in the non-directly connected layer 2 entity of the remote device, and the data to be initially transmitted in the RLC entity of the first communication interface of the remote device, the sum of the three data amounts is less than the fourth threshold.
[0232] Item J-7: When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer and duplicate transmission is not activated and the main path is a non-direct RLC bearer, and the data volume of the third data is greater than or equal to the fourth threshold, the data volume of the first data or the data volume of the second data.
[0233] Combined with the relevant content of the above-mentioned item I-6, for example, when the above-mentioned target PDCP entity is the fourteenth PDCP entity, it can be known from J-7 that when the connection between the remote device and the relay device is an ideal backhaul or a non-standard connection, the fourth cache amount also includes the data amount of the data to be transmitted in the PDU corresponding to the SDU of the fourteenth PDCP entity and the data amount in the control PDU of the fourteenth PDCP entity, or the data amount of the data to be transmitted in the PDU corresponding to the SDU of the fourteenth PDCP entity, wherein the end-to-end bearer configuration corresponding to the fourteenth PDCP entity is: separated bearer and copy transmission is not activated and the main path is a non-direct RLC bearer, and at least one of the data to be initially transmitted, the data to be retransmitted, and the data in the control PDU of the fourteenth PDCP entity in the PDU corresponding to the SDU of the fourteenth PDCP entity, the data to be initially transmitted in the non-directly connected layer 2 entity of the remote device, and the data to be initially transmitted in the RLC entity of the first communication interface of the remote device, the sum of the three data amounts is greater than or equal to the fourth threshold.
[0234] Item J-8: The end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, and the data volume of the first data when the copy transmission is not activated.
[0235] In combination with the relevant content of the aforementioned item I-7, for example, when the above-mentioned target PDCP entity is the fifteenth PDCP entity, it can be known from J-8 that when the connection between the remote device and the relay device is an ideal backhaul or a non-standard connection, the fourth cache amount also includes the amount of data to be transmitted in the PDU corresponding to the SDU of the fifteenth PDCP entity and the amount of data in the control PDU of the fifteenth PDCP entity, wherein the end-to-end bearer configuration of the fifteenth PDCP entity is: separate bearer, and copy transmission is not activated.
[0236] Optionally, in step 1002, “the relay device determines relevant information of the third BSR according to the RLC entity of the first communication interface of the relay device” includes:
[0237] The relay device counts the arrival of data of the RLC entity of the first communication interface of the relay device into the trigger condition of the third BSR, and counts the seventh data into the data cache amount in the third BSR, wherein the seventh data includes the data to be transmitted in the PDU corresponding to the SDU of the RLC entity of the first communication interface of the relay device, and the data in the control PDU of the RLC entity.
[0238] Among them, when the remote device is configured for multi-path transmission and the remote device and the relay device have a non-ideal backhaul or standard connection, the relay device needs to first receive the uplink data of the remote device from the remote device through the second communication interface before it can use these data to trigger or report the BSR (i.e., the third BSR) of the corresponding uplink first communication interface. These data are generally cached in the RLC entity of the first communication interface of the relay device. Therefore, in this case, the triggering conditions and cache amount calculation of the third BSR of the relay device only include the data to be transmitted that has arrived at the RLC entity of the first communication interface of the relay device (i.e., the data to be transmitted in the PDU corresponding to the SDU and the data in the control PDU). The third BSR of the relay device is triggered and calculated according to the priority of these data to be transmitted and the LCG configuration.
[0239] Optionally, the method further includes:
[0240] When the remote device is connected to the relay device via a second communication interface and the relay device is configured in a network-side device scheduling mode, the relay device performs at least one of the following K-1 to K-5:
[0241] Item K-1: the relay device counts the arrival of data of the RLC entity of the second communication interface of the relay device into a trigger condition of a fourth BSR of the relay device, and counts eighth data into a data cache amount of the fourth BSR, wherein the fourth BSR is a cache status report of the second communication interface, and the eighth data includes to-be-transmitted data of a PDU corresponding to an SDU of the RLC entity of the second communication interface of the relay device, and data in a control PDU of the RLC entity, where the second communication interface is a communication interface between terminals;
[0242] Item K-2: Prohibits the processing of the fourth BSR;
[0243] K-3: only the fourth BSR that is filled is retained;
[0244] K-4: Do not configure the periodic fourth BSR;
[0245] Item K-5: Do not configure retransmission of the fourth BSR.
[0246] When the remote device and the relay device are connected via the second communication interface and the relay device is configured in network-side device scheduling mode, the relay device must first receive downlink data from the remote device from the network-side device via its first communication interface and then send the downlink data to the remote device via the second communication interface. Therefore, only when the downlink data from the remote device reaches the RLC entity of the second communication interface of the relay device will the BSR (i.e., the fourth BSR) reporting and buffer size calculation of the second communication interface of the relay device be triggered.
[0247] In particular, since these data are sent by the network-side device to the relay device, the network-side device also has a basic grasp of the amount of data that the relay device needs to send to the remote device through the second communication interface. Therefore, the reporting frequency and triggering of the fourth BSR can be reduced, such as prohibiting the regular fourth BSR, or retaining only the padding fourth BSR, or not configuring the periodic fourth BSR, or not configuring the retransmission (retx) fourth BSR, etc.
[0248] In summary, the specific implementation of the cache status report processing method of the embodiment of the present application can be any one of the following implementation modes 1 to 3.
[0249] It should be noted that in the current R17 technical solution and SL Relay architecture, the remote UE only switches between the direct link and the indirect link, and does not maintain both paths simultaneously. When a normal UE performs dual connection (DC) operation, although it also maintains two paths, the Master Cell Group (MCG) and the Secondary Cell Group (SCG), and can configure various bearer types including split bearers, when the UE reports the BSR to the MCG and SCG, it uses the Uu BSR format and sends it to the two base stations separately.
[0250] In R18 SL Relay multipath transmission, when a PC5 interface is used between two UEs, if the Remote UE uses SL resource allocation (RA) mode 1 on the PC5 interface between the Remote UE and the relay device (Relay UE), that is, the Remote UE reports the data buffer it needs to transmit on the PC5 interface, and the base station dynamically schedules PC5 resources. In this case, BSR reporting is required on both the Remote UE's Uu interface and the PC5 interface. The two reported BSRs are also related, especially for split bearers. There is currently no solution for how to implement this. In addition, if the interface between the two UEs is ideal, there is currently no specific solution for Uu BSR reporting by the Remote UE and Relay UE.
[0251] The following implementation modes 1 to 3 of the present application can solve the problems described here.
[0252] Implementation Method 1
[0253] The main problem to be solved by this embodiment is: when the Remote UE is configured with multipath transmission, the PC5 interface is between the Remote UE and the Relay UE, and the Remote UE is configured with SL RA mode 1 (that is, the PC5 interface resources adopt the base station scheduling mode), the Remote UE is involved in Uu BSR reporting and SL BSR reporting at the same time. How to accurately perform each report so that the network side can better allocate appropriate Uu UL resources and PC5 interface resources to the Remote UE according to the BSR situation for Remote UE data transmission.
[0254] When multipath transmission is configured for the Remote UE, the end-to-end bearer between the Remote UE and the base station has the following configuration modes:
[0255] Direct bearer: The data of this bearer is transmitted entirely through the direct path between the Remote UE and the base station.
[0256] Indirect bearer: The data of this bearer is transmitted entirely through the indirect path between the remote UE, relay UE, and base station. The remote UE's E2E RB data must first be transmitted to the relay UE through the PC5 interface, and then finally transmitted to the gNB through the Uu interface between the relay UE and the gNB.
[0257] Split bearer with duplication activation: The bearer data will be replicated and transmitted simultaneously over both the direct and indirect paths. This means that the remote UE's E2E RB has two replicated data: one is transmitted directly over the Uu interface to the gNB, and the other is sent to the relay UE via the PC5 interface and then to the base station via the relay Uu interface.
[0258] Split bearer without duplication and primary path on direct RLC bearer: When the amount of buffered data to be transmitted is less than the corresponding threshold, the data of this bearer will be transmitted on the configured primary path, i.e., direct RLC bearer. When the amount of buffered data to be transmitted is greater than or equal to the corresponding threshold, the data can be transmitted on any path, i.e., direct RLC bearer or indirect RLC bearer.
[0259] Split bearer without duplication & primary path on indirect: When the amount of buffered data to be transmitted is less than the corresponding threshold, the data of this bearer will be transmitted on the configured primary path, i.e., the indirect RLC bearer. When the amount of buffered data to be transmitted is greater than or equal to the corresponding threshold, the data can be transmitted on any path, i.e., direct RLC bearer or indirect RLC bearer.
[0260] In addition, when the Remote UE is configured for multi-path transmission, the end-to-end bearer between the Remote UE and the base station may include multiple bearers, each of which corresponds to a PDCP, and the end-to-end bearer can be configured as one of the modes described above. Therefore, when the Remote UE is configured for multi-path transmission, the Remote UE may, based on the configuration of the end-to-end bearers corresponding to different PDCP entities, take at least one of the following to determine the "triggering conditions and cache amount of the Uu BSR, and the triggering conditions and cache amount of the SL BSR." That is, when the Remote UE has multiple end-to-end bearers, the end-to-end bearer corresponding to any one of the PDCPs shall be classified according to the triggering conditions and the cache amount calculated according to the following 1.1 to 1.5:
[0261] 1.1 If the end-to-end bearer configuration corresponding to the target PDCP entity is a direct bearer type, the arrival of the first data is only counted in the triggering condition of the Remote UE Uu BSR and the first data is only counted in the buffer size of the Remote UE Uu BSR, where the first data includes the to-be-transmitted data in the PDU corresponding to the SDU of the target PDCP entity and the data in the control PDU, and the target PDCP entity is one of the PDCP entities of the Remote UE;
[0262] 1.2 If the end-to-end bearer configuration corresponding to the target PDCP entity is of the Indirect bearer type, the arrival of the first data is only counted in the triggering condition of the Remote UE SL BSR, and the first data is only counted in the buffer size of the Remote UE SL BSR;
[0263] 1.3 If the end-to-end bearer configuration corresponding to the target PDCP entity is of the Split bearer with duplication activation type, and the primary path is a direct RLC bearer or an indirect RLC bearer, then the arrival of the first data is counted in the triggering condition of the Remote UE Uu BSR, and the first data is counted in the buffer capacity of the Remote UE Uu BSR, and the arrival of the second data is counted in the triggering condition of the Remote UE SL BSR, and the second data is counted in the buffer capacity of the Remote UE SL BSR; or, the arrival of the second data is counted in the triggering condition of the Remote UE Uu BSR, and the second data is counted in the buffer capacity of the Remote UE Uu BSR, and the arrival of the first data is counted in the triggering condition of the Remote UE SL BSR, and the first data is counted in the buffer capacity of the Remote UE SL BSR, where the second data includes the data to be transmitted in the PDU corresponding to the SDU of the target PDCP;
[0264] It should be noted here that, when duplicate transmission is activated, the data to be transmitted in the PDU corresponding to the PDCP SDU can be transmitted in both the direct RLC bearer and the indirect RLC bearer; while the data in the PDCP control PDU is sent only once, that is, it does not participate in duplicate transmission, so it can be transmitted only on the primary path. Therefore, if the primary path is configured as a direct RLC bearer at this time, the arrival of the data in the control PDU of the target PDCP entity is counted in the triggering condition of the Remote UE Uu BSR, and the data in the control PDU of the target PDCP entity is counted in the buffer amount of the Remote UE Uu BSR. If the primary path is configured as an indirect RLC bearer at this time, the arrival of the data in the control PDU of the target PDCP entity is counted in the triggering condition of the Remote UE SL BSR, and the data in the control PDU of the target PDCP entity is counted in the buffer amount of the Remote UE SL BSR.
[0265] Alternatively, the data in the control PDU of the target PDCP entity can also be transmitted only on the secondary path. If the Secondary path is configured as a non-direct RLC bearer at this time, the arrival of the data in the control PDU of the target PDCP entity is counted in the triggering condition of the Remote UE SL BSR, and the data in the control PDU of the target PDCP entity can be counted in the cache amount of the Remote UE SL BSR. If the Secondary path is configured as a direct RLC bearer at this time, the arrival of the data in the control PDU of the target PDCP entity is counted in the triggering condition of the Remote UE Uu BSR, and the data in the control PDU of the target PDCP entity is counted in the cache amount of the Remote UE Uu BSR.
[0266] 1.4 If the end-to-end bearer configuration corresponding to the target PDCP entity is Split bearer without duplication activation & primary path on direct, then if the sum of the fourth data, the amount of data to be initially transmitted in the remote device's Uu RLC buffer, and the amount of data to be initially transmitted in the remote device's PC5 RLC buffer is less than the first threshold, the arrival of the first data is only counted in the triggering condition of the Remote UE Uu BSR, and the first data is only counted in the buffer capacity of the Remote UE Uu BSR. Here, the fourth data includes at least one of the data to be initially transmitted, the data to be retransmitted, and the data in the control PDU of the target PDCP entity in the PDU corresponding to the SDU of the target PDCP entity.
[0267] When the sum of the above three is greater than or equal to the first threshold, the arrival of the first data is counted in the triggering condition of the Remote UE Uu BSR, and the first data is counted in the buffer capacity of the Remote UE Uu BSR, the arrival of the second data is counted in the triggering condition of the Remote UE SL BSR, and the second data is counted in the buffer capacity of the Remote UE SL BSR, or, the arrival of the second data is counted in the triggering condition of the Remote UE Uu BSR, the second data is counted in the buffer capacity of the Remote UE Uu BSR, the arrival of the first data is counted in the triggering condition of the Remote UE SL BSR, and the first data is counted in the buffer capacity of the Remote UE SL BSR, or, the arrival of the first data is counted in the triggering condition of the Remote UE Uu BSR and the triggering condition of the Remote UE SL BSR, and the first data is counted in the buffer capacity of the Remote UE Uu BSR and the buffer capacity of the Remote UE SL BSR;
[0268] 1.5 If the end-to-end bearer configuration corresponding to the target PDCP entity is Split bearer without duplication activation & primary path on Indirect, then if the sum of the fourth data, the amount of data to be initially transmitted in the Uu RLC buffer of the remote device, and the amount of data to be initially transmitted in the PC5 RLC buffer of the remote device is less than the second threshold, the arrival of the first data is only counted in the triggering condition of the Remote UE SL BSR, and the first data is only counted in the buffer capacity of the Remote UE SL BSR;
[0269] When the sum of the above three is greater than or equal to the second threshold, the arrival of the first data is counted in the triggering condition of the Remote UE Uu BSR, and the first data is counted in the cache amount of the Remote UE Uu BSR, the arrival of the second data is counted in the triggering condition of the Remote UE SL BSR, and the second data is counted in the cache amount of the Remote UE SL BSR, or, the arrival of the second data is counted in the triggering condition of the Remote UE Uu BSR, the second data is counted in the cache amount of the Remote UE Uu BSR, the arrival of the first data is counted in the triggering condition of the Remote UE SL BSR, and the first data is counted in the cache amount of the Remote UE SL BSR, or, the arrival of the first data is counted in the triggering condition of the Remote UE Uu BSR and the triggering condition of the Remote UE SL BSR, and the first data is counted in the cache amount of the Remote UE Uu BSR and the cache amount of the Remote UE SL BSR.
[0270] As described in 1.1 to 1.5 above, when the Remote UE is configured with multipath transmission, the PC5 interface between the Remote UE and the Relay UE is used, and the Remote UE is configured with SL RA mode 1, the buffer capacity of the Remote UE Uu BSR includes at least one of the following:
[0271] The sum of the amount of data to be transmitted in the PDU corresponding to the SDU of the RLC entity on the Uu interface of the Remote UE and the amount of data in the control PDU of the RLC entity;
[0272] The sum of the amount of data to be transmitted in the PDU corresponding to the SDU of the first PDCP entity and the amount of data in the control PDU of the first PDCP entity, where the end-to-end bearer corresponding to the first PDCP is a direct bearer;
[0273] The sum of the amount of data to be transmitted in the PDU corresponding to the SDU of the second PDCP entity and the amount of data in the control PDU of the second PDCP entity, or the amount of data to be transmitted in the PDU corresponding to the SDU of the second PDCP entity, where the end-to-end bearer corresponding to the second PDCP entity is a split bearer with duplicate transmission activated and the primary path is a direct RLC bearer;
[0274] The sum of the amount of data to be transmitted in the PDU corresponding to the SDU of the third PDCP entity and the amount of data in the control PDU of the third PDCP entity, or the amount of data to be transmitted in the PDU corresponding to the SDU of the third PDCP entity, where the end-to-end bearer corresponding to the third PDCP entity is a split bearer with duplicate transmission activated and the primary path is an indirect RLC bearer;
[0275] the sum of the amount of data to be transmitted in the PDU corresponding to the SDU of the fourth PDCP entity and the amount of data in the control PDU of the fourth PDCP entity, wherein the end-to-end bearer corresponding to the fourth PDCP entity is configured as a split bearer, duplicate transmission is not activated, and the primary path is a direct RLC bearer, and the sum of at least one item of the data to be initially transmitted, the data to be retransmitted, and the data in the control PDU of the fourth PDCP entity, the data to be initially transmitted in the non-directly connected layer 2 entity of the Remote UE, and the data to be initially transmitted in the Uu RLC entity of the Remote UE is less than a first threshold;
[0276] the sum of the amount of data to be transmitted in the PDU corresponding to the SDU of the fifth PDCP entity and the amount of data in the control PDU of the fifth PDCP entity, or the amount of data to be transmitted in the PDU corresponding to the SDU of the fifth PDCP entity, wherein the end-to-end bearer corresponding to the fifth PDCP entity is configured as a split bearer and duplicate transmission is not activated and the primary path is a direct RLC bearer, and the sum of at least one item of the data to be initially transmitted, the data to be retransmitted, and the data in the control PDU of the fifth PDCP entity in the PDU corresponding to the SDU of the fifth PDCP entity, the data to be initially transmitted in the non-directly connected layer 2 entity of the Remote UE, and the data to be initially transmitted in the Uu RLC entity of the Remote UE is greater than or equal to the first threshold;
[0277] The sum of the amount of data to be transmitted in the PDU corresponding to the SDU of the sixth PDCP entity and the amount of data in the control PDU of the sixth PDCP entity, or the amount of data to be transmitted in the PDU corresponding to the SDU of the sixth PDCP entity, wherein the end-to-end bearer corresponding to the sixth PDCP entity is configured as a separate bearer and the copy transmission is not activated and the main path is a non-direct RLC bearer, and the sum of at least one item of the data to be initially transmitted, the data to be retransmitted, and the data in the control PDU of the sixth PDCP entity in the PDU corresponding to the SDU of the sixth PDCP entity, the data to be initially transmitted in the non-directly connected layer 2 entity of the Remote UE and the data to be initially transmitted in the Uu RLC entity of the Remote UE is greater than or equal to the second threshold.
[0278] Similarly, from the content described in 1.1 to 1.5 above, it can be seen that when the Remote UE is configured with multipath transmission, the PC5 interface between the Remote UE and the Relay UE is used, and the Remote UE is configured with SL RA mode 1, the buffer size of the Remote UE SL BSR is the sum of at least one of the following items:
[0279] The sum of the amount of data to be transmitted in the PDU corresponding to the SDU of the RLC entity of the PC5 interface of the Remote UE and the amount of data in the control PDU of the RLC entity;
[0280] The sum of the amount of data to be transmitted in the PDU corresponding to the SDU of the seventh PDCP entity and the amount of data in the control PDU of the seventh PDCP entity, where the end-to-end bearer corresponding to the seventh PDCP is an indirect bearer;
[0281] The sum of the amount of data to be transmitted in the PDU corresponding to the SDU of the second PDCP entity and the amount of data in the control PDU of the second PDCP entity, or the amount of data to be transmitted in the PDU corresponding to the SDU of the second PDCP entity, where the end-to-end bearer corresponding to the second PDCP entity is a split bearer with duplicate transmission activated and the primary path is a direct RLC bearer;
[0282] The sum of the amount of data to be transmitted in the PDU corresponding to the SDU of the third PDCP entity and the amount of data in the control PDU of the third PDCP entity, or the amount of data to be transmitted in the PDU corresponding to the SDU of the third PDCP entity, where the end-to-end bearer corresponding to the third PDCP entity is a split bearer with duplicate transmission activated and the primary path is an indirect RLC bearer;
[0283] the sum of the amount of data to be transmitted in the PDU corresponding to the SDU of the fifth PDCP entity and the amount of data in the control PDU of the fifth PDCP entity, or the amount of data to be transmitted in the PDU corresponding to the SDU of the fifth PDCP entity, wherein the end-to-end bearer corresponding to the fifth PDCP entity is configured as a split bearer and duplicate transmission is not activated and the primary path is a direct RLC bearer, and the sum of at least one item of the data to be initially transmitted, the data to be retransmitted, and the data in the control PDU of the fifth PDCP entity in the PDU corresponding to the SDU of the fifth PDCP entity, the data to be initially transmitted in the non-directly connected layer 2 entity of the Remote UE, and the data to be initially transmitted in the Uu RLC entity of the Remote UE is greater than or equal to the first threshold;
[0284] the sum of the amount of data to be transmitted in the PDU corresponding to the SDU of the sixth PDCP entity and the amount of data in the control PDU of the sixth PDCP entity, or the amount of data to be transmitted in the PDU corresponding to the SDU of the sixth PDCP entity, wherein the end-to-end bearer corresponding to the sixth PDCP entity is configured as a split bearer and duplicate transmission is not activated and the primary path is a non-direct RLC bearer, and the sum of at least one item of the data to be initially transmitted, the data to be retransmitted, and the data in the control PDU of the sixth PDCP entity in the PDU corresponding to the SDU of the sixth PDCP entity, the data to be initially transmitted in the non-directly connected layer 2 entity of the Remote UE, and the data to be initially transmitted in the Uu RLC entity of the Remote UE is greater than or equal to the second threshold;
[0285] The sum of the amount of data to be transmitted in the PDU corresponding to the SDU of the eighth PDCP entity and the amount of data in the control PDU of the eighth PDCP entity, wherein the end-to-end bearer corresponding to the eighth PDCP entity is configured as a separate bearer and the copy transmission is not activated and the main path is a non-direct RLC bearer, and the sum of at least one item of the data to be initially transmitted, the data to be retransmitted, and the data in the control PDU of the eighth PDCP entity, the data to be initially transmitted in the non-directly connected layer 2 entity of the Remote UE, and the data to be initially transmitted in the Uu RLC entity of the Remote UE is less than the second threshold.
[0286] In addition, the reporting of Uu BSR or SL BSR still follows the configuration of the logical channel group (LCG), that is, for the bearers belonging to the same LCG, their data volumes are summed and finally reported as the buffer size of the LCG.
[0287] Implementation Method 2
[0288] In the U2N Relay architecture, a typical scenario involves the Remote UE and Relay UE being connected via an ideal connection (i.e., ideal backhaul) or a non-standardized interface. In this scenario, both the Remote UE and Relay UE are in the Radio Resource Control (RRC) Connected state in the multipath architecture. Both UEs must report UL BSRs to the base station to facilitate timely scheduling of their UL data, thereby effectively supporting the Remote UE's data transmission.
[0289] It should be noted that, in addition to forwarding data to the network for the Remote UE, the Relay UE may also have its own data sent directly to the network. This data is traditional Uu data, and its Uu BSR mechanism can fully reuse existing mechanisms, so this will not be explained in detail. Furthermore, a Relay UE may support more than one Remote UE. In this case, the data volume of each Remote UE can be calculated as follows. The data volume of multiple Remote UEs can be added together. Therefore, this example uses a single Remote UE as an example.
[0290] Among them, when the Remote UE is configured for multi-path transmission, the end-to-end bearer between the Remote UE and the base station may include multiple bearers, each of which corresponds to a PDCP, and the end-to-end bearer can be configured as one of the modes described above. Therefore, when the Remote UE is configured for multi-path transmission, at least one of the following items can be taken to determine the "triggering conditions and cache amount of the Remote UE Uu BSR, and the triggering condition cache amount of the Relay UE Uu BSR" based on the configuration of the end-to-end bearers corresponding to different PDCP entities. That is, when the Remote UE has multiple end-to-end bearers, the end-to-end bearers corresponding to any one of the PDCPs shall be classified according to the triggering conditions and the cache amount shall be calculated according to the contents described in 2.1 to 2.6 below:
[0291] 2.1 If the end-to-end bearer configuration corresponding to the target PDCP entity is a direct bearer type, the arrival of the first data is only counted in the triggering condition of the Remote UE Uu BSR, and the first data is only counted in the buffer size of the Remote UE Uu BSR, where the first data includes the to-be-transmitted data in the PDU corresponding to the SDU of the target PDCP entity and the data in the control PDU, and the target PDCP entity is one of the PDCP entities of the Remote UE;
[0292] 2.2 If the end-to-end bearer corresponding to the target PDCP entity is configured as an Indirect bearer type, the arrival of the first data is only counted in the triggering condition of the Relay UE Uu BSR, and the first data is only counted in the buffer size of the Relay UE Uu BSR;
[0293] 2.3 If the end-to-end bearer configuration corresponding to the target PDCP entity is of the Split bearer with duplication activation type, and the primary path is a direct RLC bearer or an indirect RLC bearer, the arrival of the first data is counted in the triggering condition of the Remote UE Uu BSR, and the first data is counted in the buffer capacity of the Remote UE Uu BSR, and the arrival of the second data is counted in the triggering condition of the Relay UE Uu BSR, and the second data is counted in the buffer capacity of the Relay UE Uu BSR; or, the arrival of the second data is counted in the triggering condition of the Remote UE Uu BSR, and the second data is counted in the buffer capacity of the Remote UE Uu BSR, and the arrival of the first data is counted in the triggering condition of the Relay UE Uu BSR, and the first data is counted in the buffer capacity of the Relay UE Uu BSR, where the second data includes the data to be transmitted in the PDU corresponding to the SDU of the target PDCP;
[0294] It should be noted here that, when duplicate transmission is activated, the data to be transmitted in the PDU corresponding to the PDCP SDU can be transmitted in both the direct RLC bearer and the indirect RLC bearer; while the data in the PDCP control PDU is sent only once, that is, it does not participate in duplicate transmission, so it can be transmitted only on the primary path. Therefore, if the primary path is configured as a direct RLC bearer at this time, the arrival of the data in the control PDU of the target PDCP entity is counted in the triggering condition of the Remote UE Uu BSR, and the data in the control PDU of the target PDCP entity is counted in the buffer amount of the Remote UE Uu BSR. If the primary path is configured as an indirect RLC bearer at this time, the arrival of the data in the control PDU of the target PDCP entity is counted in the triggering condition of the Relay UE Uu BSR, and the data in the control PDU of the target PDCP entity is counted in the buffer amount of the Relay UE Uu BSR.
[0295] Alternatively, the data in the control PDU of the target PDCP entity can also be transmitted only on the secondary path. If the Secondary path is configured as a non-direct RLC bearer at this time, the arrival of the data in the control PDU of the target PDCP entity is counted in the triggering condition of the Relay UE Uu BSR, and the data in the control PDU of the target PDCP entity can be counted in the cache amount of the Relay UE Uu BSR. If the Secondary path is configured as a direct RLC bearer at this time, the arrival of the data in the control PDU of the target PDCP entity is counted in the triggering condition of the Remote UE Uu BSR, and the data in the control PDU of the target PDCP entity is counted in the cache amount of the Remote UE Uu BSR.
[0296] 2.4 If the end-to-end bearer configuration corresponding to the target PDCP entity is Split bearer without duplication activation & primary path on direct, then if the sum of the fourth data, the amount of data to be initially transmitted in the remote device's Uu RLC buffer, and the amount of data to be initially transmitted in the remote device's PC5 RLC buffer is less than the first threshold, the arrival of the first data is only counted in the triggering condition of the Remote UE Uu BSR, and the first data is only counted in the buffer capacity of the Remote UE Uu BSR. Here, the fourth data includes at least one of the data to be initially transmitted, the data to be retransmitted, and the data in the control PDU of the target PDCP entity in the PDU corresponding to the SDU of the target PDCP entity.
[0297] When the sum of the above three is greater than or equal to the first threshold, the arrival of the first data is counted in the triggering condition of the Remote UE Uu BSR, and the first data is counted in the buffer capacity of the Remote UE Uu BSR. The arrival of the second data is counted in the triggering condition of the Relay UE Uu BSR, and the second data is counted in the buffer capacity of the Relay UE Uu BSR. Alternatively, the arrival of the second data is counted in the triggering condition of the Remote UE Uu BSR, and the second data is counted in the buffer capacity of the Remote UE Uu BSR. The arrival of the first data is counted in the triggering condition of the Relay UE Uu BSR, and the first data is counted in the buffer capacity of the Relay UE Uu BSR. Alternatively, the arrival of the first data is counted in the triggering condition of the Remote UE Uu BSR and the triggering condition of the Relay UE Uu BSR, and the first data is counted in the buffer capacity of the Relay UE Uu BSR. Alternatively, the arrival of the first data is counted in both the triggering condition of the Remote UE Uu BSR and the triggering condition of the Relay UE Uu BSR, and the first data is counted in both the buffer capacity of the Remote UE Uu BSR and the buffer capacity of the Relay UE Uu BSR.
[0298] 2.5 If the end-to-end bearer configuration corresponding to the target PDCP entity is Split bearer without duplication activation & primary path on Indirect, then if the sum of the fourth data, the amount of data to be initially transmitted in the remote device's Uu RLC buffer, and the amount of data to be initially transmitted in the remote device's PC5 RLC buffer is less than the second threshold, the arrival of the first data is only counted in the triggering condition of the Relay UE Uu BSR, and the first data is only counted in the buffer capacity of the Relay UE Uu BSR;
[0299] When the sum of the above three is greater than or equal to the second threshold, the arrival of the first data is counted in the triggering condition of the Remote UE Uu BSR, and the first data is counted in the cache capacity of the Remote UE Uu BSR. The arrival of the second data is counted in the triggering condition of the Relay UE Uu BSR, and the second data is counted in the cache capacity of the Relay UE Uu BSR. Alternatively, the arrival of the second data is counted in the triggering condition of the Remote UE Uu BSR, and the second data is counted in the cache capacity of the Remote UE Uu BSR. The arrival of the first data is counted in the triggering condition of the Relay UE Uu BSR, and the first data is counted in the cache capacity of the Relay UE Uu BSR. Alternatively, the arrival of the first data is counted in the triggering condition of the Remote UE Uu BSR and the triggering condition of the Relay UE Uu BSR, and the first data is counted in the cache capacity of the Relay UE Uu BSR. Alternatively, the arrival of the first data is counted in the triggering condition of the Remote UE Uu BSR and the triggering condition of the Relay UE Uu BSR, and the first data is counted in the cache capacity of the Remote UE Uu BSR and the cache capacity of the Relay UE Uu BSR.
[0300] 2.6 If the end-to-end bearer corresponding to the target PDCP entity is configured as a separated bearer and duplicate transmission is not activated, it can be considered that both the primary path and the secondary path can be transmitted. In this way, the arrival of the first data can be included in the triggering conditions of the Remote UE Uu BSR and the triggering conditions of the Relay UE Uu BSR, and the first data can be included in the cache amount of the Remote UE Uu BSR and the cache amount of the Relay UE Uu BSR.
[0301] As described in 2.1 to 2.6 above, when the Remote UE is configured with multipath transmission and the connection between the Remote UE and the Relay UE is an ideal backhaul or a non-standardized connection, the buffer capacity of the Remote UE Uu BSR includes at least one of the following:
[0302] The sum of the amount of data to be transmitted in the PDU corresponding to the SDU of the RLC entity on the Uu interface of the Remote UE and the amount of data in the control PDU of the RLC entity;
[0303] The sum of the amount of data to be transmitted in the PDU corresponding to the SDU of the ninth PDCP entity and the amount of data in the control PDU of the ninth PDCP entity, where the end-to-end bearer corresponding to the ninth PDCP is a direct bearer;
[0304] The sum of the amount of data to be transmitted in the PDU corresponding to the SDU of the tenth PDCP entity and the amount of data in the control PDU of the tenth PDCP entity, or the amount of data to be transmitted in the PDU corresponding to the SDU of the tenth PDCP entity, where the end-to-end bearer corresponding to the tenth PDCP entity is a split bearer with duplicate transmission activated and the primary path is a direct RLC bearer;
[0305] The sum of the amount of data to be transmitted in the PDU corresponding to the SDU of the eleventh PDCP entity and the amount of data in the control PDU of the eleventh PDCP entity, or the amount of data to be transmitted in the PDU corresponding to the SDU of the eleventh PDCP entity, where the end-to-end bearer corresponding to the eleventh PDCP entity is a split bearer with duplicate transmission activated and the primary path is an indirect RLC bearer;
[0306] the sum of the amount of data to be transmitted in the PDU corresponding to the SDU of the twelfth PDCP entity and the amount of data in the control PDU of the twelfth PDCP entity, wherein the end-to-end bearer corresponding to the twelfth PDCP entity is configured as a split bearer, duplicate transmission is not activated, and the primary path is a direct RLC bearer, and the sum of at least one item of the data to be initially transmitted, the data to be retransmitted, and the data in the control PDU of the twelfth PDCP entity, the data to be initially transmitted in the non-directly connected layer 2 entity of the Remote UE, and the data to be initially transmitted in the Uu RLC entity of the Remote UE is less than a third threshold;
[0307] the sum of the amount of data to be transmitted in the PDU corresponding to the SDU of the thirteenth PDCP entity and the amount of data in the control PDU of the thirteenth PDCP entity, or the amount of data to be transmitted in the PDU corresponding to the SDU of the thirteenth PDCP entity, wherein the end-to-end bearer corresponding to the thirteenth PDCP entity is configured as a separate bearer and duplicate transmission is not activated and the primary path is a direct RLC bearer, and the sum of at least one item of the data to be initially transmitted, the data to be retransmitted, and the data in the control PDU of the thirteenth PDCP entity, the data to be initially transmitted in the non-directly connected layer 2 entity of the Remote UE, and the data to be initially transmitted in the Uu RLC entity of the Remote UE is greater than or equal to a third threshold;
[0308] the sum of the amount of data to be transmitted in the PDU corresponding to the SDU of the fourteenth PDCP entity and the amount of data in the control PDU of the fourteenth PDCP entity, or the amount of data to be transmitted in the PDU corresponding to the SDU of the fourteenth PDCP entity, wherein the end-to-end bearer corresponding to the fourteenth PDCP entity is configured as a separate bearer and duplicate transmission is not activated and the primary path is a non-direct RLC bearer, and the sum of at least one item of the data to be initially transmitted, the data to be retransmitted, and the data in the control PDU of the fourteenth PDCP entity, the data to be initially transmitted in the non-directly connected layer 2 entity of the Remote UE, and the data to be initially transmitted in the Uu RLC entity of the Remote UE is greater than or equal to a fourth threshold;
[0309] The sum of the amount of data to be transmitted in the PDU corresponding to the SDU of the fifteenth PDCP entity and the amount of data in the control PDU of the tenth PDCP entity, wherein the end-to-end bearer corresponding to the fifteenth PDCP entity is a separated bearer and copy transmission is not activated.
[0310] Similarly, from the content described in 2.1 to 2.6 above, it can be seen that when the Remote UE is configured with multipath transmission and the connection between the Remote UE and the Relay UE is an ideal backhaul or a non-standardized connection, the buffer size of the Relay UE Uu BSR is the sum of at least one of the following items:
[0311] The sum of the amount of data to be transmitted in the PDU corresponding to the SDU of the RLC entity of the Uu interface of the Relay UE and the amount of data in the control PDU of the RLC entity;
[0312] The sum of the amount of data to be transmitted in the PDU corresponding to the SDU of the sixteenth PDCP entity and the amount of data in the control PDU of the sixteenth PDCP entity, where the end-to-end bearer corresponding to the sixteenth PDCP is an indirect bearer;
[0313] The sum of the amount of data to be transmitted in the PDU corresponding to the SDU of the tenth PDCP entity and the amount of data in the control PDU of the tenth PDCP entity, or the amount of data to be transmitted in the PDU corresponding to the SDU of the tenth PDCP entity, where the end-to-end bearer corresponding to the tenth PDCP entity is a split bearer with duplicate transmission activated and the primary path is a direct RLC bearer;
[0314] The sum of the amount of data to be transmitted in the PDU corresponding to the SDU of the eleventh PDCP entity and the amount of data in the control PDU of the eleventh PDCP entity, or the amount of data to be transmitted in the PDU corresponding to the SDU of the eleventh PDCP entity, where the end-to-end bearer corresponding to the eleventh PDCP entity is a split bearer with duplicate transmission activated and the primary path is an indirect RLC bearer;
[0315] the sum of the amount of data to be transmitted in the PDU corresponding to the SDU of the thirteenth PDCP entity and the amount of data in the control PDU of the thirteenth PDCP entity, or the amount of data to be transmitted in the PDU corresponding to the SDU of the thirteenth PDCP entity, wherein the end-to-end bearer corresponding to the thirteenth PDCP entity is configured as a separate bearer and duplicate transmission is not activated and the primary path is a direct RLC bearer, and the sum of at least one item of the data to be initially transmitted, the data to be retransmitted, and the data in the control PDU of the thirteenth PDCP entity, the data to be initially transmitted in the non-directly connected layer 2 entity of the Remote UE, and the data to be initially transmitted in the Uu RLC entity of the Remote UE is greater than or equal to a third threshold;
[0316] the sum of the amount of data to be transmitted in the PDU corresponding to the SDU of the fourteenth PDCP entity and the amount of data in the control PDU of the fourteenth PDCP entity, or the amount of data to be transmitted in the PDU corresponding to the SDU of the fourteenth PDCP entity, wherein the end-to-end bearer corresponding to the fourteenth PDCP entity is configured as a separate bearer and duplicate transmission is not activated and the primary path is a non-direct RLC bearer, and the sum of at least one item of the data to be initially transmitted, the data to be retransmitted, and the data in the control PDU of the fourteenth PDCP entity, the data to be initially transmitted in the non-directly connected layer 2 entity of the Remote UE, and the data to be initially transmitted in the Uu RLC entity of the Remote UE is greater than or equal to a fourth threshold;
[0317] the sum of the amount of data to be transmitted in the PDU corresponding to the SDU of the seventeenth PDCP entity and the amount of data in the control PDU of the seventeenth PDCP entity, wherein the end-to-end bearer corresponding to the seventeenth PDCP entity is configured as a split bearer, duplicate transmission is not activated, and the primary path is an indirect RLC bearer, and at least one item of the data to be initially transmitted, the data to be retransmitted, and the data in the control PDU of the seventeenth PDCP entity, the data to be initially transmitted in the indirect connected layer 2 entity of the Remote UE, and the data to be initially transmitted in the Uu RLC entity of the Remote UE, the sum of the three is less than a fourth threshold;
[0318] The sum of the amount of data to be transmitted in the PDU corresponding to the SDU of the fifteenth PDCP entity and the amount of data in the control PDU of the tenth PDCP entity, wherein the end-to-end bearer corresponding to the fifteenth PDCP entity is a separated bearer and copy transmission is not activated.
[0319] Implementation Method 3
[0320] This embodiment describes a scenario in which, in a Remote UE multipath configuration, the backhaul between the Relay UE and the Remote UE is non-ideal, for example, a PC5 interface or other wireless interface is used between the Remote UE and the Relay UE. The Relay UE is unlikely to obtain timely information about the Remote UE's PDCP layer data. Therefore, the Relay UE's Uu BSR reporting may not take into account the Remote UE's buffering status as in Embodiment 2, but may only consider its own buffering status. Similarly, when the Relay UE is configured in SL RA mode 1, the Relay UE also needs to report an SL BSR.
[0321] First, regarding the Uu BSR reporting of the Relay UE, the Relay UE needs to first receive the uplink data of the Remote UE from the Remote UE through the inter-UE interface, such as the PC5 interface, before it can use this data to trigger or report the corresponding UL Uu BSR. This data is generally cached in the Relay UE Uu RLC entity. Therefore, the BSR triggering and cache amount calculation of the Relay UE related to the multipath Remote UE end-to-end data only include the pending data that has arrived at the Relay Uu RLC entity. The Uu BSR triggering and calculation of the Relay UE are performed according to the priority of this pending data and the LCG configuration.
[0322] Secondly, regarding the SL BSR reporting of the Relay UE, since the Relay UE needs to first receive the downlink data of the Remote UE from the base station through its Uu interface, and then send this downlink data of the Remote UE to the Remote UE through the inter-UE interface, such as the PC5 interface. Therefore, only when the downlink data of the Remote UE reaches the Relay UE PC5 RLC entity will the Relay UE SL BSR reporting and buffer amount calculation be triggered. In particular, since this data is sent by the base station to the Relay UE, the base station also has a basic understanding of the amount of data that the Relay UE needs to send to the Remote UE through the PC5 interface. Therefore, the reporting frequency and triggering of the Relay UE SL BSR can be reduced, for example, by disabling the regular SL BSR, or retaining only the padding SL BSR, or not configuring the periodic SL BSR, or not configuring the retransmission (retx) BSR, etc.
[0323] In summary, the embodiment of the present application provides a cache reporting processing method in a Remote UE multipath scenario, so that the Remote UE and the Relay UE can accurately perform cache reporting of their respective Uu interfaces and PC5 interfaces, ensuring that the data of the Remote UE is well scheduled, thereby improving the UE experience and system efficiency while ensuring data transmission.
[0324] The cache status report processing method provided in the embodiment of the present application can be executed by a cache status report processing device. In the embodiment of the present application, the cache status report processing device executing the cache status report processing method is used as an example to illustrate the cache status report processing device provided in the embodiment of the present application.
[0325] In a third aspect, an embodiment of the present application provides a cache status report processing device, which can be applied to a remote device. As shown in FIG11 , the cache status report processing device 110 includes the following modules:
[0326] A first processing module 1101 is configured to, when the remote device is configured for multipath transmission, determine, based on a configuration mode of an end-to-end bearer between the remote device and the network-side device, information related to a first BSR and information related to a second BSR of the remote device, or determine information related to the first BSR of the remote device;
[0327] Among them, the first BSR is the cache status report of the first communication interface, the second BSR is the cache status report of the second communication interface, the first communication interface is the communication interface between the terminal and the network side device, and the second communication interface is the communication interface between the terminals.
[0328] Optionally, the first processing module 1101 includes:
[0329] The first determination submodule is used to determine the triggering condition and first cache amount of the first BSR of the remote device and the triggering condition and second cache amount of the second BSR according to the configuration mode of the end-to-end bearer between the remote device and the network side device, when the remote device and the relay device are connected through the second communication interface and the remote device is configured as the network side device scheduling mode.
[0330] Optionally, when multiple end-to-end bearers exist between the remote device and the network-side device, one end-to-end bearer corresponds to one Packet Data Convergence Protocol (PDCP) entity;
[0331] The first processing submodule is specifically configured to:
[0332] When the end-to-end bearer corresponding to the target PDCP entity is configured as a direct bearer, counting the arrival of first data into a triggering condition of the first BSR, and counting the first data into the first buffer amount, wherein the first data includes data to be transmitted in a protocol data unit (PDU) corresponding to a service data unit (SDU) of the target PDCP entity and data in a control PDU of the target PDCP entity, and the target PDCP entity is one of the PDCP entities of the remote device;
[0333] When the end-to-end bearer corresponding to the target PDCP entity is configured as a non-direct bearer, counting the arrival of the first data into a triggering condition of the second BSR, and counting the first data into the second buffer amount;
[0334] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is activated, and the primary path is a direct RLC bearer, the arrival of the first data is counted in a triggering condition of the first BSR, and the first data is counted in the first cache amount, the arrival of the second data is counted in a triggering condition of the second BSR, and the second data is counted in the second cache amount, or the arrival of the second data is counted in the triggering condition of the first BSR, and the second data is counted in the first cache amount, the arrival of the first data is counted in the triggering condition of the second BSR, and the first data is counted in the second cache amount, wherein the second data includes data to be transmitted in the PDU corresponding to the SDU of the target PDCP entity;
[0335] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is activated, and the primary path is an indirect RLC bearer, counting the arrival of the first data into a triggering condition of the first BSR and counting the first data into the first buffer amount, counting the arrival of the second data into a triggering condition of the second BSR and counting the second data into the second buffer amount, or counting the arrival of the second data into the triggering condition of the first BSR and counting the second data into the first buffer amount, counting the arrival of the first data into the triggering condition of the second BSR and counting the first data into the second buffer amount;
[0336] When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, and duplicate transmission is not activated, and the primary path is a direct RLC bearer, and the data volume of the third data is less than a first threshold, the arrival of the first data is counted in the triggering condition of the first BSR, and the first data is counted in the first cache amount, wherein the third data includes fourth data, data to be initially transmitted in the non-directly connected layer 2 entity of the remote device, and data to be initially transmitted in the radio link control protocol RLC entity of the first communication interface of the remote device, and the fourth data includes at least one of data to be initially transmitted in the PDU corresponding to the SDU of the target PDCP entity, data to be retransmitted, and data in the control PDU of the target PDCP entity;
[0337] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is not activated, the primary path is a direct RLC bearer, and the data volume of the third data is greater than or equal to the first threshold, counting the arrival of the first data into a triggering condition of the first BSR and counting the first data into the first buffer volume, counting the arrival of the second data into a triggering condition of the second BSR and counting the second data into the second buffer volume, or counting the arrival of the second data into the triggering condition of the first BSR and counting the second data into the first buffer volume, counting the arrival of the first data into the triggering condition of the second BSR and counting the first data into the second buffer volume, or counting the arrival of the first data into the triggering condition of the first BSR and the triggering condition of the second BSR, and counting the first data into the first buffer volume and the second buffer volume;
[0338] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is not activated, the primary path is an indirect RLC bearer, and the data volume of the third data is less than a second threshold, counting the arrival of the first data into the triggering condition of the second BSR, and counting the first data into the second buffer amount;
[0339] When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, and duplicate transmission is not activated, and the primary path is a non-direct RLC bearer, and the data volume of the third data is greater than or equal to the second threshold, the arrival of the first data is counted in the triggering condition of the first BSR, and the first data is counted in the first cache volume, the arrival of the second data is counted in the triggering condition of the second BSR, and the second data is counted in the second cache volume, or, the arrival of the second data is counted in the triggering condition of the first BSR, and the second data is counted in the first cache volume, the arrival of the first data is counted in the triggering condition of the second BSR, and the first data is counted in the second cache volume, or, the arrival of the first data is counted in the triggering condition of the first BSR and the triggering condition of the second BSR, and the first data is counted in the first cache volume and the second cache volume.
[0340] Optionally, the first cache amount includes at least one of the following:
[0341] a data volume of fifth data, wherein the fifth data includes data to be transmitted in a PDU corresponding to an SDU of an RLC entity of the first communication interface of the remote device, and data in a control PDU of the RLC entity;
[0342] a data volume of first data when the end-to-end bearer corresponding to the target PDCP entity is configured as a direct bearer, wherein the first data includes data to be transmitted in a PDU corresponding to an SDU of the target PDCP entity and data in a control PDU of the target PDCP entity, and the target PDCP entity is one of the PDCP entities of the remote device;
[0343] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is activated, and the primary path is a direct RLC bearer, the data volume of the first data or the data volume of the second data, wherein the second data includes the data to be transmitted in the PDU corresponding to the SDU of the target PDCP entity;
[0344] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is activated, and the primary path is an indirect RLC bearer, the data volume of the second data or the data volume of the first data;
[0345] The end-to-end bearer configuration corresponding to the target PDCP entity is a separate bearer, duplicate transmission is not activated, and the primary path is a direct RLC bearer, and the data volume of the third data is less than the data volume of the first data at the first threshold, wherein the third data includes fourth data, data to be initially transmitted in the non-directly connected layer 2 entity of the remote device, and data to be initially transmitted in the RLC entity of the first communication interface of the remote device, and the fourth data includes at least one of data to be initially transmitted in the PDU corresponding to the SDU of the target PDCP entity, data to be retransmitted, and data in the control PDU of the target PDCP entity;
[0346] when the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is not activated, the primary path is a direct RLC bearer, and the data volume of the third data is greater than or equal to the first threshold, the data volume of the first data or the data volume of the second data;
[0347] When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer and duplicate transmission is not activated and the main path is a non-direct RLC bearer, and the data volume of the third data is greater than or equal to the second threshold, the data volume of the second data or the data volume of the first data.
[0348] Optionally, the second cache amount includes at least one of the following:
[0349] a data volume of sixth data, wherein the sixth data includes data to be transmitted in a PDU corresponding to an SDU of an RLC entity of the second communication interface of the remote device, and data in a control PDU of the RLC entity;
[0350] a data volume of first data when the end-to-end bearer corresponding to the target PDCP entity is configured as a non-direct bearer, wherein the first data includes data to be transmitted in a PDU corresponding to an SDU of the target PDCP entity and data in a control PDU of the target PDCP entity, and the target PDCP entity is one of the PDCP entities of the remote device;
[0351] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is activated, and the primary path is a direct RLC bearer, the data volume of the second data or the data volume of the first data, wherein the second data includes the data to be transmitted in the PDU corresponding to the SDU of the target PDCP entity;
[0352] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is activated, and the primary path is an indirect RLC bearer, the data volume of the first data or the data volume of the second data;
[0353] The end-to-end bearer configuration corresponding to the target PDCP entity is a separate bearer and duplicate transmission is not activated and the primary path is a direct RLC bearer, and the data volume of the third data is greater than or equal to the first threshold, the data volume of the second data or the data volume of the first data, wherein the third data includes fourth data, data to be initially transmitted in the non-directly connected layer 2 entity of the remote device, and data to be initially transmitted in the radio link control protocol RLC entity of the first communication interface of the remote device, and the fourth data includes at least one of data to be initially transmitted in the PDU corresponding to the SDU of the target PDCP entity, data to be retransmitted, and data in the control PDU of the target PDCP entity;
[0354] The end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is not activated, and the primary path is an indirect RLC bearer, and the data volume of the third data is less than the data volume of the first data at the second threshold;
[0355] The end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, duplicate transmission is not activated, the main path is a non-direct RLC bearer, and the data volume of the third data is greater than or equal to the second threshold, the data volume of the first data or the data volume of the second data.
[0356] Optionally, the first processing module 1101 includes:
[0357] The second determination submodule is used to determine the triggering condition and third cache amount of the first BSR of the remote device according to the configuration mode of the end-to-end bearer between the remote device and the network side device when the connection between the remote device and the relay device is an ideal backhaul or a non-standard connection.
[0358] Optionally, when multiple end-to-end bearers exist between the remote device and the network-side device, one end-to-end bearer corresponds to one PDCP entity; and the second determining submodule is specifically configured to:
[0359] When the end-to-end bearer corresponding to the target PDCP entity is configured as a direct bearer, counting the arrival of first data into a triggering condition of the first BSR, and counting the first data into the third buffer amount, wherein the first data includes data to be transmitted in a PDU corresponding to an SDU of the target PDCP entity and data in a control PDU of the target PDCP entity, and the target PDCP entity is one of the PDCP entities of the remote device;
[0360] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is activated, and the primary path is a direct RLC bearer, counting the arrival of the first data into a triggering condition of the first BSR, and counting the first data into the third buffer amount, or counting the arrival of the second data into the triggering condition of the first BSR, and counting the second data into the third buffer amount, wherein the second data includes data to be transmitted in the PDU corresponding to the SDU of the target PDCP entity;
[0361] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is activated, and the primary path is an indirect RLC bearer, counting the arrival of the first data into a triggering condition of the first BSR and counting the first data into the third buffer amount, or counting the arrival of the second data into the triggering condition of the first BSR and counting the second data into the third buffer amount;
[0362] When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, and duplicate transmission is not activated, and the primary path is a direct RLC bearer, and the data volume of the third data is less than a third threshold, the arrival of the first data is counted in the triggering condition of the first BSR, and the first data is counted in the third cache volume, wherein the third data includes fourth data, data to be initially transmitted in the non-directly connected layer 2 entity of the remote device, and data to be initially transmitted in the RLC entity of the first communication interface of the remote device, and the fourth data includes at least one of data to be initially transmitted in the PDU corresponding to the SDU of the target PDCP entity, data to be retransmitted, and data in the control PDU of the target PDCP entity;
[0363] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is not activated, the primary path is a direct RLC bearer, and the data volume of the third data is greater than or equal to the third threshold, counting the arrival of the first data into the triggering condition of the first BSR and counting the first data into the third buffer volume, or counting the arrival of the second data into the triggering condition of the first BSR and counting the second data into the third buffer volume;
[0364] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is not activated, the primary path is an indirect RLC bearer, and the data volume of the third data is greater than or equal to a fourth threshold, counting the arrival of the first data into a triggering condition of the first BSR and counting the first data into the third buffer volume, or counting the arrival of the second data into the triggering condition of the first BSR and counting the second data into the third buffer volume;
[0365] When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer and duplicate transmission is not activated, the arrival of the first data is counted in the triggering condition of the first BSR, and the first data is counted in the third cache amount.
[0366] Optionally, the third cache amount includes at least one of the following:
[0367] a data volume of fifth data, wherein the fifth data includes data to be transmitted in a PDU corresponding to an SDU of an RLC entity of the first communication interface of the remote device, and data in a control PDU of the RLC entity;
[0368] a data volume of first data when the end-to-end bearer corresponding to the target PDCP entity is configured as a direct bearer, wherein the first data includes data to be transmitted in a PDU corresponding to an SDU of the target PDCP entity and data in a control PDU of the target PDCP entity, and the target PDCP entity is one of the PDCP entities of the remote device;
[0369] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is activated, and the primary path is a direct RLC bearer, the data volume of the first data or the data volume of the second data, wherein the second data includes the data to be transmitted in the PDU corresponding to the SDU of the target PDCP entity;
[0370] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is activated, and the primary path is an indirect RLC bearer, the data volume of the second data or the data volume of the first data;
[0371] The data volume of the first data when the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer and duplicate transmission is not activated and the primary path is a direct RLC bearer, and the data volume of the third data is less than a third threshold, wherein the third data includes fourth data, data to be initially transmitted in the non-directly connected layer 2 entity of the remote device, and data to be initially transmitted in the RLC entity of the first communication interface of the remote device, and the fourth data includes at least one of data to be initially transmitted in the PDU corresponding to the SDU of the target PDCP entity, data to be retransmitted, and data in the control PDU of the target PDCP entity;
[0372] when the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is not activated, the primary path is a direct RLC bearer, and the data volume of the third data is greater than or equal to the third threshold, the data volume of the first data or the data volume of the second data;
[0373] when the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is not activated, the primary path is an indirect RLC bearer, and the data volume of the third data is greater than or equal to a fourth threshold, the data volume of the second data or the data volume of the first data;
[0374] The end-to-end bearer configuration corresponding to the target PDCP entity is a separate bearer, and the data volume of the first data during copy transmission is not activated.
[0375] The cache status reporting processing device in the embodiments of the present application can be an electronic device, such as an electronic device with an operating system, or a component of an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal. For example, the terminal can include, but is not limited to, the types of terminal 11 listed above, and is not specifically limited in the embodiments of the present application.
[0376] The cache status report processing device provided in the embodiment of the present application can implement the various processes implemented by the method embodiment of Figure 9 and achieve the same technical effect. To avoid repetition, it will not be repeated here.
[0377] In a fourth aspect, an embodiment of the present application further provides a cache status report processing device, which can be applied to a relay device. As shown in FIG12 , the cache status report processing device 120 may include at least one of the following modules:
[0378] The second processing module 1201 is configured to determine, when the remote device is configured for multipath transmission and an ideal backhaul or non-standard connection is established between the remote device and the relay device, relevant information of a third BSR of the relay device according to a configuration mode of an end-to-end bearer between the remote device and the network-side device;
[0379] The third processing module 1201 is configured to determine, according to the RLC entity of the first communication interface of the relay device, relevant information of the third BSR when the remote device is configured for multipath transmission and a non-ideal backhaul or a standard connection is used between the remote device and the relay device;
[0380] The third BSR is a buffer status report of the first communication interface, and the first communication interface is a communication interface between the terminal and the network side device.
[0381] Optionally, when multiple end-to-end bearers exist between the remote device and the network-side device, one end-to-end bearer corresponds to one Packet Data Convergence Protocol (PDCP) entity;
[0382] The second processing module 1201 is specifically configured to perform at least one of the following:
[0383] When the end-to-end bearer corresponding to the target PDCP entity is configured as a non-direct bearer, counting the arrival of first data into the triggering condition of the third BSR, and counting the first data into the fourth buffer amount of the third BSR, wherein the first data includes data to be transmitted in a protocol data unit (PDU) corresponding to a service data unit (SDU) of the target PDCP entity and data in a control PDU of the target PDCP entity, and the target PDCP entity is one of the PDCP entities of the remote device;
[0384] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is activated, and the primary path is a direct RLC bearer, counting the arrival of second data into the triggering condition of the third BSR and counting the second data into the fourth buffer amount, or counting the arrival of the first data into the triggering condition of the third BSR and counting the first data into the fourth buffer amount, wherein the second data includes data to be transmitted in the PDU corresponding to the SDU of the target PDCP entity;
[0385] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is activated, and the primary path is an indirect RLC bearer, counting the arrival of the second data into a triggering condition of the third BSR and counting the second data into the fourth buffer amount, or counting the arrival of the first data into a triggering condition of the third BSR and counting the first data into the fourth buffer amount;
[0386] When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, and duplicate transmission is not activated, and the primary path is a direct RLC bearer, and the data volume of the third data is greater than or equal to a third threshold, the arrival of the second data is counted in the triggering condition of the third BSR, and the second data is counted in the fourth cache volume, or the arrival of the first data is counted in the triggering condition of the third BSR, and the first data is counted in the fourth cache volume, wherein the third data includes fourth data, data to be initially transmitted in the non-directly connected layer 2 entity of the remote device, and data to be initially transmitted in the RLC entity of the first communication interface of the remote device, and the fourth data includes at least one of data to be initially transmitted in the PDU corresponding to the SDU of the target PDCP entity, data to be retransmitted, and data in the control PDU of the target PDCP entity;
[0387] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is not activated, the primary path is an indirect RLC bearer, and the data volume of the third data is less than a fourth threshold, counting the arrival of the first data into the triggering condition of the third BSR, and counting the first data into the fourth buffer amount;
[0388] If the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is not activated, the primary path is an indirect RLC bearer, and the data volume of the third data is greater than or equal to the fourth threshold, counting the arrival of the second data into a triggering condition of the third BSR and counting the second data into the fourth buffer volume, or counting the arrival of the first data into a triggering condition of the third BSR and counting the first data into the fourth buffer volume;
[0389] When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer and duplicate transmission is not activated, the arrival of the first data is counted in the triggering condition of the third BSR, and the first data is counted in the fourth cache amount.
[0390] Optionally, the fourth cache amount includes at least one of the following:
[0391] The amount of seventh data, wherein the seventh data includes data to be transmitted in a PDU corresponding to an SDU of the RLC entity of the first communication interface of the relay device, and data in a control PDU of the RLC entity;
[0392] a data volume of first data when the end-to-end bearer corresponding to the target PDCP entity is configured as a non-direct bearer, wherein the first data includes data to be transmitted in a PDU corresponding to an SDU of the target PDCP entity and data in a control PDU of the target PDCP entity, and the target PDCP entity is one of the PDCP entities of the remote device;
[0393] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is activated, and the primary path is a direct RLC bearer, the data volume of the second data or the data volume of the first data, wherein the second data includes the data to be transmitted in the PDU corresponding to the SDU of the target PDCP entity;
[0394] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is activated, and the primary path is an indirect RLC bearer, the data volume of the first data or the data volume of the second data;
[0395] The end-to-end bearer configuration corresponding to the target PDCP entity is a separate bearer and duplicate transmission is not activated and the primary path is a direct RLC bearer, and the data volume of the third data is greater than or equal to a third threshold, the data volume of the second data or the data volume of the first data, wherein the third data includes fourth data, data to be initially transmitted in the non-directly connected layer 2 entity of the remote device, and data to be initially transmitted in the radio link control protocol RLC entity of the first communication interface of the remote device, and the fourth data includes at least one of data to be initially transmitted in the PDU corresponding to the SDU of the target PDCP entity, data to be retransmitted, and data in the control PDU of the target PDCP entity;
[0396] the data volume of the first data when the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is not activated, the primary path is a non-direct RLC bearer, and the data volume of the third data is less than a fourth threshold;
[0397] when the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is not activated, the primary path is a non-direct RLC bearer, and the data volume of the third data is greater than or equal to the fourth threshold, the data volume of the first data or the data volume of the second data;
[0398] The end-to-end bearer configuration corresponding to the target PDCP entity is a separate bearer, and the data volume of the first data during copy transmission is not activated.
[0399] Optionally, the third processing module 1202 is specifically configured to:
[0400] The arrival of data of the RLC entity of the first communication interface of the relay device is counted in the trigger condition of the third BSR, and the seventh data is counted in the data cache amount in the third BSR, wherein the seventh data includes the data to be transmitted in the PDU corresponding to the SDU of the RLC entity of the first communication interface of the relay device, and the data in the control PDU of the RLC entity.
[0401] Optionally, the device further comprises:
[0402] A fourth processing module is configured to, when the remote device and the relay device are connected via the second communication interface and the relay device is configured in a network-side device scheduling mode, perform at least one of the following:
[0403] counting arrival of data of the RLC entity of the second communication interface of the relay device into a trigger condition of a fourth BSR of the relay device, and counting eighth data into a data cache amount of the fourth BSR, wherein the fourth BSR is a cache status report of the second communication interface, and the eighth data includes to-be-transmitted data of a PDU corresponding to an SDU of the RLC entity of the second communication interface of the relay device, and data in a control PDU of the RLC entity, where the second communication interface is a communication interface between terminals;
[0404] prohibiting processing of the fourth BSR;
[0405] Only the padded fourth BSR is retained;
[0406] Not configuring the periodic fourth BSR;
[0407] The fourth BSR is not configured to be retransmitted.
[0408] The cache status reporting processing device in the embodiments of the present application can be an electronic device, such as an electronic device with an operating system, or a component of an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal. For example, the terminal can include, but is not limited to, the types of terminal 11 listed above, and is not specifically limited in the embodiments of the present application.
[0409] The cache status report processing device provided in the embodiment of the present application can implement the various processes implemented by the method embodiment of Figure 10 and achieve the same technical effect. To avoid repetition, it will not be repeated here.
[0410] As shown in Figure 13, an embodiment of the present application further provides a communication device 1300, including a processor 1301 and a memory 1302. The memory 1302 stores a program or instruction that can be run on the processor 1301. For example, when the communication device 1300 is a remote device, the program or instruction, when executed by the processor 1301, implements the various steps of the embodiment of the cache status report processing method described in the first aspect above, and can achieve the same technical effect. When the communication device 1300 is a relay device, the program or instruction, when executed by the processor 1301, implements the various steps of the embodiment of the cache status report processing method described in the second aspect above, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
[0411] The present application also provides a terminal including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps in the method embodiment shown in Figures 9 or 10. This terminal embodiment corresponds to the aforementioned terminal-side method embodiment, and each implementation process and implementation method of the aforementioned method embodiment is applicable to this terminal embodiment and can achieve the same technical effects.
[0412] Specifically, FIG14 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.
[0413] The terminal 1400 includes but is not limited to: a radio frequency unit 1401, a network module 1402, an audio output unit 1403, an input unit 1404, a sensor 1405, a display unit 1406, a user input unit 1407, an interface unit 1408, a memory 1409 and at least some of the components of the processor 1410.
[0414] Those skilled in the art will appreciate that the terminal 1400 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 1410 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in FIG14 does not limit the terminal. The terminal may include more or fewer components than shown, or may combine certain components, or have different component arrangements, which will not be described in detail here.
[0415] It should be understood that in an embodiment of the present application, the input unit 1404 may include a graphics processing unit (GPU) 14041 and a microphone 14042, and the graphics processor 14041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 1406 may include a display panel 14061, and the display panel 14061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1407 includes a touch panel 14071 and at least one of other input devices 14072. The touch panel 14071 is also called a touch screen. The touch panel 14071 may include two parts: a touch detection device and a touch controller. Other input devices 14072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.
[0416] In the embodiment of the present application, after receiving downlink data from a network-side device, the radio frequency unit 1401 may transmit the data to the processor 1410 for processing. Furthermore, the radio frequency unit 1401 may send uplink data to the network-side device. Typically, the radio frequency unit 1401 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.
[0417] The memory 1409 can be used to store software programs or instructions and various data. The memory 1409 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 1409 may include a volatile memory or a non-volatile memory 14. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM). The memory 1409 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.
[0418] Processor 1410 may include one or more processing units. Optionally, processor 1410 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 1410.
[0419] In the first aspect, when the terminal 1400 acts as a remote device, the processor 1410 is used to: when the remote device is configured for multi-path transmission, determine the relevant information of the first BSR of the remote device and the relevant information of the second BSR according to the configuration mode of the end-to-end bearer between the remote device and the network side device, or determine the relevant information of the first BSR of the remote device; wherein the first BSR is a cache status report of the first communication interface, the second BSR is a cache status report of the second communication interface, the first communication interface is the communication interface between the terminal and the network side device, and the second communication interface is the communication interface between the terminal and the terminal.
[0420] Optionally, the processor 1410 determines, according to a configuration mode of an end-to-end bearer between the remote device and the network-side device, relevant information of a first BSR and relevant information of a second BSR of the remote device, or determines relevant information of the first BSR of the remote device, specifically for:
[0421] When the remote device and the relay device are connected through the second communication interface and the remote device is configured as a network-side device scheduling mode, the triggering conditions and first cache amount of the first BSR of the remote device and the triggering conditions and second cache amount of the second BSR are determined according to the configuration mode of the end-to-end bearer between the remote device and the network-side device.
[0422] Optionally, when multiple end-to-end bearers exist between the remote device and the network-side device, one end-to-end bearer corresponds to one Packet Data Convergence Protocol (PDCP) entity;
[0423] The processor 1410 is specifically configured to perform at least one of the following according to the configuration mode of the end-to-end bearer between the remote device and the network-side device, the triggering condition and the first buffer amount of the first BSR, and the triggering condition and the second buffer amount of the second BSR:
[0424] When the end-to-end bearer corresponding to the target PDCP entity is configured as a direct bearer, counting the arrival of first data into a triggering condition of the first BSR, and counting the first data into the first buffer amount, wherein the first data includes data to be transmitted in a protocol data unit (PDU) corresponding to a service data unit (SDU) of the target PDCP entity and data in a control PDU of the target PDCP entity, and the target PDCP entity is one of the PDCP entities of the remote device;
[0425] When the end-to-end bearer corresponding to the target PDCP entity is configured as a non-direct bearer, counting the arrival of the first data into a triggering condition of the second BSR, and counting the first data into the second buffer amount;
[0426] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is activated, and the primary path is a direct RLC bearer, the arrival of the first data is counted in a triggering condition of the first BSR, and the first data is counted in the first cache amount, the arrival of the second data is counted in a triggering condition of the second BSR, and the second data is counted in the second cache amount, or the arrival of the second data is counted in the triggering condition of the first BSR, and the second data is counted in the first cache amount, the arrival of the first data is counted in the triggering condition of the second BSR, and the first data is counted in the second cache amount, wherein the second data includes data to be transmitted in the PDU corresponding to the SDU of the target PDCP entity;
[0427] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is activated, and the primary path is an indirect RLC bearer, counting the arrival of the first data into a triggering condition of the first BSR and counting the first data into the first buffer amount, counting the arrival of the second data into a triggering condition of the second BSR and counting the second data into the second buffer amount, or counting the arrival of the second data into the triggering condition of the first BSR and counting the second data into the first buffer amount, counting the arrival of the first data into the triggering condition of the second BSR and counting the first data into the second buffer amount;
[0428] When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, and duplicate transmission is not activated, and the primary path is a direct RLC bearer, and the data volume of the third data is less than a first threshold, the arrival of the first data is counted in the triggering condition of the first BSR, and the first data is counted in the first cache amount, wherein the third data includes fourth data, data to be initially transmitted in the non-directly connected layer 2 entity of the remote device, and data to be initially transmitted in the radio link control protocol RLC entity of the first communication interface of the remote device, and the fourth data includes at least one of data to be initially transmitted in the PDU corresponding to the SDU of the target PDCP entity, data to be retransmitted, and data in the control PDU of the target PDCP entity;
[0429] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is not activated, the primary path is a direct RLC bearer, and the data volume of the third data is greater than or equal to the first threshold, counting the arrival of the first data into a triggering condition of the first BSR and counting the first data into the first buffer volume, counting the arrival of the second data into a triggering condition of the second BSR and counting the second data into the second buffer volume, or counting the arrival of the second data into the triggering condition of the first BSR and counting the second data into the first buffer volume, counting the arrival of the first data into the triggering condition of the second BSR and counting the first data into the second buffer volume, or counting the arrival of the first data into the triggering condition of the first BSR and the triggering condition of the second BSR, and counting the first data into the first buffer volume and the second buffer volume;
[0430] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is not activated, the primary path is an indirect RLC bearer, and the data volume of the third data is less than a second threshold, counting the arrival of the first data into the triggering condition of the second BSR, and counting the first data into the second buffer amount;
[0431] When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, and duplicate transmission is not activated, and the primary path is a non-direct RLC bearer, and the data volume of the third data is greater than or equal to the second threshold, the arrival of the first data is counted in the triggering condition of the first BSR, and the first data is counted in the first cache volume, the arrival of the second data is counted in the triggering condition of the second BSR, and the second data is counted in the second cache volume, or, the arrival of the second data is counted in the triggering condition of the first BSR, and the second data is counted in the first cache volume, the arrival of the first data is counted in the triggering condition of the second BSR, and the first data is counted in the second cache volume, or, the arrival of the first data is counted in the triggering condition of the first BSR and the triggering condition of the second BSR, and the first data is counted in the first cache volume and the second cache volume.
[0432] Optionally, the first cache amount includes at least one of the following:
[0433] a data volume of fifth data, wherein the fifth data includes data to be transmitted in a PDU corresponding to an SDU of an RLC entity of the first communication interface of the remote device, and data in a control PDU of the RLC entity;
[0434] a data volume of first data when the end-to-end bearer corresponding to the target PDCP entity is configured as a direct bearer, wherein the first data includes data to be transmitted in a PDU corresponding to an SDU of the target PDCP entity and data in a control PDU of the target PDCP entity, and the target PDCP entity is one of the PDCP entities of the remote device;
[0435] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is activated, and the primary path is a direct RLC bearer, the data volume of the first data or the data volume of the second data, wherein the second data includes the data to be transmitted in the PDU corresponding to the SDU of the target PDCP entity;
[0436] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is activated, and the primary path is an indirect RLC bearer, the data volume of the second data or the data volume of the first data;
[0437] The end-to-end bearer configuration corresponding to the target PDCP entity is a separate bearer, duplicate transmission is not activated, and the primary path is a direct RLC bearer, and the data volume of the third data is less than the data volume of the first data at the first threshold, wherein the third data includes fourth data, data to be initially transmitted in the non-directly connected layer 2 entity of the remote device, and data to be initially transmitted in the RLC entity of the first communication interface of the remote device, and the fourth data includes at least one of data to be initially transmitted in the PDU corresponding to the SDU of the target PDCP entity, data to be retransmitted, and data in the control PDU of the target PDCP entity;
[0438] when the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is not activated, the primary path is a direct RLC bearer, and the data volume of the third data is greater than or equal to the first threshold, the data volume of the first data or the data volume of the second data;
[0439] When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer and duplicate transmission is not activated and the main path is a non-direct RLC bearer, and the data volume of the third data is greater than or equal to the second threshold, the data volume of the second data or the data volume of the first data.
[0440] Optionally, the second cache amount includes at least one of the following:
[0441] a data volume of sixth data, wherein the sixth data includes data to be transmitted in a PDU corresponding to an SDU of an RLC entity of the second communication interface of the remote device, and data in a control PDU of the RLC entity;
[0442] a data volume of first data when the end-to-end bearer corresponding to the target PDCP entity is configured as a non-direct bearer, wherein the first data includes data to be transmitted in a PDU corresponding to an SDU of the target PDCP entity and data in a control PDU of the target PDCP entity, and the target PDCP entity is one of the PDCP entities of the remote device;
[0443] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is activated, and the primary path is a direct RLC bearer, the data volume of the second data or the data volume of the first data, wherein the second data includes the data to be transmitted in the PDU corresponding to the SDU of the target PDCP entity;
[0444] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is activated, and the primary path is an indirect RLC bearer, the data volume of the first data or the data volume of the second data;
[0445] The end-to-end bearer configuration corresponding to the target PDCP entity is a separate bearer and duplicate transmission is not activated and the primary path is a direct RLC bearer, and the data volume of the third data is greater than or equal to the first threshold, the data volume of the second data or the data volume of the first data, wherein the third data includes fourth data, data to be initially transmitted in the non-directly connected layer 2 entity of the remote device, and data to be initially transmitted in the radio link control protocol RLC entity of the first communication interface of the remote device, and the fourth data includes at least one of data to be initially transmitted in the PDU corresponding to the SDU of the target PDCP entity, data to be retransmitted, and data in the control PDU of the target PDCP entity;
[0446] The end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is not activated, and the primary path is an indirect RLC bearer, and the data volume of the third data is less than the data volume of the first data at the second threshold;
[0447] The end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, duplicate transmission is not activated, the main path is a non-direct RLC bearer, and the data volume of the third data is greater than or equal to the second threshold, the data volume of the first data or the data volume of the second data.
[0448] Optionally, the processor 1410 determines, according to a configuration mode of an end-to-end bearer between the remote device and the network-side device, relevant information of a first BSR and relevant information of a second BSR of the remote device, or determines relevant information of the first BSR of the remote device, specifically for:
[0449] In the case where the remote device and the relay device have an ideal backhaul or a non-standard connection, the triggering condition and the third buffer amount of the first BSR of the remote device are determined according to the configuration mode of the end-to-end bearer between the remote device and the network side device.
[0450] Optionally, when multiple end-to-end bearers exist between the remote device and the network-side device, one end-to-end bearer corresponds to one PDCP entity; the processor 1410 determines, according to a configuration mode of the end-to-end bearer between the remote device and the network-side device, a triggering condition for a first BSR of the remote device and a third buffer amount, and is specifically configured to perform at least one of the following:
[0451] When the end-to-end bearer corresponding to the target PDCP entity is configured as a direct bearer, counting the arrival of first data into a triggering condition of the first BSR, and counting the first data into the third buffer amount, wherein the first data includes data to be transmitted in a PDU corresponding to an SDU of the target PDCP entity and data in a control PDU of the target PDCP entity, and the target PDCP entity is one of the PDCP entities of the remote device;
[0452] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is activated, and the primary path is a direct RLC bearer, counting the arrival of the first data into a triggering condition of the first BSR, and counting the first data into the third buffer amount, or counting the arrival of the second data into the triggering condition of the first BSR, and counting the second data into the third buffer amount, wherein the second data includes data to be transmitted in the PDU corresponding to the SDU of the target PDCP entity;
[0453] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is activated, and the primary path is an indirect RLC bearer, counting the arrival of the first data into a triggering condition of the first BSR and counting the first data into the third buffer amount, or counting the arrival of the second data into the triggering condition of the first BSR and counting the second data into the third buffer amount;
[0454] When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, and duplicate transmission is not activated, and the primary path is a direct RLC bearer, and the data volume of the third data is less than a third threshold, the arrival of the first data is counted in the triggering condition of the first BSR, and the first data is counted in the third cache volume, wherein the third data includes fourth data, data to be initially transmitted in the non-directly connected layer 2 entity of the remote device, and data to be initially transmitted in the RLC entity of the first communication interface of the remote device, and the fourth data includes at least one of data to be initially transmitted in the PDU corresponding to the SDU of the target PDCP entity, data to be retransmitted, and data in the control PDU of the target PDCP entity;
[0455] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is not activated, the primary path is a direct RLC bearer, and the data volume of the third data is greater than or equal to the third threshold, counting the arrival of the first data into the triggering condition of the first BSR and counting the first data into the third buffer volume, or counting the arrival of the second data into the triggering condition of the first BSR and counting the second data into the third buffer volume;
[0456] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is not activated, the primary path is an indirect RLC bearer, and the data volume of the third data is greater than or equal to a fourth threshold, counting the arrival of the first data into a triggering condition of the first BSR and counting the first data into the third buffer volume, or counting the arrival of the second data into the triggering condition of the first BSR and counting the second data into the third buffer volume;
[0457] When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer and duplicate transmission is not activated, the arrival of the first data is counted in the triggering condition of the first BSR, and the first data is counted in the third cache amount.
[0458] Optionally, the third cache amount includes at least one of the following:
[0459] a data volume of fifth data, wherein the fifth data includes data to be transmitted in a PDU corresponding to an SDU of an RLC entity of the first communication interface of the remote device, and data in a control PDU of the RLC entity;
[0460] a data volume of first data when the end-to-end bearer corresponding to the target PDCP entity is configured as a direct bearer, wherein the first data includes data to be transmitted in a PDU corresponding to an SDU of the target PDCP entity and data in a control PDU of the target PDCP entity, and the target PDCP entity is one of the PDCP entities of the remote device;
[0461] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is activated, and the primary path is a direct RLC bearer, the data volume of the first data or the data volume of the second data, wherein the second data includes the data to be transmitted in the PDU corresponding to the SDU of the target PDCP entity;
[0462] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is activated, and the primary path is an indirect RLC bearer, the data volume of the second data or the data volume of the first data;
[0463] The data volume of the first data when the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer and duplicate transmission is not activated and the primary path is a direct RLC bearer, and the data volume of the third data is less than a third threshold, wherein the third data includes fourth data, data to be initially transmitted in the non-directly connected layer 2 entity of the remote device, and data to be initially transmitted in the RLC entity of the first communication interface of the remote device, and the fourth data includes at least one of data to be initially transmitted in the PDU corresponding to the SDU of the target PDCP entity, data to be retransmitted, and data in the control PDU of the target PDCP entity;
[0464] when the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is not activated, the primary path is a direct RLC bearer, and the data volume of the third data is greater than or equal to the third threshold, the data volume of the first data or the data volume of the second data;
[0465] when the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is not activated, the primary path is an indirect RLC bearer, and the data volume of the third data is greater than or equal to a fourth threshold, the data volume of the second data or the data volume of the first data;
[0466] The end-to-end bearer configuration corresponding to the target PDCP entity is a separate bearer, and the data volume of the first data during copy transmission is not activated.
[0467] In a second aspect, when the terminal 1400 functions as a relay device, the processor 1410 is configured to perform at least one of the following:
[0468] When the remote device is configured for multipath transmission and an ideal backhaul or non-standard connection is established between the remote device and the relay device, determining relevant information of a third BSR of the relay device according to a configuration mode of an end-to-end bearer between the remote device and the network-side device;
[0469] When the remote device is configured for multipath transmission and a non-ideal backhaul or a standard connection is used between the remote device and the relay device, determining, according to an RLC entity of the first communication interface of the relay device, relevant information of the third BSR;
[0470] The third BSR is a buffer status report of the first communication interface, and the first communication interface is a communication interface between the terminal and the network side device.
[0471] Optionally, when multiple end-to-end bearers exist between the remote device and the network-side device, one end-to-end bearer corresponds to one Packet Data Convergence Protocol (PDCP) entity; the processor 1410 determines, based on a configuration mode of the end-to-end bearer between the remote device and the network-side device, relevant information of a third BSR of the relay device, specifically used to indicate at least one of the following:
[0472] When the end-to-end bearer corresponding to the target PDCP entity is configured as a non-direct bearer, counting the arrival of first data into the triggering condition of the third BSR, and counting the first data into the fourth buffer amount of the third BSR, wherein the first data includes data to be transmitted in a protocol data unit (PDU) corresponding to a service data unit (SDU) of the target PDCP entity and data in a control PDU of the target PDCP entity, and the target PDCP entity is one of the PDCP entities of the remote device;
[0473] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is activated, and the primary path is a direct RLC bearer, counting the arrival of second data into the triggering condition of the third BSR and counting the second data into the fourth buffer amount, or counting the arrival of the first data into the triggering condition of the third BSR and counting the first data into the fourth buffer amount, wherein the second data includes data to be transmitted in the PDU corresponding to the SDU of the target PDCP entity;
[0474] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is activated, and the primary path is an indirect RLC bearer, counting the arrival of the second data into a triggering condition of the third BSR and counting the second data into the fourth buffer amount, or counting the arrival of the first data into a triggering condition of the third BSR and counting the first data into the fourth buffer amount;
[0475] When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, and duplicate transmission is not activated, and the primary path is a direct RLC bearer, and the data volume of the third data is greater than or equal to a third threshold, the arrival of the second data is counted in the triggering condition of the third BSR, and the second data is counted in the fourth cache volume, or the arrival of the first data is counted in the triggering condition of the third BSR, and the first data is counted in the fourth cache volume, wherein the third data includes fourth data, data to be initially transmitted in the non-directly connected layer 2 entity of the remote device, and data to be initially transmitted in the RLC entity of the first communication interface of the remote device, and the fourth data includes at least one of data to be initially transmitted in the PDU corresponding to the SDU of the target PDCP entity, data to be retransmitted, and data in the control PDU of the target PDCP entity;
[0476] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is not activated, the primary path is an indirect RLC bearer, and the data volume of the third data is less than a fourth threshold, counting the arrival of the first data into the triggering condition of the third BSR, and counting the first data into the fourth buffer amount;
[0477] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is not activated, the primary path is an indirect RLC bearer, and the data volume of the third data is greater than or equal to the fourth threshold, counting the arrival of the second data into the triggering condition of the third BSR and counting the second data into the fourth buffer volume, or counting the arrival of the first data into the triggering condition of the third BSR and counting the first data into the fourth buffer volume;
[0478] When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer and duplicate transmission is not activated, the arrival of the first data is counted in the triggering condition of the third BSR, and the first data is counted in the fourth cache amount.
[0479] Optionally, the fourth cache amount includes at least one of the following:
[0480] The amount of seventh data, wherein the seventh data includes data to be transmitted in a PDU corresponding to an SDU of the RLC entity of the first communication interface of the relay device, and data in a control PDU of the RLC entity;
[0481] a data volume of first data when the end-to-end bearer corresponding to the target PDCP entity is configured as a non-direct bearer, wherein the first data includes data to be transmitted in a PDU corresponding to an SDU of the target PDCP entity and data in a control PDU of the target PDCP entity, and the target PDCP entity is one of the PDCP entities of the remote device;
[0482] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is activated, and the primary path is a direct RLC bearer, the data volume of the second data or the data volume of the first data, wherein the second data includes the data to be transmitted in the PDU corresponding to the SDU of the target PDCP entity;
[0483] When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is activated, and the primary path is an indirect RLC bearer, the data volume of the first data or the data volume of the second data;
[0484] The end-to-end bearer configuration corresponding to the target PDCP entity is a separate bearer and duplicate transmission is not activated and the primary path is a direct RLC bearer, and the data volume of the third data is greater than or equal to a third threshold, the data volume of the second data or the data volume of the first data, wherein the third data includes fourth data, data to be initially transmitted in the non-directly connected layer 2 entity of the remote device, and data to be initially transmitted in the radio link control protocol RLC entity of the first communication interface of the remote device, and the fourth data includes at least one of data to be initially transmitted in the PDU corresponding to the SDU of the target PDCP entity, data to be retransmitted, and data in the control PDU of the target PDCP entity;
[0485] the data volume of the first data when the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is not activated, the primary path is a non-direct RLC bearer, and the data volume of the third data is less than a fourth threshold;
[0486] when the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is not activated, the primary path is a non-direct RLC bearer, and the data volume of the third data is greater than or equal to the fourth threshold, the data volume of the first data or the data volume of the second data;
[0487] The end-to-end bearer configuration corresponding to the target PDCP entity is a separate bearer, and the data volume of the first data during copy transmission is not activated.
[0488] Optionally, the processor 1410 determines, according to the RLC entity of the first communication interface of the relay device, relevant information of the third BSR, specifically configured to:
[0489] The arrival of data of the RLC entity of the first communication interface of the relay device is counted in the trigger condition of the third BSR, and the seventh data is counted in the data cache amount in the third BSR, wherein the seventh data includes the data to be transmitted in the PDU corresponding to the SDU of the RLC entity of the first communication interface of the relay device, and the data in the control PDU of the RLC entity.
[0490] Optionally, the processor 1410 is further configured to:
[0491] When the remote device and the relay device are connected via the second communication interface and the relay device is configured in a network-side device scheduling mode, at least one of the following is performed:
[0492] counting arrival of data of the RLC entity of the second communication interface of the relay device into a trigger condition of a fourth BSR of the relay device, and counting eighth data into a data cache amount of the fourth BSR, wherein the fourth BSR is a cache status report of the second communication interface, and the eighth data includes to-be-transmitted data of a PDU corresponding to an SDU of the RLC entity of the second communication interface of the relay device, and data in a control PDU of the RLC entity, where the second communication interface is a communication interface between terminals;
[0493] prohibiting processing of the fourth BSR;
[0494] Only the padded fourth BSR is retained;
[0495] Not configuring the periodic fourth BSR;
[0496] The fourth BSR is not configured to be retransmitted.
[0497] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiments described in the first and second aspects above, and achieve the same or corresponding technical effects. To avoid repetition, it will not be repeated here.
[0498] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by the processor, the various processes of the cache status report processing method embodiment described in the first aspect or the second aspect above are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.
[0499] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. In some examples, the readable storage medium may be a non-transitory readable storage medium.
[0500] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the cache status report processing method embodiment described in the first aspect or the second aspect above, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
[0501] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.
[0502] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the cache status report processing method embodiment described in the first aspect or the second aspect above, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
[0503] An embodiment of the present application also provides a wireless communication system, including: a remote device and a relay device, wherein the remote device can be used to execute the steps of the cache status report processing method as described in the first aspect, and the relay device can be used to execute the steps of the cache status report processing method as described in the second aspect.
[0504] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.
[0505] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general-purpose hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or network-side device to execute the methods described in each embodiment of the present application.
[0506] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.
Claims
1. A cache status report processing method, the method comprising: In the case where the remote device is configured for multipath transmission, the remote device determines, according to the configuration mode of the end-to-end bearer between the remote device and the network side device, the relevant information of the first BSR of the remote device and the relevant information of the second BSR, or determines the relevant information of the first BSR of the remote device; Among them, the first BSR is a cache status report of the first communication interface, the second BSR is a cache status report of the second communication interface, the first communication interface is a communication interface between the terminal and the network side device, and the second communication interface is a communication interface between terminals.
2. The method according to claim 1, wherein: The remote device determines, according to a configuration mode of an end-to-end bearer between the remote device and a network-side device, relevant information of a first BSR and relevant information of a second BSR of the remote device, including: When the remote device is connected to the relay device through the second communication interface and the remote device is configured as a network side device scheduling mode, the remote device determines the triggering condition and the first cache amount of the first BSR of the remote device and the triggering condition and the second cache amount of the second BSR according to the configuration mode of the end-to-end bearer between the remote device and the network side device.
3. The method according to claim 2, wherein: When there are multiple end-to-end bearers between the remote device and the network side device, one end-to-end bearer corresponds to one Packet Data Convergence Protocol PDCP entity; The remote device determines, according to a configuration mode of an end-to-end bearer between the remote device and the network side device, a triggering condition of a first BSR and a first buffer amount and a triggering condition of a second BSR and a second buffer amount, including at least one of the following: In a case where the end-to-end bearer configuration corresponding to the target PDCP entity is a direct bearer, the remote device counts the arrival of first data into the triggering condition of the first BSR, and counts the first data into the first cache amount, wherein the first data includes the data to be transmitted in the protocol data unit PDU corresponding to the service data unit SDU of the target PDCP entity, and the data in the control PDU of the target PDCP entity, and the target PDCP entity is one of the PDCP entities of the remote device; When the end-to-end bearer corresponding to the target PDCP entity is configured as a non-direct bearer, the remote device counts the arrival of the first data into a triggering condition of the second BSR, and counts the first data into the second cache amount; In a case where the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, duplicate transmission is activated, and the primary path is a direct radio link control protocol RLC bearer, the remote device counts the arrival of the first data into the triggering condition of the first BSR, and counts the first data into the first cache amount, counts the arrival of the second data into the triggering condition of the second BSR, and counts the second data into the second cache amount, or the remote device counts the arrival of the second data into the triggering condition of the first BSR, and counts the second data into the first cache amount, counts the arrival of the first data into the triggering condition of the second BSR, and counts the first data into the second cache amount, wherein the second data includes the data to be transmitted in the PDU corresponding to the SDU of the target PDCP entity; In a case where the end-to-end bearer corresponding to the target PDCP entity is configured as a separated bearer, duplicate transmission is activated, and the primary path is an indirect RLC bearer, the remote device counts the arrival of the first data into the triggering condition of the first BSR, counts the first data into the first cache amount, and counts the arrival of the second data into the triggering condition of the first BSR. The remote device includes the arrival of the second data in the triggering condition of the second BSR and includes the second data in the second cache amount, or the remote device includes the arrival of the second data in the triggering condition of the first BSR and includes the second data in the first cache amount, includes the arrival of the first data in the triggering condition of the second BSR and includes the first data in the second cache amount; When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, and the copy transmission is not activated, and the main path is a direct RLC bearer, and the data volume of the third data is less than the first threshold, the remote device counts the arrival of the first data into the triggering condition of the first BSR, and counts the first data into the first cache volume, wherein the third data includes fourth data, data to be initially transmitted in the non-directly connected layer 2 entity of the remote device, and data to be initially transmitted in the RLC entity of the first communication interface of the remote device, and the fourth data includes at least one of data to be initially transmitted in the PDU corresponding to the SDU of the target PDCP entity, data to be retransmitted, and data in the control PDU of the target PDCP entity; When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, and duplicate transmission is not activated, and the primary path is a direct RLC bearer, and the data volume of the third data is greater than or equal to the first threshold, the remote device counts the arrival of the first data into the triggering condition of the first BSR, and counts the first data into the first cache volume, counts the arrival of the second data into the triggering condition of the second BSR, and counts the second data into the second cache volume, or, the remote device counts the arrival of the second data into the triggering condition of the first BSR, and counts the second data into the first cache volume, counts the arrival of the first data into the triggering condition of the second BSR, and counts the first data into the second cache volume, or, the remote device counts the arrival of the first data into the triggering condition of the first BSR and the triggering condition of the second BSR, and counts the first data into the first cache volume and the second cache volume; When the end-to-end bearer corresponding to the target PDCP entity is configured as a separated bearer, duplicate transmission is not activated, the primary path is an indirect RLC bearer, and the data volume of the third data is less than a second threshold, the remote device counts the arrival of the first data into the triggering condition of the second BSR, and counts the first data into the second cache volume; When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, and duplicate transmission is not activated, and the primary path is a non-direct RLC bearer, and the data volume of the third data is greater than or equal to the second threshold, the remote device counts the arrival of the first data into the triggering condition of the first BSR, and counts the first data into the first cache volume, counts the arrival of the second data into the triggering condition of the second BSR, and counts the second data into the second cache volume, or, the remote device counts the arrival of the second data into the triggering condition of the first BSR, and counts the second data into the first cache volume, counts the arrival of the first data into the triggering condition of the second BSR, and counts the first data into the second cache volume, or, the remote device counts the arrival of the first data into the triggering condition of the first BSR and the triggering condition of the second BSR, and counts the first data into the first cache volume and the second cache volume.
4. The method according to claim 2 or 3, wherein: The first cache amount includes at least one of the following: The data volume of fifth data, wherein the fifth data includes data to be transmitted in a PDU corresponding to an SDU of an RLC entity of the first communication interface of the remote device, and data in a control PDU of the RLC entity; The amount of first data when the end-to-end bearer corresponding to the target PDCP entity is configured as a direct bearer, wherein the first data includes the data to be transmitted in the PDU corresponding to the SDU of the target PDCP entity and the data in the control PDU of the target PDCP entity, and the target PDCP entity is one of the remote devices PDCP entity; When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer and duplicate transmission is activated and the primary path is a direct RLC bearer, the data volume of the first data or the data volume of the second data, wherein the second data includes the data to be transmitted in the PDU corresponding to the SDU of the target PDCP entity; When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is activated, and the primary path is an indirect RLC bearer, the data volume of the second data or the data volume of the first data; The end-to-end bearer configuration corresponding to the target PDCP entity is a separate bearer and the duplicate transmission is not activated and the main path is a direct RLC bearer, and the data volume of the third data is less than the data volume of the first data at the first threshold, wherein the third data includes fourth data, data to be initially transmitted in the non-directly connected layer 2 entity of the remote device, and data to be initially transmitted in the RLC entity of the first communication interface of the remote device, and the fourth data includes at least one of data to be initially transmitted in the PDU corresponding to the SDU of the target PDCP entity, data to be retransmitted, and data in the control PDU of the target PDCP entity; when the end-to-end bearer configuration corresponding to the target PDCP entity is a separated bearer and duplicate transmission is not activated and the primary path is a direct RLC bearer, and the data volume of the third data is greater than or equal to the first threshold, the data volume of the first data or the data volume of the second data; When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer and duplicate transmission is not activated and the main path is a non-direct RLC bearer, and the data volume of the third data is greater than or equal to the second threshold, the data volume of the second data or the data volume of the first data.
5. The method according to claim 2 or 3, wherein: The second cache amount includes at least one of the following: The data volume of sixth data, wherein the sixth data includes data to be transmitted in a PDU corresponding to an SDU of an RLC entity of the second communication interface of the remote device, and data in a control PDU of the RLC entity; a data volume of first data when the end-to-end bearer corresponding to the target PDCP entity is configured as a non-direct bearer, wherein the first data includes data to be transmitted in a PDU corresponding to an SDU of the target PDCP entity and data in a control PDU of the target PDCP entity, and the target PDCP entity is one of the PDCP entities of the remote device; When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer and duplicate transmission is activated and the primary path is a direct RLC bearer, the data amount of the second data or the data amount of the first data, wherein the second data includes the data to be transmitted in the PDU corresponding to the SDU of the target PDCP entity; When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is activated, and the primary path is an indirect RLC bearer, the data volume of the first data or the data volume of the second data; The end-to-end bearer configuration corresponding to the target PDCP entity is a separate bearer and the copy transmission is not activated and the main path is a direct RLC bearer, and the data volume of the third data is greater than or equal to the first threshold, the data volume of the second data or the data volume of the first data, wherein the third data includes fourth data, data to be initially transmitted in the non-directly connected layer 2 entity of the remote device, and data to be initially transmitted in the RLC entity of the first communication interface of the remote device, and the fourth data includes at least one of data to be initially transmitted in the PDU corresponding to the SDU of the target PDCP entity, data to be retransmitted, and data in the control PDU of the target PDCP entity; The end-to-end bearer configuration corresponding to the target PDCP entity is a separated bearer, duplicate transmission is not activated, and the primary path is a non-direct RLC bearer, and the data volume of the third data is less than the data volume of the first data at the second threshold; The end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer and duplicate transmission is not activated and the primary path When it is a non-direct RLC bearer and the data amount of the third data is greater than or equal to the second threshold, the data amount of the first data or the data amount of the second data.
6. The method according to claim 1 or 2, wherein: The remote device determines, according to a configuration mode of an end-to-end bearer between the remote device and a network-side device, relevant information of a first BSR of the remote device, including: In the case where the remote device and the relay device have an ideal backhaul or a non-standard connection, the remote device determines the triggering condition and the third cache amount of the first BSR of the remote device according to the configuration mode of the end-to-end bearer between the remote device and the network side device.
7. The method according to claim 6, wherein: When there are multiple end-to-end bearers between the remote device and the network side device, one end-to-end bearer corresponds to one PDCP entity; The remote device determines, according to a configuration mode of an end-to-end bearer between the remote device and a network-side device, a triggering condition of a first BSR of the remote device and a third buffer amount, including at least one of the following: In a case where the end-to-end bearer configuration corresponding to the target PDCP entity is a direct bearer, the remote device counts the arrival of first data into the triggering condition of the first BSR, and counts the first data into the third cache amount, wherein the first data includes the data to be transmitted in the PDU corresponding to the SDU of the target PDCP entity and the data in the control PDU of the target PDCP entity, and the target PDCP entity is one of the PDCP entities of the remote device; In a case where the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, duplicate transmission is activated, and the primary path is a direct RLC bearer, the remote device counts the arrival of the first data into the triggering condition of the first BSR, and counts the first data into the third cache amount, or the remote device counts the arrival of the second data into the triggering condition of the first BSR, and counts the second data into the third cache amount, wherein the second data includes the data to be transmitted in the PDU corresponding to the SDU of the target PDCP entity; When the end-to-end bearer corresponding to the target PDCP entity is configured as a separated bearer, duplicate transmission is activated, and the primary path is an indirect RLC bearer, the remote device counts the arrival of the first data into the triggering condition of the first BSR, and counts the first data into the third cache amount, or the remote device counts the arrival of the second data into the triggering condition of the first BSR, and counts the second data into the third cache amount; When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, and the copy transmission is not activated, and the main path is a direct RLC bearer, and the data volume of the third data is less than the third threshold, the remote device counts the arrival of the first data into the triggering condition of the first BSR, and counts the first data into the third cache volume, wherein the third data includes fourth data, data to be initially transmitted in the non-directly connected layer 2 entity of the remote device, and data to be initially transmitted in the RLC entity of the first communication interface of the remote device, and the fourth data includes at least one of data to be initially transmitted in the PDU corresponding to the SDU of the target PDCP entity, data to be retransmitted, and data in the control PDU of the target PDCP entity; When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, and duplicate transmission is not activated, and the primary path is a direct RLC bearer, and the data volume of the third data is greater than or equal to the third threshold, the remote device counts the arrival of the first data into the triggering condition of the first BSR, and counts the first data into the third cache volume, or the remote device counts the arrival of the second data into the triggering condition of the first BSR, and counts the second data into the third cache volume; The end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, and duplicate transmission is not activated, and When the primary path is a non-direct RLC bearer and the data volume of the third data is greater than or equal to a fourth threshold, the remote device counts the arrival of the first data into the triggering condition of the first BSR and counts the first data into the third cache volume, or the remote device counts the arrival of the second data into the triggering condition of the first BSR and counts the second data into the third cache volume; When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer and duplicate transmission is not activated, the remote device counts the arrival of the first data into the triggering condition of the first BSR and counts the first data into the third cache amount.
8. The method according to claim 6 or 7, wherein: The third cache amount includes at least one of the following: The data volume of fifth data, wherein the fifth data includes data to be transmitted in a PDU corresponding to an SDU of an RLC entity of the first communication interface of the remote device, and data in a control PDU of the RLC entity; a data volume of first data when the end-to-end bearer corresponding to the target PDCP entity is configured as a direct bearer, wherein the first data includes data to be transmitted in a PDU corresponding to an SDU of the target PDCP entity and data in a control PDU of the target PDCP entity, and the target PDCP entity is one of the PDCP entities of the remote device; When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer and duplicate transmission is activated and the primary path is a direct RLC bearer, the data volume of the first data or the data volume of the second data, wherein the second data includes the data to be transmitted in the PDU corresponding to the SDU of the target PDCP entity; When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is activated, and the primary path is an indirect RLC bearer, the data volume of the second data or the data volume of the first data; The end-to-end bearer configuration corresponding to the target PDCP entity is a separate bearer and the copy transmission is not activated and the main path is a direct RLC bearer, and the data volume of the third data is less than the third threshold, the data volume of the first data, wherein the third data includes fourth data, data to be initially transmitted in the non-directly connected layer 2 entity of the remote device and data to be initially transmitted in the RLC entity of the first communication interface of the remote device, and the fourth data includes at least one of data to be initially transmitted in the PDU corresponding to the SDU of the target PDCP entity, data to be retransmitted, and data in the control PDU of the target PDCP entity; when the end-to-end bearer configuration corresponding to the target PDCP entity is a separated bearer and duplicate transmission is not activated and the primary path is a direct RLC bearer, and the data volume of the third data is greater than or equal to the third threshold, the data volume of the first data or the data volume of the second data; when the end-to-end bearer configuration corresponding to the target PDCP entity is a separated bearer and duplicate transmission is not activated and the primary path is a non-direct RLC bearer, and the data volume of the third data is greater than or equal to the fourth threshold, the data volume of the second data or the data volume of the first data; The end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, and the data volume of the first data during copy transmission is not activated.
9. A method for processing a cache status report, the method comprising at least one of the following: When the remote device is configured for multipath transmission and the remote device and the relay device are connected in an ideal backhaul or non-standard manner, the relay device determines the relevant information of the third BSR of the relay device according to the configuration mode of the end-to-end bearer between the remote device and the network side device; In the case where the remote device is configured for multipath transmission and the remote device and the relay device are connected via a non-ideal backhaul or a standard connection, the relay device transmits the remote device to the relay device according to the wireless link of the first communication interface of the relay device. A road control protocol RLC entity determines relevant information of the third BSR; in, The third BSR is a buffer status report of the first communication interface, and the first communication interface is a communication interface between the terminal and the network side device.
10. The method according to claim 9, wherein: When there are multiple end-to-end bearers between the remote device and the network side device, one end-to-end bearer corresponds to one Packet Data Convergence Protocol PDCP entity; The relay device determines, according to a configuration mode of an end-to-end bearer between the remote device and the network side device, relevant information of a third BSR of the relay device, including at least one of the following: In a case where the end-to-end bearer corresponding to the target PDCP entity is configured as a non-direct bearer, the relay device counts the arrival of the first data into the triggering condition of the third BSR, and counts the first data into the fourth cache amount of the third BSR, wherein the first data includes the data to be transmitted in the protocol data unit PDU corresponding to the service data unit SDU of the target PDCP entity, and the data in the control PDU of the target PDCP entity, and the target PDCP entity is one of the PDCP entities of the remote device; When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, duplicate transmission is activated, and the primary path is a direct RLC bearer, the relay device counts the arrival of the second data into the triggering condition of the third BSR, and counts the second data into the fourth cache amount, or the relay device counts the arrival of the first data into the triggering condition of the third BSR, and counts the first data into the fourth cache amount, wherein the second data includes the data to be transmitted in the PDU corresponding to the SDU of the target PDCP entity; When the end-to-end bearer corresponding to the target PDCP entity is configured as a separated bearer, duplicate transmission is activated, and the primary path is a non-direct RLC bearer, the relay device counts the arrival of the second data into the triggering condition of the third BSR, and counts the second data into the fourth cache amount, or the relay device counts the arrival of the first data into the triggering condition of the third BSR, and counts the first data into the fourth cache amount; When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, and the copy transmission is not activated, and the main path is a direct RLC bearer, and the data volume of the third data is greater than or equal to the third threshold, the relay device counts the arrival of the second data into the triggering condition of the third BSR, and counts the second data into the fourth cache volume, or the relay device counts the arrival of the first data into the triggering condition of the third BSR, and counts the first data into the fourth cache volume, wherein the third data includes the fourth data, the data to be initially transmitted in the non-directly connected layer 2 entity of the remote device, and the data to be initially transmitted in the RLC entity of the first communication interface of the remote device, and the fourth data includes at least one of the data to be initially transmitted in the PDU corresponding to the SDU of the target PDCP entity, the data to be retransmitted, and the data in the control PDU of the target PDCP entity; When the end-to-end bearer corresponding to the target PDCP entity is configured as a separated bearer, duplicate transmission is not activated, the primary path is an indirect RLC bearer, and the data volume of the third data is less than a fourth threshold, the relay device counts the arrival of the first data into the triggering condition of the third BSR, and counts the first data into the fourth cache volume; When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, and duplicate transmission is not activated, and the primary path is a non-direct RLC bearer, and the data volume of the third data is greater than or equal to the fourth threshold, the relay device counts the arrival of the second data into the triggering condition of the third BSR, and counts the second data into the fourth cache volume, or the relay device counts the arrival of the first data into the triggering condition of the third BSR, and counts the first data into the fourth cache volume; When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer and duplicate transmission is not activated, the relay device counts the arrival of the first data into the triggering condition of the third BSR and counts the first data into the fourth cache amount.
11. The method according to claim 10, wherein: The fourth cache amount includes at least one of the following: The data volume of the seventh data, wherein the seventh data includes the data to be transmitted in the PDU corresponding to the SDU of the RLC entity of the first communication interface of the relay device, and the data in the control PDU of the RLC entity; a data volume of first data when the end-to-end bearer corresponding to the target PDCP entity is configured as a non-direct bearer, wherein the first data includes data to be transmitted in a PDU corresponding to an SDU of the target PDCP entity and data in a control PDU of the target PDCP entity, and the target PDCP entity is one of the PDCP entities of the remote device; When the end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer and duplicate transmission is activated and the primary path is a direct RLC bearer, the data amount of the second data or the data amount of the first data, wherein the second data includes the data to be transmitted in the PDU corresponding to the SDU of the target PDCP entity; When the end-to-end bearer corresponding to the target PDCP entity is configured as a split bearer, duplicate transmission is activated, and the primary path is an indirect RLC bearer, the data volume of the first data or the data volume of the second data; When the end-to-end bearer configuration corresponding to the target PDCP entity is a separate bearer and the copy transmission is not activated and the main path is a direct RLC bearer, and the data volume of the third data is greater than or equal to the third threshold, the data volume of the second data or the data volume of the first data, wherein the third data includes fourth data, data to be initially transmitted in the non-directly connected layer 2 entity of the remote device, and data to be initially transmitted in the RLC entity of the first communication interface of the remote device, and the fourth data includes at least one of data to be initially transmitted in the PDU corresponding to the SDU of the target PDCP entity, data to be retransmitted, and data in the control PDU of the target PDCP entity; when the end-to-end bearer configuration corresponding to the target PDCP entity is a separated bearer and duplicate transmission is not activated and the primary path is a non-direct RLC bearer, and the data volume of the third data is less than a fourth threshold, the data volume of the first data; when the end-to-end bearer configuration corresponding to the target PDCP entity is a separated bearer and duplicate transmission is not activated and the primary path is a non-direct RLC bearer, and the data volume of the third data is greater than or equal to the fourth threshold, the data volume of the first data or the data volume of the second data; The end-to-end bearer corresponding to the target PDCP entity is configured as a separate bearer, and the data volume of the first data during copy transmission is not activated.
12. The method according to claim 9, wherein: The relay device determines, according to the RLC entity of the first communication interface of the relay device, relevant information of the third BSR, including: The relay device counts the arrival of data of the RLC entity of the first communication interface of the relay device into the trigger condition of the third BSR, and counts the seventh data into the data cache amount in the third BSR, wherein the seventh data includes the data to be transmitted in the PDU corresponding to the SDU of the RLC entity of the first communication interface of the relay device, and the data in the control PDU of the RLC entity.
13. The method according to claim 9 or 12, wherein: The method further comprises: When the remote device and the relay device are connected via the second communication interface and the relay device is configured in a network-side device scheduling mode, the relay device performs at least one of the following: The data arrival of the RLC entity of the second communication interface of the relay device is counted into the data of the relay device. a trigger condition of a fourth BSR, and counting the eighth data into the data cache amount of the fourth BSR, wherein the fourth BSR is a cache status report of the second communication interface, and the eighth data includes the data to be transmitted of the PDU corresponding to the SDU of the RLC entity of the second communication interface of the relay device, and the data in the control PDU of the RLC entity, and the second communication interface is a communication interface between terminals; prohibiting processing of the fourth BSR; Only the padded fourth BSR is retained; Not configuring the periodic fourth BSR; The fourth BSR is not configured to be retransmitted.
14. A cache status report processing device, the device comprising: A first processing module, configured to determine, when the remote device is configured for multipath transmission, relevant information of a first BSR of the remote device and relevant information of a second BSR according to a configuration mode of an end-to-end bearer between the remote device and a network-side device, or determine relevant information of the first BSR of the remote device; Among them, the first BSR is a cache status report of the first communication interface, the second BSR is a cache status report of the second communication interface, the first communication interface is a communication interface between the terminal and the network side device, and the second communication interface is a communication interface between terminals.
15. A cache status report processing device, the device comprising at least one of the following modules: A second processing module, configured to determine relevant information of a third BSR of the relay device according to a configuration mode of an end-to-end bearer between the remote device and the network side device when the remote device is configured for multipath transmission and an ideal backhaul or a non-standard connection is established between the remote device and the relay device; A third processing module is used to determine the relevant information of the third BSR according to the radio link control protocol RLC entity of the first communication interface of the relay device when the remote device is configured for multipath transmission and a non-ideal backhaul or a standard connection is between the remote device and the relay device; in, The third BSR is a buffer status report of the first communication interface, and the first communication interface is a communication interface between the terminal and the network side device.
16. A terminal comprising a processor and a memory, wherein the memory stores a program or instruction that can be executed on the processor, and when the program or instruction is executed by the processor, the steps of the cache status report processing method as described in any one of claims 1 to 8 are implemented, or the steps of the cache status report processing method as described in any one of claims 9 to 13 are implemented.
17. A readable storage medium storing a program or instruction, wherein the program or instruction, when executed by a processor, implements the steps of the cache status report processing method as described in any one of claims 1 to 8, or implements the steps of the cache status report processing method as described in any one of claims 9 to 13.
18. A chip, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the steps of the cache status report processing method as described in any one of claims 1 to 8, or to implement the steps of the cache status report processing method as described in any one of claims 9 to 13.
19. A computer program product, wherein the program product is stored in a non-volatile storage medium and is executed by at least one processor to implement the steps of the cache status report processing method as described in any one of claims 1 to 8, or to implement the steps of the cache status report processing method as described in any one of claims 9 to 13.
Citation Information
Patent Citations
Buffer status report transmission method and terminal
CN112055415A
Scheduling request triggering method, information configuration method, terminal and network equipment
CN112566265A
Data transmission method, device and terminal
CN115996481A
Path management with direct device communication
US20220377823A1
Multi-path operation in UE-to-NW sidelink relay
WO2023044758A1
