TWI644544B - Method for increasing capacity of internet protocol private branch exchange system and system using the same - Google Patents

Abstract

The invention provides a network telephone switch virtualization capacity expansion system and method, which refers to the rapid deployment of a switch system by using container virtualization technology. The administrator can adjust the switch system architecture via the web page and use the automatic transfer phone mechanism to provide dynamic load balancing of the system. Thereby, the usage rate of the system hardware resources can be increased, and the communication service quality of the system can be improved.

Description

Network telephone switch virtualization capacity expansion system and method

The present invention relates to a capacity expansion system and method, and more particularly to an Internet Protocol - Private Branch Exchange (IP PBX) virtualization capacity expansion system and method.

In the traditional technology, the early use of stacked physical communication switches as a method of expanding the communication usage of a single network communication switch system. With the gradual maturity of virtualization technology, VoIP service providers can build multiple virtual machines in a single physical host to reduce hardware costs and expand the communication usage of a single communication system through effective shared resource sharing. purpose.

However, most service providers use virtualized technology to build virtual environments. This method requires the guest operating system to be attached to the hypervisor, so the system resources cannot be used effectively. . In a virtual network communication switch environment of a physical host, when the load of one virtual machine is high, more resources can be provided to the virtual machine with high load by configuring other physical host resources. However, when building a virtual machine, it takes a lot of basic system resources, and when a physical host resource can no longer be allocated to a virtual machine and a virtual machine is expanded, the virtual machine can no longer be adjusted without adding additional hardware resources. The method of machine resources allows the system to provide more hardware resources to the overloaded virtual machine, so it can not effectively reduce the load on the communication system.

It can be seen that the IP PBX virtualization technology system still has the above-mentioned functional deficiencies, which is not a good design, and needs to be improved to provide systems and methods with high scalability and mobility. Enterprise network communication switches have better communication service quality.

In view of the shortcomings derived from the above-mentioned conventional methods, the inventors of the present invention have improved and innovated, and after years of painstaking research, finally successfully developed the IP PBX virtualized capacity expansion system and method of the present invention.

The invention provides an IP PBX virtualized capacity expansion system, which comprises a switch core container cluster, a container cluster management module, a monitoring module, a web server, a database server and a redirection server. The switch core container cluster includes a plurality of switch core containers, wherein the foregoing switch core containers individually provide a call service to a plurality of phones. The container cluster management module establishes a communication architecture of the aforementioned switch core container and distributes the phone to the aforementioned switch core container. The monitoring module is responsible for monitoring the resource usage of the core container of the foregoing switch, processing the traffic data of the phone, and changing the core container of the switch to which each phone belongs. The web server provides a management interface for managing the aforementioned switch core containers and phones. The database server is responsible for storing the traffic volume of the aforementioned switch core container and the aforementioned phone to which the foregoing phone belongs. The redirection server is responsible for processing the received Session Initiation Protocol (SIP) packet to direct it to one of the aforementioned switch core containers corresponding to the phone number of the SIP packet. In this way, the deployment time of the overall telephone communication system of a large enterprise can be saved, the enterprise switch can be uniformly managed, and the hardware and maintenance cost of the switch can be reduced.

The invention further provides an IP PBX virtualization capacity expansion method, which is suitable for the foregoing system, including the steps of setting a communication switch, adding a new phone step, and a phone migration step. The communication switch step is set to perform the aforementioned communication architecture for establishing the aforementioned switch core container. The Add Phone step is used to add a new phone to the aforementioned system. The phone relocation mechanism step is used to transfer the phone between the core containers of the switch according to the resource usage situation of the foregoing switch core container. In this way, the balance of system load can be achieved, and the quality of communication service of the enterprise can be provided.

The above described features and advantages of the invention will be apparent from the following description.

The present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It is understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

