KR101395598B1 - Communication packet switched network for presenting particular tone of wireless service provider, apparatus thereof and method thereof - Google Patents

Abstract

The present invention relates to a packet network for providing a service provider identification sound, an apparatus therefor, and a method therefor. The present invention relates to an additional service device for storing a sound source code corresponding to a service provider identification sound, Including a circuit network; And a session connection request message for requesting a session connection for a call from the calling terminal to the calling terminal, the calling terminal transmits a service provider identification sound of the network provider, to which the called terminal belongs, to the calling terminal, And a packet network for providing a calling party with a service provider identification tone of a network operator to which the calling terminal and the called terminal are commonly subscribed. The present invention also provides an apparatus and a method for controlling a display device.

Description

Technical Field [0001] The present invention relates to a packet network for providing a service provider identification tone, a device for the same, and a packet network for providing a service provider identification sound,

The present invention relates to a technology for providing an additional service in a communication system, and more particularly, to a technology for providing a service provider identification sound that can provide a sound source unique to a network provider to a calling terminal prior to a session connection for a call between the calling terminal and the called terminal A packet network for the same, 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 terminal requesting the call outputs a ring back tone until the called party accepts the call. The user requesting the call can know that the ring tone is being output to the other party's terminal by the ringback tone. Therefore, the user requesting the call expects the other party to receive the call and concentrates the end of the ringback tone I wait. There is a need for a method that can utilize the time for outputting the ring back tone to the position of the network operator instead of the position of the individual.

SUMMARY OF THE INVENTION Accordingly, the present invention has been made keeping in mind the above problems occurring in the prior art, and it is an object of the present invention to provide a packet network for providing a calling terminal with a service provider identification sound, which is a sound source unique to a network operator before a session for call between a calling terminal and a called terminal is connected, And a method for the same.

It is a further object of the present invention to provide a method and system for providing a service provider identification sound, which is a sound source unique to a network provider, before a call session between a calling terminal and a called terminal is established in a packet network, when a calling terminal and a called terminal are subscribed to the same network provider A packet network for providing the packet to the calling terminal, an apparatus therefor, and a method therefor.

Yet another object of the present invention is to provide a packet network for providing a calling terminal with a service provider identification sound, which is a sound source unique to a network provider, before a session for call between a calling terminal and a called terminal is connected in a packet network, , An apparatus therefor and a method therefor.

According to another aspect of the present invention, there is provided a packet network for providing a service provider identification tone, the calling network relaying a session connection request message requesting a session connection with a called terminal to the called terminal Session controller; A media device for providing a calling terminal with a carrier identification sound, which is a sound source unique to a network provider; And confirming whether the calling terminal or the called terminal is subscribed to a service provider's beep service upon receiving the session connection request message. When the calling terminal is subscribed to the service provider's voice service, A subscriber who has subscribed to the service, acquires the tone generator code corresponding to the calling terminal, transmits the obtained tone generator code to the media device, and provides the calling terminal with the operator identification tone according to the acquired tone generator code And a service controller.

delete

According to another aspect of the present invention, there is provided an additional service controller for providing a service provider identification sound, comprising: a communication module for receiving a session connection request message for requesting session connection between a calling terminal and a called terminal; And if the calling terminal is subscribed to the service provider identification sound service, if the called terminal is a terminal subscribed to the same network provider as the calling terminal, the calling terminal obtains a tone source code corresponding to the calling terminal, And a control module for transmitting to the media device through the module and providing the calling terminal with a service provider identification sound according to the obtained tone generator code.

delete

delete

delete

delete

delete

delete

delete

delete

Wherein the control module acquires a sound source code corresponding to the called terminal when the called terminal subscribes to the service provider identification sound service, transmits the obtained sound source code to the media device via the communication module, To the calling terminal.

The control module transmits a sound source code request message requesting the sound source code to an additional service device of a circuit network storing a list of sound source codes through the communication module, And receiving the code response message to obtain the tone generator code.

Wherein the additional service controller further comprises a storage module for storing a tone generator code list which is a list of the tone generator codes, wherein the control module inquires a tone generator code list stored in the storage module and acquires the tone generator code do.

According to another aspect of the present invention, there is provided a method for providing a service provider identification sound of an additional service controller, the method comprising the steps of: receiving a session connection request message from a calling terminal, ; Checking whether the calling terminal or the called terminal joins the service provider's beep service from the session connection request message; Determining whether the called terminal is a terminal subscribed to the same network operator as the calling terminal when the calling terminal is subscribed to the service provider identification sound service; If it is determined that the called terminal is a terminal subscribed to the same network operator as the calling terminal, acquiring a tone generator code corresponding to the calling terminal; And a ring back tone session connection request message requesting a session connection between the calling terminal and the media device, including the obtained tone generator code, to the media device, and transmitting a provider identification sound according to the acquired tone generator code to the calling terminal And providing the data.

Acquiring a tone generator code of a business entity identification sound corresponding to the called terminal when the called terminal subscribes to the business entity identification tone service as a result of the checking; And transmitting the ringback tone session connection request message requesting a session connection between the calling terminal and the media device to the media device, wherein the calling terminal transmits the ringback tone session connection request message to the media terminal, And providing the user with a password.

According to the present invention, when a general ring back tone is output before a session for a call between a calling terminal and a called terminal is connected, a company identification sound, which is a sound source unique to a provider instead of a ring back tone, . In particular, since the call is made with the end of the ring back tone, the user is intensively listening to the ring back tone. Therefore, as in the embodiment of the present invention, when the output of the ring back tone is performed, the operator identification sound is provided, and the effect of the advertisement is excellent.

Also, when the calling terminal and the called terminal are subscribed to the same network provider, by providing the calling terminal with the operator identification sound, the calling terminal user can know that the user of the called terminal is subscribed to the same network operator. In addition, if there is such a benefit as a discount of a call charge given when a call is made between terminals of the same network provider, the user of the calling terminal can indirectly know this.

The packet network can utilize the resources established for providing additional services in the circuit network by providing the service provider identification sound service with reference to the sound source code list of the called terminal stored in the circuit network. As a result, the infrastructure cost for providing additional services can be reduced.

BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a diagram illustrating a communication system configuration for providing a provider identification sound according to an embodiment of the present invention; FIG.
2 is a diagram illustrating a configuration of an additional service controller for providing a provider identification sound according to an embodiment of the present invention;
FIG. 3 and FIG. 4 are flowcharts for explaining a method for providing a provider identification sound according to the first embodiment of the present invention; FIG.
5 and 6 are flowcharts illustrating a method for providing a provider identification sound according to a second embodiment of the present invention.
7 and 8 are flowcharts for explaining a method for providing a provider identification sound according to a third embodiment of the present invention.
9 and 10 are flowcharts for explaining a method for providing a provider identification sound according to a fourth embodiment of the present invention.
FIG. 11 is a flowchart illustrating a method for providing a service provider identification sound service of an additional service controller according to an embodiment of the present invention. FIG.

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 illustrating a configuration of a communication system for providing a service provider identification sound according to an embodiment of the present invention. Referring to FIG.

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, and a terminal 400 .

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. [ Each terminal 400 has identification information, and the identification information is information for distinguishing the terminal 400 from the other terminals 400. For example, the identification information may be the telephone number of the terminal 400. The identification information is a URI (Uniform Resource Identifier) of the calling terminal 401 or the called terminal 402 described in the SIP message when a message according to SIP (Session Initiation Protocol) Can be used as the identification information.

The packet network 100 may 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 SIP, the allocation of resources is performed through a 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 may provide a service provider identification sound service and a coloring service as an additional service. The operator identification sound is a sound source specific to the network operator, and the network operator is a company that operates the packet network 100 and the circuit network 200 according to the embodiment of the present invention. The service provider identification sound service is an additional service for providing a provider identification sound instead of a ringback tone reproduced by the calling terminal 401 prior to the call connection if there is a call connection request of the calling terminal 401. [ Coloring is a variety of sound sources, and is provided as a file in multimedia format. The coloring service is an additional service for providing the calling terminal 401 with coloring instead of the ring back tone before the call connection if there is a call connection request from the calling terminal 401. [

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 manner, the access network 300 includes a base station 310, a base station controller 320, a gateway 330, and the like. Accordingly, the access network 300 can provide a wireless section service between the base station 310 and the terminal 400 to allow the terminal 400 to access 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 through the access point to the terminal 400, so that the terminal 400 can access the packet network 100. [ As described above, the terminal 400 that can use the access network 300 can access the packet network 100 through the corresponding 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.

Hereinafter, it will be assumed that the packet network 100 is an 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 (MRF, Multimedia Resource Function, 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 additional service controller 110 is an entity for providing additional services. In order to provide the additional service, the additional service controller 110 can confirm the type of the additional service to which the calling terminal 401 or the called terminal 402 subscribes. The supplementary service controller 110 can provide supplementary services to the calling terminal 401 or the called terminal 402 depending on the type of the supplementary service to which the calling terminal 401 or the called terminal 402 subscribes. That is, when the calling terminal 401 or the called terminal 402 subscribes to the provider identification sound service or the coloring service, the additional service controller 110 causes the media device 160 to transmit the provider identification sound or coloring to the calling terminal 401 ). ≪ / RTI > Accordingly, the supplementary service controller 110 can cause a session to be connected between the calling terminal 401 and the media device 160, in order to provide the calling terminal 401 with a carrier identification tone or coloring.

The supplementary service controller 110 may also be configured to provide a service provider identification tone or coloring corresponding to the calling terminal 401 or the called terminal 402, And provides the code to the media device 160. At this time, the additional service controller 110 can inquire and obtain the tone source code from the tone source code list stored by the additional service controller 110 itself, or inquire the additional service device 230 to acquire the tone source code. Therefore, the additional service controller 110 transmits a tone generator code request message requesting a tone generator code to the additional service apparatus 230, receives a tone generator response message from the additional service apparatus 230, A sound source code can be obtained.

The additional service controller 110 can confirm the type of the additional service to which the terminal 400 subscribes through the home subscriber unit 130 or the home location register 210. In particular, the supplementary service controller 110 may utilize the service profile of the home subscriber device 130 of the packet network 100 to confirm whether the provider identification sound service or the coloring service is subscribed. 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. In addition, the supplementary service controller 110 may receive and store the service profile from the home location register 210, and then verify the stored 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. For example, the supplementary service controller 110 may provide a provider identification sound service when an item corresponding to the provider identification sound service is activated in the service profile. In addition, the additional service controller 110 can not provide the service provider identification sound service when an item corresponding to the service provider identification sound service is deactivated 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 a message transmitted from the terminal 400. The session controller 120 may forward a message to each entity in the packet network 100 to provide a service as requested by the terminal 400, thereby completing the session. 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 exchanged between the calling terminal 401, the called terminal 402, the attached service controller 110, and the media device 160 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, 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, a ring backtone session connection request for requesting a session connection for announcement of the media device 160 Message. ≪ / RTI >

The ACK message is a method used as a response indicating that the final device receiving the specific SIP message finally confirmed the specific SIP message. Therefore, the ACK message can be used for acknowledging the RBT session connection acceptance (200 OK) message as the RBT session connection acknowledgment message. In addition, the ACK message may be used as a session connection acknowledgment message informing that it confirms it in response to the session connection acceptance (200 OK) message.

Among the SIP messages, the 1xx series message (where xx is a natural number) is a kind of response message, which receives a specific request message and is used to notify that the 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. The 180 Ringing message may be used as a session connection request confirmation message indicating that a ring tone is being output from the terminal that has received the current INVITE message. Meanwhile, the supplementary service controller 110 stops delivering a session connection request (INVITE) message to the called terminal 402 in order to provide a provider identification sound to the calling terminal 401, And send a SessionProgress message to the calling terminal 401. In particular, the 183 SessionProgress message is a message indicating that the session is still in progress. The supplementary service controller 110 may continue the procedure for proceeding with the session connection between the media device 160 and the calling terminal 401 instead of the session connection for voice communication by transmitting the 183 SessionProgress message. Thus, the 183 SessionProgress message can be used as a session progress message to indicate that the session is still in progress.

Among the SIP messages, the 2xx series message (where xx is a natural number) is used as a response message to inform 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 ring back tone session connection accept message accepting a session connection with the calling terminal 401 in response to a ring back tone session connection request (INVITE) message. In addition, the 200 OK message may be used as a session connection acceptance message to indicate acceptance of a session connection in response to a session connection request (INVITE) message. The 200 OK message may be used as a ring back tone session release acceptance message informing that the session termination is accepted between the calling terminal 401 and the media device 160 in response to the ring back tone session release (BYE) message.

The BYE message is a method used to end various sessions. Therefore, the BYE message can be used as a ringback session disconnect message for requesting to release the session connection between the calling terminal 401 and the media device 160.

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 includes a multimedia resource controller 140 and a multimedia resource processor 150. When a session between the media device 160 and the calling terminal 401 is connected to the multimedia resource controller 140, the multimedia resource controller 140 controls the multimedia resource processor 150 according to the sound source code received from the additional service controller 110, To the calling terminal 401. [0064] Accordingly, the multimedia resource processor 150 may provide a provider identification tone or coloring through a session connected to the calling terminal 401 under the control of the multimedia resource controller 140. In particular, the media device 160 stores a business entity identification tone or coloring corresponding to the tone source code, and provides the business entity identification tone or coloring to the calling terminal 401 according to the corresponding tone source code. The media device 160 then provides the calling party's identification tone to the calling terminal 401 prior to coloring or general ringback tone. 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 a call forwarding, a voice message, a service provider identification sound, and a coloring service. 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. When the item is activated, the service can be provided. If the item is inactivated, the service can not be provided.

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 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 service profile required by 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 additional service controller 110 can inquire the sound source code to the additional service device 230 through the intranet gateway 220. [

The additional service device 230 may be implemented using a CRBT (Color Ring Back Tone) device for the calling terminal 402 to provide a provider identification tone and a coloring service to the calling terminal 401. The supplementary service device 230 stores the tone generator code list and can receive the tone generator code request message from the supplementary service controller 110. The sound source code request message is a request for a sound source code of a provider identification sound or coloring corresponding to the calling terminal 401 or the called terminal 402. In response to the received tone generator code request message, the additional service device 230 searches for a tone generator code corresponding to the operator identification tone or coloring from the tone generator code list, and then transmits the tone generator code response message including the searched tone generator code to the supplementary service controller (110).

2 is a diagram for explaining a configuration of an additional service controller for providing a provider identification sound 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 a tone generator code list including at least one tone generator code. The sound source code is identification information mapped to each of the carrier identification sound and the coloring, and the sound source code is mapped and stored in the terminal 400 subscribed to the service provider identification sound service or the coloring service. Accordingly, the corresponding sound source code can be searched through the identification information of the calling terminal 401 or the called terminal 402, and the additional service identification information indicating the provider identification sound service or the coloring service. In addition, the storage module 20 may store a service profile received from the home location register 210 and a 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 the service provider identification sound service in the supplementary service controller 110. For this purpose, the control module 30 can generate various messages required for the service provider identification sound 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 transmits the session connection request message to the calling terminal 401, which has transmitted the session connection request message, One additional service can be confirmed. At this time, the control module 30 receives and stores the service profile of the home location register 210 through the communication module 10, and then searches for the stored service profile, or interworks with the home subscriber device 130, (401) or the called terminal (402). According to this method, the control module 30 can confirm whether the calling terminal 401 or the called terminal 402 joins the service provider identification sound service or the coloring service.

The control module 30 may generate a tone generator code 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 extracted calling terminal identification information and the called terminal identification information in the sound source code request message. The control module 30 may include supplementary service identification information that can distinguish the provider identification sound service or the coloring service to which the calling terminal 401 or the receiving terminal 402 is subscribed from the additional service in the sound source code request message . The control module 30 transmits the tone generator code request message to the additional service device 230 of the circuit network 200 through the communication module 10. The control module 30 may acquire the tone generator code from the tone generator code response message in response to the tone generator code request message. At this time, the control module 30 can obtain the tone generator code corresponding to the calling terminal 401 through the calling terminal identification information, and obtain the tone generator code corresponding to the called terminal 402 through the called terminal identification information. Also, the control module 30 can obtain the tone generator code corresponding to the operator identification sound through the supplementary service identification information indicating the service provider identification tone service, and generates the tone generator code corresponding to the coloring through the additional service identification information indicating the coloring service Can be obtained.

When the control module 30 acquires the tone generator code, the control module 30 transmits the obtained tone generator code to the media device 160 together with the session connection request between the media device 160 and the calling terminal 401. Accordingly, when a session is established between the media device 160 and the calling terminal 401, the media device 160 can provide the calling terminal 401 with a company identification sound corresponding to the sound source code.

3 and 4 are flowcharts for explaining a method for providing a provider identification sound according to the first embodiment of the present invention.

3 and 4, the service provider identification sound service is an additional service provided by the called party, and therefore the session controller 120 and the supplementary service controller 110 can identify the entity located in the packet network 100 connected to the called terminal 402 admit. Although the calling terminal 401 is also shown as belonging to the same packet network 100, the calling terminal 401 may be located in another packet network 100 or may be a terminal located in the circuit network 200, have.

3 and 4, in step S301, 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. [ The session connection request message may be an INVITE message according to the SIP. In step S303, the session controller 120 receiving the session connection request (INVITE) message delivers the INVITE message to the supplementary service controller 110. [

After receiving the session connection request (INVITE) message, the supplementary service controller 110 confirms the supplementary service subscribed by the called terminal 402 described in the reception object in the INVITE message in step S305. In particular, the supplementary service controller 110 confirms whether it is subscribed to the provider identification sound service and the coloring service. The session connection request (INVITE) message includes a To header, and the supplementary service controller 110 can identify the called terminal 402 through the URI described in the To header. Then, the supplementary service controller 110 confirms whether the identified called terminal 402 is subscribed to the provider identification sound service and the coloring service. Here, it is assumed that the called terminal 402 is subscribed to both the provider identification sound service and the coloring service. Then, in step S307, the additional service controller 110 inquires of the sound source code list stored in the sound source code of the carrier identification sound and coloring that is mapped to the receiving terminal 402, and acquires the sound source code that is searched. The carrier identification sound and coloring have a unique sound source code distinguished from other carrier identification sounds and coloring, and the corresponding company identification sound and coloring can be obtained from the sound source code.

Next, the supplementary service controller 110 proceeds with the session connection procedure with the media device 160 to provide the calling terminal 401 with the carrier identification tone and coloring mapped to the tone source code. This is explained as follows.

In step S309, the supplementary service controller 110 transmits a ringback tone session connection request message including the acquired tone generator code to the session controller 120 (S307). The ringback tone session connection request message is a message requesting the calling terminal 401 to connect a session with the calling terminal 401 to the media device 160 in order to provide carrier identification tone and coloring. In addition, the RBT session connection request message is a message including a sound source code, and requests the media device 160 to provide a corresponding company identification sound and a ring back tone. The RBT session connection request message can use an INVITE message according to the SIP. Then, the session controller 120 delivers the INVITE message to the media device 160 in step S311.

Upon receiving the ring back tone session connection request (INVITE) message, the media device 160 transmits a ring back tone session connection acceptance message to the session controller 120 in step S313. Here, the RBT session connection accept message is a message in which the media device 160 accepts a session connection with the calling terminal 401 in response to a ring back tone session connection request (INVITE) message. The RBT session connection accept message may use the 200 OK message according to SIP. Then, the session controller 120 forwards the RBT session connection acceptance (200 OK) message to the supplementary service controller 110 in step S315.

After receiving the 200 OK message, the supplementary service controller 110 transmits a session advance message to the session controller 120 in step S317. The session progress message is used to inform the calling terminal 401 that the session procedure is still in progress. In addition, the session advance message informs the calling terminal 401 that the session connection for providing the provider identification tone and the ring back tone is in progress. The Session Progress message may use the 183 SessionProgress message according to the SIP. That is, the ASSC 110 transmits the 183 SessionProgress message in response to the received INVITE message (S303). Upon receiving the 183 SessionProgress message, the session controller 120 delivers the 183 SessionProgress message to the calling terminal 401 in step S319. The calling terminal 401 receiving the 183 SessionProgress message can confirm that the session establishment procedure is still in progress. Upon receiving the session progress message (183 Session Progress), the calling terminal 401 does not proceed any other procedure to proceed if the session connection is delayed or failed, such as a retransmission of a session connection request (INVITE) message.

In step S321, the AMS controller 110 transmits a ring back tone session connection acknowledgment message to the session controller 120. [ The RBT session connection acceptance confirmation message is a message informing that the final connection to the session connection for providing the service provider identification sound and the ring back tone is confirmed. The RBT session connection acknowledgment message is a response message corresponding to the RBT session connection acceptance (200 OK) message. This RBT session connection acknowledgment message preferably uses an ACK message according to the SIP. Then, in step S323, the session controller 120 transmits a ring back tone session connection acknowledgment (ACK) message to the media device 160. [

When the media device 160 receives the ACK message, a session is established between the calling terminal 401 and the media device 160. In step S325, the media device 160 provides the calling terminal 401 with a carrier identification tone and coloring that are mapped to the tone source code of the called terminal 402. [ The media device 160 previously received the tone generator code mapped to the called terminal 402 through the RBT session connection request message (step S311). Therefore, the media device 160 may provide the calling terminal 401 with a service provider identification tone and coloring that are mapped to the sound source code received previously through the connected session. In particular, in step S325, the media device 160 transmits the service provider identification sound before transmitting the coloring service, and reproduces the service provider identification sound. That is, the media device 160 can reproduce the coloring after reproducing the provider identification sound through the connected session. Accordingly, the user of the calling terminal 401 can confirm the operator identification sound and know the network operator to which the called terminal 402 subscribes.

In step S327, the ASSC 110 transmits the received INVITE message to the session controller 120 (S303). Then, the session controller 120 delivers the INVITE message to the called terminal 402 in step S329.

The called terminal 402 receiving the INVITE message outputs a ring tone to inform the user of the called terminal 402 that there is a session connection request, that is, a call request. In step S331, the called terminal 402 receives a session connection request (INVITE) message, and transmits a session connection request confirmation message to the session controller 120 informing that the ring tone is being output from the called terminal 402. [ Lt; / RTI > The session connection request confirmation message preferably uses the 180 Ringing message according to the SIP. The 180 Ringing message transmitted from the called terminal 401 is transmitted to the calling terminal 401 via the session controller 120, the additional service controller 110 and the session controller 120 in steps S333 and S337. The service controller 110, the session controller 120 and the calling terminal 401 that have received the 180 Ringing message in steps S331 to S337 can know that the calling terminal 401 is currently outputting a ring tone.

By the output of the ring tone, the user of the called terminal 402 can know that there is a call request, so that the user can accept the call. Upon detecting a hook-off for accepting the user's call, the called terminal 402 transmits a session connection acceptance message to the session controller 120 in step S339. The session connection acceptance message is a response to the session connection request (INVITE) message, and is a message for informing that the user of the receiving terminal 402 has accepted the session and accepts the session connection. The session connection acceptance message may use a 200 OK message, depending on the SIP. Subsequently, the session controller 120 delivers the 200 OK message to the supplementary service controller 110 in step S341.

Upon receiving the session connection acceptance (200 OK) message, the additional service controller 110 transmits a session connection between the calling terminal 401 and the media device 160 for session connection between the calling terminal 410 and the called terminal 402 It can be seen that it must be released. Accordingly, the supplementary services controller 110 transmits a ring back tone session release message to the session controller 120 in step S343. The RBT session release message is a message for requesting the release of a session between the calling terminal 401 and the media device 160, and it is preferable to use the BYE message according to the SIP. Then, the session controller 120 delivers a ring back tone session disconnect (BYE) message to the media device 160 in step S345. Accordingly, the media device 160 ends the reproduction of the carrier identification sound or the coloring in step S347. Then, at step S349, the media device 160 transmits a ring back tone session disassociation acceptance message to the session controller 120. [ The RBT session unacknowledge message is a message for notifying that the RBT session acceptance message is accepted for releasing the session connected between the calling terminal 401 and the media device 160 in response to the RBT session disconnect (BYE) message. The RBT session unassociation accept message may use the 200 OK message according to the SIP. Then, in step S351, the session controller 120 forwards the RBT session disconnection acceptance (200 OK) message to the supplementary service controller 110. [ As the additional service controller 110 receives the 200 OK message, the session connection between the calling terminal 401 and the media device 160 is released.

Upon receipt of the 200 OK message, the additional service controller 110 can recognize that the session connection between the calling terminal 401 and the media device 160 is released. Accordingly, the additional service controller 110 delivers the received session connection acceptance (200 OK) message to the session controller 120 in step S353 (S341). Then, in step S355, the session controller 120 transmits a session connection acceptance (200 OK) message to the calling terminal 401.

Upon receiving the session connection acceptance (200 OK) message, the calling terminal 401 forwards the session connection acceptance confirmation message to the session controller 120 in step S357. The session connection acceptance confirmation message is used to confirm that the session connection acceptance (200 OK) message is received in response to the session connection acceptance (200 OK) message. The session connection acceptance confirmation message can use an ACK message according to the SIP. The session connection acknowledgment (ACK) message transmitted from the calling terminal 401 is transmitted to the called terminal 402 via the session controller 120, the additional service controller 110 and the session controller 120 in steps S359 to S363 do. Thereby, a session is connected between the calling terminal 401 and the called terminal 402. Accordingly, the calling terminal 401 and the called terminal 402 can communicate through the mutually connected session in step S365.

5 and 6 are flowcharts for explaining a method for providing a provider identification sound according to a second embodiment of the present invention.

5 and 6, the service provider identification sound service is an additional service provided by the called party, so that the session controller 120 and the supplementary service controller 110 can identify the entity located in the packet network 100 connected to the called terminal 402 admit. Although the calling terminal 401 is also shown to belong to the same packet network 100 as shown in the figure, the calling terminal 401 may be located in another packet network 100 or may be located in the circuit network 200 ).

Referring to FIGS. 5 and 6, the calling terminal 401 transmits a session connection request message to the session controller 120 in step S501, and requests a call connection with the called terminal 402. FIG. 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 S503.

After receiving the session connection request (INVITE) message, the supplementary service controller 110 confirms the supplementary service subscribed by the called terminal 402 described in the reception target in the INVITE message in step S505. In particular, the supplementary service controller 110 confirms whether it is subscribed to the provider identification sound service and the coloring service. The INVITE message includes a To header, and the supplementary service controller 110 can identify the called terminal 402 via the URI described in the To header. Then, the supplementary service controller 110 confirms whether the identified called terminal 402 is subscribed to the provider identification sound service and the coloring service. Here, it is assumed that the called terminal 402 is subscribed to both the provider identification sound service and the coloring service.

After confirming the subscription to the supplementary service, the supplementary service controller 110 transmits a source code request message requesting inquiry of the provider identification sound and coloring source code mapped to the destination terminal 402 in step S507 to the supplementary service device 230 send. The tone generator code request message includes the identification information of the called terminal to request the inquiry of the tone generator code corresponding to the called terminal 402. In addition, it further includes supplementary service identification information that can distinguish each supplementary service in order to request a provider identification sound and a sound source code of coloring. In this embodiment, it is assumed that both the service provider identification sound service and the coloring service are subscribed to. However, in the case of subscribing to any one of the service provider identification sound service and the coloring service, the supplementary service controller 110 transmits, to the sound source code request message, It is possible to transmit only the service identification information.

Upon receiving the tone generator code request message, the additional service device 230 searches for tone generator code mapped to the called terminal 402 from the tone generator code list stored therein. In step S509, the additional service device 230 transmits a sound source code response message containing the corresponding sound source code to the additional service controller 110. [ The supplementary service controller 110 receiving the tone generator code response message can acquire tone generator codes. After acquiring the sound source code according to this method, the additional service controller 110 proceeds to a session connection procedure with the media device 160 to provide the calling terminal 401 with a business identification sound and coloring mapped to the sound source code do. This is explained as follows.

In step S511, the supplementary service controller 110 transmits a ring back tone session connection request message including the sound source code acquired in accordance with the procedure of steps S507 and S509 to the session controller 120. [ The ring back tone session connection request message is a message requesting the media device 160 to connect a session with the calling terminal 401 to provide the calling terminal 401 with a carrier identification tone and a ring back tone. In addition, the RBT session connection request message is a message including a sound source code, and requests the media device 160 to provide a corresponding company identification sound and a ring back tone. The RBT session connection request message can use an INVITE message according to the SIP. Then, in step S513, the session controller 120 delivers a ring back tone session connection request (INVITE) message including the tone generator code to the media device 160. [

When the media device 160 receives a session connection request (INVITE) message, it transmits a ring back tone session connection acceptance message to the session controller 120 in step S515. Here, the RBT session connection accept message is a message in which the media device 160 accepts a session connection with the calling terminal 401 in response to a ring back tone session connection request (INVITE) message. The RBT session connection accept message may use the 200 OK message according to SIP. Then, the session controller 120 forwards the RBT session connection acceptance (200 OK) message to the supplementary service controller 110 in step S517.

After receiving the 200 OK message, the supplementary service controller 110 transmits a session progress message to the session controller 120 in step S519. The session progress message is used to inform the calling terminal 401 that the session procedure is still in progress. In addition, the session advance message informs the originating terminal 401 that a session connection for providing a provider identification tone or a ring back tone is in progress. The Session Progress message may use the 183 SessionProgress message according to the SIP. Therefore, the supplementary service controller 110 transmits the 183 SessionProgress message in response to the received session connection request (INVITE) (S503). Upon receiving the 183 SessionProgress message, the session controller 120 delivers the 183 SessionProgress message to the calling terminal 401 in step S521. The calling terminal 401 receiving the 183 SessionProgress message can confirm that the session establishment procedure is still in progress. Accordingly, the calling terminal 401 does not proceed any other procedure to proceed if the session connection is delayed or failed, such as a retransmission of a session connection request (INVITE) message.

Meanwhile, the supplementary service controller 110 transmits a ring back tone session connection acknowledgment message to the session controller 120 in step S523. The RBT session connection acceptance confirmation message is a message informing that the final connection to the session connection for providing the service provider identification sound and the ring back tone is confirmed. The RBT session connection acknowledgment message is a response message corresponding to the RBT session connection acceptance (200 OK) message. This RBT session connection acknowledgment message preferably uses an ACK message according to the SIP. Subsequently, the session controller 120 delivers a ring back tone session connection acknowledgment (ACK) message to the media device 160 in step S525.

When the media device 160 receives the ACK message, a session is established between the calling terminal 401 and the media device 160. Then, in step S527, the media device 160 provides the calling terminal 401 with a carrier identification tone and coloring that are mapped to the tone source code of the called terminal 402. [ The media device 160 has previously received the tone generator code mapped to the called terminal 402 through a ring back tone session connection request (INVITE) message (step S513). Accordingly, the media device 160 can provide the calling terminal 401 with a business identification tone and coloring that are mapped to the tone source code received previously. In particular, in step S527, it is preferable that the media device 160 transmits and reproduces the provider identification sound prior to transmission of the coloring. That is, the media device 160 reproduces the coloring after reproducing the provider identification sound through the connected session. Accordingly, the user of the calling terminal 401 can confirm the operator identification sound and know the network operator to which the called terminal 402 subscribes.

The subsequent steps, that is, steps S529 to S567 correspond to steps S327 to S365 of the first embodiment, and the detailed description thereof will be omitted.

7 and 8 are flowcharts illustrating a method for providing a provider identification sound according to a third embodiment of the present invention.

7 and 8, the additional service controller 110 is divided into a calling party service controller 111 and a called party service controller 112, and the session controller 120 is connected to the calling session controller 121 and the called session controller 122). The originating service controller 111 and the originating session controller 121 are present in the packet network 100 to which the originating terminal 401 is connected and the originating service controller 112 and the terminating session controller 122 are located in the packet network 100, Is present in the packet network 100 to which the packet network 402 is connected.

7 and 8, in step S701, the calling terminal 401 transmits a session connection request message to the calling session controller 121 to request a call connection with the called terminal 402. [ The session connection request message may be an INVITE message according to the SIP. The originating session controller 121 receiving the INVITE message forwards the INVITE message to the originating service controller 111 in step S703.

After receiving the INVITE message, the originating service controller 111 confirms the supplementary service subscribed by the calling terminal 401 that transmitted the INVITE message in step S705. In particular, the originating service controller 111 confirms whether the originating terminal 401 is subscribed to the provider identification tone service. The INVITE message includes a From header, and in the From header, identification information capable of identifying the calling terminal 401 is described. This identification information may be the URI of the calling terminal 401. [ Therefore, the calling side service controller 111 can identify the calling terminal 401 through the URI described in the From header. Accordingly, the originating service controller 111 confirms whether the identified originating terminal 401 is subscribed to the provider identification tone service. Here, it is assumed that the calling terminal 401 is subscribed to the service provider identification sound service.

The originating service controller 111 includes supplementary service identification information indicating a calling provider identification sound service in order to notify that the calling terminal 401 is subscribed to the provider identification sound service in the P-SVC header of the INVITE message. Then, the originating service controller 111 transmits an INVITE message including the supplementary service identification information to the originating session controller 121 in step S707. The originating session controller 121 delivers the INVITE message to the terminating session controller 122 in step S709. The incoming session controller 122 then forwards the INVITE message to the called party service controller 112 in step S711.

In response to the INVITE message, the service controller 112 confirms the supplementary service to which the calling terminal 401 that transmitted the INVITE message and the called terminal 402 that is the destination of the INVITE message in step S713 subscribed. In particular, the terminating service controller 112 determines whether the originating terminal 401 is subscribed to the provider identification tone service and whether the terminating terminal 402 is subscribed to the coloring service. Here, the service controller 112 of the called party can check whether the calling terminal 401 is subscribed to the provider identification sound service by referring to the additional service identification information of the P-SVC header of the INVITE message. According to the above assumption, the service controller 112 of the called party can know from the INVITE message that the calling terminal 401 is subscribed to the service provider's voice service. Also, the INVITE message includes a To header, and the To header describes identification information capable of identifying the called terminal 402. [ This identification information may be the URI of the called terminal 402. The called party service controller 112 may identify the called terminal 402 via the URI described in the To header. Accordingly, the called party service controller 112 can confirm whether or not the identified called terminal 402 is subscribed to the coloring service. Here, it is assumed that the called terminal 402 is subscribed to the coloring service.

At this time, the service controller 112 of the called party confirms whether the called terminal 402 is a terminal subscribed to the same network operator as the calling terminal 401. Here, it is assumed that the called terminal 402 is a terminal subscribing to the same network operator as the calling terminal 401. [ Accordingly, the service controller 112 of the called party inquires the sound source code of the operator identification sound and coloring in step S715. The service provider controller 112 of the called party can inquire the sound source code from the sound source code list stored therein and then obtain the corresponding sound source code. The carrier identification sound and coloring have unique sound source codes distinguished from other carrier identification sounds or coloring. Therefore, it is possible to obtain the corresponding company identification sound and coloring from the sound source code. After acquiring the tone generator code, the service controller 112 of the called party proceeds with the session connection procedure with the media device 160 to provide the calling terminal 401 with the business entity identification tone and coloring mapped to the tone generator code. This is explained as follows.

The called party service controller 112 transmits a ringback tone session connection request message including the acquired tone generator code to the incoming session controller 122 in step S717 (step S715). The ring back tone session connection request message is a message requesting the calling terminal 401 to connect a session with the calling terminal 401 to the media device 160 in order to provide carrier identification sound or coloring. In addition, the ring back tone session connection request message is a message including a sound source code, and requests the media device 160 to provide a business identification sound or coloring corresponding to the sound source code. The RBT session connection request message can use an INVITE message according to the SIP. The incoming session controller 122 then forwards the ring back tone session connection request (INVITE) message to the media device 160 in step S719.

Upon receiving the INVITE message, the media device 160 transmits a ring back tone session connection acceptance message to the incoming session controller 122 in step S721. Here, the RBT session connection accept message is a message in which the media device 160 accepts a session connection with the calling terminal 401 in response to a ring back tone session connection request (INVITE) message. The RBT session connection accept message may use the 200 OK message according to SIP. The incoming session controller 122 then forwards the ring back tone session connection acceptance (200 OK) message to the caller service controller 112 in step S723.

After receiving the 200 OK message, the service controller 112 of the called party transmits a session advance message in step S725. The transmitted session progress message is transmitted to the calling terminal 401 via the incoming session controller 122, the originating session controller 121, the originating section service controller 111 and the originating session controller 121 in steps S727 to S733 . The session progress message is used to inform the calling terminal 401 that the session procedure is still in progress. In addition, the session advance message informs the originating terminal 401 that a session connection for providing a provider identification tone or a ring back tone is in progress. The Session Progress message may use the 183 SessionProgress message according to the SIP. That is, the service controller 112 of the called party transmits the 183 SessionProgress message in advance in response to the received INVITE (step S711). The calling terminal 401 receiving the 183 SessionProgress message can confirm that the session establishment procedure is still in progress. Accordingly, the calling terminal 401 does not proceed to another procedure in the case of a delay or failure of session connection, such as a retransmission of a session connection request (INVITE) message.

Meanwhile, the called party service controller 112 transmits a ring back tone session connection acknowledgment message to the incoming session controller 122 in step S735. The RBT session connection acceptance confirmation message is a message informing that the final connection to the session connection for providing the service provider identification sound and the ring back tone is confirmed. The RBT session connection acknowledgment message is a response message corresponding to the RBT session connection acceptance (200 OK) message. This RBT session connection acknowledgment message preferably uses an ACK message according to the SIP. The incoming session controller 122 then forwards the ring back tone session connection acknowledgment (ACK) message to the media device 160 in step S737.

When the media device 160 receives the ACK message, a session is established between the calling terminal 401 and the media device 160. In step S739, the media device 160 provides the calling terminal 401 with a carrier identification tone and coloring that are mapped to the tone source code of the called terminal 402. [ The media device 160 has previously received the tone generator code mapped to the called terminal 402 via a ring back tone session connection request (INVITE) message (step S719). Accordingly, the media device 160 can provide the calling terminal 401 with a business identification tone and coloring that are mapped to the tone source code received previously. In particular, in step S739, the media device 160 preferably reproduces the business entity identification sound prior to the coloring reproduction. That is, the media device 160 reproduces the coloring after reproducing the provider identification sound through the connected session. Accordingly, the user of the calling terminal 401 can confirm that the calling terminal 402 is subscribed to the same network operator as the calling terminal 402 by confirming the operator identification sound.

In step S741, the called party service controller 112 forwards the received session connection request (INVITE) message to the called session controller 122 (S711). Then, the incoming session controller 122 delivers the INVITE message to the called terminal 402 in step S743.

The called terminal 402 receiving the INVITE message outputs a ring tone to inform the user of the called terminal 402 that there is a session connection request, that is, a call request. In addition, the called terminal 402 transmits a session connection request confirmation message in step S745. The transmitted session connection request confirmation message is transmitted to the called session controller 122, the called party service controller 112, the called session controller 122, the origination session controller 121, the originating part service controller 111 and And is transmitted to the calling terminal 401 via the originating session controller 121. The session connection request confirmation message is used to notify that the ring tone is being output from the receiving terminal 402. [ The session connection request confirmation message preferably uses the 180 Ringing message according to the SIP. The called party controller 122, the called party service controller 112, the originating session controller 121, the originating entity service controller 111 and the originating terminal 401 that have received the 180 Ringing message now determine whether the current called terminal 401 Tone is being output.

By the output of the ring tone, the user can know that there is a call request, so that the user can accept the call. Upon detecting a hook-off of the user receiving the call, the called terminal 402 transmits a session connection acceptance message to the called session controller 122 in step S759. The session connection acceptance message is a response to the session connection request message, and is a message for informing that the user of the receiving terminal 402 has accepted the session and accepts the session connection. The session connection acceptance message may use a 200 OK message, depending on the SIP. The incoming session controller 122 then forwards the 200 OK message to the called party service controller 112 in step S761.

Upon receiving the session connection acceptance (200 OK) message, the service controller 112 of the called party transmits a session connection between the calling terminal 401 and the media device 160 for session connection between the calling terminal 401 and the called terminal 402 It should be released. Therefore, the called party service controller 112 transmits a ring back tone session release message to the incoming session controller 122 in step S763. The RBT session release message is a message requesting the release of the session connection between the calling terminal 401 and the media device 160, and it is preferable to use the BYE message according to the SIP. The incoming session controller 122 then forwards the ring back tone session disconnect (BYE) message to the media device 160 at step S765. Accordingly, the media device 160 ends the reproduction of the carrier identification sound or the coloring in step S767. Then, in step S769, the media device 160 transmits a ring back tone session disassociation acceptance message to the incoming session controller 122. [ The RBT session unassociation acceptance message is a message for notifying the calling terminal 401 and the media device 160 of accepting the session disconnection in response to the RBT session disconnect (BYE) message. The RBT session unassociation accept message may use the 200 OK message according to the SIP. Then, the incoming session controller 122 forwards the RBT session disconnection acceptance (200 OK) message to the caller service controller 112 in step S771. Accordingly, the session connection between the calling terminal 401 and the media device 160 is released.

Upon receipt of the 200 OK message, the service controller 112 of the called party informs that the session connection between the calling terminal 401 and the media device 160 is released. Accordingly, the service subscriber unit controller 112 transmits the received session connection acceptance (200 OK) message in step S773 (step S761). The transmitted session connection acceptance message is transmitted to the calling terminal 401 via the incoming session controller 122, the originating session controller 121, the originating service controller 111 and the originating session controller 121 in steps S775 to S781 .

The calling terminal 401 receiving the session connection acceptance (200 OK) message transmits a session connection acceptance confirmation message in step S783. The transmitted session connection acknowledgment message is transmitted from the originating session controller 121 to the originating service controller 111, the originating session controller 121, the incoming session controller 122, the destination service controller 112, And the called session controller 122 to the called terminal 420. The session connection acceptance confirmation message is used to confirm that the session connection acceptance (200 OK) message is received in response to the session connection acceptance (200 OK) message. The session connection acceptance confirmation message can use an ACK message according to the SIP. Thereby, a session is connected between the calling terminal 401 and the called terminal 402. Accordingly, the calling terminal 401 and the called terminal 402 can communicate through the mutually connected sessions in step S797.

9 and 10 are flowcharts for explaining a method for providing a provider identification sound according to a fourth embodiment of the present invention.

9 and 10, the additional service controller 110 is divided into an originating part service controller 111 and a destination part service controller 112, and the session controller 120 is connected to an originating session controller 121 and an incoming session controller 122). The originating service controller 111 and the originating session controller 121 are present in the packet network 100 to which the originating terminal 401 is connected and the originating service controller 112 and the terminating session controller 122 are located in the packet network 100, Is present in the packet network 100 to which the packet network 402 is connected.

9 and 10, in step S901, the calling terminal 401 transmits a session connection request message to the calling session controller 121 to request a call connection with the called terminal 402. [ The session connection request message may be an INVITE message according to the SIP. The originating session controller 121 receiving the INVITE message forwards the INVITE message to the originating service controller 111 in step S903.

After receiving the INVITE message, the originating service controller 111 confirms the supplementary service subscribed by the calling terminal 401 that transmitted the INVITE message in step S905. In particular, the originating service controller 111 confirms whether the originating terminal 401 is subscribed to the provider identification tone service. The INVITE message includes a From header, and in the From header, identification information capable of identifying the calling terminal 401 is described. This identification information may be the URI of the calling terminal 401. [ Therefore, the calling side service controller 111 can identify the calling terminal 401 through the URI described in the From header. Accordingly, the originating service controller 111 confirms whether the identified originating terminal 401 is subscribed to the provider identification tone service. Here, it is assumed that the calling terminal 401 is subscribed to the service provider identification sound service.

The originating service controller 111 includes supplementary service identification information indicating a provider identification sound service in order to notify that the calling terminal 401 is subscribed to the provider identification sound service in a session connection request (INVITE) message. For example, the INVITE message has a P-SVC header, and the originating service controller 111 includes supplementary service identification information indicating a provider identification tone service in the P-SVC header. Then, the originating service controller 111 transmits a session connection request (INVITE) message including the additional service identification information to the originating session controller 121 in step S907. The originating session controller 121 delivers the INVITE message to the terminating session controller 122 in step S909. The incoming session controller 122, upon receipt thereof, forwards the INVITE message to the called party service controller 112 in step S911.

In step S913, the called party service controller 112 receiving the session connection request (INVITE) message confirms the supplementary service subscribed by the calling terminal 401 that has transmitted the INVITE message and the called terminal 402 that is the call destination of the INVITE message . In particular, the terminating service controller 112 determines whether the originating terminal 401 is subscribed to the provider identification tone service and whether the terminating terminal 402 is subscribed to the coloring service. Here, the called party service controller 112 refers to the supplementary service identification information described in the P-SVC header of the received session connection request (INVITE) message to determine whether the calling terminal 401 is subscribed to the provider identification sound service . According to the above assumption, the service controller 112 of the called party can know from the INVITE message that the calling terminal 401 is subscribed to the service provider's voice service. Also, the INVITE message includes a To header, and the To header describes identification information capable of identifying the called terminal 402. [ This identification information may be the URI of the called terminal 402. The called party service controller 112 may identify the called terminal 402 via the URI described in the To header. Accordingly, the called party service controller 112 can check whether the identified calling terminal 401 is subscribed to the coloring service. Here, it is assumed that the called terminal 402 is subscribed to the coloring service.

In particular, the terminating service controller 112 confirms whether the terminating terminal 402 is a terminal subscribing to the same network operator as the calling terminal 401. Here, it is assumed that the called terminal 402 is a terminal subscribing to the same network operator as the calling terminal 401. [ Accordingly, the service unit controller 112 of the called party inquires the sound source code of the operator identification sound and coloring. The carrier identification sound and coloring have a unique sound source code distinguished from other carrier identification sounds or coloring, and the sound source code of the provider can obtain the identification sound and coloring of the corresponding carrier. In this case, in the third embodiment, the caller inquires the sound source code from the sound source code list stored in the service controller 112, but in the fourth embodiment, the service receiver 112 of the receiver unit inquires of the additional service device 230 Obtain the source code. This is explained as follows. In step S915, the service subscriber service controller 112 transmits a sound source code request message to the additional service device 230. [ Here, the tone generator code request message is a request for inquiry of at least one of a tone generator code of the business entity identification sound corresponding to the calling terminal 401 and a tone generator code of the coloring corresponding to the calling terminal 402. Therefore, when the sound source code request message requests the sound source code of the provider identification sound corresponding to the calling terminal 401, the calling terminal identification information capable of identifying the calling terminal 401 and the calling terminal identification information, And additional service identification information capable of identifying the identification sound service. In addition, when the tone generator code request message requests the tone generator code of the coloring corresponding to the called terminal 402, the tone generator code request message includes the calling terminal identification information capable of identifying the called terminal 402 and the coloring service And additional service identification information capable of identifying the additional service.

Upon receiving the tone generator code request message, the additional service device 230 searches the tone generator code stored in the tone generator code list of itself for the tone generator code of the business entity identification sound mapped to the calling terminal 401, The sound source code of the sound source is retrieved. Then, in step S917, the additional service device 230 transmits the tone generator code response message containing the corresponding tone generator code to the service provider controller 112 of the reception unit.

After acquiring the tone generator code through the tone generator code response message, the service controller 112 of the receiver unit transmits a session identification code and coloring to the caller terminal 401, which is mapped to the tone generator code, Proceed with the procedure. This is explained as follows.

In step S919, the called party service controller 112 transmits a ringback tone session connection request message including the acquired tone generator code to the incoming session controller 122 in advance (steps S915 and S917). The ring back tone session connection request message is a message requesting the calling terminal 401 to connect a session with the calling terminal 401 to the media device 160 to provide a carrier identification tone and a ring back tone. In addition, the RBT session connection request message is a message including a sound source code, and requests the media device 160 to provide a corresponding company identification sound and a ring back tone. The RBT session connection request message can use an INVITE message according to the SIP. The incoming session controller 122 then forwards the ring back tone session connection request (INVITE) message to the media device 160 in step S921.

Upon receiving the INVITE message, the media device 160 transmits a ring back tone session connection acceptance message to the incoming session controller 122 in step S923. Here, the RBT session connection accept message is a message in which the media device 160 accepts a session connection with the calling terminal 401 in response to a ring back tone session connection request (INVITE) message. The RBT session connection accept message may use the 200 OK message according to SIP. Then, the incoming session controller 122 delivers a ring back tone session connection acceptance (200 OK) message to the caller service controller 112 in step S925.

After receiving the 200 OK message, the service subscriber unit controller 112 transmits a session advance message in step S927. The transmitted session progress message is transmitted to the calling terminal 401 via the incoming session controller 122, the originating session controller 121, the originating section service controller 111 and the originating session controller 121 in steps S929 to S935 . The session progress message is used to inform the calling terminal 401 that the session procedure is still in progress. In addition, the session progress message is for informing the calling terminal 401 that the session connection for providing the provider identification tone and the coloring is in progress. The Session Progress message may use the 183 SessionProgress message according to the SIP. That is, the service controller 112 of the called party transmits the 183 SessionProgress message in advance in response to the received INVITE (step S911). The calling terminal 401 receiving the 183 SessionProgress message can confirm that the session establishment procedure is still in progress. Accordingly, the calling terminal 401 does not proceed according to the delay or failure of the session connection, such as retransmission of a session connection request (INVITE) message.

Meanwhile, the called party service controller 112 transmits a ring back tone session connection acknowledgment message to the incoming session controller 122 in step S937. The RBT session connection acceptance confirmation message is a message informing that the final connection to the session connection for providing the service provider identification sound and the ring back tone is confirmed. The RBT session connection acknowledgment message is a response message corresponding to the RBT session connection acceptance (200 OK) message. This RBT session connection acknowledgment message preferably uses an ACK message according to the SIP. The incoming session controller 122 then forwards the ring back tone session connection acknowledgment (ACK) message to the media device 160 in step S939.

When the media device 160 receives the RBT session connection acknowledgment (ACK) message, a session is established between the calling terminal 401 and the media device 160. Then, in step S941, the media device 160 provides the calling terminal 401 with a carrier identification tone and coloring that are mapped to the tone source code of the called terminal 402. [ That is, the media device 160 has previously received the sound source code mapped to the called terminal 402 through the RBT session connection request (INVITE) message (step S921). Accordingly, the media device 160 can provide the calling terminal 401 with a business identification tone and coloring that are mapped to the tone source code received previously. In particular, in step S941, the media device 160 reproduces the provider identification sound prior to the coloring reproduction. That is, the media device 160 reproduces the coloring after reproducing the provider identification sound through the connected session. Accordingly, the user of the calling terminal 401 can confirm that the calling terminal 402 is subscribed to the same network operator as the calling terminal 402 by confirming the operator identification sound.

Meanwhile, the subsequent steps, that is, steps S943 to S999, perform the same procedures corresponding to steps S741 to S797 of the third embodiment, and detailed description thereof will be omitted.

11 is a flowchart illustrating a method for providing a provider identification sound service of an additional service controller according to an embodiment of the present invention.

11, the supplementary services controller 110 may receive a session connection request (INVITE) message in which the calling terminal 401 requests a session connection for a call with the called terminal 402 in step S1101. That is, the supplementary service controller 110 can receive the INVITE message transmitted from the calling terminal 401 from the session controller 120.

In step S1103, the additional service controller 110 determines whether the calling terminal 401 or the called terminal 402 is subscribed to the service provider's voice service through the INVITE message. When the INVITE message is received from another packet network 100, the additional service controller 110 determines whether the calling terminal 401 is subscribed to the service provider identification sound service through the additional service identification information included in the INVITE message Able to know. That is, as described above, the supplementary service controller 110 can determine whether the calling terminal 401 is subscribed to the provider identification sound service by referring to the P-SVC header of the INVITE message.

If it is determined in step S1103 that the calling terminal 401 is subscribed to the provider identification sound service, the additional service controller 110 proceeds to step S1105. On the other hand, if it is determined in step S1103 that the called terminal 402 is subscribed to the provider identification sound service, the process proceeds to step S1115.

In step S1105, the additional service controller 110 determines whether the called terminal 402 is subscribed to the same network operator as the calling terminal 402. [

As a result of the determination in step S1105, if the subscriber is not subscribed to the same network operator, the additional service controller 110 relays the INVITE message according to a general procedure in step S1107.

On the other hand, if it is determined in step S1105 that the subscriber is subscribed to the same network operator, the supplementary service controller 110 inquires and acquires the source code of the carrier identification code unique to the network provider subscribed by the calling terminal 401 in step S1109. Then, the supplementary service controller 110 includes the sound source code obtained in step S1111 in a ringback tone session connection request (INVITE) message. In step S1113, the additional service controller 110 transmits a ring back tone session connection request message including the sound source code to the media device 160 through the session controller 120. [ Accordingly, the media device 160 can respond to the RBT session connection request message to connect the session with the calling terminal 401. [ In addition, the media device 160 can reproduce the service provider identification sound corresponding to the sound source code included in the ring back tone session connection request message through the connected session. Accordingly, the calling terminal 401 can receive the operator identification sound reproduced by the media device 160 through the connected session, and output it.

On the other hand, when the called terminal 402 is subscribed to the service provider identification sound service, the additional service controller 110 inquires the sound source code of the carrier identification sound unique to the network provider subscribed by the receiving terminal 401 do. Then, the supplementary service controller 110 includes the sound source code obtained in step S1117 in a ringback tone session connection request (INVITE) message. Then, in step S1119, the additional service controller 110 transmits a ring back tone session connection request message including the sound source code to the media device 160 through the session controller 120. [ The media device 160 may respond to the RBT session connection request message to connect the session with the calling terminal 401. [ In addition, the media device 160 can reproduce the service provider identification sound corresponding to the sound source code included in the ring back tone session connection request message through the connected session. Accordingly, the calling terminal 401 can receive the operator identification sound reproduced by the media device 160 through the connected session, and output the reproduced operator identification sound.

As described above, according to the embodiment of the present invention, a session is established between the calling terminal 401 and the media device before the session for the call between the calling terminal 401 and the called terminal 402 is connected, The advertisement for the network operator can be provided by outputting the provider identification sound which is the sound source unique to the provider before the reproduction of the coloring provided in place of the ring back tone in the case where the back tone or the call receiving terminal 402 is subscribed to the coloring service. In particular, since the call is made with the end of the ring back tone, the user is intensively listening to the ring back tone. Therefore, when the ringback tone is outputted as in the embodiment of the present invention, when the provider identification sound is provided instead of the ringback tone, the effect of the advertisement is excellent. In addition, when the calling terminal 401 and the called terminal 402 are subscribed to the same network provider, by providing the calling terminal 401 with the operator identification sound, the user of the calling terminal 401 can receive the user identification Is subscribed to the same network operator. In addition, if there is a benefit such as a discount of a call charge given when a call is made between terminals of the same network provider, the user of the calling terminal 401 can indirectly know this. The packet network 100 can utilize the resources established for providing additional services in the circuit network by providing the service provider identification sound service with reference to the sound source code list of the receiving terminal 402 stored in the circuit network 200. [ As a result, the infrastructure cost for providing additional services can be reduced.

The method for providing the service provider identification sound 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 service provider identification tone, a packet network for the same, and a method and a device for the same. In accordance with the present invention, before a session for call between a calling terminal and a called terminal is connected, The advertisement for the network operator can be provided by outputting the operator identification sound that is the sound source unique to the provider instead of the ring back tone when the back tone is output. In particular, since the call is made with the end of the ring back tone, the user is intensively listening to the ring back tone. Therefore, as in the embodiment of the present invention, a provider identification sound is provided instead of a ring back tone, and the effect of the advertisement is excellent. Also, when the calling terminal and the called terminal are subscribed to the same network provider, by providing the calling terminal with the operator identification sound, the calling terminal user can know that the user of the called terminal is subscribed to the same network operator. In addition, if there is such a benefit as a discount of a call charge given when a call is made between terminals of the same network provider, the user of the calling terminal can indirectly know this. The packet network can utilize the resources established for providing additional services in the circuit network by providing the service provider identification sound service with reference to the sound source code list of the called terminal stored in the circuit network. As a result, the infrastructure cost for providing additional services can be reduced. 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
111: originating service controller 112:
120: Session controller 121: Outgoing session controller
122: incoming 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:

Claims (16)

delete A session controller for relaying, to the called terminal, a session connection request message in which a calling terminal requests a session connection with a called terminal;
A media device for providing a calling terminal with a carrier identification sound, which is a sound source unique to a network provider; And
Upon receipt of the session connection request message, confirms whether the calling terminal or the called terminal is subscribed to the service provider identification sound service,
When the calling terminal is subscribed to the service provider identification sound service, requests a sound source code corresponding to the calling terminal to an additional service device of a circuit network storing a list of sound source codes and acquires the sound source code, And a supplementary service controller for transmitting the service provider identification sound to the calling terminal and providing the calling terminal with a service provider identification sound according to the acquired tone generator code. delete delete delete 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; And
If the calling terminal subscribes to the service provider's voice service, if the called terminal is a subscriber to the same network provider as the calling terminal,
A sound source code corresponding to the calling terminal is requested and obtained from an additional service device of a circuit network storing a list of sound source codes, and the acquired sound source code is transmitted to the media device through the communication module, And a control module for providing the calling terminal with a service provider identification sound according to the service provider identification sound. 12. The apparatus of claim 11, wherein the control module
When the called terminal subscribes to the provider identification sound service,
Acquires a sound source code corresponding to the called terminal, transmits the obtained sound source code to the media device through the communication module, and provides the calling terminal with a carrier identification sound according to the obtained sound source code An additional service controller for providing operator identification sounds. 13. The system of claim 11 or 12, wherein the control module
Transmitting a sound source code request message requesting the sound source code to an additional service device of a circuit network storing a list of sound source codes through the communication module and receiving a sound source code response message including the sound source code from the additional service device And the sound source code is obtained by the sound source code. 13. The service providing system according to claim 11 or 12,
And a storage module for storing a tone generator code list, which is a list of the tone generator codes,
Wherein the control module inquires a sound source code list stored in the storage module and acquires the sound source code. Receiving a session connection request message for a calling terminal to request a session connection for a call with the called terminal;
Checking whether the calling terminal or the called terminal joins the service provider's beep service from the session connection request message;
Determining whether the called terminal is a terminal subscribed to the same network operator as the calling terminal when the calling terminal is subscribed to the service provider identification sound service;
If it is determined that the called terminal is a terminal subscribed to the same network operator as the calling terminal, the calling terminal requests a supplementary service device of a circuit network storing a list of tone generator codes to a tone generator code corresponding to the calling terminal Obtaining; And
A ring back tone session connection request message requesting a session connection between the calling terminal and the media device including the acquired tone generator code is transmitted to the media device and a provider identification sound corresponding to the acquired tone generator code is provided to the calling terminal The method comprising the steps of: providing a supplementary service controller; 16. The method of claim 15,
Acquiring a sound source code of a business entity identification sound corresponding to the called terminal when the called terminal subscribes to the business entity identification sound service as a result of the checking; And
Transmitting a ring back tone session connection request message requesting a session connection between the calling terminal and the media device to the media device and transmitting a service provider identification sound according to the acquired sound source code to the calling terminal, The method comprising the steps of: providing a supplementary service controller to provide a provider identification tone to the supplementary service controller.

Images