WO2011113497A1

WO2011113497A1 - Voiceback announcement

Info

Publication number: WO2011113497A1
Application number: PCT/EP2010/058759
Authority: WO
Inventors: Jayakumar Balaji; Balasubramanian Gopalasubramanian; Nainar Mahalakshmi
Original assignee: Alcatel Lucent
Priority date: 2010-03-17
Filing date: 2010-06-22
Publication date: 2011-09-22

Abstract

Voiceback Announcement. The present invention relates to IN networks and, more particularly, to voice announcements in IN networks. A method for announcement of digits to a user belonging to an Intelligent Network. A Media Server collects digits entered by the user and concatenates an audio announcement to the digits entered by the user. The audio announcement depends on the type of the digits entered by the user and the Media Server plays the announcement to the user. A Service Control Point sends an audio announcement id to a Media Gateway Controller and the Media Gateway Controller maps the audio announcement id to a Uniform Resource Locator and sends the Uniform Resource Locator to the Media Server. The Uniform Resource Locator indicates location of the audio announcement in the Media Server.

Description

VOICEBACK ANNOUNCEMENT

TECHNICAL FIELD

[001] The present invention relates to ΓΝ networks and, more particularly, to voice announcements in IN networks.

BACKGROUND

[002] While using network resources in a communication network, a user may sometimes have to enter digits using a communication terminal. The entered digits may be used to invoke some services, enter user ID, password, destination number or any other requirement wherein dialing of digits is a prerequisite. For example, to invoke the calling card feature, the user may have to enter the service code before availing of the feature. The user enters the digits after ensuring that all Dual Tone Multi Frequency (DTMF) rules have been complied with while entering the digits. Once the user enters the number, a Media Server (MS) determines if the user has complied with the required DTMF rules while entering the digits. However, the MS does not check the authenticity of the digits entered by the user. For example, if the user has to enter a 5 digit password, and if the user enters 5 digits wherein the entered password is wrong, the MS does not indicate an error since the MS only checks to determine if the user has entered 5 digits. Thus, when a user in an Intelligent Network (IN) enters an incorrect digit, the user has no way to realize that there was an error in entering the digits.

[003] In current systems, such as Time Division Multiplexed (TDM) networks, a voiceback announcement is made to the user. The voiceback announcement plays the digits, entered by the user, back to the user after prefixing some words to the digits. For example, if the user enters the number 24680, then the voiceback announcement made to the user would be "The entered number is 24680". However, when the user enters multiple types of numbers then there is no unique voiceback announcement to differentiate the multiple types of numbers entered by the user. For example, the multiple types of numbers entered by the user may be a user ID, password, destination number or PIN number. If the user enters the user ID as 123456, then the voiceback announcement played back to the user would be "The entered number is 123456" and if the password entered by the user also happens to be 123456, then the voiceback announcement played back to the user would be "The entered number is 123456". When the user has entered multiple types of numbers, the user would not be able to understand which number is being played back since the same announcement is being prefixed to the entered digits.

SUMMARY

[004] In view of the foregoing, an embodiment herein provides a method for announcement of digits to a user belonging to an Intelligent Network. A Media Server collects digits entered by the user and concatenates an audio announcement to the digits entered by the user. The audio announcement depends on type of the digits entered by the user and the Media Server plays the announcement to the user. A Service Control Point sends an audio announcement id to a Media Gateway Controller. The Media Gateway Controller maps the audio announcement id to a Uniform Resource Locator and sends the Uniform Resource Locator to the Media Server. The Service Control Point sends the audio announcement id to the Media Gateway Controller in a Prompt and Collect User Information message. The Media Gateway Controller sends the Uniform Resource Locator to the Media Server in a Session Initiation Protocol (SIP) INFO message using Media Server Markup Language (MSML) or in Media Server Control Interactive Voice Response (MSCIVR) format. The Service Control Point sends a Boolean Parameter to a Media Gateway Controller. The Media Gateway Controller maps the audio announcement id to a Uniform Resource Locator and sends the Uniform Resource Locator to the Media Server. The Boolean Parameter is sent to the Media Gateway Controller in a Prompt and Collect User Information message.

