WO2015045575A1 - Network system, management method, and network manager - Google Patents

Abstract

Data that is transmitted and received by a terminal is transferred via a path between a first edge node and a second edge node, the terminal takes any of a plurality of terminal states including a first state in which the terminal transmits and receives only control data, and a second state in which the terminal transmits and receives data other than the control data, and a network manager has band information including a band secured for the terminal to communicate via the path in each of the terminal states, acquires information relating to the terminal state of the terminal from a management server, calculates the band secured for the terminal to communicate via the path on the basis of the number of terminals in the first state and the number of terminals in the second state, which are indicated by the information acquired from the management server, and the band information, and sets the calculated band in the first edge node and the second edge node such that the data that is transmitted and received by the terminal is transferred in the calculated band.

Description

Network system, management method, and network manager Import by reference

This application claims the priority of Japanese Patent Application No. 2013-198406, which was filed on September 25, 2013, and is incorporated herein by reference.

The present invention relates to a network system.

With the spread of high-speed wireless access services such as LTE (Long Term Evolution), the number of smartphone users is rapidly increasing. Along with this, the need for wireless data communication has increased dramatically. Against this background, wireless communication is also required to have stable communication quality equivalent to wired communication.

Current mobile backhauls are often built using ATM (Asynchronous Transfer Mode) or Ethernet. A mobile backhaul is a network for wireless communication connecting a gateway from a base station. In a mobile network, a base station accommodates a mobile terminal, and a gateway performs authentication of a user who uses the mobile terminal and control of a handover.

A network in which a communication path between a network edge node (BS-NWE node) accommodating a base station and a network edge node (GW-NWE node) accommodating a gateway is set in advance in the current mobile backhaul There is. At this time, the communication path has the following problems.

For example, when the bandwidth of the communication path is set to a fixed bandwidth and the number of terminals accommodated by the BS-NWE node is different among the BS-NWE nodes, the bandwidth of the communication path allocated to each BS-NWE node is constant. . For this reason, even in the case where there is a vacancy in the entire network resource, the communication in the BS-NWE node with a large number of terminals has been slow.

Also, for example, when the bandwidth of the communication path is set to best effort, the node hop that passes through from the edge node on the base station side to the service accommodation edge (edge node that accommodates all servers that provide services) The larger the number of communications, the higher the probability that data will be discarded, and the communications will be slower.

As described above, in the conventional mobile backhaul, the resources could not be fully utilized even if the network resources are available.

As a technique for improving the utilization efficiency of network resources, a network control system technique has been proposed (see, for example, Patent Document 1). In Patent Document 1, a plurality of servers that accommodate a plurality of terminals, a plurality of host computers, and a transmission rate adjustment server that adjusts the amount of data that the server transmits to the host computers are connected via a network. The rate adjustment server collects the number of transactions from each server from each server, and the transmission rate adjustment server notifies each server of the transmission rate for transmitting data to the network according to the collected number of transactions. Thus, a network control system for reducing network congestion is disclosed.
Patent Document 1: Japanese Patent Application Laid-Open No. 2009-206874

The technology of Patent Document 1 cannot improve the network utilization efficiency in consideration of the route through which data passes in the network. Further, when Patent Document 1 is used, if a terminal that has not output a transaction at the time when the transmission rate is set starts outputting a transaction after setting the transmission rate, the bandwidth of the newly generated transaction is secured. As a result, the transmission rate is insufficient.

The first object of the present invention is to allocate an optimum bandwidth to a communication path through which data passes in a network in view of the problems of the prior art as described above. Furthermore, when a certain relay node contains too many communication paths and congestion occurs, a network system is provided that improves the overall network utilization efficiency by resetting the communication path to a relay node with a low utilization rate. It is to be.

Furthermore, a second object of the present invention is to provide a network system that can secure a bandwidth of a path in consideration of potential users (users who are not performing data communication but who are likely to perform data communication in the future). That is.

According to a representative aspect of the present invention, a network system for transferring data transmitted and received by a terminal, the network system including a first edge node that accommodates the terminal and a terminal that holds information on the terminal A management server; a network manager connected to the terminal management server; and a second edge node connected to the first edge node, wherein data transmitted and received by the terminal is the first edge node And the terminal is transferred via a path between the second edge nodes, and the terminal is in a first state in which the terminal transmits / receives only control data, and in which the terminal transmits / receives data other than the control data. 2, and the network manager includes a processor and a memory, and the terminal In each of the states, the terminal has band information including a band reserved for communication via the path, and acquires terminal state information of the terminal from the terminal management server, and the terminal management server Based on the number of terminals in the first state and the number of terminals in the second state indicated by the information acquired from the information and the bandwidth information, the terminal is secured for communication via a path. The first edge node and the second edge node are set so that data transmitted / received by the terminal is transferred according to the calculated bandwidth.

According to an embodiment of the present invention, an optimal bandwidth can be allocated to a route through which data passes in the network.

Issues, configurations, and effects other than those described above will be clarified by the following description of the embodiments.

1 is an explanatory diagram illustrating a network system according to a first embodiment. FIG. 3 is a block diagram illustrating a physical configuration example of a network resource volume manager according to the first embodiment. It is explanatory drawing which shows NW topology DB of the present Example 1. It is explanatory drawing which shows NW resource management DB of the present Example 1. It is explanatory drawing which shows user number DB classified by service area of the present Example 1. FIG. It is explanatory drawing which shows LSP DB of the present Example 1. It is explanatory drawing which shows band coefficient DB of the present Example 1. FIG. It is a block diagram which shows the example of the functional block of the edge node of the present Example 1. FIG. It is explanatory drawing which shows the LSP management table of the present Example 1. It is explanatory drawing which shows the LSP bandwidth management table of the present Example 1. 3 is a flowchart illustrating processing for determining a bandwidth of a communication path and processing for setting a path of the communication path according to the first embodiment. It is a flowchart which shows the process for updating the zone | band of bandwidth coefficient DB of the present Example 1. It is explanatory drawing which shows the network system of the present Example 2. It is explanatory drawing which shows heavy user management DB of the present Example 2. It is explanatory drawing which shows LSP DB of the present Example 2. It is explanatory drawing which shows the heavy user identification table of the present Example 2. It is a flowchart which shows the process set to an edge node regarding the heavy user of the present Example 2.

Hereinafter, embodiments will be described in detail with reference to the drawings.

The mobile backhaul in the present embodiment uses Multi Protocol Label Switching-Transport Profile (MPLS-TP) as a network communication protocol. However, any protocol other than MPLS-TP can be used as long as the route between the edge nodes is set in advance in a packet whose attributes such as flow, destination, or transmission source are predetermined attributes. May be.

FIG. 1 is an explanatory diagram illustrating a network system according to the first embodiment.

The network system of the first embodiment includes at least one mobile backhaul 10, a plurality of service areas 11 (11-1 to 11-3), a network resource volume manager 1, a mobility management entity (MME) 7, an ESPGW 6, and a maintenance A person terminal 12 is included.

The mobile backhaul 10 is a system for accommodating communication by at least one company and optimally using network resources. The mobile backhaul 10 includes a plurality of BS-NWE (Base Station Network Edge) nodes 2 (2-1 to 2-4), a plurality of relay nodes 4 (4-1 to 4-5), and at least one GW-NWE. (Gateway Network Edge) node 3 and NMS (Network Management System) 5.

The BS-NWE node 2 is an edge node in the mobile backhaul 10 and is a network device that accommodates packets transmitted from the service area 11. The relay node 4 is a network device and transfers communication between the BS-NWE node 2 and the GW-NWE node 3. The GW-NWE node 3 is an edge node in the mobile backhaul 10 and is a network device connected to the MME 7 and the ESPGW 6.

The NMS 5 is a computer that sets the communication path and the bandwidth of the communication path in the BS-NWE node 2, the GW-NWE node 3, and the relay node 4. The NMS 5 shown in FIG. 1 is included in the mobile backhaul 10, but the network resource volume manager 1 may have the functions of the NMS 5 of this embodiment.

Here, the communication path in the first embodiment indicates a logical route used in the mobile backhaul 10 in order to transfer a packet having a predetermined attribute. A route in the mobile backhaul 10 is assigned to the communication path. The communication path in this embodiment indicates a logical path. The route in the present embodiment indicates the network device through which data actually passes and the order in which the data passes.

The network resource volume manager 1 in the first embodiment changes a network device through which a packet having a predetermined attribute passes by changing a route assigned to a communication path.

One BS-NWE node 2 is connected to one base station 8. The base station 8 communicates with the mobile terminal 9 by radio.

The service area 11 is an area where the base station 8 and the mobile terminal 9 can directly communicate. The mobile terminal 9 of the present embodiment is included in any service area 11. The base station 8 provides a mobile phone service to the mobile terminal 9.

The ESPGW 6 is a gateway that controls the authentication of the mobile terminal 9 and the bandwidth of each mobile terminal 9. The MME 7 controls the handover of the mobile terminal 9 between the plurality of service areas 11. The ESPGW 6 and the MME 7 are computers that hold information related to the mobile terminal 9, and are terminal management servers in the present embodiment. Further, the ESPGW 6 and the MME 7 have a gateway function.

The maintenance person terminal 12 transmits the input value from the maintenance person to the network resource volume manager 1.

The network resource volume manager 1 periodically collects information on the number of mobile terminals 9 included in each service area 11 from the MME 7 and the ESPGW 6. Then, the network resource volume manager 1 calculates a bandwidth for each communication path based on the collected information, and assigns a route to the communication path and sets a bandwidth to the communication path according to the calculated bandwidth. Instruct NMS5.

