KR101051021B1 - Incoming call history providing method and system - Google Patents

Abstract

Disclosed are a method and a system for providing an incoming history. The system that notifies the incoming call history to the outbound roaming terminal stores the service registration information for the outbound roaming terminal, and analyzes the service registration information when the incoming call is requested to the outbound roaming terminal. A gateway location register that generates and transmits call reception history information when the call registration is registered in the call history notification service; The call control device which stores the incoming history information and the time information at which the incoming history information is received as the history information, extracts the stored history information according to a predetermined condition, and generates and transmits the incoming history notification message including the extracted history information. ; And a message center for transmitting the incoming history notification message to the outbound roaming terminal. Accordingly, the incoming call history can be provided to the outbound roaming terminal.

Roaming, roaming, incoming call

Description

Method and system providing history of receiving call

The present invention relates to mobile communications, and more particularly, to a method and system for blocking spam calls to outbound roaming terminals.

When a subscriber does not receive an incoming call due to various reasons such as a shadow area or a busy call, a service (eg, a catch call) that provides information on an incoming communication call currently exists.

However, in case of international roaming, the originating information of the originating terminal may be distorted due to the nature of the roaming network and transmitted to the outbound roaming called terminal. For this reason, the outbound roaming called terminal does not display the calling information of the calling terminal normally. In addition, in the case of an international roaming network, when the outbound roaming terminal is located in a transliteration region, or is busy or does not answer, a call release message is transmitted to its own communication network. However, the company's communication network is not informed of the reason for the failure of the incoming call from the international roaming network, and receives a call release message, there is a problem that can not provide the catch call service.

In addition, when the outbound roaming called terminal is located in the transliteration region, or when the incoming call is unsuccessful due to busy or no answer, the outbound roaming called terminal may not grasp the incoming call from the calling terminal. .

The present invention is to provide a method and system that can provide the incoming history to the outbound roaming terminal.

In addition, the present invention can enhance the user's convenience by allowing the outbound roaming subscriber to check the incoming history while roaming.

According to one aspect of the invention, there is provided a system for notifying the incoming history to the outbound roaming terminal.

According to an embodiment of the present invention, in the system for notifying the incoming call history to the outbound roaming terminal, storing the service registration information for the outbound roaming terminal, the call request to the outbound roaming terminal A gateway location register which analyzes the service registration information and generates and transmits the reception history information when the outbound roaming terminal is registered in the reception history notification service; Stores the incoming call history information and the time information at which the incoming call history information is received as history information, extracts the stored history information according to a predetermined condition, and generates and transmits an incoming call history notification message including the extracted history information. Call control device; And a message center for transmitting the incoming history notification message to the outbound roaming terminal.

According to another aspect of the present invention, a method for notifying a call history to an outbound roaming terminal is provided.

According to an embodiment of the present invention, in a method for notifying an incoming call history of an outbound roaming terminal, the gateway location register analyzes previously stored service registration information when requesting an outgoing call to the outbound roaming terminal. When the bound roaming terminal is registered in the call history notification service, generating and transmitting call history information; Storing, by the call control device, the reception time history information and the reception history information as history information; Extracting, by the call control device, the history information according to a predetermined condition, and generating and transmitting a call history notification message including the extracted history information; And transmitting, by the message transmission center, the incoming history notification message to the outbound roaming terminal.

By providing a call history providing method and system according to the present invention, it is possible to provide a call history to the outbound roaming terminal.

In addition, the present invention also has the advantage that the outbound roaming subscriber can check the incoming history while roaming to enhance the user's convenience.

As the invention allows for various changes and numerous embodiments, particular embodiments will be illustrated in the drawings and described in detail in the written description. However, this is not intended to limit the present invention to specific embodiments, it should be understood to include all transformations, equivalents, and substitutes included in the spirit and scope of the present invention. In the following description of the present invention, if it is determined that the detailed description of the related known technology may obscure the gist of the present invention, the detailed description thereof will be omitted.

