WO2016019789A1 - 一种承载接纳控制方法及装置 - Google Patents

一种承载接纳控制方法及装置 Download PDF

Info

Publication number
WO2016019789A1
WO2016019789A1 PCT/CN2015/084224 CN2015084224W WO2016019789A1 WO 2016019789 A1 WO2016019789 A1 WO 2016019789A1 CN 2015084224 W CN2015084224 W CN 2015084224W WO 2016019789 A1 WO2016019789 A1 WO 2016019789A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
bearer
evolved base
controlled
specific direction
Prior art date
Application number
PCT/CN2015/084224
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 US15/327,646 priority Critical patent/US10278115B2/en
Priority to EP15829693.9A priority patent/EP3179774B1/en
Publication of WO2016019789A1 publication Critical patent/WO2016019789A1/zh

Links

Images

Classifications

    • 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
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • H04W36/00695—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink using split of the control plane or user plane
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters

Definitions

  • the present disclosure relates to the field of communications technologies, and in particular, to a bearer admission control method and apparatus.
  • a network architecture for realizing cooperation/aggregation between Evolved NodeBs (eNBs) through non-ideal links is proposed.
  • eNBs Evolved NodeBs
  • MCG master cell group
  • MeNB master eNB
  • SRB Signaling Radio Bearer
  • DRB Data Radio Bearer
  • the other part of the same UE (including the SRB and the DRB) is on a secondary cell group (SCG) managed by a controlled eNB (Secondary eNB, SeNB).
  • SCG secondary cell group
  • SeNB controlled eNB
  • the uplink and downlink of the UE can be separately transmitted on the two eNBs. Due to the imbalance of uplink and downlink load, the eNB may only receive one uplink data or downlink in the case of congestion. In the case of the data, the current admission control cannot support the eNB to separately accept only one uplink data or downlink data of the bearer, so that the uplink and downlink data of the bearer is rejected as a whole.
  • a non-ideal data/signaling interface Xn interface (wired or wireless interface) is adopted between the MeNB and the SeNB, and the UE can work under the MeNB and the SeNB at the same time.
  • the MeNB may transfer part or all of the data/signaling of the UE to the SeNB to obtain the service provided by the SeNB according to signal strength or load balancing.
  • the UE can simultaneously use the resources of the MeNB and the SeNB, and the inter-base station aggregation (inter-eNB aggregation).
  • multiple RBs (Radio Bearers) of the UE may be respectively carried by a cell controlled by the MeNB (MCell) and a cell controlled by the SeNB (SCell).
  • the RB in which the SeNB is separated may include a DRB and/or an SRB. Since the SeNB is under the control of the MeNB, the SeNB can be considered as a controlled eNB, and the MeNB is a master eNB.
  • a bearer separation architecture is shown in FIG. 2.
  • the UE has independent bearers in the MeNB and the SeNB, and the UE has an independent Packet Data Convergence Protocol (PDCP) entity on each eNB.
  • PDCP Packet Data Convergence Protocol
  • the uplink and downlink bearer data of the same bearer are not simultaneously transmitted to the MeNB and the SeNB for transmission.
  • FIG. 3 Another bearer separation architecture is shown in FIG. 3.
  • the UE's connection on the MeNB may have independent bearers.
  • the connection of the UE in the SeNB is carried by the same Evolved Packet System (EPS) on the MeNB.
  • EPS Evolved Packet System
  • a part of the data is offloaded to the SeNB for transmission.
  • the EPS bearer PDCP entity is still in the MeNB, and the SeNB has an independent Radio Link Control (RLC) entity.
  • RLC Radio Link Control
  • the MeNB can control whether data is sent or sent in the SeNB or the MeNB (downstream bearer data offload).
  • the network can configure the uplink data transmission direction of the UE to transmit data only on the MeNB or the SeNB (the uplink bearer data is not split), or send data on the MeNB and the SeNB in a certain proportion (upstream bearer data offload). If the MeNB configures the transmission ratio of the uplink data of the UE, 50% of the uplink data is transmitted on the MCG, and 50% of the uplink data is transmitted on the SCG.
  • Radio Admission Control controls the establishment or rejection of a new radio bearer setup request.
  • the RAC needs to consider the overall resource situation on the network side, the quality of service (QoS) requirements of the new bearer, the QoS guarantee provided by the ongoing process, and the priority and overall QoS requirements of the system.
  • QoS quality of service
  • the purpose of the RAC is to ensure high radio resource utilization by accepting radio bearer setup requests and providing corresponding available radio resources.
  • the RAC can also ensure the QoS of the ongoing process by rejecting the radio bearer setup request.
  • the source eNB provides the target eNB with a list of (E-UTRAN Radio Access Bearer, E-RAB) bearers to be established in the HANDOVER REQUEST message.
  • E-RAB E-UTRAN Radio Access Bearer
  • the target eNB accepts these E-RABs in whole or in part according to their actual available resources.
  • HANDOVER REQUEST if the target eNB cannot accept any bearer in the handover request (HANDOVER REQUEST), it feeds back to the source eNB a handover preparation failure (HANDOVER PREPARATION FAILURE) message.
  • HANDOVER PREPARATION FAILURE handover preparation failure
  • the target eNB accepts part or all of the E-RAB, it feeds back to the source eNB a handover request acknowledgement (HANDOVER REQUEST ACKNOWLEDGE) message, which carries a list of accepted E-RABs and rejected Es. -a list of RABs, and the reason for the rejection.
  • HANDOVER REQUEST ACKNOWLEDGE handover request acknowledgement
  • the bearer is established.
  • the Mobile Management Entity sends an E-RAB SETUP REQUEST message to the eNB in the process of bearer establishment, and the message carries the E-RAB bearer that is to be established. list of.
  • the eNB accepts these E-RABs in whole or in part according to their actual available resources. If the eNB accepts part of the E-RAB or all E-RABs or rejects all E-RABs, it feeds back to the MME bearer setup response (E-RAB SETUP RESPONSE) message, which carries the accepted E-RAB List and list of rejected E-RABs, and the reason for the rejection.
  • E-RAB SETUP RESPONSE MME bearer setup response
  • one bearer of the UE will be connected under multiple eNBs at the same time, so when an eNB can only accept downlink data of the bearer or can only accept uplink data, the current eNB admission control The uplink and downlink of the bearer are all rejected, so that the UE can not enjoy the transmission rate increase caused by the separate uplink bearer separation or the separate downlink bearer separation, and the network side cannot implement load balancing caused by separate uplink or separate downlink bearer separation. Gain. In the case of heavy network load, the bearer or UE connection may be released.
  • Embodiments of the present disclosure provide a bearer admission control method, apparatus, and evolved base station, which are implemented in an eNB.
  • the admission control is performed, the uplink or downlink data is separately received, and the eNB can still provide the downlink data offload transmission service even when the uplink is congested, or the eNB can still provide the uplink data offload transmission service when the downlink is congested, thereby improving the UE and the UE.
  • the throughput on the network side reduces the probability of bearer release in the case of heavy network load.
  • the SeNB When the master evolved base station MeNB determines that the bearer separation needs to be performed for the same user equipment UE from the controlled evolved base station SeNB, the SeNB adds a request message to the SeNB, where the evolved universal corresponding to the UE that needs to be accepted by the SeNB is carried.
  • the radio access network of the terrestrial radio access network carries the E-RAB list information, and the indication information of whether the bearer data transmission is performed for the bearer in a specific direction, where the specific direction is an uplink direction or a downlink direction;
  • the MeNB receives the feedback message replied by the SeNB, and obtains the bearer admission result of the SeNB, and if the MeNB accepts the bearer admission result of the SeNB, the MeNB configures the connection of the UE; otherwise, The MeNB replies to the SeNB with a message rejecting accepting the bearer admission result of the SeNB.
  • the MeNB indicates whether the SeNB needs to perform offload data transmission for the bearer in the uplink direction or the downlink direction when the SeNB needs to perform bearer separation for the same UE.
  • the SeNB sends a message to the MeNB to indicate the bearer admission result, that is, the indication is accepted.
  • the uplink bearer or the downlink bearer can be implemented, so that the eNB can selectively receive the uplink bearer or the downlink bearer of the UE, and the uplink or downlink data is separately received when the eNB accepts the control, and the eNB can still provide the downlink even when the uplink is congested.
  • the data offloading transmission service, or the eNB can still provide the uplink data offload transmission service when the downlink is congested, thereby improving the throughput of the UE and the network side, and reducing the probability of the bearer release in the case of heavy network load.
  • the bearer admission result of the SeNB includes:
  • the data received by the SeNB in the specific direction of the UE is sent by the SeNB or the indication information sent by the MeNB;
  • the SeNB adds the request message, and further includes:
  • the bearer admission result of the SeNB includes: the SeNB determines a bearer in a specific direction that is accepted or rejected.
  • the bearer admission result of the SeNB further includes:
  • the data of the UE in the specific direction is Change information of the ratio transmitted on the SeNB.
  • the SeNB if the SeNB refuses to accept a bearer in a specific direction, the SeNB does not feed back, to the MeNB, a data transmission state of the UE in the specific direction.
  • the method further includes:
  • the MeNB receives a direction change request sent by the SeNB, where the direction change request is used to indicate that the bearer data transmission is not performed on the bearer in the specific direction, and the data of the specific direction of the UE is sent on the MeNB. Change information;
  • the MeNB configures the connection of the UE; otherwise, the MeNB returns a message rejecting the direction change request sent by the SeNB to the SeNB.
  • the method further includes:
  • the MeNB configures the connection of the UE; otherwise, the MeNB returns a message rejecting the change ratio request sent by the SeNB to the SeNB.
  • the controlled evolved base station SeNB receives the SeNB addition request message sent by the master evolved base station MeNB when it is determined that the SeNB needs to be separated from the same user equipment UE, and obtains the evolved universal corresponding to the UE that needs to be accepted by the SeNB.
  • the radio access network of the terrestrial radio access network carries the E-RAB list information, and the indication information of whether the bearer data transmission is performed for the bearer in a specific direction, where the specific direction is an uplink direction or a downlink direction;
  • the SeNB generates a bearer admission result according to the E-RAB list information and the indication information, and returns a feedback message to the MeNB, where the bearer admission result of the SeNB is carried.
  • the SeNB receives the indication information of whether the MeNB adds the SeNB to the bearer in the uplink direction or the downlink direction, and sends a message to the MeNB to indicate the bearer reception result. That is, the uplink or downlink bearer is received by the eNB, so that the eNB can selectively accept the uplink or downlink bearer of the UE, and the uplink or downlink data is separately received when the eNB accepts the control, even when the eNB is still in the uplink congestion.
  • the downlink data offload transmission service can be provided, or the eNB can still provide the uplink data offload transmission service when the downlink is congested, thereby improving the throughput of the UE and the network side, and reducing the probability of the bearer release in the case of heavy network load. .
  • the bearer acceptance result includes:
  • each bearer received by the SeNB is in the Determining, by the SeNB or the indication information sent by the MeNB, the data of the specific direction of the UE;
  • the SeNB adds the request message, and further includes:
  • the bearer admission result includes: the SeNB determines a bearer in a specific direction that is accepted or rejected.
  • the bearer acceptance result further includes:
  • the data of the specific direction of the UE is changed information of the proportion transmitted on the SeNB.
  • the SeNB if the SeNB refuses to accept a bearer in a specific direction, the SeNB does not feed back, to the MeNB, a data transmission state of the UE in the specific direction.
  • the method further includes:
  • the SeNB When it is determined that the bearer data transmission is not performed for the bearer in the specific direction, when the data of the specific direction of the UE needs to be changed and sent on the MeNB, the SeNB sends a direction change request to the MeNB, where For the case where the bearer in the specific direction does not perform offload data transmission, the data of the specific direction of the UE is sent on the MeNB.
  • the method further includes:
  • the data of the specific direction of the UE needs to change the proportion of the transmission on the MeNB and the ratio of the transmission on the SeNB, the SeNB Transmitting, by the MeNB, a change ratio request, where the bearer data transmission is performed on the bearer in the specific direction, where the data of the specific direction of the UE is sent on the MeNB and/or sent on the SeNB The change information of the ratio.
  • a SeNB adding unit configured to: when determining that the master evolved base station MeNB and the controlled evolved base station SeNB are to perform bearer separation for the same user equipment UE, send an SeNB addition request message to the SeNB, where the bearer needs to be accepted by the SeNB
  • a first determining processing unit configured to receive a feedback message that is sent by the SeNB, and obtain the If the bearer acceptance result of the SeNB is accepted, the connection of the UE is configured; otherwise, the SeNB is returned with a message rejecting the bearer admission result of the SeNB.
  • the SeNB When the device determines that the MeNB and the SeNB are required to perform the bearer separation for the same UE, the SeNB is instructed whether the SeNB performs the offload data transmission for the bearer in the uplink direction or the downlink direction, and the SeNB sends a message to the MeNB to indicate the bearer admission result, that is, the indication is accepted.
  • the uplink bearer or the downlink bearer can be implemented, so that the eNB can selectively receive the uplink bearer or the downlink bearer of the UE, and the uplink or downlink data is separately received when the eNB accepts the control, and the eNB can still provide the downlink even when the uplink is congested.
  • the data offloading transmission service, or the eNB can still provide the uplink data offload transmission service when the downlink is congested, thereby improving the throughput of the UE and the network side, and reducing the probability of the bearer release in the case of heavy network load.
  • the bearer admission result of the SeNB includes:
  • the data received by the SeNB in the specific direction of the UE is sent by the SeNB or the indication information sent by the MeNB;
  • the SeNB adds the request message, and further includes:
  • the bearer admission result of the SeNB includes: the SeNB determines a bearer in a specific direction that is accepted or rejected.
  • the bearer admission result of the SeNB further includes:
  • the data of the specific direction of the UE is changed information of the proportion transmitted on the SeNB.
  • the first determining processing unit is further configured to:
  • the SeNB If the direction change request sent by the SeNB is accepted, the connection to the UE is configured; otherwise, the SeNB is returned with a message rejecting the direction change request sent by the SeNB.
  • the first determining processing unit is further configured to:
  • the SeNB If the change ratio request sent by the SeNB is accepted, the connection to the UE is configured; otherwise, the SeNB is returned with a message rejecting the change ratio request sent by the SeNB.
  • the device further includes:
  • a controlled unit configured to receive an SeNB addition request message sent by the MeNB when it is determined that the SeNB needs to perform bearer separation for the same UE, and obtain E-RAB list information corresponding to the UE that needs to be accepted by the SeNB, and for a specific direction. And indicating, by the bearer, whether the specific direction is an uplink direction or a downlink direction;
  • the second determining processing unit is configured to generate a bearer admission result according to the E-RAB list information and the indication information, and send a feedback message to the MeNB, where the bearer admission result is carried.
  • a controlled unit configured to receive an SeNB addition request message that is sent by the master evolved base station MeNB when it is determined that the controlled evolved base station SeNB needs to perform bearer separation for the same user equipment UE, and obtains the UE corresponding to the UE that needs to be accepted by the SeNB.
  • the evolved universal terrestrial radio access network radio access bears the E-RAB list information, and the indication information of whether the bearer data transmission is performed for the bearer in a specific direction, where the specific direction is an uplink direction or a downlink direction;
  • the second determining processing unit is configured to generate a bearer admission result according to the E-RAB list information and the indication information, and send a feedback message to the MeNB, where the bearer admission result is carried.
  • the receiving MeNB sends the message indicating the bearer data transmission to the MeNB when the SeNB adds the SeNB to determine whether the bearer is to be separated from the SeNB for the same UE.
  • the bearer acceptance result includes:
  • the data received by the SeNB in the specific direction of the UE is sent by the SeNB or the indication information sent by the MeNB;
  • the SeNB adds the request message, and further includes:
  • the bearer admission result includes: the SeNB determines a bearer in a specific direction that is accepted or rejected.
  • the bearer acceptance result further includes:
  • the data of the specific direction of the UE is changed information of the proportion transmitted on the SeNB.
  • the second determining processing unit is further configured to:
  • the data of the specific direction of the UE needs to be changed to be sent on the MeNB, and a direction change request is sent to the MeNB, where In the case where the bearer in a specific direction does not perform offload data transmission, the data of the specific direction of the UE is changed information transmitted on the MeNB.
  • the second determining processing unit is further configured to:
  • the data of the specific direction of the UE needs to change the proportion of the transmission on the MeNB and the ratio of the transmission on the SeNB, to the MeNB. Transmitting a change ratio request, where carrying the offload data transmission for the bearer in the specific direction, the proportion of the specific direction data of the UE sent on the MeNB and/or the proportion sent on the SeNB Change information.
  • An evolved base station provided by an embodiment of the present disclosure includes: a processor and a transceiver; wherein
  • the evolved base station is the master evolved base station MeNB, and determining that the MeNB and the controlled evolved base station SeNB perform bearer separation for the same user equipment UE, generating an SeNB addition request message, where the bearer needs to be carried by the SeNB And the received information of the evolved universal terrestrial radio access network radio access bearer E-RAB list information, and the indication information of whether the bearer data transmission is performed in a specific direction, where the specific direction is uplink or downlink And triggering the transceiver to send the SeNB addition request message to the SeNB;
  • the processor obtains the bearer admission result of the SeNB, and if the bearer acceptance result of the SeNB is accepted, the connection of the UE is configured. And triggering the transceiver to send the configuration to the UE; otherwise, triggering the transceiver to reply to the SeNB with a message rejecting accepting the bearer admission result of the SeNB.
  • the SeNB When the evolved base station is used as the MeNB, when it is determined that the SeNB needs to be added to the same UE for the bearer separation, the SeNB is instructed whether the SeNB performs the offload data transmission for the bearer in the uplink direction or the downlink direction, and the SeNB sends a message to the MeNB to indicate the bearer admission result. That is, the uplink bearer or the downlink bearer is received, so that the eNB can selectively accept the uplink bearer or the downlink bearer of the UE, and the uplink or downlink data is separately received when the eNB accepts the control, even when the uplink is congested.
  • the eNB can still provide the uplink data offload transmission service, thereby improving the throughput of the UE and the network side, and reducing the probability of the bearer release in the case of heavy network load.
  • the bearer admission result of the SeNB includes:
  • the data received by the SeNB in the specific direction of the UE is sent by the SeNB or the indication information sent by the MeNB;
  • the SeNB adds the request message, and further includes:
  • the bearer admission result of the SeNB includes: the SeNB determines a bearer in a specific direction that is accepted or rejected.
  • the bearer admission result of the SeNB further includes:
  • the data of the specific direction of the UE is changed information of the proportion transmitted on the SeNB.
  • the transceiver is further configured to receive a direction change request sent by the SeNB, where the direction change request is used to indicate that the bearer data transmission is not performed for the bearer in the specific direction, the specific Change information sent by the direction data on the MeNB;
  • the processor is further configured to: if the direction change request sent by the SeNB is received, configure a connection of the UE, and trigger the transceiver to send the configuration to the UE; otherwise, trigger the sending and receiving The messenger replies to the SeNB with a message rejecting the direction change request sent by the SeNB.
  • the transceiver is further configured to receive a change ratio request sent by the SeNB, where the change ratio request is used to indicate a situation in which the bearer data transmission is performed on the bearer in the specific direction, the specific direction of the UE Change in the proportion of data transmitted on the MeNB and/or the proportion of transmissions on the SeNB;
  • the processor is further configured to: if the change ratio request sent by the SeNB is received, configure a connection of the UE, and trigger the transceiver to send the configuration to the UE; otherwise, trigger the sending and receiving The messenger replies to the SeNB with a message rejecting the change ratio request sent by the SeNB.
  • the transceiver is further configured to: when the evolved base station is used as the SeNB, receive an SeNB add request message that is sent by the MeNB when it is determined that the SeNB needs to perform bearer separation for the same UE;
  • the processor is further configured to: obtain, from the SeNB add request message, the UE corresponding to the UE that needs to be accepted by the SeNB.
  • triggering the transceiver to reply a feedback message to the MeNB, where the bearer admission result is carried.
  • An evolved base station provided by an embodiment of the present disclosure includes: a processor and a transceiver; wherein
  • the transceiver When the evolved base station is used as the SeNB, the transceiver receives an SeNB addition request message that is sent by the MeNB when it is determined that the SeNB needs to perform bearer separation for the same UE;
  • the processor obtains the E-RAB list information corresponding to the UE that is to be accepted by the SeNB, and the indication information about whether the bearer in the specific direction performs the offload data transmission, where the specific direction is the uplink direction. Or a downlink direction; generating, according to the E-RAB list information and the indication information, a bearer admission result, and triggering the transceiver to reply a feedback message to the MeNB, where the bearer admission result is carried.
  • the receiving MeNB When the evolved base station is used as the SeNB, the receiving MeNB, when it is determined that the SeNB needs to be added to the same UE for the bearer separation, whether to perform the offload data transmission indication information on the bearer in the uplink direction or the downlink direction, and send a message indication to the MeNB.
  • the bearer admission result that is, the indication is that the uplink bearer or the downlink bearer is received, so that the eNB can selectively accept the uplink bearer or the downlink bearer of the UE, so that the uplink or downlink data is separately received when the eNB accepts the control, even if the uplink is congested.
  • the eNB can still provide the downlink data offload transmission service, or the eNB can still provide the uplink data offload transmission service when the downlink is congested, thereby improving the throughput of the UE and the network side, and reducing the network load under heavy load. The probability of carrying a release.
  • the bearer acceptance result includes:
  • the data received by the SeNB in the specific direction of the UE is sent by the SeNB or the indication information sent by the MeNB;
  • the SeNB adds the request message, and further includes:
  • the bearer admission result includes: the SeNB determines a bearer in a specific direction that is accepted or rejected.
  • the bearer acceptance result further includes:
  • the data of the specific direction of the UE is changed information of the proportion transmitted on the SeNB.
  • the processor is further configured to: when it is determined that the bearer data transmission is not performed for the bearer in the specific direction, where the data of the specific direction of the UE needs to be changed and sent on the MeNB, triggering the The transceiver sends a direction change request to the MeNB, where the bearer data transmission is not performed for the bearer in the specific direction, and the change information sent by the specific direction data of the UE on the MeNB.
  • the processor is further configured to: when determining, for the offload data transmission, for the bearer in the specific direction, the data of the specific direction of the UE needs to change the proportion of the transmission on the MeNB and When the ratio is sent by the SeNB, the transceiver is triggered to send a change ratio request to the MeNB, where the bearer data transmission is performed on the bearer in the specific direction, where the data of the specific direction of the UE is in the The ratio of transmissions on the MeNB and/or the change information of the proportions transmitted on the SeNB.
  • FIG. 1 is a schematic structural diagram of a network scenario of bearer separation in the prior art
  • FIG. 2 is a schematic diagram of a bearer separation architecture in the prior art
  • FIG. 3 is a schematic diagram of another bearer separation architecture in the prior art
  • FIG. 4 is a schematic diagram of a handover process between a source eNB and a target eNB in the prior art
  • FIG. 5 is a schematic diagram of a handover process between another source eNB and a target eNB in the prior art
  • FIG. 6 is a schematic diagram of a bearer setup process of a non-handover process in the prior art
  • FIG. 7 is a schematic flowchart of an admission control method according to Embodiment 1 of the present disclosure.
  • FIG. 8 is a schematic flowchart diagram of an admission control method according to Embodiment 2 of the present disclosure.
  • FIG. 9 is a schematic flowchart diagram of an admission control method according to Embodiment 3 of the present disclosure.
  • FIG. 10 is a schematic flowchart diagram of an admission control method according to Embodiment 4 of the present disclosure.
  • FIG. 11 is a schematic flowchart of an admission control method according to Embodiment 5 of the present disclosure.
  • FIG. 12 is a schematic flowchart diagram of an admission control method according to Embodiment 6 of the present disclosure.
  • FIG. 13 is a schematic flowchart diagram of an admission control method according to Embodiment 7 of the present disclosure.
  • FIG. 14 is a schematic flowchart diagram of an admission control method according to Embodiment 8 of the present disclosure.
  • FIG. 16 is a schematic flowchart of an admission control method on a MeNB side according to an embodiment of the present disclosure
  • FIG. 17 is a schematic flowchart of an admission control method on an SeNB side according to an embodiment of the present disclosure.
  • FIG. 18 is a schematic structural diagram of a receiving control apparatus according to an embodiment of the present disclosure.
  • FIG. 19 is a schematic structural diagram of another receiving control apparatus according to an embodiment of the present disclosure.
  • FIG. 20 is a schematic structural diagram of an evolved base station according to an embodiment of the present disclosure.
  • the embodiments of the present disclosure provide a bearer admission control method, an apparatus, and an evolved base station, which are configured to separately receive uplink or downlink data when the eNB accepts control, even when the uplink congestion occurs, the eNB can still provide downlink data offload transmission.
  • the eNB can still provide uplink data offload transmission service when the downlink is congested, thereby improving the throughput of the UE and the network side, and reducing the probability of bearer release in the case of heavy network load.
  • the eNB selectively accepts an uplink bearer or a downlink bearer of the UE when performing the admission control.
  • the controlled eNB sends a message to the master eNB indicating that the uplink or downlink of the bearer is accepted.
  • the controlled eNB sends a message to the master eNB requesting to change the direction or proportion of the bearer uplink or downlink data transmission.
  • the master eNB feeds back whether the request is accepted.
  • the uplink data transmission direction in the following embodiments of the present disclosure refers to the uplink data sent by the MeNB or the SeNB.
  • the downlink data transmission direction refers to the downlink data sent by the MeNB or the SeNB.
  • Embodiment 1 SeNB adding procedure for adding an SeNB (for an uplink bearer, the MeNB does not provide a SMC data transmission direction or ratio, and the SeNB determines a direction or a ratio).
  • an admission control method provided by this embodiment includes:
  • Step 701 After determining that the bearer is to be separated, the MeNB sends a message (for example, a SeNB Addition Request message) to the SeNB, where the E-RAB list information that is desired to be separated by the SeNB is carried.
  • the MeNB informs the SeNB whether to perform offload data transmission for the uplink bearer.
  • the MeNB does not indicate whether the uplink data is transmitted on the MeNB or on the SeNB.
  • the MeNB does not indicate the proportion of uplink data transmitted on the MeNB and transmitted on the SeNB.
  • Step 702 After receiving the message in step 701, the SeNB determines whether the uplink data of the bearer in the E-RAB list can be accepted or rejected, and the SeNB distinguishes between the bearer with uplink data transmission and the bearer without uplink data transmission, and The uplink admission result and the configuration of the bearer are sent to the MeNB (for example, the bearer admission result is sent to the MeNB by using a SeNB Addition Request Acknowledge message).
  • the SeNB indicates the proportion of the uplink data transmitted on the MeNB and transmitted on the SeNB.
  • the SeNB may provide other auxiliary information (such as load conditions on the SeNB, etc.) to assist the MeNB in subsequent decisions.
  • Step 703 After receiving the bearer admission result of the SeNB, the MeNB determines whether to accept the bearer admission result of the SeNB. If yes, if the MeNB needs to configure the connection of the UE, the MeNB may receive the bearer according to the SeNB received in step 702. The result (including the bearer configuration of the SeNB, the uplink data transmission direction or the proportion of the bearer), configures the connection of the UE (for example, by RRC Connection Reconfiguration message). If the MeNB is unable to accept the bearer admission result of the SeNB, the MeNB may feed back a message rejecting the bearer admission result of the SeNB by step 705 (the RRC Connection Reconfiguration message is not sent to the UE at this time). When the SeNB rejects the admission in the uplink direction of the bearer, the SeNB and the MeNB can still maintain the downlink data of the bearer for offload transmission on the SeNB.
  • the result including the bearer configuration of the SeNB, the uplink data transmission direction or the proportion of the bearer
  • Step 704 The UE performs connection configuration according to the message received from the MeNB in step 703, and feeds back the completion message to the MeNB after the configuration is successful, for example, feedback RRC connection reconfiguration is completed (RRC Connection Reconfiguration). Complete) message to the MeNB.
  • Step 705 According to the feedback of step 704, the MeNB sends the completion result of the air interface configuration to the SeNB (for example, the SeNB Reconfiguration Complete message is sent to the SeNB by the SeNB Reconfiguration Complete message), and the result may include the UE final. Air interface configuration information. Or according to the determination of step 703, the MeNB sends a message rejecting the bearer admission result of the SeNB to the SeNB.
  • the SeNB Reconfiguration Complete message is sent to the SeNB by the SeNB Reconfiguration Complete message
  • the result may include the UE final. Air interface configuration information.
  • the MeNB sends a message rejecting the bearer admission result of the SeNB to the SeNB.
  • the signaling sent by the MeNB to the SeNB in step 701 is a SeNB Modification Request
  • the signaling sent by the SeNB to the MeNB in step 702 is the SeNB modification request confirmation. (SeNB Modification Request Acknowledge), but the bearer admission related information included in the signaling is the same as the SeNB adding procedure, and the description is not repeated.
  • Embodiment 2 SeNB adding procedure for adding an SeNB (for an uplink bearer, the MeNB provides a SeNB data transmission direction or ratio, and the SeNB does not reject the direction or proportion).
  • an admission control method provided by this embodiment includes:
  • Step 801 When the MeNB decides to perform bearer separation, the MeNB sends a message (for example, a “SeNB Addition Request” message) to the SeNB, where the E-RAB list information that is desired to perform bearer separation in the SeNB is carried.
  • the MeNB informs the SeNB whether to perform offload data transmission for the uplink bearer. For the case where the uplink bearer transmits data without shunting, the MeNB indicates whether the uplink data is transmitted on the MeNB or transmitted on the SeNB. For the case where the uplink bearer transmits the data by the offload, the MeNB indicates the proportion of the uplink data transmitted on the MeNB and transmitted on the SeNB.
  • Step 802 After the SeNB receives the message in step 801, if the uplink bearer is not split in the step 801, the MeNB indicates that the uplink data is sent on the SeNB, or in the case of the uplink bearer offload, the MeNB instructs the uplink data to be sent on the MeNB.
  • the SeNB determines which bearer uplink data can be received or rejected, and the SeNB divides the bearer into two types, one is a bearer with uplink data transmission, and the other is a bearer without uplink data transmission, and the SeNB targets Each type of bearer is configured separately, and the SeNB sends the uplink admission result and the configuration of the bearer as the bearer admission result of the SeNB to the MeNB (for example, through a “SeNB Addition Request Acknowledge” message).
  • the SeNB may also provide other auxiliary information (such as load conditions on the SeNB, etc.) to assist the MeNB in subsequent decisions.
  • Step 803 After receiving the bearer admission result of the SeNB, the MeNB determines whether to accept the bearer admission result of the SeNB. If yes, if the MeNB needs to configure the connection of the UE, the MeNB may receive the bearer according to the SeNB received in step 802. As a result, the bearer configuration of the SeNB is included, and the connection of the UE is configured (for example, by using an RRC Connection Reconfiguration message), and the uplink data transmission of the UE may be modified according to the bearer admission result of the SeNB in step 802. Direction or proportion, for example, for an uplink bearer that is not accepted by the SeNB, the MeNB may modify the uplink data of the bearer to be sent by the MeNB.
  • the MeNB may modify the uplink data of the bearer to be sent by the MeNB.
  • step 805 is executed to send a message rejecting the bearer admission result of the SeNB to the SeNB.
  • the MeNB may choose not to separate the bearer to the SeNB or select to release the bearer when configuring the UE.
  • the SeNB and the MeNB can still keep the downlink data transmitted on the SeNB.
  • Step 804 The UE performs connection configuration according to the message received from the MeNB in step 803, and feeds back the completion message to the MeNB after the configuration is successful, for example, feeding back an RRC Connection Reconfiguration Complete message to the MeNB.
  • Step 805 According to the feedback of step 804, the MeNB sends the completion result of the air interface configuration to the SeNB (for example, the SeNB Reconfiguration Complete message is sent to the SeNB by the SeNB Reconfiguration Complete message), and the result may include the UE final. Air interface configuration information. Or according to the judgment of step 803, the MeNB sends a message rejecting the bearer admission result of the SeNB to the SeNB.
  • the SeNB Reconfiguration Complete message is sent to the SeNB by the SeNB Reconfiguration Complete message
  • the result may include the UE final. Air interface configuration information.
  • the MeNB sends a message rejecting the bearer admission result of the SeNB to the SeNB.
  • the signaling sent by the MeNB to the SeNB in step 801 is “SeNB Modification Request”, and the signaling sent by the SeNB to the MeNB in step 802 is “SeNB Modification Request Acknowledge”.
  • the bearer admission related information included in the signaling is the same as the SeNB adding process, and the description is not repeated.
  • Embodiment 3 SeNB adding procedure, for adding an SeNB (for an uplink bearer, a MeNB provides a SeNB data transmission direction or proportion, and the SeNB rejects a data transmission direction or a ratio that the MeNB provides to the SeNB).
  • an admission control method provided by this embodiment includes:
  • Step 901 After deciding to perform bearer separation, the MeNB sends a message (for example, a SeNB Addition Request message) to the SeNB, where the E-RAB list information that is required to perform bearer separation in the SeNB is carried.
  • the MeNB informs the SeNB whether to perform offload data transmission for the uplink bearer. For the case where the uplink bearer transmits data without splitting, the MeNB indicates whether the uplink data is transmitted on the MeNB or on the SeNB. For the case where the uplink bearer transmits the data by the offload, the MeNB indicates the proportion of the uplink data transmitted on the MeNB and transmitted on the SeNB.
  • Step 902 After the SeNB receives the message in step 901, if the MeNB indicates that the uplink data is sent on the SeNB, or the uplink bearer offload, the MeNB instructs the uplink data to be sent on the MeNB in the case that the uplink bearer is not split in step 901.
  • the SeNB determines the number of uplink data that can be received by the SeNB. The SeNB distinguishes between the bearer with uplink data transmission and the bearer with no uplink data transmission.
  • the SeNB changes the uplink data to be transmitted by the MeNB when the uplink bearer data is not split, and the SeNB changes the transmission ratio of the uplink data when the uplink bearer data is split, and configures the bearer and the SeNB.
  • the bearer admission result is sent to the MeNB (for example, the bearer admission result is sent to the MeNB through a SeNB Addition Request Acknowledge message).
  • the SeNB may provide other auxiliary information (such as load conditions on the SeNB, etc.) to assist the MeNB in subsequent decisions.
  • Step 903 After receiving the bearer admission result of the SeNB, the MeNB determines whether to accept the bearer admission result of the SeNB. If yes, if the MeNB needs to configure the connection of the UE, the MeNB may receive the bearer according to the SeNB received in step 902. The result of the admission, including the bearer configuration of the SeNB and the direction or proportion of the uplink data transmission of the bearer, configures the connection of the UE (eg, "RRC Connection Reconfiguration" message). If the MeNB is unable to accept the bearer admission result of the SeNB, the MeNB may feed back a message rejecting the bearer admission result of the SeNB by step 905 (the RRC Connection Reconfiguration message is not sent to the UE at this time). When the uplink direction of the bearer is rejected by the SeNB, the SeNB and the MeNB can still keep the downlink data of the bearer transmitted on the SeNB.
  • the result of the admission including the bearer configuration of the SeNB and the direction or proportion of the uplink data transmission of the
  • Step 904 The UE performs connection configuration according to the message received from the MeNB in step 903, and feeds back the completion message to the MeNB after the configuration is successful, for example, feeding back an "RRC Connection Reconfiguration Complete" message to the MeNB.
  • Step 905 According to the feedback of step 904, the MeNB sends the completion result of the air interface configuration to the SeNB (for example, the SeNB Reconfiguration Complete message is sent to the SeNB by the SeNB Reconfiguration Complete message), and the result may include the UE final. Air interface configuration information. Or according to the judgment of step 903, the MeNB sends a message rejecting the bearer admission result of the SeNB to the SeNB.
  • the SeNB for example, the SeNB Reconfiguration Complete message is sent to the SeNB by the SeNB Reconfiguration Complete message
  • the result may include the UE final.
  • Air interface configuration information Or according to the judgment of step 903, the MeNB sends a message rejecting the bearer admission result of the SeNB to the SeNB.
  • the signaling sent by the MeNB to the SeNB in step 901 is “SeNB Modification Request”, and the signaling sent by the SeNB to the MeNB in step 902 is “SeNB Modification Request Acknowledge”.
  • the bearer admission related information included in the signaling is the same as the SeNB adding process, and the description is not repeated.
  • Embodiment 4 The SeNB modification process is used to modify the UE configuration on the SeNB (the uplink bearer is not split, and the SeNB initiates the reject direction request).
  • an admission control method provided by this embodiment includes:
  • Step 101 In the case that the uplink bearer does not transmit the data, the SeNB sends an uplink data transmission direction change request to the MeNB when the uplink data transmission direction of the bearer needs to be changed to the MeNB (for example, when uplink congestion occurs) (for example, The change is sent by the MeNB to the uplink data, and is transmitted to the MeNB in a bearer configuration in which the uplink data transmission direction is changed (for example, a SeNB Modification Required message).
  • the SeNB may provide other auxiliary information (such as load conditions on the SeNB, etc.) to assist the MeNB in subsequent decisions.
  • Step 102 After receiving the uplink data transmission direction change request of the SeNB received by the MeNB, determine whether to accept the uplink data transmission direction change request of the SeNB, and if yes, if the MeNB needs to configure the connection of the UE, according to the received In step 101, the uplink data transmission direction change request of the SeNB configures the connection of the UE (for example, by "RRC Connection Reconfiguration" message). If the MeNB cannot accept the uplink data transmission direction change request of the SeNB, the MeNB may, in step 104, feed back a message rejecting the direction change request transmitted by the SeNB. When the uplink of the bearer is rejected by the SeNB, the SeNB and the MeNB can still keep the downlink data transmitted on the SeNB.
  • Step 103 The UE performs connection configuration according to the message received from the MeNB in step 102, and feeds back the completion message to the MeNB after the configuration is successful (for example, through an "RRC Connection Reconfiguration Complete" message).
  • Step 104 According to the feedback of step 103, the MeNB sends the completion result of the air interface configuration to the SeNB (for example, sends a “SeNB Modification Complete” message), and the result may include the final air interface configuration information of the UE. Or, according to the determination in step 102, the MeNB sends a message to the SeNB whether to reject the direction change request sent by the SeNB.
  • Embodiment 5 The SeNB modification process is used to modify the UE configuration on the SeNB (the uplink bearer offload, and the SeNB initiates the change of the uplink data transmission ratio request).
  • an admission control method provided by this embodiment includes:
  • Step 111 In the case that the uplink bearer transmits the data, the SeNB sends the uplink data transmission proportion change request of the bearer to the MeNB when the uplink data transmission ratio of the bearer needs to be changed (for example, when uplink congestion occurs) (for example, sending a new packet)
  • the uplink data transmission ratio is transmitted to the MeNB, and the bearer configuration after the uplink data transmission ratio is changed (for example, by "SeNB Modification Required" message transmission).
  • the SeNB may provide other auxiliary information (such as load conditions on the SeNB, etc.) to assist the MeNB in subsequent decisions.
  • Step 112 After receiving the uplink data transmission ratio change request of the SeNB, the MeNB determines whether to accept the uplink data transmission ratio change request of the SeNB. If yes, if the MeNB needs to configure the connection of the UE, the MeNB may follow the received procedure. The uplink data transmission ratio change request of the SeNB in 111 configures the connection of the UE (for example, by "RRC Connection Reconfiguration" message). If the MeNB cannot accept the uplink data transmission ratio change request of the SeNB in step 111, the MeNB may feed back the message rejecting the uplink data transmission ratio change request of the SeNB in step 114.
  • the uplink data transmission ratio change request of the SeNB in 111 configures the connection of the UE (for example, by "RRC Connection Reconfiguration" message). If the MeNB cannot accept the uplink data transmission ratio change request of the SeNB in step 111, the MeNB may feed back the message rejecting the uplink data transmission ratio change request of the SeNB in step 114.
  • Step 113 The UE performs connection configuration according to the message received from the MeNB in step 112, and feeds back the completion message to the MeNB after the configuration is successful (for example, sends an “RRC Connection Reconfiguration Complete” message).
  • Step 114 According to the feedback of step 113, the MeNB sends the completion result of the air interface configuration to the SeNB (for example, sends a “SeNB Modification Complete” message to the SeNB), and the result may include the final air interface configuration information of the UE. Or, according to the determination in step 112, the MeNB sends a message rejecting the uplink data transmission ratio change request of the SeNB to the SeNB.
  • Embodiment 6 SeNB adding process, for adding SeNB (downlink bearer, MeNB does not provide data transmission direction to SeNB, SeNB determines data transmission direction)
  • an admission control method provided in this embodiment includes:
  • Step 121 After deciding to perform bearer separation, the MeNB sends a message (for example, sends a “SeNB Addition Request” message) to the SeNB, where the E-RAB list information that is desired to be separated by the SeNB is carried. For the downlink bearer data offload transmission situation, the MeNB notifies the SeNB whether to perform offload data transmission for the downlink bearer.
  • a message for example, sends a “SeNB Addition Request” message
  • Step 122 After the SeNB receives the message in step 121, the SeNB determines which bearer downlink data can be accepted or rejected.
  • the SeNB divides the bearer into two types, one is a bearer with uplink data transmission, and the other is no uplink data transmission.
  • the SeNB configures each type of bearer separately, and the SeNB sends the downlink admission result and the configuration of the bearer as the bearer admission result of the SeNB to the MeNB (for example, sends a “SeNB Addition Request Acknowledge” message).
  • the SeNB does not perform related feedback on the downlink data transmission of the bearer to the MeNB, for example, the SeNB does not periodically feed back the downlink data buffer status of the bearer.
  • the SeNB may provide other auxiliary information (such as load conditions on the SeNB, etc.) to assist the MeNB in subsequent decisions.
  • Step 123 After receiving the bearer admission result of the SeNB, the MeNB determines whether to accept the bearer admission result of the SeNB. If yes, if the MeNB needs to configure the connection of the UE, the MeNB may receive the bearer according to the SeNB received in step 122. The result, including the bearer configuration of the SeNB, configures the connection to the UE (eg, "RRC Connection Reconfiguration" message). Subsequently, the MeNB does not send downlink data of the bearer to the SeNB for the downlink bearer that is not accepted.
  • the MeNB determines whether to accept the bearer admission result of the SeNB. If yes, if the MeNB needs to configure the connection of the UE, the MeNB may receive the bearer according to the SeNB received in step 122. The result, including the bearer configuration of the SeNB, configures the connection to the UE (eg, "RRC Connection Reconfiguration" message). Subsequently, the MeNB does not send downlink data of the bearer to the SeNB
  • the MeNB can pass Step 125 feeds back a message rejecting the bearer admission result of the SeNB (the RRC Connection Reconfiguration message is not sent to the UE at this time).
  • the SeNB and the MeNB can still keep the uplink data of the bearer transmitted on the SeNB.
  • Step 124 The UE performs connection configuration according to the message received from the MeNB in step 123, and feeds back the completion message to the MeNB after the configuration is successful (for example, feedback "RRC Connection Reconfiguration Complete” message).
  • Step 125 According to the feedback of step 124, the MeNB sends the completion result of the air interface configuration to the SeNB (for example, a feedback "SeNB Reconfiguration Complete" message), and the result may include the final air interface configuration information of the UE. Or according to the judgment of step 123, the MeNB sends a message rejecting the bearer admission result of the SeNB to the SeNB.
  • the SeNB for example, a feedback "SeNB Reconfiguration Complete" message
  • the MeNB sends a message rejecting the bearer admission result of the SeNB to the SeNB.
  • the signaling sent by the MeNB to the SeNB in step 121 is “SeNB Modification Request”, and the signaling sent by the SeNB to the MeNB in step 122 is “SeNB Modification Request Acknowledge”.
  • the bearer admission related information included in the signaling is the same as the SeNB adding process, and the description is not repeated.
  • Embodiment 7 SeNB adding procedure, for adding SeNB (downlink bearer, MeNB provides data transmission direction to SeNB, SeNB does not change direction).
  • an admission control method provided by this embodiment includes:
  • Step 131 After deciding to perform bearer separation, the MeNB sends a message (for example, a “SeNB Addition Request” message) to the SeNB, where the E-RAB list information that is desired to be separated by the bearer in the SeNB is carried.
  • the MeNB informs the SeNB whether to perform offload data transmission for the downlink bearer. For downlink data offload and downlink data splitless, the MeNB indicates whether the direction of downlink data transmission is transmitted on the MeNB or on the SeNB.
  • Step 132 After receiving the message in step 131, the SeNB determines whether the downlink data of the bearer in the E-RAB list can be accepted or rejected.
  • the SeNB divides the bearer into two types, one is a bearer with uplink data transmission, and the other is another bearer with uplink data transmission, and the other The class is a bearer with no uplink data transmission, and the SeNB configures each type of bearer separately.
  • the SeNB sends the bearer downlink admission result and the configuration as the bearer admission result of the SeNB to the MeNB (for example, sends a “SeNB Addition Request Acknowledge” message).
  • the SeNB may provide other auxiliary information (such as load conditions on the SeNB, etc.) to assist the MeNB in subsequent decisions.
  • Step 133 After receiving the bearer admission result of the SeNB, the MeNB determines whether to accept the bearer admission result of the SeNB. If yes, if the MeNB needs to configure the connection of the UE, the MeNB may receive the bearer according to the SeNB received in step 132. As a result, including the bearer configuration of the SeNB, configuring the connection of the UE (for example, by sending an RRC Connection Reconfiguration message), and modifying the downlink data sending direction of the UE according to the bearer admission result of the SeNB in step 132 or Proportion (for example, for a downlink bearer not accepted by the SeNB, the MeNB may modify the downlink data of the bearer to be sent by the MeNB).
  • the MeNB may modify the downlink data of the bearer to be sent by the MeNB.
  • the MeNB may feed back a message rejecting the bearer admission result of the SeNB by step 135 (the RRC Connection Reconfiguration message is not sent to the UE at this time), and the MeNB may be in the downlink bearer rejected by the SeNB.
  • the MeNB may feed back a message rejecting the bearer admission result of the SeNB by step 135 (the RRC Connection Reconfiguration message is not sent to the UE at this time), and the MeNB may be in the downlink bearer rejected by the SeNB.
  • the SeNB and the MeNB can still maintain the uplink number. According to transmission on the SeNB.
  • Step 134 The UE performs connection configuration according to the message received from the MeNB in step 133, and feeds back the completion message to the MeNB after the configuration is successful (for example, sends an “RRC Connection Reconfiguration Complete” message).
  • Step 135 According to the feedback of step 134, the MeNB sends the completion result of the air interface configuration to the SeNB (for example, sends a “SeNB Reconfiguration Complete” message), and the result may include the final air interface configuration information of the UE. Or according to the judgment of step 133, the MeNB sends a message rejecting the bearer admission result of the SeNB to the SeNB.
  • the signaling sent by the MeNB to the SeNB in step 131 is “SeNB Modification Request”, and the signaling sent by the SeNB to the MeNB in step 132 is “SeNB Modification Request Acknowledge”.
  • the bearer admission related information included in the signaling is the same as the SeNB adding process, and the description is not repeated.
  • Embodiment 8 SeNB adding procedure, for adding an SeNB (downlink bearer, the MeNB provides a data transmission direction to the SeNB, and the SeNB rejects the direction).
  • an admission control method provided by this embodiment includes:
  • Step 141 After determining that the bearer separation is to be performed, the MeNB sends a message (for example, sends a “SeNB Addition Request” message) to the SeNB, where the E-RAB list information that is desired to be separated in the SeNB is carried.
  • the MeNB informs the SeNB whether to perform offload data transmission for the downlink bearer. For the downlink bearer offload transmission data and the non-split transmission data, the MeNB indicates whether the downlink data transmission direction is transmitted on the MeNB or on the SeNB.
  • Step 142 After receiving the message in step 141, the SeNB determines which downlink data can be received by the SeNB, and the SeNB distinguishes between the bearer with downlink data transmission and the bearer without downlink data transmission.
  • the SeNB changes the downlink data to be transmitted by the MeNB, and sends the bearer admission result of the SeNB (including the bearer configuration) to the MeNB (for example, sends a “SeNB Addition Request Acknowledge” message).
  • the SeNB may provide other auxiliary information (such as load conditions on the SeNB, etc.) to assist the MeNB in subsequent decisions.
  • Step 143 After receiving the bearer admission result of the SeNB, the MeNB determines whether to accept the bearer admission result of the SeNB. If yes, if the MeNB needs to configure the connection of the UE, the MeNB may receive the bearer according to the SeNB received in step 142. The result, including the bearer configuration of the SeNB and the downlink data transmission direction of the bearer, configures the connection of the UE (eg, by transmitting an "RRC Connection Reconfiguration" message). If the MeNB is unable to accept the admission result of the SeNB, the MeNB may feed back a message rejecting the bearer admission result of the SeNB by step 145 (the RRC Connection Reconfiguration message is not sent to the UE at this time). When the downlink direction of the bearer is rejected by the SeNB, the SeNB and the MeNB can still keep the uplink data transmitted on the SeNB.
  • Step 144 The UE performs connection configuration according to the message received from the MeNB in step 143, and feeds back the completion message to the MeNB after the configuration is successful (for example, sends an “RRC Connection Reconfiguration Complete” message).
  • Step 145 According to the feedback of step 144, the MeNB sends the completion result of the air interface configuration to the SeNB (for example, sends a “SeNB Reconfiguration Complete” message), and the result may include the final air interface configuration information of the UE. Or, according to the judgment of step 143, the MeNB sends a message rejecting the bearer admission result of the SeNB to the SeNB.
  • the signaling sent by the MeNB to the SeNB in step 141 For the SeNB Modification Request, the signaling sent by the SeNB to the MeNB in step 142 is “SeNB Modification Request Acknowledge”, but the bearer admission related information included in the signaling is the same as the SeNB adding procedure, and the description is not repeated.
  • Embodiment 9 The SeNB modification process is used to modify the UE configuration on the SeNB (downlink bearer, and the SeNB initiates a reject direction request).
  • an admission control method provided by this embodiment includes:
  • Step 151 For the downlink bearer, when the SeNB needs to change the downlink data transmission direction of the bearer to the MeNB (for example, when downlink congestion occurs), the SeNB sends a downlink data transmission direction change request to the MeNB (for example, requesting to change the data transmission direction to the MeNB, That is, the change is to send the downlink data by the MeNB.
  • the request information of the change data transmission direction may be the ratio information of the downlink data transmission, for example, the percentage of the downlink bearer data sent by the SeNB is “0”)
  • the MeNB transmits the bearer configuration (for example, "SeNB Modification Required" message) after the downlink data transmission direction is changed.
  • the SeNB only needs to go to the downlink bearer of the MeNB to change the data transmission direction, and does not perform related feedback to the MeNB for the downlink data transmission of the bearer (for example, the SeNB does not periodically feed back the downlink data buffer state of the bearer, etc.).
  • the SeNB may provide other auxiliary information (such as load conditions on the SeNB, etc.) to assist the MeNB in subsequent decisions.
  • Step 152 After receiving the downlink data transmission direction change request of the SeNB, the MeNB determines whether to accept the downlink data transmission direction change request of the SeNB. If yes, if the MeNB needs to configure the connection of the UE, the MeNB may follow the received procedure.
  • the downlink data transmission direction change request of the SeNB in 151 configures the connection of the UE (for example, by transmitting an "RRC Connection Reconfiguration" message). Subsequently, the MeNB does not send the downlink data of the bearer to the SeNB for the downlink bearer of the MeNB to change the data transmission direction.
  • the MeNB may, in step 154, feed back to the SeNB a message rejecting the downlink data transmission direction change request of the SeNB.
  • the SeNB and the MeNB can still keep the uplink data of the bearer transmitted on the SeNB.
  • Step 153 The UE performs connection configuration according to the message received from the MeNB in step 152, and feeds back the completion message to the MeNB after the configuration is successful (for example, sends an “RRC Connection Reconfiguration Complete” message).
  • Step 154 According to the feedback of step 153, the MeNB sends the completion result of the air interface configuration to the SeNB (for example, sends a “SeNB Modification Complete” message), and the result may include the final air interface configuration information of the UE. Alternatively, according to the determination in step 152, the MeNB transmits a message rejecting the downlink data transmission direction change request of the SeNB to the SeNB.
  • the method for controlling bearer admission on the MeNB side includes the following steps:
  • the master evolved base station MeNB sends an SeNB addition request message to the SeNB, where it needs to perform bearer separation with the controlled evolved base station SeNB for the same user equipment UE, and carries the evolution corresponding to the UE that needs to be accepted by the SeNB.
  • the universal terrestrial radio access network radio access carries E-RAB list information, and indication information for whether or not the bearer data transmission is performed for the bearer in a specific direction, where the specific direction is an uplink direction or a lower direction Row direction
  • the MeNB receives a feedback message that is sent by the SeNB, and obtains a bearer admission result of the SeNB, and if the MeNB accepts a bearer admission result of the SeNB, the MeNB configures a connection of the UE. Otherwise, the MeNB replies to the SeNB with a message rejecting accepting the bearer admission result of the SeNB.
  • the MeNB indicates whether the SeNB needs to perform offload data transmission for the bearer in the uplink direction or the downlink direction when the SeNB needs to perform bearer separation for the same UE.
  • the SeNB sends a message to the MeNB to indicate the bearer admission result, that is, the indication is accepted.
  • the uplink bearer or the downlink bearer can be implemented, so that the eNB can selectively receive the uplink bearer or the downlink bearer of the UE, and the uplink or downlink data is separately received when the eNB accepts the control, and the eNB can still provide the downlink even when the uplink is congested.
  • the data offloading transmission service, or the eNB can still provide the uplink data offload transmission service when the downlink is congested, thereby improving the throughput of the UE and the network side, and reducing the probability of the bearer release in the case of heavy network load.
  • the bearer admission result of the SeNB includes:
  • the data received by the SeNB in the specific direction of the UE is sent by the SeNB or the indication information sent by the MeNB;
  • the SeNB adds the request message, and further includes:
  • the bearer admission result of the SeNB includes: the SeNB determines a bearer in a specific direction that is accepted or rejected.
  • the bearer admission result of the SeNB further includes:
  • the data of the specific direction of the UE is changed information of the proportion transmitted on the SeNB.
  • the SeNB if the SeNB refuses to accept a bearer in a specific direction, the SeNB does not feed back, to the MeNB, a data transmission state of the UE in the specific direction.
  • the method further includes:
  • the MeNB receives a direction change request sent by the SeNB, where the direction change request is used to indicate that the bearer data transmission is not performed on the bearer in the specific direction, and the data of the specific direction of the UE is sent on the MeNB. Change information;
  • the MeNB configures the connection of the UE; otherwise, the MeNB returns a message rejecting the direction change request sent by the SeNB to the SeNB.
  • the method further includes:
  • the MeNB configures the connection of the UE; otherwise, the MeNB returns a message rejecting the change ratio request sent by the SeNB to the SeNB.
  • a bearer admission control method on the SeNB side provided by the embodiment of the present disclosure generally includes the following steps:
  • the controlled evolved base station SeNB receives the SeNB addition request message sent by the master evolved base station MeNB when it is determined that the SeNB needs to perform bearer separation with the same user equipment UE, and obtains an evolution corresponding to the UE that needs to be accepted by the SeNB.
  • the universal terrestrial radio access network radio access bears the E-RAB list information, and the indication information of whether the bearer data transmission is performed for the bearer in a specific direction, where the specific direction is an uplink direction or a downlink direction;
  • the SeNB generates a bearer admission result according to the E-RAB list information and the indication information, and returns a feedback message to the MeNB, where the bearer admission result of the SeNB is carried.
  • the SeNB receives the indication information of whether the MeNB adds the SeNB to the bearer in the uplink direction or the downlink direction, and sends a message to the MeNB to indicate the bearer reception result. That is, the uplink or downlink bearer is received by the eNB, so that the eNB can selectively accept the uplink or downlink bearer of the UE, and the uplink or downlink data is separately received when the eNB accepts the control, even when the eNB is still in the uplink congestion.
  • the downlink data offload transmission service can be provided, or the eNB can still provide the uplink data offload transmission service when the downlink is congested, thereby improving the throughput of the UE and the network side, and reducing the probability of the bearer release in the case of heavy network load. .
  • the bearer acceptance result includes:
  • the data received by the SeNB in the specific direction of the UE is sent by the SeNB or the indication information sent by the MeNB;
  • the SeNB adds the request message, and further includes:
  • the bearer admission result includes: the SeNB determines a bearer in a specific direction that is accepted or rejected.
  • the bearer acceptance result further includes:
  • the data of the specific direction of the UE is changed information of the proportion transmitted on the SeNB.
  • the SeNB if the SeNB refuses to accept a bearer in a specific direction, the SeNB does not feed back, to the MeNB, a data transmission state of the UE in the specific direction.
  • the method further includes:
  • the SeNB When it is determined that the bearer data transmission is not performed for the bearer in the specific direction, when the data of the specific direction of the UE needs to be changed and sent on the MeNB, the SeNB sends a direction change request to the MeNB, where For the case where the bearer in the specific direction does not perform offload data transmission, the data of the specific direction of the UE is sent on the MeNB.
  • the method further includes:
  • the data of the specific direction of the UE needs to change the proportion of the transmission on the MeNB and the ratio of the transmission on the SeNB, the SeNB Transmitting, by the MeNB, a change ratio request, where the bearer data transmission is performed on the bearer in the specific direction, where the data of the specific direction of the UE is sent on the MeNB and/or sent on the SeNB The change information of the ratio.
  • an embodiment of the present disclosure provides a bearer admission control device.
  • the device is a device on the MeNB side, referring to FIG. 18, the device includes:
  • the SeNB adding unit 181 is configured to: when it is determined that the master evolved base station MeNB and the controlled evolved base station SeNB perform bearer separation for the same user equipment UE, send an SeNB addition request message to the SeNB, where the bearer needs to be accepted by the SeNB.
  • the first determining processing unit 182 is configured to receive a feedback message that is sent by the SeNB, and obtain a bearer admission result of the SeNB, and if the bearer acceptance result of the SeNB is accepted, configure a connection of the UE; otherwise, Responding to the SeNB a message rejecting acceptance of the bearer admission result of the SeNB.
  • the SeNB When the device determines that the MeNB and the SeNB are required to perform the bearer separation for the same UE, the SeNB is instructed whether the SeNB performs the offload data transmission for the bearer in the uplink direction or the downlink direction, and the SeNB sends a message to the MeNB to indicate the bearer admission result, that is, the indication is accepted. Is the uplink bearer or the downlink bearer, so that the eNB can be selected.
  • the uplink or downlink bearer of the UE is accepted, and the uplink or downlink data is separately received when the eNB accepts the control, and the eNB can still provide the downlink data offload transmission service even when the uplink is congested, or the eNB is in the downlink congestion.
  • the uplink data offload transmission service can still be provided, thereby improving the throughput of the UE and the network side, and reducing the probability of bearer release in the case of heavy network load.
  • the bearer admission result of the SeNB includes:
  • the data received by the SeNB in the specific direction of the UE is sent by the SeNB or the indication information sent by the MeNB;
  • the SeNB adds the request message, and further includes:
  • the bearer admission result of the SeNB includes: the SeNB determines a bearer in a specific direction that is accepted or rejected.
  • the bearer admission result of the SeNB further includes:
  • the data of the specific direction of the UE is changed information of the proportion transmitted on the SeNB.
  • the first determining processing unit 182 is further configured to:
  • the SeNB If the direction change request sent by the SeNB is accepted, the connection to the UE is configured; otherwise, the SeNB is returned with a message rejecting the direction change request sent by the SeNB.
  • the first determining processing unit 182 is further configured to:
  • the SeNB If the change ratio request sent by the SeNB is accepted, the connection to the UE is configured; otherwise, the SeNB is returned with a message rejecting the change ratio request sent by the SeNB.
  • the device when the device is used as the device on the SeNB side, referring to FIG. 19, the device further includes:
  • the control unit 191 is configured to receive an SeNB addition request message sent by the MeNB when it is determined that the SeNB needs to perform bearer separation for the same UE, and obtain E-RAB list information corresponding to the UE that needs to be accepted by the SeNB, and for a specific direction.
  • the second determining processing unit 192 is configured to generate a bearer admission result according to the E-RAB list information and the indication information, and send a feedback message to the MeNB, where the bearer admission result is carried.
  • a bearer admission control apparatus provided by an embodiment of the present disclosure, when the apparatus is used as an SeNB, includes:
  • the control unit 191 is configured to receive an SeNB addition request message sent by the master evolved base station MeNB when it is determined that the controlled evolved base station SeNB needs to perform bearer separation for the same user equipment UE, and obtain the UE that needs to be accepted by the SeNB.
  • the second determining processing unit 192 is configured to generate a bearer admission result according to the E-RAB list information and the indication information, and send a feedback message to the MeNB, where the bearer admission result is carried.
  • the receiving MeNB sends the message indicating the bearer data transmission to the MeNB when the SeNB adds the SeNB to determine whether the bearer is to be separated from the SeNB for the same UE.
  • the bearer acceptance result includes:
  • the data received by the SeNB in the specific direction of the UE is sent by the SeNB or the indication information sent by the MeNB;
  • the SeNB adds the request message, and further includes:
  • the bearer admission result includes: the SeNB determines a bearer in a specific direction that is accepted or rejected.
  • the bearer acceptance result further includes:
  • the data of the specific direction of the UE is changed information of the proportion transmitted on the SeNB.
  • the second determining processing unit 192 is further configured to:
  • the data of the specific direction of the UE needs to be changed to be sent on the MeNB, and a direction change request is sent to the MeNB, where In the case where the bearer in a specific direction does not perform offload data transmission, the data of the specific direction of the UE is changed information transmitted on the MeNB.
  • the second determining processing unit 192 is further configured to:
  • the data of the specific direction of the UE needs to change the proportion of the transmission on the MeNB and the ratio of the transmission on the SeNB, to the MeNB. Transmitting a change ratio request, where carrying the offload data transmission for the bearer in the specific direction, the proportion of the specific direction data of the UE sent on the MeNB and/or the proportion sent on the SeNB Change information.
  • the foregoing SeNB adding unit 181, the first determining processing unit 182, the controlled unit 191, and the second determining processing unit 192 may all be implemented by a physical device such as a processor having a transceiving function, and the devices may be configured by The processor is implemented together with a memory having a storage function that stores related information.
  • an evolved base station includes: a processor 201 and a transceiver 202;
  • the processor If the evolved base station is the master evolved base station MeNB, the processor generates an SeNB add request message when it is determined that the MeNB and the controlled evolved base station SeNB are required to perform bearer separation for the same user equipment UE, where the bearer needs to be carried.
  • the processor obtains the bearer admission result of the SeNB, and if the bearer acceptance result of the SeNB is accepted, the connection of the UE is configured. And triggering the transceiver to send the configuration to the UE; otherwise, triggering the transceiver to reply to the SeNB with a message rejecting accepting the bearer admission result of the SeNB.
  • the SeNB When the evolved base station is used as the MeNB, when it is determined that the SeNB needs to be added to the same UE for the bearer separation, the SeNB is instructed whether the SeNB performs the offload data transmission for the bearer in the uplink direction or the downlink direction, and the SeNB sends a message to the MeNB to indicate the bearer admission result. That is, the uplink bearer or the downlink bearer is received, so that the eNB can selectively accept the uplink bearer or the downlink bearer of the UE, which is implemented separately when the eNB accepts the control.
  • the uplink or downlink data can provide the downlink data offload transmission service even when the uplink is congested, or the eNB can still provide the uplink data offload transmission service when the downlink is congested, thereby improving the throughput of the UE and the network side. , reducing the probability of bearer release in the case of heavy network load.
  • the bearer admission result of the SeNB includes:
  • the data received by the SeNB in the specific direction of the UE is sent by the SeNB or the indication information sent by the MeNB;
  • the SeNB adds the request message, and further includes:
  • the bearer admission result of the SeNB includes: the SeNB determines a bearer in a specific direction that is accepted or rejected.
  • the bearer admission result of the SeNB further includes:
  • the data of the specific direction of the UE is changed information of the proportion transmitted on the SeNB.
  • the transceiver is further configured to receive a direction change request sent by the SeNB, where the direction change request is used to indicate that the bearer data transmission is not performed for the bearer in the specific direction, the specific Change information sent by the direction data on the MeNB;
  • the processor is further configured to: if the direction change request sent by the SeNB is received, configure a connection of the UE, and trigger the transceiver to send the configuration to the UE; otherwise, trigger the sending and receiving The messenger replies to the SeNB with a message rejecting the direction change request sent by the SeNB.
  • the transceiver is further configured to receive a change ratio request sent by the SeNB, where the change ratio request is used to indicate a situation in which the bearer data transmission is performed on the bearer in the specific direction, the specific direction of the UE Change in the proportion of data transmitted on the MeNB and/or the proportion of transmissions on the SeNB;
  • the processor is further configured to: if the change ratio request sent by the SeNB is received, configure a connection of the UE, and trigger the transceiver to send the configuration to the UE; otherwise, trigger the sending and receiving The messenger replies to the SeNB with a message rejecting the change ratio request sent by the SeNB.
  • the transceiver is further configured to: receive, by the MeNB, an SeNB addition request message that is sent when the SeNB needs to perform bearer separation with the same UE;
  • the processor is further configured to: obtain, from the SeNB Add Request message, E-RAB list information corresponding to the UE that needs to be accepted by the SeNB, and indication information about whether the bearer in a specific direction performs offload data transmission, where the specific The direction is the uplink direction or the downlink direction.
  • the bearer admission result is generated according to the E-RAB list information and the indication information, and the transceiver is triggered to reply the feedback message to the MeNB, where the bearer admission result is carried.
  • Another evolved base station includes: a processor and a transceiver; wherein
  • the transceiver When the evolved base station is used as the SeNB, the transceiver receives an SeNB addition request message that is sent by the MeNB when it is determined that the SeNB needs to perform bearer separation for the same UE;
  • the processor obtains the E-RAB list information corresponding to the UE that is to be accepted by the SeNB, and the indication information about whether the bearer in the specific direction performs the offload data transmission, where the specific direction is the uplink direction. Or a downlink direction; generating, according to the E-RAB list information and the indication information, a bearer admission result, and triggering the transceiver to reply a feedback message to the MeNB, where the bearer admission result is carried.
  • the receiving MeNB When the evolved base station is used as the SeNB, the receiving MeNB, when it is determined that the SeNB needs to be added to the same UE for the bearer separation, whether to perform the offload data transmission indication information on the bearer in the uplink direction or the downlink direction, and send a message indication to the MeNB.
  • the bearer admission result that is, the indication is that the uplink bearer or the downlink bearer is received, so that the eNB can selectively accept the uplink bearer or the downlink bearer of the UE, so that the uplink or downlink data is separately received when the eNB accepts the control, even if the uplink is congested.
  • the eNB can still provide the downlink data offload transmission service, or the eNB can still provide the uplink data offload transmission service when the downlink is congested, thereby improving the throughput of the UE and the network side, and reducing the network load under heavy load. The probability of carrying a release.
  • the bearer acceptance result includes:
  • the data received by the SeNB in the specific direction of the UE is sent by the SeNB or the indication information sent by the MeNB;
  • the SeNB adds the request message, and further includes:
  • the bearer admission result includes: the SeNB determines a bearer in a specific direction that is accepted or rejected.
  • the bearer acceptance result further includes:
  • the data of the UE in the specific direction is Change information of the ratio transmitted on the SeNB.
  • the processor is further configured to: when it is determined that the bearer data transmission is not performed for the bearer in the specific direction, where the data of the specific direction of the UE needs to be changed and sent on the MeNB, triggering the The transceiver sends a direction change request to the MeNB, where the bearer data transmission is not performed for the bearer in the specific direction, and the change information sent by the specific direction data of the UE on the MeNB.
  • the processor is further configured to: when determining, for the offload data transmission, for the bearer in the specific direction, the data of the specific direction of the UE needs to change the proportion of the transmission on the MeNB and When the ratio is sent by the SeNB, the transceiver is triggered to send a change ratio request to the MeNB, where the bearer data transmission is performed on the bearer in the specific direction, where the data of the specific direction of the UE is in the The ratio of transmissions on the MeNB and/or the change information of the proportions transmitted on the SeNB.
  • the target/controlled eNB that receives the bearer setup request selects the uplink direction or the downlink direction that individually accepts or rejects the bearer, so that the uplink or downlink data of the bearer can be separately supported. transmission.
  • the target/controlled eNB sends a message notification to the source/master eNB that sends the bearer setup request to accept or reject the uplink or downlink direction of the bearer.
  • the controlled eNB may also send a message to the master eNB requesting to change the direction or proportion of the uplink or downlink data transmission of the bearer, and may separately support the transmission of the uplink or downlink data of the bearer.
  • the master eNB notifies the result of the request of the controlled eNB, and separately supports the transmission of the uplink or downlink data carried on the controlled eNB, and can separately support the transmission of the uplink or downlink data carried on the master eNB. Therefore, under the coverage of the macro cell, a large number of small cells are deployed at the same time, and the UE may perform data transmission on multiple eNBs in a manner of separate bearers.
  • the present disclosure can provide downlink data offloading when the eNB accepts the control, and can still provide downlink data offloading when the uplink is congested.
  • the downlink data is separately received, and when the downlink is congested, The uplink data offloading function can still be provided, thereby improving the throughput of the UE and the network side, and reducing the probability of bearer release.
  • embodiments of the present disclosure can be provided as a method, system, or computer program product. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware aspects. Moreover, the present disclosure may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) including computer usable program code.
  • These computer program instructions can also be stored in a particular computer capable of booting a computer or other programmable data processing device In a computer readable memory that operates in a computer readable memory, causing instructions stored in the computer readable memory to produce an article of manufacture comprising instruction means implemented in a block or in a flow or a flow diagram and/or block diagram of the flowchart The functions specified in the boxes.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开提供了承载接纳控制方法及装置，用以减少网络负荷较重情况下的承载释放的概率。该方法包括：MeNB当确定需要与SeNB针对同一用户设备UE进行承载分离时，向该SeNB发送SeNB添加请求消息，其中携带需要由该SeNB接纳的该UE对应的E-RAB列表信息，以及对于特定方向的承载是否进行分流数据传输的指示信息，其中，所述特定方向为上行方向或下行方向；所述MeNB接收所述SeNB回复的反馈消息，从中获取所述SeNB的承载接纳结果，若所述MeNB接受所述SeNB的承载接纳结果，则MeNB对所述UE的连接进行配置；否则，所述MeNB向所述SeNB回复拒绝接受所述SeNB的承载接纳结果的消息。

Description

一种承载接纳控制方法及装置
相关申请的交叉引用
本申请主张在2014年8月5日在中国提交的中国专利申请号No.201410381925.5的优先权，其全部内容通过引用包含于此。
技术领域
本公开涉及通信技术领域，尤其涉及一种承载接纳控制方法及装置。
背景技术
随着越来越多的家庭基站、微小区、中继等众多本地节点的部署，传统的以宏基站为主的网络架构将逐步演变为更多类型基站共存的网络架构，并提供更多层次的网络覆盖。为了改善该多类型基站共存网络架构下的相关性能，一种通过非理想链路实现多演进型基站(Evolved NodeB，eNB)间协作/聚合的网络架构被提出。在该架构下，用户设备(User Equipment，UE)的一部分无线承载(Radio Bearer，RB)在主控eNB(Master eNB，MeNB)管理的主小区组(Master Cell Group，MCG)上，这部分RB包括控制面承载(Signaling Radio Bearer，SRB)和用户面承载(Data Radio Bearer，DRB)。而同一UE的另外一部分承载(包括SRB和DRB)在受控eNB(Secondary eNB，SeNB)管理的从小区组(Secondary Cell Group，SCG)上。在这种UE承载分离的过程中，UE的上行和下行可以同时在两个eNB上分别传输，由于上下行负荷的不均衡，eNB在拥塞情况下会出现只能接纳一个承载的上行数据或下行数据的情况，而当前的接纳控制无法支持eNB只对一个承载的上行数据的或下行数据的进行单独接纳，从而导致该承载上下行数据都整个被拒绝。
下面关于承载分离技术简单介绍一下。
参见图1，在一种可能的多层网络覆盖环境中，MeNB与SeNB之间采用非理想的数据/信令接口Xn接口(有线或无线接口)，UE可以同时工作在MeNB和SeNB下。当连接到MeNB的UE进入SeNB所对应的小区的覆盖范围时，MeNB可以根据信号强度或负载均衡等考虑，转移UE的部分或全部的数据/信令到SeNB以获得SeNB提供的服务。从而实现UE可以同时使用MeNB和SeNB的资源，及基站间聚合(inter-eNB聚合)。在该场景下，UE的多个RB(Radio Bearer)可以分别通过MeNB控制的小区(MCell)和SeNB控制的小区(SCell)分别承载。其中分离到SeNB的RB可以包括DRB和/或SRB。由于SeNB受到MeNB的控制，因此可将SeNB认为是受控eNB，而MeNB是主控eNB。
一种承载分离架构如图2所示，UE在MeNB和SeNB有独立的承载，UE在每个eNB上都有独立的分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)实体。同一个承载的上下行承载数据不同时分流到MeNB和SeNB上传输。
另一种承载分离架构如图3所示，UE在MeNB上的连接可以有独立的承载。UE在SeNB的连接是将MeNB上的同一个演进分组系统(Evolved Packet System，EPS)承载 的一部分数据分流到SeNB上传输，该EPS承载PDCP实体仍然在MeNB，而SeNB上是有独立的无线链路控制(Radio Link Control，RLC)实体。
对于同一个下行承载，MeNB可以控制在SeNB或MeNB是否发数据或发多少数据(下行承载数据分流)。
对于同一个上行承载，网络可以配置UE的上行数据传输方向只在MeNB或SeNB上发送数据(上行承载数据不分流)，或以一定的比例在MeNB和SeNB上发送数据(上行承载数据分流)。如MeNB配置UE的上行数据的发送比例，50％的上行数据在MCG上传输，50％的上行数据在SCG上传输。
无线接纳控制(Radio Admission Control，RAC)作为eNB的一个功能模块，是控制接纳或拒绝新的无线承载的建立请求。为了实现该目的，RAC需要考虑网络侧的整体资源情况、该新承载的服务质量(Quality of Service，QoS)需求、正在进行中的进程所提供的QoS保证以及优先级以及系统整体的QoS需求。RAC的目的是通过接纳无线承载建立请求并提供相应的可用的无线资源，从而保证较高的无线资源利用率。同时，RAC也可以通过拒绝无线承载建立请求确保正在进行中的进程的QoS。
在切换过程，源eNB会在切换请求(HANDOVER REQUEST)消息中向目标eNB提供希望建立的(E-UTRAN Radio Access Bearer，E-RAB)承载的列表。目标eNB根据自己的实际可用资源情况，全部或部分接纳这些E-RAB。如图4所示，如果目标eNB无法接纳切换请求(HANDOVER REQUEST)中的任何承载，则反馈给源eNB切换准备失败(HANDOVER PREPARATION FAILURE)消息。如图5所示，如果目标eNB接纳了部分或全部的E-RAB，则反馈给源eNB切换请求确认(HANDOVER REQUEST ACKNOWLEDGE)消息，该消息中会携带接纳的E-RAB的列表和拒绝的E-RAB的列表，以及拒绝的原因。
在非切换过程，承载建立的过程中。如图6所示，移动管理实体(Mobile Management Entity，MME)会在承载建立的过程中向eNB发送承载建立请求(E-RAB SETUP REQUEST)消息，该消息中携带了希望建立的E-RAB承载的列表。eNB根据自己的实际可用资源情况，全部或部分接纳这些E-RAB。如果eNB接纳了部分E-RAB或全部的E-RAB或拒绝了全部的E-RAB，则反馈给MME承载建立响应(E-RAB SETUP RESPONSE)消息，该消息中会携带接纳的E-RAB的列表和拒绝的E-RAB的列表，以及拒绝的原因。
综上所述，在承载分离情况下，UE的一个承载会同时在多个eNB下有连接，因此当一个eNB只能接受承载的下行数据或只能接受上行数据的时候，当前eNB的接纳控制会将该承载的上下行全部拒绝，从而导致UE侧无法享受到单独上行承载分离或单独下行承载分离所带来传输速率提升，导致网络侧无法实现单独上行或单独下行承载分离带来的负载均衡增益。在网络负荷较重的情况下，可能导致该承载或UE连接被释放。
发明内容
本公开实施例提供了一种承载接纳控制方法、装置及演进型基站，用以实现在eNB 接纳控制的时候单独接纳上行或下行数据，即使在上行拥塞的时候eNB仍然能够提供下行的数据分流传输服务，或者在下行拥塞的时候eNB仍然能够提供上行的数据分流传输服务，从而提高了UE和网络侧的吞吐量，减少了网络负荷较重情况下的承载释放的概率。
本公开实施例提供的一种承载接纳控制方法，包括：
主控演进型基站MeNB当确定需要与受控演进型基站SeNB针对同一用户设备UE进行承载分离时，向该SeNB发送SeNB添加请求消息，其中携带需要由该SeNB接纳的该UE对应的演进的通用陆地无线接入网无线接入承载E-RAB列表信息，以及对于特定方向的承载是否进行分流数据传输的指示信息，其中，所述特定方向为上行方向或下行方向；
所述MeNB接收所述SeNB回复的反馈消息，从中获取所述SeNB的承载接纳结果，若所述MeNB接受所述SeNB的承载接纳结果，则所述MeNB对所述UE的连接进行配置；否则，所述MeNB向所述SeNB回复拒绝接受所述SeNB的承载接纳结果的消息。
通过该方法，MeNB当确定需要与SeNB针对同一UE进行承载分离而添加SeNB时，指示SeNB对于上行方向或下行方向的承载是否进行分流数据传输，SeNB向MeNB发送消息指示承载接纳结果，即指示接纳的是上行承载或下行承载，从而可以实现eNB选择性的接纳UE的上行承载或下行承载，实现了在eNB接纳控制的时候单独接纳上行或下行数据，即使在上行拥塞的时候eNB仍然能够提供下行的数据分流传输服务，或者在下行拥塞的时候eNB仍然能够提供上行的数据分流传输服务，从而提高了UE和网络侧的吞吐量，减少了网络负荷较重情况下的承载释放的概率。
可选地，所述SeNB的承载接纳结果包括：
所述SeNB确定接纳或拒绝的特定方向的承载；
对于所述特定方向的承载不进行分流数据传输的情况，所述SeNB接纳的各承载在所述UE的该特定方向的数据通过所述SeNB或通过所述MeNB发送的指示信息；
对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的比例和/或在所述SeNB上发送的比例。
可选地，所述SeNB添加请求消息中，还包括：
对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送或者在所述SeNB上发送的指示信息；
对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的比例和/或在所述SeNB上发送的比例；
所述SeNB的承载接纳结果包括：所述SeNB确定接纳或拒绝的特定方向的承载。
可选地，所述SeNB的承载接纳结果还包括：
针对所述SeNB无法接纳的特定方向的承载：
对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的变更信息；
对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在 所述SeNB上发送的比例的变更信息。
可选地，若所述SeNB拒绝接纳特定方向的承载，则所述SeNB不向所述MeNB反馈所述UE的该特定方向的数据传输状态。
可选地，该方法还包括：
所述MeNB接收所述SeNB发送的方向变更请求，该方向变更请求用于指示对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的变更信息；
若所述MeNB接受所述SeNB发送的方向变更请求，则所述MeNB对所述UE的连接进行配置；否则，所述MeNB向所述SeNB回复拒绝接受所述SeNB发送的方向变更请求的消息。
可选地，该方法还包括：
所述MeNB接收所述SeNB发送的变更比例请求，该变更比例请求用于指示对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的比例和/或在所述SeNB上发送的比例的变更信息；
若所述MeNB接受所述SeNB发送的变更比例请求，则所述MeNB对所述UE的连接进行配置；否则，所述MeNB向所述SeNB回复拒绝接受所述SeNB发送的变更比例请求的消息。
本公开实施例提供的一种承载接纳控制方法，包括：
受控演进型基站SeNB接收主控演进型基站MeNB当确定需要与该SeNB针对同一用户设备UE进行承载分离时发送的SeNB添加请求消息，从中获取需要由该SeNB接纳的该UE对应的演进的通用陆地无线接入网无线接入承载E-RAB列表信息，以及对于特定方向的承载是否进行分流数据传输的指示信息，其中，所述特定方向为上行方向或下行方向；
所述SeNB根据所述E-RAB列表信息和所述指示信息，生成承载接纳结果，并向所述MeNB回复反馈消息，其中携带所述SeNB的承载接纳结果。
通过该方法，SeNB接收MeNB当确定需要与SeNB针对同一UE进行承载分离而添加SeNB时，对于上行方向或下行方向的承载是否进行分流数据传输的指示信息，并向MeNB发送消息指示承载接纳结果，即指示接纳的是上行承载或下行承载，从而可以实现eNB选择性的接纳UE的上行承载或下行承载，实现了在eNB接纳控制的时候单独接纳上行或下行数据，即使在上行拥塞的时候eNB仍然能够提供下行的数据分流传输服务，或者在下行拥塞的时候eNB仍然能够提供上行的数据分流传输服务，从而提高了UE和网络侧的吞吐量，减少了网络负荷较重情况下的承载释放的概率。
可选地，所述承载接纳结果，包括：
所述SeNB确定接纳或拒绝的特定方向的承载；
对于所述特定方向的承载不进行分流数据传输的情况，所述SeNB接纳的各承载在所 述UE的该特定方向的数据通过所述SeNB或通过所述MeNB发送的指示信息；
对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的比例和/或在所述SeNB上发送的比例。
可选地，所述SeNB添加请求消息中，还包括：
对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据在所述SeNB上发送的指示信息；
对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的比例和/或在所述SeNB上发送的比例；
所述承载接纳结果，包括：所述SeNB确定接纳或拒绝的特定方向的承载。
可选地，所述承载接纳结果，还包括：
针对所述SeNB无法接纳的特定方向的承载：
对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的变更信息；
对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述SeNB上发送的比例的变更信息。
可选地，若所述SeNB拒绝接纳特定方向的承载，则所述SeNB不向所述MeNB反馈所述UE的该特定方向的数据传输状态。
可选地，该方法还包括：
当确定对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据需要变更在所述MeNB上发送时，所述SeNB向所述MeNB发送方向变更请求，其中携带对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的变更信息。
可选地，该方法还包括：
当确定对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据需要变更在所述MeNB上发送的比例和在所述SeNB上发送的比例时，所述SeNB向所述MeNB发送变更比例请求，其中携带对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的比例和/或在所述SeNB上发送的比例的变更信息。
本公开实施例提供的一种承载接纳控制装置，包括：
SeNB添加单元，用于当确定需要主控演进型基站MeNB与受控演进型基站SeNB针对同一用户设备UE进行承载分离时，向该SeNB发送SeNB添加请求消息，其中携带需要由该SeNB接纳的该UE对应的演进的通用陆地无线接入网无线接入承载E-RAB列表信息，以及对于特定方向的承载是否进行分流数据传输的指示信息，其中，所述特定方向为上行方向或下行方向；
第一判断处理单元，用于接收所述SeNB回复的反馈消息，从中获取所述SeNB的承 载接纳结果，若接受所述SeNB的承载接纳结果，则对所述UE的连接进行配置；否则，向所述SeNB回复拒绝接受所述SeNB的承载接纳结果的消息。
通过该装置，当确定需要MeNB与SeNB针对同一UE进行承载分离而添加SeNB时，指示SeNB对于上行方向或下行方向的承载是否进行分流数据传输，SeNB向MeNB发送消息指示承载接纳结果，即指示接纳的是上行承载或下行承载，从而可以实现eNB选择性的接纳UE的上行承载或下行承载，实现了在eNB接纳控制的时候单独接纳上行或下行数据，即使在上行拥塞的时候eNB仍然能够提供下行的数据分流传输服务，或者在下行拥塞的时候eNB仍然能够提供上行的数据分流传输服务，从而提高了UE和网络侧的吞吐量，减少了网络负荷较重情况下的承载释放的概率。
可选地，所述SeNB的承载接纳结果包括：
所述SeNB确定接纳或拒绝的特定方向的承载；
对于所述特定方向的承载不进行分流数据传输的情况，所述SeNB接纳的各承载在所述UE的该特定方向的数据通过所述SeNB或通过所述MeNB发送的指示信息；
对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的比例和/或在所述SeNB上发送的比例。
可选地，所述SeNB添加请求消息中，还包括：
对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送或者在所述SeNB上发送的指示信息；
对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的比例和/或在所述SeNB上发送的比例；
所述SeNB的承载接纳结果包括：所述SeNB确定接纳或拒绝的特定方向的承载。
可选地，所述SeNB的承载接纳结果还包括：
针对所述SeNB无法接纳的特定方向的承载：
对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的变更信息；
对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述SeNB上发送的比例的变更信息。
可选地，所述第一判断处理单元，还用于：
接收所述SeNB发送的方向变更请求，该方向变更请求用于指示对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的变更信息；
若接受所述SeNB发送的方向变更请求，则对所述UE的连接进行配置；否则，向所述SeNB回复拒绝接受所述SeNB发送的方向变更请求的消息。
可选地，所述第一判断处理单元，还用于：
接收所述SeNB发送的变更比例请求，该变更比例请求用于指示对于所述特定方向的 承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的比例和/或在所述SeNB上发送的比例的变更信息；
若接受所述SeNB发送的变更比例请求，则对所述UE的连接进行配置；否则，向所述SeNB回复拒绝接受所述SeNB发送的变更比例请求的消息。
可选地，该装置还包括：
受控单元，用于接收MeNB当确定需要与SeNB针对同一UE进行承载分离时发送的SeNB添加请求消息，从中获取需要由该SeNB接纳的该UE对应的E-RAB列表信息，以及对于特定方向的承载是否进行分流数据传输的指示信息，其中，所述特定方向为上行方向或下行方向；
第二判断处理单元，用于根据该E-RAB列表信息和该指示信息，生成承载接纳结果，并向MeNB回复反馈消息，其中携带该承载接纳结果。
本公开实施例提供的一种承载接纳控制装置，包括：
受控单元，用于接收主控演进型基站MeNB当确定需要与受控演进型基站SeNB针对同一用户设备UE进行承载分离时发送的SeNB添加请求消息，从中获取需要由该SeNB接纳的该UE对应的演进的通用陆地无线接入网无线接入承载E-RAB列表信息，以及对于特定方向的承载是否进行分流数据传输的指示信息，其中，所述特定方向为上行方向或下行方向；
第二判断处理单元，用于根据所述E-RAB列表信息和所述指示信息，生成承载接纳结果，并向所述MeNB回复反馈消息，其中携带该承载接纳结果。
通过该装置，接收MeNB当确定需要与SeNB针对同一UE进行承载分离而添加SeNB时，对于上行方向或下行方向的承载是否进行分流数据传输的指示信息，并向MeNB发送消息指示承载接纳结果，即指示接纳的是上行承载或下行承载，从而可以实现eNB选择性的接纳UE的上行承载或下行承载，实现了在eNB接纳控制的时候单独接纳上行或下行数据，即使在上行拥塞的时候eNB仍然能够提供下行的数据分流传输服务，或者在下行拥塞的时候eNB仍然能够提供上行的数据分流传输服务，从而提高了UE和网络侧的吞吐量，减少了网络负荷较重情况下的承载释放的概率。
可选地，所述承载接纳结果，包括：
所述SeNB确定接纳或拒绝的特定方向的承载；
对于所述特定方向的承载不进行分流数据传输的情况，所述SeNB接纳的各承载在所述UE的该特定方向的数据通过所述SeNB或通过所述MeNB发送的指示信息；
对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的比例和/或在所述SeNB上发送的比例。
可选地，所述SeNB添加请求消息中，还包括：
对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据在所述SeNB上发送的指示信息；
对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的比例和/或在所述SeNB上发送的比例；
所述承载接纳结果，包括：所述SeNB确定接纳或拒绝的特定方向的承载。
可选地，所述承载接纳结果，还包括：
针对所述SeNB无法接纳的特定方向的承载：
对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的变更信息；
对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述SeNB上发送的比例的变更信息。
可选地，所述第二判断处理单元，还用于：
当确定对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据需要变更在所述MeNB上发送时，向所述MeNB发送方向变更请求，其中携带对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的变更信息。
可选地，所述第二判断处理单元，还用于：
当确定对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据需要变更在所述MeNB上发送的比例和在所述SeNB上发送的比例时，向所述MeNB发送变更比例请求，其中携带对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的比例和/或在所述SeNB上发送的比例的变更信息。
本公开实施例提供的一种演进型基站，包括：处理器和收发信机；其中，
处理器当所述演进型基站作为主控演进型基站MeNB，并确定需要该MeNB与受控演进型基站SeNB针对同一用户设备UE进行承载分离时，生成SeNB添加请求消息，其中携带需要由该SeNB接纳的该UE对应的演进的通用陆地无线接入网无线接入承载E-RAB列表信息，以及对于特定方向的承载是否进行分流数据传输的指示信息，其中，所述特定方向为上行方向或下行方向；并触发收发信机向该SeNB发送所述SeNB添加请求消息；
当所述收发信机接收到所述SeNB回复的反馈消息时，所述处理器从中获取所述SeNB的承载接纳结果，若接受所述SeNB的承载接纳结果，则对所述UE的连接进行配置，并触发所述收发信机将该配置发送给所述UE；否则，触发所述收发信机向所述SeNB回复拒绝接受所述SeNB的承载接纳结果的消息。
当该演进型基站作为MeNB时，当确定需要与SeNB针对同一UE进行承载分离而添加SeNB时，指示SeNB对于上行方向或下行方向的承载是否进行分流数据传输，SeNB向MeNB发送消息指示承载接纳结果，即指示接纳的是上行承载或下行承载，从而可以实现eNB选择性的接纳UE的上行承载或下行承载，实现了在eNB接纳控制的时候单独接纳上行或下行数据，即使在上行拥塞的时候eNB仍然能够提供下行的数据分流传输服务， 或者在下行拥塞的时候eNB仍然能够提供上行的数据分流传输服务，从而提高了UE和网络侧的吞吐量，减少了网络负荷较重情况下的承载释放的概率。
可选地，所述SeNB的承载接纳结果包括：
所述SeNB确定接纳或拒绝的特定方向的承载；
对于所述特定方向的承载不进行分流数据传输的情况，所述SeNB接纳的各承载在所述UE的该特定方向的数据通过所述SeNB或通过所述MeNB发送的指示信息；
对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的比例和/或在所述SeNB上发送的比例。
可选地，所述SeNB添加请求消息中，还包括：
对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送或者在所述SeNB上发送的指示信息；
对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的比例和/或在所述SeNB上发送的比例；
所述SeNB的承载接纳结果包括：所述SeNB确定接纳或拒绝的特定方向的承载。
可选地，所述SeNB的承载接纳结果还包括：
针对所述SeNB无法接纳的特定方向的承载：
对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的变更信息；
对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述SeNB上发送的比例的变更信息。
可选地，所述收发信机还用于接收所述SeNB发送的方向变更请求，该方向变更请求用于指示对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的变更信息；
所述处理器还用于：若接受所述SeNB发送的方向变更请求，则对所述UE的连接进行配置，并触发所述收发信机将该配置发送给该UE；否则，触发所述收发信机向所述SeNB回复拒绝接受所述SeNB发送的方向变更请求的消息。
可选地，所述收发信机还用于接收所述SeNB发送的变更比例请求，该变更比例请求用于指示对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的比例和/或在所述SeNB上发送的比例的变更信息；
所述处理器还用于：若接受所述SeNB发送的变更比例请求，则对所述UE的连接进行配置，并触发所述收发信机将该配置发送给该UE；否则，触发所述收发信机向所述SeNB回复拒绝接受所述SeNB发送的变更比例请求的消息。
可选地，所述收发信机还用于：当所述演进型基站作为SeNB时，接收MeNB当确定需要与该SeNB针对同一UE进行承载分离时发送的SeNB添加请求消息；
所述处理器还用于：从SeNB添加请求消息中获取需要由SeNB接纳的该UE对应的 E-RAB列表信息，以及对于特定方向的承载是否进行分流数据传输的指示信息，其中，所述特定方向为上行方向或下行方向；根据该E-RAB列表信息和该指示信息，生成承载接纳结果，并触发所述收发信机向MeNB回复反馈消息，其中携带该承载接纳结果。
本公开实施例提供的一种演进型基站，包括：处理器和收发信机；其中，
当所述演进型基站作为SeNB时，所述收发信机接收MeNB当确定需要与该SeNB针对同一UE进行承载分离时发送的SeNB添加请求消息；
所述处理器从SeNB添加请求消息中获取需要由SeNB接纳的该UE对应的E-RAB列表信息，以及对于特定方向的承载是否进行分流数据传输的指示信息，其中，所述特定方向为上行方向或下行方向；根据该E-RAB列表信息和该指示信息，生成承载接纳结果，并触发所述收发信机向MeNB回复反馈消息，其中携带该承载接纳结果。
当该演进型基站作为SeNB时，接收MeNB当确定需要与SeNB针对同一UE进行承载分离而添加SeNB时，对于上行方向或下行方向的承载是否进行分流数据传输的指示信息，并向MeNB发送消息指示承载接纳结果，即指示接纳的是上行承载或下行承载，从而可以实现eNB选择性的接纳UE的上行承载或下行承载，实现了在eNB接纳控制的时候单独接纳上行或下行数据，即使在上行拥塞的时候eNB仍然能够提供下行的数据分流传输服务，或者在下行拥塞的时候eNB仍然能够提供上行的数据分流传输服务，从而提高了UE和网络侧的吞吐量，减少了网络负荷较重情况下的承载释放的概率。
可选地，所述承载接纳结果，包括：
所述SeNB确定接纳或拒绝的特定方向的承载；
对于所述特定方向的承载不进行分流数据传输的情况，所述SeNB接纳的各承载在所述UE的该特定方向的数据通过所述SeNB或通过所述MeNB发送的指示信息；
对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的比例和/或在所述SeNB上发送的比例。
可选地，所述SeNB添加请求消息中，还包括：
对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据在所述SeNB上发送的指示信息；
对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的比例和/或在所述SeNB上发送的比例；
所述承载接纳结果，包括：所述SeNB确定接纳或拒绝的特定方向的承载。
可选地，所述承载接纳结果，还包括：
针对所述SeNB无法接纳的特定方向的承载：
对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的变更信息；
对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述SeNB上发送的比例的变更信息。
可选地，所述处理器还用于当确定对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据需要变更在所述MeNB上发送时，触发所述收发信机向所述MeNB发送方向变更请求，其中携带对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的变更信息。
可选地，所述处理器还用于当确定对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据需要变更在所述MeNB上发送的比例和在所述SeNB上发送的比例时，触发所述收发信机向所述MeNB发送变更比例请求，其中携带对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的比例和/或在所述SeNB上发送的比例的变更信息。
附图说明
图1为现有技术中的承载分离的网络场景结构示意图；
图2为现有技术中的一种承载分离架构示意图；
图3为现有技术中的另一种承载分离架构示意图；
图4为现有技术中的一种源eNB与目标eNB之间的切换过程示意图；
图5为现有技术中的另一种源eNB与目标eNB之间的切换过程示意图；
图6为现有技术中的一种非切换过程的承载建立过程示意图；
图7为本公开实施例1提供的一种接纳控制方法的流程示意图；
图8为本公开实施例2提供的一种接纳控制方法的流程示意图；
图9为本公开实施例3提供的一种接纳控制方法的流程示意图；
图10为本公开实施例4提供的一种接纳控制方法的流程示意图；
图11为本公开实施例5提供的一种接纳控制方法的流程示意图；
图12为本公开实施例6提供的一种接纳控制方法的流程示意图；
图13为本公开实施例7提供的一种接纳控制方法的流程示意图；
图14为本公开实施例8提供的一种接纳控制方法的流程示意图；
图15为本公开实施例9提供的一种接纳控制方法的流程示意图；
图16为本公开实施例提供的MeNB侧的一种接纳控制方法的总体流程示意图；
图17为本公开实施例提供的SeNB侧的一种接纳控制方法的总体流程示意图；
图18为本公开实施例提供的一种接纳控制装置的结构示意图；
图19为本公开实施例提供的另一种接纳控制装置的结构示意图；
图20为本公开实施例提供的一种演进型基站的结构示意图。
具体实施方式
本公开实施例提供了一种承载接纳控制方法、装置及演进型基站，用以实现在eNB接纳控制的时候单独接纳上行或下行数据，即使在上行拥塞的时候eNB仍然能够提供下行的数据分流传输服务，或者在下行拥塞的时候eNB仍然能够提供上行的数据分流传输服务，从而提高了UE和网络侧的吞吐量，减少了网络负荷较重情况下的承载释放的概率。
本公开实施例中，eNB在做接纳控制的时候，选择性的接纳UE的上行承载或下行承载。受控eNB向主控eNB发送消息指示接纳的是承载的上行或下行。受控eNB向主控eNB发送消息，请求更改承载上行或下行数据发送的方向或比例。主控eNB收到受控eNB更改承载上行或下行数据请求后，反馈该请求是否被接受。
以下本公开实施例中所述的上行数据发送方向，是指由MeNB或SeNB发送上行数据，同理，所述的下行数据发送方向，是指由MeNB或SeNB发送下行数据。
下面分别给出几个具体实施例的举例说明。
本公开对应的实施例如下：
实施例1：SeNB添加过程，用于添加SeNB(针对上行承载，MeNB不提供给SeNB数据发送方向或比例，由SeNB决定方向或比例)。
参见图7，本实施例提供的一种接纳控制方法包括：
步骤701：MeNB在决定要进行承载分离后，发送消息(例如SeNB添加请求(SeNB Addition Request)消息)给SeNB，其中会携带希望在SeNB进行承载分离的E-RAB列表信息。MeNB通知SeNB是否对于上行承载进行分流数据传输。对于上行承载不分流传输数据的情况(对应图2和图3所示的承载分离架构中数据不分流的情况，下同)，MeNB不指示上行数据是在MeNB上发送还是在SeNB上发送。对于上行承载分流传输数据的情况(对应图3所示的承载分离架构中数据分流的情况，下同)，MeNB不指示上行数据在MeNB上发送和在SeNB上发送的比例。
步骤702：SeNB接收到步骤701中的消息后，SeNB判断能够接纳或拒绝E-RAB列表中的哪些承载的上行数据，SeNB区别配置有上行数据发送的承载和没有上行数据发送的承载，并将该承载的上行接纳结果和配置发送给MeNB(例如通过SeNB添加请求确认(SeNB Addition Request Acknowledge)消息将该承载接纳结果发给MeNB)。对于上行承载不分流传输数据的情况，指示各承载的上行数据是通过SeNB还是通过MeNB发送。对于上行承载分流传输数据的情况，SeNB指示上行数据在MeNB上发送和在SeNB上发送的比例。SeNB可提供其他辅助信息(例如SeNB上的负载情况等)帮助MeNB后续判决。
步骤703：MeNB收到SeNB的承载接纳结果后，判断是否接受该SeNB的承载接纳结果，如果是，则MeNB如果需要对UE的连接进行配置，则可以根据步骤702中收到的SeNB的承载接纳结果(包括SeNB的承载配置、承载的上行数据发送方向或比例)，对UE的连接进行配置(例如通过RRC连接重配置(RRC Connection Reconfiguration)消息进行配置)。如果MeNB无法接受SeNB的承载接纳结果，MeNB可以通过步骤705反馈拒绝接受SeNB的承载接纳结果的消息(此时不向UE发送RRC Connection Reconfiguration消息)。在承载的上行方向被SeNB拒绝接纳时，SeNB和MeNB仍然可以保持该承载的下行数据在SeNB上进行分流传输。
步骤704：UE根据步骤703中从MeNB收到的消息进行连接配置，并在配置成功后反馈完成消息给MeNB，例如反馈RRC连接重配置完成(RRC Connection Reconfiguration  Complete)消息给MeNB。
步骤705：根据步骤704的反馈，MeNB将空口配置的完成结果发送给SeNB(例如通过SeNB重配置完成(SeNB Reconfiguration Complete)消息将空口配置的完成结果发送给SeNB)，该结果可以包含UE最终的空口配置信息。或根据步骤703的判断，MeNB将拒绝SeNB的承载接纳结果的消息发送给SeNB。
需要说明的是，对于MeNB触发的SeNB承载配置修改过程，步骤701中MeNB发送给SeNB的信令为SeNB修改请求(SeNB Modification Request)，步骤702中SeNB发送给MeNB的信令为SeNB修改请求确认(SeNB Modification Request Acknowledge)，但信令中包含的承载接纳相关信息与SeNB添加过程相同，不再重复描述。
实施例2：SeNB添加过程，用于添加SeNB(针对上行承载，MeNB提供给SeNB数据发送方向或比例，SeNB不拒绝该方向或比例)。
参见图8，本实施例提供的一种接纳控制方法包括：
步骤801、MeNB在决定要进行承载分离时，发送消息(例如“SeNB Addition Request”消息)给SeNB，其中携带希望在SeNB进行承载分离的E-RAB列表信息。MeNB通知SeNB是否对于上行承载进行分流数据传输。对于上行承载不分流传输数据的情况，MeNB指示上行数据是在MeNB上发送或者是在SeNB上发送。对于上行承载分流传输数据的情况，MeNB指示上行数据在MeNB上发送和在SeNB上发送的比例。
步骤802：SeNB接收到步骤801中的消息后，如果步骤801中在上行承载不分流的情况下MeNB指示上行数据是在SeNB上发送，或在上行承载分流情况下MeNB指示上行数据在MeNB上发送和在SeNB上发送的比例，SeNB判断能够接纳或拒绝哪些承载的上行数据，SeNB针对承载分成两类，一类是有上行数据发送的承载，另一类是没有上行数据发送的承载，SeNB针对每一类承载分别进行配置，SeNB会将承载的上行接纳结果和配置作为SeNB的承载接纳结果发送给MeNB(例如通过“SeNB Addition Request Acknowledge”消息)。SeNB还可提供其他辅助信息(例如SeNB上的负载情况等)帮助MeNB后续判决。
步骤803：MeNB收到SeNB的承载接纳结果后，判断是否接受该SeNB的承载接纳结果，如果是，则MeNB如果需要对UE的连接进行配置，则可以根据步骤802中收到的SeNB的承载接纳结果，其中包括SeNB的承载配置，对UE的连接进行配置(例如通过RRC连接重配置(RRC Connection Reconfiguration)消息进行配置)，并可以根据步骤802中的SeNB的承载接纳结果修改UE的上行数据发送方向或比例，例如，对于SeNB没有接纳的上行承载，MeNB可以修改该承载的上行数据由MeNB发送。如果MeNB无法接受被SeNB拒绝的上行承载，执行步骤805将拒绝SeNB的承载接纳结果的消息发送给SeNB。MeNB可以在对UE进行配置的时候，选择不将承载分离到SeNB，或选择将该承载进行释放。在承载的上行被SeNB拒绝时，SeNB和MeNB仍然可以保持下行数据在SeNB上传输。
步骤804：UE根据步骤803中从MeNB收到的消息进行连接配置，并在配置成功后反馈完成消息给MeNB，例如反馈RRC连接重配置完成(RRC Connection Reconfiguration Complete)消息给MeNB。
步骤805：根据步骤804的反馈，MeNB将空口配置的完成结果发送给SeNB(例如通过SeNB重配置完成(SeNB Reconfiguration Complete)消息将空口配置的完成结果发送给SeNB)，该结果可以包含UE最终的空口配置信息。或根据步骤803的判断，MeNB将拒绝SeNB的承载接纳结果的消息发送给SeNB。
需要说明的是，对于MeNB触发的SeNB承载配置修改过程，步骤801中MeNB发送给SeNB的信令为“SeNB Modification Request”，步骤802中SeNB发送给MeNB的信令为“SeNB Modification Request Acknowledge”，但信令中包含的承载接纳相关信息与SeNB添加过程相同，不再重复描述。
实施例3：SeNB添加过程，用于添加SeNB(针对上行承载，MeNB提供给SeNB数据发送方向或比例，SeNB拒绝MeNB提供给SeNB的数据发送方向或比例)。
参见图9，本实施例提供的一种接纳控制方法包括：
步骤901：MeNB在决定要进行承载分离后，发送消息(例如SeNB添加请求(SeNB Addition Request)消息)给SeNB，其中会携带希望在SeNB进行承载分离的E-RAB列表信息。MeNB通知SeNB是否对于上行承载进行分流数据传输。对于上行承载不分流传输数据的情况，MeNB指示上行数据是在MeNB上发送还是在SeNB上发送。对于上行承载分流传输数据的情况，MeNB指示上行数据在MeNB上发送和在SeNB上发送的比例。
步骤902：SeNB接收到步骤901中的消息后，如果步骤901中在上行承载不分流的情况下MeNB指示上行数据是在SeNB上发送，或上行承载分流情况下MeNB指示上行数据在MeNB上发送和在SeNB上发送的比例，SeNB判断能够接纳哪些承载的上行数据，SeNB区别配置有上行数据发送的承载和没有上行数据发送的承载。对于SeNB无法接纳上行数据发送的承载，在上行承载数据不分流的情况，SeNB变更上行数据通过MeNB发送，在上行承载数据分流的情况，SeNB变更上行数据的发送比例，并将该承载配置和SeNB的承载接纳结果发送给MeNB(例如通过SeNB添加请求确认(SeNB Addition Request Acknowledge)消息将该承载接纳结果发给MeNB)。SeNB可提供其他辅助信息(例如SeNB上的负载情况等)帮助MeNB后续判决。
步骤903：MeNB收到的SeNB的承载接纳结果后，判断是否接受该SeNB的承载接纳结果，如果是，则MeNB如果需要对UE的连接进行配置，则可以根据步骤902中收到的SeNB的承载接纳结果，其中包括SeNB的承载配置和承载的上行数据发送方向或比例，对UE的连接进行配置(如“RRC Connection Reconfiguration”消息)。如果MeNB无法接受SeNB的承载接纳结果，MeNB可以通过步骤905反馈拒绝接受SeNB的承载接纳结果的消息(此时不向UE发送RRC Connection Reconfiguration消息)。在承载的上行方向被SeNB拒绝时，SeNB和MeNB仍然可以保持该承载的下行数据在SeNB上传输。
步骤904：UE根据步骤903中从MeNB收到的消息进行连接配置，并在配置成功后反馈完成消息给MeNB，例如反馈“RRC Connection Reconfiguration Complete”消息给MeNB。
步骤905：根据步骤904的反馈，MeNB将空口配置的完成结果发送给SeNB(例如通过SeNB重配置完成(SeNB Reconfiguration Complete)消息将空口配置的完成结果发送给SeNB)，该结果可以包含UE最终的空口配置信息。或根据步骤903的判断，MeNB将拒绝SeNB的承载接纳结果的消息发送给SeNB。
需要说明的是，对于MeNB触发的SeNB承载配置修改过程，步骤901中MeNB发送给SeNB的信令为“SeNB Modification Request”，步骤902中SeNB发送给MeNB的信令为“SeNB Modification Request Acknowledge”，但信令中包含的承载接纳相关信息与SeNB添加过程相同，不再重复描述。
实施例4：SeNB修改过程，用于修改SeNB上的UE配置(上行承载不分流，SeNB发起拒绝方向请求)。
参见图10，本实施例提供的一种接纳控制方法包括：
步骤101：对于上行承载不分流传输数据的情况，SeNB在需要变更承载的上行数据发送方向到MeNB的时候(例如，发生上行拥塞的情况)，发送上行数据发送方向变更请求给MeNB(例如，要求变更由MeNB发送上行数据)，同时发送给MeNB上行数据发送方向变更后的承载配置(例如，SeNB修改请求(SeNB Modification Required)消息)。SeNB可提供其他辅助信息(如SeNB上的负载情况等)帮助MeNB后续判决。
步骤102：MeNB收到的SeNB的上行数据发送方向变更请求后，判断是否接受该SeNB的上行数据发送方向变更请求，如果是，则MeNB如果需要对UE的连接进行配置，则可以根据接收到的步骤101中SeNB的上行数据发送方向变更请求对UE的连接进行配置(例如通过“RRC Connection Reconfiguration”消息进行配置)。如果MeNB无法接受SeNB的上行数据发送方向变更请求，MeNB可以通过步骤104反馈拒绝接受SeNB发送的方向变更请求的消息。在承载的上行被SeNB拒绝时，SeNB和MeNB仍然可以保持下行数据在SeNB上传输。
步骤103：UE根据步骤102中从MeNB收到的消息进行连接配置，并在配置成功后反馈完成消息给MeNB(例如通过“RRC Connection Reconfiguration Complete”消息)。
步骤104：根据步骤103的反馈，MeNB将空口配置的完成结果发送给SeNB(例如发送“SeNB Modification Complete”消息)，该结果可以包含UE最终的空口配置信息。或根据步骤102的判断，MeNB将是否拒绝SeNB发送的方向变更请求的消息发送给SeNB。
实施例5：SeNB修改过程，用于修改SeNB上的UE配置(上行承载分流，SeNB发起变更上行数据的发送比例请求)。
参见图11，本实施例提供的一种接纳控制方法包括：
步骤111：对于上行承载分流传输数据的情况，SeNB在需要变更承载的上行数据发送比例的时候(例如，发生上行拥塞的情况)，发送承载的上行数据发送比例变更请求给MeNB(例如，发送新的上行数据发送比例)，同时发送给MeNB上行数据发送比例变更后的承载配置(例如通过“SeNB Modification Required”消息发送)。SeNB可提供其他辅助信息(例如SeNB上的负载情况等)帮助MeNB后续判决。
步骤112：MeNB收到SeNB的上行数据发送比例变更请求后，判断是否接受该SeNB的上行数据发送比例变更请求，如果是，则MeNB如果需要对UE的连接进行配置，则可以根据接收到的步骤111中SeNB的上行数据发送比例变更请求对UE的连接进行配置(例如通过“RRC Connection Reconfiguration”消息进行配置)。如果MeNB无法接受步骤111中SeNB的上行数据发送比例变更请求，MeNB可以通过步骤114反馈拒绝SeNB的上行数据发送比例变更请求的消息。
步骤113：UE根据步骤112中从MeNB收到的消息进行连接配置，并在配置成功后反馈完成消息给MeNB(例如发送“RRC Connection Reconfiguration Complete”消息)。
步骤114：根据步骤113的反馈，MeNB将空口配置的完成结果发送给SeNB(例如发送“SeNB Modification Complete”消息给SeNB)，该结果可以包含UE最终的空口配置信息。或根据步骤112的判断，MeNB将拒绝SeNB的上行数据发送比例变更请求的消息发送给SeNB。
实施例6：SeNB添加过程，用于添加SeNB(下行承载，MeNB不提供给SeNB数据发送方向，SeNB决定数据发送方向)
参见图12，本实施例提供的一种接纳控制方法包括：
步骤121：MeNB在决定要进行承载分离后，发送消息(例如发送“SeNB Addition Request”消息)给SeNB，其中携带希望在SeNB进行承载分离的E-RAB列表信息。对于下行承载数据分流传输情况，MeNB通知SeNB是否对于下行承载进行分流数据传输。
步骤122：SeNB接收到步骤121中的消息后，SeNB判断能够接纳或拒绝哪些承载的下行数据，SeNB针对承载分成两类，一类是有上行数据发送的承载，另一类是没有上行数据发送的承载，SeNB针对每一类承载分别进行配置，SeNB会将承载的下行接纳结果和配置作为SeNB的承载接纳结果发送给MeNB(例如发送“SeNB Addition Request Acknowledge”消息)。后续的，SeNB对于没有被接纳的下行承载，不对该承载的下行数据传输对MeNB进行相关反馈，例如，SeNB不周期性反馈该承载的下行数据缓冲状态等。SeNB可提供其他辅助信息(例如SeNB上的负载情况等)帮助MeNB后续判决。
步骤123：MeNB收到SeNB的承载接纳结果后，判断是否接受该SeNB的承载接纳结果，如果是，则MeNB如果需要对UE的连接进行配置，则可以根据步骤122中收到的SeNB的承载接纳结果(其中包括SeNB的承载配置)，对UE的连接进行配置(例如“RRC Connection Reconfiguration”消息)。后续的，MeNB对于没有被接纳的下行承载不发送该承载的下行数据给SeNB。如果MeNB无法接受SeNB的承载接纳结果，MeNB可以通过 步骤125反馈拒绝接受SeNB的承载接纳结果(此时不向UE发送RRC Connection Reconfiguration消息)的消息。在承载的下行方向被SeNB拒绝时，SeNB和MeNB仍然可以保持该承载的上行数据在SeNB上传输。
步骤124：UE根据步骤123中从MeNB收到的消息进行连接配置，并在配置成功后反馈完成消息给MeNB(例如反馈“RRC Connection Reconfiguration Complete”消息)。
步骤125：根据步骤124的反馈，MeNB将空口配置的完成结果发送给SeNB(例如反馈“SeNB Reconfiguration Complete”消息)，该结果可以包含UE最终的空口配置信息。或根据步骤123的判断，MeNB将拒绝SeNB的承载接纳结果的消息发送给SeNB。
需要说明的是，对于MeNB触发的SeNB承载配置修改过程，步骤121中MeNB发送给SeNB的信令为“SeNB Modification Request”，步骤122中SeNB发送给MeNB的信令为“SeNB Modification Request Acknowledge”，但信令中包含的承载接纳相关信息与SeNB添加过程相同，不再重复描述。
实施例7：SeNB添加过程，用于添加SeNB(下行承载，MeNB提供给SeNB数据发送方向，SeNB不变更方向)。
参见图13，本实施例提供的一种接纳控制方法包括：
步骤131：MeNB在决定要进行承载分离后，发送消息(例如“SeNB Addition Request”消息)给SeNB，其中携带希望在SeNB进行承载分离的E-RAB列表信息。MeNB通知SeNB是否对于下行承载进行分流数据传输。对于下行数据分流和下行数据不分流情况，MeNB指示下行数据发送的方向是在MeNB上发送还是在SeNB上发送。
步骤132：SeNB接收到步骤131中的消息后，SeNB判断能够接纳或拒绝E-RAB列表中的哪些承载的下行数据，SeNB针对承载分成两类，一类是有上行数据发送的承载，另一类是没有上行数据发送的承载，SeNB针对每一类承载分别进行配置，SeNB会将承载的下行接纳结果和配置作为SeNB的承载接纳结果发送给MeNB(例如发送“SeNB Addition Request Acknowledge”消息)。SeNB可提供其他辅助信息(例如SeNB上的负载情况等)帮助MeNB后续判决。
步骤133：MeNB收到SeNB的承载接纳结果后，判断是否接受该SeNB的承载接纳结果，如果是，则MeNB如果需要对UE的连接进行配置，则可以根据步骤132中收到的SeNB的承载接纳结果(其中包括SeNB的承载配置)，对UE的连接进行配置(例如通过发送“RRC Connection Reconfiguration”消息进行配置)，并可以根据步骤132中的SeNB的承载接纳结果修改UE的下行数据发送方向或比例(例如，对于SeNB没有接纳的下行承载，MeNB可以修改该承载的下行数据由MeNB发送)。如果MeNB无法接受SeNB的承载接纳结果，MeNB可以通过步骤135反馈拒绝接受SeNB的承载接纳结果的消息(此时不向UE发送RRC Connection Reconfiguration消息)，对于被SeNB拒绝接纳的下行承载，MeNB可以在对UE进行配置的时候，选择不将该承载分离到SeNB上，或选择将该承载进行释放。在承载的下行方向被SeNB拒绝时，SeNB和MeNB仍然可以保持上行数 据在SeNB上传输。
步骤134：UE根据步骤133中从MeNB收到的消息进行连接配置，并在配置成功后反馈完成消息给MeNB(例如发送“RRC Connection Reconfiguration Complete”消息)。
步骤135：根据步骤134的反馈，MeNB将空口配置的完成结果发送给SeNB(例如发送“SeNB Reconfiguration Complete”消息)，该结果可以包含UE最终的空口配置信息。或者根据步骤133的判断，MeNB将拒绝SeNB的承载接纳结果的消息发送给SeNB。
需要说明的是，对于MeNB触发的SeNB承载配置修改过程，步骤131中MeNB发送给SeNB的信令为“SeNB Modification Request”，步骤132中SeNB发送给MeNB的信令为“SeNB Modification Request Acknowledge”，但信令中包含的承载接纳相关信息与SeNB添加过程相同，不再重复描述。
实施例8：SeNB添加过程，用于添加SeNB(下行承载，MeNB提供给SeNB数据发送方向，SeNB拒绝该方向)。
参见图14，本实施例提供的一种接纳控制方法包括：
步骤141：MeNB在决定要进行承载分离后，发送消息(例如发送“SeNB Addition Request”消息)给SeNB，其中携带希望在SeNB进行承载分离的E-RAB列表信息。MeNB通知SeNB是否对于下行承载进行分流数据传输。对于下行承载分流传输数据和不分流传输数据的情况，MeNB指示下行数据的发给方向是在MeNB上发送还是在SeNB上发送。
步骤142：SeNB接收到步骤141中的消息后，SeNB判断能够接纳哪些承载的下行数据，SeNB区别配置有下行数据发送的承载和没有下行数据发送的承载。对于SeNB无法接纳下行数据发送的承载，SeNB变更下行数据通过MeNB发送，并将SeNB的承载接纳结果(其中包括该承载配置)发送给MeNB(例如发送“SeNB Addition Request Acknowledge”消息)。SeNB可提供其他辅助信息(例如SeNB上的负载情况等)帮助MeNB后续判决。
步骤143：MeNB收到SeNB的承载接纳结果后，判断是否接受该SeNB的承载接纳结果，如果是，则MeNB如果需要对UE的连接进行配置，则可以根据步骤142中收到的SeNB的承载接纳结果(其中包括SeNB的承载配置和承载的下行数据发送方向)，对UE的连接进行配置(例如通过发送“RRC Connection Reconfiguration”消息进行配置)。如果MeNB无法接受SeNB的接纳结果，MeNB可以通过步骤145反馈拒绝接受SeNB的承载接纳结果的消息(此时不向UE发送RRC Connection Reconfiguration消息)。在承载的下行方向被SeNB拒绝时，SeNB和MeNB仍然可以保持上行数据在SeNB上传输。
步骤144：UE根据步骤143中从MeNB收到的消息进行连接配置，并在配置成功后反馈完成消息给MeNB(例如发送“RRC Connection Reconfiguration Complete”消息)。
步骤145：根据步骤144的反馈，MeNB将空口配置的完成结果发送给SeNB(例如发送“SeNB Reconfiguration Complete”消息)，该结果可以包含UE最终的空口配置信息。或者根据步骤143的判断，MeNB将拒绝接受SeNB的承载接纳结果的消息发送给SeNB。
对于MeNB触发的SeNB承载配置修改过程，步骤141中MeNB发送给SeNB的信令 为“SeNB Modification Request”，步骤142中SeNB发送给MeNB的信令为“SeNB Modification Request Acknowledge”，但信令中包含的承载接纳相关信息与SeNB添加过程相同，不再重复描述。
实施例9：SeNB修改过程，用于修改SeNB上的UE配置(下行承载，SeNB发起拒绝方向请求)。
参见图15，本实施例提供的一种接纳控制方法包括：
步骤151：对于下行承载，SeNB在需要变更承载的下行数据发送方向到MeNB的时候(例如发生下行拥塞的情况)，发送下行数据发送方向变更请求给MeNB(例如，要求变更数据发送方向到MeNB，即变更为由MeNB发送下行数据。对于下行承载分流数据传输的情况，该变更数据发送方向的请求信息可以是下行数据发送的比例信息，例如下行承载数据在SeNB上发送的百分比为“0”)，同时，发送给MeNB下行数据发送方向变更后的承载配置(例如“SeNB Modification Required”消息)。后续的，SeNB对于改变数据发送方向只到MeNB的下行承载，不对该承载的下行数据传输对MeNB进行相关反馈(例如，SeNB不周期性反馈该承载的下行数据缓冲状态等)。SeNB可提供其他辅助信息(如SeNB上的负载情况等)帮助MeNB后续判决。
步骤152：MeNB收到SeNB的下行数据发送方向变更请求后，判断是否接受该SeNB的下行数据发送方向变更请求，如果是，则MeNB如果需要对UE的连接进行配置，则可以根据接收到的步骤151中SeNB的下行数据发送方向变更请求对UE的连接进行配置(例如通过发送“RRC Connection Reconfiguration”消息进行配置)。后续的，MeNB对于改变数据发送方向只到MeNB的下行承载不发送该承载的下行数据给SeNB。如果MeNB无法接受SeNB的下行数据发送方向变更请求，MeNB可以通过步骤154向SeNB反馈拒绝接受SeNB的下行数据发送方向变更请求的消息。在承载的下行方向被SeNB拒绝时，SeNB和MeNB仍然可以保持该承载的上行数据在SeNB上传输。
步骤153：UE根据步骤152中从MeNB收到的消息进行连接配置，并在配置成功后反馈完成消息给MeNB(例如发送“RRC Connection Reconfiguration Complete”消息)。
步骤154：根据步骤153的反馈，MeNB将空口配置的完成结果发送给SeNB(例如发送“SeNB Modification Complete”消息)，该结果可以包含UE最终的空口配置信息。或者，根据步骤152的判断，MeNB将拒绝接受SeNB的下行数据发送方向变更请求的消息发送给SeNB。
由此可见，本公开实施例提供的一种MeNB侧的承载接纳控制方法，参见图16，总体包括步骤：
S161、主控演进型基站MeNB当确定需要与受控演进型基站SeNB针对同一用户设备UE进行承载分离时，向该SeNB发送SeNB添加请求消息，其中携带需要由该SeNB接纳的该UE对应的演进的通用陆地无线接入网无线接入承载E-RAB列表信息，以及对于特定方向的承载是否进行分流数据传输的指示信息，其中，所述特定方向为上行方向或下 行方向；
S162、所述MeNB接收所述SeNB回复的反馈消息，从中获取所述SeNB的承载接纳结果，若所述MeNB接受所述SeNB的承载接纳结果，则所述MeNB对所述UE的连接进行配置；否则，所述MeNB向所述SeNB回复拒绝接受所述SeNB的承载接纳结果的消息。
通过该方法，MeNB当确定需要与SeNB针对同一UE进行承载分离而添加SeNB时，指示SeNB对于上行方向或下行方向的承载是否进行分流数据传输，SeNB向MeNB发送消息指示承载接纳结果，即指示接纳的是上行承载或下行承载，从而可以实现eNB选择性的接纳UE的上行承载或下行承载，实现了在eNB接纳控制的时候单独接纳上行或下行数据，即使在上行拥塞的时候eNB仍然能够提供下行的数据分流传输服务，或者在下行拥塞的时候eNB仍然能够提供上行的数据分流传输服务，从而提高了UE和网络侧的吞吐量，减少了网络负荷较重情况下的承载释放的概率。
可选地，所述SeNB的承载接纳结果包括：
所述SeNB确定接纳或拒绝的特定方向的承载；
对于所述特定方向的承载不进行分流数据传输的情况，所述SeNB接纳的各承载在所述UE的该特定方向的数据通过所述SeNB或通过所述MeNB发送的指示信息；
对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的比例和/或在所述SeNB上发送的比例。
可选地，所述SeNB添加请求消息中，还包括：
对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送或者在所述SeNB上发送的指示信息；
对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的比例和/或在所述SeNB上发送的比例；
所述SeNB的承载接纳结果包括：所述SeNB确定接纳或拒绝的特定方向的承载。
可选地，所述SeNB的承载接纳结果还包括：
针对所述SeNB无法接纳的特定方向的承载：
对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的变更信息；
对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述SeNB上发送的比例的变更信息。
可选地，若所述SeNB拒绝接纳特定方向的承载，则所述SeNB不向所述MeNB反馈所述UE的该特定方向的数据传输状态。
可选地，该方法还包括：
所述MeNB接收所述SeNB发送的方向变更请求，该方向变更请求用于指示对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的变更信息；
若所述MeNB接受所述SeNB发送的方向变更请求，则所述MeNB对所述UE的连接进行配置；否则，所述MeNB向所述SeNB回复拒绝接受所述SeNB发送的方向变更请求的消息。
可选地，该方法还包括：
所述MeNB接收所述SeNB发送的变更比例请求，该变更比例请求用于指示对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的比例和/或在所述SeNB上发送的比例的变更信息；
若所述MeNB接受所述SeNB发送的变更比例请求，则所述MeNB对所述UE的连接进行配置；否则，所述MeNB向所述SeNB回复拒绝接受所述SeNB发送的变更比例请求的消息。
与上述MeNB侧的方法相对应的，参见图17，本公开实施例提供的一种SeNB侧的承载接纳控制方法，总体包括步骤：
S171、受控演进型基站SeNB接收主控演进型基站MeNB当确定需要与该SeNB针对同一用户设备UE进行承载分离时发送的SeNB添加请求消息，从中获取需要由该SeNB接纳的该UE对应的演进的通用陆地无线接入网无线接入承载E-RAB列表信息，以及对于特定方向的承载是否进行分流数据传输的指示信息，其中，所述特定方向为上行方向或下行方向；
S172、所述SeNB根据所述E-RAB列表信息和所述指示信息，生成承载接纳结果，并向所述MeNB回复反馈消息，其中携带所述SeNB的承载接纳结果。
通过该方法，SeNB接收MeNB当确定需要与SeNB针对同一UE进行承载分离而添加SeNB时，对于上行方向或下行方向的承载是否进行分流数据传输的指示信息，并向MeNB发送消息指示承载接纳结果，即指示接纳的是上行承载或下行承载，从而可以实现eNB选择性的接纳UE的上行承载或下行承载，实现了在eNB接纳控制的时候单独接纳上行或下行数据，即使在上行拥塞的时候eNB仍然能够提供下行的数据分流传输服务，或者在下行拥塞的时候eNB仍然能够提供上行的数据分流传输服务，从而提高了UE和网络侧的吞吐量，减少了网络负荷较重情况下的承载释放的概率。
可选地，所述承载接纳结果，包括：
所述SeNB确定接纳或拒绝的特定方向的承载；
对于所述特定方向的承载不进行分流数据传输的情况，所述SeNB接纳的各承载在所述UE的该特定方向的数据通过所述SeNB或通过所述MeNB发送的指示信息；
对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的比例和/或在所述SeNB上发送的比例。
可选地，所述SeNB添加请求消息中，还包括：
对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据在所述SeNB上发送的指示信息；
对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的比例和/或在所述SeNB上发送的比例；
所述承载接纳结果，包括：所述SeNB确定接纳或拒绝的特定方向的承载。
可选地，所述承载接纳结果，还包括：
针对所述SeNB无法接纳的特定方向的承载：
对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的变更信息；
对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述SeNB上发送的比例的变更信息。
可选地，若所述SeNB拒绝接纳特定方向的承载，则所述SeNB不向所述MeNB反馈所述UE的该特定方向的数据传输状态。
可选地，该方法还包括：
当确定对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据需要变更在所述MeNB上发送时，所述SeNB向所述MeNB发送方向变更请求，其中携带对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的变更信息。
可选地，该方法还包括：
当确定对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据需要变更在所述MeNB上发送的比例和在所述SeNB上发送的比例时，所述SeNB向所述MeNB发送变更比例请求，其中携带对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的比例和/或在所述SeNB上发送的比例的变更信息。
与上述方法相对应地，本公开实施例提供的一种承载接纳控制装置，当该装置作为MeNB侧的装置时，参见图18，该装置包括：
SeNB添加单元181，用于当确定需要主控演进型基站MeNB与受控演进型基站SeNB针对同一用户设备UE进行承载分离时，向该SeNB发送SeNB添加请求消息，其中携带需要由该SeNB接纳的该UE对应的演进的通用陆地无线接入网无线接入承载E-RAB列表信息，以及对于特定方向的承载是否进行分流数据传输的指示信息，其中，所述特定方向为上行方向或下行方向；
第一判断处理单元182，用于接收所述SeNB回复的反馈消息，从中获取所述SeNB的承载接纳结果，若接受所述SeNB的承载接纳结果，则对所述UE的连接进行配置；否则，向所述SeNB回复拒绝接受所述SeNB的承载接纳结果的消息。
通过该装置，当确定需要MeNB与SeNB针对同一UE进行承载分离而添加SeNB时，指示SeNB对于上行方向或下行方向的承载是否进行分流数据传输，SeNB向MeNB发送消息指示承载接纳结果，即指示接纳的是上行承载或下行承载，从而可以实现eNB选择 性的接纳UE的上行承载或下行承载，实现了在eNB接纳控制的时候单独接纳上行或下行数据，即使在上行拥塞的时候eNB仍然能够提供下行的数据分流传输服务，或者在下行拥塞的时候eNB仍然能够提供上行的数据分流传输服务，从而提高了UE和网络侧的吞吐量，减少了网络负荷较重情况下的承载释放的概率。
可选地，所述SeNB的承载接纳结果包括：
所述SeNB确定接纳或拒绝的特定方向的承载；
对于所述特定方向的承载不进行分流数据传输的情况，所述SeNB接纳的各承载在所述UE的该特定方向的数据通过所述SeNB或通过所述MeNB发送的指示信息；
对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的比例和/或在所述SeNB上发送的比例。
可选地，所述SeNB添加请求消息中，还包括：
对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送或者在所述SeNB上发送的指示信息；
对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的比例和/或在所述SeNB上发送的比例；
所述SeNB的承载接纳结果包括：所述SeNB确定接纳或拒绝的特定方向的承载。
可选地，所述SeNB的承载接纳结果还包括：
针对所述SeNB无法接纳的特定方向的承载：
对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的变更信息；
对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述SeNB上发送的比例的变更信息。
可选地，所述第一判断处理单元182，还用于：
接收所述SeNB发送的方向变更请求，该方向变更请求用于指示对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的变更信息；
若接受所述SeNB发送的方向变更请求，则对所述UE的连接进行配置；否则，向所述SeNB回复拒绝接受所述SeNB发送的方向变更请求的消息。
可选地，所述第一判断处理单元182，还用于：
接收所述SeNB发送的变更比例请求，该变更比例请求用于指示对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的比例和/或在所述SeNB上发送的比例的变更信息；
若接受所述SeNB发送的变更比例请求，则对所述UE的连接进行配置；否则，向所述SeNB回复拒绝接受所述SeNB发送的变更比例请求的消息。
可选地，当该装置作为SeNB侧的装置时，参见图19，该装置还包括：
受控单元191，用于接收MeNB当确定需要与SeNB针对同一UE进行承载分离时发送的SeNB添加请求消息，从中获取需要由该SeNB接纳的该UE对应的E-RAB列表信息，以及对于特定方向的承载是否进行分流数据传输的指示信息，其中，所述特定方向为上行方向或下行方向；
第二判断处理单元192，用于根据该E-RAB列表信息和该指示信息，生成承载接纳结果，并向MeNB回复反馈消息，其中携带该承载接纳结果。
相应地，参见图19，本公开实施例提供的一种承载接纳控制装置，当该装置作为SeNB时，包括：
受控单元191，用于接收主控演进型基站MeNB当确定需要与受控演进型基站SeNB针对同一用户设备UE进行承载分离时发送的SeNB添加请求消息，从中获取需要由该SeNB接纳的该UE对应的演进的通用陆地无线接入网无线接入承载E-RAB列表信息，以及对于特定方向的承载是否进行分流数据传输的指示信息，其中，所述特定方向为上行方向或下行方向；
第二判断处理单元192，用于根据所述E-RAB列表信息和所述指示信息，生成承载接纳结果，并向所述MeNB回复反馈消息，其中携带该承载接纳结果。
通过该装置，接收MeNB当确定需要与SeNB针对同一UE进行承载分离而添加SeNB时，对于上行方向或下行方向的承载是否进行分流数据传输的指示信息，并向MeNB发送消息指示承载接纳结果，即指示接纳的是上行承载或下行承载，从而可以实现eNB选择性的接纳UE的上行承载或下行承载，实现了在eNB接纳控制的时候单独接纳上行或下行数据，即使在上行拥塞的时候eNB仍然能够提供下行的数据分流传输服务，或者在下行拥塞的时候eNB仍然能够提供上行的数据分流传输服务，从而提高了UE和网络侧的吞吐量，减少了网络负荷较重情况下的承载释放的概率。
可选地，所述承载接纳结果，包括：
所述SeNB确定接纳或拒绝的特定方向的承载；
对于所述特定方向的承载不进行分流数据传输的情况，所述SeNB接纳的各承载在所述UE的该特定方向的数据通过所述SeNB或通过所述MeNB发送的指示信息；
对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的比例和/或在所述SeNB上发送的比例。
可选地，所述SeNB添加请求消息中，还包括：
对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据在所述SeNB上发送的指示信息；
对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的比例和/或在所述SeNB上发送的比例；
所述承载接纳结果，包括：所述SeNB确定接纳或拒绝的特定方向的承载。
可选地，所述承载接纳结果，还包括：
针对所述SeNB无法接纳的特定方向的承载：
对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的变更信息；
对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述SeNB上发送的比例的变更信息。
可选地，所述第二判断处理单元192，还用于：
当确定对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据需要变更在所述MeNB上发送时，向所述MeNB发送方向变更请求，其中携带对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的变更信息。
可选地，所述第二判断处理单元192，还用于：
当确定对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据需要变更在所述MeNB上发送的比例和在所述SeNB上发送的比例时，向所述MeNB发送变更比例请求，其中携带对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的比例和/或在所述SeNB上发送的比例的变更信息。
可选地，上述SeNB添加单元181、第一判断处理单元182、受控单元191、第二判断处理单元192均可以由具有收发功能的处理器等实体装置实现，所述的装置均可以由这样的处理器和具有存储相关信息的存储功能的存储器来共同实现。
参见图20，本公开实施例提供的一种演进型基站，包括：处理器201和收发信机202；其中，
若所述演进型基站作为主控演进型基站MeNB，则所述处理器当确定需要该MeNB与受控演进型基站SeNB针对同一用户设备UE进行承载分离时，生成SeNB添加请求消息，其中携带需要由该SeNB接纳的该UE对应的演进的通用陆地无线接入网无线接入承载E-RAB列表信息，以及对于特定方向的承载是否进行分流数据传输的指示信息，其中，所述特定方向为上行方向或下行方向；并触发收发信机向该SeNB发送所述SeNB添加请求消息；
当所述收发信机接收到所述SeNB回复的反馈消息时，所述处理器从中获取所述SeNB的承载接纳结果，若接受所述SeNB的承载接纳结果，则对所述UE的连接进行配置，并触发所述收发信机将该配置发送给所述UE；否则，触发所述收发信机向所述SeNB回复拒绝接受所述SeNB的承载接纳结果的消息。
当该演进型基站作为MeNB时，当确定需要与SeNB针对同一UE进行承载分离而添加SeNB时，指示SeNB对于上行方向或下行方向的承载是否进行分流数据传输，SeNB向MeNB发送消息指示承载接纳结果，即指示接纳的是上行承载或下行承载，从而可以实现eNB选择性的接纳UE的上行承载或下行承载，实现了在eNB接纳控制的时候单独接 纳上行或下行数据，即使在上行拥塞的时候eNB仍然能够提供下行的数据分流传输服务，或者在下行拥塞的时候eNB仍然能够提供上行的数据分流传输服务，从而提高了UE和网络侧的吞吐量，减少了网络负荷较重情况下的承载释放的概率。
可选地，所述SeNB的承载接纳结果包括：
所述SeNB确定接纳或拒绝的特定方向的承载；
对于所述特定方向的承载不进行分流数据传输的情况，所述SeNB接纳的各承载在所述UE的该特定方向的数据通过所述SeNB或通过所述MeNB发送的指示信息；
对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的比例和/或在所述SeNB上发送的比例。
可选地，所述SeNB添加请求消息中，还包括：
对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送或者在所述SeNB上发送的指示信息；
对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的比例和/或在所述SeNB上发送的比例；
所述SeNB的承载接纳结果包括：所述SeNB确定接纳或拒绝的特定方向的承载。
可选地，所述SeNB的承载接纳结果还包括：
针对所述SeNB无法接纳的特定方向的承载：
对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的变更信息；
对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述SeNB上发送的比例的变更信息。
可选地，所述收发信机还用于接收所述SeNB发送的方向变更请求，该方向变更请求用于指示对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的变更信息；
所述处理器还用于：若接受所述SeNB发送的方向变更请求，则对所述UE的连接进行配置，并触发所述收发信机将该配置发送给该UE；否则，触发所述收发信机向所述SeNB回复拒绝接受所述SeNB发送的方向变更请求的消息。
可选地，所述收发信机还用于接收所述SeNB发送的变更比例请求，该变更比例请求用于指示对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的比例和/或在所述SeNB上发送的比例的变更信息；
所述处理器还用于：若接受所述SeNB发送的变更比例请求，则对所述UE的连接进行配置，并触发所述收发信机将该配置发送给该UE；否则，触发所述收发信机向所述SeNB回复拒绝接受所述SeNB发送的变更比例请求的消息。
可选地，若所述演进型基站作为SeNB，则所述收发信机还用于：接收MeNB当确定需要与该SeNB针对同一UE进行承载分离时发送的SeNB添加请求消息；
所述处理器还用于：从SeNB添加请求消息中获取需要由SeNB接纳的该UE对应的E-RAB列表信息，以及对于特定方向的承载是否进行分流数据传输的指示信息，其中，所述特定方向为上行方向或下行方向；根据该E-RAB列表信息和该指示信息，生成承载接纳结果，并触发所述收发信机向MeNB回复反馈消息，其中携带该承载接纳结果。
本公开实施例提供的另一种演进型基站，包括：处理器和收发信机；其中，
当所述演进型基站作为SeNB时，所述收发信机接收MeNB当确定需要与该SeNB针对同一UE进行承载分离时发送的SeNB添加请求消息；
所述处理器从SeNB添加请求消息中获取需要由SeNB接纳的该UE对应的E-RAB列表信息，以及对于特定方向的承载是否进行分流数据传输的指示信息，其中，所述特定方向为上行方向或下行方向；根据该E-RAB列表信息和该指示信息，生成承载接纳结果，并触发所述收发信机向MeNB回复反馈消息，其中携带该承载接纳结果。
当该演进型基站作为SeNB时，接收MeNB当确定需要与SeNB针对同一UE进行承载分离而添加SeNB时，对于上行方向或下行方向的承载是否进行分流数据传输的指示信息，并向MeNB发送消息指示承载接纳结果，即指示接纳的是上行承载或下行承载，从而可以实现eNB选择性的接纳UE的上行承载或下行承载，实现了在eNB接纳控制的时候单独接纳上行或下行数据，即使在上行拥塞的时候eNB仍然能够提供下行的数据分流传输服务，或者在下行拥塞的时候eNB仍然能够提供上行的数据分流传输服务，从而提高了UE和网络侧的吞吐量，减少了网络负荷较重情况下的承载释放的概率。
可选地，所述承载接纳结果，包括：
所述SeNB确定接纳或拒绝的特定方向的承载；
对于所述特定方向的承载不进行分流数据传输的情况，所述SeNB接纳的各承载在所述UE的该特定方向的数据通过所述SeNB或通过所述MeNB发送的指示信息；
对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的比例和/或在所述SeNB上发送的比例。
可选地，所述SeNB添加请求消息中，还包括：
对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据在所述SeNB上发送的指示信息；
对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的比例和/或在所述SeNB上发送的比例；
所述承载接纳结果，包括：所述SeNB确定接纳或拒绝的特定方向的承载。
可选地，所述承载接纳结果，还包括：
针对所述SeNB无法接纳的特定方向的承载：
对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的变更信息；
对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在 所述SeNB上发送的比例的变更信息。
可选地，所述处理器还用于当确定对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据需要变更在所述MeNB上发送时，触发所述收发信机向所述MeNB发送方向变更请求，其中携带对于所述特定方向的承载不进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的变更信息。
可选地，所述处理器还用于当确定对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据需要变更在所述MeNB上发送的比例和在所述SeNB上发送的比例时，触发所述收发信机向所述MeNB发送变更比例请求，其中携带对于所述特定方向的承载进行分流数据传输的情况，所述UE的该特定方向的数据在所述MeNB上发送的比例和/或在所述SeNB上发送的比例的变更信息。
综上所述，本公开实施例提供的技术方案中，收到承载建立请求的目标/受控eNB选择单独接纳或拒绝承载的上行方向或下行方向，从而可单独支持承载的上行或下行数据的传输。其中，目标/受控eNB向发送承载建立请求的源/主控eNB发送消息通知是接纳或拒绝了承载的上行方向或下行方向。受控eNB还可以向主控eNB发送消息请求更改承载的上行或下行数据发送的方向或比例，可单独支持承载的上行或下行数据的传输。主控eNB通知受控eNB请求的结果，并单独支持承载在受控eNB上的上行或下行数据的传输，可单独支持承载在主控eNB上的上行或下行数据的传输。因此，在宏小区覆盖下，同时部署大量的小小区，UE可以采用承载分离的方式，在多个eNB上进行数据传输。而本公开通过在eNB接纳控制的时候单独接纳上行数据，可以在上行拥塞的时候，仍然能够提供下行的数据分流作用；通过在eNB接纳控制的时候单独接纳下行数据，可以在下行拥塞的时候，仍然能够提供上行的数据分流作用，从而提高了UE和网络侧的吞吐量，减少了承载释放的概率。
本领域内的技术人员应明白，本公开的实施例可提供为方法、系统、或计算机程序产品。因此，本公开可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本公开可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器和光学存储器等)上实施的计算机程序产品的形式。
本公开是参照根据本公开实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方 式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本公开进行各种改动和变型而不脱离本公开的精神和范围。这样，倘若本公开的这些修改和变型属于本公开权利要求及其等同技术的范围之内，则本公开也意图包含这些改动和变型在内。

