Source: http://www.google.com/patents/US7961862?ie=ISO-8859-1
Timestamp: 2014-09-21 17:03:35
Document Index: 551611019

Matched Legal Cases: ['arty 10', 'arty 30', 'arty 30', 'arty 10', 'arty 10', 'arty 30', 'arty 30', 'arty 30', 'arty 122', 'arty 122', 'arty 122', 'arty 122', 'arty 122', 'arty 112']

Patent US7961862 - Method and apparatus for providing ringback in a telecommunications network - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign in<nobr>Advanced Patent Search</nobr>PatentsA method of providing ringback in a telecommunications network (100) includes: receiving a call at a service switching point (114) for a called party (112) served by the service switching point (114), the call being from a calling party (122); encountering a trigger detection point (116) while engaging...http://www.google.com/patents/US7961862?utm_source=gb-gplus-sharePatent US7961862 - Method and apparatus for providing ringback in a telecommunications networkAdvanced Patent SearchPublication numberUS7961862 B2Publication typeGrantApplication numberUS 11/352,801Publication dateJun 14, 2011Filing dateFeb 13, 2006Priority dateFeb 13, 2006Also published asCN101385319A, CN101385319B, EP1985100A2, EP1985100B1, US20070201647, WO2007095226A2, WO2007095226A3Publication number11352801, 352801, US 7961862 B2, US 7961862B2, US-B2-7961862, US7961862 B2, US7961862B2InventorsRamachendra P. Batni, Ranjan SharmaOriginal AssigneeAlcatel-Lucent Usa Inc.Export CitationBiBTeX, EndNote, RefManPatent Citations (6), Referenced by (3), Classifications (14), Legal Events (3) External Links: USPTO, USPTO Assignment, EspacenetMethod and apparatus for providing ringback in a telecommunications networkUS 7961862 B2Abstract A method of providing ringback in a telecommunications network (100) includes: receiving a call at a service switching point (114) for a called party (112) served by the service switching point (114), the call being from a calling party (122); encountering a trigger detection point (116) while engaging in a call setup for the call, the trigger detection point (116) being provisioned for the called party (112) at the service switching point (114); in response to encountering the trigger detection point (116), extending a first leg of the call to a service node (130) that provides ringback to the calling party (122); setting-up a second leg of the call between the service node (130) and the called party (112); bridging together the first and second legs of the call at the service switching point (114); and, removing the service node (130) from participation in the call after the first and second legs have been bridged together at the service switching point (114).
FIELD The present inventive subject matter relates to the telecommunication arts. One particular application is found in conjunction with ETSI (European Telecommunications Standards Institute) wire-line networks, and the specification makes particular reference thereto. However, it is to be appreciated that aspects of the present inventive subject matter are also amenable to other like applications.
BACKGROUND In telephony, ringback or a ringback signal is an audible tone or series of tones or an audible message or other like signal provided to a calling party's telephone or other device or end user terminal (EUT) to indicate that the called party's EUT is receiving a ringing signal or is otherwise being alerted. Traditionally, in wire-line networks such as those conforming to the ETSI standards, the ringback signal is generated and/or provided by a telecommunications switch within the PSTN (Public Switched Telephone Network). For example, the switch may be a class 5 telecommunications switch such as Lucent Technologies 5ESS or another like switch. The ringback signal is commonly provided by the switch serving the called party, and the ringback signal is the same for all calls.
For example, with reference to FIG. 1, a calling party 10 being served by a switch or SSP (Service Switching Point) 12 places a call over the PSTN 20 to a called party 30 being served by a switch or SSP 32. Suitably, the customized ringback signals are generated and/or provided by a service node (SN) 34 operatively connected to the SSP 32, e.g., via trunks or other like transmission channels. Assuming the called party 30 subscribes to the customized ringback service, when the call placed by the calling party 10 makes its appearance at the SSP 32 (i.e., via the PSTN 30), the SSP 32 detects that special handling is to be provided by the SN 34. Accordingly, the SSP 32 extends the call to the SN 34 via one of the trunks (e.g., trunk 36). Traditionally, the SN 34 initiates a second leg of the call for the called party using a separate trunk (e.g., trunk 38), and in parallel, provides the subscriber selected ringback signal to the calling party 10. When the called party 30 answers the call, the SN 34 �bridges� or otherwise connects the two legs of the call together, as indicated by the hairpin or arrow 40.
As can be appreciated from the above example, call hair-pinning at the SN 34 in the manner shown unduly ties-up various resources. For example, the two trunks 36 and 38 are both occupied for the duration of the call. Moreover, resources within the SN 34 (e.g., ports, conference circuits, etc.) also remain used for the entire duration of the call. Accordingly, it is desirable to circumvent or bypass call hair pinning and/or extricate the SN 34 from participation in the call after the called party 30 has answered the call. That is to say, it is desirable to have a �call drop back� feature or function, whereby once the called party 30 has answered the call, the two call legs are bridged at the SSP 32 rather that being hair-pinned in the SN 34, thereby allowing the SN 34 to be dropped out of the call.
SUMMARY In accordance with one embodiment, a method of providing ringback in a telecommunications network includes: receiving a call at a service switching point for a called party served by the service switching point, the call being from a calling party; encountering a trigger detection point while engaging in a call setup for the call, the trigger detection point being provisioned for the called party at the service switching point; in response to encountering the trigger detection point, extending a first leg of the call to a service node that provides ringback to the calling party; setting-up a second leg of the call between the service node and the called party; bridging together the first and second legs of the call at the service switching point; and, removing the service node from participation in the call after the first and second legs have been bridged together at the service switching point.
DETAILED DESCRIPTION For clarity and simplicity, the present specification shall refer to structural and/or functional elements, entities and/or facilities, relevant communication standards, protocols and/or services, and other components and features that are commonly known in the art without further detailed explanation as to their configuration or operation except to the extent they have been modified or altered in accordance with and/or to accommodate the embodiment(s) presented herein.
Generally, a TDP (Trigger Detection Point) refers to a DP that is provisioned with a statically and/or manually armed trigger, e.g., armed via a suitable service management tool (SMT) 115 or the like. That is to say, a DP is made or turned into a TDP by arming a trigger associated with the DP. Optionally, different TDPs are classified as �Request� or �Notification� TDPs. Thus, during a call setup, either TDP-R's and/or TDP-N's may be encountered by the SSP 114. If an �-R� or �Request� type of TDP is encountered, then the SSP 114 suspends call processing when communication with the SN 130 is initiated. Suitably, call processing by the SSP 114 resumes when a response is received from the SN 130. Alternately, if an �-N� or �Notification� type of TDP is encountered, then the SSP 114 continues with call processing when the trigger fires, e.g., after it sends out the message to the SN 130 notifying the SN 130 that a certain event has occurred. Additionally, the TDPs encounter by the SSP 114 in the TBCSM may also be unconditional or conditional TDPs. Suitably, unconditional TDPs, e.g., invoke access to the SN 130 regardless of the call status or call data at that moment, while conditional TDPs, e.g., have additional criteria to be fulfilled before accessing of the SN 130 is performed.
In response to receiving the connect message in step 204, at step 206, the SSP 114 issues a SETUP or other like message to the address identified and/or referenced in the recently received connect message, i.e., to the ringback server 134. At this point, the ringback server 134 determines which one of a plurality of different customized or specialized ringback signals is to be played or otherwise provided to the calling party 122. For example, using logic and/or algorithms provisioned in the SN 130 and/or the ringback server 134, the chosen ringback is selected based upon one or more determinate factors. For example, the determinate factors are optionally, the identity of the calling party, the time, day and or date of the call, etc. Based upon the status or state of the determinate factors, the subscriber 122 sets as desired which one or more ringback signals are to be played and/or provided to the calling party 122. More specifically, e.g., the subscriber may select a ringback like the song �happy birthday� to be provided to the calling party 122 if the call in question is received on the calling party's birthday. Alternately, a subscriber may select a ringback that plays a customized message or a specific song to a calling party based upon the calling party's particular identity. Suitably, the subscriber 112 has a wide variety of different ringback signals to chose from and/or optionally they may create their own personalized ringback. Suitably, for a particular combination of determinate factors, the subscriber 112 optionally assigns one or more ringback signals to be chosen for playback to the calling party 122. In an exemplary embodiment, the actual states of the determinate factors for any given call are suitably obtained from the relevant call data and/or information contained in the setup message received in step 206. For example, the setup massage of step 206 includes the identity and/or telephone number of the calling party 122, the identity and/or telephone number of the called party 112, date and/or time stamp information, etc.
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS20040120494Dec 10, 2003Jun 24, 2004Shaoning JiangMethod and system for customized call terminationUS20050021713 *Apr 5, 2004Jan 27, 2005Andrew DuganIntelligent networkUS20050078812Oct 10, 2003Apr 14, 2005Batni Ramachendra P.Feedback to calling communication device on call connected with intelligent network signalingUS20050105706 *Sep 24, 2004May 19, 2005Antti KokkinenMethod and apparatus for providing pre-connection messaging and outputEP1523199A1Sep 29, 2004Apr 13, 2005Lucent Technologies Inc.Feedback to calling communication device on call connected with intelligent network signalingWO1998021901A1Nov 13, 1997May 22, 1998Nokia Telecommunications OyMerging of calls* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS8085929 *Jul 15, 2008Dec 27, 2011Verizon Patent And Licensing Inc.Method and apparatus for providing customized ringbacksUS8238523 *Dec 6, 2004Aug 7, 2012Realnetworks Asia Pacific Co., Ltd.Method and system for providing ring back tone service by using play announcement message in intelligent networkUS20070116244 *Dec 6, 2004May 24, 2007Choi Sung SMethod and system for providing ring back tone service by using play announcement message in intellegent network* Cited by examinerClassifications U.S. Classification379/207.16, 379/221.09, 379/221.08, 379/196, 379/201.01International ClassificationH04M3/42Cooperative ClassificationH04Q2213/13152, H04M3/42059, H04Q3/0029, H04M2203/2072, H04M3/42017, H04M3/4211European ClassificationH04Q3/00D3, H04M3/42BLegal EventsDateCodeEventDescriptionMar 7, 2013ASAssignmentFree format text: SECURITY INTEREST;ASSIGNOR:ALCATEL-LUCENT USA INC.;REEL/FRAME:030510/0627Effective date: 20130130Owner name: CREDIT SUISSE AG, NEW YORKApr 20, 2011ASAssignmentFree format text: MERGER;ASSIGNOR:LUCENT TECHNOLOGIES INC.;REEL/FRAME:026154/0521Owner name: ALCATEL-LUCENT USA INC., NEW JERSEYEffective date: 20081101Apr 18, 2006ASAssignmentOwner name: LUCENT TECHNOLOGIES INC., NEW JERSEYFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BATNI, RAMACHENDRA P.;SHARMA, RANJAN;REEL/FRAME:017770/0434;SIGNING DATES FROM 20060331 TO 20060405Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BATNI, RAMACHENDRA P.;SHARMA, RANJAN;SIGNING DATES FROM 20060331 TO 20060405;REEL/FRAME:017770/0434RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services©2012 Google