JP4659867B2 - Communication system, control 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.

To achieve the above object, the communication system of the present invention, across multiple networks, the header information of the packet, and the operating parameters of the application identification information and the application indicates an application for providing a predetermined service, the application network to create a node identification information for identifying the service processing node for executing an application indicated by the identification information, the flow identification table that associates network identification information for identifying a network to which the service processing node is received An inter-network control node, an intra-network control node that is arranged in each of the plurality of networks and that distributes the flow identification table created by the inter-network control node in the arranged network, and the intra- network control node The delivered flow identification table is recorded and a packet is recorded. Upon receiving the door, and the application identification information and the operating parameters corresponding to the header information of the received the packet and the node identification information and the network identification information read from the flow identification table, read the application identification information and the An operation parameter and the node identification information are assigned to the packet, and the network indicated by the network identification information read from the packet to which the application identification information and the operation parameter and the node identification information are assigned is accommodated. If the network indicated by the network identification information is transferred to a service processing node through a predetermined route in the network in which the network is contained and the read network identification information is not contained in the network, Transfer to a gateway of the network indicated by the network identification information via a predetermined route A transfer node, the when receiving the packet transferred from the transfer node, if the received the packet service processing node indicated by the node identifier added to its own, the application assigned to the packet received A service processing node that executes an application indicated by the identification information in accordance with the operation parameter given to the packet .

The control system of the present invention, over a plurality of networks to execute the header information of the packet, and the operating parameters of the application identification information and the application indicates an application for executing a predetermined service, the application indicated by the application identification information An inter-network control node that creates a flow identification table in which node identification information for identifying a service processing node and network identification information for identifying a network in which the service processing node is accommodated are associated ; The flow identification table arranged in each of the networks and created by the inter-network control node is added to the packet by adding the application identification information, the operation parameter, and the node identification information to the packet. It is delivered to the transfer node to be transferred in accordance with the Having an inner control node, the.

Communication method of the present invention is a control node over a plurality of networks, the header information of the packet, and the operating parameters of the application identification information and the application indicates an application for providing a predetermined service, the application indicated by the application identification information Creating a flow identification table in which node identification information for identifying a service processing node for executing a network and network identification information for identifying a network in which the service processing node is accommodated are associated with each other. in arranged reticuloendothelial control node, respectively, the flow identification table in which the inter-network control node is created, delivered in placed the network, the forwarding node, the flow distributed from the network in a control node Record the identification table and packet Upon receipt, and said and said application identification information and the operating parameter node identification information and the network identification information corresponding to the header information of the packet read from the flow identification table, read the application identification information and the operating parameters and the Node identification information is attached to the received packet, and the network indicated by the network identification information from which the packet having the application identification information, the operation parameter, and the node identification information is read is accommodated. If it is a network, it is transferred to a service processing node via a predetermined route in the network in which it is accommodated, and if the network indicated by the read network identification information is not the network in which it is accommodated, the network transferred in a predetermined path to a network gateway indicated by the identification information, before In the service processing node, wherein when receiving the packet from the forwarding node, if service processing node indicated by the node identifier added to the packet received itself, the application identification information given to the packet received Is executed according to the operation parameter given to the packet .

  According to the present invention, since the control node distributes the flow identification table in which the header information and the application identification information are associated with each other to the forwarding node, each forwarding node does not create the flow identification table, and the control node Can be managed centrally. Further, when there is a change in service, it is not necessary to change the flow identification table in the forwarding node, so that the service can be easily changed in the communication system.

