WO2018077184A1 - 流量调度 - Google Patents

流量调度 Download PDF

Info

Publication number
WO2018077184A1
WO2018077184A1 PCT/CN2017/107636 CN2017107636W WO2018077184A1 WO 2018077184 A1 WO2018077184 A1 WO 2018077184A1 CN 2017107636 W CN2017107636 W CN 2017107636W WO 2018077184 A1 WO2018077184 A1 WO 2018077184A1
Authority
WO
WIPO (PCT)
Prior art keywords
bras
target
mac address
openflow switch
correspondence
Prior art date
Application number
PCT/CN2017/107636
Other languages
English (en)
French (fr)
Inventor
柳佳佳
孙凯
Original Assignee
新华三技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 新华三技术有限公司 filed Critical 新华三技术有限公司
Publication of WO2018077184A1 publication Critical patent/WO2018077184A1/zh

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/12—Avoiding congestion; Recovering from congestion
    • H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2854—Wide area networks, e.g. public data networks
    • H04L12/2856—Access arrangements, e.g. Internet access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2854—Wide area networks, e.g. public data networks
    • H04L12/2856—Access arrangements, e.g. Internet access
    • H04L12/2869—Operational details of access network equipments
    • H04L12/287—Remote access server, e.g. BRAS
    • 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/08—Configuration management of networks or network elements
    • H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/25—Routing or path finding in a switch fabric
    • H04L49/253—Routing or path finding in a switch fabric using establishment or release of connections between ports

