WO2015065003A1 - Procédé de contrôle de qos via une gestion de trafic dépendant du service - Google Patents

Procédé de contrôle de qos via une gestion de trafic dépendant du service Download PDF

Info

Publication number
WO2015065003A1
WO2015065003A1 PCT/KR2014/010169 KR2014010169W WO2015065003A1 WO 2015065003 A1 WO2015065003 A1 WO 2015065003A1 KR 2014010169 W KR2014010169 W KR 2014010169W WO 2015065003 A1 WO2015065003 A1 WO 2015065003A1
Authority
WO
WIPO (PCT)
Prior art keywords
queue
service
traffic
qos
network device
Prior art date
Application number
PCT/KR2014/010169
Other languages
English (en)
Korean (ko)
Inventor
안태진
김형수
이세희
한경아
Original Assignee
주식회사 케이티
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 주식회사 케이티 filed Critical 주식회사 케이티
Priority to US15/032,707 priority Critical patent/US20160323189A1/en
Priority claimed from KR1020140147076A external-priority patent/KR101877595B1/ko
Publication of WO2015065003A1 publication Critical patent/WO2015065003A1/fr

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/30—Flow control; Congestion control in combination with information about buffer occupancy at either end or at transit nodes
    • 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/24—Traffic characterised by specific attributes, e.g. priority or QoS