For convenience of explanation, the BS-NWE node 2 and the GW-NWE node 3 of this embodiment are identified by different names, but the BS-NWE node 2 and the GW-NWE node 3 have the same function. Information collected by the network resource volume manager 1 from the MME 7 and ESPGW 6 and information set in the NMS 5 will be described later.

FIG. 1 shows a case where there is one company that uses the mobile backhaul 10, but a plurality of companies may share one mobile backhaul 10. In this case, the MME 7, ESPGW 6, and service area 11 for each provider may be connected to the mobile backhaul 10. In the mobile backhaul 10, a communication path between the BS-NWE node 2 and the GW-NWE node 3 may be set for each carrier. The MME 7, ESPGW 6, and service area 11 for each provider may be implemented by physically different devices, or may be implemented by logically different devices.

FIG. 2 is a block diagram illustrating a physical configuration example of the network resource volume manager 1 according to the first embodiment.

The network resource volume manager 1 is a computer configured for the purpose of improving the use efficiency of network resources in the mobile backhaul 10 of this embodiment. The network resource volume manager 1 includes a CPU 21, a network management IF 22, a maintenance person terminal connection IF 23, a bandwidth coefficient DB 24, an NW topology DB 25, an NW resource management DB 26, a service area user count DB 27, and an LSP DB 28. The network resource volume manager 1 has a memory (not shown).

The CPU 21 is an arithmetic device that implements the function of the network resource volume manager 1 by executing a program or the like stored in the memory. The CPU 21 may be any processor other than the CPU as long as it is an arithmetic device, and may be configured by one or a plurality of processors. The CPU 21 may implement the functions of the bandwidth determination unit 211 and the bandwidth instruction unit 212 by executing a program.

The bandwidth determination unit 211 has a function of determining the bandwidth of the communication path in the mobile backhaul 10 according to the number of mobile terminals 9 included in the service area 11. In addition, the bandwidth determination unit 211 determines a network device through which the communication path passes as necessary, and thereby assigns a route to the communication path.

The band instruction unit 212 has a function of instructing the NMS 5 to set the band or route determined by the band determination unit 211 in each network device of the mobile backhaul 10.

The bandwidth determination unit 211 and the bandwidth instruction unit 212 may be implemented by a single program, or may each be implemented by a plurality of programs. In addition, the CPU 21 may incorporate one or a plurality of physical devices that implement the bandwidth determination unit 211 and the bandwidth instruction unit 212.

The network management IF 22 is an interface for connecting to the NMS 5, MME 7 and ESPGW 6. The maintenance person terminal connection IF 23 is an interface for connecting to the maintenance person terminal 12.

The bandwidth coefficient DB 24, the NW topology DB 25, the NW resource management DB 26, the service area user count DB 27, and the LSP DB 28 are connected via the CPU 21 and the database access path.

FIG. 3 is an explanatory diagram illustrating the NW topology DB 25 according to the first embodiment.

The NW topology DB 25 is set in advance in the network resource volume manager 1 and indicates the network topology of all networks managed by the network resource volume manager 1. In the first embodiment, since the network resource volume manager 1 manages the mobile backhaul 10, the NW topology DB 25 shown in FIG. 3 shows the network topology of the mobile backhaul 10. The contents shown in the NW topology DB 25 in FIG. 3 will be described below.

BS-NWE nodes 2-1 to 2-4 are connected to service areas 11-1 to 11-4, respectively. BS-NWE nodes 2-1 to 2-4 are connected to relay nodes 4-1 to 4-4. The GW-NWE node 3-1 is connected to the relay node 4-5 and the service area 11-5. The relay nodes 4-1 to 4-5 are connected in a ring shape.

In this embodiment, the BS-NWE nodes 2-1 to 2-4 are assigned E1 to E4 as identifiers, respectively, and the GW-NWE node 3-1 is assigned E5 as an identifier. Further, S1 to S5 are assigned to the relay nodes 4-1 to 4-5 as identifiers. Service areas 11-1 to 11-5 are assigned identifiers A1 to A5.

Note that the NW topology DB 25 may be generated based on information held by the NMS 5. Further, for example, the program or physical device included in the network resource volume manager 1 may collect the information from the NMS 5 periodically to generate the NW topology DB 25.

FIG. 4 is an explanatory diagram illustrating the NW resource management DB 26 according to the first embodiment.

The NW resource management DB 26 indicates a bandwidth used in a link between two network devices. The NW resource management DB 26 indicates a link between each network device of the mobile backhaul 10 managed by the network resource volume manager 1.

The NW resource management DB 26 includes a link ID 51, a band 52, and a remaining band 53. The link ID 51 indicates an identifier that identifies a link between network devices. A link ID 51 shown in FIG. 4 indicates an identifier generated by the identifier and hyphen of each network device.

Band 52 indicates a band used in the link indicated by the link ID 51. The remaining bandwidth 53 indicates a bandwidth that is not used by the set communication path in the link indicated by the link ID 51. That is, the remaining bandwidth 53 indicates a bandwidth that can be used by a newly set communication path.

The NW resource management DB 26 may be set in advance by a maintenance person via the maintenance person terminal 12. For example, the NW resource management DB 26 may be generated by a program or a physical device included in the network resource volume manager 1 periodically collecting information from the NMS 5.

FIG. 5 is an explanatory diagram showing the service area user count DB 27 according to the first embodiment.

The service area user count DB 27 indicates the number and status of the mobile terminals 9 included in the service area 11 for each business operator. Here, the states of the mobile terminal 9 in FIG. 5 are a connected state and an idle state. However, the state of the mobile terminal 9 in the present embodiment is a state where it is necessary to change the band necessary for communication in the mobile backhaul 10 according to the frequency, amount, content, purpose, etc. of communication of the mobile terminal 9. Any state may be used.

The connection state in the present embodiment is a state in which the mobile terminal 9 transmits / receives data other than control data (hereinafter, actual data) under a predetermined condition. The predetermined condition is, for example, transmission / reception exceeding a predetermined frequency. The connection state includes a state in which the mobile terminal 9 can immediately transmit and receive actual data.

Actual data in this embodiment is data for directly providing a service desired by the user using the mobile terminal 9 to the mobile terminal 9. Further, the control data in the present embodiment is data for the mobile terminal 9 to communicate. The control data in the present embodiment includes, for example, data for establishing or disconnecting communication of the mobile terminal 9 or data for reporting the communication status of the mobile terminal 9.

The idle state in the present embodiment is a state where the mobile terminal 9 is not transmitting / receiving actual data according to a predetermined condition, for example, a state where actual data is not transmitted / received for a predetermined time. The idle state includes a state in which only control data is transmitted / received.

State transitions in the present embodiment such as the above-described connection state and idle state are standardized by 3GPP. In general, the mobile terminal 9 in the connected state transmits and receives more data than the mobile terminal 9 in the idle state.

5 includes an area ID 61, a provider ID 62, a node ID 63, a connection state user number 64, and an idle state user number 65. The area ID 61 indicates an identifier of the service area 11. The business operator ID 62 indicates an identifier of the business operator.

The node ID 63 indicates the BS-NWE node 2 connected to the base station 8 in the service area 11 indicated by the area ID 61. The node ID 63 shown in FIG. 5 indicates one BS-NWE node 2, but the node ID 63 in this embodiment is the BS-NWE node 2 used as the main server and the BS of the sub-server used when the main server fails. -NWE node 2 may be indicated.

The number 64 of connected users indicates the number of connected mobile terminals 9 among the mobile terminals 9 included in the service area 11 indicated by the area ID 61. The number of idle state users 65 indicates the number of mobile terminals 9 in the idle state among the mobile terminals 9 included in the service area 11 indicated by the area ID 61.

The service area user count DB 27 is generated based on information about the mobile terminal 9 for each service area 11 collected from the MME 7 or ESPGW 6 by the network resource volume manager 1. The bandwidth determination unit 211 accurately grasps the number of users and the state of each service area 11 by holding the service area user count DB 27, and performs communication between the BS-NWE node 2 and the GW-NWE node 3. It is possible to calculate a communication band necessary for the path.

FIG. 6 is an explanatory diagram showing the LSP DB 28 according to the first embodiment.

The LSP DB 28 holds a route and a band set in a communication path (LSP: Label Switched Path) between the BS-NWE node 2 and the GW-NWE node 3. The LSP DB 28 includes an area ID 71, a provider ID 72, an LSP ID 73, an edge node ID 74, a relay node ID 75, an edge node ID 76, and a set bandwidth Bw0 (77).

Area ID 71 indicates an identifier of the service area 11. The business ID 72 indicates an identifier of the business. The LSP ID 73 indicates a communication path (LSP) identifier. In the following first embodiment, since all communication paths are defined by LSP, the communication path in the first embodiment is referred to as LSP.

Edge node ID 74 indicates the identifier of BS-NWE node 2 or GW-NWE node 3 that is the start point of the LSP. The relay node ID 75 indicates the identifier of the relay node 4 through which the LSP passes. The relay node ID 75 illustrated in FIG. 6 indicates the order in which the LSP passes through the relay node 4. The edge node ID 76 indicates the identifier of the BS-NWE node 2 or GW-NWE node 3 that is the end point of the LSP. The set bandwidth Bw0 (77) indicates a bandwidth set in the LSP indicated by the LSP ID 73.

