KR101111229B1 - Caller id conversion application server - Google Patents

Abstract

The caller number translation application server includes a caller number database that stores a telephone number pair between a first caller number of a Fixed Mobile Convergence (FMC) terminal and a second caller number uniquely assigned to the FMC terminal, and a caller number and recipient number. And a number conversion module for retrieving the corresponding second calling party number from the calling party number database and converting the calling party number into the corresponding second calling party number to generate a second call setting message.

Description

Caller ID Conversion Application Server {CALLER ID CONVERSION APPLICATION SERVER}

The disclosed technology relates to a caller number conversion application server applicable to a Voice over IP (VoIP) service or an IP Multimedia Subsystem (IMS) service, and in particular, a caller of a fixed mobile convergence (FMC) terminal that can use two communication services. A caller number translation application server for translating numbers.

The caller verification service informs the receiver of the caller's calling telephone number, and the receiver can identify the caller through the calling telephone number. For example, the receiving terminal may store a list of telephone numbers including a name and a telephone number, and display the caller's name when the telephone number is received. However, if the caller uses another terminal, the receiving terminal cannot identify the caller.

Among the embodiments, the caller number translation application server stores a caller number database and caller number that stores a telephone number pair between a first caller number of a Fixed Mobile Convergence (FMC) terminal and a second caller number uniquely assigned to the FMC terminal. A number conversion for retrieving the corresponding second calling party number from the calling party number database and converting the calling party number to the corresponding second calling party number to generate a second call setting message when a first call setting message including a callee number and a recipient number is received; Contains modules

Among the embodiments, the call setup method between the fixed mobile convergence (FMC) terminal and the receiving terminal is a caller number conversion including an IP Multimedia Subsystem (IMS) core, a Home Subscriber Server (HSS) and a caller number conversion application server. Is performed in the system. The FMC terminal has a first caller number for a VoIP service, the home subscriber server includes subscription information for a caller number translation service, and the caller number conversion application server is between the first caller number and the second caller number. Store a telephone number pair, and the second caller number is uniquely assigned to the FMC terminal. The method includes receiving, by the IMS core, a first call setup message from the FMC terminal, the first call setup message including the first caller number and the receiver number, wherein the first call setup message is received via a VoIP service. Determining whether the first caller number is subscribed to a caller number conversion service by communicating with the home subscriber server, and the IMS core sends the first call setup message to the caller number translation application server; Determining, by the caller number conversion application server, whether there is a second caller number associated with the first caller number, and the caller number conversion application server generates a second call setup message based on the associated second caller number; Transmitting to the IMS core and the IMS core to the second call setup method. On the basis of whether a step of performing a call setup between the FMC terminal and the called terminal.

Among the embodiments, the caller number translation system includes an IP Multimedia Subsystem (IMS) core, a Home Subscriber Server (HSS) and a caller number translation application server and establishes a call between a Fixed Mobile Convergence (FMC) terminal and a receiving terminal. Do this. The FMC terminal has a first caller number for a VoIP service, the home subscriber server includes subscription information for a caller number translation service, and the caller number conversion application server is between the first caller number and the second caller number. Store a telephone number pair, and the second caller number is uniquely assigned to the FMC terminal. The IMS core receives a first call setup message including the first caller number and the recipient number from the FMC terminal through a VoIP service, and the first caller number is the caller number conversion service through communication with the home subscriber server. Determine whether it is subscribed to, send the first call setup message to the caller number conversion application server, the caller number conversion application server determines whether there is a second caller number associated with the first caller number, A second call setup message is generated based on the associated second calling party number and transmitted to the IMS core, and the IMS core performs call setup between the FMC terminal and the receiving terminal based on the second call setup message. .

1 is a diagram illustrating a caller number translation system according to an embodiment of the disclosed technology.
FIG. 2 is a block diagram illustrating a caller number translation application server of FIG. 1.
FIG. 3 is a flowchart illustrating a procedure in which the web client of FIG. 1 registers a second caller number with a caller number conversion application server.
4 is a flowchart illustrating a call setup method between an FMC terminal and a receiving terminal performed in the caller number conversion system of FIG. 1.

The description of the disclosed technique is merely an example for structural or functional explanation and the scope of the disclosed technology should not be construed as being limited by the embodiments described in the text. That is, the embodiments may be variously modified and may have various forms, and thus the scope of the disclosed technology should be understood to include equivalents capable of realizing the technical idea.