The terms first, second, etc. may be used to describe various components, but the components should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from another.

The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting of the present invention. Singular expressions include plural expressions unless the context clearly indicates otherwise. In this application, the terms "comprise" or "have" are intended to indicate that there is a feature, number, step, action, component, part, or combination thereof described in the specification, and one or more other It is to be understood that the present invention does not exclude the possibility of the presence or the addition of features, numbers, steps, operations, components, parts, or a combination thereof.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is a block diagram schematically illustrating a configuration of a mobile communication system according to an embodiment of the present invention.

Referring to FIG. 1, a mobile communication system according to an embodiment of the present invention includes a first communication network and a second communication network. In the present specification, the first communication network is its own communication network, and the second communication network will be described on the assumption that it is an overseas third party network. This is for convenience of description and does not limit the communication network to which the present invention can be applied.

The first communication network includes a switch (mobile switching center (MSC) (hereinafter referred to as MSC) 110), a gateway location register (GLR) 120, a call control device (SCP) point, hereinafter referred to as SCP 130, and a home location register (HLR: 140).

The MSC 110 performs a control function and an interworking function between a public telephone network and another network switch so that the wireless base stations can be efficiently operated. In addition, when the incoming call is requested from the calling terminal 170, the MSC 110 requests the HLR 150 for location information of the called terminal 160 accordingly. Here, the MSC 110 may be a gateway mobile switching center (GMSC). GMSC is another form of MSC 110, which performs a gateway function between two networks. That is, the MSC 110 according to the embodiment of the present invention may be the MSC 110 or the GMSC 110 corresponding to the communication service provider to which the calling terminal 170 subscribes. Of course, it will be apparent to those skilled in the art in view of the technical spirit of the present invention that the MSC 110 and the GMSC 110 may be implemented as one device performing the same or similar functions regardless of the name in the first communication network.

The GMSC 120 serves as a gateway to enable roaming services between mobile operators using different mobile application part (MAP) protocols (eg, GSM, ANSI-41, PDC, etc.).

In addition, the GMSC 120 includes incoming information and outgoing information when the called terminal (ie, the outbound roaming terminal) is registered in the incoming history notification service corresponding to the incoming call requested to the outbound roaming terminal. Generate incoming call history information and send it to SCP (130). In this case, the incoming information may be identification information of the called terminal 160, and the calling information may be identification information of the calling terminal 170. In addition, identification information of the called terminal 160 and the calling terminal 170 may be any one of a telephone number, a mobile identification number (MIN), and an electronic serial number (ESN).

Hereinafter, the incoming call history notification service according to an embodiment of the present invention is a service for storing incoming call history information for a predetermined period in a state where the called terminal is outbound roaming, and providing the stored history information to the called terminal according to a predetermined condition. Explain. However, it will be apparent to those skilled in the art in view of the technical spirit of the present invention that history information according to an embodiment of the present invention may be provided to the called terminal in various ways.

In addition, when the GMSC 120 receives the incoming history message from the message center 140, the GMSC 120 may transmit it to the foreign exchange.

SCP 130 is a device for managing an intelligent network service subscriber and performing service logic. For this purpose, SCP 130 manages the profiles of the intelligent network service subscribers and / or related databases.

In addition, when the reception history information is received from the GMSC 120, the SCP 130 stores the received reception history information and the time information at which the reception history information is received as history information. Here, the history information may be mapped to and stored in the called information or roaming information for the called terminal.

Here, the history information may further include transmission status information. If the history information further includes transmission status information, the SCP 130 may extract history information of which transmission status information is not transmitted from the accumulated history information according to a predetermined condition, and transmit the extracted history information. have.

In addition, SCP 130 may store the history information, extract the accumulated (stored) history information according to a predetermined condition, and generate and transmit an incoming call history notification message including the extracted history information.