FIG. 7 is an explanatory diagram showing the band coefficient DB 24 of the first embodiment.

The bandwidth coefficient DB 24 indicates a bandwidth reserved for one mobile terminal 9 in the LSP, and indicates the bandwidth of the mobile terminal 9 in each state. Further, the bandwidth coefficient DB 24 illustrated in FIG. 7 indicates a bandwidth for each business operator to which the mobile terminal 9 belongs. The band coefficient DB 24 includes a provider ID 81, a band α82, and a band β83.

The provider ID 81 indicates the identifier of the provider. A band α82 indicates a band secured in the mobile terminal 9 whose state is the connected state. A band β83 indicates a band reserved for the mobile terminal 9 whose state is the idle state.

The band coefficient DB 24 shown in FIG. 7 holds only the bands according to the two states of the mobile terminal 9, but holds three or more bands when three or more states of the mobile terminal 9 are defined. Also good.

In this embodiment, the band α is a band per mobile terminal 9 in the connected state, and the band β is a band per mobile terminal 9 in the idle state. These values can be set appropriately for each business unit, so that the service grade among business operators can be varied.

Advantages of setting the band α 82 and the band 83 for each provider when a plurality of providers use the mobile backhaul 10 are shown below. For example, the operator A may provide a mobile data communication service using the mobile backhaul 10 in advance of other companies by setting the band α 82 to be 10 Mbit / s and the band β 83 to be 2 Mbit / s.

In this case, when the operator B newly starts a mobile data communication service using the mobile backhaul 10 with the setting that the band α82 is 20 Mbit / s and the band β83 is 4 Mbit / s, The operator B has a larger band to be secured per mobile terminal 9 than the operator A.

For this reason, the business operator B can increase the satisfaction level of the mobile terminal 9 belonging to the business operator B more than the business operator A. Furthermore, by setting in this way, the business operator C who owns the mobile backhaul 10 can collect more usage charges than the business operator A from the business operator B in return for the above setting.

The band α82 and the band β83 may be set in advance by a maintenance person. In addition, the band determination unit 211 may determine the band α82 and the band β83 using the connection state user number 64 and the idle state user number 65 acquired a predetermined number of times for a predetermined period. Details of the method of determining the band α82 and the band β83 will be described later.

When only one company uses the mobile backhaul 10, the service ID 62 of the service area user count DB 27, the service ID 72 of the LSP DB 28, and the service ID 81 of the bandwidth coefficient DB 24 are not required. .

FIG. 8 is a block diagram illustrating an example of functional blocks of the edge node according to the first embodiment.

The BS-NWE node 2 and the GW-NWE node 3 of this embodiment have the same functional blocks shown in FIG. Hereinafter, the BS-NWE node 2 and the GW-NWE node 3 are collectively referred to as edge nodes.

The edge node includes at least one access NWIF card 31 (31-1 to 31-m, m is an arbitrary positive number), a switch (SW) 32, and at least one relay NWIF card 33 (33-1 to 33-n, n is an arbitrary positive number) and a device control unit 34.

The access NWIF card 31 is an NW interface for connecting to the base station 8, the MME 7, or the ESPGW 6. The relay NWIF card 33 is an NW interface for connecting to the relay node 4 or another edge node.

SW32 switches the packet transmission destination between the NWIF cards. The device control unit 34 is connected to the NMS 5. The device control unit 34 sets each NWIF card according to an instruction from the NMS 5, monitors the state of each functional block included in the edge node, and notifies the NMS 5 of the monitoring result according to the instruction from the NMS 5.

The access NWIF card 31 includes an LSP management table 29, an LSP bandwidth management table 30, an NW reception circuit 35, a user flow specifying unit 36, an SW transmission circuit 37, an SW reception circuit 38, an MPLS termination circuit 39, and an NW transmission circuit 40. Have.

The NW receiving circuit 35 receives a packet from a device such as the base station 8, MME 7, or ESPGW 6.

The user flow specifying unit 36 searches the LSP management table 29 and the LSP bandwidth management table 30 based on the header information of the received packet. Then, as a result of the search, the user flow specifying unit 36 determines an LSP for encapsulating the received packet, and further encapsulates the received packet. In addition, the user flow specifying unit 36 controls the bandwidth of the packet.

SW transmission circuit 37 transfers the received packet to SW32. The SW receiving circuit 38 receives a packet from the SW 32. The MPLS termination circuit 39 deletes the MPLS header from the received packet. The NW transmission circuit 40 transmits a packet to a device such as the base station 8, the MME 7, or the ESPGW 6.

The relay NWIF card 33 includes an NW reception circuit 41, an output IF specifying unit 42, an SW transmission circuit 43, an SW reception circuit 44, and an NW transmission circuit 45. The NW receiving circuit 41 receives a packet (MPLS packet in the first embodiment) received from the relay node 4 and other edge nodes. The output IF specifying unit 42 extracts information for specifying the NWIF card that outputs the received packet from the header of the received packet.

SW transmission circuit 43 transfers the received packet to SW32. The SW receiving circuit 44 receives a packet from the SW 32. The NW transmission circuit 45 transmits a packet to the relay node 4 or another edge node.

FIG. 9 is an explanatory diagram illustrating the LSP management table 29 according to the first embodiment.

The LSP management table 29 indicates the LSP corresponding to the flow indicated by the packet header. The LSP management table 29 includes a flow identifier 91 and an LSP ID 92. The LSP management table 29 is set according to instructions from the NMS 5.

The flow identifier 91 is a flow identifier. The LSP ID 92 is an LSP identifier for encapsulating a packet transmitted by the flow indicated by the flow identifier 91.

FIG. 10 is an explanatory diagram illustrating the LSP bandwidth management table 30 according to the first embodiment.

The LSP bandwidth management table 30 indicates the communication bandwidth set for the LSP. The LSP bandwidth management table 30 includes an LSP ID 101 and a set bandwidth 102. The LSP bandwidth management table 30 is set according to an instruction from the NMS 5.

LSP ID 101 indicates the identifier of the LSP. The set band 102 indicates a communication band set in the LSP indicated by the LSP ID 101. In each LSP, the communication band stored in the set band 102 is guaranteed.

The user flow specifying unit 36 extracts a flow identifier included in the header information of the received packet. Then, the user flow identification unit 36 searches the LSP management table 29 using the extracted flow identifier, thereby acquiring the LSP identifier for encapsulating the received packet from the LSP management table 29.

When the LSP identifier is acquired, the user flow specifying unit 36 searches the LSP bandwidth management table 30 using the LSP identifier, and acquires the value of the set bandwidth 102. Then, when transmitting the received packet, the user flow specifying unit 36 determines whether or not the bandwidth of the received packet in the LSP is within the value of the acquired set bandwidth 102.

The user flow specifying unit 36 updates the priority for transferring the received packet according to the determination result. The priority is a value stored in the header of the packet. The user flow specifying unit 36 transfers the packet whose priority has been updated to the SW transmission circuit 37.

Further, for example, when the user flow specifying unit 36 determines that the LSP band of the received packet exceeds the value of the set band 102 corresponding to the LSP, the user flow specifying unit 36 may discard the received packet. By discarding the packet, the edge node of the first embodiment can prevent the packet from flowing into the mobile backhaul 10 beyond the preset setting bandwidth 102. Thus, the edge node according to the first embodiment can suppress packet loss due to congestion that occurs in the mobile backhaul 10.

Further, for example, when the user flow specifying unit 36 determines that the LSP bandwidth of the received packet exceeds the value of the set bandwidth 102 corresponding to the LSP, the user flow specifying unit 36 sets a higher priority for discarding the received packet. After the update, the received packet may be transmitted. In the present embodiment, the higher the priority for discarding, the higher the possibility that the packet will be discarded. For example, the priority is a value stored in the LSP header.

By increasing the priority for discarding the packet, the edge node of the first embodiment causes the packet to flow into the mobile backhaul 10 beyond the preset bandwidth 102 and congestion occurs in the network. In this case, it is possible to preferentially discard a packet that has flowed beyond the set bandwidth 102. As a result, the edge node according to the first embodiment can suppress the loss of the packet that flows into the mobile backhaul 10 within the set bandwidth 102.

After executing these processes, the user flow specifying unit 36 transfers the received packet to the SW transmission circuit 37. The SW transmission circuit 37 specifies the NWIF card to which the packet is to be transferred from the LSP information (identifier and the like) added to the received packet, and transfers the packet toward the specified NWIF card.

Next, the network resource volume manager 1 according to the first embodiment changes the communication band of the LSP between the BS-NWE node 2 and the GW-NWE node 3 according to the number of mobile terminals 9 accommodated by the BS-NWE node 2 And a method of changing the LSP path.

FIG. 11 is a flowchart illustrating processing for determining the bandwidth of the communication path and processing for setting the path of the communication path according to the first embodiment.

As preconditions for the processing shown in FIG. 11, an LSP necessary for communication is set in advance between each BS-NWE node 2 and GW-NWE node 3 for each operator and for each service area. It is assumed that values are set in advance in the management table 29 and the LSP bandwidth management table 30.

First, the bandwidth determination unit 211 of the network resource volume manager 1 starts the process shown in FIG. 11 for each predetermined update cycle. Note that the bandwidth determination unit 211 starts the processing illustrated in FIG. 11 when, for example, the ESPGW 6 or the MME 7 acquires that the number of mobile terminals 9 included in at least one service area 11 has increased or decreased at a certain rate. May be.