[005] Embodiments further disclose a Service Control Point for enabling announcement of digits to a user belonging to an Intelligent Network. The Service Control Point sends an audio announcement id to a Media Gateway Controller when digits have to be collected from the user, wherein the audio announcement id depends on the type of the digits entered by the user and an audio announcement is played to the user after concatenating the audio announcement to the digits. The audio announcement ID points to an audio announcement. The Service Control Point sends the audio announcement id to the Media Gateway Controller in a Prompt and Collect User Information message.

[006] Embodiments herein also disclose a Media Gateway Controller for enabling announcement of digits to a user belonging to an Intelligent Network. The Media Gateway Controller sends a Uniform Resource Locator to a Media Server to indicate a location of the audio announcement, when digits have to be collected from the user and the audio announcement is played to the user after concatenating the audio announcement to the digits. The Uniform Resource Locator is sent in a Session Initiation Protocol (SIP) INFO message using either Media Server Markup Language (MSML) or Media Server Control Interactive Voice Response (MSCIVR) format. The Media Gateway Controller sends the Uniform Resource Locator on receiving an audio announcement id from a Service Control Point. The Media Gateway Controller maps the audio announcement id to the Uniform Resource Locator of the audio announcement.

[007] Also, disclosed herein is a Media Server for enabling announcement of digits to a user belonging to an Intelligent Network user. The Media Server collects digits entered by the user and plays an audio announcement to the user after concatenating the audio announcement to the digits, wherein the audio announcement depends on type of the digits. The Media Server receives a Uniform Resource Locator of the audio announcement from a Media Gateway Controller, wherein the Uniform Resource Locator indicates location of the audio announcement in the Media Server.

[008] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings.

BRIEF DESCRIPTION OF THE FIGURES

[009] The embodiments herein will be better understood from the following detailed description with reference to the drawings, in which:

[0010] FIG. 1 illustrates a block diagram of a user in an Intelligent Network (IN), according to an embodiment herein;

[0011] FIG. 2 is a block diagram of a Service Control Point (SCP), according to an embodiment herein;

[0012] FIG. 3 is a block diagram of a Media Gateway Controller (MGC), according to an embodiment herein;

[0013] FIG. 4 is a block diagram of a Media Server (MS), according to an embodiment herein;

[0014] FIGS. 5a and 5b are flowcharts depicting a method for voiceback announcement of digits, according to an embodiment herein;

[0015] FIG. 6 illustrates a flow diagram for an example illustrating voiceback announcement, according to an embodiment herein;

DETAILED DESCRIPTION OF EMBODIMENTS

[0016] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well- known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.

[0017] The embodiments herein disclose a system and method for voiceback announcement of digits to an IN user. When an IN user communicates digits to the network, the network collects the digits and plays the collected digits back to the IN user as a voiceback announcement. Referring now to the drawings, and more particularly to FIGS. 1 through 6, where similar reference characters denote corresponding features consistently throughout the figures, there are shown embodiments.

[0018] FIG. 1 illustrates a block diagram of a user in an Intelligent Network (IN). In a communication network, an IN user 101 may have to communicate the digits of a number to a Media Server (MS) 102. For example, the IN user 101 may have to enter a user ID and password in order to avail of a service offered by the network. The MS 102 is a server that helps establish and maintain a multi media session with IN user 101. The MS 102 also stores media and shares the stored media with users of the network. Before communicating the digits, the IN user 101 initiates a communication link with the network. The IN user 101 may initiate the communication link by sending a request to a Media Gateway Controller (MGC) 103. The MGC 103 receives signaling information from the MS

102 and instructs the MS 102 to alert the destination in order to start a communication session between the calling user and the destination. The destination may be a second user in the communication network with whom the calling user wishes to communicate. The MGC 103 also acts as a Service Switching Point (SSP) and makes available additional services during a communication session. In other embodiments, the SSP may be a network element located outside the MGC 103.

[0019] On receiving the request from the IN user 101 and on determining that digits have to be collected from the IN user 101, the MGC

