System and method for correcting private branch exchange settings

Abstract

To provide a technique to make it possible to achieve efficiency and optimization with respect to settings including operational settings in accordance with the customer's environment when constructing and operating a private branch exchange (PBX) in the customer's environment.SOLUTION: A private branch exchange (PBX) set value correction method is for correcting a setting value related to a PBX. The method has, as a step to be executed by a computer, a step (S103) in which the computer monitors an operational sequence of the PBX in a customer's environment and acquires monitoring information of the operational sequence and steps (S105, S106) in which the computer corrects an operational value of the setting information of the PBX in the customer's environment on the basis of a comparison (S104) between the operational sequence based on the monitoring information and a model sequence specified in advance.SELECTED DRAWING: Figure 4

Description

[Technical Field]

[0001] The present invention relates to a technique relating to a private branch exchange (PBX). [Background technology]

[0002] Systems including PBX (sometimes referred to as PBX systems) are increasingly being introduced that use IP (Internet Protocol) networks (sometimes referred to as IP-PBX), and even more so, PBXs that use cloud computing systems (sometimes referred to as cloud PBX). IP-PBXs are configured using IP networks built within the customer's environment. Cloud PBXs are configured on cloud computing systems.

[0003] An example of prior art is Japanese Patent Application Laid-Open Publication No. 2019-16923 (Patent Document 1). Patent Document 1 describes, as an IP-PBX system and an IP-PBX configuration automation method, that "automates the setting and registration of configuration information for a SIP (Session Initiation Protocol)-GW (gateway) during installation work," and that "analyzes an error response message returned as a response to a REGISTER request message sent to a SIP server without authentication information, identifies the communication service provider of the SIP server based on parameter information added to the error response message, and generates authentication configuration information that matches the specifications of the identified communication service provider." [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Publication No. 2019-16923 Summary of the Invention [Problem to be solved by the invention]

[0005] Prior art PBX systems lack the functionality to improve efficiency and optimization, or to assist with configuration work, in the broad sense of configuration required for building and operating a PBX in a customer environment, such as a system including a company's LAN, gateway, and telephone terminals. Even if prior art PBX systems possess such functionality, it is insufficient. Note that the broad sense of configuration includes not only the initial settings made during construction, but also settings related to operation in accordance with the customer environment. For ease of explanation, operational settings may be referred to as operational settings. Furthermore, parameter values ​​for operational settings may be referred to as operational values ​​or operational setting values.

[0006] Even when a certain PBX specification is used as the standard, operational values ​​may differ for each customer environment, or may fluctuate within the customer environment. For example, each customer environment may use a LAN or a WAN as the connection method to the PBX. Furthermore, each customer environment may have different latency times in communications based on protocols such as SIP. PBX systems of the prior art example do not have a mechanism that can efficiently accommodate these operational settings. PBX systems of the prior art example do not have the functionality to set efficient and optimal operational settings as initial settings when building a PBX-based system for each customer environment. Furthermore, PBX systems of the prior art example do not have the functionality to adjust operational settings to suit the customer environment after building and starting operation.

[0007] As a result, the PBX system of the prior art example requires a lot of effort, time, and cost for manual setup work, and there is room for improvement in order to achieve efficient and suitable setup work and operation.

[0008] The purpose of the present disclosure is to provide technology related to the above-mentioned PBX that can achieve efficiency and optimization in settings, including operational settings tailored to the customer environment, when building and operating a PBX in a customer environment, thereby reducing the effort, time, cost, etc. required for manual configuration work and enabling efficient and suitable configuration work and operation.

[0009] The technology of Patent Document 1 enables external line connections by automatically selecting a carrier from the contents of a SIP message and configuring data according to that carrier when connecting a SIP gateway to a public network. This technology reads the different specifications for each carrier contained in a REGISTER request message and automatically configures the SIP-GW. However, this method of determining from a response message can only determine an abnormality in the interface between the terminal ends, and cannot correct settings other than those between the ends, such as network delay. [Means for solving the problem]

[0010] A representative embodiment of the present disclosure has the following configuration: A private branch exchange setting value correction method of the embodiment is a method for correcting setting values ​​related to a private branch exchange (PBX), and includes, as steps executed by a computer, a step of the computer monitoring an operation sequence of the PBX in a customer environment and acquiring monitoring information of the operation sequence, and a step of the computer correcting operation values ​​of the setting information of the PBX in the customer environment based on a comparison between the operation sequence based on the monitoring information and a predefined model sequence. [Effects of the Invention]

[0011] According to a representative embodiment of the present disclosure, with regard to the technology related to the above-mentioned PBX, when constructing and operating a PBX in a customer environment, it is possible to realize efficiency and optimization of settings, including operational settings according to the customer environment, and to support the setting work, thereby reducing the effort, time, cost, etc. of the setting work and realizing efficient and suitable setting work and operation. Problems, configurations, effects, etc. other than those described above will be described in the description for carrying out the invention. [Brief explanation of the drawings]

[0012] [Figure 1] 1 shows an example of the configuration of the entire system including the PBX setting value correction system according to the first embodiment. [Figure 2] 2 shows an example of a functional block configuration of a PBX system in the PBX setting value correction system according to the first embodiment. [Figure 3] In the first embodiment, an example of the configuration of a server computer system of a PBX system is shown. [Figure 4] In the first embodiment, the processing flow of the PBX system is shown. [Figure 5] FIG. 10 shows an explanatory diagram relating to setting of operation information in step S102 in the first embodiment. [Figure 6] In the first embodiment, an explanatory diagram regarding data collection in step S103 and operation sequence check in step S104 will be shown. [Figure 7] In the first embodiment, an explanatory diagram regarding a comparison between a model sequence and an operation sequence is shown. [Figure 8] In the first embodiment, an explanatory diagram regarding the determination of the correction value in step S105 and the correction action in step S106 will be shown. [Figure 9] In the first embodiment, a detailed example of the process flow regarding the determination of the correction value in step S105 will be shown. [Figure 10] FIG. 10 is an explanatory diagram regarding DB update in step S107 in the first embodiment. [Figure 11] In the first embodiment, an example of the configuration of a parameter sheet is shown. [Figure 12]In the first embodiment, an example of the configuration of the operation information DB will be shown. [Figure 13] In the first embodiment, an example of the configuration of the operation sequence log DB will be shown. [Figure 14] In the first embodiment, an example of the configuration of the operational setting value DB will be shown. [Figure 15] In the first embodiment, an example of the configuration of the setting value correction DB will be shown. [Figure 16] In the first embodiment, an example of the configuration of the model sequence DB will be shown. [Figure 17] In the first embodiment, an example of the configuration of the statistical information DB will be shown. [Figure 18] In the first embodiment, an example of a screen for inputting operational information is shown. [Figure 19] In the first embodiment, specific examples of data etc. used when initializing the operational values ​​will be shown. [Figure 20] In the first embodiment, specific examples of data etc. used when adjusting operational values ​​will be shown. [Figure 21] In the first embodiment, an example of a screen for confirming an operational value is shown. [Figure 22] In the first embodiment, examples of operation sequences before and after correction of operation values ​​and statistical information before and after updating are shown. [Figure 23] 1 shows an example of the overall configuration of a system according to a first modification of the first embodiment. [Figure 24] In the first modification, an example of the functional block configuration of a PBX system is shown. [Figure 25] In Modification 1, an example of the configuration of the operation value determination DB is shown. [Figure 26] In the first modification, an explanatory diagram regarding the setting of the operational information in step S102 is shown. [Figure 27] 10 shows an example of the overall configuration of a system according to a second modification of the first embodiment. [Figure 28] 10 shows an overview of the functions in the third modification of the first embodiment. [Figure 29] 1 shows an example of the configuration of a system as a comparative example in comparison with the first embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0013] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In the drawings, identical parts are generally designated by the same reference numerals, and repeated explanations will be omitted. For the purpose of explanation, when describing processing by a program, the program, functions, processing units, etc. may be described as the main focus. However, the main focus of these hardware components is a processor, or a controller, device, computer, system, etc., configured with the processor, etc. The computer executes processing according to a program loaded into memory using resources such as memory and communication interfaces as appropriate, thereby realizing predetermined functions, processing units, etc. The processor may be configured with semiconductor devices such as a CPU / MPU or GPU. Processing is not limited to software program processing, and can also be implemented using dedicated circuits. Examples of the dedicated circuits that can be used include FPGAs, ASICs, CPLDs, etc.

[0014] The program may be pre-installed as data on the target computer, or may be distributed as data from a program source to the target computer. The program source may be a program distribution server on a communication network, or a non-transitory computer-readable storage medium, such as a memory card or disk. The program may be composed of multiple modules. Software including the program may be accompanied by a pre-designed data set (e.g., a database). The computer system may be composed of multiple devices. The computer system may be composed of a client-server system, a cloud computing system, an IoT system, etc. Various data and information may be composed of structures such as tables and lists, for example, but are not limited to these. Expressions such as identification information, identifiers, IDs, names, and numbers are interchangeable.

[0015] <Assignments, etc.> Here is some additional information on the issues. Traditionally, PBX systems have been constructed by specialized dealer installers. The operational conditions for PBX systems vary widely depending on the customer environment. The operational settings (i.e., configuration data and parameter values) of a PBX system differ depending on the user requirements of the customer environment. For example, differences in connection topology include using the PBX only within the customer's own LAN, using the PBX via a WAN, or using the PBX via the Internet. The required operational settings change depending on these user requirements, or in other words, the requirements and operational information that represent the desired operation for each customer environment. Therefore, the work of installers setting and adjusting operational settings to suit each customer environment requires a lot of effort, time, and cost.

[0016] Operational settings tailored to user requirements can change depending on the system configuration and operational configuration of the customer's environment, as well as changes in customer demand. Therefore, with current PBX systems, operational settings are left to the individual knowledge, experience, and skills of each installation company. For example, if someone with little knowledge or experience performs the operational settings, they may end up with inadequate settings. In such cases, customer support inquiries are made, which require manual analysis of the cause and setting changes. As a result, building and maintaining stable operation of a PBX system requires a great deal of time and effort.

[0017] When building and operating a PBX system tailored to a customer's environment, the PBX operational setting parameters are set based on factors such as the experience of the individual installer. Initial settings, including operational settings, are made during construction. However, after the PBX system is built and put into operation, there can be cases where the actual operational status of the customer's environment does not match or is inconsistent with the initial operational setting parameters. In such cases, the installer must visit the customer's environment and manually adjust the operational setting values.

[0018] In addition, the know-how for building and configuring the PBX system is accumulated by the individual construction company that carried out the setup, but the know-how is not shared between companies or individuals, making it difficult.

[0019] <Solutions, etc.> In consideration of the above-mentioned problems, the PBX setting value correction system and method according to the embodiment provide a function for performing configuration support and automatic adjustment for configuration / setting, including operational settings of a PBX system, which has traditionally been performed manually. The system and method according to the embodiment has a function for correcting operational values, which are operational setting parameter values, while taking into consideration the user requirements and actual operational status of each customer environment. This correction or adjustment function automatically determines suitable operational values ​​or correction values ​​so as to match and align the operational information and operational sequence corresponding to the user requirements and operational status of each customer environment, and updates the operational settings of the customer environment.

[0020] The PBX setting value correction system and method of the embodiment, which will be described in detail later, monitors an operational sequence including communication between a PBX system such as a server with PBX functionality and an external device such as a telephone terminal in a customer environment connected to the PBX system, and acquires and stores an operational sequence log as monitoring information.