Definitions

  • the present invention relates to QoS control, and more particularly, to a QoS control method through traffic processing for each service in a software defined networking environment.
  • SDN Software Defined Network
  • Open Networking Foundation defines an interface between hardware (switch) and controller (Network OS). This is a protocol for interacting with the data plane by separating the control plane from the physical network to control how data packets are delivered through the network.
  • An object of the present invention for solving the above problems is to provide a QoS control method in an SDN environment.
  • Another object of the present invention for solving the above problems is to provide a QoS control method using traffic processing according to a service.
  • Another object of the present invention for solving the above problems is to provide a method for adding or deleting a queue for processing traffic according to a service, and a QoS control method using traffic processing according to queue statistics and network types.
  • a method for controlling QoS by a controller includes performing at least one of adding, deleting, and changing at least one queue configured at an output port of a network device. Determining a setting change of the queue for; And transmitting a queue state change message including information on the setting change of the determined queue to a network device, to perform setting change of the queue.
  • the setting change of the queue may be determined based on a service requirement or a QoS policy change.
  • the method includes receiving queue characteristic information for at least one queue set at an output port of a network device; Generating a flow entry for mapping between a service and at least one queue based on the queue characteristic information; The method may further include controlling the network device to process traffic for each service according to the generated flow entry.
  • the queue status message including the queue characteristic information may be received from a network device.
  • each service may be mapped to at least one queue set separately by being divided into a priority queue and at least one weighted round robin (WRR) queue.
  • WRR weighted round robin
  • the generating of the flow entry may include mapping traffic for the highest rank service to be assigned to a priority queue and mapping traffic for the next rank service to be sequentially assigned to at least one WRR queue. have.
  • the generating of the flow entry may sequentially process traffic for the service of the highest rank and sequentially perform traffic for the service of the next rank based on a weight applied to each of the at least one WRR queue in the remaining traffic range. Can be mapped to be assigned.
  • traffic allocated to at least one critical server may be mapped to different WRR queues.
  • the controlling of the network device may include: transmitting a flow table change message including a generated flow entry to the network device; Updating the flow table of the network device using the flow table change message;
  • the method may include controlling the network device to process traffic for each service based on the updated flow table.
  • the queue that can be supported by the output port of the network device from the network device (Queue) Receiving a queue setting information message including information about; Mapping between a service and at least one queue based on a queue establishment information message and a QoS policy; Sending a queue state change message to the network device to establish at least one queue based on a mapping relationship between a service and at least one queue.
  • mapping between the service and at least one queue comprises: setting each of the at least one queue to a Priority queue or at least one Weighted Round Robin (WRR) queue; Mapping each service to at least one queue based on the priority of each service.
  • WRR Weighted Round Robin
  • the mapping of the services to the at least one queue based on the priority of each service may include mapping traffic for the highest priority service to be allocated to the priority queue and at least traffic for the next rank service. It can be mapped to be sequentially assigned to one WRR queue.
  • mapping the services to the at least one queue based on the priority of each service may be performed by processing the traffic for the highest priority service and applying a weight to each of the at least one WRR queue in the remaining traffic range. Based on this, traffic for next-order services may be mapped sequentially.
  • the queue state change message may include a command for adding or deleting a queue to an output port of the network device.
  • the method comprises the steps of: receiving information about a lost packet from a network device to calculate a packet loss rate; The method may further include changing a weight applied to each of the at least one WRR queue based on the packet loss rate.
  • the changing of the weights applied to each of the at least one WRR queue may be performed by including a command for changing a weight in the queue state change message and transmitting the weight change command to the network device.
  • the method comprises the steps of: receiving a queue status message comprising queue characteristic information for at least one queue set based on the queue status change message; Generating a flow entry for mapping between a service and at least one queue based on the queue characteristic information; The method may further include controlling the network device to process traffic for each service according to the generated flow entry.
  • a queue (support) supported by the output port of the network device Transmitting a queue setting information message including information on the controller to the controller; Receiving a queue state change message generated by the controller based on the queue setting information message and the QoS policy; Setting at least one queue to an output port according to the queue state change message.
  • the queue state change message may include information generated by a controller by mapping between a service and at least one queue based on a queue setting information message and a QoS policy.
  • the queue state change message may include information generated by the controller by mapping between a network and at least one queue according to a network type priority based on a queue setting information message and a QoS policy.
  • the setting of the output port may be configured such that traffic for a service of the highest rank is allocated to a priority queue and traffic for a service of a next rank may be sequentially assigned to at least one WRR queue. .
  • the setting of the output port may include sequentially processing traffic for a service of the highest priority and sequentially processing traffic for a service of the next rank based on a weight applied to each of the at least one WRR queue in the remaining traffic range. Can be set to be assigned.
  • the QoS control method using the traffic processing according to the service according to the present invention as described above it is possible to efficiently use the network resources while satisfying the service quality by differentiating and processing the various services according to the traffic characteristics.
  • the controller can accurately determine the queue status of the switch in real time so that it can issue appropriate QoS control commands to the switch.
  • FIG. 1 is a block diagram illustrating a configuration of a controller and a network apparatus for performing a QoS control method using traffic processing according to a service according to an embodiment of the present invention.
  • FIG. 2 is a conceptual diagram illustrating a priority queue and a weighted round robin queue according to an embodiment of the present invention.
  • FIG. 3 is a flowchart illustrating a method of controlling QoS by mapping a queue for each service according to an embodiment of the present invention.
  • FIG. 4 is an exemplary diagram for explaining a queue status message according to an embodiment of the present invention.
  • FIG. 5 is a flowchart illustrating a method of controlling QoS by changing a queue state according to an embodiment of the present invention.
  • FIG. 6 is a flowchart illustrating a procedure of adding a queue according to an embodiment of the present invention.
  • FIG. 7 is a flowchart illustrating a procedure of a method of deleting a queue according to an embodiment of the present invention.
  • FIG. 8 is a flowchart illustrating a procedure of changing a queue characteristic based on a lost packet rate according to an embodiment of the present invention.
  • FIG. 9 is a flowchart illustrating a procedure of mapping traffic allocated to a critical server to different queues according to an embodiment of the present invention.
  • FIG. 10 is a flowchart illustrating a method of controlling QoS by mapping queues for each network type according to an embodiment of the present invention.
  • 11 is a conceptual diagram illustrating a case where a queue is mapped for each network type according to an embodiment of the present invention.
  • first, second, A, and B may be used to describe various components, but the components should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from another.
  • the first component may be referred to as the second component, and similarly, the second component may also be referred to as the first component.
  • the controller referred to in the present invention is an integrated SDN controller, which may mean a function element for controlling related components (eg, a switch, a router, etc.) to control the flow of traffic. Can be.
  • related components eg, a switch, a router, etc.
  • controller is not limited to the physical implementation form or implementation location.
  • a controller refers to a controller function entity defined by OpenFlow (ONF), Internet Engineering Task Force (IETF), European Telecommunication Standards Institute (ETSI) and / or International Telecommunication Union Telecommunication (ITU-T). can do.
  • OpenFlow OpenFlow
  • IETF Internet Engineering Task Force
  • ETSI European Telecommunication Standards Institute
  • ITU-T International Telecommunication Union Telecommunication
  • the network device referred to in the present invention may refer to a functional element that substantially forwards, switches, or routes traffic (or packets), such as 'switch' or 'router'. Therefore, in the present invention, the network device may be referred to as a switch or a router.
  • a network device may mean a switch, a router, a switching element, a routing element, a forwarding element, and the like defined in ONF, IETF, ETSI, and / or ITU-T. Can be.
  • the parameter and / or message type (for example, flow table entry) defined in the ONF is used in the operation for QoS control in the openflow switch.
  • the mapping is not limited to the contents defined in ONF, and various parameters that can distinguish a controller from a switch can be used in transmitting a QoS control command between a controller and a switch, and messages used in an operation process for QoS control. Nor is it limited to the specific message mentioned later.
  • FIG. 1 is a block diagram illustrating a configuration of a controller and a network apparatus for performing a QoS control method using traffic processing according to a service according to an embodiment of the present invention.
  • a QoS control method using traffic processing according to a service may be performed by a controller and a switch.
  • the controller 100 includes a QoS policy management unit 110, a switch control unit 120, a flow table management unit 130, and a switch interworking processing unit 140.
  • the QoS policy manager 110 may manage a QoS policy for a domain managed by the controller 100.
  • the switch controller 120 may control the switch 200 to communicate with the controller 100 through the switch interworking processor 140. For example, the switch controller 120 may generate a control command for adding, modifying, and deleting a flow entry based on the QoS policy managed by the QoS policy manager 110, and may generate a control command.
  • the switch 200 can be controlled.
  • the flow table manager 130 may store and manage a parameter and a flow table for synchronizing the flow table.
  • the switch interworking processor 140 may process a protocol so that the switch 200 and the controller 100 can communicate.
  • the switch 200 includes a Qos controller 210, a switch controller 220, a flow table manager 230, and a controller interworking processor 240.
  • the QoS controller 210 may actually perform QoS control on the packet delivered to the output port.
  • the switch controller 220 may control the switch such as setting a queue characteristic for the output port. In addition, the switch controller 220 may receive and execute a control command from the controller 100.
  • the flow table manager 230 may manage the flow table received from the controller 100. That is, the flow table manager 230 may store and manage the parameters and the flow table for synchronizing the flow table for the switch.
  • the controller interworking processor 240 processes the protocol so that the controller 100 and the switch 200 can communicate.
  • FIG. 2 is a conceptual diagram illustrating a priority queue and a weighted round robin queue according to an embodiment of the present invention.
  • At least one queue may be set at an output port of a network device.
  • WRR weighted round robin
  • Service traffic can be classified into gold, silver, bronze, and best effort (BE) according to their characteristics.
  • Gold traffic is assigned to the priority queue and can be processed with the highest priority. In other words, if a packet is in a Priority queue, it can always be processed first, even if there is a packet in another queue.
  • Silver traffic has priority after Gold traffic. However, not all Silver traffic will always be processed before other Bronze or Best effort traffic, but will be processed by the assigned weight and then Bronze traffic.
  • Bronze traffic may also be processed by the assigned weight, followed by Best effort traffic.
  • Silver traffic can use 50% of the remaining bands used by Gold traffic
  • Bronze traffic can use 30% of the remaining bands used by Gold traffic
  • Best effort traffic can use the remaining bands left by Gold traffic. It may be set to use 20% of the band. Therefore, silver traffic may be processed with a higher priority than Bronze traffic, and Bronze traffic may be processed with a higher priority than Best effort traffic.
  • FIG. 3 is a flowchart illustrating a method of controlling QoS by mapping a queue for each service according to an embodiment of the present invention.
  • the switch may set a queue property for the output port x by using a command line interface (CLI) or a configuration protocol (S310).
  • CLI command line interface
  • S310 configuration protocol
  • the switch sets four queues for output port x, one queue (Q1) to Priority queue and the other three queues (Q2, Q3, Q4) to WRR (weighted round robin) queues. Can be set.
  • the switch sets four queues for output port x.However, the number of queues that can be set for an output port may vary depending on the functions or capabilities provided by the switch. The number of possible queues may also be three or more.
  • Weights may be set to w1% (Q2), w2% (Q3), and w3% (Q4) for the three queues Q2, Q3, and Q4 set to WRR, respectively.
  • high weights may be set for Q2, medium weights for Q3, and low weights for Q4.
  • the switch may newly set the queue characteristic for the output port x or, if the parameter value of the previously set queue characteristic is changed, may immediately notify the controller through the queue status message (S320).
  • the queue status message may include queue characteristic information such as output port x where the queue status change occurred, queue list, and queue characteristic values for the queue included in the queue list.
  • the queue characteristic value may include information on whether the corresponding queue is a priority queue or a WRR queue, and information on weight when the queue is a WRR queue.
  • the controller Since the controller receives the queue status message from the switch and knows the characteristics of each queue from the queue characteristic information, the controller configures a service-specific queue mapping table to determine which queues to assign flows to each service characteristic. It may be (S330).
  • Which queue to allocate for each service is determined by establishing QoS policy considering the importance of each service and sensitivity to delay or loss of packets according to network operation policy.
  • very important packets used for Broadband convergence Network (BcN) service or routing protocol can be assigned to Q1 queue as Gold service and important packets such as VoIP or IPTV service can be assigned to Q2 queue. have.
  • BcN Broadband convergence Network
  • packets such as VoD or VPN service may be assigned to the Q3 queue by defining it as a Bronze service, and general Internet service may be assigned to the Q4 queue by setting it as a best effort service.
  • the controller may configure or generate a flow entry so that the actual service-specific flow may be mapped to the corresponding queue (S340).
  • a flow entry may be divided into a match field for distinguishing flows and an action field indicating what action to perform on a corresponding flow packet.
  • the controller sends Flow 1 for BcN or routing protocol packets to Q1, Flow 2 for VoIP or real-time IPTV packets to Q2, and Flow 3 for VoD or VPN packets to Q3.
  • Flow 4 which is a normal Internet packet, can configure a flow entry to send a command to the switch to send to Q4.
  • the controller may include them in a flow table change message and transmit them to the switch (S350).
  • the switch may receive a flow table change message from the controller and update the flow table of the switch using a flow entry list included therein (S360).
  • QoS control according to queue characteristics may be performed by transmitting to the corresponding queue of the corresponding output port according to the action content set in the action field. That is, the switch may perform QoS control by allocating flows to different queues for each service (for example, a priority queue or a WRR queue) (S370).
  • FIG. 4 is an exemplary diagram for explaining a queue status message according to an embodiment of the present invention.
  • a queue status message transmitted by a switch to a controller will be described as an example.
  • Q2 can assign property to WRR and assign value to 50%
  • Q3 can assign property to WRR and assign value to 30%
  • Q4 can assign property to WRR. And value to 20%.
  • the value allocated to each queue can be determined by predicting the priority and traffic amount for each service, and the value can be changed by periodically collecting traffic during operation.
  • FIG. 5 is a flowchart illustrating a method of controlling QoS by changing a queue state according to an embodiment of the present invention.
  • the controller may control the QoS by transmitting a queue state change message to the switch.
  • the controller in order for the controller to change (e.g., add / modify / delete) the queue state of output switch x of the switch, it is necessary to provide configuration information such as the maximum number of queues that can be set on output port x or the supported queue characteristics. You must know.
  • the controller may transmit a queue setting information request message to the switch in order to know the queue setting information of the switch (S510).
  • the switch may transmit a queue setting information message for the output port x to the controller (S520).
  • the queue setting information message may include setting information such as the maximum number of queues that can be set in the output port x or the queue characteristics that can be supported.
  • the output port parameter is set to 'ANY' instead of x, it may mean that the queue setting information for all output ports of the switch is sent.
  • the switch may receive the queue configuration information request message and include the configuration information such as the maximum number of queues that can be set for the output port x and the queue characteristics that can be supported in the queue configuration information message and transmit the same to the controller.
  • the switch can configure the configuration information such as the maximum queue count and the supported queue characteristics of all output ports in a list form and send them to the controller. .
  • configuration information such as the maximum queue number that can be set for all output ports and the queue characteristics that can be supported may be identical.
  • the controller may determine to which service to map the corresponding queues according to the QoS policy (S530).
  • the switch may set four queues for output port x, and one of the queues Q1 as a priority queue and the other three queues Q2, Q3, and Q4 as weighted round robin (WRR) queues.
  • WRR weighted round robin
  • the controller maps the very important packets used for BcN service or routing protocol to Q1 queue by mapping Gold service, and important packets such as VoIP or IPTV service are mapped to Silver service, and high weight among WRR queues. Can be assigned to the Q2 queue with.
  • packets such as VoD or VPN service are mapped to the Bronze service and assigned to the Q3 queue having the middle weight among the WRR queues, and general Internet services are mapped to the best effort service to the Q4 queue having the lowest weight among the WRR queues. Can be.
  • the controller may transmit a queue state change message to the switch to reflect this to the switch (S540).
  • the queue state change message may include an output port x, a command, a queue list, and property information for each queue as an output port parameter.
  • the command may indicate a command to add, delete, or change the queue.
  • the queue characteristic information can be understood with reference to the table shown in FIG.
  • the switch may set the queue characteristic for the output port x by receiving a queue state change message from the controller (S550).
  • the switch sets one queue (Q1) to Priority Q for output port x, and the other three queues (Q2, Q3, and Q4) to weighted round robin (WRR) queues, and the weights of Q2, Q3, and Q4.
  • WRR weighted round robin
  • (weight) can be set to w1%, w2% and w3%, respectively.
  • the switch may transmit a queue status message to the controller (S560).
  • the queue status message may include an output port x, a queue list, a queue characteristic value, and the like.
  • the controller may generate a flow entry for QoS control after receiving the queue status message from the switch (S570), and load the generated flow entry into a flow table change message to the switch (S580).
  • the switch receiving the flow table change message may update the flow table (S590), and execute QoS control on the actual packet (S593).
  • FIG. 6 is a flowchart illustrating a procedure of adding a queue according to an embodiment of the present invention.
  • the controller may add a queue to a corresponding output port by sending an 'ADD' command to the switch.
  • the controller can add a queue with new queue characteristics to the switch according to the request of the service system or the change of the QoS policy.
  • the Q1 set on an existing switch can't handle this requirement if it is requested from a service system or QoS policy. You need to add a queue.
  • Q2 guarantees minimum bandwidth a bps (kbps, Mbps) for traffic (e.g., if output port x is a 1 Gbps port, the minimum bandwidth is a ⁇ 10 Mbps), while the maximum bandwidth is b bps (kbps, Mbps). For example, if the output port x is a 1 Gbps port, it may mean that the maximum bandwidth is limited to b ⁇ 10 Mbps.
  • the controller may transmit a queue state change message to the switch (S620).
  • the queue state change message may include parameters such as an output port x, a command to add a new queue, an id of a queue to be added, and property information on the queue to be added. Therefore, Q2 is added to output port x using a queue state change message that includes a command to add a new queue (ADD), and the minimum bandwidth (min_rate) is a% of the maximum transmission speed of output port x by the characteristic of Q2.
  • the maximum bandwidth (max_rate) can be set to be b% of the maximum transmission rate of the output port x.
  • the switch may further set Q2 to the output port x after receiving the queue state change message from the controller (S630). For example, two queues Q1 and Q2 may be set at the output port x.
  • the switch can send a queue status message to the controller (S640).
  • the queue status message may include an output port x, queue lists Q1 and Q2, and queue property values.
  • the controller may generate a flow entry for QoS control with reference to this (S650).
  • the controller could create a flow entry to send all packets destined for the destination (Dest. IP) to Q2 on output port x.
  • the controller may load the flow table change message to the switch (S660).
  • the flow table change message may include a parameter such as a new flow entry and a command to add it to the flow table.
  • the switch receiving the flow table change message may add a newly received flow entry to the flow table (S670). Therefore, the switch may transmit all packets destined for the destination (Dest. IP) to 10.1.1.0 among the packets entering the switch to Q2 of the output port x to perform QoS control according to the properties of Q2 (S680). ).
  • FIG. 7 is a flowchart illustrating a procedure of a method of deleting a queue according to an embodiment of the present invention.
  • the controller transmits a 'DELETE' command to a switch to delete a queue at a corresponding output port.
  • the output port x of the switch is currently assigned two queues, Q1 and Q2, and the property of Q1 is assigned to BE (Best Effort), and the property of Q2 is that the minimum bandwidth is equal to the maximum transmission speed of output port x.
  • the controller may determine to delete the queue set in the switch according to the request of the service system or the change of the QoS policy (S710). For example, you can guarantee at least some bandwidth for traffic destined for a particular server, but when the server stops service, you no longer need to guarantee bandwidth. In addition, if you guarantee a minimum amount of bandwidth for traffic to a specific customer site, and the customer terminates or changes the service, you may not need the minimum bandwidth guarantee. In this case, it is necessary to delete Q2 set at the output port x of the switch.
  • the controller may transmit a queue state change message to the switch (S720).
  • the queue state change message may include parameters such as an output port x, a command to DELETE the queue, and a queue id to be deleted.
  • the switch may delete Q2 at the output port x after receiving the queue state change message from the controller (S730). Therefore, output port x can delete Q2 from the two queues Q1 and Q2 and leave only Q1.
  • the switch may transmit a queue status message to the controller (S740).
  • the queue status message may include an output port x, a queue list Q1, a queue property value, and the like.
  • the switch may delete the flow entry related to Q2 of the output port x in the flow table (S750) and transmit a flow entry delete message to the controller (S760).
  • the controller may delete the flow entry after receiving the flow entry deletion message from the switch (S770).
  • the switch could delete the flow entry to send all packets destined for the destination (Dest. IP) to Q2 on output port x. Therefore, all packets coming into the output port x of the switch may be delivered to Q1 and processed as BE (Best Effort) (S780).
  • BE Best Effort
  • FIG. 8 is a flowchart illustrating a procedure of changing a queue characteristic based on a lost packet rate according to an embodiment of the present invention.
  • the controller may analyze the overall traffic situation as well as change the QoS policy during operation of the switch, and change the previously set queue property as needed.
  • the weight of the queue can be changed flexibly according to traffic conditions.
  • the controller may periodically send a queue statistics request message to the switch to request traffic statistics data for the queues (S810).
  • the queue statistics request message may include parameters such as a corresponding output port and a queue id.
  • the switch may transmit the queue statistics message including the traffic statistics data for the corresponding queue according to the queue statistics request message to the controller (S820).
  • the queue statistics message may include an output port, a queue id, a number of transmission packets, and a number of lost packets.
  • the controller may calculate a packet loss rate for the corresponding queue by receiving the queue statistics message (S830).
  • the packet loss rate may be calculated as lost packets / (transmitted packets + lost packets).
  • the controller may change the weights of the WRR queues by comparing the packet loss rate of the queues with a threshold preset for each queue (S830).
  • the weight of Q2 assigned to the silver service is increased to handle more traffic.
  • the controller may transfer information on the changed queue characteristic to a queue state change message and transmit the information to the switch (S840).
  • the queue status change message may include parameters such as an output port x, a command to change the queue characteristics (MODIFY), information about a queue id and queue characteristics to be changed, and the like.
  • the switch may change the weight for each queue according to the queue state change message (S850), and transmit the result to the queue state message to the controller (S860). For example, the switch may change the weights w1%, w2%, and w3% applied to the WRR queues Q2, Q3, and Q4 to y1%, y2%, and y3%, respectively.
  • FIG. 9 is a flowchart illustrating a procedure of mapping traffic allocated to a critical server to different queues according to an embodiment of the present invention.
  • the controller may map a queue to handle traffic destined for important servers differently from general data traffic.
  • the switch may set the characteristics of the queue and the set queue to the output port, respectively (S910).
  • the controller can know the information on the queue set in the switch by receiving a queue status message from the switch (S920).
  • the controller may configure a queue mapping table for processing traffic to important servers differently from general data traffic according to the QoS policy (S930).
  • the controller can map traffic to the SDN Controller to Q2 for processing as Silver service, and traffic to SIP Call Server to Q3 for processing to Bronze service.
  • the controller may generate a flow entry so that the actual flow may be mapped to the corresponding queue (S940).
  • the SDN Controller uses 10.1.1.1 as the IP address and yyyy as the port for the TCP connection with the switch.
  • the SIP Call Server uses 20.1.1.1 as the IP address and the TCP connection for the terminal. It is assumed that zzzz is used as the port.
  • the flow entry generated by the controller may be divided into a match field for distinguishing flows and an action field indicating what action to perform on packets of the flow.
  • the source IP and port can be represented by '*' indicating Any, and the traffic to the SIP Call Server.
  • the source IP and port may be marked with '*' because the destination IP only needs to specify the destination IP and port.
  • the action field may include an action to send the traffic flow to the SDN controller to Q2, and to send the traffic flow to the SIP Call Server to Q3.
  • the controller may load the flow table change message to the switch (S950).
  • the switch may receive the flow table change message from the controller and update the flow table of the switch by using the flow entry included in the flow table change message (S960).
  • the switch forwards it to Q2 of the output port x and processes it as WRR-type Silver traffic.
  • the switch forwards it to Q3 of the output port x and Bronze of WRR method. Traffic may be processed, and through this, QoS control according to a corresponding queue property may be performed (S970).
  • FIG. 10 is a flowchart illustrating a method of controlling QoS by mapping a queue for each network type according to an embodiment of the present invention
  • FIG. 11 illustrates a case of mapping a queue for each network type according to an embodiment of the present invention. This is a conceptual diagram.
  • the controller may perform QoS control according to the type of network in association with a switch.
  • the switch may set the characteristics of the queue and the set queue to the output port, respectively (S1010).
  • the controller can know the information on the queue set in the switch by receiving a queue status message from the switch (S1020).
  • the controller may configure a queue mapping table that may set a QoS policy differently according to the network type by referring to the queue status message (S1030).
  • the controller maps Q2 to process Silver Internet for wireless Internet traffic coming from 3G or 4G wireless access networks, and Q3 to process Bronze service for wireless Internet traffic coming from WIBRO wireless access networks.
  • Q4 For wired Internet traffic coming from a wired access network, it can be mapped to Q4 to be treated as a Best Effort (BE) service.
  • BE Best Effort
  • the cost to process the same data is highest for the 3G / 4G wireless Internet, followed by the higher WIBRO Internet and the lowest wired Internet. Therefore, the 3G / 4G wireless Internet is treated as a Silver service, the WIBRO wireless Internet is treated as a Bronze service, the QoS policy is set to treat the wired Internet as a BE (Best Effort) service, and the controller is assigned to the QoS policy for each network type. QoS can be controlled based on this.
  • the controller may configure a queue mapping table to differentiate traffic for each network type, and then generate a flow entry for allowing the actual flow to be mapped to the corresponding queue (S1040).
  • 3G / 4G wireless Internet traffic may enter Ingress 1 of the switch, WIBRO wireless Internet traffic may enter Ingress 2, and wired Internet traffic may enter Ingress 3.
  • the controller sets the Action field to forward flows coming into Ingress 1 of the match field to Q2 on output port x, and the Action field sets forwarding flows to Ingress 2 of the match field to Q3 of output port x.
  • the Action field can be configured to forward the flow into Ingress 3 of the Match field to Q4 of the output port x.
  • the controller may load it on the flow table change message to the switch (S1050).
  • the switch may receive a flow table change message from the controller and update the flow table of the switch using the flow entry included in the flow table change message.
  • the switch forwards 3G / 4G wireless Internet packets from Ingress 1 to Q2 on output port x for WRR-based Silver service, and WIBRO wireless Internet packets from Ingress 2 are forwarded to Q3 on output port x to WRR.
  • Processed by the Bronze service of the method, and wired Internet packets from Ingress 3 are delivered to Q4 of the output port x and processed by the BE (Best Effort) service of the WRR method to perform QoS control for each network type (S1060). .
  • QoS can be controlled through traffic discrimination processing for each service in the open flow switch.
  • WRR weighted round robin
  • the controller when the queue state is changed in the switch, the controller immediately informs the controller of the change, so that the controller can effectively change the queue state of the switch according to a network operation policy or traffic condition. QoS control can be effectively performed.