Claims (29)

  1. 一种承载接纳控制方法，该方法包括：
    主控演进型基站当确定需要与受控演进型基站针对同一用户设备进行承载分离时，向该受控演进型基站发送受控演进型基站添加请求消息，其中携带需要由该受控演进型基站接纳的该用户设备对应的演进的通用陆地无线接入网无线接入承载列表信息，以及对于特定方向的承载是否进行分流数据传输的指示信息，其中，所述特定方向为上行方向或下行方向；
    所述主控演进型基站接收所述受控演进型基站回复的反馈消息，从中获取所述受控演进型基站的承载接纳结果，若所述主控演进型基站接受所述受控演进型基站的承载接纳结果，则所述主控演进型基站对所述用户设备的连接进行配置；否则，所述主控演进型基站向所述受控演进型基站回复拒绝接受所述受控演进型基站的承载接纳结果的消息。
  2. 根据权利要求1所述的方法，其中，所述受控演进型基站的承载接纳结果包括：
    所述受控演进型基站确定接纳或拒绝的特定方向的承载；
    对于所述特定方向的承载不进行分流数据传输的情况，所述受控演进型基站接纳的各承载在所述用户设备的该特定方向的数据通过所述受控演进型基站或通过所述主控演进型基站发送的指示信息；
    对于所述特定方向的承载进行分流数据传输的情况，所述用户设备的该特定方向的数据在所述主控演进型基站上发送的比例和/或在所述受控演进型基站上发送的比例。
  3. 根据权利要求1所述的方法，其中，所述受控演进型基站添加请求消息中，还包括：
    对于所述特定方向的承载不进行分流数据传输的情况，所述用户设备的该特定方向的数据在所述主控演进型基站上发送或者在所述受控演进型基站上发送的指示信息；
    对于所述特定方向的承载进行分流数据传输的情况，所述用户设备的该特定方向的数据在所述主控演进型基站上发送的比例和/或在所述受控演进型基站上发送的比例；
    所述受控演进型基站的承载接纳结果包括：所述受控演进型基站确定接纳或拒绝的特定方向的承载。
  4. 根据权利要求3所述的方法，其中，所述受控演进型基站的承载接纳结果还包括：
    针对所述受控演进型基站无法接纳的特定方向的承载：
    对于所述特定方向的承载不进行分流数据传输的情况，所述用户设备的该特定方向的数据在所述主控演进型基站上发送的变更信息；
    对于所述特定方向的承载进行分流数据传输的情况，所述用户设备的该特定方向的数据在所述受控演进型基站上发送的比例的变更信息。
  5. 根据权利要求2或4所述的方法，其中，若所述受控演进型基站拒绝接纳特定方向的承载，则所述受控演进型基站不向所述主控演进型基站反馈所述用户设备的该特定方 向的数据传输状态。
  6. 根据权利要求1-4任一权项所述的方法，其中，该方法还包括：
    所述主控演进型基站接收所述受控演进型基站发送的方向变更请求，该方向变更请求用于指示对于所述特定方向的承载不进行分流数据传输的情况，所述用户设备的该特定方向的数据在所述主控演进型基站上发送的变更信息；
    若所述主控演进型基站接受所述受控演进型基站发送的方向变更请求，则所述主控演进型基站对所述用户设备的连接进行配置；否则，所述主控演进型基站向所述受控演进型基站回复拒绝接受所述受控演进型基站发送的方向变更请求的消息。
  7. 根据权利要求1-4任一权项所述的方法，其中，该方法还包括：
    所述主控演进型基站接收所述受控演进型基站发送的变更比例请求，该变更比例请求用于指示对于所述特定方向的承载进行分流数据传输的情况，所述用户设备的该特定方向的数据在所述主控演进型基站上发送的比例和/或在所述受控演进型基站上发送的比例的变更信息；
    若所述主控演进型基站接受所述受控演进型基站发送的变更比例请求，则所述主控演进型基站对所述用户设备的连接进行配置；否则，所述主控演进型基站向所述受控演进型基站回复拒绝接受所述受控演进型基站发送的变更比例请求的消息。
  8. 一种承载接纳控制方法，该方法包括：
    受控演进型基站接收主控演进型基站当确定需要与该受控演进型基站针对同一用户设备进行承载分离时发送的受控演进型基站添加请求消息，从中获取需要由该受控演进型基站接纳的该用户设备对应的演进的通用陆地无线接入网无线接入承载列表信息，以及对于特定方向的承载是否进行分流数据传输的指示信息，其中，所述特定方向为上行方向或下行方向；
    所述受控演进型基站根据所述演进的通用陆地无线接入网无线接入承载列表信息和所述指示信息，生成承载接纳结果，并向所述主控演进型基站回复反馈消息，其中携带所述受控演进型基站的承载接纳结果。
  9. 根据权利要求8所述的方法，其中，所述承载接纳结果，包括：
    所述受控演进型基站确定接纳或拒绝的特定方向的承载；
    对于所述特定方向的承载不进行分流数据传输的情况，所述受控演进型基站接纳的各承载在所述用户设备的该特定方向的数据通过所述受控演进型基站或通过所述主控演进型基站发送的指示信息；
    对于所述特定方向的承载进行分流数据传输的情况，所述用户设备的该特定方向的数据在所述主控演进型基站上发送的比例和/或在所述受控演进型基站上发送的比例。
  10. 根据权利要求8所述的方法，其中，所述受控演进型基站添加请求消息中，还包括：
    对于所述特定方向的承载不进行分流数据传输的情况，所述用户设备的该特定方向的 数据在所述受控演进型基站上发送的指示信息；
    对于所述特定方向的承载进行分流数据传输的情况，所述用户设备的该特定方向的数据在所述主控演进型基站上发送的比例和/或在所述受控演进型基站上发送的比例；
    所述承载接纳结果，包括：所述受控演进型基站确定接纳或拒绝的特定方向的承载。
  11. 根据权利要求10所述的方法，其中，所述承载接纳结果，还包括：
    针对所述受控演进型基站无法接纳的特定方向的承载：
    对于所述特定方向的承载不进行分流数据传输的情况，所述用户设备的该特定方向的数据在所述主控演进型基站上发送的变更信息；
    对于所述特定方向的承载进行分流数据传输的情况，所述用户设备的该特定方向的数据在所述受控演进型基站上发送的比例的变更信息。
  12. 根据权利要求9或11所述的方法，其中，若所述受控演进型基站拒绝接纳特定方向的承载，则所述受控演进型基站不向所述主控演进型基站反馈所述用户设备的该特定方向的数据传输状态。
  13. 根据权利要求8-11任一权项所述的方法，其中，该方法还包括：
    当确定对于所述特定方向的承载不进行分流数据传输的情况，所述用户设备的该特定方向的数据需要变更在所述主控演进型基站上发送时，所述受控演进型基站向所述主控演进型基站发送方向变更请求，其中携带对于所述特定方向的承载不进行分流数据传输的情况，所述用户设备的该特定方向的数据在所述主控演进型基站上发送的变更信息。
  14. 根据权利要求8-11任一权项所述的方法，其中，该方法还包括：
    当确定对于所述特定方向的承载进行分流数据传输的情况，所述用户设备的该特定方向的数据需要变更在所述主控演进型基站上发送的比例和在所述受控演进型基站上发送的比例时，所述受控演进型基站向所述主控演进型基站发送变更比例请求，其中携带在所述特定方向的承载进行分流数据传输的情况下，所述用户设备的该特定方向的数据在所述主控演进型基站上发送的比例和/或在所述受控演进型基站上发送的比例的变更信息。
  15. 一种承载接纳控制装置，该装置包括：
    受控演进型基站添加单元，用于当确定需要主控演进型基站与受控演进型基站针对同一用户设备进行承载分离时，向该受控演进型基站发送受控演进型基站添加请求消息，其中携带需要由该受控演进型基站接纳的该用户设备对应的演进的通用陆地无线接入网无线接入承载列表信息，以及对于特定方向的承载是否进行分流数据传输的指示信息，其中，所述特定方向为上行方向或下行方向；
    第一判断处理单元，用于接收所述受控演进型基站回复的反馈消息，从中获取所述受控演进型基站的承载接纳结果，若接受所述受控演进型基站的承载接纳结果，则对所述用户设备的连接进行配置；否则，向所述受控演进型基站回复拒绝接受所述受控演进型基站的承载接纳结果的消息。
  16. 根据权利要求15所述的装置，其中，所述受控演进型基站的承载接纳结果包括：
    所述受控演进型基站确定接纳或拒绝的特定方向的承载；
    对于所述特定方向的承载不进行分流数据传输的情况，所述受控演进型基站接纳的各承载在所述用户设备的该特定方向的数据通过所述受控演进型基站或通过所述主控演进型基站发送的指示信息；
    对于所述特定方向的承载进行分流数据传输的情况，所述用户设备的该特定方向的数据在所述主控演进型基站上发送的比例和/或在所述受控演进型基站上发送的比例。
  17. 根据权利要求15所述的装置，其中，所述受控演进型基站添加请求消息中，还包括：
    对于所述特定方向的承载不进行分流数据传输的情况，所述用户设备的该特定方向的数据在所述主控演进型基站上发送或者在所述受控演进型基站上发送的指示信息；
    对于所述特定方向的承载进行分流数据传输的情况，所述用户设备的该特定方向的数据在所述主控演进型基站上发送的比例和/或在所述受控演进型基站上发送的比例；
    所述受控演进型基站的承载接纳结果包括：所述受控演进型基站确定接纳或拒绝的特定方向的承载。
  18. 根据权利要求17所述的装置，其中，所述受控演进型基站的承载接纳结果还包括：
    针对所述受控演进型基站无法接纳的特定方向的承载：
    对于所述特定方向的承载不进行分流数据传输的情况，所述用户设备的该特定方向的数据在所述主控演进型基站上发送的变更信息；
    对于所述特定方向的承载进行分流数据传输的情况，所述用户设备的该特定方向的数据在所述受控演进型基站上发送的比例的变更信息。
  19. 根据权利要求15-18任一权项所述的装置，其中，所述第一判断处理单元，还用于：
    接收所述受控演进型基站发送的方向变更请求，该方向变更请求用于指示对于所述特定方向的承载不进行分流数据传输的情况，所述用户设备的该特定方向的数据在所述主控演进型基站上发送的变更信息；
    若接受所述受控演进型基站发送的方向变更请求，则对所述用户设备的连接进行配置；否则，向所述受控演进型基站回复拒绝接受所述受控演进型基站发送的方向变更请求的消息。
  20. 根据权利要求15-18任一权项所述的装置，其中，所述第一判断处理单元，还用于：
    接收所述受控演进型基站发送的变更比例请求，该变更比例请求用于指示对于所述特定方向的承载进行分流数据传输的情况，所述用户设备的该特定方向的数据在所述主控演进型基站上发送的比例和/或在所述受控演进型基站上发送的比例的变更信息；
    若接受所述受控演进型基站发送的变更比例请求，则对所述用户设备的连接进行配 置；否则，向所述受控演进型基站回复拒绝接受所述受控演进型基站发送的变更比例请求的消息。
  21. 根据权利要求15所述的装置，其中，该装置还包括：
    受控单元，用于接收主控演进型基站当确定需要与受控演进型基站针对同一用户设备进行承载分离时发送的受控演进型基站添加请求消息，从中获取需要由该受控演进型基站接纳的该用户设备对应的演进的通用陆地无线接入网无线接入承载列表信息，以及对于特定方向的承载是否进行分流数据传输的指示信息，其中，所述特定方向为上行方向或下行方向；
    第二判断处理单元，用于根据该演进的通用陆地无线接入网无线接入承载列表信息和该指示信息，生成承载接纳结果，并向主控演进型基站回复反馈消息，其中携带该承载接纳结果。
  22. 一种承载接纳控制装置，该装置包括：
    受控单元，用于接收主控演进型基站当确定需要与受控演进型基站针对同一用户设备进行承载分离时发送的受控演进型基站添加请求消息，从中获取需要由该受控演进型基站接纳的该用户设备对应的演进的通用陆地无线接入网无线接入承载列表信息，以及对于特定方向的承载是否进行分流数据传输的指示信息，其中，所述特定方向为上行方向或下行方向；
    第二判断处理单元，用于根据所述演进的通用陆地无线接入网无线接入承载列表信息和所述指示信息，生成承载接纳结果，并向所述主控演进型基站回复反馈消息，其中携带该承载接纳结果。
  23. 根据权利要求22所述的装置，其中，所述承载接纳结果，包括：
    所述受控演进型基站确定接纳或拒绝的特定方向的承载；
    对于所述特定方向的承载不进行分流数据传输的情况，所述受控演进型基站接纳的各承载在所述用户设备的该特定方向的数据通过所述受控演进型基站或通过所述主控演进型基站发送的指示信息；
    对于所述特定方向的承载进行分流数据传输的情况，所述用户设备的该特定方向的数据在所述主控演进型基站上发送的比例和/或在所述受控演进型基站上发送的比例。
  24. 根据权利要求22所述的装置，其中，所述受控演进型基站添加请求消息中，还包括：
    对于所述特定方向的承载不进行分流数据传输的情况，所述用户设备的该特定方向的数据在所述受控演进型基站上发送的指示信息；
    对于所述特定方向的承载进行分流数据传输的情况，所述用户设备的该特定方向的数据在所述主控演进型基站上发送的比例和/或在所述受控演进型基站上发送的比例；
    所述承载接纳结果，包括：所述受控演进型基站确定接纳或拒绝的特定方向的承载。
  25. 根据权利要求24所述的装置，其中，所述承载接纳结果，还包括：
    针对所述受控演进型基站无法接纳的特定方向的承载：
    对于所述特定方向的承载不进行分流数据传输的情况，所述用户设备的该特定方向的数据在所述主控演进型基站上发送的变更信息；
    对于所述特定方向的承载进行分流数据传输的情况，所述用户设备的该特定方向的数据在所述受控演进型基站上发送的比例的变更信息。
  26. 根据权利要求22-25任一权项所述的装置，其中，所述第二判断处理单元，还用于：
    当确定对于所述特定方向的承载不进行分流数据传输的情况，所述用户设备的该特定方向的数据需要变更在所述主控演进型基站上发送时，向所述主控演进型基站发送方向变更请求，其中携带对于所述特定方向的承载不进行分流数据传输的情况，所述用户设备的该特定方向的数据在所述主控演进型基站上发送的变更信息。
  27. 根据权利要求22-25任一权项所述的装置，其中，所述第二判断处理单元，还用于：
    当确定对于所述特定方向的承载进行分流数据传输的情况，所述用户设备的该特定方向的数据需要变更在所述主控演进型基站上发送的比例和在所述受控演进型基站上发送的比例时，向所述主控演进型基站发送变更比例请求，其中携带对于所述特定方向的承载进行分流数据传输的情况，所述用户设备的该特定方向的数据在所述主控演进型基站上发送的比例和/或在所述受控演进型基站上发送的比例的变更信息。
  28. 一种演进型基站，包括：处理器和收发信机；
    处理器当所述演进型基站作为主控演进型基站，并确定需要该主控演进型基站与受控演进型基站针对同一用户设备进行承载分离时，生成受控演进型基站添加请求消息，其中携带需要由该受控演进型基站接纳的该用户设备对应的演进的通用陆地无线接入网无线接入承载列表信息，以及对于特定方向的承载是否进行分流数据传输的指示信息，其中，所述特定方向为上行方向或下行方向；并触发收发信机向该受控演进型基站发送所述受控演进型基站添加请求消息；
    当所述收发信机接收到所述受控演进型基站回复的反馈消息时，所述处理器从中获取所述受控演进型基站的承载接纳结果，若接受所述受控演进型基站的承载接纳结果，则对所述用户设备的连接进行配置，并触发所述收发信机将该配置发送给所述用户设备；否则，触发所述收发信机向所述受控演进型基站回复拒绝接受所述受控演进型基站的承载接纳结果的消息。
  29. 一种演进型基站，包括：处理器和收发信机；
    当所述演进型基站作为受控演进型基站时，所述收发信机接收主控演进型基站当确定需要与该受控演进型基站针对同一用户设备进行承载分离时发送的受控演进型基站添加请求消息；
    所述处理器从受控演进型基站添加请求消息中获取需要由受控演进型基站接纳的该 用户设备对应的演进的通用陆地无线接入网无线接入承载列表信息，以及对于特定方向的承载是否进行分流数据传输的指示信息，其中，所述特定方向为上行方向或下行方向；根据该演进的通用陆地无线接入网无线接入承载列表信息和该指示信息，生成承载接纳结果，并触发所述收发信机向主控演进型基站回复反馈消息，其中携带该承载接纳结果。