For example, when the incoming call history notification request message is received from the GLR 120, the SCP 130 may extract and store the stored (accumulated) history information to generate and transmit the incoming call history notification message. For example, the GLR 120 may set a communication state of an outbound roaming terminal to a non-receiving state when a call release message is received from a foreign exchange without setting an incoming call. When the communication state of the outbound roaming terminal is changed from the non-receivable state to the callable state, the GLR 120 may generate a call history notification request message and transmit it to the SCP 130.

In another example, SCP 130 generates each incoming call history information for a cumulative incoming call history every certain period (e.g., 30 minutes, 1 hour, 1 day, etc.). Subsequently, the SCP 130 may generate an incoming history message including the incoming history information and transmit it to the outbound roaming terminal. Here, SCP 130 may prevent the historical information from being transmitted when the number of stored (or accumulated) historical information is less than a threshold value (eg, when the number of accumulated historical information is 0) according to an implementation method. It may be.

Here, the incoming call history information may include calling information and calling time information. Of course, the incoming call history information may further include various information corresponding to the calling terminal 170 (for example, nickname information set corresponding to the calling terminal 170, the name of the calling subscriber, etc.).

The HLR 150 stores various information about the subscriber and manages location information on the mobile communication terminal. In addition, when the location query request message is received, the HLR 150 extracts roaming information corresponding to the called terminal 160 and transmits the extracted roaming information to the GLR 120. Here, the location query request message includes incoming information and originating information. The incoming information may be identification information of the called terminal 160 and the calling information may be identification information of the calling terminal 170. For example, the identification information of the called terminal 160 and the calling terminal 170 may be a telephone number of each terminal, a mobile identification number (MIN), and an electronic serial number (ESN).

Roaming information may include an international mobile station identity (IMSI) of the called terminal 160 and originating information.

The message center 140 performs a function of transmitting a call history message to the called terminal 160 under the control of the SCP 130. Here, the incoming history message may be transmitted in any one of a short message, a long message, and a multimedia message.

The second communication network is an overseas communication network in which the outbound roaming terminal roams, and provides a roaming service to the outbound roaming terminal.

The calling terminal 170 and the called terminal 160 are terminals connected to a communication network to perform incoming and outgoing functions of voice calls. For example, the calling terminal 170 and the called terminal 160 may be a cellular phone, a personal communication service (PCS) phone, a PDA phone, a GSM phone, a WCDMA phone, a CDMA-2000 phone, a DMB phone, or the like. Hereinafter, it will be described on the assumption that the called terminal 160 is an outbound roaming terminal.

2 is a block diagram illustrating an internal configuration of a call control device according to an embodiment of the present invention.

Referring to FIG. 2, the SCP 130 according to an embodiment of the present invention includes a communication unit 210, a history storage unit 220, a message transmission unit 230, and a control unit 240.

The communication unit 210 performs a function of transmitting and receiving data with other devices (eg, the HLR 150, the GLR 120, the message center 140, etc.) of the mobile communication system through a communication network.

For example, the communication unit 210 receives an incoming history message including the origination information and the incoming information from the GLR 120. In addition, the communication unit 210 may transmit a call history notification message including one or more call history information to the message center 140 according to a preset condition under the control of the controller 240.

The history storage unit 220 extracts outgoing information and incoming information from the incoming history message received from the GLR 120, and stores the incoming history message as history information together with the received time information. The history information may further include state information for distinguishing whether the history information has been transmitted to the called terminal 160. When the status information is included in the history information, the transmitted history information is stored in a transmission completion state. Accordingly, the controller 240 may extract the history information whose status information is not in the transmission completion state from the accumulated history information according to a predetermined condition and notify the called terminal 160.

According to the implementation method, the history information may be implemented to be deleted after the transmission to the destination terminal 160 is completed. In this case, the controller 240 may generate a call history notification message using the accumulated history information according to a predetermined condition and transmit the received call notification message to the called terminal 160.

The message transmitter 230 converts the incoming history notification message including one or more history information into a preset message form under the control of the controller 240 and transmits it. That is, the message transmitter 230 may convert the short message, the long message, and the multimedia message into any one message form and transmit the message.