Abstract

L'invention concerne un procédé de contrôle de QoS via une gestion du trafic de chaque service dans un environnement réseau piloté par logiciel. Le procédé de contrôle de QoS par un contrôleur comprend les étapes consistant à : déterminer un changement de configuration de file d'attente consistant à exécuter une ou plusieurs opérations d'ajout, suppression et changement d'une ou plusieurs files d'attente configurées pour un port de sortie d'un appareil de réseau ; et exécuter le changement de configuration en transmettant à l'appareil de réseau un message de changement d'état de file d'attente contenant des informations relatives au changement de file d'attente déterminé. Divers services peuvent ainsi être traités différemment d'après leurs caractéristiques de trafic, ce qui procure à chaque service une qualité suffisante et permet d'utiliser efficacement les ressources réseau.
PCT/KR2014/010169 2013-10-28 2014-10-28 Procédé de contrôle de qos via une gestion de trafic dépendant du service WO2015065003A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US15/032,707 US20160323189A1 (en) 2013-10-28 2014-10-28 Method for controlling qos by handling traffic depending on service

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
KR10-2013-0128231 2013-10-28
KR20130128231 2013-10-28
KR10-2014-0147076 2014-10-28
KR1020140147076A KR101877595B1 (ko) 2013-10-28 2014-10-28 서비스에 따른 트래픽 처리를 이용한 QoS 제어 방법

