KR100920891B1 - System for Providing Incomplete Calling Information for Called Parties - Google Patents

Abstract

The present invention relates to a system for providing call origination information in a wireless communication network, wherein the system (1) transmits a catch call request message when a call call data occurs because the calling subscriber attempts to make a call to the called subscriber but the call is not established. And (2) if the first catch call request message is received from the HLR, it is determined that this is a duplicate catch call request message, and if it is not a duplicate catch call request message, it is transmitted and the duplicate catch call request message is In this case, after storing the first catch call request message and waiting, the second calling party may receive the second catch call request message for the second catch call data generated because the call was not established. When the catch call request to transmit the last first catch call request message of the duplicate catch call request message When receiving the service server, and (3) requests the transmission of a call message from the catch the catch call service server and a short message service center for transmitting an outgoing call information to the called party as a short message. According to the present invention, since the call subscriber information is provided to the called party only for the final catch call data among the duplicated catch call data generated from the same calling party, the called party does not have to receive several short messages that are duplicated for a short time. Detailed information about the number and time of call attempts can be provided.

Incomplete call data, short message, duplicate call attempt

Description

System for Providing Incomplete Calling Information for Called Parties}

1 is a block diagram showing the overall configuration of a wireless network that implements a call origination information providing system according to the present invention.

2 is a view for explaining an example of a catch call service call processing process according to the call origination information providing system of the present invention.

3 is a flowchart of a catch call service call processing process according to a call origination information providing system of the present invention;

The present invention relates to a system for providing call origination information in a wireless communication network. More particularly, the present invention relates to a call origination information providing system capable of providing detailed information on a duplicate call attempt for which a call is not established.

The wireless telecommunication supplementary service provided by the applicant includes a "catch call service" that provides the called subscriber with call origination information of the calling subscriber when the call is attempted but the call is not established. This catch-call service attempts to make a call attempt to this subscriber if the catch-call subscriber's telephone is unreachable (for example, if the telephone is powered off, if the telephone is in a shadowed area, or if it is busy or unanswered). If incomplete call data (i.e. catch call data) occurs due to incomplete completion, when the subscriber's telephone is available to be called later, past call origination information can be checked through the Short Message Service (SMS). Say service. SMS notification of catch call data occurs in four cases:

(1) If Call Forwarding Unconditional (CFU), Voice Mail Unconditional (VMU), and Do Not Disturb (DND) services are enabled for the called party,

(2) when the state of the telephone terminal of the called subscriber is power off,

(3) if the called party is busy

(4) The called party did not answer the phone or left the coverage.

As described above, a technique of transmitting incomplete call data to a called subscriber in a short message has been described in various conventional documents.

For example, Patent No. 10-0374964 No. 10-0374964, registered on February 21, 2003, has a separate system for processing incomplete call data and has a separate system for processing incomplete call data. It is determined whether the short message can be received and transmits the incomplete call data to the short message service center only when the short message can be received. In addition, Japanese Patent Laid-Open No. 6-165247, published on June 10, 1994, indicates that the mobile terminal is located outside the service area of the base station or when the mobile terminal is turned off. Notifying the caller of the unresponsive state of the terminal and simultaneously storing the caller's telephone number and the incoming time in the storage means, and when the mobile terminal returns to the available state, the caller's telephone number and the incoming time are initiated on the mobile terminal. have.

On the other hand, Japanese Patent Laid-Open Publication No. 2000-32559 published on January 28, 2000, when the called subscriber attempts to make a call when the mobile communication terminal is in a disabled state, an incoming call data is generated. The present invention relates to a system for automatically notifying a mobile terminal of a called subscriber of information about an incomplete call received when the subscriber's mobile terminal returns to a call enabled state. In the prior art, when an incomplete call occurs due to an inability of a caller or an out of service area, the receiving mobile station transmits the calling party's telephone number, incoming call time, and the total number of incoming calls associated with the incomplete call. It stores in the information management table and notifies the receiving mobile terminal of incomplete call data in the order of callers with the highest number of incoming calls.