Please refer to FIG. 1 , which is a schematic structural diagram of an IP PBX virtualized capacity expansion system according to the present invention. As shown in FIG. 1 , the system 100 includes a switch core container cluster 1, a container cluster management module 2, a monitoring module 3, a web server 4, a database server 5, and a redirection server 6. The switch core container cluster 1 includes a plurality of switch core containers 11, 12, ..., 1N (N is a positive integer), wherein each switch core container 11, 12, ..., 1N provides a call service to a plurality of phones (not shown) . The container cluster management module 2 establishes a communication architecture of the switch core containers 11, 12, ..., 1N, and distributes the aforementioned phones to the switch core containers 11, 12, ..., 1N. The monitoring module 3 is responsible for monitoring the resource usage of the switch core containers 11, 12, ..., 1N, processing the traffic data of the phone, and changing the switch core containers 11, 12, ..., 1N to which the aforementioned phones belong. The web server 4 provides a management interface for managing the switch core containers 11, 12, ..., 1N and the aforementioned phones. The database server 5 is responsible for storing the user data of the phone, the switch core containers 11, 12, ..., 1N to which the phone belongs, and the traffic of the phone. The redirection server 6 is responsible for processing the received Session Initiation Protocol (SIP) packet to direct it to one of the switch core containers 11, 12, ..., 1N corresponding to the phone number of the SIP packet.

Each of the above-described modules of FIG. 1 may include a plurality of sub-modules, respectively, depending on the purpose of the invention, and will be described below with reference to FIG.

Please refer to FIG. 2 , which is a schematic diagram of internal sub-modules of each module shown in FIG. 1 . As shown in FIG. 2, the container cluster management module 2 includes a container management sub-module 21 and a communication material management sub-module 22. The container management sub-module 21 is responsible for receiving the container setting request of the web server 4 to add, modify, and delete the switch core containers 11, 12, ..., 1N accordingly. The communication data management sub-module 22 is responsible for receiving the communication construction data setting request of the web server 4, and modifying the construction materials of the switch core containers 11, 12, ..., 1N correspondingly, and allocating the new telephone when adding a new telephone Add a new phone to one of the switch core containers 11, 12, ..., 1N.

The monitoring module 3 includes a container monitoring sub-module 31, a data processing sub-module 32, and a load control sub-module 33. In summary, the function of the monitoring module 3 is to monitor the resource usage status of the switch core container cluster 1, to process the traffic data of each phone, and to accommodate the transfer of the phone between the switch core containers 11, 12, ..., 1N. Specifically, the load control sub-module 33 is responsible for executing a phone relocation mechanism to replace the switch core containers 11, 12, ..., 1N to which the phone belongs. The container monitoring sub-module 31 is responsible for monitoring the operation status and resource usage of each switch core container 11, 12, ..., 1N, and correspondingly providing the communication data management sub-module 22, the load control sub-module 33, and the web server. 4. The data processing sub-module 32 is responsible for processing the traffic information of each call, and storing the traffic information in the database server 5.

Through the function operation of each sub-module in the monitoring module 3, the manager can observe the load situation of the entire system 100 through the web interface, and store the processed traffic data and the changed phone location in the database server 5, In order for a new telephone call to be made through the redirection server 6, the correct location of the dialed telephone is found.

Referring again to FIG. 1, the web server 4 functions to send a setting request to the container management sub-module 21 to request the system 100 to establish a communication architecture, and at the same time obtain the resource usage of the container monitoring sub-module 31 to facilitate querying the complete system 100. load. The web server 4 is also responsible for transmitting the new phone data to the communication data management sub-module 22 to balance all of the phones of the system 100.

The redirection server 6 is responsible for the packet forwarding function. After receiving the phone call, the system checks the phone number of the received SIP packet, and queries the database server 5 for the switch core container 11 to which the phone corresponding to the phone number belongs. 12, ..., 1N, thereby directing the packet to the core container switch core containers 11, 12, ..., 1N to which the phone number belongs, so that the system 100 can successfully establish a basic call.

The container management sub-module 21 of the present invention is responsible for receiving the communication switch setting request of the web server 4, and adding, modifying, and deleting the switch core containers 11, 12, ..., 1N, thereby constructing the completeness according to the customer's requirements. Telephone communication environment.

The communication data management sub-module 22 is responsible for receiving the set user data request of the web server 4, and assigning the initial subordinate switch core container of the phone when adding the phone data. When the system 100 is initially set up, the communication data management sub-module 22 distributes the phone data evenly to each of the switch core containers 11, 12, ..., 1N. When the system 100 starts operating, the communication data management sub-module 22 According to the information of the container monitoring sub-module 31, the newly added phone data is distributed to the currently-switched switch core containers 11, 12, ..., 1N.

