WO2019062866A1

WO2019062866A1 - Data transmission method and device

Info

Publication number: WO2019062866A1
Application number: PCT/CN2018/108396
Authority: WO
Inventors: 方建民; 黄河; 施小娟
Original assignee: 中兴通讯股份有限公司
Priority date: 2017-09-28
Filing date: 2018-09-28
Publication date: 2019-04-04
Also published as: CN109587722A

Abstract

A data transmission method and device. The data transmission method comprises: a monitoring node receives configuration information from a configuration node, wherein the configuration information comprises monitoring subject information, monitoring configuration information, and report configuration information; the monitoring node monitors a monitoring subject corresponding to the monitoring subject information according to the monitoring configuration information, and reports a monitoring result to the configuration node according to the report configuration information.

Description

Data transmission method and data transmission device

The present disclosure claims the priority of the Chinese Patent Application, filed on Sep. 28, 2017, the entire disclosure of which is hereby incorporated by reference.

Technical field

The present disclosure relates to, but is not limited to, the field of wireless communication technologies, for example, to a data transmission method and a data transmission device.

Background technique

The 4th Generation mobile communication technology (4G) mobile network has entered the stage of rapid popularization. At the same time, the 5th Generation mobile communication technology (5G) standard has also emerged. In a 4G, 5G, or 4G/5G hybrid network, the user equipment may be connected to one base station or may be connected to two or more base stations at the same time. However, in the related art, the user equipment is connected in a connected state. How to implement rate control or traffic reporting when switching or dual-connection/multi-connection, no effective solution has been proposed.

Summary of the invention

The present disclosure provides a data transmission method and a data transmission device, which can implement rate control or traffic reporting of a user equipment in a connected state, a connection handover, or a dual connectivity/multiple connection in a 4G, 5G, or 4G/5G hybrid network.

The present disclosure provides a data transmission method, including:

The monitoring node receives configuration information of the configuration node, where the configuration information includes monitoring object information, monitoring configuration information, and report configuration information;

The monitoring node monitors the monitoring object corresponding to the monitoring object information according to the monitoring configuration information, and reports the monitoring result to the configuration node according to the report configuration information.

The present disclosure also provides a data transmission method, including:

The monitoring node receives configuration information of the configuration node, where the configuration information includes a monitoring object, and at least one of the following: a traffic reporting period, a traffic report triggering threshold, and a single traffic reporting indication;

The monitoring node monitors the traffic of the monitoring object, and reports the monitoring result to the configuration node according to at least one of the following: the traffic reporting period, the traffic report triggering threshold, and the single traffic reporting indication.

The present disclosure also provides a data transmission apparatus, including a first receiving unit and a first monitoring unit, where

a first receiving unit, configured to receive configuration information of the configuration node, and output the configuration information to the first monitoring unit, where the configuration information includes monitoring object information, monitoring configuration information, and report configuration information;

The first monitoring unit is configured to monitor the monitoring object corresponding to the monitoring configuration information according to the monitoring configuration information, and report the monitoring result to the configuration node according to the report configuration information.

The present disclosure also provides a data transmission apparatus including a second receiving unit and a second monitoring unit, wherein:

The second receiving unit is configured to receive the configuration information of the configuration node and output the configuration information to the second monitoring unit, where the configuration information includes the monitoring object, and further includes at least one of the following: a traffic reporting period, a traffic report trigger threshold, Single flow report indication;

The second monitoring unit is configured to monitor the traffic of the monitoring object, and report the monitoring result to the configuration node according to at least one of the following: the traffic reporting period, the traffic report triggering threshold, and the single traffic reporting indication.

The present disclosure also provides a computer readable storage medium storing computer executable instructions for performing the data transfer method described above.

DRAWINGS

1 is a schematic structural diagram of a base station control plane and a user plane separated according to an embodiment;

2 is a schematic diagram of a separation structure of a base station centralized unit and a distribution unit according to an embodiment;

FIG. 3 is a schematic diagram of uplink and downlink data flow directions when a primary cell component bearer (MCG split bearer) is used according to an embodiment;

4 is a schematic diagram of uplink and downlink data flow directions when a secondary cell component bearer (SCG split bearer) is provided according to an embodiment;

FIG. 5 is a schematic flowchart of a data transmission method according to an embodiment; FIG.

FIG. 6 is a schematic flowchart of a data transmission method according to another embodiment;

FIG. 7 is a schematic structural diagram of a data transmission apparatus according to an embodiment; FIG.

FIG. 8 is a schematic structural diagram of a data transmission apparatus according to another embodiment; FIG.

FIG. 9 is a schematic flowchart of a data transmission method according to another embodiment;

FIG. 10 is a schematic flowchart diagram of a data transmission method according to another embodiment;

FIG. 11 is a schematic flowchart diagram of a data transmission method according to another embodiment;

FIG. 12 is a schematic flowchart of a data transmission method according to another embodiment;

FIG. 13 is a schematic flowchart diagram of a data transmission method according to another embodiment;

FIG. 14 is a schematic flowchart diagram of a data transmission method according to another embodiment;

FIG. 15 is a schematic flowchart diagram of a data transmission method according to another embodiment.

Detailed ways

The embodiments provided by the present disclosure will be described below with reference to the accompanying drawings. In a 4G or Long Term Evolution (LTE) mobile communication system, data flows with the same Quality of Service (QoS) requirements are aggregated into bearers, and the Radio Access Network (RAN) and the Radio Access Network (RAN) The core network (CN) handles QoS by bearer. In the 4G system, the RAN includes an Evolved Node B (eNB) and a User Equipment (UE). The network side bearer on the S1 interface between the eNB and the core network device and the radio bearer on the radio interface (Radio Interface) between the eNB and the UE are 1:1.

In the 5G system, the core network, base station and UE will all undergo major evolution. A 5G base station is called a new generation RAN Node (gNB). Similar to the X2 interface between eNBs in a 4G system, the interface between gNBs is called an Xn interface. The interface between the gNB and the 5G core network device is called the NG interface. A new QoS mechanism is adopted in the 5G system. The concept of the radio bearer on the radio interface still remains as the Data Radio Bearer (DRB). However, there is no concept of network side bearer on the NG interface. Instead, the protocol data unit session is replaced. Protocol Data Unit Session (PDU Session) and Quality of Service Flow (QoS Flow). A UE can have multiple PDU sessions. A PDU session can contain multiple QoS flows. Multiple QoS flows of the same PDU session can be mapped to the same DRB. The QoS flows of different PDU sessions cannot be mapped to the same DRB.

