JP2005229285A - Network device, and method for controlling network - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To enable a network provider to provide a service quality different to each client terminal device of a user by realizing the change control of the service quality on the network in a data distribution system. <P>SOLUTION: This network device is provided with: a communication path control means for controlling the communication path of inputted communication data based on address data in the inputted communication data; and a priority conversion means for converting priority data in the inputted communication data based on the address data in the inputted communication data. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to priority change control in a network device that controls service quality on a communication path.

  In recent years, the capacity of the network infrastructure has increased, and from a group of server devices that store various types of data such as images and voices using a relatively large network such as an in-house network or ISP (Internet Service Provider). A system for providing a data distribution service to a client terminal device via a network can be configured. In particular, a system used for high-quality image and audio streaming and content distribution such as E-learning is called a CDN (Contents Delivery Network). In such a data distribution system, when the load on the server device increases with an increase in service requests, the service quality is degraded.

  As a method for reducing the load on the server device in order to maintain the service quality, for example, in Patent Document 1, in an address translation device that relays communication data, a destination address based on the address of a client terminal device that is a source of a service request A method is disclosed in which service requests are distributed to a plurality of server devices and load is distributed by converting.

JP 2000-155736 A

  In the address translation device which is a conventional network device disclosed in Patent Document 1, although service quality can be maintained by distributing service requests to a plurality of server devices and distributing the load, for example, for each client terminal device However, there is a problem that it is not possible to cope with control of service quality on a network such as providing different service qualities.

  The present invention has been made to solve the above-described problems. In a data distribution system such as a CDN, the present invention realizes control of change of service quality on a network, and a network provider performs each client terminal device of a user. The purpose is to provide different service quality.

  The network device according to the present invention is based on communication path control means for controlling a communication path of the input communication data based on address data in the input communication data, and on the basis of address data in the input communication data. And priority conversion means for converting priority data in the input communication data.

  The present invention realizes control of quality of service on a network in a data distribution system by performing priority control of communication data based on converted priority data in another network device or server device on the network. be able to.

Embodiment 1 FIG.
The network device according to the first embodiment of the present invention refers to a conversion table in which predetermined conversion conditions are stored, and based on the address data of the transmission source, not only communication path control of communication data but also priority in communication data Data distribution system by performing priority control of communication data based on the converted priority data in another network device on the network or a server device that is the reception target of the communication data by converting the degree data The service quality control over the network can be realized.

  FIG. 1 is a block diagram showing a network system using a network device according to Embodiment 1 of the present invention. In FIG. 1, this network system includes server devices 201 to 203 that provide data, client terminal devices 204 and 205 that receive provision of a requested data distribution service, and a network device 206 that performs priority control based on priority data in communication data. Network device 207 that performs conversion of priority data in communication data and communication path control, server device network 208 that connects server devices 201 to 203 and network device 206, and server that connects network device 206 and network device 207 A device network 209, a network 207, and a user network 210 for connecting the client terminal devices 204 and 205 are provided.

  FIG. 2 is a block diagram showing a network device according to Embodiment 1 of the present invention. In FIG. 2, this network device 207 includes, for example, a frame processing unit 301 for realizing transmission / reception of a MAC (Media Access Control) frame (hereinafter referred to as a frame) based on Ethernet (registered trademark). A queue management unit 302 that manages a queue for transferring frames between the frame processing units 301, and an address in which information for determining priority in address conversion and priority conversion processing for an input frame is set Address conversion and priority conversion processing unit 303 that performs priority conversion processing based on the address conversion and priority conversion table 303 for frames input to the queue managed by the conversion and priority conversion table 303 and the queue management unit 302 304 is provided. The address conversion / priority conversion processing unit 304 corresponds to a communication path control unit and a priority conversion unit.

