WO2017214871A1 - 业务数据分流方法及装置 - Google Patents

业务数据分流方法及装置 Download PDF

Info

Publication number
WO2017214871A1
WO2017214871A1 PCT/CN2016/085797 CN2016085797W WO2017214871A1 WO 2017214871 A1 WO2017214871 A1 WO 2017214871A1 CN 2016085797 W CN2016085797 W CN 2016085797W WO 2017214871 A1 WO2017214871 A1 WO 2017214871A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
amount
data amount
expected
preset
Prior art date
Application number
PCT/CN2016/085797
Other languages
English (en)
French (fr)
Inventor
闫海东
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP16904988.9A priority Critical patent/EP3462772A4/en
Priority to CN201680086579.5A priority patent/CN109314884B/zh
Priority to PCT/CN2016/085797 priority patent/WO2017214871A1/zh
Publication of WO2017214871A1 publication Critical patent/WO2017214871A1/zh
Priority to US16/220,550 priority patent/US10911985B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution
    • H04W28/086—Load balancing or load distribution among access entities
    • H04W28/0861—Load balancing or load distribution among access entities between base stations
    • H04W28/0864—Load balancing or load distribution among access entities between base stations of different hierarchy levels, e.g. Master Evolved Node B [MeNB] or Secondary Evolved node B [SeNB]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/30—Flow control; Congestion control in combination with information about buffer occupancy at either end or at transit nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0231—Traffic management, e.g. flow control or congestion control based on communication conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution
    • H04W28/09—Management thereof
    • H04W28/0925—Management thereof using policies
    • H04W28/0942—Management thereof using policies based on measured or predicted load of entities- or links
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints
    • H04W28/12—Flow control between communication endpoints using signalling between network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/20—Interfaces between hierarchically similar devices between access points
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0876—Network utilisation, e.g. volume of load or congestion level
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/28—Flow control; Congestion control in relation to timing considerations
    • H04L47/283—Flow control; Congestion control in relation to timing considerations in response to processing delays, e.g. caused by jitter or round trip time [RTT]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a service data offloading method and apparatus.
  • the 3GPP (3rd Generation Partnership Project) Release 12 standard introduces DC (Dual Connectivity) technology.
  • the dual connectivity technology means that the UE (User Equipment) can simultaneously transmit uplink and downlink service data by using the radio resources of the two base stations.
  • the UE User Equipment
  • the service data of the RLC AM Radio Link Control Acknowledged Mode
  • two base stations involved in the dual connectivity technology include a MeNB (Master eNB, a primary base station) and an SeNB (Secondary eNB, secondary base station).
  • the MeNB can directly send the service data received from the core network to the UE. , as shown by the data flow indicated by the solid arrow in Figure 1.
  • the MeNB can receive the service data from the core network, and divide the service data into two parts, part of the service data is sent by the MeNB to the UE; another part of the service data is offloaded by the MeNB to the SeNB, and the SeNB is used by the SeNB. The part of the service data is sent to the UE, as indicated by the data flow indicated by the dashed arrow in FIG.
  • the process of offloading the service data of the UE in the dual connectivity technology may be: the SeNB sends the expected traffic volume to the MeNB, where the expected traffic data volume refers to the amount of data that the SeNB needs to acquire the service data from the MeNB each time.
  • the MeNB offloads the service data received from the core network to the SeNB according to the received expected amount of offloaded data.
  • the size of the expected offloaded data is determined by each vendor according to the needs.
  • the MeNB performs offloading according to the expected offloaded data.
  • the data transmission delay varies between the two. If the expected data volume is fixed, when the SeNB side transmission rate decreases or the data transmission delay becomes small, the SeNB buffers data accumulation, and the delay increases, which in turn leads to a decrease in throughput; or When the SeNB side transmission rate increase or the data transmission delay becomes large, the SeNB cache data is insufficient, which also causes the throughput rate to decrease.
  • an embodiment of the present invention provides a service data offloading method and apparatus.
  • the technical solution is as follows:
  • a method for traffic data offloading comprising:
  • determining a data volume change state of the offload service data where the data volume change state includes a cache data amount decrease state, a cache data amount accumulation state, and a received data amount shortage state;
  • the offloaded service data can adapt to the change of the SeNB transmission rate, and the data between the MeNB and the SeNB. The change of the transmission delay and the change of the amount of service data received by the MeNB, thereby improving the throughput of the system.
  • determining a data volume change status of the offload service data includes:
  • the SeNB can increase the first expected offload data amount according to the state, so as to increase the amount of data received by the SeNB from the MeNB, thereby improving the system throughput rate.
  • determining a data volume change status of the offload service data includes:
  • the preset period is a full scheduling period, where the full scheduling period is required to be sent to the UE for each system scheduling in the preset period.
  • the amount of data is not greater than the amount of data of the cached business data
  • the SeNB can reduce the amount of the first expected offload data according to the state, so as to reduce the amount of data received by the SeNB from the MeNB, thereby reducing the transmission delay of the SeNB.
  • determining a data volume change status of the offload service data includes:
  • the SeNB can reduce the first expected offload data amount according to the state, so as to reduce the amount of data received by the SeNB from the MeNB, thereby improving the system throughput rate.
  • the first expected offload data volume is adjusted according to the data volume change state, and the second expected split data volume is obtained by:
  • the data amount change state is the cache data amount decrease state, adding a first preset adjustment value to obtain the second expected split data amount on the basis of the first expected split data amount;
  • the data volume change state is the cached data amount accumulation state, reducing a second preset adjustment value to obtain the second desired split data amount based on the first expected split data amount;
  • the third preset adjustment value is decreased on the basis of the first expected split data amount, and the second expected split data amount is obtained.
  • the amount of the desired offload data is adjusted according to different data volume change states, so that the offloaded service data can adapt to the change of the SeNB transmission rate, the change of the data transmission delay between the MeNB and the SeNB, and the amount of the service data received by the MeNB. Changes, which in turn increase the throughput of the system.
  • the method before the first preset adjustment value is added, the method also includes:
  • the data amount change state is the cache data amount decrease state, determining whether the first expected split data amount is smaller than a maximum split data amount
  • the first expected shunt data amount is not less than the maximum shunt data amount
  • the first desired shunt data amount is not adjusted.
  • the amount of the desired traffic is adjusted within a certain range according to different data volume change states, so that the traffic data of the offload can adapt to the change of the transmission rate of the SeNB and the data transmission between the MeNB and the SeNB while satisfying the system data transmission capability.
  • the method before the second preset adjustment value is reduced, the method also includes:
  • the data volume change state is the cache data amount accumulation state, determining whether the first expected split data amount is greater than a minimum split data amount
  • the first expected split data amount is greater than the minimum split data amount, performing a step of reducing the second preset adjustment value based on the first expected split data amount;
  • the first expected shunt data amount is not greater than the minimum shunt data amount
  • the first desired shunt data amount is not adjusted.
  • the amount of the desired traffic is adjusted within a certain range according to different data volume change states, so that the traffic data of the offload can adapt to the change of the transmission rate of the SeNB and the data transmission between the MeNB and the SeNB while satisfying the system data transmission capability.
  • the method before the third preset adjustment value is reduced, the method also includes:
  • the data amount change state is the received data amount insufficient state, determining the first period Whether the amount of split data is greater than the minimum amount of split data;
  • the first expected shunt data amount is not greater than the minimum shunt data amount
  • the first desired shunt data amount is not adjusted.
  • the amount of the desired traffic is adjusted within a certain range according to different data volume change states, so that the traffic data of the offload can adapt to the change of the transmission rate of the SeNB and the data transmission between the MeNB and the SeNB while satisfying the system data transmission capability.
  • a service data distribution device comprising a plurality of functional modules for performing the method of the first aspect described above.
  • the apparatus further includes other functional modules for performing the methods described in the various possible implementations of the first aspect described above.
  • a base station including: a receiver, a transmitter, a memory, and a processor,
  • the receiver, the transmitter, and the memory are respectively coupled to the processor, the memory is configured to store executable instructions of the processor, and the processor is configured to:
  • the offloaded service data is the service data that is divided by the MeNB according to the first expected offloaded data volume; when the preset period is reached, the offloaded service data is determined.
  • a data amount change state wherein the data amount change state is a cache data amount decrease state, a cache data amount accumulation state, and a received data amount insufficient state; and the first desired split data amount is adjusted according to the data amount change state And obtaining a second expected offload data volume; sending the second expected offload data volume to the MeNB, where the MeNB performs offloading according to the second expected offload data volume.
  • the amount of the desired traffic is adjusted within a certain range according to different data volume change states, so that the traffic data of the offload can adapt to the change of the transmission rate of the SeNB and the data transmission between the MeNB and the SeNB while satisfying the system data transmission capability.
  • the change of the delay and the change of the amount of service data received by the MeNB thereby improving the throughput of the system.
  • the offloaded service data can adapt to the change of the SeNB transmission rate, and the data between the MeNB and the SeNB.
  • the change in transmission delay increases the throughput of the system.
  • FIG. 1 is a schematic diagram of service data splitting in a dual connectivity technology according to an embodiment of the present invention
  • 2A is a system architecture diagram for traffic data offloading according to an embodiment of the present invention.
  • 2B is a message format diagram of a specified message carrying a desired amount of split data according to an embodiment of the present invention
  • 2C is a user plane protocol stack of a MeNB and a NeNB according to an embodiment of the present invention
  • 3A is a flowchart of a service data offloading method according to an embodiment of the present invention.
  • FIG. 3B is a flowchart of determining whether a data amount change state is a cache data amount reduction state according to an embodiment of the present invention
  • FIG. 3C is a flowchart of determining whether a data volume change state is a buffered data amount accumulation state according to an embodiment of the present invention
  • FIG. 3D is a flowchart of determining whether a data volume change state is a state in which a received data amount is insufficient according to an embodiment of the present invention
  • FIG. 3E is a block diagram of an SeNB adjusting an expected amount of split data according to an embodiment of the present invention.
  • FIG. 4 is a block diagram of a service data offloading apparatus according to an embodiment of the present invention.
  • FIG. 5 is a schematic structural diagram of a base station according to an embodiment of the present invention.
  • FIG. 2A is a schematic diagram of a system architecture for service data offloading according to an embodiment of the present invention. 2A, including a core network, a MeNB, a SeNB, and a UE.
  • the MeNB is configured to receive service data from the core network. If the service data is service data that cannot be offloaded, such as RLC UM mode service data, the service data is directly sent to the UE. If the service data is service data that can be offloaded, such as RLC AM mode service data, the service data is split into two parts, part of the service data is sent by the MeNB to the UE; and another part of the service data is offloaded by the MeNB to the SeNB. The SeNB sends the part of the service data to the UE.
  • service data is service data that cannot be offloaded, such as RLC UM mode service data
  • RLC AM mode service data service data that can be offloaded
  • the SeNB sends the part of the service data to the UE.
  • the process of the MeNB offloading to the SeNB may be: the SeNB periodically sends the expected amount of offloaded data to the MeNB.
  • the MeNB offloads the service data received from the core network to the SeNB according to the received expected amount of offloaded data.
  • the expected amount of offloaded data may be periodically sent by the SeNB to the MeNB according to a preset transmission period.
  • the preset transmission period may be preset or modified by the system, which is not specifically limited in the embodiment of the present invention.
  • the initial value of the expected offloaded data volume may be preset according to the data transmission capability of the SeNB, which is not specifically limited in this embodiment of the present invention.
  • the expected amount of the offloaded data may be continuously adjusted by the SeNB according to the state of the data volume change, so that the offloaded service data can adapt to the change of the SeNB transmission rate, the change of the data transmission delay between the MeNB and the SeNB, and the service data received by the MeNB.
  • the amount of change which in turn increases the throughput of the system, is detailed in the embodiment shown in Figure 3A.
  • the amount of offloaded data can be carried in the specified message and sent to the MeNB.
  • the expected amount of offloaded data is one field in the specified message.
  • the specified message may be a DL DATA DELIVERY STATUS message or other message, and the message format of the specified message may be as shown in FIG. 2B.
  • the expected amount of offloaded data may be a Desired Buffer Size field in the specified message. As shown in FIG. 2B, the Desired Buffer Size field may be 4 bytes in length.
  • the specified message format further includes a Highest Successfully delivered PDCP Sequence Number field, which is used to indicate a maximum sequence number of the PDCP data packet successfully sent by the SeNB to the UE, and a Minimum desired buffer size for the UE field, which is used to indicate that the UE is in the dual connectivity.
  • the MeNB offloads the received service data at the PDCP layer.
  • 2C is a user plane protocol stack of the MeNB and the NeNB.
  • the MeNB includes a PDCP (Packet Data Convergence Protocol) layer, an RLC layer, and a MAC (Media Access). Control, media access control) layer.
  • the SeNB includes an RLC layer and a MAC layer.
  • the MeNB packs the service data into a PDCP PDU (PDCP Protocol Data Unit) packet through the PDCP layer.
  • the PDCP PDU packet is then shunted according to the desired amount of traffic split.
  • the PDCP PDU data packet that is offloaded to the SeNB is processed by the RLC layer and the MAC layer in the SeNB, and then transmitted to the UE.
  • the PDCP PDU data packet remaining in the MeNB is processed by the RLC layer and the MAC layer in the MeNB, and then transmitted to the UE.
  • FIG. 3A is a flowchart of a service data offloading method according to an embodiment of the present invention, which is applied to an SeNB.
  • the method process provided by the embodiment of the present invention includes:
  • the 301 Receive the offloaded service data sent by the MeNB, and cache the offloaded service data, where the offloaded service data refers to service data that is offloaded by the MeNB according to the first expected offloaded data volume.
  • the SeNB sends the first expected offload data volume to the MeNB before receiving the offloaded service data.
  • the first expected offload data amount is used to indicate the amount of data that the MeNB sends the service data to the SeNB each time.
  • the MeNB After receiving the first expected offload data volume, the MeNB performs traffic data offloading to the SeNB according to the first expected data amount.
  • the SeNB After the traffic data is buffered, the SeNB sends the buffered traffic data to the UE at a certain transmission rate according to the system scheduling.
  • the transmission rate is not necessarily fixed and may be affected by factors such as the network environment.
  • determining a data volume change state of the offload service data where the data volume change state includes a cache data amount reduction state, a cache data amount accumulation state, and a received data volume shortage state.
  • the SeNB in order to prevent the SeNB from degrading the system throughput due to buffered data accumulation or insufficient cache data, the SeNB monitors the buffered data volume of the offloaded service data, thereby determining whether the data volume change state is a cache data amount reduction. Status or cached data volume accumulation status.
  • the process of determining whether the data volume change state is the cache data volume decrease state may be as shown in FIG. 3B, and includes the following steps:
  • Step 1 When the preset period is reached, it is determined whether the data amount of the buffered offload service data is less than a first preset threshold.
  • Step 2 If the data volume of the buffered traffic data is less than the first preset threshold, determine that the data volume change state is a cache data volume reduction state.
  • Step 3 If the data volume of the buffered traffic data is not less than the first preset threshold, determine The data amount change state is not the cache data amount reduction state.
  • the first preset threshold may be preset according to the data transmission capability of the SeNB, or may be pre-configured or modified according to the service requirement, which is not specifically limited in this embodiment of the present invention.
  • the reason for the decrease in the amount of data cached by the SeNB may be as follows:
  • the data transmission delay between the MeNB and the SeNB is unchanged, and the transmission rate of the service data sent by the SeNB to the UE is increased, so that the amount of data received by the SeNB from the MeNB is within a certain period of time.
  • the amount of data sent to the UE increases, resulting in a reduction in the amount of data buffered.
  • the amount of service data received by the MeNB is unchanged, the transmission rate of the SeNB is unchanged, and the data transmission delay between the MeNB and the SeNB becomes large, so that the amount of data sent by the SeNB to the UE does not change for a period of time.
  • the amount of data received by the MeNB is reduced, resulting in a reduction in the amount of data buffered.
  • the process of determining whether the data volume change status is the cache data amount accumulation state may be as shown in FIG. 3C, and includes the following steps:
  • Step 1 When the preset period is reached, it is determined whether the data amount of the buffered offload service data is greater than the amount of data buffered when the preset period is reached.
  • the SeNB each time the preset period is reached, the SeNB records the amount of data of the buffered offloaded service data. Specifically, a correspondence relationship between each preset period and the amount of data of the buffered offload service data may be established.
  • Step 2 If the data volume of the buffered traffic data is greater than the amount of data cached when the preset time is reached, determine whether the data volume of the buffered traffic data is greater than a second preset threshold.
  • the second preset threshold may be preset according to the data transmission capability of the SeNB, or may be pre-configured or modified according to the service requirement, which is not specifically limited in this embodiment of the present invention.
  • the second preset threshold is greater than the first preset threshold.
  • the data volume of the buffered traffic data is not greater than the amount of data cached when the preset period is reached, it is determined that the data volume change state is not the cache data volume accumulation state.
  • Step 3 If the data volume of the buffered traffic data is greater than the second preset threshold, determine whether the preset period is a full scheduling period, where the full scheduling period refers to whether the data volume of the service data buffered in the preset period is not less than The maximum amount of data indicated by the secondary downlink scheduling.
  • the SeNB sends the service data to the UE in the time slot indicated by the downlink scheduling. For example, the SeNB needs to send the service data to the UE within one TTI (Transmission Time Interval).
  • TTI Transmission Time Interval
  • the MAC layer of the SeNB is based on the UE.
  • the maximum amount of data that can be sent to the UE is calculated based on the location, the quality of the data link, and the quality of the air interface. If the amount of data to be cached is not less than the maximum amount of data, the service data of the maximum amount of data is obtained from the cached service data, and the service data of the maximum amount of data is sent to the UE.
  • the maximum amount of data indicated by each downlink scheduling may be the same or different, and is determined by the calculation manner of the MAC layer and the actual calculation data, which is not specifically limited in this embodiment of the present invention.
  • the number of times the SeNB sends the service data to the UE in the preset period is not necessarily fixed, that is, the number of downlink scheduling in the preset period is not necessarily fixed.
  • the SeNB may send multiple service data to the UE.
  • the SeNB determines whether the data volume of the buffered service data is not less than the maximum data amount indicated by the downlink scheduling, and The judgment result is recorded. If the data volume of the cached service data is not less than the maximum data amount indicated by the downlink scheduling, the preset period is determined to be a full scheduling period.
  • Step 4 If the preset period is a full scheduling period, and the preset period of the first preset number is a full scheduling period, the data volume change state is determined to be a buffered data amount accumulation state.
  • the first preset number may be preset or modified according to actual service requirements, which is not specifically limited in this embodiment of the present invention.
  • the SeNB may record whether each preset period is a full scheduling period. If the preset period is a full scheduling period, it is determined whether there is a first preset number of preset periods including the preset period. For a full scheduling period. If so, it is determined that the data amount change state at this time is the cache data amount accumulation state. For example, the first preset number is 3, and the preset period is a full scheduling period. When two preset periods before the preset period are full scheduling periods, determining the data volume change state is buffered data accumulation. status.
  • the data transmission delay between the MeNB and the SeNB is unchanged, and the transmission rate of the service data sent by the SeNB to the UE is decreased, so that the amount of data received by the SeNB from the MeNB is within a certain period of time. No change, but the amount of data sent to the UE is reduced, resulting in caching The amount of data is stacked.
  • the amount of service data received by the MeNB is unchanged, the transmission rate of the SeNB is unchanged, and the data transmission delay between the MeNB and the SeNB is small, so that the amount of data sent by the SeNB to the UE does not change for a period of time.
  • the amount of data received by the MeNB increases, resulting in a stack of cached data.
  • the preset period is not the full scheduling period, it is determined that the data volume change state is not the cache data amount accumulation state; or, if the preset period is the full scheduling period, but the preset period does not exist continuously first If the preset number of preset periods are all full scheduling periods, it is determined that the data amount change state is not the cache data amount accumulation state.
  • the amount of service data received by the MeNB from the core network is not necessarily fixed each time, when the amount of service data received by the MeNB decreases, the amount of data of the service data that the MeNB branches to the SeNB may not satisfy the first expected offload.
  • the amount of data is such that the amount of service data received by the SeNB is smaller than the amount of the first expected offloaded data, thereby affecting the system throughput rate.
  • the SeNB In order to prevent the system throughput from decreasing due to insufficient received service data, the SeNB also monitors the data volume of each received traffic data, and then determines whether the data volume change state is a received data shortage state, and the determination process As shown in FIG. 3D, the following steps are included:
  • Step 1 When the preset period is reached, it is determined whether the data amount of the shunt service data received each time in the preset period is less than the first expected stream size.
  • the preset sending period in which the SeNB sends the desired amount of the split data to the MeNB may be the same as the preset period, or may be different.
  • the preset sending period may be less than the preset period, which is not specifically limited in this embodiment of the present invention. If the preset period is the same as the preset sending period, the SeNB receives the number of offloaded services once in the preset period. If not, the SeNB can receive the multiple offloaded data service within the preset period. After receiving the offloaded service data, the SeNB determines whether the received offloaded service data is smaller than the first expected split data amount, and records the judgment result.
  • the SeNB when the SeNB receives the number of the offloaded services in the preset period, it only needs to determine whether the offloaded service data received in the preset period is smaller than the first expected offloaded data amount.
  • Step 2 If yes, determine that the preset period is a period of insufficient reception.
  • the preset period is the insufficient amount of reception period. If the amount of data of the offloaded service data received in each of the preset periods is equal to the amount of the first desired offloaded data, it is determined that the amount of the offloaded service data received in the preset period is sufficient.
  • the SeNB in order to increase the flexibility of adjusting the amount of data required to be offloaded, The flexibility of the service data offloading is increased.
  • the SeNB can receive multiple times of splitting data services within a preset period, the ratio of the number of received service data is smaller than the first expected stream of data to the total number of received times.
  • the percentage is preset, it is determined that the preset period is a period of insufficient reception. For example, the preset percentage is 60%, and the shunt service data is received 4 times in the preset period, wherein the received service data amount is less than the first expected shunt data, and the received service data amount is smaller than the first.
  • the ratio of the number of times of splitting the data volume to the total number of received times is 75%, which is greater than 60%, and it is determined that the preset period is a period of insufficient receiving amount.
  • the preset percentage may be preset or modified, which is not specifically limited in the embodiment of the present invention.
  • Step 3 If the preset period is the period of insufficient reception, and the preset period of the second preset number is the period of insufficient reception, the data quantity change state is determined to be the received data insufficient state. .
  • the second preset number may be preset or modified according to actual service requirements, which is not specifically limited in this embodiment of the present invention.
  • the SeNB may record whether each preset period is a period of insufficient reception amount. If the preset period is a period of insufficient reception, it is determined whether there is a second preset number of presets including the preset period. The periods are all periods of insufficient reception. If so, it is determined that the data amount change state at this time is the received data amount insufficient state. For example, the second preset number is 3, and the preset period is the insufficient amount of receiving period. If two preset periods before the preset period are the insufficient receiving period, the data amount change state is determined to be the receiving data. Insufficient state.
  • the preset period is not the insufficient amount of receiving period, it is determined that the data amount change state is not the received data amount insufficient state; or, if the preset period is the received amount insufficient period, but there is no continuous period including the preset period
  • the second preset number of preset periods are all the under-receiving periods, and it is determined that the data amount change state is not the received data amount insufficient state.
  • the embodiment of the present invention provides a block diagram for adjusting the amount of data required by the SeNB. As shown in FIG. 3E, the SeNB changes the state according to the data amount to the first.
  • the process of adjusting the amount of data to be shunted can be as follows:
  • the first preset adjustment value is added on the basis of the first expected split data amount to obtain the second desired split data amount.
  • the second preset adjustment value is decreased on the basis of the first expected split data amount to obtain the second desired split data amount.
  • the first expected offload data volume is reduced, so as to reduce the amount of data received by the subsequent SeNB from the MeNB, thereby reducing the transmission delay of the SeNB.
  • the third preset adjustment value is decreased on the basis of the first expected split data amount, and the second desired split data amount is obtained.
  • the first preset adjustment value, the second preset adjustment value, and the third preset adjustment value may be equal or not equal, which is not specifically limited in the embodiment of the present invention.
  • the first preset adjustment value, the second preset adjustment value, and the third preset adjustment value may be preset and modified by the system, which is not specifically limited in the embodiment of the present invention.
  • the SeNB may perform the required split data amount according to the maximum split data amount and the minimum split data amount. Adjustment.
  • the maximum amount of the split data and the minimum amount of the split data may be preset or modified by the system according to the service requirement or the data transmission capability, which is not specifically limited in this embodiment of the present invention.
  • the SeNB adjusts the first expected split data volume according to the maximum split data volume and the minimum split data volume, including the following situations:
  • the data amount change state is the cache data amount decrease state
  • the data volume change state is the cache data amount accumulation state
  • the step of reducing the second preset adjustment value is performed on the basis of the expected amount of the offloaded data; if the first expected shunt data amount is not greater than the minimum shunt data amount, the first expected shunt data amount is not adjusted.
  • the data amount change state is the received data amount insufficient state, it is determined whether the first expected split data amount is greater than the minimum split data amount; if the first desired split data amount is greater than the minimum score Flow data amount, performing a step of reducing a third preset adjustment value based on the first expected split data amount; if the first desired split data amount is not greater than the minimum split data amount, not performing the first desired split data amount Adjustment.
  • the second expected offload data volume is sent to the MeNB, and the MeNB performs offloading according to the second expected offload data volume.
  • the SeNB may send the obtained second expected offload data volume to the MeNB when the preset period is reached, that is, the SeNB may send the expected offload data volume to the MeNB according to a preset period.
  • the period in which the SeNB sends the expected amount of the offloaded data to the MeNB may be different from the preset period, which is not specifically limited in this embodiment of the present invention.
  • the MeNB After receiving the second expected offload data volume, the MeNB performs offload according to the second offloaded data volume, and sends the offloaded service data to the SeNB.
  • the method provided by the embodiment of the present invention can be applied to a traffic distribution scenario of an LTE system, and can also be applied to a traffic distribution scenario of other communication systems, such as a traffic distribution scenario of LTE and WiFi (Wireless Fidelity).
  • the embodiment of the present invention does not specifically limit this.
  • the method provided by the embodiment of the present invention adjusts the data volume change state of the traffic off service data periodically, and adjusts the expected traffic volume according to different data volume change states, so that the offloaded service data can adapt to the SeNB transmission rate.
  • the SeNB is in the buffered data amount accumulation state, the first expected offload data volume is reduced, so as to reduce the amount of data received by the subsequent SeNB from the MeNB, thereby reducing the transmission delay of the SeNB.
  • the apparatus includes: a receiving module 401, a cache module 402, a determining module 403, an adjusting module 404, and a sending module 405.
  • the receiving module 401 is connected to the cache module 402, and is configured to receive the offloaded service data sent by the MeNB, where the offloaded service data refers to the service data that is offloaded by the MeNB according to the first expected offloaded data volume;
  • the cache module 402 is connected to the determining module 403, where Cache the traffic data;
  • the determining module 403 is connected to the adjusting module 404, and is configured to determine a data volume change state of the traffic data when the preset period is reached, where the data volume change state includes a buffer data volume reduction state, a cache data volume accumulation state, and
  • the receiving module 404 is connected to the sending module 405, and is configured to adjust the first expected shunt data amount according to the data volume change state to obtain a second expected shunt data amount; and send module 405, And configured to send the second expected offload data volume to the MeNB, where the MeNB performs offload according to the second expected offload data volume.
  • the determining module 403 is configured to determine, when the preset period is reached, that the data amount change state is a cache data amount decrease state, if the data amount of the buffered offload service data is less than the first preset threshold.
  • the determining module 403 is configured to determine, when the preset period is reached, whether the amount of data of the buffered offloaded service data is greater than the amount of data that is cached when the preset period is reached; if the amount of data of the buffered offloaded service data is greater than If the amount of data buffered in the preset period is reached, it is determined whether the data volume of the buffered traffic data is greater than a second preset threshold; if the data volume of the buffered traffic data is greater than the second preset threshold, the preset period is determined.
  • the full scheduling period refers to whether the data amount of the service data buffered in the preset period is not less than the maximum amount of data indicated by each downlink scheduling; if the preset period is a full scheduling period, and includes a preset period
  • the first preset number of preset periods are all full scheduling periods, and the data amount change state is determined to be a buffered data amount accumulation state.
  • the determining module 403 is configured to determine, when the preset period is reached, whether the data amount of the shunt service data received each time in the preset period is less than the first expected stream of split data; if yes, determine the preset period. If the preset period is the under-receiving period, and the preset period is the second preset number of preset periods, the data amount change status is the received data. Insufficient state.
  • the adjusting module 404 is configured to: if the data volume change state is a cache data amount decrease state, add a first preset adjustment value on the basis of the first expected split data amount, to obtain a second expected split data amount; If the data volume change state is the cache data amount accumulation state, or the data volume change state is the received data amount shortage state, the second preset adjustment value is decreased based on the first desired split data amount, and the second desired split data amount is obtained. .
  • the adjusting module 404 is further configured to: if the data volume change status is a cache data amount decrease state, determine whether the first expected split data amount is less than a maximum split data amount; if the first expected split data amount is less than the maximum split data amount, Then, the step of increasing the first preset adjustment value is performed on the basis of the first expected shunt data amount; if the first expected shunt data amount is not less than the maximum shunt data amount, the first expected shunt data amount is not adjusted.
  • the adjusting module 404 is further configured to: if the data volume change state is a cache data amount accumulation state, or the data amount change state is a received data volume shortage state, determine whether the first expected split data amount is greater than a minimum split data amount; If the first expected split data amount is greater than the minimum split data amount, performing the step of reducing the second preset adjustment value based on the first expected split data amount; if the first desired score If the amount of stream data is not greater than the minimum amount of split data, the amount of the first desired split data is not adjusted.
  • the device provided by the embodiment of the present invention periodically determines the data volume change state of the traffic split data, and adjusts the expected traffic volume according to different data volume change states, so that the offloaded service data can adapt to the SeNB transmission rate. Changes, changes in data transmission delay between the MeNB and the SeNB, improve system throughput.
  • the data transmission device provided by the foregoing embodiment performs service data offloading
  • only the division of the foregoing functional modules is illustrated.
  • the function distribution may be completed by different functional modules as needed.
  • the internal structure of the device is divided into different functional modules to perform all or part of the functions described above.
  • the service data offloading device and the service data offloading method are provided in the same embodiment. The specific implementation process is described in detail in the method embodiment, and details are not described herein again.
  • FIG. 5 is a schematic structural diagram of a base station according to an embodiment of the present invention.
  • the receiver 501, the transmitter 502, the memory 503, and the processor 504, the receiver 501, the transmitter 502, and the memory 503 are provided.
  • the memory 503 is configured to store executable instructions of the processor, and the processor 504 is configured to:
  • the offloaded service data refers to the service data that is split by the MeNB according to the first expected split data volume
  • the data amount change state is a cache data amount decrease state, a cache data amount accumulation state, and a received data amount insufficient state
  • the first desired split data amount is adjusted to obtain a second desired split data amount
  • It is desirable that the amount of offloaded data is transmitted to the MeNB, and the MeNB performs offloading according to the second expected offloaded data amount.
  • determining a data volume change status of the offload service data includes:
  • the SeNB can increase the first expected offload data amount according to the state, so as to increase the amount of data received by the SeNB from the MeNB, thereby improving the system throughput rate.
  • determining a data volume change status of the offload service data includes:
  • the preset period is a full scheduling period, and the full scheduling period refers to the amount of data that is sent to the UE for each system scheduling in the preset period.
  • the amount of data larger than the cached business data
  • the data amount change state is determined to be a buffered data amount accumulation state.
  • the SeNB can reduce the amount of the first expected offload data according to the state, so as to reduce the amount of data received by the SeNB from the MeNB, thereby reducing the transmission delay of the SeNB.
  • determining a data volume change status of the offload service data includes:
  • the data amount change state is determined to be the received data amount insufficient state.
  • the SeNB can reduce the first expected offload data amount according to the state, so as to reduce the amount of data received by the SeNB from the MeNB, thereby improving the system throughput rate.
  • adjusting the first expected offload data volume according to the data volume change state, and obtaining the second expected split data volume includes:
  • the first preset adjustment value is added to obtain the second expected split data amount on the basis of the first expected split data amount
  • the data volume change state is the buffered data amount accumulation state, reducing the second preset adjustment value to obtain the second desired split data amount on the basis of the first expected split data amount;
  • the third preset adjustment value is decreased on the basis of the first desired split data amount to obtain the second desired split data amount.
  • the amount of the desired offload data is adjusted according to different data volume change states, so that the offloaded service data can adapt to the change of the SeNB transmission rate, the change of the data transmission delay between the MeNB and the SeNB, and the amount of the service data received by the MeNB. Changes, which in turn increase the throughput of the system.
  • the method further includes:
  • the data amount change state is the cache data amount decrease state, determining whether the first expected split data amount is smaller than the maximum split data amount
  • the first expected shunt data amount is less than the maximum shunt data amount, performing a step of increasing the first preset adjustment value on the basis of the expected shunt data amount;
  • the first expected shunt data amount is not less than the maximum shunt data amount
  • the first desired shunt data amount is not adjusted.
  • the amount of the desired traffic is adjusted within a certain range according to different data volume change states, so that the traffic data of the offload can adapt to the change of the transmission rate of the SeNB and the data transmission between the MeNB and the SeNB while satisfying the system data transmission capability.
  • the method further includes:
  • the data volume change state is the cache data amount accumulation state, determining whether the first expected split data amount is greater than the minimum split data amount
  • the first expected shunt data amount is not greater than the minimum shunt data amount
  • the first desired shunt data amount is not adjusted.
  • the amount of the desired traffic is adjusted within a certain range according to different data volume change states, so that the traffic data of the offload can adapt to the change of the transmission rate of the SeNB and the data transmission between the MeNB and the SeNB while satisfying the system data transmission capability.
  • the method further includes:
  • the data volume change state is the received data amount insufficient state, determining whether the first expected split data amount is greater than the minimum split data amount;
  • the first expected shunt data amount is not greater than the minimum shunt data amount
  • the first desired shunt data amount is not adjusted.
  • the amount of the desired traffic is adjusted within a certain range according to different data volume change states, so that the traffic data of the offload can adapt to the change of the transmission rate of the SeNB and the data transmission between the MeNB and the SeNB while satisfying the system data transmission capability.
  • the base station provided by the embodiment of the present invention periodically determines the data volume change status of the offload service data, and adjusts the expected split data volume according to different data volume change states, so that the offloaded service data can adapt to the SeNB transmission rate. Changes, changes in data transmission delay between the MeNB and the SeNB, improve system throughput.
  • a person skilled in the art may understand that all or part of the steps of implementing the above embodiments may be completed by hardware, or may be instructed by a program to execute related hardware, and the program may be stored in a computer readable storage medium.
  • the storage medium mentioned may be a read only memory, a magnetic disk or an optical disk or the like.