A 5G base station introduces a new protocol sub-layer (Service Data Adaptation Protocol (SDAP) layer) on the Packet Data Convergence Protocol (PDCP) layer. Used for mapping between QoS flow and DRB. Each PDU Session has one SDAP entity (Entity), and each DRB corresponds to one PDCP entity.

As shown in FIG. 1 and FIG. 2, a 5G base station can be divided into a central unit (CU) and a distributed unit (DU). One base station has one CU, and one base station can have multiple DUs. Centralized unit distribution unit separation (CU DU Split). The CU of the 5G base station or the 5G base station can be divided into two parts: Control Plane (CP) and User Plane (UP), which is called CP UP Split. The interface between CU and DU is called For the F1 interface, the interface between the CP and the UP is temporarily called the E1 interface.

The 5G base station also has a transitional base station called a New Generation eNB (NG-eNB), which can be simultaneously connected to the 4G core network Evolved Packet Core (EPC) and the 5G core network (5G Core Network, 5GC), while the NG-eNB's wireless interface is closer to the 4G wireless interface.

Dual connectivity (DC) is supported in both 4G and 5G systems. The dual-connected UE can maintain connection with two base stations at the same time. One base station is called a primary base station (MN), and the other base station is called a secondary base station (SN). The dual-connected UE is mainly controlled by the MN. The dual-connection bearer type can be in four forms: a primary cell group bearer (MCG bearer), a secondary cell group bearer (SCG bearer), and a primary cell group bearer (MCG split bearer). And the secondary cell component bearer (SCG Split bearer). As shown in Figure 3, when the MCG split bearer is used, the downlink data flows from the CN device to the MN, branches in the MN, flows directly to the UE, and the other flows through the SN to the UE; as shown in Figure 4, when the SCG Split bearer is used The downlink data flows from the CN device to the SN, branches at the SN, one flows directly to the UE, and the other flows to the UE through the MN. When an MCG bearer or SCG bearer is used, downlink data flows from the CN device to the MN or SN, and then flows directly to the UE.

The type of bearer carried in dual connectivity can be changed, such as MCG bearer changed to MCG split bearer, MCG bearer changed to SCG bearer, SCG bearer changed to MCG bearer or SCG bearer changed to SCG split bearer. In 5G systems, Multiple Connectivity (MC) is also supported. The UE can maintain connection with more than two base stations at the same time, one of the base stations is the primary base station, and the other base stations are the secondary base stations.

When 4G/5G hybrid networking enters DC, there are three implementations: Evolved Universal Terrestrial Radio Access - New Wireless (E-UTRA-NR, EN) DC, Next Generation Evolved Universal Terrestrial Radio Access - New Wireless (NG E-UTRA-NR, NGEN) DC and New Wireless - Next Generation Evolved Universal Terrestrial Radio Access (NR-NG E-UTRA, NE) DC. When EN DC is used, MN is 4G base station eNB, SN is 5G base station gNB; when NGEN DC is used, MN is NG-eNB, SN is 5G base station gNB; when NE DC is used, MN is 5G base station gNB, SN is NG-eNB .

When the 4G/5G hybrid network is deployed, there are various forms of handover, including: intra-system intra-RAT handover (Radio Access Technology, RAT), such as handover between eNBs or Intra-system inter-RAT handover, such as handover between NG-eNB and gNB when connected to 5GC; inter-system inter-RAT handover For example, handover between NG-eNB and gNB when connecting to EPC or handover between eNB and gNB; inter-system intra-RAT handover, such as NG-eNB connected to EPC and connected to Switching between NG-eNBs at 5GC.

When the 4G/5G hybrid network is deployed, the offline charging function needs to be introduced. It is mainly used in scenarios such as EN DC. When the eNB and the gNB may belong to different carriers, the inter-operator billing settlement is supported.

In the 4G, 5G, and 4G/5G hybrid networks (including CP/UP split scenarios), how to implement rate control and traffic reporting for the UE in the connected state, or when switching, dual connectivity/multiple connectivity is disclosed. content.

FIG. 5 is a schematic flowchart of a data transmission method according to an embodiment. As shown in FIG. 5, the data transmission method provided in this embodiment includes the following steps.

Step 5010: The monitoring node receives configuration information of the configuration node, where the configuration information includes monitoring object information, monitoring configuration information, and report configuration information.

Step 5020: The monitoring node monitors the monitoring object corresponding to the monitoring object information according to the monitoring configuration information, and reports the monitoring result to the configuration node according to the report configuration information.

In an embodiment, the monitoring configuration information includes at least one of the following: a rate control indication, a guaranteed bit rate, a monitoring window duration, a monitoring window interval, and a traffic report indication.

In an embodiment, the monitoring object information includes at least one of the following: a user equipment, a bearer, a logical channel, a protocol data unit session, and a quality of service stream.

In an embodiment, the monitoring object information includes at least one of: a bit rate of the user equipment, a bit rate of the bearer, a bit rate of the logical channel, a bit rate of the protocol data unit session, a bit rate of the quality of service stream, and a user. Total traffic of the device, total traffic carried by the traffic, total traffic of the logical channel, total traffic of the protocol data unit session, total traffic of the quality of service flow, total traffic transmitted by at least one wireless access technology used by the user equipment, and bearer usage The total traffic transmitted by at least one radio access technology and the total traffic transmitted by the radio access technology used by the logical channel.

In an embodiment, the report configuration information includes at least one of the following: a report type, a report event configuration, a minimum report interval, and a maximum number of reports.

In an embodiment, the report type includes at least one of the following: a single report after receiving the configuration information, a periodic report, an event triggered single report, an event triggered periodic report, and when the bearer, the logical channel, or the UE Reported when released.

In an embodiment, where the report type includes reporting when the bearer, the logical channel, or the user equipment is released, the method further includes releasing the bearer, the logical channel, or when the bearer, the logical channel, or the user equipment is released. The monitoring result is carried in the response message corresponding to the message of the user equipment.

In an embodiment, the report event configuration includes at least one of the following: a report event type and a preset condition.

In an embodiment, the report event type includes at least one of the following: the measurement result of the monitoring object satisfies a preset condition; the measurement result of the monitoring object does not satisfy the preset condition; the measurement result of the monitoring object satisfies the preset condition and remains pre- The measurement result of the monitoring object does not meet the preset condition and maintains the preset duration; the measurement result of the monitoring object never satisfies the preset condition until the preset condition is satisfied; the measurement result of the monitoring object satisfies the preset condition to the unsatisfied The condition is set; the measurement result of the monitoring object never satisfies the preset condition until the preset condition is satisfied and the preset duration is maintained; the measurement result of the monitoring object satisfies the preset condition and does not satisfy the preset condition and maintains the preset duration.