The bandwidth determination unit 211 first collects information on the mobile terminal 9 in each of the service areas 11 from at least one of the ESPGW 6 and the MME 7 (S001).

The information on the mobile terminal 9 in FIG. 11 includes the identifier of the BS-NWE node 2 (corresponding to the node ID 63), the number of connected mobile terminals 9 in each service area 11 (corresponding to the number of connected state users 64), and The number of idle portable terminals 9 (corresponding to the number of idle users 65) is included for each operator.

However, the information regarding the mobile terminal 9 in the present embodiment may include information regarding the state of the mobile terminal 9, for example, the identifier of the mobile terminal 9, the identifier indicating the state of the mobile terminal 9, and the operator to which the mobile terminal 9 belongs An identifier may be included. Then, the bandwidth determination unit 211 may calculate the number of mobile terminals 9 for each state of the mobile terminal 9 from the collected information regarding the mobile terminal 9.

Further, when there is one BS-NWE node 2 or when there is one operator, the information regarding the mobile terminal 9 includes the identifier of the BS-NWE node 2 or the identifier of the operator. It does not have to be.

After S001, the bandwidth determination unit 211 updates the service area user count DB 27 using the collected information on the mobile terminal 9 (S002). Specifically, the bandwidth determination unit 211 updates at least the number of connected users 64 and the number of idle users 65 based on information about the mobile terminal 9.

After S002, the bandwidth determination unit 211 uses the updated service area-specific user number DB 27 to obtain information about the LSP set for each area ID 61 and business ID 62 from the LSP DB 28 (S003).

Specifically, in S003, the bandwidth determination unit 211 extracts one entry for which the processing from S004 onward is not executed in the service area user count DB 27.

Here, the service area 11 indicated by the area ID 61 of the extracted entry is described as area a, and the business operator indicated by the business ID 62 of the extracted entry is described business operator a.

In step S003, the bandwidth determination unit 211 extracts an entry in the LSP DB 28 having an area ID 71 and an operator ID 72 corresponding to the area a and the operator a. Then, the bandwidth determination unit 211 acquires information on the LSP ID 73, the edge node ID 74, the relay node ID 75, the edge node ID 76, and the set bandwidth Bw0 (77) of the extracted entry as information about the LSP.

Here, the LSP indicated by the acquired LSP ID 73 is referred to as LSPa. Note that the bandwidth determination unit 211 may extract two entries corresponding to communication in both directions as entries in the LSP DB 28 having the area ID 71 and the provider ID 72 corresponding to the area a and the provider a. In this case, the band determination unit 211 executes the processing from S004 onward for each entry indicating one-way communication.

After S003, the bandwidth determination unit 211 identifies the entry of the bandwidth coefficient DB 24 having the business entity ID 81 corresponding to the business operator a, and acquires the values of the bandwidth α82 and the bandwidth β83 of the identified entry (S004).

After S004, the bandwidth determination unit 211 includes the connection state user count 64 and the idle state user count 65 of the entry extracted from the service area user count DB 27 in S003, and the bandwidth α82 and the bandwidth β83 acquired from the bandwidth coefficient DB24. The bandwidth Bw1 to be newly set in LSPa is calculated using Equation 1 (S005).

Band Bw1 = Band α82 × Number of connected users 64 + Band β83 × Idle state users 65 (Formula 1)

After S005, the bandwidth determination unit 211 determines whether or not the LSPa bandwidth can be changed to the calculated bandwidth Bw1 by the processing of S006 to S008. That is, the bandwidth determination unit 211 determines whether or not the network resource for setting the calculated bandwidth Bw1 can be secured on the route assigned to LSPa.

Through the processing of S006 to S008, the bandwidth determination unit 211 can suppress the occurrence of congestion in the mobile backhaul 10 even after dynamically changing the LSPa bandwidth.

First, in S006, the band determining unit 211 calculates a band increase / decrease value Bw2 based on the value of the set band Bw0 (77) acquired in S003, the band Bw1, and Expression 2 (S006). The band increase / decrease value Bw2 is the amount of change between the band Bw1 that should be newly set in LSPa and the set band Bw0 that has already been set in LSPa.

Bandwidth increase / decrease value Bw2 = bandwidth Bw1-set bandwidth Bw0 (Formula 2)

After S006, the bandwidth determination unit 211 generates at least one link ID for connecting the network devices based on the edge node ID 74, the relay node ID 75, and the edge node ID 76 acquired from the LSP DB 28 in S003 (S007). ). The order of connecting the network devices follows the edge node ID 74, the relay node ID 75, and the edge node ID 76 acquired in S003.

The bandwidth determination unit 211 in the present embodiment may generate the link ID by connecting the identifier of the edge node ID 74 and the identifier of the relay node ID 75 with a hyphen, for example. The bandwidth determination unit 211 may generate any link ID as long as a unique policy is defined for the link ID in the network system.

Further, when the maintenance person presets the link ID in the NW topology DB 25, the bandwidth determination unit 211 may acquire the link ID from the NW topology DB 25 in S007.

After S007, the bandwidth determination unit 211 searches the NW resource management DB 26 using the generated link ID to acquire the network resource in each link through which the LSPa passes, and the bandwidth 52 and the remaining bandwidth 53 for each link ID. To get. Further, the band determining unit 211 subtracts the band increase / decrease value Bw2 from the remaining band 53 of each link using Expression 3 (S008). Each of the post-change remaining bands calculated here is a remaining band in each link after LSPa is set to a new band Bw1.

Remaining bandwidth after change = Remaining bandwidth-Band increase / decrease value Bw2 (Formula 3)

The bandwidth determination unit 211 calculates the post-change remaining bandwidth for all links through which LSPa passes. When the remaining bandwidth after change in all links is 0 or more, sufficient bandwidth is secured in each link even after the change to the new bandwidth Bw1. On the other hand, if the remaining bandwidth after the change in at least one link is less than 0, after the change to the new bandwidth Bw1, there will be a link whose bandwidth is insufficient in the LSPa path.

Therefore, the bandwidth determination unit 211 determines whether or not the post-change remaining bandwidth calculated in each link is negative after S008 (S009).

In S009, when it is determined that the remaining bandwidth after the setting change is not negative, that is, 0 or more, the bandwidth determination unit 211 executes the processing from S010 onward in order to set the new bandwidth Bw1 to LSPa. If it is determined in S009 that the post-change remaining bandwidth is negative, the bandwidth determination unit 211 executes processing subsequent to S021 to change the LSPa path.

In S010, the bandwidth determination unit 211 updates the remaining bandwidth 53 of the NW resource management DB 26 corresponding to the link of the LSPa to the changed remaining bandwidth calculated in S008. After S010, the bandwidth determination unit 211 updates the set bandwidth Bw0 (77) of the LSP DB 28 corresponding to the LSPa with the value of the bandwidth Bw1 (S011).

After S011, the band instruction unit 212 notifies the NMS 5 of a band change request regarding LSPa (S012). The bandwidth change request for the LSPa includes information on each link of the LSPa (identifier indicating the edge node and the relay node 4 through which the LSPa passes) and an instruction to change the bandwidth of each link to the bandwidth Bw1. The bandwidth instruction unit 212 generates a bandwidth change request for LSPa based on the LSP DB 28.

When the NMS 5 receives the bandwidth change request regarding the LSPa from the network resource volume manager 1, the NMS 5 sends the LSPa to the edge node and the relay node 4 through which the LSPa indicated by the bandwidth change request passes based on the database and the bandwidth change request that the NMS 5 has. Is instructed to be changed to the bandwidth Bw1. The database possessed by the NMS 5 is, for example, a database for associating identifiers and addresses of edge nodes and relay nodes 4 with each other.

The device control unit 34 of the edge node updates the value of the set bandwidth 102 of the LSP ID 101 of the LSP bandwidth management table 30 corresponding to the LSPa to the bandwidth Bw1 when instructed by the NMS 5 to change the bandwidth of the LSPa. Further, the relay node 4 updates the band for transferring the packet having the label of LSPa to the band Bw1.

In response to the processing from S001 to S012 by the network resource volume manager 1 described above and the bandwidth change instruction to the edge node and the relay node 4 by the NMS 5, the network device through which the LSPa that changes the bandwidth passes changes the bandwidth. Can do. Then, by these band changes, the network resource volume manager 1 according to the first embodiment allows the BS-NWE node 2 to accommodate the LSPa (communication path) band from the BS-NWE node 2 to the GW-NWE node 3. The bandwidth can be changed to the optimum bandwidth Bw1 according to the number of terminals 9 and the state of the mobile terminal 9, and network utilization efficiency can be improved.

On the other hand, if it is determined in S009 that the remaining bandwidth after the setting change is negative, if the LSPa bandwidth is changed to a new bandwidth Bw1, congestion occurs at the edge node or the relay node 4 of the LSPa route, and the LSPa bandwidth is changed. Each network device cannot transfer data properly. Therefore, the bandwidth determination unit 211 executes the processing from S021 onward in order to change the LSPa path.

The bandwidth determination unit 211 first releases the bandwidth already set in LSPa in S021. Specifically, the bandwidth determination unit 211 adds the value of the set bandwidth Bw0 (77) of the LSPa acquired in S003 to the remaining bandwidth 53 of the NW resource management DB 26 corresponding to each link of the LSPa path (S021). ).

After S021, the bandwidth determination unit 211 refers to the NW resource management DB 26 and the NW topology DB 25, can connect the BS-NWE node 2 and the GW-NWE node 3 of the LSPa, and has a new bandwidth Bw1 or higher. A link having a remaining bandwidth 53 is extracted. Then, the bandwidth determination unit 211 determines a new path of the LSPa by using the extracted link (S022).

