TW201620321A - Evolved nodeb and traffic dispatch method thereof - Google Patents

Abstract

A traffic dispatch method of a first eNB comprises the following steps: generating an estimation result according to measurement reports of a plurality of user equipments (UEs), wherein parts of the measurement reports are provided by a second eNB connected to the first eNB through a backhaul connection and parts of the measurement reports are provided by parts of the UEs, wherein coverage area of the second eNB is encompassed by the first eNB; receiving a status report from the second eNB; and making a traffic split decision according to the estimation result and the status report of the second eNB to dispatch traffic to the second eNB through the backhaul connection.

Description

Evolved Node B and traffic scheduling method

The present invention is generally related to a communication device and an operation method, and is related to an evolved Node B (eNB) and a traffic scheduling method.

Long Term Evolution-Advanced (LTE-A) is a developing standard that is expected to support the high-speed data transmission services of the fourth-generation mobile network. According to the requirements of the fourth-generation mobile network, LTE The downlink and uplink data rates supported by the -A network can reach 1 Gbps and 500 Mbps, respectively. In an LTE-A network, user equipment (UE), each connected to an evolved Node B (generally or an evolved base station), can provide user plane and control plane services as its base station.

It is foreseeable that future mobile applications will become more complex and the bandwidth requirements will grow rapidly. However, when the traffic load of the LTE-A network is busy, the network will inevitably be difficult to provide a good user experience quality.

This case provides an evolved Node B and traffic scheduling method. The implementation example of the present disclosure discloses a mechanism for scheduling traffic between the first evolved Node B and the second evolved Node B, so as to reduce the traffic of the first evolved Node B.

According to one of the implementation examples of the present application, an evolved NodeB (eNB) in the network is provided, and the evolved Node B is a first evolved Node B connected to the second evolved Node B through a backhaul network (backhaul). And the coverage of the second evolved Node B is within the coverage of the first evolved Node B. The first evolved node B includes at least an estimation module and a distribution decision module, and the estimation module generates a estimation result according to a measurement report of the plurality of user equipments, wherein the partial measurement report is a second evolution. Provided by Node B, and some measurement reports are provided by some user equipment. The traffic distribution decision module performs traffic offloading decision according to the estimation result and the status report of the second evolved node B, so as to schedule traffic to the second node B through the back-end network connection.

According to one of the implementation examples of the present application, a method for scheduling traffic of a first evolved Node B in a network is provided, and at least includes the following steps. The estimation result is generated according to the measurement report of the plurality of user equipments, wherein part of the measurement report is provided by the second evolved Node B connected to the first evolved Node B through the backend network, and the partial measurement report is Provided by a portion of the user equipment, and wherein the coverage of the second evolved Node B is within the coverage of the first evolved Node B. Receiving a status report from the second evolved Node B, and performing flow according to the estimation result and the status report of the second evolved Node B The traffic splitting decision is made to schedule traffic to the second evolved Node B through the back-end network connection.

According to one of the implementation examples of the present invention, an evolved Node B in a network is provided, and the Node B is a second evolved Node B connected to the first evolved Node B through a backend network, and serves multiple user equipments, where The coverage of the second evolved Node B is within the coverage of the first evolved Node B. The second evolved Node B includes at least a status report module to generate a status report of the second evolved Node B and provide the first evolved Node B for the first evolved Node B to report traffic according to the status of the second evolved Node B. Diversion decision.

The above and other advantages of the present invention will be described in detail below with reference to the accompanying drawings.

100‧‧‧Network

102‧‧‧First Evolved Node B

104‧‧‧Second Evolved Node B

User equipment, u1~u4‧‧‧ user equipment

BH‧‧‧Backend network

202‧‧‧ Estimation module

204‧‧‧Split Decision Module

206‧‧‧Status Reporting Module

MR‧‧‧Measurement report

ER‧‧‧ estimation results

SR‧‧‧ Status Report

BSI‧‧‧ Buffer Status Information

SQV‧‧‧ signal quality value

It‧‧‧ interval

T1, T2‧‧‧ time points

S1, s2, s3‧‧‧ Evolved Node B

ATF‧‧‧App Traffic Traffic Information

B1~b6, b1-1~b1-2, b2-1~b2-2‧‧‧bearer

Mapping relationship between M ^u (.)‧‧‧ bearers and user equipment

Mapping relationship between M ^s (.)‧‧‧ user equipment and second evolved Node B

S21, S22, S23, S232, S234, S52, S54, S62, S64, S1002, S1004, S1202, S1204‧‧‧ process steps

The drawings illustrate exemplary embodiments of the present invention and, together with the description

FIG. 1 is a schematic diagram showing an embodiment of a network in accordance with the present invention.

FIG. 2A is a schematic diagram showing an embodiment of the first evolved Node B and the second evolved Node B in FIG. 1 .

2B, 2C, and 2D are diagrams showing a flow of a flow scheduling method of the first evolved Node B (102) according to an embodiment of the present invention.

Figure 3 is a diagram showing an estimation module conforming to an embodiment of the present invention to determine user equipment loss A time interval diagram of the rate of exit.

FIG. 4 is a diagram showing an example of message flows between the first evolved Node B and the second evolved Node B in a periodic traffic scheduling phase according to an embodiment of the present invention.

FIG. 5 is a schematic diagram showing the flow of scheduling traffic between the first evolved Node B and the second evolved Node B according to an embodiment of the present invention.

FIG. 6 is a schematic diagram showing the flow of scheduling traffic between the first evolved Node B and the second evolved Node B according to an embodiment of the present invention.

FIG. 7 is a diagram showing an example of configuring an information flow of a split bearer for a tMS type user equipment between a first evolved Node B and a second evolved Node B according to an embodiment of the present invention.

FIG. 8 is a diagram showing an example of a mapping relationship between a bearer, a user equipment, and a second evolved Node B according to an embodiment of the present disclosure.

