The present invention provides a network-based personalized music on hold system for communications service providers, e.g., a telephone company, a cable TV company, a wireless carrier, etc. Communications service providers may offer the network-based personalized music on hold system as a personalized music on hold service to business and residential subscribers. The personalized music on hold system assists a music on hold (MoH) subscriber, e.g., a business, a residential telephone subscriber, etc., in customizing a listening experience for callers by allowing the personalized MoH subscriber to select a music type, a music genre, and/or a music track chosen specifically for the callers to be played and listened to when the callers are placed on hold by the MoH subscriber. One or both parties, i.e., callers and called parties, on a call may be a personalized MoH subscriber and the personalized MoH subscriber(s) may place the other party, i.e., callers or called parties, on hold and initiate the personalized music on hold feature.
MoH Application Server 110 is one or more of an application server that provides a MoH selection, e.g., a music clip, to a caller when the caller has been placed on hold by a MoH subscriber that uses personalized music on hold system 100. In one embodiment of the invention, MoH Application Server 110 is invoked to obtain the MoH selection chosen by the MoH subscriber for the caller on hold when the MoH subscriber presses a service access code, e.g., *98, on a telephone during a telephone conversation. In another embodiment of the invention, MoH Application Server 110 is invoked to obtain the MoH selection chosen by the MoH subscriber for the caller when the MoH subscriber places the caller on hold to answer a Call Waiting service call. In yet another embodiment of the invention, MoH Application Server 110 is invoked to obtain the MoH selection chosen by the MoH subscriber for the caller when a Session Description Protocol (SDP) offer transmitted from the MoH subscriber's telephone contains a request to put a session on hold.
MoH Application Server 110 accesses a stored profile and determines the MoH selection based on an interest of the caller maintained in the profile. MoH Application Server 110 signals MoH Front End 120 to transmit the MoH selection to the caller's telephone, and to play the MoH selection during the silent period of the call while the caller is placed on hold by the MoH subscriber. In one embodiment of the invention, the MoH subscriber may press a second service access code, e.g., *99, on any telephone to invoke MoH Application Server 110 to terminate the MoH selection when the MoH subscriber is ready to resume the conversation with caller. In another embodiment of the invention, the MoH subscriber pivots from the Call Waiting service call to the caller to terminate the MoH selection. In yet another embodiment of the invention, the MoH selection is terminated when a SDP offer transmitted from the MoH subscriber's telephone contains a request to retrieve the call from on hold.
Optionally, MoH Application Server 110 allows callers receiving music while on hold to change characteristics of the music, e.g., increase or decrease volume, pause, deactivate or activate the MoH selection, by pressing a dual tone multi-frequency (DTMF) key on their telephone.
When implemented in a network, such as an IP Multimeda Subsystem (IMS), as will be appreciated by those skilled in the art, one or more of MoH Application Server 110 may serve hundreds or thousands of users of personalized music on hold system 100 within a given area. MoH Application 110 is connected to MoH Front End 120 via a SIP interface, Services manager 150 via a Transmission Control Protocol/Internet Protocol (TCP/IP) interface, and IP Network 160 via a Real Time Protocol (RTP) interface. MoH Application 110, in one embodiment, comprises one or more of an Enhanced Media Resource Server (eMRS) (Lucent Technologies).
MoH Front End 120 is one or more of an application server that manipulates a call path between callers and MoH Application Server 110. More specifically, MoH Front End 120 determines when a caller has been placed on hold by the MoH subscriber that uses personalized music on hold system 100. In one embodiment of the invention, MoH Front End 120 determines when a caller has been placed on hold based on an evaluation of the DTMF signals received when the MoH subscriber presses the first service access code, e.g., *98. In another embodiment of the invention, MoH Front End 120 determines when the caller has been placed on hold when the MoH subscriber answers a Call Waiting service call. In yet another embodiment of the invention, MoH Front End 120 determines when the caller has been placed on hold by determining whether a Session Description Protocol (SDP) offer transmitted from the MoH subscriber's telephone contains a request to put a session on hold. Upon determining that the MoH subscriber has placed the caller on hold, MoH Front End 120 transmits a request to MoH Application Server 110 to find an appropriate MoH selection to play during the silent period while the caller is on hold. When MoH Application Server 110 finds the MoH selection, then MoH Front End 120 transmits the MoH selection to the caller.
Upon determining that the caller is no longer on hold, MoH Front End 120 transmits a request to MoH Application Server 110 to terminate the music. In one embodiment of the invention, MoH Front End 120 determines that the caller is no long on hold based on an evaluation of the DTMF signals received when the MoH subscriber presses the second service access code, e.g., *99. In another embodiment of the invention, MoH Front End 120 determines that the caller is no long on hold when the MoH subscriber pivots from the Call Waiting service call to the caller. In yet another embodiment of the invention, MoH Front End 120 determines that the caller is no long on hold when a SDP offer transmitted from the MoH subscriber's telephone contains a request to retrieve the call from on hold.
MoH Front End 120 is connected to MoH Application Server 110 and Control Layer 130120 via SIP interfaces. MoH Front End 120, in one embodiment, comprises one or more of a Feature Server 5000 (Lucent Technologies).
Control Layer 130 provides network control for voice and data services. Control Layer 130 performs communication session set up, tear down, coordination and blending of multimedia services. Control Layer 130 is connected to MoH Front End 120 and Gateway 140 via SIP interfaces, and IP Network 160 via a RTP interface. Control Layer 130, in one embodiment, comprises one or more of an Session Control Layer (Lucent Technologies).
Gateway 140 bridges both traditional circuit networks and Internet Protocol (IP) networks by providing translations between IP network and circuit network transport protocols. Gateway 140 passes bearer traffic among public switched telephone network (PSTN) and IP networks for SIP-enabled devices and wireline and wireless callers. Gateway 140 is bearer protocol agnostic, supporting a wide variety of time division multiplexing (TDM), voice over IP (VoIP) and wireless applications. Gateway 140 is connected to Control Layer 130 via a SIP interface, IP network 160 via a RTP interface, and circuit network 170 via circuit bearer channels. Gateway 140, in one embodiment, comprises one or more of a Lucent Network Gateway (Lucent Technologies).
Services manager 150 is a management system that provides operations, administration, maintenance and provisioning (OAM&P) support for MoH Application Server 110. Services manager 150 assists the MoH subscriber that uses personalized music on hold system 100 in configuring, i.e., creating, editing, and updating, etc., a stored profile. The MoH subscriber configures the stored profile to a) determine what music to play, i.e., a MoH selection, when callers are placed on hold and b) impose conditions for when to play specific MoH selections. The MoH subscriber may access their account via an Internet web portal tool to Services manager 150 in order to configure profiles maintained by the MoH subscriber. The Internet web portal tool may be a personal computer that allows access to Services manager 150's software configuration data. Upon accessing the account, the MoH subscriber may, illustratively, configure a profile for a caller A to play song #1 when caller A has been placed on hold. Also illustratively, the MoH subscriber may configure a profile for a caller B to play song #2 when caller B has been placed on hold on any Monday. Further illustratively, the MoH subscriber may configure a profile for anyone from the New York Yankees baseball team to play song #3 when anyone from the New York Yankees baseball team has been placed on hold.
In some instances, the MoH subscriber may desire to configure personalized music on hold system 100 to deactive the music on a per call basis. Illustratively, the MoH subscriber may desire to deactive the music on hold during a conference call in which one or more conferees may be placed on hold.
Services manager 150 is connected to MoH Application Server 110 via a TCP/IP interface. Services manager 150, in one embodiment, comprises one or more of an Enhanced Services Manager (eSM) (Lucent Technologies).
Those of ordinary skill in the art will readily be able to select application servers, Control Layers, and gateways appropriate for use in any particular implementation of the personalized music on hold system 100.
A first column of the profile may provide a name of the callers. The name of the callers may be the name of a business, the name of an individual, or a default assignment. The length of the name may be limited to a predetermined width of the column.
A second column of the profile may provide a telephone number of the callers.
A third column of the profile may provide an affiliation of the callers, such as a hobby, a favorite sport, or an employer.
A fourth column of the profile may provide a condition for transmitting a music on hold selection to the callers. The condition may include a date, a time interval, e.g., between 8:00 a.m. and 10:00 a.m., a specific day and time, e.g., Monday at 1:00 p.m., or an area code of each caller.
A fifth column of the profile may provide and identify a music on hold (MoH) selection that may be based on an interest of the callers chosen by the MoH subscriber that uses personalized music on hold system 100. Also, the MoH selection chosen by the MoH subscriber may be used as a technique for distinguishing between callers. Illustratively, callers from different area codes may have different MoH selections. Also, illustratively, callers from the same employer or the same interest group may have the same MoH selections. The MoH selection may be a) at least one song title, b) at least one musical artist, c) at least one musical group, d) at least one music genre, or e) a random song selection. Optionally, the music on hold selection may be pre-selected by the caller.
The profile may be stored in MoH Application Server 110 and the profile may be administered by Services manager 150. The telephone number of the caller and the telephone number of the MoH subscriber may be used as a unique identifier to access a particular record of a caller. Records used to populate the profile may be provided from a customer directory if the MoH subscriber is a business subscriber or a telephone address book if the MoH subscriber is a residential subscriber.
Advantageously, personalized music on hold system 100 plays music selected for specific callers by the MoH subscriber to personalize the listening experience of the specific callers. The MoH subscriber may be a business or residential subscriber. Also advantageously, MoH subscribers using personalized music on hold system 100 can distinguish between callers on hold with the music selections. Further advantageously, the existence of a network connection to the callers on hold means that the connection between the MoH subscriber and MoH Application Server 110 can be completely dropped. Thus, the MoH subscriber using personalized music on hold system 100 may hang up the telephone, leaving the callers on hold listening to the MoH selection. This situation may benefit businesses with leased line connections, because the businesses may be able to accommodate more simultaneous calls per hour without using additional ports on a PBX.
At 1, User 1 uses a hook-flash on a telephone and dials a “call hold” service access code, e.g., *98. User 1's customer provided equipment (CPE) transmits an INVITE request to an application server, e.g., MoH Application Server 110 (
At 2 (
At 3, the MoH MRF selects a User Datagram Protocol (UDP) port and IP address, and transmits this information in a Session Description Protocol (SDP) offer as part of a 200 OK response. The SDP offer is the method for negotiating the bearer path characteristics.
At 4, the application server transmits a REINVITE request to User 2. The SDP offer received from the MoH MRF is included in the REINVITE request.
At 5, User 2's CPE transmits a SDP answer as part of a 200 OK response.
At 6, the SDP answer received from User 2 is transmitted in an ACK response to the MoH MRF, and a bearer path is now established between the MoH MRF and User 2. User 2 now hears the music supplied by the MoH MRF.
At 7, the application server will confirm the INVITE request transmitted by User 1 by transmitting a 200 OK response.
At 8, the application server transmits a BYE response to User 1 terminating the dialog. User 1 can now hang up the telephone, leaving User 2 on hold listening to the MoH selection.
At 1, User 1 dials a “call retrieve” service access code, e.g., *99, from any telephone to retrieve the call on hold. User 1's CPE transmits an INVITE request to an application server, e.g., MoH Application Server 110 (
At 2 (
At 3 (
At 4 (
The foregoing merely illustrates the embodiments of the invention. It will thus be appreciated that those skilled in the art will be able to devise various arrangements, which, although not explicitly described or shown herein, embody the principles of the invention, and are included within its spirit and scope.