KR20130067426A - Apparatus and method for supporting clauding telephony service based on client - Google Patents

Abstract

PURPOSE: A client based clouding telephony service device and a method thereof are provided to build with an FMC(Fixed Mobile Convergence) client or a PC soft client without having a private switch. CONSTITUTION: A call processing control unit(21) synchronizes number plan information and controls a call of internal and external subscribers. A subscriber information control unit(24) transmits its own state information to another client in a domain under control of the call processing control unit and receives state information of another client. A subscriber information management DB(25) stores and manages state information of another client. A system DB(26) stores and manages number plan information. An internal call processing control unit(23) processes an internal subscriber call with another client in the domain based on the state information. A relay line call processing control unit(22) processes an external subscriber call with a device located outside the domain based on the state information and number plan information under control of the call processing control unit. [Reference numerals] (21) Call processing control unit; (22) Relay line call processing control unit; (23) Internal call processing control unit; (24) Subscriber information control unit; (25) Subscriber information management DB; (26) System DB; (27) Individual DB; (AA) FMC client clouding telephony service equipment

Description

Client-based cloud telephony service apparatus and method {APPARATUS AND METHOD FOR SUPPORTING CLAUDING TELEPHONY SERVICE BASED ON CLIENT}

The present invention relates to a client-based cloud telephony service apparatus and method, and more particularly, to establish a cloud telephony service using only fixed mobile convergence (FMC) clients without a private branch exchange (PBX).

Private branch exchanges (PBXs) are miniaturized telephone exchanges, and are used mainly for building internal telephone networks in general companies that use large numbers of telephones or telecommunication terminals. Such a private exchange is a private network based on a PSTN. However, as the Internet is activated, recently, a private IP (Pure IP private exchange, for example, IP-PBX) based on an IP network, which is a packet network, has been introduced. The IP-based private exchange provides multimedia services such as voice or video communication over the IP network using the H.323 or SIP protocol.

PBX refers to an exchange that provides various services such as a company, a school, etc. as one area, and provides various services such as call transfer, call waiting, three-way call, and call forwarding service. Used.

The PBX provides support for several telephone exchanges in one space and building. The PBX can also connect to a company or other local private exchange to use a local area network using a regular telephone line without the addition of a local area network that can control communications between terminals, computers and other information processing devices. In addition, the PBX is connected to the trunk line exchange and performs the same role as the terminal, and is used internally as the exchange of the PBX network. The PBX eliminates the hassle and inconvenience of moving such facilities as the current line.

The UMA (Unlicensed Mobile Access) based FMC service, which requires a dual mode terminal, connects to a PBX in the premises using a single wireless terminal and operates as an extension of a private exchange. To use. In other words, because it operates as an extension subscriber of a private exchange in the premises, it is possible to use not only free calls between stations, but also various functions provided by the PBX.

However, to do this, you must install a PBX in the premises and install the FMC client program on the device that can work with the PBX. Currently, the convenience of FMC service due to the rapid spread of smart phones has been a burden in terms of cost to purchase, install and maintain PBX in a situation where the need for extension phones is reduced in the premises.

Korea Patent Registration 10-1016644 (2011.02.15 registration)

It is an object of the present invention to establish a clouding telephony service with a client only without a private exchange (PBX).

According to an aspect of the present invention, a client-based clouding telephony service apparatus and method for establishing a clouding telephony service with a client only without a private exchange (PBX) are disclosed. According to the present invention, one client transmits and synchronizes number planning information shared by all clients existing in a domain to another client in the domain, transmits its own status information to another client, and receives status information of another client. . Thereafter, one client processes an extension subscriber call with another client in the domain based on the status information and the number plan information, and an external subscriber call with an apparatus existing outside the domain based on the number plan information.

According to the present invention, a cloud telephony service can be established using only a FMC client or a soft client for a PC without a private exchange (PBX).

1 is a diagram schematically showing a configuration of an exemplary communication network to which the present invention can be applied.
2 is a diagram illustrating a configuration of a wired / wireless integrated client-based cloud telephony service device according to an embodiment of the present invention.
3 is a flowchart illustrating a processing procedure when changing a DB for a clouding telephony service according to an embodiment of the present invention.
4 is a flowchart illustrating an outgoing call processing procedure for a clouding telephony service according to an embodiment of the present invention.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. In the following description, well-known functions or constructions will not be described in detail if they obscure the subject matter of the present invention.

1 is a diagram schematically illustrating a configuration of an exemplary communication network to which the present invention may be applied.