Next, the operation will be described.
The network device 207 receives the request communication data for the server devices 201 to 203 transmitted from the client terminal device 204 or 205 from the user network 210. At that time, in the network device 207, the frame processing unit 301 first receives the request frame. The received request frame is transferred to the queue management unit 302 for transfer processing. The request frame that has been passed to the queue management unit 302 and buffered is subjected to priority conversion by the address conversion and priority conversion processing unit 304. The priority value to be converted at this time is determined by the address conversion and priority conversion processing unit 304 based on the setting contents set in advance in the address conversion and priority conversion table 303. The request frame for which the conversion process has been completed is transferred from each queue management unit 302 to the frame processing unit 301 on the output side, and transmitted from the frame processing unit 301 to the outside of the network device 207.

  FIG. 3 is a diagram showing an address conversion and priority conversion table in the network device according to the first embodiment of the present invention. The address conversion and priority conversion table 303 shown in FIG. 3 includes a plurality of entries. Each entry includes a client 401 and mask 402 for specifying the address of the client terminal device, a global server address 403 for specifying the address of the server device, a protocol 404 for specifying the protocol, and a TCP (Transmission Control) in the protocol 404. When Protocol (UDP) or UDP (User Datagram Protocol) is specified, port number 405 for specifying the port number, local server address 406 indicating the address of the server device in the private network, and priority when the conditions match Each field of priority 407 for designating the degree is provided.

  4 and 5 are flowcharts showing the procedures of address translation and priority translation processing in the network device according to the first embodiment of the present invention. The processing target frame buffered in the queue management unit 302 is processed based on the flow shown in FIGS. At this time, the condition determination and the designated priority determination are performed with reference to the address conversion and priority conversion table 303 shown in FIG.

Next, the procedure of address conversion and priority conversion processing will be described in detail according to the flow of FIG.
First, it is checked whether the input frame is an IP (Internet Protocol) packet (step ST10). At this time, it is also necessary to check the IP version. Here, description will be made on the premise of IPv4 (Internet Protocol version 4). If the input frame is not an IP packet in step ST10 (NO in step ST10), it is not a priority conversion target of this process, and therefore a packet transmission request signal is output without conversion (step ST60). ), The address conversion and the priority conversion process are terminated.

  On the other hand, if the input frame is an IP packet in step ST10 (YES in step ST10), the input frame and the conditions 401 to 406 are selected from the entries of the address conversion and priority conversion table 303 set in advance. It is examined whether or not entries that all match are detected (step ST20).

  In step ST20, if an entry that matches all of the conditions is not detected (NO in step ST20), the input frame is not subject to address conversion and priority conversion in this process, and therefore a packet discard request signal is output. Output (step ST30), and the address conversion and priority conversion processing ends.

  On the other hand, if an entry that matches all the conditions is detected in step ST20 (YES in step ST20), the priority data in the input frame data buffered in the queue management unit 302 is set to the priority 407 in this entry. (Step ST40), the destination address data is converted to the data of the local server address 406 in this entry (step ST50), a packet transmission request signal is issued (step ST60), address conversion and priority The conversion process ends.

Next, according to the flow of FIG. 5, the detailed examination procedure in step ST20 will be described.
As a procedure for scrutiny, first, one entry is selected from the address conversion and priority conversion table 303 set in advance (step ST21), and the process proceeds to step ST22.

Then, it is determined whether or not the source IP address set in the IP packet in the input frame matches within the address range specified by the client 401 and the mask 402 in the selected entry (step ST22).
If the source IP address does not match in step ST22 (NO in step ST22), the process proceeds to step ST27.
If all the entries have not been confirmed in step ST27 (NO in step ST27), the process returns to step ST21. On the other hand, if all the entries have been confirmed (YES in step ST27), no entry that matches all the conditions is detected (NO in step ST20), and the process proceeds to step ST30.

If the source IP address matches in step ST22 (YES in step ST22), it is next determined whether or not the destination IP address in the input frame matches the global server address 403 (step ST23). .
If the destination IP address does not match in step ST23 (NO in step ST23), the process proceeds to step ST27.
If all the entries have not been confirmed in step ST27 (NO in step ST27), the process returns to step ST21. On the other hand, if all the entries have been confirmed (YES in step ST27), no entry that matches all the conditions is detected (NO in step ST20), and the process proceeds to step ST30.

If the destination IP address matches in step ST23 (YES in step ST23), it is next determined whether or not the upper layer protocol of the IP in the input frame matches the protocol 404 (step ST24). .
In step ST24, if the upper protocols do not match (NO in step ST24), the process proceeds to step ST27.
If all the entries have not been confirmed in step ST27 (NO in step ST27), the process returns to step ST21. On the other hand, if all the entries have been confirmed (YES in step ST27), no entry that matches all the conditions is detected (NO in step ST20), and the process proceeds to step ST30.