PCT/CN2015/084224 2014-08-05 2015-07-16 一种承载接纳控制方法及装置 WO2016019789A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US15/327,646 US10278115B2 (en) 2014-08-05 2015-07-16 Bearer admission control method and bearer admission control apparatus
EP15829693.9A EP3179774B1 (en) 2014-08-05 2015-07-16 Bearer admission control method and bearer admission control apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410381925.5 2014-08-05
CN201410381925.5A CN104202778B (zh) 2014-08-05 2014-08-05 一种承载接纳控制方法及装置

Publications (1)

Publication Number Publication Date
WO2016019789A1 true WO2016019789A1 (zh) 2016-02-11

Family

ID=52087989

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/084224 WO2016019789A1 (zh) 2014-08-05 2015-07-16 一种承载接纳控制方法及装置

Country Status (4)

Country Link
US (1) US10278115B2 (zh)
EP (1) EP3179774B1 (zh)
CN (1) CN104202778B (zh)
WO (1) WO2016019789A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115460711A (zh) * 2021-06-08 2022-12-09 中国移动通信集团重庆有限公司 业务流量分流方法、装置、电子设备和存储介质

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6227933B2 (ja) * 2013-08-21 2017-11-08 株式会社Ｎｔｔドコモ 移動通信方法
CN104918329B (zh) * 2014-03-13 2019-06-25 中国移动通信集团公司 一种通信处理方法、装置及基站
CN104202778B (zh) 2014-08-05 2017-12-19 电信科学技术研究院 一种承载接纳控制方法及装置
CN105992181B (zh) * 2015-01-30 2019-10-25 上海诺基亚贝尔股份有限公司 在双连接系统中确定计费策略的方法和装置
JP2018510548A (ja) * 2015-02-09 2018-04-12 華為技術有限公司Ｈｕａｗｅｉ Ｔｅｃｈｎｏｌｏｇｉｅｓ Ｃｏ．，Ｌｔｄ． Ｒｌｃデータパケットオフロード方法および基地局
US10568159B2 (en) * 2015-07-03 2020-02-18 Nokia Solutions And Networks Oy Split bearer enhancement for multi-connectivity
WO2017022166A1 (ja) 2015-07-31 2017-02-09 日本電気株式会社 基地局及びその方法
CN113316203A (zh) * 2016-08-11 2021-08-27 华为技术有限公司 通信方法和装置
CN111885642B (zh) * 2016-11-02 2022-06-10 中兴通讯股份有限公司 切换方法及装置
CN110089151B (zh) * 2016-12-20 2022-05-31 苹果公司 在切换过程期间用于分组转发的系统和方法
CN108566309B (zh) * 2017-01-26 2019-08-06 华为技术有限公司 一种接入目标小区的方法以及设备
CN110324848B (zh) * 2017-06-16 2020-10-16 华为技术有限公司 信息处理方法、通信装置以及计算机存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102348244A (zh) * 2010-08-03 2012-02-08 华为技术有限公司 蜂窝通信系统、终端在小区间切换的方法及宏基站
US20120163313A1 (en) * 2010-12-23 2012-06-28 Electronics And Telecommunications Research Institute Call processing method for use in machine-type communication terminal
CN102655682A (zh) * 2011-03-03 2012-09-05 华为技术有限公司 一种采用载波汇聚方式传输数据的方法、系统及装置
CN103546928A (zh) * 2012-07-11 2014-01-29 电信科学技术研究院 一种承载管理方法、装置及系统
CN104202778A (zh) * 2014-08-05 2014-12-10 电信科学技术研究院 一种承载接纳控制方法及装置

