Multi-path processing method and apparatus, and communication system

Abstract

Provided in the embodiments of the present application are a multi-path processing method and apparatus, and a communication system. The method comprises: using a direct path and an indirect path to communicate with a network device; and triggering or sending a Uu BSR corresponding to the direct path and one BSR in an SL-BSR corresponding to the indirect path, or triggering or sending a first SR associated with the Uu BSR corresponding to the direct path and one SR in a second SR associated with the SL-BSR corresponding to the indirect path, or triggering or sending the first SR and the second SR, wherein the same SR configuration is used for the first SR and the second SR.

Description

Multipath processing method, device and communication system Technical Field

[0001] The embodiments of the present application relate to the field of communication technologies. Background Art

[0002] In Release 18, the 3rd Generation Partnership Project (3GPP) is researching solutions to support multipath to enhance communication reliability and throughput. A multipath scenario involves a remote UE connecting to the same network device (e.g., a gNB) using both a direct path and an indirect path. A direct path involves the UE connecting directly to the network device via the Uu interface, while an indirect path involves the UE connecting to the network device via a Layer 2 (L2) UE-to-Network relay, for example, a relay UE connecting to the network device.

[0003] It should be noted that the above introduction to the technical background is merely for convenience, to provide a clear and complete description of the technical solutions of this application and to facilitate understanding by those skilled in the art. It should not be assumed that the above technical solutions are well known to those skilled in the art simply because they are described in the background technology section of this application.

[0004] Summary of the Invention

[0005] The inventors discovered that for a multi-path bearer, the primary Radio Link Control (RLC) entity and the secondary RLC entity can be associated with a single Medium Access Control (MAC) entity. Because the Uu interface logical channel (Uu LCH) and the side link logical channel (SL LCH) are typically configured in different logical channel groups (LCGs), when data arrives for the multi-path bearer, both the Uu interface buffer status report (BSR) and the side link buffer status report (SL-BSR) may be triggered.

[0006] Since the BSR (Uu BSR) and SL-BSR of the Uu interface are both sent through the direct path, for example, they may both be sent through the primary cell (PCell), which will consume more radio resources in the direct path.

[0007] To address at least one of the above problems, embodiments of the present application provide a multi-path processing method, device, and communication system.

[0008] According to one aspect of an embodiment of the present application, a multi-path processing device is provided, which is configured in a remote terminal device, and the device includes: a first communication unit, which uses a direct path and an indirect path to communicate with a network device; and a first processing unit, which triggers or sends a buffer status report (BSR) of the Uu interface corresponding to the direct path (Uu BSR) and a side link buffer status report (SL-BSR) corresponding to the indirect path.

[0009] According to another aspect of an embodiment of the present application, a multi-path processing device is provided, which is configured in a remote terminal device, wherein the device includes: a second communication unit, which communicates with a network device using a direct path and an indirect path; and a second processing unit, which triggers or sends a first scheduling request (SR) associated with a Uu BSR corresponding to the direct path and a second SR associated with an SL-BSR corresponding to the indirect path, or triggers or sends the first SR and the second SR, wherein the first SR and the second SR use the same SR configuration.

[0010] According to another aspect of an embodiment of the present application, a multi-path processing device is provided, which is configured in a remote terminal device, wherein the device includes: a third communication unit, which communicates with a network device using a direct path and an indirect path, wherein a PDCP entity is associated with a first RLC entity corresponding to the direct path and an SRAP entity corresponding to the indirect path; and a third processing unit, which indicates the PDCP data volume, and the PDCP data volume is used to trigger a BSR.

[0011] According to another aspect of an embodiment of the present application, a multi-path processing device is provided, which is configured in a network device, wherein the device includes: a fourth communication unit, which communicates with a remote terminal device using a direct path and an indirect path; and a first receiving unit, which receives a buffer status report (BSR) of a Uu interface corresponding to the direct path (Uu BSR) and a side link buffer status report (SL-BSR) corresponding to the indirect path.

[0012] According to another aspect of an embodiment of the present application, a multi-path processing device is provided, which is configured in a network device, wherein the device includes: a fifth communication unit, which communicates with the network device using a direct path and an indirect path; and a second receiving unit, which receives one of a first scheduling request (SR) associated with a Uu BSR corresponding to the direct path and a second SR associated with an SL-BSR corresponding to the indirect path, or receives the first SR and the second SR, wherein the first SR and the second SR use the same SR configuration.

[0013] According to another aspect of an embodiment of the present application, a multi-path processing method is provided, which is applied to a remote terminal device, the method comprising: communicating with a network device using a direct path and an indirect path; and triggering or sending a buffer status report (BSR) of a Uu interface corresponding to the direct path (Uu BSR) and a side link buffer status report (SL-BSR) corresponding to the indirect path.

[0014] According to another aspect of an embodiment of the present application, a multi-path processing method is provided, which is applied to a remote terminal device. The method includes: using a direct path and an indirect path to communicate with a network device; and triggering or sending a first scheduling request (SR) associated with a Uu BSR corresponding to the direct path and a second SR associated with an SL-BSR corresponding to the indirect path, or triggering or sending the first SR and the second SR, wherein the first SR and the second SR use the same SR configuration.

[0015] According to another aspect of an embodiment of the present application, a multi-path processing method is provided, which is applied to a remote terminal device, the method comprising: communicating with a network device using a direct path and an indirect path, wherein a PDCP entity is associated with a first RLC entity corresponding to the direct path and an SRAP entity corresponding to the indirect path; and indicating a PDCP data volume, wherein the PDCP data volume is used to trigger a BSR.

[0016] According to another aspect of an embodiment of the present application, a multi-path processing method is provided, which is applied to a network device, the method comprising: communicating with a remote terminal device using a direct path and an indirect path; and receiving a buffer status report (BSR) of a Uu interface corresponding to the direct path (Uu BSR) and a side link buffer status report (SL-BSR) corresponding to the indirect path.

[0017] According to another aspect of an embodiment of the present application, a multi-path processing method is provided, which is applied to a network device. The method includes: communicating with the network device using a direct path and an indirect path; and receiving a first scheduling request (SR) associated with a Uu BSR corresponding to the direct path and a second SR associated with an SL-BSR corresponding to the indirect path, or receiving the first SR and the second SR, wherein the first SR and the second SR use the same SR configuration.

[0018] According to another aspect of an embodiment of the present application, a remote terminal device is provided, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the multi-path processing method on the remote terminal device side.

[0019] According to another aspect of an embodiment of the present application, a network device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the multi-path processing method on the network device side.

[0020] According to another aspect of an embodiment of the present application, a communication system is provided, comprising the above-mentioned remote terminal device and network device.

[0021] One of the beneficial effects of the embodiments of the present application is to reduce wireless resource consumption, save UE power consumption and save uplink wireless resources.

[0022] With reference to the following description and accompanying drawings, specific embodiments of the present application are disclosed in detail, indicating the manner in which the principles of the present application can be employed. It should be understood that the embodiments of the present application are not limited in scope. Within the spirit and scope of the appended claims, the embodiments of the present application include many variations, modifications and equivalents.

[0023] Features described and / or illustrated with respect to one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.

[0024] It should be emphasized that the term "include / comprising" when used herein refers to the presence of features, integers, steps or components, but does not exclude the presence or addition of one or more other features, integers, steps or components. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The elements and features described in one figure or one embodiment of the present application can be combined with the elements and features shown in one or more other figures or embodiments. In addition, in the accompanying drawings, similar reference numerals represent corresponding parts in several figures and can be used to indicate corresponding parts used in more than one embodiment.

[0026] FIG1 is a schematic diagram of a communication system according to an embodiment of the present application;

[0027] FIG2 is a schematic diagram of a multipath scenario according to an embodiment of the present application;

[0028] FIG3 is a schematic diagram of multi-path bearer according to an embodiment of the present application;

[0029] FIG4 is a schematic diagram of the data volume in the protocol entity of the multipath bearer according to an embodiment of the present application;

[0030] 5 to 9 are schematic diagrams of a multi-path processing method according to an embodiment of the present application;

[0031] 10 to 14 are schematic diagrams of a multi-path processing device according to an embodiment of the present application;

[0032] FIG15 is a schematic diagram of the structure of a remote terminal device according to an embodiment of the present application;

[0033] FIG16 is a schematic diagram of the structure of a network device according to an embodiment of the present application. DETAILED DESCRIPTION

[0034] The above and other features of the present application will become apparent through the following description with reference to the accompanying drawings. In the description and the accompanying drawings, specific embodiments of the present application are disclosed in detail, which illustrate some embodiments in which the principles of the present application can be adopted. It should be understood that the present application is not limited to the described embodiments. On the contrary, the present application includes all modifications, variations and equivalents that fall within the scope of the appended claims.

[0035] In the embodiments of the present application, the terms "first," "second," etc. are used to distinguish different elements in terms of title, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one and all combinations of one or more of the associated listed terms. The terms "comprising," "including," "having," etc. refer to the presence of the stated features, elements, components, or components, but do not exclude the presence or addition of one or more other features, elements, components, or components.

[0036] In the embodiments of this application, the singular forms "a," "the," etc. include plural forms and should be broadly understood to mean "a" or "a type" rather than being limited to "one." Furthermore, the term "said" should be understood to include both singular and plural forms, unless the context clearly indicates otherwise. Furthermore, the term "according to" should be understood to mean "at least in part based on...", and the term "based on" should be understood to mean "at least in part based on...", unless the context clearly indicates otherwise.