The control unit 240 extracts one or more history information from the history storage unit 220 according to a preset condition, generates an incoming call history notification message including the extracted history information, and outputs the message to the message transmission unit 230.

Here, the preset condition may be a predetermined time period (30 minutes, 1 hour, etc.), a case in which a call history notification request message is received from the GLR 120, and the like. This will be described in more detail with reference to the accompanying drawings below.

3 is a flowchart illustrating a call procedure according to a call failure of a general outbound roaming terminal.

In step 310, when the GMSC 110 requests an incoming call from the originating terminal 150 to the called terminal 160, the GMSC 110 transmits a transmission routing message to the HLR 140.

In step 315, the HLR 140 transmits a roaming information request message (PRN) to a foreign exchange where the destination terminal 160 is located according to the transmission routing message.

Accordingly, in step 320, the foreign exchange checks whether the called terminal 160 is in a callable state, and if the callable state is available, assigns a roaming number (MSRN) and generates a response message (PRN ACK) including the HLR (HLR). 140).

In step 325, the HLR 140 extracts the roaming number from the response message and transmits it to the GMSC 110.

In step 330 GMSC 110 requests an incoming call to the foreign exchange using the roaming number.

In step 335, the foreign exchange attempts an incoming call to an outbound roaming terminal (ie, called terminal 160).

In step 340, the foreign exchange determines whether the outbound roaming terminal (i.e., the called terminal 160) is in an impossible state.

For example, a foreign exchange cannot receive a call when an incoming call is attempted to an outbound roaming terminal (i.e., the called terminal 160) and there is no response for a predetermined time or the outbound roaming terminal is busy or powered off. It can be judged as a state.

Accordingly, in step 345, the foreign exchange generates a call release request message (eg, ISUP_REL) and transmits it to the GMSC 110. Here, the call clearing request message includes a normal call clearing information as a preset clearing code.

In step 350, when the GMSC 110 receives a call release request message from the foreign exchange, the GMSC 110 transmits it to the calling terminal 170.

In the case of the non-receipt state, the call release request message sent by the foreign exchange does not include information on the failure of the call. For this reason, the GMSC 110 cannot analyze the specific reason for the failure of the incoming call even when the call release request message is received, and thus cannot notify the originating terminal 170 of the failure reason.

As such, when the incoming call fails, the outbound roaming terminal (that is, the called terminal 160) cannot be separately informed about the incoming call attempted by the calling terminal 170.

If the outbound roaming terminal is in a callable state as a result of the determination of step 340, in step 355, the foreign exchange performs a procedure for setting an incoming call with the outbound roaming terminal in the same manner as in the prior art. Since this is obvious to those skilled in the art, a separate description thereof will be omitted.

4 is a flowchart illustrating a method in which an outbound roaming called terminal subscribes to a call history notification service according to an embodiment of the present invention.

In step 410, the SCP 130 registers the incoming history notification service corresponding to the called terminal 160, when the incoming history notification service registration message is received from the registration device (not shown). The incoming call history notification service registration message includes incoming information. Accordingly, the SCP 130 may extract the incoming information from the received incoming history notification service registration message and register the incoming history notification service according to the incoming information.

The registration device is a device in which a mobile communication service provider is connected to a server providing a service for registering a service and receives and outputs a web page for service registration. The registration device may be a computer, a notebook, a wireless terminal, or the like.

The following procedure will be described on the assumption that a location registration message is received from an outbound roaming terminal (ie, the called terminal 160) while the incoming history notification service is registered corresponding to the called terminal 160. FIG. .

In step 415, the foreign exchange generates and sends a location registration request message to the GLR 120 in response to the location registration request from the outbound roaming terminal. Here, the location registration request message includes roaming information for the outbound roaming terminal. Roaming information may include one or more of an international mobile station identification number (IMSI), an international standard telephone number (MSISDN), and overseas network information of an outbound roaming terminal.

