JP6477084B2 - Communication device and communication method - Google Patents

Description

  The present invention relates to a communication device and a communication method, and more particularly to a communication device and a communication method that charge for a flow.

  In recent years, a centralized control type network architecture has been proposed. As an example of the centralized control type network architecture, there is a technique called OpenFlow (for example, Patent Documents 1 and 2, Non-Patent Documents 1 and 2). OpenFlow is realized by an OpenFlow Controller and an OpenFlow Switch.

  The OpenFlow controller sets a flow entry describing the processing content for each flow in the flow table of the OpenFlow switch. When the OpenFlow switch receives a packet, the OpenFlow switch processes the received packet according to the flow entry of the flow corresponding to the packet. Note that if the flow corresponding to the received packet is not set, the OpenFlow controller sets the flow entry.

  Also, a technique for charging for a flow has been proposed (for example, Patent Document 3). The technique described in Patent Document 3 counts the number of packets and the number of bytes for each flow, and generates billing information based on the total number of packets and the total number of bytes. Furthermore, the technology described in Patent Document 3 defines a plurality of flows as one flow group, counts the number of packets and the number of bytes for each flow group, and generates billing information based on the total number of packets and the total number of bytes. Also do.

International Publication No. 2012/098786 International Publication No. 2012/133060 JP 2002-374251 A

“OpenFlow Switch Specification”, Version 1.1.0 Implemented (Wire Protocol 0x02), February 28, 2011 “OpenFlow Switch Specification”, Version 1.3.4 (Protocol version 0x04), March 27, 2014

  In the open flow, when charging for a flow, the technique described in Patent Document 3 described above may be applied. According to the technique described in Patent Literature 3, billing information is generated for each flow or flow group based on the total number of packets and the total number of bytes. Therefore, it is possible to charge for each flow or each flow group.

  However, in the technique described in Patent Document 3, when charging is performed for each flow group, the number of packets and the number of bytes are collectively counted for flows belonging to the same flow group. It is thought that the number is not counted. For this reason, there is a problem in that it is not possible to cope with a change in charging rate for each flow belonging to the same flow group.

  Accordingly, one of the objects of the present invention is to solve the above-described problem and charge the entire plurality of flows at the charging rate for each flow even when the charging rate is set for each of the plurality of flows. It is to provide a communication apparatus and a communication method that can be used.

  In one aspect, for each flow, the communication device includes a match condition that identifies the flow, statistical information of a packet that matches the match condition, an instruction that indicates processing contents of the packet that matches the match condition, and the flow A switch having a flow table in which a flow entry describing the flow entry is set, a match condition for identifying the flow for each flow, flow cookie information assigned to the flow, And a controller including a charging table in which a charging entry describing the charging rate for charging the flow is set. Here, as the flow cookie information, the same flow cookie information can be assigned to a plurality of flows. When the switch receives a packet that matches a match condition of any flow entry in the flow table, the switch processes the received packet according to the instruction of the flow entry and updates the statistical information of the flow entry. To do. When calculating the charge amount for the entire flow to which the specific flow cookie information is assigned, the controller acquires, from the switch, statistical information for each flow to which the specific flow cookie information is assigned, and the charge table Then, a charging rate for each flow to which the specific flow cookie information is assigned is acquired, and the charging amount is calculated based on the acquired statistical value and charging rate for each flow.

  In one aspect, a communication method includes: a switch, for each flow, a matching condition that identifies the flow; statistical information of a packet that matches the matching condition; processing content of the packet; and a flow assigned to the flow A flow table in which a flow entry describing cookie information is set is provided, and for each flow, a match condition for identifying the flow, flow cookie information assigned to the flow, and charging for the flow are provided in the controller. A billing table is provided in which a billing entry describing the billing rate when performing the billing is set. Here, as the flow cookie information, the same flow cookie information can be assigned to a plurality of flows. When the switch receives a packet that matches the match condition of any flow entry in the flow table, the switch processes the received packet according to the processing content of the flow entry, and displays statistical information of the flow entry. Update. When the controller calculates a charge amount for the entire flow to which the specific flow cookie information is assigned, the controller obtains statistical information for each flow to which the specific flow cookie information is assigned, and the charge table Then, a charging rate for each flow to which the specific flow cookie information is assigned is acquired, and the charging amount is calculated based on the acquired statistical value and charging rate for each flow.

  According to the above-described aspect, even when a charging rate is set for each of a plurality of flows, there is an effect that it is possible to charge the entire plurality of flows at a charging rate for each flow.