[0037] In the embodiments of the present application, the term "communication network" or "wireless communication network" may refer to a network that complies with any of the following communication standards, such as Long Term Evolution (LTE), enhanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0038] Furthermore, communication between devices in the communication system may be carried out according to communication protocols of any stage, for example, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G, New Radio (NR), etc., and / or other communication protocols currently known or to be developed in the future.

[0039] In the embodiments of the present application, the term "network device" refers to, for example, a device in a communication system that connects a terminal device to the communication network and provides services to the terminal device. Network devices may include, but are not limited to, the following devices: base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.

[0040] Base stations may include, but are not limited to, NodeB (NB), evolved NodeB (eNodeB or eNB), and 5G base stations (gNB), among others. They may also include remote radio heads (RRHs), remote radio units (RRUs), relays, or low-power nodes (e.g., femeto, pico, etc.). The term "base station" may include some or all of their functions, and each base station may provide communication coverage for a specific geographic area. The term "cell" may refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0041] In the embodiments of the present application, the term "user equipment" (UE) or "terminal equipment" (TE) refers to, for example, a device that accesses a communication network through a network device and receives network services. A terminal device can be fixed or mobile and may also be referred to as a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), a station, and so on.

[0042] Among them, terminal devices may include but are not limited to the following devices: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smart phones, smart watches, digital cameras, wearable devices, etc.

[0043] For another example, in scenarios such as the Internet of Things (IoT), the terminal device can also be a machine or device for monitoring or measurement, including but not limited to: machine type communication (MTC) terminals, vehicle-mounted communication terminals, device-to-device (D2D) terminals, machine-to-machine (M2M) terminals, terminals that support edge links, and the like.

[0044] In addition, the term "network side" or "network device side" refers to one side of the network, which can be a base station or one or more network devices as described above. The term "user side" or "terminal side" or "terminal device side" refers to the user or terminal side, which can be a UE or one or more terminal devices as described above. Unless otherwise specified herein, "device" can refer to either network equipment or terminal equipment.

[0045] Figure 1 is a schematic diagram of a communication system according to an embodiment of the present application, illustrating a situation using a remote terminal device, a relay terminal device, and a network device as an example. As shown in Figure 1 , communication system 100 may include a remote terminal device 101, a relay terminal device 102, and a network device 103. Remote terminal device 101 is connected to network device 103 via a direct path and an indirect path via relay terminal device 102. For simplicity, Figure 1 illustrates only two terminal devices (one remote terminal device and one relay terminal device) and one network device as an example, but embodiments of the present application are not limited thereto.

[0046] In the embodiment of the present application, existing services or future services can be carried out between the network device 103 and the remote terminal device 101 and the relay terminal device 102. For example, these services may include, but are not limited to, enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable and low-latency communication (URLLC), etc.

[0047] Figure 2 is a schematic diagram of a multipath scenario in accordance with an embodiment of the present application. As shown in Figure 2 , in accordance with an embodiment of the present application, a remote terminal device can communicate with a network device (e.g., a gNB) via both a direct path and an indirect path. For example, a remote terminal device can communicate with a network device via a Uu interface (direct path) and communicate with the same network device via a relay terminal device (indirect path).

[0048] For example, the direct path between the remote terminal device and the network device uses the Uu interface protocol stack, the indirect path between the remote terminal device and the network device is transmitted via the relay terminal device, the side link between the remote terminal device and the relay terminal device uses the PC5 interface protocol stack, and the Uu interface protocol stack is used between the relay terminal device and the network device.

[0049] In some embodiments, a multipath bearer can be transmitted using duplication or split transmission. For split bearers (referred to as split bearers) and duplication bearers (referred to as duplication bearers), the concepts of a primary path and a primary RLC entity are used, as defined in the prior art. For duplication bearers, PDCP control PDUs are sent only on the primary RLC entity.

[0050] For split data radio bearers (split DRBs), an uplink data split transmission threshold can be optionally configured. When the sum of the PDCP layer data volume (PDCP data volume), the Uu interface RLC data volume (Uu RLC data volume), and the side link RLC data volume (SL-RLC data volume) exceeds this threshold, PDCP can send data over both the direct and indirect paths.

[0051] Figure 3 is a schematic diagram of a multipath bearer according to an embodiment of the present application. As shown in Figure 3 , in a multipath bearer, bearer types can include bearers transmitted only via direct paths (referred to as direct path bearers, direct bearers), bearers transmitted only via indirect paths (referred to as indirect path bearers, indirect bearers), and bearers transmitted via both direct and indirect paths, i.e., bearers transmitted via multiple paths (referred to as multipath bearers).

[0052] Among them, the PDCP entity corresponding to the direct bearer is associated with one or more Uu RLC entities (RLC entity 3 in Figure 3); the PDCP entity corresponding to the indirect bearer is associated with one or more SRAP entities, and the SRAP entity is associated with one or more SL-RLC entities (RLC entity 4 in Figure 3); the PDCP entity corresponding to the multi-path bearer is associated with a Uu RLC entity (RLC entity 1 in Figure 3) and the SRAP entity of the indirect path, and the SRAP entity is associated with an SL-RLC entity (RLC entity 2 in Figure 3).

[0053] In some embodiments, as shown in FIG3 , multiple paths may be supported by a single MAC entity.

[0054] In some embodiments, as shown in FIG3 , for a direct path bearer, a buffer size in a Uu BSR may be used to indicate data of a logical channel group (Uu LCH) associated with the Uu BSR, where the logical channel group includes at least one logical channel.

[0055] In some embodiments, as shown in FIG3 , for indirect path bearer, the buffer size in the SL-BSR may be used to indicate data of a sidelink logical channel (sidelink LCH) group associated with the SL-BSR, where the sidelink logical channel group includes at least one sidelink logical channel.

[0056] FIG4 is a schematic diagram of the data volume in the protocol entity of the multipath bearer according to an embodiment of the present application. In some embodiments, as shown in FIG4 , for the multipath bearer, the buffer size in the Uu BSR can be used to indicate the sum of the data volume in the PDCP entity corresponding to all logical channels in the logical channel group and the data volume in the Uu RLC entity (RLC entity 1), and the buffer size in the SL-BSR can be used to indicate the sum of the data volume in the PDCP entity corresponding to all logical channels in the logical channel group and the data volume in the SL-RLC entity (RLC entity 2).

[0057] For example, the sum of the data amount D1 in the PDCP entity and the data amount D2 in the Uu RLC entity (RLC entity 1) can be calculated in the buffer size of the Uu BSR, and the sum of the data amount D1 in the PDCP entity and the data amount D3 in the SL-RLC entity (RLC entity 2) can be calculated in the buffer size of the SL-BSR.

[0058] The following describes various implementations of the present application in conjunction with the accompanying drawings. These implementations are merely illustrative and are not intended to limit the present application.

[0059] Embodiments of the first aspect

[0060] The present application embodiment provides a multi-path processing method, which is applied to a remote terminal device. FIG5 is a schematic diagram of the multi-path processing method of the present application embodiment. As shown in FIG5 , the method includes:

[0061] 501, communicating with a network device using a direct path and an indirect path; and

[0062] 502 : Trigger or send a buffer status report (BSR) of a Uu interface corresponding to a direct path (Uu BSR) and a side link buffer status report (SL-BSR) corresponding to an indirect path.

[0063] According to the above embodiment, in a multipath scenario, the remote terminal device triggers or sends one of the cache status report and the edge link cache status report of the Uu interface, thereby reducing the resource consumption of reporting the cache status report, thereby saving power consumption of the remote terminal device and saving uplink wireless resources.

[0064] For example, when the buffer status report of the Uu interface and the buffer status report of the side link need to be reported in the same path or cell, resource consumption can be reduced and resource utilization can be improved.

[0065] In some embodiments, the remote terminal device can communicate with the same network device via a direct path and an indirect path, that is, the remote terminal device is connected to the same network device using a direct path and an indirect path.

[0066] The remote terminal device may be connected to a first cell of the network device, and the relay terminal device may be connected to a second cell of the network device. The first cell and the second cell may be the same cell or different cells.

[0067] In some embodiments, the Uu BSR corresponding to the direct path can also be expressed as BSR, uplink BSR or UL-BSR, which is used to report the buffer status information corresponding to the uplink logical channel group, for example, the amount of data to be transmitted in the uplink logical channel group.

[0068] The SL-BSR corresponding to the indirect path is used to report the buffer status information corresponding to the side link logical channel group, for example, the amount of data to be transmitted in the side link logical channel group.

[0069] In some embodiments, when the logical channel (Uu LCH) and the side link logical channel (SL LCH) of the Uu interface are configured in different logical channel groups (LCG, Logic Chanel Group) and data arrives at the multi-path bearer, the remote terminal device can trigger only one of the Uu BSR and SL-BSR.

[0070] In some embodiments, the triggered BSR may be a BSR corresponding to a primary path or a BSR associated with a primary radio link management (RLC) entity.

[0071] For example, when the primary path is a direct path, the triggered BSR may be a Uu BSR; when the primary path is an indirect path, the triggered BSR may be an SL-BSR.

[0072] For another example, when the BSR associated with the primary RLC entity is a Uu BSR, the triggered BSR may be a Uu BSR; when the BSR associated with the primary RLC entity is a SL-BSR, the triggered BSR may be a SL-BSR.

[0073] In some embodiments, at the remote terminal device side, the MAC entity determines whether to trigger the BSR. The specific manner in which the MAC entity determines whether to trigger the BSR can be described in the form of Table 1.

[0074] Table 1: Example of a MAC entity triggering a BSR

[0075] In some embodiments, the triggered BSR may be a Uu BSR, that is, the triggered BSR may be a Uu BSR associated with an uplink RLC entity.

[0076] For example, the specific manner in which the MAC entity determines whether to trigger the BSR can be described in the form of Table 2.

