KR100734740B1 - Processing Method of Destination Information Reporting System Using Intelligent Network - Google Patents

Abstract

The present invention relates to a processing method of an incoming information notification system for notifying incoming call information (call inflow notification) to a called party's terminal (WEB or WAP capable terminal) and a system for implementing the method.

The present invention provides a processing method of an incoming information notification system in a communication system.

Setting, by the subscriber, a call transfer condition for transferring a call when the called terminal is not answered or busy, and a receiving information receiving terminal at the time of transfer; When any caller attempts to call the called terminal, the intelligent network notifying the called information receiving terminal of the incoming call to the called terminal; An incoming attempt step of the intelligent network attempting to receive the called terminal; And a call forwarding notification step of notifying, by the intelligent network, that the call forwarding information receiving terminal is forwarded when the intelligent network receives that the incoming call attempt is not answered or busy.

The present invention as described above, by using the incoming trigger (Trigger) method used in the existing communication network to notify the incoming information to the recipient's Web (WEB) or WAP (WAP) / US (ME) program of the recipient By doing so, it is possible to use the incoming trigger service more easily and efficiently.

 Incoming trigger, service controller, incoming information

Description

Processing Method of Destination Information Reporting System Using Intelligent Network

1 is an exemplary configuration diagram of an incoming call notification system to which the present invention is applied.

Figure 2 is a detailed flowchart of an embodiment of a call transfer process when the called party is unanswered in the processing method of the incoming information notification system according to the present invention.

3 is a detailed flowchart illustrating an exemplary embodiment of a call transfer process when a called party is busy in a method of processing an incoming information notification system according to the present invention.

Figure 4 is a detailed flowchart illustrating an embodiment of the call conversion process unconditionally among the processing method of the incoming information notification system according to the present invention.

FIG. 5 is a detailed flowchart illustrating an embodiment of a method of connecting a voice (/ video) mailbox unconditionally among processing methods of an incoming information notification system according to the present invention; FIG.

6A and 6B are detailed flowcharts illustrating an embodiment of a call termination process when a called party is non-responsive in a method of processing an incoming information notification system according to the present invention.

7A and 7B are detailed flowcharts illustrating an embodiment of a call termination process when a called party is busy in a method of processing an incoming information notification system according to the present invention;

8 is a detailed flowchart illustrating an embodiment of an unconditional call termination process in a method of processing an incoming information notification system according to the present invention;

The present invention relates to a processing method of an incoming information notification system.

More specifically, the present invention uses the incoming call trigger when the incoming call information (call inflow notification) is connected to the recipient's Internet (hereinafter referred to as incoming information receiving terminal) (PC, notebook, PDA, portable Internet terminal) The present invention relates to a processing method of an incoming information notification system which is notified of, and a system for realizing the method.

In the present invention, the trigger refers to an operation that is automatically performed when the database DB meets a predetermined condition.

As telephones become popular, they are used in various environments. In particular, with the development of wireless communication, many people use mobile phones (wireless communication terminals), and in the home, wireless phones are popularized, and telephones are now available at anytime and anywhere, not only at home.

However, the present Caller ID (CID) service that is currently in service collects the calling number from the calling exchange through the inter-station signaling method for the incoming call, and transmits the calling number through the subscriber line before the subscriber responds. It is displayed on the display device of the terminal.

Therefore, the calling party number information is displayed only on the display device of the wired / wireless communication terminal subscribed to the CID service, and especially, when there is a subscriber in a different (distant) place from the wireless communication terminal subscribed to the CID service, it cannot be immediately confirmed. There was a problem. For example, if you leave the company at home with a caller ID information displayed on a wireless communication terminal subscribed to a CID service that you have left at work, or if you leave your wireless communication terminal (mobile phone) at home, the company subscribes to your home CID service. There was no way to know the calling number information displayed on the terminal.

In addition, when looking at the current VMS service that is operated on the server side, the user can move the mobile terminal to a specific place and receive the call as if the user leaves the mobile terminal at home or at work. If there is no ringing signal (about 5 to 6 times) ringing at the called terminal, it automatically switches to voicemail (VMS) mode when the incoming call is not received. Instead, the caller may try again because he or she does not know the current situation of the called party (such as if he or she has left the terminal or if he does not recognize the incoming call), but should be satisfied with leaving his or her information unsuccessful in the end. do.

Of course, if the user leaves the mobile communication terminal at home or go to work at work, such as when leaving the mobile communication terminal in a specific place may receive a call using a call forwarding service, but the call In the case of using the forwarding service, while receiving a call by setting up call forwarding to a user-specific terminal, a call cannot be received by the original number of the terminal that has set up call forwarding, causing other inconvenience. A wireless communication terminal or a wired telephone that is subject to call forwarding is required, and call forwarding setting is required every time.