The present invention consists only of the FMC client 10 without establishing any telephony server such as a PBX or call server. In addition, since the PBX is not installed in the premises, there is no need to install the PBX interworking program that can interoperate with the PBX in the FMC client 10.

Information to be shared by the FMC client 10 is stored in the system DB, and information that may be stored only in the FMC client 10 is stored in a separate DB. In the present invention, when the system DB is updated, all the clients in the domain are synchronized between each FMC client 10-1 to 10-4 to have the same system DB. Each FMC client 10-1 to 10-4 transmits the changed information to all other clients in real time using a User Datagram Protocol (UDP) or a Transmission Control Protocol (TCP).

For reference, TCP (connection-oriented communication) is the most common and widely used protocol scheme on the Internet. The reason is that TCP communication performs error correction. In other words, when the server transmits some information to the client, the client may send a message back to the server confirming that the information received from the server has been properly received, and request the server to resend if the client does not receive the information. The server then sends the lost data back to the client. UDP (Unconnected Communication) is also a popular protocol on the Internet. Unlike TCP communication, it performs one-way communication. In other words, the server transmits to the client or the client to the server without any error correction. UDP communication is much faster than TCP communication because it accepts data loss that may occur in between. TCP communication is mainly used for web page transmission and the like, and UDP communication is mainly used for video / audio streaming signal transmission.

In the above, the type of information stored in the system DB includes number planning information such as a trunk line calling code, an extension telephone number, a function code, etc., which should be shared by all FMC clients 10-1 to 10-4. Types of information to be stored include rejection and call forwarding that may be stored only in each of the FMC clients 10-1 to 10-4.

FIG. 2 is a diagram illustrating a configuration of a cloud telephony service apparatus based on a wired / wireless integrated client according to an embodiment of the present invention.

As shown in Fig. 2, the clouded telephony service apparatus 20 based on the wired / wireless integrated (FMC) client 10-1 according to the present invention synchronizes number planning information and controls calls of extension and external subscribers. Under the control of the call processing control unit 21 and the call processing control unit 21, the state information of the self 10-1 is transmitted to the other clients 10-2 to 10-4 in the domain, and the other clients 10 A subscriber information control unit 24 which receives the status information of -2 to 10-4, a subscriber information management DB 25 to store and manage the status information of other clients 10-2 to 10-4, and a number Station subscribers with other clients 10-2 to 10-4 in the domain based on the status information and the number plan information under the control of the system DB 26 for storing and managing the plan information and the call processing control unit 21. Under the control of the extension call processing control unit 23 and the call processing control unit 21 which process the call, the domain is processed based on the number plan information. And a relay line call processing control unit 22 for processing an external subscriber call with a device (other PBX system or an external subscriber device of the PSTN) existing outside the network. It further includes an individual DB 27 for storing and managing its own individual setting information not shared with other clients 10-2 to 10-4.

Here, the status information is log on / off information of other clients 10-2 to 10-4 existing in the domain. The number plan information is stored in the system DB 26, such as the extension telephone number and the trunk line calling code, which should be shared by all clients 10-1 to 10-4 existing in the domain. The number plan information may further include a function code. As the individual setting information, information that may be stored only in the individual client 10-1 such as reception rejection and call forwarding is stored in the individual DB 27.

The call processing control unit 21 queries the system DB 26, the individual DB 27, and the subscriber information management DB 25, and the relay line call processing control unit 22, the extension call processing control unit 23, and the subscriber information control unit ( 25) distribute relevant information and perform other call processing functions provided by function codes. Specifically, when the number (digit) is input from the extension subscriber, the call processing control unit 21 searches the number plan information of the system DB 26 and checks the validity of the corresponding number. As a result of the inspection, when the extension connection (internal user call) is requested, the related information is distributed to the extension call processing control unit 23, and when the extension connection (external user call) is requested, the related information is distributed to the relay line call processing control unit 22. When the function code is input, the corresponding function (for example, call forwarding, pickup, etc.) is performed.