[0077] Table 2: Example of a MAC entity triggering a BSR

[0078] In some embodiments, the triggered BSR may be a SL-BSR, that is, the triggered BSR may be a SL-BSR associated with a side link RLC entity.

[0079] For example, the specific manner in which the MAC entity determines whether to trigger the BSR can be described in the form of Table 3.

[0080] Table 3: Example of MAC entity triggering BSR

[0081] In some embodiments, the triggered BSR may be a BSR determined based on indication information or configuration information of the network device. In other words, the triggered BSR may be indicated or configured by the network device.

[0082] The indication information or configuration information of the network device may be included in an RRC message or a MAC CE. For example, the indication information or configuration information indicates the BSR used by all multi-path bearers configured for the UE, or indicates the BSR used by each multi-path bearer configured for the UE.

[0083] In some embodiments, the triggered BSR may be a BSR determined based on the priorities of the Uu BSR and the SL-BSR in resource allocation in the current Logical Channel Prioritization (LCP) process, for example, triggering the BSR with a higher priority between the Uu BSR and the SL-BSR.

[0084] In some embodiments, when the logical channel (Uu LCH) and the side link logical channel (SL LCH) of the Uu interface are configured in different logical channel groups (LCGs) and data arrives from a multipath bearer, the remote terminal device can trigger a Uu BSR and an SL-BSR and send one of the triggered Uu BSR and SL-BSR. That is, both the Uu BSR and the SL-BSR will be triggered, but only one of them will be sent.

[0085] In some embodiments, one of a Buffer Status Report Medium Access Control Control Element for Uu Interface (Uu BSR MAC CE) and a Side Link Buffer Status Report Medium Access Control Control Element (SL-BSR MAC CE) is generated.

[0086] For example, the specific manner in which the MAC entity generates the BSR MAC CE may be described in the form of Table 4.

[0087] Table 4: Example of MAC generating BSR MAC CE

[0088] In some embodiments, the remote terminal device may generate one of the Uu BSR MAC CE and the SL-BSR MAC CE in the following manner:

[0089] Based on the priorities of the Uu BSR and the SL-BSR in resource allocation in the current logical channel priority process, one of the Uu BSR MAC CE and the SL-BSR MAC CE is generated, for example, a MAC CE of the BSR with a higher priority between the Uu BSR and the SL-BSR is generated; or

[0090] The Uu BSR MAC CE is generated before the SL-BSR MAC CE; or

[0091] The SL-BSR MAC CE is generated before the Uu BSR MAC CE; or

[0092] A Media Access Control Element (MAC CE) for the BSR corresponding to the primary path is generated or a BSR MAC CE corresponding to the secondary path is not generated, for example, if the direct path is configured as the primary path, a Uu BSR MAC CE is generated or a SL-BSR MAC CE is not generated; or

[0093] Based on configuration information or indication information of the network device, one of the Uu BSR MAC CE and the SL-BSR MAC CE is generated. For example, the indication information or configuration information of the network device may be included in an RRC message or a MAC CE. The configuration information or indication information may instruct the UE which BSR MAC CE to generate in the above situation, or instruct each multi-path bearer configured for the UE which BSR MAC CE to generate in the above situation, etc.; or

[0094] Based on the predefined information, one of the Uu BSR MAC CE and the SL-BSR MAC CE is generated.

[0095] In some embodiments, one of the Uu BSR MAC CE and the SL-BSR MAC CE is included in one media access control packet data unit (MAC PDU).

[0096] For example, the MAC PDU can be described in the form of Table 5.

[0097] Table 5: Example of MAC PDU

[0098] In some embodiments, the remote terminal device may include one of the Uu BSR MAC CE and the SL-BSR MAC CE in a MAC PDU in the following manner:

[0099] Based on the priorities of the Uu BSR and the SL-BSR in resource allocation in the current logical channel priority process, one of the Uu BSR MAC CE and the SL-BSR MAC CE is included in the MAC PDU, for example, the MAC CE of the BSR with a higher priority between the Uu BSR and the SL-BSR is included in the MAC PDU; or

[0100] The Uu BSR MAC CE is included in the MAC PDU before the SL-BSR MAC CE; or

[0101] The SL-BSR MAC CE is included in the MAC PDU before the Uu BSR MAC CE; or

[0102] The MAC CE of the BSR corresponding to the primary path is included in the MAC PDU or the MAC CE of the BSR corresponding to the secondary path is not included in the MAC PDU, for example, if the direct path is configured as the primary path, the Uu BSR MAC CE is included in the MAC PDU or the SL-BSR MAC CE is not included in the MAC PDU; or

[0103] Based on configuration information or indication information of the network device, one of the Uu BSR MAC CE and the SL-BSR MAC CE is included in the MAC PDU. For example, the indication information or configuration information of the network device may be included in an RRC message or a MAC CE. The configuration information or indication information may indicate to the UE which BSR MAC CE is included in the MAC PDU in the above case, or indicate to each multi-path bearer configured for the UE which BSR MAC CE is included in the MAC PDU in the above case; or

[0104] Based on predefined information, one of the Uu BSR MAC CE and the SL-BSR MAC CE is included in the MAC PDU.

[0105] In some embodiments, one of the triggered Uu BSR and SL-BSR is canceled.

[0106] For example, the cancellation of triggered Uu BSR or SL-BSR may be described in the form of Table 6.

[0107] Table 6: Example of cancelling a triggered Uu BSR or SL-BSR

[0108] In some embodiments, one of the triggered Uu BSR and SL-BSR may be canceled as follows:

[0109] Based on the priorities of the Uu BSR and the SL-BSR in resource allocation in the current logical channel priority process, one of the Uu BSR and the SL-BSR is cancelled, for example, the one with the lower priority between the Uu BSR and the SL-BSR is cancelled; or

[0110] The Uu BSR is cancelled in preference to the SL-BSR; or

[0111] The SL-BSR takes precedence over the Uu BSR and is cancelled; or

[0112] The BSR corresponding to the primary path is not cancelled or the BSR corresponding to the secondary path is cancelled. For example, if the direct path is configured as the primary path, the Uu BSR is not cancelled or the SL-BSR is cancelled; or

[0113] Based on configuration information or indication information of the network device, one of the Uu BSR and the SL-BSR is canceled. For example, the indication information or configuration information of the network device may be included in an RRC message or a MAC CE. The configuration information or indication information may instruct the UE which BSR to cancel in the above situation, or instruct each multi-path bearer configured for the UE which BSR to cancel in the above situation; or

[0114] Based on predefined information, one of the Uu BSR and the SL-BSR is canceled.

[0115] It is worth noting that FIG5 above is merely a schematic illustration of an embodiment of the present application, and the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the description of FIG5 above.

[0116] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0117] As can be seen from the above embodiment, in a multipath scenario, a remote terminal device triggers or sends either a Uu interface buffer status report or a side link buffer status report. This reduces the resource consumption of reporting the buffer status report, thereby saving power on the remote terminal device and conserving uplink wireless resources. For example, if the Uu interface buffer status report and the side link buffer status report need to be reported on the same path or cell, resource consumption can be reduced and resource utilization can be improved.

[0118] Embodiments of the second aspect

[0119] The present application provides a multipath processing method for use on a remote terminal device. The contents identical to those of the first aspect are not repeated here. The second aspect can be implemented independently, or in combination with the first aspect.

[0120] FIG6 is a schematic diagram of a multipath processing method according to an embodiment of the present application. As shown in FIG6 , the method includes:

[0121] 601, communicating with a network device using a direct path and an indirect path; and

[0122] 602. Trigger or send one of the Uu BSR association or the first scheduling request (SR) corresponding to the direct path and the SL-BSR association or the second SR corresponding to the indirect path, or trigger or send the first SR and the second SR, where the first SR and the second SR use the same SR configuration.

[0123] In some embodiments, for a multipath bearer, if both the Uu BSR and the SL-BSR are triggered or can be sent (for example, the Uu BSR and the SL-BSR are triggered or sent according to their respective conditions), if there are no uplink resources available for new transmission (for example, there are no uplink resources for transmitting the Uu BSR and the SL-BSR) or the uplink resources available for new transmission cannot accommodate the Uu BSR MAC CE plus its subheader or the SL-BSR plus its subheader, etc., the Uu BSR and the SL-BSR will each trigger the associated SR, which will increase the consumption of uplink resources.

[0124] According to the above embodiment, in a multipath scenario, the remote terminal device triggers or sends one of the first SR associated with the Uu BSR and the second SR associated with the SL-BSR, or uses the same SR configuration to trigger or send the first SR and the second SR. This can avoid unnecessary SR reporting and reduce resource consumption for reporting SR, thereby saving power consumption of the remote terminal device and saving uplink wireless resources.

[0125] In some embodiments, the remote terminal device may trigger or send one of the first SR and the second SR in the following manner:

[0126] Based on the priorities of the Uu BSR and the SL-BSR in resource allocation in the current logical channel priority processing, an associated SR between the Uu BSR and the SL-BSR is triggered or sent, for example, the SR associated with the BSR with a higher priority between the Uu BSR and the SL-BSR is triggered or sent; or

[0127] The first SR associated with the Uu BSR is triggered or sent before the second SR associated with the SL-BSR; or

[0128] The second SR associated with the SL-BSR is triggered or sent before the first SR associated with the Uu BSR; or

[0129] The SR associated with the BSR corresponding to the primary path is triggered or sent, or the SR associated with the BSR corresponding to the secondary path is not triggered or sent. For example, if the direct path is configured as the primary path, the SR associated with the Uu BSR corresponding to the direct path is triggered or sent, or the SR associated with the SL-BSR corresponding to the indirect path is not triggered or sent; or