The container monitoring sub-module 31 is responsible for monitoring the operation status and resource usage of each switch core container 11, 12, ..., 1N in the switch core container cluster 1, and the administrator can query the container monitoring sub-module 31 to collect through the web interface. Container information to. The aforementioned container information includes container CPU usage, memory usage, and call history. The container monitoring sub-module 31 is also responsible for providing container information to the communication data management sub-module 22 and the load control sub-module 33.

The data processing sub-module 32 is responsible for monitoring the traffic volume of each telephone, and storing the traffic information of each call in the database server 5, the traffic information includes the caller, the callee, the call start time, and the total call. Time and so on.

The function of the load control sub-module 33 is to receive the container information sent by the container monitoring sub-module 31, and find out the heavy-duty switch core container (for example, the switch core container 11) through the container information, and according to the data processing sub-module 32. The traffic information stored in the database server 5 calculates the load ratio of each phone belonging to the switch core container 11, thereby finding out the switch core container that needs to be transferred (hereinafter referred to as the transfer phone) and the light load. (For example, the switch core container 12), and modify the phone data of the SIP communication server to be changed, and the location of the phone stored in the database server 5.

Therefore, when the administrator completes the setting of the customer requirement through the web server 4, the communication architecture of the switch core container inside the system 100 can be automatically installed and established. In this case, the deployment time of the overall telephone communication system of the large enterprise can be saved, the enterprise switch can be uniformly managed, and the hardware and maintenance cost of the switch can be reduced.

The present invention further provides an IP PBX virtualized capacity expansion method, which is suitable for the system 100 shown in FIG. 1, and includes the steps of setting a communication switch, adding a new phone, and the step of moving the phone. The communication switch step is set to perform the aforementioned communication architecture for establishing the aforementioned switch core container. The Add Phone step is used to add a new phone to the aforementioned system. The phone relocation mechanism step is used to transfer the phone between the core containers of the switch according to the resource usage situation of the foregoing switch core container. The details of each step of the foregoing method will be described below with reference to FIGS. 1 and 2 based on FIGS. 3 to 6.

Please refer to FIG. 3, which is a flow chart of a step of setting a communication switch of an IP PBX virtualized capacity expansion method according to the present invention. First, in step S10, a predetermined number of simultaneous calls and a total number of predetermined telephones can be obtained from the management interface. In an embodiment, the administrator can use the web server 4 to set the customer demand (ie, the predetermined number of simultaneous calls and the total number of predetermined phones), and send a setting request to the container management sub-module 21 through the web server 4 to trigger. Step S10, but the present invention is not limited thereto.

Next, in step S11, the container management sub-module 21 correspondingly calculates the first number of switch core containers that need to be established. In step S12, the container management sub-module 21 queries the system 100 for the presence of a switch core container in operation. That is, before starting the setting, the container management sub-module 21 will query the system 100 whether there is a switch core container that has been established and started to operate.

If the system 100 has not yet established any switch core container, in step S14, the container management sub-module 21 will start to establish the switch core container to achieve the purpose of automatically constructing the entire telephone communication system architecture at the beginning.

On the other hand, if the system has established the switch core container, in step S13, the container management sub-module 21 compares the first quantity (ie, the number of switch core containers to be established) with the second of the already operated switch core containers. The number (that is, the number of switch core containers that have been running) is the same. The second number of switch core containers can be maintained if the same representative does not need to make any changes to the second number of switch core containers. On the contrary, the container management sub-module 21 determines in step S15 whether the first number is greater than the second number.

If the number of switch core containers that need to be established is greater than the number of established switch core containers, it means that the number of core containers of the switch needs to be augmented. Therefore, the container management sub-module 21 continues to step S16 to add a new switch core container.

Conversely, if the number of switch core containers that need to be established is smaller than the number of established switch core containers, you need to delete the redundant switch core containers. Therefore, in step S17, the container management sub-module 21 selects the switch core container to be deleted, and simultaneously transfers the phone served by the switch core container to be deleted to other un-removed switch core containers. Next, in step S18, the container management sub-module 21 deletes the switch core container to be deleted.