(First embodiment)
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 FIG. 1, the communication system 1 includes a transfer system group control system processing device (control node) 15, a transfer system processing device (transfer node) 31, and a service system processing device (service processing node) 33. .

  The transfer processing device 31 and the service processing device 33 are accommodated in the metro subnetwork 3. Nodes (31 and 33) in the metro subnetwork 3 are connected to the transfer system group control system processor 15 via the metro subnetwork 3. In addition, a service subscriber device 71 is connected to the communication system 3. The service subscriber devices 71 and 73 are devices used by subscribers who receive services.

  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 unit 15 performs route calculation in the metro subnetwork based on, for example, information given in advance, and serves as an SCE (Subnetwork Control Element) that controls the nodes (31, 33) in the communication system 1. Operate. 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 flow identification table 1513.

  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 the service processing device (33). Referring to the figure, the metro 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, 33) 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 indicated by the flow identification table 1513. The flow identification table 1312 is a table stored with packet header information and application identification information indicating an application for executing a predetermined service. Referring to the figure, the flow identification table 1113 includes information (header information) indicating “source address”, “destination address”, “source port number”, “destination port number”, and “protocol identification number”. , Information indicating “application identification number” (application identification information).

  “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 “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 153 distributes the metro sub-network routing table 1511 created by the table creation unit 151 to each node (31 and 35) of the metro sub-network. Further, the SCE function unit 153 distributes the flow identification table 1512 to the transfer processing device (31).

  FIG. 5 is a block diagram showing a configuration of the transfer processing device 31. The forwarding processor 31 forwards packets to and from other nodes (33), 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 flow identification table 3113. The metro sub-network routing table 3111 and the flow identification table 3113 have the same configuration as the metro sub-network routing table 1511 and the flow identification table 1513, respectively.

  When the FE function unit 313 receives a packet, the FE function unit 313 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 313 uses 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 3113.

  Then, as shown in FIG. 6, the FE function unit 313 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 in-metro sub-network routing table 3112 and transfers the packet with the “application identification number” to the service processing apparatus (33).

  FIG. 7 is a block diagram illustrating a configuration of the service processing apparatus 33. Referring to the figure, the service processor 33 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 device 33 includes a storage unit 331 and an SE function unit 333.

  The storage unit 331 stores a metro sub-network routing table 3311 and one or more applications 3313. The metro sub-network routing table 3311 has the same configuration as the metro sub-network routing table 1511.

  When receiving a packet, the SE function unit 333 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 3313 and executed.

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

  When all the applications have been executed, the SE function unit 333 refers to the metro subnetwork routing table 3311, assigns an MPLS label, and transfers the packet to another node (for example, 31).

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

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

  Then, the service processing apparatus (31) 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 S5, the transfer processing device (31) refers to the metro sub-network routing table (3113), and MPLS is added to the packet. Label and transfer. After step S7, the transfer processing unit (31) ends the packet transfer process.

  FIG. 9 is a flowchart showing service processing executed by the service processing apparatus (33). This service processing starts when the service processing device (33) receives the packet. Referring to the figure, the service processor (33) 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 (33) executes the application indicated by the “application identification number” (step T5). The service processing device (33) deletes the “application identification number” corresponding to the executed application from the extension header (step T7). After step T5, the service processor (33) returns to step U3.

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

  In the present embodiment, the metro sub-network routing table 1511 is a cut-through routing system table, but may be a packet-by-packet routing system table.

  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 31 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 the present embodiment, the inter-subnetwork integrated control device 11 is configured to associate only “application identification number” with the header information in the flow identification table 1513, but the “application identification number” indicates the order in which the application is executed. It can also be stored in association.

  In the present embodiment, the service processing device 33 is configured to read and execute the stored application, but reads the application indicated by the “application identification number” from a storage device shared with other nodes, The application may be executed.

  In the present embodiment, the transfer system group control system processing device 15 is configured to distribute the flow identification table 1513 to each transfer system processing device. However, the transfer system group control system processing device 15 is not provided, and each transfer system 15 The flow identification table 1113 may be stored in advance in the system processing device.

  As described above, according to the present embodiment, the transfer system group control system processing device 15 (control node) uses the transfer system processing device 31 (transfer) in the flow identification table 1513 in which header information and application identification information are associated with each other. Therefore, each forwarding node does not need to create the flow identification table 1513, and the control node can centrally manage information on services. Further, when there is a change in service, it is not necessary to change the service change table in the forwarding node, so that the service can be easily changed in the communication system 1.