In an embodiment, the preset condition includes at least one of: a measurement result of the monitoring object is greater than, greater than or equal to, equal to, less than, or less than or equal to a pre-configured threshold; and, the measurement result of the monitoring object is greater than, Greater than or equal to, equal to, less than, or less than or equal to the pre-configured first threshold, and greater than, greater than or equal to, equal to, less than, or less than or equal to the pre-configured second threshold.

In an embodiment, the preset condition, the threshold, the first threshold, the second threshold, and the preset duration are configured by protocol signaling or agreed in a standard.

In an embodiment, the monitoring configuration information further includes at least one of the following: a rate control indication, a guaranteed bit rate (GBR), a monitoring window duration, and a monitoring window interval.

In an embodiment, the monitoring node performs rate monitoring on the monitoring object in the monitoring configuration information for the monitoring object that needs rate control according to the monitoring window duration (for example, the average rate in the monitoring window duration), if the monitoring is performed. If the rate does not reach the currently configured GBR (or the monitored rate reaches the GBR of the higher level configuration), the monitoring result is reported, and the interval between the two reports is at least the minimum reporting interval, and the total number of reports does not exceed the maximum. The number of reports.

In an embodiment, the data transmission method further includes: the monitoring node receiving the configuration information of the configuration node multiple times; the monitoring node saves the guaranteed bit rate in each received configuration information, and the first The guaranteed bit rate in the received configuration information is saved as the guaranteed bit rate of the initial configuration, and the guaranteed bit rate in the configuration information received multiple times is sorted and saved in the order of high and low.

In an embodiment, when the monitoring node receives the configuration information of the configuration node by using the forwarding node, the configuration information includes a guaranteed bit rate in each received configuration information saved by the forwarding node.

In an embodiment, the monitoring result includes monitoring object information, and further includes at least one of the following: the monitored rate, the monitored rate does not reach an indication of the currently configured guaranteed bit rate, and the monitored rate reaches the stated The initial configured guaranteed bit rate indication, the monitored rate reaches an indication of a guaranteed guaranteed bit rate that is one level higher than the currently configured guaranteed bit rate, the monitored rate reaches the currently configured guaranteed bit rate and is guaranteed with the current configuration The bit rate difference reaches the M/N information of the gap between the currently configured guaranteed bit rate and the initially configured guaranteed bit rate, where / is the ratio, N and M are both natural numbers, and N > M.

In an embodiment, if the gap between the currently configured GBR and the initially configured GBR is too large, for example, the initially configured GBR is 100, and the currently configured GBR is 40 (the configured GBR may be lowered from 80, 60, and 40). The monitoring node can decide by itself to lower the trigger threshold for reporting the monitoring result. For example, if 1/2 is taken, it will report when it reaches (100-40)/2+40=70, and if it takes 1/3, it will be reached ( Reported when 100-40)/3+40=60.

In an embodiment, the data transmission method further includes: the monitoring node receiving configuration information of the configuration node multiple times; and the monitoring node saving the guaranteed bit rate in the configuration information received for the first time as an initial The guaranteed bit rate is configured to save the guaranteed bit rate in the last received configuration information as the currently configured guaranteed bit rate.

In an embodiment, when the monitoring node receives configuration information of the configuration node by using a forwarding node, where the configuration information includes an initial configured guaranteed bit rate saved by the forwarding node and a currently configured guaranteed bit rate.

In an embodiment, the monitoring node reports the monitoring result to the configuration node according to the report configuration information, including: if the currently configured guaranteed bit rate and the initially configured guaranteed bit rate differ by more than a preset gap threshold And the monitoring node calculates, according to the currently configured guaranteed bit rate and the initially configured guaranteed bit rate, a bit rate report threshold threshold that triggers reporting of the monitoring result, when the monitored bit rate reaches a bit rate reporting threshold threshold, Reporting the monitoring result to the configuration node according to the report configuration information.

In an embodiment, the monitoring node receives the configuration information of the configuration node, and the monitoring node receives the configuration information of the configuration node by using the forwarding node.

In an embodiment, the reporting the monitoring result to the configuration node includes: reporting, by the forwarding node, a monitoring result to the configuration node.

In an embodiment, the monitoring node may receive the configuration information of the configuration node through the forwarding node and report the monitoring result to the configuration node through the forwarding node (the configuration information and the monitoring result are forwarded), that is, the forwarding node receives the configuration information of the configuration node, and the forwarding node The configuration information is forwarded to the monitoring node, and the monitoring node monitors the monitoring configuration information and reports the monitoring result to the forwarding node, and the forwarding node forwards the monitoring result to the configuration node. The forwarding node can also receive the configuration information of the configuration node and directly to the configuration node. Reporting the monitoring result (configuration information forwarding only), that is, the forwarding node receives the configuration information of the configuration node, and the forwarding node forwards the configuration information to the monitoring node, and the monitoring node monitors the monitoring configuration information and directly reports the monitoring result to the configuration node.

In an embodiment, the configuration node and the monitoring node may be any one of the following: the configuration node is a core network device, and the monitoring node is a base station (such as an eNB, a gNB, or an NG-eNB), and the configuration information is And the monitoring result is sent through the S1 or the NG interface; the configuration node is the primary base station, the monitoring node is the secondary base station, and the configuration information and the monitoring result are sent through the X2 or Xn interface; The user plane is separated from the control plane, the configuration node is a base station control plane, the monitoring node is a base station user plane, and the configuration information and the monitoring result are sent through the E1 interface.

In an embodiment, the configuration node, the forwarding node (the configuration information and the monitoring result are forwarded), and the monitoring node may be any one of the following: applied to a dual connectivity/multi-connection scenario, where the configuration node is a core network device, The forwarding node is a primary base station, and the monitoring node is a secondary base station, and the configuration information is sent through an S1 or NG interface and forwarded through an X2 or Xn interface, and the monitoring result is sent through an X2 or Xn interface and through an S1 or NG interface. Forwarding; applied to the control plane user plane separation scenario, the configuration node is a core network device, the forwarding node is a base station control plane, the monitoring node is a base station user plane, and the configuration information is sent and passed through the S1 or NG interface. The E1 interface forwards the packet. The monitoring result is sent through the E1 interface and forwarded through the S1 or NG interface.