Such a conventional incomplete call notification system or method has an HLR interworking function capable of handling an incomplete call occurrence message transmitted from a network such as MSC, HLR, an SMSC interworking function for transmitting an incomplete call data transmission request message to the SMSC, and duplicated. Duplicate message check timer technology for identifying message and sending message only once, database processing function, function to edit incomplete call data into text, statistics processing function, and search for incomplete call data history through web.

However, in the conventional incomplete call notification system, when the incomplete call notification request message is transmitted in the network, the SMSC requests the SMSC to transmit the message in almost real time, and thus cannot express the last call attempt time processing and the number of call attempts of the calling subscriber. In addition, the conventional incomplete call notification system has a problem that it does not provide detailed information about the call of the called party, and since the duplicate message is determined by the timer, when a large number of duplicate catch calls occur within a certain time, the called party Had the inconvenience of receiving a large number of catch call messages at once.

An object of the present invention is to provide the called party with detailed information on the call attempt of the originating subscriber that generated the incomplete call data when incomplete call data occurs.

Another object of the present invention is to provide a system for providing a call origination information for incomplete call data without degrading the system and eliminating the inconvenience of the called subscriber by not judging whether the catch call overlaps with a timer.

The call origination information providing system according to the present invention includes (1) an HLR that transmits a catch call request message when the calling subscriber attempts to make a call to the called subscriber but the call is not established and the catch call data occurs. 1, if the catch call request message is received, it is determined whether it is a duplicate catch call request message, and if it is not a duplicate catch call request message, the transmission of the first catch call message is requested, and in the case of the duplicate catch call request message, the first When the second call subscriber receives the second catch call request message for the second catch call data generated because the second calling subscriber attempts to make a call to the called subscriber but the call is not established, the duplicate call waiting is stored and stored. A catch requesting the transmission of the first catch call message based on the last first catch call request message among the catch call request messages. And a (3) short message service center for transmitting the outgoing call information to the called subscriber in a short message when a request for transmission of the catch call message is received from the catch call service server.

Embodiment

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

1 is a block diagram showing the overall configuration of a wireless network implemented in a call origination information providing system according to the present invention.

As shown in FIG. 1, the wireless network is a network for communication between the calling subscriber 10 and the called subscriber 30, and includes an originating mobile switching center (OMSC) and a home location register 20 (HLR: Home Location). Register), receiving switching center (25, tMSC: terminating MSC), SS7 network (35, Signaling System No. 7 Network), catch call service server (40, CCS: Catch Call Server), IP network (45), customer service and A billing center 50, a customer service and billing system (CS), a short message service center (SMSC 60), a customer management device 65, a customer relation management (CRM), and a temporary database 70 are included. .

In FIG. 1, the HLR 20 may include 2G-HLR for CDMA network subscribers and 3G-HLR for WCDMA network subscribers. The CS 50 registers, inquires, changes, and deletes catch call subscriber information to the CCS 40. The CRM 65 receives catch call generation information received from the CCS 40 and history information on processing results. Is provided to the called party in a web environment and / or a WAP environment.

The catch call service server 40 (CS) is an interface for transmitting SS7 messages to an application program, a controller that manages the entire catch call service call processing scenario, and formats and transmits and receives an SMSC 60 interworking message for catch call text data processing. Process, process of formatting and sending and receiving CRM 65 interworking message, process of managing subscriber profile, formatting and sending and receiving CS 50 interworking message, process in charge of retransmission of message failed to interwork with CRM 65, catch call During the call processing, the database access management process required to store duplicate catch call data by the same originating subscriber and send it to the SMSC 60, the interface process for performing operator command (MML), and CCS Operational management processes, such as system performance, failures, statistics, status, and configuration The child interface may be included as an internal component.