FIG. 9 is a diagram showing an example of a traffic offloading mechanism between a first evolved Node B and a second evolved Node B according to an embodiment of the present disclosure.

FIG. 10 is a schematic diagram showing the flow of scheduling traffic between the first evolved Node B and the second evolved Node B according to an embodiment of the present invention.

FIG. 11 is a diagram showing an example of a mapping relationship between a bearer, a user equipment, and a second evolved Node B according to an embodiment of the present disclosure.

FIG. 12 is a schematic diagram showing a flow of a traffic scheduling method in an instant traffic processing phase according to an embodiment of the present invention.

Figure 13 is a diagram showing the first embodiment of the present invention in the instant traffic processing stage. An illustration of an information flow between an evolved Node B and a second evolved Node B.

The above general description and the following detailed description are exemplary, and are intended to provide a detailed explanation of the present invention as claimed. However, the disclosed content may not be able to enumerate all of the aspects and embodiments of the present technology, and the inventive concept may adopt various modified embodiments, and thus does not imply any limitation or limitation. In addition, the present technology may cover modifications and modifications that are clearly foreseen by those of ordinary skill in the art.

Hereinafter, the embodiment according to the present invention will be described in detail with reference to the accompanying drawings, which will be readily understood by those skilled in the art. In some places, conventional structures and devices are simply shown to have simplified drawings, and the description of the well-known portions is omitted, and the same reference numerals are used in the present drawings.

FIG. 1 is a schematic diagram of a network 100 embodiment consistent with the present invention. The network 100 includes a first evolved Node B 102 and a second evolved Node B 104. As shown in FIG. 1 , the first evolved Node B 102 is connected to the second evolved Node B 104 through a backend network BH, and the coverage of the second evolved Node B 104 is within the coverage of the first evolved Node B 102. The coverage of an evolved Node B 102 is larger than that of the second evolved Node B 104. The second evolved Node B 104 can play the role of a base station and possibly serve user equipment located in their coverage.

In an embodiment, the first evolved Node B 102 is a giant cell (macro, macro) eNB, and the second evolved Node B 104 is a small cell (small cell). eNB, but the embodiments of the present invention are not limited thereto. For example, the second evolved Node B 104 may also be a slave evolved Node B (slave eNB), a micro cell eNB, a pico cell eNB, a femto cell eNB, or a relay node ( Relay node) and so on, this case is known as small cell evolution node B. Furthermore, the number of the first evolved Node B, the second evolved Node B, and the user equipment and the arrangement of the apparatus illustrated in FIG. 1 are merely used as an illustration for explanation, and are not intended to limit the implementation manner of the present invention, and It can be adjusted as needed.

Since a user equipment can link the first evolved Node B 102 and/or the second evolved Node B 104 to obtain data and control services, in the context of small cells, the network 100 can configure the user equipment using the following three types:

1) The user equipment is only connected to the first evolved Node B 102 (tM type)

2) The user equipment simultaneously connects the first evolved Node B 102 and the second evolved Node B 104 (tMS type)

3) The user equipment is only connected to the second evolved Node B 104 (tS type)

When a user equipment has dual connectivity capabilities, the user equipment can be set to the tMS type. According to the LTE-A specification, when the user equipment has a dual connectivity capability, it can have split bears, that is, a part of the bearer content is transmitted via the first evolved Node B 102, and the content of the other part is via the second The evolved Node B 104 transmits. In other words, the tMS type user equipment can simultaneously receive data from one of the first evolved Node B 102 and the second evolved Node B 104. On the one hand, when the network load is not busy, the tMS type user equipment can enjoy a higher data rate than the tM type and the tS type user equipment. On the other hand, the existence of tMS type user equipment can also The first evolved Node B 102 is assisted in mitigating traffic by forwarding some traffic to the second evolved Node B 104. As such, by appropriately distributing the traffic of the tMS type user equipment to the second evolved Node B 104, the throughput of the network 100 can be increased.

In an embodiment consistent with the present invention, a two-layer data scheduling mechanism is provided, one level is a periodic traffic scheduling layer, and the other layer is an instantaneous traffic processing layer, and the first evolved Node B 102 can be at a periodic traffic scheduling level or instant. The traffic processing layer schedules traffic to the second evolved Node B 104. In one embodiment, when the network 100 is in a steady state, based on the traffic scheduling decision in the periodic traffic scheduling layer, the network 100 can achieve better throughput. On the other hand, when the network 100 is in a state of change, the second evolved Node B 104 may request to obtain more data traffic from the first evolved Node B 102 or reduce the data rate of the offloaded bearer in the instantaneous traffic processing layer. The two-level embodiment will be detailed in the following paragraphs.

Periodic traffic scheduling layer

Please refer to FIG. 2A and FIG. 2B. FIG. 2A is a schematic diagram showing an embodiment of the first evolved Node B 102 and the second evolved Node B 104 according to FIG. 1 , and FIG. 2B illustrates a first evolution consistent with an embodiment of the present application. An example of the flow of the traffic scheduling method of the Node B 102. The first evolved Node B 102 includes at least one estimation module 202 and one offload decision module 204. The second evolved Node B 104 includes at least one status reporting module 206. In the 3GPP/LTE scenario, it can be understood, but not limited thereto, that the estimation module 202, the offload decision module 204, and the status reporting module 206 can be respectively in the Radio Resource Control layer (Radio Resource Control layer). Packet Data Convergence Protocol layer and none Line links control the RLC layer (Radio Link Control layer) to complete their functions.

Referring to step S21, the first evolved Node B 102 generates an estimation result ER according to the measurement report of the plurality of user equipments. In more detail, the estimation module 202 of the first evolved Node B 102 can generate the estimation result ER according to the measurement report MR of the plurality of user equipments. In one embodiment, the partial measurement report is provided by the second evolved Node B 104, and the partial measurement report is provided by a portion of the user equipment.