103 triggers a Service Control Point (SCP) 104. The SCP 104 is used to help control the services offered by the network. The SCP 104 identifies the number to which a communication session is to be routed and then routes the communication session to the number. The SCP 104 also helps in playing voice messages or play prompt announcements to the IN user 101. The SCP 104 contains the service logic that implements the services related to collection of the digits from the IN user 101. On being triggered, the SCP 104 instructs the MS 102, using the MGC 103, to start a communication session with the SIP user 101. When digits have to be collected from the IN user 101, the SCP 104 sends a prompt announcement to the MS 102 and instructs the MS 102 that digits have to be collected from IN user 101. The SCP 104 also sends a voiceback announcement ID indicating the announcement to be played to IN user 101 while communicating the digits back to the IN user 101. For example, the SCP 104 may send a Prompt and Collect User Information (PACUI) to the MS 102. The PACUI is used to play a prompt announcement, collect digits from the SIP user 101 and includes the announcement ID of the announcement to be played to the IN user 101. The prompt announcement played to the IN user 101 may be "Enter the password" and if the IN user 101 enters, 2468, then the voiceback announcement played to the IN user 1 0 1 woul d b e " The entered p assword i s 2468". The voiceback announcement is played to IN user 101 after prefixing the voiceback announcement to the digits entered by IN user 101. The voiceback announcement depends on the type of digit entered by IN user 101 and the voiceback announcement is different for different types of numbers entered by IN user 101. For example, if IN user 101 enters the user ID, then the voiceback announcement played to the user may be "The entered user ID is". If user 101 enters the destination number, then the voiceback announcement played to the user may be "The entered destination number is". The SCP 104 may also include Dual Tone Multi Frequency (DTMF) rules, in the PACUI, to be checked by the MS 102. For example, a DTMF rule may state that the minimum number of digits to be entered by IN user 101 is 7. After collecting the digits from the IN user 101, the MS 102 checks to determine if the IN user 101 has followed all DTMF rules while entering the digits. If the rules have been followed, then the MS 102 plays the voiceback announcement to the IN user 101 after suffixing the digits entered by the IN user 101 to the voiceback announcement. For example, if IN user 101 has entered the PIN number as 13579 after following the DTMF rules, then the MS 102 plays a voiceback announcement as "The entered PIN number is 13579". The MS 102 sends the result of the check to the MGC 103. The MGC 103 then forwards the response to the SCP 104.

[0020] FIG. 2 is a block diagram of a Service Control Point (SCP). In a communication network, an IN user 101 may have to communicate the digits of a number to the MS 102. Before communicating the digits, the IN user 101 initiates a communication link with the network. The IN user 101 may initiate the communication link by sending a request to the MGC 103. On receiving the request, from the IN user 101, and on determining that digits have to be collected from the IN user 101, the MGC 103 triggers the SCP 104. The SCP 104 receives the triggering message from the MGC 103 through a receiver 202. The SCP 104 helps in playing voice messages or play prompt announcements to the IN user 101. On being triggered, the SCP 104 instructs the MS 102 using the MGC 103 to start a communication session with the SIP user 101. When digits have to be collected from the IN user 101, the SCP 104 sends a prompt announcement to the MS 102 through the MGC 103, and instructs the MS 102 that digits have to be collected from IN user 101. The SCP 104 also sends the required DTMF rules and a voiceback announcement ID indicating the announcement to be played to IN user 101 while communicating the digits back to the IN user 101. For example, the SCP 104 may send a PACUI with the voiceback announcement ID as "voiceback: 3". A processor 201 controls the functioning of the SCP 104. All the actions performed by the SCP 104 are co-ordinated by the processor 201. The processor 201 determines the voiceback announcement ID after taking into consideration the voiceback announcement to be played to the IN user 101. For example, if the voiceback announcement to be played to the IN user 101 is "The entered password is" and if the announcement ID corresponding to the announcement is "3", then the processor 201 includes the voiceback announcement ID as "voiceback: 3" in the message sent to the MGC 104. The announcement ID of the corresponding voiceback announcement may be stored in a memory 204. The processor 201 obtains the announcement ID of the corresponding voiceback announcement from the memory 204 and includes the voiceback announcement ID in the message sent to the MGC 104. The voiceback announcement is played to the IN user 101 after prefixing the voiceback announcement to the digits entered by the IN user 101. The voiceback announcement is different for different types of numbers entered by the IN user 101. The SCP 104 sends messages to the MGC 103 through a transmitter 203.

