KR101398398B1 - Communicationpacket switched network for presenting Anonymous Communication Rejection and Communication Barring service, apparatus thereof and method thereof - Google Patents

Abstract

The present invention relates to a communication system for providing a call disconnection service, a packet network for the same, and a method and a device for the same. The present invention relates to a communication system for providing a session connection request message A transmitting terminal for transmitting the data; A circuit network storing a reception rejection list of the called terminal for providing the individual call reception rejection service; And if the identification number of the calling terminal is an identification number registered in the reception rejection list while relaying the session connection request message to the called terminal, And a packet network for transmitting a session connection refusal message to the calling terminal indicating that the terminal is not connected. It is possible to prevent the calling terminal user from unnecessarily continuously attempting to make a call by providing the announcement that the reception is rejected.

Description

Technical Field [0001] The present invention relates to a packet network for providing an individual call rejection service, an apparatus therefor, and a method for the same.

The present invention relates to a technique of providing an additional service in a communication system, and more particularly, to a technique of providing an additional service in a communication system, in which a receiving terminal rejects reception of a calling terminal using an identification number registered in a reception rejection list registered in advance, To a packet network for providing an individual call rejection service for providing an announcement, an apparatus therefor, and a method therefor.

IP Multimedia Subsystems (IMS), which was originally developed for the Internet Protocol (IP) multimedia service of the 3G mobile communication network, is now becoming a core technology for providing new services in the next generation communication environment based on All IP.

The need for service control over IMS in packet-based networks can be found in the convergence of service quality, billing, and different services. Although we can provide all multimedia services through existing Internet connections, this is limited to best-effort services that do their best but do not guarantee quality. For example, streaming data is transmitted in a streaming format, but does not guarantee its quality for delay by the network. However, in the case of the IMS network, the quality of the session can be guaranteed by performing resource allocation for the session. That is, the IMS network performs packet switching.

The IMS network also enables proper billing of sessions. It is possible to provide an appropriate charging method according to the type and quality of the service, the characteristics of the user, and the policy of the network provider and the service provider, not simply the billing based on the flat rate or the packet amount. In addition, the IMS network can easily create a new service through an open interface protocol and provide an environment for creating a new service by combining with an existing service.

The above-mentioned point is to provide a control and billing capability for a service to both a network operator and a service provider, and to provide a user with a means to perform all his / her services in his / Characteristics. This is why IMS defined for mobile communication is becoming a basic control platform in the wired / wireless integrated environment based on All IP.

By introducing the IMS network, which is a packet-switched packet network, it is possible to provide mVoIP (mobile voice over IP) service to users through packet-based voice call service. However, if the All IP environment is not yet fully implemented, and if all the new infrastructure is built to provide additional services for packet-based voice call services, then redundant investment in the same existing infrastructure and its infrastructure The time and cost involved can be a burden.

On the other hand, the conventional voice call service provides various additional services, and there is a reception rejection service in which a called terminal rejects a call request of a calling terminal among the conventional additional services. However, the general reception rejection service can not know that the called terminal rejects reception on the calling terminal side. Therefore, the user of the originating terminal can continuously try to make a call connection, which can be a waste of radio wave resources.

SUMMARY OF THE INVENTION Accordingly, the present invention has been made keeping in mind the above problems occurring in the prior art, and an object of the present invention is to provide a packet network for providing an individual call rejection service for informing a user of a calling terminal that reception is denied, And to provide a method for this.

Another object of the present invention is to provide a private call rejection service capable of providing individual call rejection service in a packet network by utilizing resources used for providing an additional service in a circuit network in cooperation with a circuit network A packet network, a device for the same, and a method therefor.

According to another aspect of the present invention, there is provided a packet network for providing a Private Call Acceptance Rejection Service according to the present invention includes a session connection request message requesting a session connection for a call with a called terminal, A session controller for relaying to the called terminal; A media device for providing an announcement informing that the session connection request is not accepted; And receiving the session connection request message and inquiring of the reception reject list having at least one identification number rejected by the receiver terminal if the identification number of the calling terminal is registered in the reception reject list, And an additional service controller for instructing the media device to provide the announcement broadcast to the calling terminal.

delete

delete

delete

delete

delete

delete

delete

delete

delete

According to another aspect of the present invention, there is provided an add-on service controller for providing a call termination service for a call service, comprising a communication module for receiving a session connection request message for requesting session connection between a calling terminal and a called terminal, ; And a reception rejection list having at least one identification number for rejecting reception by the called terminal, and if the identification number of the calling terminal is registered in the reception reject list, And a control module for instructing the communication module to provide an announcement guide for rejecting the announcement.

The control module transmits an inquiry request message for inquiring a reception rejection list stored in an additional service device of the circuit network through the communication module, receives an inquiry response message responding to the inquiry request message transmitted, And confirms whether the identification number of the calling terminal is registered in the reception rejection list according to the response message.

Wherein the additional service controller further comprises a storage module for storing a reception rejection list having at least one identification number for which the receiver terminal refuses to receive the service, the control module inquiring the reception rejection list stored in the storage module, Whether the identification number of the calling terminal is registered in the reception rejection list.

According to another aspect of the present invention, there is provided a method for providing an individual call rejection service of an additional service controller in a preferred embodiment of the present invention, Receiving a message; Inquiring whether or not the identification number of the calling terminal is registered in the reception rejection list of the called terminal, from the reception rejection list stored in any one of the supplementary service device and the supplementary service controller of the circuit network; And instructing the media device to provide an announcement notification to the calling terminal indicating that the receiving terminal is rejected if the identification number of the calling terminal is registered in the reception rejection list as a result of the inquiry.

And transmitting a session connection rejection message indicating that the session connection request through the session connection request message can not be accepted to the calling terminal after the step of instructing.

According to SIP, the session connection request message is an INVITE message, and the session connection rejection message is a 487 RequestTerminated message.

Wherein the inquiring comprises generating an inquiry request message for requesting inquiry of the inquiry list when the inquiry list is stored in the additional service device and transmitting the inquiry inquiry message to the additional service device, And receives an inquiry response message providing a result.

Wherein the inquiry request message includes additional service identification information for distinguishing the subscribed individual call reception rejection service from other supplementary services and calling terminal identification information and calling terminal identification information extracted from the session connection request message .

Wherein the inquiry response message describes whether or not an identification number corresponding to the calling terminal identification information is registered in a reception rejection list corresponding to the called terminal identification information.

According to the present invention, when rejecting reception of a call connection request from the calling terminal, the calling terminal is notified that the reception is rejected. The user of the calling terminal can know that reception has been denied through the announcement, so that the user of the calling terminal may not make an unnecessary attempt to continuously request a call connection. Thus, waste of radio wave resources can be prevented.

Also, the packet network can utilize the database and web resources established for providing additional services in the circuit network by providing the individual call rejection service by referring to the reception rejection list of the destination terminals stored in the circuit network. As a result, the infrastructure cost for providing additional services can be reduced.