In step ST24, if the upper protocols match (YES in step ST24), it is determined whether the protocol is TCP or UDP (step ST25).
If the protocol is TCP or UDP in step ST25 (YES in step ST25), it is next determined whether or not the destination port number matches the port number 405 (step ST26).
If the port numbers do not match in step ST26 (NO in step ST26), the process proceeds to step ST27.
If all the entries have not been confirmed in step ST27 (NO in step ST27), the process returns to step ST21. On the other hand, if all the entries have been confirmed (YES in step ST27), no entry that matches all the conditions is detected (NO in step ST20), and the process proceeds to step ST30.

If the port numbers match in step ST26 (YES in step ST26), the client 401, mask 402, global server address 403, protocol 404, and port number 405 all match the input frame setting conditions. An entry has been detected (YES in step ST20).
In step ST25, if the protocol is other than TCP and UDP (NO in step ST25), since there is no concept of the port number, it is considered that all matching entries are detected when the protocol 404 is matched. (YES in step ST20).

  Through the above procedure, the request communication data transmitted from the client terminal device 204 or 205 is received by the network device 207 via the user network 210, and the network device 207 refers to the address conversion and priority conversion table 303. Thus, the priority data of the requested communication data is converted. The request communication data in which the priority data is converted is transmitted from the network device 207 to the server device network 209 and received by the other network device 206 via the server device network 209.

  The network device 206 performs priority control in the device based on the priority data specified in the received request communication data, and transfers it to the server device network 208. The requested communication data is delivered to one of the server apparatuses 201 to 203 via the server apparatus network 208. In the server apparatuses 201 to 203 that have received the request communication data, the request communication data is transferred to the application based on the priority data.

  Through the above operation, the request communication data transmitted from the client terminal device 204 or 205 is packet-transferred preferentially in the server device network 208 and the server devices 201 to 203, and for the data distribution service in the server devices 201 to 203. Delivered to applications.

  Next, the content communication data is transmitted from the server apparatuses 201 to 203 to the client terminal apparatus 204 or 205 as a response to the request communication data. The server devices 201 to 203 transmit the content communication data to the server device network 208 in order to deliver the content communication data to the client terminal device 204 or 205.

  The content communication data transferred to the server device network 208 is transferred to the network device 207 via the network device 206 and the server device network 209. In the network device 207, the address conversion and priority conversion processing in the content communication data is performed with reference to the address conversion and priority conversion table 303 in the same manner as the processing in the request communication data.

  Here, the procedure of the address conversion and priority conversion processing is performed by the same processing as the flow shown in FIG. 4 and FIG. 5, but the communication direction in the content communication data and the communication direction in the request communication data are the packet direction. Therefore, the address and port number to be compared are reversed for the transmission source and the destination.

Next, according to the flow of FIG. 4, the procedure of address conversion and priority conversion processing when content communication data is returned from the server apparatus 201 to 203 to the client terminal apparatus 204 or 205 will be described in detail.
First, it is checked whether the input frame is an IP packet (step ST10). At this time, it is also necessary to check the IP version. If the input frame is not an IP packet in step ST10 (NO in step ST10), it is not a priority conversion target of this process, and therefore a packet transmission request signal is output without conversion (step ST60). ), The address conversion and the priority conversion process are terminated.

  On the other hand, if the input frame is an IP packet in step ST10 (YES in step ST10), the input frame and the conditions 401 to 406 are selected from the entries of the address conversion and priority conversion table 303 set in advance. It is examined whether or not entries that all match are detected (step ST20).

  In step ST20, if an entry that matches all of the conditions is not detected (NO in step ST20), the input frame is not subject to address conversion and priority conversion in this process, and therefore a packet discard request signal is output. Output (step ST30), and the address conversion and priority conversion processing ends.

  On the other hand, if an entry that matches all the conditions is detected in step ST20 (YES in step ST20), the priority data in the input frame data buffered in the queue management unit 302 is set to the priority 407 in this entry. (Step ST40), the source IP address is converted to the global server address 403 in this entry (step ST50), a packet transmission request signal is issued (step ST60), and address conversion and priority conversion are performed. The process ends.