In S022, if the bandwidth determination unit 211 cannot determine a new path for the LSPa, the bandwidth determination unit 211 does not change the LSPa bandwidth and the LSPa path, and ends the processing illustrated in FIG.

After S022, the bandwidth determination unit 211 updates the relay node ID 75 corresponding to the LSPa in the LSP DB 28 based on the new route determined in S022. Then, the bandwidth determining unit 211 updates the set bandwidth Bw0 (77) corresponding to LSPa with the bandwidth Bw1 (S023).

After S023, the bandwidth determination unit 211 subtracts the bandwidth Bw1 from the value of the remaining bandwidth 53 of the NW resource management DB 26 for each link through which the new path of LSPa passes (S024).

After S024, the bandwidth instruction unit 212 deletes a request for deleting each LSPa network device on the existing path of LSPa and a generation request indicating that each network device on the new path of LSPa generates LSPa. To NMS5 (S025). The generation request includes information indicating the band Bw1.

When the NMS 5 receives the deletion request and the generation request from the network resource volume manager 1, the NMS 5 refers to the database of the NMS 5 and each network device (BS-NWE node 2, GW-NWE node) on the path of LSPa indicated by the deletion request 3 and the relay node 4) are instructed to delete the LSPa setting. Further, the NMS 5 instructs each network device (BS-NWE node 2, GW-NWE node 3 and relay node 4) on the path of LSPa indicated by the generation request to set the LSPa with the band Bw1.

Here, if necessary, the NMS 5 may hold the flow identifier of the flow corresponding to the LSPa, and transmit the identifier indicating the LSPa and the identifier of the flow to the edge node.

The device controller 34 of the edge node updates the LSP management table 29 and the LSP bandwidth management table 30 when instructed by the NMS 5 to delete and add LSPa settings. Specifically, when each of the edge nodes is instructed to delete the LSPa setting, each of the edge nodes corresponds to the LSP management table 29 entry having the LSP ID 92 corresponding to the LSPa and the LSPa in the LSP bandwidth management table 30. The entry of the LSP management table 29 having the LSP ID 101 is deleted.

When the device controller 34 of the edge node is instructed to add the LSPa setting, the flow identifier of the flow corresponding to the LSPa and the identifier indicating the LSPa, the flow identifier 91 of the LSP management table 29, and the LSP ID 92 are displayed. To store. Further, each device control unit 34 stores an identifier indicating the LSPa and the bandwidth Bw1 in the LSP ID 101 and the set bandwidth 102 of the LSP bandwidth management table 30.

Further, the edge node and the relay node 4 update their destination information and the like based on the instruction from the NMS 5 so as to transfer the packet added with the LSPa as a label along the route of the LSPa.

The route of LSPa is changed by the processing of S021 to S025 and the instruction to change the setting of LSPa from the NMS 5 to the edge node and the relay node 4.

Through the processing of S021 to S025, the network resource volume manager 1 according to the first embodiment determines the path of the communication path even when the bandwidth of the communication path from the BS-NWE node 2 to the GW-NWE node 3 is insufficient. By re-setting, the optimum bandwidth can be secured. In addition, the network resource volume manager 1 according to the first embodiment can secure an optimal bandwidth according to the number of mobile terminals 9 accommodated in the BS-NWE node 2 and the state of the mobile terminals 9, thereby The utilization efficiency of is improved.

More specifically, the network resource volume manager 1 according to the first embodiment can reduce the number of relay nodes 4 in which the bandwidth of the accommodated communication path is excessive by resetting the communication path. Then, by setting a communication path for the relay node 4 having a low usage rate, the network usage efficiency can be improved. In addition, for example, a large band can be allocated to the service area 11 including a large number of mobile terminals 9, and the use efficiency of the network can be improved.

The bandwidth coefficient DB 24 described above was previously set by a maintenance person. However, the bandwidth determination unit 211 uses the connection state user number 64 and the idle state user number 65 collected a predetermined number of times in the past to calculate a statistical value indicating the change between the connection state user number 64 and the idle state user number 65. And the bandwidth coefficient DB 24 may be updated based on the calculated statistical value. FIG. 12 shows an example of processing for updating the band coefficient DB 24.

FIG. 12 is a flowchart showing a process for updating the bandwidth of the bandwidth coefficient DB 24 of the first embodiment.

The bandwidth determination unit 211 of the network resource volume manager 1 accumulates the collected connection state user number 64 and idle state user number 65 in its own memory each time the processing shown in FIG. 11 is executed. Then, the bandwidth determination unit 211 of the network resource volume manager 1 periodically executes the process shown in FIG.

Hereinafter, the process shown in FIG. 12 is executed and the bandwidth coefficient DB 24 is updated, which is referred to as a periodic update. Moreover, the process shown in FIG. 12 may be performed after the process shown in FIG. 11 is complete | finished, when the process shown in FIG. 11 is performed regularly.

The bandwidth determination unit 211 acquires the latest connection state user count 64 and idle state user count 65 from the bandwidth coefficient DB 24 (S101). The connection state user number 64 and the idle state user number 65 acquired here are set as a connection state user number CU ₀ and an idle state user number IU ₀ .

After S101, the bandwidth determination unit 211 uses the connection state user number CU ₀ and the idle state user number IU ₀ acquired in the process of S101 executed in the previous periodic update as the connection state user number CU ₁ and the idle state user. Obtained as the number IU ₁ . Then, the bandwidth determination unit 211 calculates the change amount V ₀ (absolute value) of the number of connected state users using the number of connected state users CU ₀ , the number of connected state users CU _1, and Expression 4 (S 102).

| V ₀ | = CU ₁ -CU ₀ (Formula 4)

After S102, the bandwidth determining unit 211 uses the idle number of users IU ₁ in a connected state the number of users change amount V ₀ and the equation 5 to calculate the change rate R ₀ (S103).

R ₀ = | V ₀ | / IU ₁ (Formula 5)

After S103, the bandwidth determination unit 211 acquires the _n rate of change R ₀ calculated in the past n regular updates as rate of change R ₀ to rate of change R _n-1 and changes rate R ₀ to the rate of change. Using the rate R _n-1 and Equation 6, the average RA of the rate of change is calculated (S104).

RA = Sum (R _n-1 : R ₀ ) / n (Formula 6)

Note that the predetermined number of times n used in Equation 6 is set in advance by the maintainer. When the process shown in FIG. 11 is periodically executed, the value n may be determined by designating a predetermined period during which the process shown in FIG. 11 is executed by a maintenance person.

After S104, the band determining unit 211 calculates the band β using the average RA of the change rate, the band α, and Equation 7 (S105). Here, the band α used in Expression 7 is a value of the band α82 whose value is set in advance by the maintainer.

Β = RA × α (Formula 7)

When the band β is calculated in S105, the band determining unit 211 updates the band β83 of the band coefficient DB 24 with the newly calculated band β. By periodically updating the band β83 by the process of FIG. 12 described above, the band β83 can be determined based on the latest information on the number (change amount) of the mobile terminals 9 that transition from the idle state to the connected state. .

In addition, the bandwidth determination unit 211 performs the processing of FIG. 12, thereby generating congestion in the network while securing bandwidth more efficiently for the mobile terminal 9 (potential user) that transitions from the idle state to the connected state. Can be prevented in advance.

For example, when the average RA of the rate of change at which the mobile terminal 9 in the idle state transitions to the connected state at the time of regular update is calculated based on the past statistics by the process shown in FIG. The unit 211 may determine the band β to be 20% of the band α. Thereby, even when the portable terminal 9 in the idle state transitions to the connected state, a band of 20% of the band α is secured in the portable terminal 9.

Further, the bandwidth determination unit 211 may add a predetermined surplus bandwidth to the bandwidth β calculated in S105, and update the bandwidth β83 with the bandwidth β including the predetermined surplus bandwidth. As a result, even when the number of mobile terminals 9 that transition from the idle state to the connected state exceeds the average RA of the rate of change, a sufficient bandwidth can be secured for all the mobile terminals 9 in the connected state, and the mobile backhaul 10 The occurrence of congestion can be prevented in advance.

Further, the bandwidth determining unit 211 may update the bandwidth β83 with the same value as the bandwidth α82 instead of executing the processing shown in FIG. Thereby, the bandwidth determination unit 211 can assign the same bandwidth to all the mobile terminals 9 included in the service area 11. As a result, even when all the mobile terminals 9 in the idle state transition to the connected state, a sufficient bandwidth can be secured and the occurrence of congestion in the network can be prevented.

Furthermore, the band coefficient DB 24 of the present embodiment may include any band other than the band α82 and the band β83. Here, the state of the mobile terminal 9 according to the present embodiment includes contents or purposes communicated by the mobile terminal 9, and the bandwidth coefficient DB 24 is specific to the contents or purposes communicated by the mobile terminal 9. A band may be included.

For example, the state of the mobile terminal 9 of the present embodiment may be the state of the mobile terminal 9 provided with a predetermined network service. Examples of the network service include a moving image distribution server for the mobile terminal 9.

When a predetermined network service is provided by the application server, the network resource volume manager 1 is connected to the application server in addition to the MME 7 and the ESPGW 6, and the bandwidth coefficient DB 24 is a bandwidth reserved for the mobile terminal 9 communicating with the application server. The band α1 may be provided instead of the band α.