Therefore, in the current technical field, there is an urgent need for a method of processing an incoming call notification system that notifies incoming call information (call inflow notification) to a called party's incoming information receiving terminal (PC, laptop, PDA, portable Internet terminal, etc.). do.

The present invention has been proposed to meet the above requirements, and the incoming call information (call inflow notification) to the incoming call information receiving terminal (PC, notebook, PDA, portable Internet terminal, etc.) connected to the Internet of the called party It is an object of the present invention to provide a processing method of an information notification system and a system for realizing the method.

In the present invention, to receive the incoming information when the incoming call is connected to the Internet of the called party using the incoming trigger (Trigger) method used in the existing communication network in order to use the incoming trigger (Trigger) service more easily and efficiently By notifying the program of ',' it defines the 'incoming information notification service' method that adds an additional method to the incoming trigger method used in the communication network.

1 is an exemplary configuration diagram of an incoming call notification system to which the present invention is applied.

The 'incoming information notification service' is a service provider (e.g., a messenger program) installed on an incoming information receiving terminal (a terminal connected to the Internet, for example, a PC, a laptop, a PDA, a portable Internet terminal, etc.) or a wired / wireless Internet. After accessing the wired / wireless internet server, the subscriber can use it after the proper sign-up procedure according to the access guide screen of the wired / wireless internet server. And call transfer / end. In addition to wired and wireless Internet access such as WEB or WAP, service registration based on ARS connection will be possible.

That is, the user can register and use the 'incoming information notification service' through a separate subscription procedure, and use a separate program (for example, a PC, a laptop, a PDA, a portable Internet terminal, etc.) For example, a messenger program) can be installed or used using a wired / wireless internet.

'Incoming information notification service' is a program (e.g., a messenger program) installed in a subscriber's incoming information receiving terminal (for example, PC, laptop, PDA, mobile Internet terminal, etc.) according to incoming call setting conditions among information set by the recipient. It is a service that notifies the relevant information and transfers or terminates an incoming call.

The 'incoming information notification service' may start a service in a different manner according to the operator's network (wireless communication network, wired communication network, VoIP network, BcN network, etc.), and is equipped with a service controller (Service Control Point). It can be used by all operators of wired / wireless networks. At this time, all the exchanges of the network operator (for example, mobile communication exchange (MSC), service exchange (SSP), etc.), soft switch (Soft Switch) should support the incoming trigger. Thus, the incoming trigger condition of the subscriber is initiated by the incoming information of the exchange or soft switch.

The basic information of the subscriber is a subscriber's mobile phone number, the subscriber's home phone number, and the subscriber's company phone number. These numbers can be registered after performing authentication at the time of registration. In this case, the registered information may be modified, and may be modified after authentication.

Hereinafter, the call destination terminals 11, 21, 22, and 31 for the 'call destination information service' include a wired / wireless telephone capable of voice communication, a POTS / xDSL terminal, a mobile communication terminal such as a cellular phone or a PCS phone, an IMT- Next generation mobile communication terminals such as 2000 (International Mobile Telecommunication), UMTS (Universal Mobile Telecommunication Service), personal digital assistant (PDA), VoIP terminal (SIP terminal, Soft Phone, H.323 terminal, etc.) As far as possible, voice communication of the receiving terminal is revealed that it is not subject to the type of the target network (wired communication network, wireless communication network, VoIP network, NGN network, BcN network, etc.) 10-30.

In addition, the incoming information receiving terminal 53 may be a mobile communication terminal such as a PC, a notebook computer, a cellular phone, or a personal communication service (PCS) phone, a smart phone, an international mobile telecommunication (IMT-2000), a universal mobile telecommunication service (UMTS), or the like. The next generation mobile communication terminal, personal digital assistant (PDA), wireless Internet (WAP / ME) terminal, wired Internet (WEB) terminal, portable Internet terminal, and the like, as long as data communication, the applicable network (wired) Communication network, wireless communication network, VoIP network, NGN network, BcN network, etc.

Now, the function of each component of the called information notification system for the called information notification service will be described.

The service switch point (SSP) 23 switches the call resource management and service of the terminals 21 of the wired communication network 20.

The mobile switching center (MSC) 12 switches call resource management and services of the terminals 11 of the wireless communication network 10.

The service controller 50 (SCP / AS: Service Control Point / Application Server) 50 controls the intelligent network service and manages the information of the intelligent network service subscriber to provide the exchanges 12 and 23 with information necessary for call processing. . In addition, by interlocking with the network resources of the communication network and the Internet through its own interlocking standards to provide a converged / combined application service with various environments. In addition, in a VoIP (Voice over Internet Protocol) network, in conjunction with the soft switch 32, various additional services are provided through call and media processing.