[0130] Based on configuration information or indication information of the network device, one of the associated SRs between the Uu BSR and the SL-BSR is triggered or sent. For example, the configuration information or indication information of the network device may be included in an RRC message or a MAC CE. The configuration information or indication information may indicate which SR the UE should trigger or send in the above situation, or indicate which SR should be triggered or sent for each multi-path bearer configured for the UE; or

[0131] Based on predefined information, one of the associated SRs among the Uu BSR and the SL-BSR is triggered or sent.

[0132] In some embodiments, when both the first SR and the second SR are triggered or sent, the first SR and the second SR use the same SR configuration. The terminal device can determine the order in which the first SR and the second SR are sent based on the following method:

[0133] Determine the order in which the first SR and the second SR are sent based on the priorities of the Uu BSR and the SL-BSR in resource allocation in the current logical channel priority processing, for example, the SR associated with the BSR with a higher priority between the Uu BSR and the SL-BSR is sent first; or

[0134] The first SR associated with the Uu BSR is sent before the second SR associated with the SL-BSR; or

[0135] The second SR associated with the SL-BSR is sent before the first SR associated with the Uu BSR; or

[0136] The SR associated with the BSR corresponding to the primary path is sent first, or the SR associated with the BSR corresponding to the secondary path is sent later. For example, if the direct path is configured as the primary path, the SR associated with the Uu BSR corresponding to the direct path is sent first, or the SR associated with the SL-BSR corresponding to the indirect path is sent later; or

[0137] Determine the order in which the first SR and the second SR are sent based on configuration information or indication information of the network device. For example, the configuration information or indication information of the network device may be included in an RRC message or a MAC CE. The configuration information or indication information may indicate which SR the UE should send first or later in the above situation, or indicate which SR should be sent first or later for each multi-path bearer configured for the UE; or

[0138] Based on the predefined information, the order in which the first scheduling request and the second scheduling request are sent is determined, that is, one of the associated SRs of the Uu BSR and the SL-BSR is sent first.

[0139] In some embodiments, the SR configuration may include a set of physical uplink control channel (PUCCH) resources configured for the SR in different partial bandwidths (BWPs) and cells. The present application is not limited thereto, and the SR configuration may also include other content.

[0140] It is worth noting that FIG6 above is merely a schematic illustration of an embodiment of the present application, and the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the description of FIG6 above.

[0141] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0142] It can be seen from the above embodiments that in a multipath scenario, the remote terminal device triggers or sends one of the first SR associated with the Uu BSR and the second SR associated with the SL-BSR, or uses the same SR configuration to trigger or send the first SR and the second SR. This can avoid unnecessary SR reporting and reduce resource consumption for reporting SR, thereby saving power consumption of the remote terminal device and saving uplink wireless resources.

[0143] Embodiments of the third aspect

[0144] The present application provides a multipath processing method for use on a remote terminal device. The contents identical to those of the first and second aspects are not repeated here. The third aspect may be implemented independently, or in combination with the first and / or second aspects.

[0145] FIG7 is a schematic diagram of a multipath processing method according to an embodiment of the present application. As shown in FIG7 , the method includes:

[0146] 701, communicating with a network device using a direct path and an indirect path, wherein a PDCP entity is associated with a first RLC entity corresponding to the direct path and an SRAP entity corresponding to the indirect path; and 702, indicating a PDCP data volume, where the PDCP data volume is used to trigger a BSR.

[0147] In some embodiments, in 701, as shown in FIG3 and FIG4, for a multipath bearer, one PDCP entity is associated with a first RLC entity (RLC entity 1) corresponding to a direct path and one SRAP entity corresponding to an indirect path. One SRAP entity is associated with a second RLC entity (RLC entity 2).

[0148] In some embodiments, one of the first RLC entity and the second RLC entity is configured as a master RLC entity. For example, if the direct path is the master path, the first RLC entity is configured as the master RLC entity; if the indirect path is the master path, the second RLC entity is configured as the master RLC entity.

[0149] In some embodiments, the first RLC entity and the SRAP entity correspond to one MAC entity. The present application is not limited thereto, and the first RLC entity and the SRAP entity may also correspond to different MAC entities.

[0150] In some embodiments, in 702, the PDCP entity may indicate the data amount to the MAC entity, whereby the MAC entity may trigger a BSR based on the data amount or calculate a buffer size (BS). The manner in which the MAC entity triggers or sends a BSR may refer to the contents described in the embodiment of the first aspect.

[0151] In some embodiments, the PDCP entity may indicate the data amount to the MAC entity in the following manner. For example, when PDCP repetition is activated: indicating the PDCP data amount to the MAC entity associated with the primary RLC entity; and / or indicating the PDCP data amount excluding PDCP control PDUs to the MAC entity associated with an RLC entity other than the primary RLC entity for which PDCP repetition is activated; and / or indicating that the PDCP data amount is 0 to the MAC entity associated with the RLC entity for which PDCP repetition is deactivated.

[0152] In some embodiments, the PDCP entity may also indicate the data amount to the MAC entity in the following manner: For example, if a split secondary RLC entity is configured and the total amount of PDCP data and the amount of RLC data to be transmitted in the primary path and the secondary path is greater than or equal to a preset threshold, the PDCP data amount is indicated to the MAC entity associated with the primary RLC entity and the split secondary RLC entity; and / or the PDCP data amount is indicated to the MAC entity associated with RLC entities other than the primary RLC entity and the split secondary RLC entity as 0.

[0153] In some embodiments, the PDCP entity may also indicate the data amount to the MAC entity in the following manner: for example, if a split secondary RLC entity is not configured, indicating the PDCP data amount to the MAC entity associated with the primary RLC entity; and / or indicating that the PDCP data amount is 0 to the MAC entity associated with an RLC entity other than the primary RLC entity.

[0154] For example, the way in which the PDCP entity indicates the amount of data can be described in the form of Table 7.

[0155] Table 7: Example of PDCP entity indicating data volume

[0156] In some embodiments, the split secondary RLC entity may be an RLC entity other than the primary RLC entity. For example, the split secondary RLC entity may be described in the form of Table 8.

[0157] Table 8: Example of splitting a secondary RLC entity

[0158] It is worth noting that FIG7 above is merely a schematic illustration of an embodiment of the present application, and the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the description of FIG7 above.

[0159] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0160] As can be seen from the above embodiment, when a remote terminal device communicates with a network device using a direct path and an indirect path, a PDCP entity is associated with a first RLC entity corresponding to the direct path and an SRAP entity corresponding to the indirect path. The PDCP entity indicates the PDCP data volume to the MAC entity. The MAC entity can then properly trigger a BSR based on the data volume, thereby facilitating proper allocation of uplink radio resources.

[0161] Embodiments of the fourth aspect

[0162] The embodiment of the present application provides a multi-path processing method, which is applied to a network device side. The contents that are the same as those of the embodiments of the first to third aspects are not repeated here.

[0163] FIG8 is a schematic diagram of a multipath processing method according to an embodiment of the present application. As shown in FIG8 , the method includes:

[0164] 801, communicating with a remote terminal device using a direct path and an indirect path; and

[0165] 802 : Receive a buffer status report (BSR) from a buffer status report (Uu BSR) of a Uu interface corresponding to a direct path and a side link buffer status report (SL-BSR) corresponding to an indirect path.

[0166] In some embodiments, the received BSR is a BSR corresponding to a primary path or a BSR associated with a primary radio link management (RLC) entity.

[0167] In some embodiments, the received BSR is the Uu BSR.

[0168] In some embodiments, the received BSR is the SL-BSR.

[0169] In some embodiments, the received BSR is a BSR determined based on indication information or configuration information of the network device.

[0170] In some embodiments, the received BSR is a BSR determined based on the priorities of the Uu BSR and the SL-BSR in resource allocation in the current logical channel priority process.

[0171] In some embodiments, one of a Buffer Status Report Medium Access Control Control Element for a Uu Interface (Uu BSR MAC CE) and a Side Link Buffer Status Report Medium Access Control Control Element (SL-BSR MAC CE) is received.

[0172] In some embodiments, one of the Uu BSR MAC CE and the SL-BSR MAC CE is received based on the priorities of the Uu BSR and the SL-BSR in resource allocation in the current logical channel priority process; or

[0173] The Uu BSR MAC CE is received before the SL-BSR MAC CE; or

[0174] The SL-BSR MAC CE is received before the Uu BSR MAC CE; or

[0175] The media access control element (MAC CE) of the BSR corresponding to the primary path is received; or

[0176] Based on configuration information or instruction information of the network device, one of a Uu BSR MAC CE and a SL-BSR MAC CE is received; or

[0177] Based on the predefined information, one of the Uu BSR MAC CE and the SL-BSR MAC CE is received.

[0178] In some embodiments, one of the Uu BSR MAC CE and the SL-BSR MAC CE is included in one media access control packet data unit (MAC PDU).

[0179] In some embodiments, one of the Uu BSR MAC CE and the SL-BSR MAC CE is included in the MAC PDU based on the priorities of the Uu BSR and the SL-BSR in resource allocation in the current logical channel priority process; or

[0180] The Uu BSR MAC CE is included in the MAC PDU before the SL-BSR MAC CE; or

[0181] The SL-BSR MAC CE is included in the MAC PDU before the Uu BSR MAC CE; or

[0182] The MAC CE of the BSR corresponding to the primary path is included in the MAC PDU; or

[0183] Based on configuration information or instruction information of the network device, one of the Uu BSR MAC CE and the SL-BSR MAC CE is included in the MAC PDU; or

[0184] Based on predefined information, one of the Uu BSR MAC CE and the SL-BSR MAC CE is included in the MAC PDU.