Referring to step S22, the first evolved Node B 102 receives the status report SR from the second evolved Node B 104. In an embodiment, the status report module 206 may output the status report SR of the second evolved Node B 104 to the first evolved Node B 102, so that the first evolved Node B 102 can perform the offload decision according to the status report SR of the second evolved Node B 104. In another embodiment, the status report module 206 can report the buffer status information BSI and the signal quality value SQV of the tMS and tS type user equipment served by the second evolved Node B 104 to the status report module 206 to assist in the offloading decision. . In some embodiments, the buffer status information BSI displays associated data of at least one user equipment (first user equipment) that remains in the second evolved Node B 104 and is served by the second evolved Node B 104.

Referring to step S23, the first evolved Node B 102 may perform a offload decision according to the estimation result ER and the status report SR of the second evolved Node B 104 to schedule traffic to the second evolved Node B 104 through the backend network BH. In more detail, the offload decision module 204 of the first evolved Node B 102 can perform a split decision according to the estimation result ER and the status report SR to schedule traffic to the second play through the backend network BH. Advance to node B104. In addition to the estimation result ER and the status report SR, as shown in step S232 of FIG. 2C, in an embodiment, the shunt decision module 204 can further refer to the application traffic flow information (ATF) for traffic. Diversion decision.

In this level, the network 100 can configure the user equipment to periodically report their measurement results MR, and the estimation module 202 can perform estimation based on the data rate of the unit resources RB per unit of the user equipment. After the step S22 is performed, in an embodiment, as shown in step S234 of the 2D figure, the first evolved Node B 102 may perform the traffic offloading decision according to the estimation result ER and the status report SR periodically reported by the second evolved Node B 104. . In an embodiment, the network 100 can configure the user equipment in the following manner, measure and report to the first evolved Node B 102 or the second evolved Node B 104: tM-type user equipment, and measure the first evolved Node B 102 that serves it. The measurement report MR is periodically reported to the first evolved Node B 102.

The tMS type user equipment should measure its first evolved Node B 102 and the second evolved Node B 104, and periodically report the measurement report MR to the first evolved Node B 102.

The tS type user equipment should measure its second evolved Node B 104 and periodically report the measurement report MR to the second evolved Node B 104.

The above configuration may be transmitted by the first evolved Node B 102 to the user equipment via the LTE-A measurement control information. After receiving the measurement control information, the user equipment performs a measurement procedure conforming to the LTE-A Radio Resource Control (RRC) specification.

Since the tS-type user equipment is only served by the second evolved Node B 104 and is not served by the first evolved Node B 102, the measurement report MR of the tS-type user equipment is only reported to the second evolved Node B 104. The second evolved Node B 104 may transmit the measurement report MR received from the tS type user equipment to the first evolved Node B 102 to inform the first evolved Node B 102 tS type user equipment. Therefore, in some embodiments, the partial measurement report MR received by the estimation module 202 can be provided by the second evolved Node B 104.

In this aspect, the estimation module 202 determines the output data rate of the user equipment at the next interval according to the measured channel condition in the measurement report MR. Figure 3 of a line with the case illustrated embodiment, at time point Tl, Collocation module 202 based on the measurement report MR in the amount of measured channel conditions, determines the next time interval I _T output data rate of the user equipment . At the next time point T2, the estimation module 202 can repeat the operations stated above to update the output data rate of the user equipment. In some embodiments, the channel condition for the first evolved Node B 102 is measured by the amount of user equipment served by the first evolved Node B 102, and the channel condition for the second evolved Node B 104 is served by the second evolved Node B 104. User equipment is measured. Channel conditions may include, for example, but not limited to, channel parameters, signal to noise ratio SNR, transmission data rate, and channel selection in all communication service modes of the corresponding service base station, for example, first evolved Node B 102 or Two evolved Node B 104. A more detailed data rate estimation process will be explained in the following paragraphs.

For a user equipment u _i , at a point in time, we can use Q ^M ( u _i ), Q ^S ( u _i ) to construct the signal quality measurement report MR of the first evolved Node B 102 and the second evolved Node B 104, respectively. For a tS-type user equipment, such as u _i , for example, the first evolved Node B 102 can obtain its Q ^S ( u _i ) from the second evolved Node B 104. Since the wireless signal is independent in the time domain, the signal trend can be estimated from the history. In some embodiments, the estimation module 202 may be estimated by the measurement report MR of the user equipment u _i to estimate the first interval time of the first evolved Node B 102 or the second evolved Node B 104 by using one of the following exemplary solutions. The signal quality Q ^' ( u _i ) of the user equipment u _i .

1) Moving average: The moving average of the signal quality Q ^M ( u _i ) or Q ^S ( u _i ) is received as the estimated signal quality Q ^' ( u _i ) at a previous interval. Assuming that avg ( Q ^M ( u _i )) is the previous interval time average quality value and Q ^{M '} ( u _i ) is the last estimated value, the signal quality Q ^' estimated by the first evolved Node B 102 at the next interval time ( u _i ) can be obtained as follows: Q ^' ( u _i ) = α × avg ( Q ^M ( u _i )) + (1 - α ) × Q ^{M '} ( u _i ), where α is a predefined parameter and (0 α 1).

2) Exponential moving average: This scheme is similar to the previous moving average scheme, but α is set as an exponential function when it is built.

3) a moving average window type (window based moving average): the moving average with a different embodiment, the moving average of all programs included in the history push conjecture signal quality, the system of the reference embodiment this predefined time interval before a constant value W To calculate the Q ^' ( u _i ) value.

The signal quality Q ^' ( u _i ) estimated by the user equipment u _i can be converted by the function F(.) into the maximum allowable data rate per unit resource block RB. ( u _i ) or ( u _i ), where ( u _i ) is the data rate of the first evolved Node B 102, ( u _i ) is the data rate of the second evolved Node B 104. For example, the function F(.) can be determined by the network operator's adaptive modulation and coding (AMC) algorithm.