If the calling subscriber 10 attempts to make a call to the called subscriber 30, but the call fails to be established and catch call data is generated in the four cases described above, the HLR 20 triggers catch call generation information. To the catch call service server 40 through the SS7 network 35. The catch call service server 40 processes the catch call service call in association with the HLR 20, tMSC 25, CS 50, SMSC 60, and CRM 65. Here, 'Catch Call Service Call Processing' refers to the MAP (Mobile Application Part) message (ie, "information directive") triggered by the HLR 20 and interworked with the CS 50, the SMSC 60, the CRM 65, and the like. Means a series of procedures for providing call origination information to the called party 30 and allowing the subscriber 30 to confirm the call origination information through the CRM 65.

As shown in FIG. 1, the catch call service server 40 of the present invention includes an HLR 20, an oMSC 15, a tMSC 25, a CS 50, an SMSC 60, a CRM 65, and a DB 70. And a separate system. The catch call service server 40 notifies the call subscriber information to the called subscriber 30 in a short message and transmits the occurrence information of the catch call and the history information on the processing result to the CRM 65. The subscriber profile managed by the catch call service server 40 for the catch call service includes, for example, a terminal identification number (MSID), the subscriber's telephone number (MDN), whether the catch call service is activated, the latest catch call message originating phone number, and a duplicate. It may include data such as the number of catch calls.

According to the present invention, when the catch call server 40 sends a catch call message transmission request to the SMSC 60, the catch call server 40 does not use the timer to determine the duplicate catch call of the first calling subscriber and does not apply to the duplicate catch call of the first calling subscriber. When the catch call occurs from the second calling subscriber which is another calling subscriber, the last catch call data (i.e., the latest catch call data) among the duplicate catch call data of the first calling subscriber is sent. It adds the ability to count the number of call attempts for catch calls. Unlike conventional incomplete call data notification system, call processing and database structure have been greatly improved.

2 is a view illustrating a catch call service call processing process according to a call origination information providing system of the present invention.

In FIG. 2, the calling subscribers are called A and C, respectively, and they try to make a call to the called party B, but the call is not established.

First, A tried to talk to B at 'X: XX', but B was in an unreachable state.After 1 minute, at 'X: XX + 1', the same calling party A was again sent to B, the same called party. A call was made but no call was made, and A no longer tried to call B. That is, duplicate catch call data for the called party B is generated from the calling party A. Meanwhile, another calling party C tried to talk to the same called party B at 'Y: YY' but no call was made. 'Y hour YY minute' is later than 'X hour XX + 1 minute'. In this case, the catch call service server 40 is duplicated when A attempts to call B at 'X hour XX + 1 minute' before the call call by the calling party C occurs, 'Y hour YY minute'. Instead of requesting transmission of the catch call data to the SMSC 60, a catch call by the calling party C must occur before the final call call data by the calling party A (i.e., catch call data generated at 'XX hour XX + 1 minute'). Request the SMSC 60 to transmit.

At this time, the catch call message received from the SMSC 60 and delivered to the called party B includes the calling party's phone number, the time when the calling party last tried to call (or the time when the last catch call data occurred), and A called. Data about the number of attempts is included.

On the other hand, the catch call data generated when A attempts to make a call to B at time 'X hour XX' is not the duplicate catch call data, but the catch call data generated by A first, so that the catch call service server 40 receives the SMSC (60). Request a transfer. Similarly, the first catch call data of C generated at 'Y hour YY minute' is also transmitted from the catch call service server 40 to the SMSC 60. Although not shown in FIG. 2, if a duplicate catch call is generated by the calling party C after 'Y hour YY', catching by another calling party (including A) is performed similarly to the duplicate catch call by A described above. The call call service server 40 makes a request for transmission to the SMSC 60 only when there is a call.

