A data transmission method and apparatus

Abstract

The application provides a data transmission method and device. The method is applied to a TPAP entity in a base station, and comprises the following steps: receiving a downlink service flow sent by a GTP-U entity; if it is judged that feature information of the downlink service flow hits a preset matching rule, the downlink service flow is cached into a cache queue corresponding to a target virtual DRB corresponding to the feature information; if it is judged that the cache queue satisfies a preset condition, the cache time and total data size of the downlink service flow corresponding to the target virtual DRB are notified to a MAC entity by using a first common DRB; and based on the data amount to be transmitted of the target virtual DRB notified by the MAC entity, the target downlink service flow in the cache queue is transmitted to the MAC entity for processing by using the first common DRB and an SDAP entity in the base station in the order of the cache time. The application can realize the scheduling of multiple downlink service flows of the same Qos flow of the same PDU session.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a data transmission method and device. Background Art

[0002] In 5G networks, the 5G Core Network (5GC) is typically located in core areas such as carrier data centers or cloud data centers. The core network is a key component of the 5G network and includes elements such as the Mobility Management Entity (MME), Session Management Function (SMF), and User Plane Function (UPF). It provides core network functions such as user authentication, session management, data transmission, and control, serving as the management and control center for the entire 5G network.

[0003] Base stations, also known as Next Generation Radio Access Networks (NG-RAN), are deployed in locations close to wireless coverage and services, such as rooftops, telecom towers, campuses, and factories. As the wireless access component of a 5G network, base stations receive wireless signals from user equipment (UE), such as mobile phones and IoT devices, and connect to the core network for data communication.

[0004] Since the core network is deployed in the core area, private networks with special needs, such as campuses and smart factories, need to be built without being able to modify the core network configuration. These private networks may need to provide QoS priority guarantees for specific downlink service flows of the same QoS flow carried by the same Protocol Data Unit (PDU) session to meet their specific business needs. Therefore, how to meet the business needs of these services is one of the technical issues that need to be solved. Summary of the Invention

[0005] In order to overcome the problems existing in the related art, the present application provides a data transmission method and device.

[0006] According to a first aspect of an embodiment of the present application, a data transmission method is provided. The method is applied to a Traffic Priority Adaptation Protocol (TPAP) entity in a base station, and the method includes:

[0007] Receiving a downlink service flow from a UPF network element in a core network, which is sent by a GPRS Tunneling Protocol User Plane (GTP-U) entity in the base station;

[0008] If it is determined that the characteristic information of the downlink service flow hits a preset matching rule, the downlink service flow is cached in a cache queue corresponding to a target virtual data radio bearer (DRB) corresponding to the characteristic information, wherein a quality of service (QoS) flow to which the downlink service flow belongs corresponds to multiple downlink service flows, and the QoS flow corresponds to a first common DRB and multiple virtual DRBs, different virtual DRBs correspond to different priorities, and different virtual DRBs correspond to different downlink service flows;

[0009] If it is determined that the cache queue meets the preset condition, the cache time of the current downlink service flow corresponding to the target virtual DRB and the total data size of the current downlink service flow are notified to the Media Access Control (MAC) entity in the base station using the first common DRB, so that the MAC entity performs QoS scheduling based on the cache time and total data size of the downlink service flow corresponding to the current at least one DRB and the priority corresponding to the at least one DRB;

[0010] Based on the amount of data that needs to be transmitted by the target virtual DRB notified by the MAC entity, the target downlink service flow in the cache queue is transmitted to the MAC entity for processing through the Service Data Adaptation Protocol (SDAP) entity in the base station using the first ordinary DRB in order of cache time, wherein the total data size of the target downlink service flow is the same as the data amount.

[0011] According to a second aspect of an embodiment of the present application, a data transmission device is provided, where the device is applied to a TPAP entity in a base station, and the device includes:

[0012] A receiving module, configured to receive a downlink service flow from a UPF network element in a core network, sent by a GTP-U entity in the base station;

