CA2590579A1 - Enabling native language support preferences in a telecommunications network - Google Patents
Enabling native language support preferences in a telecommunications network Download PDFInfo
- Publication number
- CA2590579A1 CA2590579A1 CA002590579A CA2590579A CA2590579A1 CA 2590579 A1 CA2590579 A1 CA 2590579A1 CA 002590579 A CA002590579 A CA 002590579A CA 2590579 A CA2590579 A CA 2590579A CA 2590579 A1 CA2590579 A1 CA 2590579A1
- Authority
- CA
- Canada
- Prior art keywords
- preference
- call setup
- native language
- language support
- network
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
- 238000000034 method Methods 0.000 claims description 37
- 238000004891 communication Methods 0.000 claims description 7
- 230000011664 signaling Effects 0.000 abstract description 21
- 230000006870 function Effects 0.000 description 7
- 230000002860 competitive effect Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
- H04M3/51—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/487—Arrangements for providing information services, e.g. recorded voice services or time announcements
- H04M3/493—Interactive information services, e.g. directory enquiries ; Arrangements therefor, e.g. interactive voice response [IVR] systems or voice portals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2203/00—Aspects of automatic or semi-automatic exchanges
- H04M2203/20—Aspects of automatic or semi-automatic exchanges related to features of supplementary services
- H04M2203/2061—Language aspects
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/42025—Calling or Called party identification service
- H04M3/42034—Calling party identification service
- H04M3/42059—Making use of the calling party identifier
- H04M3/42068—Making use of the calling party identifier where the identifier is used to access a profile
Abstract
The present invention enables service providers, e.g., VoIP service providers, to offer users the ability to register their native language or preferred language with a network based service so that all network announcements, network prompts, and network service features can be provided in the user~s native language. This provisioned parameter can be entered and stored in the network on a default basis or placed into the signaling messages on a per call basis.
Description
ENABLING NATIVE LANGUAGE SUPPORT PREFERENCES IN A
TELECOMMUNICATIONS NETWORK
[0001] The present invention relates generally to communication networks and, more particularly, to a method and apparatus for enabling native language support preferences in a packet-switched network, e.g., a Voice over Internet Protocol (VoIP) network.
BACKGROUND OF THE INVENTION
[00021 As the US becomes more diversified, the ability for service providers to offer features in multiple languages has become more critical to gain competitive advantages and to attract customers whose native language is not English. Therefore, a need exists for a method and apparatus for enabling native language support preferences in a packet-switched network, e.g., a Voice over Internet Protocol (VoIP) network.
SUMMARY OF THE INVENTION
[00031 In one embodiment, the present invention enables service providers, e.g., VoIP service providers to offer users the ability to register their native language with a network based service so that all network announcements, network prompts, and network service features can be provided in the user's native language. This provisioned parameter can be entered and stored in the network on a default basis_or placed into the signaling messages on a per call basis.
BRIEF DESCRIPTION OF THE DRAWINGS
[00041 The teaching of the present invention can be readily understood by considering the following detailed description in conjunction with the accompanying drawings, in which:
[0005] FIG. I illustrates an exemplary Voice over Internet Protocol (VoIP) network related to the present invention;
[0006] FIG. 2 illustrates an example of enabling native language support preference in a VoIP network of the present invention;
[0007] FIG. 3 illustrates a flowchart of a method for registering native language support preference of the present invention;
[0008] FIG. 4 illustrates a flowchart of a method for enabling native language support preference of the present invention; and [0009] FIG. 5 illustrates a high level block diagram of a general purpose computer suitable for use in performing the functions described herein.
[0010] To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures.
DETAILED DESCRIPTION
[0011] To better understand the present invention, FIG. I illustrates an example network, e.g., a packet-switched network such as a VoIP network related to the present invention. The VoIP network may comprise various types of customer endpoint devices connected via various types of access networks to a carrier (a service provider) VoIP core infrastructure over an Internet Protocol/Multi-Protocol Label Switching (IP/MPLS) based core backbone network. Broadly defined, a VoIP network is a network that is capable of carrying voice signals as packetized data over an IP network. An IP network is broadly defined as a network that uses Internet Protocol to exchange data packets.
[0012] The customer endpoint devices can be either Time Division Multiplexing (TDM) based or IP based. TDM based customer endpoint devices 122, 123, 134, and 135 typically comprise of TDM phones or Private Branch Exchange (PBX). IP based customer endpoint devices 144 and145 typically comprise IP phones or PBX. The Terminal Adaptors (TA) 132 and 133 are used to provide necessary interworking functions between TDM customer endpoint devices, such as analog phones, and packet based access network technologies, such as Digital Subscriber Loop (DSL) or Cable broadband access networks. TDM based customer endpoint devices access Vol P services by using either a Public Switched Telephone Network (PSTN) 120, 121 or a broadband access network via a TA 132 or 133. IP based customer endpoint devices access VoIP services by using a Local Area Network (LAN) 140 and 141 with a VoIP gateway or router 142 and 143, respectively.
[0013] The access networks can be either TDM or packet based. A TDM
PSTN 120 or 121 is used to support TDM customer endpoint devices connected via traditional phone lines. A packet based access network, such as Frame Relay, ATM, Ethernet or IP, is used to support IP based customer endpoint devices via a customer LAN, e.g., 140 with a VoIP gateway and router 142. A packet based access network 130 or 131, such as DSL or Cable, when used together with a TA 132 or 133, is used to support TDM based customer endpoint devices.
[0014] The core VoIP infrastructure comprises of several key VoIP
components, such the Border Element (BE) 112 and 113, the Call Control Element (CCE) 111, and VoIP related servers 114. The BE resides at the edge of the VoIP core infrastructure and interfaces with customers endpoints over various types of access networks. A BE is typically implemented as a Media Gateway and performs signaling, media control, security, and call admission control and related functions. The CCE resides within the VoIP infrastructure and is connected to the BEs using the Session Initiation Protocol (SIP) over the underlying IP/MPLS based core backbone network 110. The CCE is typically implemented as a Media Gateway Controller and performs network wide call control related functions as well as interacts with the appropriate VoIP
service related servers when necessary. The CCE functions as a SIP back-to-back user agent and is a signaling endpoint for all call legs between all BEs and the CCE. The CCE may need to interact with various VoIP related servers in order to complete a call that require certain service specific features, e.g.
translation of an E.164 voice network address into an IP address.
[0015] For calls that originate or terminate in a different carrier, they can be handled through the PSTN 120 and 121 or the Partner IP Carrier 160 interconnections. For originating or terminating TDM calls, they can be handled via existing PSTN interconnections to the other carrier. For originating or terminating VoIP calls, they can be handled via the Partner IP carrier interface 160 to the other carrier.
TELECOMMUNICATIONS NETWORK
[0001] The present invention relates generally to communication networks and, more particularly, to a method and apparatus for enabling native language support preferences in a packet-switched network, e.g., a Voice over Internet Protocol (VoIP) network.
BACKGROUND OF THE INVENTION
[00021 As the US becomes more diversified, the ability for service providers to offer features in multiple languages has become more critical to gain competitive advantages and to attract customers whose native language is not English. Therefore, a need exists for a method and apparatus for enabling native language support preferences in a packet-switched network, e.g., a Voice over Internet Protocol (VoIP) network.
SUMMARY OF THE INVENTION
[00031 In one embodiment, the present invention enables service providers, e.g., VoIP service providers to offer users the ability to register their native language with a network based service so that all network announcements, network prompts, and network service features can be provided in the user's native language. This provisioned parameter can be entered and stored in the network on a default basis_or placed into the signaling messages on a per call basis.
BRIEF DESCRIPTION OF THE DRAWINGS
[00041 The teaching of the present invention can be readily understood by considering the following detailed description in conjunction with the accompanying drawings, in which:
[0005] FIG. I illustrates an exemplary Voice over Internet Protocol (VoIP) network related to the present invention;
[0006] FIG. 2 illustrates an example of enabling native language support preference in a VoIP network of the present invention;
[0007] FIG. 3 illustrates a flowchart of a method for registering native language support preference of the present invention;
[0008] FIG. 4 illustrates a flowchart of a method for enabling native language support preference of the present invention; and [0009] FIG. 5 illustrates a high level block diagram of a general purpose computer suitable for use in performing the functions described herein.
[0010] To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures.
DETAILED DESCRIPTION
[0011] To better understand the present invention, FIG. I illustrates an example network, e.g., a packet-switched network such as a VoIP network related to the present invention. The VoIP network may comprise various types of customer endpoint devices connected via various types of access networks to a carrier (a service provider) VoIP core infrastructure over an Internet Protocol/Multi-Protocol Label Switching (IP/MPLS) based core backbone network. Broadly defined, a VoIP network is a network that is capable of carrying voice signals as packetized data over an IP network. An IP network is broadly defined as a network that uses Internet Protocol to exchange data packets.
[0012] The customer endpoint devices can be either Time Division Multiplexing (TDM) based or IP based. TDM based customer endpoint devices 122, 123, 134, and 135 typically comprise of TDM phones or Private Branch Exchange (PBX). IP based customer endpoint devices 144 and145 typically comprise IP phones or PBX. The Terminal Adaptors (TA) 132 and 133 are used to provide necessary interworking functions between TDM customer endpoint devices, such as analog phones, and packet based access network technologies, such as Digital Subscriber Loop (DSL) or Cable broadband access networks. TDM based customer endpoint devices access Vol P services by using either a Public Switched Telephone Network (PSTN) 120, 121 or a broadband access network via a TA 132 or 133. IP based customer endpoint devices access VoIP services by using a Local Area Network (LAN) 140 and 141 with a VoIP gateway or router 142 and 143, respectively.
[0013] The access networks can be either TDM or packet based. A TDM
PSTN 120 or 121 is used to support TDM customer endpoint devices connected via traditional phone lines. A packet based access network, such as Frame Relay, ATM, Ethernet or IP, is used to support IP based customer endpoint devices via a customer LAN, e.g., 140 with a VoIP gateway and router 142. A packet based access network 130 or 131, such as DSL or Cable, when used together with a TA 132 or 133, is used to support TDM based customer endpoint devices.
[0014] The core VoIP infrastructure comprises of several key VoIP
components, such the Border Element (BE) 112 and 113, the Call Control Element (CCE) 111, and VoIP related servers 114. The BE resides at the edge of the VoIP core infrastructure and interfaces with customers endpoints over various types of access networks. A BE is typically implemented as a Media Gateway and performs signaling, media control, security, and call admission control and related functions. The CCE resides within the VoIP infrastructure and is connected to the BEs using the Session Initiation Protocol (SIP) over the underlying IP/MPLS based core backbone network 110. The CCE is typically implemented as a Media Gateway Controller and performs network wide call control related functions as well as interacts with the appropriate VoIP
service related servers when necessary. The CCE functions as a SIP back-to-back user agent and is a signaling endpoint for all call legs between all BEs and the CCE. The CCE may need to interact with various VoIP related servers in order to complete a call that require certain service specific features, e.g.
translation of an E.164 voice network address into an IP address.
[0015] For calls that originate or terminate in a different carrier, they can be handled through the PSTN 120 and 121 or the Partner IP Carrier 160 interconnections. For originating or terminating TDM calls, they can be handled via existing PSTN interconnections to the other carrier. For originating or terminating VoIP calls, they can be handled via the Partner IP carrier interface 160 to the other carrier.
[0016] In order to illustrate how the different components operate to support a VoIP call, the following call scenario is used to illustrate how a VolP call is setup between two customer endpoints. A customer using IP device 144 at location A places a call to another customer at location Z using TDM device 135. During the call setup, a setup signaling message is sent from IP device 144, through the LAN 140, the VoIP Gateway/Router 142, and the associated packet based access network, to BE 112. BE 112 will then send a setup signaling message, such as a SIP-INVITE message if SIP is used, to CCE 111.
CCE 111 looks at the called party information and queries the necessary VoIP
service related server 114 to obtain the information to complete this call. If BE
113 needs to be involved in completing the call; CCE 111 sends another call setup message, such as a SIP-INVITE message if SIP is used, to BE 113.
Upon receiving the call setup message, BE 113 forwards the call setup message, via broadband network 131, to TA 133. TA 133 then identifies the appropriate TDM device 135 and rings that device. Once the call is accepted at location Z by the called party, a call acknowledgement signaling message, such as a SIP-ACK message if SIP is used, is sent in the reverse direction back to the CCE 111. After the CCE 111 receives the call acknowledgement message, it will then send a call acknowledgement signaling message, such as a SIP-ACK message if SIP is used, toward the calling party. In addition, the CCE 111 also provides the necessary information of the call to both BE 112 and BE 113 so that the call data exchange can proceed directly between BE 112 and BE
113. The call signaling path 150 and the call data path 151 are illustratively shown in FIG. 1. Note that the call signaling path and the call data path are different because once a call has been setup up between two endpoints, the CCE 111 does not need to be in the data path for actual direct data exchange.
[0017] Note that a customer in location A using any endpoint device type with its associated access network type can communicate with another customer in location Z using any endpoint device type with its associated network type as well. For instance, a customer at location A using IP customer endpoint device 144 with packet based access network 140 can call another customer at location Z using TDM endpoint device 123 with PSTN access network 121. The BEs 112 and 113 are responsible for the necessary signaling protocol translation, e.g., SS7 to and from SIP, and media format conversion, such as TDM voice format to and from IP based packet voice format.
[0018] As the US becomes more diversified, the ability for service providers to offer features in multiple languages has become more critical to gain competitive advantages and to attract customers whose native language is not English. To address this need, the present invention enables VolP service providers to offer users the ability to register their native language with a network based service so that all network announcements, network prompts, and network service features can be provided in the user's native language.
This provisioned parameter can be entered and stored in the network on a default basis or placed into the signaling messages on a per call basis.
[0019] FIG. 2 illustrates an example of enabling native language support preference in a VoIP network. A subscriber 220, (e.g., user A), registers his native language preference either via a telephone interface 230 or a website interface 240 to enter and store the subscriber's default preference. It should be noted that registering the subscriber's preference is broadly defined to include registering the language reference for the subscriber's endpoint device, for the subscriber's phone number, for the subscriber's name, for the subscriber's IP address and the like. The network stores his native language preference in an Application Server (AS) 213 and the preference can be retrieved by the CCE 211 during call processing when needed.
[0020] When CCE 211 receives a call or call setup 231 originating from or destined to user A, who is a subscriber of the native language support service feature, the CCE checks if language support is necessary, flow 232, for that call. If the call requires native language support, the language preference will be retrieved from AS 213 by CCE 211 in order to process the call appropriately.
For instance, for a call that the network needs to relay a network announcement to user A, the CCE 211 will use the user's default language preference, if the signaling indicates no other choice of language to be used. Namely, the network will relay the network announcement in the default language. In the case that if the signaling message of a call comprises a language preference selection, then CCE 211 will process the call requiring language support using the selected language indicated in the signaling message. If the selected language preference in a signaling message is different from the default language preference stored in the network, the language preference indicated in the signaling message will be used.
[0021] FIG. 3 illustrates a flowchart of a method 300 for registering native language support preference by the network. Method 300 starts in step 305 and proceeds to step 310.
[0022] In step 310, the method registers a subscriber's native language support preference either via a phone or website interface. For example, the subscriber can register Spanish, Chinese, Italian, German, Japanese, Russian, French, Portuguese and the like as the native language support preference.
[00231 In step 320, the method associates the default language preference with the subscriber's phone number and/or website login name. Method 300 ends in step 330.
[0024) FIG. 4 illustrates a flowchart of a method 400 for enabling native language support preference by the CCE. Method 400 starts in step 405 and proceeds to step 410.
[0025] In step 410, the method receives a call originated from or destined to a subscriber who has registered for native language support preference. In step 420, the method checks if the call requires language support features. If the call requires language support, the method proceeds to step 430;
otherwise, the calls proceeds to step 440.
[0026] In step 430, the method retrieves the default native language preference of the user either from the AS that stores the user's native language preference or the signaling message if the native language preference selection is present. Then CCE 211 applies the selected native language to process the call.
[0027] In one embodiment, if the language preference (e.g., Spanish) in the signaling message is different than the user's default native language preference (e.g., English), then the network will apply the language preference (e.g., Spanish in this example) as specified in the signaling message. This situation may arise if on a per call basis, a current user (e.g., someone who does not speak English) of the endpoint device may be a friend or relative of the subscriber. As such, the present invention allows on a per call basis for a user to override the default native language preference.
[00281 Alternatively, an incoming call that contains a(anguage preference (e.g., English) in the signaling message is different than the user's default native language preference (e.g., Spanish), then the network will apply the language preference (e.g., Spanish in this example) as specified in the user's default native language preference. This situation may arise from an organization who wants to contact the user in the manner most receptive to the user. If the user has a native language preference, then the calling party will want to accommodate that preference.
[00291 Returning to FIG. 4, in step 440, the method continues to process the call using the selected native language preference. If no selection is available from the user, the network uses the network default language to continue processing the call. The network default language is configurable by the network provider. Method 400 ends in step 450.
[0030] FIG. 5 depicts a high level block diagram of a general purpose computer suitable for use in performing the functions described herein. As depicted in FIG. 5, the system 500 comprises a processor element 502 (e.g., a CPU), a memory 504, e.g., random access memory (RAM) and/or read only memory (ROM), a native language support module 505, and various input/output devices 506 (e.g., storage devices, including but not limited to, a tape drive, a floppy drive, a hard disk drive or a compact disk drive, a receiver, a transmitter, a speaker, a display, a speech synthesizer, an output port, and a user input device (such as a keyboard, a keypad, a mouse, and the like)).
[00311 It should be noted that the present invention can be implemented in software and/or in a combination of software and hardware, e.g., using application specific integrated circuits (ASIC), a general purpose computer or any other hardware equivalents. In one embodiment, the present native language support module or process 505 can be loaded into memory 504 and executed by processor 502 to implement the functions as discussed above. As such, the present native language support process 505 (including associated data structures) of the present invention can be stored on a computer readable medium or carrier, e.g., RAM memory, magnetic or optical drive or diskette and the like.
[0032] While various embodiments have been described above, it should be understood that they have been presented by way of example only, and not limitation. Thus, the breadth and scope of a preferred embodiment should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.
CCE 111 looks at the called party information and queries the necessary VoIP
service related server 114 to obtain the information to complete this call. If BE
113 needs to be involved in completing the call; CCE 111 sends another call setup message, such as a SIP-INVITE message if SIP is used, to BE 113.
Upon receiving the call setup message, BE 113 forwards the call setup message, via broadband network 131, to TA 133. TA 133 then identifies the appropriate TDM device 135 and rings that device. Once the call is accepted at location Z by the called party, a call acknowledgement signaling message, such as a SIP-ACK message if SIP is used, is sent in the reverse direction back to the CCE 111. After the CCE 111 receives the call acknowledgement message, it will then send a call acknowledgement signaling message, such as a SIP-ACK message if SIP is used, toward the calling party. In addition, the CCE 111 also provides the necessary information of the call to both BE 112 and BE 113 so that the call data exchange can proceed directly between BE 112 and BE
113. The call signaling path 150 and the call data path 151 are illustratively shown in FIG. 1. Note that the call signaling path and the call data path are different because once a call has been setup up between two endpoints, the CCE 111 does not need to be in the data path for actual direct data exchange.
[0017] Note that a customer in location A using any endpoint device type with its associated access network type can communicate with another customer in location Z using any endpoint device type with its associated network type as well. For instance, a customer at location A using IP customer endpoint device 144 with packet based access network 140 can call another customer at location Z using TDM endpoint device 123 with PSTN access network 121. The BEs 112 and 113 are responsible for the necessary signaling protocol translation, e.g., SS7 to and from SIP, and media format conversion, such as TDM voice format to and from IP based packet voice format.
[0018] As the US becomes more diversified, the ability for service providers to offer features in multiple languages has become more critical to gain competitive advantages and to attract customers whose native language is not English. To address this need, the present invention enables VolP service providers to offer users the ability to register their native language with a network based service so that all network announcements, network prompts, and network service features can be provided in the user's native language.
This provisioned parameter can be entered and stored in the network on a default basis or placed into the signaling messages on a per call basis.
[0019] FIG. 2 illustrates an example of enabling native language support preference in a VoIP network. A subscriber 220, (e.g., user A), registers his native language preference either via a telephone interface 230 or a website interface 240 to enter and store the subscriber's default preference. It should be noted that registering the subscriber's preference is broadly defined to include registering the language reference for the subscriber's endpoint device, for the subscriber's phone number, for the subscriber's name, for the subscriber's IP address and the like. The network stores his native language preference in an Application Server (AS) 213 and the preference can be retrieved by the CCE 211 during call processing when needed.
[0020] When CCE 211 receives a call or call setup 231 originating from or destined to user A, who is a subscriber of the native language support service feature, the CCE checks if language support is necessary, flow 232, for that call. If the call requires native language support, the language preference will be retrieved from AS 213 by CCE 211 in order to process the call appropriately.
For instance, for a call that the network needs to relay a network announcement to user A, the CCE 211 will use the user's default language preference, if the signaling indicates no other choice of language to be used. Namely, the network will relay the network announcement in the default language. In the case that if the signaling message of a call comprises a language preference selection, then CCE 211 will process the call requiring language support using the selected language indicated in the signaling message. If the selected language preference in a signaling message is different from the default language preference stored in the network, the language preference indicated in the signaling message will be used.
[0021] FIG. 3 illustrates a flowchart of a method 300 for registering native language support preference by the network. Method 300 starts in step 305 and proceeds to step 310.
[0022] In step 310, the method registers a subscriber's native language support preference either via a phone or website interface. For example, the subscriber can register Spanish, Chinese, Italian, German, Japanese, Russian, French, Portuguese and the like as the native language support preference.
[00231 In step 320, the method associates the default language preference with the subscriber's phone number and/or website login name. Method 300 ends in step 330.
[0024) FIG. 4 illustrates a flowchart of a method 400 for enabling native language support preference by the CCE. Method 400 starts in step 405 and proceeds to step 410.
[0025] In step 410, the method receives a call originated from or destined to a subscriber who has registered for native language support preference. In step 420, the method checks if the call requires language support features. If the call requires language support, the method proceeds to step 430;
otherwise, the calls proceeds to step 440.
[0026] In step 430, the method retrieves the default native language preference of the user either from the AS that stores the user's native language preference or the signaling message if the native language preference selection is present. Then CCE 211 applies the selected native language to process the call.
[0027] In one embodiment, if the language preference (e.g., Spanish) in the signaling message is different than the user's default native language preference (e.g., English), then the network will apply the language preference (e.g., Spanish in this example) as specified in the signaling message. This situation may arise if on a per call basis, a current user (e.g., someone who does not speak English) of the endpoint device may be a friend or relative of the subscriber. As such, the present invention allows on a per call basis for a user to override the default native language preference.
[00281 Alternatively, an incoming call that contains a(anguage preference (e.g., English) in the signaling message is different than the user's default native language preference (e.g., Spanish), then the network will apply the language preference (e.g., Spanish in this example) as specified in the user's default native language preference. This situation may arise from an organization who wants to contact the user in the manner most receptive to the user. If the user has a native language preference, then the calling party will want to accommodate that preference.
[00291 Returning to FIG. 4, in step 440, the method continues to process the call using the selected native language preference. If no selection is available from the user, the network uses the network default language to continue processing the call. The network default language is configurable by the network provider. Method 400 ends in step 450.
[0030] FIG. 5 depicts a high level block diagram of a general purpose computer suitable for use in performing the functions described herein. As depicted in FIG. 5, the system 500 comprises a processor element 502 (e.g., a CPU), a memory 504, e.g., random access memory (RAM) and/or read only memory (ROM), a native language support module 505, and various input/output devices 506 (e.g., storage devices, including but not limited to, a tape drive, a floppy drive, a hard disk drive or a compact disk drive, a receiver, a transmitter, a speaker, a display, a speech synthesizer, an output port, and a user input device (such as a keyboard, a keypad, a mouse, and the like)).
[00311 It should be noted that the present invention can be implemented in software and/or in a combination of software and hardware, e.g., using application specific integrated circuits (ASIC), a general purpose computer or any other hardware equivalents. In one embodiment, the present native language support module or process 505 can be loaded into memory 504 and executed by processor 502 to implement the functions as discussed above. As such, the present native language support process 505 (including associated data structures) of the present invention can be stored on a computer readable medium or carrier, e.g., RAM memory, magnetic or optical drive or diskette and the like.
[0032] While various embodiments have been described above, it should be understood that they have been presented by way of example only, and not limitation. Thus, the breadth and scope of a preferred embodiment should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.
Claims (20)
1. A method for enabling language support preference in a communication network, comprising:
registering a native language support preference of a subscriber;
receiving a call setup from said subscriber or to said subscriber, where said call setup requires a language support; and processing said call setup in accordance with said native language support preference or a selected language preference in said call setup.
registering a native language support preference of a subscriber;
receiving a call setup from said subscriber or to said subscriber, where said call setup requires a language support; and processing said call setup in accordance with said native language support preference or a selected language preference in said call setup.
2. The method of claim 1, wherein said communication network is a Voice over Internet Protocol (VoIP) network.
3. The method of claim 1, wherein said native language support preference is registered via a telephone or a website interface.
4. The method of claim 1, wherein said registering comprises:
associating said native language support preference with at least one of:
at least one telephone number registered by said subscriber and at least one endpoint device.
associating said native language support preference with at least one of:
at least one telephone number registered by said subscriber and at least one endpoint device.
5. The method of claim 1, wherein said call setup is processed by a call control element (CCE).
6. The method of claim 1, wherein said processing comprises:
retrieving said native language support preference stored in the network;
and using said native language support preference to process said call setup if said selected language preference in not specified in said call setup.
retrieving said native language support preference stored in the network;
and using said native language support preference to process said call setup if said selected language preference in not specified in said call setup.
7. The method of claim 6, wherein said native language support preference is retrieved by a call control element (CCE) from an application server (AP).
8. The method of claim 1, wherein said processing comprises:
using said selected language preference instead of said native language support preference on a per call basis to process said call setup.
using said selected language preference instead of said native language support preference on a per call basis to process said call setup.
9. The method of claim 1, wherein said processing comprises:
using said native language support preference instead of said selected language preference in said call setup if said call setup is destined to said subscriber.
using said native language support preference instead of said selected language preference in said call setup if said call setup is destined to said subscriber.
10. A computer-readable medium having stored thereon a plurality of instructions, the plurality of instructions including instructions which, when executed by a processor, cause the processor to perform the steps of a method for enabling language support preference in a communication network, comprising:
registering a native language support preference of a subscriber;
receiving a call setup from said subscriber or to said subscriber, where said call setup requires a language support; and processing said call setup in accordance with said native language support preference or a selected language preference in said call setup.
registering a native language support preference of a subscriber;
receiving a call setup from said subscriber or to said subscriber, where said call setup requires a language support; and processing said call setup in accordance with said native language support preference or a selected language preference in said call setup.
11. The computer-readable medium of claim 10, wherein said communication network is a Voice over Internet Protocol (VoIP) network.
12. The computer-readable medium of claim 10, wherein said native language support preference is registered via a telephone or a website interface.
13. The computer-readable medium of claim 10, wherein said registering comprises:
associating said native language support preference with at least one of:
at least one telephone number registered by said subscriber and at least one endpoint device.
associating said native language support preference with at least one of:
at least one telephone number registered by said subscriber and at least one endpoint device.
14. The computer-readable medium of claim 10, wherein said call setup is processed by a call control element (CCE).
15. The computer-readable medium of claim 10, wherein said processing comprises:
retrieving said native language support preference stored in the network;
and using said native language support preference to process said call setup if said selected language preference in not specified in said call setup.
retrieving said native language support preference stored in the network;
and using said native language support preference to process said call setup if said selected language preference in not specified in said call setup.
16. The computer-readable medium of claim 15, wherein said native language support preference is retrieved by a call control element (CCE) from an application server (AP).
17. The computer-readable medium of claim 10, wherein said processing comprises:
using said selected language preference instead of said native language support preference on a per call basis to process said call setup.
using said selected language preference instead of said native language support preference on a per call basis to process said call setup.
18. The computer-readable medium of claim 10, wherein said processing comprises:
using said native language support preference instead of said selected language preference in said call setup if said call setup is destined to said subscriber.
using said native language support preference instead of said selected language preference in said call setup if said call setup is destined to said subscriber.
19. A system for enabling language support preference in a communication network, comprising:
means for registering a native language support preference of a subscriber;
means for receiving a call setup from said subscriber or to said subscriber, where said call setup requires a language support; and means for processing said call setup in accordance with said native language support preference or a selected language preference in said call setup.
means for registering a native language support preference of a subscriber;
means for receiving a call setup from said subscriber or to said subscriber, where said call setup requires a language support; and means for processing said call setup in accordance with said native language support preference or a selected language preference in said call setup.
20. The system of claim 19, wherein said communication network is a Voice over Internet Protocol (VoIP) network.
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US11/017,023 | 2004-12-20 | ||
| US11/017,023 US20060146993A1 (en) | 2004-12-20 | 2004-12-20 | Method and apparatus for enabling native language support preferences in a network |
| PCT/US2005/046057 WO2006069034A1 (en) | 2004-12-20 | 2005-12-20 | Enabling native language support preferences in a telecommunications network |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CA2590579A1 true CA2590579A1 (en) | 2006-06-29 |
Family
ID=36118128
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002590579A Abandoned CA2590579A1 (en) | 2004-12-20 | 2005-12-20 | Enabling native language support preferences in a telecommunications network |
Country Status (6)
| Country | Link |
|---|---|
| US (1) | US20060146993A1 (en) |
| EP (1) | EP1829349A1 (en) |
| JP (1) | JP2008524964A (en) |
| KR (1) | KR20070097043A (en) |
| CA (1) | CA2590579A1 (en) |
| WO (1) | WO2006069034A1 (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR100969760B1 (en) * | 2007-03-09 | 2010-07-13 | 삼성전자주식회사 | Apparatus and method for providing a voice message in a communication system |
| US20090187398A1 (en) * | 2008-01-18 | 2009-07-23 | Avaya Technology Llc | Script Selection Based On SIP Language Preference |
| US8279861B2 (en) * | 2009-12-08 | 2012-10-02 | International Business Machines Corporation | Real-time VoIP communications using n-Way selective language processing |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7106843B1 (en) * | 1994-04-19 | 2006-09-12 | T-Netix, Inc. | Computer-based method and apparatus for controlling, monitoring, recording and reporting telephone access |
| US5841852A (en) * | 1995-12-29 | 1998-11-24 | Mci Communications Corporation | Method and system for telecommunications language support |
| US6038292A (en) * | 1997-11-07 | 2000-03-14 | American Express Travel Related Services Company, Inc. | Methods and apparatus for language registration of prepaid, remote entry customer account |
| US6757023B2 (en) * | 1999-10-14 | 2004-06-29 | Mustek Systems Inc. | Method and apparatus for displaying and adjusting subtitles of multiple languages between human-machine interfaces |
| US7027990B2 (en) * | 2001-10-12 | 2006-04-11 | Lester Sussman | System and method for integrating the visual display of text menus for interactive voice response systems |
| US6925155B2 (en) * | 2002-01-18 | 2005-08-02 | Sbc Properties, L.P. | Method and system for routing calls based on a language preference |
| EP1808010A2 (en) * | 2004-10-25 | 2007-07-18 | Intrado, Inc. | System and method for unilateral verification of caller location information |
| US7372851B2 (en) * | 2006-06-28 | 2008-05-13 | International Business Machines Corporation | Method and system for automatic language negotiation on voice (over IP) calls |
-
2004
- 2004-12-20 US US11/017,023 patent/US20060146993A1/en not_active Abandoned
-
2005
- 2005-12-20 EP EP05854720A patent/EP1829349A1/en not_active Withdrawn
- 2005-12-20 CA CA002590579A patent/CA2590579A1/en not_active Abandoned
- 2005-12-20 KR KR1020077013921A patent/KR20070097043A/en not_active Application Discontinuation
- 2005-12-20 JP JP2007548375A patent/JP2008524964A/en active Pending
- 2005-12-20 WO PCT/US2005/046057 patent/WO2006069034A1/en active Application Filing
Also Published As
| Publication number | Publication date |
|---|---|
| KR20070097043A (en) | 2007-10-02 |
| WO2006069034A1 (en) | 2006-06-29 |
| JP2008524964A (en) | 2008-07-10 |
| US20060146993A1 (en) | 2006-07-06 |
| EP1829349A1 (en) | 2007-09-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9210027B2 (en) | Method and apparatus for enabling phone number dialing using email addresses | |
| US20070189469A1 (en) | Method and apparatus for providing location information for an emergency service | |
| US9137361B2 (en) | Method and apparatus for enabling global telephony capabilities in communication networks | |
| EP1748634A2 (en) | Method and apparatus for protecting calling party identification | |
| WO2006071935A1 (en) | Method and apparatus for providing multiple calling name identifiers for a phone number | |
| EP1677504A1 (en) | Method and apparatus for registering multiple phone numbers associated with a frequently called party | |
| CA2588800A1 (en) | Downloading of network based information to ip phones | |
| US20100086115A1 (en) | Method and apparatus for providing an audible calling party identification for a call waiting service | |
| US8064452B2 (en) | Method and apparatus for routing calls to an alternative endpoint during network disruptions | |
| WO2006069212A1 (en) | Personalized calling name identification in telecommunication networks | |
| US8730941B1 (en) | Method and apparatus for providing multiple calling name identifiers | |
| US7734021B1 (en) | Method and apparatus for supporting out of area phone number for emergency services | |
| US7734024B1 (en) | Method and apparatus for providing user access via multiple partner carriers for international calls | |
| CA2590579A1 (en) | Enabling native language support preferences in a telecommunications network | |
| US20100135281A1 (en) | Method and apparatus for sending updates to a call control element from an application server | |
| US7881289B1 (en) | Method and apparatus for porting telephone numbers of endpoint devices | |
| US7664252B1 (en) | Method and apparatus for sending alerts to internet protocol phones | |
| US8295461B1 (en) | Method and apparatus for re-originating calls | |
| US7852832B1 (en) | Method and apparatus for providing secure interface to externally hosted application servers | |
| US20060182257A1 (en) | Method and apparatus for notifying the calling party about the status of the called endpoint |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| FZDE | Discontinued |