Definitions

  • the Broadband Remote Access Server is an access gateway for broadband network applications. It is located at the edge layer of the backbone network and can complete the user's bandwidth IP (Internet Protocol)/ATM (Asynchronous Transfer Mode). , Asynchronous Transfer Mode) Data access to the network to achieve broadband access to commercial buildings and residential households.
  • IP Internet Protocol
  • ATM Asynchronous Transfer Mode
  • FIG. 1 is a schematic diagram of a metropolitan area network networking architecture according to an exemplary embodiment of the present application
  • FIG. 2 is a flowchart of a traffic scheduling method according to an exemplary embodiment of the present application.
  • FIG. 3 is a flowchart of a traffic scheduling method according to an exemplary embodiment of the present application.
  • FIG. 4 is a schematic diagram of a hardware structure of a service orchestrator in which traffic scheduling logic is shown in an exemplary embodiment of the present application;
  • FIG. 5 is a schematic structural diagram of traffic scheduling logic according to an exemplary embodiment of the present application.
  • the client of the broadband user is served by the OLT. (Optical Line Terminal, optical line terminal) access, and then connected to the BRAS through a POP (Point of Present) switch.
  • the POP switch can be an aggregation switch provided by an operator, for example, an aggregation switch in a machine room.
  • PPPoE Point-to-Point Protocol over Ethernet
  • the PPPoE client initiates the establishment of a PPPoE session through a PADI (PPPoE Active Discovery Initial) message.
  • PADI PPPoE Active Discovery Initial
  • multiple BRASs as PPPoE servers
  • the PPPoE client will establish a PPPoE session with the first responding BRAS.
  • load balancing of multiple BRASs in the resource pool cannot be achieved.
  • the following embodiments provide a traffic scheduling method and a traffic scheduling device.
  • the MAN network architecture of the embodiment of the present application is as shown in FIG. 1 , and includes: a Service Orchestrator (SO), multiple BRASs in a resource pool, an OpenFlow switch, a POP switch, and an OLT.
  • SO Service Orchestrator
  • the client (not shown in FIG. 1) communicates with multiple BRASs in the resource pool via the OLT, the POP switch, and the OpenFlow switch, and the OpenFlow switch connects to the service orchestrator through the OpenFlow protocol control channel, where the OpenFlow protocol control channel includes: Packet In (message delivery) channel and Packet Out (message delivery) channel.
  • an OpenFlow switch can also be integrated into a POP switch.
  • the multiple BRASs included in the resource pool are functionally equivalent and can be backed up to each other.
  • the BRAS can be a physical BRAS device or a vBRAS (virtual BRAS) running on a general-purpose x86 server; the service orchestrator is responsible for creating, deploying, and managing A BRAS in the resource pool, a service channel is established between the service orchestrator and each BRAS (not shown in FIG. 1), for example, the management channel is a netconf (configuration management) channel, an SNMP (Simple Network Management Protocol) channel, Or a proprietary protocol channel.
  • netconf configuration management
  • SNMP Simple Network Management Protocol
  • the traffic scheduling method performed by the service orchestrator is as shown in FIG. 2 , and includes the following steps:
  • Step S201 Acquire load information of each BRAS of the plurality of remote access servers BRAS.
  • Step S202 receiving an access initiation message from the client sent by the OpenFlow OpenFlow switch.
  • the client communicates with the plurality of broadband BRASs through the OpenFlow switch.
  • Step S203 Select, according to the acquired load information, a target BRAS with the smallest load from the plurality of BRASs, and determine a MAC address of the target BRAS and a target port identifier of the target BRAS connected to the OpenFlow switch.
  • Step S204 Send the MAC address and the target port identifier of the target BRAS to the OpenFlow switch.
  • the OpenFlow switch replaces the destination MAC address of the access initiation message with the MAC address of the target BRAS, and sends the destination MAC address to the target BRAS.
  • the traffic scheduling method performed by the service orchestrator is as shown in FIG. 3 , and includes the following steps:
  • Step S301 Acquire a MAC address of each BRAS of the multiple BRASs, and a correspondence between the port identifiers of the BRASs connected to the BRAS on the OpenFlow switch.
  • an advertisement message is sent to the OpenFlow switch, where The source MAC address of the advertisement packet is the MAC address of the BRAS.
  • the OpenFlow switch After receiving the advertisement packet, the OpenFlow switch sends the advertisement packet and the port identifier of the advertisement packet received by the OpenFlow switch to the service orchestrator through the Packet In channel.
  • the service orchestrator can record the source MAC address of the advertisement packet and the port identifier when receiving the advertisement packet sent by the OpenFlow switch and the port identifier of the advertisement packet received by the OpenFlow switch. Corresponding relationship, so that the correspondence between the MAC address of the BRAS that sends the advertisement message and the port identifier of the BRAS connected to the OpenFlow switch is obtained.
  • the traffic classifier can send the first flow entry to the OpenFlow switch, where the first flow entry is used to indicate that the OpenFlow switch will receive the advertisement packet and the port identifier of the advertisement packet received by the OpenFlow switch. Sent to the business choreographer.
  • the OpenFlow switch can send the received advertisement message and the port identifier of the OpenFlow switch to the service orchestrator according to the first flow entry sent by the service orchestrator.
  • the advertisement message may be an RARP (Reverse Address Resolution Protocol) packet
  • the MAC address of the BRAS is specifically a MAC address of a downlink port connected to the OpenFlow switch on the BRAS.
  • the service orchestrator when creating the BRAS, the service orchestrator records the ID of the BRAS. In step S301, the service orchestrator can obtain the MAC address of the BRAS from the BRAS through the management channel, record the correspondence between the ID of the BRAS and the acquired MAC address, and obtain the correspondence between the BRAS ID and the MAC address of the BRAS. relationship.
  • Step S302 acquiring load information of each of the plurality of BRASs
  • the service orchestrator can periodically acquire the load information of each BRAS through the management channel, and record the correspondence between the ID of the BRAS and the acquired load information of the BRAS.
  • the acquired load information may be one or more combinations of load information.
  • the acquired load information is the number of broadband users carried by the BRAS, the CPU of the BRAS (central processing unit), the memory utilization of the BRAS, and the BRAS.
  • the load information such as line data traffic One or more combinations.
  • Step S303 when receiving the access initiation message sent by the OpenFlow switch, selecting the target BRAS with the smallest load from the plurality of BRASs according to the acquired load information, searching for the MAC address of the target BRAS, and the connection destination BRAS of the OpenFlow switch.
  • Target port identifier when receiving the access initiation message sent by the OpenFlow switch, selecting the target BRAS with the smallest load from the plurality of BRASs according to the acquired load information, searching for the MAC address of the target BRAS, and the connection destination BRAS of the OpenFlow switch.
  • weight values may be separately set for the plurality of load information.
  • a weighted load value corresponding to a plurality of load information combinations is obtained, and the BRAS having the smallest weighted load value is selected as the target BRAS.
  • the load information includes memory utilization, CPU utilization, PPPoE users, and uplink and downlink data traffic, and the corresponding weight values are 0.5, 0.1, 0.15, and 0.25, respectively.
  • a weighted load value is obtained, and the BRAS with the smallest weighted load value is selected as the target BRAS.
  • the service orchestrator may send a second flow entry to the OpenFlow switch, where the second flow entry is used to indicate the OpenFlow switch to the SO Send the received access initiation message from the client.
  • the OpenFlow switch sends the access initiation packet to the service orchestration device through the Packet In channel according to the second flow entry when receiving the access initiation packet sent by the client.
  • the access initiation packet is a broadcast packet.
  • step S303 if the service orchestrator receives the access initiation message, the ID of the target BRAS with the smallest load is found from the correspondence between the recorded BRAS ID and the load information, and the recorded BRAS ID and MAC address are obtained.
  • the MAC address of the target BRAS is found, and the destination port identifier of the connection destination BRAS on the OpenFlow switch is found from the correspondence between the recorded MAC address of the BRAS and the port identifier of the BRAS connected to the OpenFlow switch.
  • the MAC address of the target BRAS and the target port identifier of the connection target BRAS on the OpenFlow switch are obtained.
  • Step S304 Send the found MAC address and the target port identifier to the OpenFlow switch, so that the OpenFlow switch replaces the destination MAC address of the access initiation message with the MAC address, and then sends the destination MAC address to the target BRAS.
  • the target BRAS When receiving the access initiation packet, the target BRAS will respond to the access initiation packet, and subsequently, the client establishes a session with the target BRAS.
  • the service orchestrator can send the found MAC address and the target port identifier to the OpenFlow switch through the Packet Out channel, so that the OpenFlow switch can replace the destination MAC (Media Access Control) address of the access initiation message with the target.
  • the MAC address of the BRAS is then sent to the target BRAS through the destination port. Subsequently, the client establishes a session with the target BRAS and carries the corresponding data stream.
  • the foregoing access initiation packet is a packet for initiating a PPPoE session establishment, for example, a PADI packet; and IPoE (Internet Protocol over Ethernet) is adopted.
  • the access-initiated message is a packet for initiating an IPoE session establishment, for example, a DHCP (Dynamic Host Configuration Protocol) Discover report. Text.
  • the OpenFlow switch receives the access initiation packet sent by the client, sends the initiated access packet to the service orchestrator instead of all the BRASs in the resource pool. If the service orchestrator receives the access initiation message, the service candidate may select the target BRAS with the smallest load according to the pre-acquired load information, and obtain the MAC address of the target BRAS and the identifier of the target port connected to the target BRAS on the OpenFlow switch.
  • the target BRAS is configured to respond to the access initiation message and establish a session with the client, so that load balancing between the BRASs in the resource pool is implemented by scheduling traffic to the bearer on the BRAS with the smallest load.
  • the present application also provides an embodiment of a traffic scheduling device.
  • FIG. 4 is a hardware structural diagram of a service orchestrator provided by some embodiments of the present application.
  • the service organizer 400 can include a processor 410 and a machine readable storage medium 420.
  • the processor 410 and the machine readable storage medium 420 can communicate via a system bus 430. And, by reading and executing machine executable instructions corresponding to the traffic scheduling logic 60 stored in the machine readable storage medium 420, the processor 410 can perform the traffic scheduling method described above.
  • the machine-readable storage medium 420 referred to herein can be any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, and the like.
  • the machine-readable storage medium 420 may be a RAM (Random Access Memory), a volatile memory, a non-volatile memory, a flash memory, a storage drive (such as a hard disk drive), a solid state drive, or any type of A storage disk (such as a compact disc, a DVD, etc.), or a similar storage medium, or a combination thereof.
  • the traffic scheduling logic 60 of the embodiment of the present application includes the following units: an obtaining unit 601, a receiving unit 602, a selection searching unit 603, and a sending unit 604, where:
  • the obtaining unit 601 is configured to acquire load information of each BRAS of the plurality of remote access servers BRAS;
  • the receiving unit 602 is configured to receive, by the OpenFlow OpenFlow switch, an access initiation message sent by the client, where the client communicates with the multiple broadband BRASs through the OpenFlow switch;
  • the selecting and searching unit 603 is configured to select a target with the smallest load from the plurality of BRASs according to the acquired load information. Determining, by the BRAS, a MAC address of the target BRAS, and a target port identifier of the OpenFlow switch connected to the target BRAS;
  • the sending unit 604 is configured to send the MAC address and the target port identifier of the target BRAS to the OpenFlow switch, so that the OpenFlow switch replaces the destination MAC address of the access initiation message with the MAC address of the target BRAS. Transmitting to the target BRAS through the target port.
  • the obtaining unit 601 is further configured to acquire, for each of the plurality of BRASs, a first correspondence between the ID of the BRAS and the load information of the BRAS, and an ID of the BRAS. a second correspondence between the MAC address and a third correspondence between the MAC address of the BRAS and the port identifier of the BRAS connected to the OpenFlow switch.
  • the selection and searching unit 603 is configured to search for an ID of the target BRAS from the first correspondence, and search for a MAC address of the target BRAS from the second correspondence according to the ID of the found target BRAS; And searching, according to the MAC address of the target BRAS that is found, a target port identifier that is connected to the target BRAS on the OpenFlow switch from the third correspondence.
  • the obtaining unit 601 is configured to receive an advertisement packet sent by the OpenFlow switch, and a port identifier of the advertisement packet received by the OpenFlow switch, and record a source MAC address of the advertisement packet and the port identifier.
  • the third correspondence where the source MAC address of the advertisement packet is the MAC address of the BRAS that sends the advertisement packet.
  • the sending unit 604 is further configured to send, to the OpenFlow switch, a first flow entry, where the first flow entry is used to instruct the OpenFlow switch to send the received BRAS from the BRAS.
  • the sending unit 604 is further configured to send a second flow entry to the OpenFlow switch, where the second flow entry is used to instruct the OpenFlow switch to send the received location from the client to the SO.
  • the access initiation message is described.
  • the access initiation message is a message used to initiate a PPPoE session establishment or a message used to initiate an IPoE session establishment.
  • the device embodiment since it basically corresponds to the method embodiment, reference may be made to the partial description of the method embodiment.
  • the device embodiments described above are merely illustrative in which the single illustrated as separate components
  • the elements may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment. Those of ordinary skill in the art can understand and implement without any creative effort.

