[go: up one dir, main page]

WO2018082597A1 - 拥塞控制方法及装置、基站 - Google Patents

拥塞控制方法及装置、基站 Download PDF

Info

Publication number
WO2018082597A1
WO2018082597A1 PCT/CN2017/109056 CN2017109056W WO2018082597A1 WO 2018082597 A1 WO2018082597 A1 WO 2018082597A1 CN 2017109056 W CN2017109056 W CN 2017109056W WO 2018082597 A1 WO2018082597 A1 WO 2018082597A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
service data
congested
data stream
congestion
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2017/109056
Other languages
English (en)
French (fr)
Inventor
刘壮
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Priority to US16/347,802 priority Critical patent/US11751096B2/en
Publication of WO2018082597A1 publication Critical patent/WO2018082597A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/11—Identifying congestion
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0273—Traffic management, e.g. flow control or congestion control adapting protocols for flow control or congestion control to wireless environment, e.g. adapting transmission control protocol [TCP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0278—Traffic management, e.g. flow control or congestion control using buffer status reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0289—Congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints

Definitions

  • the present disclosure relates to the field of wireless communications, such as a congestion control method and apparatus, and a base station.
  • TCP Transmission Control Protocol
  • ACK duplicate acknowledgement
  • IETF Internet Engineering Task Force
  • ECN Explicit Congestion Notification
  • the TCP sender receives the TCP ACK message with the ECE bit set to 1 to discover the node congestion in time, and can adopt the corresponding congestion control strategy to reduce the TCP transmission rate before the data packet is lost.
  • the original ECN is mainly to support congestion control based on TCP data stream.
  • the subsequent IETF also formulated the usage specification of ECN based on User Datagram Protocol (UDP) protocol, which is mainly applied to real-time transmission protocol of UDP (Adaptive coding rate adjustment of Real-time Transport Protocol (RTP).
  • UDP User Datagram Protocol
  • RTP Real-time Transport Protocol
  • the wireless communication network also adopts a transport layer protocol based on TCP and UDP.
  • ECN-based congestion control strategies on TCP and UDP data streams are also supported in existing wireless communication standards developed by the Third Generation Partnership Projects (3GPP).
  • the existing 3GPP ECN congestion control scheme is also to set the ECN congestion bit in the IP data packet for whether the entire base station node is congested.
  • the base station node is different from the routers and switches in the Internet. In the routers and switches, because there is no user service layer logic, the node can only identify IP packets and forward them. Therefore, nodes such as routers and switches are all for the entire transit node. Whether it is congested to set the ECN congestion bit. For a base station node in a 3GPP network, different service flows can be identified for different users.
  • QOS Quality of Service
  • GBR Guaranteed Bit Rate
  • the base station node can ensure that the GBR guaranteed rate service is not affected first, and the rate of other lower priority services is reduced, in the case that the transmission resource is limited (congested).
  • the base station sets the congestion bit of the transmitted IP packet only for whether the entire base station node is congested, which may cause the service that does not need to be slowed down to be slowed down by the transmitting end. Therefore, the existing base station side has a relatively large defect in setting the ECN congestion bit according to the congestion of the entire node of the base station instead of the user service, and needs to be improved.
  • the current 3GPP ECN congestion control scheme is only suitable for a single base station connection.
  • user traffic is transmitted only through one base station.
  • multi-connection transmission technology will be more and more widely used in order to improve user speed and meet hotspot capacity and coverage requirements.
  • one user can maintain connection with two or more base stations.
  • the user has the service data. After multiple transmission paths are generated, after a certain base station is congested, the service flow can be more distributed to other base stations for transmission.
  • the base station on a certain path generates congestion and the service that cannot represent the user is bound to be congested.
  • the rate of the sender decreases, it takes a long time to recover to the original rate, which will seriously affect the user throughput.
  • multi-connection technology can be widely used.
  • the ECN explicit congestion control scheme in the existing 3GPP wireless communication network has considerable defects and needs to be improved.
  • the embodiments of the present disclosure provide a congestion control method and apparatus, and a base station, to at least solve the problem that the base station side affects user throughput only for node congestion judgment in the related art.
  • a congestion control method including: determining whether a traffic data stream transmitted on a base station generates congestion; and if a service data stream transmitted on the base station generates congestion, a service is performed
  • the network protocol IP data packet in the data stream is set, wherein the set IP data packet is used to indicate that the service data stream transmitted by the base station generates congestion.
  • a congestion control apparatus including: a determining module configured to determine whether a traffic data stream transmitted on a base station is congested; and a setting module configured to determine in the determining module In the case that the traffic data transmitted on the base station is congested, the network protocol IP data packet in the service data stream is set, wherein the set IP data packet is used to indicate that the service data stream transmitted by the base station is congested.
  • a base station including: a first processor configured to determine whether a traffic data stream transmitted on a base station generates congestion; and a second processor configured to be in the first processor If the result of the judgment is that the service data stream transmitted on the base station is congested, the network protocol IP data packet in the service data stream is set, wherein the set IP data packet is used to indicate the service data flow generated by the base station. Congested.
  • a storage medium is also provided.
  • the storage medium is configured to store program code for performing the steps of: determining whether a traffic data stream transmitted on the base station is congested; and in the case where the traffic data stream transmitted on the base station generates a congestion, the traffic data stream
  • the network protocol IP data packet is set, wherein the set IP data packet is used to indicate that the service data stream transmitted by the base station generates congestion.
  • whether the service data flow carried by the base station is congested may be determined, and if the result of the determination is that the service data flow is congested, the IP data packet in the service data flow is set to indicate the service.
  • the data stream is congested, and the different service data can be distinguished, so that when a certain service data stream is congested and other service data streams are not congested, the service data stream that is not congested is not caused to be sent by the sender.
  • FIG. 1 is a flow chart of a congestion control method in accordance with an embodiment of the present disclosure
  • FIG. 2 is a structural block diagram of a congestion control apparatus according to an embodiment of the present disclosure
  • FIG. 3 is a schematic structural diagram of a base station according to an embodiment of the present disclosure.
  • FIG. 4 is an architectural diagram of a single connection scenario provided in accordance with an alternative embodiment of the present disclosure.
  • FIG. 5 is an architectural diagram of a core network side offload provided in accordance with an alternative embodiment of the present disclosure
  • FIG. 6 is a schematic structural diagram of a base station side offload in multiple connections according to an alternative embodiment of the present disclosure
  • FIG. 7 is a schematic flowchart of a method for determining whether to allow a base station to set ECN congestion bits for an IP data stream in a DRB of a certain transmission according to an alternative embodiment of the present disclosure
  • FIG. 8 is a schematic diagram of an apparatus for setting ECN congestion bits on a base station side according to an alternative embodiment of the present disclosure
  • FIG. 9 is a schematic diagram of a congestion control flow under single connection transmission according to an alternative embodiment of the present disclosure.
  • 10 is a schematic diagram of a congestion control flow of the present disclosure under 1A dual connectivity transmission (ie, CN side offload);
  • 11 is a schematic diagram of a congestion control flow of the present disclosure under 3C dual connectivity transmission (ie, base station side offload).
  • FIG. 1 is a flowchart of a congestion control method according to an embodiment of the present disclosure. As shown in FIG. 1, the flow includes the following steps:
  • Step S102 determining whether the service data stream transmitted on the base station generates congestion
  • Step S104 in the case that the service data stream transmitted on the base station is congested, setting a network protocol IP data packet in the service data stream, where the set IP data packet is used to indicate the service data transmitted by the base station.
  • the flow creates congestion.
  • the IP data packet in the service data stream is set to indicate the service data flow, because the service data flow carried by the base station is determined to be congested, and the result of the determination is that the service data flow is congested. Congestion is generated, and different service data can be distinguished, so that when a certain service data flow is congested and other service data flows are not congested, the traffic data flow without congestion is not slowed down by the transmitting end.
  • the problem, and thus the impact on the throughput of the user, is greatly reduced, and the problem that the base station side affects the user throughput only for the node congestion judgment in the related art can be solved.
  • step S102 may be performed by: determining whether a transmission rate of the service data flow satisfies a transmission rate requirement corresponding to the quality of service QoS; wherein, if the transmission rate requirement is not met, determining that the service data flow is congested .
  • whether the transmission rate meets the transmission rate requirement corresponding to the quality of service QoS may be determined according to at least one of the following information: channel information, transmission delay Storage area occupancy information, wireless resource invocation information, and service QoS information.
  • the method may further include: determining whether the base station allows to set a congestion bit for the IP data packet of the service data flow, where the IP data for the service data flow is allowed.
  • the packet is set to the congestion bit, the IP data packet in the service data stream is set; and the setting of the IP data packet in the service data stream includes: assigning the congestion bit in the IP data packet to a specified value, where the congestion bit For the specified value, it is used to indicate that the service data stream transmitted by the base station is congested.
  • congestion bit may be an ECN, but is not limited thereto, and the specified value may be 11, and is not limited thereto.
  • the foregoing method may be applied to at least one of the following scenarios: one terminal is connected to only one base station; one terminal is connected to multiple base stations; and the service data stream is carried only on one of the plurality of base stations.
  • a terminal is only connected to one base station, that is, a single connection.
  • the base station is set to allow setting of congestion bits for IP data packets of the service data stream; one terminal is connected to multiple base stations.
  • the traffic data flow is carried only on one base station, in which case the traffic data flow is offloaded through the core network.
  • the base station carried by the service data flow may be the primary base station or the secondary base station, and the execution body of the foregoing step S102 and step S104 may be the service.
  • the base station carried by the data stream may be the primary base station or the secondary base station, and the execution body of the foregoing step S102 and step S104 may be the service.
  • the base station carried by the data stream may be the primary base station or the secondary base station, and the execution body of the foregoing step S102 and step S104 may be the service.
  • the execution entity of the foregoing step may be a primary base station or a secondary base station
  • the service data flow may be a service data flow that is offloaded to the core network and distributed to the base station, or may be a primary base station offloaded to the base station.
  • the service data stream which may also be the entire service data stream sent by the core network, is not limited to this.
  • the foregoing base station may include: a primary base station and a plurality of secondary base stations; and one terminal is connected to the primary base station and the plurality of secondary base stations, and the service data stream is offloaded to the primary base station and the plurality of secondary base stations.
  • the method further includes at least one of the following: (i) determining, by the base station, the slave base station, whether the traffic data stream that is offloaded on the designated slave base station generates congestion; In the case that the offload generates congestion on the service data flow on the designated secondary base station, the designated secondary base station notifies the first message that the traffic flow generated by the designated secondary base station is congested. Said primary base station; and (ii) said primary base station determines that the offload is on said primary base station Whether the traffic has generated congestion.
  • step S102 may be performed after the primary base station receives the first message sent by the designated base station, and/or the determination result of the primary base station is the offloading to the In the case where the traffic data flow on the primary base station is congested, the primary base station determines whether the entire service data flow is congested.
  • the above method further includes at least one of: (i) determining, by the base station, whether the designated slave base station is congested by the designated one of the plurality of base stations; and in the case that the designated slave base station is congested, the designating from the base station The base station transmits the second message designated to be congested from the base station to the primary base station; and (ii) the primary base station determines whether the primary base station is congested.
  • the primary base station determines whether the entire service data flow is congested. .
  • whether the base station determines whether the entire service data stream is congested may be: the primary base station determines whether the service data flow that is offloaded to the designated secondary base station can be offloaded to the primary base station and the multiple Determining the entire base station from the base station other than the designated slave base station; if the service data offloaded to the designated slave base station cannot be offloaded to the master base station and the other slave base stations The traffic of the service data stream is congested; and/or the primary base station determines whether the traffic data stream destined to the primary base station can be offloaded to the plurality of slave base stations, wherein the offloading to the primary base station In the case where the upper service data stream cannot be offloaded to the plurality of slave base stations, it is determined that the entire service data stream is congested.
  • the above-mentioned primary base station is set to allow setting of congestion bits for IP data packets of the service data flow; and the designated base station and/or other secondary base stations are set to not allow congestion packets to be set for IP data packets of the service data flow.
  • the foregoing solution in the multiple connection may solve the problem that the congestion control in the related art is applicable only to the single connection situation, and the single path congestion causes the user all paths to be slowed down by the transmitting end to affect the user throughput problem.
  • portions of the embodiments of the present disclosure that contribute in essence or to the prior art may be embodied in the form of a computer software product stored in a storage medium (eg, ROM/RAM, diskette).
  • the optical disc includes a plurality of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the methods described in various embodiments of the present disclosure.
  • a congestion control device is also provided, which is used to implement the above-mentioned embodiments and optional embodiments, and has not been described again.
  • the term “module” can be a combination of software and/or hardware that implements a predetermined function.
  • the devices described in the following embodiments are implemented in software, hardware, or a combination of software and hardware, is also possible and conceivable.
  • the apparatus includes:
  • the determining module 22 is configured to determine whether the service data stream transmitted on the base station is congested
  • the setting module 24 is connected to the determining module 22, and configured to set the network protocol IP data packet in the service data stream when the judgment result of the determining module is that the service data stream transmitted by the base station is congested, wherein The set IP data packet is used to indicate that the service data stream transmitted by the base station is congested.
  • the setting module 24 sets the IP data packet in the service data flow, because the determining module 22 can determine whether the service data flow carried by the base station is congested, and if the judgment result is that the service data flow is congested, In order to indicate that the service data flow is congested, and thus different service data can be distinguished, so that when a certain service data flow is congested and other service data flows are not congested, the service data without congestion is not caused.
  • the problem that the stream is slowed down by the transmitting end, thereby greatly reducing the impact on the throughput of the user, can solve the problem that the base station side affects the user throughput only for the node congestion judgment in the related art.
  • the determining module 22 may be further configured to determine whether a transmission rate of the service data flow satisfies a transmission rate requirement corresponding to the quality of service QoS, where the service data flow is determined to be generated if the transmission rate requirement is not met. Congested.
  • the determining module 22 may be further configured to determine, according to at least one of the following information, whether the transmission rate meets a transmission rate requirement: channel information, transmission buffer occupation information, and radio resources.
  • the source invokes information and QoS information for the service.
  • the determining module 22 may further be configured to determine whether the base station allows to set a congestion bit for the IP data packet of the service data flow, where the congestion bit is allowed to be set for the IP data packet of the service data flow.
  • the setting module is further configured to assign the congestion bit in the IP data packet to a specified value, where the congestion bit is a specified value, and is used to indicate the service data transmitted by the base station. The flow creates congestion.
  • congestion bit may be an ECN, but is not limited thereto, and the specified value may be 11, and is not limited thereto.
  • the foregoing apparatus may be applied to one scenario in which one terminal is connected to only one base station; one terminal is connected to multiple base stations; and the service data stream is carried only on one of the plurality of base stations.
  • the foregoing base station may include: a primary base station and a plurality of secondary base stations; and one terminal is connected to the primary base station and the plurality of secondary base stations, and the service data stream is offloaded to the primary base station and the plurality of secondary base stations.
  • the foregoing determining module 22 may include at least one of the following: a first determining unit, located in the designated secondary base station of the plurality of secondary base stations, configured to determine whether the traffic data flow on the designated secondary base station is congested; The traffic distribution is congested on the designated traffic data flow from the base station, and the first message is sent to the primary base station by the first message indicating that the traffic data flow from the base station is congested.
  • the second determining unit is located in the primary base station and configured to determine Whether the traffic of the service stream on the primary base station is congested.
  • the second determination is performed.
  • the unit can also be configured to determine if the entire service data stream is congested.
  • the foregoing second determining unit may be further configured to: determine whether the service data flow that is offloaded to the designated secondary base station can be offloaded to the primary base station and the multiple secondary base stations except the designated secondary base station. Determining that the entire service data stream is congested if the service data offloaded to the designated secondary base station cannot be offloaded to the primary base station and the other secondary base stations And/or determining whether the traffic data stream destined to the primary base station can be offloaded to the multiple secondary base stations, wherein the traffic data flow destined to the primary base station cannot be offloaded to the multiple In the case of a slave base station, it is determined that the entire service data stream is congested.
  • the foregoing base station includes: a primary base station and a plurality of secondary base stations;
  • the determining module 22 may include at least one of the following: a third determining unit, where the terminal is connected to the primary base station and the plurality of secondary base stations, and the service data stream is offloaded to the primary base station and the multiple secondary base stations. And being located in the designated slave base station of the plurality of slave base stations, configured to determine whether the designated slave base station is congested; and if the designated slave base station is congested, sending the second message specified to be congested from the base station to The primary base station and the fourth determining unit are located in the primary base station, and are configured to determine whether the primary base station is congested.
  • the fourth determining unit may be further configured to: when the primary base station receives the second message and/or the determination result of the primary base station is that the primary base station is congested, determine the entire service. Whether the data stream is congested.
  • the foregoing fourth determining unit may be further configured to: determine whether a service data flow that is offloaded to the designated secondary base station can be offloaded to the primary base station and the multiple secondary base stations except the specified Determining that the entire service data stream is generated, where the service data offloaded to the designated slave base station cannot be offloaded to the master base station and the other slave base stations, Congesting; and/or determining whether the traffic data stream destined to the primary base station can be offloaded to the plurality of secondary base stations, wherein the traffic data stream destined to the primary base station cannot be offloaded to the In the case of a plurality of slave base stations, it is determined that the entire traffic data stream is congested.
  • the fourth determining unit and the second determining unit may be the same unit, and the third determining unit and the first determining unit may be the same unit, but is not limited thereto.
  • the primary base station is configured to allow congestion bits to be set for IP data packets of the traffic data stream; the slave base station and/or other secondary base stations are set to not allow congestion packets to be set for IP data packets of the traffic data stream.
  • the foregoing apparatus further solves the problem that the congestion control in the prior art is only applicable to a single connection situation, causing a single path to be congested, causing all the paths of the user to be slowed down by the transmitting end to affect the user throughput problem.
  • service data flow may be one of the following: the service data flow that the core network branches to the base station; the service data flow that the primary base station branches to the base station; and the entire service data flow that is sent by the core network.
  • each of the above modules may be implemented by software or hardware.
  • the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the above modules are in any combination.
  • the forms are located in different processors.
  • FIG. 3 is a schematic structural diagram of a base station according to an embodiment of the present disclosure. As shown in FIG. 3, the base station includes:
  • the first processor 32 is configured to determine whether the service data stream transmitted on the base station is congested
  • the second processor 34 is configured to set a network protocol IP data packet in the service data flow when the first processor determines that the service data flow transmitted by the base station is congested, where The set IP packet is configured to indicate that the traffic of the service data transmitted by the base station is congested.
  • the base station can determine whether the service data flow carried by the base station is congested, and if the result of the determination is that the service data flow is congested, set the IP data packet in the service data flow to indicate that the service data flow is generated. Congestion, in turn, can distinguish different service data, so that when a certain service data flow is congested and other service data flows are not congested, the uncongested service data flow is not slowed down by the transmitting end. The problem, and thus the impact on the throughput of the user, is greatly reduced, and the problem that the base station side affects the user throughput only for the node congestion judgment in the related art can be solved.
  • the foregoing first processor 32 may be further configured to determine whether a transmission rate of the service data flow satisfies a transmission rate requirement corresponding to the quality of service QoS, where the service data is determined if the transmission rate requirement is not met.
  • the flow creates congestion.
  • the foregoing first processor 32 may be further configured to determine, according to at least one of the following information, whether the transmission rate satisfies a transmission rate requirement: channel information, transmission buffer occupation information, radio resource invocation information, and service QoS information.
  • the first processor 32 may be further configured to determine whether the base station allows to set a congestion bit for the IP data packet of the service data flow, where the second processor is further configured to be in the When the judgment result of the processor is to allow the congestion of the IP data packet of the service data flow, the IP data packet in the service data flow is set; the second processor 34 can also be configured to The congestion bit in the data packet is assigned a specified value, where the congestion bit is a specified value, which is used to indicate that the service data stream transmitted by the base station is congested.
  • one terminal is only connected to the base station; or one terminal is connected to multiple base stations and the service data stream is only carried on the base station; wherein the base station is one of the plurality of base stations.
  • the embodiment of the present disclosure further provides a system, including: a primary base station, configured to determine an entire service Whether the data stream is congested; and the network protocol IP data packet in the service data stream is set in the case that the entire service data stream is congested, wherein the set IP data packet is used to indicate the base station The transmitted traffic data stream is congested.
  • the first slave base station of the plurality of slave base stations may be configured to determine whether a traffic data stream that is offloaded on the first slave base station generates congestion; and that the traffic is off at the first When the congestion is generated from the service data flow on the base station, the first message to which the traffic data flow on the first secondary base station is congested is notified to the primary base station; the primary base station may also be configured as After receiving the first message, determining whether the service data flow that is offloaded to the first secondary base station can be offloaded to the primary base station and the multiple secondary base stations except the first secondary base station.
  • the other slave base station wherein, in the case that the service data stream that is offloaded to the first slave base station cannot be offloaded to the master base station and the other slave base stations, determining that the entire service data stream is generated congestion.
  • the foregoing primary base station may be further configured to: determine whether congestion is generated by the service data flow that is offloaded to the primary base station; and that the service data flow that is offloaded to the primary base station generates congestion. And determining whether the service data flow that is offloaded to the primary base station can be offloaded to the multiple secondary base stations, where the service data flow that is offloaded to the primary base station cannot be offloaded to the multiple In the case of a slave base station, it is determined that the entire service data stream is congested.
  • the second slave base station of the plurality of slave base stations may be configured to determine whether the second slave base station is congested; and if the second slave base station is congested, The second message from the second base station is notified to the primary base station; the primary base station is further configured to determine whether the service data flow that is offloaded to the second secondary base station can be offloaded to the primary base station and the multiple a slave base station other than the second slave base station, wherein the traffic data stream destined to the second slave base station cannot be offloaded to the master base station and the other slave base stations In the above case, it is determined that the entire service data stream is congested.
  • the primary base station may be configured to determine whether the primary base station is congested; and if the primary base station is congested, determine whether the service data flow destined to the primary base station can be offloaded. And determining, by the plurality of secondary base stations, that the service data flow that is offloaded to the primary base station cannot be offloaded to the multiple secondary base stations, determining that the entire service data flow is congested.
  • the primary base station is set to allow setting of congestion bits for IP data packets of the service data flow; and the designated base station and/or other secondary base stations are set to not allow IP data packet settings for the service data flow. Congested bits.
  • the foregoing system further solves the problem that the congestion control in the prior art is only applicable to a single connection situation, causing a single path to be congested, causing all the paths of the user to be slowed down by the sending end to affect the user throughput problem.
  • Embodiments of the present disclosure also provide a computer readable storage medium.
  • the above storage medium may be provided to store computer executable instructions or program code for executing the method in Embodiment 1.
  • the foregoing storage medium may include, but not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, and a magnetic memory.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • a mobile hard disk e.g., a hard disk
  • magnetic memory e.g., a hard disk
  • the processor performs the steps of the method in Embodiment 1 according to the stored program code in the storage medium.
  • an alternative embodiment of the present disclosure includes a provision for setting ECN congestion bits for a transmitted IP data packet in a base station: an alternative embodiment of the present disclosure specifies a base station side
  • the ECN congestion bit setting is set for a user service data bearer with a specific type of QOS on the base station.
  • the base station can detect IP data packets in the DRB service of the user only if the base station detects that a certain DRB data stream is congested (or the transmission resource is limited).
  • Set ECN congestion is set by the base station side for whether the base station as a whole is congested, which is disadvantageous for accurate QOS control of a single service.
  • An optional embodiment of the present disclosure further includes a discriminating method and a discriminating device for setting an ECN congestion flag for an IP packet in a certain user service data stream (such as a certain DRB) carried by the base station: when the user and After the base station newly establishes or reconfigures the service bearer, the base station can determine whether a certain DRB of the user is offloaded to multiple base stations (Split Bearer). When the DRB is established on a single base station, the base station is allowed to allow the DRB. IP data sets the ECN congestion bit; if The DRB is established on multiple base stations, that is, the DRB service is a split bearer.
  • the base station is set to allow ECN congestion bits to be set for the IP data packet of the DRB. If the base station is a secondary base station, the base station is set to not allow ECN congestion bits to be set for the IP data packets of the DRB.
  • An optional embodiment of the present disclosure further includes a method and a step of how the base station performs congestion control in a data transmission process: after the service bearer is established or reconfigured, the base station determines the current method according to the discriminating method in the foregoing technical solution. Whether the service data DRB bearer configuration of the base station allows setting the ECN congestion bit of the IP packet of the DRB.
  • FIG. 4 is an architectural diagram of a single connection scenario according to an alternative embodiment of the present disclosure.
  • the base station according to channel/transmission buffer occupation/radio resource scheduling information, and QOS of user DRB service, etc., It is judged whether the transmission rate of the user service data can satisfy the QOS requirement, thereby determining whether the DRB is congested. If it is judged that the DRB does not generate congestion, the data is directly transmitted.
  • the base station determines whether the DRB is established on multiple base stations. If the DRB service is only carried on the base station, it is not offloaded to other base stations (in this case, the CN side split in multiple connections, reference may be made to the current Figure 5 is an architectural diagram of a core network side offload according to an alternative embodiment of the present disclosure, as shown in Figure 5, in which the user plane of the base station is downlinked. The data also comes from the core network, but the bearer management of its control plane, including the offload decision and control, is in the primary base station MeNB, and not in the MME.
  • the base station Determining whether the transmission rate of the user service data can meet the QOS requirement according to the channel/transmission buffer occupation/radio resource scheduling information and the QOS information of the user DRB service, thereby determining whether the DRB is congested. If the DRB does not generate congestion Send data directly.
  • the base station determines whether the DRB is established on multiple base stations, if the DRB
  • the service is divided by multiple base stations, which is the base station side offload in the multi-connection, and can refer to the Alternative3C architecture in the multi-connection defined in the existing 3GPP.
  • FIG. 6 is a multi-connection base station according to an alternative embodiment of the present disclosure. Schematic diagram of the side-split architecture, as shown in FIG. 6, in this architecture, the same downlink user plane DRB data stream of the primary base station is split across the base station interface, such as the Xn interface, and transmitted to multiple base stations for transmission.
  • the base station and the primary base station exchange capability information, and the primary base station forwards the DRB data to the secondary base station through the interface between the primary base station and the secondary base station, such as the Xn interface, according to the transmitted data and the existing transmission capability of the secondary base station.
  • the base station checks that the transmission capacity of the base station is limited, and the data forwarded by the primary base station cannot be transmitted in time, the base station cannot set the ECN congestion bit for the DRB data according to the discriminating method in the above technical solution, and the secondary base station needs the primary base station.
  • the transmission capability information is communicated to notify the primary base station that congestion has occurred.
  • the primary base station determines, according to the transmission capabilities of the base station and other base stations, whether more traffic splits can be transmitted on the base station and other base stations, and if so, more data is offloaded to other base stations, if not, and the DRB
  • congestion control of the RB service of the user in the 3GPP network can better perform refined QOS control, and prevent the base station side from setting congestion only for the node, causing some user service senders. Unnecessary rate reduction.
  • the present disclosure can solve the problem that the existing ECN mechanism is not applicable in the multi-connection architecture, and can avoid the ECN congestion control triggered by the congestion of only a single base station in the case of multiple connections, thereby causing the transmission end to reduce the rate, resulting in The transmission rate is reduced on all transmission paths.
  • the disclosure can effectively improve the throughput of users and networks.
  • FIG. 7 is a schematic flowchart of a method for determining whether to allow the base station to set ECN congestion bits for an IP data stream in a DRB of a certain transmission according to an alternative embodiment of the present disclosure. As shown in FIG. Methods include:
  • Step 710 This step indicates that the current user and the base station newly establish or reconfigure the user plane service DRB bearer completion.
  • Step 720 The base station may determine whether a DRB of the user is offloaded to multiple base stations (whether it is a Split Bearer).
  • Step 730 When the DRB is established on a single base station, set the base station to allow IP to the DRB.
  • the data sets the ECN congestion bit
  • Step 740 If the DRB is established on multiple base stations, that is, the DRB service is a split bearer, it is determined whether the base station is a primary base station or a secondary base station under multiple connections.
  • Step 750 If the base station is a secondary base station, the base station is set to not allow ECN congestion bits to be set for the IP data packet of the DRB.
  • Step 760 If the base station is an anchored primary base station, set the base station to allow ECN congestion bits to be set for the IP data packets of the DRB.
  • FIG. 8 is a schematic diagram of a device for setting ECN congestion bits on a base station side according to an alternative embodiment of the present disclosure, including a congestion decision module and an ECN congestion bit setting module, which will be described in detail in conjunction with FIG. 8:
  • the congestion decision module 810 determines whether the transmission rate of the user service data can meet the QOS requirement according to the channel/transmission buffer occupation/radio resource scheduling information and the QOS information of the user DRB service, thereby determining Whether the DRB is congested.
  • the significant difference between the congestion decision scheme and the related scheme in the alternative embodiment of the present disclosure is that the solution in this embodiment is to determine whether a certain QOS service data stream carried by the base station is congested; and the related scheme is to the base station. The entire node is congested for air interface judgment.
  • the significant difference between the congestion decision scheme and the related scheme in the present disclosure is that, in the solution, the ECN bit is set for the IP data stream in a certain QOS service data stream carried by the base station; The IP data stream transmitted by the entire node of the base station is set, and does not distinguish between the user and the user service bearer.
  • FIG. 9 is a schematic diagram of a congestion control flow under single connection transmission according to an alternative embodiment of the present disclosure, which will be described in detail in conjunction with FIG. 9:
  • Step 910 this step indicates that the current user and the base station newly establish or reconfigure the user plane service DRB bearer completion.
  • the user is connected to a single base station.
  • Step 920 Determine whether the base station allows ECN congestion bits to be set for a certain service DRB bearer IP data stream of the user. Since the user establishes a connection with the single base station, the base station is allowed to set ECN congestion bits for the IP data stream in the service DRB of the user.
  • Step 930 The base station determines whether the transmission rate of the user service data can meet the QOS requirement according to the channel/transmission buffer occupation/radio resource scheduling information and the QOS information of the user DRB service, thereby determining whether the DRB is congested.
  • FIG. 10 is a schematic diagram of a congestion control flow of the present disclosure under 1A dual connectivity transmission (ie, CN side offload). It should be noted that the present embodiment is described in the existing dual connectivity architecture, but is also applicable to future multiple connections, and belongs to the protection scope of the present disclosure. It will be described in detail in conjunction with Figure 10:
  • Step 1010 this step indicates that the current user and the base station newly establish or reconfigure the user plane service DRB bearer completion.
  • the user and the dual base station are connected, but the user plane data stream is offloaded on the core network side.
  • Step 1020 Determine whether the base station allows ECN congestion bits to be set for a certain service DRB bearer IP data stream of the user. Since the user plane data is offloaded on the core network side, the core network directly sends data to the primary base station and the secondary base station, so the operation is similar for the primary base station and the secondary base station, and the user DRB carried by the base station is set to allow setting of the ECN.
  • the base station determines whether the transmission rate of the user service data can meet the QOS requirement according to the channel/transmission buffer occupation/radio resource scheduling information and the QOS information of the user DRB service, thereby determining whether the DRB is congested.
  • FIG. 11 is a schematic diagram of a congestion control flow of the present disclosure under 3C dual connectivity transmission (ie, base station side offload). It should be noted that the present embodiment is described in the existing dual connectivity architecture, but is also applicable to future multiple connections, and belongs to the protection scope of the present disclosure. It will be described in detail in conjunction with Figure 11:
  • Step 1110 This step indicates that the current user and the base station newly establish or reconfigure the user plane service DRB bearer completion. In this step, the user is connected to the dual base station, and the user plane data stream is offloaded on the base station side.
  • Step 1120 in this step, the ECN congestion bit is set on the primary base station side to allow the DRB to be offloaded to the user. In this step, the ECN congestion bit is set on the DRB configured from the base station side to not allow the user to be offloaded.
  • Step 1130 The core network sends service data to the primary base station.
  • Step 1140 in this step, the flow control information and the transmission capability information are exchanged between the primary base station and the secondary base station to complete the flow control function.
  • the primary base station can know how much data can be offloaded to the secondary base station for transmission.
  • Step 1150 According to the flow control result of step 1140, the primary base station forwards the corresponding number of offloaded data to the secondary base station.
  • Step 1160 In this step, the base station determines whether the data to be distributed can be timely sent according to the channel/send buffer area occupation/radio resource scheduling information and the data transmission result, so as to determine whether the DRB is generated from the base station side. Congested.
  • Step 1170 in step 110, if it is determined by the base station that the offloaded DRB is congested from the base station, the primary base station is notified during the flow control process.
  • Step 1180 In this step, the primary base station monitors whether the DRB split by the primary and secondary base stations generates congestion according to the primary base station channel/transmission buffer area occupation/radio resource scheduling information and the flow control information exchange process with the secondary base station.
  • modules or steps of the present disclosure described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • whether the service data flow carried by the base station is congested may be determined, and if the result of the determination is that the service data flow is congested, the IP data packet in the service data flow is set to indicate the service.
  • the data stream is congested, and the different service data can be distinguished, so that when a certain service data stream is congested and other service data streams are not congested, the service data stream that is not congested is not caused to be sent by the sender.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本文公布一种拥塞控制方法及装置、基站。拥塞控制方法包括：判断基站上传输的业务数据流是否产生了拥塞；在所述基站上传输的业务数据流产生了拥塞的情况下，对业务数据流中的网络协议IP数据包进行设置，其中，所设置的IP数据包用于指示基站传输的业务数据流产生了拥塞。通过本公开，解决了相关技术中基站侧仅针对节点拥塞判断而影响用户吞吐量的问题。

Description

拥塞控制方法及装置、基站 技术领域
本公开涉及无线通信领域，例如一种拥塞控制方法及装置、基站。
背景技术
传统传输控制协议(Transmission Control Protocol，简称TCP)是隐式拥塞控制，只有检测到重复的确认字符(Acknowledgement，简称ACK)或者重传超时的时候认为发生拥塞，这种机制需要等待较长的时间才能发现链路拥塞，降低了拥塞控制的效率。为改善此种情况，互联网工程任务组IETF(The Internet Engineering Task Force，简称IETF)定义了显式拥塞通告(Explicit Congestion Notification，简称ECN)显式拥塞控制机制。TCP链路建立的时候可以进行ECN的协商，如果协商成功，当传输链路的中间节点检测到本节点发生拥塞的时候，需要将本节点传输的互联网协议(Internet Protocol，简称IP)头部ECN比特为ECN＝01或ECN＝10的IP数据包(ECN＝01或者10表示协商成功支持ECN，如果不支持ECN，ECN＝00)修改为ECN＝11，表明传输路径上发生了拥塞。TCP接收端收到IP头设置为的ECN＝11的IP数据包，就知道了传输路径上发生了拥塞，并在回复TCP ACK时将TCP头中ECE比特置1来通知发送端。TCP发送端在收到ECE比特置1的TCP ACK报文从而及时发现节点拥塞，在数据包丢失之前就可以采取相应的降低TCP发送速率的拥塞控制策略。最初ECN主要是为了支持基于TCP数据流的拥塞控制，后续IETF也制定了ECN在基于用户数据报协议(User Datagram Protocol，简称UDP)协议上的使用规范，主要是应用于UDP的实时传输协议(Real-time Transport Protocol，简称RTP)的自适应编码速率调整。对于RTP业务，当协商成功支持ECN的传输链路的中间节点检测到本节点发生拥塞的时候，可以将传输的IP数据包头部ECN比特修改为ECN＝11表明发生拥塞，当接收端接收到ECN＝11的IP数据包，可以发送命令通知发送端降低业务的编码速率。
由于无线通信网络中同样采用基于TCP和UDP的传输层协议。在第三代伙伴组织计划(Third Generation Partnership Projects，简称3GPP)制定的现有无线通信标准中也支持在TCP和UDP数据流上的基于ECN的拥塞控制策略。对于无线通信系统中的TCP业务和UDP业务，3GPP协议规定了，基站在检测到本基站节点拥塞的时候，需要将基站节点传输的ECN＝01或ECN＝10的IP数据包(表明协商成功支持ECN，如果不支持ECN，ECN＝00)修改为ECN＝11，表明当前基站节点发生了拥塞。
从上面描述可以看出，现有的3GPP的ECN拥塞控制方案，也是针对整个基站节点是否拥塞来在IP数据包中设置ECN拥塞比特位的。但基站节点和互联网中路由器，交换机等节点不同，在路由器、交换机中由于没有用户业务这层逻辑，节点只能识别IP数据包并进行转发，所以路由器、交换机这样的节点都是针对整个传输节点是否拥塞来设置ECN拥塞比特的。而对于3GPP网络中的基站节点是可以识别不同用户的不同业务流，这些业务流有不同的服务质量(Quality of Service，简称QOS)控制等级，比如不同的业务可能最大，最小允许速率，是否是保证速率业务(Guaranteed Bit Rate，简称GBR)等QOS特性都不尽相同，系统根据业务的QOS进行有区别的调度和传输。基站节点可以在传输资源受限(拥塞)的情况下，完全可以首先保证GBR保证速率业务不受影响，同时降低其他优先级较低的业务的速率。而现有3GPP ECN方案中基站仅针对整个基站节点是否拥塞来设置所传输的IP报文的拥塞比特位，这样容易导致不需要降速的业务被发送端降速了。所以现有的基站侧根据基站整个节点拥塞而不是按用户业务来设置ECN拥塞比特有比较大的缺陷，需要改进。
另外目前3GPP的ECN拥塞控制方案也仅仅适合单基站连接的情况，在这种情况下，用户业务只通过一个基站传输。在无线通信向LTE-A，5G以及未来无线系统的演进过程中，为了提高用户速率，满足热点的容量和覆盖需求，多连接传输技术会被越来越广泛的使用。在多连接技术中，一个用户可以和两个或者两个以上的基站保持连接，当一个用户的单一业务数据被分流到两个或者两个以上的基站来传输的时候，由于用户该业务数据有多条传输路径，其中某个基站产生拥塞后，此业务流可以更多的分流到其他基站上传输，所以某个路径上的基站产生拥塞并不能代表用户的该业务必然会拥塞。但是按照现有的3GPP ECN方案，当其中某个基站节点产生拥塞后，该基站就会在所传输的IP数据包中设置ECN＝11拥塞指示，而忽视了业务数据传输可以分流到其他不拥 塞的基站上，这样会导致发送端不必要的降低速率，当发送端速率降低后，需要较长的一段时间才能恢复到原始速率，这将严重影响用户吞吐量。在未来通信系统演进中，在超密集小区部署中，可以预测多连接技术会被广泛使用，当用户连接的基站越多，由于传输路径越多，越可能出现某个基站产生拥塞而触发拥塞控制，而单个节点拥塞就触发拥塞控制导致发送端降速，使得所有路径的传输速率都被降低是很不合理的。
所以现有3GPP无线通信网络中的ECN显式拥塞控制方案存在相当的缺陷，需要改进。
针对上述技术问题，目前尚未提出有效的解决方案。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为限制权利要求的保护范围。
本公开实施例提供了一种拥塞控制方法及装置、基站，以至少解决相关技术中基站侧仅针对节点拥塞判断而影响用户吞吐量的问题。
根据本发明的一个实施例，提供了一种拥塞控制方法，包括：判断基站上传输的业务数据流是否产生了拥塞；在所述基站上传输的业务数据流产生了拥塞的情况下，对业务数据流中的网络协议IP数据包进行设置，其中，所设置的IP数据包用于指示基站传输的业务数据流产生了拥塞。
根据本发明的一个实施例，提供了一种拥塞控制装置，包括：判断模块，配置为判断基站上传输的业务数据流是否产生了拥塞；设置模块，配置为在所述判断模块的判断结果为基站上传输的业务数据流产生了拥塞是的情况下，对业务数据流中的网络协议IP数据包进行设置，其中，所设置的IP数据包用于指示基站传输的业务数据流产生了拥塞。
根据本发明的一个实施例，提供了一种基站，包括：第一处理器，配置成判断基站上传输的业务数据流是否产生了拥塞；第二处理器，配置成在所述第一处理器的判断结果为基站上传输的业务数据流产生了拥塞的情况下，对业务数据流中的网络协议IP数据包进行设置，其中，所设置的IP数据包用于指示基站传输的业务数据流产生了拥塞。
根据本发明的又一个实施例，还提供了一种存储介质。该存储介质设置为存储用于执行以下步骤的程序代码：判断基站上传输的业务数据流是否产生了拥塞；在所述基站上传输的业务数据流产生了拥塞塞的情况下，对业务数据流中的网络协议IP数据包进行设置，其中，所设置的IP数据包用于指示基站传输的业务数据流产生了拥塞。
基于本公开的实施例，可以针对基站承载的业务数据流是否拥塞判断，并在判断结果为业务数据流产生了拥塞的情况下，对业务数据流中的IP数据包进行设置，以指示该业务数据流产生了拥塞，进而可以区分不同的业务数据，使得在某个业务数据流产生了拥塞而其他业务数据流并未产生拥塞的情况下，不会导致未产生拥塞的业务数据流被发送端降速的问题，进而大大减少对用户的吞吐量的影响，可以解决相关技术中基站侧仅针对节点拥塞判断而影响用户吞吐量的问题。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图概述
此处所说明的附图用来提供对本公开的进一步理解，构成本申请的一部分，本公开的示意性实施例及其说明用于解释本公开，并不构成对本公开的不当限定。在附图中：
图1是根据本公开实施例的拥塞控制方法的流程图；
图2是根据本公开实施例的拥塞控制装置的结构框图；
图3是根据本公开实施例提供的基站的结构示意图；
图4是根据本公开可选实施例提供的单连接的情况的架构图；
图5是根据本公开可选实施例提供的核心网侧分流的架构图；
图6是根据本公开可选实施例提供的多连接下基站侧分流的架构示意图；
图7是根据本公开可选实施例提供的在基站侧的判断是否允许本基站为某个传输的DRB中IP数据流的设置ECN拥塞比特的判决方法的流程示意图；
图8是根据本公开可选实施例提供的基站侧设置ECN拥塞比特的装置示意图；
图9是根据本公开可选实施例的在单连接传输下拥塞控制流程示意图；
图10是本公开在1A双连接传输下(即CN侧分流)拥塞控制流程示意图；
图11是本公开在3C双连接传输下(即基站侧分流)拥塞控制流程示意图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本公开。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本公开的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
实施例1
在本实施例中提供了一种拥塞控制方法，图1是根据本公开实施例的拥塞控制方法的流程图，如图1所示，该流程包括如下步骤：
步骤S102，判断基站上传输的业务数据流是否产生了拥塞；
步骤S104，在所述基站上传输的业务数据流产生了拥塞的情况下，对业务数据流中的网络协议IP数据包进行设置，其中，所设置的IP数据包用于指示基站传输的业务数据流产生了拥塞。
通过上述步骤，由于可以针对基站承载的业务数据流是否拥塞判断，并在判断结果为业务数据流产生了拥塞的情况下，对业务数据流中的IP数据包进行设置，以指示该业务数据流产生了拥塞，进而可以区分不同的业务数据，使得在某个业务数据流产生了拥塞而其他业务数据流并未产生拥塞的情况下，不会导致未产生拥塞的业务数据流被发送端降速的问题，进而大大减少对用户的吞吐量的影响，可以解决相关技术中基站侧仅针对节点拥塞判断而影响用户吞吐量的问题。
需要说明的是，上述步骤S102可以表现为：判断业务数据流的传输速率是否满足与服务质量QoS对应的传输速率要求；其中，在不满足传输速率要求的情况下，确定业务数据流产生了拥塞。具体地，可以根据以下至少之一信息判断传输速率是否满足与服务质量QoS对应的传输速率要求：信道信息、发送缓 存区占用信息、无线资源调用信息和业务的QoS信息。
在本公开的一个实施例中，在上述步骤S104之前，上述方法还可以包括：判断基站是否允许对业务数据流的IP数据包设置拥塞比特，其中，在允许对所述业务数据流的IP数据包设置拥塞比特的情况下，对业务数据流中的IP数据包进行设置；对业务数据流中的IP数据包进行设置包括：将IP数据包中的拥塞比特赋值为指定值，其中，拥塞比特为指定值，用于指示基站传输的业务数据流产生了拥塞。
需要说明的是，上述拥塞比特可以是ECN，但并不限于此，上述指定值可以是11，也并不限于此。
需要说明的是，上述方法可以应用于以下至少之一场景：一个终端只与一个基站连接；一个终端与多个基站连接且业务数据流仅在多个基站中的一个基站上承载。
需要说明的是，一个终端只与一个基站连接，即为单连接的情况，在该情况下，该基站被设置为允许对业务数据流的IP数据包设置拥塞比特；一个终端与多个基站连接，即为多连接的情况，在多连接的情况下，业务数据流仅在一个基站上承载，在该情况下，业务数据流是通过核心网进行分流的。
需要说明的是，在多连接且业务数据流仅在一个基站上承载的情况下，业务数据流承载的基站可以是主基站也可以是从基站，上述步骤S102和步骤S104的执行主体可以是业务数据流承载的基站。
需要说明的是，上述步骤的执行主体可以是主基站，也可以是从基站，上述业务数据流可以是分流到核心网分流到基站上的业务数据流，也可以是主基站分流到基站上的业务数据流，也可以是核心网发送的整个业务数据流并不限于此。
在本公开的一个实施例中，上述基站可以包括：主基站和多个从基站；在一个终端与主基站和多个从基站连接且业务数据流被分流到主基站和多个从基站传输的情况下，在上述步骤S102之前，上述方法还包括以下至少之一：(i)所述多个从基站中的指定从基站判断分流在所述指定从基站上的业务数据流是否产生了拥塞；在所述分流在所述指定从基站上的业务数据流产生了拥塞的情况下，所述指定从基站将分流在所述指定从基站上的业务数据流产生了拥塞的第一消息通知给所述主基站；以及(ii)所述主基站判断分流在所述主基站上的 业务数据流是否产生了拥塞。
需要说明的是，上述步骤S102可以表现为：在所述主基站接收到所述指定从基站发送的所述第一消息后和/或在所述主基站的判断结果为所述分流到所述主基站上的业务数据流产生了拥塞的情况下，所述主基站判断整个业务数据流是否产生了拥塞。
在本公开的一个实施例中，在上述一个终端与一个主基站和多个从基站连接且所述业务数据流被分流到所述主基站和多个从基站传输的情况下，在上述步骤S102之前，上述方法还包括以下至少之一：(i)所述多个从基站中的指定从基站判断所述指定从基站是否拥塞；以及在所述指定从基站拥塞的情况下，所述指定从基站将所述指定从基站拥塞的第二消息发送给所述主基站；以及(ii)所述主基站判断所述主基站是否拥塞。
需要说明的是，在所述主机站接收到所述第二消息和/或所述主基站的判断结果为所述主基站拥塞的情况下，所述主基站判断整个业务数据流是否产生了拥塞。
需要说明的是，上述基站判断整个业务数据流是否产生了拥塞可以表现为：所述主基站判断分流到所述指定从基站上的业务数据流是否能分流到所述主基站和所述多个从基站中除了所述指定从基站之外的其他从基站；在所述分流到所述指定从基站上的业务数据不能分流到述主基站和所述其他从基站的情况下，确定所述整个业务数据流产生了拥塞；和/或，所述主基站判断分流到所述主基站上的业务数据流是否能分流到所述多个从基站中，其中，在所述分流到所述主基站上的业务数据流不能分流到所述多个从基站的情况下，确定所述整个业务数据流产生了拥塞。
需要说明的是，上述主基站被设置为允许对业务数据流的IP数据包设置拥塞比特；指定从基站和/或其他从基站被设置为不允许对业务数据流的IP数据包设置拥塞比特。
需要说明的是，上述多连接下的上述方案可以解决相关技术中拥塞控制仅适用于单连接情况导致单一路径拥塞就导致用户所有路径都被发送端降速而影响用户吞吐量问题。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以 通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本公开的实施例本质上或者说对现有技术做出贡献的部分可以以计算机软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本公开各个实施例所述的方法。
实施例2
在本实施例中还提供了一种拥塞控制装置，该装置用于实现上述实施例及可选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以是实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图2是根据本公开实施例的拥塞控制装置的结构框图，如图2所示，该装置包括：
判断模块22，配置为判断基站上传输的业务数据流是否产生了拥塞；
设置模块24，与判断模块22连接，配置为在所述判断模块的判断结果为基站上传输的业务数据流产生了拥塞的情况下，对业务数据流中的网络协议IP数据包进行设置，其中，所设置的IP数据包用于指示基站传输的业务数据流产生了拥塞。
通过上述装置，由于判断模块22可以针对基站承载的业务数据流是否拥塞判断，并在判断结果为业务数据流产生了拥塞的情况下，设置模块24对业务数据流中的IP数据包进行设置，以指示该业务数据流产生了拥塞，进而可以区分不同的业务数据，使得在某个业务数据流产生了拥塞而其他业务数据流并未产生拥塞的情况下，不会导致未产生拥塞的业务数据流被发送端降速的问题，进而大大减少对用户的吞吐量的影响，可以解决相关技术中基站侧仅针对节点拥塞判断而影响用户吞吐量的问题。
需要说明的是，上述判断模块22，还可以配置为判断业务数据流的传输速率是否满足与服务质量QoS对应的传输速率要求，其中，在不满足传输速率要求的情况下，确定业务数据流产生了拥塞。
需要说明的是，上述判断模块22，还可以配置为根据以下至少之一信息判断传输速率是否满足传输速率要求：信道信息、发送缓存区占用信息、无线资 源调用信息和业务的QoS信息。
在本公开的一个实施例中，上述判断模块22，还可以配置为判断基站是否允许对业务数据流的IP数据包设置拥塞比特，其中，在允许对业务数据流的IP数据包设置拥塞比特的情况下，对业务数据流中的IP数据包进行设置；设置模块，还配置为将IP数据包中的拥塞比特赋值为指定值，其中，拥塞比特为指定值，用于指示基站传输的业务数据流产生了拥塞。
需要说明的是，上述拥塞比特可以是ECN，但并不限于此，上述指定值可以是11，也并不限于此。
需要说明的是，上述装置可以应用于以下之一场景：一个终端只与一个基站连接；一个终端与多个基站连接且业务数据流仅在多个基站中的一个基站上承载。
在本公开的一个实施例中，上述基站可以包括：主基站和多个从基站；在一个终端与主基站和多个从基站连接且业务数据流被分流到主基站和多个从基站传输的情况下，上述判断模块22可以包括以下至少之一：第一判断单元，位于多个从基站中的指定从基站中，配置为判断分流在指定从基站上的业务数据流是否产生了拥塞；在分流在指定从基站上的业务数据流产生了拥塞，将分流在指定从基站上的业务数据流产生了拥塞的第一消息通知给主基站；第二判断单元，位于主基站中，配置为判断分流在主基站上的业务数据流是否产生了拥塞。
需要说明的是，在主基站接收到指定从基站发送的第一消息后和/或在第二判断单元的判断结果为分流到主基站上的业务数据流产生了拥塞的情况下，第二判断单元还可以配置为判断整个业务数据流是否产生了拥塞。
需要说明的是，上述第二判断单元还可以配置为：判断分流到所述指定从基站上的业务数据流是否能分流到所述主基站和所述多个从基站中除了所述指定从基站之外的其他从基站上，其中，在所述分流到所述指定从基站上的业务数据不能分流到述主基站和所述其他从基站的情况下，确定所述整个业务数据流产生了拥塞；和/或，判断分流到所述主基站上的业务数据流是否能分流到所述多个从基站，其中，在所述分流到所述主基站上的业务数据流不能分流到所述多个从基站的情况下，确定所述整个业务数据流产生了拥塞。
在本公开的一个实施例中，上述基站包括：主基站和多个从基站；在一个 终端与主基站和多个从基站连接且所述业务数据流被分流到所述主基站和所述多个从基站传输的情况下，上述判断模块22可以包括以下至少之一：第三判断单元，位于所述多个从基站中的指定从基站中，配置为判断所述指定从基站是否拥塞；在所述指定从基站拥塞的情况下，将所述指定从基站拥塞的第二消息发送给所述主基站；第四判断单元，位于所述主基站中，配置为判断所述主基站是否拥塞。
需要说明的是，上述第四判断单元，还可以配置为在所述主基站接收到所述第二消息和/或所述主基站的判断结果为所述主基站拥塞的情况下，判断整个业务数据流是否产生了拥塞。
需要说明的是，上述第四判断单元，还可以配置为：判断分流到所述指定从基站上的业务数据流是否能分流到所述主基站和所述多个从基站中除了所述指定从基站之外的其他从基站上，其中，在所述分流到所述指定从基站上的业务数据不能分流到述主基站和所述其他从基站的情况下，确定所述整个业务数据流产生了拥塞；和/或，判断分流到所述主基站上的业务数据流是否能分流到所述多个从基站中，其中，在所述分流到所述主基站上的业务数据流不能分流到所述多个从基站的情况下，确定所述整个业务数据流产生了拥塞。
需要说明的是，上述第四判断单元与上述第二判断单元可以是同一个单元，上述第三判断单元与上述第一判断单元可以是同一个单元，但并不限于此。
需要说明的是，主基站被设置为允许对业务数据流的IP数据包设置拥塞比特；指定从基站和/或其他从基站被设置为不允许对业务数据流的IP数据包设置拥塞比特。
需要说明的是，上述装置还进一步解决现有技术中拥塞控制仅适用于单连接情况导致单一路径拥塞就导致用户所有路径都被发送端降速而影响用户吞吐量问题。
需要说明的是，上述业务数据流可以为以下之一：核心网分流到基站上的业务数据流；主基站分流到基站上的业务数据流；核心网发送的整个业务数据流。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
实施例3
本公开实施例中，还提供了一种基站，图3是根据本公开实施例提供的基站的结构示意图，如图3所示，该基站包括：
第一处理器32，配置为判断基站上传输的业务数据流是否产生了拥塞；
第二处理器34，配置为在所述第一处理器的判断结果为基站上传输的业务数据流产生了拥塞的情况下，对业务数据流中的网络协议IP数据包进行设置，其中，所设置的IP数据包配置为指示基站传输的业务数据流产生了拥塞。
通过上述基站，可以针对基站承载的业务数据流是否拥塞判断，并在判断结果为业务数据流产生了拥塞的情况下，对业务数据流中的IP数据包进行设置，以指示该业务数据流产生了拥塞，进而可以区分不同的业务数据，使得在某个业务数据流产生了拥塞而其他业务数据流并未产生拥塞的情况下，不会导致未产生拥塞的业务数据流被发送端降速的问题，进而大大减少对用户的吞吐量的影响，可以解决相关技术中基站侧仅针对节点拥塞判断而影响用户吞吐量的问题。
需要说明的是，上述第一处理器32，还可以配置为判断业务数据流的传输速率是否满足与服务质量QoS对应的传输速率要求，其中，在不满足传输速率要求的情况下，确定业务数据流产生了拥塞。
需要说明的是，上述第一处理器32，还可以配置为根据以下至少之一信息判断传输速率是否满足传输速率要求：信道信息、发送缓存区占用信息、无线资源调用信息和业务的QoS信息。
在本公开的一个实施例中，上述第一处理器32，还可以配置为判断基站是否允许对业务数据流的IP数据包设置拥塞比特，其中，上述第二处理器还配置成在所述第一处理器的判断结果为允许对所述业务数据流的IP数据包设置拥塞比特的情况下，对业务数据流中的IP数据包进行设置；上述第二处理器34，还可以配置为将IP数据包中的拥塞比特赋值为指定值，其中，拥塞比特为指定值，用于指示基站传输的业务数据流产生了拥塞。
需要说明的是，一个终端只与基站连接；或者一个终端与多个基站连接且业务数据流仅在基站上承载；其中，基站为多个基站中的一个基站。
本公开实施例，还提供了一种系统，包括：主基站，配置为判断整个业务 数据流是否产生了拥塞；以及在整个业务数据流产生了拥塞的情况下，对所述业务数据流中的网络协议IP数据包进行设置，其中，所设置的IP数据包用于指示所述基站传输的业务数据流产生了拥塞。
在本公开的一个实施例中，上述多个从基站中的第一从基站可以配置为判断分流在所述第一从基站上的业务数据流是否产生了拥塞；以及在分流在所述第一从基站上的业务数据流产生了拥塞的情况下，将分流在所述第一从基站上的业务数据流产生了拥塞的第一消息通知给所述主基站；上述主基站，还可以配置为接收所述第一消息后，判断所述分流到所述第一从基站上的业务数据流是否能分流到所述主基站和所述多个从基站中除了所述第一从基站之外的其他从基站上，其中，在所述分流到所述第一从基站上的业务数据流不能分流到所述主基站和所述其他从基站上的情况下，确定所述整个业务数据流产生了拥塞。
需要说明的是，上述主基站，还可以配置为判断分流到所述主基站上的业务数据流是否产生了拥塞；以及在所述分流到所述主基站上的业务数据流产生了拥塞的情况下，判断所述分流到所述主基站上的业务数据流是否能分流到所述多个从基站上，其中，在所述分流到所述主基站上的业务数据流不能分流到所述多个从基站的情况下，确定所述整个业务数据流产生了拥塞。
在本公开的一个实施例中，上述多个从基站中的第二从基站，可以配置为判断所述第二从基站是否拥塞；以及在所述第二从基站拥塞的情况下，将所述第二从基站拥塞的第二消息通知给所述主基站；上述主基站，还可以配置为判断分流到所述第二从基站上的业务数据流是否能分流到所述主基站和所述多个从基站中除了所述第二从基站之外的其他从基站上，其中，在所述分流到所述第二从基站上的业务数据流不能分流到所述主基站和所述其他从基站上的情况下，确定所述整个业务数据流产生了拥塞。
需要说明的是，上述主基站，还可以配置为将判断所述主基站是否拥塞；以及在所述主基站拥塞的情况下，判断所述分流到所述主基站上的业务数据流是否能分流到所述多个从基站上，其中，在所述分流到所述主基站上的业务数据流不能分流到所述多个从基站上的情况下，确定所述整个业务数据流产生了拥塞。
需要说明的是，主基站被设置为允许对业务数据流的IP数据包设置拥塞比特；指定从基站和/或其他从基站被设置为不允许对业务数据流的IP数据包设置 拥塞比特。
需要说明的是，上述系统还进一步解决现有技术中拥塞控制仅适用于单连接情况导致单一路径拥塞就导致用户所有路径都被发送端降速影响用户吞吐量问题。
实施例4
本公开的实施例还提供了一种计算机可读存储介质。可选地，在本实施例中，上述存储介质可以被设置为存储用于执行实施例1中的方法的计算机可执行指令或程序代码。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
可选地，在本实施例中，处理器根据存储介质中已存储的程序代码执行实施例1中的方法的步骤。
可选地，本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
为了更好地理解本公开，以下结合可选的实施例对本公开做进一步解释。
本公开提供了一种可选的实施例，本公开的可选实施例包含一种在基站中为所传输IP数据包设置ECN拥塞比特位的规定：本公开的可选实施例规定基站侧的ECN拥塞比特设置是针对该基站上具有特定一类QOS的用户业务数据承载来设置的。如针对某个DRB业务来设置的，只有基站检测到如承载的某个DRB数据流发生拥塞(或者传输资源受限)导致QOS不能满足，基站则可以针对该用户DRB业务中的IP数据报文设置ECN拥塞。在相关的方案中，ECN设置是基站侧针对基站整体是否拥塞来设置，不利于单个业务的精确QOS控制。
本公开的可选实施例还包含一种针对基站是否允许为该基站承载的某个用户业务数据流(如某个DRB)中IP数据包设置ECN拥塞标志的判别方法和判别装置：当用户和基站新建立或者重配置业务承载完成以后，基站可以判断该用户的某个DRB是否被分流到多个基站上(Split Bearer)，当该DRB建立在单基站上，则设置本基站允许对该DRB的IP数据设置ECN拥塞比特；如果该 DRB建立在多个基站上，也就是该DRB业务是分裂承载(Split Bearer)，那么如果本基站是锚定的主基站，则设置本基站为允许对该DRB的IP数据包设置ECN拥塞比特，如果本基站是从基站，则对本基站设置为不允许对该DRB的IP数据包设置ECN拥塞比特。
本公开的可选实施例还包含一种基站在数据传输过程中如何进行拥塞控制的方法和步骤：在业务承载建立或者重配完成后，基站按照上文技术方案中的判别方法，判断在本基站的业务数据DRB承载配置是否允许设置该DRB的IP数据包的ECN拥塞比特。
图4是根据本公开的可选实施例提供的单连接的情况的架构图，如图4所示，基站根据信道/发送缓存区占用/无线资源调度信息，以及用户DRB业务的QOS等信息，判断对用户业务数据的传输速率是否可以满足QOS要求，从而判断该DRB是否产生了拥塞。如果判断DRB没有产生拥塞，则直接发送数据。在基站判断该DRB产生拥塞的时候，如果该DRB中的IP数据包已经被标识为ECN＝01或ECN＝10(表明支持ECN，如果不支持ECN，则ECN＝00)，则将该IP数据包中ECN修改为ECN＝11，表明当前基站节点传输的该DRB数据流发生了拥塞。
在多连接的情况下，基站判断该DRB是否建立在多个基站上，如果该DRB业务仅在本基站上承载，没有分流到其他基站(这种情况就是多连接中CN侧分流，可以参照现有3GPP中定义的多连接中的AlternativelA架构，图5是根据本公开可选实施例提供的核心网侧分流的架构图，如图5所示，在这种架构下，从基站的用户面下行数据同样来自核心网，但其控制面的承载管理，包括分流决策及调控等，是在主基站MeNB，而不再是在MME。如果DRB业务仅在本基站承载，没有分流到其他基站，基站根据信道/发送缓存区占用/无线资源调度信息，以及用户DRB业务的QOS等信息，判断对用户业务数据的传输速率是否可以满足QOS要求，从而判断该DRB是否产生了拥塞。如果DRB没有产生拥塞，则直接发送数据。在基站判断该DRB产生拥塞的时候，如果该DRB中的IP数据包已经被标识为ECN＝01或ECN＝10(表明支持ECN，如果不支持ECN，ECN＝00)，则将该IP数据包中ECN修改为ECN＝11，表明当前基站节点传输的DRB数据流发生了拥塞。
在多连接的情况下，基站判断该DRB是否建立在多个基站上，如果该DRB 业务由多个基站分流传输，这种情况就是多连接中基站侧分流，可以参照现有3GPP中定义的多连接中的Alternative3C架构，图6是根据本公开可选实施例提供的多连接下基站侧分流的架构示意图，如图6所示，在这种架构下，主基站的同一个下行用户面DRB数据流跨基站间接口，如Xn接口，被分流到多个基站上传输。在这种情况下，从基站和主基站交互传输能力信息，主基站根据从基站已传输数据和现有传输能力，通过主基站和从基站间接口，如Xn接口，转发DRB数据给从基站传输。当从基站检查到本基站传输能力受限，无法及时传输主基站转发的数据，由于根据上文技术方案中的判别方法，从基站无法为该DRB数据设置ECN拥塞比特，从基站需要和主基站交互传输能力信息，通知主基站发生了拥塞。主基站根据本基站和其他基站传输能力，判断是否可以将数据流更多的分流在本基站和其他基站上传输，如果能，则将较多的数据分流在其他基站，如果不能，且该DRB中的IP数据包已经被标识为ECN＝01或ECN＝10(表明支持ECN，如果不支持ECN，ECN＝00)，则将主基站传输或者转发的属于该DRB的数据流中的IP数据包头的ECN比特设置修改为ECN＝11，表明当前基站节点传输的DRB数据流发生了拥塞。
采用本公开可选实施例所述的方法，在3GPP网络中对用户的RB业务进行拥塞控制，可以更好的进行精细化QOS控制，避免基站侧仅针对节点设置拥塞导致某些用户业务发送端不必要的速率降低。另外，采用本公开，可以解决现有的ECN机制在多连接架构下不适用问题，可以在多连接情况下避免由于只是某个单个基站产生拥塞触发ECN拥塞控制，而导致发送端降低速率，导致所有传输路径上传输速率都被降低。采用本公开可以有效提高用户和网络的吞吐量。
可选实施例1：
图7是根据本公开可选实施例提供的在基站侧的判断是否允许本基站为某个传输的DRB中IP数据流的设置ECN拥塞比特的判决方法的流程示意图，如图7所示，该方法包括：
步骤710 此步骤表明当前用户和基站新建立或者重配置用户面业务DRB承载完成。
步骤720 基站可以判断该用户的某个DRB是否被分流到多个基站上(是否是Split Bearer)。
步骤730 当该DRB建立在单基站上，则设置本基站允许对该DRB的IP 数据设置ECN拥塞比特；
步骤740 如果该DRB建立在多个基站上，也就是该DRB业务是分裂承载Split Bearer，则判断本基站是多连接下的主基站还是从基站。
步骤750 如果本基站是从基站，则对本基站设置为不允许对该DRB的IP数据包设置ECN拥塞比特。
步骤760 如果本基站是锚定的主基站，则设置本基站为允许对该DRB的IP数据包设置ECN拥塞比特。
可选实施例2：
图8是根据本公开可选实施例提供的基站侧设置ECN拥塞比特的装置示意图，包括拥塞判决模块和ECN拥塞比特设置模块，现结合图8予以详细说明：
拥塞判决模块810(相当于上述判断模块22)根据信道/发送缓存区占用/无线资源调度信息，以及用户DRB业务的QOS等信息，判断对用户业务数据的传输速率是否可以满足QOS要求，从而判断该DRB是否产生了拥塞。在本公开可选实施例中的拥塞判决方案和相关方案的显著区别在于，本实施例的方案是对基站承载的某个具备一定QOS的业务数据流是否拥塞进行判决；而相关方案是对基站整个节点空口拥塞进行判断。
ECN拥塞设置模块820(相当于上述的设置模块24)在判断该DRB产生了拥塞并且该基站允许为该DRB设置拥塞比特的时候，如果该DRB中的IP数据包已经被标识为ECN＝01或ECN＝10(表明支持ECN，如果不支持ECN，ECN＝00)，则将IP数据头修改为ECN＝11，表明当前基站节点传输的DRB数据流发生了拥塞。在本公开中的拥塞判决方案和相关方案的显著区别在于，本方案中，ECN比特是对基站承载的某个具备一定QOS的业务数据流中的IP数据流进行设置的；而相关方案是对基站整个节点中传输的IP数据流进行设置的，并不区分用户和用户业务承载。
可选实施例3：
图9是根据本公开可选实施例的在单连接传输下拥塞控制流程示意图，现结合图9予以详细说明：
步骤910，此步骤表明当前用户和基站新建立或者重配置用户面业务DRB承载完成。在此步骤中，用户和单基站连接。
步骤920，判断本基站是否允许对该用户的某个业务DRB承载IP数据流设置ECN拥塞比特。由于用户和单基站建立连接，则允许该基站对用户的业务DRB中IP数据流设置ECN拥塞比特。
步骤930，基站根据信道/发送缓存区占用/无线资源调度信息，以及用户DRB业务的QOS等信息，判断对用户业务数据的传输速率是否可以满足QOS要求，从而判断该DRB是否产生了拥塞。
步骤940，如果基站判断该DRB产生拥塞，并且该DRB中的IP数据包已经被标识为ECN＝01或ECN＝10(表明支持ECN，如果不支持ECN，ECN＝00)，则将IP数据头修改为ECN＝11，表明当前基站节点传输的此DRB数据流发生了拥塞。
可选实施例4：
图10是本公开在1A双连接传输下(即CN侧分流)拥塞控制流程示意图。需要说明的是，本实施例虽然是以现有的双连接架构说明，但对于未来的多连接也是适用的，属于本公开的保护范围。现结合图10予以详细说明：
步骤1010，此步骤表明当前用户和基站新建立或者重配置用户面业务DRB承载完成。在此步骤中，用户和双基站连接，但用户面数据流是在核心网侧进行分流。
步骤1020，判断本基站是否允许对该用户的某个业务DRB承载IP数据流设置ECN拥塞比特。由于用户面数据是在核心网侧分流，核心网直接下发数据到主基站和从基站，所以对于主基站和从基站操作是类似的，对本基站承载的用户DRB设置为允许设置ECN。
步骤1030，基站根据信道/发送缓存区占用/无线资源调度信息，以及用户DRB业务的QOS等信息，判断对用户业务数据的传输速率是否可以满足QOS要求，从而判断该DRB是否产生了拥塞。
步骤1040，如果基站判断该DRB产生拥塞，并且该DRB中的IP数据包已经被标识为ECN＝01或ECN＝10(表明支持ECN，如果不支持ECN，ECN＝00)， 则将IP数据头修改为ECN＝11，表明当前基站节点传输的此DRB数据流发生了拥塞。
可选实施例5：
图11是本公开在3C双连接传输下(即基站侧分流)拥塞控制流程示意图。需要说明的是，本实施例虽然是以现有的双连接架构说明，但对于未来的多连接也是适用的，属于本公开的保护范围。现结合图11予以详细说明：
步骤1110，此步骤表明当前用户和基站新建立或者重配置用户面业务DRB承载完成。在此步骤中，用户和双基站连接，用户面数据流是在基站侧进行分流。
步骤1120，在本步骤中，在主基站侧配置为允许对该用户分流的DRB设置ECN拥塞比特。在本步骤中，在从基站侧配置为不允许对该用户分流的DRB设置ECN拥塞比特。
步骤1130，核心网向主基站发送业务数据。
步骤1140，在本步骤中，主基站和从基站之间交互流控信息和传输能力信息，完成流控功能。在本步骤中，主基站可以知道能分流多少数据给从基站传输。
步骤1150根据步骤1140的流控结果，主基站转发相应数量的分流数据到从基站。
步骤1160，在本步骤中，从基站根据信道/发送缓存区占用/无线资源调度信息，以及数据传输结果等信息，判断是否能够及时下发分流的数据，从而判断该DRB在从基站侧是否产生了拥塞。
步骤1170，在步骤110中，如果从基站判断分流的DRB在从基站产生了拥塞，则在流控过程中，通知主基站。
步骤1180，在本步骤中，主基站根据主基站信道/发送缓存区占用/无线资源调度信息，以及和从基站的流控信息交互过程，监测在主从基站分流的DRB是否产生了拥塞。
步骤1190，在步骤1180中，如果主基站判断分流的用户DRB产生了拥塞， 那么对于产生拥塞的DRB，判断主/从基站现有能力是否可以传输更多数据，(在多连接架构下还需要判断是否可以更多的分流到其他不拥塞的从基站上)，如果不能，则将该DRB中的IP数据包已经被标识为ECN＝01或ECN＝10包修改为ECN＝11，表明产生拥塞。
显然，本领域的技术人员应该明白，上述的本公开的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。
以上所述仅为本公开的可选实施例而已，并不用于限制本公开，对于本领域的技术人员来说，本公开可以有各种更改和变化。
工业实用性
基于本公开的实施例，可以针对基站承载的业务数据流是否拥塞判断，并在判断结果为业务数据流产生了拥塞的情况下，对业务数据流中的IP数据包进行设置，以指示该业务数据流产生了拥塞，进而可以区分不同的业务数据，使得在某个业务数据流产生了拥塞而其他业务数据流并未产生拥塞的情况下，不会导致未产生拥塞的业务数据流被发送端降速的问题，进而大大减少对用户的吞吐量的影响，可以解决相关技术中基站侧仅针对节点拥塞判断而影响用户吞吐量的问题。

Claims (37)

  1. 一种拥塞控制方法，包括：
    判断基站上传输的业务数据流是否产生了拥塞；
    在所述基站上传输的业务数据流产生了拥塞的情况下，对所述业务数据流中的网络协议IP数据包进行设置，其中，所设置的IP数据包用于指示所述基站传输的业务数据流产生了拥塞。
  2. 根据权利要求1所述的方法，其中，判断基站上传输的业务数据流是否产生了拥塞包括：
    判断所述业务数据流的传输速率是否满足与服务质量QoS对应的传输速率要求；其中，在不满足传输速率要求的情况下，确定所述业务数据流产生了拥塞。
  3. 根据权利要求2所述的方法，其中，判断所述业务数据流的传输速率是否满足与服务质量QoS对应的传输速率要求包括：
    根据以下至少之一信息判断所述传输速率是否满足所述传输速率要求：信道信息、发送缓存区占用信息、无线资源调用信息和所述业务的QoS信息。
  4. 根据权利要求1所述的方法，其中，在对所述业务数据流中的网络协议IP数据包进行设置之前，所述方法还包括：判断所述基站是否允许对所述业务数据流的IP数据包设置拥塞比特，其中，在允许对所述业务数据流的IP数据包设置拥塞比特的情况下，对所述业务数据流中的IP数据包进行设置；
    对所述业务数据流中的IP数据包进行设置包括：将所述IP数据包中的拥塞比特赋值为指定值，其中，所述拥塞比特为所述指定值，用于指示所述基站传输的业务数据流产生了拥塞。
  5. 根据权利要求1至4中任一项所述的方法，其中，所述方法应用于以下之一场景：
    一个终端只与一个基站连接；
    一个终端与多个基站连接且所述业务数据流仅在所述多个基站中的一个基站上承载。
  6. 根据权利要求1所述的方法，其中，所述基站包括：主基站和多个从基站；在一个终端与所述主基站和所述多个从基站连接且所述业务数据流被分流 到所述主基站和所述多个从基站传输的情况下，在判断基站上传输的业务数据流是否产生了拥塞之前，所述方法还包括以下至少之一：
    (i)所述多个从基站中的指定从基站判断分流在所述指定从基站上的业务数据流是否产生了拥塞；在所述分流在所述指定从基站上的业务数据流产生了拥塞的情况下，所述指定从基站将分流在所述指定从基站上的业务数据流产生了拥塞的第一消息通知给所述主基站；以及
    (ii)所述主基站判断分流在所述主基站上的业务数据流是否产生了拥塞。
  7. 根据权利要求6所述的方法，其中，判断基站上传输的业务数据流是否产生了拥塞包括：
    在所述主基站接收到所述指定从基站发送的所述第一消息后和/或在所述主基站的判断结果为所述分流到所述主基站上的业务数据流产生了拥塞的情况下，所述主基站判断整个业务数据流是否产生了拥塞。
  8. 根据权利要求1所述的方法，其中，所述基站包括：主基站和多个从基站；在一个终端与所述主基站和所述多个从基站连接且所述业务数据流被分流到所述主基站和所述多个从基站传输的情况下，在判断基站上传输的业务数据流是否产生了拥塞之前，所述方法还包括以下至少之一：
    (i)所述多个从基站中的指定从基站判断所述指定从基站是否拥塞；在所述指定从基站拥塞的情况下，所述指定从基站将所述指定从基站拥塞的第二消息发送给所述主基站；以及
    (ii)所述主基站判断所述主基站是否拥塞。
  9. 根据权利要求8所述的方法，其中，判断基站上传输的业务数据流是否产生了拥塞包括：
    在主机站接收到所述第二消息和/或所述主基站的判断结果为所述主基站拥塞的情况下，所述主基站判断整个业务数据流是否产生了拥塞。
  10. 根据权利要求7或9所述的方法，其中，所述主基站判断所述整个业务数据流是否产生了拥塞包括：
    所述主基站判断分流到所述指定从基站上的业务数据流是否能分流到所述主基站和所述多个从基站中除了所述指定从基站之外的其他从基站上，其中，在所述分流到所述指定从基站上的业务数据不能分流到述主基站和所述其他从 基站的情况下，确定所述整个业务数据流产生了拥塞；和/或，
    所述主基站判断分流到所述主基站上的业务数据流是否能分流到所述多个从基站中，其中，在所述分流到所述主基站上的业务数据流不能分流到所述多个从基站的情况下，确定所述整个业务数据流产生了拥塞。
  11. 根据权利要求6至9中任一项所述的方法，其中，所述主基站被设置为允许对业务数据流的IP数据包设置拥塞比特；所述指定从基站和/或其他从基站被设置为不允许对所述业务数据流的IP数据包设置拥塞比特。
  12. 根据权利要求1所述的方法，其中，所述业务数据流为以下之一：
    核心网分流到所述基站上的业务数据流；
    主基站分流到所述基站上的业务数据流；
    核心网发送的整个业务数据流。
  13. 一种拥塞控制装置，其中，包括：
    判断模块，配置为判断基站上传输的业务数据流是否产生了拥塞；
    设置模块，配置为在所述判断模块的判断结果为基站上传输的业务数据流产生了拥塞的情况下，对所述业务数据流中的网络协议IP数据包进行设置，其中，所设置的IP数据包用于指示所述基站传输的业务数据流产生了拥塞。
  14. 根据权利要求13所述的装置，其中，所述判断模块，还配置为判断所述业务数据流的传输速率是否满足与服务质量QoS对应的传输速率要求，其中，在不满足传输速率要求的情况下，确定所述业务数据流产生了拥塞。
  15. 根据权利要求14所述的装置，其中，所述判断模块，还配置为根据以下至少之一信息判断所述传输速率是否满足所述传输速率要求：信道信息、发送缓存区占用信息、无线资源调用信息和所述业务的QoS信息。
  16. 根据权利要求13所述的装置，其中，所述判断模块，还配置为判断所述基站是否允许对所述业务数据流的IP数据包设置拥塞比特，其中，在允许对所述业务数据流的IP数据包设置拥塞比特的情况下，对所述业务数据流中的IP数据包进行设置；
    所述设置模块，还配置为将所述IP数据包中的拥塞比特赋值为指定值，其中，所述拥塞比特为所述指定值，用于指示所述基站传输的业务数据流产生了 拥塞。
  17. 根据权利要求13至16中任一项所述的装置，其中，所述装置应用于以下之一场景：
    一个终端只与一个基站连接；
    一个终端与多个基站连接且所述业务数据流仅在所述多个基站中的一个基站上承载。
  18. 根据权利要求13所述的装置，其中，所述基站包括：主基站和多个从基站；在一个终端与所述主基站和所述多个从基站连接且所述业务数据流被分流到所述主基站和所述多个从基站传输的情况下，所述判断模块包括以下至少之一：
    第一判断单元，位于所述多个从基站中的指定从基站中，配置成判断分流在所述指定从基站上的业务数据流是否产生了拥塞；在分流在所述指定从基站上的业务数据流产生了拥塞的情况下，将分流在所述指定从基站上的业务数据流产生了拥塞的第一消息通知给所述主基站；
    第二判断单元，位于所述主基站中，配置成判断分流在所述主基站上的业务数据流是否产生了拥塞。
  19. 根据权利要求18所述的装置，其中，在所述主基站接收到所述指定从基站发送的所述第一消息后和/或在所述第二判断单元的判断结果为所述分流到所述主基站上的业务数据流产生了拥塞的情况下，所述第二判断单元还配置成判断整个业务数据流是否产生了拥塞。
  20. 根据权利要求19所述的装置，其中，所述第二判断单元还配置成：
    判断分流到所述指定从基站上的业务数据流是否能分流到所述主基站和所述多个从基站中除了所述指定从基站之外的其他从基站上；在所述分流到所述指定从基站上的业务数据不能分流到述主基站和所述其他从基站的情况下，确定所述整个业务数据流产生了拥塞；和/或
    判断分流到所述主基站上的业务数据流是否能分流到所述多个从基站；在所述分流到所述主基站上的业务数据流不能分流到所述多个从基站的情况下，确定所述整个业务数据流产生了拥塞。
  21. 根据权利要求18所述的装置，其中，所述判断模块包括以下至少之一：
    第三判断单元，位于所述多个从基站中的指定从基站中，配置成判断所述指定从基站是否拥塞；在所述指定从基站拥塞的情况下，将所述指定从基站拥塞的第二消息发送给所述主基站；
    第四判断单元，位于所述主基站中，配置成判断所述主基站是否拥塞。
  22. 根据权利要求21所述的装置，其中，所述第四判断单元，还配置成在主基站接收到所述第二消息和/或所述主基站的判断结果为所述主基站拥塞的情况下，判断整个业务数据流是否产生了拥塞。
  23. 根据权利要求22所述的装置，其中，所述第四判断单元，还配置成：
    判断分流到所述指定从基站上的业务数据流是否能分流到所述主基站和所述多个从基站中除了所述指定从基站之外的其他从基站上；在所述分流到所述指定从基站上的业务数据不能分流到述主基站和所述其他从基站的情况下，确定所述整个业务数据流产生了拥塞；和/或，
    判断分流到所述主基站上的业务数据流是否能分流到多个所述从基站中；在所述分流到所述主基站上的业务数据流不能分流到所述多个从基站的情况下，确定所述整个业务数据流产生了拥塞。
  24. 根据权利要求20至23中任一项所述的装置，其中，所述主基站被设置为允许对业务数据流的IP数据包设置拥塞比特；所述指定从基站和/或其他从基站被设置为不允许对所述业务数据流的IP数据包设置拥塞比特。
  25. 根据权利要求13所述的装置，其中，所述业务数据流为以下之一：
    核心网分流到所述基站上的业务数据流；
    主基站分流到所述基站上的业务数据流；
    核心网发送的整个业务数据流。
  26. 一种基站，包括：
    第一处理器，配置成判断基站上传输的业务数据流是否产生了拥塞；
    第二处理器，配置成在所述第一处理器的判断结果为基站上传输的业务数据流产生了拥塞的情况下，对所述业务数据流中的网络协议IP数据包进行设置，其中，所设置的IP数据包用于指示所述基站传输的业务数据流产生了拥塞。
  27. 根据权利要求26所述的基站，其中，所述第一处理器，还配置成判断 所述业务数据流的传输速率是否满足与服务质量QoS对应的传输速率要求，其中，在不满足传输速率要求的情况下，确定所述业务数据流产生了拥塞。
  28. 根据权利要求27所述的基站，其中，所述第一处理器，还配置成根据以下至少之一信息判断所述传输速率是否满足所述传输速率要求：信道信息、发送缓存区占用信息、无线资源调用信息和所述业务的QoS信息。
  29. 根据权利要求26所述的基站，其中，所述第一处理器，还配置成判断所述基站是否允许对所述业务数据流的IP数据包设置拥塞比特；所述第二处理器还配置成在所述第一处理器的判断结果为允许对所述业务数据流的IP数据包设置拥塞比特的情况下，对所述业务数据流中的IP数据包进行设置；
    所述第二处理器，还配置为将所述IP数据包中的拥塞比特赋值为指定值，其中，所述拥塞比特为所述指定值，用于指示所述基站传输的业务数据流产生了拥塞。
  30. 根据权利要求26至29中任一项所述的基站，其中，一个终端只与所述基站连接；或者一个终端与多个基站连接且所述业务数据流仅在所述基站上承载；其中，所述基站为所述多个基站中的一个基站。
  31. 一种系统，包括：主基站和多个从基站；其中，一个终端与所述主基站和所述多个从基站连接且业务数据流被分流到所述主基站和所述多个从基站传输；
    所述主基站，配置为判断整个业务数据流是否产生了拥塞；以及在整个业务数据流产生了拥塞的情况下，对所述业务数据流中的网络协议IP数据包进行设置，其中，所设置的IP数据包用于指示所述基站传输的业务数据流产生了拥塞。
  32. 根据权利要求31所述的系统，其中，
    所述多个从基站中的第一从基站配置成判断分流在所述第一从基站上的业务数据流是否产生了拥塞；以及在所述分流在所述第一从基站上的业务数据流产生了拥塞的情况下，将所述分流在所述第一从基站上的业务数据流产生了拥塞的第一消息通知给所述主基站；
    所述主基站，还配置成接收所述第一消息后，判断所述分流到所述第一从基站上的业务数据流是否能分流到所述主基站和所述多个从基站中除了所述第 一从基站之外的其他从基站上；在所述分流到所述第一从基站上的业务数据流不能分流到所述主基站和所述其他从基站上的情况下，确定所述整个业务数据流产生了拥塞。
  33. 根据权利要求31或32所述的系统，其中，
    所述主基站，还配置为判断分流到所述主基站上的业务数据流是否产生了拥塞；以及在所述分流到所述主基站上的业务数据流产生了拥塞的情况下，判断所述分流到所述主基站上的业务数据流是否能分流到所述多个从基站上，其中，在所述分流到所述主基站上的业务数据流不能分流到所述多个从基站的情况下，确定所述整个业务数据流产生了拥塞。
  34. 根据权利要求31所述的系统，其中，
    所述多个从基站中的第二从基站，配置成判断所述第二从基站是否拥塞；以及在所述第二从基站拥塞的情况下，将所述第二从基站拥塞的第二消息通知给所述主基站；
    所述主基站，还配置为判断分流到所述第二从基站上的业务数据流是否能分流到所述主基站和所述多个从基站中除了所述第二从基站之外的其他从基站上，其中，在所述分流到所述第二从基站上的业务数据流不能分流到所述主基站和所述其他从基站上的情况下，确定所述整个业务数据流产生了拥塞。
  35. 根据权利要求31或34所述的系统，其中，所述主基站，还配置成判断所述主基站是否拥塞；以及在所述主基站拥塞的情况下，判断所述分流到所述主基站上的业务数据流是否能分流到所述多个从基站上，其中，在所述分流到所述主基站上的业务数据流不能分流到所述多个从基站上的情况下，确定所述整个业务数据流产生了拥塞。
  36. 根据权利要求32所述的系统，其中，所述主基站被设置为允许对业务数据流的IP数据包设置拥塞比特；所述指定从基站和/或所述其他从基站被设置为不允许对所述业务数据流的IP数据包设置拥塞比特。
  37. 一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令配置为执行权利要求1-12中任一项所述的方法。
PCT/CN2017/109056 2016-11-07 2017-11-02 拥塞控制方法及装置、基站 Ceased WO2018082597A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US16/347,802 US11751096B2 (en) 2016-11-07 2017-11-02 Congestion control method and device, and base station

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610988394.5A CN108064058B (zh) 2016-11-07 2016-11-07 拥塞控制方法及装置、基站
CN201610988394.5 2016-11-07

Publications (1)

Publication Number Publication Date
WO2018082597A1 true WO2018082597A1 (zh) 2018-05-11

Family

ID=62075729

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/109056 Ceased WO2018082597A1 (zh) 2016-11-07 2017-11-02 拥塞控制方法及装置、基站

Country Status (3)

Country Link
US (1) US11751096B2 (zh)
CN (1) CN108064058B (zh)
WO (1) WO2018082597A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020141933A1 (en) 2019-01-03 2020-07-09 Samsung Electronics Co., Ltd. Multi-path end-to-end connectivity for cellular mesh networks

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110708721A (zh) * 2019-09-05 2020-01-17 中国联合网络通信集团有限公司 一种数据传输方法及装置
CN111050341B (zh) * 2019-12-24 2022-02-22 展讯通信（上海）有限公司 双连接场景下空口拥塞状态的判定方法及装置
CN115428516B (zh) * 2020-04-23 2025-03-11 华为技术有限公司 一种通信方法及装置
CN114339873B (zh) * 2020-09-29 2025-04-25 中国移动通信集团山东有限公司 一种数据的发送方法和基站
CN120264501A (zh) 2021-01-15 2025-07-04 华为技术有限公司 多链路的重配置方法及装置
CN114124825B (zh) * 2021-10-26 2023-05-16 中国联合网络通信集团有限公司 一种数据传输的方法、系统、装置及存储介质
FI20225055A1 (en) * 2022-01-25 2023-07-26 Nokia Solutions & Networks Oy Method and apparatus for splitting downlink data in a dual/multi connectivity system
AU2022470393B2 (en) * 2022-07-21 2025-09-25 Zte Corporation Method, device, and system for congestion control in wireless networks
CN117692958A (zh) * 2022-09-05 2024-03-12 维沃移动通信有限公司 信息处理方法、设备及可读存储介质
US20240224114A1 (en) * 2023-01-04 2024-07-04 Verizon Patent And Licensing Inc. Method and system for congestion notification in transport nodes

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101997644A (zh) * 2009-08-24 2011-03-30 华为技术有限公司 速率调整方法、系统、编码方式选择方法和装置
CN102158896A (zh) * 2010-02-12 2011-08-17 华为技术有限公司 处理本地链路拥塞的方法和装置
CN102223663A (zh) * 2010-04-15 2011-10-19 中兴通讯股份有限公司 一种获取网络负荷的方法及系统
WO2012048026A1 (en) * 2010-10-06 2012-04-12 Qualcomm Incorporated Method and apparatus for ecn receiver driven congestion control
WO2013116255A1 (en) * 2012-01-31 2013-08-08 Alcatel-Lucent Usa Inc. Method and apparatus for providing intelligent codec rate adaptation for wireless users

Family Cites Families (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE69635880T2 (de) * 1995-09-18 2006-10-05 Kabushiki Kaisha Toshiba, Kawasaki Anlage und Methode zur Übertragung von Paketen, geeignet für eine grosse Anzahl von Eingangstoren
JPH10322392A (ja) * 1997-05-16 1998-12-04 Hitachi Ltd パケットネットワークシステム及び通信制御装置
US9414255B2 (en) * 2002-09-13 2016-08-09 Alcatel Lucent Packet flow control in a wireless communications network based on an indication contained in a packet
JP2005102104A (ja) * 2003-09-02 2005-04-14 Nippon Telegr & Teleph Corp <Ntt> Ｉｐマルチキャスト配信システムとそのレート制御方法、およびそのプログラムと記録媒体
CN1713633B (zh) * 2004-06-24 2010-07-07 华为技术有限公司 一种网络流量控制的方法
GB0701668D0 (en) * 2007-01-29 2007-03-07 Tang Bob Immediate ready implementation of virtually congestion free guaranteed service capable network: external internet nextgenTCP nextgenFTP nextgenUDPs
CN101267382A (zh) * 2007-03-13 2008-09-17 大唐移动通信设备有限公司 确定数据传输通道拥塞状态的方法及装置
EP2068511B1 (en) * 2007-12-06 2011-04-06 Alcatel-Lucent USA Inc. Controlling congestion in a packet switched data network
CN101577938B (zh) * 2008-05-07 2011-06-01 华为技术有限公司 无线网状网络拥塞控制方法及系统和基站
WO2010056158A1 (en) * 2008-11-11 2010-05-20 Telefonaktiebolaget L M Ericsson (Publ) Method and device for enabling indication of congestion in a telecommunications network
US8427949B2 (en) * 2009-08-07 2013-04-23 Future Wei Technologies, Inc. System and method for adapting a source rate
EP2471302B1 (en) * 2009-08-25 2014-03-05 Telefonaktiebolaget LM Ericsson (publ) Using the ecn mechanism to signal congestion directly to the base station
CN101646196A (zh) * 2009-08-31 2010-02-10 华为技术有限公司 保证业务服务质量的方法及装置
CN101765145A (zh) * 2009-12-22 2010-06-30 中兴通讯股份有限公司 无线通信系统中拥塞判决及解除方法和装置
CN102281183B (zh) * 2010-06-09 2015-08-26 中兴通讯股份有限公司 处理网络拥塞的方法、装置和核心网络实体
US9549339B2 (en) * 2011-11-09 2017-01-17 Telefonaktiebolaget Lm Ericsson (Publ) Radio network node, network control node and methods therein
CN104125607A (zh) * 2013-04-23 2014-10-29 中兴通讯股份有限公司 用户面拥塞处理方法、装置及服务网关
CN103888846B (zh) * 2014-03-04 2017-02-08 浙江大学 基于QoE的无线视频流业务自适应速率控制方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101997644A (zh) * 2009-08-24 2011-03-30 华为技术有限公司 速率调整方法、系统、编码方式选择方法和装置
CN102158896A (zh) * 2010-02-12 2011-08-17 华为技术有限公司 处理本地链路拥塞的方法和装置
CN102223663A (zh) * 2010-04-15 2011-10-19 中兴通讯股份有限公司 一种获取网络负荷的方法及系统
WO2012048026A1 (en) * 2010-10-06 2012-04-12 Qualcomm Incorporated Method and apparatus for ecn receiver driven congestion control
WO2013116255A1 (en) * 2012-01-31 2013-08-08 Alcatel-Lucent Usa Inc. Method and apparatus for providing intelligent codec rate adaptation for wireless users

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020141933A1 (en) 2019-01-03 2020-07-09 Samsung Electronics Co., Ltd. Multi-path end-to-end connectivity for cellular mesh networks
EP3906723A4 (en) * 2019-01-03 2022-10-05 Samsung Electronics Co., Ltd. END-TO-END MULTI-PATH CONNECTIVITY FOR MESH CELLULAR NETWORKS

Also Published As

Publication number Publication date
CN108064058A (zh) 2018-05-22
CN108064058B (zh) 2022-11-01
US11751096B2 (en) 2023-09-05
US20190297527A1 (en) 2019-09-26

Similar Documents

Publication Publication Date Title
WO2018082597A1 (zh) 拥塞控制方法及装置、基站
US9716653B2 (en) System and method for flow-based addressing in a mobile environment
CN103959882B (zh) 移动网络的基站中的拥塞处置
JP6983885B2 (ja) 基地局装置及び無線区間のＱｏＳ制御方法
JP2021530135A (ja) パス変更方法および装置
CN110831075A (zh) 数据传输方法及装置，业务切换方法及装置
WO2021027860A1 (zh) 路由方法、bsr的生成方法、装置和存储介质
US10285090B2 (en) Data offloading path establishing method and device
CN107925905A (zh) 用于处理向wlan载波卸载drb的方法和无线通信系统
WO2015027719A1 (zh) 一种协作多流传输数据的方法及基站
CN105264845A (zh) 数据传输控制节点、通信系统及数据传输管理方法
WO2017198132A1 (zh) 数据发送方法及装置
CN106465177A (zh) 支持被关注和未被关注服务的演进型Node‑B、移动管理实体、用户设备以及方法
KR20230091908A (ko) 패킷 리라우팅을 위한 방법 및 장치
TWI721333B (zh) 在無線通訊系統中建立承載的方法和裝置
CN114079871A (zh) 信息控制方法、装置及基站
CN1996933B (zh) 对实时组播业务进行拥塞控制的方法
CN103067937B (zh) 状态信息处理方法与系统
CN116347506A (zh) 节点及其方法
US10075959B2 (en) Method and apparatus for controlling uplink coverage in wireless communication system
WO2020192250A1 (zh) 无线承载建立方法及装置
CN114390593A (zh) 一种iab网络中的通信方法及其装置
CN109803390B (zh) 消息、策略发送方法及装置，存储介质，处理器
CN107431940B (zh) 用于在无线通信系统中控制上行链路的覆盖的方法和装置
US20240414582A1 (en) Method for coexistence of low latency, low loss and scalable throughput (l4s) and non-l4s traffic in 5g-type networks

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17866566

Country of ref document: EP

Kind code of ref document: A1