If the circuit network and the packet network use the same reception reject list, the same reception reject list is used to deny reception to the corresponding calling terminal, thereby providing a consistent individual call reject service in the circuit network and the packet network .

BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a diagram for explaining a communication system configuration for providing a private call reception rejection service according to an embodiment of the present invention; FIG.
BACKGROUND OF THE INVENTION 1. Field of the Invention [0001]
3 is a view for explaining a method of registering a reception rejection list according to an embodiment of the present invention.
FIG. 4 and FIG. 5 are flowcharts for explaining a method for providing a Private Call Blocking service of a packet network according to an embodiment of the present invention;
FIG. 6 and FIG. 7 are flowcharts for explaining a method for providing a Private Call Blocking service of a packet network according to another embodiment of the present invention;
8 is a flowchart illustrating a method for providing an individual call rejection service of an additional service controller according to an embodiment of the present invention.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. In the following description and the accompanying drawings, detailed description of well-known functions or constructions that may obscure the subject matter of the present invention will be omitted. It should be noted that the same constituent elements are denoted by the same reference numerals as possible throughout the drawings.

The terms and words used in the present specification and claims should not be construed as limited to ordinary or dictionary meanings and the inventor is not limited to the meaning of the terms in order to describe his invention in the best way. It should be interpreted as meaning and concept consistent with the technical idea of the present invention. Therefore, the embodiments described in the present specification and the configurations shown in the drawings are merely the most preferred embodiments of the present invention, and not all of the technical ideas of the present invention are described. Therefore, It is to be understood that equivalents and modifications are possible.

FIG. 1 is a diagram for explaining a configuration of a communication system for providing a personalized call rejection service according to an embodiment of the present invention.

Referring to FIG. 1, a communication system according to an embodiment of the present invention includes a packet switched network 100, a circuit switched network 200, an access network 300, a terminal 400, And a business entity terminal 500.