[0013] A cache module is configured to cache the downlink service flow in a cache queue corresponding to a target virtual DRB corresponding to the characteristic information if it is determined that the characteristic information of the downlink service flow hits a preset matching rule, wherein the QoS flow to which the downlink service flow belongs corresponds to multiple downlink service flows, and the QoS flow corresponds to a first common DRB and multiple virtual DRBs, different virtual DRBs correspond to different priorities, and different virtual DRBs correspond to different downlink service flows;

[0014] A notification module is configured to notify a MAC entity in the base station of the cache time and the total data size of the current downlink service flow corresponding to the target virtual DRB, if it is determined that the cache queue meets the preset condition, using the first common DRB, so that the MAC entity performs QoS scheduling based on the cache time and total data size of the downlink service flow corresponding to the current at least one DRB and the priority corresponding to the at least one DRB;

[0015] The first transmission module is used to transmit the target downlink service flow in the cache queue to the MAC entity for processing through the SDAP entity in the base station using the first ordinary DRB in order of cache time based on the amount of data that the target virtual DRB needs to transmit notified by the MAC entity, wherein the total data size of the target downlink service flow is the same as the data amount.

[0016] The technical solutions provided by the embodiments of the present application may have the following beneficial effects:

[0017] In the embodiment of the present application, a TPAP entity is added in the base station, and the following data transmission process is performed: receiving downlink service flows from a UPF network element in the core network sent by a GTP-U entity in the base station; if it is judged that the feature information of the downlink service flow hits the preset matching rule, the downlink service flow is cached in a cache queue corresponding to a target virtual DRB corresponding to the feature information, wherein the Qos flow to which the downlink service flow belongs corresponds to multiple downlink service flows, and the Qos flow corresponds to a first common DRB and multiple virtual DRBs, different virtual DRBs correspond to different priorities, and different virtual DRBs correspond to different downlink service flows; if it is judged that the cache queue meets the preset condition, the cache time of the current downlink service flow corresponding to the target virtual DRB and the total data size of the current downlink service flow are notified to the MAC entity in the base station using the first common DRB, so that the MAC entity performs Qos scheduling based on the cache time and the total data size of the downlink service flow corresponding to at least one DRB and the priority of the at least one DRB; based on the data amount that the target virtual DRB needs to transmit notified by the MAC entity, the target downlink service flow in the cache queue is transmitted to the MAC entity for processing through the SDAP entity in the base station using the first common DRB in the order of cache time, wherein the total data size of the target downlink service flow is the same as the data amount.

[0018] In this way, in the case that multiple downlink service flows corresponding to one Qos flow of one PDU session need to be Qos scheduled, a common DRB and multiple virtual DRBs with different priorities can be established for the Qos flow, different downlink service flows correspond to different virtual DRBs, and the Qos scheduling of the downlink service flows in the air interface is assisted by the TPAP entity, which meets the service requirements and improves the user experience.

[0019] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the present application. BRIEF DESCRIPTION OF DRAWINGS

[0020] The accompanying drawings, which are incorporated into and form part of the specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the application.

[0021] Figure 1 One of the flow diagrams of a data transmission method provided for the embodiment of the present application;

[0022] Figure 2 The second flow diagram of a data transmission method provided for the embodiment of the present application;

[0023] Figure 3 The structure diagram of a data transmission device provided for the embodiment of the present application. DETAILED DESCRIPTION

[0024] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

[0025] The terms used in this application are for the purpose of describing specific embodiments only and are not intended to limit this application. As used in this application and the appended claims, the singular forms "a," "an," "the," and "the" are intended to include the plural forms, unless the context clearly indicates otherwise. It should also be understood that the term "and / or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

[0026] It should be understood that although the terms first, second, third, etc. may be used in this application to describe various information, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of this application, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the words "if" or "if" as used herein may be interpreted as "when" or "when".

[0027] Next, the embodiments of the present application are described in detail.