The Intelligent Peripheral (IP) (16, 25) manages special resources such as tones, announcements, conference call bridge management, and text-to-speech (TTS) required for service logic control. Process. That is, the intelligent network service user / subscriber performs additional intelligent network services using voice or text.

The home location register (HLR) 13 performs location registration of the wireless communication terminals 11 and manages state information of the terminals 11 and knows an accurate location. That is, as a database management system that stores and manages subscriber parameters and location information for all the terminals 11 registered in its own area, it manages important data such as access capability, basic services, and additional services of the terminal 11. It performs the routing function of the called subscriber.

The Short Message Service Center (SMSC) 15 is connected to the mobile communication switch 12 and plays a key role in SMS processing, sets SMS parameters, and provides a communication service identifier (TI: Teleservice Identifier) of an input signal. ) And the Destination Address are interpreted and transmitted to the network element.

The POTS / xDSL 22 is a device and a terminal capable of providing a basic voice service without additional functions such as circuit control or feature compensation for data transmission through an xDSL network.

Signaling gateway (33) is a device that serves as a gateway for implementing the existing public telephone network (PSTN) service on the next-generation communication network (NGN), converting the signal of the signal relay switch (SS7) to the IP signal of the NGN Solution to the soft switch (32).

An access gateway 35 is a device required to connect a general telephone user of a wired / wireless communication network such as a PSTN to a packet network (VoIP or VoATM), and converts voice data from the general telephone to be transmitted to the packet network.

The trunk gateway 34 is a device for interworking a public telephone network (PSTN) and a packet network (VoIP or VoATM) and transmits a large amount of data generated from the public telephone network to the packet network.

Soft switch 32, also called a media gateway controller, is a device that performs an interworking function between a packet network and an existing wired / wireless communication network. The soft switch 32 transmits signals between heterogeneous networks and performs call processing. 35) or media gateways such as trunk gateway 34 and signal gateway 33.

The media server 37 is a system for processing special resources such as Tone, Announcement, Conference Call Bridge Management, TTS, etc. which are required in the service logic control process. However, the difference from the IP 25 for the existing PSTN is that it provides a special resource required for packet-based service logic control in conjunction with the soft switch 32 of the NGN. In addition, it provides special resources such as video stream required for NGN's multimedia-based supplementary service in the future.

Now, let's take a closer look at the 'Incoming Information Notification Service' procedure.

First, the 'incoming information notification service' may be largely classified into a call forwarding setting service and a call termination service.

The forwarding setup service includes a call forwarding service scenario in which there is no answer when a call is attempted and a call is forwarded to a registered forwarding number when a "call forward if no answer" flag is set for the called party. (Refer to FIG. 2 below), 'Call Forwarding When Calling', which is busy when calling and attempts to transfer the call to the registered call forwarding number when the "Call Forward When Busy" flag is set for the called party. Scenario '(see FIG. 3 below),' unconditional call forwarding service scenario 'in which a call is transferred to a forwarding number registered when an incoming call is attempted to a subscriber when the "unconditional call forwarding" flag is set for the called party. (Refer to FIG. 4 below), when the incoming call is in a call and the "voice (/ video) mailbox switching when busy" flag is set for the called subscriber, Voice / Video Mailbox Switching Service Scenario When Calling to Connect to Voice (/ Video) Mailbox or Save Message, and No Answer on Incoming Attempt, and "Voice When Not Answered" ) "Switch mailbox" to the registered voice (/ video) mailbox when the "Flag" is set, or to "call the voice (/ video) mailbox switching service scenario when no response is performed." When the "Unconditional voice (/ video) privacy switching" flag (Flag) is set, the "unconditional voice (/ video) that connects to the registered voice (/ video) mailbox or performs a call processing to store a message when an incoming call is attempted to the subscriber ) Mailbox switching service scenario '(see FIG. 5 below).

In addition, the call termination service, if the call is not answered when the incoming attempt and the "end call if no response" flag (flag) is set for the called subscriber 'if the call is not answered to terminate the call after appropriate announcement (Play) End Service Scenario '(see FIG. 6 below), when the incoming call is attempted and the call termination is set for the called subscriber, the call is terminated after the appropriate announcement. 'Call Termination Service Scenario in Call' (refer to FIG. 7 below), and when the "Unconditional Call Termination" flag is set for the called party, the call is sent after the appropriate announcement is played. End condition "unconditional call termination service scenario" (see Figure 8 below) and the like.