Thereby, when the administrator completes setting the customer demand through the web server 4 (for example, the predetermined number of simultaneous calls and the total number of predetermined telephones), the communication architecture of the switch core container inside the system 100 can be automatically installed and established. In this case, the deployment time of the overall telephone communication system of the large enterprise can be saved, the enterprise switch can be uniformly managed, and the hardware and maintenance cost of the switch can be reduced.

Please refer to FIG. 4 and FIG. 5 , wherein FIG. 4 is a flow chart of a new phone of the IP PBX virtualized capacity expansion method according to the present invention, and FIG. 5 is a processing of the IP PBX virtualized capacity expansion method according to the present invention. Flow chart of the steps of the switch core container.

In step S20, the administrator can use the web server 4 to establish the phone data, and send a request for adding a new phone to the communication data management sub-module 21 via the web server 4 to add a new phone, but the present invention is not limited thereto.

After receiving the new phone request sent by the web server 4, the communication data management sub-module 22 proceeds to step S21 to perform the allocation of the switch core container to which the phone belongs. Specifically, in step S210, the communication material management sub-module 22 obtains the basic communication data of the newly added phone from the management interface, and correspondingly sends a request to the container management sub-module 21 to obtain the load situation of the switch core container. Moreover, in step S211, the communication material management sub-module 22 checks whether the number of new telephones is one. If only one new phone is added, step S215 is performed to allocate the new phone to the lightest switch core container, and the allocation information is stored in the database server 5 in step S214 (for example, a new phone and a station will be added) The correspondence between the attached switch core containers is stored in the database server 5).

On the other hand, when the number of new telephones is not 1, the communication data management sub-module 22 uses the number pattern of the telephone (for example, the length of the number and the number or letter at the beginning of the number) to divide the telephone into plurals in step S212. Groups, and in step S213, the groups are sequentially allocated from large to small according to the size of the group to the switch core container whose load situation is light to heavy. Thereafter, in step S214, the allocation information is stored in the database server 5 in step S214 (for example, the correspondence between the phone and the switch core container is stored in the database server 5).

Then, in step S22, the communication material management sub-module 22 adds the phone data of the newly added phone to the switch core container to which the new phone is assigned.

Thereby, the system 100 can achieve load balancing effect when a new phone appears.

Please refer to FIG. 6, which is a flowchart of a process for processing a transfer phone according to an IP PBX virtualized capacity expansion method according to the present invention.

In step S30, the load control sub-module 33 continues to send a request to the container monitoring sub-module 21 to obtain the load situation of the switch core container. Further, in step S31, if the first container in the switch core container exceeds the set load value, the load control sub-module 33 acquires the traffic data of the phone established in the first container from the database server 5.

In step S32, the load control sub-module 33 calculates the phone load ratio of the first container by using the traffic data of the phone of the first container to find a to-be-transferred phone, for example, the phone that most frequently sends and receives calls. Specifically, the reason why the load situation is often heavy is that the phone frequently makes/receives calls and long-time calls, so the traffic ratio of each call can be calculated and calculated using the traffic data such as the number of calls and each call.

In step S33, the load control sub-module 33 queries the call state of the to-be-transferred phone. In step S34, the load control sub-module 33 determines whether the to-be-transferred phone is in a call state, and the load control sub-module 33 continues to wait for a preset time (for example, 10 seconds) in step S35 to avoid interruption of the online call. . After that, it can return to step S33 to query again whether the to-be-transferred telephone is in a call state.

After the call to be transferred ends the call state, in step S36, the load control sub-module 33 queries whether the system 100 has resources for establishing a new switch core container. If so, the load control sub-module 33 establishes a new switch core container in step S37, and then changes the switch core container to which the phone in the database server 5 belongs in step S38 and changes the phone construction in the core container of the switch. Data (for example, the phone to be transferred can be transferred to the new switch core container and the database server 5 is updated accordingly) so that the redirect server 6 can direct the next call to the phone to the correct switch core. container.