[0021] On receiving the voiceback announcement ID from the SCP 104, the MGC 103 maps the voiceback announcement ID to the corresponding Uniform Resource Locator (URL) of the voiceback announcement. The URL indicates the location of the voiceback announcement in the MS 102. For example, if the voiceback announcement ID indicates that the voiceback announcement to be played to the IN user 101 is "The entered password is" and the voiceback announcement is located at "loci" in the MS 102 and the name of the voiceback announcement file is "VBl .wav" then the URL of the voiceback announcement may be "file:/locl/VBl .wav". The SCP 104 may also include DTMF rules and a prompt announcement in the message sent to the MGC 103. The MGC 103 sends the URL of the voiceback announcement to the MS 102. The MS 102 collects the digits from the IN user 101 and checks to determine if the IN user 101 has followed all DTMF rules while entering the digits. If the rules have been followed, then the MS 102 plays the voiceback announcement to the IN user 101 after suffixing the digits entered by the IN user 101 to the voiceback announcement. The MS 102 sends the result of the check to the MGC 103. The MGC 103 then forwards the response to the SCP 104.

[0022] FIG. 3 is a block diagram of a Media Gateway Controller (MGC). In a communication network, an IN user 101 may have to communicate the digits of a number to the MS 102. Before communicating the digits, the IN user 101 initiates a communication link with the network. The IN user 101 may initiate the communication link by sending a request to the MGC 103. The MGC 103 receives the request through a receiver 302. On receiving the request from the IN user 101, and on determining that digits have to be collected from the IN user 101, the MGC 103 triggers the SCP 104. On being triggered, the SCP 104 instructs the MS 102, using the MGC 103, to start a communication session with the SIP user 101. When digits have to be collected from the IN user 101, the SCP 104 sends a prompt announcement to the MS 102, through the MGC 103, and instructs the MS 102 that digits have to be collected from IN user 101. The SCP 104 also sends the required DTMF rules and a voiceback announcement ID indicating the announcement to be played to IN user 101 while communicating the digits back to the IN user 101.

[0023] On receiving the voiceback announcement ID from the SCP 104, the MGC 103 maps the voiceback announcement ID to the corresponding Uniform Resource Locator (URL) of the voiceback announcement. The URL indicates the location of the voiceback announcement in the MS 102. The MGC 103 receives the announcement ID from the SCP 104, determines the location of the voiceback announcement in the MS 102 and maps the voiceback announcement ID to the corresponding URL of the voiceback announcement. A processor 301 controls the functioning of the MGC 103. All the actions performed by the MGC 103 are co-ordinated by the processor 301. The processor 301 maps the announcement ID to the URL of the voiceback announcement. The URL of a corresponding voiceback announcement ID may be stored in a memory 304. The MGC 103 sends the URL of the voiceback announcement to the MS 102 through a transmitter 303. For example, the MGC 103 may send the URL of the voiceback announcement in a Session Initiation Protocol (SIP) INFO message using Media Server Markup Language (MSML)/ Media Server Control Interactive Voice Response (MSCIVR) format. The MGC 103 may also send the URL of the prompt announcement to be played to the IN user 101 and the DTMF rules to the MS 102.

[0024] On receiving the message from the MGC 103, the MS 102 determines that digits have to be collected from IN user 101. The MS 102 plays the prompt announcement to the IN user 101 and collects the digits from IN user 101 when IN user 101 enters the digits. For example, the prompt announcement played to IN user 101 may be "Enter security number and press # to end". The prompt announcement may be played through a communication terminal of the IN user and the IN user 101 may enter the digits using the communication terminal. After collecting the digits, the MS 102 checks to determine if the IN user 101 has followed the required DTMF rules while entering the digits. If the required DTMF rules have been followed by the IN user 101, then the MS plays back the entered digits to the IN user 101. For example, if the IN user 101 had entered 236789#, then the voiceback announcement played to the IN user 101 could be "The entered security number is 236789". If the IN user 101 enters an end of digit character to end the digit collection session with the MS 102, then the end of digit character is not played back to the IN user 101 during the voiceback announcement. In the previous example, # is the end of digit character and # is not played back to the IN user 101 during the voiceback announcement. The voiceback announcement to IN user 101 may also be made through the communication terminal. After the MS 102 checks the digits entered by the IN user 101 to determine if the digits comply with the required DTMF rules, the MS 102 sends the result of the check to the SCP 104 through the MGC 103.