[0185] It is worth noting that FIG8 above is merely a schematic illustration of an embodiment of the present application, and the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the description of FIG8 above.

[0186] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0187] As can be seen from the above embodiment, in a multipath scenario, a network device receives either a Uu interface buffer status report or a side link buffer status report. This reduces the resource consumption of reporting the buffer status report, thereby saving power on the remote terminal device and conserving uplink wireless resources. For example, if the Uu interface buffer status report and the side link buffer status report need to be reported on the same path or cell, this can reduce resource consumption and improve resource utilization.

[0188] Embodiments of the fifth aspect

[0189] The embodiment of the present application provides a multi-path processing method, which is applied to a network device side. The contents that are the same as those of the embodiments of the first to fourth aspects are not repeated here.

[0190] FIG9 is a schematic diagram of a multipath processing method according to an embodiment of the present application. As shown in FIG9 , the method includes:

[0191] 901, communicating with a network device using a direct path and an indirect path; and

[0192] 902. Receive one of a first scheduling request (SR) associated with a Uu BSR corresponding to a direct path and a second SR associated with an SL-BSR corresponding to an indirect path, or receive the first SR and the second SR, wherein the first SR and the second SR use the same SR configuration.

[0193] In some embodiments, based on the priorities of said Uu BSR and said SL-BSR in resource allocation in the current logical channel priority process, an associated SR of the Uu BSR and the SL-BSR is received; or

[0194] The first SR associated with the Uu BSR is received before the second SR associated with the SL-BSR; or

[0195] The second SR associated with the SL-BSR is received before the first SR associated with the Uu BSR; or

[0196] The SR associated with the BSR corresponding to the primary path is received; or

[0197] Based on configuration information or instruction information of the network device, an associated SR of the Uu BSR and the SL-BSR is received; or

[0198] Based on predefined information, an associated SR of one of the Uu BSR and the SL-BSR is received.

[0199] In some embodiments, the SR configuration includes a set of physical uplink control channel (PUCCH) resources configured for the SR in different part bandwidths (BWPs) and cells.

[0200] It is worth noting that FIG9 above is merely a schematic illustration of an embodiment of the present application, and the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the description of FIG9 above.

[0201] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0202] It can be seen from the above embodiments that in a multipath scenario, the network device receives one of the first SR associated with the Uu BSR and the second SR associated with the SL-BSR, or receives the first SR and the second SR using the same SR configuration. This can reduce the resource consumption of reporting the SR, thereby saving power consumption of the remote terminal device and saving uplink wireless resources.

[0203] Embodiments of the sixth aspect

[0204] The embodiment of the present application provides a multi-path processing device, which can be, for example, a remote terminal device, or one or more components or assemblies configured in the remote terminal device, and the same contents as those in the embodiment of the first aspect will not be repeated.

[0205] FIG10 is a schematic diagram of a multi-path processing device according to an embodiment of the present application. As shown in FIG10 , the multi-path processing device 1000 includes:

[0206] A first communication unit 1001 that communicates with a network device using a direct path and an indirect path; and

[0207] The first processing unit 1002 triggers or sends a buffer status report (BSR) of a Uu interface corresponding to the direct path (Uu BSR) and a side link buffer status report (SL-BSR) corresponding to the indirect path.

[0208] In some embodiments, the triggered BSR is a BSR corresponding to a primary path or a BSR associated with a primary radio link management (RLC) entity.

[0209] In some embodiments, the triggered BSR is the Uu BSR.

[0210] In some embodiments, the triggered BSR is the SL-BSR.

[0211] In some embodiments, the triggered BSR is a BSR determined based on indication information or configuration information of the network device.

[0212] In some embodiments, the triggered BSR is a BSR determined based on the priorities of the Uu BSR and the SL-BSR in resource allocation in the current logical channel priority process.

[0213] In some embodiments, the Uu BSR and the SL-BSR are triggered, and one of the Uu BSR and the SL-BSR is sent.

[0214] In some embodiments, one of a Buffer Status Report Medium Access Control Control Element for Uu Interface (Uu BSR MAC CE) and a Side Link Buffer Status Report Medium Access Control Control Element (SL-BSR MAC CE) is generated.

[0215] In some embodiments, one of the Uu BSR MAC CE and the SL-BSR MAC CE is generated based on the priorities of the Uu BSR and the SL-BSR in resource allocation in the current logical channel priority process; or

[0216] The Uu BSR MAC CE is generated prior to the SL-BSR MAC CE; or

[0217] The SL-BSR MAC CE is generated prior to the Uu BSR MAC CE; or

[0218] A media access control element (MAC CE) for the BSR corresponding to the primary path is generated; or

[0219] Based on the configuration information or instruction information of the network device, one of the Uu BSR MAC CE and the SL-BSR MAC CE is generated; or

[0220] Based on the predefined information, one of the Uu BSR MAC CE and the SL-BSR MAC CE is generated.

[0221] In some embodiments, one of the Uu BSR MAC CE and the SL-BSR MAC CE is included in one media access control packet data unit (MAC PDU).

[0222] In some embodiments, one of the Uu BSR MAC CE and the SL-BSR MAC CE is included in the MAC PDU based on the priorities of the Uu BSR and the SL-BSR in resource allocation in the current logical channel priority process; or

[0223] The Uu BSR MAC CE is included in the MAC PDU before the SL-BSR MAC CE; or

[0224] The SL-BSR MAC CE is included in the MAC PDU before the Uu BSR MAC CE; or

[0225] The MAC CE of the BSR corresponding to the primary path is included in the MAC PDU; or

[0226] Based on configuration information or instruction information of the network device, one of the Uu BSR MAC CE and the SL-BSR MAC CE is included in the MAC PDU; or

[0227] Based on predefined information, one of the Uu BSR MAC CE and the SL-BSR MAC CE is included in the MAC PDU.

[0228] In some embodiments, one of the triggered Uu BSR and the triggered SL-BSR is canceled.

[0229] In some embodiments, based on the priorities of the Uu BSR and the SL-BSR in resource allocation in the current logical channel priority process, one of the Uu BSR and the SL-BSR is cancelled; or

[0230] The Uu BSR is cancelled in preference to the SL-BSR; or

[0231] The SL-BSR is cancelled in preference to the Uu BSR; or

[0232] The BSR corresponding to the primary path is not cancelled or the BSR corresponding to the secondary path is cancelled; or

[0233] Based on configuration information or instruction information of the network device, one of the Uu BSR and the SL-BSR is cancelled; or

[0234] Based on predefined information, one of the Uu BSR and the SL-BSR is canceled.

[0235] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0236] It is worth noting that the above description only describes the components or modules related to the present application, but the present application is not limited thereto. The multi-path processing device 1000 may also include other components or modules. For details of these components or modules, please refer to the relevant art.

[0237] In addition, for the sake of simplicity, FIG10 only illustrates the connection relationship or signal direction between various components or modules. However, it should be clear to those skilled in the art that various related technologies such as bus connection can be used. The above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; the implementation of this application is not limited to this.

[0238] According to the above embodiment, in a multipath scenario, a remote terminal device triggers or sends either a Uu interface buffer status report or a side link buffer status report. This reduces the resource consumption associated with reporting the buffer status report, thereby saving power on the remote terminal device and conserving uplink wireless resources. For example, if the Uu interface buffer status report and the side link buffer status report need to be reported on the same path or cell, this can reduce resource consumption and improve resource utilization.

[0239] Embodiments of the seventh aspect

[0240] The embodiment of the present application provides a multi-path processing device, which may be, for example, a remote terminal device, or one or more components or assemblies configured in the remote terminal device, and the same contents as those in the embodiment of the second aspect will not be repeated here.

[0241] FIG11 is a schematic diagram of a multi-path processing device according to an embodiment of the present application. As shown in FIG11 , the multi-path processing device 1100 includes:

[0242] A second communication unit 1101 that communicates with the network device using a direct path and an indirect path; and

[0243] The second processing unit 1102 triggers or sends one of the first scheduling request (SR) associated with the Uu BSR corresponding to the direct path and the second SR associated with the SL-BSR corresponding to the indirect path, or triggers or sends the first SR and the second SR, where the first SR and the second SR use the same SR configuration.

[0244] In some embodiments, based on the priorities of the Uu BSR and the SL-BSR in resource allocation in the current logical channel priority process, an associated SR of the Uu BSR and the SL-BSR is triggered or sent; or

[0245] The first SR associated with the Uu BSR is triggered or sent before the second SR associated with the SL-BSR; or

[0246] The second SR associated with the SL-BSR is triggered or sent before the first SR associated with the Uu BSR; or

[0247] The SR associated with the BSR corresponding to the primary path is triggered or sent; or

[0248] Based on the configuration information or instruction information of the network device, an associated SR between the Uu BSR and the SL-BSR is triggered or sent; or

[0249] Based on predefined information, an associated SR of one of the Uu BSR and the SL-BSR is triggered or sent.

[0250] In some embodiments, when both the first SR and the second SR are triggered or sent, the first SR and the second SR use the same SR configuration. The terminal device can determine the order in which the first SR and the second SR are sent based on the following method:

[0251] Determine the order in which the first SR and the second SR are sent based on the priorities of the Uu BSR and the SL-BSR in resource allocation in the current logical channel priority processing; or

[0252] The first SR associated with the Uu BSR is sent before the second SR associated with the SL-BSR; or

[0253] The second SR associated with the SL-BSR is sent before the first SR associated with the Uu BSR; or

[0254] The SR associated with the BSR corresponding to the primary path is sent first, or the SR associated with the BSR corresponding to the secondary path is sent later; or