Next, according to the flow of FIG. 5, the detailed examination procedure in step ST20 will be described.
As a procedure for scrutiny, first, one entry is selected from the address conversion and priority conversion table 303 set in advance (step ST21), and the process proceeds to step ST22.

Then, it is determined whether or not the source IP address set in the IP packet in the input frame matches the local server address 406 in the selected entry (step ST22).
If the source IP address does not match in step ST22 (NO in step ST22), the process proceeds to step ST27.
If all the entries have not been confirmed in step ST27 (NO in step ST27), the process returns to step ST21. On the other hand, if all the entries have been confirmed (YES in step ST27), no entry that matches all the conditions is detected (NO in step ST20), and the process proceeds to step ST30.

If the source IP addresses match in step ST22 (YES in step ST22), then the destination IP address in the input frame matches within the address range specified by the client 401 and the mask 402. Is determined (step ST23).
If the destination IP address does not match in step ST23 (NO in step ST23), the process proceeds to step ST27.
If all the entries have not been confirmed in step ST27 (NO in step ST27), the process returns to step ST21. On the other hand, if all the entries have been confirmed (YES in step ST27), no entry that matches all the conditions is detected (NO in step ST20), and the process proceeds to step ST30.

If the destination IP address matches in step ST23 (YES in step ST23), it is next determined whether or not the upper layer protocol of the IP in the input frame matches the protocol 404 (step ST24). .
In step ST24, if the upper protocols do not match (NO in step ST24), the process proceeds to step ST27.
If all the entries have not been confirmed in step ST27 (NO in step ST27), the process returns to step ST21. On the other hand, if all the entries have been confirmed (YES in step ST27), no entry that matches all the conditions is detected (NO in step ST20), and the process proceeds to step ST30.

In step ST24, if the upper protocols match (YES in step ST24), it is determined whether the protocol is TCP or UDP (step ST25).
If the protocol is TCP or UDP in step ST25 (YES in step ST25), it is next determined whether or not the destination port number matches the port number 405 (step ST26).
If the port numbers do not match in step ST26 (NO in step ST26), the process proceeds to step ST27.
If all the entries have not been confirmed in step ST27 (NO in step ST27), the process returns to step ST21. On the other hand, if all the entries have been confirmed (YES in step ST27), no entry that matches all the conditions is detected (NO in step ST20), and the process proceeds to step ST30.

In step ST26, when the port numbers match (YES in step ST26), an entry whose input frame and all the conditions match is detected (YES in step ST20).
In step ST25, if the protocol is other than TCP and UDP (NO in step ST25), since there is no concept of port number, an entry with all matching conditions is detected when protocol 404 is matched. Can be regarded as having been made (YES in step ST20).

  Through the above operation, the content communication data transmitted from the server device 201 is received by the network device 207 via the user network 208, the network device 206, and the server device network 209. Here, the network device 207 refers to the address conversion and priority conversion table 303 and converts the priority data of the content communication data. The content communication data in which the priority data is converted is transmitted from the network device 207 to the user network 210 and received by the client terminal devices 204 and 205 via the network.

  As described above, in the network device according to the first embodiment of the present invention, frame priority setting control can be performed on input frames according to preset conditions. As a result, by converting the priority of the frame, priority control according to the converted priority can be performed in other network devices, and priority control can be performed in the entire server device network. There is.

  In addition, the addresses of the client terminal devices are classified in advance, a service class with a priority such as High or Low is defined for each classification, the quality level for each service class is distinguished, and a priority such as High or Low is assigned to the network device. By converting the degree data, a content distribution network having a quality control function corresponding to a profile such as a contract class for each user can be realized.