In this level, the first evolved Node B 102 configures its second evolved Node B 104 to periodically report status reports SR, including, for example, 1) buffer status information of tMS type and tS type user equipment, and/or 2) tS type. The measurement report MR of the user equipment. In an embodiment, the second evolved Node B 104 may report the channel status between the second evolved Node B 104 and the user equipment to the first evolved Node B 102 in response to the report configuration information transmitted by the first evolved Node B 102, and wherein the channel The condition is measured by the user equipment served by the second evolved Node B 104. As shown in FIG. 4 in accordance with an embodiment of the present invention, the two types of information are called, the information SenbStatusReportConfiguration and the information SenbStatusReportMessage are designed for use by the status reporting module. Initially, the first evolved Node B 102 configures its second evolved Node B 104 with the information SenbStatusReportConfiguration, and the second evolved Node B 104 then sets the corresponding field in the user equipment, and the information SenbStatusReportMessage is periodically transmitted to the first evolved Node B 102. In the information SenbStatusReportMessage, some user equipments may only report buffer status, some user equipments need to report measurement results, and some other user equipments are required to provide their bearer configuration. An embodiment of the first evolved Node B 102 and the second evolved Node B 104 processing the two information will be set forth in the following paragraphs.

When the second evolved Node B 104 is connected to the first evolved Node B 102, the first evolved Node B 102 configures the interval Reportlnterval to the second evolved Node B 104 with the information SenbStatusReportConfiguration, such that the second evolved Node B 104 returns the status with the information SenbStatusReportMessage at each interval Reportlnterval Report SR. When receiving the SenbStatusReportMessage information transmitted from the second evolved Node B 104 including the corresponding identification code SeNBld, the first evolved Node B 102 checks the user equipment carried in the information (assuming that the first evolved Node B 102 uses the corresponding identifier UEID to the user equipment u _i Do the work). If the first evolved Node B 102 finds that the user equipment u _i carries the (active flag, bearer, data rate) field, the active flag is checked. When the active flag is enabled, for example, the flag active flag=1, the first evolved Node B 102 records (bearer identification, data rate) information and sets the user equipment u _{i to} be tS type. Next, the first evolved Node B 102 records the mapping relationship of <bearer identification (ID) / UEID / SeNBld >. When the active flag is disabled, for example, the flag active flag=0, the first evolved Node B 102 removes the bearer ID information from the recorded <bearer ID/UEID/SeNBld> mapping relationship. If the MeasurementResult field exists, the first evolved Node B 102 records the measurement result of the user equipment u _i . And the first evolved Node B 102 uses the estimation module 202 to derive the output rate of the user equipment on the second evolved Node B 104. Then, the first evolved Node B 102 records the buffer status information of the user equipment u _i . As shown in FIG. 5, in accordance with an embodiment of the present invention, in step S52, the first evolved Node B 102 allocates an interval to the second evolved Node B with the first configuration information, so that the second evolved Node B transmits the time at each interval. Back to status report SR. In step S54, the first evolved Node B 102 checks the status report to record or remove the bearer information of the user equipment tS (second user equipment).

On the other hand, when the second evolved Node B 104 receives the information SenbStatusReportConfiguration, the second evolved Node B 104 sets the periodic report information SenbStatusReportMessage with the interval length Reportlnterval to the first evolved Node B 102. When the timer expires, the second evolved Node B 104 checks which user equipments are still connected to it.

In an embodiment, the information SenbStatusReportMessage may include a 3-yuan combination field, a MeasurementResult field, and a bufferStatus field. If the user equipment u _i is tS type and its bearer is changed, the second evolved Node B 104 may decide to join a new bearer or remove a bearer. If the user equipment u _i has a new bearer, the second evolved Node B 104 sets the 3-ary combination field to be (active flag=1, bearer identification ID, bearer data rate). If a bearer of the user equipment u _i has been removed, the second evolved Node B 104 sets the 3-ary combination field to be (active flag=0, bearer identification ID, 0).

If the user equipment u _i is of the tS type, the second evolved node B 104 may use the user equipment u _i at the interval Reportlnterval by the foregoing solution, for example, a moving average scheme, an exponential type moving average scheme, or a window type moving average scheme. The average value of the reported signal quality is entered in the MeasurementResult field. In addition, the second evolved Node B 104 may fill the total amount of remaining data of all bearers belonging to the user equipment u _i into the bufferStatus field.

Referring again to the embodiment of FIG. 2A, the split-flow module 204 reports the SR with the estimation result ER of the user equipment and the status provided by the second evolved Node B 104. Line splitting decisions. When a user equipment is tM type or tS type, the network 100 can configure the bearer according to the procedure in the LTE-A specification. When the tMS type user equipment is configured, the network 100 can simultaneously configure the user equipment to link the first evolved Node B 102 and the second evolved Node B 104 according to the procedure in the LTE-A specification. The first evolved Node B 102 may transmit reconfiguration information including an Information Element (IE) to the tMS type user equipment to notify the tMS type user equipment whether the corresponding bearer is offloaded. When a bearer is configured for a user equipment, the information element IE can be attached to the LTE-A information rrcConnectionReconfiguration.