Abstract

本发明实施例提供了一种业务数据分流方法及装置，涉及通信技术领域，方法包括：接收MeNB根据第一期望分流数据量发送的分流业务数据，缓存分流业务数据；当到达预设周期时，确定分流业务数据的数据量变化状态，数据量变化状态为缓存数据量减少状态、缓存数据量堆积状态和接收数据量不足状态；根据数据量变化状态，对第一期望分流数据量进行调整，得到第二期望分流数据量；将第二期望分流数据量发送至MeNB，由MeNB根据第二期望分流数据量进行分流。通过周期性的确定根据不同的数据量变化状态，对期望分流数据量进行调整，使得分流的业务数据能够适应SeNB发送速率的变化、MeNB与SeNB之间数据传输时延的变化，提高了系统吞吐率。

Description

业务数据分流方法及装置 技术领域
本发明涉及通信技术领域，特别涉及一种业务数据分流方法及装置。
背景技术
随着通信技术的发展，3GPP(3rd Generation Partnership Project，第三代合作伙伴计划)Release 12标准引入了DC(Dual Connectivity，双连接)技术。双连接技术是指UE(User Equipment，用户设备)可以同时利用两个基站的无线资源传输上下行业务数据。在利用两个基站传输UE的下行业务数据时，涉及到业务数据的分流。3GPP Release 12标准中规定了可以进行分流的业务数据为RLC AM(Radio Link Control Acknowledged Mode，无线链路层控制协议确认模式)的业务数据。如图1所示，双连接技术中涉及的两个基站包括MeNB(Master eNB，主基站)和SeNB(Secondary eNB，辅基站)。对于标准规定的不可进行分流的业务数据，如RLC UM(Radio Link Control Unacknowledged Mode，无线链路层控制协议非确认模式)的业务数据，可由MeNB直接将从核心网接收到的业务数据发送至UE，如图1中实线箭头所指示的数据流所示。对于标准规定的可以进行分流的业务数据，可由MeNB从核心网接收业务数据，并将该业务数据分成两部分，一部分业务数据由MeNB发送至UE；另一部分业务数据由MeNB分流至SeNB，由SeNB将该部分业务数据发送至UE，如图1中虚线箭头所指示的数据流所示。
目前，双连接技术中对UE的业务数据进行分流的过程可以为：SeNB向MeNB发送期望分流数据量，该期望分流数据量是指SeNB每次期望从MeNB获取业务数据的数据量。MeNB根据接收到的期望分流数据量，将从核心网接收到的业务数据分流至SeNB。其中，期望分流数据量的大小由各厂商根据需要自行确定，当期望分流数据量确定后，MeNB便会按照该期望分流数据进行分流。
在实现本发明的过程中，发明人发现现有技术至少存在以下问题：
由于在业务数据分流的过程中，SeNB的发送速率以及MeNB与SeNB之 间的数据传输时延均会发生变化，如果期望数据量固定，则当SeNB侧发送速率下降或数据传输时延变小时，会造成SeNB缓存数据堆积，时延增加，进而导致吞吐率下降；或者，当SeNB侧发送速率提升或数据传输时延变大时，会造成SeNB缓存数据不足，同样导致吞吐率下降。
发明内容
为了解决现有技术的问题，本发明实施例提供了一种业务数据分流方法及装置。所述技术方案如下：
第一方面，提供了一种业务数据分流方法，所述方法包括：
接收主基站MeNB发送的分流业务数据，缓存所述分流业务数据，所述分流业务数据是指所述MeNB根据第一期望分流数据量分流的业务数据；
当到达预设周期时，确定分流业务数据的数据量变化状态，所述数据量变化状态包括缓存数据量减少状态、缓存数据量堆积状态和接收数据量不足状态；
根据所述数据量变化状态，对所述第一期望分流数据量进行调整，得到第二期望分流数据量；
将所述第二期望分流数据量发送至所述MeNB，由所述MeNB根据所述第二期望分流数据量进行分流。通过周期性的确定分流业务数据的数据量变化状态，并根据不同的数据量变化状态，对期望分流数据量进行调整，使得分流的业务数据能够适应SeNB发送速率的变化、MeNB与SeNB之间数据传输时延的变化以及MeNB接收到的业务数据量的变化，进而提高系统的吞吐率。
结合第一方面，在第一方面的第一种可能的实现方式中，当到达预设周期时，确定分流业务数据的数据量变化状态包括：
当到达所述预设周期时，如果缓存的分流业务数据的数据量小于第一预设阈值，则确定所述数据量变化状态为所述缓存数据量减少状态。通过确定数据量变化状态为数据量减少状态，使得SeNB可以根据该状态，增加第一期望分流数据量，以便提高后续SeNB从MeNB接收的数据量，进而提高系统吞吐率。
结合第一方面，在第一方面的第二种可能的实现方式中，当到达预设周期时，确定分流业务数据的数据量变化状态包括：
当到达所述预设周期时，判断缓存的分流业务数据的数据量是否大于上一次到达预设周期时缓存的数据量；
如果缓存的分流业务数据的数据量大于上一次到达预设周期时缓存的数据量，则判断缓存的分流业务数据的数据量是否大于第二预设阈值；
如果缓存的分流业务数据的数据量大于第二预设阈值，则判断所述预设周期是否为满调度周期，满调度周期是指预设周期内每次系统调度所需向所述UE发送的数据量均不大于缓存的业务数据的数据量；
如果所述预设周期为满调度周期，且包括所述预设周期在内连续有第一预设数目的预设周期均为满调度周期，则确定数据量变化状态为所述缓存数据量堆积状态。通过确定数据量变化状态为数据量堆积状态，使得SeNB可以根据该状态，减少第一期望分流数据量，以便减少后续SeNB从MeNB接收的数据量，进而降低了SeNB的传输时延。
结合第一方面，在第一方面的第三种可能的实现方式中，当到达预设周期时，确定分流业务数据的数据量变化状态包括：
当到达预设周期时，判断所述预设周期内每次接收到的分流业务数据的数据量是否均小于所述第一期望分流数据量；
如果是，则确定所述预设周期为接收量不足周期；
如果所述预设周期为接收量不足周期，且包括所述预设周期在内连续有第二预设数目的预设周期均为接收量不足周期，则确定数据量变化状态为所述接收数据量不足状态。通过确定数据量变化状态为接收数据量不足状态，使得SeNB可以根据该状态，减少第一期望分流数据量，以便减少后续SeNB从MeNB接收的数据量，进而提高系统吞吐率。
结合第一方面，在第一方面的第四种可能的实现方式中，根据所述数据量变化状态，对所述第一期望分流数据量进行调整，得到第二期望分流数据量包括：
如果所述数据量变化状态为所述缓存数据量减少状态，则在所述第一期望分流数据量的基础上，增加第一预设调整值，得到所述第二期望分流数据量；或，
如果所述数据量变化状态为所述缓存数据量堆积状态，则在所述第一期望分流数据量的基础上，减少第二预设调整值，得到所述第二期望分流数据量；或，
如果所述数据量变化状态为所述接收数据量不足状态，则在所述第一期望分流数据量的基础上，减少第三预设调整值，得到所述第二期望分流数据量。 通过根据不同的数据量变化状态，对期望分流数据量进行调整，使得分流的业务数据能够适应SeNB发送速率的变化、MeNB与SeNB之间数据传输时延的变化以及MeNB接收到的业务数据量的变化，进而提高系统的吞吐率。
结合第一方面的第四种可能的实现方式，在第一方面的第五种可能的实现方式中，在所述第一期望分流数据量的基础上，增加第一预设调整值之前，所述方法还包括：
如果所述数据量变化状态为所述缓存数据量减少状态，则判断所述第一期望分流数据量是否小于最大分流数据量；
如果所述第一期望分流数据量小于所述最大分流数据量，则执行在所述期望分流数据量的基础上，增加第一预设调整值的步骤；
如果所述第一期望分流数据量不小于所述最大分流数据量，则不对所述第一期望分流数据量进行调整。通过根据不同的数据量变化状态，对期望分流数据量在一定范围内进行调整，使得分流的业务数据在满足系统数据传输能力的同时，能够适应SeNB发送速率的变化、MeNB与SeNB之间数据传输时延的变化以及MeNB接收到的业务数据量的变化，进而提高系统的吞吐率。
结合第一方面的第四种可能的实现方式，在第一方面的第六种可能的实现方式中，在所述第一期望分流数据量的基础上，减少第二预设调整值之前，所述方法还包括：
如果所述数据量变化状态为所述缓存数据量堆积状态，则判断所述第一期望分流数据量是否大于最小分流数据量；
如果所述第一期望分流数据量大于所述最小分流数据量，则执行在所述第一期望分流数据量的基础上，减少第二预设调整值的步骤；
如果所述第一期望分流数据量不大于所述最小分流数据量，则不对所述第一期望分流数据量进行调整。通过根据不同的数据量变化状态，对期望分流数据量在一定范围内进行调整，使得分流的业务数据在满足系统数据传输能力的同时，能够适应SeNB发送速率的变化、MeNB与SeNB之间数据传输时延的变化以及MeNB接收到的业务数据量的变化，进而提高系统的吞吐率。
结合第一方面的第四种可能的实现方式，在第一方面的第七种可能的实现方式中，在所述第一期望分流数据量的基础上，减少第三预设调整值之前，所述方法还包括：
如果所述数据量变化状态为所述接收数据量不足状态，则判断所述第一期 望分流数据量是否大于最小分流数据量；
如果所述第一期望分流数据量大于所述最小分流数据量，则执行在所述第一期望分流数据量的基础上，减少第三预设调整值的步骤；
如果所述第一期望分流数据量不大于所述最小分流数据量，则不对所述第一期望分流数据量进行调整。通过根据不同的数据量变化状态，对期望分流数据量在一定范围内进行调整，使得分流的业务数据在满足系统数据传输能力的同时，能够适应SeNB发送速率的变化、MeNB与SeNB之间数据传输时延的变化以及MeNB接收到的业务数据量的变化，进而提高系统的吞吐率。
第二方面，提供了一种业务数据分流装置，所述装置包括多个功能模块用于执行上述第一方面所述的方法。在一种可能的实现方式中，所述装置还包括其他功能模块用于执行上述第一方面中多种可能的实现方式所述的方法。通过周期性的确定分流业务数据的数据量变化状态，并根据不同的数据量变化状态，对期望分流数据量进行调整，使得分流的业务数据能够适应SeNB发送速率的变化、MeNB与SeNB之间数据传输时延的变化以及MeNB接收到的业务数据量的变化，进而提高系统的吞吐率。
第三方面，提供了一种基站，包括：接收器、发射器、存储器和处理器，
所述接收器、所述发射器和所述存储器分别与所述处理器连接，所述存储器用于存储所述处理器的可执行指令，所述处理器被配置为：
接收主基站MeNB发送的分流业务数据，缓存所述分流业务数据，所述分流业务数据是指所述MeNB根据第一期望分流数据量分流的业务数据；当到达预设周期时，确定分流业务数据的数据量变化状态，所述数据量变化状态为缓存数据量减少状态、缓存数据量堆积状态和接收数据量不足状态；根据所述数据量变化状态，对所述第一期望分流数据量进行调整，得到第二期望分流数据量；将所述第二期望分流数据量发送至所述MeNB，由所述MeNB根据所述第二期望分流数据量进行分流。通过根据不同的数据量变化状态，对期望分流数据量在一定范围内进行调整，使得分流的业务数据在满足系统数据传输能力的同时，能够适应SeNB发送速率的变化、MeNB与SeNB之间数据传输时延的变化以及MeNB接收到的业务数据量的变化，进而提高系统的吞吐率。
本发明实施例提供的技术方案的有益效果：
通过周期性的确定分流业务数据的数据量变化状态，并根据不同的数据量变化状态，对期望分流数据量进行调整，使得分流的业务数据能够适应SeNB发送速率的变化、MeNB与SeNB之间数据传输时延的变化，提高了系统的吞吐率。
附图说明
为了更清楚地说明本发明实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本发明实施例提供的一种双连接技术中业务数据分流示意图；
图2A是本发明实施例提供的一种用于业务数据分流的系统架构图；
图2B是本发明实施例提供的一种携带期望分流数据量的指定消息的消息格式图；
图2C是本发明实施例提供的一种MeNB和NeNB的用户平面协议栈；
图3A是本发明实施例提供的一种业务数据分流方法的流程图；
图3B是本发明实施例提供的一种判断数据量变化状态是否为缓存数据量减少状态的流程图；
图3C是本发明实施例提供的一种判断数据量变化状态是否为缓存数据量堆积状态的流程；
图3D是本发明实施例提供的一种判断数据量变化状态是否为接收数据量不足状态的流程图；
图3E是本发明实施例提供的一种SeNB对期望分流数据量进行调整的框图；
图4是本发明实施例提供的一种业务数据分流装置的框图；
图5是本发明实施例提供的一种基站的结构示意图。
具体实施方式
为使本发明的目的、技术方案和优点更加清楚，下面将结合附图对本发明实施方式作进一步地详细描述。
图2A为本发明实施例提供的一种用于业务数据分流的系统架构图，参见 图2A，包括核心网、MeNB、SeNB和UE。
其中，MeNB用于从核心网接收业务数据，如果该业务数据为不可进行分流的业务数据，比如RLC UM模式的业务数据，则直接将该业务数据发送至UE。如果该业务数据为可进行分流的业务数据，比如RLC AM模式的业务数据，则将该业务数据分流成两部分，一部分业务数据由MeNB发送至UE；另一部分业务数据由MeNB分流至SeNB，由SeNB将该部分业务数据发送至UE。
MeNB向SeNB分流的过程可以为：SeNB周期性地向MeNB发送期望分流数据量。MeNB根据接收到的期望分流数据量，将从核心网接收到的业务数据分流至SeNB。其中，该期望分流数据量可由SeNB按照预设发送周期，周期性地发送给MeNB。该预设发送周期可由系统进行预先设置或修改，本发明实施例对此不作具体限定。该期望分流数据量的初始值可根据SeNB的数据传输能力进行预先设置，本发明实施例对此不作具体限定。该期望分流数据量可由SeNB根据自身数据量变化状态不断地进行调整，以使分流的业务数据能够适应SeNB发送速率的变化、MeNB与SeNB之间数据传输时延的变化以及MeNB接收到的业务数据量的变化，进而提高系统的吞吐率，具体过程详见图3A所示的实施例。
具体地，期望分流数据量可以携带在指定消息中发送给MeNB，比如，该期望分流数据量为指定消息中的一个字段。该指定消息可为DL DATA DELIVERY STATUS消息或其他消息，该指定消息的消息格式可如图2B所示。该期望分流数据量可为该指定消息中的Desired Buffer Size字段，如图2B所示，该Desired Buffer Size字段的长度可为4个字节。该指定消息格式中还包括Highest Successfully delivered PDCP Sequence Number字段，用于指示SeNB向UE成功发送的PDCP数据包的最大序列号；Minimum desired buffer size for the UE字段，用于指示在双连接中为UE建立数据承载的最小缓存大小；Number of lost X2-U Sequence Number ranges reported字段，用于指示报告的已丢失的数据包序列号的范围；Start of lost X2-U Sequence Number range字段，用于指示丢失数据包的起始序列号；End of lost X2-U Sequence Number range字段，用于指示丢失数据包的结束序列号；Spare extension字段为备用的扩展字段。
具体地，MeNB在PDCP层对接收到的业务数据进行分流。图2C为MeNB和NeNB的用户平面协议栈，参见图2C，MeNB中包括PDCP(Packet Data Convergence Protocol，分组数据汇聚协议)层，RLC层和MAC(Media Access  Control，媒介访问控制)层。SeNB中包括RLC层和MAC层。MeNB在接收到业务数据后，将该业务数据通过PDCP层打包为PDCP PDU(PDCP Protocol Data Unit，PDCP协议数据单元)数据包。然后根据期望分流数据量，对PDCP PDU数据包进行分流。分流至SeNB的PDCP PDU数据包经过SeNB中的RLC层和MAC层处理后，发送至UE。同样，留在MeNB的PDCP PDU数据包经过MeNB中的RLC层和MAC层处理后，发送至UE。
图3A是本发明实施例提供的一种业务数据分流方法的流程图，应用于SeNB，参见图3A，本发明实施例提供的方法流程包括：
301、接收MeNB发送的分流业务数据，缓存该分流业务数据，该分流业务数据是指MeNB根据第一期望分流数据量分流的业务数据。
在本发明实施例中，SeNB在接收分流业务数据之前，会向MeNB发送第一期望分流数据量。该第一期望分流数据量用于指示MeNB每次向SeNB发送业务数据的数据量。当MeNB接收到该第一期望分流数据量后，根据该第一期望数据量向SeNB进行业务数据分流。
在对分流业务数据进行缓存后，SeNB会根据系统调度以一定的发送速率将缓存的分流业务数据发送至UE。其中，该发送速率不一定是固定的，会受到网络环境等因素的影响而变化。
302、当到达预设周期时，确定分流业务数据的数据量变化状态，该数据量变化状态包括缓存数据量减少状态、缓存数据量堆积状态和接收数据量不足状态。
在本发明实施例中，为了避免SeNB由于缓存数据堆积或者缓存数据不足而导致系统吞吐率下降，SeNB会对分流业务数据的缓存数据量进行监控，进而判断数据量变化状态是否为缓存数据量减少状态或缓存数据量堆积状态。
其中，判断数据量变化状态是否为缓存数据量减少状态的流程可如图3B所示，包括如下步骤：
步骤一、当到达预设周期时，判断缓存的分流业务数据的数据量是否小于第一预设阈值。
步骤二、如果缓存的分流业务数据的数据量小于第一预设阈值，则确定数据量变化状态为缓存数据量减少状态。
步骤三、如果缓存的分流业务数据的数据量不小于第一预设阈值，则确定 数据量变化状态不是缓存数据量减少状态。
该第一预设阈值可根据SeNB的数据传输能力进行预先设置，或者根据业务需求进行预先配置或修改，本发明实施例对此不作具体限定。
需要说明的是，导致SeNB缓存数据量减少的原因可能如下：
一、由于MeNB接收到的业务数据量不变，MeNB与SeNB之间的数据传输时延不变，而SeNB向UE发送业务数据的发送速率提升，使得一段时间内SeNB从MeNB接收到的数据量不变，而向UE发送的数据量增加，导致缓存的数据量减少。
二、由于MeNB接收到的业务数据量不变，SeNB的发送速率不变，而MeNB与SeNB之间的数据传输时延变大，使得一段时间内SeNB向UE发送的数据量不变，而从MeNB接收到的数据量减少，导致缓存的数据量减少。
其中，判断数据量变化状态是否为缓存数据量堆积状态的流程可如图3C所示，包括如下步骤：
步骤一、当到达预设周期时，判断缓存的分流业务数据的数据量是否大于上一次到达预设周期时缓存的数据量。
需要说明的是，每当到达预设周期时，SeNB均会对缓存的分流业务数据的数据量进行记录。具体地，可建立每个预设周期与缓存的分流业务数据的数据量的对应关系。
步骤二、如果缓存的分流业务数据的数据量大于上一次到达预设周期时缓存的数据量，则判断缓存的分流业务数据的数据量是否大于第二预设阈值。
该第二预设阈值可根据SeNB的数据传输能力进行预先设置，或者根据业务需求进行预先配置或修改，本发明实施例对此不作具体限定。该第二预设阈值大于上述第一预设阈值。
需要说明的是，如果缓存的分流业务数据的数据量不大于上一次到达预设周期时缓存的数据量，则确定数据量变化状态不是缓存数据量堆积状态。
步骤三、如果缓存的分流业务数据的数据量大于第二预设阈值，则判断预设周期是否为满调度周期，满调度周期是指预设周期内缓存的业务数据的数据量是否不小于每次下行调度所指示的最大数据量。
需要说明的是，SeNB在下行调度所指示的时隙上向UE发送业务数据，例如，SeNB需在一个TTI(Transmission Time Interval，传输时间间隔)内向UE发送业务数据。在向UE发送业务数据之前，SeNB的MAC层会根据UE 的所在位置、数据链路质量以及自身的空口质量等条件，计算能够向UE发送的最大数据量，也即是下行调度所指示的最大数据量。如果缓存的数据量不小于该最大数据量，则从缓存的业务数据中，获取该最大数据量的业务数据，将该最大数据量的业务数据发送给UE。如果缓存的数据量小于该最大数据量，则将缓存的全部数据发送给UE。其中，每一次下行调度所指示的最大数据量可以相同也可以不同，由MAC层的计算方式和实际的计算数据决定，本发明实施例对此不作具体限定。
在本发明实施例中，在预设周期内SeNB向UE发送业务数据的次数不一定是固定的，也即是，预设周期内下行调度的次数不一定是固定的。预设周期内SeNB可能会向UE发送多次业务数据，在每次向UE发送业务数据时，SeNB均会判断缓存的业务数据的数据量是否不小于下行调度所指示的最大数据量，并对判断结果进行记录。如果到达预设周期时，每一次记录结果均为缓存的业务数据的数据量不小于下行调度所指示的最大数据量，则确定该预设周期为满调度周期。
需要说明的是，如果缓存的分流业务数据的数据量不大于第二预设阈值，则确定数据量变化状态不是缓存数据量堆积状态。
步骤四、如果预设周期为满调度周期，且包括预设周期在内连续有第一预设数目的预设周期均为满调度周期，则确定数据量变化状态为缓存数据量堆积状态。
其中，第一预设数目可以进行预先设置，或根据实际业务需求进行修改，本发明实施例对此不作具体限定。
SeNB可对每个预设周期是否为满调度周期进行记录，如果本次预设周期是满调度周期，则判断包含本次预设周期在内是否连续有第一预设数目的预设周期均为满调度周期。如果是，则确定此时数据量变化状态为缓存数据量堆积状态。例如，第一预设数目为3，本次预设周期为满调度周期，则本次预设周期之前连续两个预设周期均为满调度周期时，确定数据量变化状态为缓存数据量堆积状态。
需要说明的是，导致SeNB缓存数据量堆积的原因可能如下：
一、由于MeNB接收到的业务数据量不变，MeNB与SeNB之间的数据传输时延不变，而SeNB向UE发送业务数据的发送速率下降，使得一段时间内SeNB从MeNB接收到的数据量不变，而向UE发送的数据量减少，导致缓存 数据量堆积。
二、由于MeNB接收到的业务数据量不变，SeNB的发送速率不变，而MeNB与SeNB之间的数据传输时延变小，使得一段时间内SeNB向UE发送的数据量不变，而从MeNB接收到的数据量增加，导致缓存数据量堆积。
需要说明的是，如果预设周期不是满调度周期，则确定数据量变化状态不是缓存数据量堆积状态；或者，如果预设周期为满调度周期，但包括预设周期在内不存在连续第一预设数目的预设周期均为满调度周期，则确定数据量变化状态不是缓存数据量堆积状态。
此外，由于MeNB每次从核心网接收的业务数据量不一定是固定的，当MeNB接收到的业务数据量下降时，有可能导致MeNB向SeNB分流的业务数据的数据量不满足第一期望分流数据量，使得SeNB接收到的业务数据量小于第一期望分流数据量，进而影响系统吞吐率。
为了避免由于接收的业务数据量不足而导致系统吞吐率下降，SeNB还会对每次接收到的分流业务数据的数据量进行监控，进而判断数据量变化状态是否为接收数据量不足状态，判断过程可如图3D所示，包括如下步骤：
步骤一、当到达预设周期时，判断预设周期内每次接收到的分流业务数据的数据量是否均小于第一期望分流数据量。
需要说明的是，SeNB向MeNB发送期望分流数据量的预设发送周期可以与预设周期相同，也可以不同，比如预设发送周期可小于预设周期，本发明实施例对此不作具体限定。如果预设周期与预设发送周期相同，则SeNB在预设周期内接收一次分流业务数，如果不相同，则SeNB在预设周期内可接收多次分流数据业务。在预设周期内，SeNB在接收到分流业务数据后，均会判断该接收的分流业务数据是否小于第一期望分流数据量，并对判断结果进行记录。
需要说明的是，当SeNB在预设周期内接收一次分流业务数时，仅需判断预设周期内接收到的分流业务数据是否小于第一期望分流数据量即可。
步骤二、如果是，则确定预设周期为接收量不足周期。
如果预设周期内每次接收到的分流业务数据的数据量均小于第一期望分流数据量，则确定预设周期为接收量不足周期。如果预设周期内每次接收到的分流业务数据的数据量均等于第一期望分流数据量，确定本次预设周期内接收的分流业务数据量充足。
在另一实施例中，为了提高对期望分流业务数据量进行调整的灵活性，进 而提高业务数据分流的灵活性，当SeNB在预设周期内可接收多次分流数据业务时，还可在接收到的业务数据量小于第一期望分流数据量的次数与总接收次数的比例超过预设百分比时，确定该预设周期为接收量不足周期。例如，该预设百分比为60％，该预设周期内接收到4次分流业务数据，其中有3次接收到的业务数据量小于第一期望分流数据，则接收到的业务数据量小于第一期望分流数据量的次数与总接收次数的比例为75％，大于60％，则确定该预设周期为接收量不足周期。其中，预设百分比可以进行预先设置或修改，本发明实施例对此不作具体限定。
步骤三、如果预设周期为接收量不足周期，且包括预设周期在内连续有第二预设数目的预设周期均为接收量不足周期，则确定数据量变化状态为接收数据量不足状态。
其中，第二预设数目可以进行预先设置，或根据实际业务需求进行修改，本发明实施例对此不作具体限定。
SeNB可对每个预设周期是否为接收量不足周期进行记录，如果本次预设周期是接收量不足周期，则判断包含本次预设周期在内是否连续有第二预设数目的预设周期均为接收量不足周期。如果是，则确定此时数据量变化状态为接收数据量不足状态。例如，第二预设数目为3，本次预设周期为接收量不足周期，则本次预设周期之前连续两个预设周期均为接收量不足周期时，确定数据量变化状态为接收数据量不足状态。
需要说明的是，如果预设周期不是接收量不足周期，则确定数据量变化状态不是接收数据量不足状态；或者，如果预设周期为接收量不足周期，但包括预设周期在内不存在连续第二预设数目的预设周期均为接收量不足周期，则确定数据量变化状态不是接收数据量不足状态。
303、根据该数据量变化状态，对第一期望分流数据量进行调整，得到第二期望分流数据量。
为了更加清楚的描述SeNB对期望分流数据量的调整过程，本发明实施例提供了的SeNB对期望分流数据量进行调整的框图，如图3E所示，SeNB根据该数据量变化状态，对第一期望分流数据量进行调整的过程可以为如下几种情况：
一、如果数据量变化状态为缓存数据量减少状态，则在第一期望分流数据量的基础上，增加第一预设调整值，得到第二期望分流数据量。
二、如果数据量变化状态为缓存数据量堆积状态，则在第一期望分流数据量的基础上，减少第二预设调整值，得到第二期望分流数据量。通过在SeNB处于缓存数据量堆积状态时，减少第一期望分流数据量，以便减少后续SeNB从MeNB接收的数据量，进而降低了SeNB的传输时延。
三、如果数据量变化状态为接收数据量不足状态，则在第一期望分流数据量的基础上，减少第三预设调整值，得到第二期望分流数据量。
四、如果数据量变化状态不是上述三种状态中的任一种，则不对第一期望分流数据量进行调整。
其中，第一预设调整值、第二预设调整值和第三预设调整值可以相等，也可以不相等，本发明实施例对此不作具体限定。第一预设调整值、第二预设调整值和第三预设调整值均可由系统进行预先设置和修改，本发明实施例对此不作具体限定。
需要说明的是，为了避免调整后的第二期望分流数据量过大或过小而导致业务数据分流的不合理，SeNB可根据最大分流数据量和最小分流数据量，对期望分流数据量的进行调整。该最大分流数据量和最小分流数据量可由系统根据业务需求或数据传输能力进行预先设置或修改，本发明实施例对此不作具体限定。
具体地，在确定的数据量变化状态后，SeNB根据最大分流数据量和最小分流数据量，对第一期望分流数据量进行调整，包括如下几种情况：
第一种情况、如果数据量变化状态为缓存数据量减少状态，则判断第一期望分流数据量是否小于最大分流数据量；如果第一期望分流数据量小于最大分流数据量，则执行在第一期望分流数据量的基础上，增加第一预设调整值的步骤；如果第一期望分流数据量不小于最大分流数据量，则不对第一期望分流数据量进行调整。
第二种情况、如果数据量变化状态为缓存数据量堆积状态，则判断第一期望分流数据量是否大于最小分流数据量；如果第一期望分流数据量大于最小分流数据量，则执行在第一期望分流数据量的基础上，减少第二预设调整值的步骤；如果第一期望分流数据量不大于最小分流数据量，则不对第一期望分流数据量进行调整。
第三种情况，如果数据量变化状态为接收数据量不足状态，则判断第一期望分流数据量是否大于最小分流数据量；如果第一期望分流数据量大于最小分 流数据量，则执行在第一期望分流数据量的基础上，减少第三预设调整值的步骤；如果第一期望分流数据量不大于最小分流数据量，则不对第一期望分流数据量进行调整。
304、将第二期望分流数据量发送至MeNB，由MeNB根据第二期望分流数据量进行分流。
在本发明实施中，SeNB在到达预设周期时，可将得到的第二期望分流数据量发送至MeNB，也即是，SeNB可根据预设周期向MeNB发送期望分流数据量。此外，SeNB向MeNB发送期望分流数据量的周期还可不同于该预设周期，本发明实施例对此不作具体限定。
当MeNB接收到第二期望分流数据量后，根据第二分流数据量进行分流，并将分流的业务数据发送至SeNB。
需要说明的是，本发明实施例提供的方法可应用于LTE系统的分流场景中，还可应用于其他通信制式的分流场景中，比如LTE与WiFi(Wireless Fidelity，无线保真)的分流场景中，本发明实施例对此不作具体限定。
本发明实施例提供的方法，通过周期性的确定分流业务数据的数据量变化状态，并根据不同的数据量变化状态，对期望分流数据量进行调整，使得分流的业务数据能够适应SeNB发送速率的变化、MeNB与SeNB之间数据传输时延的变化以及MeNB接收到的业务数据量的变化，进而提高系统的吞吐率。进一步地，通过在SeNB处于缓存数据量堆积状态时，减少第一期望分流数据量，以便减少后续SeNB从MeNB接收的数据量，进而降低了SeNB的传输时延。
图4是本发明提供的一种业务数据分流装置的框图，应用于SeNB。参见图4，该装置包括：接收模块401、缓存模块402、确定模块403、调整模块404和发送模块405。
其中，接收模块401与缓存模块402连接，用于接收MeNB发送的分流业务数据，分流业务数据是指MeNB根据第一期望分流数据量分流的业务数据；缓存模块402与确定模块403连接，用于缓存分流业务数据；确定模块403与调整模块404连接，用于当到达预设周期时，确定分流业务数据的数据量变化状态，数据量变化状态包括缓存数据量减少状态、缓存数据量堆积状态和接收数据量不足状态；调整模块404与发送模块405连接，用于根据数据量变化状态，对第一期望分流数据量进行调整，得到第二期望分流数据量；发送模块405， 用于将第二期望分流数据量发送至MeNB，由MeNB根据第二期望分流数据量进行分流。
可选地，确定模块403用于当到达预设周期时，如果缓存的分流业务数据的数据量小于第一预设阈值，则确定数据量变化状态为缓存数据量减少状态。
可选地，确定模块403用于当到达预设周期时，判断缓存的分流业务数据的数据量是否大于上一次到达预设周期时缓存的数据量；如果缓存的分流业务数据的数据量大于上一次到达预设周期时缓存的数据量，则判断缓存的分流业务数据的数据量是否大于第二预设阈值；如果缓存的分流业务数据的数据量大于第二预设阈值，则判断预设周期是否为满调度周期，满调度周期是指预设周期内缓存的业务数据的数据量是否不小于每次下行调度所指示的最大数据量；如果预设周期为满调度周期，且包括预设周期在内连续有第一预设数目的预设周期均为满调度周期，则确定数据量变化状态为缓存数据量堆积状态。
可选地，确定模块403用于当到达预设周期时，判断预设周期内每次接收到的分流业务数据的数据量是否均小于第一期望分流数据量；如果是，则确定预设周期为接收量不足周期；如果预设周期为接收量不足周期，且包括预设周期在内连续有第二预设数目的预设周期均为接收量不足周期，则确定数据量变化状态为接收数据量不足状态。
可选地，调整模块404用于如果数据量变化状态为缓存数据量减少状态，则在第一期望分流数据量的基础上，增加第一预设调整值，得到第二期望分流数据量；如果数据量变化状态为缓存数据量堆积状态，或数据量变化状态为接收数据量不足状态，则在第一期望分流数据量的基础上，减少第二预设调整值，得到第二期望分流数据量。
可选地，调整模块404还用于如果数据量变化状态为缓存数据量减少状态，则判断第一期望分流数据量是否小于最大分流数据量；如果第一期望分流数据量小于最大分流数据量，则执行在第一期望分流数据量的基础上，增加第一预设调整值的步骤；如果第一期望分流数据量不小于最大分流数据量，则不对第一期望分流数据量进行调整。
可选地，调整模块404还用于如果数据量变化状态为缓存数据量堆积状态，或数据量变化状态为接收数据量不足状态，则判断第一期望分流数据量是否大于最小分流数据量；如果第一期望分流数据量大于最小分流数据量，则执行在第一期望分流数据量的基础上，减少第二预设调整值的步骤；如果第一期望分 流数据量不大于最小分流数据量，则不对第一期望分流数据量进行调整。
本发明实施例提供的装置，通过周期性的确定分流业务数据的数据量变化状态，并根据不同的数据量变化状态，对期望分流数据量进行调整，使得分流的业务数据能够适应SeNB发送速率的变化、MeNB与SeNB之间数据传输时延的变化，提高了系统吞吐率。
需要说明的是：上述实施例提供的数据传输装置在进行业务数据分流时，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将装置的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。另外，上述实施例提供的业务数据分流装置与业务数据分流方法实施例属于同一构思，其具体实现过程详见方法实施例，这里不再赘述。
图5是本发明实施例提供的一种基站的结构示意图，参见图5，包括：接收器501、发射器502、存储器503和处理器504，该接收器501、该发射器502和该存储器503分别与该处理器504连接，该存储器503用于存储所述处理器的可执行指令，该处理器504被配置为：
接收主基站MeNB发送的分流业务数据，缓存分流业务数据，分流业务数据是指MeNB根据第一期望分流数据量分流的业务数据；当到达预设周期时，确定分流业务数据的数据量变化状态，数据量变化状态为缓存数据量减少状态、缓存数据量堆积状态和接收数据量不足状态；根据数据量变化状态，对第一期望分流数据量进行调整，得到第二期望分流数据量；将第二期望分流数据量发送至MeNB，由MeNB根据第二期望分流数据量进行分流。
可选地，当到达预设周期时，确定分流业务数据的数据量变化状态包括：
当到达预设周期时，如果缓存的分流业务数据的数据量小于第一预设阈值，则确定数据量变化状态为缓存数据量减少状态。通过确定数据量变化状态为数据量减少状态，使得SeNB可以根据该状态，增加第一期望分流数据量，以便提高后续SeNB从MeNB接收的数据量，进而提高系统吞吐率。
可选地，当到达预设周期时，确定分流业务数据的数据量变化状态包括：
当到达预设周期时，判断缓存的分流业务数据的数据量是否大于上一次到达预设周期时缓存的数据量；
如果缓存的分流业务数据的数据量大于上一次到达预设周期时缓存的数 据量，则判断缓存的分流业务数据的数据量是否大于第二预设阈值；
如果缓存的分流业务数据的数据量大于第二预设阈值，则判断预设周期是否为满调度周期，满调度周期是指预设周期内每次系统调度所需向UE发送的数据量均不大于缓存的业务数据的数据量；
如果预设周期为满调度周期，且包括预设周期在内连续有第一预设数目的预设周期均为满调度周期，则确定数据量变化状态为缓存数据量堆积状态。通过确定数据量变化状态为数据量堆积状态，使得SeNB可以根据该状态，减少第一期望分流数据量，以便减少后续SeNB从MeNB接收的数据量，进而降低了SeNB的传输时延。
可选地，当到达预设周期时，确定分流业务数据的数据量变化状态包括：
当到达预设周期时，判断预设周期内每次接收到的分流业务数据的数据量是否均小于第一期望分流数据量；
如果是，则确定预设周期为接收量不足周期；
如果预设周期为接收量不足周期，且包括预设周期在内连续有第二预设数目的预设周期均为接收量不足周期，则确定数据量变化状态为接收数据量不足状态。通过确定数据量变化状态为接收数据量不足状态，使得SeNB可以根据该状态，减少第一期望分流数据量，以便减少后续SeNB从MeNB接收的数据量，进而提高系统吞吐率。
可选地，根据数据量变化状态，对第一期望分流数据量进行调整，得到第二期望分流数据量包括：
如果数据量变化状态为缓存数据量减少状态，则在第一期望分流数据量的基础上，增加第一预设调整值，得到第二期望分流数据量；或，
如果数据量变化状态为缓存数据量堆积状态，则在第一期望分流数据量的基础上，减少第二预设调整值，得到第二期望分流数据量；或，
如果数据量变化状态为接收数据量不足状态，则在第一期望分流数据量的基础上，减少第三预设调整值，得到第二期望分流数据量。通过根据不同的数据量变化状态，对期望分流数据量进行调整，使得分流的业务数据能够适应SeNB发送速率的变化、MeNB与SeNB之间数据传输时延的变化以及MeNB接收到的业务数据量的变化，进而提高系统的吞吐率。
可选地，在第一期望分流数据量的基础上，增加第一预设调整值之前，方法还包括：
如果数据量变化状态为缓存数据量减少状态，则判断第一期望分流数据量是否小于最大分流数据量；
如果第一期望分流数据量小于最大分流数据量，则执行在期望分流数据量的基础上，增加第一预设调整值的步骤；
如果第一期望分流数据量不小于最大分流数据量，则不对第一期望分流数据量进行调整。通过根据不同的数据量变化状态，对期望分流数据量在一定范围内进行调整，使得分流的业务数据在满足系统数据传输能力的同时，能够适应SeNB发送速率的变化、MeNB与SeNB之间数据传输时延的变化以及MeNB接收到的业务数据量的变化，进而提高系统的吞吐率。
可选地，在第一期望分流数据量的基础上，减少第二预设调整值之前，方法还包括：
如果数据量变化状态为缓存数据量堆积状态，则判断第一期望分流数据量是否大于最小分流数据量；
如果第一期望分流数据量大于最小分流数据量，则执行在第一期望分流数据量的基础上，减少第二预设调整值的步骤；
如果第一期望分流数据量不大于最小分流数据量，则不对第一期望分流数据量进行调整。通过根据不同的数据量变化状态，对期望分流数据量在一定范围内进行调整，使得分流的业务数据在满足系统数据传输能力的同时，能够适应SeNB发送速率的变化、MeNB与SeNB之间数据传输时延的变化以及MeNB接收到的业务数据量的变化，进而提高系统的吞吐率。
可选地，在第一期望分流数据量的基础上，减少第三预设调整值之前，方法还包括：
如果数据量变化状态为接收数据量不足状态，则判断第一期望分流数据量是否大于最小分流数据量；
如果第一期望分流数据量大于最小分流数据量，则执行在第一期望分流数据量的基础上，减少第三预设调整值的步骤；
如果第一期望分流数据量不大于最小分流数据量，则不对第一期望分流数据量进行调整。通过根据不同的数据量变化状态，对期望分流数据量在一定范围内进行调整，使得分流的业务数据在满足系统数据传输能力的同时，能够适应SeNB发送速率的变化、MeNB与SeNB之间数据传输时延的变化以及MeNB接收到的业务数据量的变化，进而提高系统的吞吐率。
本发明实施例提供的基站，通过周期性的确定分流业务数据的数据量变化状态，并根据不同的数据量变化状态，对期望分流数据量进行调整，使得分流的业务数据能够适应SeNB发送速率的变化、MeNB与SeNB之间数据传输时延的变化，提高了系统吞吐率。
本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以通过硬件来完成，也可以通过程序来指令相关的硬件完成，所述的程序可以存储于一种计算机可读存储介质中，上述提到的存储介质可以是只读存储器，磁盘或光盘等。
以上所述仅为本发明的较佳实施例，并不用以限制本发明，凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。