In step 420, the GLR 120 transmits a location registration request message to the HLR 150. Accordingly, the HLR 150 extracts roaming information from the location registration request message and registers (or updates) a location for the outbound roaming terminal using the extracted roaming information.

When the location registration procedure for the outbound roaming terminal is completed, the GLR 120 transmits roaming information for the outbound roaming terminal to the SCP 130 in step 425.

That is, the GLR 120 may receive a location registration response message from the HLR 150 and analyze the location registration response message to determine whether it is successful or failed. Accordingly, when the location registration response message is received from the HLR 150, the GLR 120 may determine that the location registration procedure is completed and transmit the roaming information to the SCP 130.

In step 430, when the roaming information is received, the SCP 130 determines whether the outbound roaming terminal corresponding to the roaming information is registered in the incoming call history notification service.

If the outbound roaming terminal is registered with the incoming history notification service, in step 435 SCP 130 sends a roaming information response message including the incoming history notification service registration information to GLR 120.

Accordingly, in step 440, the GLR 120 extracts the incoming call history notification service and the roaming information from the received roaming information response message, and registers the incoming call history notification service according to the roaming information. Accordingly, when the roaming call (ie, incoming call) to the outbound roaming terminal is requested, the GLR 120 may generate the corresponding incoming call history information and transmit it to the SCP 130.

5 is a flowchart illustrating a method of providing a call history to an outbound roaming terminal according to an embodiment of the present invention. Hereinafter, assuming that the incoming call history notification service to the outbound roaming terminal is registered in the GLR 120 and the SCP 130 will be described with emphasis on this.

In step 510 GMSC 110 receives an incoming call request message from the calling terminal 170. Here, the incoming call request message includes call information and incoming call information.

In step 515, the GMSC 110 generates a location query message corresponding to the incoming call request message and transmits the location query message to the HLR 150. Here, the location query message includes origination information and incoming information.

In step 520, when the location query message is received, the HLR 150 extracts incoming information from the location query message and determines whether or not it is roaming.

For example, the HLR 150 may extract incoming information from the location query message, and determine whether roaming by determining whether roaming information corresponding to the extracted incoming information is registered. Here, the called terminal 160 is an outbound roaming terminal.

If the called terminal 160 is roaming, in step 525, the HLR 150 extracts roaming information corresponding to the incoming information, generates a roaming call request message including the roaming information and the originating information, and sends it to the GLR 120. send.

In step 530, when the roaming call request message is received, the GLR 120 extracts the roaming information and checks whether the called terminal corresponding to the roaming information is subscribed to the incoming history notification service.

If the called terminal is subscribed to the call history notification service, in step 535, the GLR 120 generates call history information including roaming information and call origination information and transmits it to the SCP 130.

In addition, in step 535, the GLR 120 requests roaming calls to the foreign exchange using the roaming information.

In step 540, when the incoming call history information is received, the SCP 130 stores the incoming call history information and the time information when the incoming call history information is received as history information.

Here, SCP 130 may further store the transmission status information in the history information. The transmission state information may be any one of transmission completion information and a transmission waiting state. Of course, depending on the implementation method, the transmission status information may be set as flag information indicating whether the transmission is complete.

If the history information further includes the transmission status information, the SCP 130 determines that the transmission status information is set to the transmission completion information, and the transmission information is set to the remaining transmission standby state except that the transmission information is completed. Unrecorded) history information may be extracted and transmitted to a called terminal (ie, an outbound roaming terminal).

Hereinafter, assuming that the transmission state information is not included in the history information, the following procedure will be described with emphasis on this.

In step 545, SCP 130 extracts the history information set corresponding to the outbound roaming terminal according to a predetermined period.

In step 550, SCP 130 converts the extracted history information into a preset message form and transmits it to the outbound roaming terminal.

More specifically, SCP 130 generates a message (hereinafter referred to as an incoming call history notification message) corresponding to the type of the preset message to the extracted history information and transmits it to the message center.