[0025] FIG. 4 is a block diagram of a Media Server. In a communication network, an IN user 101 may have to communicate the digits of a number to the MS 102. Before communicating the digits, the IN user 101 initiates a communication link with the network. The IN user 101 may initiate the communication link by sending a request to the MGC 103. On receiving the request, from the IN user 101, and on determining that digits have to be collected from the IN user 101, the MGC 103 triggers the SCP 104. The SCP 104 helps in playing voice messages or play prompt announcements to the IN user 101. On being triggered, the SCP 104 instructs the MS 102, using the MGC 103, to start a communication session with the SIP user 101. When digits have to be collected from the IN user 101, the SCP 104 sends a prompt announcement to the MS 102,through the MGC 103, and instructs the MS 102 that digits have to be collected from IN user 101. The SCP 104 also sends the required DTMF rules and the voiceback announcement ID indicating the announcement to be played to the IN user 101 while communicating the digits back to the IN user 101. On receiving the voiceback announcement ID from the SCP 104, the MGC 103 maps the voiceback announcement ID to the corresponding Uniform Resource Locator (URL) of the voiceback announcement. The MGC 103 sends the URL of the voiceback announcement to the MS 102. The MGC 103 may also send the URL of the prompt announcement to be played to the IN user 101 and the DTMF rules to the MS 102.

[0026] On receiving the message from the MGC 103, the MS 102 determines that digits have to be collected from IN user 101 and establishes a communication session with the IN user 101. The MS 102 receives the message from the MGC 103 through a receiver 402. A processor 201 controls the functioning of the MS 102. All the actions performed by the MS 102 are co-ordinated by the processor 201. The processor 401 locates the prompt announcement from a memory 404 using the URL of the prompt announcement and plays the prompt announcement to the IN user 101. For example, if the URL of the prompt announcement received from the MGC 103 is "file:/locl/PROMPTl .wav" and the location indicated by the URL has the prompt announcement "Enter the destination number and press zero to end" then the MS plays the announcement to IN user 101. The MS 102 collects the digits entered by the IN user 101 and the processor 401 checks to determine if the IN user 101 has complied with the required DTMF rules while entering the digits. The MS 102 receives the digits from the IN user 101 through a receiver 402. If the check reveals that the digits follow the required DTMF rules, then the processor 401 locates the voiceback announcement based on the URL of the voiceback announcement received from the MGC 103. The processor 401 prefixes the voiceback announcement to the digits entered by the IN user 101 and plays the voiceback announcement to the IN user 101. For example, if the URL of the voiceback announcement received from the MGC 103 is "file:/locl/VOICEBACK2.wav" and the location indicated by the URL has the prompt announcement "The destination number entered is" then the MS 102 prefixes the voiceback announcement to the digits entered by the IN user 101 plays the announcement to IN user 101. The MS 102 plays the prompt announcement and the voiceback announcement to IN user 101 through a transmitter 403. The voiceback announcement from the MS 102 to the IN user 101 may be provided in all Intelligent Network Application Part (INAP) and Customized Applications for Mobile Network Enhanced Logic (CAMEL) architectures. The MS 102 may also provide voiceback announcements to users of a communication network for supplementary features provided by the MGC 103. For example, supplementary features provided by the MGC 103 may be Call Forwarding, Call Waiting and Outgoing Call Barring features. The voiceback announcement can also be played to users availing of features offered by the IN system in Next Generation Networking (NGN)/Internet Protocol Multimedia Services (IMS) architecture. The MS 102 then sends the result of the check, to determine if the digits follow the required DTMF rules, to the SCP 104 through the MGC 103.