Publications (1)

Publication Number Publication Date
WO2015065003A1 true WO2015065003A1 (fr) 2015-05-07

Family

ID=53004527

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2014/010169 WO2015065003A1 (fr) 2013-10-28 2014-10-28 Procédé de contrôle de qos via une gestion de trafic dépendant du service

Country Status (1)

Country Link
WO (1) WO2015065003A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017052154A1 (fr) * 2015-09-24 2017-03-30 엘지전자 주식회사 Procédé et dispositif au moyen duquel un service d'ordre prioritaire est transmis
WO2017157347A1 (fr) 2016-03-18 2017-09-21 Huawei Technologies Co., Ltd. Procédé et appareil pour tampons programmables dans des réseaux mobiles
CN107624230A (zh) * 2015-05-11 2018-01-23 华为技术有限公司 业务可用性管理的方法与实体

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20030052840A (ko) * 2001-12-21 2003-06-27 주식회사 케이티 차등형 서비스 네트워크에 적용되는 라우터의 측정된로드-기반 패킷 스케줄링방법
US20040092278A1 (en) * 2002-11-13 2004-05-13 Wilhelmus Diepstraten Managing priority queues and escalation in wireless communication systems
US20100302946A1 (en) * 2009-05-29 2010-12-02 Futurewei Technologies, Inc. System and Method for Relay Node Flow Control in a Wireless Communications System
US20110058564A1 (en) * 2009-09-09 2011-03-10 Alaxala Networks Corporation Network relay device and memory control method
US8208406B1 (en) * 2008-03-25 2012-06-26 Juniper Networks, Inc. Packet forwarding using feedback controlled weighted queues dynamically adjusted based on processor utilization

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20030052840A (ko) * 2001-12-21 2003-06-27 주식회사 케이티 차등형 서비스 네트워크에 적용되는 라우터의 측정된로드-기반 패킷 스케줄링방법
US20040092278A1 (en) * 2002-11-13 2004-05-13 Wilhelmus Diepstraten Managing priority queues and escalation in wireless communication systems
US8208406B1 (en) * 2008-03-25 2012-06-26 Juniper Networks, Inc. Packet forwarding using feedback controlled weighted queues dynamically adjusted based on processor utilization
US20100302946A1 (en) * 2009-05-29 2010-12-02 Futurewei Technologies, Inc. System and Method for Relay Node Flow Control in a Wireless Communications System
US20110058564A1 (en) * 2009-09-09 2011-03-10 Alaxala Networks Corporation Network relay device and memory control method

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107624230A (zh) * 2015-05-11 2018-01-23 华为技术有限公司 业务可用性管理的方法与实体
US10530668B2 (en) 2015-05-11 2020-01-07 Huawei Technologies Co., Ltd. Method and entities for service availability management
CN107624230B (zh) * 2015-05-11 2020-12-15 华为技术有限公司 业务可用性管理的方法与实体
US10972365B2 (en) 2015-05-11 2021-04-06 Huawei Technologies Co., Ltd. Method and entities for service availability management
US11805031B2 (en) 2015-05-11 2023-10-31 Huawei Technologies Co., Ltd. Method and entities for service availability management
WO2017052154A1 (fr) * 2015-09-24 2017-03-30 엘지전자 주식회사 Procédé et dispositif au moyen duquel un service d'ordre prioritaire est transmis
WO2017157347A1 (fr) 2016-03-18 2017-09-21 Huawei Technologies Co., Ltd. Procédé et appareil pour tampons programmables dans des réseaux mobiles
CN109155753A (zh) * 2016-03-18 2019-01-04 华为技术有限公司 用于移动网络中的可编程缓存区的方法和设备
EP3412007A4 (fr) * 2016-03-18 2019-03-13 Huawei Technologies Co., Ltd. Procédé et appareil pour tampons programmables dans des réseaux mobiles
US10645009B2 (en) 2016-03-18 2020-05-05 Futurewei Technologies, Inc. Method and apparatus for programmable buffers in mobile networks
CN109155753B (zh) * 2016-03-18 2021-01-29 华为技术有限公司 用于移动网络中的可编程缓存区的方法和设备
EP3913866A1 (fr) * 2016-03-18 2021-11-24 Huawei Technologies Co., Ltd. Procédé et appareil pour tampons programmables dans des réseaux mobiles