There are a number of ways to be notified to the subscriber of the 'information notification service', and the subscriber may be notified of the incoming call to the notification window of the user program UI when the incoming call is attempted (notifying the notification window when the call is received), or the subscriber is called. At the time of the attempt, the user is informed that the call is received by the ringtone set in the user program UI (notification of the ringtone when the call is received), or the subscriber is notified of the received content by the user program UI when receiving a new voice (/ video) message (new voice ( / Video) message reception notification), if the subscriber set the "end call" If the subscriber is notified of the termination of the call to the user program UI (call blocking notification), or the subscriber set the "call forward" There is a method (notification of call forwarding) that informs the subscriber of the contents of the call transfer when the call is attempted.

In addition, the service subscriber can easily change the called number by simply changing the configuration file of the user program UI, and if the user program UI is not used, the call transfer and call termination is automatically performed according to the subscriber's information. It is possible to set the operation to handle the call (operation setting when away) and the operation setting to handle the call transfer and call termination according to the subscriber's information automatically set when the user program UI is logged off. (Operation setting when user program UI LogOff).

Now, the procedure of 'incoming information notification service' will be described in more detail. However, the service may be started in different manners according to the operator's network. Hereinafter, for convenience of description, the mobile communication switch (MSC) 12 and the service controller (SCP) (AS ( 50) and the call processing procedure between the special resource handler (IP) 16, but the configuration thereof can be replaced and changed with other components of the same function according to the service network. Reveal. For example, the service controller of the present invention can be replaced by various intelligent networks (for example, intelligent networks using a parlay application server) having similar functions.

2 is a detailed flowchart illustrating a call transfer process when a called party is non-responsive in the processing method of the called party information notification system according to the present invention. This is the case in which the called party sets the called number as the called terminal B, sets the call transfer when the called party does not answer, and designates the called terminal C as the called forwarding number.

When any caller (originating terminal A) attempts to call the service subscriber (terminal B) (202), the "initialDP" is sent to the service controller 50 by the trigger information set on the called party at the originating exchange 12. Send a message to indicate that the call is initiated (203).

Next, the service controller 50 transmits a "CallEvent (CID)" message to a logged-in program (for example, a messenger program) installed in the incoming information receiving terminal 53 of the called subscriber to notify that the call flows. (205). At this time, the information transferred from the service controller 50 to the incoming information receiving terminal 53 depends on the setting information of the called subscriber.

The service controller 50 then sends a " Request Report BCSM Event (RRB) " message to the exchange 12 to set up an event of the originating / receiving terminal (208).

The service controller 50 transmits the message " Connect " to the called number and attempts to reach the called terminal B (209). This process takes place via the exchange 12. That is, when the service controller 50 transmits a "Connect" message to the destination number to the switch 12, the switch 12 attempts to call the destination terminal B.

If the destination terminal B does not respond (No_Answer), the switch 12 notifies the destination terminal B of the non-response state by transmitting an "ERB (EventReportBCSM) (No_Answer)" message to the service controller 50 (210).

In response to this, the service controller 50 transmits a "CallEvent" message to a program (for example, a messenger program) installed and logged in to the called party's incoming information receiving terminal 53 to notify that the call is transferred (212). . At this time, the information transferred from the service controller 50 to the incoming information receiving terminal 53 depends on the setting information of the called subscriber.

Then, the service controller 50 attempts to reach the destination terminal C by transmitting a "Connect" message to the call forwarding number when no answer (215). This process takes place via the exchange 12. That is, when the service controller 50 transmits the message “Connect” to the switch 12 as the call forwarding number, the switch 12 attempts to call the corresponding terminal C.

If the answering terminal C responds (O_Answer), the switch 12 transmits an "ERB (O_Answer)" message to the service controller 50 to notify the answering state of the called terminal C (216).

In response to this, the service controller 50 transmits a "CallEvent" message to a logged-in program (for example, a messenger program) installed in the incoming information receiving terminal 53 of the called party and notifies that the call has been answered (217). ). At this time, the information transferred from the service controller 50 to the incoming information receiving terminal 53 depends on the setting information of the called subscriber.

When the calling terminal A and the called terminal C terminate the call in the busy state, the switch 12 transmits the message “ERB (Disconnect)” to the service controller 50 to notify that the call is terminated (218).

3 is a detailed flowchart illustrating a call transfer process when a called party is busy in a method of processing a call information notification system according to the present invention. This is the case in which the called party sets the called number as the called terminal B, sets the call transfer when the called party is busy, and designates the called terminal C as the called forwarding number.

When any caller (calling terminal A) attempts to call the service subscriber (terminal B) (302), the "initialDP" is sent to the service controller 50 by the trigger information set in the called subscriber at the calling switch 12. Send a message to indicate that the call is initiated (303).