[0255] Determine the order in which the first SR and the second SR are sent based on configuration information or instruction information of the network device; or

[0256] Based on the predefined information, an order in which the first scheduling request and the second scheduling request are sent is determined.

[0257] In some embodiments, the SR configuration includes a set of physical uplink control channel (PUCCH) resources configured for the SR in different bandwidth parts (BWPs) and cells.

[0258] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0259] It should be noted that the above description only describes the components or modules related to the present application, but the present application is not limited thereto. The multi-path processing device 1100 may also include other components or modules. For details of these components or modules, reference may be made to related technologies.

[0260] In addition, for the sake of simplicity, FIG11 only illustrates the connection relationship or signal direction between various components or modules. However, it should be clear to those skilled in the art that various related technologies such as bus connection can be used. The above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; the implementation of this application is not limited to this.

[0261] According to the above embodiment, in a multipath scenario, the remote terminal device triggers or sends one of the first SR associated with the Uu BSR and the second SR associated with the SL-BSR, or uses the same SR configuration to trigger or send the first SR and the second SR. This can avoid unnecessary SR reporting and reduce resource consumption for reporting SR, thereby saving power consumption of the remote terminal device and saving uplink wireless resources.

[0262] Embodiments of the eighth aspect

[0263] The embodiment of the present application provides a multi-path processing device, which may be, for example, a remote terminal device, or one or more components or assemblies configured in the remote terminal device, and the contents identical to those in the embodiment of the third aspect will not be repeated.

[0264] FIG12 is a schematic diagram of a multi-path processing device according to an embodiment of the present application. As shown in FIG12 , the multi-path processing device 1200 includes:

[0265] A third communication unit 1201 communicates with a network device using a direct path and an indirect path, wherein a PDCP entity is associated with a first RLC entity corresponding to the direct path and an SRAP entity corresponding to the indirect path; and

[0266] The third processing unit 1202 indicates the amount of PDCP data, where the amount of PDCP data is used to trigger a BSR.

[0267] In some embodiments, the SRAP entity corresponds to a second RLC entity.

[0268] In some embodiments, one of the first RLC entity and the second RLC entity is configured as a master RLC entity.

[0269] In some embodiments, the first RLC entity and the SRAP entity correspond to one MAC entity.

[0270] In some embodiments, when PDCP repetition is activated,

[0271] Indicating the amount of PDCP data to the MAC entity associated with the primary RLC entity; and / or

[0272] indicating to a MAC entity associated with an RLC entity other than a primary RLC entity for PDCP reactivation an amount of PDCP data excluding PDCP control PDUs; and / or

[0273] Indicates to the MAC entity associated with the RLC entity for PDCP reactivation that the PDCP data amount is 0.

[0274] In some embodiments, when the split secondary RLC entity is configured and the total amount of PDCP data and the amount of RLC data to be transmitted in the primary path and the secondary path is greater than or equal to a preset threshold,

[0275] indicating the amount of PDCP data to a MAC entity associated with the primary RLC entity and the split secondary RLC entity; and / or

[0276] Indicate to a MAC entity associated with an RLC entity other than the primary RLC entity and the split secondary RLC entity that the PDCP data amount is 0.

[0277] In some embodiments, when the split secondary RLC entity is not configured,

[0278] Indicating the amount of PDCP data to the MAC entity associated with the primary RLC entity; and / or

[0279] Indicates to the MAC entity associated with the RLC entity other than the primary RLC entity that the PDCP data amount is 0.

[0280] In some embodiments, the split secondary RLC entity is an RLC entity other than the primary RLC entity.

[0281] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0282] It is worth noting that the above description only describes the components or modules related to the present application, but the present application is not limited thereto. The multi-path processing device 1200 may also include other components or modules. For details of these components or modules, please refer to the relevant art.

[0283] In addition, for the sake of simplicity, FIG12 only illustrates the connection relationship or signal direction between various components or modules. However, it should be clear to those skilled in the art that various related technologies such as bus connection can be used. The above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; the implementation of this application is not limited to this.

[0284] According to the above embodiment, when a remote terminal device communicates with a network device using a direct path and an indirect path, a PDCP entity is associated with a first RLC entity corresponding to the direct path and an SRAP entity corresponding to the indirect path. The PDCP entity indicates the PDCP data volume to the MAC entity. Thus, the MAC entity can properly trigger a BSR based on the data volume, thereby facilitating proper allocation of uplink radio resources.

[0285] Embodiments of the ninth aspect

[0286] The embodiment of the present application provides a multi-path processing device, which may be, for example, a network device, or one or more components or assemblies configured in the network device, and the same contents as those in the embodiment of the fourth aspect will not be repeated here.

[0287] FIG13 is a schematic diagram of a multi-path processing device according to an embodiment of the present application. As shown in FIG13 , the multi-path processing device 1300 includes:

[0288] a fourth communication unit 1301 that communicates with a remote terminal device using a direct path and an indirect path; and

[0289] The first receiving unit 1302 receives a buffer status report (BSR) of a Uu interface corresponding to a direct path (Uu BSR) and a side link buffer status report (SL-BSR) corresponding to an indirect path.

[0290] In some embodiments, the received BSR is a BSR corresponding to a primary path or a BSR associated with a primary radio link management (RLC) entity.

[0291] In some embodiments, the received BSR is the Uu BSR.

[0292] In some embodiments, the received BSR is the SL-BSR.

[0293] In some embodiments, the received BSR is a BSR determined based on indication information or configuration information of the network device.

[0294] In some embodiments, the received BSR is a BSR determined based on the priorities of the Uu BSR and the SL-BSR in resource allocation in the current logical channel priority process.

[0295] In some embodiments, one of a Buffer Status Report Medium Access Control Control Element for a Uu Interface (Uu BSR MAC CE) and a Side Link Buffer Status Report Medium Access Control Control Element (SL-BSR MAC CE) is received.

[0296] In some embodiments, one of the Uu BSR MAC CE and the SL-BSR MAC CE is received based on the priorities of the Uu BSR and the SL-BSR in resource allocation in the current logical channel priority process; or

[0297] The Uu BSR MAC CE is received before the SL-BSR MAC CE; or

[0298] The SL-BSR MAC CE is received before the Uu BSR MAC CE; or

[0299] The media access control element (MAC CE) of the BSR corresponding to the primary path is received; or

[0300] Based on configuration information or instruction information of the network device, one of a Uu BSR MAC CE and a SL-BSR MAC CE is received; or

[0301] Based on the predefined information, one of the Uu BSR MAC CE and the SL-BSR MAC CE is received.

[0302] In some embodiments, one of the Uu BSR MAC CE and the SL-BSR MAC CE is included in one media access control packet data unit (MAC PDU).

[0303] In some embodiments, one of the Uu BSR MAC CE and the SL-BSR MAC CE is included in the MAC PDU based on the priorities of the Uu BSR and the SL-BSR in resource allocation in the current logical channel priority process; or

[0304] The Uu BSR MAC CE is included in the MAC PDU before the SL-BSR MAC CE; or

[0305] The SL-BSR MAC CE is included in the MAC PDU before the Uu BSR MAC CE; or

[0306] The MAC CE of the BSR corresponding to the primary path is included in the MAC PDU; or

[0307] Based on configuration information or instruction information of the network device, one of the Uu BSR MAC CE and the SL-BSR MAC CE is included in the MAC PDU; or

[0308] Based on predefined information, one of the Uu BSR MAC CE and the SL-BSR MAC CE is included in the MAC PDU.

[0309] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0310] It is worth noting that the above description only describes the components or modules related to the present application, but the present application is not limited thereto. The multi-path processing device 1300 may also include other components or modules. For details of these components or modules, reference may be made to related technologies.

[0311] In addition, for the sake of simplicity, FIG13 only illustrates the connection relationship or signal direction between various components or modules. However, it should be clear to those skilled in the art that various related technologies such as bus connection can be used. The above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; the implementation of this application is not limited to this.

[0312] According to the above embodiment, in a multipath scenario, a network device receives either a Uu interface buffer status report or a side link buffer status report. This reduces resource consumption for reporting the buffer status report, thereby saving power in the remote terminal device and conserving uplink wireless resources. For example, if the Uu interface buffer status report and the side link buffer status report need to be reported on the same path or cell, resource consumption can be reduced and resource utilization can be improved.

[0313] Embodiments of the tenth aspect

[0314] The embodiment of the present application provides a multi-path processing device, which can be, for example, a network device, or one or more components or assemblies configured on the network device, and the same contents as those in the embodiment of the fifth aspect will not be repeated here.

[0315] FIG14 is a schematic diagram of a multi-path processing device according to an embodiment of the present application. As shown in FIG14 , the multi-path processing device 1400 includes:

[0316] a fifth communication unit 1401 that communicates with the network device using a direct path and an indirect path; and

[0317] The second receiving unit 1402 receives one of a first scheduling request (SR) associated with a Uu BSR corresponding to a direct path and a second SR associated with an SL-BSR corresponding to an indirect path, or receives the first SR and the second SR, wherein the first SR and the second SR use the same SR configuration.

[0318] In some embodiments, based on the priorities of said Uu BSR and said SL-BSR in resource allocation in the current logical channel priority process, an associated SR of the Uu BSR and the SL-BSR is received; or

[0319] The first SR associated with the Uu BSR is received before the second SR associated with the SL-BSR; or

[0320] The second SR associated with the SL-BSR is received before the first SR associated with the Uu BSR; or

[0321] The SR associated with the BSR corresponding to the primary path is received; or

[0322] Based on configuration information or instruction information of the network device, an associated SR of the Uu BSR and the SL-BSR is received; or