1 is a diagram illustrating a configuration example of a communication device according to a first embodiment. It is a figure which shows the example of the flow entry described in the nonpatent literature 1. It is a figure which shows the example of the flow entry described in the nonpatent literature 2. FIG. It is a figure which shows the example of the match conditions used in Embodiment 1,2. It is a figure which shows the example of the accounting table used in Embodiment 1,2. It is a figure which shows the structural example of the gateway apparatus of Embodiment 2. FIG. It is a figure which shows the peripheral structural example of the gateway apparatus of Embodiment 2. FIG. FIG. 10 is a sequence diagram illustrating an operation example of the gateway device according to the second embodiment.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.
(1) Embodiment 1
FIG. 1 shows a configuration example of the communication apparatus 10 of the present embodiment. A communication device 10 illustrated in FIG. 1 includes a switch 11 and a controller 12. The switch 11 includes a flow table 111, and the controller 12 includes a charging table 121. The switch 11 can be realized by an open flow switch, and the controller 12 can be realized by an open flow controller.

The flow table 111 is a table in which a plurality of flow entries for each flow can be set. FIG. 2 shows an example of a flow entry described in Non-Patent Document 1. The flow entry shown in FIG. 2 includes the following fields:
・ Match Fields
・ Counters
・ Instructions

FIG. 3 shows an example of the flow entry described in Non-Patent Document 2. The flow entry shown in FIG. 3 includes the following fields:
・ Match Fields
・ Priority
・ Counters
・ Instructions
・ Timeouts
・ Cookie
・ Flags