Next, the service controller 50 transmits a "CallEvent (CID)" message to a logged-in program (for example, a messenger program) installed in the incoming information receiving terminal 53 of the called subscriber to notify that the call flows. (305). At this time, the information transferred from the service controller 50 to the incoming information receiving terminal 53 depends on the setting information of the called subscriber.

Then, the service controller 50 transmits a "RRB (RequestReportBCSMEvent)" message to the exchange 12 to set up the event of the originating and terminating terminal (308).

The service controller 50 transmits the message " Connect " to the called number and attempts to reach the called terminal B (309). This process takes place via the exchange 12.

If the receiving terminal B is busy (Busy), the exchange 12 transmits an "ERB (Busy)" message to the service controller 50 to notify the busy state of the receiving terminal B (310).

In response to this, the service controller 50 transmits a "CallEvent" message to a logged-in program (for example, a messenger program) installed in the incoming information receiving terminal 53 of the called subscriber to notify that the call is transferred (312). . At this time, the information transferred from the service controller 50 to the incoming information receiving terminal 53 depends on the setting information of the called subscriber.

Then, the service controller 50 transmits the message "Connect" to the call forwarding number and attempts to call the destination terminal C (315). This process takes place via the exchange 12.

If the answering terminal C responds (O_Answer), the switch 12 transmits an "ERB (O_Answer)" message to the service controller 50 to inform the answering state of the called terminal C (316).

In response to this, the service controller 50 transmits a " CallEvent " message to a logged-in program (for example, a messenger program) installed in the incoming information receiving terminal 53 of the called subscriber and notifies that the call has been answered (317). . At this time, the information transferred from the service controller 50 to the incoming information receiving terminal 53 depends on the setting information of the called subscriber.

When the calling terminal A and the called terminal C terminate the call in the busy state, the switch 12 transmits an "ERB (Disconnect)" message to the service controller 50 to notify that the call is terminated (318).

Figure 4 is a detailed flowchart of an embodiment of the call conversion process unconditionally among the processing method of the incoming information notification system according to the present invention. This is the case where the called party unconditionally transfers the call and designates the called terminal C as the called forwarding number. In other words, the call to the terminal B is forcibly switched to the terminal C regardless of whether the terminal B is busy or unanswered.

When any caller (calling terminal A) attempts to call the service subscriber (terminal B) (402), the calling controller 12 sends the "InitialDP" to the service controller 50 by the trigger information set at the called subscriber. Send a message to indicate that the call is initiated (403).

Next, the service controller 50 transmits a "CallEvent (CID)" message to a logged-in program (for example, a messenger program) installed in the incoming information receiving terminal 53 of the called subscriber to notify that the call flows. (405). At this time, the information transferred from the service controller 50 to the incoming information receiving terminal 53 depends on the setting information of the called subscriber.

The service controller 50 then sends a " RequestBBCBCEvent " (RRB) message to the exchange 12 to set up an event of the originating / receiving terminal (408).

Then, the service controller 50 transmits the message “Connect” to the call forwarding number (unconditional call forwarding number) and attempts to call the called terminal C (409). This process takes place via the exchange 12.

If the answering terminal C responds (O_Answer), the switch 12 transmits an "ERB (O_Answer)" message to the service controller 50 to notify the answering state of the called terminal C (410).

In response, the service controller 50 transmits a " CallEvent " message to a logged-in program (e.g., a messenger program) installed in the incoming information receiving terminal 53 of the called subscriber to notify that the incoming call has been answered. (411). At this time, the information transferred from the service controller 50 to the incoming information receiving terminal 53 depends on the setting information of the called subscriber.

When the calling terminal A and the called terminal C terminate the call in the busy state, the switch 12 transmits an "ERB (Disconnect)" message to the service controller 50 to notify that the call is terminated (412).

5 is a detailed flowchart illustrating an embodiment of a method of connecting a voice (/ video) mailbox unconditionally among processing methods of an incoming information notification system according to the present invention. This is the case that the called subscriber unconditionally switches to the voice (/ video) mailbox and stores the voice (/ video) message. In other words, the terminal B is forced to switch to the voice (/ video) mailbox without receiving.

When any caller (calling terminal A) attempts to call the service subscriber (terminal B) (502), the "InitialDP" is sent to the service controller 50 by the trigger information set on the called subscriber at the calling switch 12. A message is sent to indicate that the call is initiated (503).

Next, the service controller 50 transmits a "CallEvent (CID)" message to a logged-in program (for example, a messenger program) installed in the terminal 53 of the called subscriber and notifies that the call flows (505). . At this time, the information transferred from the service controller 50 to the incoming information receiving terminal 53 depends on the setting information of the called subscriber.