[0021] The PBX setting value correction system and method of the embodiment compare and check the monitored operation sequence with a model sequence that is predefined as a model of a normal or standard operation sequence based on the PBX specifications. The system and method of the embodiment analyzes and determines discrepancies and differences between them. Based on the results of the comparison, the system and method of the embodiment corrects the operation setting parameter values ​​related to PBX usage in the customer environment, for example, to eliminate discrepancies between the model and operation or to reduce the differences.

[0022] As described above, the PBX setting value correction system and method according to the embodiment checks and confirms the operational sequence between the PBX system and external devices, and corrects the operational values ​​to match the operational conditions of each customer environment. This allows the setting of operational values ​​to match the operation of each customer environment to be achieved automatically with higher accuracy than before. As a result, the effort and time required for manual setup by the installer can be reduced.

[0023] Furthermore, the PBX setting value correction system and method of the embodiment targets multiple customer environments, aggregates the operational requirements (corresponding operational information), actual operational status (corresponding operational sequence logs), and operational setting parameter values ​​for each customer environment, and generates and stores statistical information related to them.When building a PBX system in a new customer's environment, the system and method of the embodiment can create and set optimal operational values ​​using the statistical information as the initial settings.This improves the accuracy of operational settings during construction and reduces problems after operation begins.

[0024] The PBX setting value correction method and system of the embodiment can be implemented by software such as a program inside the PBX system, and corresponding examples will be described, but are not limited to this. The method and system of the embodiment can also be implemented by software such as a program outside the PBX system or an external system, as will be shown in the modified examples described later.

[0025] The PBX setting value correction method and system of the embodiment will be described in particular as being implemented in a cloud PBX, but this is not limiting. As will be shown in the modified example described below, they can also be implemented in an IP-PBX. By using a cloud PBX as their base, the PBX setting value correction method and system of the embodiment can provide PBX setting value correction functionality for multiple customer environments. Furthermore, by using a cloud PBX as their base, the PBX setting value correction method and system of the embodiment can easily collect and aggregate data such as operational information, operational sequence monitoring information, and operational setting values ​​from multiple customer environments and generate statistical information related to them. This allows the method and system of the embodiment to use this statistical information to propose operational setting values ​​for each customer environment. In other words, the method and system of the embodiment can generate optimal operational values ​​using statistical information as initial operational values, for example, when building a PBX-based system for a new customer environment. This allows for optimal operation from the start, improves the accuracy of automatic adjustments, and reduces problems after operation begins.

[0026] <Comparative Example> 29 shows an example of the overall system configuration, including a PBX system 291 as a comparative example to the embodiment. This PBX system 291 is a cloud PBX configured on a cloud computing system such as a data center of a business operator. The PBX system 291 is configured with a server, a router, a database (DB), etc., and has at least a PBX function.

[0027] FIG. 29 shows customer environments A and B as examples of customer environments. Each customer environment has one or more bases, and each base has an external device 292 that uses a PBX. The customer environment is, for example, an organization such as a company and the computer systems that make up the organization. The bases are locations such as Tokyo and Osaka. The external device 292 can be a telephone terminal (e.g., an IP telephone), a router, a gateway, or other device. Note that the external device 292 is external to the PBX. The external device 292 can also be referred to as a PBX-using device. The external device 292 makes and receives calls to the PBX of the PBX system 291. The external device 292, which is the call source, and the external device 292, which is the destination, are connected via the PBX to make a call.

[0028] Each base may have a different computer system and may have a different external device 292 configuration. Each base may have a different PBX operation. For example, in customer environment A, the external device 292 at base A1 connects to the PBX using a LAN, and the external device 292 at base A2 connects to the PBX using a WAN. Communications QA1, QA2, QB1, and QB2 indicate communications between the external device 292 at each base and the PBX of the PBX system 291, in other words, operational sequences.

[0029] User U1, a configurator at a contractor, performs configuration work related to the use, construction, and operation of PBX system 1 for the customer environment he or she is responsible for. For example, configurator A at contractor A performs configuration work for customer environment A. User U1 configures data and information related to configuration, including operational settings for the PBX in the customer environment, for PBX system 1. For example, settings CA and CB indicate settings 2901, including operational settings for the PBX system for each customer environment, for PBX system 291 from each user U1's terminal 30. During configuration 2901, user U1 configures operational setting parameter values ​​that are considered based on the configuration of the customer environment. The required settings vary depending on the requirements of the customer environment. For example, the operational configuration, such as the connection type, may differ for each location.

[0030] For example, when communication between an external device 292 at site A1 and a PBX (e.g., a SIP server) in PBX system 291 is performed using a PBX, the communication is performed via a LAN within site A1. On the other hand, when communication between an external device 292 at site A2 and a PBX in PBX system 1 is performed using a WAN, the communication is performed via a WAN. The communication delay for the PBX at site A2 is relatively large compared to the communication delay for the PBX at site A1. Assume that the PBX systems at sites A1 and A2 are configured and operated based on the same PBX specifications. For example, in these operational settings, the timer time for waiting for a response to a request in a SIP communication sequence is set to the same operational value. In this case, there may be discrepancies in at least one of the operational conditions, such as communication delay characteristics, that differ between the sites in the customer environment, which is undesirable as an operational value. Therefore, it is more preferable to set the operation value of the timer at the site A2 to be relatively larger than the operation value of the timer at the site A1, for example.

[0031] The operational settings made by user U1, who is the configurator, may have inadequate settings. For example, the content of the operational settings may not match or be consistent with the actual operational configuration of the customer environment or the customer's requests. Furthermore, after the operational settings have been made, the actual operational configuration of the customer environment or the customer's requests may change, and the operational settings may not be able to adapt to these changes. Inadequate or insufficient settings may occur depending on the individual differences in the knowledge and experience of user U1, who is the configurator. Furthermore, conventional methods may not be able to respond quickly to changes in the operational configuration, etc.

[0032] Improper configuration of the PBX mentioned above is likely to cause problems. Improper configuration can result in, for example, an inquiry 2902 from a contractor to the maintenance center. Depending on the individual differences of user U1, the number of inquiries increases, and the work time required to respond to support inquiries increases. Each time a configuration error occurs, manual work such as checking and identifying the cause and correcting the settings is required. As such, when building and operating a PBX-based system for each customer environment, optimal configuration and stable operation require effort, time, cost, etc.

[0033] Note that a PBX system built for each customer environment may be referred to as a PBX-using system when distinguishing it from the provider's PBX system. For example, the PBX-using system for location A1 in Figure 29 is a system that combines a system including location A1's own LAN and external device 292 with the PBX function of the provider's PBX system 291. As shown in the example, differences in PBX-using systems and operations can occur not only between different customers, but also between locations within the same customer.

[0034] The PBX setting value correction method and system of the embodiment realize functions that can address the issues described in the comparative example. That is, the method and system of the embodiment have functions to support configuration, including operational settings, for each customer environment, and to correct operational values ​​for each customer environment, so as to accommodate differences in the PBX usage system and operation for each customer environment. More specifically, the method and system have functions to monitor the operational sequence for each customer environment, and, if a mismatch is detected in comparison with a model sequence, automatically correct and adjust the operational values ​​for the customer environment.

[0035] <First Embodiment> A PBX setting value correction method and system according to a first embodiment of the present disclosure will be described with reference to Figures 1 to 29. The PBX setting value correction system according to the first embodiment is configured by the PBX system 1 shown in Figure 1. The PBX setting value correction method according to the first embodiment is a method having steps executed by the PBX system 1 shown in Figure 1, which is the PBX setting value correction system according to the first embodiment.

[0036] [System Wide] FIG. 1 shows an example of the overall system configuration, including a PBX system 1, which is a PBX setting value correction system according to the first embodiment. The system in FIG. 1 shows the overall system, including the PBX system 1, which is a PBX setting value correction system according to the first embodiment, and a PBX usage system for each customer environment 2. The system in FIG. 1 is based on a cloud PBX, similar to the comparative example system in FIG. 29. The example of the customer environment 2 in FIG. 1, the example of the construction company 3, and the example of the maintenance center 4 are also similar to the examples in FIG. 29.

[0037] The PBX setting value correction system of the first embodiment is a system including a PBX system 1 managed by a business operator. The PBX setting value correction system of the first embodiment has a function of supporting settings including operational settings of the PBX for each customer environment 2, and a function of correcting and adjusting the operational setting values ​​of the PBX for each customer environment 2.

[0038] A PBX system 1 is configured on a cloud computing system using a data center 100 of a business operator. The PBX system 1 is configured to include, for example, a server 10, a router 11, and a database 12. The router 11 is connected to a wide area communication network. The server 10 has a PBX function as well as a PBX setting support function and an operational value correction function. The database 12 stores various data and information related to each function. In other words, the database 12 is a storage unit.

[0039] An example of customer environment 2 includes customer environments A and B, with customer environment A having locations A1 and A2, and customer environment B having locations B1 and B2. Each location has its own computer system, including an external device 20. For example, the external device 20 at location A1 (e.g., Tokyo) is connected to the PBX system 1 via a LAN, for example. The external device 20 at location A2 (e.g., Osaka) is connected to the PBX system 1 via a WAN, for example. Communications QA1, QA2, QB1, and QB2 are examples of communications between the external devices 20 at each location and the PBX of the PBX system 1, or in other words, examples of operation sequences.