Referring to FIG. 6 and FIG. 7 , FIG. 6 is a schematic diagram showing a flow of scheduling traffic between the first evolved Node B 102 and the second evolved Node B 104 according to an embodiment of the present disclosure. FIG. 7 is a diagram showing an example of configuring an information flow for a tMS type user equipment between a first evolved Node B 102 and a second evolved Node B 104 according to an embodiment of the present disclosure. In step S62, the first evolved Node B 102 transmits the first reconfiguration information including the information element IE to the third user equipment to notify the third user equipment whether the corresponding bearer is offloaded, wherein the at least one third user equipment is used by the second evolved node. B104 is served by the first evolved Node B 102 (i.e., tMS type user equipment). In step S64, the first evolved Node B 102 transmits the offloaded bearer information to the second evolved Node B 104 to notify the second evolved Node B 104 of the mapping relationship between the third user equipment and the corresponding bearer; and wherein the second evolved Node B 104 transmits the information element including The second reconfiguration information of the IE is sent to the third user equipment in response to the offloading bearer information, and the third user equipment mapping is correspondingly carried to the first evolved Node B 102 and the second evolved Node B 104.

As shown in FIG. 7, the first evolved Node B 102 transmits the offloaded bearer The information (ie, splitBearerInfo information) is sent to the second evolved Node B 104 to inform the second evolved Node B 104 of the mapping relationship between the user equipment and the corresponding bearer. In response to the offloading bearer information, the second evolved Node B 104 transmits the reconfiguration information (ie, rrcConnectionReconfiguration information) including the additional information element IE to the user equipment, so that the user equipment maps the corresponding bearer to the first evolved Node B 102 and the second evolved Node B 104. .

In the embodiment of Figure 7, the first evolved Node B 102 first transmits the information rrcConnectionReconfiguration, which includes an additional information element IE, such as SPLITED "IE, in the corresponding bearer field to the user equipment. When the user equipment receives the corresponding bearer field from the corresponding bearer field The information rrcConnectionReconfiguration of the first evolved Node B 102, the user equipment expects that it will receive another information rrcConnectionReconfiguration from the second evolved Node B 104. The first evolved Node B 102 transmits splitBearerInfo information to the second evolved Node B 104, the information including the UEID The mapping between the bearer ID and the bearer ID. When the splitBearerInfo information is received, the second evolved Node B 104 transmits the corresponding information rrcConnectionReconfiguration to the user equipment, and the information includes the □SPLITED" IE in the corresponding bearer field. When the user equipment receives the information rrcConnectionReconfiguration from the second evolved Node B 104, the user equipment records the <UEID/bearer ID/SeNBld> mapping of the offloaded bearer to its local database. After the foregoing configuration is completed, the shunt decision module 204 can begin to work based on certain network parameters and the values reported by the other two modules.

FIG. 8 is a diagram showing an example of a mapping relationship between a bearer, a user equipment, and a second evolved Node B 104 according to an embodiment of the present disclosure. In this example, there are multiple bearers labeled B = b ₁ , b ₂ ,..., b _n , multiple user equipments labeled U = u ₁ , u ₂ ,..., u _m and the indications A plurality of second evolved Node Bs of S = s ₁ , s ₂ , ..., s _k . According to the mapping relationship M ^U (.) between the bearer and the user equipment, the bearers b ₁ and b ₂ are assigned to the user equipments u ₁ and u _{2 respectively} , the bearers b ₃ and b ₄ are assigned to the user equipment u ₃ , and the bearers b ₅ and b ₆ are assigned to the user equipment u ₄ . The user equipments u ₁ and u ₃ are served by the second evolved Node B s ₁ according to the mapping relationship M ^S (.) between the user equipment and the second evolved Node B 104, and the user equipments u ₂ and u ₄ are used by the second evolved Node B s ₂ service.

FIG. 9 is a diagram showing an example of a traffic offloading mechanism between a first evolved Node B 102 and a second evolved Node B 104 according to an embodiment of the present disclosure. As shown in FIG. 9, the first evolved Node B 102 and the second evolved Node B 104 are configured according to the 3GPP standard conference, and have an RRC layer, a PDCP layer, an RLC layer, and a Media Accsss Control MAC layer.

The first evolved Node B 102 aggregates information reported from the second evolved Node B 104 (for example, including the signal quality of each tS type user equipment and the remaining data of each tS type and tMS type user equipment located in the second evolved Node B 104). The RRC layer of the first evolved Node B 102 aggregates the measurement report MR of the user equipment. After the measurement report MR is gathered, the first evolved Node B 102 can use the estimation module 202 to obtain the output data rate of all user equipments. ( u _i ) or ( u _i ) and report to the PDCP layer. The shunt decision module 204 located at the PDCP layer can refer to the application traffic flow information ATF. For example, in an embodiment, parameters such as R _in ( b ₁ ), R _in ( b ₂ ), ..., R _in ( b _n ) and R _bh ( s ₁ ), R _bh ( s ₂ )..., R _bh ( s _n ) perform flow splitting decision, ie calculate the split data rate R _sp ( b ₁ ), R _sp ( b ₂ ),..., R _sp ( b _n ), where R _in ( b ₁ ), R _in ( b ₂ ),..., R _in ( b _n ) are traffic flow parameters of the application layer, such as individual bearers Input data rate, and R _bh ( s ₁ ), R _bh ( s ₂ )..., R _bh ( s _n ) is the back-end network data rate from the first evolved Node B 102 to each of the second evolved Node Bs 104 , marked with S = s ₁ , s ₂ ,..., s _n .

The shunt decision module 204 can use a plurality of constraints to adjust the amount of data that all user devices can transmit or the radio resources available to all user devices (eg, channel bandwidth/transmission data rate). The restriction condition is established based on the estimation result ER and the status report SR of the second evolved Node B 104. FIG. 10 is a schematic diagram showing a flow of scheduling traffic between the first evolved Node B 102 and the second evolved Node B 104 according to an embodiment of the present disclosure. As shown in FIG. 10, in step S1002, a plurality of restriction conditions are established according to the status report SR of the second evolved Node B 104 and the estimation result ER. In step S1004, the first evolved Node B 102 adjusts the amount of data that all user equipments can transmit or the radio resources that all user equipment can use according to the restriction condition. In some applications, the shunt decision module 204 can use a number of constraints to, for example, maximize the amount of data that all user devices can transmit. The constraint can be expressed as follows: Target: max D ^M ( u _i )+ D ^S ( u _i )

