WO2021164471A1 - 拥塞控制方法、装置、设备、介质及系统 - Google Patents

拥塞控制方法、装置、设备、介质及系统 Download PDF

Info

Publication number
WO2021164471A1
WO2021164471A1 PCT/CN2021/071418 CN2021071418W WO2021164471A1 WO 2021164471 A1 WO2021164471 A1 WO 2021164471A1 CN 2021071418 W CN2021071418 W CN 2021071418W WO 2021164471 A1 WO2021164471 A1 WO 2021164471A1
Authority
WO
WIPO (PCT)
Prior art keywords
gateway
service
application server
coordination
congestion control
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/CN2021/071418
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 KR1020227007750A priority Critical patent/KR102767398B1/ko
Priority to US17/764,294 priority patent/US12245073B2/en
Priority to EP21756626.4A priority patent/EP4109941A4/en
Publication of WO2021164471A1 publication Critical patent/WO2021164471A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0289—Congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12—Discovery or management of network topologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0876—Network utilisation, e.g. volume of load or congestion level
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/16—Threshold monitoring
    • 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/12—Avoiding congestion; Recovering from congestion
    • H04L47/122—Avoiding congestion; Recovering from congestion by diverting traffic away from congested entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/288—Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/02—Resource partitioning among network components, e.g. reuse partitioning
    • H04W16/04—Traffic adaptive resource partitioning
    • 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/0215—Traffic management, e.g. flow control or congestion control based on user or device properties, e.g. MTC-capable devices
    • 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/0284—Traffic management, e.g. flow control or congestion control detecting congestion or overload during communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution
    • H04W28/09—Management thereof
    • H04W28/0925—Management thereof using policies
    • H04W28/0942—Management thereof using policies based on measured or predicted load of entities- or links
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints
    • H04W28/12—Flow control between communication endpoints using signalling between network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16Y—INFORMATION AND COMMUNICATION TECHNOLOGY SPECIALLY ADAPTED FOR THE INTERNET OF THINGS [IoT]
    • G16Y10/00—Economic sectors
    • G16Y10/75—Information technology; Communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/14—Backbone network devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/16—Gateway arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/02—Inter-networking arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/045—Interfaces between hierarchically different network devices between access point and backbone network device
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/24—Interfaces between hierarchically similar devices between backbone network devices