(Second Embodiment)
A second embodiment of the present invention will be described with reference to the drawings. This embodiment is different from the first embodiment in that the transfer system group control system processing device 15 uses the flow identification table 1513a to control the application processing pattern by the service processing device 33.

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

  FIG. 10 is a table summarizing the contents of the flow identification table 1513a of this embodiment. Referring to the figure, the flow identification table 1513a is associated with the “application identification number” on a one-to-one basis and includes information (parameter information) indicating “operation parameter” as indicated by the hatched portion. Different from 1513.

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

  The service processing device 33 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 33 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. 11 is a diagram showing a packet format of the present embodiment. Referring to the figure, the transfer processing device (31) further assigns “parameter number” (shaded portion) together with “application identification number”.

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

  As described above, according to the present embodiment, the transfer system group control system processing device 15 can control the parameters set when executing the application using the flow identification table 1513a. The parameters can be changed accordingly, 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. 12 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 34 (shaded portion) in addition to the service processing unit 33.

  The configuration of the service processing unit 34 is the same as that of the service processing unit 33.

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

  The “SE identification number” is a number for identifying the service processing device (33, 34) 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. 14 is a diagram illustrating a packet format of the present embodiment. Referring to the figure, in addition to “application identification number” and “operation parameter”, the transfer processing device (31) further adds “SE identification number” (shaded portion) to the extension header of the packet.

  The transfer processing device (31) 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 (31) is the last group to be executed (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 processing device (33, 34) executes the application.

  FIG. 15 is a flowchart showing service processing of the present embodiment. Referring to the figure, when receiving the packet, the service processor (33, 34) 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 “SE identification number” is itself (step T1: YES), the service processing devices (33, 34) execute step T3. When the node indicated by the “SE identification number” is not itself (step T1: NO), the service processing devices (33, 34) execute step T9.

  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 (33, 34) can be provided, the service processing load can be distributed to a plurality of nodes to further improve the service quality. it can.

(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. 16 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 transfer processing unit 35 accommodated in the metro subnetwork 3, a node accommodated in the metro subnetwork 5, and a transfer system group control system for controlling the nodes in the metro subnetwork 5. The configuration is the same as that of the communication system 1b except that the processing device 17 is further included.

  In the metro subnetwork 5, transfer system processing devices 51 and 53 and a service system processing device 53 are accommodated as indicated by the hatched portion. A service subscriber device 73 is connected to the metro subnetwork 5.

  The transfer processing devices 35 and 55 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. The functions of the nodes (31, 33, 35) accommodated in the metro sub network 3 are the same as the functions of the nodes (51, 53, 55) accommodated in the metro sub network 5.

  Whereas a plurality of transfer processing devices 31 are arranged at the edge of the service subscriber side that accommodates a plurality of service subscriber devices (71), the transfer processing device 35 has these transfer systems in addition to the gateway function. It also operates as a relay FE that bundles the processing devices (31).

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

  FIG. 17 is a block diagram showing the configuration of the transfer system group control processing unit 15c of this embodiment. Referring to the figure, the table creation unit 151 further creates a routing table 1512 between metro-sub networks by exchanging route information with the transfer system group control processing unit 17, and instead of the flow identification table 1513. In addition, it differs from the inter-subnetwork integrated control device 11 of the third embodiment in that a flow identification table 1113c is created.

  18 is a table summarizing the contents shown in the routing table 1512 between metro-sub networks. The metro sub-network routing table 1512 is a table showing routes between edge nodes (35, 55) of the respective metro sub-networks (3, 5). Referring to the figure, the metro sub-network routing table 1512 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 configuration of the transfer system group control system processor 17 is the same as that of the transfer system group control system processor 15c.

  The transfer device group control processing devices 15c and 17 transmit the created metro subnetwork routing table 1112 to the nodes (35 and 55) having the gateway function of each metro subnetwork (3 and 5).

  FIG. 19 is a table summarizing the contents of the flow identification table 1513c. Referring to the figure, the flow identification table 1513c is different from the flow identification table 1513b in that it further includes information (network identification information) indicating a “metro sub network identification number” as indicated by the hatched portion.

  The “metro sub network identification number” is a number for identifying the metro sub network in which the service processing devices (33, 53) are accommodated. “Metro sub network identification number” and “SE identification number” have a one-to-many correspondence.

  FIG. 20 is a block diagram showing the configuration of the transfer processing device 35. Referring to the figure, the transfer processing device 35 has a storage unit 351 and an FE function unit 353.

  The storage unit 351 stores a metro sub-network routing table 3511, a metro sub-network routing table 3512, and a flow identification table 3513.

  The metro sub-network routing table 3511, the metro sub-network routing table 3512, and the flow identification table 3513 are the same as the metro sub-network routing table 1511, the metro sub-network routing table 1512, and the flow identification table 1513c.

  If the “application identification number” or the like is not assigned to the received packet, the transfer processing device 35 refers to the flow identification table 3513 and assigns the “application identification number” or the like.

  When the metro sub network indicated by the “metro sub network identification number” corresponding to the “SE identification number” is the metro sub network in which it is accommodated, the transfer processing device 35 refers to the routing table 3511 in the metro sub network and transmits the packet. Forward. When the metro sub network indicated by the “metro sub network identification number” corresponding to the “SE identification number” is not the metro sub network in which it is accommodated, the transfer processing device 35 transfers the packet with reference to the routing table 3512 between metro sub networks. To do.

  FIG. 21 is a flowchart showing packet transfer processing of the transfer processing device 35 of this embodiment. Referring to the figure, this packet transfer process is the same as the packet transfer process executed by the transfer processor 31 except that steps S8 and S11 are executed.

  When the information indicating the application identification number is given (step S1: NO), or after step S5, the transfer processing device (35) sends the information to the metro subnetwork indicated by the “metrosubnetwork identification number” given to the packet. It is determined whether or not it is accommodated (step T8).

  If it is accommodated in the metro sub network indicated by the “metro sub network identification number” (step S8: YES), the transfer processing device 31 executes step T9. If the metro sub network indicated by the “metro sub network identification number” is not accommodated (step S8: NO), the transfer processing device 31 uses a protocol such as ARP (Address Resolution Protocol) or OPSF (Open Shortest Path First). The packet is transferred to the gateway (55) by referring to the metro sub-network routing table 3512 (step T9).

  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 table creation processing is distributed.

  FIG. 22 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 (control node). However, the inter-subnetwork integrated control device 11 creates a routing table in each metro subnetwork instead of the transfer device group control system processing devices 15d and 17d.

  The inter-subnetwork integrated control apparatus 11 operates as an NCE (Network Control Element) that performs route calculation in the metro subnetworks 5 and 7 and controls the transfer system group control system processing apparatuses 15d and 17d. The inter-subnetwork integrated control device 11 creates a metro subnetwork routing table for each of the metro subnetworks 3 and 5, and distributes it to the transfer system group control system processing devices 15d and 17d.

  The inter-subnetwork integrated control apparatus 11 further creates a flow identification table (1513) and distributes it to the transfer system group control system processing apparatuses 15d and 17d.

  As described above, according to the present embodiment, the inter-subnetwork integrated control device 11 shares the creation and distribution of the table, so that the processing load on the inter-subnetwork integrated control device 11 can be 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 flow identification table 1113 is stored in a database.

  FIG. 23 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. 24 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, and node identification information 135.

  FIG. 25 is a table summarizing the contents indicated by the subscriber information 131. 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. 26 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. 27 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.

  The inter-subnetwork integrated control apparatus 11 reads the subscriber information 131, the application management information 133, and the node identification information 135 from the database 13, and creates a flow identification table (1513) from these information.

  As described above, according to the present embodiment, the inter-subnetwork integrated control apparatus 11 uses the database 13 to manage information for creating the flow identification table (1513) by dividing it into a plurality of tables. Therefore, the service change is further facilitated.

  Note that all or part of the flowcharts shown in FIGS. 8, 9, 15, and 21 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 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. 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 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 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 the table | surface which put together the content which the flow identification table 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 flowchart which shows the packet transfer process 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.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1, 1b, 1c Communication system 3, 5 Metro subnetwork 11 Inter-subnetwork integrated control apparatus 13 Database 15, 15c, 15d, 16, 17 Transfer system group control system processing apparatus 31, 35, 51, 55 Transfer system processing apparatus 33 , 34, 53 Service processing unit 71, 73 Service subscriber unit 131 Subscriber information 133 Application management information 135 Node identification information 151 Table creation unit 153 NCE function unit 311, 331 Storage unit 313, 333 FE function unit 333 SE function unit 1511, 3111, 3311, 3511 Metro sub-network routing table 1512, 3512 Metro sub-network routing table 1513, 3113, 1513a, 1513b, 1513c, 3513 Flow identification table 3313 Applications S1-S9, T1 ~ T7 step

Claims (5)

To identify packet header information, application identification information indicating an application for providing a predetermined service , operation parameters of the application, and a service processing node that executes the application indicated by the application identification information, across a plurality of networks An inter-network control node that creates a flow identification table in which the node identification information is associated with the network identification information for identifying the network in which the service processing node is accommodated , and
Disposed in each of said plurality of networks, the flow identification table the networks control node is created, and the network in a control node for distributing in deployed the network,
When the flow identification table distributed from the intra-network control node is recorded and a packet is received, the application identification information corresponding to the received header information of the packet, the operation parameter, the node identification information, and the network identification information DOO read from the flow identification table, reads the said application identification information and the operating parameters and the node identification information given to the packet was granted and the application identification information and the operating parameters and the node identification information the If the network indicated by the read network identification information is a network in which the packet is contained, the packet is transferred to a service processing node through a predetermined route in the network in which the packet is contained, and the read network identification The network indicated by the information must be the network in which it is housed. , A transfer node for transfer to the network gateway in a predetermined path indicated by the net-identification information,
When the packet transferred from the forwarding node is received , if the service processing node indicated by the node identification information given to the received packet is itself, the application identification information given to the received packet is indicated A service processing node for executing an application in accordance with the operation parameter given to the packet ;
A communication system. The inter-network control node further creates a routing table indicating a predetermined route,
The intra-network control node further distributes the routing table created by the inter-network control node to the forwarding node,
The communication system according to claim 1 , wherein the forwarding node records the routing table distributed from the control node and forwards the packet along the route indicated by the routing table. To identify packet header information, application identification information indicating an application for executing a predetermined service , operation parameters of the application, and a service processing node executing the application indicated by the application identification information, across a plurality of networks An inter-network control node that creates a flow identification table in which the node identification information is associated with the network identification information for identifying the network in which the service processing node is accommodated , and
The flow identification table arranged in each of the plurality of networks and created by the inter-network control node , the application identification information, the operation parameter, and the node identification information are added to the packet , and the packet is An in-network control node that delivers to a forwarding node that forwards according to network identification information ;
Having a control system . In control nodes across multiple networks ,
Packet header information, application identification information indicating an application for providing a predetermined service , operation parameters of the application, node identification information for identifying a service processing node that executes the application indicated by the application identification information, and Creating a flow identification table in association with network identification information for identifying the network in which the service processing node is accommodated ,
In the network control node arranged in each of the plurality of networks,
Distributing the flow identification table created by the inter-network control node within the arranged network ,
In the forwarding node:
Record the flow identification table distributed from the in- network control node,
When receiving a packet, the application identification information corresponding to the packet header information, the operation parameter, the node identification information, and the network identification information are read from the flow identification table,
The read application identification information and the operation parameter and the node identification information are attached to the received packet,
If the network indicated by the network identification information that has read the packet to which the application identification information, the operation parameter, and the node identification information are read is a network that accommodates itself, the network that accommodates itself If the network indicated by the read network identification information is not the network in which it is accommodated, it is transferred to the gateway of the network indicated by the network identification information via the predetermined route. And
In the service processing node,
When receiving the packet from the forwarding node , if the service processing node indicated by the node identification information attached to the received packet is itself, the application indicated by the application identification information assigned to the received packet is : A communication method executed according to the operation parameter given to the packet . In the inter-network control node,
Create another routing table showing the given route,
In the network control node,
Further distributing the routing table created by the inter-network control node to the forwarding node;
In the forwarding node,
5. The communication method according to claim 4 , wherein the routing table distributed from the intra-network control node is recorded, and the packet is transferred along the route indicated by the routing table.

Images