[0040] Each customer environment 2 has a user U1 who is a setter or operator of the construction company 3. User U1 performs setting work related to the construction and operation of a PBX-using system in the customer environment 2 (e.g., a company's computer system) of the customer (e.g., a company) that he / she is in charge of. User U1 sets operational setting parameter values ​​that are considered based on the operational configuration of the customer environment 2 as operational values. User U1 uses, for example, a terminal 30 for setting work. Terminal 30 is, in other words, a user terminal, a setting terminal, or an information processing device, such as a general-purpose laptop PC. Settings CA and CB show examples of settings for the PBX system 1 from user U1's terminal 30.

[0041] The PBX system 1 has a user interface for settings. The PBX system 1 provides a parameter sheet 13 for settings to the user U1. As a specific example, this user interface for settings is realized as a Web system. That is, the PBX system 1 provides a Web page or the like having a GUI for settings, including the parameter sheet 13, which is data, to the terminal 30 of the user U1. In other words, the parameter sheet 13 is an operation information input table.

[0042] For example, user U1 accesses the web server function of PBX system 1 from terminal 30. In response to the access and request, the web server function of PBX system 1 transmits a web page including parameter sheet 13. User U1's terminal 30 displays a screen based on the received web page on its display. Parameter sheet 13 and other information are displayed on the screen. User U1 inputs operational information and other information appropriate to customer environment 2 into parameter sheet 13 on the screen as data and information required to configure PBX usage in customer environment 2. Terminal 30 transmits the operational information and other information input into parameter sheet 13 to the web server function of PBX system 1. The web server function of PBX system 1 acquires the operational information and other information received from terminal 30 and registers and stores it in DB 12.

[0043] As will be described later, the parameter sheet 13 comprehensively pre-specifies operational setting parameters and input candidate parameter values. User U1 can input operational information as parameter values ​​for each parameter on the parameter sheet 13. For the sake of explanation, the operational information and the operational values ​​are different. The operational information input to the parameter sheet 13 is information elements that are conventionally known for PBX operation, and specific examples will be described later.

[0044] For example, when a PBX-using system is constructed in the customer environment 2, user U1 performs initial settings, including operational settings, and the settings are registered in DB 12. Then, operation of the PBX-using system in the customer environment 2 begins. The PBX system 1 in the first embodiment monitors and checks the operational sequence of the PBX-using system in the customer environment 2 based on the operational settings. For example, the server 10 of the PBX system 1 monitors operational sequences such as communication QA1. For example, the server 10 can monitor the operational sequence by capturing and acquiring packets of communication between a PBX function (e.g., a SIP server) and an external device 20 such as a telephone terminal, and record the data as a log. The data and information obtained by monitoring may be referred to as operational sequence monitoring information, captured data, etc.

[0045] The PBX system 1 compares, collates, and checks the operational sequence of the customer environment 2 based on the monitoring information with a predefined model sequence, thereby determining and detecting any discrepancies or inconsistencies between those sequences. For example, the PBX system 1 determines and detects any step where the status, etc., between the sequences does not match.

[0046] The PBX system 1 predefines and stores a model of a normal or standard operation sequence based on the standard PBX specifications as a model sequence. The operation sequence and model sequence, which will be described later, are sequences in which statuses of messages related to SIP or the like occur in multiple sequential steps in a time series.

[0047] Based on the results of the above-mentioned monitoring and checks to determine discrepancies, etc., the PBX system 1 corrects the operational values ​​of the customer environment 2 to more suitable operational values. In other words, the PBX system 1 adjusts the operational values ​​by increasing or decreasing them to match the operational configuration of the customer environment 2 at that time and to bring the operational sequence of the customer environment 2 closer to the model sequence. In this case, the PBX system 1 calculates and determines a correction value for correcting the operational values ​​for the step portion where there is a discrepancy, etc., and the corresponding operational setting parameters. Then, the PBX system 1 corrects the operational values ​​in DB 12 using the correction value, thereby updating the operational setting values ​​of the customer environment 2.

[0048] In addition, when the setting information including the operational setting values ​​for each customer environment 2 in DB12 is updated by the above correction, the immediate reflection means that from that point onwards, operation will begin using the updated operational setting values.

[0049] The PBX setting value correction method and system of the first embodiment performs automatic adjustment by correcting operational values ​​based on the operational monitoring for each customer environment 2 as described above. As a result, the effort, time, cost, etc. of the configuration work by user U1, who is the person setting up the installer 3, can be reduced, and problems due to improper configuration can be reduced. The method and system can achieve more suitable operational settings and optimization to match the actual operational configuration of the customer environment 2. As a result, the time required for building and operating and managing a PBX-using system for each customer environment 2 can be reduced, and changes in the customer environment 2 can be quickly responded to.

[0050] [PBX System] Figure 2 shows an example of the functional block configuration of the PBX system 1 in Figure 1. Each functional block is realized by the cooperation of predetermined hardware and software. For example, each functional block is realized by the processor of the server 10 executing program processing in memory. Alternatively, each functional block may be realized by a dedicated circuit or a separate device.

[0051] The server 10 of the PBX system 1 has, as functional blocks, a PBX communication unit 101 and a PBX setting support unit 102. The PBX communication unit 101 is a unit that realizes basic PBX functions and performs PBX-related communications with an external device 20 in the customer environment 2 via a router 11. In a specific example, the PBX communication unit 101 functions as a SIP server or UA (User Agent) that performs communications in accordance with SIP. Note that while FIG. 2 shows a case in which both the PBX communication unit 101 and the PBX setting support unit 102 are implemented within a single server 10, this is not limiting, and each functional block may be implemented separately on two or more servers, etc.

[0052] The PBX setting support unit 102 is a unit that realizes the PBX setting support function and the PBX setting value correction function. More specifically, the PBX setting support unit 102 has multiple function blocks. The PBX setting support unit 102 has a parameter sheet providing unit 103, a customer environment operation information setting unit 104, a data collecting unit (in other words, an operation sequence monitoring unit) 105, an operation sequence checking unit 106, an operation correction value determining unit 107, a correction action unit 108, a DB updating unit (in other words, a statistics unit) 109, and an operation value generating unit 110.

[0053] The DB 12, which is a storage unit, for example a DB server, stores various types of data and information, such as the following: The DB 12 is broadly divided into a customer DB 15 and a common DB 16. The customer DB 15 is a DB that stores separate data and information for each customer environment 2, and is provided for each customer environment 2 and is managed securely. The common DB 16 is a DB that stores data that is common to multiple customer environments 2, and is not dependent on a specific customer environment 2.

[0054] The customer DB 15 includes an operation information DB (in other words, a parameter sheet DB) 151, an operation sequence log DB 152, and a PBX setting information DB 153. The PBX setting information DB 153 includes an operation setting value DB 154.

[0055] The operation information DB 151 is a DB that registers and stores operation information entered in accordance with the parameter sheet 13. The data of the parameter sheet 13 is also managed in the operation information DB 151. The operation sequence log DB 152 is a DB that stores operation sequence logs obtained by collecting data through operation sequence monitoring. The operation sequence log includes data that captures the contents of communication packets such as SIP. The operation sequence log may also include data collected or acquired from external devices 20, etc. The PBX setting information DB 153 is a DB that stores all setting information related to the construction and operation of the PBX-using system in the customer environment 2. The operation setting value DB 154 is a DB that stores operation setting values ​​from the setting information.

[0056] The setting information registered in the PBX setting information DB 153 and the operational setting values ​​in the operational setting value DB 154 are the setting information of the PBX system 1 and the PBX-using system of the customer environment 2. As mentioned above, updating the setting information directly means updating the system or starting a new operation.

[0057] The common DB 16 has a setting value correction DB 161, a model sequence DB 162, and a statistical information DB 163. The setting value correction DB 161 is a DB that holds data and information for correcting operation setting values. A correspondence table, which will be described later, is defined in advance in the setting value correction DB 161 as correction information. This correspondence table contains data and information for determining correction values ​​for operation setting parameter values ​​for each combination of the step status of the operation sequence and the operation information.

[0058] The model sequence DB 162 is a DB that stores data of predefined model sequences. The statistical information DB 163 is a DB that stores statistical information related to operational information, operational sequences, and operational setting values ​​of multiple customer environments 2. The PBX system 1 obtains statistical information by statistically processing information set or collected from each of the multiple customer environments 2.

[0059] As described above, the parameter sheet providing unit 103 provides data including the parameter sheet 13 to the terminal 30 of the user U1 who is the configurator. The parameter sheet 13 has parameters related to the PBX operation settings listed and organized as a list. The user U1 who is the configurator can input values ​​of operation information into the parameter items of the parameter sheet 13. The detailed format of the parameter sheet 13 is not limited, and an example will be described later. The parameter sheet 13 may be configured to allow input of not only operation information but also various other information such as customer information.

[0060] The customer environment operational information setting unit 104 acquires the operational information inputted in the parameter sheet 13 and registers it in the operational information DB 151 .

[0061] The data collection unit 105 monitors the actual operation sequence of the PBX-using system in the customer environment 2 in cooperation with the PBX communication unit 101 (e.g., by exchanging information), collects data on the monitored operation sequence as a log, and stores it in the operation sequence log DB 152.

[0062] The operation sequence check unit 106 compares and collates the operation sequence of the monitoring result by the data collection unit 105 with the model sequence in the model sequence DB 162, and determines and detects any discrepancies or inconsistencies between these sequences.

[0063] The operational correction value determination unit 107 determines a correction value and a correction action for correcting the operational value of the customer environment 2 based on the check result by the operational sequence check unit 106. In doing so, the operational correction value determination unit 107 determines the correction value based on the operational information of the customer environment 2 referenced from the operational information DB 151 and the correction information referenced from the setting value correction DB 161. This correction value may be the corrected operational value itself to be replaced depending on the parameter, or may be a correction adjustment value, a correction coefficient, a correction candidate value, a correction formula, or the like. In addition, the correction action refers to a correction method for a parameter to be corrected. The parameter to be corrected is determined as, for example, a parameter corresponding to the step portion where a mismatch occurred, such as a timer time.

[0064] The correction action unit 108 performs a correction calculation in which the correction value determined by the operation correction value determination unit 107 is applied to the pre-correction operation value in the operation setting value DB 154 using the determined correction action, thereby correcting and adjusting the operation value of the customer environment 2. In other words, this correction action updates the operation value in the operation setting value DB 154. The correction calculation at this time may vary depending on the parameters of the operation settings, and may, for example, be a substitution by a correction value, or may be addition, subtraction, multiplication, or division of the pre-correction operation value by the correction value.

[0065] The DB update unit 109 generates statistical information including statistical values ​​such as averages and variances based on the operation information, operation sequence logs, operation setting values, etc. of each of the multiple customer environments 2, and stores the information in the statistical information DB 163. The DB update unit 109 updates the statistical information in the statistical information DB 163 as new information occurs.

[0066] The operation value generation unit 110 generates suitable operation values ​​for the customer environment 2 based on the operation information registered in the operation information DB 151 by the customer environment operation information setting unit 104, and registers the values ​​in the operation setting value DB 154. For example, the operation value generation unit 110 generates initial setting operation values ​​based on the operation information initially input and set when the PBX-using system is introduced and constructed in the customer environment 2. Furthermore, at this time, if there is statistical information related to the operation information, the operation value generation unit 110 uses the statistical information to generate more suitable operation values. Note that although they are separated for the sake of explanation, the operation value generation unit 110 may be integrated with the customer environment operation information setting unit 104 or with the operation correction value determination unit 107.

[0067] [Computer System] Fig. 3 shows an example of the configuration of the server 10 in Fig. 2 as a computer system. The computer that is the server 10 includes a processor 301, a memory 302, a communication interface device 303, an input / output interface device 304, etc., and these components are interconnected via a bus 309, etc.

[0068] The processor 301 includes, for example, a CPU, a ROM, a RAM, etc., and executes processing in accordance with a control program 311. This realizes predetermined functions, such as at least a PBX function 321 and a PBX setting support function 322 corresponding to the configuration in FIG.

[0069] The memory 302 is configured using a nonvolatile storage device or the like. The memory 302 stores a control program 311, setting information 312, processing data 313, and the like. The control program 311 is various programs for realizing the functions of the server 10. The setting information 312 is system setting information and user setting information related to the control program 311. The processing data 313 is various data generated in the processing process by the server 10. Note that the DB 12 in FIG. 2 may be configured on the memory 302. Instead of the memory 302, other storage means, such as an external storage device or a DB server, may also be used.

[0070] The communication interface device 303 is a device equipped with a communication interface, and corresponds to a communication interface with the router 11, a communication interface with the DB 12, etc. The input / output interface device 304 is a device equipped with an input / output interface, and an input device 305 and an output device 306 can be externally connected.

[0071] The control program 311, that is, the program for realizing the method and system of the first embodiment, may be downloaded, installed, updated, etc. from a business operator's system, a program distribution server, etc.

[0072] [Processing flow] Fig. 4 shows a processing flow of the PBX setting value correction method and system according to embodiment 1. The PBX system 1 executes processing according to the flow of Fig. 4. The flow of Fig. 4 has steps S101 to S108.

[0073] In step S101, the PBX system 1 performs initial setting of the setting information including the operational values ​​when constructing the PBX-using system in the customer environment 2. Note that this initial setting at the time of construction may be performed manually as in the past, or may be performed as described above by generating operational values ​​according to the operational information using the customer environment operation information setting unit 104 and the operational value generating unit 110 in Fig. 2. Also, step S101 may be omitted from the flow, and the method and system of the first embodiment may be a method and system for the customer environment 2 that has already been constructed and is in operation.

[0074] In step S102, the PBX system 1 uses the parameter sheet 13 to acquire operational information of the customer environment 2 and registers it in the operational information DB 151. At this time, as described above, the parameter sheet providing unit 103 in FIG. 2 provides the parameter sheet 13 to the terminal 30 of the user U1, acquires the operational information entered in the parameter sheet 13, and registers it in the operational information DB 151.

[0075] In step S103, the PBX system 1 monitors the operation sequence of the customer environment 2 after the start of operation using the data collection unit 105 in FIG.

[0076] In step S104, the PBX system 1 compares and collates the operation sequence log in the operation sequence log DB 152 with the model sequence in the model sequence DB 162 using the operation sequence check unit 106 of Figure 2, and determines and detects any inconsistencies between the sequences.

[0077] In step S105, if correction is necessary based on the check result of step S104, the PBX system 1 determines a correction value for correcting the operation value of the customer environment 2 using the operation correction value determination unit 107 of Fig. 2. At this time, the operation correction value determination unit 107 determines the correction value by referring to the operation information of the customer environment 2 and the setting information in the setting value correction DB 161.

[0078] In step S106, the PBX system 1 corrects the operation values ​​of the customer environment 2 by the correction action unit 108 in Fig. 2 using the correction values ​​obtained as a result of step S105. The correction action unit 108 updates the operation values ​​in the operation setting value DB 154 by correcting them with the correction values.

[0079] In step S107, the PBX system 1 causes the DB update unit 109 in FIG. 2 to update the statistical information in the statistical information DB 163 using the updated operation information, operation sequence log, and operation value.

[0080] Step S108 is a check to see if all processing for each customer environment 2 has been completed. If it has been completed (Y), the flow in Figure 4 ends. If it has not been completed (N), the process returns to step S101 and the processing for each customer environment 2 is repeated in the same manner.

[0081] [Operation information settings] FIG. 5 is an explanatory diagram showing an example of a configuration related to the registration of operational information of the customer environment 2 using the parameter sheet 13, which relates to steps S101 and S102 in FIG. 4. The example in FIG. 5 is an example in which steps S101 and S102 are realized together. FIG. 5 shows an example of processing between functional blocks between the user U1 who is the setting person and the PBX system 1. In FIG. 5 and other figures, functional blocks such as the server 10 and the PBX setting support unit 102 are not shown. An example of a processing sequence between the functional blocks is as follows:

[0082] In step S201, the parameter sheet providing unit 103 of the PBX system 1 transmits data including the parameter sheet 13 to the terminal 30 of the user U1 via the Web system. In step S202, the user U1 inputs operational information that matches the operational configuration of the customer environment 2 for each parameter item in the parameter sheet 13 displayed on the screen of the terminal 30. The operational configuration of the customer environment 2 is understood, for example, through a hearing from the customer. In step S203, the terminal 30 of the user U1 transmits at least the operational information input in the parameter sheet 13 to the PBX system 1. Here, the parameter sheet 13 may be transmitted together with the operational information. In step S204, the customer environment operational information setting unit 104 registers the operational information received and acquired from the terminal 30 in the operational information DB 151.

[0083] Furthermore, in step S205, the operation value generation unit 110 of the PBX system 1 (which may alternatively be the customer environment operation information setting unit 103 or the operation correction value determination unit 107 as described above) extracts statistical information corresponding to the registered operation information from the statistical information DB 163.

[0084] In step S206, the performance value generating unit 110 generates a performance value using the extracted statistical information. This generation may involve determining the performance value using, for example, an average value in the extracted statistical information.

[0085] In step S207, the operation value generation unit 110 registers the generated and determined operation values ​​in the operation setting value DB 154. Up to this point, it is possible to register operation information using the parameter sheet 13 during construction and to initially set operation values ​​using statistical information.

[0086] In the above processing example, if applicable statistical information is not available, the PBX system 1 may initialize the operational values ​​as in the conventional case without using statistical information. For example, the operational values ​​are manually set by the user U1. In the above processing example, if applicable statistical information is available, suitable operational values ​​can be automatically generated and set as initial settings.

[0087] [Data collection (operation sequence monitoring)] FIG. 6 is an explanatory diagram of data collection by the data collection unit 105 in FIG. 2, checks by the operation sequence check unit 106, and the like, relating to steps S103 and S104 in FIG.

[0088] In step S301, the data collection unit 105 monitors an operation sequence, which is a sequence of communication between the PBX communication unit 101 and the external device 20, and acquires data related to the operation sequence through the PBX communication unit 101. For example, the PBX communication unit 101 exchanges communication packets based on SIP with the external device 20. The data collection unit 105 acquires, for example, the contents of the communication packets from the PBX communication unit 101 as capture data. The data collection unit 105 acquires capture data of the contents of each packet at each timing on a time series. The operation sequence log includes a collection of such capture data at each point in time ordered on a time series. In step S302, the data collection unit 105 stores the capture data acquired by the above monitoring as an operation sequence log in the operation sequence log DB 152.

[0089] [Operation sequence check] Also in FIG. 6, in step S303, the operation sequence check unit 106 extracts the latest operation sequence log stored in the operation sequence log DB 152. In step S304, the operation sequence check unit 106 references model sequence data from the model sequence DB 162 of the common DB 16. In step S305, the operation sequence check unit 106 compares and collates the extracted operation sequence with the model sequence to determine and detect discrepancies, differences, etc. As a result, if there are any parts in the sequence, such as steps that are inconsistent, these parts are detected.

[0090] [Operation Sequence] FIG. 7 shows an example of an operation sequence related to PBX usage. The operation sequence is a communication sequence that conforms to the specifications of a certain PBX, for example, a protocol called SIP. The horizontal direction in FIG. 7 shows the communication entities, "PBX," which is a UA by the PBX communication unit 101 of the PBX system 1, and "SIP1," which is a UA by the external device 20. The vertical direction shows the time series, or time axis. For the purpose of explanation, the time series has ordered steps, indicated by steps S1, S2, etc. These steps are for controlling the functions in embodiment 1. Each step can have various statuses. The operation sequence has a collection of statuses for this series of steps.

[0091] The left side of Figure 7 (A) shows an example of a model sequence, and in contrast, the right side (B) shows an example of an abnormal sequence as an example of an operational sequence in a certain customer environment 2. The operational sequence of customer environment 2 is a communication sequence that corresponds to the operational value settings of that customer environment 2. When the model sequence is assumed to be normal, an abnormal sequence corresponds to a discrepancy or large difference with the normal model. An abnormal sequence does not mean that the PBX cannot be used.

[0092] In the model sequence of Figure 7(A), for example, a PBX is the calling party and sends an INVITE message to SIP1 at time point 701. The message is described in a packet. Timer A starts counting from the time point 701 when the INVITE message is sent and received. Timer A is a timer (Timer A in Figure 14 described later) that specifies the interval between retransmissions of the INVITE message.

[0093] In response to the INVITE message from the PBX, SIP1 sends "100 try." In step S1, the PBX receives the "100 try" from SIP1. That is, the status in step S1 is "100 try." In step S2, SIP1 sends "180 Ring," and the PBX receives the "180 Ring." That is, the status in step S2 is "180 Ring."

[0094] The count time of Timer A ends at a time corresponding to the set value (one of the operation values) of Timer A. For example, Timer A ends at time 702. After that, in step S3, SIP1 sends "200 OK" to the PBX. That is, the status in step S3 is "200 OK." The PBX sends "ACK" in response to "200 OK." This establishes a session. After that, communication is performed between the PBX and SIP1 using RTP (Real-time Transport Protocol).

[0095] On the other hand, in the abnormal sequence of Figure 7 (B), the PBX does not receive a response from SIP1 to the INVITE message from the PBX to SIP1 within the time set by timer A. That is, the status is "no response" in steps S1 and S2. Since the PBX did not receive a response within the time set by timer A, the PBX resends the INVITE message in step S3. That is, the status is an INVITE message in step S3. Thereafter, after the time set by timer A expires at time 702, for example at time 703, the PBX receives "100 try" sent from SIP1.

[0096] In this way, for example, if the status is such that "100 try" is received within the time of timer A (time point 701 to time point 702), it is determined to be normal, and the model sequence (A) is predefined. When the model sequence (A) is compared with the operation sequence (B), for example, if the status is such that "100 try" is not received within the time of timer A, it can be determined to be an abnormal sequence.

[0097] In the above example, the step status is described as seen from the PBX, but the present invention is not limited to this.

[0098] As in the above example, when the monitored operational sequence is compared with the model sequence and it is determined that there is a discrepancy or a large difference, the PBX system 1 corrects the operational values. In particular, the PBX system 1 can detect parts of the operational sequence where the step statuses do not match. In the above example, since there is a mismatch at least with respect to "100 tries" in step S1 of the model sequence, it can be determined that the operational values ​​for that part of step S1 need to be corrected.

[0099] SIP is a protocol for creating, modifying, and disconnecting sessions between terminals (called User Agents: UAs). The server 10 of the PBX system 1 and the external device 20 (e.g., an IP telephone) in the customer environment 2 are each UAs equipped with SIP-compatible applications, and exchange data such as voice over sessions controlled by SIP. UAs are identified by URIs. The meaning of SIP messages can be briefly explained as follows: An "INVITE" message is an invitation message for establishing a session, and includes the URI of the sender (e.g., the PBX) and the URI of the other party (e.g., SIP1). "100 try" indicates a response that is being attempted, and is a provisional response that notifies the PBX, for example, that "an invitation to SIP1 is being executed." Of these, "100" is a status code defined by SIP.

[0100] "180 Ring" indicates a response during a call. For example, SIP1 processes the call and sends "180 Ring" to the PBX. "200 OK" indicates a success response. SIP1 sends "200 OK" to the PBX in response to the IP phone going off-hook, etc. When the PBX receives "200 OK," it sends a response "ACK" to SIP1 indicating acknowledgement of the session establishment. This creates and establishes a session. After that, data such as voice is exchanged between the UAs of the PBX and SIP1 in accordance with RTP. Note that the example in Figure 7 shows only two UAs, the PBX and SIP1 (external device 20), but this is not limiting; SIP communication is also possible between three or more UAs (for example, when a SIP gateway is interposed).

[0101] [Correction value determination] FIG. 8 is an explanatory diagram relating to the determination of the correction value by the operational correction value determination unit 107 and the corrective action by the corrective action unit 108 in FIG. 2, which relate to steps S105 and S106 in FIG.

[0102] In step S401, the operation correction value determination unit 107 refers to the judgment result information from the operation sequence check unit 106. The judgment result information includes, for example, an operation sequence log, a judgment value such as normal / abnormal, and a mismatched step portion. In step S402, the operation correction value determination unit 107 extracts the operation values ​​of the target customer environment 2 from the operation setting value DB 154 based on the judgment result information. In step S403, the operation correction value determination unit 107 refers to correction information (a correspondence table described later) from the setting value correction DB 161. In step S404, if the judgment value is abnormal (in other words, if there is a mismatched step portion), the operation correction value determination unit 107 determines a correction value for the operation value based on the correction information in accordance with a combination of the step status of the operation sequence and the operation information.

[0103] Then, in step S405, corrective action unit 108 refers to the correction value determined by operation correction value determination unit 107. In step S406, corrective action unit 108 refers to the target operation value from operation set value DB 154. In step S407, corrective action unit 108 performs a correction calculation on the target operation value using the correction value to obtain a corrected operation value. Then, in step S408, corrective action unit 108 updates the corresponding operation value in operation set value DB 154 with the corrected operation value.

[0104] Fig. 9 shows a detailed example of a process flow relating to the determination of the correction value in step S105, as another representation of Fig. 8. The example of the process flow in Fig. 9 includes additional processes in addition to the basic processes.

[0105] In step S901, the operation correction value determination unit 107 checks whether the judgment result of the operation sequence check indicates an abnormality, in other words, whether there is a discrepancy, a mismatch, a large difference, or a low degree of agreement. If the answer is YES in step S901, the process proceeds to step S902 of the flow indicated by A, and if the answer is NO, the process proceeds to step S904 of the flow indicated by B. Flow A indicates basic processing functions, and the PBX system 1 performs at least the basic processing of flow A.

[0106] In step S902 , the operational correction value determination unit 107 extracts operational information of the customer environment 2 from the operational information DB 151 .

[0107] In step S903, the operation correction value determination unit 107 determines a correction value by extracting a correction value related to the operation value from the correspondence table of the setting value correction DB 161 based on a combination of the step status value captured from the operation sequence log and the value of the extracted operation information. After step S903, the flow in Fig. 9 ends, and the process continues to the correction action in step S106.

[0108] On the other hand, flow B indicates an additional processing function, although it is not essential. In embodiment 1, the PBX system 1 performs additional processing of flow B in addition to the basic processing of flow A. In a variation of embodiment 1, the additional processing of flow B may be omitted. If step S901 returns NO, this means that the difference between the model sequence and the operational sequence is small and similar, and there appears to be no problem at first glance. However, in embodiment 1, even in this case, it is assumed that there is room for adjustment of the operational values, and an adjustment is attempted by performing additional processing of flow B.

[0109] In step S904, the operational correction value determination unit 107 refers to the operational information corresponding to the customer environment 2 from the operational information DB 151. The operational correction value determination unit 107 also refers to the operational values ​​corresponding to the customer environment 2 from the operational setting value DB 154.

[0110] In step S905, the operation correction value determination unit 107 extracts correction values ​​related to the operation values ​​from the set value correction DB 161 based on the step status values ​​captured from the operation sequence log, the operation information values, and the operation values.

[0111] In this case, in flow B, the operational correction value determination unit 107 compares the step status value with the operational value to check whether the operational value is far from the optimal operational value. If it is far from the optimal operational value, the PBX system 1 determines that the operational value needs to be adjusted and extracts a correction value.

[0112] If flow A is used to repeatedly correct the operating value when the sequences do not match, for example, the operating value for the time of Timer A in Figure 7 may become too long to match the operating sequence of Customer Environment 2. In that case, the operating value for the time of Timer A will be far from the optimal operating value. Therefore, flow B checks the step status even when the sequences match, and determines whether the operating value at that time is far from the operating value of the model. For example, it determines whether the difference is greater than or equal to a threshold. Depending on the results of this determination, the operating value is adjusted to approach the optimal operating value.

[0113] Step S906 is a branch that determines whether a correction value has been obtained as a result of the steps up to step S905. If a correction value has been obtained (YES), the flow in Fig. 9 ends and continues to the correction action, and if a correction value has not been obtained (NO), the flow in Fig. 9 ends and returns to, for example, data collection in step S103 in Fig. 4.

[0114] [Statistics] FIG. 10 is an explanatory diagram of the generation of statistical information by the DB update unit 109 of FIG. 2, which relates to step S107 of FIG. 4. In step S1001, the DB update unit 109 references the operational information of the customer environment 2 from the operational information DB 151, and in step S1002, references the corrected operational values ​​from the operational setting value DB 154. In step S1003, the DB update unit 109 references the statistical information DB 163 of the shared DB 16 for the corrected operational values ​​of the customer environment 2. In step S1004, the DB update unit 109 generates or updates statistical information, such as average values, for the parameters of the operational values. In step S1005, the DB update unit 109 updates the statistical information in the statistical information DB 163 for the parameters of the operational values ​​using the generated or updated statistical information.

[0115] [Parameter sheet] FIG. 11 shows an example of the configuration of the parameter sheet 13. This parameter sheet 13 is configured as a table. This parameter sheet 13 can be implemented using, for example, a spreadsheet software sheet, but is not limited to this. The table of the parameter sheet 13 in FIG. 11 has columns of "item number," "sheet name," "category," "item," and "remarks." This parameter sheet 13 is in a format that allows input of operational information for each customer environment 2 for each table. Note that FIG. 11 shows the structure of the parameter sheet 13, but does not show values ​​of operational information as parameter input values.

[0116] The "item number" is identification information for each row. The "sheet name" is the name of each sheet, and a value such as "extension (required)" is set. Operational settings related to extensions are required as part of the operational information. The "classification" is a classification related to the operational information, and a value such as "extension." The "item" is an item related to the operational information, and has values ​​such as "extension number," "telephone type," "connection type," and "location." The "remarks" are remarks related to the "item." For example, the "extension number" item specifies the extension number. The "telephone type" item specifies the type of telephone. A telephone is a type of external device 20 mentioned above. The "connection type" item specifies the type of network connection related to PBX use, and possible values ​​for the connection type include LAN / WAN / Internet. The "location" item specifies the location of the base, and possible values ​​for the location include Tokyo / Osaka / Sapporo.

[0117] [Operation information DB] FIG. 12 shows an example of the configuration of the operation information DB 151, and also shows an example of operation information input via the parameter sheet 13. The operation information DB 151 holds the operation information input to the parameter sheet 13. The operation information DB 151 in FIG. 12 has a table. This table has input values ​​for "Classification" and "Item" of the parameter sheet 13 in FIG. 11. This table has columns such as "Classification," "Extension Number," "Telephone Type," "Connection Type," and "Location," and has input values ​​for each row. "Classification" has the same value as "Classification" of the parameter sheet 13 (e.g., "Extension"). Values ​​such as "1000," "1001," "2000," and "3000" are input for "Extension Number." Values ​​such as "SIP Telephone" or "IP Telephone" are input for "Telephone Type." Values ​​such as "LAN," "WAN," or "Internet" are input for "Connection Type." For example, "Tokyo," "Osaka," or "Sapporo" is input as a value for "location."

[0118] [Operation sequence log DB] FIG. 13 shows an example of the configuration of the operation sequence log DB 152. The operation sequence log DB 152 in FIG. 13 has a table of operation sequence logs. This table has columns such as "call number," "source," "destination," "time," and "sequence content." This table holds information for each time period (the aforementioned capture data) in each row, and the operation sequence log in chronological order is represented by multiple rows. "Call number" stores the value of the call number in the PBX. "Source" stores the address of the source. "Destination" stores the address of the destination. "Time" stores information on a point in time, for example, the year, month, day, hour, minute, and second. "Sequence content" stores information such as protocol messages as the status of each step constituting the operation sequence as shown in FIG. 7.

[0119] [Operational setting value DB] Fig. 14 shows an example of the configuration of the operation setting value DB 154. The operation values ​​of the current PBX-using system are registered in the operation setting value DB 154. These operation values ​​are the same as the data set in the server 10 of the PBX system 1 (particularly, the PBX communication unit 101 in Fig. 2). The operation setting value DB 154 in Fig. 14 has a table. This table has columns such as "timer type," "name," and "operation value." In this example, as parameter values ​​of operation settings, operation values ​​relating to timers in SIP (such as timer A in Fig. 7) will be described in particular, but the present invention is not limited to this. "Timer type" is set to a value from 0 to 10, etc., indicating the type of timer. "Name" is set to a name for each timer type.

[0120] For example, the timer with timer type = 0 is T1, the initial retransmission time for a request. The timer with timer type = 1 is T2, the maximum retransmission time for a request. The timer with timer type = 2 is T4, the transaction end timeout from receiving the final response. The timer with timer type = 3 is the setting value for the Expire header of the INVITE request. The timer with timer type = 4 is the minimum value of the Expire header of a REG request. The timer with timer type = 5 is the maximum value of the Expire header of a REG request. The timer with timer type = 6 is the wait time for accepting the final response after receiving an INVITE. The timer with timer type = 7 is the initial retransmission interval for an INVITE request (timer A mentioned above). The timer with timer type = 8 is the retransmission expiration time for an INVITE request (timer B). The timer with timer type = 9 is the retransmission wait time for an INVITE response (timer D). The timer with timer type = 10 is the initial retransmission interval for requests other than INVITE (timer E).

[0121] The "operation value" is set to an operation value for each timer. For example, the value of the parameter "maximum request retransmission time T2", which is a timer with timer type = 1, is "500 ms". The unit is, for example, milliseconds (ms).

[0122] If the operation setting values, such as timer values, are not set appropriately for each customer environment 2, the operation sequence related to the PBX system will be inefficient. If the operation setting values ​​are set optimally, the operation sequence related to the PBX system will be efficient.

[0123] [Setting value correction DB] 15 shows an example of the configuration of the setting value correction DB 161. In the setting value correction DB 161, a correspondence table such as the table in FIG. 15 is predefined as correction information for correcting operation setting values. The correspondence table in FIG. 15 registers correction values ​​corresponding to combinations of step status and operation information, or information for calculating and determining correction values. This table has columns such as "step number," "received data," "correction action," and "correction adjustment value." The "step number" contains information such as a number for identifying each step in the operation sequence shown in FIG. 7. The "received data" contains a status value for each step, such as a value of a message received by the PBX from SIP1 (external device 20).

[0124] Note that steps S1 and the like in the operational sequence are defined for the purpose of explanation and are units related to the order in a chronological order. For example, the first step, step S1, indicates that there are four possible candidate statuses ("received data"). Cases can be considered according to the status of the message that actually occurred. Correction actions and correction adjustment values ​​are pre-associated and specified according to the combination of the step status and the operational information. The correction value and correction content can be determined according to this combination.

[0125] For example, for step number = S1, the candidate status values ​​are "100 try received (within timer A)", "100 try received (after timer A)", "486 Busy received", and "not received". For example, for step number = S2, the candidate status values ​​are "180 received (within Expire)" and "180 received (after Expire)". For example, for step number = S3, the candidate status values ​​are "200 received (within Expire)", "200 received (after Expire)", and "422 received".

[0126] The "correction action" is set to a correction action to be performed when using the extracted correction value. For example, for step S1, if the step status value, which is the received data value, is "received within 100 tries (within timer A)" or "received after timer A," the correction action value is "timer A correction." If it is "received 486 Busy," the correction action value is "none." If it is "not received," the correction action value is "correction of number of retries (double the number of retransmissions)." For example, for step S2, if the status value is "received 180 (within Expire)" or "received 180 (after Expire)," the correction action value is "expire correction." For example, for step S3, if the status value is "received 200 (within Expire)" or "received 200 (after Expire)," the correction action value is "expire correction," and if it is "received 422," the correction action value is "session timer correction."

[0127] The "Correction Adjustment Value" column contains adjustment values ​​related to the adjustment values ​​for the operational values. These adjustment adjustment values ​​are addition values ​​when the operational setting value is corrected by addition, or subtraction values ​​when the operational setting value is corrected by subtraction. In this example, the "Correction Adjustment Value" column also has columns for each of the connection topology values ​​described above (FIG. 12): "LAN," "WAN," and "Internet." Each of these connection topology value columns also has an "Add" column for addition values ​​and a "Subtract" column for subtraction values.

[0128] A correction adjustment value is set in the cell where the row of the step status values ​​"Received Data" value and "Adjustment Action" value intersects with the "Adjustment Adjustment Value" column. For example, for step S1, the row for "100 try reception (within Timer A)" and "Timer A adjustment" has a subtraction value of "5 ms" when the connection type is "LAN," a subtraction value of "15 ms" when the connection type is "WAN," and a subtraction value of "100 ms" when the connection type is "Internet." The row for "100 try reception (after Timer A)" and "Timer A adjustment" has an addition value of "10 ms" when the connection type is "LAN," a addition value of "30 ms" when the connection type is "WAN," and an addition value of "200 ms" when the connection type is "Internet." For the rows for "No reception" and "Adjustment of retry count (......)", the addition value is set to "6 times" and the subtraction value is set to "1 time" when the connection type is "LAN", the addition value is set to "6 times" and the subtraction value is set to "1 time" when the connection type is "WAN", and the addition value is set to "6 times" and the subtraction value is set to "1 time" when the connection type is "Internet".

[0129] 15, the correction values ​​corresponding to the combinations of the step status value and the connection topology value as an example of the operation information are comprehensively set. In this correspondence table, correction values ​​can be similarly defined not only for the connection topology as the operation information but also for other operation information.

[0130] A value such as "5 ms" set in a cell in the "Correction Adjustment Value" column corresponds to the aforementioned correction value. From this correspondence table, the PBX system 1 extracts a correction value such as the "5 ms" subtraction value according to the combination of the step status value based on the operation sequence monitoring information and the value of the operation information. For example, according to the combination of "100 try reception (within timer A)" and "LAN," the "5 ms" subtraction value is extracted as the correction value. In this case, this "5 ms" subtraction value is the correction value for "Timer A Correction" indicated in "Correction Action," and indicates that the correction should be made by subtracting this "5 ms" from the operation value of Timer A at that time before correction.

[0131] In this example, the correction value is in the form of a "correction adjustment value," but this is not limiting. As another example of setting the correction value, a correction coefficient for correction such as multiplication or division may be specified. For example, if the multiplication coefficient is set to "1.5" depending on the combination, the correction may be to multiply the operational value by that coefficient "1.5." If the correction is to increase the number of retries by n times, then that n value may be used as the correction value.

[0132] As another example of setting the correction value, a candidate range (e.g., an upper limit value or a lower limit value) for the correction value or the corrected operating value, or a candidate value to be selected, may be specified. For example, a correction value may be selected from the candidate range or candidate values ​​depending on a combination of values. As another example of setting the correction value, a formula for calculating the correction value or the corrected operating value may be specified. For example, depending on a combination of values, the correction value or the corrected operating value may be calculated using the corresponding formula.

[0133] [Model Sequence DB] Fig. 16 shows an example of the configuration of the model sequence DB 162. The model sequence DB 162 in Fig. 16 has a table. This table has columns such as "Message Issuer," "Sequence Content," and "Step Number." Information specifying the issuer of a message such as SIP is set in "Message Issuer." Information such as SIP messages at each step in an operational sequence such as that in Fig. 7 is set in "Sequence Content." Information for identifying each step in an operational sequence is set in "Step Number," similar to the "Step Number" in the correspondence table in Fig. 15.

[0134] In the example of Figure 16, a model sequence is set in multiple rows of the table. In the first row, the value of "Message Issuer" is "Caller", the value of "Sequence Content" is "INVITE...", and the step number is "-". Similarly, the second row is "Callee", "100 try", and "S1". The third row is "Callee", "180 Ring", and "S2". The fourth row is "Caller", "200 OK", and "-". The fifth row is "Callee", "ACK", and "S3". In other words, this model sequence represents the model sequence in the example of Figure 7.

[0135] [Statistics information DB] FIG. 17 shows an example of the configuration of the statistical information DB 163. The statistical information DB 163 of FIG. 17 has a table. This table has columns such as "External Device Type," "Connection Type," "Location," "Step Number," "Setting Item," "Statistical Value," and "Count of Statistical Values." "External Device Type," "Connection Type," and "Location" are examples of operational information items. "External Device Type" is information indicating the type of external device 20 and corresponds to "Telephone Type" in FIG. 12. "Connection Type" corresponds to "Connection Type" in FIG. 12. "Location" corresponds to "Location" in FIG. 12. "Step Number" is information indicating a step in the operational sequence and corresponds to "Step Number" in FIG. 15. "Setting Item" is a parameter related to an operational setting value, such as "Timer A," "Number of Retry Count," "Expire," and "Session Timer." "Statistical Value" stores a statistical value related to the operational value of the parameter of "Setting Item" corresponding to the combination of "External Device Type" to "Setting Item" in the row. Examples of statistical values ​​are the average value and variance. "Statistical count" stores information indicating how many times the statistical information for the corresponding row has been generated or updated.

[0136] Regarding the operation information and operation values, for example, as shown in the first row, a customer environment 2 can be identified that satisfies the conditions that the external device 20 is a SIP phone, the connection type is LAN, and the location of the base is Tokyo. Regarding the operation setting value of timer A for step S1 ("100 tries") of the operation sequence in that customer environment 2, the statistical value for the fourth time is "1010 ms," and the statistical value for the number of retries is "12 times." Furthermore, for example, as shown in the seventh row, a customer environment 2 can be identified that satisfies the conditions that the external device 20 is a SIP phone, the connection type is WAN, and the location of the base is Osaka. Regarding the operation setting value of timer A for step S1 ("100 tries") of the operation sequence in that customer environment 2, the statistical value for the sixth time is "1030 ms," and the statistical value for the number of retries is "12 times."

[0137] Such operational information and statistical values ​​relating to the operational values ​​can be used when generating the above-mentioned operational values.

[0138] [Specific example] Below, specific examples of generating and correcting operational values ​​for the customer environment 2 will be shown using Figures 18 and 19, etc. Figure 18 shows an image of inputting operational information into the parameter sheet 13 on the display screen of the terminal 30 of user U1, who is the person who set the parameters. Figure 18 shows specific examples of data and information. Figure 19 shows (A) an example of operational information, (B) an example of statistical information, (C) an example of corrected values ​​for operational setting values, and (D) an example of operational setting values ​​before and after correction.

[0139] First, an example of generating suitable operating values ​​based on operating information during initial configuration at the time of construction is as follows.

[0140] In the parameter sheet 13 on the screen of Fig. 18, parameter sheet information can be displayed for each tab item such as "Extension (required)", and parameter values ​​can be entered for each parameter item of operational information (for example, extension number, telephone type, connection type, location, etc.). For each item, candidate parameter values ​​are displayed, for example, in a list, and user U1 can select and enter values ​​from the candidates. For example, each item may be input using text.

[0141] The customer environment operation information setting unit 104 of the PBX system 1 in Fig. 2 registers the operation information entered in the parameter sheet 13 in the operation information DB 151. As an example of operation information according to the customer environment 2, assume that the location of the base is Osaka, the connection type is WAN, and the telephone type is SIP telephone (data in rows numbered 4 and 5 in Fig. 18). The operation information is shown in Fig. 19(A).

[0142] For this operational information, in the case of the first embodiment, the PBX system 1 extracts the data portion of the row indicated by the dashed frame from the table of the statistical information DB 163 in, for example, Figure 17 as data corresponding to the operational information. The extracted data portion has the value {SIP phone, WAN, Osaka, S1, Timer A, 1030 ms, 6}. This data value includes the statistical value "1030 ms" of the operational value of Timer A in step S1 of the operational sequence. This statistical information is shown in (B) of Figure 19.

[0143] Based on the above data values, the PBX system 1 can determine that the operation value (in other words, the correction value) of timer A in step S1 of the operation sequence should be set to "1030 ms" for the operation information of the customer environment 2. Taking into account the statistical values ​​of the operation status of similar customer environments 2, the PBX system 1 can propose "1030 ms" as the initial setting value (or the correction value for adjustment) of the operation value for a certain customer environment 2. This correction value is shown in Figure 19 (C).

[0144] The PBX system 1 reflects the determined operating value "1030 ms" in the portion indicated by the corresponding dashed frame in the operating setting value DB 154 in Fig. 14. For example, as shown in Fig. 19(D), the operating value before correction "1000 ms" is updated to the corrected operating value "1030 ms".

[0145] Next, a specific example of automatic adjustment of operational values ​​based on operational sequence monitoring is described below using Fig. 20. Fig. 20 shows (A) an example of operational sequence monitoring information, (B) an example of model sequence data, (C) a comparison between the model sequence and (D) the operational sequence, (E) an example of a correspondence table, and (F) an example of operational setting values.

[0146] Assume that the data collection unit 105 in Figure 2 has obtained operation sequence monitoring information (in other words, capture data) such as that shown in Figure 20(A). From this data, the following can be seen. Regarding the operation sequence for the outgoing call of call number 134 in (A), as shown in Figures 7 and 20(C) and (D), 1050 ms elapsed between the INVITE message from the PBX to SIP1 (external device 20) and the start of timer A counting (time 2001) and the "100 try" response from SIP1 (time 2003). 1050 ms is the difference between 10:50:24.856 and 10:50:25.906. Assume that the operation value of timer A before correction is 1030 ms. The end point of timer A's time of 1030 ms is time 2002. As shown in (D), the time until the "100 try" response, 1050 ms, exceeds the time of Timer A, 1030 ms (time point 2002). Therefore, as shown in the second line of (A) and (D), the INVITE message is retransmitted before the "100 try" response. The delay time from the time point 2002 when Timer A ends to the time point 2003 when the "100 try" response is received is 20 ms.

[0147] Considering the model sequences of Figure 7(A) and Figure 20(B), it is normal or preferable for the status of step S1 to respond to an INVITE message with "100 try" within the time of timer A. In contrast, in this example, in step S1, there is no "100 try" response within the time of timer A, and the "100 try" response occurs at time 2003, after the end of timer A at time 2002. Therefore, it can be determined that the monitored operation sequence is abnormal or inappropriate compared to the model sequence and requires correction.

[0148] As described above, the operation sequence check unit 106 of the PBX system 1 compares an operation sequence such as (A) or (D) in Figure 20 with a model sequence such as (B) or (C) to determine differences and changes in the status of multiple steps in time series. In particular, with regard to the operation value of the timer, the time for requests and responses between steps is determined. As a result of the comparison, the operation sequence check unit 106 can determine and detect a mismatch between the operation sequence (A) and the model sequence (B), for example, in the part of step S1, as in (C) and (D).

[0149] Based on the discrepancy resulting from the check, the PBX system 1 determines that the operational value for timer A in step S1 needs to be corrected. The operational correction value determination unit 107 references the operational information (such as the remote terminal information and the connection type) of the target customer environment 2 from the operational information DB 151, as shown in FIG. 9. The operational correction value determination unit 107 references the portion of the correspondence table of the setting value correction DB 161 in FIG. 15, which is indicated by a dashed line as the portion corresponding to step S1, where the discrepancy occurs. In particular, the portion corresponding to the details of the discrepancy is the "100 try reception (after timer A)" portion in the second row, as indicated by the dashed line. Furthermore, because the connection type is WAN, as shown in FIG. 19A, the operational information of the target customer environment 2 corresponds to the "WAN" column, as indicated by the dashed line. The correction adjustment value for the cell where these matrices intersect is the addition value "30 ms." This allows the operational correction value determination unit 107 to determine the correction value as the addition value "30 ms" (+30 ms). FIG. 20(E) shows the portion extracted from the correspondence table.

[0150] Using the determined correction value (+30 ms), corrective action unit 108 executes "Timer A correction" shown in the "Correction Action" column. As shown in (F) of Fig. 20, corrective action unit 108 corrects the operation value (1030 ms) of timer A extracted from operation setting value DB 154 by the correction value (+30 ms), and registers the corrected operation value (1060 ms) in operation setting value DB 154. As a result, the operation setting value of timer A related to the initial retransmission interval of an INVITE request is updated from 1030 ms to 1060 ms.

[0151] Although the above describes an example of processing in which each processing unit in Fig. 2 reads and writes to each DB each time, the present invention is not limited to this. A processing unit can also read necessary information from a DB, and then pass the information to another processing unit, without the other processing unit accessing the DB.

[0152] When the operation setting values ​​are updated, the PBX system 1 may notify the user U1 who set the values. For example, the status of the updated operation setting values ​​may be displayed together with a GUI on the display screen of the terminal 30 of the user U1. This allows the user U1 to check the status of the updated operation setting values ​​on the screen.

[0153] 21 shows an example of a screen displaying the status of updated operational setting values ​​on the display screen of user U1's terminal 30. The operational information and operational setting values ​​of the customer environment 2 on this screen may be displayed using tables of each DB, or may be displayed in a format converted based on the information of each DB.

[0154] The example screen in Figure 21 displays customer information and information about customer environment 2, which user U1 can select and display. Area 2101 displays the current status of the operational setting values ​​when the automatic adjustment shown in the specific example above is performed. The screen also displays a notification that the operational value of timer A has been adjusted to match the customer environment. User U1 can check the current status of the operational values ​​and the fact that automatic adjustment has been performed on this screen.

[0155] As another example of the screen, the operational values ​​before and after the correction may be displayed side by side, or the user U1 may be asked whether or not to apply the correction, and the correction may be performed only if the user U1 selects the affirmative. If the user U1 does not want to apply the correction, the user U1 may manually set it.

[0156] After the automatic adjustments based on the correction of the operational values ​​described above, the operational sequence in customer environment 2 becomes more optimal. Figure 22 shows examples of operational sequences before and after the correction. In the operational sequence before correction (A), as described above, there is no "100 try" response even though the timer A time of 1030 ms (time point 2202) has elapsed since the first INVITE message (time point 2201), resulting in a retransmission of the INVITE message. In contrast, in the operational sequence after correction (B), even if a "100 try" response occurs at the same time point 2203 as in (A), the response will be received within the adjusted timer A time of 1060 ms (time point 2204). As a result, the INVITE message will not be retransmitted. Therefore, the operation after the correction is more optimal than before the correction.

[0157] Furthermore, automatic adjustments can be made using the same mechanism during subsequent operations. For example, if the operational values ​​after the first correction are determined to be abnormal, a second adjustment will be made. By continuing to monitor the operation, adjustments will be made as many times as necessary, and as a result, the operational values ​​can be brought closer to the optimal values.

[0158] 22(C) and (D), the statistical information in the statistical information DB 163 is also updated with each adjustment. For example, (C) is the statistical information before the update, and (D) is the statistical information after the update. The statistical value is recalculated by taking into account the adjusted operational value of timer A, 1060 ms, and the resulting statistical value of 1034 ms is registered as the updated statistical value of timer A, 1034 ms. In addition, the number of times the statistics are collected is updated from 6 to 7.

[0159] However, for example, if the time set for Timer A becomes too long as a result of adjusting Timer A in step S1, retransmission will not occur, but the operation value may not be optimal. Therefore, as in the flow in B of Figure 9, even if there is no mismatch, it is possible to check whether the operation value is appropriate and adjust the time set for Timer A to be shorter by correcting the operation value using, for example, the subtraction value in Figure 15. This allows the time set for Timer A to be brought closer to the optimal value.

[0160] [Effects of the first embodiment] As described above, according to the PBX setting value correction system and method of embodiment 1, it is possible to achieve efficiency and optimization in the settings, including operational settings according to the customer environment, when constructing and operating a PBX in the customer environment. As a result, it is possible to reduce the effort, time, cost, etc. of manual setting work, and to achieve efficient and suitable setting work and operation.

[0161] According to the first embodiment, operation settings can be supported to achieve more optimal operation values ​​without relying on the knowledge and experience of the person setting them at the construction company. During construction, optimal initial settings of operation values ​​can be made using statistical information related to the operation of multiple customer environments. Furthermore, even if a discrepancy occurs between the actual operation status and the operation setting parameter values ​​after operation has begun, automatic adjustments can be made to achieve more optimal operation values ​​based on operation sequence monitoring information. This reduces the need for a construction company to visit the customer environment each time to adjust the operation values.

[0162] According to embodiment 1, statistical information regarding the operation of the customer environment is accumulated and operational values ​​are corrected using the statistical information, so that know-how on PBX operational settings can be accumulated by the system and shared between individuals without relying on individuals, thereby making operational settings more efficient.

[0163] [About modified examples] In the first embodiment, an example has been described in which the PBX system 1 as a cloud PBX realizes functions such as operational value correction. In particular, when implementing the functions using the statistical information described above, it is preferable to use a cloud PBX as in the first embodiment. However, this is not limited to this. As will be described later, the functions in the first embodiment are also applicable to an IP-PBX. In the case of a PBX system using an IP-PBX, there is a form in which the functions using the statistical information described above are not implemented, but this is not limited to this. As will be described later, it is also possible to implement the functions using the statistical information described above by linking PBX systems using multiple IP-PBXs or using a higher-level system.

[0164] In the first embodiment, as shown in Fig. 2, the PBX system 1 has the PBX setting support unit 102 in addition to the PBX communication unit 101 that realizes the PBX function, but is not limited to this. It may also be implemented as a system having only the PBX setting support unit 102 without the PBX communication unit 101.

[0165] In the first embodiment, it has been explained that when a model sequence is defined as a normal operation sequence based on the specifications of a certain PBX, it is possible to accommodate differences in operation depending on the customer environment 2. However, this is not limiting, and the functions of the first embodiment can be similarly applied to the specifications of various known PBXs. For example, a model sequence may be defined for each variation in the specifications of the PBX.

[0166] As will be described later, it is also possible for any computer system installed in the customer environment 2, for example, a dedicated device such as a server or a single external device 20, to realize the same functions as those in embodiment 1. In this case, the computer system in the customer environment 2 performs processes such as operational sequence monitoring and operational value correction.

[0167] Furthermore, as will be described later, it is also possible to realize the same functions as those of the first embodiment, for example, in a client-server system between a computer system of, for example, a business operator outside the customer environment 2 and a computer system within the customer environment 2. A client terminal or server that can be operated by a person configuring the settings is provided within the customer environment 2. In this case, the computer system within the customer environment 2 may only be responsible for configuration support functions including a GUI, such as the function of the parameter sheet 13 and the setting value confirmation function, or may be responsible for processing such as operation sequence monitoring and operation value correction.

[0168] The functions in the first embodiment have been described as being implemented almost entirely automatically by a computer system, but this is not limiting. While the main processing of the functions described above is performed by a computer or the like, some of the functions may require human intervention. For example, the input and acquisition of operational information using the parameter sheet 13 described above can be achieved automatically, such as by a computer reading and interpreting the parameter sheet 13 to extract operational information. Alternatively, a person such as a configurator or administrator may perform auxiliary tasks, such as formatting some of the operational information entered in the parameter sheet 13 or entering missing information. Furthermore, for example, communication and user interfaces on the PBX setting value correction system may be used to communicate instructions and responses between the operator's administrator, the installer's configurator, or the customer's user.

[0169] [Variation 1] FIG. 23 shows an example of the overall system configuration including a PBX setting value correction system according to Variation 1 of Embodiment 1. Variation 1 shows an example of an IP-PBX type system, rather than a cloud PBX type system as in Embodiment 1. In Variation 1, a PBX system 1 is configured as an IP-PBX system for each customer environment 2. In the example of FIG. 23, customer environment A has a PBX system 1A, and customer environment B has a PBX system 1B. Similarly, a PBX system 1 as an IP-PBX system is provided for each customer environment 2. The PBX system 1 is under the control of a business operator.

[0170] The PBX system 1 for each customer environment 2 is configured by, for example, a server or the like in a computer system at a base or the like of the customer environment 2, but is not limited to this. The functions of the PBX system 1 may also be configured by a computer such as a server of a business outside the customer environment 2. In this case, the server or the like outside the customer environment 2 communicates with an external device 20 or the like within the customer environment 2. The functions of the PBX system 1 may also be realized by communication between a server computer of a business outside the customer environment 2 and a client computer within the customer environment 2 in a client-server system.

[0171] In Modification 1, the PBX system 1 for each customer environment 2 has a function to correct the operational values ​​of that customer environment 2, and the details of this function are the same as in Embodiment 1. The main difference between Modification 1 and Embodiment 1 is that it does not have the function to use the statistical information described above.

[0172] User U1, who is a configurator A for contractor A and in charge of customer environment A, performs configuration CA for customer environment A in PBX system 1A from terminal 30. User U1, who is a configurator B for contractor B and in charge of customer environment B, performs configuration CB for customer environment B in PBX system 1B from terminal 30. PBX system 1A monitors the operation sequence based on communications QA1 and QA2 between server 10 with PBX functionality and external device 20 in customer environment A. Similarly, PBX system 1B monitors the operation sequence based on communications QB1 and QB2 between server 10 with PBX functionality and external device 20 in customer environment B. PBX system 1A corrects the operation values ​​for customer environment A based on the monitoring information and updates DB 12. PBX system 1B corrects the operation values ​​for customer environment B based on the monitoring information and updates DB 12.

[0173] Fig. 24 shows an example of a functional block configuration of the PBX system 1 in Modification 1. The configuration of Modification 1 differs from the configuration of Fig. 2 in that the server 10 does not have a DB update unit 109 and the common DB 16 does not have a statistical information DB 163. On the other hand, in Modification 1, the customer DB 15 for each customer environment 2 additionally has an operation value determination DB 155.

[0174] The operational value determination DB 155 is a DB in which information is set for determining operational values ​​(for example, initial settings at the time of construction) for operational information for each customer environment 2 without using statistical information.

[0175] FIG. 25 illustrates an example of the configuration of the operational value determination DB 155 in the first modification. The operational value determination DB 155 in FIG. 25 includes a table. This table includes columns such as "External Device Type," "Connection Type," "Location," "Step Number," "Setting Item," and "Operation Value." The columns from "External Device Type" to "Setting Item" contain the same information items as the columns in the table of the statistical information DB 163 in FIG. 17. The table of the operational value determination DB 155 does not include the "Statistical Value" column of the table of the statistical information DB 161, but instead includes a column of "Operation Value." In this table, "Operation Values" for "Setting Item" for each step of the operational sequence are preset as operational information for the customer environment 2, depending on the values ​​of "External Device Type," "Connection Type," and "Location." When a value of the operational information for the customer environment 2 is given, the PBX system 1 can refer to the row in this table corresponding to that value and determine the "Operation Value."

[0176] The processing flow in Modification 1 is roughly similar to the flow in FIG. 4 of Embodiment 1, but the main difference is that the DB update process in step S107 is not included. Processing is performed for each PBX system 1 in the customer environment 2 according to the flow shown in FIG. 4 (excluding step S107). Also, in Modification 1, when the PBX system 1 is initially set up at the time of construction in step S101, the PBX system 1 generates initial setting operating values ​​using the operating value determination DB 155 without using statistical information. Alternatively, in a configuration without the operating value determination DB 155, the PBX system 1 may be initially set as in the past. In Modification 1, at least the correction of operating values ​​based on operation sequence monitoring can be achieved in the same way as in Embodiment 1.

[0177] Fig. 26 is an explanatory diagram relating to the setting of operational information in step S102 of Fig. 4 in Modification 1. For example, in steps S201 to S204 in Fig. 26, PBX system 1A in customer environment A in Fig. 23 acquires operational information entered into parameter sheet 13 by user U1, who is the setting person, and registers it in operational information DB 151 of customer DB 15. Up to this point, it is the same as in Embodiment 1.

[0178] Next, in step S211, the operation value generation unit 110 of the PBX system 1A extracts an operation value corresponding to the operation information of the above-mentioned customer environment 2 from the operation value determination DB 155. For example, if the value of the operation information is {SIP phone, WAN, Osaka} as in (A) of FIG. 19, the data portion of the corresponding row is extracted from the table of the operation value determination DB 155 in FIG. 25, as shown in the dashed frame. The extracted data portion has the value {SIP phone, WAN, Osaka, S1, timer A correction, 1000 ms}. This data value includes the correction value "1000 ms" of the operation value of timer A in step S1 of the operation sequence. From the above data value, the PBX system 1 can determine that "1000 ms" should be set as the operation value of timer A in step S1 of the operation sequence for the operation information of customer environment A.

[0179] Next, in step S212, the operation value generation unit 110 of the PBX system 1A registers the extracted operation value in the operation setting value DB 154 of Fig. 14. That is, in the case of the initial settings at the time of construction, 1000 ms is registered as the operation value of timer A in the operation setting value DB 154. If an operation value has already been set in the operation setting value DB 154, the operation value is updated to 1000 ms.

[0180] As described above, according to variant example 1, even in the case of an IP-PBX, it is possible to adjust operational values ​​based on operational sequence monitoring, as in embodiment 1, and it is possible to adjust operational values ​​in a closed manner within the target customer environment 2 without using statistical information regarding multiple customer environments.

[0181] In FIG. 23, the PBX system 1 may be isolated for each customer environment 2. However, as a further modification, the PBX systems 1 for each customer environment 2 may be linked via wide-area communication. For example, a provider's host system may be installed outside the customer environment 2, and the PBX system 1 for each customer environment 2 may communicate with the host system. Alternatively, one or more of the multiple PBX systems 1 may be additionally equipped with the functionality of a host system. The host system may, for example, collect and store information from the PBX system 1 of each customer environment 2. The host system may also perform functions related to the aforementioned statistical information. In this case, the host system may generate statistical information based on the information collected and stored from the PBX system 1 of each customer environment 2 and provide the statistical information to the PBX system 1 of each customer environment 2. The PBX system 1 of each customer environment 2 may use the provided statistical information to generate and correct operational values.

[0182] [Variation 2] FIG. 27 shows an example of the overall system configuration including a PBX setting value correction system according to Modification 2, which is another modification of Embodiment 1. Similar to Embodiment 1, Modification 2 is premised on, for example, a cloud PBX. For example, as shown in FIG. 27, a data center 100 has a computer system 1a as a component of the PBX system 1. In addition, in Modification 2, a computer system 1b as a component of the PBX system 1 is also provided in a base system, for example, within a customer environment 2. The computer system 1b provided within the customer environment 2 and the computer system 1a in the data center 100 communicate with each other. This communication may be, for example, a client-server communication system. The PBX system 1 is configured through this communication.

[0183] The computer system 1a in the data center 100 is configured to include, for example, a server 10 and a DB 12, similar to the first embodiment. The computer system 1b in the customer environment 2 is configured to include, for example, a server 21 and a DB 22. For example, in the system at base A1 of the customer environment A, the computer system 1b is connected to a LAN. The server 21 cooperates with the server 10 by communicating with it.

[0184] The computer system 1b in the customer environment 2 is responsible for some of the functions of the aforementioned PBX system 1. In this example, the computer system 1b in the customer environment 2 is responsible for monitoring the operation sequence of the customer environment 2 and managing the operation settings of the customer environment 2, in other words, providing a GUI.

[0185] User U1, who is the configurator A of customer environment A, performs configuration work on server 10 on the cloud or server 21 in customer environment A from terminal 30. In this example, user U1 performs configuration CA on server 21 in customer environment A from terminal 30. Server 21 provides parameter sheet 13 for configuration support to terminal 30. Server 21 acquires the operational information entered in parameter sheet 13 and registers it in DB 22 in customer environment 2.

[0186] The server 21 may also communicate with the server 10 and transmit the information in the DB 22 to the server 10, in which case the server 10 registers the information acquired from the server 21 in the DB 12.

[0187] The server 10 provides a function as a cloud PBX, similar to the first embodiment. When the external device 20 in the customer environment 2 uses a PBX, communication is performed between the external device 20 and the PBX function of the server 10. For example, communication QA1 is communication between the external device 20 in the base A1 and the PBX function of the server 10, and has a corresponding operation sequence.

[0188] The server 10 or the server 21 monitors the operation sequence of communication between the external device 20 in the customer environment 2 and the PBX function of the server 10. In this example, the server 21 in the base A1 of the customer environment A monitors the operation sequence. The server 21 stores the monitored information, an operation sequence log, in the DB 22 and transmits the monitored information to the server 10 at an appropriate timing. The server 10 stores the operation sequence log, which is the monitoring information acquired from the server 21, in the DB 12.

[0189] Similar to the first embodiment, the server 10 corrects the operation values ​​of the customer environment 2 based on the monitoring information of the operation sequence, and registers the corrected operation values ​​in the DB 12. The server 10 transmits the corrected operation values ​​to the server 21. The server 21 registers the corrected operation values ​​in the DB 22. This updates the operation of the PBX at the location A1.

[0190] In the above example, a computer system 1b such as a server 20 separate from the external device 20 is provided within the base of the customer environment 2, but this is not limiting. In other embodiments, a function equivalent to the server 20 may be implemented in, for example, one specific external device 20 (e.g., a SIP gateway) within the customer environment 2. The specific external device 20 may download and install an application program, data set, etc. for realizing the function from the provider's system.

[0191] [Variation 3] FIG. 28 is an explanatory diagram illustrating an overview of a PBX setting value correction system according to Modification 3, which is another modification of Embodiment 1. The PBX system 1 in the PBX setting value correction system according to Modification 3 not only generates operational values ​​using statistical information when the PBX system is constructed, but also corrects the operational values ​​using statistical information after operation has begun. In FIG. 28, the vertical axis shows an example of the timing of generating and correcting operational values, with the horizontal axis representing time series, when multiple customer environments 2, such as customer environments A (A1, A2) and B (B1, B2) shown in FIG. 1, are used. When constructing the PBX system for each customer environment 2 (e.g., at times t11, t21, t31, and t41), optimal initial settings can be achieved by using the aforementioned function for generating operational values ​​using statistical information. If sufficient data is not collected, manual configuration may be used instead of configuration using statistical information.

[0192] Furthermore, in Modification 3, the PBX system 1 has a function of correcting operational values ​​using statistical information even after operation has begun. For example, for location A1 in customer environment A, the PBX system 1 adjusts the operational values ​​initially set at time t11 by correcting them at time t12 using the statistical information at that time. Similarly, the PBX system 1 adjusts the operational values ​​at time t12 by correcting them at time t13 using the statistical information at that time. Similarly, for locations B1 and B2 in customer environment B, the operational values ​​are corrected at appropriate times (times t32, t33, t42, and t43).

[0193] The timing for correcting the operation values ​​using statistical information may be when a discrepancy occurs as a result of the above-mentioned operation sequence monitoring, or when the statistical information is updated. For example, it may be when a change occurs in the operation configuration of the customer environment 2 within the statistical collection range. Furthermore, although the operation sequence monitoring in the above-mentioned first embodiment is continuous monitoring (for example, during business hours every day), it is not limited to this and may be periodic monitoring (for example, once a day, once a week, etc.) according to user settings, etc.

[0194] Although the embodiments of the present disclosure have been specifically described above, they are not limited to the above-described embodiments and can be modified in various ways without departing from the spirit of the present disclosure. Except for essential components, components can be added, deleted, or replaced in each embodiment. Unless otherwise specified, each component can be singular or plural. A combination of each embodiment and its variations is also possible. [Explanation of symbols]

[0195] 1...PBX system, 2...customer environment, 3...construction contractor, 4...maintenance center, 10...server, 11...router, 12...DB, 13...parameter sheet, 20...external device, 30...terminal, U1...user, 100...data center, CA...settings, QA1...communication (operation sequence), 1001...correction of operation values.

Claims

1. A method for correcting settings of a private branch exchange (PBX), comprising: The steps performed by the computer are: a step in which the computer monitors an operation sequence of the PBX in the customer environment and acquires monitoring information of the operation sequence; a step in which the computer corrects an operation value among setting information of the PBX in the customer environment based on a comparison between the operation sequence based on the monitoring information and a predefined model sequence; A private branch exchange setting value correction method comprising:

2. 2. The method for correcting private branch exchange settings according to claim 1, a step in which the computer provides a parameter sheet for acquiring operation information of the PBX according to the customer environment to a setting person; a step in which the computer acquires the operation information input by the setter into the parameter sheet; and the step of correcting the operational value is a step of correcting the operational value of the PBX in the customer environment based on a result of comparison between the operational sequence and the model sequence and the operational information, A method for correcting private branch exchange setting values.

3. 3. The method for correcting private branch exchange settings according to claim 2, The step of correcting the operational value is a step of referring to a predetermined correspondence table, extracting a correction value for the operational value from the correspondence table in accordance with a combination of the status of the step of the operational sequence, which is the mismatched part in the comparison result, and the operational information, and correcting the operational value with the correction value. A method for correcting private branch exchange setting values.

4. 2. The method for correcting private branch exchange settings according to claim 1, a step in which the computer collects the operational values ​​for each of a plurality of customer environments and generates statistical information based on the collected information; a step in which the computer generates the operational values ​​of the setting information of the PBX in the customer environment using the statistical information; A private branch exchange setting value correction method comprising:

5. 5. The method for correcting private branch exchange settings according to claim 4, a step of said computer acquiring operation information of said customer environment when constructing said PBX in a new customer environment; the step of generating the operational value is a step of generating the operational value for initial setup of the PBX in the customer environment by the computer using the statistical information and the operational information; A method for correcting private branch exchange setting values.

6. A private branch exchange (PBX) setting value correction system including a computer for correcting setting values ​​relating to a private branch exchange (PBX), The computer monitoring an operation sequence of the PBX in a customer environment, and acquiring monitoring information of the operation sequence; correcting an operational value among setting information of the PBX in the customer environment based on a comparison between the operational sequence based on the monitoring information and a predefined model sequence; Private branch exchange setting value correction system.

7. 7. The private branch exchange setting value correction system according to claim 6, The computer providing a parameter sheet for acquiring operational information of the PBX according to the customer environment to a configurator; Acquire the operational information input by the setter into the parameter sheet; When correcting the operational value, the operational value of the PBX in the customer environment is corrected based on a result of the comparison between the operational sequence and the model sequence and the operational information. Private branch exchange setting value correction system.

8. 8. The private branch exchange setting value correction system according to claim 7, When correcting the operational value, the computer refers to a predefined correspondence table, extracts a correction value for the operational value from the correspondence table in accordance with a combination of the status of the step of the operational sequence, which is the mismatched part in the comparison result, and the operational information, and corrects the operational value using the correction value. Private branch exchange setting value correction system.

9. 7. The private branch exchange setting value correction system according to claim 6, The computer Collecting the operational values ​​for each of a plurality of customer environments, and generating statistical information based on the collected information; generating the operational values ​​of the setting information of the PBX in the customer environment using the statistical information; Private branch exchange setting value correction system.

10. 10. The private branch exchange setting value correction system according to claim 9, The computer When constructing the PBX in a new customer environment, operation information of the customer environment is acquired; generating the operational values ​​for initial setup of the PBX in the customer environment using the statistical information and the operational information when generating the operational values; Private branch exchange setting value correction system.

Images