JP2005151478A - Private branch exchange system, private branch exchange, and charging method used for same - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a private branch exchange system which can perform charging collection for used parts of an IP network, irrespective of connection patterns of IP terminals in any composition or using status. <P>SOLUTION: When an IP terminal (B) 2-2 in a center office 1-1 or an IP terminal (D) 2-4 in a remote office 1-3 moves into another remote office 1-2, the private branch exchange 3 automatically acquires own IP address, IP address of the accommodated private branch exchange, area information, etc. from an IP device (B) 6-1 by connecting with the IP network 101, accommodates the IP terminal (B) 2-2 and the IP terminal (D) 2-4 using the known technology based on these information, and makes them in an usable condition. The private branch exchange 3 controls area information, automatically gives association with IP address, designated area information, and extension number for a registration request from the IP terminal, and manages the area. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to a private branch exchange system, a private branch exchange, and a billing method used therefor, and more particularly, to a billing method for an IP network used by an IP (Internet Protocol) terminal between remote offices in a VoIP (Voice over Internet Protocol) private branch exchange system. .

  Conventionally, in an IP network, a PRI (Primary Rate Interface) / BRI (Basic Rate Interface) line interface function implemented in a private branch exchange is used, and voice conversion [TDM (Time Division Multiplexing) is performed at the VoIP gateway at the end of the line. ) -IP].

  In this case, the address of the IP extension telephone installed on the IP network is resolved at each gateway connected to the private branch exchange. As a result, IP extension telephones that move between IP networks are accommodated (see, for example, Patent Document 1).

JP 2001-285476 A

  In the above-described conventional IP network, even when an IP terminal moves between remote offices, the service can be inherited without making the caller aware of the moving location by accommodating the extension number to be used. . On the other hand, in the conventional IP network, the extension number managed by the charging information of the private branch exchange system is not changed, so the moving location cannot be specified, and charging is collected for the public or private IP network used at the moving destination. Can not do.

  Therefore, in a conventional IP network, charging for extension mutual calls between IP terminals controlled by a VoIP-compatible private branch exchange system, or an analog / ISDN (Integrated Services Digital Network) trunk line installed in an IP terminal and a remote office ( Hereinafter, information collection for charging between IP devices having a TRK line) is performed by extension number or TRK line number, and the connection state in the network cannot be managed.

Also, in the conventional IP network, even if the connection state is managed, there is no means other than constructing a static database, and the conventional billing collection method can be adapted to the case where the IP terminal moves between remote offices. Can not.
In the conventional IP network, there is a problem that an IP address or a MAC (Media Access Control) address cannot be used for specifying a movement destination.

  In a conventional IP network, for example, a phone that is used as an IP terminal is not moved, but only an extension number is moved (the user's own phone ID is used to log in using the user's destination ID) Area information can be specified using the MAC address.

  However, in a conventional IP network, in the case of an IP terminal that operates as an application installed in a portable PC (personal computer), or when it is moved and used for each telephone used as an IP terminal, it is remote including the terminal. Since it moves between offices, the MAC address also moves between remote offices, so it cannot be used to specify the destination.

  In addition, the reason why the IP address cannot be used for specifying the movement destination is that the global address and the private address are the same in a situation where a public or private IP network is used between a plurality of remote offices. It becomes impossible to specify the destination.

  For example, in a conventional IP network, even if management and operation are performed using IP addresses, the manufacturer, SE (System Engineer), and maintenance personnel must specify the range of IP addresses used at the installation destination. And may not be accepted by network administrators.

  In addition, in the conventional IP network, even if the private IP address range is managed by the private branch exchange, it is necessary to change the management data setting of the private branch exchange every time the IP network is changed. Problems will arise.

  In other operation cases, regardless of whether or not the IP address for the mobile terminal is used, the IP address is always secured, and the management data setting on the private branch exchange side is performed to identify the destination. It is possible. However, in other operation cases, in order to identify the destination, the IP address group used by the mobile terminal must be retained regardless of whether it is used, which is a cause of IP address depletion. There is a risk of becoming.

  Further, in another operation case, it is indicated that if an IP address used by an IP extension is specified, an operation using a DHCP (Dynamic Host Configuration Protocol) server cannot be performed in obtaining an IP address of the IP terminal. There seems to be a problem in force.

  In any case, if the above problem is solved with the MAC address or IP address, there is a problem in terms of serviceability and maintainability, and it is considered that the MAC address or IP address cannot be selected.

  Therefore, an object of the present invention is to eliminate the above-mentioned problems, and in any configuration or usage situation, a private branch exchange system and a private branch exchange that can collect charges for the portion of the IP network used regardless of the connection pattern of the IP terminal And a billing method used therefor.

