KR20030093540A - System and method for controlling a telephony-communication service based on the internet-network - Google Patents

Abstract

PURPOSE: A method for managing a telephone communication service based on an Internet network is provided to enable many distributed gatekeepers to supply module environments according to operated states of self user terminals, thereby enabling service providers to freely supply a series of telephone communication services to users. CONSTITUTION: A DNS server decides whether version management server IP address request events are generated(S101). If so, the DNS server transmits version management server IP address information to a user terminal(S103). A version management server decides whether firmware version check request events are generated(S104). If so, the version management server transmits firmware version up-upgrade data to the terminal(S106,S107). The DNS server decides whether common gatekeeper IP address request events are generated(S108). If so, the DNS server transmits common gatekeeper IP address information to the terminal(S110). A common gatekeeper decides whether registration request events are generated(S111). If so, the gatekeeper authenticates whether the terminal is right(S113). If so, the gatekeeper transmits distributed gatekeeper information to the terminal(S114). An authenticating server decides whether user authentication and update request events are generated(S115). If so, the server updates information on the terminal(S117), and transmits updated result data to the gatekeeper(S118).

Description

System and method for controlling a telephony-communication service based on the internet-network}

The present invention relates to a telecommunications service management system based on the Internet network, and more particularly, to a series of central management units according to an operation of a user terminal managed by a plurality of distributed gatekeepers connected to an online network. For example, an authentication server, a common gatekeeper, a version control server, etc. installed in the module environment can be selectively provided and commonly used, thereby allowing a large number of service providers to provide only a distributed gatekeeper without any other equipment. The present invention relates to a telecommunication service management system based on an internet network that can induce a series of telecommunication services freely to general users. Furthermore, the present invention relates to a telecommunication service management method based on the Internet network using such a telecommunication service management system.

Recently, with the rapid development of Internet-related technology, the telecommunication service based on the Internet network is also rapidly developing.

For example, Korean Patent Publication No. 2000-30822 "Calling System Using the Internet", Korean Patent Publication No. 2000-50103 "Call Rate Discount Service Method", Korean Patent Publication No. 2000-54575 "Internet Department" Message insertion method using advertisement by telephone ", Korean Patent Laid-Open Publication No. 2000-55248" Method and apparatus for providing Internet service using telephone network ", Korean Patent Publication No. 2000-58355" Telephone service with advertisement function on the Internet Provision system and method thereof, and Korean Patent Laid-Open Publication No. 2000-58522, "Calling and encounter service combining the Internet and a mobile phone", etc., discloses in detail an example of a telecommunication service using an Internet network according to the prior art. have.

In general, under the conventional Internet telephony service system described above, in order for any service provider to normally perform a series of telephony services, various equipment such as a large gatekeeper, an authentication server, and the like must be provided by itself.

However, since most of these equipments are very expensive, in the end, any operator who wants to implement the Internet telephony service under the conventional system will have to bear the problem of enormous capital investment for equipment installation.

Moreover, in order for these equipments to continue their normal functions, the maintenance, maintenance, and up-grade process of the equipments must be continuously performed by experts. In addition to the initial installation costs of the equipment mentioned above, any operator wishing to implement them is forced to bear the inconvenience of additional enormous self-maintenance costs to manage them.

Under these problems, the cost burden of the operators is gradually increased, and if this causes many operators to abandon the telephony service business itself, the impact will inevitably affect the Internet telephony market. Unless a separate countermeasure for operators is devised, the conventional Internet telephony market is inevitably shrinking.

Accordingly, an object of the present invention is to provide a user terminal that manages, for example, an authentication server, a common gatekeeper, a version control server, etc., in which a plurality of operator gatekeepers connected to an online network are installed in a series of central management units. Depending on the operational situation, a modular environment that can be selectively and commonly used can be constructed, and based on this, many Internet telephony service providers can freely implement a series of telephony services without building their own expensive equipment. It is.

Another object of the present invention is to induce a plurality of Internet telephony service providers to freely implement a series of telephony services without building their own equipment, thereby minimizing the cost waste of each service provider, It is to prevent the contraction of the Internet telephony market due to business abandonment.

Still other objects of the present invention will become more apparent from the following detailed description and the accompanying drawings.

1 is a block diagram conceptually illustrating a telecommunication service management system based on the Internet network according to the present invention;

2 and 3 are flowcharts sequentially showing a method for managing a telecommunication service based on an internet network according to the present invention.

In order to achieve the above object, in the present invention, a plurality of operator-side units having a series of data areas individually, the operator-side units and the Internet network are selectively signal-connected, A telecommunication service management system based on an internet network comprising a central management unit for common management of a series of events occurring in a side unit frame is disclosed.