In the present invention, if the same caller generates two or more catch call data with respect to the same receiver, all of them are determined as duplicate catch call data. It does not need to be configured like a timer. That is, the present invention does not use the same timer as the conventional method because it does not check whether there is a call attempt of the same calling party within a predetermined time from the first catch call data when determining whether it is duplicate catch call data. Therefore, when a large number of duplicate catch call data is generated (eg, 50 times in 30 minutes) beyond the predetermined time (eg, 5 minutes) set as a timer, a large number of catch call data are simultaneously transmitted to the SMSC 60 or a large number of catches. The problem that the call message is sent to the called party 30 can also be solved.

In the present invention, in order to transmit the catch call message only for the last catch call data among the duplicate catch call data, storing the duplicate catch call data generated from the same calling subscriber in a database and confirming the stored data (that is, duplicate call call events Division work) is required.

To this end, the catch call server 40 interworks with the database 70 as shown in FIG. In the present invention, unlike a general database that simply stores data, the database 70 temporarily inserts catch call data into the database whenever a call processing occurs, that is, whenever a catch call event occurs, and a duplicate message is inserted. When it occurs, it has a temporary database structure that searches the database and deletes the database when the transmission of the SMS message (catch call message) is completed. The reason for this configuration of the database 70 is to solve the system degradation problem that can occur when there are a large number of subscribers of the catch call service (e.g., more than 1 million). For example, if the number of subscribers that a conventional catch call server can handle is one million, in the present invention, since duplicate messages must always be checked, the temporary database structure is not a method of searching all data for each million subscribers. Therefore, the catch call data can be temporarily stored, retrieved, updated, and deleted only when an event occurs, thereby preventing the performance of the catch call server.

3 is a flowchart illustrating a catch call service call processing process according to the present invention.

The originating exchange 15 receiving the originating call of the originating subscriber 10 sends the location request message of the called party to the HLR 20 of the called party, and the HLR 20 receives the originating call 10 A routing request message is sent to the client, and a receipt confirmation message (routing request_ack, location request_ack) is returned. When the HLR 20 has information indicating that the called party is inactive, the HLR 20 sends a catch call request message (Information Directive) to the CCS 40.

On the other hand, when the HLR 20 does not have information indicating that the called party is inactive, the originating exchange 15 sends an initial address message to the receiving exchange 25, and the receiving exchange 25 Paging the called subscriber 30. If no response is received from the called subscriber as a result of the call, the receiving switching center 25 sends a Transfer To Number Request (TTNR) message to the calling switching center 15, and the HLR 20 sends a catch call request message to the CCS 40. send.

The catch call request message sent by the HLR 20 to the CCS 40 includes a calling party number string corresponding to the MSID (Mobile Station Identifier) of the called party, the Mobile Directory Number (MDN) of the called party, and the telephone number of the calling party. 1) Alternatively, data such as an electronic serial number (ESN) of the calling subscriber and a catch call data generation time is included.

If the catch call server 40 receives the catch call request message by the first originating subscriber from the HLR 20, if it is not a duplicate request message, the catch call server 40 immediately requests the SMSC 60 to transmit the request. If the catch call request message is a duplicate request message, it does not immediately request the catch call message transmission to the SMSC 60 and waits for catch call data generated by another calling party (second calling party). Catch call data in the standby state is stored in the temporary database 70 described above. When duplicate catch call data for the first originating subscriber occurs before the catch call data by the second originating subscriber occurs, the secondary catch call request message is transmitted from the HLR 20 to the CCS 40. The secondary catch call request message is also stored in the database 70 and waits until catch call data by the second originating subscriber occurs. When catch call data by the second originating subscriber occurs, the CCS 40 searches the database 70 to retrieve a final catch call request message by the first originating subscriber (second catch call request message in the example of FIG. 3). Request transmission of the catch call message to the SMSC 60 on the basis.

When the CCS 40 requests the SMSC 60 to send a catch call message, the destination address, originating address, callback number, SMS text, time of the last catch call, and the number of duplicate call attempts by the calling subscriber It transmits data such as SMS message identifier, status report indicator, etc. assigned by CCS.