Family Cites Families (28)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002096030A2 (de) 2000-10-09 2002-11-28 Siemens Aktiengesellschaft Verfahren zur übertragung von datenpaketen über eine luftschnittstelle eines mobilfunksystems
US8532653B2 (en) * 2006-08-11 2013-09-10 Intellectual Ventures Holding 81 Llc Managing control signalling over different radio access technologies (RATS) using different types of spectrum
CN102480712B (zh) * 2010-11-24 2015-06-03 中兴通讯股份有限公司 一种数据分流系统中的切换方法和系统
CN103517356B (zh) 2012-06-28 2017-04-05 电信科学技术研究院 一种进行切换的方法、系统和设备
EP2869656B1 (en) * 2012-07-23 2018-05-30 Huawei Technologies Co., Ltd. Data offloading method, macro base station, and small node
US9848322B2 (en) * 2013-01-17 2017-12-19 Intel IP Corporation Method, apparatus and system for managing bearers in a wireless communication system
US9173147B2 (en) * 2013-01-18 2015-10-27 Blackberry Limited Communicating data using a local wireless access network node
US9838158B2 (en) * 2013-07-17 2017-12-05 Lg Electronics Inc. Method for reporting a radio link control re-transmission failure and a device therefor
US9807818B2 (en) * 2013-08-08 2017-10-31 Industrial Technology Research Institute Method of radio bearer establishment in dual connectivity
EP2835925B1 (en) * 2013-08-09 2018-08-08 Panasonic Intellectual Property Corporation of America Efficient Status Reporting for UEs in dual connectivity during mobility
US20160157155A1 (en) * 2013-09-09 2016-06-02 Nokia Solutions And Networks Oy Selective Bearer Splitting in Cell System
GB2519975A (en) * 2013-11-01 2015-05-13 Nec Corp Communication system
JP6445032B2 (ja) * 2013-11-01 2018-12-26 サムスン エレクトロニクス カンパニー リミテッド ベアラを再構成する方法及び装置
US20150124748A1 (en) * 2013-11-01 2015-05-07 Lg Electronics Inc. Method and apparatus for performing dual-connectivity operation in heterogeneous network
KR20150061487A (ko) * 2013-11-27 2015-06-04 한국전자통신연구원 데이터 오프로딩 방법
EP2894903B1 (en) * 2014-01-13 2021-02-24 Alcatel Lucent Bearer offload in dual connectivity operation
WO2015108291A1 (en) * 2014-01-17 2015-07-23 Lg Electronics Inc. Bearer setup method and apparatus in wierless communication system supporting dual connectivity
CN104812003A (zh) * 2014-01-28 2015-07-29 上海贝尔股份有限公司 用于主基站和辅基站的流控制方法和设备
EP3720237B1 (en) * 2014-01-29 2023-08-30 Huawei Technologies Co., Ltd. Transmission of configuration messages
US9544920B2 (en) * 2014-01-30 2017-01-10 Intel IP Corporation Random access procedure for dual connectivity
US20150223095A1 (en) * 2014-01-31 2015-08-06 Telefonaktiebolaget L M Ericsson (Publ) Method for Configuring a Dual Connectivity User Equipment
US10034186B2 (en) * 2014-02-09 2018-07-24 Lg Electronics Inc. Method for calculating and submitting an amount of data available for transmission and a device therefor
US10264484B2 (en) * 2014-03-12 2019-04-16 Lg Electronics Inc. Method for calculating and reporting an amount of data available for transmission and a device therefor
CN104918232A (zh) * 2014-03-14 2015-09-16 中国移动通信集团公司 一种缓存状态的上报方法、装置、终端及基站
JP6303743B2 (ja) * 2014-04-10 2018-04-04 富士通株式会社 無線基地局
US9838282B2 (en) * 2014-05-09 2017-12-05 Telefonaktiebolaget Lm Ericsson (Publ) PDCP and flow control for split bearer
GB2528913B (en) * 2014-08-04 2017-03-01 Samsung Electronics Co Ltd Signalling in dual connectivity mobile communication networks
US20160057687A1 (en) * 2014-08-19 2016-02-25 Qualcomm Incorporated Inter/intra radio access technology mobility and user-plane split measurement configuration

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102348244A (zh) * 2010-08-03 2012-02-08 华为技术有限公司 蜂窝通信系统、终端在小区间切换的方法及宏基站
US20120163313A1 (en) * 2010-12-23 2012-06-28 Electronics And Telecommunications Research Institute Call processing method for use in machine-type communication terminal
CN102655682A (zh) * 2011-03-03 2012-09-05 华为技术有限公司 一种采用载波汇聚方式传输数据的方法、系统及装置
CN103546928A (zh) * 2012-07-11 2014-01-29 电信科学技术研究院 一种承载管理方法、装置及系统
CN104202778A (zh) * 2014-08-05 2014-12-10 电信科学技术研究院 一种承载接纳控制方法及装置