Claims (17)

  1. 一种业务数据分流方法，其特征在于，所述方法包括：
    接收主基站MeNB发送的分流业务数据，缓存所述分流业务数据，所述分流业务数据是指所述MeNB根据第一期望分流数据量分流的业务数据；
    当到达预设周期时，确定分流业务数据的数据量变化状态，所述数据量变化状态包括缓存数据量减少状态、缓存数据量堆积状态和接收数据量不足状态；
    根据所述数据量变化状态，对所述第一期望分流数据量进行调整，得到第二期望分流数据量；
    将所述第二期望分流数据量发送至所述MeNB，由所述MeNB根据所述第二期望分流数据量进行分流。
  2. 根据权利要求1所述的方法，其特征在于，当到达预设周期时，确定分流业务数据的数据量变化状态包括：
    当到达所述预设周期时，如果缓存的分流业务数据的数据量小于第一预设阈值，则确定所述数据量变化状态为所述缓存数据量减少状态。
  3. 根据权利要求1所述的方法，其特征在于，当到达预设周期时，确定分流业务数据的数据量变化状态包括：
    当到达所述预设周期时，判断缓存的分流业务数据的数据量是否大于上一次到达预设周期时缓存的数据量；
    如果缓存的分流业务数据的数据量大于上一次到达预设周期时缓存的数据量，则判断缓存的分流业务数据的数据量是否大于第二预设阈值；
    如果缓存的分流业务数据的数据量大于第二预设阈值，则判断所述预设周期是否为满调度周期，满调度周期是指预设周期内缓存的业务数据的数据量是否不小于每次下行调度所指示的最大数据量；
    如果所述预设周期为满调度周期，且包括所述预设周期在内连续有第一预设数目的预设周期均为满调度周期，则确定数据量变化状态为所述缓存数据量堆积状态。
  4. 根据权利要求1所述的方法，其特征在于，当到达预设周期时，确定分 流业务数据的数据量变化状态包括：
    当到达预设周期时，判断所述预设周期内每次接收到的分流业务数据的数据量是否均小于所述第一期望分流数据量；
    如果是，则确定所述预设周期为接收量不足周期；
    如果所述预设周期为接收量不足周期，且包括所述预设周期在内连续有第二预设数目的预设周期均为接收量不足周期，则确定数据量变化状态为所述接收数据量不足状态。
  5. 根据权利要求1所述的方法，其特征在于，根据所述数据量变化状态，对所述第一期望分流数据量进行调整，得到第二期望分流数据量包括：
    如果所述数据量变化状态为所述缓存数据量减少状态，则在所述第一期望分流数据量的基础上，增加第一预设调整值，得到所述第二期望分流数据量；或，
    如果所述数据量变化状态为所述缓存数据量堆积状态，则在所述第一期望分流数据量的基础上，减少第二预设调整值，得到所述第二期望分流数据量；或，
    如果所述数据量变化状态为所述接收数据量不足状态，则在所述第一期望分流数据量的基础上，减少第三预设调整值，得到所述第二期望分流数据量。
  6. 根据权利要求5所述的方法，其特征在于，在所述第一期望分流数据量的基础上，增加第一预设调整值之前，所述方法还包括：
    如果所述数据量变化状态为所述缓存数据量减少状态，则判断所述第一期望分流数据量是否小于最大分流数据量；
    如果所述第一期望分流数据量小于所述最大分流数据量，则执行在所述期望分流数据量的基础上，增加第一预设调整值的步骤；
    如果所述第一期望分流数据量不小于所述最大分流数据量，则不对所述第一期望分流数据量进行调整。
  7. 根据权利要求5所述的方法，其特征在于，在所述第一期望分流数据量的基础上，减少第二预设调整值之前，所述方法还包括：
    如果所述数据量变化状态为所述缓存数据量堆积状态，或所述数据量变化 状态为所述接收数据量不足状态，则判断所述第一期望分流数据量是否大于最小分流数据量；
    如果所述第一期望分流数据量大于所述最小分流数据量，则执行在所述第一期望分流数据量的基础上，减少第二预设调整值的步骤；
    如果所述第一期望分流数据量不大于所述最小分流数据量，则不对所述第一期望分流数据量进行调整。
  8. 根据权利要求5所述的方法，其特征在于，在所述第一期望分流数据量的基础上，减少第三预设调整值之前，所述方法还包括：
    如果所述数据量变化状态为所述接收数据量不足状态，则判断所述第一期望分流数据量是否大于最小分流数据量；
    如果所述第一期望分流数据量大于所述最小分流数据量，则执行在所述第一期望分流数据量的基础上，减少第三预设调整值的步骤；
    如果所述第一期望分流数据量不大于所述最小分流数据量，则不对所述第一期望分流数据量进行调整。
  9. 一种业务数据分流装置，其特征在于，所述装置包括：
    接收模块，用于接收主基站MeNB发送的分流业务数据，所述分流业务数据是指所述MeNB根据第一期望分流数据量分流的业务数据；
    缓存模块，用于缓存所述分流业务数据；
    确定模块，用于当到达预设周期时，确定分流业务数据的数据量变化状态，所述数据量变化状态包括缓存数据量减少状态、缓存数据量堆积状态和接收数据量不足状态；
    调整模块，用于根据所述数据量变化状态，对所述第一期望分流数据量进行调整，得到第二期望分流数据量；
    发送模块，用于将所述第二期望分流数据量发送至所述MeNB，由所述MeNB根据所述第二期望分流数据量进行分流。
  10. 根据权利要求9所述的装置，其特征在于，所述确定模块用于当到达所述预设周期时，如果缓存的分流业务数据的数据量小于第一预设阈值，则确定所述数据量变化状态为所述缓存数据量减少状态。
  11. 根据权利要求9所述的装置，其特征在于，所述确定模块用于当到达所述预设周期时，判断缓存的分流业务数据的数据量是否大于上一次到达预设周期时缓存的数据量；如果缓存的分流业务数据的数据量大于上一次到达预设周期时缓存的数据量，则判断缓存的分流业务数据的数据量是否大于第二预设阈值；如果缓存的分流业务数据的数据量大于第二预设阈值，则判断所述预设周期是否为满调度周期，满调度周期是指预设周期内缓存的业务数据的数据量是否不小于每次下行调度所指示的最大数据量；如果所述预设周期为满调度周期，且包括所述预设周期在内连续有第一预设数目的预设周期均为满调度周期，则确定数据量变化状态为所述缓存数据量堆积状态。
  12. 根据权利要求9所述的装置，其特征在于，所述确定模块用于当到达预设周期时，判断所述预设周期内每次接收到的分流业务数据的数据量是否均小于所述第一期望分流数据量；如果是，则确定所述预设周期为接收量不足周期；如果所述预设周期为接收量不足周期，且包括所述预设周期在内连续有第二预设数目的预设周期均为接收量不足周期，则确定数据量变化状态为所述接收数据量不足状态。
  13. 根据权利要求9所述的装置，其特征在于，所述调整模块用于如果所述数据量变化状态为所述缓存数据量减少状态，则在所述第一期望分流数据量的基础上，增加第一预设调整值，得到所述第二期望分流数据量；或，如果所述数据量变化状态为所述缓存数据量堆积状态，则在所述第一期望分流数据量的基础上，减少第二预设调整值，得到所述第二期望分流数据量；或，所述数据量变化状态为所述接收数据量不足状态，则在所述第一期望分流数据量的基础上，减少第三预设调整值，得到所述第二期望分流数据量。
  14. 根据权利要求13所述的装置，其特征在于，所述调整模块还用于如果所述数据量变化状态为所述缓存数据量减少状态，则判断所述第一期望分流数据量是否小于最大分流数据量；如果所述第一期望分流数据量小于所述最大分流数据量，则执行在所述第一期望分流数据量的基础上，增加第一预设调整值的步骤；如果所述第一期望分流数据量不小于所述最大分流数据量，则不对所 述第一期望分流数据量进行调整。
  15. 根据权利要求13所述的装置，其特征在于，所述调整模块还用于如果所述数据量变化状态为所述缓存数据量堆积状态，则判断所述第一期望分流数据量是否大于最小分流数据量；如果所述第一期望分流数据量大于所述最小分流数据量，则执行在所述第一期望分流数据量的基础上，减少第二预设调整值的步骤；如果所述第一期望分流数据量不大于所述最小分流数据量，则不对所述第一期望分流数据量进行调整。
  16. 根据权利要求13所述的装置，其特征在于，所述调整模块还用于如果所述数据量变化状态为所述接收数据量不足状态，则判断所述第一期望分流数据量是否大于最小分流数据量；如果所述第一期望分流数据量大于所述最小分流数据量，则执行在所述第一期望分流数据量的基础上，减少第三预设调整值的步骤；如果所述第一期望分流数据量不大于所述最小分流数据量，则不对所述第一期望分流数据量进行调整。
  17. 一种基站，其特征在于，包括：接收器、发射器、存储器和处理器，
    所述接收器、所述发射器和所述存储器分别与所述处理器连接，所述存储器用于存储所述处理器的可执行指令，所述处理器被配置为：
    接收主基站MeNB发送的分流业务数据，缓存所述分流业务数据，所述分流业务数据是指所述MeNB根据第一期望分流数据量分流的业务数据；当到达预设周期时，确定分流业务数据的数据量变化状态，所述数据量变化状态为缓存数据量减少状态、缓存数据量堆积状态和接收数据量不足状态；根据所述数据量变化状态，对所述第一期望分流数据量进行调整，得到第二期望分流数据量；将所述第二期望分流数据量发送至所述MeNB，由所述MeNB根据所述第二期望分流数据量进行分流。