On the other hand, if the system 100 does not have the resources to establish a new switch core container, the load control sub-module 33 continues to change the switch core container to which the phone in the database server 5 belongs and change the switch core container in step S38. The internal telephone construction data (for example, transferring the to-be-transferred telephone to the switch core container with a light load condition and updating the database server 5), so that the redirection server 6 can direct the next call to the telephone of the telephone The correct switch core container.

As apparent from the above, the present invention has been directed to providing a method of automatically relocating a telephone. By this method, the system 100 dynamically replaces the switch core container to which the heavy-duty phone belongs. In this way, in the case of limited hardware resources, the burden of each switch core container can be alleviated to achieve the purpose of system load balancing, and provide a system with more stable and better communication service quality.

In summary, the present invention provides an IP PBX virtualization capacity expansion system and method, which can be implemented by using a Docker container virtualization management tool. Compared with the conventional method of stacking communication switches and the method of expanding the system capacity by using the full virtualization technology to build a virtual machine environment, the present invention provides a communication system that utilizes host resources more effectively, thereby enabling enterprises and service providers to save more. The hardware cost of a communication system switch.

In addition, the present invention provides a single network communication switch system that can be used to support the entire communication environment of a large enterprise or a large organization. The administrator can set up through the management interface of the web server, and the system of the present invention automatically establishes the communication system architecture required by the enterprise to save the deployment time of the telephone communication system. The administrator can also use the management interface to add/delete resources and communication user data configured in the system to the core container of the switch, thereby making the system of the present invention highly scalable and unified. This saves the maintenance costs of large telephone companies that need to manage different brands of VoIP switches.

Moreover, in view of the limitation of the basic resources for constructing the core container of the communication switch, the method provided by the present invention can transmit the load to the load with a relatively heavy load (for example, a high traffic volume) through a limited transfer of hardware resources. The switch core container to ease the burden of a single switch core container. Thereby, the system of the present invention can achieve the effect of load balancing, thereby improving the performance of a single large enterprise communication delivery system.

Although the present invention has been disclosed in the above embodiments, it is not intended to limit the present invention, and any one of ordinary skill in the art can make some changes and refinements without departing from the spirit and scope of the present invention. The scope of the invention is defined by the scope of the appended claims.

100‧‧‧ system

1‧‧‧Switch core container cluster

2‧‧‧ Container Cluster Management Module

21‧‧‧ Container Management Sub-module

22‧‧‧Communication Data Management Sub-module

3‧‧‧Monitoring module

31‧‧‧ Container Monitoring Sub-module

32‧‧‧Data Processing Sub-module

33‧‧‧Load Control Submodule

4‧‧‧Web server

5‧‧‧Database server

6‧‧‧Re-directed server

11, 12, ..., 1N‧‧‧ switch core container

S10~S18, S20~S22, S210~S215, S30~S38‧‧‧ steps

1 is a schematic structural diagram of an IP PBX virtualized capacity expansion system according to the present invention; FIG. 2 is a schematic diagram of an internal sub-module of an IP PBX virtualized capacity expansion system and method according to the present invention; FIG. 3 is an IP PBX virtualization capacity according to the present invention; FIG. 4 is a flow chart of a new phone step of an IP PBX virtualized capacity expansion method according to the present invention; FIG. 5 is a process for processing an IP PBX virtualized capacity expansion method according to the present invention; The flow chart of the subordinate location step; FIG. 6 is a step of processing the transfer phone of the IP PBX virtualized capacity expansion method according to the present invention.

Claims (7)