[0028] The embodiment of the present application provides a data transmission method, which is applied to a TPAP entity in a base station, such as Figure 1 As shown, the method may include the following steps:

[0029] S11. Receive the downlink service flow from the UPF network element in the core network, which is sent by the GTP-U entity in the base station.

[0030] S12: If it is determined that the characteristic information of the downlink service flow matches a preset matching rule, the downlink service flow is cached in a cache queue corresponding to a target virtual DRB corresponding to the characteristic information.

[0031] In this step, the QoS flow to which the downlink service flow belongs corresponds to multiple downlink service flows, and the QoS flow corresponds to a first ordinary DRB and multiple virtual DRBs, different virtual DRBs correspond to different priorities, and different virtual DRBs correspond to different downlink service flows.

[0032] S13. If it is determined that the cache queue meets the preset conditions, the cache time of the current downlink business flow corresponding to the target virtual DRB and the total data size of the current downlink business flow will be notified to the MAC entity in the base station using the first ordinary DRB, so that the MAC entity can perform Qos scheduling based on the cache time and total data size of the downlink business flow corresponding to at least one current DRB, and the priority corresponding to at least one DRB.

[0033] S14. Based on the amount of data that needs to be transmitted by the target virtual DRB notified by the MAC entity, use the first ordinary DRB to transmit the target downlink service flow in the cache queue to the MAC entity for processing through the SDAP entity in the base station in the order of cache time.

[0034] In this step, the total data size of the target downlink service flow is the same as the data volume.

[0035] It should be noted that, in the embodiment of the present application, the TPAP entity may also perform the following operations:

[0036] If it is determined that the characteristic information of the downlink service flow does not hit the preset matching rule, the second common DRB corresponding to the QoS flow to which the downlink service flow belongs is used to transmit the downlink service flow to the MAC entity through the SDAP entity for processing.

[0037] Here, after the downlink service flow reaches the SDAP entity, the subsequent processing flow is the existing technology and will not be described in detail here.

[0038] Specifically, in the above step S12, the TPAP entity may determine whether the characteristic information of the downlink service flow matches the preset matching rule in the following manner:

[0039] Determine whether the quintuple information of the downlink service flow is in the preset quintuple information set;

[0040] If the judgment result is yes, it is determined that the characteristic information of the downlink service flow hits the preset matching rule;

[0041] If the judgment result is no, it is determined that the characteristic information of the downlink service flow does not match the preset matching rule.

[0042] It should be noted that the TPAP entity may also use other methods to determine whether the characteristic information of the downlink service flow matches the preset matching rule, which are not listed here one by one.

[0043] It should be further explained that the above-mentioned preset matching rules and the multiple virtual DRBs corresponding to the first common DRB corresponding to the above-mentioned Qos flow can be established by the TPAP entity based on relevant notification instructions from the Radio Resource Control (RRC) entity.

[0044] Furthermore, multiple virtual DRBs corresponding to the first normal DRB are established on the MAC entity side. These virtual DRBs may be established by the MAC entity based on relevant notification instructions from the Radio Resource Control (RRC) entity. Here, different virtual DRBs have different priorities.

[0045] Specifically, in the above step S13, the TPAP entity may determine whether the cache queue meets the preset condition in the following manner:

[0046] If the cache queue satisfies any one of the first condition and the second condition, it is determined that the cache queue satisfies the preset condition;

[0047] The first condition is that the total data size of the current downlink service flow in the cache queue is not less than the set data size;

[0048] The second condition is reaching the timeout duration corresponding to the cache queue.

[0049] Of course, in the embodiment of the present application, the TPAP entity may also use other methods to determine whether the cache queue meets the preset conditions, which are not listed here one by one.

[0050] In addition, in the above step S13, the data size and timeout period can be set by the administrator according to network requirements and configured in advance on the TPAP entity.

[0051] It should be noted that in the embodiment of the present application, for the MAC entity, when the current at least one DRB includes multiple DRBs, these DRBs may include only virtual DRBs, or may include both virtual DRBs and ordinary DRBs.