Similar Documents

Publication Publication Date Title
WO2015030491A1 (fr) Procédé de fourniture de bande passante sur la base d'un groupement de plusieurs flux
KR101877595B1 (ko) 서비스에 따른 트래픽 처리를 이용한 QoS 제어 방법
WO2018074703A1 (fr) Dispositif de station de base et procédé de commande de qos dans une section sans fil
WO2023033585A1 (fr) Système d'accès par passerelle et tunnellisation, optimisé pour un environnement de passerelle distribué, et procédé associé
WO2016023148A1 (fr) Procédé de régulation de paquets, commutateur et contrôleur
WO2019200728A1 (fr) Procédé et dispositif de commutation primaire et de secours dans une passerelle virtuelle, et support de stockage lisible par ordinateur
WO2016021773A1 (fr) Procédé et système de flux vidéo à qs garantie, et serveur de transmission
WO2016003234A1 (fr) Procédé et dispositif pour recevoir et transmettre des informations dans un système multimédia
WO2017131285A1 (fr) Système de gestion de réseau conteneur et procédé de mise en réseau conteneur
WO2015199340A1 (fr) Dispositif de réseau et terminal de communication à trajets multiples, procédé de commande correspondant, et programme implémentant un procédé de commande
WO2015065003A1 (fr) Procédé de contrôle de qos via une gestion de trafic dépendant du service
WO2015080525A1 (fr) Procédé et appareil destinés à la régulation dynamique du trafi dans un environnement sdn
WO2018038412A1 (fr) Procédé et équipement utilisateur permettant la connexion au moyen d'une pluralité d'accès dans un réseau de nouvelle génération
WO2015012454A1 (fr) Procédé d'amélioration des performances d'un réseau par commande de liaison virtuelle, et système de réseau l'employant
WO2018184302A1 (fr) Procédé de transmission de données, système, équilibreur de charge virtuelle et support de stockage lisible
WO2012165805A2 (fr) Dispositif et procédé destinés à un service de transmission de données simultanée en utilisant deux réseaux ou plus
WO2011136538A2 (fr) Procédé et appareil de transmission de données ethernet par l'intermédiaire d'une interface audio/vidéo
WO2015002436A1 (fr) Procédé et appareil permettant d'optimiser un trajet de données dans un système de communications mobiles
WO2015096040A1 (fr) Nœud d'accès, élément réseau de gestion mobile et procédé de traitement de message d'appel radio
WO2022092632A2 (fr) Procédé de découverte de créneau et de trajet de transmission basé sur un décalage pour une transmission de trafic à faible latence de bout en bout périodique, et dispositif de commande le mettant en œuvre
WO2015010252A1 (fr) Procédé, dispositif et système de fourniture de services dans un système de câble coaxial
WO2011031097A2 (fr) Procédé pour configurer une pluralité de sessions et nœud utilisant celui-ci
WO2011145896A2 (fr) Procédé et appareil de détermination d'un coordinateur
WO2012091288A1 (fr) Procédé de communication entre un terminal ip et un client
WO2019083223A1 (fr) Dispositif terminal, dispositif d'émission/réception de données, et procédé d'exploitation de dispositif

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 15032707

Country of ref document: US

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC ( EPO FORM 1205A DATED 10/08/2016 )

122 Ep: pct application non-entry in european phase

Ref document number: 14857370

Country of ref document: EP

Kind code of ref document: A1