At this time, each operator-side unit registers and manages information on any user-side terminals registered in the operator-side units, in a state distributed and installed in each data area, and is randomly selected from a specific user-side terminal among the user-side terminals. When a series of telephone call initiation events occur for a called party's terminal, the call is authenticated to a specific user terminal through a signal exchange process with the central management unit. A plurality of distributed gatekeepers are arranged to transmit information about the terminal to a specific user side terminal, thereby inducing a call path to be connected between the specific user side terminal and the called party terminal.

In addition, the central management unit is signal-connected selectively with user terminals and distributed gatekeepers, and among the aforementioned user terminals, the self-registering user terminal is targeted from a specific distributed gatekeeper to which a specific user terminal is registered. When a user authentication request or user information update request event occurs, the user authentication result data and user information update result data are generated through a series of authentication / update procedures, and the user authentication result data and user information update result data that have been created are completed. Transmits to a specific distributed gatekeeper, and when a series of call availability check request events occur from the specific distributed gatekeeper by starting a call of a specific user side terminal, checks whether or not the user side terminal is available for call, Generate a series of call result data And, an authentication server is arranged to generate a completed call availability passes the result data to the front of a particular distributed gatekeeper.

In addition, the central management unit is selectively signal-connected with the user terminals and the authentication server in a state of collectively storing and storing information on the previous distributed gatekeepers. In this state, among the previous user terminals, a specific user terminal When a series of registration request events are generated from the distributed gatekeepers, among the distributed gatekeepers, a specific distributed gatekeeper to which a specific user side terminal can be registered is designated, and the corresponding assignment result data is transmitted to the specific user side terminal. When there is a request for information transfer from the authentication server to the distributed gatekeepers, a common gatekeeper for extracting and transferring the information is arranged.

In addition, when the central management unit selectively connects to the user terminals, when a series of self firmware version check request events occur from a specific user terminal among the user terminals, the central management unit displays the firmware version of the user terminal. After checking, based on the check result, a version management server for selectively generating a series of firmware version up-upgrade data and transmitting the generated firmware version up-upgrade data to the user terminal is arranged.

Hereinafter, a system and method for managing a telecommunication service based on an internet network according to the present invention will be described in detail with reference to the accompanying drawings.

As shown in FIG. 1, the telecommunication service management system according to the present invention is largely established based on the Internet network, and includes a plurality of operator-side units 200 to 300 to 400 each having a series of data areas. ), And these unit-side units (200 ‥ 300 ‥ 400 ‥) and the internet network in front of the network, are selectively connected to each other, It consists of the combination of the central management unit 100 which manages common events. In this case, as shown in the figure, for example, distributed gatekeepers 201 ... 401 ..., web servers 202 ... are disposed in each operator-side units 200 ... 300 ... 400 ....

Under such a system of the present invention, operators who wish to implement a series of Internet telephony service businesses establish their own operator units 200 to 300 and 400 on the web, and then the operator side units 200 to 300. In addition, a distributed gatekeeper 201 401 401 provided by the central management unit 100 is installed in the ... 400 ..., and an arbitrary unique number and an IP address (Internet Protocol address) are given to arbitrary users. By selling the user terminal 1, 2, 3 ..., the base environment in which the present invention can proceed smoothly is prepared.

In this case, the general users who have purchased the user terminal 1, 2, 3 ... from the service providers are provided with the web server (200 ... 300 ... 400 ...) of each operator side unit 200 ... 300 ... 400 ... via the Internet network before the full implementation of the present invention. By connecting to 202 ..., the terminal information desired by the user can be set in advance, for example, "telephone number, usage time, payment method ...".

At this time, the distributed gatekeepers 201 401 401 distributed and installed in each operator side units 200 ‥ 300 ‥ 400 ‥ are arbitrary user terminals registered in the operator side units 200 ‥ 300 ‥ 400 ‥ While registering and managing information relating to (1, 2, 3 ...), among the user terminals 1, 2, 3 ..., for example, any called party side terminal from the user side terminal 1, for example, the user side terminal ( 2) When a series of telephone call initiation events for the user terminal 3 occurs, it is possible to authenticate whether or not the user terminal 1 is available through a signal exchange process with the central management unit 100, In accordance with the availability of the call, information about the user terminal 2 and the user terminal 3 is transmitted to the user terminal 1 so that a series of call paths are established between the user terminal 1 and the user terminal 2,3. It plays a role in inducing selective connection.

On the other hand, as shown in the figure, the central management unit 100 mentioned above includes an authentication server 103, a common gatekeeper 104, a DNS (Domain Name System) server 105, a version control server 107, etc. Is placed.