On the other hand, the meaning of the terms described in the present application should be understood as follows.

The terms " first ", " second ", and the like are used to distinguish one element from another and should not be limited by these terms. For example, the first component may be named a second component, and similarly, the second component may also be named a first component.

The term “and / or” should be understood to include all combinations that can be suggested from one or more related items. For example, the meaning of “first item, second item and / or third item” may be given from two or more of the first, second or third items as well as the first, second or third items. Any combination of the possible items.

When a component is referred to as being "connected" to another component, it should be understood that there may be other components in between, although it may be directly connected to the other component. On the other hand, when an element is referred to as being "directly connected" to another element, it should be understood that there are no other elements in between. On the other hand, other expressions describing the relationship between the components, such as "between" and "immediately between" or "neighboring to" and "directly neighboring to", should be interpreted as well.

Singular expressions should be understood to include plural expressions unless the context clearly indicates otherwise, and terms such as "include" or "have" refer to features, numbers, steps, operations, components, parts, or parts thereof described. It is to be understood that the combination is intended to be present, but not to exclude in advance the possibility of the presence or addition of one or more other features or numbers, steps, operations, components, parts or combinations thereof.

For each step, the identifiers (e.g., a, b, c, ...) are used for convenience of description, and the identifiers do not describe the order of the steps, and each step is clearly contextual. Unless stated in a specific order, it may occur differently from the stated order. That is, each step may occur in the same order as specified, may be performed substantially simultaneously, or may be performed in the reverse order.

All terms used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. Terms defined in commonly used dictionaries should be interpreted to be consistent with meaning in the context of the relevant art and can not be construed as having ideal or overly formal meaning unless expressly defined in the present application.

1 is a diagram illustrating a caller number translation system according to an embodiment of the disclosed technology.

Referring to FIG. 1, the calling party number conversion system 100 includes a fixed mobile convergence (FMC) terminal 110, an access point (AP) 112, a base station transceiver subsystem (BTS) 114, and an IMS ( IP Multimedia Subsystem (120) core, home subscriber server (HSS) 130, caller number translation application server 140 and Web client 150. The FMC terminal 110 is a terminal capable of accessing both a local area network (LAN) such as WiFi or Bluetooth and a cellular network such as CDMA or WCDMA. Hereinafter, the FMC terminal 110 has a VoIP client using a Voice over IP (VoIP) service. Assume a terminal. That is, the FMC terminal 110 and the access point 112 are connected by a Voice over IP (VoIP) service, and the FMC terminal 110 and the BTS 114 are connected by a cellular service. The FMC terminal 110 may have a first caller ID (ie, an Internet phone number) for VoIP service. For example, in Korea, the first calling party number may correspond to [070-xxxx-xxxx]. The IMS core 120 is an architecture for various communication services, such as the FMC terminal 110 and a WLAN or cellular network. It can be connected through. In the connection of the WLAN communication, the IMS core 120 is connected to the FMC terminal 110 by VoIP service. In the connection of cellular communication, the IMS core 120 may be connected to the FMC terminal 110 as a cellular data service for various data-based communication including the VoIP based voice service of the FMC terminal 110, For voice communication based on cellular circuit communication, the FMC terminal 110 may be connected to a cellular voice service through a device such as a media gateway control function (MGCF) of the IMS core 120.

The home subscriber server 130 is a master database for subscriber information and stores subscriber information for providing a communication service. For example, the home subscriber server 130 may store subscriber profile information such as name, age or gender and subscriber location information. In addition, the home subscriber server 130 includes subscription information for the calling party number translation service. The subscription information for the calling party number conversion service indicates whether the subscriber subscribes to the calling party number conversion service.

Calling party number conversion application server 140 stores the first calling party number and the second calling party number associated with the first calling party number. Here, the second calling party number is not an arbitrarily assignable number but corresponds to a cellular phone, home phone number or work phone number uniquely assigned to the FMC terminal 110. In one embodiment, the second caller number may correspond to the number of a cellular phone, home phone or work phone owned by the owner of the FMC terminal 110. In another embodiment, the second caller number may correspond to a number managed by the owner of the FMC terminal 110. Here, the “managed number” is the number of a cellular phone, home phone or work phone not owned by the owner of the FMC terminal 110, through which the authentication procedure performed by the owner of the FMC terminal 110 can be legally passed. Means. The authentication procedure is in accordance with the policy of the communication provider, and may correspond to, for example, a procedure of confirming whether the second calling party number is legally owned or managed by the owner of the FMC terminal 110. In one embodiment, the caller ID translation application server 140 may be applied to an IMS network, and in another embodiment, the caller ID translation application server 140 is a VoIP configured with a Session Initiation Protocol (SIP) Proxy or an H.323 Gatekeeper. Applicable to the service network.

The web client 150 may be implemented as a computing device for web communication. In one embodiment, the web client 150 may be implemented as a computer on which a web browser is installed. That is, if the FMC terminal 110 can perform web communication, the web client 150 may be implemented as the FMC terminal 110.

FIG. 2 is a block diagram illustrating a caller number translation application server of FIG. 1.

Referring to FIG. 2, the caller number conversion application server 140 includes a web server module 210, a caller number database 220, an authentication module 230, a number conversion module 240, and a controller 250. The web server module 210 performs web communication with the web client 150 to register the second caller ID. Calling party number database 220 stores a telephone number pair between the first calling party number and the second calling party number associated with the first calling party number. That is, the caller number database 220 stores a telephone number pair between the Internet phone number of the FMC terminal 110 and a cellular phone, home telephone number, or work telephone number uniquely assigned to the FMC terminal 110.

The authentication module 230 is a cellular phone in which the web client 150 is uniquely assigned to the first caller number (ie, the Internet phone number of the FMC terminal 110) and the second caller number (ie, the FMC terminal 110). Number) to perform authentication when registering the caller ID database (230). If successfully authenticated, the authentication module 230 registers a telephone number pair between the first caller number and the second caller number in the caller number database 220.