Then, the bandwidth determination unit 211 may collect the number of mobile terminals 9 from the MME 7 or ESPGW 6, and may further collect the number of mobile terminals 9 that communicate with the application server from each application server. Then, the bandwidth determining unit 211 may calculate a new bandwidth Bw1 by multiplying the number of mobile terminals 9 communicating with the application server by the bandwidth corresponding to the network service provided by the application server.

Thereby, in addition to the case where the state of the mobile terminal 9 is the connected state or the idle state, the mobile terminal 9 can ensure the optimum bandwidth according to the provided network service. And the band determination part 211 can improve the utilization efficiency of a network.

In addition, the bandwidth determination unit 211 described above changes the bandwidth and route of the communication path in the mobile backhaul 10 according to the number and state of the mobile terminals 9 that perform wireless communication in the service area 11. However, in the present embodiment, the edge node corresponding to the BS-NWE node 2 may accommodate a wired terminal, and the bandwidth determination unit 211 of the first embodiment is configured so that the number of terminals that communicate with the edge node by wired and The bandwidth and route of the communication path in the mobile backhaul 10 may be changed according to the state.

For example, the network system according to the first embodiment can be applied to a network system in which the BS-NWE node 2 is connected to the OLT and the OLT is connected to a plurality of ONUs by wire. In this case, the number of ONUs registered in the OLT and the number of ONUs not registered in the OLT are collected by a server equivalent to ESPGW6 or MME7, and the bandwidth determining unit 211 sends the OLT from the terminal management server equivalent to ESPGW6 or MME7 to the OLT. The number of registered ONUs and the number of ONUs not registered in the OLT may be collected. Then, the bandwidth determination unit 211 may determine the bandwidth or route of the communication path in the mobile backhaul 10 by the process shown in FIG. 12 based on the collected information about the ONU.

According to the first embodiment, the network resource volume manager 1 and the NMS 5 communicate the communication path between the BS-NWE node 2 and the GW-NWE node 3 according to the number of mobile terminals 9 accommodated by the BS-NWE node 2. Change the bandwidth and communication path. As a result, the network resource volume manager 1 according to the first embodiment avoids setting an excessive bandwidth in one relay node 4 even when a plurality of communication paths are set in the mobile backhaul 10, and the utilization rate is reduced. By setting a communication path to the relay node 4 with a low network resource utilization efficiency can be improved.

Further, the network resource volume manager 1 according to the first embodiment calculates a necessary bandwidth in the mobile backhaul 10 based on the bandwidth coefficient DB 24 corresponding to the state of the mobile terminal 9 (connected state or idle state). . For this reason, it is possible to secure a bandwidth for a potential user such as the mobile terminal 9 in the idle state, and congestion in the mobile backhaul 10 even when the mobile terminal 9 in the idle state transitions to the connected state. Can be reduced. In addition, for example, packet discard can be suppressed.

Further, when the bandwidth coefficient DB 24, the service area user count DB 27, and the LSP DB 28 of the present embodiment have the carrier ID 72, a plurality of carriers share the same mobile backhaul 10. In addition, the bandwidth determination unit 211 can associate the business operator with the LSP. For this reason, even when a plurality of operators use one mobile backhaul 10, the network resource volume manager 1 of the first embodiment changes the bandwidth and route of the communication path allocated for each operator. The use efficiency of network resources can be improved for each business operator.

In addition, the network resource volume manager 1 can update the information such as the number of connected users 64 and the number of idle users 65 on a regular basis for each operator, thereby providing an equivalent function to a plurality of operators. The mobile backhaul 10 can be used between businesses. On the other hand, different services can be provided for each business operator.

The network system according to the second embodiment aims to improve the use efficiency of network resources even when a heavy user occurs in the mobile terminal 9 that uses the mobile backhaul 10.

For example, when the bandwidth set for the communication path of the mobile backhaul 10 is best effort, since some of the plurality of mobile terminals 9 accommodated in the GW-NWE node 3 are heavy users, Communication by all the mobile terminals 9 other than the user is delayed.

Therefore, in the network system according to the second embodiment, when a heavy user who transmits and receives a large number of packets in one service area 110 occurs, offloading communication by the heavy user to a network where quality is not secured, The quality of communication by the portable terminal 9 is ensured, and the utilization efficiency of network resources is improved.

FIG. 13 is an explanatory diagram showing the network system of the second embodiment.

The network system according to the second embodiment has two connections between the BS-NWE 103 corresponding to the BS-NWE node 2 according to the first embodiment and the GW-NWE node 104 corresponding to the GW-NWE node 3 according to the first embodiment. Including the above networks. Note that the BS-NWE node 103 and the GW-NWE node 104 of the second embodiment are edge nodes having the same functions as the BS-NWE node 2 and the GW-NWE node 3 of the first embodiment. Differences between the edge node of the second embodiment and the edge node of the first embodiment will be described later.

The network system shown in FIG. 13 includes a network 120a and a network 120b. The network 120a is a network constructed by MPLS-TP whose quality is ensured as in the first embodiment. The network 120b is a network whose quality is not guaranteed, for example, a network such as MPLS-TP or Ethernet whose quality is not guaranteed.

The network system of the second embodiment includes a network resource volume manager 100, a maintenance person terminal 12, at least one service area 11 (11-1 to 11-3), ESPGW6, MME7, network 120a and network 120b. The network system according to the second embodiment accommodates communication by at least one business operator.

The maintenance person terminal 12, service area 11, ESPGW6, and MME7 of the second embodiment are the same as the maintenance person terminal 12, service area 11, ESPGW6, and MME7 of the first embodiment.

The network 120a corresponds to the mobile backhaul 10 of the first embodiment, and includes a BS-NWE node 103-1, a BS-NWE node 103-4, a GW-NWE node 104, and at least one relay node 4a (4a-1 to 4a). -5) and NMS5a. The network 120b includes BS-NWE nodes 103-1 to 103-4, a GW-NWE node 104, at least one relay node 4b (4b-1 to 4b-5), and an NMS 5b.

The BS-NWE node 103-1, the BS-NWE node 103-4, and the GW-NWE node 104 are included in both the network 120a and the network 120b.

Packets in the network 120a are transferred by MPLS-TP. For this reason, the NMS 5a sets the packet transfer path and bandwidth by MPLS in the edge node and the relay node 4a included in the network 120a. The NMS 5b of the network 120b sets information for transferring Ethernet packets to the edge node and the relay node 4b included in the network 120b.

The network resource volume manager 100 according to the second embodiment, like the network resource volume manager 1 according to the first embodiment, periodically collects the number and state of the mobile terminals 9 communicating with each of the base stations 8 from the MME 7 and the ESPGW 6, Based on the collected information, a bandwidth to be set for each communication path is calculated. Further, the network resource volume manager 100 according to the second embodiment determines a new route of the communication path in the network 120a, as with the network resource volume manager 1 according to the first embodiment.

The network resource volume manager 100 of the second embodiment has the same function as the network resource volume manager 1 of the first embodiment. However, the network resource volume manager 100 of the second embodiment is different from the network resource volume manager 1 of the first embodiment in that it has a heavy user management DB 130. Further, the information included in the LSP DB 28 of the first embodiment is different from the information included in the LSP DB 28 of the second embodiment.

The BS-NWE node 103 according to the second embodiment can distribute the packet received from the base station 8 to the network 120a or the network 120b according to the header information of the packet. The GW-NWE node 104 according to the second embodiment can distribute a packet received from outside the network 120a and the network 120b to the network 120a or the network 120b according to the header information of the packet.

The BS-NWE node 103 and the GW-NWE node 104 of the second embodiment are different from the BS-NWE node 2 and the GW-NWE node 3 of the first embodiment in that they have a heavy user identification table 140. The heavy user identification table 140 is included in the access NWIF card 31 and is read by the user flow specifying unit 36.

FIG. 14 is an explanatory diagram illustrating the heavy user management DB 130 according to the second embodiment.

The heavy user management DB 130 indicates heavy users acquired in each service area 11 and each business operator. The heavy user management DB 130 includes an area ID 131, an operator ID 132, an LSP ID 133, an edge node ID 134, and a heavy user ID 135. The area ID 131 indicates the identifier of the service area 11. The business operator ID 132 indicates an identifier of the business operator.

LSP ID 133 indicates an identifier (label) of the LSP. The LSP ID 133 indicates a communication path through which a packet transmitted by a heavy user passes or a communication path through which a packet transmitted toward the heavy user passes.

The edge node ID 134 indicates an identifier of the BS-NWE node 103 or the GW-NWE node 104. The edge node ID 134 indicates an edge node that needs to transmit information about a heavy user, and thus indicates an edge node that is a starting point of a route through which a packet passes in the network 120a and the network 120b.

The heavy user ID 135 indicates an identifier of a heavy user among the mobile terminals 9. The heavy user in the present embodiment is a mobile terminal 9 that satisfies a predetermined condition indicating that the amount of packets to be transmitted / received is large, for example, a packet is transmitted / received exceeding a predetermined rate. The identifier stored in the heavy user ID 135 corresponds to the identifier of the heavy user included in the packet transmitted and received by the heavy user, and is, for example, the address of the heavy user.

FIG. 15 is an explanatory diagram showing the LSP DB 28 of the second embodiment.