At this time, the authentication server 103 is selectively connected to the user terminal (1, 2, 3 ...) and the distributed gatekeepers (201 ... 401 ...), in this state, the user terminal (1, 2, 3), a user authentication request and a user information update request event for the user terminal 1 are generated from a distributed gatekeeper 201 in which a specific user terminal, for example, the user terminal 1 is registered. In this case, the user authentication result data and the user information update result data are generated through a series of authentication / update procedures, and the user authentication result data and the user information update result data, which are generated, are transmitted to the distributed gatekeeper 201. Perform.

In addition, when a series of call availability check request events are generated from the distributed gatekeeper 201 by the start of the call of the user terminal 1, the authentication server 103 enables call of the corresponding user terminal 1. Checks to generate a series of call availability result data, and transmits the completed call availability result data to the previous distributed gatekeeper 201.

Together with the authentication server 103, the common gatekeeper 104 stores and stores the information on the above-described distributed gatekeepers 201 to 401 ..., and the user terminals 1, 2, 3 ... And an authentication server 103, and in this state, a series of registration request events from a specific user side terminal, for example, the user side terminal 1, among the previous user side terminals 1, 2, 3. Is generated, a specific distributed gatekeeper, for example, a distributed gatekeeper 201, to which the user-side terminal 1 can be registered, is designated among the distributed gatekeepers 201 to 401 ..., and the corresponding designated result data is assigned. It plays a role of transmitting to the user terminal 1, and extracts and delivers the information when there is a request for information transmission from the authentication server 103 to the distributed gatekeepers 201 401 401. Do this.

In addition, the above-mentioned version control server 107 is selectively connected to the user-side terminals (1, 2, 3 ...), of the user-side terminals (1, 2, 3 ...), a specific user side terminal, for example, When a series of self firmware version check request events occur from the user terminal 1, after checking the firmware version of the user terminal 1, based on the check result, a series of firmware version up-upgrade data is selectively selected. It generates and transmits the firmware version up-upgrade data, which has been generated, to the user terminal 1. By the operation of this version control server 107, the user can easily obtain the advantage that the firmware installed on his terminal 1 is always automatically upgraded to the latest state.

In addition, the above-described DNS server 105, for example, in the state of storing the IP address of the version control server 107, the IP address of the common gatekeeper 104, etc., the user terminal (1, 2, 3 ...) And an optional signal connection between the user side terminals 1, 2, 3, from the specific user side terminal, for example, the user side terminal 1, " IP address request event of the version management server 107 " When the IP address request event of "104" occurs, it extracts the corresponding IP address information from its database and transmits it to the user terminal 1.

On the other hand, as shown in the figure, the central management unit 100, in addition to the above-described authentication server 103, common gatekeeper 104, DNS server 105, version management server 107, the interface module (101, 102) , Billing server 106 and the like are further arranged.

In this case, the interface modules 101 and 102 may include the user terminal 1, 2, 3 ..., the distributed gatekeeper 201 ... 401 ... of the operator-side units 200 ... 300 ... 400 ... and the central management unit 100. User side terminals 1, 2, 3 ..., distributed gatekeepers 201 ... 401 with the authentication server 103, the common gatekeeper 104, the DNS server 105, the version control server 107, etc. Process the event data transmitted from ..., etc. in a format suitable for the central management unit 100, and transmit the event data to the authentication server 103, the common gatekeeper 104, the DNS server 105, the version control server 107, and the like. In addition to transmitting the information, the information transmitted from the authentication server 103, the common gatekeeper 104, the DNS server 105, the version control server 107, and the like is transmitted to the operator-side unit (200 ‥ 300 ‥ 400 ‥). To the user side terminal (1, 2, 3 ...) distributed gatekeeper (201 ... 401 ...), etc. Perform.

In addition, the billing server 106, for example, in the form of a series of signal connection relationships with the authentication server 103, billing information of each user who purchased the user terminal 1, 2, 3 ..., for example, " In addition to storing and managing call time history, phone bill payment history, remaining amount information ..., etc., and extracting billing information for each user from the authentication server 103, the billing information is extracted. · Plays a role of delivery.

Hereinafter, a method of managing a telecommunication service unique to the present invention using the telecommunication service management system having the above-described configuration will be described in detail.

As shown in Figures 2 and 3, the telecommunication service management method of the present invention largely consists of a combination of the user terminal registration guide process (step S100) and the user terminal call progress guide process (step S200).