[0323] Based on predefined information, an associated SR of one of the Uu BSR and the SL-BSR is received.

[0324] In some embodiments, the SR configuration includes a set of physical uplink control channel (PUCCH) resources configured for the SR in different part bandwidths (BWPs) and cells.

[0325] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0326] It should be noted that the above description only describes the components or modules related to the present application, but the present application is not limited thereto. The multi-path processing device 1400 may also include other components or modules. For details of these components or modules, reference may be made to related technologies.

[0327] In addition, for the sake of simplicity, FIG14 only illustrates the connection relationship or signal direction between various components or modules. However, it should be clear to those skilled in the art that various related technologies such as bus connection can be used. The above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; the implementation of this application is not limited to this.

[0328] According to the above embodiment, in a multipath scenario, the network device receives one of the first SR associated with the Uu BSR and the second SR associated with the SL-BSR, or receives the first SR and the second SR using the same SR configuration. This can reduce the resource consumption of reporting the SR, thereby saving power consumption of the remote terminal device and saving uplink wireless resources.

[0329] Embodiment of the eleventh aspect

[0330] An embodiment of the present application provides a communication system, and reference may be made to FIG1 . The contents identical to those in the first to tenth embodiments will not be repeated here.

[0331] In some embodiments, the communication system 100 may include: a remote terminal device 101 and / or a relay terminal device 102 and / or a network device 103 .

[0332] In an embodiment of the present application, the remote terminal device 101 is configured to execute the multi-path processing method described in the embodiments of the first aspect and / or the second aspect and / or the third aspect, the contents of which are incorporated herein and will not be repeated here.

[0333] In an embodiment of the present application, the network device 103 is configured to execute the multi-path processing method described in the embodiments of the fourth aspect and / or the fifth aspect, the contents of which are incorporated herein and will not be repeated here.

[0334] An embodiment of the present application also provides a remote terminal device.

[0335] Figure 15 is a schematic diagram of the structure of a terminal device according to an embodiment of the present application, which may be a remote terminal device. As shown in Figure 15 , terminal device 1500 may include a processor 1501 and a memory 1502. Memory 1502 stores data and programs and is coupled to processor 1501. It should be noted that this diagram is exemplary; other types of structures may be used to supplement or replace this structure to implement telecommunication or other functions.

[0336] For example, the processor 1501 may be configured to execute a program to implement the multipath processing method as described in the embodiment of the first aspect. For example, the processor 1501 may be configured to perform the following operations: communicate with a network device using a direct path and an indirect path; and trigger or send a buffer status report (BSR) of a Uu interface corresponding to the direct path (Uu BSR) and a side link buffer status report (SL-BSR) corresponding to the indirect path.

[0337] For another example, the processor 1501 may be configured to execute a program to implement the multipath processing method as described in the embodiment of the second aspect. For example, the processor 1501 may be configured to perform the following operations: communicate with a network device using a direct path and an indirect path; trigger or send a first scheduling request (SR) associated with a Uu BSR corresponding to the direct path and a second SR associated with an SL-BSR corresponding to the indirect path, or trigger or send the first SR and the second SR, where the first SR and the second SR use the same SR configuration.

[0338] For another example, the processor 1501 may be configured to execute a program to implement the multipath processing method as described in the embodiment of the third aspect. For example, the processor 1501 may be configured to perform the following operations: communicate with a network device using a direct path and an indirect path, wherein a PDCP entity is associated with a first RLC entity corresponding to the direct path and an SRAP entity corresponding to the indirect path; and indicate a PDCP data volume, where the PDCP data volume is used to trigger a BSR.

[0339] As shown in Figure 15 , the terminal device 1500 may further include: a communication module 1503, an input unit 1504, a display 1505, and a power supply 1506. The functions of these components are similar to those in the prior art and are not described in detail here. It is worth noting that the terminal device 1500 does not necessarily include all of the components shown in Figure 15 , and these components are not essential. Furthermore, the terminal device 1500 may also include components not shown in Figure 15 , for which reference may be made to related art.

[0340] An embodiment of the present application further provides a network device, which may be, for example, a base station, but the present application is not limited thereto and may also be other network devices.

[0341] Figure 16 is a schematic diagram illustrating the structure of a network device according to an embodiment of the present application. As shown in Figure 16 , network device 1600 may include a processor 1601 (e.g., a central processing unit (CPU)) and a memory 1602 ; the memory 1602 is coupled to the processor 1601 . The memory 1602 may store various data and information processing programs, which are executed under the control of the processor 1601 .

[0342] For example, the processor 1601 may be configured to execute a program to implement the multipath processing method as described in the embodiment of the fourth aspect. For example, the processor 1601 may be configured to perform the following operations: communicate with a remote terminal device using a direct path and an indirect path; and receive a buffer status report (BSR) of a Uu interface corresponding to the direct path (Uu BSR) and a side link buffer status report (SL-BSR) corresponding to the indirect path.

[0343] For another example, the processor 1601 may be configured to execute a program to implement the multipath processing method as described in the embodiment of the fifth aspect. For example, the processor 1601 may be configured to perform the following operations: communicate with a network device using a direct path and an indirect path; and receive a first scheduling request (SR) associated with a Uu BSR corresponding to the direct path and a second SR associated with an SL-BSR corresponding to the indirect path, or receive the first SR and the second SR, wherein the first SR and the second SR use the same SR configuration.

[0344] In addition, as shown in FIG16 , network device 1600 may further include: a transceiver 1603 and an antenna 1605; wherein, the functions of the above components are similar to those in the prior art and are not described in detail here. It is worth noting that network device 1600 does not necessarily include all the components shown in FIG16 ; in addition, network device 1600 may also include components not shown in FIG16 , and reference may be made to the prior art for details.

[0345] An embodiment of the present application also provides a computer-readable program, wherein when the program is executed in a remote terminal device, the program causes the computer to execute the multi-path processing method described in the embodiments of the first aspect and / or the second aspect and / or the third aspect in the remote terminal device.

[0346] An embodiment of the present application also provides a storage medium storing a computer-readable program, wherein the computer-readable program enables a computer to execute the multi-path processing method described in the embodiments of the first aspect and / or the second aspect and / or the third aspect in a remote terminal device.

[0347] An embodiment of the present application also provides a computer-readable program, wherein when the program is executed in a network device, the program enables the computer to execute the multipath processing method described in the embodiments of the fourth aspect and / or the fifth aspect in the network device.

[0348] An embodiment of the present application also provides a storage medium storing a computer-readable program, wherein the computer-readable program enables a computer to execute the multi-path processing method described in the embodiments of the fourth aspect and / or the fifth aspect in a network device.

[0349] The above devices and methods of the present application can be implemented by hardware or by a combination of hardware and software. The present application relates to such a computer-readable program that, when executed by a logic component, enables the logic component to implement the devices or components described above, or enables the logic component to implement the various methods or steps described above. The present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0350] The method / apparatus described in conjunction with the embodiments of the present application can be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, one or more of the functional block diagrams shown in the figure and / or one or more combinations of functional block diagrams can correspond to various software modules of the computer program flow or to various hardware modules. These software modules can correspond to the various steps shown in the figure, respectively. These hardware modules can be implemented by solidifying these software modules, for example, using a field programmable gate array (FPGA).

[0351] The software module may be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be an integral part of the processor. The processor and the storage medium may be located in an ASIC. The software module may be stored in the memory of the mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a large-capacity MEGA-SIM card or a large-capacity flash memory device, the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device.

[0352] One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may be implemented as a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any appropriate combination thereof for performing the functions described in this application. One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0353] The present application has been described above in conjunction with specific embodiments. However, those skilled in the art should understand that these descriptions are merely illustrative and are not intended to limit the scope of protection of the present application. Those skilled in the art may make various modifications and variations to the present application based on the spirit and principles of the present application, and such modifications and variations are also within the scope of the present application.

[0354] Regarding the implementation methods including the above embodiments, the following additional notes are also disclosed:

[0355] Note 1. A multi-path processing device, configured in a remote terminal device, comprising:

[0356] a third communication unit, configured to communicate with the network device using a direct path and an indirect path, wherein a PDCP entity is associated with a first RLC entity corresponding to the direct path and an SRAP entity corresponding to the indirect path; and

[0357] The third processing unit indicates the amount of PDCP data, where the amount of PDCP data is used to trigger a BSR.

[0358] Note 2. The device according to Note 1, wherein:

[0359] The SRAP entity corresponds to the second RLC entity.

[0360] Note 3. The device according to Note 2, wherein:

[0361] One of the first RLC entity and the second RLC entity is configured as a master RLC entity.

[0362] Note 4. The device according to Note 1, wherein:

[0363] The first RLC entity and the SRAP entity correspond to one MAC entity.

[0364] Note 5. The device according to Note 1, wherein:

[0365] In case PDCP repetition is activated,

[0366] Indicating the amount of PDCP data to the MAC entity associated with the primary RLC entity; and / or

[0367] indicating to a MAC entity associated with an RLC entity other than a primary RLC entity for PDCP reactivation an amount of PDCP data excluding PDCP control PDUs; and / or

[0368] Indicates to the MAC entity associated with the RLC entity for PDCP reactivation that the PDCP data amount is 0.

[0369] Note 6. The device according to Note 1, wherein:

[0370] When the split secondary RLC entity is configured and the total amount of PDCP data and the amount of RLC data to be transmitted in the primary path and the secondary path is greater than or equal to the preset threshold,

[0371] indicating the amount of PDCP data to a MAC entity associated with the primary RLC entity and the split secondary RLC entity; and / or

[0372] Indicate to a MAC entity associated with an RLC entity other than the primary RLC entity and the split secondary RLC entity that the PDCP data amount is 0.