Embodiment 2. FIG.
The network device according to the second embodiment of the present invention refers to a conversion table in which predetermined conversion conditions are stored, and performs not only communication path control of communication data but also TCP of communication data based on source address data. By performing priority data conversion in the PUSH flag of the header, the server device on the network performs priority control of communication data based on the converted priority data, so that the service on the network can be performed in the data distribution system. Quality control can be realized.

  6 and 5 are flowcharts showing the procedures of address conversion and priority conversion processing in the network device according to the second embodiment of the present invention. FIG. 7 is a diagram showing a TCP header that is a target of address conversion and priority conversion processing in the network device according to the second embodiment of the present invention.

  The flow of the address conversion and priority conversion processing shown in FIG. 6 performs almost the same processing branch as the flow of the address conversion and priority conversion processing shown in FIG. The difference is that the PUSH flag of the header is operated (step ST40a).

  Although FIG. 7 shows the contents of the TCP header, the priority conversion in this embodiment is realized by converting the PUSH flag in the “flag” field. After the data conversion, the checksum value of each protocol field is changed.

  As described above, in the network device according to the second embodiment of the present invention, the priority setting control of the TCP packet can be performed on the input frame according to the preset condition. Thereby, priority conversion according to the set priority is attained in the receiving side server apparatus apparatus by converting a priority.

Embodiment 3 FIG.
The network device according to the third embodiment of the present invention refers to a conversion table in which predetermined conversion conditions are stored, and performs not only communication path control of communication data but also IP of communication data based on address data of a transmission source. Data distribution system by performing priority control of communication data based on the converted priority data in another network apparatus or server apparatus on the network by performing conversion of priority data in the Type of Service field of the header The service quality control over the network can be realized.

  8 and 5 are flowcharts showing the procedures of address conversion and priority conversion processing in the network device according to the third embodiment of the present invention. FIG. 9 is a diagram showing an IP header that is a target of address conversion and priority conversion processing in the network device according to the third embodiment of the present invention. FIG. 10 is a diagram showing an address conversion and priority conversion table in the network device according to the third embodiment of the present invention.

  The address conversion and priority conversion processing flow shown in FIG. 8 performs almost the same processing branch as the address conversion and priority conversion processing flow shown in FIG. The difference is that the set value in the Type of Service field of the header is manipulated (step ST40b).

  Although FIG. 9 shows the contents of the IP header, priority conversion in the present embodiment is realized by converting the Type of Service field. After the data conversion, the checksum value of each protocol field is changed.

FIG. 10 shows the structure of the address conversion and priority conversion table 303 referred to in the address conversion and priority conversion processing flow shown in FIG.
The address conversion and priority conversion table 303 shown in FIG. 10 includes a plurality of entries. Each entry includes a client terminal device 1001 and a mask 1002 for specifying the address of the client terminal device, a global server device address 1003 for specifying the address of the server device, a protocol 404 for specifying the protocol, and a TCP in the protocol 404. Alternatively, when UDP is specified, the port number 1005 for specifying the port number, the local server device address 1006 indicating the address of the server device in the private network, and the priority when the conditions match are specified. Each field of priority 1007 is provided. The difference between this table and that shown in FIG. 5 is that the conversion contents of the priority are “delay”, “throughput”, or “not set” so as to correspond to Type of Service.

  As described above, in the network device according to the third embodiment of the present invention, priority setting control of IP packets can be performed on input frames in accordance with preset conditions. Thus, by changing the priority, priority control according to the priority set in the IP packet can be performed in the receiving server device and other network devices in the server device network.

Embodiment 4 FIG.
The network device according to the fourth embodiment of the present invention refers to a conversion table in which predetermined conversion conditions are stored, and performs not only communication path control of communication data but also a VLAN of communication data based on address data of a transmission source. By performing the conversion of the priority data in the priority field of the (Virtual Local Area Network) tag, the other network devices on the network perform the priority control of the communication data based on the converted priority data. In the distribution system, control of service quality on the network can be realized.

  FIG. 11 and FIG. 5 are flowcharts showing the procedures of address conversion and priority conversion processing in the network device according to the fourth embodiment of the present invention. FIG. 12 is a diagram showing VLAN tags to be subjected to address conversion and priority conversion processing in the network device according to Embodiment 4 of the present invention.

  The flow of the address conversion and priority conversion processing shown in FIG. 11 performs almost the same processing branch as the flow of the address conversion and priority conversion processing shown in FIG. 5, but in the processing portion that performs the priority conversion processing, the VLAN The difference is that the tag priority field is operated (step ST40c).

  FIG. 12 shows the contents of the VLAN tag. The priority conversion in this embodiment is realized by converting the value of the priority field. After the data conversion, the checksum value of each protocol field is changed.

  As described above, in the network device according to the fourth embodiment of the present invention, it is possible to perform priority setting control for VLAN-compatible Ethernet (registered trademark) frames in accordance with preset conditions for input frames. Thereby, by setting the priority, priority control according to the priority set in the VLAN tag in the other network devices in the server device network becomes possible.