1) For all bearers b _j B ^tMS , ; 2) for all user equipment u _i U , And ; 3) for each second evolved node B s _k S , ; 4) For the first evolved Node B, ; 5) for each second evolved node B s _k S ,

Under constraints 1 through 5, the objective function attempts to maximize the amount of data that can be transmitted by all user equipment (via the first evolved Node B 102 and the second evolved Node B 104) to optimize network traffic. In the constraint condition 1, when the bearer set B ^{tMS is} assigned to each bearer b _{j of the} tMS type user equipment, the split data rate R _sp ( b _j ) is smaller than the input data rate R _in ( b _j ) of the bearer b _j . ). In the constraint condition 2, the calculated output data rates D ^M ( u _i ) and D ^S ( u _i ) may not be greater than the input data amount of the user equipment at the first evolved Node B 102, that is, ( u _i )× I _t , and the amount of input data of the user equipment on the second evolved Node B 104, that is, ( u _i )× I _t , respectively adding the remaining data located in the first evolved Node B 102, that is, ( u _i ), and the remaining data located in the second evolved Node B 104, that is, ( u _i ), where D ^M ( u _i ) and D ^S ( u _i ) represent the total amount of data that the user equipment u _i can transmit during the time interval I _t . In the constraint 3, for the offloaded bearers that have been sent to the second evolved Node B s _k , the total amount of the split flow rate is not greater than the back end network capacity of the second evolved Node B s _k ( R _bh ( s _k )) . In the constraint condition 4, the resource block RB amount (located in the first evolved Node B 102) assigned to the user equipment is not greater than the maximum RB amount of the first evolved Node B 102 (ie, ). Constraints 4 5 similar constraints, constraints to 5, requires an amount of RB's assigned to the user equipment (the second service evolved node B s _k) is not greater than ( s _k ). The above construction method can be solved by any linear programming solution tool and R _sp ( b ₁ ), R _sp ( b ₂ ),..., R _sp ( b _n ) and RB ^M ( u ₁ ), RB ^M ( u ₂ ), ..., RB ^M ( u _m ), RB ^S ( u ₁ ), RB ^S ( u ₂ ), ..., RB ^S ( u _m ).

For example, the foregoing configuration may be extended to support a distributed bearer for a plurality of second evolved Node Bs 104. In this scenario, a user equipment can receive messages from more than two evolved Node Bs simultaneously. In an embodiment, FIG. 11 is a diagram showing an example of a mapping relationship between a bearer, a user equipment, and a second evolved Node B according to an embodiment of the present disclosure. In FIG. 11, the configuration bearers b ₁ and b ₂ are respectively branched to the second evolved nodes B s ₁ and s ₃ , and s ₂ and s ₃ . In this embodiment, the carriers b ₁ and b ₂ may be further divided into ( b _1-1 , b _1-2 ) and ( b _2-1 , b _2-2 ). The above scheme can also be applied to calculate scheduling decisions.

Immediate traffic processing layer

In this aspect, the first evolved Node B 102 dynamically schedules traffic to the second evolved Node B 104 in response to the traffic request information transmitted by the second evolved Node B 104.

FIG. 12 is a schematic diagram showing a flow of a traffic scheduling method in an instant traffic processing phase according to an embodiment of the present invention. As shown in FIG. 12, in step 1202, the first evolved Node B 102 dynamically performs a traffic offloading decision in response to the demand traffic information transmitted by the second evolved Node B 104 to schedule traffic to the second evolved Node B 102. In step 1204, the first evolved Node B 102 dynamically adjusts the traffic offloading decision in response to the demand traffic information transmitted by the second evolved Node B 104 to schedule traffic to the second evolved Node B 102. After periodically performing the traffic scheduling decision, the first evolved Node B 102 is based on the split data rate R _sp ( b _j ), where b _j B ^tMS , scheduling data in the ^offloading bearer. When the system is executing, the network traffic flow arrives at the first evolved Node B 102 in the form of a packet followed by a packet. The first evolved Node B 102 relays the bearer b _j packet to the second evolved Node B 104 to satisfy the requirement of the split data rate R _sp ( b _j ). When a split bearer b _j packet comes, the first evolved node B 102 checks whether the split data rate R _sp ( b _j ) has been satisfied. If not, the first evolved Node B 102 relays the packet to the second evolved Node B 104. Otherwise, the first evolved Node B 102 processes the packet itself.

In some embodiments, the offloaded bearer packet may not arrive so smoothly to the first evolved Node B 102, and the observed second evolved Node B 104 user equipment signal quality may be variability. In order to preserve network traffic, in this level, some tMS-type user equipments may request more data from the first evolved Node B 102 or request a slower data rate.

FIG. 13 is a diagram showing an example of information flow between a first evolved Node B and a second evolved Node B in an instant traffic processing phase according to an embodiment of the present invention. As shown in Figure 13, two information MenbDispatchDecision information and SenbTrafficRequestMessage information are designed to exchange scheduling decisions and traffic request information. After the scheduling decision is made, the first evolved Node B 102 fills in the information MinbDispatchDecision that the offloading decision is made in the bearer to prepare for the second evolved Node B 104. After performing for a while, if the second evolved Node B 104 finds that it has more capacity to serve more data, the information SenbTrafficRequestMessage is sent to the first evolved Node B 102 to request more traffic offloaded data, or to request to slow traffic flow.

For the second evolved Node B 104, denoted s _k , the first evolved Node B 102 finds that these tMS type user equipments are mapped to the second evolved Node B s _k . For the user equipments in the second evolved Node B s _k , the first evolved Node B 102 finds the offload bearer corresponding to the user equipment and fills in the determined split rate in the field of the information MenbDispatchDecision. The first evolved Node B 102 is then further attached The ( u _i ) value is in the information MenbDispatchDecision.