The number conversion module 240 is a caller included in the first call setup message in the caller number database 220 when the first call setup message including the caller number and the receiver number is received from the IP Multimedia Subsystem (IMS) core 120. The second caller number corresponding to the number is searched and the caller number included in the first call setup message is converted into the corresponding cellular phone number to generate a second call setup message. If not found, the number conversion module 240 generates the second call setup message without converting the first call setup message. When the second call setup message is generated, the number translation module 240 transmits the second call setup message to the IMS core 120.

The control unit 240 controls the entire module of the caller ID translation application server 140, and allows the IMS core 120 to perform a call setup between the FMC terminal 110 and the receiving terminal with the second call setup message. 3 to 4, the operation method of the controller 240 will be described.

On the other hand, in another embodiment, unlike the Figure 2, when the subscriber subscribes to the number conversion service, the second caller number is specified in the subscription information, and as the service subscription procedure, the first caller number and the first caller number in the database 2 Caller ID pairs can be registered. In this case, the caller ID translation application server 140 may not include the web server module 210 and the authentication module 230. In another embodiment, if the subscriber subscribes to the calling party number conversion service, the operator prepares for the calling party number conversion service based on the first caller number of the FMC terminal for the VoIP service and the second caller number uniquely assigned to the FMC terminal. To complete.

FIG. 3 is a flowchart illustrating a procedure in which the web client of FIG. 1 registers a second caller number with a caller number conversion application server.

FIG. 3 assumes that the service provider performs an authentication procedure for registration of the second calling party number. However, another communication provider may register the default number as the second caller number without performing the authentication procedure of FIG. 3.

In FIG. 3, the web client 150 performs an authentication procedure. The web client 150 transmits authentication data for authentication to the caller number translation application server 140 (step S310). In one embodiment, the authentication data may include an ID and password for the owner of the FMC terminal 110. If necessary, the authentication data may further include data relating to an accredited certificate. The caller number translation server 140 performs authentication (step S320). In one embodiment, the caller ID translation application server 140 may request the home subscriber server 130 to verify the owner's personal information.

When the authentication is completed, the web client 150 performs a second caller ID registration procedure. The web client 150 transmits the second caller number to the caller number conversion application server 140 (step S330). In one embodiment, prior to transmission, the caller ID translation application server 140 may receive the default cellular phone number of the FMC terminal 110 by sending the second caller number to the web client 150. In another embodiment, the web client 150 may receive an appropriate cellular phone number under the control of the owner of the FMC terminal 110 and transmit it to the caller number conversion application server 140. The caller number conversion application server 140 stores the caller number database 220 together with the first caller number if the second caller number received from the web client 150 is appropriate (step S340). When the registration is completed, the calling party number conversion application server 140 transmits the registration completion information to the web client 150 (step S350).