[0027] FIGS. 5a and 5b are flowcharts depicting a method for voiceback announcement of digits. In a communication network, an IN user 101 may have to communicate the digits of a number to the MS 102. Before communicating the digits, the IN user 101 initiates a communication link with the network. The IN user 101 may initiate the communication link by sending (501) a request to the MGC 103. On receiving the request, from the IN user 101, and on determining that digits have to be collected from the IN user 101, the MGC 103 triggers (502) the SCP 104. On being triggered, the SCP 104 instructs the MS 102, using the MGC 103, to start a communication session with the SIP user 101. When digits have to be collected from the IN user 101, the SCP 104 sends (503) a prompt announcement to the MS 102, through the MGC 103, and instructs the MS 102 that digits have to be collected from IN user 101. The SCP 104 also sends (503) the required DTMF rules and a voiceback announcement ID indicating the announcement to be played to the IN user 101, while communicating the digits back to the IN user 101. On receiving the voiceback announcement ID from the SCP 104, the MGC 103 maps the voiceback announcement ID to the corresponding Uniform Resource Locator (URL) of the voiceback announcement and sends (504) the URL to the MS 102. The URL indicates the location of the voiceback announcement in the MS 102.

[0028] On receiving the message from the MGC 103, the MS 102 determines that digits have to be collected from IN user 101 and establishes a communication session with the IN user 101. The MS 102 locates the prompt announcement using the URL of the prompt announcement and plays (505) the prompt announcement to the IN user 101. The MS 102, then, collects (506) the digits entered by the IN user 101 and checks (507) to determine if the IN user 101 has complied with the required DTMF rules while entering the digits. If there is any error in the digits collected, then the digit collection session is stopped (508). For example, if the DTMF rule specifies that IN user 101 has to enter a minimum of 7 digits and if the IN user 101 enters only 4 digits then an error occurs. If the check reveals that the digits follow the required DTMF rules, then the MS 102 locates the voiceback announcement based on the URL of the voiceback announcement received from the MGC 103. The MS 102 prefixes the voiceback announcement to the digits entered by the IN user 101 and plays (509) the voiceback announcement to the IN user 101. The MS 102 then sends (5010) the result of the check, to determine if the digits follow the required DTMF rules, to the SCP 104 through the MGC 103. The various actions in method 500 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 5 may be omitted.

[0029] FIG. 6 illustrates a flow diagram for an example illustrating voiceback announcement. In a communication network, an IN user 101 may have to enter the digits of a number to the MS 102. For example, the IN user 101 may want to avail of calling card feature, wherein the IN user 101 can make calls using a calling card, and needs to enter a user ID before availing the feature. Before entering the digits, the IN user 101 initiates a communication link with the network. The IN user 101 may initiate the communication link by sending a request to the MGC 103. For example, to avail of calling card feature the IN user 101 may send a Service code 602 to the MGC 104. On receiving the request, from the IN user 101, and on determining that digits have to be collected from the IN user 101, the MGC 103 triggers the SCP 104. For example, the MGC 103 may trigger the SCP

104 by sending an Initial Detection Point (IDP) 603 to the SCP 104. On being triggered, the SCP 104 instructs the MS 102, using the MGC 103, to start a communication session with the SIP user 101. The SCP 104 sends a message to the MS 102, through the MGC 103, to instruct the MS 102. For example, the SCP 104 may send a Connect to Resource (CTR) 604 message to the MGC 103 and the MGC 103 may send an Invite 605 message to the MS 102. The MS 102 then tries to establish a communication session with IN user 101 and sends a message to the MGC 103 indicating that the MS 102 is trying to establish a communication session with IN user 101. For example, the message sent by the MS 102 to the MGC 103 may be a 100 Trying 606 message. On successfully establishing a session with IN user 101, the MS 102 sends a message to the MGC 103 indicating the successful establishment of the session. For example, the MS 102 may send a 200 OK 607 message to the MGC 103 indicating the successful establishment of the session and the communication between the MS 102 and IN user 101 may happen through Real-time Transport Protocol (RTP).

[0030] When digits have to be collected from the IN user 101, the SCP 104 sends a prompt announcement to the MS 102, through the MGC 103, and instructs the MS 102 that digits have to be collected from IN user 101. The SCP 104 also sends the required DTMF rules and a voiceback announcement ID indicating the announcement to be played to IN user 101 while communicating the digits back to the IN user 101. For example, the SCP 104 may send the prompt announcement ID, required DTMF rules and the voiceback announcement ID as a PACUI 608 to the MGC 103. On receiving the voiceback announcement ID from the SCP 104, the MGC 103 maps the voiceback announcement ID to the corresponding URL of the voiceback announcement and sends the URL to the MS 102. The URL indicates the location of the voiceback announcement in the MS 102. The MGC 103 also maps the prompt announcement ID to the URL of the prompt announcement to be played to the IN user 101. For example, the MGC 103 may send the URL of the prompt announcement, URL of the voiceback announcement and the DTMF rules as a Media Server Markup Language (MSML)/Media Server Control Interactive Voice Response (MSCIVR) 609 in the SIP INFO message.