Landscapes

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

Abstract

本申请提供流量调度方法、业务编排器SO及机器可读存储介质，在实施例中，该SO获取多个远程接入服务器BRAS中的每一个BRAS的负载信息；接收到开放流OpenFlow交换机发送的来自客户端的接入发起报文；根据获取的负载信息，从所述多个BRAS中选择负载最小的目标BRAS，并确定所述目标BRAS的MAC地址、以及所述OpenFlow交换机上连接所述目标BRAS的目标端口标识；将目标BRAS的MAC地址和目标端口标识发送给所述OpenFlow交换机，以使所述OpenFlow交换机将所述接入发起报通过所述目标端口发送给所述目标BRAS。

Description

流量调度
相关申请的交叉引用
本专利申请要求于2016年10月26日提交的、申请号为201610948995.3、发明名称为“流量调度方法及装置”的中国专利申请的优先权，该申请的全文以引用的方式并入本文中。
背景技术
宽带远程接入服务器(Broadband Remote Access Server，BRAS)是面向宽带网络应用的接入网关，它位于骨干网的边缘层，可以完成用户带宽的IP(Internet Protocol，因特网协议)/ATM(Asynchronous Transfer Mode，异步传输模式)网的数据接入，实现商业楼宇及小区住户的宽带上网。
附图说明
图1是本申请一示例性实施例示出的城域网组网架构示意图；
图2是本申请一示例性实施例示出的流量调度方法的流程图；
图3是本申请一示例性实施例示出的流量调度方法的流程图；
图4是本申请一示例性实施例示出的流量调度逻辑所在的业务编排器的硬件结构示意图；
图5是本申请一示例性实施例示出的流量调度逻辑的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
在城域网(Metropolitan Area Network，MAN)组网模型中，宽带用户的客户端由OLT (Optical Line Terminal，光线路终端)接入，再通过POP(Point of Present，业务呈现点)交换机连接至BRAS。在一示例中，该POP交换机可为运营商提供的汇聚交换机，例如，机房中的汇聚交换机。
可采用PPPoE(Point-to-Point Protocol over Ethernet，基于以太网的点对点协议)接入以太网。在一示例中，PPPoE客户端通过PADI(PPPoE Active Discovery Initial，PPPoE活动发现初始)报文来发起PPPoE会话的建立。在如图1所示的组网中，资源池中的多台BRAS(作为PPPoE服务器)均会接收到该PADI报文并进行响应，PPPoE客户端会与最先响应的BRAS建立PPPoE会话。但是，在这种情况下，就无法实现资源池中的多台BRAS的负载均衡。
为了实现资源池中多台BRAS的负载均衡，本申请以下实施例中提供了流量调度方法，以及流量调度装置。
本申请实施例的城域网组网架构如图1所示，包括：业务编排器(Service Orchestrator，SO)、资源池中的多台BRAS、开放流(OpenFlow)交换机、POP交换机、以及OLT。客户端(图1中未示出)经由OLT、POP交换机、OpenFlow交换机与资源池中的多台BRAS通信，OpenFlow交换机通过OpenFlow协议控制通道与业务编排器连接，其中，OpenFlow协议控制通道包括：Packet In(报文上送)通道和Packet Out(报文下发)通道。在一示例中，OpenFlow交换机也可以集成到POP交换机中。
其中，资源池中包含的多个BRAS的功能对等，可以相互备份，BRAS可以是物理BRAS设备，也可以是通用x86服务器上运行的vBRAS(虚拟BRAS)；业务编排器负责创建、部署和管理资源池中的BRAS，业务编排器与每一个BRAS之间建立有管理通道(图1中未示出)，例如，该管理通道为netconf(配置管理)通道、SNMP(简单网络管理协议)通道、或者私有协议通道。
基于如图1所示的组网架构，本申请实施例中，业务编排器执行的流量调度方法如图2所示，包括以下步骤：
步骤S201，获取多个远程接入服务器BRAS中的每一个BRAS的负载信息。
步骤S202，接收到开放流OpenFlow交换机发送的来自客户端的接入发起报文。
所述客户端通过所述OpenFlow交换机与所述多个宽带BRAS通信。
步骤S203，根据获取的负载信息，从所述多个BRAS中选择负载最小的目标BRAS，并确定所述目标BRAS的MAC地址、以及所述OpenFlow交换机上连接所述目标BRAS的目标端口标识。
步骤S204，将该目标BRAS的MAC地址和目标端口标识发送给所述OpenFlow交换机。
所述OpenFlow交换机将所述接入发起报文的目的MAC地址替换为所述目标BRAS的MAC地址，通过所述目标端口发送给所述目标BRAS。
基于如图1所示的组网架构，本申请实施例中，业务编排器执行的流量调度方法如图3所示，包括以下步骤：
步骤S301，获取多个BRAS中的每一个BRAS的MAC地址、以及OpenFlow交换机上连接该BRAS的端口标识的对应关系；
为了能够让业务编排器获取到BRAS的MAC地址、以及该BRAS所连接的OpenFlow交换机的端口标识的对应关系，本申请实施例中，当BRAS启动，会向OpenFlow交换机发送通告报文，其中，该通告报文的源MAC地址为该BRAS的MAC地址。OpenFlow交换机在接收到该通告报文之后，会将该通告报文、以及OpenFlow交换机接收到该通告报文的端口标识，通过Packet In通道发送给业务编排器。这样，在步骤S301中，业务编排器当接收到OpenFlow交换机发送的通告报文、以及OpenFlow交换机接收到该通告报文的端口标识，就可以记录该通告报文的源MAC地址与该端口标识的对应关系，从而获得了发出该通告报文的BRAS的MAC地址与OpenFlow交换机上连接该BRAS的端口标识的对应关系。
其中，业务编排器可向OpenFlow交换机下发的第一流表项，其中，第一流表项用于指示所述OpenFlow交换机将接收到的通告报文、以及OpenFlow交换机接收到该通告报文的端口标识发送给业务编排器。OpenFlow交换机可以根据业务编排器下发的第一流表项，将接收到的通告报文、以及OpenFlow交换机接收到该通告报文的端口标识发送给业务编排器。
在一示例中，上述通告报文具体可以是RARP(反向地址解析协议)报文，BRAS的MAC地址具体为该BRAS上连接OpenFlow交换机的下行口的MAC地址。
另外，在创建该BRAS时，业务编排器记录该BRAS的ID。在步骤S301中，业务编排器还可以通过管理通道从BRAS获取该BRAS的MAC地址，记录该BRAS的ID与获取到的MAC地址的对应关系，从而获得BRAS的ID、该BRAS的MAC地址的对应关系。
步骤S302，获取这多个BRAS中的每一个BRAS的负载信息；
在一示例中，业务编排器可以通过管理通道，周期性的获取每一个BRAS的负载信息，记录BRAS的ID与获取到的该BRAS的负载信息的对应关系。获取的负载信息可以是一种或多种负载信息组合，例如，获取的负载信息为BRAS承载的宽带用户数、BRAS的CPU(中央处理单元)资源利用率、BRAS的内存利用率、BRAS的上下行数据流量等负载信息中的 一种或多种组合。
步骤S303，在接收到OpenFlow交换机发送的接入发起报文时，根据获取的负载信息，从多个BRAS中选择负载最小的目标BRAS，查找目标BRAS的MAC地址、以及OpenFlow交换机上连接目标BRAS的目标端口标识；
在一示例中，当获取的负载信息包括多种负载信息组合时，可为多种负载信息分别设置权重值。根据权重值，得到多种负载信息组合对应的加权负载值，选择加权负载值最小的BRAS作为目标BRAS。例如，负载信息包括内存利用率、CPU利用率、PPPoE用户数、上下行数据流量，其所对应的权重值分别为0.5、0.1、0.15、0.25。根据上述权重值，得到加权负载值，选择加权负载值最小的BRAS作为目标BRAS。
为了能够让OpenFlow交换机向SO发送来自客户端的接入发起报文，业务编排器可以向OpenFlow交换机下发第二流表项，其中，所述第二流表项用于指示所述OpenFlow交换机向SO发送接收到的来自客户端的接入发起报文。这样，OpenFlow交换机如果接收到客户端发来的接入发起报文，就会根据该第二流表项，将该接入发起报文通过Packet In通道发送给业务编排器。其中，接入发起报文为广播报文。
在步骤S303中，业务编排器如果接收到接入发起报文，从记录的BRAS的ID与负载信息的对应关系中，查找到负载最小的目标BRAS的ID，从记录的BRAS的ID与MAC地址的对应关系中，查找到目标BRAS的MAC地址，从记录的BRAS的MAC地址与OpenFlow交换机上连接该BRAS的端口标识的对应关系中，查找到OpenFlow交换机上连接目标BRAS的目标端口标识。从而，得到该目标BRAS的MAC地址，以及OpenFlow交换机上连接目标BRAS的目标端口标识。
步骤S304，将查找到的MAC地址和目标端口标识发送给OpenFlow交换机，以使OpenFlow交换机将接入发起报文的目的MAC地址替换为该MAC地址后，通过该目标端口发送给目标BRAS。
目标BRAS当接收到该接入发起报文会对该接入发起报文进行应答，后续，客户端会与目标BRAS建立会话。
其中，业务编排器可以通过Packet Out通道将查找到的MAC地址和目标端口标识发送给OpenFlow交换机，这样，OpenFlow交换机就可以将该接入发起报文的目的MAC(媒体访问控制)地址替换为目标BRAS的MAC地址，然后，将该接入发起报文通过目标端口发送给目标BRAS。后续，客户端就会与目标BRAS建立会话，并承载相应的数据流。
在本申请上述实施例的方法中，当采用PPPoE接入方式时，上述的接入发起报文为用于发起PPPoE会话建立的报文，例如，PADI报文；当采用IPoE(Internet Protocol over Ethernet，基于以太网的因特网协议)接入方式时，上述的接入发起报文为用于发起IPoE会话建立的报文，例如，DHCP(Dynamic Host Configuration Protocol，动态主机配置协议)Discover(发现)报文。
通过如图3所示的方法，OpenFlow交换机如果接收到客户端发来的接入发起报文，会将该发起接入报文发送给业务编排器，而不是广播给资源池中的所有BRAS。业务编排器如果接收到该接入发起报文，可以根据预先获取的负载信息，选择负载最小的目标BRAS，并得到该目标BRAS的MAC地址、以及OpenFlow交换机上连接该目标BRAS的目标端口的标识，然后将该MAC地址和目标端口标识发送给OpenFlow交换机，这样，OpenFlow交换机就会将该接入发起报文的目的MAC地址替换为查找到的MAC地址，通过目标端口发送给该目标BRAS，以使得该目标BRAS对该接入发起报文进行应答，并与客户端建立会话，从而通过将流量调度到负载最小的BRAS上承载，实现了资源池中的BRAS之间的负载均衡。
与前述流量调度方法的实施例相对应，本申请还提供了流量调度装置的实施例。
参见图4，图4为本申请一些实施例提供的业务编排器的硬件结构图。该业务编排器400可包括处理器410以及机器可读存储介质420。其中，处理器410和机器可读存储介质420可经由系统总线430通信。并且，通过读取并执行机器可读存储介质420中存储的与流量调度逻辑60对应的机器可执行指令，处理器410可执行上文所述的流量调度方法。
本文提到的机器可读存储介质420可以是任何电子、磁性、光学或其他物理存储装置，可以包含或存储信息，如可执行指令、数据，等等。例如，所述机器可读存储介质420可以是RAM(Random Access Memory，随机存取存储器)、易失存储器、非易失性存储器、闪存、存储驱动器(如硬盘驱动器)、固态硬盘、任何类型的存储盘(如光盘、DVD等)，或者类似的存储介质，或者它们的组合。
请参考图5，从功能上划分，本申请实施例的流量调度逻辑60中包括以下单元：获取单元601、接收单元602、选择查找单元603和发送单元604，其中：
获取单元601，用于获取多个远程接入服务器BRAS中的每一个BRAS的负载信息；
接收单元602，用于接收到开放流OpenFlow交换机发送的来自客户端的接入发起报文，其中，所述客户端通过所述OpenFlow交换机与所述多个宽带BRAS通信；
选择查找单元603，用于根据获取的负载信息，从所述多个BRAS中选择负载最小的目标 BRAS，并确定所述目标BRAS的MAC地址、以及所述OpenFlow交换机上连接所述目标BRAS的目标端口标识；
发送单元604，用于将目标BRAS的MAC地址和目标端口标识发送给所述OpenFlow交换机，以使所述OpenFlow交换机将所述接入发起报文的目的MAC地址替换为所述目标BRAS的MAC地址，通过所述目标端口发送给所述目标BRAS。
在一示例中，所述获取单元601进一步用于针对多个所述BRAS中的每一个BRAS，分别获取所述BRAS的ID与所述BRAS的负载信息的第一对应关系、该BRAS的ID与MAC地址的第二对应关系、以及所述BRAS的MAC地址与所述OpenFlow交换机上连接该BRAS的端口标识的第三对应关系。
所述选择查找单元603用于从所述第一对应关系中查找所述目标BRAS的ID；根据所述查找到的目标BRAS的ID，从所述第二对应关系中查找目标BRAS的MAC地址；根据所述查找到的目标BRAS的MAC地址，从所述第三对应关系中查找所述OpenFlow交换机上连接所述目标BRAS的目标端口标识。
在一示例中，获取单元601用于接收所述OpenFlow交换机发送的通告报文、以及所述OpenFlow交换机接收到该通告报文的端口标识；记录该通告报文的源MAC地址与该端口标识的第三对应关系，其中，该通告报文的源MAC地址是发出该通告报文的BRAS的MAC地址。
在一示例中，发送单元604，还用于向所述OpenFlow交换机发送第一流表项，其中，所述第一流表项用于指示所述OpenFlow交换机向所述SO发送接收到的来自BRAS的所述通告报文、以及所述OpenFlow交换机接收到该通告报文的端口标识。
在一示例中，发送单元604，还用于向所述OpenFlow交换机发送第二流表项，其中，所述第二流表项用于指示所述OpenFlow交换机向SO发送接收到的来自客户端的所述接入发起报文。
在一示例中，接入发起报文为用于发起PPPoE会话建立的报文，或者用于发起IPoE会话建立的报文。
上述逻辑中各个单元的功能和作用的实现过程具体详见上述方法中对应步骤的实现过程，在此不再赘述。
对于装置实施例而言，由于其基本对应于方法实施例，所以相关之处参见方法实施例的部分说明即可。以上所描述的装置实施例仅仅是示意性的，其中所述作为分离部件说明的单 元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
需要说明的是，在本文中，诸如第一和第二等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来，而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。
以上对本发明实施例所提供的方法和装置进行了详细介绍，本文中应用了具体个例对本发明的原理及实施方式进行了阐述，以上实施例的说明只是用于帮助理解本发明的方法及其核心思想；同时，对于本领域的一般技术人员，依据本发明的思想，在具体实施方式及应用范围上均会有改变之处，综上所述，本说明书内容不应理解为对本发明的限制。