[0373] Note 7. The device according to Note 1, wherein:

[0374] In case the split secondary RLC entity is not configured,

[0375] Indicating the amount of PDCP data to the MAC entity associated with the primary RLC entity; and / or

[0376] Indicates to the MAC entity associated with the RLC entity other than the primary RLC entity that the PDCP data amount is 0.

[0377] Note 8. The device according to Note 6 or 7, wherein:

[0378] The split secondary RLC entity is an RLC entity other than the primary RLC entity.

[0379] Note 9. A multipath processing method, applied to a remote terminal device, comprising:

[0380] communicating with the network device using a direct path and an indirect path, wherein a PDCP entity is associated with a first RLC entity corresponding to the direct path and an SRAP entity corresponding to the indirect path; and

[0381] Indicates the amount of PDCP data, which is used to trigger the BSR.

[0382] Note 10. A communication system, wherein the communication system comprises:

[0383] a remote terminal device that communicates with a network device using a direct path and an indirect path, triggering or sending one of a Uu BSR corresponding to the direct path and an SL-BSR corresponding to the indirect path, or triggering or sending one of a first SR associated with the Uu BSR corresponding to the direct path and a second SR associated with the SL-BSR corresponding to the indirect path, or triggering or sending the first SR and the second SR, and the first SR and the second SR use the same SR configuration; and

[0384] A network device receives the BSR or SR.

Claims

1. A multi-path processing device, configured in a remote terminal device, comprising: a first communication unit that communicates with the network device using a direct path and an indirect path; as well as The first processing unit triggers or sends a buffer status report BSR of a Uu interface corresponding to the direct path and a side link buffer status report SL-BSR corresponding to the indirect path.

2. The device according to claim 1, wherein: The triggered BSR is a BSR corresponding to the primary path or a BSR associated with the primary radio link management RLC entity.

3. The device according to claim 1, wherein: The triggered BSR is the Uu BSR; or the triggered BSR is the SL-BSR.

4. The device according to claim 1, wherein: The triggered BSR is a BSR determined based on the indication information or configuration information of the network device.

5. The device according to claim 1, wherein: The triggered BSR is a BSR determined based on the priorities of the Uu BSR and the SL-BSR in resource allocation in the current logical channel priority processing.

6. The device according to claim 1, wherein: The Uu BSR and the SL-BSR are triggered, and one of the Uu BSR and the SL-BSR is sent.

7. The device according to claim 6, wherein: One of the buffer status report media access control control element Uu BSR MAC CE of the Uu interface and the side link buffer status report media access control control element SL-BSR MAC CE is generated.

8. The device according to claim 7, wherein: Based on the priorities of the Uu BSR and the SL-BSR in resource allocation in the current logical channel priority process, one of the Uu BSR MAC CE and the SL-BSR MAC CE is generated; or The Uu BSR MAC CE is generated prior to the SL-BSR MAC CE; or The SL-BSR MAC CE is generated prior to the Uu BSR MAC CE; or A media access control element of the BSR corresponding to the primary path is generated; or Based on the configuration information or instruction information of the network device, Uu BSR MAC CE and SL-BSR MAC One of the CEs is generated; or Based on the predefined information, one of the Uu BSR MAC CE and the SL-BSR MAC CE is generated.

9. The device according to claim 6, wherein: A media access control packet data unit MAC PDU includes one of the Uu BSR MAC CE and the SL-BSR MAC CE.

10. The device according to claim 9, wherein: Based on the priorities of the Uu BSR and the SL-BSR in resource allocation in the current logical channel priority process, one of the Uu BSR MAC CE and the SL-BSR MAC CE is included in the MAC PDU; or The Uu BSR MAC CE is included in the MAC PDU before the SL-BSR MAC CE; or The SL-BSR MAC CE is included in the MAC PDU before the Uu BSR MAC CE; or The MAC CE of the BSR corresponding to the primary path is included in the MAC PDU; or Based on the configuration information or indication information of the network device, one of the Uu BSR MAC CE and the SL-BSR MAC CE is included in the MAC PDU; or Based on the predefined information, one of the Uu BSR MAC CE and the SL-BSR MAC CE is included in the MAC PDU.

11. The device according to claim 6, wherein: One of the triggered Uu BSR and the triggered SL-BSR is cancelled.

12. The device according to claim 11, wherein Based on the priorities of the Uu BSR and the SL-BSR in resource allocation in the current logical channel priority process, one of the Uu BSR and the SL-BSR is cancelled; or The Uu BSR is cancelled in preference to the SL-BSR; or The SL-BSR is cancelled in preference to the Uu BSR; or The BSR corresponding to the primary path is not cancelled or the BSR corresponding to the secondary path is cancelled; or Based on the configuration information or instruction information of the network device, one of the Uu BSR and the SL-BSR is cancelled; or Based on predefined information, one of the Uu BSR and the SL-BSR is cancelled.

13. A multi-path processing device, configured in a remote terminal device, comprising: a second communication unit that communicates with the network device using a direct path and an indirect path; as well as A second processing unit triggers or sends a scheduling request among a first scheduling request associated with a cache status report Uu BSR of the Uu interface corresponding to the direct path and a second scheduling request associated with a side link cache status report SL-BSR corresponding to the indirect path, or triggers or sends the first scheduling request and the second scheduling request, wherein the first scheduling request and the second scheduling request adopt the same scheduling request configuration.

14. The device according to claim 13, wherein: Based on the priorities of the Uu BSR and the SL-BSR in resource allocation in the current logical channel priority process, a scheduling request associated with one of the Uu BSR and the SL-BSR is triggered or sent; or The first scheduling request associated with the Uu BSR is triggered or sent before the second scheduling request associated with the SL-BSR; or The second scheduling request associated with the SL-BSR is triggered or sent prior to the first scheduling request associated with the Uu BSR; or The scheduling request associated with the BSR corresponding to the primary path is triggered or sent; or Based on the configuration information or indication information of the network device, a scheduling request associated with one of the Uu BSR and the SL-BSR is triggered or sent; or Based on predefined information, a scheduling request associated with one of the Uu BSR and the SL-BSR is triggered or sent.

15. The device according to claim 13, wherein: In the case of triggering or sending the first scheduling request and the second scheduling request, the order in which the first scheduling request and the second scheduling request are sent is determined based on the following method: Determine the order in which the first scheduling request and the second scheduling request are sent based on the priorities of the Uu BSR and the SL-BSR in the resource allocation in the current logical channel priority processing; or The first scheduling request associated with the Uu BSR is sent before the second scheduling request associated with the SL-BSR; or The second scheduling request associated with the SL-BSR is sent prior to the first scheduling request associated with the Uu BSR; or The scheduling request associated with the BSR corresponding to the primary path is sent first or the scheduling request associated with the BSR corresponding to the auxiliary path is sent later; or Determine, based on configuration information or indication information of the network device, the order in which the first scheduling request and the second scheduling request are sent; or Based on the predefined information, an order in which the first scheduling request and the second scheduling request are sent is determined.

16. The device according to claim 14, wherein: The scheduling request configuration includes a set of physical uplink control channel (PUCCH) resources for the scheduling request configuration in different bandwidth parts (BWP) and cells.

17. A multi-path processing method, applied to a remote terminal device, the method comprising: Uses one direct path and one indirect path to communicate with network devices; as well as Trigger or send one of the Uu BSR corresponding to the direct path and the SL-BSR corresponding to the indirect path; or, trigger or send a first scheduling request associated with the Uu BSR corresponding to the direct path and a second scheduling request associated with the SL-BSR corresponding to the indirect path, or, trigger or send the first scheduling request and the second scheduling request, the first scheduling request and the second scheduling request adopt the same scheduling request configuration.

18. The method according to claim 17, wherein: The BSR that is triggered or sent is at least one of the following: The BSR corresponding to the primary path or the BSR associated with the primary RLC entity; the Uu BSR; the SL-BSR; A BSR determined based on indication information or configuration information of the network device; or A BSR determined by the priorities of the Uu BSR and the SL-BSR in resource allocation in the LCP is processed based on the current logical channel priority.

19. The method according to claim 17, wherein: The scheduling request associated with the triggered or sent BSR is at least one of the following: The scheduling request associated with the BSR corresponding to the primary path or the scheduling request associated with the BSR associated with the primary RLC entity; The scheduling request associated with the Uu BSR; a scheduling request associated with the SL-BSR; A scheduling request associated with a BSR determined based on indication information or configuration information of the network device; or Processing a BSR-associated scheduling request determined by the priorities of the Uu BSR and the SL-BSR in the resource allocation in the LCP based on the current logical channel priority; or In the case of triggering or sending the first scheduling request and the second scheduling request, the order in which the first scheduling request and the second scheduling request are sent is determined based on the following method: Determine the order in which the first scheduling request and the second scheduling request are sent based on the priorities of the Uu BSR and the SL-BSR in the resource allocation in the current logical channel priority processing; or The first scheduling request associated with the Uu BSR is sent before the second scheduling request associated with the SL-BSR; or The second scheduling request associated with the SL-BSR is sent prior to the first scheduling request associated with the Uu BSR; or The scheduling request associated with the BSR corresponding to the primary path is sent first or the scheduling request associated with the BSR corresponding to the auxiliary path is sent later; or Determine, based on configuration information or indication information of the network device, the order in which the first scheduling request and the second scheduling request are sent; or Based on the predefined information, an order in which the first scheduling request and the second scheduling request are sent is determined.

20. The method according to claim 17, wherein: The scheduling request configuration includes a set of physical uplink control channel (PUCCH) resources for the scheduling request configuration in different bandwidth parts (BWP) and cells.

Images