In an embodiment, the configuration node, the forwarding node (configuration information forwarding only), and the monitoring node may be: applied to a handover scenario, the configuration node is a core network device, the forwarding node is a source base station, and the monitoring is performed. The node is the target base station, and the configuration information is sent through the S1 or NG interface and forwarded through the X2 or Xn interface, and the monitoring result is directly sent through the S1 or NG interface.

In an embodiment, the sending and forwarding manners of the configuration information and the monitoring result may be any one of the following: designing a new cell by using an existing message on the S1/NG interface, the X2/Xn interface, or the E1 interface. Design new messages on the S1/NG interface, X2/Xn interface, and E1 interface.

In an embodiment, when the bearer, the logical channel, or the UE is released, the monitoring result is carried in a response message corresponding to the message of the release bearer, the logical channel, or the UE.

FIG. 6 is a schematic flowchart diagram of a data transmission method according to another embodiment. As shown in FIG. 6, the data transmission method provided in this embodiment includes the following steps.

Step 6010: The monitoring node receives the configuration information of the configuration node, where the configuration information includes the monitoring object, and further includes at least one of the following: a traffic reporting period, a traffic report triggering threshold, and a single traffic reporting indication.

Step 6020: The monitoring node monitors according to the configuration information, and reports the monitoring result to the configuration node.

In an embodiment, the configuration information further includes a traffic report indication.

In an embodiment, the traffic report indicated in the configuration information is a monitoring object that needs the traffic report, and the total traffic on the monitoring node side is monitored. If the monitored total traffic reaches the traffic report trigger threshold, the monitoring result is reported, and the total traffic is cleared. 0, restart monitoring, wait until the next time the total traffic reaches the traffic report trigger threshold, report the monitoring result again; or report the monitoring result periodically according to the traffic reporting period. After each report, the total traffic is cleared to 0, restart monitoring; or press A single flow report indicates that the monitoring results are reported only once at the end.

In an embodiment, the monitoring result includes: monitoring the monitored object and the monitored total traffic, and the monitored total traffic includes at least one of: a total traffic of the wireless interface between the monitoring node and the user equipment of the monitoring object; The total traffic of the S1/NG interface between the monitoring node and the core network device is monitored.

In an embodiment, the monitoring node may receive the configuration information of the configuration node through the forwarding node and report the monitoring result to the configuration node through the forwarding node (the configuration information and the monitoring result are forwarded), that is, the forwarding node receives the configuration information of the configuration node, and the forwarding node The configuration information is forwarded to the monitoring node, and the monitoring node monitors the configuration information and reports the monitoring result to the forwarding node. The forwarding node forwards the monitoring result to the configuration node. The forwarding node can also receive the configuration information of the configuration node and report directly to the configuration node. The monitoring result (configuration information forwarding only), that is, the forwarding node receives the configuration information of the configuration node, and the forwarding node forwards the configuration information to the monitoring node, and the monitoring node monitors according to the configuration information and directly reports the monitoring result to the configuration node.

In an embodiment, the configuration node and the monitoring node may be any one of the following: the configuration node is a core network device, and the monitoring node is a base station (such as an eNB, a gNB, an NG-eNB), and the configuration information is And the monitoring result is sent through the S1 or the NG interface; the configuration node is the primary base station, the monitoring node is the secondary base station, and the configuration information and the monitoring result are sent through the X2 or Xn interface; The user plane is separated from the control plane, the configuration node is a base station control plane, the monitoring node is a base station user plane, and the configuration information and the monitoring result are sent through the E1 interface.

FIG. 7 is a schematic structural diagram of a data transmission apparatus according to an embodiment. As shown in FIG. 7, the data transmission apparatus provided in this embodiment includes a first receiving unit 701 and a first monitoring unit 702. In an embodiment, the first receiving unit 701 is configured to receive configuration information of the configuration node, and output the configuration information to the first monitoring unit 702, where the configuration information includes monitoring object information, monitoring configuration information, and report configuration information; The first monitoring unit 702 is configured to monitor the monitoring object corresponding to the monitoring object information according to the monitoring configuration information, and report the monitoring result to the configuration node according to the report configuration information.

In an embodiment, the first receiving unit 701 is configured to implement configuration information of receiving a configuration node by receiving configuration information of the configuration node by using a forwarding node.

In an embodiment, the first monitoring unit 702 is configured to report the monitoring result to the configuration node by reporting the monitoring result to the configuration node by using the forwarding node.

In an embodiment, the monitoring object information includes at least one of the following: a user equipment, a bearer, a protocol data unit session, and a quality of service stream.

In an embodiment, the first receiving unit 701 is further configured to: receive the configuration information of the configuration node multiple times, save the guaranteed bit rate in each received configuration information, and configure the first received configuration. The guaranteed bit rate in the information is saved as the guaranteed bit rate of the initial configuration, and the guaranteed bit rate in the configuration information received multiple times is sorted and saved in order of high and low.

In an embodiment, the first receiving unit 701 is further configured to: receive the configuration information of the configuration node multiple times, and save the guaranteed bit rate in the first received configuration information as the initial configured guaranteed bit rate. The guaranteed bit rate in the last received configuration information is saved as the currently configured guaranteed bit rate.

In an embodiment, the first monitoring unit 702 is configured to report the monitoring result to the configuration node according to the report configuration information, by: if the currently configured guaranteed bit rate and the initial configuration And ensuring that the bit rate difference is greater than a preset gap threshold, and calculating, according to the currently configured guaranteed bit rate and the initially configured guaranteed bit rate, a bit rate report threshold threshold that triggers reporting of the monitoring result, when the monitored bit rate reaches a bit rate. When the threshold threshold is reported, the monitoring result is reported to the configuration node according to the report configuration information.

The report configuration information includes at least one of the following: a report type, a report event configuration, a minimum report interval, and a maximum number of reports.

In an embodiment, the content of the report type and the report event configuration are as described above, and details are not described herein again.

In an embodiment, the configuration node and the monitoring node are as described above, and are not described herein again.

FIG. 8 is a schematic structural diagram of a data transmission apparatus according to another embodiment. As shown in FIG. 8, the data transmission apparatus provided in this embodiment includes a second receiving unit 801 and a second monitoring unit 802.

In an embodiment, the second receiving unit 801 is configured to receive configuration information of the configuration node, and output the configuration information to the second monitoring unit 802, where the configuration information includes a monitoring object, and further includes at least the following a traffic reporting period, a traffic report triggering threshold, and a single traffic reporting indication; the second monitoring unit 802 is configured to monitor the traffic of the monitoring object, and report the monitoring result to the configuration node according to at least one of the following: the traffic reporting period , traffic report trigger threshold and single traffic report indication.