PCT/CN2016/085797 2016-06-15 2016-06-15 业务数据分流方法及装置 WO2017214871A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP16904988.9A EP3462772A4 (en) 2016-06-15 2016-06-15 METHOD AND DEVICE FOR DISTRIBUTING SERVICE DATA
CN201680086579.5A CN109314884B (zh) 2016-06-15 2016-06-15 业务数据分流方法及装置
PCT/CN2016/085797 WO2017214871A1 (zh) 2016-06-15 2016-06-15 业务数据分流方法及装置
US16/220,550 US10911985B2 (en) 2016-06-15 2018-12-14 Service data splitting method and apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/085797 WO2017214871A1 (zh) 2016-06-15 2016-06-15 业务数据分流方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/220,550 Continuation US10911985B2 (en) 2016-06-15 2018-12-14 Service data splitting method and apparatus

Publications (1)

Publication Number Publication Date
WO2017214871A1 true WO2017214871A1 (zh) 2017-12-21

Family

ID=60662819

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/085797 WO2017214871A1 (zh) 2016-06-15 2016-06-15 业务数据分流方法及装置

Country Status (4)

Country Link
US (1) US10911985B2 (zh)
EP (1) EP3462772A4 (zh)
CN (1) CN109314884B (zh)
WO (1) WO2017214871A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110121186A (zh) * 2019-06-28 2019-08-13 京信通信系统（中国）有限公司 一种双连接下数据分发方法及设备
CN112469085A (zh) * 2020-11-18 2021-03-09 杭州红岭通信息科技有限公司 5g基站f1-u接口下行流量控制方法

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3461216B1 (en) * 2016-06-30 2023-12-13 Huawei Technologies Co., Ltd. Multi-connection communication method and device
CN110572882B (zh) * 2017-08-11 2021-03-05 华为技术有限公司 一种通信方法、装置、计算机存储介质和通信系统
CN112953849B (zh) * 2019-12-10 2023-05-09 中国移动通信有限公司研究院 一种数据量处理方法、设备及介质
CN113141627B (zh) * 2020-01-17 2022-09-27 大唐移动通信设备有限公司 一种基于nsa的下行数据分流方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104202768A (zh) * 2014-08-05 2014-12-10 电信科学技术研究院 一种进行l2测量的方法和设备
US20150043492A1 (en) * 2013-08-12 2015-02-12 Electronics And Telecommunications Research Institute Method for providing dual connectivity in wireless communication system
CN104427554A (zh) * 2013-08-29 2015-03-18 中兴通讯股份有限公司 一种协作多流传输数据的方法及基站
CN104812003A (zh) * 2014-01-28 2015-07-29 上海贝尔股份有限公司 用于主基站和辅基站的流控制方法和设备

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8085657B2 (en) * 2005-04-01 2011-12-27 Sony Corporation Flow control in a cellular communication system
US20150089382A1 (en) * 2013-09-26 2015-03-26 Wu-chi Feng Application context migration framework and protocol
CN104797000B (zh) * 2014-01-21 2018-06-19 普天信息技术有限公司 双连接网络中的无线承载建立方法及系统
US9838282B2 (en) 2014-05-09 2017-12-05 Telefonaktiebolaget Lm Ericsson (Publ) PDCP and flow control for split bearer
EP3372003B1 (en) * 2015-11-04 2021-04-21 Telefonaktiebolaget LM Ericsson (PUBL) Method, system and device for providing flow control in a split bearer environment
EP3372008B1 (en) * 2015-11-06 2023-01-11 Nokia Technologies Oy Flow control feedback from user equipment receiving a split bearer

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150043492A1 (en) * 2013-08-12 2015-02-12 Electronics And Telecommunications Research Institute Method for providing dual connectivity in wireless communication system
CN104427554A (zh) * 2013-08-29 2015-03-18 中兴通讯股份有限公司 一种协作多流传输数据的方法及基站
CN104812003A (zh) * 2014-01-28 2015-07-29 上海贝尔股份有限公司 用于主基站和辅基站的流控制方法和设备
CN104202768A (zh) * 2014-08-05 2014-12-10 电信科学技术研究院 一种进行l2测量的方法和设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3462772A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110121186A (zh) * 2019-06-28 2019-08-13 京信通信系统（中国）有限公司 一种双连接下数据分发方法及设备
CN112469085A (zh) * 2020-11-18 2021-03-09 杭州红岭通信息科技有限公司 5g基站f1-u接口下行流量控制方法