The system DB 26 is a DB that stores number planning information that should be shared by all clients 10-1 to 10-4. For example, the number plan information includes information such as an extension telephone number, a trunk line call code, and a function code. Here, the trunk line call code is a trunk line occupation code (for example, using a digit '9' as a trunk line call code) for calling an external user from a PBX or a key phone system. In addition, the extension telephone number is the telephone number of the extension user existing in the PBX or the key phone system (for example, the number 1000-1999 is designated as the extension subscriber's telephone number). Also, the function code is a code for using a function such as call forwarding / pickup (for example, using a digit '#' as a pickup function code).

When a number (digit) is input from the user, the call processing control unit 21 retrieves the number plan information of the system DB 26 and checks the validity. If the first digit of the number entered by the user is '2', the number planning information does not have a number starting with '2' (since it is not the number planning information such as the extension telephone number, the trunk line call code, or the function code). Treat as (error). If the number entered by the user is '1xxx', the extension telephone number '1xxx' is transmitted to the extension call processing controller 23 because the extension number is a valid extension telephone number, and the extension call processing controller 23 transmits the extension telephone number. Check the connection state of the subscriber through the information management DB (25), and if it is in the on-state process the extension subscriber call. In addition, if the number input from the user is '9xxxxxxx', since the first digit '9' is the trunk line calling code, the external telephone number ('xxxxxxx') is transferred to the trunk line call processing controller 22 after occupying the designated trunk line, and the relay line call. The processing control unit 22 processes an external subscriber call with an external subscriber device of another PBX system or PSTN existing outside the domain.

The individual DB 27 is a DB that stores individual setting information that does not need to be shared with other clients 10-2 to 10-4. For example, the type of individual setting information includes information such as reception rejection and call forwarding.

The subscriber information management DB 25 is a DB that stores log on / off information indicating a connection state of other clients 10-2 to 10-4 existing in the domain. At the extension connection request, the extension call processing control unit 23 checks the connection status of the corresponding client corresponding to the extension telephone number based on the subscriber information management DB 25 and connects the clients in the on state. To this end, the subscriber information control unit 24 transmits the status information of the client 10-1 to other clients 10-2 to 10-4 in the domain in real time, and the other clients 10-2 to 10-4. Status information is stored in the subscriber information management DB 25 and managed.

That is, the subscriber information control unit 24 plays a role of updating the subscriber information management DB 25 through the exchange of FMC client subscriber information in the domain. The client 10-1 logging on / off the domain transmits its status information to all other clients 10-2-10-4 in the domain and receives the client-10-10-10-receiving this information. 4) updates the information necessary for call processing in its subscriber information management DB, and can directly call the desired client without going through a separate call server in the extension call processing.

The extension call processing control unit 23 queries the system DB 26 and the subscriber information management DB 25 to obtain the extension telephone number and the status information, and performs the functions such as signal processing and call control for calls between stations. . Specifically, under the control of the call processing control unit 21, the extension call processing control unit 23 requests an extension telephone number (e.g., client 2) when an extension connection request is made to other clients 10-2 to 10-4 existing in the domain. Check the extension number of the client to check the connection state of the client 10-2 and process the extension subscriber call with the client 10-2 in the on state.

When the call originating from the call processing control unit 21 is determined to be a relay line call, the relay line call processing controller 22 queries the system DB 26 and recognizes that the relay line is a call code. Do this. Specifically, under the control of the call processing control unit 21, the relay line call processing control unit 22 checks the relay line call code when requesting an external connection to a device (an external PBX system or an external subscriber device of the PSTN) existing outside the domain. Handles an external subscriber call with the device.

3 is a flowchart illustrating a processing procedure when changing a DB for a clouding telephony service according to an embodiment of the present invention.

The number plan information synchronized by the FMC client 10 is stored in the system DB 26 as information that all clients must share, such as a trunk line call code, an extension telephone number, a function code, and the like. In addition, information that may be stored only in the client, such as rejection and call forwarding, is stored in the individual DB 27.

When the number plan information stored in the system DB 26 is changed (302), the change is allowed only when logged in with the administrator ID (302 to 304), otherwise the change request is rejected (306). When the system DB 26 is changed in one client 10-1, the changed details are transmitted to other clients 10-2 to 10-4 so that all the clients can share. That is, when the system DB 26 is updated, information is also transmitted to other clients 10-2 to 10-4 in the domain to synchronize all clients 10-1 to 10-4 in the domain to have the same system DB. .

On the other hand, when changing the information stored in the individual DB (27) (302) is not shared with other clients (10-2 ~ 10-4), only the information of the individual DB (27) of the client 10-1 Update (307). That is, when the information stored in the individual DB 27 is changed, only the individual DB 27 of the own 10-1 is updated and not transmitted to the other clients 10-2 to 10-4.

The reason for separating into the individual DB 27 and the system DB 26 as described above is to minimize the traffic for DB synchronization. Information that can collect the status of the other party while exchanging call processing messages, such as rejection and call forwarding, is built into a separate DB 27 and minimizes the system DB 26.