Non-Patent Citations (1)

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

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115460711A (zh) * 2021-06-08 2022-12-09 中国移动通信集团重庆有限公司 业务流量分流方法、装置、电子设备和存储介质
CN115460711B (zh) * 2021-06-08 2024-04-26 中国移动通信集团重庆有限公司 业务流量分流方法、装置、电子设备和存储介质

Also Published As

Publication number Publication date
EP3179774A1 (en) 2017-06-14
CN104202778A (zh) 2014-12-10
US20170215125A1 (en) 2017-07-27
EP3179774A4 (en) 2017-06-28
EP3179774B1 (en) 2018-10-31
US10278115B2 (en) 2019-04-30
CN104202778B (zh) 2017-12-19

Similar Documents

Publication Publication Date Title
WO2016019789A1 (zh) 一种承载接纳控制方法及装置
US11477712B2 (en) Maintaining communication and signaling interfaces through a network role transition
US10085189B2 (en) Method of controlling handover procedure and base station
KR102174932B1 (ko) 이중 연결 상태에서 데이터를 송수신하는 방법 및 그 장치
CN106941733B (zh) 双连接中实现重配置的方法、主服务基站及辅服务基站
USRE47613E1 (en) System and method for primary point handovers
CN108282836B (zh) 辅基站切换方法、装置及基站
WO2018219039A1 (zh) 一种移动切换的管理方法、装置、设备及存储介质
CN105009678B (zh) 用于在多个e节点b和用户设备之间提供同时连接的方法和系统
US9961707B2 (en) Terminal multiple connection management method, device and system
WO2015184889A1 (zh) 一种用户设备切换基站的方法及基站、用户设备
US20170325135A1 (en) Method and apparatus for performing handover of user equipment in wireless communication system supporting dual connectivity
US11323923B2 (en) Method and system for communication in wireless communication network
WO2017054538A1 (zh) 建立辅助信令链路的方法及其装置、基站及终端
CN109905849A (zh) 使用多连接来对业务进行多播
KR102016728B1 (ko) 데이터 중복 전송을 제어하는 방법 및 그 장치
KR20170043533A (ko) 인터/인트라 무선 액세스 기술 이동성 및 사용자 평면 스플릿 측정 구성
JP7147883B2 (ja) ｇＮＢ－ＣＵ－ＵＰにおける完全性保護のハンドリング
CN113709909B (zh) 多连接通信方法和设备
CN106465435A (zh) 双连接重建
US9877235B2 (en) Method and system for setup or modification of data flows, primary node, secondary node, UE and computer program product
CN103517357B (zh) 一种进行切换的方法、系统和设备
US10212750B2 (en) Method and device for establishing a dual connectivity between a user equipment and a MeNB and a SeNB, by providing the user equipment history information
WO2015018094A1 (zh) 一种消息传输方法及设备
CN105792292B (zh) 一种基站切换方法、系统及相关装置

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: 15829693

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 15327646

Country of ref document: US

REEP Request for entry into the european phase

Ref document number: 2015829693

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2015829693

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE