JP4630360B2 - Communication system and communication method - Google Patents

Description

  The present invention relates to a technique for transferring and processing a packet in a communication system.

  In recent years, various applications such as e-mail, WWW (World Wide Web), and VoIP (Voice over IP) can be used in an IP (Internet Protocol) network, and communication traffic is rapidly increasing. This IP network is configured by a router that determines the output line of a packet based on the IP header information of the received packet. Initially, routing processing was performed by software, but in recent years, in order to cope with an increase in communication traffic. Routers that perform this processing in hardware are in the spotlight.

In hardware implementation of transfer processing, a function distribution system as disclosed in Patent Document 1 and Non-Patent Document 1 has been proposed for the purpose of further improving the performance of the router. Specifically, it is a communication system in which the function of a router is divided into a function for controlling routing and a function for transferring packets, and these are assigned to different nodes. According to this configuration, the communication system can perform the packet transfer process without being affected by the load on the routing control process.
JP 2006-135975 A TV Laksman, T. Nandagopal, R. Ramjee, K. Sabnani, and T. Woo, "The SoftRouter architecture," in Proc. ACM SIGCOMM Workshop on Hot Topics in Networking, November 2004.

  However, even with such a function-distributed communication system, when the number of applications for providing services is large, the operation of the communication system may be hindered.

  More specifically, as the number of applications and the number of nodes that provide services by executing the applications increase, the number of combinations increases. For each of these combinations, it is necessary to assign a number or label as an identifier for identifying the combination, making it difficult to manage a large number of identifiers.

  Further, when a plurality of services are executed by a plurality of nodes, it may be necessary to change the routing table stored in each node of the entire communication system even if the service is partially changed.

  For this reason, in a complicated communication system, there has been a problem that it is difficult to make changes such as service addition and deletion.

  An object of this invention is to provide the technique which implement | achieves the communication system which can change a service easily.

In order to achieve the above object, a communication system of the present invention includes a first forwarding node accommodated in a first network, a second forwarding node and a service processing node accommodated in a second network, and a control. The control node creates a first table in which packet header information and application identification information indicating an application for providing a predetermined service are associated with each other, A second table in which a first table is distributed to the second forwarding node , and header information of the packet is associated with network identification information indicating a second network in which a service processing node that processes the packet is accommodated; further creates a table, to deliver the second table created in the first forwarding node, said first transfer node, the from the control node Receiving a second table, when receiving the packet, it reads from the network identification information of the second, which has received the table corresponding to the header information of the packet, stored in the second network indicated by the read-out net-identification information The packet is forwarded to the second forwarding node, and the second forwarding node receives the first table from the control node. When the packet is received, the application corresponding to the header information of the packet is received. The identification information is read from the received first table, the read application identification information is added to the packet, the packet with the application identification information is transferred to the service processing node via a predetermined route, and the service When the processing node receives the packet transferred from the second transfer node, the processing node adds the address assigned to the received packet. Executing the application indicated by the re-identification.

The communication method of the present invention creates a first table in which the header information of a packet is associated with application identification information indicating an application for providing a predetermined service in the control node, and the created first table To the second forwarding node, and further creating a second table in which the header information of the packet is associated with the network identification information indicating the second network in which the service processing node that processes the packet is accommodated The generated second table is distributed to the first forwarding node, and the first forwarding node accommodated in the first network receives the second table from the control node and receives the packet. then, reading from the network identification information of the second, which has received the table corresponding to the header information of the packet, the indicated by the read-out net-identification information The packet transferred to the housed second network a second transfer node, the second transfer node contained in the second network, receiving said first table from the control node, a packet Is received from the first table that received the application identification information corresponding to the header information of the packet, the read application identification information is attached to the packet, and the packet with the application identification information is attached to the packet. When the packet transferred from the second transfer node is received by the service processing node accommodated in the second network and transferred to the service processing node through a predetermined route, the packet is added to the received packet. A communication method for executing an application indicated by the application identification information.

  The program of the present invention is a program for controlling a forwarding node storing a first table in which header information of a packet is associated with application identification information indicating an application for providing a predetermined service, The application identification information corresponding to the header information of the received packet is read from the first table to the computer, and the application identification is performed by the packet processing procedure for adding the read application identification information to the packet, and the packet processing means This is a program for executing a transfer procedure for transferring the packet to which information is added to another node through a predetermined route.

  According to the present invention, since the service processing node is connected to a network different from that of the first forwarding node, it is not necessary to change the routing table of the first forwarding node even when changing the service.

  In addition, since the control node creates a second table in which header information and application identification information are associated with each other separately from the routing table, it is necessary to change the routing table of the second forwarding node unless the connection form is changed. There is no.

  Therefore, even if there is a change in service, the path control becomes easy, and the communication system can easily change the service.

  A first embodiment for carrying out the present invention will be described in detail with reference to the drawings. FIG. 1 is an overall view showing a configuration of a communication system 1 according to the present embodiment. Referring to the figure, communication system 1 includes transfer system group control system processing devices 15 and 16 (control node), transfer system processing devices (first transfer nodes) 31 and 33, and transfer system processing devices (first processing nodes). 2 forwarding nodes) 41 and a service processing device (service processing node) 43.

  Transfer processing units (first transfer nodes) 31 and 33 are accommodated in the metro subnetwork 3 (first network), and transfer processing units (second transfer nodes) 41 and service processing units (service processing nodes). ) 43 is accommodated in the SE sub-network 4 (second network).

  A service subscriber device 71 is connected to the metro subnetwork 3. The service subscriber device 71 is a device used by a subscriber who receives a service.

  FIG. 2 is a block diagram showing the configuration of the transfer system group control system processing device 15. The transfer system group control system processing device 15 operates as a SCE (Subnetwork Control Element) that controls a node (31) in the communication system 1 by performing route calculation in the metro subnetwork based on, for example, information given in advance. . Referring to the figure, the transfer system group control processing unit 15 includes a table creation unit 151 and an SCE function unit 153.

The table creation unit 151 performs route calculation in the metro subnetwork and creates a metro subnetwork routing table 1511. The table creation unit 151 creates a metro sub network flow identification table 1513 (first table).
FIG. 3 is a table summarizing the contents shown in the metro subnetwork routing table 1511. The metro sub-network routing table 1511 is a table showing a route for transferring a packet received by the transfer processing device (31) to another node in the metro sub-network 3. Referring to the figure, the sub-network routing table 1511 uses, for example, a cut-through routing method, and uses “node identification information”, “MPLS input label”, “address prefix”, “output IF”, and “MPLS”. Information indicating “output label” is included.

  The “node identification number” is a number for identifying each node (31) in the communication system 1. The “MPLS input label” is an input label in MPLS (Multiprotocol Label Switching), and the “MPLS output label” is an output label replaced at the time of transfer. The “output IF” is a number for identifying a communication interface that transfers a packet.

  FIG. 4 is a table summarizing the contents shown in the metro sub network flow identification table 1513. The flow identification table 1312 is a table stored with packet header information and network identification information indicating a network (SE subnetwork) in which a node that executes a predetermined service is accommodated. Referring to the figure, metro subnetwork flow identification table 1513 includes information (header information) indicating “source address”, “destination address”, “source port number”, “destination port number”, and “protocol identification number”. ), Information indicating “SE sub-network identification number” (network identification information), and information indicating “LSP number”.

  “Source address” and “source address” are the IP (Internet Protocol) address of the source and source of the packet, respectively. “Source port number” and “destination port number” are numbers for identifying services provided to the source and the source, respectively. The “protocol identification number” is a number for identifying a communication protocol to be used.

  The “SE subnetwork identification number” is a number for identifying the SE subnetwork (4) that accommodates the node (41) that provides the service indicated by the service identification number. The “LSP number” is a number for identifying an LSP (label Switched Path) established between the metro subnetwork and the SE subnetwork. The header information and the “LSP number” have a one-to-one correspondence.

  The SCE function unit 153 distributes the metro sub-network routing table 1511 and the metro sub-network flow identification table 1513 created by the table creation unit 151 to the node (31) of the metro sub-network.

  FIG. 5 is a block diagram showing the configuration of the transfer system control device 31. The transfer processing device 31 transfers the packet received from the service subscriber device 71 or the like to another node (41), and operates as an FE (Forwarding Element) in the communication system 1. Referring to the figure, the transfer processing device 31 includes a storage unit 311 and an FE function unit 313. The storage unit 311 stores a metro sub network routing table 3111 and a metro sub network flow identification table 3113. The metro sub-network routing table 3111 and the metro sub-network flow identification table 3113 are the same tables as the metro sub-network routing table 1511 and the metro sub-network flow identification table 1513.

  When receiving the packet, the transfer processing device 31 refers to the metro sub network flow identification table 3113 and reads the “LSP number” and “SE sub network identification number” corresponding to the header information of the received packet. The transfer processing device 31 establishes an LSP tunnel corresponding to the “LSP number” in the SE subnetwork indicated by the “SE subnetwork identification number”, and passes through the route indicated by the routing table 3111 in the metro subnetwork. The packet is transmitted to the gateway (41).

  The configuration of the transfer processing device 33 is the same as the configuration of the transfer processing device 31.

  The transfer processing device 33 is a node arranged at the edge on the service subscriber side that accommodates a plurality of service subscriber devices (71). A plurality of transfer processing devices 33 may be arranged. The transfer processing device 31 operates as a relay FE that bundles these transfer processing devices 33 and has a gateway function.

  The relay FE that bundles the transfer processing devices 33 and the gateway may be configured as separate nodes.

  FIG. 6 is a block diagram showing the configuration of the transfer system group control system processing device 16. The transfer system group control system processing device 16 includes a table creation unit 161 and an SCE function unit 163. The table creation unit 161 creates an SE sub-network routing table 1611 and an SE sub-network flow identification table 1513 (second table).

  The SE sub-network routing table 1611 is a table showing routes in the SE sub-network 4. The SE sub-network routing table 1611 uses, for example, a cut-through routing method.

  FIG. 7 is a table summarizing the contents shown in the SE sub-network flow identification table 1613. The SE sub-network flow identification table 1613 is a table in which header information is associated with “application identification number” and the like. Referring to the figure, SE sub-network flow identification table 1113g includes header information, information indicating “application identification number” (application identification information), information indicating “SE identification number” (node identification information), “ Information indicating “LSP number”.

  The “application identification number” is a number indicating an application for providing a service to a packet transmission source (subscriber), and the header information and the application identification number have a one-to-many correspondence.

  The SCE function unit 163 distributes the SE sub-network routing table 1611 created by the table creation unit 161 to the nodes (41, 43) in the SE sub-network, and transfers the SE sub-network flow identification table 1613 in the SE sub-network. Delivered to the system processor (41).

  FIG. 8 is a block diagram showing a configuration of the transfer system control device 41. Referring to the figure, the transfer system control device 41 includes a storage unit 411 and an FE function unit 413. The storage unit 411 stores an SE subnetwork routing table 4111 and an SE subnetwork flow identification table 4113. The SE sub-network routing table 4111 and the SE sub-network flow identification table 4113 are the same tables as the SE sub-network routing table 1611 and the SE sub-network flow identification table 1613.

  When the FE function unit 413 receives a packet, the FE function unit 413 refers to the IP header of the packet and determines whether an “application identification number” is given to the packet.

  If the “application identification number” is not assigned, the FE function unit 413 reads the “source address” from the L3 (Layer 3) and L4 (Layer 4) headers such as the TCP (Transmission Control Protocol) / IP header of the packet. The header information of “destination address”, “source port number”, “destination port number”, and “protocol identification number” is read, and all the “application identification numbers” corresponding to these are read from the flow identification table 4113.

  Then, as shown in FIG. 9, the FE function unit 413 adds information indicating the read “application identification number” to the extension header provided in the IP header. If there are a plurality of “application identification numbers”, the FE function unit 313 first assigns a number corresponding to the application to be processed last, and finally assigns a number corresponding to the application to be processed first. “App identification number” is given by “Last In First Out” method.

  The FE function unit 313 refers to the SE sub-network routing table 4111 and transfers the packet with the “application identification number” to the service processing apparatus (43).

  FIG. 10 is a block diagram illustrating a configuration of the service processing apparatus 43. Referring to the figure, the service processor 43 provides a service indicated by a “service identification number” and operates as an SE (Serving Element) in the communication system 1. Referring to the figure, the service processing unit 43 includes a storage unit 431 and an SE function unit 433.

  The storage unit 431 stores an SE subnetwork routing table 4311 and one or more applications 4313. The SE sub-network routing table 4311 has the same configuration as the SE sub-network routing table 3111.

  When receiving the packet, the SE function unit 433 reads the “application identification number” from the extension header of the packet, and executes the application indicated by the “application identification number”.

  For example, the application indicated by the “application identification number” is read from the stored application 4313 and executed.

  The SE function unit 433 deletes the “application identification number” corresponding to the executed application from the extension header. If the “application identification number” remains after the deletion, the SE function unit 433 executes the corresponding application.

  When all the applications have been executed, the SE function unit 433 refers to the metro sub-network routing table 3313, assigns an MPLS label, and transfers the packet to another node (41).

  FIG. 11 is a flowchart showing packet transfer processing of the transfer processing device (41). This packet transfer processing starts when the transfer processing device (41) receives a packet. Referring to the figure, the transfer processing device (41) refers to the IP header of the received packet and determines whether or not information indicating an application identification number is given to the extension header (step S1). .

  If the information indicating the application identification number is not given (step S1: NO), the transfer processing device (41) reads predetermined header information from the L3 and L4 headers of the packet, and the “application corresponding to the header information” "Identification number" is read (step S3).

  Then, the service processing apparatus (41) gives the read “application identification number” to the extension header (step S5).

  When the information indicating the application identification number is given (step S1: NO), or after step T5, the transfer processing device (41) refers to the SE sub-network routing table (4113) and transmits the packet. An MPLS label is assigned and transferred. After step S7, the transfer processing device (41) ends the packet transfer processing.

  FIG. 12 is a flowchart showing service processing executed by the service processing apparatus (43). This service processing starts when the service processing unit (43) receives a packet. Referring to the figure, the service processor (43) refers to the extension header and determines whether or not an “application identification number” is assigned (step T3).

  If the “application identification number” or the like is assigned (step T3: YES), the service processing apparatus (43) executes the application indicated by the “application identification number” (step T5). The service processing device (43) deletes the “application identification number” corresponding to the executed application from the extension header (step T7). After step T5, the service processor (43) returns to step T3.

  If the “application identification number” or the like is not assigned (step T3: NO), the service processing unit (43) refers to the SE sub-network routing table 4311 and assigns an MPLS label to the packet for transfer. (Step T9). After step T9, the service processor (31) ends the service process.

  In the present embodiment, only one SE sub-network connected to the metro sub-network is configured. However, a plurality of SE sub-networks connected to one metro sub-network may exist. A plurality of metro sub-networks may be connected to one SE sub-network.

  In this embodiment, the routing tables (1511, 1611, 3111, 4111, and 4311) are cut-through routing tables, but may be packet-by-packet routing tables.

  In this embodiment, one transfer system processing device 31 is provided, but a plurality of transfer system processing devices may be provided. The transfer processing device 31 may have the same function as the service processing device 33.

  In the present embodiment, the transfer processing device 41 is configured to give the “application identification number” to the extension header of the IP header, but may be configured to give the “application identification number” to another header such as an MPLS header. .

  In this embodiment, the transfer system device group control processing devices 15 and 16 create each table (1511, 1513, 1611, and 1613) and distribute it to each node (31, 41, and 43). . If the table is distributed from the control nodes (15 and 16) as described above, it is not necessary to update the table for each node even when the topology is changed. If the topology change is hardly considered or the number of nodes is small, the transfer system group control system processing devices 15 and 16 are not provided, and a necessary table is stored in advance in each node. It can also be.

  As described above, according to this embodiment, since the service processing node 43 is accommodated in a different network from the transfer processing device 31 (first transfer node), the application identification information is attached to the packet and transferred. Therefore, even when the service is changed, it is not necessary to change the routing table of the first forwarding node.

  In addition, the forwarding device group control processing device 16 (control node) uses the SE sub-network flow identification table 4113 (second table) in which the header information and the application identification information are associated with each other in the SE sub-network routing table 4111. Since it is created separately, there is no need to change the routing table of the second forwarding node unless the connection form is changed.

  Therefore, even if there is a change in service, route control becomes easy, and the communication system 1 can easily change the service.

Since the transfer processing device 31 transmits a packet with probability of an LSP tunnel in the SE subnetwork, it is not necessary to provide an extension header for a packet transmitted and received in the communication system 3, and no special specification change is required. As a result, the configuration of the communication system 1 that facilitates service changes can be easily introduced into an existing communication system.
(Second Embodiment)
A second embodiment of the present invention will be described with reference to the drawings. This embodiment differs from the first embodiment in that the transfer processing device 41 uses the SE sub-network flow identification table 4113 to control parameters set when executing an application.

  The configuration of the communication system 1 of the present embodiment is the same as that of the first embodiment.

  FIG. 13 is a table summarizing the contents of the SE sub-network flow identification table 1613a of this embodiment. Referring to the figure, the SE sub-network flow identification table 1613a includes information (parameter information) indicating “operation parameters” as shown by hatching in association with “application identification numbers” on a one-to-one basis. Different from the SE sub-network flow identification table 1613.

  The “operation parameter” is a value for the service processing device 43 to select an application processing pattern.

  The service processing device 43 holds a table in which “operation parameters” and processing patterns are associated with each application, and refers to this table to perform any output processing on the input packet. To decide.

  For example, when the service processor 43 provides a DSCP (Differentiated Services Code Point) value rewriting service, it determines which value to rewrite according to the value of the “operation parameter”.

  FIG. 14 is a diagram illustrating a packet format of the present embodiment. Referring to the figure, the transfer processing device (41) further assigns “parameter number” (shaded portion) together with “application identification number”.

  The service processing device (43) sets the parameter according to the “parameter number” given to the packet and executes the application.

  As described above, according to the present embodiment, the transfer processing device 41 can control the parameters set when executing the application using the SE sub-network flow identification table (1613a). The parameters can be changed according to the situation, and a more flexible service can be provided.

(Third embodiment)
A third embodiment of the present invention will be described with reference to the drawings. This embodiment is different from the second embodiment in that a plurality of service processing devices are provided.

  FIG. 15 is an overall view showing the configuration of the communication system 1b of the present embodiment. Referring to the figure, the communication system 1b has the same configuration as the communication system 1 except that it includes a service processing unit 45 (shaded portion) in addition to the service processing unit 43.

  The configuration of the service processor 45 is the same as that of the service processor 43.

  FIG. 16 is a table summarizing the contents of the SE sub-network flow identification table 1613b of this embodiment. Referring to this figure, SE sub-network flow identification table 1613b is different from SE sub-network flow identification table 1613a in that it further includes information (node identification information) indicating “SE identification number” as indicated by the hatched portion.

  The “SE identification number” is a number for identifying the service processing apparatus (43, 45) that executes the application indicated by the “application identification number”. The “SE identification number” and the “application identification number” have a one-to-many correspondence.

  FIG. 17 is a diagram illustrating a packet format according to the present embodiment. Referring to the figure, the transfer processing device (41) adds “SE identification number” (shaded portion) to the extension header of the packet in addition to “application identification number” and “operation parameter”.

  The transfer processing device (41) assigns the packets in the order of “SE identification number”, “application identification number”, and “operation parameter”. When there are a plurality of sets of “application identification numbers” and “operation parameters” corresponding to one “SE identification number”, the transfer processing device (41) is the last set (given first) at that node. Only the “SE identification number” is given to the other group, and only the “application identification number” and “operation parameter” are given to the other groups.

  If the node indicated by the “SE identification number” given to the packet is itself, the service processor (43, 45) executes the application.

  FIG. 18 is a flowchart illustrating service processing according to the present embodiment. Referring to the figure, when receiving the packet, the service processor (43, 45) determines whether or not the node indicated by the “SE identification number” given to the extension header of the packet is itself (see FIG. Step T1).

  When the node indicated by the “SE identification number” is itself (step T1: YES), the service processing devices (43, 45) execute step T3. When the node indicated by the “SE identification number” is not itself (step U1: NO), the service processing device (43, 45) executes step T9.

  Next, an example of the operation result of the communication system 1b will be described with reference to FIG. The figure shows a packet transfer path in the communication system 1b. In the figure, the direction of the white arrow indicates the direction in which the packet is transferred. Here, it is assumed that the communication system 1 f includes a service processing device 47 in addition to the service processing devices 43 and 45 in the SE sub-network 4.

  When receiving the packet from the service subscriber device 71, the transfer processing device 31 reads the “LSP number” corresponding to the packet from the metro subnetwork flow identification table 3513, establishes the LSP tunnel of the “LSP number”, and sets the SE. Transfer to the gateway (41) of the sub-network 4.

  The transfer processing device 41 refers to the SE subnetwork flow identification table 4113 and reads the “application identification number” and the like corresponding to the service identification number given to the packet received from the transfer processing device 31. The packet is transferred to the service processor 43 corresponding to the service identification number through the route indicated by the internal routing table 4111.

  The service processing devices 43, 45, and 47 execute the application indicated by the “application identification number” and transfer the packet to the next node (45, 47, and 41).

  The transfer processing device 41 transfers the packet received from the service processing device 47 to the transfer processing device 31.

  In the present embodiment, the communication system 1 is provided with two service processing devices. Of course, three or more service processing devices may be provided.

  As described above, according to the present embodiment, since a plurality of service processing devices (43, etc.) can be provided, the service processing load can be distributed to a plurality of nodes, and the service quality can be further improved. .

(Fourth embodiment)
A fourth embodiment will be described with reference to the drawings. This embodiment is different from the third embodiment in that a plurality of metro sub-networks are provided.

  FIG. 20 is an overall view showing the configuration of the communication system 1c of the present embodiment. Referring to the figure, the communication system 1c includes a node accommodated in the metro subnetwork 5 and a transfer system group control system processor 17 that controls the nodes in the metro subnetwork 5, as indicated by the hatched portion. The configuration is the same as that of the communication system 1b.

  In the metro subnetwork 5, transfer system processing devices 51 and 53 are accommodated and a service subscriber device 73 is connected as indicated by the hatched portion. The configuration of the service subscriber device 73 is the same as that of the service subscriber device 71. The transfer processing device 51 is connected to the transfer processing device 31. Transfer processing devices 31, 41, and 51 are connected to the inter-subnetwork integrated control device 11 (control node).

  The transfer processing devices 31 and 51 are nodes arranged at the edges of the metro sub-networks 3 and 5, and have a gateway function in addition to a packet transfer function.

FIG. 21 is a block diagram showing the configuration of the transfer system group control processing unit 15c of the present embodiment. Referring to the figure, the transfer system group control system processing device 15c is configured such that the table creation unit 151 exchanges route information with the transfer system group control system processing device 17.
The configuration is the same as that of the transfer system group control system processing apparatus 15 of the first embodiment except that the metro sub-network routing table 1512 is further created.

  FIG. 22 is a table summarizing the contents of the routing table 1512 between metro-sub networks. The metro sub-network routing table 1111 is a table showing routes between edge nodes (31, 51) of the respective metro sub-networks (3, 5). Referring to the figure, the metro sub-network routing table 1112 uses, for example, a packet-by-packet routing method, and indicates “node identification number”, “address prefix”, “output IF”, and “metric”. including.

  “Node identification information” is a number for identifying a node at the edge of each metro subnetwork. The “address prefix” is a part indicating a network address among IP addresses corresponding to packets. “Metric” is a number indicating the priority in packet transfer.

  The transfer device group control processing device 15c transmits the created metro subnetwork routing table 1512 to the node (31) having the gateway function of the metro subnetwork (3).

  The configuration of the transfer system group control system processor 17 is the same as that of the transfer system group control system processor 15c.

  FIG. 23 is a block diagram showing the configuration of the transfer processing device 31 of this embodiment. Referring to the figure, the transfer processing device 31 of this embodiment is the same as the configuration of the transfer processing device 31 of the third embodiment except that the storage unit 311 has a metro sub-network routing table 3512. . The metro sub-network routing table 3112 is the same table as the metro sub-network routing table 1512.

  When the transfer processing device 31 receives the packet, the metro sub network indicated by the “metro sub network identification number” corresponding to the header information with reference to the metro sub network flow identification table 3513 is a metro sub network in which it is accommodated. The packet is transferred with reference to the routing table 3111 in the metro subnetwork. When the metro sub network indicated by the “metro sub network identification number” is not the metro sub network in which it is stored, the transfer processing device 35 transfers the packet with reference to the routing table 3112 between the metro sub networks.

  In the present embodiment, the communication system 1 is provided with two metro sub-networks. Of course, three or more metro sub-networks may be provided.

  As described above, according to the present embodiment, a plurality of metro sub-networks can be provided and the service load can be distributed to a plurality of networks, so that service quality can be improved and service functions can be changed more easily.

(Fifth embodiment)
A fifth embodiment will be described with reference to the drawings. This embodiment is different from the fourth embodiment in that the load of the routing table creation process is distributed.

  FIG. 24 is an overall view showing the configuration of the communication system 1d of the present embodiment. Referring to the figure, the communication system 1d has the same configuration as the communication system 1c except that it further includes an inter-subnetwork integrated control device 11.

  The inter-subnetwork integrated control device 11 calculates the route between the metro subnetworks from the route information of the metrosubnetwork gateway notified from the transfer device group control system processing devices (15, 17), for example. It operates as an NCE (Network Control Element) that controls a node (31, etc.). The inter-subnetwork integrated control device 11 creates a routing table having the same contents as the metro-subnetwork routing table 1511, the metro-subnetwork flow identification table 1513, and the SE-subnetwork flow identification table 1613. , 16 and 17.

  As described above, according to the present embodiment, since the inter-subnetwork integrated control device 11 creates each table, the load on the transfer system device group control system processing devices 15, 16, and 17 is reduced. .