Claims (15)

  1. 一种流量调度方法，包括：
    业务编排器SO获取多个远程接入服务器BRAS中的每一个BRAS的负载信息；
    所述SO接收到开放流OpenFlow交换机发送的来自客户端的接入发起报文，其中，所述客户端通过所述OpenFlow交换机与所述多个宽带BRAS通信；
    所述SO根据获取的负载信息，从所述多个BRAS中选择负载最小的目标BRAS，并确定所述目标BRAS的MAC地址、以及所述OpenFlow交换机上连接所述目标BRAS的目标端口标识；
    所述SO将目标BRAS的MAC地址和目标端口标识发送给所述OpenFlow交换机，以使所述OpenFlow交换机将所述接入发起报文的目的MAC地址替换为所述目标BRAS的MAC地址，通过所述目标端口发送给所述目标BRAS。
  2. 根据权利要求1所述的方法，进一步包括：
    针对多个所述BRAS中的每一个BRAS，所述SO分别获取所述BRAS的ID与所述BRAS的负载信息的第一对应关系、该BRAS的ID与MAC地址的第二对应关系、以及所述BRAS的MAC地址与所述OpenFlow交换机上连接该BRAS的端口标识的第三对应关系；
    所述确定所述目标BRAS的MAC地址、以及所述OpenFlow交换机上连接所述目标BRAS的目标端口标识，包括：
    所述SO从所述第一对应关系中查找所述目标BRAS的ID；
    根据所述查找到的目标BRAS的ID，所述SO从所述第二对应关系中查找目标BRAS的MAC地址；
    根据所述查找到的目标BRAS的MAC地址，所述SO从所述第三对应关系中查找所述OpenFlow交换机上连接所述目标BRAS的目标端口标识。
  3. 根据权利要求2所述的方法，其中，所述获取所述BRAS的MAC地址、以及所述OpenFlow交换机上连接该BRAS的端口标识的第三对应关系包括：
    所述SO接收所述OpenFlow交换机发送的通告报文、以及所述OpenFlow交换机接收到该通告报文的端口标识；
    所述SO记录该通告报文的源MAC地址与该端口标识的第三对应关系，其中，该通告报文的源MAC地址是发出该通告报文的BRAS的MAC地址。
  4. 根据权利要求3所述的方法，其中，所述方法还包括：
    所述SO向所述OpenFlow交换机发送第一流表项，其中，所述第一流表项用于指示所述 OpenFlow交换机向所述SO发送接收到的来自BRAS的所述通告报文、以及所述OpenFlow交换机接收到该通告报文的端口标识。
  5. 根据权利要求1所述的方法，其中，所述方法还包括：
    所述SO向所述OpenFlow交换机发送第二流表项，其中，所述第二流表项用于指示所述OpenFlow交换机向SO发送接收到的来自客户端的所述接入发起报文。
  6. 根据权利要求1所述的方法，其中，所述接入发起报文为以下任一报文：
    用于发起建立以太网的点对点协议PPPoE会话的报文，或者
    用于发起建立以太网的因特网协议IPoE会话的报文。
  7. 一种业务编排器SO，包括：
    处理器和机器可读存储介质，
    所述机器可读存储介质存储有能够被所述处理器执行的机器可执行指令，所述处理器被所述机器可执行指令促使：
    获取多个远程接入服务器BRAS中的每一个BRAS的负载信息；
    接收到开放流OpenFlow交换机发送的来自客户端的接入发起报文，其中，所述客户端通过所述OpenFlow交换机与所述多个宽带BRAS通信；
    根据获取的负载信息，从所述多个BRAS中选择负载最小的目标BRAS，并确定所述目标BRAS的MAC地址、以及所述OpenFlow交换机上连接所述目标BRAS的目标端口标识；
    将目标BRAS的MAC地址和目标端口标识发送给所述OpenFlow交换机，以使所述OpenFlow交换机将所述接入发起报文的目的MAC地址替换为所述目标BRAS的MAC地址，通过所述目标端口发送给所述目标BRAS。
  8. 根据权利要求7所述的业务编排器，其中，所述处理器进一步被所述机器可执行指令促使：
    针对多个所述BRAS中的每一个BRAS，分别获取所述BRAS的ID与所述BRAS的负载信息的第一对应关系、该BRAS的ID与MAC地址的第二对应关系、以及所述BRAS的MAC地址与所述OpenFlow交换机上连接该BRAS的端口标识的第三对应关系；
    所述处理器具体地被所述机器可执行指令促使：
    从所述第一对应关系中查找所述目标BRAS的ID；
    根据所述查找到的目标BRAS的ID，从所述第二对应关系中查找目标BRAS的MAC地址；
    根据所述查找到的目标BRAS的MAC地址，从所述第三对应关系中查找所述OpenFlow 交换机上连接所述目标BRAS的目标端口标识。
  9. 根据权利要求8所述的业务编排器，其中，所述处理器被所述机器可执行指令促使：
    接收所述OpenFlow交换机发送的通告报文、以及所述OpenFlow交换机接收到该通告报文的端口标识；
    记录该通告报文的源MAC地址与该端口标识的第三对应关系，其中，该通告报文的源MAC地址是发出该通告报文的BRAS的MAC地址。
  10. 根据权利要求9所述的业务编排器，其中，所述处理器进一步被所述机器可执行指令促使：
    向所述OpenFlow交换机发送第一流表项，其中，所述第一流表项用于指示所述OpenFlow交换机向所述SO发送接收到的来自BRAS的所述通告报文、以及所述OpenFlow交换机接收到该通告报文的端口标识。
  11. 根据权利要求7所述的业务编排器，其中，所述处理器进一步被所述机器可执行指令促使：
    向所述OpenFlow交换机发送第二流表项，其中，所述第二流表项用于指示所述OpenFlow交换机向SO发送接收到的来自客户端的所述接入发起报文。
  12. 根据权利要求7所述的业务编排器，其中，所述接入发起报文为用于发起以下任意：
    用于发起建立以太网的点对点协议PPPoE会话的报文，或者
    用于发起建立以太网的因特网协议IPoE会话的报文。
  13. 一种机器可读存储介质，存储有机器可执行指令，在被网络设备的处理器调用和执行时，所述机器可执行指令促使所述处理器执行：
    获取多个远程接入服务器BRAS中的每一个BRAS的负载信息；
    接收到开放流OpenFlow交换机发送的来自客户端的接入发起报文，其中，所述客户端通过所述OpenFlow交换机与所述多个宽带BRAS通信；
    根据获取的负载信息，从所述多个BRAS中选择负载最小的目标BRAS，并确定所述目标BRAS的MAC地址、以及所述OpenFlow交换机上连接所述目标BRAS的目标端口标识；
    将目标BRAS的MAC地址和目标端口标识发送给所述OpenFlow交换机，以使所述OpenFlow交换机将所述接入发起报文的目的MAC地址替换为所述目标BRAS的MAC地址，通过所述目标端口发送给所述目标BRAS。
  14. 根据权利要求13所述的机器可读存储介质，其中，所述机器可执行指令促使所述处理器进一步执行：
    针对多个所述BRAS中的每一个BRAS，分别获取所述BRAS的ID与所述BRAS的负载信息的第一对应关系、该BRAS的ID与MAC地址的第二对应关系、以及所述BRAS的MAC地址与所述OpenFlow交换机上连接该BRAS的端口标识的第三对应关系；
    所述机器可执行指令促使所述处理器执行：
    从所述第一对应关系中查找所述目标BRAS的ID；
    根据所述查找到的目标BRAS的ID，从所述第二对应关系中查找目标BRAS的MAC地址；
    根据所述查找到的目标BRAS的MAC地址，从所述第三对应关系中查找所述OpenFlow交换机上连接所述目标BRAS的目标端口标识。
  15. 根据权利要求14所述的机器可读存储介质，其中，所述机器可执行指令促使所述处理器执行：
    接收所述OpenFlow交换机发送的通告报文、以及所述OpenFlow交换机接收到该通告报文的端口标识；
    记录该通告报文的源MAC地址与该端口标识的第三对应关系，其中，该通告报文的源MAC地址是发出该通告报文的BRAS的MAC地址。