In the present embodiment, the flow entry of the flow table 111 corresponds to a match condition corresponding to “Match Fields”, statistical information corresponding to “Counters”, an instruction corresponding to “Instructions”, and “Cookie”. And at least the flow cookie information to be described. The match condition is a condition for identifying a flow, and is checked against packet header information. FIG. 4 shows an example of match conditions used in the present embodiment. The match condition shown in FIG. 4 corresponds to an excerpt of some match conditions from the match conditions shown in Non-Patent Document 2, and includes the following fields.
・ Ingress Port
・ Ether source
・ Ether dst
・ Ether type
・ VLAN id
・ VLAN priority
・ IP src
・ IP dst
・ IP proto
・ IP ToS bits
・ TCP / UDP src port
・ TCP / UDP dst port

  The statistical information is information representing statistical values (packet amount (byte), number of packets, etc.) of packets that match the matching condition. The statistical information is updated when a packet that matches the matching condition is received. The instruction is information indicating the processing content (transfer, discard, etc.) of the packet that matches the matching condition.

  The flow cookie information is information representing a cookie assigned to the flow. Note that the flow entry described in Non-Patent Document 1 shown in FIG. 2 does not show a cookie, but actually a cookie attached to the flow exists in the message structure. Further, in the section of A.3.4 Modify State Messages of Non-Patent Document 1, it is described that a cookie can be specified by struct ofp_flow_mod. Also, in the section of A.3.6 Read State Messages in Non-Patent Document 1, it is described that a cookie can be specified in a struct ofp_flow_stats_request set in a body included in a struct ofp_stats_request.

  The billing table 121 is a table in which a plurality of billing entries for each flow can be set. In the billing table 121, billing entries for predetermined flows including flows that are expected to occur in the future are set in advance. FIG. 5 shows an example of the billing table 121 used in this embodiment. In the present embodiment, it is assumed that at least a match condition, flow cookie information, and a charging rate are described in the charging entry of the charging table 121. The match condition is a condition for identifying a flow, and is checked against packet header information. Note that the match condition of the accounting table 121 corresponds to the match condition of the flow table 111. The flow cookie information is information representing a cookie assigned to the flow. The billing rate is a billing rate when billing the flow. Note that FIG. 5 shows a charging rate when the statistical information of the flow table 111 is a packet amount (byte). Further, in FIG. 5, “*” means any whose value is arbitrary.

  Here, the flow cookie information described in the flow table 111 and the billing table 121 can assign the same flow cookie information to a plurality of flows. For example, when charging is performed for all of a plurality of flows, the same flow cookie information can be assigned to the plurality of flows. For example, in FIG. 5, a flow whose source IP address (IP src) is “192.168.2.1” and whose destination IP address (IP dst) is “192.168.4.1” (hereinafter referred to as flow # 1 as appropriate). There is a flow (hereinafter referred to as flow # 2 as appropriate) having a source IP address “192.168.2.1” and a destination IP address “192.168.5.1”. The same flow cookie information (Cookie) “0000 0000 0000 0002” is assigned to these flows # 1 and # 2.

  When the switch 11 receives a packet that matches the match condition of any flow entry in the flow table 111, the switch 11 processes the received packet and updates the statistical information of the flow entry according to the instruction of the flow entry. .

  When calculating the charge amount for the entire flow to which the specific flow cookie information is assigned, the controller 12 obtains statistical information for each flow to which the specific flow cookie information is assigned from the switch 11 and from the charge table 121. The charge rate for each flow to which the specific flow cookie information is assigned is acquired. Then, the controller 12 calculates the charge amount based on the statistical information and the charge rate for each flow to which the specific flow cookie information is assigned.

  As described above, in the present embodiment, the flow cookie information described in the flow table 111 and the billing table 121 can be assigned the same flow cookie information to a plurality of flows. When calculating the charge amount for the entire flow to which the specific flow cookie information is assigned, the controller 12 obtains statistical information for each flow to which the specific flow cookie information is assigned from the switch 11 and from the charge table 121. The charge rate for each flow to which the specific flow cookie information is assigned is acquired. Then, the controller 12 calculates a charging amount based on the statistical information and the charging rate for each flow to which specific flow cookie information is assigned. Therefore, for a plurality of flows to which specific flow cookie information is assigned, the charging amount for all of the plurality of flows can be calculated based on the statistical information and the charging rate for each of the plurality of flows. As a result, even when a charging rate is set for each of a plurality of flows, it is possible to charge the entire plurality of flows at a charging rate for each flow.

(2) Embodiment 2
In the present embodiment, the communication device 10 of the first embodiment is applied to a gateway device. FIG. 6 shows a configuration example of the gateway device 20 of the present embodiment. The gateway device 20 shown in FIG. 2 connects an Ethernet (registered trademark), a Wi-Fi (Wireless Fidelity (registered trademark)), and a cellular network to each other. The gateway device 20 includes a switch 21, a controller 22, and communication I / F (Interface) 23-1 to 23-4. Here, the communication I / Fs 23-1 and 23-2 correspond to an Ethernet (registered trademark) network, the communication I / F 23-3 corresponds to a Wi-Fi (registered trademark) network, and the communication I / F 23- 4 corresponds to a cellular network. The switch 21 includes a flow table 211, and the controller 22 includes a charging table 221. The switch 21 can be realized by an open flow switch, and the controller 22 can be realized by an open flow controller. FIG. 7 shows a peripheral configuration example of the gateway device 20 of the present embodiment. The gateway device 20 is connected to peripheral terminals 30-1 to 30-4. In FIG. 7, the numbers below the names of the components represent IP addresses. The terminals 30-1 to 30-4 are connected to the communication I / Fs 23-1 to 23-4 in the gateway device 20, respectively.

  The flow table 211 and the charging table 221 are the same as the flow table 111 and the charging table 121 of the first embodiment, respectively. In addition, the flow cookie information described in the flow table 211 and the billing table 221 can assign the same flow cookie information to a plurality of flows as in the first embodiment.

  When receiving a packet from the terminals 30-1 to 30-4, the switch 21 searches the flow table 211 for a flow entry whose matching condition matches the received packet. When the flow entry is searched, the switch 21 updates the statistical information of the flow entry and processes the received packet according to the instruction of the flow entry. On the other hand, when the flow entry is not searched, the switch 21 transfers the received packet to the controller 22.

  When the controller 22 receives a packet from the switch 21, the controller 22 searches the charging table 221 for a charging entry whose matching condition matches the received packet. When the charging entry is retrieved, the controller 22 determines the instruction of the packet, generates a new flow entry describing the matching condition, the determined instruction, and the same flow cookie information as the charging entry, and generates The flow entry is set in the flow table 211 of the switch 21. Thus, when setting the flow entry in the flow table 211, the controller 22 sets the flow entry describing the match condition, the instruction, and the flow cookie information, and the statistical information of the flow entry is configured by the switch 21. Note that if a charging entry whose matching condition matches the packet received from the switch 21 is not found, the controller 22 generates a new flow entry describing “discard” as an instruction of the received packet, and stores it in the flow table 211. Although set, flow cookie information is not described in this flow entry.

  When calculating the charge amount for the entire flow to which the specific flow cookie information is assigned, the controller 22 obtains statistical information for each flow to which the specific flow cookie information is assigned from the switch 21 and from the charge table 221. The charge rate for each flow to which the specific flow cookie information is assigned is acquired. Then, for each flow to which the specific flow cookie information is assigned, the controller 22 multiplies the statistical value indicated by the statistical information of the flow by the charging rate of the flow, and adds the multiplication result of each flow. Calculate the billing amount.

  Hereinafter, in the gateway device 20 of this embodiment, an operation when the switch 21 receives a packet whose match condition does not match the flow table 211 will be described with reference to FIG. Here, it is assumed that the statistical information of the flow table 211 is the packet amount (byte), and the state of the accounting table 221 is the state of FIG.

  First, when the switch 21 receives a packet addressed to the terminal 30-3 from the terminal 30-1 (step A1), the switch 21 refers to the header information of the packet, and from the flow table 211, a flow whose matching condition matches the packet. Search for an entry. However, here, it is assumed that the flow entry is not searched. Therefore, the switch 21 stores the packet in the OFPT_PACKET_IN message for inquiring about the processing content of the packet received from the terminal 30-1, and transmits the OFPT_PACKET_IN message to the controller 22 (step A2).

  When receiving the OFPT_PACKET_IN message from the switch 21, the controller 22 refers to the header information of the packet stored in the OFPT_PACKET_IN message. Then, the controller 22 searches the charging table 221 for a charging entry whose matching condition matches the packet. Here, the accounting table 221 includes an accounting entry for flow # 1 whose source IP address is “192.168.2.1” of the terminal 30-1 and whose destination IP address is “192.168.4.1” of the terminal 30-3. To do. Therefore, the controller 22 determines the packet instruction to be transferred to the terminal 30-3. Then, the controller 22 sets information for setting the flow entry of the flow # 1 describing the match condition of the flow # 1, the determined instruction, and the flow cookie information “0000 0000 0000 0002” that is the same as the accounting entry of the flow # 1. Is stored in the OFPT_FLOW_MOD message for the OFPT_PACKET_IN message. Then, the controller 22 transmits the OFPT_FLOW_MOD message to the switch 21 (step A3).

  When the switch 21 receives the OFPT_FLOW_MOD message from the controller 22, the switch 21 sets a flow entry for the new flow # 1 in the flow table 211. As a result, the flow cookie information “0000 0000 0000 0002” is described in this flow entry. In addition, since the flow table 211 includes a flow entry that matches the matching condition with the packet constituting the flow # 1, the switch 21 transfers the packet received from the terminal 30-1 to the terminal 30-3. (Step A4). Therefore, when the switch 21 subsequently receives a packet addressed to the terminal 30-3 from the terminal 30-1, the switch 21 forwards the packet to the terminal 30-3 without transmitting an OFPT_PACKET_IN message to the controller 22 ( Step A5), the packet amount of statistical information is counted. Here, it is assumed that there is a flow entry in the flow table 211 that matches the matching condition with the packet addressed to the terminal 30-4 (packet constituting the flow # 2) received from the terminal 30-1. Therefore, even when the switch 21 receives a packet addressed to the terminal 30-4 from the terminal 30-1, the switch 21 transfers the packet to the terminal 30-4 without transmitting the OFPT_PACKET_IN message to the controller 22 (step A6). The amount of statistical information packets will be counted.

  On the other hand, after setting the flow entry of flow # 1 in the flow table 211, the controller 22 calculates the charge amount for the entire flow to which the same flow cookie information “0000 0000 0000 0002” as the flow # 1 is assigned. Then, a timer (not shown) is started (step A7). When the timer expires (step A8), the controller 22 designates the flow cookie information “0000 0000 0000 0002” and sends an OFPT_STATS_REQUEST (OFPST_FLOW) message requesting statistical information for each flow in which the flow cookie information is set. It transmits to the switch 21 (step A9).

  When the switch 21 receives the OFPT_STATS_REQUEST (OFPST_FLOW) message from the controller 22, the switch 21 displays the statistical information for each flow to which the flow cookie information “0000 0000 0000 0002” specified by the OFPT_STATS_REQUEST (OFPST_FLOW) message is assigned from the flow table 211. get. Here, statistical information for each flow # 1 and # 2 is acquired. Then, the switch 21 stores the statistical information for each flow # 1 and # 2 in the OFPT_STATS_REPLY message for the OFPT_STATS_REQUEST (OFPST_FLOW) message, and transmits the OFPT_STATS_REPLY message to the controller 22 (step A10).

  When the controller 22 receives the OFPT_STATS_REPLY message from the switch 21, the controller 22 extracts the statistical information for each flow # 1, # 2 from the OFPT_STATS_REPLY message. Then, the controller 22 acquires from the charging table 221 the charging rate for each flow # 1, # 2 to which the flow cookie information “0000 0000 0000 0002” is assigned. Here, the charging rate of flow # 1 is “¥ 0.002”, and the charging rate of flow # 2 is “¥ 0.003”. Therefore, the controller 22 first multiplies the packet amount indicated by the statistical information of the flow # 1 by the accounting rate “¥ 0.002” for the flow # 1. Subsequently, for the flow # 2, the controller 22 multiplies the packet amount indicated as the statistical information of the flow # 2 by the charging rate “¥ 0.003”. Then, the controller 12 adds the multiplication results for the two flows # 1 and # 2, and calculates the billing amount for the entire two flows # 1 and # 2.

  As described above, in the present embodiment, the same flow cookie information can be assigned to a plurality of flows as the flow cookie information described in the flow table 211 and the accounting table 221. When calculating the charge amount for the entire flow to which the specific flow cookie information is assigned, the controller 22 obtains statistical information for each flow to which the specific flow cookie information is assigned from the switch 21 and from the charge table 221. The charge rate for each flow to which the specific flow cookie information is assigned is acquired. Then, for each flow to which specific flow cookie information is assigned, the controller 12 multiplies the statistical value indicated by the statistical information of the flow by the charging rate of the flow, adds the multiplication result of each flow, and assigns it. Calculate the amount. Therefore, for a plurality of flows to which specific flow cookie information is assigned, the charging amount for all of the plurality of flows can be calculated based on the statistical information and the charging rate for each of the plurality of flows. As a result, even when a charging rate is set for each of a plurality of flows, it is possible to charge the entire plurality of flows at a charging rate for each flow.

In addition, this invention is not limited to the said embodiment, It is possible to change suitably in the range which does not deviate from the meaning.
For example, in the above embodiment, the controller sets the flow entry of the flow in the flow table with the OFPT_FLOW_MOD message when a new flow occurs in the switch and the OFPT_PACKET_IN message is received from the switch. However, the controller may set a flow entry of a predetermined flow in which a charging entry is set in the charging table in the flow table in advance.

  In the above embodiment, the controller starts the timer after setting the flow entry of the flow in the flow table with the OFPT_FLOW_MOD message. However, the controller may start the timer in advance at a predetermined timing. The predetermined timing may be when the OFPT_PACKET_IN message is received or before that. In this case, the flow cookie information for calculating the charge amount is not limited to the flow cookie information assigned to a newly generated flow.

  In the above embodiment, after the timer expires, the controller transmits an OFPT_STATS_REQUEST message to the switch to acquire statistical information from the switch. However, the controller may acquire statistical information at a desired timing without using a timer.

  In the above embodiment, the controller designates flow cookie information with an OFPT_STATS_REQUEST (OFPST_FLOW) message, and acquires only the statistical information of the flow to which the designated flow cookie information is assigned. However, in Non-Patent Document 1, the OFPT_STATS_REQUEST (OFPST_FLOW) message has a message structure that cannot specify flow cookie information. Therefore, the controller may acquire statistical information for each flow of all flows with the OFPT_STATS_REPLY message without specifying the flow cookie information with the OFPT_STATS_REQUEST (OFPST_FLOW) message. In this case, the controller may filter the statistical information of all flows, extract the statistical information for each flow to which specific flow cookie information is assigned, and calculate the billing amount.

  Moreover, in the said embodiment, the controller designates flow cookie information and acquires the statistical information of the flow to which the designated flow cookie information was allocated. However, the controller may prepare a predetermined bit mask and specify not only the flow cookie information but also a predetermined bit mask. The predetermined bit mask is a bit string having the same number of bits as the flow cookie information. In this case, the switch performs an AND operation on the flow cookie information with a predetermined bit mask for each bit string. The switch uses not only the flow cookie information specified by the controller but also the flow cookie information in which the result of the logical product operation is the same bit string as the predetermined bit mask as the specific flow cookie information. Then, the switch extracts all flows to which specific flow cookie information is assigned, and returns statistical information for each extracted flow to the controller. In this case, even if the flow cookie information specified by the controller is different, the statistical information of the flow in which the bit specified by the bit mask is set can also be acquired.

  In the above embodiment, the flow entry statistical information is the packet amount (byte), but it may be the number of packets.

  In the above embodiment, an example is given in which a flow is identified by an IP address, and charging can be performed for each user identified by the IP address. However, charging is performed in various units depending on the description of the match condition in the flow table. Can be done. Examples are given below.

  For example, consider a case where charging is performed on a per-user basis in a situation where a single device is used by a plurality of users. In this case, since a plurality of users transmit packets using the same IP address, the user cannot be identified by the IP address. Therefore, in this case, the flow can be identified by dividing the destination port (TCP / UDP dst port) for each user.

  Also, consider a case where a plurality of devices are grouped and charging is performed in units of groups. In this case, a flow can be identified by dividing a VLAN (Virtual Local Area Network) identifier (VLAN id) used for each group.

  Also, consider a case where charging is performed on a service basis. For example, it is conceivable that the terminal 30-3 has a server function and provides a service from the terminal 30-3 to the terminal 30-1. In this case, the flow can be identified by dividing the destination IP address (IP dst) for each service or dividing the destination port (TCP / UDP dst port).

  Consider a case where charging is performed according to the communication I / F to which the terminal is connected. In this case, the flow can be identified by referring to the reception port (Ingress Port).

  Moreover, in the said embodiment, although both the controller and the switch were provided in the communication apparatus, you may provide a controller and a switch in a separate apparatus.

  Further, the processing in the communication device may be realized by causing a CPU (Central Processing Unit) to execute a computer program. The program may be stored using various types of non-transitory computer readable media and supplied to a computer. Non-transitory computer readable media include various types of tangible storage media. Examples of non-transitory computer-readable media are magnetic recording media (for example, flexible disks, magnetic tapes, hard disk drives), magneto-optical recording media (for example, magneto-optical disks), CD-ROMs (Compact Disk-Read Only Memory). CD-R (CD-Recordable), CD-R / W (CD-ReWritable), semiconductor memory (for example, mask ROM, PROM (Programmable ROM), EPROM (Erasable PROM), flash ROM, RAM (random access memory) )including. Further, the program may be supplied to the computer by various types of temporary computer readable media. Examples of transitory computer readable media include electrical signals, optical signals, and electromagnetic waves. The temporary computer-readable medium can supply the program to the computer via a wired communication path such as an electric wire and an optical fiber, or a wireless communication path.

DESCRIPTION OF SYMBOLS 10 Communication apparatus 11 Switch 111 Flow table 12 Controller 121 Charge table 20 Gateway apparatus 21 Switch 211 Flow table 22 Controller 221 Charge table 23-1 to 23-4 Communication I / F
30-1 to 30-4 terminal

Claims (11)

For each flow, a matching condition for identifying the flow, statistical information of a packet that matches the matching condition, an instruction that indicates processing contents of the packet that matches the matching condition, and flow cookie information assigned to the flow A switch having a flow table in which a flow entry describing
A charging table is provided in which a charging entry describing a matching condition for identifying the flow, flow cookie information assigned to the flow, and a charging rate for charging the flow is set for each flow. A controller, and
The flow cookie information can assign the same flow cookie information to a plurality of flows,
When the switch receives a packet that matches a match condition of any flow entry in the flow table, the switch processes the received packet according to the instruction of the flow entry and updates the statistical information of the flow entry. And
When calculating the charge amount for the entire flow to which the specific flow cookie information is assigned, the controller acquires, from the switch, statistical information for each flow to which the specific flow cookie information is assigned, and the charge table To obtain a charging rate for each flow to which the specific flow cookie information is assigned, and calculate the charging amount based on the acquired statistical value and the charging rate for each flow.   The controller, for each flow to which the specific flow cookie information is assigned, multiplies the statistical value indicated by the statistical information of the flow by the charging rate of the flow, and adds the multiplication result of each flow to The communication apparatus according to claim 1, wherein a charge amount is calculated. In the billing table, a billing entry for a predetermined flow is set in advance,
The controller, when setting a flow entry of a flow for which a charging entry is set in the charging table in the flow table, describes the same flow cookie information as the charging entry in the flow entry. The communication apparatus as described in.   The controller sets, in the flow table, a flow entry describing the match condition, the processing content, and the flow cookie information as a flow entry of the flow when a new flow occurs in the switch. The communication apparatus according to claim 3.   5. The communication apparatus according to claim 4, wherein when the flow entry of a new flow is set in the flow table, the controller uses the flow cookie information assigned to the flow as the specific flow cookie information.   The communication device according to claim 5, wherein the controller starts a timer after setting a flow entry of a new flow in the flow table, and calculates the billing amount after the timer expires.   The communication device according to claim 3, wherein the controller sets in advance in the flow table a flow entry describing the match condition, the processing content, and the flow cookie information as the flow entry of the predetermined flow. .   8. The controller according to claim 1, wherein the controller specifies the specific flow cookie information for the switch, and obtains statistical information for each flow to which the specified specific flow cookie information is assigned from the switch. The communication apparatus of any one of Claims.   The controller acquires statistical information for each flow of all flows from the switch, and extracts statistical information for each flow to which the specific flow cookie information is assigned from the acquired statistical information. 8. The communication device according to any one of 1 to 7. The controller is
Prepare a predetermined bit mask that is a bit string of the same number of bits as the flow cookie information,
When the flow cookie information is ANDed with the predetermined bit mask for each bit string, the flow cookie information whose operation result is the same bit string as the predetermined bit mask is also the specific flow cookie information. Item 10. The communication device according to any one of Items 1 to 9. A flow that describes, for each flow, a match condition for identifying the flow, statistical information of a packet that matches the match condition, processing contents of the packet, and flow cookie information assigned to the flow. Provide a flow table where entries are set,
A charging table in which a charging entry describing a matching condition for identifying the flow, flow cookie information assigned to the flow, and a charging rate for charging the flow is set for each flow in the controller Provided,
The flow cookie information can assign the same flow cookie information to a plurality of flows,
When the switch receives a packet that matches the match condition of any flow entry in the flow table, the switch processes the received packet according to the processing content of the flow entry, and displays statistical information of the flow entry. Updated,
When the controller calculates a charge amount for the entire flow to which the specific flow cookie information is assigned, the controller obtains statistical information for each flow to which the specific flow cookie information is assigned, and the charge table The communication method of acquiring a charging rate for each flow to which the specific flow cookie information is assigned, and calculating the charging amount based on the acquired statistics and charging rate for each flow.

Images