A private branch exchange system according to the present invention is a private branch exchange system in which a center station including a private branch exchange and a plurality of remote offices each accommodating an IP (Internet Protocol) terminal are connected via at least an IP network,
Associating means for associating an IP address with designated area information and an extension number in response to a registration request from the IP terminal, and means for managing an area where the IP terminal exists based on the association, in the private branch exchange Prepared,
A charging device is provided that collects and outputs charging information according to the connection state of the IP network that changes according to the destination of the IP terminal based on the area information.

  A private branch exchange according to the present invention is a private branch exchange disposed in the center station in a system in which a center station and a plurality of remote offices each capable of accommodating an IP (Internet Protocol) terminal are connected via at least an IP network. And an association means for associating an IP address, designated area information, and an extension number with a registration request from the IP terminal, and means for managing an area where the IP terminal exists based on the association. ing.

The charging method according to the present invention is a charging method for the IP terminal in a private branch exchange system in which a center station including a private branch exchange and a plurality of remote offices each capable of accommodating an IP (Internet Protocol) terminal are connected via at least an IP network. A billing method for
A first step of associating an IP address, designated area information, and an extension number in response to a registration request from the IP terminal on the private branch exchange side, and managing an area where the IP terminal exists based on the association And a second step to
A billing device collects and outputs billing information according to the connection state of the IP network that changes according to the destination of the IP terminal based on the area information.

  That is, since the private branch exchange system of the present invention knows the location of a movable IP (Internet Protocol) terminal by managing area information independently, the IP address and the MAC address are moved when the IP terminal moves. It is possible to manage the destination area without using it, and it is possible to collect charges for the IP network usage part regardless of the connection pattern of the IP terminal in any IP network configuration and usage situation. .

  The private branch exchange system of the present invention comprises a center station including a private branch exchange and a plurality of remote offices connected to the center station via at least an IP network. An IP device that cannot be moved is installed in the remote office.

  The IP device has a unique DHCP (Dynamic Host Configuration Protocol) function including an analog / ISDN (Integrated Services Digital Network) trunk line (hereinafter referred to as a TRK line) and an authentication function for authenticating a user to be used. ing.

  In the private branch exchange system of the present invention, by managing the area information of the remote office using the DHCP function and authentication function of this IP device, the private branch exchange is automatically accommodated regardless of the area where the IP terminal is installed. Can be used. Therefore, even if the IP terminal moves between remote offices, the public who changes according to the destination by recognizing that the IP terminal has moved easily and automatically without being aware of the user / maintenance person. The billing information can be collected and output according to the connection state of the IP network or the local IP network.

  Therefore, in the private branch exchange system of the present invention, an area (region) where the IP terminal is installed is specified without using information such as an IP address and a MAC address, and the data change of the private branch exchange is performed for the management. It is possible to collect and output charges for the public / premises IP network used between the remote offices as needed based on the area information, without requiring any other special modification work.

  With the configuration and operation described below, the present invention has the effect of being able to collect charges for the IP network usage portion regardless of the connection pattern of the IP terminal, regardless of the configuration or usage situation. It is done.

  Next, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a block diagram showing the configuration of a private branch exchange system according to an embodiment of the present invention. In FIG. 1, a private branch exchange system according to an embodiment of the present invention includes a center station [AC (area code) -0: Tokyo] 1-1, a remote office (AC-1: Osaka) 1-2, a remote office ( AC-2: Fukuoka) 1-3.

  The center station 1-1 is connected to a remote office 1-2 via a billing target IP (Internet Protocol) network 101, and is connected to a remote office 1-3 via a billing non-target IP network 102. The remote office 1-2 and the remote office 1-3 are connected to each other via an analog / ISDN (Integrated Services Digital Network) 103.

  The center station 1-1 includes a private branch exchange 3, a billing device 4, and a router 5-1, and accommodates movable IP terminals (A) 2-1 and IP terminals (B) 2-2. The remote office 1-2 includes a router 5-2 and an IP device (B) 6-1, and can accommodate movable IP terminals (B) 2-2 and IP terminals (D) 2-4. Yes. The remote office 1-3 includes a router 5-3 and an IP device (A) 6-2, and accommodates movable IP terminals (C) 2-3 and IP terminals (D) 2-4.

  FIG. 2 is a block diagram showing the configuration of the private branch exchange 3 of FIG. In FIG. 2, the private branch exchange 3 includes a TCP (Transmission Control Protocol) / IP I / F (interface) 31, a call control processing unit 32, and a database 33 including an area information management memory area 33a.

  FIG. 3 is a block diagram showing the configuration of the charging apparatus 4 of FIG. In FIG. 3, the billing apparatus 4 includes a TCP / IP I / F 41, a billing processing unit 42, and a billing information memory 43, and performs billing output.

  FIG. 4 is a block diagram showing the configuration of the IP device (B) 6-1 and the IP device (A) 6-2 in FIG. In FIG. 4, an IP device (B) 6-1 and an IP device (A) 6-2 are DHCP (Dynamic Host Configuration Protocol) having an analog / ISDN (Integrated Services Digital Network) trunk line (hereinafter referred to as a TRK line). ) A function 61 and a user authentication function 62 for authenticating a user to be used are incorporated.

  Private branch exchange 3 includes IP terminal (A) 2-1 and IP terminal (B) 2-2 accommodated in center station 1-1, billing apparatus 4, and IP terminal accommodated in remote office 1-2. (B) 2-2 and the IP terminal (D) 2-4, and the IP terminal (C) 2-3 and the IP terminal (D) 2-4 accommodated in the remote office 1-3 are all controlled. However, the connection between the IP terminals or between the IP terminal and the IP device used for connection outside the office is directly connected without going through the private branch exchange 3.

  In the above configuration, the IP network 102 in the center station 1-1 or between the center station 1-1 and the remote office 1-3 is a non-billing private IP network that does not need to be collected. The IP network between the center station 1-1 and the remote office 1-2 is a public IP network 101 to be charged.

  When the IP terminal (B) 2-2 in the center station 1-1 or the IP terminal (D) 2-4 in the remote office 1-3 moves to another remote office 1-2, the private branch exchange 3 By connecting to the network 101, it automatically obtains its own IP address / IP address / area information of the private branch exchange from the IP device (B) 6-1 and uses a known technique based on the information. Then, the IP terminal (B) 2-2 and the IP terminal (D) 2-4 are accommodated and are in a usable state.

  In this embodiment, the area information can be newly managed, and from the IP terminal (A) 2-1, IP terminal (B) 2-2, IP terminal (C) 2-3, and IP terminal (D) 2-4. In response to the registration request, the IP address, the designated area information, and the extension number are automatically associated to manage the area where each IP terminal is installed.

  The private branch exchange 3 has an IP terminal (A) 2-1, an IP terminal (B) 2-2, an IP terminal (C) 2-3, and an IP terminal on call control processing for interconnecting extensions and connecting an extension to a trunk. (D) In order to distinguish between 2-4 and general extension, unified management using the accommodation position is performed. The accommodation position is data used as an index of a database (not shown) in the private branch exchange 3.

  Private branch exchange 3 accommodates IP terminal (A) 2-1, IP terminal (B) 2-2, IP terminal (C) 2-3, and IP terminal (D) 2-4, and is used in the same manner as a general extension. In order to make this possible, a correspondence table between the accommodation location and the IP address is created, and the IP address and the extension number are associated by two methods.

  The first method is a method of determining an extension number by checking a MAC (Media Access Control) address in advance, and the other method is IP terminal (A) 2-1, IP terminal (B) 2-2. When the IP terminal (C) 2-3 and the IP terminal (D) 2-4 transmit a registration request using a user input value such as a user ID (identification information), and for the MAC address described above This is a method of determining a user ID as an extension number when an extension number assignment database is not registered.

  The association between the extension number and the IP address is performed by these two methods. By performing this association, the private branch exchange 3 can calculate an IP address for the extension number to be handled, and can perform the same call control as that of a general extension. So far, this is a known technique.

  As a result, the private branch exchange 3 recognizes that the IP terminal (B) 2-2 has moved to the remote office 1-2, and between the IP terminal (A) 2-1 and the IP terminal (B) 2-2. As for charging at the time of extension mutual calls, it is possible to correctly determine the movement from the non-charging target of the IP networks 101 and 102 to the charging target.

  Similarly, for the IP terminal (D) 2-4, the private branch exchange 3 correctly recognizes that the area of the IP terminal (D) 2-4 has moved from the remote office 1-3 to the remote office 1-2. be able to.

  Thus, the area that can flexibly cope with the movement of the IP terminal (A) 2-1, the IP terminal (B) 2-2, the IP terminal (C) 2-3, and the IP terminal (D) 2-4. By collecting and outputting billing information based on the information management method and data, billing information management according to the IP network 101 used between areas can be performed.

  FIG. 5A is a diagram showing the configuration of the area information management memory area 33a used in the embodiment of the present invention, and FIG. 5B is a diagram showing network settings in the embodiment of the present invention.

  FIG. 6 is a sequence chart showing an operation when accommodating an IP terminal according to an embodiment of the present invention in a private branch exchange. FIG. 6 shows the operation when the IP address of the IP terminal is set individually. With reference to FIG. 1 to FIG. 6, the operation when the IP terminal according to the embodiment of the present invention is accommodated in the private branch exchange will be described. In the following description, it is assumed that the IP terminal (B) 2-2 has moved to the remote office 1-2.

  When the IP terminal (B) 2-2 moves to a different area (area of the remote office 1-2) on the IP network 101, the IP terminal sets the IP address and changes / registers the default gateway IP address and the like (FIG. 6). A1). Thereafter, if the IP terminal (B) 2-2 is a PC (personal computer) installation type, the application is started (a2 in FIG. 6), and if it is a telephone type, an automatic reset / restart-up process is performed.

  The IP terminal (B) 2-2 requests the IP device (B) 6-1 for its own IP address and the IP address of the private branch exchange 3 (a3 in FIG. 6), and the IP device (B) 6-1 The request source product authenticates with the IP terminal accommodated in the private branch exchange 3 (a11 in FIG. 6) by checking the encrypted terminal ID (identification information), and the authentication result is normal (OK) If so (a12 in FIG. 6), the requested information is returned (a14 in FIG. 6). If the authentication result is abnormal (NG) (a12 in FIG. 6), the IP device (B) 6-1 returns an authentication NG (a13 in FIG. 6).

  The IP terminal (B) 2-2 confirms the data received from the IP device (B) 6-1 (a4 in FIG. 6). If the authentication is OK (a5 in FIG. 6), the area is determined based on the received information. Information is added and an IP terminal registration request is sent to the private branch exchange 3 (a6 in FIG. 6). If the IP terminal (B) 2-2 is an authentication NG (a5 in FIG. 6), the process returns to the above-described a2.

  When the private branch exchange 3 receives the IP terminal registration request (a21 in FIG. 6), it performs IP extension registration processing. The private branch exchange 3 calculates the extension number from the MAC address of the IP terminal (B) 2-2 if the extension number corresponding to the MAC address is registered, and if not registered, the IP terminal (B) 2-2. The extension number is determined based on the information sent from the terminal (a22 in FIG. 6), and the related memory (not shown) is set based on the IP address / area information (a23 in FIG. 6). This memory setting is converted from the extension number into accommodation position information used by the private branch exchange 3 and set in the area information management memory area 33a [see FIG. 5A] managed for each accommodation position information.

  In this embodiment, the area information can be newly managed in this association processing, and the IP address designation area information and the extension number are automatically associated with the registration request from the IP terminal (B) 2-2. The area where each IP terminal is installed can be managed. The area information management memory area 33a created at this time is shown in FIG.

  As shown in FIG. 5A, the private branch exchange 3 allocates accommodation location information (used as an index for all databases) used only within the private branch exchange 3 from the extension number of the IP terminal (B) 2-2. The area information management memory area can be managed for each storage position. In this embodiment, as shown in FIG. 5B, the area code of the center station (Tokyo) 1-1 is “0”, the area code of the remote office (Osaka) 1-2 is “1”, and the remote office ( (Fukuoka) The area code of 1-3 is “2”.

  Through the above processing, in this embodiment, the IP terminal (B) 2-2 moved to another area is also accommodated in the private branch exchange 3 using the same extension number as before the movement. The private branch exchange 3 notifies the result to the IP terminal (B) 2-2 (a24 and a7 in FIG. 6).

  FIG. 7 is a sequence chart showing an operation when accommodating an IP terminal according to an embodiment of the present invention in a private branch exchange. FIG. 7 shows the operation when the IP address of the IP terminal is automatically assigned. With reference to FIG. 1 to FIG. 5 and FIG. 7, the operation when the IP terminal according to the embodiment of the present invention is accommodated in the private branch exchange will be described.

  In the following description, it is assumed that the IP terminal (B) 2-2 has moved to the remote office 1-2. In this case, in FIG. 7, when the IP address to be used is not individually set for each device but assigned from the DHCP server in a lump, the IP terminal (B) 2-2 has the DHCP function 61 built-in. The operation of obtaining such information from the existing IP device (B) 6-1 is shown.

  After the movement, the IP terminal (B) 2-2 does not perform pre-setting after connecting to the network (b1 in FIG. 7). If the IP terminal (B) 2-2 is a PC installation type, the application is started (b2 in FIG. 7), and if it is a telephone type, an automatic reset / restart-up process is performed.

  When various IP addresses are not set, the protocol BOOTP (BOOTtrap Protocol) is automatically used, and the IP address / default gateway IP address, subnet mask, private branch exchange 3 used by the IP terminal (B) 2-2 IP address and area information are requested to the IP device (B) 6-1 (b3 in FIG. 7).

  The IP device (B) 6-1 assigns an IP address to the IP terminal (B) 2-2 (b11 in FIG. 7), and the encrypted terminal ID in the request signal from the IP terminal (B) 2-2 By checking this, the request source product is authenticated as an IP terminal accommodated in the private branch exchange 3 (b12 in FIG. 7), and if the authentication result is normal (OK) (b13 in FIG. 7), it is requested. Information is returned (b15 in FIG. 7). If the authentication result is abnormal (NG) (b13 in FIG. 7), the IP device (B) 6-1 returns an authentication NG (b14 in FIG. 7).

  The IP terminal (B) 2-2 confirms the data received from the IP device (B) 6-1 (b4 in FIG. 7). If the authentication is OK (b5 in FIG. 7), the area is based on the received information. Information is added and an IP terminal registration request is sent to the private branch exchange 3 (b6 in FIG. 7). If the IP terminal (B) 2-2 is authenticated NG (b5 in FIG. 7), the process returns to the above-described process b2.

  When the private branch exchange 3 receives the IP terminal registration request (b21 in FIG. 7), it performs IP extension registration processing. The private branch exchange 3 calculates the extension number from the MAC address of the IP terminal (B) 2-2 if the extension number corresponding to the MAC address is registered, and if not registered, the IP terminal (B) 2-2. The extension number is calculated based on the information sent from (b22 in FIG. 7), and the related memory (not shown) is set based on the IP address / area information (b23 in FIG. 7).

  Through the above processing, in this embodiment, the IP terminal (B) 2-2 moved to another area is also accommodated in the private branch exchange 3 using the same extension number as before the movement. The private branch exchange 3 notifies the result to the IP terminal (B) 2-2 (b24 and b7 in FIG. 7).

  FIG. 8 is a flowchart showing an operation when adding area information to billing information according to an embodiment of the present invention. With reference to these FIG. 1 and FIG. 8, the operation | movement at the time of giving area information to the billing information by one Example of this invention is demonstrated.

  When the other party number is dialed from the caller terminal (step S1 in FIG. 8), the private branch exchange 3 sends a busy sound to the caller terminal (step S2 in FIG. 8) if the other party is busy (step S2 in FIG. 8). S3).

  The private branch exchange 3 calls the partner (step S4 in FIG. 5) if the partner is empty (step S2 in FIG. 8). When the private branch exchange 3 responds (step S5 in FIG. 8), the private branch exchange 3 shifts to a call state, creates a billing information memory area, and adds area information to the billing information (step S6 in FIG. 8).

  When the other party recovers (call disconnection) (step S7 in FIG. 8), the private branch exchange 3 transitions to a free state, outputs the contents of the billing information memory area to the billing apparatus 4 (step S8 in FIG. 8), and ends the process. .

  FIG. 9 is a diagram showing the configuration of the billing information memory 43 according to one embodiment of the present invention. In FIG. 9, billing information memory 43 according to one embodiment of the present invention includes header information, calling party information (calling party number), call monitoring time, call end time, and called party information (called party number). And area information (originating side) and area information (destination side).

  Regarding the billing collection means when calling from the IP extension, the processing conventionally performed in the PBX (Private Branch eXchange) system, the extension number on the called side when dialing from the originating IP terminal, and the external TRK line This is different in that a process for assigning area information is added to the billing information memory area created when the line number is determined. The configuration of the billing information memory 43 to which the area information is assigned is as shown in FIG. 9 and includes the IP terminal (A) 2-1, IP terminal (B) 2-2, IP terminal (C) 2-3, IP Area information is set according to the usage status of the terminal (D) 2-4, the IP device (B) 6-1, and the IP device (A) 6-2. This information includes IP terminal (A) 2-1, IP terminal (B) 2-2, IP terminal (C) 2-3, IP terminal (D) 2-4, IP device (B) 6-1, IP device. (A) Only set for 6-2.

  An example of charge collection will be described using a connection between Tokyo and Osaka as a charge target and a connection between Tokyo and Fukuoka as a non charge target. If the originating side is the IP terminal (A) 2-1 in the extension interconnection between the IP terminal (A) 2-1 and the IP terminal (D) 2-4 before the movement, Is set to “0”, and “2” is set to the destination area information. The extension number of the IP terminal (A) 2-1 is set as the calling side extension number, and the extension number of the IP terminal (D) 2-4 is set as the called side extension number. Time information in the private branch exchange 3 is set for the call start time and the call end time.

  The information is sent to the billing device 4, and it is determined by the billing device 4 that the IP network 101 to be billed is not used, and is reported to the user. In the extension interconnection between the IP terminal (A) 2-1 and the IP terminal (D) 2-4 after the movement of the IP terminal (D) 2-4, the calling side is designated as the IP terminal (A) 2 When −1, the calling-side area information in the billing information is “0” and the called-side area information is “1”. In addition, the extension number is set the same as before the movement. When this information is sent to the billing device 4, the billing device 4 determines that the billing target IP network 101 is being used and reports it to the user.

  As described above, the IP terminal (A) 2-1, the IP terminal (B) 2-2, the IP terminal (C) 2-3, and the IP terminal (D) 2-4 move on the IP networks 101 and 102. It is possible to specify the area information while taking advantage of convenience, and at the same time, it is possible to specify detailed billing targets / non-targets of IP networks such as public IP network vendors and private IP leased lines. Can be used as information for determining the usage status of the IP network.

  In this way, in this embodiment, the area information is managed independently, so that the IP terminal (A) 2-1, the IP terminal (B) 2-2, the IP terminal (C) 2-3, the IP terminal (D ) In the movement of 2-4, the IP destination (A) 2-1 and IP can be managed in any IP network configuration and usage situation by managing the destination area without using the IP address or MAC address. Regardless of the connection pattern of the terminal (B) 2-2, the IP terminal (C) 2-3, and the IP terminal (D) 2-4, it is possible to collect the charging information of the IP network usage part.