Accordingly, the message center may transmit the received incoming call history notification message to the outbound roaming terminal.

6 is a diagram illustrating an incoming history notification message received by an outbound roaming terminal according to an embodiment of the present invention.

As shown in FIG. 6, the incoming call history notification message may include time information and origination information. In this specification, for convenience of understanding and explanation, it is assumed that the incoming call history notification message is provided to the outbound roaming terminal in the form of a short message. However, the incoming call history notification message may be provided to the outbound roaming terminal in the form of various messages such as a long message or a multimedia message in addition to the short message.

It will be apparent to those skilled in the art that various modifications and variations can be made in the present invention without departing from the spirit or scope of the invention as defined in the appended claims. It will be understood that the invention may be varied and varied without departing from the scope of the invention.

1 is a block diagram schematically illustrating a configuration of a mobile communication system according to an embodiment of the present invention.

2 is a block diagram illustrating an internal configuration of a call control device according to an embodiment of the present invention.

3 is a flowchart illustrating a call procedure according to a call failure of a general outbound roaming terminal.

4 is a flowchart illustrating a method of subscribing to an incoming call history notification service by an outbound roaming called terminal according to an embodiment of the present invention;

5 is a flowchart illustrating a method of providing a call history to an outbound roaming terminal according to an embodiment of the present invention.

6 is a diagram illustrating an incoming history notification message received by an outbound roaming terminal according to an embodiment of the present invention.

Claims (8)

In the system for notifying the incoming call history to the outbound roaming terminal, Store service registration information for the outbound roaming terminal, and analyze the service registration information when the incoming call is requested to the outbound roaming terminal and the outbound roaming terminal is registered in the incoming call history notification service; A gateway location register that generates and transmits incoming call history information; Storing the incoming call history information, the time information at which the incoming history information was received, and the transmission state information as history information, and analyzing the transmission state information to extract history information of which the transmission state information is not transmitted, and extracting the extracted A call control device for generating and transmitting a call history notification message including history information; And And a message center for transmitting the incoming history notification message to the outbound roaming terminal. The method according to claim 1, The gateway location register further stores communication state information of the outbound roaming terminal, and when the communication state information of the outbound roaming terminal is changed from a non-receivable state to a callable state, generates a call history notification request message. Transmit to the call control device, And the call control device generates and transmits the call history notification message when the call history notification request message is received. The method according to claim 1 or 2, The incoming call includes outgoing information and incoming information, And the gateway location register extracts the outgoing information and the incoming information from the incoming call and generates the incoming history information including the extracted outgoing information and the incoming information. delete In the method for notifying the incoming call history to the outbound roaming terminal, Generating, by the gateway location register when the outbound roaming terminal is registered with the incoming history notification service when the outbound roaming terminal is registered in the incoming history notification service when the outbound roaming terminal requests the incoming call to the outbound roaming terminal; ; Storing, by the call control device, the reception time history information, the reception history information, and the transmission status information as history information; Analyzing, by the call control device, the transmission state information of each history information to extract history information of which the transmission state information is not transmitted; Generating and transmitting the incoming call history notification message including the extracted history information by the call control device; And And sending, by the message transmission center, the call history notification message to the outbound roaming terminal. 6. The method of claim 5, Generating and transmitting the incoming call history information, The gateway location register extracting outgoing information and incoming information from the incoming call; And And generating and transmitting the incoming call history information including the originating information and the incoming information extracted by the gateway location register. The method according to claim 5 or 6, Generating and transmitting the incoming call history notification message may include: The call control device generates and transmits the incoming history notification message when the incoming history notification request message is received from the gateway location register. The gateway location register stores communication state information of the outbound roaming terminal, and when the communication state information of the outbound roaming terminal is changed from a non-receivable state to a callable state, generates a call history notification request message. Incoming call history notification method characterized in that the transmission to the call control device. delete

Images