4 is a flowchart illustrating an outgoing call processing procedure for a clouding telephony service according to an embodiment of the present invention.

If a number (digit) is input from the user, the call processing control unit 21 checks the validity by searching the number plan information of the system DB 26 (401).

As a result of the check, if the number input from the user is a function code, the call processing control unit 21 performs a corresponding function (for example, call forwarding, pickup, etc.) (403).

As a result of the inspection, if the number input from the user is a trunk line call code (for example, the first digit is '9'), the relevant information is distributed to the trunk line call processing controller 22 after occupying the designated trunk line. The relay line call processing controller 22 processes an external subscriber call with an external subscriber device of another PBX system or PSTN existing outside the domain by using the relay line protocol (step 404).

As a result of the inspection, if the number input from the user is a valid extension telephone number, the relevant information is distributed to the extension call processing control section 23 (that is, the extension telephone number is transferred to the extension call processing control section 23), and the extension call processing control section 23 is provided. Check the connection state of the corresponding extension telephone number through the subscriber information management DB (25) (405), and if it is on, processes the extension subscriber call using the extension protocol (406).

As described above, the present invention can reduce the amount of traffic for synchronizing the system DB and the subscriber information management DB, and if the number of FMC clients is large, a large amount of bandwidth is required, so that it can be flexibly implemented in a small domain.

The client-based cloud telephony service of the present invention can be applied not only to the environment using the FMC but also to the small office using the IP wired network. Instead of installing a separate PBX, a small IP telephony service can be implemented by simply installing a soft client for the PC.

Although the present invention has been described in connection with some embodiments thereof, it should be understood that various changes and modifications may be made therein without departing from the spirit and scope of the invention as understood by those skilled in the art. something to do. It is also contemplated that such variations and modifications are within the scope of the claims appended hereto.

21: call processing control unit 22: relay line call processing control unit
23: extension call processing control unit 24: subscriber information control unit
25: subscriber information management DB 26: system DB
27: individual DB

Claims (11)

A client-based cloud telephony service device,
A call processing control unit for synchronizing the number planning information and controlling call of extension and external subscribers;
A subscriber information control unit which transmits its own state information to another client in a domain and receives the state information of the other client under the control of the call processing controller;
A subscriber information management DB that stores and manages state information of the other clients;
A system DB for storing and managing the number plan information;
An extension call processing control unit for processing an extension subscriber call with the other client in the domain based on the state information and the number plan information under the control of the call processing control unit; And
And a relay line call processing control unit for processing an external subscriber call with a device existing outside the domain based on the number planning information, under the control of the call processing control unit. The method of claim 1,
And the status information is log on / off information of the other client. The method of claim 2,
And the number plan information includes an extension telephone number and a trunk line call code shared by all clients existing in the domain. The method of claim 3,
The number plan information, the client-based cloud telephony service device further comprises a function code. The method of claim 3,
The extension call processing control unit checks the extension telephone number when checking the extension connection request to the other client, checks the connection state of the corresponding client, and processes the extension subscriber call with the on-state client. Ding Telephony Service Device. 5. The method of claim 4,
The relay line call processing controller, when requesting an external line connection to a device outside the domain, checks the relay line call code and processes an external subscriber call with the device. 7. The method according to any one of claims 1 to 6,
A client-based clouding telephony service device further comprising a separate DB for storing and managing their own setting information not shared with the other clients. Client-based cloud telephony service method,
a) synchronizing, by one client, transmitting number plan information shared by all clients existing in the domain to another client in the domain;
b) the one client transmitting its status information to the other client and receiving the status information of the other client;
c) processing, at the one client, an extension subscriber call with the other client in the domain based on the status information and the number planning information; And
d) processing, at the one client, an external subscriber call with a device existing outside the domain based on the number planning information. 9. The method of claim 8,
The status information is log on / off information of the other client,
The number planning information, the client-based cloud telephony service method including an extension telephone number and a trunk line call code shared by all clients existing in the domain. 10. The method of claim 9,
In step c), when the extension connection request is made to the other client, the client-based clouding process checks the extension telephone number, checks the connection state of the corresponding client, and processes the extension subscriber call with the on-state client. Telephony service method. 10. The method of claim 9,
The step d) is a client-based cloud telephony service method for processing an external subscriber call with the device by checking the relay line call code when requesting an external connection to the device that exists outside the domain.

Images