A network telephone switch virtualization capacity expansion system, comprising: a switch core container cluster, comprising a plurality of switch core containers, wherein the switch core containers individually provide a call service to a plurality of phones; a container cluster management module is established a communication architecture of the core containers of the switches, and allocating the phones to the core containers of the switches; a monitoring module for monitoring resource usage of the core containers of the switches, processing traffic information of the phones, and Transforming the core container of the switch to which the phone belongs; a web server providing a management interface, wherein the management interface is used to manage the switch core containers and the phones; and a database server is responsible for storing the phones User data, the core container of the switch to which the phones belong, the traffic of the phones; and a redirection server responsible for processing the received Session Initiation Protocol (SIP) packets to direct them The core container of the switch corresponding to the phone number of the SIP packet The container cluster management module is configured to: obtain a predetermined number of simultaneous calls and a total number of predetermined phones from the management interface, and calculate a first quantity of the core containers to be established correspondingly; and query whether the system is There are some switch core containers in operation. If the system has not yet established any switch core containers, the switch core containers are started to be established. Otherwise, if the system has established the switch core containers, the first one is compared. Whether the quantity is the same as a second quantity of the core containers of the switches that have been run, and if the same, maintaining the second quantity of the core containers of the switches, and vice versa, determining whether the first quantity is greater than the second quantity, and if so Start adding at least one new switch core container. If not, select the switch core containers to be deleted, and at the same time transfer the phones served by the switch core containers to be deleted to other switch cores that are not deleted. The container is then deleted from the core containers of the switch to be deleted. The system of claim 1, wherein the container cluster management module comprises: a container management sub-module, configured to receive a container setting request of the web server, to add, modify, and delete the corresponding a switch core container; and a communication data management sub-module, configured to receive a communication configuration data setting request of the web server, and correspondingly modify the construction materials of the core containers of the switch, and allocate the new phone when adding a new phone Add a new phone to one of the core containers of these switches. The system of claim 2, wherein the monitoring module comprises: a load control sub-module, configured to perform a phone relocation mechanism to replace the switch core containers to which the phones belong; a container monitoring The sub-module is responsible for monitoring the operation status of the core container of each switch and the resource usage situation, and correspondingly providing the communication data management sub-module, the load control sub-module and the web server; A data processing sub-module is responsible for processing the traffic information of each call and storing the traffic information in the database server. The system of claim 2, wherein when the communication data management sub-module modifies the construction materials of the core containers of the switches, the database server is updated accordingly. A method for expanding a virtual capacity of a network telephone switch, which is suitable for the system as described in claim 1, comprising: a step of setting up a communication switch for establishing the communication architecture of the core containers of the switches, including: The management interface obtains a predetermined number of simultaneous calls and a total number of predetermined telephones, and correspondingly calculates a first number of the core containers of the switches to be established; and queries whether the system has the switch core containers in operation, if the system If any switch core containers have not been established, the switch core containers are started to be established. If the switch core containers are already established, the first quantity is compared with a second quantity of the switch core containers that have been operated. If the same, the second quantity of the core containers of the switches is maintained. Otherwise, it is determined whether the first quantity is greater than the second quantity. If yes, at least one new switch core container is added. If not, the selected one is deleted. The core of the switch, and at the same time the switch cores that will be removed The phones served by the container are transferred to other switch core containers that are not deleted, and the switch core containers to be deleted are deleted; a new phone step for adding a new phone to the system; and a phone relocation mechanism step for transferring the phones between the switch core containers according to resource usage conditions of the switch core containers. The method of claim 5, wherein the adding a phone step comprises: obtaining basic communication data of the new phone from the management interface, and correspondingly transmitting a request for obtaining a load situation of the core containers of the switches; Check whether the number of the newly added phones is 1, and if so, assign the new phone to one of the core containers of the switch with the lightest load condition, and connect the new phone to one of the core containers of the switch to which the switch belongs. Corresponding relationship is stored in the database server; if not, the number of the phone is used to divide the phones into a plurality of groups, and the groups are sequentially arranged according to the size of the groups Large to small, allocated to the switch core containers of the load situation from light to heavy, and store the correspondence between the phones and the core containers of the switches to the database server; and the new phone The phone core containers assigned to the switch add the phone data of the new phone. The method of claim 5, wherein the processing the transferring the phone comprises: continuously transmitting a request for obtaining a load condition of the core containers of the switches; if a first container of the switch core containers exceeds a set load a value obtained from the database server to obtain traffic data of the phones established in the first container; Calculating, by using the traffic data of the phones of the first container, the phone load ratio of the phones of the first container to find a phone to be transferred; querying whether the to-be-transferred phone is in a call state, and if so, waiting for the phone After the call is terminated, the system queries whether the system has a resource for establishing a new switch core container. If yes, the new switch core container is established, and the to-be-transferred phone is transferred to the new switch core container. And updating the database server accordingly; and if the system has no available resources, transferring the to-be-transferred phone to another of the switch core containers that are lightly loaded, and updating the database server .