The service controller 50 then sends a " RequestBBCBCEvent " (RRB) message to the exchange 12 to set up an incoming / outgoing event (508). The service controller 50 establishes a connection with the special resource processor (IP) 16 by transmitting an ETC (EstablishTemporaryConnection) message to the exchange 12 (509).

Then, the exchange 12 receives the ETC message and transmits an "IAM (InitailAddressMessage)" message to the special resource processor 16 (510). In response, the special resource processor 16 transmits an "ARI (AssistRequest Instructions)" message to the service controller 50 to notify that it is ready to play the comment (511).

Subsequently, the service controller 50 sets and transmits a message ID to the special resource processor 16 by setting a message ID in the message " PlayAnnouncement (PA) " In response to this, the special resource processor 16 transmits the corresponding message set by the subscriber to the caller (calling terminal A), and then transmits the message by playing the message by transmitting the message “SRR (Specialized Resource Report)” to the service controller 50. Notify that the has been completed (513).

Next, the service controller 50 transmits the message "PRM (PromptAndRecordMessage)" to the special resource handler 16 to start recording the message (516), and the special resource handler 16 records the message through the "PRM_ack" message. Answer 517.

Then, the service controller 50 transmits the " CallEvent " message to the logged-in program (e.g., messenger program, etc.) installed in the incoming information receiving terminal 53 of the called party, indicating that a voice (/ video) message has arrived. Notify (519). At this time, the information transferred from the service controller 50 to the incoming information receiving terminal 53 depends on the setting information of the called subscriber.

Then, the service controller 50 transmits a "disconnected (DFC)" message to the exchange 12 to terminate the call with the special resource processor 16 (521).

6 is a detailed flowchart illustrating an example of a call termination process when a called party is unanswered in the method of processing the called party information notification system according to the present invention. When the called subscriber sets the called party number to the called terminal B, and sets the 'end call when the called party does not answer', it switches to the voice (/ video) mailbox when there is no answer and saves the voice (/ video) message. to be.

When any caller (calling terminal A) attempts to call the service subscriber (terminal B) (602), the calling controller 12 sends the "InitialDP" to the service controller 50 by the trigger information set at the called subscriber. A message is sent to indicate that the call is initiated (603).

Next, the service controller 50 transmits a "CallEvent (CID)" message to a logged-in program (for example, a messenger program) installed in the incoming information receiving terminal 53 of the called subscriber to notify that the call flows. (605). At this time, the information transferred from the service controller 50 to the incoming information receiving terminal 53 depends on the setting information of the called subscriber.

Then, the service controller 50 transmits a "RRB (RequestReportBCSMEvent)" message to the switch 12 to set up the event of the originating and terminating terminal (608).

Then, the service controller 50 transmits the message “Connect” to the called number and attempts to reach the called terminal B (609). This process takes place via the exchange 12.

If the destination terminal B does not respond (No_Answer), the switch 12 transmits a "ERB (No_Answer)" message to the service controller 50 to notify the non-response state of the destination terminal B (610).

In response to this, the service controller 50 transmits a " CallEvent " message to a logged-in program (e.g., a messenger program) installed in the incoming information receiving terminal 53 of the called subscriber and notifies the non-responsive state (611). . At this time, the information transferred from the service controller 50 to the incoming information receiving terminal 53 depends on the setting information of the called subscriber.

In addition, the service controller 50 sets a call / incoming event by transmitting a "RRB (RequestReportBCSMEvent)" message to the exchange 12 because the called subscriber sets 'end call when no answer' is set (614). 12) establishes a connection with the special resource handler (IP) 16 by transmitting an " ETC (EstablishTemporaryConnection) " message (step 615).

Then, the exchange 12 receives the ETC message and transmits an "IAM (InitailAddressMessage)" message to the special resource handler 16 (616). In response, the special resource processor 16 transmits an ARI (AssistRequest Instructions) message to the service controller 50 to notify that it is ready to play the announcement (617).

Thereafter, the service controller 50 sets the message ID to the special resource processor 16 and transmits the comment ID to the message " PlayAnnouncement (PA) " (618). In response to this, the special resource processor 16 transmits the corresponding message set by the subscriber to the caller (calling terminal A), and then transmits the message by playing the message by transmitting the message “SRR (Specialized Resource Report)” to the service controller 50. Notify that the operation has ended (619).

In addition, the service controller 50 transmits a message "PRM (PromptAndRecordMessage)" to the special resource handler 16 to start recording a message (622), and the special resource handler 16 uses the "PRM_ack" message to record the message. Answer 623.