It is a block diagram which shows the structure of the private branch exchange system by one Example of this invention. It is a block diagram which shows the structure of the private branch exchange of FIG. It is a block diagram which shows the structure of the charging device of FIG. It is a block diagram which shows the structure of the IP apparatus of FIG. (A) is a figure which shows the structure of the area information management memory area | region used in one Example of this invention, (b) is a figure which shows the network setting in one Example of this invention. It is a sequence chart which shows the operation | movement at the time of accommodating the IP terminal by one Example of this invention in a private branch exchange. It is a sequence chart which shows the operation | movement at the time of accommodating the IP terminal by one Example of this invention in a private branch exchange. It is a flowchart which shows the operation | movement at the time of providing area information to the billing information by one Example of this invention. It is a figure which shows the structure of the accounting information memory 43 by one Example of this invention.

Explanation of symbols

1-1 Center station 1-2, 1-3 Remote office
2-1 IP terminal (A)
2-2 IP terminal (B)
2-3 IP terminal (C)
2-4 IP terminal (D)
3 Private branch exchange
4 Billing device 5-1 to 5-3 Router
6-1 IP device (B)
6-2 IP device (A)
31, 41 TCP / IP I / F (interface)
32 Call control processing unit
33 database
33a Area information management memory area
42 Charge processing section
43 Accounting information memory
61 DHCP function
62 User authentication function
101 IP network to be charged
102 Non-chargeable IP network
103 Analog / ISDN