Definitions

  • This application relates to the field of communication technology, for example, to a congestion control method, device, device, medium, and system.
  • Massive Machine Type Communication (mMTC, Massive Machine Type Communication), as one of the three application scenarios defined by the 5th Generation Mobile Communication Technology (5G) Communication technology (the 4th Generation Mobile Communication Technology, 4G) is increased by 10-100 times, supporting the connection of 1 million devices per square kilometer, and the number of supported device connections is at least 100 billion. With such massive access, network congestion will become inevitable , How to achieve congestion control has become an urgent problem to be solved.
  • 5G 5th Generation Mobile Communication Technology
  • This application provides a congestion control method, device, equipment, medium, and system to implement congestion control and meet the application requirements of the 5G Internet of Things.
  • the embodiment of the present application provides a congestion control method, which is applied to a first gateway, and includes:
  • the second gateway is a collaborative gateway of the first gateway
  • the embodiment of the present application provides a congestion control method, which is applied to a central gateway, and includes:
  • the second gateway After receiving the service overload notification of the second gateway sent by the first gateway, and/or after receiving the service recovery notification of the second gateway sent by the first gateway, adjust the network status of the governed gateway according to the current network status.
  • Collaboration relationship wherein, the second gateway is a collaborative gateway of the first gateway.
  • the embodiment of the present application provides a congestion control method, which is applied to an application server, and includes:
  • the service coordination request of the second gateway sent by the first gateway If the service coordination request of the second gateway sent by the first gateway is received, perform service forwarding settings for the second gateway; wherein, the second gateway is a collaborative gateway of the first gateway.
  • An embodiment of the present application provides a congestion control system, including: an application server, a central gateway, and at least one first gateway, where:
  • the central gateway is connected to the application server and each first gateway, and is configured to adjust the coordination relationship of the gateways under its jurisdiction according to the network status of the current network, and send a coordination relationship update message of the current network to the application server;
  • the first gateway is connected to the application server and the second gateway, and is used to monitor the node status information of the second gateway, and notify the central gateway of the service of the second gateway according to the node status information Overload or recovery, sending a service coordination request or service coordination cancellation request of the second gateway to the application server; wherein, the second gateway is a collaborative gateway of the first gateway;
  • the application server is configured to perform service forwarding settings for the second gateway when receiving the service coordination request of the second gateway sent by the first gateway, or, after receiving the first gateway sent by the first gateway, When the service coordination cancellation request of the two gateways is performed, the service forwarding cancellation setting is performed for the second gateway.
  • An embodiment of the present application provides a congestion control device, which is applied to a first gateway, and includes:
  • a monitoring module configured to monitor node status information of a second gateway; wherein, the second gateway is a collaborative gateway of the first gateway;
  • the reporting and requesting module is configured to notify the central gateway of the service overload of the second gateway when the node status information indicates the service overload of the second gateway, and send the service coordination request of the second gateway to the application server ;
  • the embodiment of the present application provides a congestion control device, which is applied to a central gateway, and includes:
  • the coordination relationship adjustment module is configured to, after receiving the service overload notification of the second gateway sent by the first gateway, and/or, after receiving the service recovery notification of the second gateway sent by the first gateway, according to the current network Status, adjust the coordination relationship of the governed gateways; wherein, the second gateway is a coordination gateway of the first gateway.
  • the embodiment of the present application provides a congestion control device, which is applied to an application server, and includes:
  • the congestion control module is configured to perform service forwarding settings for the second gateway if a service coordination request of the second gateway sent by the first gateway is received; wherein, the second gateway is a collaborative gateway of the first gateway .
  • the embodiment of the present application provides a gateway including: one or more processors; a storage device for storing one or more programs; when the one or more programs are executed by the one or more processors, such that The one or more processors implement the congestion control method applied to the first gateway according to any embodiment of the present application, or implement the congestion control method applied to the central gateway according to any embodiment of the present application.
  • An embodiment of the present application provides an application server, including: one or more processors; a storage device, configured to store one or more programs; when the one or more programs are executed by the one or more processors, The one or more processors are caused to implement the congestion control method applied to the application server as described in any embodiment of the present application.
  • An embodiment of the present application provides a storage medium that stores a computer program that, when executed by a processor, implements the congestion control method described in any embodiment of the present application.
  • Figure 1 is a schematic structural diagram of a congestion control system provided by this application.
  • FIG. 2 is a schematic diagram of an IoT edge gateway provided by this application.
  • FIG. 3 is a schematic flowchart of a congestion control method provided by this application.
  • FIG. 4 is a schematic flowchart of a congestion control method provided by this application.
  • FIG. 5 is a schematic flowchart of a congestion control method provided by this application.
  • FIG. 6 is a schematic structural diagram of a congestion control device provided by this application.
  • FIG. 7 is a schematic structural diagram of a congestion control device provided by this application.
  • FIG. 8 is a schematic structural diagram of a congestion control device provided by this application.
  • FIG. 9 is a schematic structural diagram of a gateway provided by this application.
  • FIG. 10 is a schematic structural diagram of an application server provided by this application.
  • FIG. 11 is a schematic structural diagram of a congestion control system provided by this application.
  • the congestion control system provided by the present application includes: an application server 10, a central gateway 20, and at least one first gateway 30 (ie, gateway 1 to gateway n in Fig. 1).
  • the central gateway 20 is connected to the application server 10 and each first gateway 30, and is used to adjust the coordination relationship of the gateways under the jurisdiction according to the network status of the current network, and send the coordination relationship update message of the current network to the application server 10.
  • the first gateway 30 is connected to the application server 10 and the second gateway, and is used to monitor the node status information of the second gateway, and notify the central gateway 20 of the service overload or recovery of the second gateway according to the node status information.
  • the application server 10 sends the service coordination request or the service coordination cancellation request of the second gateway.
  • the second gateway is a collaborative gateway of the first gateway 30. Taking the first gateway 30 as gateway 1 in FIG. 1 as an example, the collaborative gateways are gateway 2 and gateway 3, and gateway 2 can be referred to as The second gateway, gateway 3 may also be referred to as the above-mentioned second gateway.
  • the application server 10 is configured to perform service forwarding settings for the second gateway when receiving the service coordination request of the second gateway sent by the first gateway 30, or, upon receiving the service coordination request sent by the first gateway 30 When the service coordination cancellation request of the second gateway is performed, the service forwarding cancellation setting is performed for the second gateway.
  • each gateway in the network needs to upload data information to the application server.
  • the first gateway is a common gateway in the network, and each first gateway has at most two cooperative gateways.
  • the cooperative gateways can monitor each other’s survival status and backup each other’s data information; and the central gateway is selected in the network
  • a special first gateway the number is one, it not only has all the functions of a normal gateway, but also has a designated function, that is, according to the network status, all the gateways in the network are assigned cooperative gateways, which can be specifically based on the network topology, node status, etc.
  • the information assigns cooperative gateways to all gateways in the network.
  • the application server performs service forwarding settings for the second gateway according to the service coordination request of the second gateway sent by the first gateway, or, when receiving the service coordination cancellation request of the second gateway sent by the first gateway, The second gateway performs service forwarding cancellation settings.
  • the gateway involved in this application may be an IoT (Internet of Things, Internet of Things) gateway, or another type of gateway, it may be a separate gateway device, or it may be deployed in other devices.
  • IoT gateway Internet of Things, Internet of Things
  • MEC Mobile Edge Computing
  • MEC mobile edge-to-end delivery delay of mobile services
  • edge includes not only mobile terminals and mobile communication base stations, but also other specific devices in the wireless network (such as base station aggregation nodes).
  • the IoT gateway is the link between the sensor network and the traditional communication network. In the wireless sensor network, it is an indispensable core device. Because IoT devices at the end of the network often have limited resources in terms of computing and storage, they cannot support the traditional Transmission Control Protocol/Internet Protocol (TCP/IP) protocol stack, and can only run simple communication protocols. Therefore, IoT The gateway needs to perform related protocol conversion functions to support access control requests from the Internet.
  • TCP/IP Transmission Control Protocol/Internet Protocol
  • the MEC system provides conditions for supporting such IoT services.
  • the IoT gateway can be deployed in a software-based manner in the MEC system.
  • the processing capabilities of the edge server can be used to provide support for a variety of different IoT protocols, and provide more Multiple functions to enhance the manageability of the IoT network, thereby simplifying deployment and improving business flexibility.
  • a central IoT gateway needs to be determined in the IoT network, and each IoT gateway needs to upload data information to the IoT application server.
  • each IoT gateway has at most two collaborative gateways.
  • the collaborative IoT gateways can monitor each other’s survival status and back up each other’s data information;
  • the central IoT gateway has all the functions of a common IoT gateway and has a designated function. That is, according to information such as network topology, node status, etc., coordinated gateways are allocated to all IoT gateways in the IoT network.
  • FIG. 3 is a schematic flowchart of a congestion control method provided by this application. This method can be applied to the situation of network congestion in large-scale machine type communication. The method can be executed by the congestion control device applied to the first gateway provided by the present application, and the congestion control device can be implemented by software and/or hardware and integrated in the gateway.
  • a congestion control method provided by the present application, applied to the first gateway includes:
  • S310 Monitor the node state information of the second gateway; where the second gateway is a collaborative gateway of the first gateway.
  • Any gateway in the network except the central gateway can be called the first gateway, and the collaborative gateway of the first gateway is called the second gateway.
  • Each first gateway monitors the node status information of its collaborative gateway (that is, the second gateway), for example, monitors the application information or device information of its collaborative gateway, which can specifically be node bandwidth information, whether it is overloaded, device operating speed, etc. Wait.
  • the first gateway may determine the service congestion status of the second gateway according to the node status information of the second gateway, whether it is service overload or service recovery.
  • the first gateway determines that the service load of the second gateway reaches the first preset threshold according to the node status information of the second gateway, it can determine that the service of the second gateway is overloaded.
  • the first gateway determines that the service load of the second gateway is lower than the first preset threshold or the second preset threshold according to the node status information of the second gateway, it can determine that the service of the second gateway is restored .
  • the threshold for the first gateway to determine the service overload or recovery of the second gateway may be the same, for example, it is determined based on the first preset threshold, and the threshold for the first gateway to determine the service overload or recovery of the second gateway The value may also be different.
  • the first preset threshold is used to determine whether the service is overloaded
  • the second preset threshold is used to determine whether the service is restored
  • the second preset threshold is lower than the first preset threshold.
  • the first gateway judges whether the service carrying capacity of its cooperative gateway (gateway B) reaches the first preset threshold according to the node status information of the second gateway (for example, gateway B) received by it, and if so, The notification message is sent to the central gateway of the network, the central gateway is notified of the service overload of the second gateway (gateway B), and the service coordination request of the second gateway (gateway B) is sent to the application server.
  • the service coordination request is used to request the application server to forward the service message of the second gateway, that is, the gateway A requests the application server to forward the service message of the gateway B.
  • the central gateway After the central gateway receives the service overload notification of the second gateway sent by the first gateway, it adjusts the coordination relationship of the gateways under its jurisdiction according to the current network state, specifically according to the current network topology state and/or node state.
  • the central gateway reassigns a collaborative gateway (for example, gateway C) to the first gateway (that is, gateway A) according to the topological status and/or node status of the current network.
  • a collaborative gateway for example, gateway C
  • the central gateway determines that there are some gateways in the current network according to the current network topology status and/or node status, and its current collaborative gateway is not optimal, then it will re-allocate collaborative gateways to these gateways, that is, these gateways.
  • the collaborative gateway after reallocation is better than the collaborative gateway before reallocation.
  • the central gateway After adjusting the coordination relationship of the gateways under its jurisdiction, the central gateway sends a coordination relationship update message to the application server. After receiving the coordination relationship update message sent by the central gateway, the application server updates the gateway coordination relationship configuration information of the corresponding network.
  • the application server After receiving the service coordination request of the second gateway (gateway B) sent by the first gateway (gateway A), the application server performs service forwarding settings for the second gateway (gateway B). In an example, the application server retrieves whether there is a suspended service message of the second gateway (gateway B) locally according to the identifier of the second gateway (gateway B), and if it exists, the suspended service of the second gateway The message is forwarded to the first gateway, and if it does not exist, a forwarding flag is set for the second gateway (gateway B), where the forwarding flag is used to indicate to forward the service message of the second gateway.
  • the forwarding flag is set for the second gateway (gateway B)
  • a service message needs to be sent to the second gateway (gateway B)
  • it is configured according to the gateway coordination relationship of the network where the second gateway (gateway B) is located
  • the information determines the current collaborative gateway of the second gateway (gateway B), and forwards the service message of the second gateway (gateway B) to the current collaborative gateway, so as to solve the congestion problem of the second gateway (gateway B).
  • the collaborative gateway of the second gateway will change according to the central gateway's adjustment of the coordination relationship of the gateways under its jurisdiction. Therefore, at this time, the current collaborative gateway of the second gateway (gateway B) may be gateway A or gateway D ( Gateway D is the collaborative gateway redistributed by the central gateway to gateway B). Furthermore, when the application server needs to send a service message to the second gateway (gateway B), it sends the current collaborative gateway of the second gateway (gateway B), that is, to the current collaborative gateway of the second gateway (gateway B). The gateway A or the gateway D forwards the service message of the second gateway (gateway B).
  • the current collaborative gateway (gateway A or gateway D) of the second gateway (gateway B) judges whether the service of its collaborative gateway (gateway B) is restored according to the node status information of the second gateway (gateway B) it receives Specifically, it can be determined according to the node status information of the second gateway (gateway B) whether the service carrying capacity of the second gateway (gateway B) is lower than the first preset threshold or the second preset threshold, and if so, the notification message is sent to The central gateway of the network notifies the central gateway of the service recovery of the second gateway (gateway B), and sends the service coordination cancellation request of the second gateway (gateway B) to the application server.
  • the service coordination cancellation request is used to request the application server to cancel forwarding the service message of the second gateway, that is, the gateway A or the gateway D requests the application server to cancel forwarding the service message of the gateway B.
  • gateway A sends a service overload notification of gateway B to the central gateway, and sends a service coordination request of gateway B to the application server. It is assumed that during the service forwarding setting of gateway B by the application server, the central gateway will coordinate with gateway B. The gateway is adjusted from gateway A to gateway D.
  • gateway D When the central gateway announces to gateway D, it will also inform gateway D that gateway B is in a service overload state at this time, and then after gateway D and gateway B establish a cooperative relationship, they will receive the gateway forwarded by the application server B's service message, and by monitoring the node status information of gateway B, determine whether the service of gateway B is restored, and when it is determined that the service of gateway B is restored, notify the central gateway of the service of the second gateway (gateway B) Restore, and send the service coordination cancellation request of the second gateway (gateway B) to the application server.
  • the central gateway After the central gateway receives the service recovery notification of the second gateway (gateway B) sent by the first gateway (gateway A or gateway D), it can be based on the current network status, specifically according to the current network topology status and/or node status , Adjust the coordination relationship of the gateways under its jurisdiction.
  • the central gateway determines that there are some gateways in the current network according to the current network topology status and/or node status, and its current collaborative gateway is not optimal, it will re-allocate collaborative gateways to these gateways, that is, these gateways.
  • the collaborative gateway after reallocation is better than the collaborative gateway before reallocation.
  • the central gateway After adjusting the coordination relationship of the gateways under its jurisdiction, the central gateway sends a coordination relationship update message to the application server. After receiving the coordination relationship update message sent by the central gateway, the application server updates the gateway coordination relationship configuration information of the corresponding network.
  • the application server After the application server receives the service coordination cancellation request of the second gateway (gateway B) sent by the first gateway (gateway A or gateway D), it performs service forwarding cancellation settings for the second gateway (gateway B). Specifically, according to the second gateway (gateway B) The identifier of the gateway (gateway B) locally retrieves whether there is a forwarding flag set for the second gateway (gateway B), and if so, the second gateway (gateway B) revokes the forwarding flag.
  • gateway A, gateway B, gateway C, and gateway D involved in this application are all the first gateway mentioned in this application, and they can all perform the congestion control applied to the first gateway provided by this application. method.
  • the above technical solution realizes the congestion control of the collaborative gateway, where the gateway may be an IoT edge gateway to realize the congestion control processing capability of the IoT edge gateway, thereby meeting the further requirements of the 5G IoT application for the IoT edge gateway.
  • FIG. 4 is a schematic flowchart of a congestion control method provided by this application. This method can be applied to the situation of network congestion in large-scale machine type communication. The method can be executed by the congestion control device applied to the central gateway provided by this application, and the congestion control device can be implemented by software and/or hardware and integrated in the gateway.
  • a congestion control method provided by this application, applied to a central gateway includes:
  • the central gateway After the central gateway receives the service overload notification of the second gateway sent by the first gateway, and/or after receiving the service recovery notification of the second gateway sent by the first gateway, according to the current network status, it can be specifically based on The current network topology status and/or node status adjusts the coordination relationship of the gateways under its jurisdiction.
  • the central gateway reassigns a collaborative gateway to the first gateway that sends the second gateway service overload notification and/or service recovery notification according to the current network topology status and/or node status.
  • the central gateway determines that there are some gateways in the current network according to the current network topology status and/or node status, and its current collaborative gateway is not optimal, it will re-allocate collaborative gateways to these gateways, that is, these gateways.
  • the collaborative gateway after reallocation is better than the collaborative gateway before reallocation.
  • the central gateway after adjusting the coordination relationship of the gateways under its jurisdiction, the central gateway sends a coordination relationship update message to the application server.
  • the application server After receiving the coordination relationship update message sent by the central gateway, the application server updates the gateway coordination relationship configuration information of the corresponding network.
  • the above technical solution realizes the congestion control of the collaborative gateway, where the gateway may be an IoT edge gateway to realize the congestion control processing capability of the IoT edge gateway, thereby meeting the further requirements of the 5G IoT application for the IoT edge gateway.
  • FIG. 5 is a schematic flowchart of a congestion control method provided by this application. This method can be applied to the situation of network congestion in large-scale machine type communication. The method can be executed by the congestion control device applied to the application server provided by the present application, and the congestion control device can be implemented by software and/or hardware and integrated in the gateway.
  • a congestion control method provided by this application applied to an application server, includes:
  • the service coordination request is used to request the application server to forward the service message of the second gateway.
  • the application server performs service forwarding settings for the second gateway, which may specifically be:
  • the application server sets a forwarding flag for the second gateway, when it needs to send a service message to the second gateway, it determines the second gateway according to the gateway coordination relationship configuration information of the network where the second gateway is located.
  • the current collaborative gateway of the gateway forwards the service message of the second gateway to the current collaborative gateway.
  • the application server receives the coordination relationship update message sent by the central gateway, and updates the gateway coordination relationship configuration information according to the coordination relationship update message.
  • the service forwarding cancellation setting is performed for the second gateway.
  • the service coordination cancellation request is used to request the application server to cancel forwarding the service message of the second gateway.
  • the application server performs the service forwarding cancellation setting for the second gateway, which may specifically be: retrieving whether the forwarding flag is set for the second gateway, and if so, revoking the forwarding flag for the second gateway.
  • the above technical solution realizes the congestion control of the collaborative gateway, where the gateway may be an IoT edge gateway to realize the congestion control processing capability of the IoT edge gateway, thereby meeting the further requirements of the 5G IoT application for the IoT edge gateway.
  • FIG. 6 is a schematic structural diagram of a congestion control device provided by this application. As shown in FIG. 6, a congestion control device provided by an embodiment of this application is applied to a first gateway. , The device includes: a monitoring module 610 and a reporting and requesting module 620, where:
  • the monitoring module 610 is configured to monitor node status information of a second gateway; wherein, the second gateway is a collaborative gateway of the first gateway;
  • the reporting and requesting module 620 is configured to notify the central gateway of the service overload of the second gateway when the node status information indicates that the service of the second gateway is overloaded, and send the service coordination of the second gateway to the application server Request; and/or, when the node status information indicates that the service of the second gateway is restored, notify the central gateway of the service restoration of the second gateway, and send the information of the second gateway to the application server Business collaboration cancellation request.
  • the congestion control device applied to the first gateway provided in this embodiment is used to implement the congestion control method applied to the first gateway as described in the embodiment of this application, and the congestion control applied to the first gateway provided in this embodiment
  • the implementation principle and technical effect of the control device are similar to the congestion control method applied to the first gateway described in the embodiment of the present application, and will not be repeated here.
  • the service coordination request is used to request the application server to forward the service message of the second gateway.
  • the service coordination cancellation request is used to request the application server to cancel forwarding the service message of the second gateway.
  • the node status information characterizing the service overload of the second gateway includes:
  • the node state information indicates that the service load of the second gateway reaches a first preset threshold.
  • the node state information characterizing the recovery of the second gateway service includes:
  • the node state information indicates that the service carrying capacity of the second gateway is lower than the first preset threshold or the second preset threshold.
  • FIG. 7 is a schematic structural diagram of a congestion control device provided by this application. As shown in FIG. 7, a congestion control device provided by an embodiment of this application is applied to a central gateway. The device includes: a coordination relationship adjustment module 710, wherein:
  • the coordination relationship adjustment module 710 is configured to, after receiving the service overload notification of the second gateway sent by the first gateway, and/or, after receiving the service recovery notification of the second gateway sent by the first gateway, according to the current network
  • the network status adjusts the coordination relationship of the governed gateways; wherein, the second gateway is a coordination gateway of the first gateway.
  • the congestion control device applied to the central gateway provided in this embodiment is used to implement the congestion control method applied to the central gateway as described in the embodiment of this application, and the congestion control device applied to the central gateway provided in this embodiment implements The principle and technical effect are similar to the congestion control method applied to the central gateway described in the embodiment of the present application, and will not be repeated here.
  • the above-mentioned apparatus further includes: an update message sending module configured to send a coordination relationship update message to the application server after adjusting the coordination relationship of the gateways under its jurisdiction.
  • FIG. 8 is a schematic structural diagram of a congestion control device provided by this application. As shown in FIG. 8, a congestion control device provided by an embodiment of this application is applied to an application server. The device includes: a congestion control module 810, wherein:
  • the congestion control module 810 is configured to perform service forwarding settings for the second gateway if it receives a service coordination request from the second gateway sent by the first gateway; wherein, the second gateway is the coordination of the first gateway Gateway.
  • the congestion control device applied to the application server provided in this embodiment is used to implement the congestion control method applied to the application server as described in the embodiment of this application, and the congestion control device applied to the application server provided in this embodiment implements The principle and technical effect are similar to the congestion control method applied to the application server described in the embodiment of the present application, and will not be repeated here.
  • the service coordination request is used to request the application server to forward the service message of the second gateway.
  • the above-mentioned apparatus further includes: a congestion control cancellation module configured to perform service forwarding cancellation settings for the second gateway if a service coordination cancellation request of the second gateway sent by the first gateway is received.
  • the service coordination cancellation request is used to request the application server to cancel forwarding the service message of the second gateway.
  • the congestion control module 810 is specifically configured to retrieve whether there is a suspended service message of the second gateway: if it exists, forward the suspended service message of the second gateway to the first Gateway; if it does not exist, set a forwarding flag for the second gateway, where the forwarding flag is used to indicate that the service message of the second gateway is forwarded.
  • the congestion control module 810 is further specifically configured to, after setting a forwarding flag for the second gateway, when it needs to send a service message to the second gateway, then according to the gateway of the network where the second gateway is located
  • the coordination relationship configuration information determines the current coordination gateway of the second gateway, and forwards the service message of the second gateway to the current coordination gateway.
  • the above apparatus further includes: a coordination relationship configuration update module configured to receive a coordination relationship update message sent by a central gateway; and update the gateway coordination relationship configuration information according to the coordination relationship update message.
  • a coordination relationship configuration update module configured to receive a coordination relationship update message sent by a central gateway; and update the gateway coordination relationship configuration information according to the coordination relationship update message.
  • the congestion control cancellation module is specifically configured to retrieve whether a forwarding flag is set for the second gateway, and if so, to cancel the forwarding flag for the second gateway.
  • FIG. 9 is a schematic structural diagram of a gateway provided by this application.
  • the gateway provided by this application includes: one or more processors 910 and a memory 920; There may be one or more processors 910 of the gateway.
  • one processor 910 is taken as an example; the memory 920 is used to store one or more programs; the one or more programs are used by the one or more processors. 910 executes, so that the one or more processors 910 implement the congestion control method applied to the first gateway or the congestion control method applied to the central gateway as described in the embodiment of the present invention.
  • the processor 910 and the memory 920 in the gateway may be connected through a bus or other methods.
  • the connection through a bus is taken as an example.
  • the memory 920 can be configured to store software programs, computer-executable programs, and modules, such as the program instructions/modules (for example, The monitoring module 610 and the reporting and requesting module 620 applied to the congestion control device of the first gateway, and the program instructions/modules corresponding to the congestion control method applied to the central gateway as described in the embodiment of the present application (for example, applied to the central The coordination relationship adjustment module in the congestion control device of the gateway 710).
  • the memory 920 may include a program storage area and a data storage area, where the program storage area may store an operating system and an application program required by at least one function; the data storage area may store data created according to the use of the device, and the like.
  • the memory 920 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices.
  • the memory 920 may further include a memory remotely provided with respect to the processor 910, and these remote memories may be connected to a communication node through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.
  • FIG. 10 is a schematic structural diagram of an application server provided by this application.
  • the application server provided by this application includes: one or more processors 1010 and a memory. 1020; the processor 1010 of the application server may be one or more.
  • one processor 1010 is taken as an example; the memory 1020 is used to store one or more programs; the one or more programs are used by the one or Multiple processors 1010 execute, so that the one or more processors 1010 implement the congestion control method applied to the application server as described in the embodiment of the present invention.
  • the processor 1010 and the memory 1020 in the application server may be connected through a bus or other methods.
  • the connection through a bus is taken as an example.
  • the memory 1020 can be configured to store software programs, computer-executable programs, and modules, such as program instructions/modules (for example, application The congestion control module 810 in the congestion control device of the application server).
  • the memory 1020 may include a program storage area and a data storage area, where the program storage area may store an operating system and an application program required by at least one function; the data storage area may store data created according to the use of the device, and the like.
  • the memory 1020 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices.
  • the memory 1020 may further include a memory remotely provided with respect to the processor 1010, and these remote memories may be connected to a communication node through a network.
  • networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.
  • An embodiment of the present application further provides a storage medium that stores a computer program that, when executed by a processor, implements the congestion control method applied to the first gateway in any of the embodiments of the present application , Or applied to the congestion control method in the central gateway, or applied to the congestion control method in the application server.
  • a congestion control method applied to the first gateway includes:
  • the second gateway is a collaborative gateway of the first gateway
  • a congestion control method applied to a central gateway including:
  • the second gateway After receiving the service overload notification of the second gateway sent by the first gateway, and/or after receiving the service recovery notification of the second gateway sent by the first gateway, adjust the network status of the governed gateway according to the current network status.
  • Collaboration relationship wherein, the second gateway is a collaborative gateway of the first gateway.
  • a congestion control method applied to an application server including:
  • the service coordination request of the second gateway sent by the first gateway If the service coordination request of the second gateway sent by the first gateway is received, perform service forwarding settings for the second gateway; wherein, the second gateway is a collaborative gateway of the first gateway.
  • the embodiment of the present application also provides a congestion control system, including: an application server, a central gateway, and at least one first gateway, where:
  • the central gateway is connected to the application server and each first gateway, and is configured to adjust the coordination relationship of the gateways under its jurisdiction according to the network status of the current network, and send a coordination relationship update message of the current network to the application server;
  • the first gateway is connected to the application server and the second gateway, and is used to monitor the node status information of the second gateway, and notify the central gateway of the service of the second gateway according to the node status information Overload or recovery, sending a service coordination request or service coordination cancellation request of the second gateway to the application server; wherein, the second gateway is a collaborative gateway of the first gateway;
  • the application server is configured to perform service forwarding settings for the second gateway when receiving the service coordination request of the second gateway sent by the first gateway, or, after receiving the first gateway sent by the first gateway, When the service coordination cancellation request of the two gateways is performed, the service forwarding cancellation setting is performed for the second gateway.
  • the first gateway monitors the node status information of the second gateway; wherein, the second gateway is a collaborative gateway of the first gateway; when the node status information indicates that the second gateway is overloaded, it will report to the center
  • the gateway notifies the second gateway of the service overload, and sends the service coordination request of the second gateway to the application server; and/or, when the node status information indicates that the service of the second gateway is restored, to the center
  • the gateway notifies the second gateway of the service recovery, and sends a service coordination cancellation request of the second gateway to the application server.
  • the service collaboration request is used to request the application server to forward the service message of the second gateway;
  • the service collaboration cancellation request is used to request the application server to cancel the forwarding of the service message of the second gateway.
  • the node status information characterizing the service overload of the second gateway includes:
  • the node state information indicates that the service load of the second gateway reaches a first preset threshold.
  • the node state information characterizing the recovery of the second gateway service includes:
  • the node state information indicates that the service carrying capacity of the second gateway is lower than the first preset threshold or the second preset threshold.
  • the central gateway receives the service overload notification of the second gateway sent by the first gateway, and/or after receiving the service recovery notification of the second gateway sent by the first gateway, according to the current network status, Adjust the coordination relationship of the governed gateways; wherein, the second gateway is a coordination gateway of the first gateway.
  • the central gateway After adjusting the coordination relationship of the gateways under its jurisdiction, the central gateway sends a coordination relationship update message to the application server.
  • the application server receives the service coordination request of the second gateway sent by the first gateway, it performs service forwarding settings for the second gateway; wherein, the second gateway is a collaborative gateway of the first gateway.
  • the service coordination request is used to request the application server to forward the service message of the second gateway.
  • the application server receives the service coordination cancellation request of the second gateway sent by the first gateway, it performs service forwarding cancellation settings for the second gateway.
  • the service coordination cancellation request is used to request the application server to cancel forwarding the service message of the second gateway.
  • the application server when it performs service forwarding settings for the second gateway, it retrieves whether there is a suspended service message of the second gateway: if it exists, the suspended service message of the second gateway Forward to the first gateway; if it does not exist, set a forwarding flag for the second gateway, where the forwarding flag is used to indicate to forward the service message of the second gateway.
  • the application server determines the gateway coordination relationship configuration information of the network where the second gateway is located.
  • the current collaborative gateway of the second gateway forwards the service message of the second gateway to the current collaborative gateway.
  • the application server receives the coordination relationship update message sent by the central gateway; and updates the gateway coordination relationship configuration information according to the coordination relationship update message.
  • the application server when the application server performs the service forwarding cancellation setting for the second gateway, it searches whether the forwarding flag is set for the second gateway, and if so, the second gateway cancels the forwarding flag.
  • the above technical solution realizes the congestion control of the collaborative gateway, where the gateway may be an IoT edge gateway to realize the congestion control processing capability of the IoT edge gateway, thereby meeting the further requirements of the 5G IoT application for the IoT edge gateway.
  • the corresponding congestion control system is shown in Figure 11, and the specific implementation steps are as follows:
  • Step 101 The IoT gateway (gateway A) receives the node status information of its cooperative IoT gateway (gateway B).
  • Step 102 The IoT gateway (gateway A) judges whether the service carrying capacity of its cooperative gateway (gateway B) reaches a preset threshold (threshold a) according to the received node status information, and if so, sends an announcement The message is sent to the central gateway of the IoT network, notifying the service overload of the collaborative IoT gateway (gateway B).
  • a preset threshold threshold a
  • Step 103 After receiving the notification message, the central IoT gateway reassigns a collaborative gateway (gateway C) to the IoT gateway (gateway A) according to the topology state and/or node state of the current IoT network. If there are currently some IoT gateways in the IoT network (the current collaborative gateways of these IoTs are not optimal), then the collaborative gateways are re-allocated to these IoT gateways.
  • Step 104 The central IoT gateway sends a coordination relationship update message to the IoT application server, and the IoT application server updates the IoT gateway coordination relationship configuration information of the IoT network.
  • Step 105 The IoT gateway (gateway A) sends a service coordination request message to the IoT application server, requesting to forward the service message of the cooperative IoT gateway (gateway B).
  • Step 106 After the IoT application server receives the service coordination request message, it locally searches whether there is a suspended service of the cooperative IoT gateway (gateway B) according to the identifier of the cooperative IoT gateway (gateway B) Message: if it exists, go to step 106a; if not, go to step 106b.
  • Step 106a The IoT application server forwards the suspended service message of its collaborative IoT gateway (gateway B) to the IoT gateway (gateway A).
  • Step 106b The IoT application server sets a forwarding flag for the collaborative IoT gateway (gateway B) locally, and when it needs to send a service message to the collaborative IoT gateway (gateway B), according to the collaborative IoT gateway
  • the identifier of (gateway B) retrieves the current collaborative IoT gateway (perhaps gateway A or D) of its collaborative IoT gateway (gateway B) in the IoT gateway collaboration relationship configuration information of the IoT network, and sends it to the current collaborative IoT gateway
  • the IoT gateway (gateway A or D) forwards the service message of its cooperative gateway (gateway B).
  • Step 107 The current collaborative IoT gateway (gateway A or D) receives node status information of its collaborative IoT gateway (gateway B).
  • Step 108 The current collaborative IoT gateway (gateway A or D) judges whether the service carrying capacity of the collaborative gateway (gateway B) is lower than a preset threshold (threshold a or b) according to the received node status information If yes, send a notification message to the central gateway of the IoT network to notify the service recovery of the collaborative IoT gateway (gateway B).
  • a preset threshold threshold a or b
  • Step 109 After the central IoT gateway receives the notification message, according to the topology state and/or node state of the current IoT network, if it is determined that some IoT gateways currently exist in the IoT network (the current collaborative gateways of the IoT are not Optimal), then re-allocate collaborative gateways to these IoT gateways.
  • Step 110 The central IoT gateway sends a coordination relationship update message to the IoT application server to update the IoT gateway coordination relationship configuration information of the IoT network.
  • Step 111 The current collaborative IoT gateway (gateway A or D) sends a service collaboration cancellation request message to the IoT application server, requesting cancellation and forwarding of the service message of the collaborative IoT gateway (gateway B).
  • Step 112 After the IoT application server receives the service coordination cancellation request message, it searches locally according to the identifier of the cooperative IoT gateway (gateway B) whether there is a forwarding set for the cooperative IoT gateway (gateway B) If the flag exists, the set forwarding flag of the collaborative IoT gateway (gateway B) is revoked.
  • user terminal encompasses any suitable type of wireless user equipment, such as a mobile phone, a portable data processing device, a portable web browser, or a vehicle-mounted mobile station.
  • the various embodiments of the present application can be implemented in hardware or dedicated circuits, software, logic or any combination thereof.
  • some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device, although the present application is not limited thereto.
  • the embodiments of the present application may be implemented by executing computer program instructions by a data processor of a mobile device, for example, in a processor entity, or by hardware, or by a combination of software and hardware.
  • Computer program instructions can be assembly instructions, Industry Subversive Alliance (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, status setting data, or written in any combination of one or more programming languages Source code or object code.
  • ISA Industry Subversive Alliance
  • the block diagram of any logic flow in the drawings of the present application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions.
  • the computer program can be stored on the memory.
  • the memory can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as but not limited to read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), optical Memory devices and systems (Digital Video Disk (DVD) or Portable Compact Disc (CD)), etc.
  • Computer-readable media may include non-transitory storage media.
  • the data processor can be any type suitable for the local technical environment, such as but not limited to general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSP), application specific integrated circuits (ASICs), programmable Logic devices (Field Programmable Gate Array, FPGA) and processors based on multi-core processor architecture.
  • DSP digital signal processors
  • ASICs application specific integrated circuits
  • FPGA programmable Logic devices

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Environmental & Geological Engineering (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请提供一种拥塞控制方法、装置、设备、介质及系统。所述拥塞控制方法，应用于第一网关，包括：监测第二网关的节点状态信息；其中，所述第二网关为所述第一网关的协同网关；在所述节点状态信息表征所述第二网关业务过载时，向中心网关通知所述第二网关的业务过载，并向应用服务器发送所述第二网关的业务协同请求；和/或，在所述节点状态信息表征所述第二网关业务恢复时，向所述中心网关通知所述第二网关的业务恢复，并向所述应用服务器发送所述第二网关的业务协同撤销请求。

Description

拥塞控制方法、装置、设备、介质及系统
本申请要求在2020年02月19日提交中国专利局、申请号为202010102683.7的中国专利申请的优先权，该申请的全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，例如涉及一种拥塞控制方法、装置、设备、介质及系统。
背景技术
大规模机器类型通信(mMTC，Massive Machine Type Communication)，作为第五代移动通信技术(the 5th Generation Mobile Communication Technology，5G)定义的三大应用场景之一，其设备连接密度相比第四代移动通信技术(the4th Generation Mobile Communication Technology，4G)提升10-100倍，支持每平方公里100万台设备的连接，支持的设备连接数量至少为1000亿台，如此海量的接入，网络拥塞将成为必然，如何实现拥塞控制成为亟待解决的问题。
发明内容
本申请提供一种拥塞控制方法、装置、设备、介质及系统，以实现拥塞控制，满足5G物联网的应用需求。
本申请实施例提供一种拥塞控制方法，应用于第一网关，包括：
监测第二网关的节点状态信息；其中，所述第二网关为所述第一网关的协同网关；
在所述节点状态信息表征所述第二网关业务过载时，向中心网关通知所述第二网关的业务过载，并向应用服务器发送所述第二网关的业务协同请求；
和/或，在所述节点状态信息表征所述第二网关业务恢复时，向所述中心网关通知所述第二网关的业务恢复，并向所述应用服务器发送所述第二网关的业务协同撤销请求。
本申请实施例提供一种拥塞控制方法，应用于中心网关，包括：
在接收到第一网关发送的第二网关的业务过载通知后，和/或，在接收到第一网关发送的第二网关的业务恢复通知后，根据当前网络的网络状态，调整所辖网关的协同关系；其中，所述第二网关为所述第一网关的协同网关。
本申请实施例提供一种拥塞控制方法，应用于应用服务器，包括：
如果接收到第一网关发送的第二网关的业务协同请求，则为所述第二网关进行业务转发设置；其中，所述第二网关为所述第一网关的协同网关。
本申请实施例提供一种拥塞控制系统，包括：应用服务器，中心网关和至少一个第一网关，其中，
所述中心网关，与所述应用服务器以及每个第一网关相连，用于根据当前网络的网络状态，调整所辖网关的协同关系，并向所述应用服务器发送当前网络的协同关系更新消息；
所述第一网关，与所述应用服务器以及第二网关相连，用于监测所述第二网关的节点状态信息，并根据所述节点状态信息向所述中心网关通知所述第二网关的业务过载或恢复，向所述应用服务器发送所述第二网关的业务协同请求或业务协同撤销请求；其中，所述第二网关为所述第一网关的协同网关；
所述应用服务器，用于在接收到第一网关发送的所述第二网关的业务协同请求时，为所述第二网关进行业务转发设置，或者，在接收到第一网关发送的所述第二网关的业务协同撤销请求时，为所述第二网关进行业务转发撤销设置。
本申请实施例提供一种拥塞控制装置，应用于第一网关，包括：
监测模块，设置为监测第二网关的节点状态信息；其中，所述第二网关为所述第一网关的协同网关；
上报及请求模块，设置为在所述节点状态信息表征所述第二网关业务过载时，向中心网关通知所述第二网关的业务过载，并向应用服务器发送所述第二网关的业务协同请求；
和/或，在所述节点状态信息表征所述第二网关业务恢复时，向所述中心网关通知所述第二网关的业务恢复，并向所述应用服务器发送所述第二网关的业务协同撤销请求。
本申请实施例提供一种拥塞控制装置，应用于中心网关，包括：
协同关系调整模块，设置为在接收到第一网关发送的第二网关的业务过载通知后，和/或，在接收到第一网关发送的第二网关的业务恢复通知后，根据当前网络的网络状态，调整所辖网关的协同关系；其中，所述第二网关为所述第一网关的协同网关。
本申请实施例提供一种拥塞控制装置，应用于应用服务器，包括：
拥塞控制模块，设置为如果接收到第一网关发送的第二网关的业务协同请求，则为所述第二网关进行业务转发设置；其中，所述第二网关为所述第一网 关的协同网关。
本申请实施例提供一种网关，包括：一个或多个处理器；存储装置，用于存储一个或多个程序；当所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现如本申请任意实施例所述的应用于第一网关的拥塞控制方法，或者实现如本申请任意实施例所述的应用于中心网关的拥塞控制方法。
本申请实施例提供一种应用服务器，包括：一个或多个处理器；存储装置，用于存储一个或多个程序；当所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现如本申请任意实施例所述的应用于应用服务器的拥塞控制方法。
本申请实施例提供一种存储介质，所述存储介质存储有计算机程序，所述计算机程序被处理器执行时实现如本申请任意实施例所述的拥塞控制方法。
附图说明
图1为本申请提供的一种拥塞控制系统的结构示意图；
图2为本申请提供的一种IoT边缘网关的示意图；
图3为本申请提供的一种拥塞控制方法的流程示意图；
图4为本申请提供的一种拥塞控制方法的流程示意图；
图5为本申请提供的一种拥塞控制方法的流程示意图；
图6为本申请提供的一种拥塞控制装置的结构示意图；
图7为本申请提供的一种拥塞控制装置的结构示意图；
图8为本申请提供的一种拥塞控制装置的结构示意图；
图9为本申请提供的一种网关的结构示意图；
图10为本申请提供的一种应用服务器的结构示意图；
图11为本申请提供的一种拥塞控制系统的结构示意图。
具体实施方式
下文中将结合附图对本申请的实施例进行详细说明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。
为了便于理解本申请提供的一种拥塞控制方法，首先对本申请提供的一种拥塞控制系统进行简单解释说明。如图1所示，本申请提供的拥塞控制系统，包括：应用服务器10，中心网关20和至少一个第一网关30(即图1中网关1～网关n)。
其中，中心网关20，与应用服务器10以及每个第一网关30相连，用于根据当前网络的网络状态，调整所辖网关的协同关系，并向应用服务器10发送当前网络的协同关系更新消息。
第一网关30，与应用服务器10以及第二网关相连，用于监测第二网关的节点状态信息，并根据所述节点状态信息向中心网关20通知所述第二网关的业务过载或恢复，向应用服务器10发送所述第二网关的业务协同请求或业务协同撤销请求。其中，所述第二网关为所述第一网关30的协同网关，以第一网关30为图1中网关1为例，其协同网关为网关2和网关3，此时网关2可称为上述的第二网关，网关3也可称为上述的第二网关。
应用服务器10，用于在接收到第一网关30发送的所述第二网关的业务协同请求时，为所述第二网关进行业务转发设置，或者，在接收到第一网关30发送的所述第二网关的业务协同撤销请求时，为所述第二网关进行业务转发撤销设置。
具体的，网络中的每个网关都需要向应用服务器上传数据信息。其中，第一网关是网络中的普通网关，每个第一网关具有至多两个协同网关，协同网关间能够相互监测对方的存活状态，备份对方的数据信息；而中心网关是网络中选定的一个特殊的第一网关，数量为一个，其不仅具有普通网关的所有功能，并拥有一项指定功能，即根据网络状态为网络中的所有网关分配协同网关，具体可以根据网络拓扑、节点状态等信息为网络中的所有网关分配协同网关。应用服务器根据第一网关发送的第二网关的业务协同请求，为所述第二网关进行业务转发设置，或者，在接收到第一网关发送的所述第二网关的业务协同撤销请求时，为所述第二网关进行业务转发撤销设置。
在一示例中，本申请涉及的网关可以是IoT(Internet of Things，物联网)网关，也可以是其他类型的网关，可以是单独的网关设备，也可以部署在其他设备中。示例性的，如图2所示，还可以将IoT网关部署在与基站共享统一站址的MEC(Mobile Edge Computing，移动边缘计算)服务器内，这样设置的意义在于可有效降低业务交付的往返时延，并且利用MEC服务器相对强大的处理能力，可额外支持大数据分析等计算密集型功能。
其中，MEC的基本思想是把云计算平台从网络内部迁移到网络边缘，减少移动业务的端到端交付时延，有效抑制网络拥塞，发掘无线网络的内在能力， 提升用户体验并促进业务创新。所谓“边缘”，既包括移动终端及移动通信基站，也包括无线网络内的其他特定设备(例如基站汇聚节点)。
IoT网关是连接传感网络与传统通信网络的纽带，在无线传感网络中，它是不可或缺的核心设备。由于网络末端的IoT设备在计算及存储方面往往资源有限，无法支持传统的传输控制协议/网际协议(Transmission Control Protocol/Internet Protocol，TCP/IP)协议栈，只能运行简单的通信协议，因此IoT网关需要执行相关的协议转换功能，以支持来自互联网的访问控制请求。
随着IoT应用的不断普及，一些对时延敏感的业务开始出现(例如智能工业控制)，MEC系统为支持此类IoT业务提供了条件。在一示例中，可以通过在MEC系统内以软件化的方式部署IoT网关，在保证低时延的条件下，可利用边缘服务器的处理能力对多种不同的IoT协议提供支持，并能提供更多的功能来增强IoT网络的可管理性，从而简化部署，提升业务灵活性。
对应的，在IoT网络中需要确定一个中心IoT网关，每个IoT网关需要向IoT应用服务器上传数据信息。其中，每个IoT网关有至多两个协同网关，协同IoT网关间能够相互监测对方的存活状态，备份对方的数据信息；而中心IoT网关具有普通IoT网关的所有功能，并拥有一项指定功能，即根据网络拓扑、节点状态等信息，为IoT网络中的所有IoT网关分配协同网关。
在一个示例性实施方式中，图3为本申请提供的一种拥塞控制方法的流程示意图。该方法可以适用于大规模机器类型通信中网络拥塞的情况。该方法可以由本申请提供的应用于第一网关的拥塞控制装置执行，该拥塞控制装置可以由软件和/或硬件实现，并集成在网关中。
如图3所示，本申请提供的一种拥塞控制方法，应用于第一网关中，包括：
S310、监测第二网关的节点状态信息；其中，所述第二网关为所述第一网关的协同网关。
网络中除中心网关之外的任何一个网关都可称为第一网关，第一网关的协同网关称为第二网关。每个第一网关监测其协同网关(也即第二网关)的节点状态信息，例如是监测其协同网关的应用信息或者设备信息等，具体可以是节点带宽信息、是否超负荷、设备运行速度等等。
S320、在所述节点状态信息表征所述第二网关业务过载时，向中心网关通知所述第二网关的业务过载，并向应用服务器发送所述第二网关的业务协同请求；和/或，在所述节点状态信息表征所述第二网关业务恢复时，向所述中心网关通知所述第二网关的业务恢复，并向所述应用服务器发送所述第二网关的业 务协同撤销请求。
第一网关可以根据第二网关的节点状态信息来判断第二网关的业务拥塞状态，是业务过载还是业务恢复。
在一示例中，第一网关根据第二网关的节点状态信息判断出第二网关的业务承载量到达第一预设门限时，可以确定第二网关的业务过载。
在一示例中，第一网关根据第二网关的节点状态信息判断出第二网关的业务承载量低于所述第一预设门限或第二预设门限时，可以确定第二网关的业务恢复。
其中，第一网关判断第二网关的业务过载或恢复的门限值可以是相同的，例如均是根据第一预设门限来判断，第一网关判断第二网关的业务过载或恢复的门限值也可以是不同的，例如根据第一预设门限来判断是否业务过载，根据第二预设门限来判断是否业务恢复，第二预设门限低于第一预设门限。
第一网关(例如是网关A)根据其接收到的第二网关(例如是网关B)的节点状态信息判断其协同网关(网关B)的业务承载量是否达到第一预设门限，如果是，则发送通告消息给网络的中心网关，向中心网关通告所述第二网关(网关B)的业务过载，并向应用服务器发送所述第二网关(网关B)的业务协同请求。在一示例中，所述业务协同请求用于向所述应用服务器请求转发所述第二网关的业务消息，也即网关A向应用服务器请求转发网关B的业务消息。
中心网关接收到第一网关发送的第二网关的业务过载通知后，根据当前网络的网络状态，具体可以是根据当前网络的拓扑状态和/或节点状态，调整所辖网关的协同关系。
可选的，中心网关根据所述当前网络的拓扑状态和/或节点状态，为所述第一网关(即网关A)重新分配一个协同网关(例如是网关C)。可选的，中心网关如果根据当前网络的拓扑状态和/或节点状态，确定当前网络中存在一些网关，其当前的协同网关不是最优的，则重新为这些网关分配协同网关，也即这些网关的重新分配后的协同网关要优于重新分配前的协同网关。
进一步的，中心网关在调整所辖网关的协同关系之后，向应用服务器发送协同关系更新消息。应用服务器接收到中心网关发送的协同关系更新消息之后，更新对应网络的网关协同关系配置信息。
应用服务器接收到第一网关(网关A)发送的第二网关(网关B)的业务协同请求之后，为第二网关(网关B)进行业务转发设置。在一示例中，应用服务器根据第二网关(网关B)的标识检索本地是否存在挂起的第二网关(网关B)的业务消息，如果存在，则将挂起的所述第二网关的业务消息转发给所述第一 网关，如果不存在，则为第二网关(网关B)设置转发标志，所述转发标志用于指示将所述第二网关的业务消息进行转发。在一示例中，在为第二网关(网关B)设置转发标志之后，当需要向第二网关(网关B)发送业务消息时，则根据第二网关(网关B)所在网络的网关协同关系配置信息确定第二网关(网关B)的当前协同网关，向所述当前协同网关转发第二网关(网关B)的业务消息，以此解决第二网关(网关B)的拥塞问题。
其中，第二网关(网关B)的协同网关会根据中心网关对其所辖网关的协同关系的调整而变化，故此时第二网关(网关B)的当前协同网关可能是网关A或网关D(网关D为中心网关为网关B重新分配的协同网关)，进而，应用服务器当需要向第二网关(网关B)发送业务消息时，向第二网关(网关B)的当前协同网关，也即向网关A或网关D转发第二网关(网关B)的业务消息。
进一步的，第二网关(网关B)的当前协同网关(网关A或网关D)，根据其接收到的第二网关(网关B)的节点状态信息判断其协同网关(网关B)的业务是否恢复，具体可以根据第二网关(网关B)的节点状态信息判断第二网关(网关B)的业务承载量是否低于第一预设门限或第二预设门限，如果是，则发送通告消息给网络的中心网关，向中心网关通告所述第二网关(网关B)的业务恢复，并向应用服务器发送所述第二网关(网关B)的业务协同撤销请求。在一示例中，所述业务协同撤销请求用于向所述应用服务器请求撤销转发所述第二网关的业务消息，也即网关A或网关D向应用服务器请求撤销转发网关B的业务消息。
在一示例中，网关A向中心网关发送网关B的业务过载通知，向应用服务器发送网关B的业务协同请求，假设，在应用服务器为网关B进行业务转发设置期间，中心网关将网关B的协同网关由网关A调整为网关D，在中心网关向网关D通告时，会同时告知网关D此时网关B为业务过载状态，进而网关D与网关B建立协同关系后，会接收应用服务器转发的网关B的业务消息，并通过对网关B的节点状态信息的监测，判断网关B的业务是否恢复，并在确定网关B的业务恢复时，向中心网关通告所述第二网关(网关B)的业务恢复，并向应用服务器发送所述第二网关(网关B)的业务协同撤销请求。
中心网关接收到第一网关(网关A或网关D)发送的第二网关(网关B)的业务恢复通知后，根据当前网络的网络状态，具体可以是根据当前网络的拓扑状态和/或节点状态，调整所辖网关的协同关系。
可选的，中心网关如果根据当前网络的拓扑状态和/或节点状态，确定当前网络中存在一些网关，其当前的协同网关不是最优的，则重新为这些网关分配协同网关，也即这些网关的重新分配后的协同网关要优于重新分配前的协同网 关。
进一步的，中心网关在调整所辖网关的协同关系之后，向应用服务器发送协同关系更新消息。应用服务器接收到中心网关发送的协同关系更新消息之后，更新对应网络的网关协同关系配置信息。
应用服务器接收到第一网关(网关A或网关D)发送的第二网关(网关B)的业务协同撤销请求之后，为第二网关(网关B)进行业务转发撤销设置，具体的，根据第二网关(网关B)的标识本地检索是否存在为第二网关(网关B)设置的转发标志，若是，则为第二网关(网关B)撤销转发标志。
值得指出的是，本申请所涉及的网关A、网关B、网关C及网关D，均是一个本申请所提到的第一网关，均可以执行本申请提供的应用于第一网关的拥塞控制方法。
上述技术方案，实现了协同网关的拥塞控制，其中，网关可以是IoT边缘网关，以实现IoT边缘网关的拥塞控制处理能力，从而满足了5G物联网应用对IoT边缘网关的进一步需求。
在一个示例性实施方式中，图4为本申请提供的一种拥塞控制方法的流程示意图。该方法可以适用于大规模机器类型通信中网络拥塞的情况。该方法可以由本申请提供的应用于中心网关的拥塞控制装置执行，该拥塞控制装置可以由软件和/或硬件实现，并集成在网关中。
如图4所示，本申请提供的一种拥塞控制方法，应用于中心网关中，包括：
S410、在接收到第一网关发送的第二网关的业务过载通知后，和/或，在接收到第一网关发送的第二网关的业务恢复通知后，根据当前网络的网络状态，调整所辖网关的协同关系；其中，所述第二网关为所述第一网关的协同网关。
中心网关接收到第一网关发送的第二网关的业务过载通知后，和/或，在接收到第一网关发送的第二网关的业务恢复通知后，根据当前网络的网络状态，具体可以是根据当前网络的拓扑状态和/或节点状态，调整所辖网关的协同关系。
可选的，中心网关根据所述当前网络的拓扑状态和/或节点状态，为发送第二网关业务过载通知和/或业务恢复通知的第一网关重新分配一个协同网关。
可选的，中心网关如果根据当前网络的拓扑状态和/或节点状态，确定当前网络中存在一些网关，其当前的协同网关不是最优的，则重新为这些网关分配协同网关，也即这些网关的重新分配后的协同网关要优于重新分配前的协同网关。
在一示例中，中心网关在调整所辖网关的协同关系之后，向应用服务器发送协同关系更新消息。应用服务器接收到中心网关发送的协同关系更新消息之后，更新对应网络的网关协同关系配置信息。
本实施方式未尽详细解释之处请参见前述实施方式，在此不再赘述。
上述技术方案，实现了协同网关的拥塞控制，其中，网关可以是IoT边缘网关，以实现IoT边缘网关的拥塞控制处理能力，从而满足了5G物联网应用对IoT边缘网关的进一步需求。
在一个示例性实施方式中，图5为本申请提供的一种拥塞控制方法的流程示意图。该方法可以适用于大规模机器类型通信中网络拥塞的情况。该方法可以由本申请提供的应用于应用服务器的拥塞控制装置执行，该拥塞控制装置可以由软件和/或硬件实现，并集成在网关中。
如图5所示，本申请提供的一种拥塞控制方法，应用于应用服务器中，包括：
S510、如果接收到第一网关发送的第二网关的业务协同请求，则为所述第二网关进行业务转发设置；其中，所述第二网关为所述第一网关的协同网关。
在一示例中，所述业务协同请求用于向所述应用服务器请求转发所述第二网关的业务消息。
在一示例中，应用服务器为所述第二网关进行业务转发设置，具体可以是：
检索是否存在挂起的所述第二网关的业务消息，如果存在，则将挂起的所述第二网关的业务消息转发给所述第一网关，如果不存在，则为所述第二网关设置转发标志，所述转发标志用于指示将所述第二网关的业务消息进行转发。
进一步的，应用服务器在为所述第二网关设置转发标志之后，当需要向所述第二网关发送业务消息时，则根据所述第二网关所在网络的网关协同关系配置信息确定所述第二网关的当前协同网关，向所述当前协同网关转发所述第二网关的业务消息。
在一示例中，应用服务器接收中心网关发送的协同关系更新消息，根据所述协同关系更新消息，更新所述网关协同关系配置信息。
进一步的，如果接收到第一网关发送的所述第二网关的业务协同撤销请求，则为所述第二网关进行业务转发撤销设置。
在一示例中，所述业务协同撤销请求用于向所述应用服务器请求撤销转发所述第二网关的业务消息。
在一示例中，应用服务器为所述第二网关进行业务转发撤销设置，具体可以是：检索是否为所述第二网关设置转发标志，若是，则为所述第二网关撤销转发标志。
本实施方式未尽详细解释之处请参见前述实施方式，在此不再赘述。
上述技术方案，实现了协同网关的拥塞控制，其中，网关可以是IoT边缘网关，以实现IoT边缘网关的拥塞控制处理能力，从而满足了5G物联网应用对IoT边缘网关的进一步需求。
本实施例还提供了拥塞控制装置，图6为本申请提供的一种拥塞控制装置的结构示意图，如图6所示，本申请实施例提供的一种拥塞控制装置，应用于第一网关中，该装置包括：监测模块610和上报及请求模块620，其中，
监测模块610，设置为监测第二网关的节点状态信息；其中，所述第二网关为所述第一网关的协同网关；
上报及请求模块620，设置为在所述节点状态信息表征所述第二网关业务过载时，向中心网关通知所述第二网关的业务过载，并向应用服务器发送所述第二网关的业务协同请求；和/或，在所述节点状态信息表征所述第二网关业务恢复时，向所述中心网关通知所述第二网关的业务恢复，并向所述应用服务器发送所述第二网关的业务协同撤销请求。
本实施例提供的应用于第一网关中的拥塞控制装置用于实现如本申请实施例所述的应用于第一网关中的拥塞控制方法，本实施例提供的应用于第一网关中的拥塞控制装置实现原理和技术效果与本申请实施例所述的应用于第一网关中的拥塞控制方法类似，此处不再赘述。
在一示例中，所述业务协同请求用于向所述应用服务器请求转发所述第二网关的业务消息。
在一示例中，所述业务协同撤销请求用于向所述应用服务器请求撤销转发所述第二网关的业务消息。
在一示例中，所述节点状态信息表征所述第二网关业务过载，包括：
所述节点状态信息表征所述第二网关的业务承载量到达第一预设门限。
在一示例中，所述节点状态信息表征所述第二网关业务恢复，包括：
所述节点状态信息表征所述第二网关的业务承载量低于所述第一预设门限或第二预设门限。
本实施例还提供了拥塞控制装置，图7为本申请提供的一种拥塞控制装置的结构示意图，如图7所示，本申请实施例提供的一种拥塞控制装置，应用于中心网关中，该装置包括：协同关系调整模块710，其中，
协同关系调整模块710，设置为在接收到第一网关发送的第二网关的业务过载通知后，和/或，在接收到第一网关发送的第二网关的业务恢复通知后，根据当前网络的网络状态，调整所辖网关的协同关系；其中，所述第二网关为所述第一网关的协同网关。
本实施例提供的应用于中心网关中的拥塞控制装置用于实现如本申请实施例所述的应用于中心网关中的拥塞控制方法，本实施例提供的应用于中心网关中的拥塞控制装置实现原理和技术效果与本申请实施例所述的应用于中心网关中的拥塞控制方法类似，此处不再赘述。
在一示例中，上述装置还包括：更新消息发送模块，设置为在调整所辖网关的协同关系之后，向应用服务器发送协同关系更新消息。
本实施例还提供了拥塞控制装置，图8为本申请提供的一种拥塞控制装置的结构示意图，如图8所示，本申请实施例提供的一种拥塞控制装置，应用于应用服务器中，该装置包括：拥塞控制模块810，其中，
拥塞控制模块810，设置为如果接收到第一网关发送的第二网关的业务协同请求，则为所述第二网关进行业务转发设置；其中，所述第二网关为所述第一网关的协同网关。
本实施例提供的应用于应用服务器中的拥塞控制装置用于实现如本申请实施例所述的应用于应用服务器中的拥塞控制方法，本实施例提供的应用于应用服务器中的拥塞控制装置实现原理和技术效果与本申请实施例所述的应用于应用服务器中的拥塞控制方法类似，此处不再赘述。
在一示例中，所述业务协同请求用于向所述应用服务器请求转发所述第二网关的业务消息。
进一步的，上述装置还包括：拥塞控制撤销模块，设置为如果接收到第一网关发送的所述第二网关的业务协同撤销请求，则为所述第二网关进行业务转发撤销设置。
在一示例中，所述业务协同撤销请求用于向所述应用服务器请求撤销转发所述第二网关的业务消息。
在一示例中，拥塞控制模块810，具体设置为检索是否存在挂起的所述第二 网关的业务消息：如果存在，则将挂起的所述第二网关的业务消息转发给所述第一网关；如果不存在，则为所述第二网关设置转发标志，所述转发标志用于指示将所述第二网关的业务消息进行转发。
在一示例中，拥塞控制模块810，还具体设置为在为所述第二网关设置转发标志之后，当需要向所述第二网关发送业务消息时，则根据所述第二网关所在网络的网关协同关系配置信息确定所述第二网关的当前协同网关，向所述当前协同网关转发所述第二网关的业务消息。
在一示例中，上述装置还包括：协同关系配置更新模块，设置为接收中心网关发送的协同关系更新消息；根据所述协同关系更新消息，更新所述网关协同关系配置信息。
在一示例中，拥塞控制撤销模块，具体设置为检索是否为所述第二网关设置转发标志，若是，则为所述第二网关撤销转发标志。
本申请实施例提供了一种网关，图9为本申请提供的一种网关的结构示意图，如图9所示，本申请提供的网关，包括：一个或多个处理器910和存储器920；该网关的处理器910可以是一个或多个，图9中以一个处理器910为例；存储器920用于存储一个或多个程序；所述一个或多个程序被所述一个或多个处理器910执行，使得所述一个或多个处理器910实现如本发明实施例中所述的应用于第一网关的拥塞控制方法，或者应用于中心网关的拥塞控制方法。
网关中的处理器910、存储器920可以通过总线或其他方式连接，图9中以通过总线连接为例。
存储器920作为一种计算机可读存储介质，可设置为存储软件程序、计算机可执行程序以及模块，如本申请实施例所述应用于第一网关的拥塞控制方法对应的程序指令/模块(例如，应用于第一网关的拥塞控制装置中的监测模块610和上报及请求模块620)，又如本申请实施例所述应用于中心网关的拥塞控制方法对应的程序指令/模块(例如，应用于中心网关的拥塞控制装置中的协同关系调整模块710)。存储器920可包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序；存储数据区可存储根据设备的使用所创建的数据等。此外，存储器920可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。在一些实例中，存储器920可进一步包括相对于处理器910远程设置的存储器，这些远程存储器可以通过网络连接至通信节点。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组 合。
本申请实施例提供了一种应用服务器，图10为本申请提供的一种应用服务器的结构示意图，如图10所示，本申请提供的应用服务器，包括：一个或多个处理器1010和存储器1020；该应用服务器的处理器1010可以是一个或多个，图10中以一个处理器1010为例；存储器1020用于存储一个或多个程序；所述一个或多个程序被所述一个或多个处理器1010执行，使得所述一个或多个处理器1010实现如本发明实施例中所述的应用于应用服务器的拥塞控制方法。
应用服务器中的处理器1010、存储器1020可以通过总线或其他方式连接，图10中以通过总线连接为例。
存储器1020作为一种计算机可读存储介质，可设置为存储软件程序、计算机可执行程序以及模块，如本申请实施例所述应用于应用服务器的拥塞控制方法对应的程序指令/模块(例如，应用于应用服务器的拥塞控制装置中的拥塞控制模块810)。存储器1020可包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序；存储数据区可存储根据设备的使用所创建的数据等。此外，存储器1020可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。在一些实例中，存储器1020可进一步包括相对于处理器1010远程设置的存储器，这些远程存储器可以通过网络连接至通信节点。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
本申请实施例还提供一种存储介质，所述存储介质存储有计算机程序，所述计算机程序被处理器执行时实现本申请实施例中任一所述的应用于第一网关中的拥塞控制方法，或者应用于中心网关中的拥塞控制方法，或者应用于应用服务器中的拥塞控制方法。
其中，一种应用于第一网关中的拥塞控制方法，包括：
监测第二网关的节点状态信息；其中，所述第二网关为所述第一网关的协同网关；
在所述节点状态信息表征所述第二网关业务过载时，向中心网关通知所述第二网关的业务过载，并向应用服务器发送所述第二网关的业务协同请求；
和/或，在所述节点状态信息表征所述第二网关业务恢复时，向所述中心网关通知所述第二网关的业务恢复，并向所述应用服务器发送所述第二网关的业 务协同撤销请求。
一种应用于中心网关中的拥塞控制方法，包括：
在接收到第一网关发送的第二网关的业务过载通知后，和/或，在接收到第一网关发送的第二网关的业务恢复通知后，根据当前网络的网络状态，调整所辖网关的协同关系；其中，所述第二网关为所述第一网关的协同网关。
一种应用于应用服务器中的拥塞控制方法，包括：
如果接收到第一网关发送的第二网关的业务协同请求，则为所述第二网关进行业务转发设置；其中，所述第二网关为所述第一网关的协同网关。
本申请实施例还提供一种拥塞控制系统，包括：应用服务器，中心网关和至少一个第一网关，其中，
所述中心网关，与所述应用服务器以及每个第一网关相连，用于根据当前网络的网络状态，调整所辖网关的协同关系，并向所述应用服务器发送当前网络的协同关系更新消息；
所述第一网关，与所述应用服务器以及第二网关相连，用于监测所述第二网关的节点状态信息，并根据所述节点状态信息向所述中心网关通知所述第二网关的业务过载或恢复，向所述应用服务器发送所述第二网关的业务协同请求或业务协同撤销请求；其中，所述第二网关为所述第一网关的协同网关；
所述应用服务器，用于在接收到第一网关发送的所述第二网关的业务协同请求时，为所述第二网关进行业务转发设置，或者，在接收到第一网关发送的所述第二网关的业务协同撤销请求时，为所述第二网关进行业务转发撤销设置。
具体的，第一网关监测第二网关的节点状态信息；其中，所述第二网关为所述第一网关的协同网关；在所述节点状态信息表征所述第二网关业务过载时，向中心网关通知所述第二网关的业务过载，并向应用服务器发送所述第二网关的业务协同请求；和/或，在所述节点状态信息表征所述第二网关业务恢复时，向所述中心网关通知所述第二网关的业务恢复，并向所述应用服务器发送所述第二网关的业务协同撤销请求。
其中，所述业务协同请求用于向所述应用服务器请求转发所述第二网关的业务消息；所述业务协同撤销请求用于向所述应用服务器请求撤销转发所述第二网关的业务消息。
在一示例中，所述节点状态信息表征所述第二网关业务过载，包括：
所述节点状态信息表征所述第二网关的业务承载量到达第一预设门限。
在一示例中，所述节点状态信息表征所述第二网关业务恢复，包括：
所述节点状态信息表征所述第二网关的业务承载量低于所述第一预设门限或第二预设门限。
具体的，中心网关在接收到第一网关发送的第二网关的业务过载通知后，和/或，在接收到第一网关发送的第二网关的业务恢复通知后，根据当前网络的网络状态，调整所辖网关的协同关系；其中，所述第二网关为所述第一网关的协同网关。
进一步的，在调整所辖网关的协同关系之后，中心网关向应用服务器发送协同关系更新消息。
具体的，应用服务器如果接收到第一网关发送的第二网关的业务协同请求，则为所述第二网关进行业务转发设置；其中，所述第二网关为所述第一网关的协同网关。
在一示例中，所述业务协同请求用于向所述应用服务器请求转发所述第二网关的业务消息。
进一步的，应用服务器如果接收到第一网关发送的所述第二网关的业务协同撤销请求，则为所述第二网关进行业务转发撤销设置。
在一示例中，所述业务协同撤销请求用于向所述应用服务器请求撤销转发所述第二网关的业务消息。
在一示例中，应用服务器为所述第二网关进行业务转发设置时，检索是否存在挂起的所述第二网关的业务消息：如果存在，则将挂起的所述第二网关的业务消息转发给所述第一网关；如果不存在，则为所述第二网关设置转发标志，所述转发标志用于指示将所述第二网关的业务消息进行转发。
在一示例中，应用服务器在为所述第二网关设置转发标志之后，当需要向所述第二网关发送业务消息时，则根据所述第二网关所在网络的网关协同关系配置信息确定所述第二网关的当前协同网关，向所述当前协同网关转发所述第二网关的业务消息。
在一示例中，应用服务器接收中心网关发送的协同关系更新消息；根据所述协同关系更新消息，更新所述网关协同关系配置信息。
在一示例中，应用服务器为所述第二网关进行业务转发撤销设置时，检索是否为所述第二网关设置转发标志，若是，则为所述第二网关撤销转发标志。
上述技术方案，实现了协同网关的拥塞控制，其中，网关可以是IoT边缘网关，以实现IoT边缘网关的拥塞控制处理能力，从而满足了5G物联网应用对 IoT边缘网关的进一步需求。
下述以网关为IoT边缘网关为例，给出一种实施方式，相应的拥塞控制系统的示意图如图11所示，具体实现步骤如下：
拥塞控制阶段：
步骤101：IoT网关(网关A)接收其协同IoT网关(网关B)的节点状态信息。
步骤102：所述IoT网关(网关A)根据接收到的所述节点状态信息判断所述其协同网关(网关B)的业务承载量是否达到预设门限(门限a)，如果是，则发送通告消息给所述IoT网络的中心网关，通告所述其协同IoT网关(网关B)业务过载。
步骤103：所述中心IoT网关接收到所述通知消息后，根据所述当前IoT网络的拓扑状态和/或节点状态，为所述IoT网关(网关A)重新分配一个协同网关(网关C)。如果所述IoT网络当前存在一些IoT网关(这些IoT当前的协同网关不是最优的)，则重新为这些IoT网关分配协同网关。
步骤104：所述中心IoT网关发送协同关系更新消息给IoT应用服务器，所述IoT应用服务器更新所述IoT网络的IoT网关协同关系配置信息。
步骤105：所述IoT网关(网关A)发送业务协同请求消息给所述IoT应用服务器，请求转发所述其协同IoT网关(网关B)的业务消息。
步骤106：所述IoT应用服务器接收到所述业务协同请求消息后，根据所述其协同IoT网关(网关B)的标识本地检索是否存在挂起的所述其协同IoT网关(网关B)的业务消息：如果存在，则执行步骤106a；如不存在，则执行步骤106b。
步骤106a：所述IoT应用服务器转发所述挂起的所述其协同IoT网关(网关B)的业务消息给所述IoT网关(网关A)。
步骤106b：所述IoT应用服务器在本地为所述其协同IoT网关(网关B)设置转发标志，当需要发送业务消息给所述其协同IoT网关(网关B)时，根据所述其协同IoT网关(网关B)的标识在所述IoT网络的IoT网关协同关系配置信息中检索所述其协同IoT网关(网关B)的当前协同IoT网关(可能是网关A或D)，并向所述当前协同IoT网关(网关A或D)转发所述其协同网关(网关B)的业务消息。
拥塞控制撤销阶段：
步骤107：所述当前协同IoT网关(网关A或D)接收其协同IoT网关(网 关B)的节点状态信息。
步骤108：所述当前协同IoT网关(网关A或D)根据接收到的所述节点状态信息判断所述其协同网关(网关B)的业务承载量是否低于预设门限(门限a或b)，如果是，则发送通告消息给所述IoT网络的中心网关，通告所述其协同IoT网关(网关B)业务恢复。
步骤109：所述中心IoT网关接收到所述通知消息后，根据所述当前IoT网络的拓扑状态和/或节点状态，如果确定所述IoT网络当前存在一些IoT网关(这些IoT当前的协同网关不是最优的)，则重新为这些IoT网关分配协同网关。
步骤110：所述中心IoT网关发送协同关系更新消息给所述IoT应用服务器，更新所述IoT网络的IoT网关协同关系配置信息。
步骤111：所述当前协同IoT网关(网关A或D)发送业务协同撤销请求消息给所述IoT应用服务器，请求撤销转发所述其协同IoT网关(网关B)的业务消息。
步骤112：所述IoT应用服务器接收到所述业务协同撤销请求消息后，根据所述其协同IoT网关(网关B)的标识本地检索是否存在设置的所述其协同IoT网关(网关B)的转发标志，如果存在，则撤销所述设置的所述其协同IoT网关(网关B)的转发标识。
以上所述，仅为本申请的示例性实施例而已，并非用于限定本申请的保护范围。
本领域内的技术人员应明白，术语用户终端涵盖任何适合类型的无线用户设备，例如移动电话、便携数据处理装置、便携网络浏览器或车载移动台。
一般来说，本申请的多种实施例可以在硬件或专用电路、软件、逻辑或其任何组合中实现。例如，一些方面可以被实现在硬件中，而其它方面可以被实现在可以被控制器、微处理器或其它计算装置执行的固件或软件中，尽管本申请不限于此。
本申请的实施例可以通过移动装置的数据处理器执行计算机程序指令来实现，例如在处理器实体中，或者通过硬件，或者通过软件和硬件的组合。计算机程序指令可以是汇编指令、指令集架构(Industry Subversive Alliance，ISA)指令、机器指令、机器相关指令、微代码、固件指令、状态设置数据、或者以一种或多种编程语言的任意组合编写的源代码或目标代码。
本申请附图中的任何逻辑流程的框图可以表示程序步骤，或者可以表示相 互连接的逻辑电路、模块和功能，或者可以表示程序步骤与逻辑电路、模块和功能的组合。计算机程序可以存储在存储器上。存储器可以具有任何适合于本地技术环境的类型并且可以使用任何适合的数据存储技术实现，例如但不限于只读存储器(Read-Only Memory，ROM)、随机访问存储器(Random Access Memory，RAM)、光存储器装置和系统(数码多功能光碟(Digital Video Disk，DVD)或便携式紧凑磁盘(Compact Disc，CD))等。计算机可读介质可以包括非瞬时性存储介质。数据处理器可以是任何适合于本地技术环境的类型，例如但不限于通用计算机、专用计算机、微处理器、数字信号处理器(DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、可编程逻辑器件(Field Programmable Gate Array，FPGA)以及基于多核处理器架构的处理器。

Claims (22)

  1. 一种拥塞控制方法，应用于第一网关，包括：
    监测第二网关的节点状态信息，其中，所述第二网关为所述第一网关的协同网关；
    执行以下至少之一：
    在所述节点状态信息表征所述第二网关的业务过载的情况下，向中心网关通知所述第二网关的业务过载，并向应用服务器发送所述第二网关的业务协同请求；
    或，在所述节点状态信息表征所述第二网关的业务恢复的情况下，向所述中心网关通知所述第二网关的业务恢复，并向所述应用服务器发送所述第二网关的业务协同撤销请求。
  2. 根据权利要求1所述的方法，其中，所述业务协同请求用于向所述应用服务器请求转发所述第二网关的业务消息。
  3. 根据权利要求1所述的方法，其中，所述业务协同撤销请求用于向所述应用服务器请求撤销转发所述第二网关的业务消息。
  4. 根据权利要求1所述的方法，其中，所述节点状态信息表征所述第二网关的业务过载，包括：
    所述节点状态信息表征所述第二网关的业务承载量到达第一预设门限。
  5. 根据权利要求1所述的方法，其中，所述节点状态信息表征所述第二网关的业务恢复，包括：
    所述节点状态信息表征所述第二网关的业务承载量低于第一预设门限或第二预设门限，所述第二预设门限低于所述第一预设门限。
  6. 一种拥塞控制方法，应用于中心网关，包括：
    在执行以下至少之一后，根据当前网络的网络状态，调整所辖网关的协同关系：在接收到第一网关发送的第二网关的业务过载通知后，或，在接收到第一网关发送的第二网关的业务恢复通知后；其中，所述第二网关为所述第一网关的协同网关。
  7. 根据权利要求6所述的方法，其中，在所述调整所辖网关的协同关系之后，还包括：
    向应用服务器发送协同关系更新消息。
  8. 一种拥塞控制方法，应用于应用服务器，包括：
    在接收到第一网关发送的第二网关的业务协同请求的情况下，为所述第二 网关进行业务转发设置；其中，所述第二网关为所述第一网关的协同网关。
  9. 根据权利要求8所述的方法，其中，所述业务协同请求用于向所述应用服务器请求转发所述第二网关的业务消息。
  10. 根据权利要求8或9所述的方法，还包括：
    在接收到第一网关发送的所述第二网关的业务协同撤销请求的情况下，为所述第二网关进行业务转发撤销设置。
  11. 根据权利要求10所述的方法，其中，所述业务协同撤销请求用于向所述应用服务器请求撤销转发所述第二网关的业务消息。
  12. 根据权利要求8所述的方法，其中，所述为所述第二网关进行业务转发设置，包括：
    检索是否存在挂起的所述第二网关的业务消息：
    在存在挂起的所述第二网关的业务消息的情况下，将挂起的所述第二网关的业务消息转发给所述第一网关；
    在不存在挂起的所述第二网关的业务消息的情况下，为所述第二网关设置转发标志，所述转发标志用于指示将所述第二网关的业务消息进行转发。
  13. 根据权利要求12所述的方法，其中，在所述为所述第二网关设置转发标志之后，还包括：
    在需要向所述第二网关发送业务消息的情况下，根据所述第二网关所在网络的网关协同关系配置信息确定所述第二网关的当前协同网关，向所述当前协同网关转发所述第二网关的业务消息。
  14. 根据权利要求13所述的方法，还包括：
    接收中心网关发送的协同关系更新消息；
    根据所述协同关系更新消息，更新所述网关协同关系配置信息。
  15. 根据权利要求10所述的方法，其中，所述为所述第二网关进行业务转发撤销设置，包括：
    检索是否为所述第二网关设置转发标志，在为所述第二网关设置转发标志的情况下，为所述第二网关撤销转发标志。
  16. 一种拥塞控制系统，包括：应用服务器，中心网关和至少一个第一网关，其中，
    所述中心网关，与所述应用服务器以及每个第一网关相连，设置为根据当前网络的网络状态，调整所辖网关的协同关系，并向所述应用服务器发送所述 当前网络的协同关系更新消息；
    所述第一网关，与所述应用服务器以及第二网关相连，设置为监测所述第二网关的节点状态信息，并根据所述节点状态信息向所述中心网关通知所述第二网关的业务过载或恢复，以及向所述应用服务器发送所述第二网关的业务协同请求或业务协同撤销请求，其中，所述第二网关为所述第一网关的协同网关；
    所述应用服务器，设置为在接收到第一网关发送的所述第二网关的业务协同请求的情况下，为所述第二网关进行业务转发设置，或者，在接收到第一网关发送的所述第二网关的业务协同撤销请求的情况下，为所述第二网关进行业务转发撤销设置。
  17. 一种拥塞控制装置，应用于第一网关，包括：
    监测模块，设置为监测第二网关的节点状态信息，其中，所述第二网关为所述第一网关的协同网关；
    上报及请求模块，设置为执行以下至少之一：在所述节点状态信息表征所述第二网关的业务过载的情况下，向中心网关通知所述第二网关的业务过载，并向应用服务器发送所述第二网关的业务协同请求；
    或，在所述节点状态信息表征所述第二网关的业务恢复的情况下，向所述中心网关通知所述第二网关的业务恢复，并向所述应用服务器发送所述第二网关的业务协同撤销请求。
  18. 一种拥塞控制装置，应用于中心网关，包括：
    协同关系调整模块，设置为在执行以下至少之一后，根据当前网络的网络状态，调整所辖网关的协同关系：在接收到第一网关发送的第二网关的业务过载通知后，或，在接收到第一网关发送的第二网关的业务恢复通知后；其中，所述第二网关为所述第一网关的协同网关。
  19. 一种拥塞控制装置，应用于应用服务器，包括：
    拥塞控制模块，设置为在接收到第一网关发送的第二网关的业务协同请求的情况下，为所述第二网关进行业务转发设置；其中，所述第二网关为所述第一网关的协同网关。
  20. 一种网关，包括：
    一个或多个处理器；
    存储器，设置为存储一个或多个程序；
    当所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现如权利要求1-5中任一项所述的拥塞控制方法，或者实现如权利要 求6-7中任一项所述的拥塞控制方法。
  21. 一种应用服务器，包括：
    一个或多个处理器；
    存储器，设置为存储一个或多个程序；
    当所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现如权利要求8-15中任一项所述的拥塞控制方法。
  22. 一种存储介质，所述存储介质存储有计算机程序，所述计算机程序被处理器执行时实现权利要求1-15中任一项所述的拥塞控制方法。
PCT/CN2021/071418 2020-02-19 2021-01-13 拥塞控制方法、装置、设备、介质及系统 Ceased WO2021164471A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
KR1020227007750A KR102767398B1 (ko) 2020-02-19 2021-01-13 혼잡 제어 방법, 장치, 설비, 매체 및 시스템
US17/764,294 US12245073B2 (en) 2020-02-19 2021-01-13 Congestion control method, apparatus and system, device and medium
EP21756626.4A EP4109941A4 (en) 2020-02-19 2021-01-13 Congestion control method, apparatus and system, device and medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010102683.7 2020-02-19
CN202010102683.7A CN112512021B (zh) 2020-02-19 2020-02-19 拥塞控制方法、装置、设备、介质及系统

Publications (1)

Publication Number Publication Date
WO2021164471A1 true WO2021164471A1 (zh) 2021-08-26

Family

ID=74953375

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/071418 Ceased WO2021164471A1 (zh) 2020-02-19 2021-01-13 拥塞控制方法、装置、设备、介质及系统

Country Status (5)

Country Link
US (1) US12245073B2 (zh)
EP (1) EP4109941A4 (zh)
KR (1) KR102767398B1 (zh)
CN (1) CN112512021B (zh)
WO (1) WO2021164471A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115378798A (zh) * 2022-08-22 2022-11-22 中国联合网络通信集团有限公司 基于动态感知的多集群网关协同方法及系统

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111181747B (zh) * 2018-11-09 2023-05-02 中兴通讯股份有限公司 一种网关协同实现方法、装置、IoT网关及存储介质
WO2024076904A1 (en) * 2022-10-03 2024-04-11 Convida Wireless, Llc Multiple simultaneously active gateways in a personal iot network

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102378264A (zh) * 2010-08-20 2012-03-14 中兴通讯股份有限公司 拥塞控制方法和系统
WO2015106565A1 (zh) * 2014-01-17 2015-07-23 中兴通讯股份有限公司 通过twan接入核心网时的拥塞控制方法及装置
CN110311800A (zh) * 2018-03-27 2019-10-08 中兴通讯股份有限公司 通信设备、节点的连接方法、存储介质、电子装置
CN110753002A (zh) * 2019-09-29 2020-02-04 北京浪潮数据技术有限公司 流量调度方法及装置

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7299294B1 (en) * 1999-11-10 2007-11-20 Emc Corporation Distributed traffic controller for network data
EP3694235A1 (en) * 2010-04-22 2020-08-12 Huawei Technologies Co. Ltd. Congestion/overload control method and apparatus
CN103888994B (zh) * 2012-12-21 2017-11-21 中国科学院计算技术研究所 一种具有热灾备能力的多网关处理方法及系统
JP5940990B2 (ja) * 2013-01-17 2016-06-29 日本電信電話株式会社 Ａｐｌ−ｓｃｍ−ｆｅおよびアプリケーション連携方法
CN104270725B (zh) * 2014-09-24 2018-04-10 中兴通讯股份有限公司 指示信息的确定、处理以及请求消息的处理方法及装置
WO2016056156A1 (ja) * 2014-10-07 2016-04-14 日本電気株式会社 通信集約システム、制御装置、処理負荷制御方法及びプログラムを格納した非一時的なコンピュータ可読媒体
CN204376932U (zh) * 2015-02-02 2015-06-03 武汉物联远科技有限公司 一种智能家居系统
US10567495B2 (en) * 2016-11-16 2020-02-18 Cisco Technology, Inc. Application based intelligent edge computing in a low power wide area network environment
CN109308233A (zh) * 2017-07-28 2019-02-05 中兴通讯股份有限公司 数据备份方法、装置及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102378264A (zh) * 2010-08-20 2012-03-14 中兴通讯股份有限公司 拥塞控制方法和系统
WO2015106565A1 (zh) * 2014-01-17 2015-07-23 中兴通讯股份有限公司 通过twan接入核心网时的拥塞控制方法及装置
CN110311800A (zh) * 2018-03-27 2019-10-08 中兴通讯股份有限公司 通信设备、节点的连接方法、存储介质、电子装置
CN110753002A (zh) * 2019-09-29 2020-02-04 北京浪潮数据技术有限公司 流量调度方法及装置

Non-Patent Citations (1)

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

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115378798A (zh) * 2022-08-22 2022-11-22 中国联合网络通信集团有限公司 基于动态感知的多集群网关协同方法及系统
CN115378798B (zh) * 2022-08-22 2024-02-13 中国联合网络通信集团有限公司 基于动态感知的多集群网关协同方法及系统

Also Published As

Publication number Publication date
EP4109941A4 (en) 2024-02-28
EP4109941A1 (en) 2022-12-28
US12245073B2 (en) 2025-03-04
CN112512021B (zh) 2025-11-25
US20220345935A1 (en) 2022-10-27
CN112512021A (zh) 2021-03-16
KR20220046626A (ko) 2022-04-14
KR102767398B1 (ko) 2025-02-14

Similar Documents

Publication Publication Date Title
CN110012437B (zh) 一种组播报文的发送方法、装置及系统
KR102835676B1 (ko) 이벤트 통지 방법, 장치 및 저장매체
CN110535676B (zh) Smf动态容灾的实现方法、装置、设备及存储介质
WO2021004444A1 (zh) 一种通信方法以及网元
WO2021227561A1 (zh) 通信方法和装置
CN110730487B (zh) 一种选择会话管理功能网元的方法、装置及系统
WO2021164471A1 (zh) 拥塞控制方法、装置、设备、介质及系统
WO2022237505A1 (zh) 一种通信方法、设备及系统
WO2019096306A1 (zh) 一种处理请求的方法以及相应实体
WO2018233451A1 (zh) 通信方法、装置和系统
CN110557265A (zh) 一种组播方法及装置
CN112243284B (zh) 选择amf的方法、装置及存储介质
WO2016165524A1 (zh) 内容访问方法、无线接入网内容分发网络基站和核心内容分发网络装置
WO2022095048A1 (zh) 一种通信方法、装置及计算机可读存储介质
CN116671137A (zh) 一种确定mec接入点的方法及装置
US20250193115A1 (en) Communication method, apparatus, and device
WO2014107836A1 (zh) 网络告警的方法和装置
CN114422427A (zh) 一种流量均衡方法、装置、电子设备和存储介质
WO2022068771A1 (zh) 一种通信方法及通信装置
TWI663884B (zh) 無線自主網路中通信設備的資料通信方法和通信設備
CN101815281A (zh) 一种处理本地疏导业务的方法、设备及通信系统
CN115915199A (zh) 一种5gc架构对应的方法及装置
KR102169718B1 (ko) 세션 그룹 제어 방법 및 장치
WO2018188447A1 (zh) 一种ip地址配置方法及装置
CN101656759B (zh) 实现移动网络p2p应用的方法、终端及系统

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 20227007750

Country of ref document: KR

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2021756626

Country of ref document: EP

Effective date: 20220919

WWG Wipo information: grant in national office

Ref document number: 17764294

Country of ref document: US