Then, the service controller 50 transmits the "CallEvent" message to the logged-in program (for example, messenger program) installed in the incoming information receiving terminal 53 of the called subscriber to notify whether or not the message call termination processing. (625). In addition, when a voice (/ video) message of the caller (sending terminal A) is recorded (stored), it may be notified of this.

In the above, steps "622" to "623" is a process of recording and storing the caller's voice (/ video) is not necessarily an essential operation process.

7 is a detailed flowchart illustrating a call termination process when a called party is busy in a method of processing a called party information notification system according to the present invention. When the called subscriber sets the called party number to the called terminal B, and sets the 'end call when the called party is busy', and switches to the busy voice (/ video) mailbox to store the voice (/ video) message to be.

When any caller (originating terminal A) attempts to call the service subscriber (terminal B) (702), "InitialDP" to the service controller 50 by the trigger information set in the called party at the originating exchange 12. Send a message to indicate that the call is initiated (703).

Next, the service controller 50 transmits a "CallEvent (CID)" message to a logged-in program (for example, a messenger program) installed in the incoming information receiving terminal 53 of the called subscriber to notify that the call flows. (705). At this time, the information transferred from the service controller 50 to the incoming information receiving terminal 53 depends on the setting information of the called subscriber.

The service controller 50 then sends a " RequestBBCBCEvent " (RRB) message to the exchange 12 to set up the event of the originating and terminating terminal (708).

Then, the service controller 50 transmits the message "Connect" to the called number and attempts to reach the called terminal B (709). This process takes place via the exchange 12.

If the receiving terminal B is busy (Busy), the exchange 12 transmits an "ERB (Busy)" message to the service controller 50 to notify the busy state of the receiving terminal B (710).

In response, the service controller 50 transmits a " CallEvent " message to a logged-in program (for example, a messenger program) installed in the incoming information receiving terminal 53 of the called party and notifies the non-responsive state (711). . At this time, the information transferred from the service controller 50 to the incoming information receiving terminal 53 depends on the setting information of the called subscriber.

In addition, the service controller 50 sets a call / incoming event by transmitting a "RRB (RequestReportBCSMEvent)" message to the exchange 12 because the called subscriber sets 'end call waiting' (step 714). 12) establishes a connection with the special resource handler (IP) 16 by sending an " ETC (EstablishTemporaryConnection) " message.

Then, the exchange 12 receives the ETC message and transmits an "IAM (InitailAddressMessage)" message to the special resource handler 16 (716). In response, the special resource processor 16 transmits an "ARI (AssistRequest Instructions)" message to the service controller 50 to notify that it is ready to play the comment (717).

Thereafter, the service controller 50 sets the message ID to the special resource processor 16 and transmits the message ID to the special resource processor 16 (718). In response to this, the special resource processor 16 transmits the corresponding message set by the subscriber to the caller (calling terminal A), and then transmits the message by playing the message by transmitting the message “SRR (Specialized Resource Report)” to the service controller 50. Notify that the operation has ended (719).

Next, the service controller 50 transmits a message "PRM (PromptAndRecordMessage)" to the special resource handler 16 to start recording a message (722), and the special resource handler 16 records the message through the "PRM_ack" message. Answer (723).

Then, the service controller 50 transmits a "CallEvent" message to a logged-in program (for example, a messenger program) installed in the incoming information receiving terminal 53 of the called party and notifies whether the message call is terminated ( 725). In addition, when a voice (/ video) message of the caller (sending terminal A) is recorded (stored) (722 to 723) it may be notified.

In the above, the steps "722" to "723" is a process of recording and storing the caller's voice (/ video) is not necessarily required.

8 is a detailed flowchart illustrating an embodiment of an unconditional call termination process in a method of receiving information notification service according to the present invention. This is the case in which the called party ends the call unconditionally without receiving the terminal B when the incoming subscriber is absent. Therefore, the terminal B switches to the voice (/ video) mailbox without receiving the terminal B to store the voice (/ video) message.

Then, when any caller (calling terminal A) attempts to call the service subscriber (terminal B) (802), the calling switch 12 is sent to the service controller 50 by the trigger information set at the called subscriber. InitialDP "message is sent to notify that the call is initiated (803).

Next, the service controller 50 transmits a "CallEvent (CID)" message to a logged-in program (for example, a messenger program) installed in the incoming information receiving terminal 53 of the called subscriber to notify that the call flows. (805).

In addition, the service controller 50 sets a call / incoming event by transmitting a "RRB (RequestReportBCSMEvent)" message to the exchange 12 because the called subscriber has set 'unconditional call termination' (808), and the switch 12 In step 809, a connection is established with the special resource handler (IP) 16 by transmitting an " ETC (EstablishTemporaryConnection) " message.