In an embodiment, the monitoring result includes: monitoring the monitored object and the monitored total traffic, and the monitored total traffic includes at least one of: a wireless interface between the monitoring object and the user equipment on the second monitoring unit side. The traffic flow; and the total traffic of the S1/NG interface between the second monitoring unit side and the core network device.

The following examples are provided to explain the present disclosure, and the following examples are only for the purpose of better description of the disclosure and are not intended to limit the disclosure. The following various embodiments may exist independently, and the technical features in different embodiments may be combined and used in combination in one embodiment. The designation of the specific configuration information, the specific interface name, and the specific node name may be changed in the present disclosure, and the title does not affect the method implementation in the present disclosure.

Embodiment 1

As shown in Figure 9, for the QoS flow that needs rate control, the CN device sends configuration information to the base station for the first time. The configuration information includes the QoS flow identifier, the PDU session identifier, the rate control indication, and the guaranteed bit rate GBR (such as 1000). Bit rate (Kbps), monitoring window duration, minimum reporting interval, and maximum number of reports.

The GBR in the configuration information saved by the base station is the current configuration GBR. For the rate control in the configuration information, the QoS flow is required to be rate controlled. The base station performs rate monitoring according to the duration of the monitoring window (for example, the average rate in the duration of the monitoring window).

If the monitored rate does not reach the current configured GBR (1000 Kbps), the base station reports the monitoring result to the CN device, including the QoS flow identifier, the PDU Session identifier, and the monitored rate, and the interval between the two reports is at least the minimum reporting interval. The total number of reports does not exceed the maximum number of reports.

The CN device determines the subsequent action according to the received monitoring result, for example, sending the configuration information to the base station for the second time after the relevant QoS flow is reduced by the GBR (for example, 800 Kbps).

The base station saves the current configuration GBR (that is, the GBR in the first configuration information) as the initial configuration GBR, and saves the GBR in the second configuration information as the current configuration GBR, and the base station continues to perform rate monitoring.

When the monitored rate does not reach the current configuration GBR (800 Kbps), or the monitored rate reaches the high-level configuration GBR (here, the initial configuration GBR), the base station reports the monitoring result to the CN device, and the monitoring result includes the QoS flow identifier. , PDU Session ID and the monitored rate (here set to the monitored rate to reach the initial configuration GBR).

The CN device determines the subsequent action according to the received monitoring result. For example, the configuration information is sent to the base station for the third time after the initial configuration of the GBR for the relevant QoS flow recovery.

Embodiment 2

As shown in FIG. 10, for the QoS flow that needs rate control, the CN device sends configuration information to the base station for the first time, and the configuration information includes the QoS flow identifier of the monitoring object, the PDU Session identifier, the rate control indication, and the guaranteed bit rate GBR (for example, 1000 Kbps). ), monitoring window duration, minimum reporting interval, and maximum number of reports.

The GBR in the configuration information saved by the base station is the current configuration GBR. For the QoS flow indicating that the rate control is required in the configuration information, the base station performs rate monitoring according to the duration of the monitoring window (for example, the average rate in the duration of the monitoring window).

If the monitored rate does not reach the current configured GBR (1000 Kbps), the base station reports the monitoring result to the CN device, and the monitoring result includes the QoS flow identifier, the PDU Session identifier, the monitored rate does not reach the current configuration GBR indication, and two The interval between sub-reports is at least the minimum reporting interval, and the total number of reports does not exceed the maximum number of reports.

When the monitored rate does not reach the current configuration GBR (800 Kbps), or the monitored rate reaches the high-level configuration GBR (here, the initial configuration GBR), the base station reports the monitoring result to the CN device, and the monitoring result includes the QoS flow identifier. The PDU session identifier and the monitored rate do not reach the current configuration GBR indication (here, the monitored rate does not reach the current configuration GBR).

The CN device determines the subsequent action according to the received monitoring result, for example, sending the configuration information to the base station for the third time after the relevant QoS flow is reduced by the GBR (for example, 400 Kbps).

The base station saves the GBR in the third configuration information as the current configured GBR, and the base station continues to perform rate monitoring.

When the monitored rate does not reach the current configuration GBR (400Kbps), or the monitored rate reaches 1/2 of the initial configuration GBR (the base station sets itself in advance), the base station reports the monitoring result to the CN device, and the monitoring result Including the QoS flow identifier, the PDU Session identifier, and the information that the monitored rate reaches 1/2 of the gap with the initial configuration GBR (here, the monitored rate reaches 1/2 of the gap with the initial configuration GBR, that is, reaches (1000). -400) / 2+400 = 700 Kbps).

The CN device determines the subsequent action according to the received monitoring result, for example, sending the configuration information to the base station for the fourth time after the relevant QoS flow is increased by the GBR (for example, 700 Kbps).

Embodiment 3

As shown in Figure 11, for the QoS flow that needs rate control, the CN device sends configuration information to the base station for the first time. The configuration information includes the QoS flow identifier of the monitoring object, the PDU session identifier, the rate control indication, and the guaranteed bit rate GBR (for example, 1000 Kbps). ), monitoring window duration, minimum reporting interval, and maximum number of reports.

If the monitored rate does not reach the current configured GBR, the base station reports the monitoring result to the CN device, and the monitoring result includes the QoS flow identifier, the PDU Session identifier, and the monitored rate does not reach the current configuration GBR indication, and the two reports are The interval between at least is the minimum reporting interval, and the total number of reports does not exceed the maximum number of reports.

The CN device determines the subsequent action according to the received monitoring result, for example, sending the configuration information to the base station for the third time after the relevant QoS flow is reduced by the GBR (for example, 600 Kbps).

The base station saves the current configuration GBR (that is, the GBR in the second configuration information) as the higher-level configuration GBR, and saves the GBR in the third configuration information as the current configuration GBR, and the base station continues to perform rate monitoring.

When the monitored rate does not reach the current configuration GBR (600 Kbps), or the monitored rate reaches the high-level configuration GBR (800 Kbps), the base station reports the monitoring result to the CN device, and the monitoring result includes the QoS flow identifier, the PDU Session identifier, The monitored rate reaches the indication that the GBR is configured at a higher level (here, the monitored rate reaches the higher level configuration GBR).

The CN device determines the subsequent action according to the received monitoring result, for example, sending the configuration information to the base station for the fourth time after the relevant QoS flow is increased by the GBR (for example, 800 Kbps).

Embodiment 4

As shown in FIG. 12, for the QoS flow that needs to perform rate control, the CN device sends configuration information to the primary base station for the first time, and the configuration information includes the QoS flow identifier of the monitoring object, the PDU Session identifier, the standard rate control indication, and the guaranteed bit rate GBR ( Such as 1000Kbps), monitoring window duration, minimum reporting interval, and maximum number of reports.