(Sixth embodiment)
A sixth embodiment will be described with reference to the drawings. This embodiment is different from the fifth embodiment in that information for creating the metro sub network flow identification table 1112 and the SE sub network flow identification table 1113 is stored in the database.

  FIG. 25 is an overall view showing the configuration of the communication system 1e of the present embodiment. Referring to the figure, the communication system 1e has the same configuration as the communication system 1d except that it further includes a database 13 (shaded portion) connected to the inter-subnetwork integrated control device 11.

  FIG. 26 is a block diagram showing the configuration of the database 13. Referring to the figure, the database 13 stores subscriber information 131, application management information 133, node identification information 135, and network connection information 137.

  FIG. 27 is a table in which the contents indicated by the subscriber information 131 are summarized. Referring to the figure, the subscriber information 131 includes header information such as “source address”, “destination address”, “source port number”, “destination port number”, and “protocol identification number”; And information indicating “service identification number”.

  The header information and the information indicating the “service identification number” have a one-to-one correspondence.

  The “service identification number” is a number for identifying a service provided to a packet transmission source (subscriber).

  FIG. 28 is a table in which the contents indicated by the application management information 133 are summarized. The application management information 113 is information related to an application for providing a predetermined service. Referring to the figure, the application management information 113 includes information indicating “service identification number”, “operation parameter”, and “application identification number”.

  “Service identification number” and “application identification number” have a one-to-many correspondence, and “application identification number” and “operation parameter” have a one-to-one correspondence.

  FIG. 29 is a table in which the contents indicated by the node identification information 135 are summarized. Referring to the figure, node identification information 115 includes information indicating “application identification number”, “metro sub network identification number”, and “SE identification number”.

  “SE identification number” and “application identification number” have a one-to-many correspondence, and “Metro sub network identification number” and “SE identification number” have a one-to-many correspondence.

  FIG. 30 is a table in which the contents indicated by the network identification information 137 are summarized. Referring to the figure, network identification information 117 includes information indicating “metro sub network identification number” and “SE sub network identification number”. The “SE sub network identification number” is a number for identifying the SE sub network connected to the “metro sub network identification”. “Metro sub network identification number” and “SE sub network identification number” have a one-to-many correspondence relationship.

  The inter-subnetwork integrated control device 11e of this embodiment creates a metro subnetwork flow identification table (1513) from the subscriber information 111, the node identification information 115, and the network identification information, and the subscriber information 111, the application management information 113, The SE subnetwork flow identification table (1613) is created from the node identification information 115.

  The inter-subnetwork integrated control device 11e then processes the metro subnetwork flow identification table (1513) in the transfer system group control system processing devices 15 and 17, and the SE subnetwork flow identification table (1613) in the transfer system group control system processing. Delivered to the device 16.

  As described above, according to the present embodiment, the integrated system control device 11e uses the database 13 to manage information for creating the flow identification tables (1513, 1613) in a plurality of tables. Therefore, the service change is further facilitated.

  Note that all or part of the flowcharts shown in FIGS. 11, 12, and 18 can also be realized by executing a computer program.