The LSP DB 28 according to the second embodiment holds a route and a set bandwidth for each communication path (LSP) set between the BS-NWE node 103 and the GW-NWE node 104, similarly to the LSP DB 28 according to the first embodiment. As in the first embodiment, the LSP DB 28 according to the second embodiment includes an area ID 71, an operator ID 72, an LSP ID 73, an edge node ID 74, a relay node ID 75, an edge node ID 76, and a set bandwidth Bw0 (77). The LSP DB 28 of the second embodiment further includes a network ID 78 and a heavy user NWID 79.

The network ID 78 indicates an identifier of each of the plurality of networks 120 managed by the network resource volume manager 1 according to the second embodiment. The heavy user NWID 79 indicates an identifier of the network 120 for the heavy user that transfers a packet transmitted / received by the heavy user instead of the network 120 indicated by the network ID 78.

In Example 2, an entry indicating a plurality of different LSPs is set in one-way communication of one set of area ID 71 and business operator ID 72. In particular, the LSP DB 27 set in the network shown in FIG. 13 has two communication paths for passing through two networks as communication paths assigned to one-way communication of one set of area ID 71 and operator ID 72. Is set.

In the LSP DB 27 shown in FIG. 15, an entry a indicating one of the two communication paths is set in advance as an entry indicating the network 120 for passing a packet of the mobile terminal 9 that is not a heavy user. . In this entry a, a value is set for the heavy user NWID 79. The LSP ID 73 of entry a indicates the LSP of the network 120a.

Further, of the two communication paths, the entry b indicating the other communication path is set in advance as the network 120 for allowing the packet transmitted / received by the heavy user to pass. In this entry b, no value is set for the heavy user NWID 79, and the value of the heavy user NWID 79 of the entry a is set in the network ID 78. The LSP ID 73 of the entry b indicates the LSP of the network 120b.

Note that the LSP DB 28 shown in FIG. 15 has a heavy user NWID 79 to identify a network through which a heavy user packet passes. However, the network resource volume manager 100 may have the heavy user NWID 79 by any method, and may have a table for identifying a network through which the heavy user's packet is passed separately from the LSP DB 28.

FIG. 16 is an explanatory diagram illustrating the heavy user identification table 140 according to the second embodiment.

The heavy user identification table 140 is referred to when the packet is transferred by the user flow specifying unit 36 of the edge node of the second embodiment. The heavy user identification table 140 has a heavy user ID 141 and an LSP ID 142.

The heavy user ID 141 is an identifier corresponding to the user identifier included in the received packet, and indicates a heavy user. The LSP ID 142 indicates the LSP to which the packet transmitted by the heavy user is transferred.

FIG. 17 is a flowchart illustrating processing for setting an edge node for a heavy user according to the second embodiment.

The bandwidth determination unit 211 according to the second embodiment may execute the process illustrated in FIG. 17 after the process illustrated in FIG. 11. When a plurality of processors are used, the process illustrated in FIG. 11 and the process illustrated in FIG. 17 are performed. It may be executed in parallel.

The bandwidth determination unit 211 according to the second embodiment, like the bandwidth determination unit 211 according to the first embodiment, periodically collects the number of connected users 64 and the number of idle users 65 for each service area 11 from the MME 7 or the ESPG 6. However, the bandwidth determination unit 211 of the second embodiment is different from the bandwidth determination unit 211 of the first embodiment, in addition to the number of connected users and the number of idle users, information on heavy users for each service area 11 is also received from the MME 7 or ESPGW6. Collect (S201).

The information regarding the heavy user includes an identifier of the service area 11 in which the heavy user is included, an identifier of the business operator to which the heavy user belongs, and a heavy user ID indicating the heavy user.

Servers that provide mobile services such as MME 7 and ESPGW 6 collect transmission / reception information indicating the amount (rate) of data to be transmitted / received for each mobile terminal 9. For this reason, at least one of MME7 and ESPGW6 can specify that the mobile terminal 9 that transmits and receives data exceeding a predetermined threshold is a heavy user.

Note that the network resource volume manager 100 may collect transmission / reception information for each portable terminal 9 from the MME 7 or ESPGW 6 and specify a heavy user based on the collected transmission / reception information and a predetermined threshold.

Further, when the information on the heavy user cannot be acquired from the MME 7 or the ESPGW 6, or when the heavy user cannot be specified even in the network resource volume manager 100, the bandwidth determination unit 211 may end the process illustrated in FIG.

When the information regarding the heavy user is acquired after S201, the bandwidth determining unit 211 acquires an entry from the LSP DB 28 using the information regarding the heavy user using the area ID 71 and the business ID 72 as search keys (S202).

In the network system shown in FIG. 13, since there are two networks that can be used by one service area 11 and one operator group, the LSP DB 28 contains one set of area ID 71 and operator ID 72. Two different entries are set for direction communication. For this reason, in S202, the bandwidth determination unit 211 acquires two entries from the LSP DB 28 in one direction.

In S202, when a plurality of entries corresponding to two-way communication are acquired, the bandwidth determination unit 211 executes the processing after S203 for each one-way communication. In the following, the processing of S203 to S206 executed for an entry indicating one-way communication will be described.

After S202, the bandwidth determination unit 211 specifies the network 120 through which a packet transmitted / received by the heavy user is to be passed based on the network ID 78 and the heavy user NWID 79 of the entry acquired in S202 (S203). Specifically, the bandwidth determination unit 211 extracts the identifier of the heavy user NWID 79 from the entries stored in the heavy user NWID 79 out of the entries acquired in S202, and further adds the extracted identifier to the network ID 78. Identify the entry that contains it.

Then, the network 120 indicated by the extracted identifier is specified as the network 120 through which the packet transmitted / received by the heavy user is to be passed. The network 120 specified here is the network 120b in the network system shown in FIG.

After S203, the bandwidth determination unit 211 acquires the area ID 71, the operator ID 72, the LSP ID 73, and the edge node ID 74 from the entry of the network 120b specified in S203 (S204). The LSP ID 73 acquired here indicates an LSP in the network 120b.

After S204, the bandwidth determining unit 211 adds the information acquired in S204 to a new entry in the heavy user management DB 130. Specifically, the bandwidth determination unit 211 adds the area ID 71, the provider ID 72, the LSP ID 73, and the edge node ID 74 to the area ID 131, the provider ID 132, the LSP ID 133, and the edge node ID 134. In addition, the bandwidth determination unit 211 adds the heavy user ID acquired in S201 to the heavy user ID 135 of the new entry in the heavy user management DB 130 (S205).

When the entry corresponding to the information related to the LSP in the network 120b acquired in S204 is already included in the heavy user management DB 130, the bandwidth determination unit 211 sets the heavy user ID 135 of the entry corresponding to the LSP in the network 120b to S201. The heavy user ID acquired in step 1 may be added.

After S205, the bandwidth instructing unit 212 sets the values of the heavy user ID 135, the LSP ID 133, and the edge node ID 134 of the newly added entry (heavy user ID, LSP ID, and edge) in order to set the heavy user information in the edge node. Node ID) is notified to the NMS 5. Here, the bandwidth instruction unit 212 acquires the edge node through which the packet by the heavy user passes from the edge node ID 134 of the entry of the heavy user management DB 130 corresponding to the LSP in the network 120b, and sends it to the NMS 5 connected to the acquired edge node. Information such as a heavy user ID is transmitted.

The NMS 5 notifies the edge node indicated by the information transmitted from the network resource volume manager 100 of the heavy user ID and LSP ID included in the transmitted information. In the network 120a and the network 120b in the second embodiment, the LSP indicated by the LSP DB 28 has been set.

The device control unit 34 of the edge node sets the heavy user ID and LSP ID received from the NMS 5 to the heavy user ID 141 and the LSP ID 142 of the new entry in the heavy user identification table 140.

When the packet is received after the information is set in the heavy node identification table 140 of the edge node, the user flow specifying unit 36 first sets the heavy user identification table 140 using the header information included in the received packet. Search for.

For example, when the source or destination mobile terminal 9 indicated by the header information of the received packet indicates the heavy user ID 141 in the heavy user identification table 140, the user flow specifying unit 36 is more than the search result in the LSP management table 29. The search result of the heavy user identification table 140 is used with priority.

In the heavy user identification table 140, the user flow specifying unit 36 extracts the LSP identifier from the LSP ID 142 of the entry corresponding to the transmission source or destination of the received packet, and receives it by the MPLS header including the extracted LSP identifier. Encapsulate the packet. Then, the user flow specifying unit 36 and the SW transmission circuit 37 transfer the encapsulated packet to the SW 32.

Thereby, the packet transmitted by the heavy user or the packet transmitted toward the heavy user passes through the network 120b.

Note that if the relay node 4b in the network 120b supports Ethernet frame transfer and is not set to transfer MPLS-TP packets, the relay node 4b included in the network 120b is connected to the edge node access NWIF card. The packet can be transferred by connecting to the terminal 31.

More specifically, a packet by heavy user communication is encapsulated by an MPLS header in the access NWIF card 31 and then transferred to another access NWIF card 31 in the SW 32. The packet by the heavy user communication is decapsulated in the MPLS header in the transfer destination access NWIF card 31 and transferred to the relay node 4b. Therefore, the relay node 4b receives the packet that is not encapsulated by the MPLS header, and transfers the packet based on the Ethernet format of the received packet.

According to the second embodiment, among mobile terminals 9 included in one service area 11 and belonging to one operator, a packet by a heavy user is different from a packet by a mobile terminal 9 other than the heavy user. It is transferred using the path. For this reason, the network resource volume manager 100 of Example 2 can suppress the situation where the packet of the portable terminals 9 other than a heavy user is discarded by communication by a heavy user.