The packet network 100 is a core network that provides a communication service to the terminal 400 according to a packet switched scheme based on an IP (Internet Protocol), and the circuit network 200 is a circuit exchange (Core Network) that provides a communication service to the terminal 400 according to a Circuit Switched scheme. The access network 300 provides a wireless section service to the terminal 400 and the terminal 400 can access the packet network 100 or the circuit network 200 through the access network 300. [ In the embodiment of the present invention, a terminal 400 requesting a call connection among terminals 400 is referred to as an originating terminal 401 and a terminal 400 to be a call connection terminal is referred to as a terminating terminal 402. [ The terminal 400 has an identification number, and the identification number is information for distinguishing the terminal from other terminals. For example, the identification number may be a telephone number.

The packet network 100 can basically provide a voice call service to the terminal 400. [ The packet network 100 can allocate resources for communication between the calling terminal 401 and the called terminal 402 when the calling terminal 401 requests a call connection with the called terminal 402. [ According to the Session Initiation Protocol (SIP), resource allocation is performed through session connection between the calling terminal 401 and the called terminal 402. When the session is connected, the calling terminal 401 and the called terminal 402 can exchange voice packets through a connected session, which can be performed according to the mVoIP (mobile voice over IP) method. In addition, the packet network 100 may provide an additional service for a voice call service, which is a basic service. In particular, the packet network 100 can provide a private call rejection service as an additional service. The individual call reception rejection service is a service denying reception of a session connection request of the calling terminal 401 when the calling terminal 401 requests a session connection for a call with the called terminal 402. The reception rejection is performed on the calling terminal 401 having the identification number previously registered in the reception rejection list by the called terminal 402. [ Particularly, the individual call reception rejection service according to the embodiment of the present invention provides the announcement terminal 401 to announce the reception rejected. Accordingly, the user of the calling terminal 401 can recognize that the reception is rejected, and may not unnecessarily continue to make a call.

The terminal 400 can access the packet network 100 through an access network 300 and the access network 300 can access the packet network 100 through the terminal 400, (400) and the packet network (100). The packet network 100 can support all kinds of access networks 300. [ For example, the access network 300 may be a fixed access system such as a digital subscriber line (DSL), a cable modem, and an Ethernet. In this method, the access network 300 connects the terminal 400 to the packet network 100 through a modem, a router, a gateway, or the like connected to the terminal 400 by wire, Connection service can be provided. Also, the access network 300 may be a mobile access system such as W-CDMA, CDMA2000, GSM, and GPRS. In this method, the access network 300 includes a base station 310, a base station controller 320, a gateway 330, and the like, and provides a wireless section service between the access network 300 and the terminal 400 , The terminal 400 can be connected to the packet network 100. The access network 300 may be a wireless access network such as a WLAN (Wireless Local Area Network), a WiFi (Wireless Fidelity), or a WiMAX (Worldwide Interoperability for Microwave Access). In this case, the access network 300 may include an access point and an access router. Accordingly, the access network 300 can provide a wireless section service to the terminal 400, allowing the terminal 400 to access the packet network 100. [ Therefore, the terminal 400 that can use the access network 300 can access the packet network 100 through the access network 300. 1, it is assumed that the access network 300 includes the base station 310, the base station controller 320, and the gateway 330 in the mobile access scheme. However, the connection network 300 according to the embodiment of the present invention is not limited thereto, and the connection network 300 of the fixed connection type or the wireless connection type may be used.

Particularly, in the embodiment of the present invention, the packet network 100 is assumed to be IMS (IP Multimedia Subsystems). The packet network 100 is composed of a plurality of entities, and each of the entities may be implemented as one device, or may be implemented as a different device for each entity.

Entities of the packet network 100 according to an embodiment of the present invention may include a Telephony Application Server (TAS) 110, a Call Session Control Function (CSCF) 120, a Home Subscriber Server 130, and a media device 160. In particular, the media device 160 includes a Multimedia Resource Function Controller (MRFC) 140 and a Multimedia Resource Function Processor (MRFP) 150. Other entities of the packet network 100 omit explanations in order to clarify the gist of the invention.

The supplementary service controller 110 is for providing the individual call rejection service. When the calling terminal 401 receives a session connection request message requesting a session connection with the called terminal 402, the supplementary service controller 110 transmits the identification number of the calling terminal 401 to the called terminal 402 It can inquire whether it is registered in the rejection list. The session connection request message may use the INVITE message according to the SIP. The INVITE message includes information for identifying the calling terminal 401 requesting the session connection and the called terminal 402 that is the object of the session connection and accordingly requests the session connection between the calling terminal 401 and the called terminal 402 do. At this time, the supplementary service controller 110 determines whether the identification number of the calling terminal 401 is stored in the reception rejection list stored in the supplementary service device 230 of the circuit network 200, It is possible to inquire whether or not it is registered in the reception rejection list of the mobile terminal. Here, the identification number may be identification information for distinguishing the calling terminal 401 from the other terminals 400. [ For example, the identification number may be the telephone number of the calling terminal 401.

In particular, the supplementary service controller 110 may transmit an inquiry request message requesting inquiry to the supplementary service device 230. Accordingly, the additional service device 230 can transmit an inquiry response message to the supplementary service controller 110 in response to the inquiry request message.

The inquiry request message includes the additional service identification information, the called terminal identification information, and the calling terminal identification information as its parameters. Here, the supplementary service identification information is for distinguishing the supplementary service from other supplementary services. In addition, the additional service identification information is for informing that a request for inquiry list inquiry necessary for providing a private call reception rejection service is requested. The called terminal identification information is for distinguishing the called terminal 402 from other terminals. In addition, the destination terminal identification information is for requesting to inquire the reception rejection list mapped to the destination terminal 402. [ The calling terminal identification information is for distinguishing the calling terminal 401 from other terminals. In addition, the calling terminal identification information is for requesting to inquire whether the identification number of the calling terminal 401 is registered in the reception rejection list. The INVITE message may include a From header or a P-Asserted-Id header. According to this, the identification number of the calling terminal 401 can be mapped to a URI (Uniform Resource Locator) of a From header or a P-Asserted-Id header. For example, when the identification number is a telephone number, the URI of the telephone number and the From header or the P-Asserted-Id header are mapped to each other, and the identification number of the reception reject list can be retrieved through the URI of the From header.

According to the MAP (Mobile Application Part), the inquiry request message can use the Service Request Inv (Invoke) message. The Service Request Inv (Invoke) message includes Digits (dialed), CPND1 (CallingPartyNumberDigit1), and SVCID (Service ID) as its parameters. Here, the called terminal identification information may be digits (dialed). That is, the additional service controller 110 can extract the URI of the To header from the INVITE message received from the calling terminal 401 and write it in the parameter Digits of the Service Request Inv message. Also, the calling terminal identification information may be CPND1. That is, the additional service controller 110 can extract the URI of the From header or the P-Asserted-Id header from the received INVITE message and describe the URI in the parameter CPND1 of the Service Request Inv message. And the supplementary service identification information may be SVCID. That is, the supplementary service controller 110 can describe the supplementary service identification information indicating the individual call reception rejection service in the parameter SVCID of the Service Request Inv message.

The additional service device 230 inquires the reception rejection list according to the supplementary service identification information of the inquiry request message. At this time, the additional service device 230 inquires whether the identification number of the calling terminal 401 mapped to the calling terminal identification information is registered in the reception rejection list mapped to the called terminal identification information. In response to the inquiry result, the additional service device 230 transmits an inquiry response message informing whether the identification number of the calling terminal 401 is included in the reception rejection list or whether or not the calling terminal 401 is opted- To the controller (110). According to the MAP, the inquiry response message can use the service request rrl (return result) message. The service request rrl message includes an ActionCode as its parameter, and the additional service device 230 determines whether the identification number of the calling terminal 401 is included in the reception rejection list or not, It can be described in the parameter ActionCode of the Request rrl message and transmitted to the supplementary service controller 110.

When the identification number of the calling terminal 401 is registered in the reception rejection list of the called terminal 402, the additional service controller 110 provides the individual call reception rejection service. According to the individual call reception rejection service, the supplementary service controller 110 requests session connection for announcement broadcasting between the media device 160 and the calling terminal 401 to provide announcement to the calling terminal 401, The user can instruct the media device 160 to provide the announcement. Also, the supplementary service controller 110 may transmit a session connection rejection message informing the calling terminal 401 that the session connection request is not accepted. The session connection rejection request message can use the 487 RequestTerminated message according to the SIP. Here, the 487 RequestTerminated message is basically used for a negative response such as an error to a specific SIP message. Particularly, according to the embodiment of the present invention, the 487 RequestTerminated message responds to the INVITE message and can be used as a message indicating that the session connection is denied.

On the other hand, before providing the above-mentioned individual call reception rejection service, the additional service controller 110, upon receiving the session connection request message, notifies that the calling terminal 401 requests a call connection with the called terminal 402 have. Accordingly, the additional service controller 110 can confirm the type of the additional service to which the called terminal 402 subscribes to provide the additional service. At this time, the additional service controller 110 can confirm the type of the additional service subscribed by the receiving terminal 402 through the home subscriber device 130. [ Accordingly, when the called terminal 402 subscribes to the individual call reception rejection service, the additional service controller 110 can provide the individual call reception rejection service. The supplementary service controller 110 may use the service profile stored in the home subscriber device 130 of the packet network 100 to confirm whether or not to join the individual call reception reject service. The additional service controller 110 can check the service profile by inquiring the service profile of the home subscriber device 130, or receive and store the service profile of the home subscriber device 130, and confirm the service profile. A service profile includes a list of supplementary services to which a user subscribes, and each item in the list represents a service. Here, the service includes a basic service and an additional service. The supplementary service controller 110 can provide a private call rejection service when an item corresponding to the individual call rejection service is activated in the service profile. Also, the additional service controller 110 can not provide the individual call reception rejection service when the item corresponding to the individual call reception reject service is disabled in the service profile.

The session controller 120 establishes a session between each entity of the packet network 100 and the terminal 400 and receives and processes the SIP message transmitted from the terminal 400. [ The session controller 120 delivers a SIP message to each entity in the packet network 100 to provide the service as requested by the terminal 400, thereby allowing the session to be completed. The session controller 120 may include I (Interrogating) - CSCF, S (Service) - CSCF, and P (Proxy) - CSCF.

The session controller 120 basically supports connection and termination of sessions for voice communication according to a packet exchange method between the calling terminal 401 and the called terminal 402. For this, a message exchange between the calling terminal 401 and the called terminal 402 can be relayed. In particular, according to an embodiment of the present invention, a message may use a message according to SIP, i.e., a SIP message.

The SIP message used in the embodiment of the present invention will be described as follows.

The INVITE message is a method for requesting a session connection between a device and a device. Here, the apparatus includes each entity of terminal 400 and packet network 100. For the session connection, the INVITE message specifies the object of the session connection. Therefore, according to the embodiment of the present invention, the INVITE message includes a session connection request message for requesting a session connection for voice communication between the calling terminal 401 and the called terminal 402, As a broadcast session connection request message.

The ACK message is a method used as a response indicating that the device that received the specific SIP message finally confirmed the specific SIP message. Therefore, according to the embodiment of the present invention, the ACK message can be used as a broadcast session connection acceptance confirmation message informing that the broadcast session connection acceptance (200 OK) message has been confirmed. In addition, the ACK message may be used as a session connection rejection acknowledgment message informing that it has confirmed the rejection of the session connection, in response to the session connection rejection (487 RequestTerminated) message.

Among the SIP messages, the 1xx series message (where xx is a natural number) is a kind of response message. The 1xx series messages are used to notify that a specific request message has been received and message processing is continuing. When the calling terminal 401 transmits an INVITE message requesting a session connection to the called terminal 402, the called terminal 402 may respond with a 180 Ringing message. However, the supplementary service controller 110 does not deliver the INVITE message to the calling terminal 402, and the supplementary service controller 110 transmits the 183 SessionProgress message to the calling terminal 401 in order to reject the calling terminal 401. [ Lt; / RTI > In particular, the 183 SessionProgress message is a message indicating that the session is still in progress. The supplementary service controller 110 can continue the procedure for proceeding with session connection for announcement broadcasting instead of session connection for voice communication by transmitting the 183 SessionProgress message. Therefore, the 183 SessionProgress message can be used as a session progress message to inform that the session is in progress.

Of the SIP messages, 2xx series messages (where xx is a natural number) are used to indicate success in response to a specific SIP message. In particular, a 200 OK message is used to indicate acceptance, acknowledgment of acknowledgment, acknowledgment, etc. for a particular message. Therefore, according to the embodiment of the present invention, the 200 OK message can be used as a broadcast session connection acceptance message for accepting a session connection in response to a broadcast session connection request (INVITE) message. In addition, the 200 OK message may be used as a broadcast acceptance message informing that broadcast announcement is to be performed in response to a broadcast instruction (INFO) message instructing to perform broadcast. The 200 OK message may be used as an end confirmation message indicating that the end notification (INFO) message for ending the announcement has been confirmed. Also, the 200 OK message may be used as a broadcast session connection end acceptance message informing that the 200 OK message is accepted in response to the broadcast session connection end (BYE) message.

Of the SIP messages, 4xx series messages (where xx is a natural number) are response messages used for the purpose of the response. 4xx series messages are used to indicate that a particular message contains an error or that it can not process a particular message. In particular, the 487 RequestTerminated message indicates that the request has been terminated in response to a particular request message. Accordingly, the 487 RequestTerminated message can be used as a session connection refusal message indicating that the session connection request is rejected. The supplementary service controller 110 may transmit the 487 RequestTerminated message to the calling terminal 401 in response to the INVITE message requesting the session connection with the calling terminal 402 of the calling terminal 401 instead of the calling terminal 402. [

The BYE message is a method used to end various sessions. Therefore, the BYE message can be used as a broadcast session connection termination message informing the end of session connection for broadcasting.

The INFO message is a method for transmitting additional information within a previously established session. Accordingly, after the session for broadcasting is connected, the INFO message can be used for the broadcast instruction message for instructing the start of the announcement broadcast and the end instruction message for notifying the end of the announcement broadcast.

The home subscriber device 130 stores user information and supports entities that perform session control. The home subscriber device 130 stores the subscription information of the user related to the session control, that is, the location information of the user, the security information for authentication and permission of the user, and the service profile, which is a list of services to which the user subscribes.

The media device 160 may connect the session between the media device 160 itself and the calling terminal 401 at the request of the supplementary service controller 110 when providing the individual call rejection service. This is a session for announcement broadcasting. When the session for the announcement is connected, the media device 160 provides the announcement to the calling terminal 401 at the request of the supplementary service controller 110. [ At this time, the supplementary service controller 110 requests to provide the announcement through the INFO message. Accordingly, the media device 160 provides the prepared announcement broadcast to the calling terminal 401. [ When the prepared announcement is completed, the media device 160 transmits an INFO message to the supplementary service controller 110 to inform that the broadcast has ended. The INFO message transmitted by the supplementary service controller 110 is a broadcast instruction message for instructing announcement broadcasting, and the INFO message transmitted by the media device 160 is an end announcement message informing the end of announcement broadcast. This INFO message is used to send additional information between the entities to which the session is connected. Accordingly, the supplementary service controller 110 and the media device 160 can instruct the start of the announcement through the INFO message or notify that the announcement has ended.

The media device 160 includes a multimedia resource controller 140 and a multimedia resource processor 150. When the session is connected, the multimedia resource controller 140 may control the multimedia resource processor 150 to transmit the announcement. Accordingly, the multimedia resource processor 150 can provide announcement broadcasting to the calling terminal 401 under the control of the multimedia resource controller 140. [ In addition, the multimedia resource controller 140 and the multimedia resource processor 150 may perform multimedia related functions. Multimedia related functions may include announcement of voice or video, audio stream mixing required for media conferencing, conversion between characters and voice or speech recognition, and real-time transcoding of multimedia data. In addition, the multimedia resource controller 140 and the multimedia resource processor 150 may be implemented as independent devices or as a single device.

Next, the configuration of the circuit network 200 according to the embodiment of the present invention will be described. The circuit network 200 includes a home location register (HLR) 210, an intranet gateway (IGW) 220, and an additional service device 230.

The home location register 210 basically manages users in the circuit network 200. [ That is, the home location register 210 may perform functions such as user authentication and location registration. In particular, the home location register 210 may manage the services to which the user subscribes. This service includes basic services and additional services. Herein, the basic service can exemplify a voice call, and the additional service can exemplify call forwarding, voice message, and the like. In order to manage the service to which the user subscribes, the home location register 210 may store a service profile, which is a list of services to which the user subscribes. Each item in this list represents a service. If the item is activated, the corresponding service can be provided. If it is inactivated, the corresponding service can not be provided. The above-mentioned service includes a basic service and an additional service.

The intranet gateway 220 is a gateway between the additional service controller 110 and the home location register 210 and the additional service device 230. That is, the intranet gateway 220 connects the additional service controller 110 with the home location register 210 and the additional service device 230.

The additional service device 230 may be implemented using a Telephony IP Integration System (TIIS) to provide the individual call rejection service in which the called terminal 402 rejects the call to the calling terminal 401. [

The supplementary service device 230 may store the rejection list corresponding to the called terminal 402. [ The called terminal 402 can register the identification number to which the reception terminal 402 intends to reject reception in the reception rejection list in advance. To this end, the additional service device 230 may provide a web environment for registering and changing or deleting an identification number for rejection in the reception rejection list. For example, in the case where the destination terminal 402 wants to register (update), change, delete, or inquire the identification number to reject the reception, it can be done through the web page or web application provided by the additional service device 230 have. The supplementary service controller 110 may refer to the reception rejection list of the supplementary service device 230 and use the web environment described above when providing the individual call rejection service. Accordingly, the additional service provided in the circuit network 200 can be directly provided in the packet network 100, and the service consistency can be maintained.

The supplementary service controller 110 is interworked with the home location register 210 through the intranet gateway 220 and the supplementary service controller 110 and the home location register 210 can communicate with each other according to the MAP. The supplementary service controller 110 may receive and store the required service profile from the home location register 210. [ If the service profile received and stored from the home location register 210 is changed, the additional service controller 110 can deliver it to the home location register 210. In addition, the home location register 210 may transmit the changed service profile to the additional service controller 110 when the service profile stored therein is changed. Accordingly, the service profiles stored in the additional service controller 110 and the home location register 210 can be kept equal to each other.

The supplementary service controller 110 is connected to the supplementary service device 230 through the intranet gateway 220 and the supplementary service controller 110 and the supplementary service device 230 are connected to each other via the intranet gateway 220 according to the MAP Communication. Accordingly, the supplementary service controller 110 can inquire the reception rejection list stored in the supplementary service device 230.

The destination terminal 402 or the business entity terminal 500 accesses the supplementary service controller 110 or the supplementary service device 230 and transmits an identification number to the destination terminal 402 for rejection to the destination terminal 402 You can register on the deny list. Here, the vendor terminal 500 may be a terminal of a vendor operating the packet network 100 and the circuit network 200. The business entity terminal 500 may be a PC (Personal Computer). Therefore, when registering through the called terminal 402, the user of the called terminal 402 directly registers the identification number in the rejection list. When registering through the business entity terminal 500, the business entity registers the business entity at the request of the user of the called terminal 402. As shown in the figure, the vendor terminal 500 can access the supplementary service controller 110 or the supplementary service device 230 through the access network in the same manner as the receiver terminal 402. In addition, the business entity terminal 500 preferably connects directly to the additional service controller 110 or the additional service device 230 through an intra-net of the business entity.

Next, a configuration of an additional service controller for providing a call reception denial service according to an embodiment of the present invention will be described. 2 is a diagram for explaining a configuration of an additional service controller for providing a call reception denial service according to an embodiment of the present invention.

2, the supplementary service controller 110 includes a communication module 10, a storage module 20, and a control module 30. [

The communication module 10 is for transmitting and receiving data with other entities in the packet network 100 and with the configurations of the circuit network 200. [ For this purpose, the communication module 10 may have a function of processing data with a protocol suitable for the object to be communicated. The supplementary services controller 110 can basically communicate with other entities within the packet network 100 according to SIP. Accordingly, the communication module 10 can process the data to be transmitted and received according to the SIP when communicating with other entities of the packet network 100. That is, the communication module 10 transmits and receives the SIP message. In addition, the supplementary services controller 110 can communicate with the home subscriber device 130 according to the DIAMETER protocol for data security. Accordingly, when the communication module 10 communicates with the home subscriber device 130 of the packet network 100, the communication module 10 can process the data transmitted and received according to the DIAMETER protocol. The supplementary service controller 110 can communicate with the intranet gateway 220 according to the MAP. Accordingly, when the communication module 10 communicates with the intranet gateway 220, the supplementary service controller 110 can process data to be transmitted / have.

The storage module 20 may store the rejection list. The called terminal 402 can register (store), change or delete the identification number to which the reception terminal 402 desires to reject the reception. In order to support this, the supplementary service controller 110 may have a web function for registering, changing or deleting the identification number in the rejection list. For example, the additional service controller 110 may provide an interface for supporting the registration, change, or deletion of the identification number through a web page. Accordingly, the storage module 20 may store a web page providing an interface for registering, changing or deleting an identification number. The storage module 20 may store the service profile received from the home location register 210 and the service profile received from the home subscriber device 130. [ In addition, the storage module 20 may temporarily or permanently store various messages transmitted and received.

The control module 30 is for providing an individual call rejection service in the supplementary service controller 110. For this, the control module 30 can generate various messages required for the individual call rejection service. The control module 30 may extract necessary information from the message received through the communication module 10 or may include information necessary for the message and transmit the information through the communication module 10.

When the control module 30 receives the session connection request message through the communication module 10, the control module 30 can check whether the calling terminal 401 is subscribed to the individual call rejection service. That is, the control module 30 can confirm whether to join the individual call rejection service by interworking with the home location register 210 or the home subscriber device 130 through the communication module 10.

The control module 30 may generate the inquiry request message. The control module 30 may extract the calling terminal identification information and the called terminal identification information from the session connection request message and then include the calling terminal identification information and the called terminal identification information in the inquiry request message. The control module 30 may include supplementary service identification information, which allows the calling terminal 402 to distinguish the individual call reception rejection service from other supplementary services, in the inquiry request message. The control module 30 transmits the inquiry request message to the additional service device 230 of the circuit network 200 through the communication module 10. [ The control module 30 can confirm whether the identification number of the calling terminal 401 is included in the reception rejection list of the called terminal 402 through the inquiry response message in response to the inquiry request message.

If the identification number of the calling terminal 401 is included in the reception rejection list of the called terminal 402, the control module 30 proceeds to a session establishment procedure for requesting the media device 160 for announcement broadcasting. Then, when a session for announcement broadcasting between the calling terminal 401 and the media device 160 is connected, the control module 30 requests the media device 160 to send a broadcast request to the calling terminal 401 An instruction message can be generated and transmitted. The control module 30 may generate a session connection rejection message indicating that the session connection request of the calling terminal 401 can not be accepted and transmit the session connection rejection message to the calling terminal 401.

Next, a method of registering a reception rejection list according to an embodiment of the present invention will be described. 3 is a diagram for explaining a method of registering a reception rejection list according to an embodiment of the present invention.

3, the called terminal 402 or the business entity terminal 500 accesses the supplementary service controller 110 or the supplementary service device 230 to receive an identification number to which the called terminal 402 rejects reception It can be registered in the reception rejection list of the terminal 402.

It is preferable that the destination terminal 402 or the business entity terminal 500 is connected to the additional service controller 110 or the additional service device 230 through a web environment. In this case, the additional service controller 110 or the additional service device 230 may provide a web page. Here, the web page has an interface capable of creating a rejection list for registration of an identification number for rejecting reception. Through the interface, the additional service controller 110 or the additional service device 230 can receive at least one identification number for which the user of the called terminal 402 desires to reject the reception. Accordingly, the additional service controller 110 or the additional service device 230 can store the reception reject list. Thus, the reception rejection list is created in accordance with the intention of the user of the called terminal 402, and has at least one identification number for which the user of the called terminal 402 desires to reject.

In particular, according to an embodiment of the present invention, the identification number is identification information for distinguishing the calling terminal 401 or the calling terminal 401 user from other terminals or other terminal users. This identification number may be the same as the URI of the From header or the P-Asserted-Id header of the INVITE message, or it may be mapped. Therefore, the identification number registered in the rejection list can be inquired through the URI of the From header of the INVITE message or the P-Asserted-Id header.

Then, as described above, a method of providing the individual call reception rejection service in a state where the reception rejection list of the call reception terminal 402 is registered will be described.

4 and 5 are flowcharts for explaining a method for providing a Private Call Notification Service of a packet network according to an embodiment of the present invention.

Referring to FIG. 4, the calling terminal 401 transmits a session connection request message to the session controller 120 in step S401, and requests a call connection with the called terminal 402. As described above, the session connection request message may be an INVITE message according to the SIP. The session controller 120 receiving the INVITE message forwards the INVITE message to the supplementary service controller 110 in step S403.

After receiving the INVITE message, the supplementary service controller 110 checks whether the called terminal 402 described in the reception object is subscribed to the individual call rejection service in the INVITE message. If the called terminal 402 is subscribed to the individual call rejection service, the supplementary service controller 110 determines whether the identification number of the calling terminal 401 is registered in the reception rejection list of the called terminal 402 in step S405 do. Here, it is assumed that the identification number of the calling terminal 401 is registered in the reception rejection list of the called terminal 402. [ Then, the supplementary service controller 110 proceeds with a process for providing the individual call rejection service.

According to the individual call reception rejection service, it is possible to provide a guidance broadcast to guide the calling terminal 401 that the reception is denied. The supplementary service controller 110 proceeds to connect a session between the media device 160 and the calling terminal 401 in order to provide an announcement to the calling terminal 401. [ That is, in step S407, the AMS controller 110 transmits a broadcast session connection request message to the session controller 120 requesting a session connection between the media device 160 and the calling terminal 401. [ This is to allow the media device 160 to provide the announcement to the calling terminal 401. Here, the broadcast session connection request message can use the INVITE message according to the SIP. Then, the session controller 120 delivers the INVITE message to the media device 160 in step S409.

Upon receiving the INVITE message, the media device 160 transmits a 200 OK message to the session controller 120 in step S411. Here, the 200 OK message is a broadcast session connection acceptance message meaning accepting a session connection with the calling terminal 401. The session controller 120 forwards the 200 OK message to the supplementary service controller 110 in step S413.

Upon receiving the 200 OK message, the supplementary services controller 110 transmits an ACK message to the session controller 120 in step S415, and the session controller 120 transmits an ACK message to the media device 160 in step S417. Here, the ACK message is a broadcast session connection acknowledgment message informing that it has confirmed the acceptance of the session connection for broadcasting.

After transmitting the ACK message, the ASSC 110 transmits an 183 SessionProgress message to the session controller 120 in step S419, and the session controller 120 transmits a 183 SessionProgress message to the calling terminal 401 in step S421. . 183 The SessionProgress message is a response to the INVITE message originally transmitted by the calling terminal 401, and is a session progress message informing that the session establishment procedure is still in progress. The session setup procedure must be in progress for announcement due to rejection and rejection. Therefore, the supplementary service controller 110 transmits the 183 SessionProgress message in response to the INVITE message instead of the called terminal 402.

After transmitting the 183 SessionProgress message, the supplementary service controller 110 transmits the INFO message to the session controller 120 in step S423, and the session controller 120 transmits the INFO message to the media device 160 in step S425 . The INFO message is a broadcast instruction message for instructing the media device 160 to broadcast announcement.

Upon receiving the broadcast instruction message, the media device 160 transmits a 200 OK message to the session controller 120 in step S427. Then, the session controller 120 forwards the 200 OK message to the supplementary service controller 110 in step S429. Here, the 200 OK message is a broadcast acceptance message informing that broadcast announcement will be performed in response to the broadcast indication message. After transmitting the broadcast admission message, the media device 160 provides announcement broadcast to the calling terminal 401 in step S431. This announcement broadcast informs the calling terminal 401 of the reception rejection of the receiving terminal 402. [

5, the media device 160 transmits the INFO message to the session controller 120 in step S433 after the announcement is completed, and the session controller 120 transmits the INFO message to the supplementary service controller 110 ). Here, the INFO message is an end notification message informing that announcement is terminated.

The supplementary service controller 110 transmits a 200 OK message to the session controller 120 in response to the INFO message in step S437. Then, the session controller 120 delivers the 200 OK message to the media device 160 in step S439. Here, the 200 OK message is an end confirmation message informing that the end of the announcement has been confirmed.

After transmitting the end confirmation message (200 OK), the supplementary service controller 110 transmits a session connection rejection message to the session controller 120 in step S441. This session connection rejection message is a response to the session connection request message transmitted first by the calling terminal 401, and informs that the session connection request is terminated. That is, it informs the reception rejection. The Session Connection Reject message may use the 487 RequestTerminated message, depending on the SIP. The calling terminal 401 transmits a session connection request message in step S601, and the 487 RequestTerminated message is a session connection rejection message indicating that the request is not accepted for the INVITE message, which is a session connection request message. Then, in step S443, the session controller 120 transmits a session connection rejection message (487 RequestTerminated) to the calling terminal 401.

Upon receiving the session connection rejection message, the calling terminal 401 transmits an ACK message to the session controller 120 in response to the 487 RequestTerminated message in step S445. Then, the session controller 120 transmits an ACK message to the supplementary service controller 110 in step S447. Here, the ACK message is a session connection refusal confirmation message informing that the refusal of the session connection has been confirmed in response to the session connection refusal message.

Upon receiving the ACK message, the supplementary service controller 110 transmits a BYE message to the session controller 120 in step S449 to terminate the connection of the broadcast session between the media device 160 and the calling terminal 401. [ Lt; / RTI > The session controller 120 delivers the BYE message to the media device 160 in step S451. Here, the BYE message is a broadcast session connection termination message informing the end of the session connection for broadcasting.

Upon receiving the broadcast session connection termination message, the media device 160 transmits a 200 OK message to the session controller 120 in response to the BYE message in step S453. Then, the session controller 120 delivers the 200 OK message to the supplementary service controller 110 in step S455. Here, the 200 OK message is a broadcast session connection end acceptance message informing that the broadcast session connection end is accepted. The session connection between the media device 160 and the calling terminal 401 is terminated.

FIG. 6 and FIG. 7 are flowcharts for explaining a method for providing a Private Call Blocking service of a packet network according to another embodiment of the present invention.

Referring to FIG. 6, in step S601, the calling terminal 401 transmits a session connection request message to the session controller 120 to request a call connection with the called terminal 402. FIG. Here, the session connection request message may be an INVITE message according to the SIP. The session controller 120 receiving the INVITE message forwards the INVITE message to the supplementary service controller 110 in step S603.

Upon receiving the session connection request (INVITE) message, the supplementary service controller 110 determines whether the called terminal 402 receiving the INVITE message is subscribed to the individual call rejection service. It is necessary to check whether the identification number of the calling terminal 401 is registered in the reception rejection list of the called terminal 402. In this case, To this end, the additional service controller 110 delivers an inquiry request message to the additional service device 230 in step S605. The inquiry request message is for inquiring the receiver rejection list stored in the additional service device 230. According to a MAP (Mobile Application Part), an inquiry request message can use a Service Request Inv (Invoke) message. The inquiry request message includes additional service identification information, identification information of the called terminal 402, Information. The supplementary service device 230 can know that the supplementary service controller 110 requests the inquiry of the rejection list necessary for providing the individual call reception rejection service through the supplementary service identification information. In step S607, the additional service device 230 searches the reception rejection list mapped to the identification information of the called terminal 402 to determine whether the identification number corresponding to the identification information of the calling terminal 401 is registered in the reception rejection list Can be confirmed. Accordingly, the supplementary service device 230 transmits an inquiry response message to the supplementary service controller 110 in response to the inquiry request message in step S609. The inquiry response message indicates whether the identification number of the calling terminal 401 is registered in the reception rejection list of the called terminal 402. [ According to the MAP, the inquiry response message can use the service request rrl (return result) message. Here, it is assumed that the identification number of the calling terminal 401 is registered in the reception rejection list of the called terminal 402. [ Accordingly, the supplementary service controller 110 receiving the inquiry response message proceeds with the process of providing the individual call rejection service.

According to the individual call reception rejection service, it is possible to provide a guidance broadcast to guide the calling terminal 401 that the reception is denied. The supplementary service controller 110 proceeds with the procedure for connecting the session between the media device 160 and the calling terminal 401 in cooperation with the media device 160 in order to provide the calling terminal 401 with the announcement . That is, the supplementary service controller 110 transmits a broadcast session connection request message to the session controller 120, requesting a session connection between the media device 160 and the calling terminal 401 in step S611. This is for the media device 160 to provide the announcement to the calling terminal 401. Here, the broadcast session connection request message can use the INVITE message according to the SIP. The session controller 120 receiving the INVITE message forwards the INVITE message to the media device 160 in step S613.

Upon receiving the INVITE message, the media device 160 transmits a 200 OK message to the session controller 120 in step S615. Here, the 200 OK message is a broadcast session connection acceptance message meaning accepting a session connection with the calling terminal 401. The session controller 120 forwards the 200 OK message to the supplementary service controller 110 in step S617.

Upon receiving the 200 OK message, the access point controller 110 transmits an ACK message to the session controller 120 in step S619, and the session controller 120 transmits an ACK message to the media device 160 in step S621. Here, the ACK message is a broadcast session connection acknowledgment message informing that the session connection acceptance for broadcasting has been confirmed.

After transmitting the ACK message, the AMS controller 110 transmits an 183 SessionProgress message to the session controller 120 in step S623. The session controller 120 transmits a 183 SessionProgress message to the calling terminal 401 in step S625. . The 183 SessionProgress message is a response to the INVITE message transmitted by the calling terminal 401 in step S601, and is a session progress message informing that the session establishment procedure is in progress.

After transmitting the 183 SessionProgress message, the supplementary service controller 110 transmits the INFO message to the session controller 120 in step S627, and the session controller 120 transmits the INFO message to the media device 160 in step S629 . The INFO message is a broadcast instruction message for instructing the media device 160 to broadcast announcement.

In step S631, the media device 160 that has accepted the broadcast instruction message transmits a 200 OK message to the session controller 120. [ Then, the session controller 120 forwards the 200 OK message to the supplementary service controller 110 in step S633. Here, the 200 OK message is a broadcast acceptance message informing that broadcast announcement will be performed in response to the broadcast indication message. After transmitting the broadcast admission message, the media device 160 provides announcement broadcast to the calling terminal 401 in step S635. This announcement broadcast informs the calling terminal 401 that the reception is rejected.

7, the media device 160 transmits the INFO message to the session controller 120 in step S637 after ending the announcement broadcast, and the session controller 120 transmits the INFO message to the supplementary service controller 120 in step S639 110). Here, the INFO message is an end notification message informing that announcement is terminated.

In step S641, the supplementary service controller 110 transmits a 200 OK message to the session controller 120 in response to the INFO message. Then, the session controller 120 delivers the 200 OK message to the media device 160 in step S643. Here, the 200 OK message is an end confirmation message informing that the broadcasting guide end is confirmed.

After transmitting the termination confirmation message, the supplementary service controller 110 transmits a 487 RequestTerminated message to the session controller 120 in step S645. Then, the session controller 120 forwards the 487 RequestTerminated message to the calling terminal 401 in step S647. The calling terminal 401 transmits a session connection request message in step S601, and the 487 RequestTerminated message is a session connection rejection message indicating that the request is not accepted for the INVITE message, which is a session connection request message.

Upon receiving the session connection rejection message, the calling terminal 401 transmits an ACK message to the session controller 120 in response to the 487 RequestTerminated message in step S649. Then, the session controller 120 transmits an ACK message to the supplementary service controller 110 in step S651. Here, the ACK message is a session connection refusal confirmation message informing that the session connection refusal has been confirmed in response to the session connection refusal message.

Upon receiving the session connection rejection confirmation message, the supplementary service controller 110 transmits a BYE message to the session controller 120 in step S653 to terminate the connection of the broadcast session. The session controller 120 delivers the BYE message to the media device 160 in step S655. Here, the BYE message is a broadcast session connection termination message informing the end of the session connection for broadcasting.

In response to the BYE message, the media device 160 having received the broadcast session connection termination message transmits a 200 OK message to the session controller 120 in step S657. Then, the session controller 120 forwards the 200 OK message to the supplementary service controller 110 in step S659. Here, the 200 OK message is a broadcast session connection end acceptance message informing that the broadcast session connection end is accepted. The session connection between the media device 160 and the calling terminal 401 is terminated.

8 is a flowchart illustrating a method for providing an individual call rejection service of an additional service controller according to an embodiment of the present invention.

8, the additional service controller 110 may receive an INVITE message requesting a session connection for a call with the calling terminal 402 of the calling terminal 401 in step S801. The supplementary service controller 110 may receive the INVITE message transmitted by the calling terminal 401 from the session controller 120. [

In step S803, the additional service controller 110 determines whether the called terminal 402 is subscribed to the individual call rejection service through the INVITE message.

If it is determined in step S803 that the called terminal 402 is not subscribed to the individual call reception rejection service, the supplementary service controller 110 relays the SIP message to the called terminal 402 according to a general session connection procedure in step S805 . On the other hand, if it is determined in step S803 that the called terminal 402 is subscribed to the individual call reception rejection service, the supplementary service controller 110 proceeds to step S807 and performs a procedure for providing the individual call reception rejection service .

The reception reject list may be stored in at least one of the supplementary service controller 110 and the supplementary service device 230. [ Accordingly, the supplementary services controller 110 determines in step S807 which of the reception rejection list of the supplementary service device 230 and its own reception reject list to inquire.

As a result of the determination in step S807, in the case of using the additional service device 230, the additional service controller 110 determines whether the identification number of the calling terminal 401 is received by the receiving terminal 402 through the additional service device 230 in step S809 It inquires whether it is registered in the rejection list or not. This is done through the exchange of inquiry request messages and inquiry response messages. The inquiry request message includes supplementary service identification information for distinguishing the subscribed individual call reception rejection service from other supplementary services, originating terminal identification information and calling terminal identification information extracted from the session connection request message. Also, the inquiry response message describes whether or not the identification number corresponding to the calling terminal identification information is registered in the reception rejection list corresponding to the called terminal identification information.

On the other hand, if the supplementary service device 230 is not used in accordance with the determination in step S807, the supplementary service controller 110 transmits the identification number of the calling terminal 401 through the reception rejection list stored in itself in step S811 It is inquired whether or not it is registered in the reception rejection list of the terminal 402. [

In step S813, the additional service controller 110 checks whether the identification number of the calling terminal 401 is registered in the reception reject list according to the inquiry of step S809 or S811 described above.

As a result of checking in step S813, if it is not the identification number registered in the reception rejection list, the supplementary service controller 110 relays the SIP message to the reception terminal 402 according to a general session connection procedure in step S805. On the other hand, if it is determined in step S813 that the identification number is an identification number registered in the reception rejection list, the supplementary service controller 110 provides an announcement to the calling terminal 401 through the media device 160 in step S815 do. That is, the supplementary service controller 110 interlocks with the media device 160, connects the session between the media device 160 and the calling terminal 401, and instructs the media device 160 to inform the calling terminal 401 Instructs to provide the broadcast.

In step S817, the ASSC 110 transmits a 487 RequestTerminated message, which is a session connection rejection message indicating that the request is not accepted, to the INVITE message, which is a session connection request message, Rejects the session connection request for the session 402. That is, in step S801, the ASSC 110 transmits a 487 RequestTerminated message to the INVITE message in response to the received INVITE message instead of the called terminal 402, thereby notifying that the session connection request of the calling terminal 401 is not accepted . According to the embodiment of the present invention as described above, when the calling terminal 401 having the identification number previously registered in the reception rejection list of the called terminal 402 requests session connection, the additional service controller 110 rejects it . Then, the supplementary service controller 110 provides a guidance broadcast to guide the rejection of the session connection through the media device 160, so that the user of the calling terminal 401 can know that the reception is rejected, The user of the mobile station 401 may not make unnecessary attempts to continue to make a call connection.

According to the embodiment of the present invention as described above, the supplementary service controller 110 exists in the IMS network, which is the packet network 100, to provide the supplementary service, that is, the individual call rejection service. The supplementary service controller 110 can provide the individual call rejection service in cooperation with the supplementary service device 230 providing the individual call rejection service in the circuit network 200. [ The additional service device 230 may store a reception rejection list for providing the individual call rejection service. In this way, by sharing the reception rejection list with the circuit network 200, it is possible to continuously and jointly provide the individual call reception rejection services provided in the circuit network 200 in the packet network 100 as well. Accordingly, in the packet network 100, a terminal 400 receiving a packet-based voice service such as mVoIP, a terminal 400 receiving a voice call service based on a circuit switching scheme in the circuit network 200, It is possible to consistently provide the individual call reception rejection service to the terminal 400 capable of accommodating both the packet and the voice call service based on the circuit exchange method.

The method for providing the individual call rejection service of the supplementary service controller according to the embodiment of the present invention may be implemented in a form of a program readable by various computer means and recorded in a computer readable recording medium. Here, the recording medium may include program commands, data files, data structures, and the like, alone or in combination. Program instructions to be recorded on a recording medium may be those specially designed and constructed for the present invention or may be available to those skilled in the art of computer software. For example, the recording medium may be a magnetic medium such as a hard disk, a floppy disk and a magnetic tape, an optical medium such as a CD-ROM or a DVD, a magneto-optical medium such as a floppy disk magneto-optical media, and hardware devices that are specially configured to store and execute program instructions such as ROM, RAM, flash memory, and the like. Examples of program instructions may include machine language code such as those generated by a compiler, as well as high-level language code that may be executed by a computer using an interpreter or the like. Such a hardware device may be configured to operate as one or more software modules to perform the operations of the present invention, and vice versa.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is evident that many alternatives, modifications, and variations will be apparent to those skilled in the art. It is self-evident to those who have. Furthermore, although specific terms are used in this specification and the drawings, they are used in a generic sense only to facilitate the description of the invention and to facilitate understanding of the invention, and are not intended to limit the scope of the invention.

The present invention relates to a communication system for providing a private call reception rejection service, a packet network for the same, an apparatus therefor, and a method therefor. The additional service controller of the packet network comprises: It is possible to provide a call rejection service. In other words, by using the infrastructure of the circuit network, by providing a private call rejection service for a packet-based voice call in the packet network, it is possible to utilize the database and web resources established for providing additional services in the circuit network. Accordingly, it is possible to reduce the infrastructure cost for providing the individual call rejection service. Further, by using the same database, service continuity and connectivity can be maintained. Accordingly, it is possible to provide a consistent individual call reception rejection service to the user. In addition, it is possible that the user of the terminal whose reception is rejected by providing the announcement to the user of the terminal whose reception is rejected may not continue unnecessary call attempts, thereby saving radio resources. This is not only a possibility of commercialization or sales, but also a possibility of being industrially applicable since it is practically possible to repeatedly carry out clearly.

10: communication module 20: storage module
30: Control module
100: Packet network 110: Additional service controller
120: Session Controller 130: Home Subscriber Device
140: media resource controller 150: media resource processor
160: Media device
200: Circuit network 210: Home location register
220: Intranet gateway 230: Additional service device
300: access network 310: base station
320: base station controller 330: gateway
400: Terminal 401: Originating terminal
402: Incoming terminal 500: Business terminal

Claims (14)

delete A session controller for relaying, to the called terminal, a session connection request message in which a calling terminal requests a session connection for a call with the called terminal;
A media device for providing an announcement informing that the session connection request is not accepted; And
Upon receipt of the session connection request message, inquires the reception reject list having at least one identification number for rejecting reception of the reception terminal stored therein and the reception reject list stored in the additional service device of the circuit network, And an additional service controller for instructing the media terminal to provide the announcement broadcast to the calling terminal if the identification number of the terminal is registered in any one of the two reception rejection lists Packet network for providing. delete delete delete delete delete A communication module for receiving a session connection request message for requesting session connection between a calling terminal and a called terminal;
A storage module for storing a reception reject list having at least one identification number for which the receiver terminal rejects reception; And
A reception deny list stored in the storage module and a reception denied list stored in an additional service device of the circuit network, and if the identification number of the calling terminal is registered in any one of the two reception rejection lists, And a control module for instructing the communication module to provide an announcement guiding reception rejection to the subscriber station through the communication module. 9. The apparatus of claim 8, wherein the control module
Transmits an inquiry request message for inquiring a reception rejection list stored in an additional service device of the circuit network through the communication module, receives an inquiry response message responding to the inquiry request message transmitted, Whether the identification number of the calling terminal is registered in the reception rejection list. delete Receiving a session connection request message for a calling terminal to request a session connection for a call with the called terminal;
Inquiring whether the identification number of the calling terminal is registered in the reception rejection list of the called terminal from the reception reject list stored in the additional service device of the circuit network and the reception reject list stored in the supplementary service controller of the packet network; And
And instructing the media device to provide an announcement broadcast to the calling terminal indicating that the reception is rejected if the identification number of the calling terminal is registered in any one of the two types of blocked reception lists as a result of the inquiry Wherein the method comprises the steps of: 12. The method of claim 11,
Further comprising: transmitting a session connection rejection message informing that the session connection request through the session connection request message can not be received to the calling terminal. Way. 13. The method of claim 12,
Wherein the session connection request message is an INVITE message according to SIP and the session connection rejection message is a 487 RequestTerminated message. 12. The method of claim 11, wherein the querying comprises:
And transmits the inquiry request message requesting the inquiry to the supplementary service apparatus when the inquiry of the inquiry list is received from the supplementary service apparatus and provides the inquiry result in response to the inquiry request message, And a response message is received from the additional service controller.

Images