Then, the exchange 12 receives the ETC message and transmits an "IAM (InitailAddressMessage)" message to the special resource handler 16 (810). In response, the special resource processor 16 transmits an "ARI (AssistRequest Instructions)" message to the service controller 50 to notify that it is ready to play a comment (811).

Subsequently, the service controller 50 sets the ID of the message to the special resource processor 16 and transmits the message ID to the special resource processor 16 (812). In response to this, the special resource processor 16 transmits a corresponding message set by the subscriber to the caller (calling terminal A), and then transmits the message by playing a “SRR (Specialized ResourceReport)” message to the service controller 50. Notify that the operation has ended (813).

Next, the service controller 50 transmits the message "PRM (PromptAndRecordMessage)" to the special resource handler 16 to start recording the message (816), and the special resource handler 16 records the message through the "PRM_ack" message. Answer (817).

Then, the service controller 50 transmits a "CallEvent" message to a logged-in program (for example, a messenger program) installed in the incoming information receiving terminal 53 of the called party and notifies whether the message call is terminated ( 819). In addition, when a voice (/ video) message of the caller (sending terminal A) is recorded (stored) (816 to 817), it may be notified.

In the above, steps "814" to "817" are a process of recording and storing the caller's voice (/ video), not necessarily required.

The present invention described above is capable of various substitutions, modifications, and changes without departing from the technical spirit of the present invention for those skilled in the art to which the present invention pertains. It is not limited by the drawings.

The present invention as described above, by using the incoming trigger (Trigger) method used in the existing communication network to notify the incoming information to the program of the receiving information receiving terminal connected to the recipient's Internet when the incoming call ('Incoming information notification service' ), It makes it possible to use the incoming trigger service more easily and efficiently.

Claims (12)

A processing method of an incoming information notification system in a communication system, Setting, by the subscriber, a call transfer condition for transferring a call when the called terminal is not answered or busy, and a receiving information receiving terminal at the time of transfer; When any caller attempts to call the called terminal, the intelligent network notifying the called information receiving terminal of the incoming call to the called terminal; An incoming attempt step of the intelligent network attempting to receive the called terminal; And a call forwarding notification step of notifying, by the intelligent network, that the call forwarding information is received when the intelligent network receives a result of the incoming call attempt as a result of no answer or a call. A processing method of an incoming information notification system in a communication system, Setting, by the subscriber, an intelligent network with a call transfer condition for unconditional call transfer and an incoming information receiving terminal; When any caller attempts to make a call to the called terminal, the intelligent network notifying the incoming information receiving terminal of the incoming call to the called terminal; And a call forwarding attempt step, wherein the intelligent network attempts to forward a call to a call forwarding terminal. A processing method of an incoming information notification system in a communication system, Setting up the receiving information receiving terminal in the intelligent network; When any caller attempts to make a call to the called terminal, the intelligent network notifying the incoming information receiving terminal of the incoming call to the called terminal; A mailbox switching step for the intelligent network to forward the mailbox to the mailbox; And a message arrival notification step of notifying, by the intelligent network, that the message has arrived to the called party's information receiving terminal after the message is processed in the mailbox. A processing method of an incoming information notification system in a communication system, Setting up a call termination condition for terminating a call when no answer or a call is in progress, and a receiving information receiving terminal in an intelligent network; When any caller attempts to make a call to the called terminal, the intelligent network notifying the incoming information receiving terminal of the incoming call to the called terminal; An incoming attempt step of the intelligent network attempting to receive the called terminal; And a guidement transmission step of transmitting a guidement to a calling terminal when the intelligent network receives that the incoming call attempt is not answered or is busy. A processing method of an incoming information notification system in a communication system, Setting a call termination condition for unconditional call termination and an incoming information receiving terminal in an intelligent network; When any caller attempts to make a call to the called terminal, the intelligent network notifies the called party of the incoming information to the called terminal by the called telephone number; And a announcement message transmitting step of transmitting the announcement message to the calling terminal. The method according to any one of claims 1 to 5, In the incoming notification step, And the intelligent network checks a caller's telephone number in association with a customer information program installed in the incoming information receiving terminal, and displays detailed information of the caller on the incoming information receiving terminal. The method according to claim 4 or 5, And recording the caller's message. The method according to any one of claims 1 to 5, wherein the intelligent network uses a service controller. The method according to any one of claims 1 to 5, wherein the intelligent network uses a parlay application server. The method according to any one of claims 1 to 5, wherein the incoming information receiving terminal is a terminal connected to the Internet. 6. The processing method according to any one of claims 1 to 5, wherein the incoming information receiving terminal is a mobile communication terminal. 6. The method according to any one of claims 1 to 5, wherein the incoming information receiving terminal is a VoIP softphone.

Images