4 is a flowchart illustrating a call setup method between an FMC terminal and a receiving terminal performed in the caller number conversion system of FIG. 1.

In FIG. 4, the FMC terminal 110 transmits a first call setup message to the IMS core 120 through the access point 112 (step S410). The call establishment message includes a first caller number (ie, an Internet phone number) and a recipient number. In one embodiment, the first call setup message may be sent via a VoIP service. That is, the IMS core 120 receives the first call setup message including the first caller number and the receiver number from the FMC terminal 110.

The IMS core 120, in communication with the home subscriber server 130, determines whether the first caller number is subscribed to the caller number translation service. More specifically, the IMS core 120 inquires whether the home subscriber server 130 subscribes to the calling party number conversion service of the first calling party number (step S415). The home subscriber server 130 responds to the IMS core 120 whether to subscribe to the calling party number conversion service based on the first calling party number (step S420).

The IMS core 120 transmits the first call setup message to the caller number translation application server 140 (step S425). The calling party number conversion application server 140 determines whether there is a second calling party number associated with the first calling party number, and generates and transmits a second call setup message to the IMS core 120 based on the second calling party number ( Step S430). Here, the second call setup message corresponds to a message in which the caller number is converted to the second caller number in the first call setup message.

The IMS core 120 performs call setup with the receiving terminal 160 in the second call setup message (step S435). In the call setup process, if the receiving terminal 160 corresponds to the cellular phone, the IMS core 120 may search for the location of the receiving terminal 160 to perform paging. Here, even though the IMS core 120 performs call setup with the receiving terminal 160 using the second caller ID, call setup between the FMC terminal 110 and the IMS core 120 is performed with the first caller ID.

The receiving terminal 160 responds to the second call setup message (step S440). The IMS core 120 performs call setup between the FMC terminal 110 and the receiving terminal 160 based on the second call setup message (step S445). That is, the FMC terminal 110 completes the call setup with the receiving terminal 160 by VoIP service in terms of transmission, and completes the call setup with the receiving terminal 160 by the service corresponding to the second caller number in view of reception. When the call setup is completed, the FMC terminal 110 transmits the first voice or non-voice data to the receiving terminal 160 through the VoIP service (step S450). In the course of transmission, the first voice or non-voice data is transmitted to the VoIP service via the access point 114.

When the call setup is completed, the receiving terminal 160 transmits the second voice or non-voice data to the FMC terminal 110 (step S460). In terms of reception, the FMC terminal 110 completes the call setup with the reception terminal 160 as a service corresponding to the second caller ID. For example, if the calling party number of the FMC terminal 110 corresponds to a cellular phone number, the second voice or non-voice data may be transmitted to the cellular service. The disclosed technique may have the following effects. It is to be understood, however, that the scope of the disclosed technology is not to be construed as limited thereby, as it is not meant to imply that a particular embodiment should include all of the following effects or only the following effects.

The calling party number conversion system according to an embodiment provides a recipient with a cellular phone number uniquely assigned to the owner of the FMC terminal in a cellular service, rather than a calling party number for the VoIP service of the FMC terminal, in a call connection process. Make it easy to identify the caller. For example, even if the number of the calling terminal corresponds to [070-xxxx-xxxx], the receiving terminal may display [010-yyyy-yyyy] as the called number. In the case of cellular phone numbers, the likelihood of a recipient misunderstanding the calling number is lower. In particular, if the cost of the VoIP service is lower, the calling party number conversion system may help the calling party to use the cellular phone number at a lower cost.

In the caller ID conversion system according to an embodiment, the receiving terminal can easily contact the calling terminal through the cellular phone number rather than the Internet phone number that is unfamiliar to the user. In particular, since the cellular phone number is provided to the receiving terminal, the receiving terminal can easily contact the calling terminal through the cellular phone number even in a situation where the FMC terminal moves to an area where VoIP service cannot be received.

The caller number translation system according to an embodiment may help the caller's location tracking since the cellular phone number is transmitted. For example, if the caller makes an emergency call (eg, 119), the service provider can track the caller's location based on the cellular phone number.