[0052] The specific scheduling process of the MAC entity performing Qos scheduling based on the cache time and total data size of the downlink service flow corresponding to at least one current DRB, and the priority corresponding to at least one DRB is an existing technology and will not be described in detail here.

[0053] After Qos scheduling, if the number of virtual DRBs is one, the MAC entity notifies the TPAP entity of the amount of data that this virtual DRB needs to transmit, so that the TPAP entity can use the corresponding ordinary DRB to transmit the relevant downlink service flow in the corresponding cache queue to the MAC entity for processing through the SDAP entity in the order of cache time based on the amount of data that this virtual DRB needs to transmit notified by the MAC entity.

[0054] If there are multiple virtual DRBs, the MAC entity notifies the TPAP entity of the amount of data that all virtual DRBs need to transmit and the transmission order of all virtual DRBs, so that the TPAP entity can use the corresponding ordinary DRB to transmit the relevant downlink service flows in the corresponding cache queue to the MAC entity for processing through the SDAP entity based on the transmission order of these virtual DRBs notified by the MAC entity and the amount of data that each virtual DRB needs to transmit in turn, in the order of cache time.

[0055] It should be further explained that, in the embodiment of the present application, after the TPAP executes the above step S14, the specific processing process after the downlink service flow reaches the MAC entity is the existing technology and will not be described in detail here.

[0056] The above data transmission method is described in detail below with reference to specific embodiments.

[0057] like Figure 2 As shown, it is assumed that UPF network element 1 in the core network needs to send downlink service flow 1 (not DNS service flow) corresponding to Qos flow 1 corresponding to PDU session 1 to UE1, and Qos flow 1 also corresponds to downlink service flow 2 and downlink service flow 3 that are not DNS service flows.

[0058] On both the TPAP entity side and the MAC entity side, corresponding virtual DRBs (for example, virtual DRBa, virtual DRBb, and virtual DRBz) are established for the normal DRB (for example, normal DRBn) corresponding to QoS flow 1. In addition, a preset five-tuple set (including at least five-tuple information corresponding to downstream service flow 1, downstream service flow 2, and downstream service flow 3) is configured on the TPAP entity side. Virtual DRBa corresponds to the five-tuple information of downstream service flow 1, virtual DRBb corresponds to the five-tuple information of downstream service flow 2, and virtual DRBz corresponds to the five-tuple information of downstream service flow 3. The specific transmission process is as follows:

[0059] 1. UPF network element 1 sends downlink service flow 1 to the GTPU entity in the base station.

[0060] 2. The GTP-U entity sends downlink service flow 1 to the TPAP entity.

[0061] Here, the specific sending process of the GTP-U entity sending the downlink service flow 1 is the existing technology and will not be described in detail here.

[0062] 3. The TPAP entity receives the downlink service flow 1 and determines that the quintuple information of the downlink service flow 1 is in the preset quintuple information set. At this time, the TPAP entity caches the downlink service flow 1 in the cache queue corresponding to the virtual DRBa.

[0063] Assume that the TPAP entity also determines that the total data size of the current downlink service flow in the cache queue is not less than the set data size. At this time, the TPAP entity uses DRBn to notify the MAC entity in the base station of the cache time of the current downlink service flow corresponding to the virtual DRBa and the total data size of the current downlink service flow.

[0064] 4. The MAC entity performs QoS scheduling based on the cache time and total data size of the downlink service flow corresponding to the current DRB (assuming there is only virtual DRBa), as well as the priority corresponding to the virtual DRBa.

[0065] 5. The MAC entity notifies the TPAP entity DRBa of the amount of data that needs to be transmitted.