When the first evolved Node B 102 receives the information SenbTrafficRequestMessage and knows that a user equipment in the second evolved Node B s _k is in starvation, the first evolved Node B 102 is based on the restriction that the increase rate cannot exceed R _bh ( s _k ). The split ratio of the carrying b _j can be slowly increased, where M ^U ( b _j )= u _i . When the first evolved Node B102 receive the message and learned second evolution SenbTrafficRequeMessage a user equipment node B s _k has been satisfied in the first evolved Node B102 may check the signal quality of the first user equipment in an evolved Node B102 u _i of . If the signal quality of u _i is better than expected, the first evolved Node B 102 can relay less data to the second evolved Node B s _k .

On the other hand, when the second evolved Node B s _k receives the information MenbDispatchDecision, it will try to schedule the traffic of the corresponding bearer recorded in the information. For the tMS type user equipment u _i , the second evolved Node B s _k can know the expected resource block RB ( RB ^S ( u _i )) usable by the user equipment u _i and all upcoming bearer data rates (such as R _sp ( b _x ), R _sp ( b _y ),...). When performing traffic processing for the user equipment u _i , the second evolved node B s _k may be recorded Observing the user equipment u _i in ( u _i ) can transmit 1) the same amount of data as expected, 2) more data than expected, and 3) less information than expected.

In an embodiment, the second evolved Node B s _k can determine the state of the user equipment according to the following three tables (Tables 1 to 3):

Briefly, when the second evolved Node B s _k determines that the user equipment may need to request more information from the first evolved Node B 102, the second evolved Node B s _k sets the user equipment to be hungry. When the Node B s _k determines that the user equipment needs to reduce the data, the second evolved Node B s _k sets the user equipment to □ satiety. After a short time interval, the second evolved node B s _k can collect user equipment □ hunger "or satiated □", and transmits the information to the first SenbTrafficRequestMessage evolved Node B102.

Based on the above paragraphs, a data scheduling mechanism is provided and can be applied to a network including a first evolved Node B and a second evolved Node B. According to the various implementation examples provided by the present application, the first evolved Node B may perform the traffic offloading policy to offload the traffic to the second evolved node based on the measurement report of the user equipment and the status report of the second evolved Node B. B, thus increasing network traffic.

In summary, although the present invention has been disclosed above by way of example, it is not intended to limit the present invention. Those who have ordinary knowledge in the technical field of the present invention can make various changes and refinements without departing from the spirit and scope of the present case. Therefore, the scope of protection of this case is subject to the definition of the scope of the appended patent application.

102‧‧‧First Evolved Node B

104‧‧‧Second Evolved Node B

202‧‧‧ Estimation module

204‧‧‧Split Decision Module

206‧‧‧Status Reporting Module

MR‧‧‧Measurement report

ER‧‧‧ estimation results

SR‧‧‧ Status Report

BSI‧‧‧ Buffer Status Information

SQV‧‧‧ signal quality value

ATF‧‧‧App Traffic Traffic Information

Claims (36)