Upon receiving the request for catch call message transmission, the SMSC 60 requests the destination exchange station 25 to send a catch call message (marked as 'catch call mail' in FIG. 3) to the called party 30, and the destination exchange station ( 25) a response signal (catch call mail reception response).

On the other hand, in the above-described example, if the called party returns to the callable state after the duplicate catch call data by the first calling party occurs, the first calling party regardless of whether or not the catch call data is generated by the second calling party. The catch call service server 40 requests the SMSC 60 to send the last catch call data of the SMSC 60.

Although specific embodiments of the present invention have been described with reference to the drawings, this is intended to be easily understood by those skilled in the art and is not intended to limit the technical scope of the present invention. Therefore, the technical scope of the present invention is determined by the matters described in the claims, and the embodiments described with reference to the drawings may be modified or modified as much as possible within the technical spirit and scope of the present invention.

According to the present invention, since it is not determined whether the duplicate catch call is based on the time set by the timer, it is possible to eliminate the inconvenience that the duplicate catch call data generated during the time exceeding the timer setting time is transmitted to the called subscriber at once. Can be.

In addition, in the present invention, since the call originating information is provided to the called party only for the last catch call data among the duplicated catch call data generated from the same calling party, the called party does not need to receive multiple short messages that are duplicated for a short time, and the call of the calling party is called. There is an effect that can be provided with detailed information about the number and time of attempts.

In addition, the present invention can provide a high-quality service to a large number of subscribers without incurring the performance degradation of the system that provides the call origination information by using the temporary database technology, and also prevents the phenomenon that numerous short messages are delivered to the SMSC at once. can do.

Claims (7)

Outgoing call information providing system, An HLR that transmits a first catch call request message when a first catch call data occurs because a first call subscriber attempts to make a call to a called subscriber but the call is not established; In case of receiving the first catch call request message from the HLR, it is determined whether this is a duplicate catch call request message, and if it is not a duplicate catch call request message, the transmission of the first catch call message is requested. In this case, after storing the first catch call request message and waiting, the second calling party may receive the second catch call request message for the second catch call data generated because the call was not established. A catch call service server requesting transmission of a first catch call message based on a final first catch call request message among the duplicate catch call request messages; And a short message service center for transmitting the outgoing call information to the called subscriber as a short message when receiving the request for transmission of the first catch call message from the catch call service server. In claim 1, The catch call service server transmits the first catch call message with the number of occurrences of the catch call data generated from the first calling subscriber when duplicate catch call data is generated from the first calling subscriber before receiving the second catch call request message from the HLR. Call shortening information providing system comprising a request to the short message service center in the request. delete The method of claim 1 or 2, When the catch call service server receives the duplicate first catch call request message from the HLR and the called party returns to the callable state, the catch call service server transmits the first catch call message regardless of whether or not the second catch call request message is transmitted. Call origination information providing system, characterized in that to the short message service center. The method of claim 1 or 2, Further comprising a temporary database for storing the first catch call request message, The catch call service server searches for the first catch call data stored in the temporary database to determine whether the catch call event is duplicated, and if the request for transmitting the second catch call message is sent to the short message service center, Call origination information providing system, characterized in that for deleting the stored first catch call data. In claim 2, Information that the catch call service server requests the short message service center to transmit the first catch call message includes a destination address, an originating address, a callback number, an SMS text, a final catch call generation time, Outgoing call information providing system, characterized in that the number of duplicate call attempt data of the calling subscriber is included. The method of claim 1 or 2, The catch call service server includes (A) an interface for delivering an SS7 message to an application program, (B) a controller that manages the entire catch call service call processing scenario, and an interworking message with the short message service center for catch call text data processing. And a database access management process necessary to determine whether to store and catch duplicate catch call data by the same originating subscriber during catch call call processing and send it to the short message service center during the catch call call processing. Call information provision system.

Images