Embodiment 5 FIG.
The network device according to the fifth embodiment of the present invention refers to a conversion table in which predetermined conversion conditions are stored, and performs communication path control of communication data based on source address data and priority data. The address conversion rule to be applied can be switched on condition of priority data of communication data.

FIGS. 13 and 14 are flowcharts showing the procedures of address conversion and priority conversion processing in the network device according to the fifth embodiment of the present invention.
Address conversion and priority conversion processing are performed according to the flow shown in FIGS. 13 and 14, and the priority of the input frame is set as a condition for address conversion (step ST28). This makes it possible to switch the address translation rule to be applied on condition of the priority data of the input frame.

1 is a configuration diagram showing a network system using a network device according to Embodiment 1 of the present invention. The block diagram which shows the network device by Embodiment 1 of this invention The figure which shows the address conversion and priority conversion table in the network device by Embodiment 1 of this invention The flowchart which shows the procedure of the address translation in the network device by Embodiment 1 of this invention, and a priority translation process The flowchart which shows the procedure of the address translation in the network device by Embodiment 1 of this invention, and a priority translation process The flowchart which shows the procedure of the address conversion in the network apparatus by Embodiment 2 of this invention, and a priority conversion process The figure which shows the TCP header used as the object of the address translation and the priority translation process in the network device by Embodiment 2 of this invention The flowchart which shows the procedure of the address conversion in the network apparatus by Embodiment 3 of this invention, and a priority conversion process The figure which shows the IP header used as the object of the address conversion and the priority conversion process in the network device by Embodiment 3 of this invention The figure which shows the address conversion and priority conversion table in the network device by Embodiment 3 of this invention The flowchart which shows the procedure of the address conversion in the network apparatus by Embodiment 4 of this invention, and a priority conversion process The figure which shows the VLAN tag used as the object of the address conversion and the priority conversion process in the network device by Embodiment 4 of this invention The flowchart which shows the procedure of the address conversion in the network device by Embodiment 5 of this invention, and a priority conversion process The flowchart which shows the procedure of the address conversion in the network device by Embodiment 5 of this invention, and a priority conversion process

Explanation of symbols

204, 205 Client terminal device 207 Network device 303 Address conversion and priority conversion table 304 Address conversion and priority conversion processing unit

Claims (8)

Communication path control means for controlling a communication path of the input communication data based on address data in the input communication data;
Priority conversion means for converting priority data in the input communication data based on address data in the input communication data;
A network device comprising: A conversion table storing predetermined conversion conditions for converting priority data in the input communication data;
Priority conversion means for converting priority data in the input communication data based on address data in the input communication data with reference to the conversion table;
The network apparatus according to claim 1, further comprising: A conversion in which predetermined conversion conditions for converting priority data in the input communication data are stored, in which the addresses of a plurality of client terminal devices are classified, and the converted priority is associated with each class. Table,
The network apparatus according to claim 2, further comprising: Priority conversion means for converting priority data in a PUSH flag of a TCP (Transmission Control Protocol) header of the input communication data based on address data in the input communication data;
The network apparatus according to claim 1, further comprising: Priority conversion means for converting priority data in a Type of Service field of an IP (Internet Protocol) header of the input communication data based on address data in the input communication data;
The network apparatus according to claim 1, further comprising: Priority conversion means for converting priority data in a priority field of a VLAN (Virtual Local Area Network) tag of the input communication data based on address data in the input communication data;
The network apparatus according to claim 1, further comprising: Communication path control means for controlling a communication path of the input communication data based on address data and priority data in the input communication data;
The network apparatus according to claim 1, further comprising: A communication path control step for controlling a communication path of the input communication data based on address data in the input communication data;
A priority conversion step of converting priority data in the input communication data based on address data in the input communication data;
A network control method comprising:

Images