The primary base station forwards the first configuration information to the secondary base station for the QoS flow that is offloaded to the secondary base station (ie, the QoS flow mapped to the SCG bearer and the SCG split bearer).

The secondary base station saves the GBR in the configuration information as the current configuration GBR. For the configuration information, the rate control indicates that the rate control is QoS flow, and the secondary base station performs rate monitoring according to the monitoring window duration (for example, the average rate in the monitoring window duration).

If the monitored rate does not reach the current configured GBR (1000 Kbps), the secondary base station reports the monitoring result to the primary base station, and the monitoring result includes the QoS flow identifier, the PDU Session identifier, and the monitored rate, and the interval between the two reports is at least For the minimum reporting interval, the total number of reports does not exceed the maximum number of reports.

The primary base station forwards the monitoring result reported by the secondary base station to the CN device.

Based on the received monitoring result, the CN device determines the subsequent action. For example, after the relevant QoS flow is reduced, the GBR sends the configuration information to the primary base station for the second time (for example, 800 Kbps).

The primary base station forwards the second configuration information to the secondary base station for the QoS flow that is offloaded to the secondary base station.

The secondary base station saves the current configuration GBR (that is, the GBR in the first configuration information) as the initial configuration GBR, and saves the GBR in the second configuration information as the current configuration GBR, and the secondary base station continues to perform rate monitoring.

When the monitored rate does not reach the current configuration GBR (800 Kbps), or the monitored rate reaches the high-level configuration GBR (here, the initial configuration GBR), the secondary base station reports the monitoring result to the primary base station, and the monitoring result includes the QoS flow. ID, PDU Session ID, and monitored rate (here set to the monitored rate to the initial configuration GBR).

The CN device determines the subsequent action according to the received monitoring result. For example, the configuration information is sent to the primary base station for the third time after the initial configuration of the GBR for the relevant QoS flow recovery.

The primary base station forwards the third configuration information to the secondary base station for the QoS flow that is offloaded to the secondary base station.

Embodiment 5

As shown in FIG. 12, for the QoS flow that needs to perform rate control, the CN device sends configuration information to the control plane of the base station for the first time, and the configuration information includes the QoS flow identifier of the monitoring object, the PDU Session identifier, the standard rate control indication, and the guaranteed bit rate GBR. (eg 1000Kbps), monitoring window duration, minimum reporting interval, and maximum number of reports.

The base station controls to forward the first configuration information to the base station user plane.

The GBR in the configuration information of the base station user saves the current configuration GBR, and the rate control indication in the configuration information indicates that the rate control is QoS flow, and the base station user performs rate monitoring according to the duration of the monitoring window (for example, the average rate in the duration of the monitoring window) ).

If the monitored rate does not reach the current configured GBR (1000 Kbps), the base station user reports the monitoring result to the base station control plane, and the monitoring result includes the QoS flow identifier, the PDU Session identifier, and the monitored rate, and the interval between the two reports. At least the minimum reporting interval, the total number of reports does not exceed the maximum number of reports.

The base station control plane forwards the monitoring result reported by the base station user plane to the CN device.

The CN device determines the subsequent action according to the received monitoring result. For example, after the relevant QoS flow is reduced, the GBR (for example, 800 Kbps) sends configuration information to the control plane of the base station for the second time.

The base station controls to forward the second configuration information to the base station user plane.

The base station user plane saves the current configuration GBR (that is, the GBR in the first configuration information) as the initial configuration GBR, and saves the GBR in the second configuration information as the current configuration GBR, and the base station user plane continues to perform rate monitoring.

When the monitored rate does not reach the current configuration GBR (800Kbps), or the monitored rate reaches the high-level configuration GBR (here, the initial configuration GBR), the base station user reports the monitoring result to the base station control plane, and the monitoring result includes QoS. The flow identifier, the PDU Session identifier, and the monitored rate (here, the monitored rate reaches the initial configuration GBR).

The CN device determines the subsequent action according to the received monitoring result. For example, the configuration information is sent to the control plane of the base station for the third time after the initial configuration of the GBR is resumed.

The base station control forwards the third configuration information to the base station user plane.

Embodiment 6

As shown in FIG. 13, for the QoS flow that needs to perform rate control, the CN device sends configuration information to the source base station for the first time, and the configuration information includes the QoS flow identifier of the monitoring object, the PDU Session identifier, the standard rate control indication, and the guaranteed bit rate GBR ( Such as 1000Kbps), monitoring window duration, minimum reporting interval, and maximum number of reports.

The source base station saves the GBR in the configuration information as the current configuration GBR. For the configuration information, the rate control indicates that the rate control is QoS flow, and the source base station performs rate monitoring according to the duration of the monitoring window (for example, the average rate in the duration of the monitoring window).

If the monitored rate does not reach the current configured GBR (1000 Kbps), the source base station reports the monitoring result to the CN device, and the monitoring result includes the QoS flow identifier, the PDU Session identifier, and the monitored rate, and the interval between the two reports is at least For the minimum reporting interval, the total number of reports does not exceed the maximum number of reports.

The CN device determines the subsequent action according to the received monitoring result. For example, after the relevant QoS flow is reduced by the GBR (for example, 800 Kbps), the configuration information is sent to the source base station for the second time.

The source base station saves the current configuration GBR (that is, the GBR in the first configuration information) as the initial configuration GBR, and saves the GBR in the second configuration information as the current configuration GBR, and the source base station continues to perform rate monitoring.

The source base station performs handover preparation, and forwards the configuration information to the target base station. The configuration information includes the QoS flow identifier, the PDU session identifier, the standard rate control indication, the guaranteed bit rate GBR, the monitoring window duration, the minimum reporting interval, and the maximum number of reports. It also includes the saved initial configuration GBR (1000Kbps) and the current configuration GBR (800Kbps).

The UE switches from the source base station to the target base station.

The target base station performs rate monitoring.

When the monitored rate does not reach the current configuration GBR, or the monitored rate reaches the high-level configuration GBR (here, the initial configuration GBR), the target base station reports the monitoring result to the CN device, and the monitoring result includes the QoS flow identifier and the PDU. The session ID and the monitored rate (here set to the monitored rate reaches the initial configuration GBR).

The CN device determines the subsequent action according to the received monitoring result, for example, sends the configuration information to the target base station for the third time after the initial configuration of the GBR for the relevant QoS flow recovery.

Example 7