At this time, the user terminal registration guide process (step S100) is a general user who purchased the user terminal (1, 2, 3 ...) from the Internet telecommunications service providers, the corresponding user (1, 2, 3 ...) When registering to the operating distributed gatekeeper (201 401 401), it refers to a procedure for guiding this, the user terminal call progress guide process (dungeon S200) through the previous user terminal registration guide process, the own terminal ( This refers to a procedure for guiding users who have already registered 1,2,3 ... to a distributed gatekeeper (201 ... 401 ...) operated by a specific operator to make a phone call with another user.

In this case, the previous user terminal registration guide process (step S100) is repeatedly performed at an initial time point when the user turns on the terminal which has been turned off every time.

Of course, under the system of the present invention, if the user does not go through the previous user terminal registration guide procedure (step S100) in advance, the terminal (1, 2, 3 ...) of the user as "normal subscriber terminal", It cannot be registered in the distributed gatekeeper (201 401 401) of the operator side unit (200 ‥ 300 ‥ 400 ‥). In this case, even if the user purchases the user side terminals 1, 2, 3 ... You will not be able to proceed.

Therefore, every user who wishes to enjoy the present invention, every time when the terminal is turned off, by step S100 every time, the self-owned terminal (1, 2, 3 ...) is the operator-side unit (200 ... 300) It is possible to stably register the distributed gatekeeper 201 .401.

For convenience, in the following description, it is assumed that the user terminal registration guide process (step S100) and the user terminal call progress guide process (step S200) are limited to the user side terminal 1 and the gatekeeper 201.

First, the user terminal registration guide process (step S100) according to the present invention will be described in detail.

As shown in FIG. 2, first, the DNS server 105 continuously checks the interface module 101 to determine whether a series of version control server IP address request events have occurred from the user terminal 1. (Step S101).

At this time, if it is determined that no separate version control server IP address request event has occurred from the user terminal 1, the DNS server 105 proceeds to step S102 to maintain a series of standby states.

However, if it is determined that the user has turned off the terminal and the series of version control server IP address request events have occurred from the user terminal 1, the DNS server 105 immediately searches its own database area. Search to extract previously stored version control server IP address information, and transmit the extracted version control server IP address information to the user terminal 1 via the interface module 101. (Step S103).

When this procedure is completed, the user terminal 1 can easily grasp the IP address of the version control server 107 to be connected to.

In this state, the version control server 107 continuously checks the interface module 101, so that a series of firmware version check request events including, for example, "self-installed firmware version information" has occurred from the user terminal 1. It is determined whether or not (step S104).

At this time, if it is determined that a separate firmware version check request event has not occurred from the user terminal 1, the version control server 107 proceeds to step S105 to maintain a series of standby states.

However, if it is determined that a series of firmware version check request events have occurred from the user terminal 1, the version management server 107 checks the firmware version of the user terminal 1, and then based on the check result, A process of selectively generating the firmware version up-upgrade data and transmitting the generated firmware version up-upgrade data to the user terminal 1 is performed (steps S106 and S107).

When this procedure is completed, the user can easily obtain the advantage that the firmware installed in the terminal is automatically upgraded to the latest state as soon as the terminal 1 is turned on.

On the other hand, at the end of the above-described automatic upgrade process, the DNS server 105 continuously checks the interface module 101, so that a series of common gatekeeper IP address request events have occurred from the user terminal 1. It is determined whether or not (step S108).

At this time, if it is determined that no separate common gatekeeper IP address request event has occurred from the user terminal 1, the DNS server 105 advances the flow to step S109 to maintain a series of standby states.

However, if the user proceeds with a series of terminal operations and determines that a series of common gatekeeper IP address request events have occurred from the user terminal 1, the DNS server 105 immediately searches its database area ( Search to extract the pre-stored common gatekeeper IP address information, and transmit the extracted common gatekeeper IP address information to the user terminal 1 via the interface module 101. (Step S110).

When this procedure is completed, the user terminal 1 can easily determine the IP address of the common gatekeeper 104 to which it is to be connected.

In this state, the common gatekeeper 104 continuously checks the interface module 101, whereby a series of registration request events including, for example, "terminal information, user information, operator information", etc., are received from the user terminal 1. It is judged whether or not it has occurred (step S111). At this time, the terminal information, the user information, the operator information, and the like are previously recorded in the terminal 1 from the point of sale of the terminal 1 so that the user terminal 1 can easily follow a series of registration procedures.

At this time, if it is determined that no separate registration request event has occurred from the user terminal 1, the common gatekeeper 104 proceeds to step S112 to maintain a series of standby states.

However, if it is determined that a series of registration request events have occurred from the user terminal 1, the common gatekeeper 104 immediately proceeds with a series of signal exchange processes with the authentication server 103, whereby the user terminal 1 It is authenticated whether or not the validity of (step S113).

In this case, the common gatekeeper 104 of the present invention is characterized by transmitting the media access control address (MAC address) of the user terminal 1 to the authentication server 103, thereby providing the authentication server 103. Provides a base environment that can stably authenticate the basic requirements of the user-side terminal (1).

In this situation, the authentication server 103 is "operator information contracted with the central management unit 100 side ", " terminal information and user information previously reported from each of the distributed gatekeepers 201 40401 " The terminal information transmitted from the terminal 1, for example, "media access control address information of the user terminal," and the user information, business information, etc. are compared, and the validity of the corresponding user terminal 1 is authenticated, and the authentication result thereof. Is quickly passed to the common gatekeeper 104.

Through this procedure, if the validity of the user terminal 1 is authenticated, the common gatekeeper 104 immediately sells the user terminal 1 of the distributed gatekeeper information previously stored in its data area. The information of the distributed gatekeeper 201 operated by the operator, for example, "IP address information of the distributed gatekeeper 201" is extracted, and the distributed gatekeeper 201 information, which has been extracted, is transferred through the interface module 101. In step S114, the process of transmitting to the user terminal 1 is performed.

When this process is completed, the user terminal 1 can easily determine the IP address of the distributed gatekeeper 201 to which the user side 1 is to be connected. As soon as this determination is completed, the user terminal 1 can quickly access the distributed gatekeeper 201. As a result, the distributed gatekeeper 201 can be notified that "they have already undergone a series of registration procedures via the common gatekeeper 104".

In this state, the authentication server 103 continuously checks the interface module 101, whereby a series of user authentication requests and users targeting the "user-side terminal 1 registered to the user" from the distributed gatekeeper 201. It is determined whether or not an information update request event has occurred (step S115).

At this time, if it is determined that a separate user authentication request and user information update request event have not occurred from the distributed gatekeeper 201, the authentication server 103 immediately proceeds to the flow to step S116, and a series of standby states are performed. Keep it.

However, the user terminal 1 connects to the distributed gatekeeper 201 and notifies that "they have already undergone a series of registration procedures through the common gatekeeper 104" and based on this, the distributed gate If it is determined that a series of user authentication request and user information update request events have occurred from the keeper 201, the authentication server 103 immediately utilizes the billing server 106 to, for example, purchase the user terminal 1. Check the call charge history of the user, thereby authenticating the user's validity of the call and updating the information of the user terminal 1 stored in his database to, for example, "registration completed" (step) S117).

When the user authentication / user information update process is completed, the authentication server 103 immediately generates a series of user authentication result data and user information update result data, and then completes the user authentication result data and user information update result. The data is transmitted to the distributed gatekeeper 201 via the interface module 101 (step S118).

When the user authentication result data and the user information update result data are transmitted and completed from the authentication server 103 through the above-described procedure, the distributed gatekeeper 201 immediately sends the user side terminal 1 to " all registration procedures. And a call can be initiated. ”In the end, the user can utilize the user terminal 1 to normally proceed with a series of telephone calls he / she wants.

Next, the user terminal call progress guide process (step S200) according to the present invention will be described in detail.

As shown in FIG. 3, first, when a user initiates a telephone call through a series of terminal manipulation processes, the user side terminal 1 may, for example, own "terminal information / calling number information / called number information". It transfers to the distributed gatekeeper 201 which it belongs, and requests establishment of a series of calls (step S1, S2).

In this state, the distributed gatekeeper 201 checks the preceding terminal information / calling number information and the like, for example, confirms basic requirements such as "registration of user terminal" or the like, and then receives an incoming call from the user terminal 1. The number information is checked, and it is determined whether or not the call destination called number transmitted from the user terminal is a called number belonging to a distributed gatekeeper other than the self belonging (steps S201 and S202).

At this time, the target call destination number does not exist in its own database, and it turns out that the target call destination number transmitted from the user terminal 1 is a destination number belonging to a distributed gatekeeper other than its own destination number. If so, the distributed gatekeeper 201 immediately transmits the calling terminal information, the calling number information, the called number information, and the like transmitted from the user terminal 1 to the authentication server 103, and the call of the corresponding user terminal 1 is transmitted. A check is requested (step S203).

In this case, the authentication server 103 utilizes the billing server 106, for example, proceeds with the process of extracting the available time information, the remaining money information, etc. of the user terminal 1, the common gatekeeper ( 104, the process of extracting the called party information related to the called number, for example, "IP address information of the distributed gatekeeper 401 managing the called party terminal 3 having the called number". When the information extraction process is completed, the authentication server 103 performs a series of call availability result data including, for example, call availability time information / remaining amount information / IP address information of the called party's distributed gatekeeper 401, and the like. It generates and transmits the call availability result data is completed to the distributed gate keeper 201.

In this state, the distributed gatekeeper 201 checks the data transmission status of the authentication server 103, whereby, for example, " callable time information / remaining amount information / recipient side information " It is determined whether or not the call availability check result information has been transmitted (step S204).

At this time, if it is determined from the authentication server 103 that the separate call availability check result information has not yet been transmitted, the distributed gatekeeper 201 immediately proceeds to the flow at step S205 to maintain a series of standby states. do.

However, if it is determined that the above-mentioned call availability check result information has been transmitted from the authentication server 103, the distributed gatekeeper 201 determines whether the user side terminal 1 is available for call based on this (step S206). .

At this time, for example, if there is a problem that "the user is not available for the call time" or "the amount of the remaining money of the user", and the user is determined to be unable to make a normal telephone call, distributed gatekeeper 201 ) Immediately generates a series of error messages, such as "Your money is not enough and the call is not possible.", And transmits the generated error message to the user terminal 1 so that the user can make a corresponding error. It is guided to promptly take appropriate measures appropriate to the situation (step S207).

However, if there is no problem in the call availability check result information transmitted from the authentication server 103, and it is determined that the user can make a normal telephone call, the distributed gatekeeper 201 immediately determines the called party. On the basis of the IP address information of the distributed gatekeeper 401, a process of calling the distributed gatekeeper 401 which manages the called party side terminal 3 is performed (step S208).

In this state, the distributed gatekeeper 201 determines whether or not a call response signal corresponding to the previous call is returned from the distributed gatekeeper 401 (step S209).

At this time, if it is determined from the distributed gatekeeper 401 that no separate call response signal has been returned yet, the distributed gatekeeper 201 immediately proceeds to the flow in step S210 to maintain a series of standby states.

However, if it is determined that a series of call response signals have been returned from the distributed gatekeeper 401, the distributed gatekeeper 201 immediately connects the call path between the user terminal 1 and the called party terminal 3 by the connection. , So that the user can easily proceed with a series of telephone call process with the desired counterpart (step S211).

Of course, if there is a separate problem for the user managing the called party's terminal 3, for example, "lack of talkable time," "lack of remaining money available," such a call path cannot be connected normally. In this case, the distributed gatekeeper 201 generates a series of error messages, such as, for example, "the other party's call amount is insufficient and the call is not possible." ) To induce the user to quickly take the appropriate action for the error.

Under the conventional system, since any service provider has no choice but to provide various equipments such as a large gatekeeper, an authentication server, etc., in order to normally execute a series of telephony services, the service provider bears enormous cost. I had to hug you.

However, in the case of the present invention, as described above, according to the operation of the user terminal (1, 2, 3 ...) managed by the plurality of distributed gatekeepers (201 ... 401 ...) connected to the online network, Since a module environment is provided which can selectively and commonly use, for example, the authentication server 103, the common gatekeeper 104, the version control server 107, etc. installed in the series of central management units 100, Under the system, many service providers do not have expensive equipments themselves, and even if only a distributed gatekeeper (201 401 401) is provided, a series of telephony services can be freely provided to general users. In the case where the implementation of the present invention creates an environment in which a plurality of Internet telephony service providers can freely execute a series of telephony services without building their own equipment, The cost burden of the service provider can be minimized. As a result, the contraction of the Internet telephony market due to the abandonment of the service provider can be prevented.

On the other hand, in the above-described step S202, if the preceding call destination number exists in its database, and it is determined that "the call destination destination number transmitted from the user side terminal 1 is its own destination number," the distributed gatekeeper ( 201 immediately transmits the calling terminal information / calling number information transmitted from the user terminal 1 to the authentication server 103, and requests a check of whether the corresponding user terminal 1 can be called (step S212). ).

In this case, the authentication server 103 utilizes the billing server 106 to perform, for example, a process of extracting callable time information, remaining money information, etc. of the user terminal 1. When the information extraction process is completed, the authentication server 103 generates a series of call availability result data including, for example, callable time information / remaining amount information, and the like, and precedes the call completion result data that has been generated. The process of transferring the distributed gatekeeper 201 is performed.

In this state, the distributed gatekeeper 201 checks the data transmission status of the authentication server 103, thereby checking whether or not the call can be recorded from the authentication server 13, for example, " callable time information / remaining amount information " It is determined whether or not the result information has been transmitted (step S213).

At this time, if it is determined that the separate call availability check result information has not yet been transmitted from the authentication server 103, the distributed gatekeeper 201 immediately proceeds to the flow at step S214 to maintain a series of standby states. do.

However, if it is determined that the above-mentioned call availability check result information has been transmitted from the authentication server 103, the distributed gatekeeper 201 determines whether the user side terminal 1 can talk based on this (step S215). .

At this time, for example, if there is a problem that "the user is not available for the call time" or "the amount of the remaining money of the user", and the user is determined to be unable to make a normal telephone call, distributed gatekeeper 201 ) Immediately generates a series of error messages, such as "Your money is not enough and the call is not possible.", And transmits the generated error message to the user terminal 1 so that the user can make a corresponding error. It is guided to promptly take appropriate measures appropriate to the situation (step S216).

However, if there is no problem in the call availability check result information transmitted from the authentication server 103, and it is determined that the user can make a normal phone call, the distributed gatekeeper 201 immediately and automatically belongs to itself. The process of calling the called party's terminal 2 is carried out (step S217).

In this state, the distributed gatekeeper 201 determines whether or not a call response signal corresponding to the preceding call is returned from the called party's terminal 2 (step S218).

At this time, if it is determined from the called party's terminal 2 that no separate call response signal has been returned yet, the distributed gatekeeper 201 immediately proceeds to the flow at step S219 to maintain a series of standby states.

However, if it is determined that a series of call response signals have been returned from the called party's terminal 2, the distributed gatekeeper 201 immediately proceeds to the aforementioned step S211, whereby the user terminal 1 and the called party's side. Connecting the call path between the terminal (2), thereby inducing the user to easily proceed with a series of telephone call process with the desired counterpart.

Of course, even in this case, when the user who manages the called party's terminal 2 has another problem, for example, "a problem of lack of available talk time", "a problem of lack of available money remaining", etc. In this case, the distributed gatekeeper 201 generates a series of error messages such as, "The other party's call amount is insufficient, so the call is not possible." By transmitting to the user side terminal 1, the user can be promptly taken to take appropriate measures appropriate for the error situation.

As described above, in the present invention, a plurality of distributed gatekeepers connected to the online network are installed in a series of central management units, for example, an authentication server, a common gatekeeper, and version management, depending on the operation status of a user terminal managed by the user. Provides a modular environment that can optionally use a common server and the like, through which a number of service providers have a series of telecommunications services, even with a distributed gatekeeper, without the need for other equipment itself Encourage them to do it freely.

By the implementation of the present invention, the cost burden of each service provider can be minimized when a "environment in which a plurality of Internet telephony service providers can freely execute a series of telephony services without building their own equipment" is created. As a result, the contraction of the Internet telephony market due to abandonment of service providers can be prevented.

While specific embodiments of the invention have been described and illustrated above, it will be apparent that the invention may be embodied in various modifications by those skilled in the art.

Such modified embodiments should not be understood individually from the technical spirit or point of view of the present invention and such modified embodiments should fall within the scope of the appended claims of the present invention.

Claims (9)

A plurality of operator-side units having a series of data areas individually; It is made of a central management unit that is selectively connected to the signal through the operator unit and the Internet network, a common management unit for the series of events occurring in the operator unit frame, The respective operator side units register and manage information on any user side terminals registered in the operator side units while being distributed and installed in the respective data areas, and among the user side terminals, specific user side terminals. When a series of telephone call initiation events occur for any called party's terminal from the terminal, through the signal exchange process with the central management unit, it is possible to authenticate whether or not the specific user's terminal is available for call, Accordingly, a plurality of distributed gatekeepers are arranged to transmit information about the called party's terminal to the specific user's terminal to induce a call path between the specific user's terminal and the called party's terminal. The central management unit is selectively signal-connected with the user-side terminals and distributed gatekeepers, and among the user-side terminals, a user authentication request for a self-registered user-side terminal from a specific distributed gatekeeper to which a specific user-side terminal is registered; When the user information update request event occurs, the user authentication result data and the user information update result data are generated through a series of authentication / update procedures, and the specific user authentication result data and the user information update result data are distributed. In addition to transmitting to the gatekeeper, when a series of call availability check request events occur from the specific distributed gatekeeper by initiating a call of the specific user side terminal, the user side terminal checks whether or not the user side can be called and a series of Generate call availability result data And an authentication server for generating a complete, transfer the call available if the result data in the particular dispersion and the gatekeeper; In a state where the information on the distributed gatekeepers is collectively stored, the signal is selectively connected to the user terminals and the authentication server, and when a series of registration request events occur from a specific user terminal among the user terminals, Among the distributed gatekeepers, a specific distributed gatekeeper may be designated to which the specific user-side terminal can be registered, and the corresponding designation result data is transmitted to the specific user-side terminal, and the authentication server may be configured for the distributed gatekeepers. A common gatekeeper for extracting and delivering the information when there is a request for information transfer; After the signal is selectively connected to the user terminals, and when a series of self firmware version check request events occur from a specific user terminal among the user terminals, after checking the firmware version of the specific user terminal, Based on the check result, a version management server for selectively generating a series of firmware version up-upgrade data and transmitting the generated firmware version up-upgrade data to the specific user side terminal is arranged. Telephony service management system based on. The apparatus of claim 1, wherein the central management unit is selectively connected to the user terminal in a state of storing the IP addresses of the version control server and the common gatekeeper, and among the user terminals, from the specific user terminals. When an IP address request event of a version control server and a common gatekeeper occurs, a DNS (Domain Name System) server for extracting the IP address information and transmitting it to the specific user side terminal is further provided. Based telephony service management system. A plurality of operator side units each having a series of distributed gatekeepers for registering and managing a plurality of user side terminals, and selectively connected via the operator side unit and the internet network, and the operator side unit It operates under the system of telecommunication service management system, which consists of a central management unit equipped with an authentication server, a common gatekeeper, a version control server and a DNS server, which connect and manage a series of events occurring in the framework. Determining, by the common gatekeeper, whether a series of registration request events have occurred from a specific user-side terminal among the user-side terminals; When the registration request event occurs from the specific user side terminal, the common gate keeper designates a specific distributed gate keeper to which the specific user side terminal can be registered among distributed gate keepers to which the common gate keeper belongs, and designates the specified result data. Transmitting to a specific user side terminal; Determining, by the authentication server, whether a user authentication request or a user information update request event for a self-registered user side terminal has occurred from a specific distributed gatekeeper among the distributed gatekeepers; When the user authentication request and user information update request event are generated from the specific distributed gatekeeper, the user authentication result data and the user information update result data are generated through a series of authentication / update procedures, and the user authentication result data is completed. And transmitting user data update result data to the specific distributed gatekeeper. The method of claim 3, wherein when the registration request event occurs from the specific user side terminal, the common gatekeeper transmits a media access control address (MAC address) of the specific user side terminal to the authentication server. And a step of authenticating the basic requirements of the specific user-side terminal is further performed. 4. The method of claim 3, further comprising: determining, by the DNS server, whether a series of common gatekeeper IP address request events have occurred from the user-side terminal; When the common gatekeeper IP address request event occurs from the user terminal, the DNS server extracts the previously stored common gatekeeper IP address information and then transfers the extracted common gatekeeper IP address information to the user terminal. Telephony service management method based on the Internet, characterized in that the further step of transmitting. 4. The method of claim 3, further comprising: determining, by the version control server, whether a series of self firmware version check request events has occurred from a specific user terminal among the user terminals; When the self firmware version check request event occurs from the specific user terminal, after checking the firmware version of the user terminal, a series of firmware version up-grade data is selectively generated based on the check result. And transmitting the completed firmware version up-upgrade data to the specific user-side terminal. 7. The method of claim 6, further comprising: determining, by the DNS server, whether a series of version control server IP address request events have occurred from the user terminal; When the version control server IP address request event occurs from the user terminal, the DNS server extracts the previously stored version control server IP address information, and then extracts the extracted version control server IP address information to the user terminal. Telephony service management method based on the Internet, characterized in that the further step of transmitting. A plurality of operator side units each having a series of distributed gatekeepers for registering and managing a plurality of user side terminals, and selectively connected via the operator side unit and the internet network, and the operator side unit Under the system of telecommunication service management system consisting of a central management unit having an authentication server, a common gatekeeper and a DNS server, which link and manage a series of events occurring in the framework, At the start of the call of the user terminal, a series of user terminal information / calling number information / called number information transmitted from the user terminal is checked to determine whether the called number is a called number belonging to another distributed gatekeeper. Making a step; If the called number is a called number belonging to another distributed gatekeeper, transmitting the user side terminal information / calling number information / called number information to the authentication server and requesting a check of whether the corresponding user side terminal can be called; ; Determining whether or not a call availability check result information in which a series of talk time information / remaining amount information / recipient side information is recorded is transmitted from the authentication server; When the call availability check result information is transmitted from the authentication server, determining whether the user terminal can make a call based on the call availability check result information; If the call of the user terminal is possible, calling the called party distributed gatekeeper managing the called number based on the called party side information, and connecting a call path between the user terminal and the called party terminal; Telephony service management method based on the Internet network characterized in that. The method of claim 8, further comprising: transmitting the user side terminal information / calling number information to the authentication server when the called number is a self belonging called number, and requesting a check of a call possibility of the corresponding user side terminal; Determining whether or not a call availability check result information in which a series of talk time information / remaining amount information is recorded is transmitted from the authentication server; When the call availability check result information is transmitted from the authentication server, determining whether the user terminal can make a call based on the call availability check result information; If the user terminal is possible to make a call, the step of connecting the call path between the user terminal and the called party terminal by calling the called party's terminal belonging to the party having the called number is further based on the Internet network. Telephony service management method.