An evolved Node B in a network, the evolved Node B is a first evolved Node B connected to a second evolved Node B through a backend network, and the coverage of the second evolved Node B is at the first evolved Node B. The first evolved node B includes: an estimation module, and generates a estimation result according to the measurement report of the plurality of user equipments, wherein the partial measurement report is provided by the second evolved node B, and the partial quantity is The measurement report is provided by a part of the user equipment; and the distribution decision module performs a traffic offloading decision according to the estimation result and the status report of the second evolved Node B, to schedule traffic to the second node through the backend network connection B. The evolved node B of claim 1, wherein the estimation module determines an output data rate of the plurality of user equipments at a next interval according to the measured channel conditions in the measurement reports. The evolved Node B according to claim 1, wherein the plurality of user equipments comprise one or more first user equipments served by the second evolved Node B, the status report includes buffer status information, The buffer status information displays the associated data of at least one first user equipment that remains in the second evolved Node B. The evolved Node B as described in claim 3, wherein the one or more first user equipments comprise one or more second user equipments served by the second evolved Node B, the first evolved Node B Check the status report record or remove the one or Bearer information of multiple second user equipments. The evolved Node B according to claim 1, wherein the plurality of user equipments comprise at least one third user equipment served by the second evolved Node B and the first evolved Node B, and the first evolved Node B transmits the The first reconfiguration information of the information element is sent to the third user equipment to notify the third user equipment whether the corresponding bearer is offloaded. The evolved Node B, as described in claim 5, wherein the first evolved Node B transmits the offloaded bearer information to the second evolved Node B, to notify the second evolved Node B of the mapping of the at least one third user equipment and the corresponding bearer. Corresponding to the first evolved Node B, the second evolved Node B transmits the second reconfiguration information including the information element to the third user equipment, so that the third user equipment maps the corresponding bearer to the first evolved Node B and the second evolved node. B. The evolved Node B, as described in claim 1, wherein the offload decision module uses a plurality of restrictions to determine the amount of data that can be transmitted by all user equipments or the radio resources that can be used by all user equipments, wherein the second evolved node is used. The status report of B and the estimation result establish the plurality of restrictions. The egress node B according to claim 1, wherein the offload decision module performs the traffic offloading decision scheduling traffic to the second node B according to the estimation result and the status report of the second evolved Node B periodically. The evolved Node B, as described in claim 8, wherein the offload decision module dynamically adjusts the traffic offloading decision scheduling traffic to the second Node B in response to the traffic request information transmitted by the second evolved Node B. The evolved Node B, as described in claim 1, wherein the traffic distribution decision module dynamically performs the traffic offloading scheduling scheduling traffic to the second evolved Node B in response to the traffic request information transmitted by the second evolved Node B. For example, the evolved Node B described in claim 1 , wherein the split decision module is located at the packet data aggregation protocol layer, and refers to the application traffic flow information to perform the traffic offload decision. The evolved Node B according to claim 1, wherein the first evolved Node B is a Giant Cell Evolution Node B, and the second evolved Node B is a Small Cell Evolution Node B. The evolved Node B as described in claim 1, wherein when the second evolved Node B is connected to the first evolved Node B, the first evolved Node B configures the second evolved Node B with the first configuration information including the interval time. So that the second evolved Node B returns the status report at each of the intervals. The evolved Node B as described in claim 13 wherein the first evolved Node B checks the status report to remove or record bearer information of a user served by the second evolved Node B. A traffic scheduling method for a first evolved Node B in a network, comprising: generating a estimation result according to a measurement report of a plurality of user equipments, wherein part of the measurement report is connected to the first evolved Node B through a back-end network Provided by the second evolved Node B, and the partial measurement report is provided by a part of the user equipment, and wherein the coverage of the second evolved Node B is within the coverage of the first evolved Node B; from the second evolved Node B Receive status reports; And performing, according to the estimation result, the traffic offloading decision with the status report of the second evolved Node B, to schedule traffic to the second evolved Node B through a backend network connection. The traffic scheduling method of claim 15, wherein the step of generating the estimation result comprises: determining, according to the measured channel condition in the measurement reports, the multiple user equipments at a next interval. The output data rate. The traffic scheduling method according to claim 15, wherein the plurality of user equipments comprise one or more first user equipments served by the second evolved Node B, the status report includes buffer status information, The buffer status information displays the associated data of at least one first user equipment that remains in the second evolved Node B. The traffic scheduling method of claim 17, wherein the one or more first user equipments comprise one or more second user equipments served by the second evolved Node B, and the traffic scheduling method comprises: The status report is checked to record or remove bearer information of the one or more second user equipments. The traffic scheduling method according to claim 15, wherein the plurality of user equipments include at least one third user equipment served by the second evolved Node B and the first evolved Node B, and the traffic scheduling method includes: The first evolved Node B transmits the first reconfiguration information including the information element to the third user equipment to notify the third user equipment whether the corresponding bearer is offloaded. The traffic scheduling method according to claim 19, wherein the first evolved Node B transmits a offloaded bearer information to the second evolved Node B, Notifying the second evolved Node B that the at least one third user equipment is associated with the mapping of the corresponding bearer; wherein the second evolved Node B transmits the second reconfiguration information including the information element to the third user equipment, in response to the offloaded bearer information, The third user equipment mapping is correspondingly carried to the first evolved Node B and the second evolved Node B. The method for traffic scheduling according to claim 15 includes: using a plurality of restrictions to determine a quantity of data that can be transmitted by all user equipments or radio resources that are available to all user equipments, wherein the second evolved Node B The status report and the estimation result establish the plurality of restrictions. The traffic scheduling method according to claim 15 is characterized in that: the traffic offloading decision scheduling traffic is sent to the second node B according to the estimation result and the periodic report of the second evolved Node B. The traffic scheduling method according to claim 22, further comprising: dynamically adjusting the traffic offloading scheduling scheduling traffic to the second node B in response to the traffic request information transmitted by the second evolved Node B. The traffic scheduling method according to claim 15, wherein the method further comprises: dynamically performing the traffic offloading scheduling scheduling traffic to the second evolved Node B in response to the traffic request information transmitted by the second evolved Node B. For example, the traffic scheduling method described in claim 15 includes: referring to application traffic flow information to perform the traffic offloading decision. The traffic scheduling method according to claim 15, wherein the first evolved node B is a giant cell evolution node B, and the second evolved node B is a small cell. Enter node B. The traffic scheduling method of claim 15, the method comprising: configuring the second evolved Node B with the first configuration information including the interval, so that the second evolved Node B returns the state at each interval. report. The traffic scheduling method according to claim 27, wherein the checking includes: checking the status report to remove or record the bearer information of the user served by the second evolved Node B. An evolved Node B in a network, the evolved Node B is a second evolved Node B connected to the first evolved Node B through a backend network, and the coverage of the second evolved Node B is at the first evolved Node B. The second evolved node B includes: a status report module, and outputs an output status report to the first evolved node B, so that the first evolved node B performs a traffic offload decision according to the status report. The evolved Node B according to claim 29, wherein the status report includes buffer status information, and the buffer status information displays associated data of at least one user equipment that remains in the second evolved Node B, and A measurement report of one or more of the plurality of user equipments served by the second evolved Node B. The evolved Node B as described in claim 29, wherein the second evolved Node B periodically reports the status report to the first evolved Node B in response to the report configuration information transmitted by the first evolved Node B. An evolved Node B as described in claim 31, wherein the response is Reporting configuration information, the second evolved Node B reporting the channel status with the one or more user equipments to the first evolved Node B, wherein the channel status is by the one or more users served by the second evolved Node B The device is measured. The evolved Node B, as described in claim 31, wherein when the report configuration information is received, the second evolved Node B sets the time report to report the status report periodically, and when the time meter expires, the second The evolved Node B checks the one or more user equipments connected thereto and updates the bearer mapping of the one or more user equipments. The evolved Node B according to claim 29, wherein the second evolved Node B transmits the reconfiguration information to the one or more user equipments in response to the offloaded bearer information received from the first evolved Node B, so that the one Or one of the plurality of user equipments maps the offloading bearer to the first evolved Node B and the second evolved Node B. The evolved Node B, as described in claim 29, wherein the second evolved Node B transmits a traffic request message to the first evolved Node B, to request the first evolved Node B to adjust the traffic that is offloaded to the second evolved Node B. The evolved Node B according to claim 29, wherein the first evolved Node B is a Giant Cell Evolution Node B, and the second evolved Node B is a Small Cell Evolution Node B.