PCT/CN2017/107636 2016-10-26 2017-10-25 流量调度 WO2018077184A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610948995.3A CN107995124B (zh) 2016-10-26 2016-10-26 流量调度方法及装置
CN201610948995.3 2016-10-26

Publications (1)

Publication Number Publication Date
WO2018077184A1 true WO2018077184A1 (zh) 2018-05-03

Family

ID=62024384

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/107636 WO2018077184A1 (zh) 2016-10-26 2017-10-25 流量调度

Country Status (2)

Country Link
CN (1) CN107995124B (zh)
WO (1) WO2018077184A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110891028A (zh) * 2018-09-07 2020-03-17 华为技术有限公司 确定负载均衡策略的方法、装置及存储介质
CN112104566A (zh) * 2020-09-18 2020-12-18 网易（杭州）网络有限公司 一种负载均衡的处理方法和装置

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112653633B (zh) * 2020-11-16 2022-08-30 新华三技术有限公司 负载分担的实现方法及装置
CN113746709B (zh) * 2021-08-25 2023-01-31 烽火通信科技股份有限公司 转控分离动态容量管理方法、装置、设备及存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104040966A (zh) * 2012-11-09 2014-09-10 华为技术有限公司 处理报文的方法、转发面装置及网络设备
WO2014169470A1 (en) * 2013-04-19 2014-10-23 Telefonaktiebolaget L M Ericsson(Publ) Method and switch for lawful interception

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104040966A (zh) * 2012-11-09 2014-09-10 华为技术有限公司 处理报文的方法、转发面装置及网络设备
EP2908480A1 (en) * 2012-11-09 2015-08-19 Huawei Technologies Co., Ltd. Method, forwarding-plane apparatus, and network device for processing packet
WO2014169470A1 (en) * 2013-04-19 2014-10-23 Telefonaktiebolaget L M Ericsson(Publ) Method and switch for lawful interception
EP2987278A1 (en) * 2013-04-19 2016-02-24 Telefonaktiebolaget LM Ericsson (publ) Method and switch for lawful interception

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
LI, XIAOSHUANG, DISCUSSION ON IP NETWORK FLOW OPTIMIZATION BASED ON, 30 June 2015 (2015-06-30) *
MIU, WEI ET AL.: "Explore the Methods and Steps of the Evolution of MAN BRAS to SDN", DATA COMMUNICATIONS, 29 February 2016 (2016-02-29) *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110891028A (zh) * 2018-09-07 2020-03-17 华为技术有限公司 确定负载均衡策略的方法、装置及存储介质
CN110891028B (zh) * 2018-09-07 2021-12-21 华为技术有限公司 确定负载均衡策略的方法、装置及存储介质
CN112104566A (zh) * 2020-09-18 2020-12-18 网易（杭州）网络有限公司 一种负载均衡的处理方法和装置
CN112104566B (zh) * 2020-09-18 2024-02-27 网易（杭州）网络有限公司 一种负载均衡的处理方法和装置