In addition, this invention is not limited to the Example mentioned above, Various modifications are included.

For example, the above-described embodiments have been described in detail for easy understanding of the present invention, and are not necessarily limited to those having all the configurations described. Further, a part of the configuration of one embodiment can be replaced with the configuration of another embodiment, and the configuration of another embodiment can be added to the configuration of one embodiment. In addition, it is possible to add, delete, or replace another configuration for a part of the configuration of each embodiment.

Further, the database and table in the present embodiment may hold information in any format including the above-described contents, and may hold information in a format such as CSV other than the table format.

In addition, each of the above-described configurations, functions, processing units, and processing procedures may be realized by hardware by designing a part or all of them with, for example, an integrated circuit. Each of the above-described configurations, functions, and the like may be realized by software by interpreting and executing a program that realizes each function by the processor. Information such as a program, a table, or a file that realizes each function can be stored in a recording device such as a memory, a hard disk, or an SSD (Solid State Drive), or a recording medium such as an IC card, an SD card, or a DVD.

Also, the control lines and information lines indicate objects that are considered necessary for explanation, and not all control lines and information lines on the product are necessarily shown. Actually, it may be considered that almost all the components are connected to each other.

Claims (15)

1. A network system for transferring data transmitted and received by a terminal,
   The network system is connected to a first edge node that accommodates the terminal, a terminal management server that holds information on the terminal, a network manager connected to the terminal management server, and the first edge node. A second edge node,
   Data transmitted and received by the terminal is transferred via a path between the first edge node and the second edge node;
   The terminal takes one of a plurality of terminal states including a first state in which the terminal transmits / receives only control data and a second state in which the terminal transmits / receives data other than the control data,
   The network manager
   A processor and a memory;
   In each of the terminal states, the terminal has band information including a band reserved for the terminal to communicate via the path;
   Obtaining terminal status information of the terminal from the terminal management server,
   The terminal communicates via a path based on the number of terminals in the first state and the number of terminals in the second state indicated by the information acquired from the terminal management server and the bandwidth information. Calculating the bandwidth reserved for
   A network system, characterized in that the first edge node and the second edge node are set so that data transmitted / received by the terminal is transferred according to the calculated bandwidth.
2. The network system according to claim 1,
   The band information includes an identifier indicating a business operator to which the terminal belongs,
   The terminal status information of the terminal includes an identifier of a business operator to which the terminal belongs,
   The network manager is based on the number of terminals in the first state, the number of terminals in the second state, the identifier of the operator, and the bandwidth information indicated by the information acquired from the terminal management server. And calculating a bandwidth reserved for the terminal to communicate via a path.
3. The network system according to claim 1 or 2,
   The terminal state includes a state of a terminal for which network service is provided,
   The network manager
   Connected to an application server providing the network service,
   Obtaining the number of the terminals provided with the network service from the application server;
   The terminal communicates via a path based on the number of terminals provided with the network service acquired from the application server, the terminal status and the number of terminals acquired from the terminal management server, and the bandwidth information. A network system characterized by calculating a bandwidth reserved for the purpose.
4. The network system according to claim 1,
   The network system includes at least one relay node connected to the first edge node and the second edge node;
   The network manager
   Resource management information indicating a usable bandwidth between each of the first edge node, the second edge node, and the relay node;
   It is determined based on the resource management information whether or not the data transmitted and received by the terminal can be transferred via the first path through which communication is performed using the calculated bandwidth,
   As a result of the determination, when data transmitted / received by the terminal cannot be transferred via the first path, a second path different from the first path is determined based on the resource management information,
   The first and second edge nodes are set so that data transmitted and received by the terminal is transferred through the second path using the calculated bandwidth. Network system.
5. The network system according to claim 1,
   The network manager
   From the terminal management server, obtain information indicating a heavy user that is the terminal that transmits and receives the amount of data exceeding a predetermined condition,
   The data transmitted and received by the heavy user indicated by the acquired information is set to the first edge node or the second edge node so as to be transferred by a path other than the path in which communication is performed. Network system.
6. The network system according to claim 1,
   The network manager
   The number of terminals in the terminal state acquired a predetermined number of times is stored in the memory,
   Based on the number of terminals in the stored terminal state, calculate a statistical value indicating a change between the number of terminals in the first state and the number of terminals in the second state;
   A network system characterized in that, based on the statistical value, a bandwidth reserved for the terminal to communicate via a path is calculated for each terminal state.
7. A management method by a network system for transferring data transmitted and received by a terminal,
   The network system is connected to a first edge node that accommodates the terminal, a terminal management server that holds information on the terminal, a network manager connected to the terminal management server, and the first edge node. A second edge node,
   Data transmitted and received by the terminal is transferred via a path between the first edge node and the second edge node;
   The terminal takes one of a plurality of terminal states including a first state in which the terminal transmits / receives only control data and a second state in which the terminal transmits / receives data other than the control data,
   The network manager
   A processor and a memory;
   In each of the terminal states, the terminal has band information including a band reserved for the terminal to communicate via the path;
   The method
   The processor obtains terminal status information of the terminal from the terminal management server,
   Based on the number of terminals in the first state and the number of terminals in the second state indicated by the information acquired from the terminal management server by the processor, and the bandwidth information, the terminal Calculating the bandwidth reserved for communication via
   The management method, wherein the processor sets the first edge node and the second edge node to transfer data transmitted / received by the terminal according to the calculated bandwidth.
8. The management method according to claim 7,
   The band information includes an identifier indicating a business operator to which the terminal belongs,
   The terminal status information of the terminal includes an identifier of a business operator to which the terminal belongs,
   In the method, the processor includes the number of terminals in the first state, the number of terminals in the second state, the identifier of the operator, and the bandwidth information indicated by the information acquired from the terminal management server. And a bandwidth that is reserved for the terminal to communicate via a path.
9. The management method according to claim 7 or 8,
   The terminal state includes a state of a terminal for which network service is provided,
   The network manager is connected to an application server that provides the network service;
   The method
   The processor obtains the number of the terminals to which the network service is provided from the application server;
   Based on the number of terminals provided with the network service acquired by the processor from the application server, the terminal status and the number of terminals acquired from the terminal management server, and the bandwidth information, the terminal passes the path. A management method characterized by calculating a bandwidth reserved for communication via a network.
10. The management method according to claim 7,
    The network system includes at least one relay node connected to the first edge node and the second edge node;
    The network manager has resource management information indicating a usable bandwidth between each of the first edge node, the second edge node, and the relay node;
    The method
    Based on the resource management information, the processor determines whether the data transmitted / received by the terminal can be transferred via the first path through which communication is performed using the calculated bandwidth. And
    As a result of the determination, if the data transmitted / received by the terminal cannot be transferred via the first path, the processor determines a second path different from the first path based on the resource management information. Decide
    The processor sets the first edge node and the second edge node to transfer data transmitted / received by the terminal through the second path using the calculated bandwidth. A management method characterized by that.
11. The management method according to claim 7,
    The method
    The processor acquires, from the terminal management server, information indicating a heavy user that is the terminal that transmits and receives the data in an amount exceeding a predetermined condition,
    The processor sets the first edge node or the second edge node so that the data transmitted / received by the heavy user indicated by the acquired information is transferred by a path other than the path in which communication is performed. A management method characterized by:
12. The management method according to claim 7,
    The method
    The processor stores the number of terminals in the terminal state acquired a predetermined number of times in the memory,
    The processor calculates a statistical value indicating a change between the number of terminals in the first state and the number of terminals in the second state based on the number of terminals in the stored terminal state. ,
    The management method, wherein the processor calculates, for each terminal state, a bandwidth reserved for the terminal to communicate via a path based on the statistical value.
13. A network manager provided in the network system,
    The network system includes a first edge node that accommodates the terminal, a terminal management server that holds information on the terminal, and a second edge node connected to the first edge node,
    Data transmitted and received by the terminal is transferred via a path between the first edge node and the second edge node;
    The terminal takes one of a plurality of terminal states including a first state in which the terminal transmits / receives only control data and a second state in which the terminal transmits / receives data other than the control data,
    The network manager
    Connected to the terminal management server,
    A processor and a memory;
    In each of the terminal states, the terminal has band information including a band reserved for the terminal to communicate via the path;
    Obtaining terminal status information of the terminal from the terminal management server,
    The terminal communicates via a path based on the number of terminals in the first state and the number of terminals in the second state indicated by the information acquired from the terminal management server and the bandwidth information. Calculating the bandwidth reserved for
    A network manager configured to set the first edge node and the second edge node to transfer data transmitted / received by the terminal according to the calculated bandwidth.
14. The network manager according to claim 13, comprising:
    The band information includes an identifier indicating a business operator to which the terminal belongs,
    The terminal status information of the terminal includes an identifier of a business operator to which the terminal belongs,
    The network manager is based on the number of terminals in the first state, the number of terminals in the second state, the identifier of the operator, and the bandwidth information indicated by the information acquired from the terminal management server. And calculating a bandwidth reserved for the terminal to communicate via a path.
15. The network manager according to claim 13 or 14, comprising:
    The terminal state includes a state of a terminal for which network service is provided,
    The network manager
    Connected to an application server providing the network service,
    Obtaining the number of the terminals provided with the network service from the application server;
    The terminal communicates via a path based on the number of terminals provided with the network service acquired from the application server, the terminal status and the number of terminals acquired from the terminal management server, and the bandwidth information. A network manager characterized by calculating a bandwidth reserved for the purpose.

Images