Claims (23)

A private branch exchange system in which a center station including a private branch exchange and a plurality of remote offices each capable of accommodating an IP (Internet Protocol) terminal are connected via at least an IP network,
Associating means for associating an IP address with designated area information and an extension number in response to a registration request from the IP terminal, and means for managing an area where the IP terminal exists based on the association, in the private branch exchange Have
A private branch exchange system comprising: a billing device that collects and outputs billing information according to a connection state of the IP network that varies according to a destination of the IP terminal based on the area information.   2. The private branch exchange system according to claim 1, wherein the private branch exchange performs centralized management using the accommodation location of the IP terminal in a call control process for performing at least extension interconnection and connection between the extension and a trunk. .   The association means creates a correspondence table between the accommodation location and the IP address of the IP terminal in order to accommodate and use the IP terminal, and associates the IP address with the extension number. The private branch exchange system according to claim 2, characterized in that it is a private branch exchange system.   The private branch exchange system according to any one of claims 1 to 3, wherein the extension number is determined by examining a MAC (Media Access Control) address of the IP terminal in advance.   The IP terminal transmits the registration request using at least user identification information, and determines that the user identification information is the extension number when an extension number is not assigned to a MAC (Media Access Control) address. The private branch exchange system according to any one of claims 1 to 3.   Each of the plurality of remote offices includes an authentication device for authenticating the IP terminal, and means for issuing unique user identification information including the area information to the IP terminal authenticated by the authentication device. The private branch exchange system according to any one of claims 1 to 5, wherein service contents in each of the plurality of remote offices are determined based on user identification information.   The authentication device is incorporated in any one of a device having a line connectable to an analog / ISDN (Integrated Services Digital Network) public network, an IP extension telephone, and an application installed in a personal computer. The private branch exchange system according to claim 6.   The private authentication apparatus according to claim 6 or 7, wherein the authentication apparatus adds the area information to an IP address used when connecting the IP terminal to the private branch exchange and notifies the private branch exchange. Exchange system.   The private branch exchange system according to any one of claims 1 to 8, wherein each of the plurality of remote offices includes a DHCP (Dynamic Host Configuration Protocol) function for assigning the IP address to the IP terminal.   A private branch exchange installed in the center station in a system in which a center station and a plurality of remote offices each capable of accommodating an IP (Internet Protocol) terminal are connected via at least an IP network, A private branch exchange comprising: association means for associating an IP address, designated area information, and an extension number with a registration request; and means for managing an area where the IP terminal exists based on the association .   11. The private branch exchange according to claim 10, wherein centralized management using the accommodation location of the IP terminal is performed at least in a call control process for connecting an extension interconnection and a connection between the extension and a trunk.   The association means creates a correspondence table between the accommodation location and the IP address of the IP terminal in order to accommodate and use the IP terminal, and associates the IP address with the extension number. The private branch exchange according to claim 11, characterized in that it is a private branch exchange.   The private branch exchange according to any one of claims 10 to 12, wherein the extension number is determined by checking a MAC (Media Access Control) address of the IP terminal in advance.   The IP terminal transmits the registration request using at least user identification information, and determines that the user identification information is the extension number when an extension number is not assigned to a MAC (Media Access Control) address. The private branch exchange according to any one of claims 10 to 12. A charging method for charging an IP terminal in a private branch exchange system in which a center station including a private branch exchange and a plurality of remote offices each capable of accommodating an IP (Internet Protocol) terminal are connected via at least an IP network. ,
A first step of associating an IP address, designated area information, and an extension number in response to a registration request from the IP terminal on the private branch exchange side, and managing an area where the IP terminal exists based on the association And a second step to
A charging method, wherein a charging device collects and outputs charging information according to a connection state of the IP network that changes according to a destination of the IP terminal based on the area information.   16. The accounting method according to claim 15, wherein the private branch exchange performs centralized management using the accommodation location of the IP terminal in call control processing for at least extension interconnection and connection between the extension and a trunk.   The first step creates a correspondence table between the accommodation location and the IP address of the IP terminal in order to accommodate and use the IP terminal, and associates the IP address with the extension number. The charging method according to claim 16.   The accounting method according to any one of claims 15 to 17, wherein the extension number is determined by checking a MAC (Media Access Control) address of the IP terminal in advance.   The IP terminal transmits the registration request using at least user identification information, and determines that the user identification information is the extension number when an extension number is not assigned to a MAC (Media Access Control) address. The charging method according to any one of claims 15 to 17.   An authentication device for authenticating the IP terminal and means for issuing unique user identification information including the area information to the IP terminal authenticated by the authentication device are provided in each of the plurality of remote offices and issued 20. The charging method according to claim 15, wherein service contents in each area of the plurality of remote offices are determined based on user identification information.   The authentication device is incorporated in any one of a device having a line connectable to an analog / ISDN (Integrated Services Digital Network) public network, an IP extension telephone, and an application installed in a personal computer. 21. The charging method according to claim 20.   The billing according to claim 20 or 21, wherein the authentication device adds the area information to an IP address used when connecting the IP terminal to the private branch exchange and notifies the private branch exchange. Method. 23. The charging method according to claim 15, further comprising a DHCP (Dynamic Host Configuration Protocol) function for assigning the IP address to the IP terminal in each of the plurality of remote offices.

Images