Also Published As

Publication number Publication date
CN109314884B (zh) 2021-01-29
CN109314884A (zh) 2019-02-05
US10911985B2 (en) 2021-02-02
EP3462772A4 (en) 2019-06-26
US20190124552A1 (en) 2019-04-25
EP3462772A1 (en) 2019-04-03

Similar Documents

Publication Publication Date Title
WO2017214871A1 (zh) 业务数据分流方法及装置
US8817806B2 (en) Method and apparatus for flow control between RLC and PDCP in a communication
US11677689B2 (en) Data processing method and apparatus
JP5159890B2 (ja) 無線リンク制御プロトコルデータユニットサイズを選択する方法および装置
US8837285B2 (en) Method and apparatus for initializing, preserving, and reconfiguring token buckets
US10542450B2 (en) Techniques for improving discontinuous reception in wideband wireless networks
CN108337633B (zh) 数据分流配置方法、基站系统和用户终端
US20170019803A1 (en) Optimization of Downlink Throughput
US11930391B2 (en) Wireless communications apparatus and methods
KR20140118650A (ko) 이동통신 시스템에서 무선랜을 이용해서 트래픽을 오프 로드하는 방법 및 장치
WO2013086953A1 (zh) 一种视频传输方法及装置
JP2019525622A (ja) グラントフリー伝送のためのアップリンクデータスケジューリングのためのシステムおよび方法
CN108847919B (zh) 一种数据传输的方法、基站和无线通信设备
CN108391289B (zh) 一种拥塞控制方法和基站
WO2006069534A1 (fr) Procede pour regler la taille du tampon de transmission d'une sous-couche rlc
US20190223256A1 (en) Data transmission method, network device, and terminal device
WO2022001175A1 (zh) 数据包发送的方法、装置
TW201739283A (zh) 適應性ｔｔｉ調諧之方法以及使用者設備
CN111066272B (zh) 移动无线电接入网络中的分组延迟减少
CN107484204B (zh) 基站上行突发缓解方法及装置
JP7432714B2 (ja) 通信制御方法及び通信装置
CN108200605B (zh) 一种基站的数据传输方法和装置
KR20090084701A (ko) ＳＲ (Ｓｃｈｅｄｕｌｉｎｇ Ｒｅｑｕｅｓｔ) 과 ＰＢＲ (Ｐｒｉｏｒｉｔｉｚｅｄ Ｂｉｔ Ｒａｔｅ)을 고려하여 ＤＲＸ(Ｄｉｓｃｏｎｔｉｎｕｏｕｓ Ｒｅｃｅｐｔｉｏｎ) 동작을 효율적으로 수행하는 방법
TWI757221B (zh) 無線通訊裝置與資料處理方法
JP2024064705A (ja) 移動通信システム、サーバ装置、基地局装置、及びコアネットワーク装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16904988

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2016904988

Country of ref document: EP

Effective date: 20181227