1 is an overall view showing a configuration of a communication system according to a first embodiment. It is a block diagram which shows the structure of the transfer type | system | group apparatus group control system processing apparatus of 1st Embodiment. 4 is a table summarizing the contents of a routing table in a metro subnetwork according to the first embodiment. 4 is a table summarizing the contents shown in the metro subnetwork flow identification table of the first embodiment. It is a block diagram which shows the structure of the transfer type | system | group processing apparatus of 1st Embodiment. It is a block diagram which shows the structure of the transfer type | system | group apparatus group control system processing apparatus of 1st Embodiment. It is the table | surface which put together the content which the SE subnetwork flow identification table of 1st Embodiment shows. It is a block diagram which shows the structure of the transfer type | system | group processing apparatus of 1st Embodiment. FIG. 3 is a diagram illustrating a packet format according to the first embodiment. It is a block diagram which shows the structure of the service type processing apparatus of 1st Embodiment. 3 is a flowchart illustrating packet transfer processing according to the first embodiment. 3 is a flowchart illustrating service processing according to the first embodiment. It is the table | surface which put together the content which the flow identification table of 2nd Embodiment shows. It is a figure which shows the format of the packet of 2nd Embodiment. It is a general view which shows the structure of the communication system of 3rd Embodiment. It is the table | surface which put together the content which the SE sub network flow identification table of 3rd Embodiment shows. It is a figure which shows the format of the packet of 3rd Embodiment. It is a flowchart which shows the service process of 3rd Embodiment. It is the figure which showed the transfer path | route of the packet in the communication system of 3rd Embodiment. It is a general view which shows the structure of the communication system of 4th Embodiment. It is a block diagram which shows the structure of the transfer type | system | group apparatus group control system processing apparatus of 4th Embodiment. It is the table | surface which put together the content which the routing table between metro subnetworks of 4th Embodiment shows. It is a block diagram which shows the structure of the transfer type | system | group processing apparatus of 4th Embodiment. It is a general view which shows the structure of the communication system of 5th Embodiment. It is a general view which shows the structure of the communication system of 6th Embodiment. It is a block diagram which shows the structure of the database of 6th Embodiment. It is the table | surface which put together the content which the subscriber information of 6th Embodiment shows. It is the table | surface which put together the content which the application management information of 6th Embodiment shows. It is the table | surface which put together the content which the node identification information of 6th Embodiment shows. It is the table | surface which put together the content which the network identification information of 8th Embodiment shows.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1, 1b, 1c, 1d, 1e Communication system 3, 5 Metro sub network 4 SE sub network 11 Inter sub network integrated control device 13 Database 15, 16, 17 Transfer processing unit group control processing unit 31, 41, 51, 53 Transfer processing unit 43, 45, 47, 53 Service processing unit 71, 73 Service subscriber unit 131 Subscriber information 133 Application management information 135 Node identification information 137 Network management information 151, 161 Table creation unit 153, 163 NCE function unit 311, 431 Storage unit 313, 413 FE function unit 433 SE function unit 3111, 3111 Metro sub network routing table 1511, 3512 Metro sub network routing table 1512, 3113 Metro sub network flow identification table 1511, 1611, 4111, 4311 SE Sub-network routing table 1613, 4311 SE sub-network flow identification table 4313 Application S1-S9, T1-T7 Step

Claims (2)

A communication system having a first forwarding node accommodated in a first network, a second forwarding node and a service processing node accommodated in a second network, and a control node,
The control node creates a first table in which packet header information is associated with application identification information indicating an application for providing a predetermined service, and the created first table is transferred to the second transfer A second table in which the header information of the packet distributed to the node and the network identification information indicating the second network in which the service processing node that processes the packet is associated is created, and the created second table 2 table to the first forwarding node,
The first forwarding node receives the second table from the control node, and when receiving a packet, reads and reads the network identification information corresponding to the header information of the packet from the received second table. Forwarding the packet to the second forwarding node accommodated in the second network indicated by the network identification information;
When the second forwarding node receives the first table from the control node and receives a packet, the second forwarding node reads and reads the application identification information corresponding to the header information of the packet from the received first table. Assigning the application identification information to the packet, transferring the packet with the application identification information to the service processing node via a predetermined route,
When the service processing node receives the packet transferred from the second transfer node, the service processing node executes an application indicated by the application identification information given to the received packet. In the control node
Creating a first table in which packet header information is associated with application identification information indicating an application for providing a predetermined service, and delivering the created first table to the second forwarding node;
Further creating a second table in which the header information of the packet is associated with the network identification information indicating the second network in which the service processing node for processing the packet is accommodated, and the created second table is Delivered to the first forwarding node,
In the first forwarding node accommodated in the first network,
When receiving the second table from the control node and receiving a packet, the network identification information corresponding to the header information of the packet is read from the received second table, and the read network identification information indicates the network identification information. Forwarding the packet to the second forwarding node accommodated in a second network;
In a second forwarding node accommodated in the second network,
Receiving the first table from the control node;
When receiving a packet, the application identification information corresponding to the header information of the packet is read from the received first table,
The read application identification information is attached to the packet, the packet with the application identification information is transferred to the service processing node through a predetermined route,
In the service processing node accommodated in the second network,
A communication method for executing an application indicated by the application identification information attached to the received packet when the packet transferred from the second transfer node is received.

Images