As shown in FIG. 14, the CN device sends configuration information to the primary base station for the QoS flow that needs to report the traffic. The configuration information includes the QoS flow identifier, the PDU session identifier, the traffic report indication, and the traffic report period and the traffic report trigger threshold. And a single traffic report indicates one of the three.

For the QoS flow associated with the secondary base station, that is, the QoS flow mapped to the MCG split bearer, the SCG bearer, and the SCG split bearer, the primary base station forwards the configuration information to the secondary base station, and the configuration information includes the QoS flow identifier, the PDU session identifier, and the traffic report. One of the indications, as well as the traffic reporting period, the traffic report trigger threshold, and the single traffic report indication.

The secondary base station saves the traffic report triggering condition in the configuration information. For the traffic report indicating that the traffic report indicates that the traffic report is required, the secondary base station performs traffic monitoring.

When the traffic report trigger condition is met (such as periodic triggering according to the traffic report period included in the configuration information, the total traffic is cleared to 0 after each report, and monitoring is restarted; or the traffic report trigger threshold is included in the configuration information. When the monitored total traffic reaches the threshold, it is triggered. After each report, the total traffic is cleared to 0, and monitoring is restarted. Or, according to the single traffic report indication included in the configuration information, when the relevant QoS flow is removed from the secondary base station to the primary base station or to other The secondary base station or the one-time triggering when the secondary base station is released, the secondary base station reports the monitoring result to the primary base station, and the monitoring result includes the QoS flow identifier, the PDU session identifier, and the total monitored traffic (including the wireless interface between the QoS flow and the UE on the secondary base station side). The total traffic and the QoS flow are at least one of the total traffic of the S1/NG interface between the QoS flow secondary base station side and the core network device.

Example eight

As shown in FIG. 14, the CN device sends configuration information to the control plane of the base station for the QoS flow that needs to report the traffic. The configuration information includes the QoS flow identifier, the PDU session identifier, the traffic report indication, and the traffic report period and the traffic report trigger. The threshold and single flow report indicate one of the three.

The base station controls the forwarding configuration information for the base station user plane, and the configuration information includes one of a QoS flow identifier, a PDU Session identifier, a traffic report indication, and a traffic report period, a traffic report trigger threshold, and a single traffic report indication.

The base station user plane saves the traffic report triggering condition in the configuration information, and performs traffic monitoring on the base station user plane for the QoS flow indicating that the traffic report indicates that the traffic report is required in the configuration information.

When the traffic report trigger condition is met (such as periodic triggering according to the traffic report period included in the configuration information, the total traffic is cleared to 0 after each report, and monitoring is restarted; or the traffic report trigger threshold is included in the configuration information. When the monitored total traffic reaches the threshold, the total traffic is cleared to 0 after each report, and the monitoring is restarted. The monitoring result is reported by the base station control plane, and the monitoring result includes the QoS flow identifier, the PDU Session identifier, and the total traffic monitored (including the total traffic of the QoS flow between the UE and the UE and the QoS flow between the UE and the core network device). At least one of the total traffic of the S1/NG interface).

Example nine

As shown in FIG. 15, the CN device sends configuration information to the source base station, where the configuration information includes the monitoring target UE identifier, the traffic report indication, the traffic report period, the traffic report trigger threshold, and the single traffic report indication. One of the three.

The source base station saves the traffic report triggering condition in the configuration information, and the source base station performs traffic monitoring for the UE whose traffic report indicates that the traffic report is required in the configuration information.

When the traffic report trigger condition is met (such as periodic triggering according to the traffic report period included in the configuration information, the total traffic is cleared to 0 after each report, and monitoring is restarted; or the traffic report trigger threshold is included in the configuration information. When the monitored total traffic reaches the threshold, the total traffic is cleared to 0 after each report, and the monitoring is restarted. Or, according to the single traffic report indication included in the configuration information, when the relevant UE switches from the source base station to the target base station, the source base station The source base station reports the monitoring result to the CN device when the wireless interface data transmission is stopped or when the UE is released. The monitoring result includes the UE identifier and the total traffic monitored (including the total traffic of the QoS flow between the source base station and the UE. And at least one of the total traffic of the S1/NG interface between the source base station and the core network device of the QoS flow.

The source base station performs handover preparation and forwards the configuration information to the target base station. The configuration information includes one of the UE identifier, the traffic report indication, and the traffic report period, the traffic report trigger threshold, and the single traffic report indication.

The UE switches from the source base station to the target base station.

The target base station saves the traffic report triggering condition in the configuration information, and the target base station performs traffic monitoring for the UE whose traffic report indicates that the traffic report is required in the configuration information.

When the traffic report trigger condition is met (such as periodic triggering according to the traffic report period included in the configuration information, the total traffic is cleared to 0 after each report, and monitoring is restarted; or the traffic report trigger threshold is included in the configuration information. When the monitored total traffic reaches the threshold, it is triggered. After each report, the total traffic is cleared to 0, and monitoring is restarted. Or, according to the single traffic report indication included in the configuration information, when the relevant UE switches from the target base station to other base stations, the target base station The target base station reports the monitoring result to the CN device when the wireless interface data transmission is stopped or when the UE is released. The monitoring result includes the UE identifier and the total monitored traffic (including the total traffic of the QoS flow between the target base station and the UE. (including at least one of the data transmitted by the source base station to the target base station during the handover process) and at least one of the total traffic of the S1/NG interface between the target base station and the core network device.

One of ordinary skill in the art will appreciate that all or a portion of the steps described above can be accomplished by a program that instructs the associated hardware, such as a read-only memory, a magnetic or optical disk, and the like. In an embodiment, all or part of the steps of the foregoing embodiments may also be implemented by using one or more integrated circuits. In an embodiment, each module/unit in the above embodiment may be implemented in the form of hardware. It can be implemented in the form of a software function module.

The above description is only an embodiment of the present disclosure, and is not intended to limit the present disclosure.

Claims

A data transmission method includes:

The monitoring node receives configuration information of the configuration node, where the configuration information includes monitoring object information, monitoring configuration information, and report configuration information;

The monitoring node monitors the monitoring object corresponding to the monitoring object information according to the monitoring configuration information, and reports the monitoring result to the configuration node according to the report configuration information.
The data transmission method according to claim 1, wherein the monitoring configuration information comprises at least one of the following:

Rate control indication, guaranteed bit rate, monitoring window duration, monitoring window interval, and traffic report indication.
The data transmission method according to claim 2, wherein in the case that the monitoring configuration information includes the guaranteed bit rate, the method further comprises:

The monitoring node receives the configuration information of the configuration node multiple times, and saves the guaranteed bit rate in the configuration information received for the first time as the initial configured guaranteed bit rate, and the configured configuration is received multiple times. The guaranteed bit rate in the message is sorted and saved in high and low order.
The data transmission method according to claim 3, wherein the monitoring result comprises the monitoring object information, and further comprising at least one of the following: the monitored rate, the monitored rate does not reach the currently configured guaranteed bit rate. Indicating, indicating that the monitored rate reaches the initial configured guaranteed bit rate, the monitored rate reaches an indication of the guaranteed guaranteed bit rate that is one level higher than the currently configured guaranteed bit rate, and the monitored rate reaches the current configuration Guaranteeing a bit rate and the difference between the monitored rate and the currently configured guaranteed bit rate reaches an M/N of the difference between the currently configured guaranteed bit rate and the initially configured guaranteed bit rate, wherein / is the ratio, N and M are both natural numbers, and N>M.
The data transmission method according to claim 2, wherein in the case that the monitoring configuration information includes the guaranteed bit rate, the method further comprises:

The monitoring node receives the configuration information of the configuration node multiple times, and saves the guaranteed bit rate in the first received configuration information as the initial configured guaranteed bit rate, and the guaranteed bit in the last received configuration information. The rate is saved as the guaranteed bit rate of the current configuration.
The data transmission method according to claim 5, wherein the monitoring node reports the monitoring result to the configuration node according to the report configuration information, including:

And if the difference between the guaranteed bit rate of the current configuration and the guaranteed bit rate of the initial configuration is greater than a preset gap threshold, the monitoring node calculates according to the currently configured guaranteed bit rate and the initially configured guaranteed bit rate. And triggering a bit rate report threshold threshold for reporting the monitoring result, and when the monitored bit rate reaches the bit rate report threshold threshold, reporting the monitoring result to the configuration node according to the report configuration information.
The data transmission method according to any one of claims 1 to 6, wherein the monitoring object information comprises at least one of: a user equipment, a bearer, a logical channel, a protocol data unit session, and a quality of service stream.
The data transmission method according to claim 1, wherein the monitoring object information comprises at least one of: a bit rate of the user equipment, a bit rate of the bearer, a bit rate of the logical channel, a bit rate of the protocol data unit session, a service The bit rate of the quality stream, the total traffic of the user equipment, the total traffic carried, the total traffic of the logical channel, the total traffic of the protocol data unit session, the total traffic of the quality of service stream, and the transmission of at least one wireless access technology used by the user equipment The total traffic, the total traffic transmitted by at least one radio access technology used by the bearer, and the total traffic transmitted by the radio access technology used by the logical channel.
The data transmission method according to claim 1, wherein the report configuration information comprises at least one of the following:

Report type, report event configuration, minimum report interval, and maximum number of reports.
The data transmission method according to claim 9, wherein said report type comprises at least one of the following:

After receiving the configuration information, a single report, a periodic report, an event triggered single report, an event triggered periodic report, and a report when the bearer, the logical channel, or the user equipment is released.
The data transmission method according to claim 10, wherein when the report type includes reporting when a bearer, a logical channel, or a user equipment is released, the reporting the monitoring result to the configuration node according to the report configuration information includes:

When the bearer, the logical channel, or the user equipment is released, carrying a monitoring result in a response message corresponding to the message releasing the bearer, the logical channel, or the user equipment to report to the configuration node Monitoring results.
The data transmission method according to claim 9, wherein the report event configuration comprises at least one of: a report event type and a preset condition;

The report event type includes at least one of the following:

The measurement result of the monitoring object satisfies the preset condition;

The measurement result of the monitoring object does not satisfy the preset condition;

The measurement result of the monitoring object satisfies the preset condition and maintains a preset duration;

The measurement result of the monitoring object does not satisfy the preset condition and maintains a preset duration;

The measurement result of the monitoring object never satisfies the preset condition until the predetermined condition is met;

The measurement result of the monitoring object is from satisfying the preset condition to not meeting the preset condition;

The measurement result of the monitoring object never satisfies the preset condition until the preset condition is satisfied and the preset duration is maintained;

The measurement result of the monitoring object is from satisfying the preset condition to not satisfying the preset condition and maintaining a preset duration;

The preset condition includes at least one of the following:

The measurement result of the monitoring object is greater than, greater than or equal to, equal to, less than or less than or equal to a pre-configured threshold; and,

The measurement result of the monitoring object is greater than, greater than or equal to, equal to, less than or less than or equal to the pre-configured first threshold, and greater than, greater than or equal to, equal to, less than or less than or equal to the pre-configured second threshold.
The data transmission method according to claim 12, wherein the preset condition, the threshold, the first threshold, the second threshold, and the preset duration are configured by protocol signaling or agreed in a standard .
The data transmission method according to any one of claims 1 to 13, wherein the configuration node and the monitoring node are any one of the following:

The configuration node is a core network device, and the monitoring node is a base station.
The data transmission method according to claim 14, wherein the monitoring node receives configuration information of the configuration node, including:

The monitoring node receives configuration information of the configuration node by using a forwarding node.
The data transmission method according to claim 15, wherein said forwarding node is a source base station, and said monitoring node is a target base station.
The data transmission method according to claim 15, wherein the reporting the monitoring result to the configuration node comprises:

The monitoring result is reported to the configuration node by the forwarding node.
The data transmission method according to claim 17, wherein said forwarding node and said monitoring node are any one of the following:

The forwarding node is a primary base station, and the monitoring node is a secondary base station;

Alternatively, the forwarding node is a base station control plane, and the monitoring node is a base station user plane.
The data transmission method according to claim 1, wherein the report configuration information comprises at least one of the following: a traffic report period, a traffic report trigger threshold, and a single traffic report indication.
The data transmission method according to claim 19, wherein the monitoring result comprises: the monitoring object information and the monitored total traffic, wherein the monitored total traffic comprises at least one of the following:

The monitoring object is monitoring the total traffic of the interface between the node side and the user equipment; and,

The monitoring object monitors the total traffic of the interface between the node side and the core network.
A data transmission device includes a receiving unit and a monitoring unit, wherein

The receiving unit is configured to receive configuration information of the configuration node and output the configuration information to the monitoring unit, where the configuration information includes monitoring object information, monitoring configuration information, and report configuration information; the monitoring unit, And being configured to monitor the monitoring object corresponding to the monitoring object information according to the monitoring configuration information, and report the monitoring result to the configuration node according to the report configuration information.
A computer readable storage medium storing computer executable instructions for performing the data transmission method of any one of claims 1-20.