[0031] The MS 102 locates the prompt announcement using the

URL of the prompt announcement and plays the prompt announcement to the IN user 101. For example, the prompt message may start as a Start Ann 6010 message and end as an End Ann 6011 message. The MS 102, then, collects the digits entered by the IN user 101. For example, the MS 102 may start digit collection as Start digit collection 6012. After entering the digits, the IN user 101 enters the character to end digit collection session with the MS 102 and on receiving the end of session character, the MS 102 stops digit collection session. For example, the MS 102 may stop digit collection as End digit collection 6013. After collecting the digits entered by IN user 101, the MS 102 checks to see if IN user 101 has followed all required DTMF rules while entering the digits. If there is any error in the digits collected, then the digit collection session is stopped. If the check reveals that the digits follow the required DTMF rules, then the MS 102 locates the voiceback announcement based on the URL of the voiceback announcement received from the MGC 103. The MS 102 prefixes the voiceback announcement to the digits entered by the IN user 101 and plays the voiceback announcement to the IN user 101. For example, the voiceback announcement may be played as a Voiceback announcement 6014 message. The MS 102 then sends the collected digits and the result of the check, to determine if the digits follow the required DTMF rules to the MGC 103. For example, the MS 102 may send the collected digits and the result of the check to the MGC 103 in MSML/MSCIVR 6015 format in a SIP INFO message. The MGC 103 sends the message, obtained from the MS 102, to the SCP 104. For example, the response sent to the SCP 104 may be sent as a PACUI RSLT 6016 message.

[0032] In other embodiments, the SCP 104 may send a Boolean parameter to indicate to the MS 102 that voiceback announcement has to be made to the IN user 101. For example, the SCP 104 may send a voiceback parameter as "voiceback = True", in the PACUI message, to the MS 102 through the MGC 103. The SCP 104 may also send the prompt announcement ID and the required DTMF rules to the MGC 103. On receiving the voiceback announcement ID from the SCP 104, the MGC 103 maps the voiceback announcement ID to the corresponding URL of the voiceback announcement and sends the URL to the MS 102. The MGC 103 also maps the prompt announcement ID to the URL of the prompt announcement to be played to the IN user 101. The MGC 103 sends the URL of the prompt announcement and the DTMF rules to the MGC 103. The MS 102 locates the prompt announcement using the URL of the prompt announcement and plays the prompt announcement to the IN user 101. The MS 102 collects the digits entered by the IN user 101 and checks if the digits have been entered after complying with the required DTMF rules. If there is no error in the collected digits then the MS 102 prefixes the voiceback announcement to the collected digits and plays the voiceback announcement to the IN user 101. The voiceback announcement is different for different types of numbers entered by IN user 101.

[0033] The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the network elements. The network elements shown in Fig. 1, Fig. 2, Fig. 3 and Fig. 4 include blocks which can be at least one of a hardware device, or a combination of hardware device and software module. [0034] The embodiment disclosed herein specifies a system for voiceback announcement of digits to an IN user 101. Therefore, it is understood that the scope of the protection is extended to such a program and in addition to a computer readable means having a message therein, such computer readable storage means contain program code means for implementation of one or more steps of the method, when the program runs on a server or mobile device or any suitable programmable device. The method is implemented in a preferred embodiment through or together with a software program written in e.g. Very high speed integrated circuit Hardware Description Language (VHDL) another coding language, or implemented by one or more VHDL or several software modules being executed on at least one hardware device. The hardware device can be any kind of device which can be programmed including e.g. any kind of computer like a server or a personal computer, or the like, or any combination thereof, e.g. one processor and two FPGAs. The device may also include means which could be e.g. hardware means like e.g. an ASIC, or a combination of hardware and software means, e.g. an ASIC and an FPGA, or at least one microprocessor and at least one memory with software modules located therein. The method embodiments described herein could be implemented in pure hardware or partly in hardware and partly in software. Alternatively, the invention may be implemented on different hardware devices, e.g. using a plurality of CPUs. [0035] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the spirit and scope of the claims as described herein.