Also Published As

Publication number Publication date
CN107995124B (zh) 2020-10-09
CN107995124A (zh) 2018-05-04

Similar Documents

Publication Publication Date Title
WO2018077184A1 (zh) 流量调度
WO2018090872A1 (zh) 数据处理
US7512139B2 (en) Methods and systems for enabling remote booting of remote boot clients in a switched network defining a plurality of virtual local area networks (VLANS)
US10791167B2 (en) User migration
US9992271B2 (en) ENF selection for NFVI
WO2017054757A1 (zh) 宽带接入
US9438679B2 (en) Method, apparatus, name server and system for establishing FCOE communication connection
JP6722816B2 (ja) パケット転送
US11431671B2 (en) Method and apparatus for dynamic discovery of a blockchain component in a cloud computing system
TW201519621A (zh) 用於在虛擬區域網路中管理雲端裝置之管理伺服器及其管理方法
WO2018233588A1 (zh) 转发表项生成
US11146531B2 (en) Separating CGN forwarding and control
WO2017186122A1 (zh) 流量调度
CN110430076B (zh) 一种路由管理方法及装置
WO2017186159A1 (zh) 报文传输
WO2018019216A1 (zh) Ap接入控制
EP2765743A1 (en) Layer 2 inter-connecting method, apparatus and system based on ipv6
WO2018010616A1 (zh) 基于链路层的网络管理
US10637717B2 (en) Fault resilient virtual broadband gateway
US10439877B2 (en) Systems and methods for enabling wide area multicast domain name system
US11418843B2 (en) Forwarding video-on-demand flow
WO2020135871A1 (zh) 光线路终端-内容分发网络的实现方法及装置、介质、网络系统
WO2016177185A1 (zh) 媒体访问控制mac地址的处理方法及装置
US20190207982A1 (en) Lan/san network security management
EP3726789A1 (en) Load sharing method, device, and system and computer readable storage medium

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

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

Country of ref document: EP

Kind code of ref document: A1