[0066] 6. Based on the amount of data that needs to be transmitted by DRBa notified by the MAC entity, the TPAP entity uses DRBn to transfer the target downlink service flow in the cache queue through the SDAP entity ( Figure 2 The total data size of the target downlink service flow is the same as the data volume.

[0067] Here, the target downlink service flow will pass through the SDAP entity, the Packet Data Convergence Protocol (PDCP) entity ( Figure 2 Not shown), and Radio Link Control (RLC) entity ( Figure 2 The specific transmission process and subsequent transmission process are existing technologies and will not be described in detail here.

[0068] It can be seen from the above technical solution that in the embodiment of the present application, a TPAP entity is newly added in the base station, and the following data transmission process is executed: the downlink service flow from the UPF network element in the core network is received and sent by the GTP-U entity in the base station; if it is judged that the characteristic information of the downlink service flow hits the preset matching rule, the downlink service flow is cached in the cache queue corresponding to the target virtual DRB corresponding to the characteristic information, wherein the QoS flow to which the downlink service flow belongs corresponds to multiple downlink service flows, and the QoS flow corresponds to a first ordinary DRB and multiple virtual DRBs, different virtual DRBs correspond to different priorities, and different virtual DRBs correspond to different downlink service flows; if it is judged that the cache queue meets the preset matching rule, If the conditions are set, the cache time of the current downlink business flow corresponding to the target virtual DRB and the total data size of the current downlink business flow are notified to the MAC entity in the base station using the first common DRB, so that the MAC entity performs Qos scheduling based on the cache time and total data size of the downlink business flow corresponding to at least one current DRB, and the priority corresponding to at least one DRB; based on the amount of data that needs to be transmitted by the target virtual DRB notified by the MAC entity, the target downlink business flow in the cache queue is transmitted to the MAC entity for processing through the SDAP entity in the base station using the first common DRB in the order of cache time, wherein the total data size of the target downlink business flow is the same as the data amount.

[0069] In this way, when multiple downlink service flows corresponding to a QoS flow of a PDU session need to be QoS scheduled, a common DRB and multiple virtual DRBs of different priorities can be established for the QoS flow. In addition, different downlink service flows correspond to different virtual DRBs. The TPAP entity assists in implementing the QoS scheduling of these downlink service flows on the air interface, which meets the service needs and improves the user experience.

[0070] Based on the same inventive concept, the present application also provides a data transmission device, which is applied to a TPAP entity in a base station. Figure 3 As shown, specifically including:

[0071] A receiving module 31 is configured to receive a downlink service flow from a UPF network element in a core network, sent by a GTP-U entity in the base station;

[0072] The cache module 32 is configured to cache the downlink service flow in a cache queue corresponding to a target virtual DRB corresponding to the characteristic information if it is determined that the characteristic information of the downlink service flow hits a preset matching rule, wherein the QoS flow to which the downlink service flow belongs corresponds to multiple downlink service flows, and the QoS flow corresponds to a first common DRB and multiple virtual DRBs, different virtual DRBs correspond to different priorities, and different virtual DRBs correspond to different downlink service flows;

[0073] The notification module 33 is configured to, if it is determined that the cache queue meets the preset condition, notify the MAC entity in the base station of the cache time and the total data size of the current downlink service flow corresponding to the target virtual DRB using the first common DRB, so that the MAC entity performs QoS scheduling based on the cache time and total data size of the downlink service flow corresponding to the current at least one DRB and the priority corresponding to the at least one DRB;

[0074] The first transmission module 34 is used to transmit the target downlink service flow in the cache queue to the MAC entity for processing through the SDAP entity in the base station using the first ordinary DRB in the order of cache time based on the amount of data that the target virtual DRB needs to transmit notified by the MAC entity, wherein the total data size of the target downlink service flow is the same as the data amount.

[0075] Preferably, the device further comprises:

[0076] The second transmission module ( Figure 3 Not shown), if the cache module determines that the characteristic information of the downlink business flow does not hit the preset matching rule, the second ordinary DRB corresponding to the QoS flow to which the downlink business flow belongs is used to transmit the downlink business flow to the MAC entity through the SDAP entity for processing.

[0077] Preferably, the cache module 32 is specifically configured to determine whether the characteristic information of the downlink service flow matches a preset matching rule in the following manner:

[0078] Determining whether the quintuple information of the downlink service flow is in a preset quintuple information set;

[0079] If the judgment result is yes, it is determined that the characteristic information of the downlink service flow hits the preset matching rule;

[0080] If the judgment result is no, it is determined that the characteristic information of the downlink service flow does not match the preset matching rule.

[0081] Preferably, the notification module 33 is specifically configured to determine whether the cache queue meets a preset condition in the following manner:

[0082] If the cache queue satisfies any one of the first condition and the second condition, it is determined that the cache queue satisfies the preset condition;

[0083] The first condition is that the total data size of the current downlink service flow in the cache queue is not less than the set data size;

[0084] The second condition is reaching the timeout duration corresponding to the cache queue.

[0085] It can be seen from the above technical solution that in the embodiment of the present application, a TPAP entity is newly added in the base station, and the following data transmission process is executed: the downlink service flow from the UPF network element in the core network is received and sent by the GTP-U entity in the base station; if it is judged that the characteristic information of the downlink service flow hits the preset matching rule, the downlink service flow is cached in the cache queue corresponding to the target virtual DRB corresponding to the characteristic information, wherein the QoS flow to which the downlink service flow belongs corresponds to multiple downlink service flows, and the QoS flow corresponds to a first ordinary DRB and multiple virtual DRBs, different virtual DRBs correspond to different priorities, and different virtual DRBs correspond to different downlink service flows; if it is judged that the cache queue meets the preset matching rule, If the conditions are set, the cache time of the current downlink business flow corresponding to the target virtual DRB and the total data size of the current downlink business flow are notified to the MAC entity in the base station using the first common DRB, so that the MAC entity performs Qos scheduling based on the cache time and total data size of the downlink business flow corresponding to at least one current DRB, and the priority corresponding to at least one DRB; based on the amount of data that needs to be transmitted by the target virtual DRB notified by the MAC entity, the target downlink business flow in the cache queue is transmitted to the MAC entity for processing through the SDAP entity in the base station using the first common DRB in the order of cache time, wherein the total data size of the target downlink business flow is the same as the data amount.

[0086] In this way, when multiple downlink service flows corresponding to a QoS flow of a PDU session need to be QoS scheduled, a common DRB and multiple virtual DRBs of different priorities can be established for the QoS flow. In addition, different downlink service flows correspond to different virtual DRBs. The TPAP entity assists in implementing the QoS scheduling of these downlink service flows on the air interface, which meets the service needs and improves the user experience.

[0087] The above description is only a preferred embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A data transmission method, characterized in that: The method is applied to a service priority adaptation protocol TPAP entity in a base station, and the method includes: Receiving a downlink service flow from a user plane function UPF network element in a core network, which is sent by a user plane general packet radio service tunneling protocol GTP-U entity in the base station; If it is determined that the characteristic information of the downlink service flow hits a preset matching rule, the downlink service flow is cached in a cache queue corresponding to a target virtual data radio bearer (DRB) corresponding to the characteristic information, wherein the quality of service (QoS) flow to which the downlink service flow belongs corresponds to multiple downlink service flows, and the QoS flow corresponds to a first common DRB and multiple virtual DRBs, different virtual DRBs correspond to different priorities, and different virtual DRBs correspond to different downlink service flows; If it is determined that the cache queue meets the preset condition, the cache time of the current downlink service flow corresponding to the target virtual DRB and the total data size of the current downlink service flow are notified to the media access control MAC entity in the base station using the first ordinary DRB, so that the MAC entity performs QoS scheduling based on the cache time and total data size of the downlink service flow corresponding to the current at least one DRB and the priority corresponding to the at least one DRB, wherein the at least one DRB includes a virtual DRB, or the at least one DRB includes a virtual DRB and an ordinary DRB; Based on the amount of data that needs to be transmitted by the target virtual DRB notified by the MAC entity, the target downlink service flow in the cache queue is transmitted to the MAC entity for processing through the Service Data Adaptation Protocol SDAP entity in the base station using the first ordinary DRB in order of cache time, wherein the total data size of the target downlink service flow is the same as the data amount.

2. The method according to claim 1, characterized in that The method further comprises: If it is determined that the characteristic information of the downlink service flow does not hit the preset matching rule, the second common DRB corresponding to the QoS flow to which the downlink service flow belongs is used to transmit the downlink service flow to the MAC entity through the SDAP entity for processing.

3. The method according to claim 1 or 2, characterized in that Whether the characteristic information of the downlink service flow matches the preset matching rule is determined in the following manner: Determining whether the quintuple information of the downlink service flow is in a preset quintuple information set; If the judgment result is yes, it is determined that the characteristic information of the downlink service flow hits the preset matching rule; If the judgment result is no, it is determined that the characteristic information of the downlink service flow does not match the preset matching rule.

4. The method according to claim 1, wherein Determine whether the cache queue meets the preset conditions by the following method: If the cache queue satisfies any one of the first condition and the second condition, it is determined that the cache queue satisfies the preset condition; The first condition is that the total data size of the current downlink service flow in the cache queue is not less than the set data size; The second condition is reaching the timeout duration corresponding to the cache queue.

5. A data transmission device, characterized in that: The device is applied to a service priority adaptation protocol TPAP entity in a base station, and the device includes: A receiving module, configured to receive a downlink service flow from a user plane function UPF network element in a core network, sent by a user plane general packet radio service tunneling protocol GTP-U entity in the base station; A cache module is configured to cache the downlink service flow in a cache queue corresponding to a target virtual data radio bearer (DRB) corresponding to the characteristic information if it is determined that the characteristic information of the downlink service flow hits a preset matching rule, wherein the quality of service (QoS) flow to which the downlink service flow belongs corresponds to multiple downlink service flows, and the QoS flow corresponds to a first common DRB and multiple virtual DRBs, different virtual DRBs correspond to different priorities, and different virtual DRBs correspond to different downlink service flows; A notification module is configured to, if it is determined that the cache queue meets a preset condition, notify the media access control MAC entity in the base station of the cache time and the total data size of the current downlink service flow corresponding to the target virtual DRB using the first common DRB, so that the MAC entity performs QoS scheduling based on the cache time and the total data size of the downlink service flow corresponding to the current at least one DRB and the priority corresponding to the at least one DRB, wherein the at least one DRB includes a virtual DRB, or the at least one DRB includes a virtual DRB and a common DRB; The first transmission module is used to transmit the target downlink service flow in the cache queue to the MAC entity for processing through the Service Data Adaptation Protocol SDAP entity in the base station using the first ordinary DRB in order of cache time based on the amount of data that the target virtual DRB needs to transmit as notified by the MAC entity, wherein the total data size of the target downlink service flow is the same as the data amount.

6. The device according to claim 5, characterized in that The device further comprises: The second transmission module is used to use the second ordinary DRB corresponding to the QoS flow to which the downlink business flow belongs to transmit the downlink business flow to the MAC entity for processing through the SDAP entity if the cache module determines that the characteristic information of the downlink business flow does not hit the preset matching rule.

7. The device according to claim 5 or 6, characterized in that The cache module is specifically configured to determine whether the characteristic information of the downlink service flow matches a preset matching rule in the following manner: Determining whether the quintuple information of the downlink service flow is in a preset quintuple information set; If the judgment result is yes, it is determined that the characteristic information of the downlink service flow hits the preset matching rule; If the judgment result is no, it is determined that the characteristic information of the downlink service flow does not match the preset matching rule.

8. The device according to claim 5, characterized in that The notification module is specifically configured to determine whether the cache queue meets a preset condition by: If the cache queue satisfies any one of the first condition and the second condition, it is determined that the cache queue satisfies the preset condition; The first condition is that the total data size of the current downlink service flow in the cache queue is not less than the set data size; The second condition is reaching the timeout duration corresponding to the cache queue.

Images