Claims

CLAIMS What is claimed is:

1. A method for announcement of digits to a user belonging to an Intelligent Network, said method comprising steps of: a Media Server (102) collecting digits entered by said user;

said Media Server (102) concatenating an audio announcement to said digits entered by said user, wherein said audio announcement depends on type of said digits entered by said user; and

said Media Server (102) playing said announcement to said user.

2. The method, as claimed in claim 1, wherein said method further comprises of a Service Control Point (104) sending an audio announcement ID to a Media Gateway Controller (103);

said Media Gateway Controller (103) mapping said audio announcement ID to a Uniform Resource Locator; and

said Media Gateway Controller (103) sending said Uniform

Resource Locator to said Media Server (102).

3. The method, as claimed in claim 2, wherein said Service Control Point (104) sends said audio announcement ID to said Media Gateway Controller (103) in a Prompt and Collect User Information message.

4. The method, as claimed in claim 3, wherein said Media Gateway Controller (103) sends said Uniform Resource Locator to said Media Server (102) in a Session Initiation Protocol (SIP) INFO message using one of Media Server Markup Language (MSML) and Media Server Control Interactive Voice Response (MSCIVR) format.

5. The method, as claimed in claim 1, wherein said method further comprises of said Service Control Point (104) sending a Boolean Parameter to a Media Gateway Controller (103);

said Media Gateway Controller (103) sending said Uniform Resource Locator to said Media Server (102).

6. The method, as claimed in claim 5, wherein said Service Control Point (104) sends said Boolean Parameter to said Media Gateway Controller (103) in a Prompt and Collect User Information message.

7. A Service Control Point (104) enabling announcement of digits to a user belonging to an Intelligent Network when digits have to be collected from said user, said Service Control Point (104) having at least one means adapted for sending an audio announcement ID to a Media Gateway Controller (103), wherein said audio announcement ID points to an audio announcement, wherein said audio announcement depends on type of said digits entered by said user and said audio announcement is played to said user after concatenating said audio announcement to said digits.

8. The Service Control Point (104), as claimed in claim 7, wherein said Service Control Point (104) is adapted to send said audio announcement ID to said Media Gateway Controller (103) in a Prompt and Collect User Information message.

9. A Media Gateway Controller (103) enabling announcement of digits to a user belonging to an Intelligent Network, when digits have to be collected from said user, said Media Gateway Controller (103) having at least one means adapted for sending a Uniform Resource Locator to a Media Server (102) to indicate a location of an audio announcement, wherein sai d audi o announcement i s played to sai d user after concatenating said audio announcement to said digits.

10. The Media Gateway Controller ( 103 ), as claimed in claim 9, wherein said Media Gateway Controller (103) is adapted to send said Uniform Resource Locator to said Media Server (102) in a Session Initiation Protocol (SIP) INFO message using one of Media Server Markup Language (MSML) and Media Server Control Interactive Voice Response (MSCIVR) format.

11. The Media Gateway Controller ( 103 ), as claimed in claim 9, wherein said Media Gateway Controller (103) is adapted to send said Uniform Resource Locator to said Media Server (102) on receiving an audio announcement ID from a Service Control Point (104).

12. The Media Gateway Controller (103), as claimed in claim 11, wherein said Media Gateway Controller (103) is adapted to map said audio announcement ID to said Uniform Resource Locator of said audio announcement.

13. A Media Server (102) enabling announcement of digits to a user belonging to an Intelligent Network, said Media Server (102) having at least one means adapted for: collecting digits entered by said user; and

playing an audio announcement to said user after concatenating said audio announcement to said digits, wherein said audio announcement depends on type of said digits.

14. The Media Server (102), as claimed in claim 14, wherein said Media Server (102) is adapted to receive a Uniform Resource Locator of said audio announcement from a Media Gateway Controller (103), wherein said Uniform Resource Locator indicates location of said audio announcement in said Media Server (102).