The calling party number conversion system according to an embodiment may use any number that the subscriber wants to show to the other party as the calling party number, such as a home number and a work phone number, as well as a cellular number as the second calling party number. However, since the calling party number conversion system does not assign an arbitrary calling party number to the calling terminal, illegal use of the cellular phone number can be prevented.

Although described above with reference to a preferred embodiment of the present invention, those skilled in the art will be variously modified and changed within the scope of the invention without departing from the spirit and scope of the invention described in the claims below I can understand that you can.

Claims (12)

A caller number database for storing a telephone number pair between a first caller number of a fixed mobile convergence (FMC) terminal and a second caller number uniquely assigned to the FMC terminal; And
When a first call setup message including a caller number and a receiver number is received, the second caller number is retrieved from the caller number database, and the caller number is converted into the corresponding second caller number to generate a second call setup message. Caller number translation application server comprising a number translation module. The method of claim 1, wherein the number translation module
And if the second caller number is not found, generating the second call setup message without converting the first call setup message. The method of claim 2, wherein the FMC terminal is
A caller number translation application server, characterized in that the call setup with the receiving terminal is completed by a Voice over IP (VoIP) service. The method of claim 3, wherein the FMC terminal is
In terms of reception, the caller number conversion application server, characterized in that the call setup with the receiving terminal is completed by the service corresponding to the second caller number. 5. The caller number translation application server of claim 4, wherein if the second caller number corresponds to a cellular phone number, the service corresponding to the second caller number corresponds to a cellular service. The method of claim 1, wherein the caller ID translation application server
IP Multimedia Subsystem (IMS) core and home subscribers. Caller number translation application server, characterized in that connected to the server (HSS, Home Subscriber Server) by IP network. The method of claim 6, wherein the caller ID translation application server
And a web server module for performing web communication with a web client for authenticating the FMC terminal. The method of claim 7, wherein the caller ID translation application server
And an authentication module for performing authentication when the web client registers the first caller number and the second caller number in the caller number database. The method of claim 8, wherein the caller ID translation application server
And a control unit for causing the IMS core to perform call setup between the FMC terminal and the receiving terminal with the second call setup message. The method of claim 1, wherein the second caller number is
Caller number conversion application server, characterized in that corresponding to the cellular phone number, home phone number or work phone number that is uniquely assigned to the FMC terminal. In a call setup method between a fixed mobile convergence (FMC) terminal and a receiving terminal performed in a calling party number conversion system including an IMS (IP Multimedia Subsystem) core, a home subscriber server (HSS), and a calling party number conversion application server. The FMC terminal has a first caller number for a VoIP service, the home subscriber server includes subscription information for a caller number conversion service, and the caller number conversion application server includes the first caller number and the second caller. Store telephone number pairs between numbers, and wherein the second caller number is uniquely assigned to the FMC terminal;
Receiving, by the IMS core, a first call setup message from the FMC terminal, the first call setup message comprising the first caller number and the recipient number, the first call setup message being received via a VoIP service;
Determining, by the IMS core, whether the first calling party number is subscribed to a calling party number conversion service by communicating with the home subscriber server;
The IMS core sending the first call setup message to the caller number translation application server;
Determining, by the caller number translation application server, whether there is a second caller number associated with the first caller number;
Generating, by the caller number translation application server, a second call setup message based on the associated second caller number and transmitting it to the IMS core; And
And the IMS core performing call setup between the FMC terminal and the receiving terminal based on the second call setup message. In a caller number conversion system including an IP Multimedia Subsystem (IMS) core, a home subscriber server (HSS), and a caller number conversion application server and performing call setup between a fixed mobile convergence (FMC) terminal and a receiving terminal, The FMC terminal has a first caller number for VoIP service, the home subscriber server includes subscription information for caller number conversion service, and the caller number conversion application server includes the first caller number and the second caller number. A telephone number pair, and wherein the second caller number is uniquely assigned to the FMC terminal-
The IMS core receives a first call setup message including the first caller number and the recipient number from the FMC terminal through a VoIP service, and the first caller number is the caller number conversion service through communication with the home subscriber server. Determine whether the service is subscribed to, transmit the first call setup message to the caller number translation application server,
The calling party number conversion application server determines whether there is a second calling party number associated with the first calling party number, generates a second call setup message based on the associated second calling party number, and sends it to the IMS core;
And the IMS core performs call setup between the FMC terminal and the receiver terminal based on the second call setup message.

Images