CA2174799C - Method for determining an optimum point for database queries during call delivery in a telecommunications network - Google Patents
Method for determining an optimum point for database queries during call delivery in a telecommunications networkInfo
- Publication number
- CA2174799C CA2174799C CA002174799A CA2174799A CA2174799C CA 2174799 C CA2174799 C CA 2174799C CA 002174799 A CA002174799 A CA 002174799A CA 2174799 A CA2174799 A CA 2174799A CA 2174799 C CA2174799 C CA 2174799C
- Authority
- CA
- Canada
- Prior art keywords
- switch
- lnp
- database
- central office
- optimum
- 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.)
- Expired - Fee Related
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q3/00—Selecting arrangements
- H04Q3/0016—Arrangements providing connection between exchanges
- H04Q3/0029—Provisions for intelligent networking
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13513—UPT - personal as opposed to terminal mobility, inc. number portability
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13522—Indexing scheme relating to selecting arrangements in general and for multiplex systems traffic management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13547—Indexing scheme relating to selecting arrangements in general and for multiplex systems subscriber, e.g. profile, database, database access
Abstract
A method for determining an optimum database query point during call delivery in a telecommunications network comprises a local number portability traffic analysis system (LNP-TAS) in communication with at least one originating central office switch and one standard terminating central office switch in the telecommunications network. The LNP-TAS receives LNP database-related query statistics from each central office switch at predetermined intervals to determine an optimum database query point based upon predefined optimization criteria.
Upon determination of an optimum database query point, the LNP-TAS updates the appropriate switches with switch control update messages in accordance with the optimization determination.
Upon determination of an optimum database query point, the LNP-TAS updates the appropriate switches with switch control update messages in accordance with the optimization determination.
Description
21 7~
METHOD FOR DETERMINING AN OPTIMUM POINT FOR DATABASE QUERIES
DURING CALL DELIVERY IN A TELECOMMUNICATIONS NETWORK
5 Technical Field This invention relates to a method and system for A.~te....;~ g an ol)thllulll point during call delivery for ~.Çolllling A~t~b,~e queries le.luiled for routing calls to ported directory in a local telecoll~.ulications ~ wu~
The public-~wilched t~l~ph--l-e nelwc,l~ in~ll)Aes: a large number of central office ~wi~L~s serving local ~ slu~, lines and trunks; a smaller nulll~l of tandem ~wil~hes for providing u~ P~ n~ n central office swilcllej, a co.. ~ c ~,lwvlL cQmrri~ing a large n~b~. of analog and digital coll~lul~ic~tion paths intc~Q~ e~,t;.~g the centTal offlce ~wi~l~s and tandem swi~l~e" and optional ~ s, such as local number portability (LNP) 5 A~ hs~ 5, for storing routing data wd by swi~L~s for call d~ e. ~ .
Calls ~t~ n t~l~h- ne Cu~)lll,.a in the United States are established on the basis of a n~tion~l di,~Lol~ n.,l,l~ plan which ,~u"~s a caller to dial seven or ten digits to identify a called party. A 1 0-digit dialed dh~,~to, ~ number Co~ " ;~,,s a thre~e-digit area code (generally denoted by the letters "NPA") which defines a s~ ;rc geoL; r~hic region and p,~edes a three 20 digit office code (d~ 3d by the letters '~') which id .1;rFs a particular central office switch that serves the called party. The office code is followed by a four digit ~iu~lulll~,. line id~ ;r.~ Jt~ by the letters "X~X'). A seven-digit dialed di~ecto,,~ number is indicative of an intra-area code call and simply co.. .l..; ~,s the three-digit offlce code ('~') followed by a four~igit customer line id~ -~1;fi'-,~ ("X~'). Although a calla may dial only seven digits 25 (NXX-XXX~ when placing a call, the calla's area code (NPA) is often p,~ ed to the dialed seven digits by a digit l~C~i;Ving switch (i.e. the originating switch), as is known in the art.
fo.~" evay o~ltgoing call can be treated as a 10 digit di,~ number even if the caller only actually dials seven digits.
There are catain S;IV~1;QI~C in which the operations of an ~ 8 ~wilching ~,lwo,k can 30 benefit from the int~d~lçtior of additional centTal office awi~hes which share one or more ~1 74799 office codes with the eYiCting IklWOIk. Indeed, during the next several years, it is expected that the Ill~n~ held by local eY~ k~nge carriers (LECs) in providing local telephnn~ service will be s~ y altered and that co...~ ;ve access providers (CAPs) will offer local telephone service to ~ tO~ a. When a awilchillg n~lwo~ n~ d by a CAP is added to a particular geographic area ( i.e. a local access teleco.. l~-lic~tions area (LATA)), it is generally desirable that any ~r~. of c~ u....,. Iines ~e~e."l the eYi~ting local e~ nge carrier and co~ ilive access providers occur wi~oul c~ s to ~ e~ dil~,~,lo. ~ numbers.
Dile~,t~ numbers that include office code digits ck~ t~,~ ;C tiC of a first central office switch but which identify .;~ lu.. .Iines actually served by a second central office switch are knownas"ported"dL~,.,l~" ......... ~ ~ Properdeli~ of callsto~ lu.~ withported ~lL~ r mlrnhers le~uil~s l~h;~ of routing data by a central office switch from a local n.~l.,~, portability (LNP) database. Current ~e~luile,lle~'ta for a pl~,f~ d imple . . nt~1 ;on of the LNP ~ h.q~ system specify that retrieval of routing data may be ~ fv....ed either by the central offlce switch in the local area which first l~ S the dialed digits of the ported dL~
15 number (i.e. the "ori~;n~ ' switch) or the central office switch which would normally sene the dialed NXX (i.e. the ' at;~ni ~ g" switch).
One solution for establishin~ the point in a call delivery process at which the LNP
database is queried lC~Uile,S ori~ swil~ih~s to launch LNP~ bq~e queries each time t~ ~1 (i.e. "trigger") NPA-NXX digits are ~ .~. More particularly, this solution20 l~ ,s o ig;" ~1;"g swilch~s to make LNP database queries if the called NPA-NXX digits are ntifi~ as trigger digits. Under current practice, the NPA-NXX digits are marked and stored in the orig~ g switch ~ GI~ as triggers as soon as a single di~e.,tul~ number is ported from the id. ..1;1~ triggcr NXX. Retrieval of routing data by the orig;. - 1;.~g switch is the most time-~IT;C;.~ .~t ma~ for del;~,~g an o~lg~ g call to a ported d~ul~ nu.llber since the serving 25 switch (i.e. thc central office s vitch that actually serves the ported di~ number) is identifi~ before call delivery is attempted. However, ~lu~ ing an LNP~1A~hq~ for routing data is least el~ 1 for non-ported numbers which need no ~d~iiti~n~ql routing infolll~lion.
Hence, if only a few ~ u.. ~ leph~ne lines in a trigger '~' (i.e. s~dd~ tf - ~ g central office switch) have been ported, I~ g LNp~l~t~h~q~e queries at the origjnqting 21 74~q9 switch may cause n~lPss LNP ~ ,.bq~ queries as the vast majority of queries result in a ~'no routing data found" ~on3e.
Another solution for establishing the point in the call deli~,e.~ process at which an LNP
~Iqt~hq~ is queried is a default query process. In accor~ ce with the default query approach, S LNP ~t~ha~e queries are p~- r.. ~d by the ~ldald t~ .. in~ g switch (that is, the switch which normally serves the dialed N~-X~X that has now been ported). Particularly, a standard t~ g switch which lecf ivcs an ;I-~o...i~g call initially ~t~lll~ to deliver the call norm~lly (i.e. wi~loul querying an LNP ~ t ~bq~). If the call cannot be delive.~ norrnally, an LNP ~t~h~e query is l.-~.n~l-e~ RetIieval of routing data from an LNP ~ h.q~e by the 10 standard tf ~ ~ g switch ...in;-n;~cs the nurnber of LNP datab~ queries since the majority of calls dcli~ d to the t~ ...;.. ~t;l~g switch will be dcli~ d n~ rn~lly. However, for every ported n-lm~, a re-routing from a ~l~d~.l t~-...in~ R switch is l~UilC;I. Hence, if a particular ~ ~ad&.l ~ .;n~ g switch has many ported dir~;tu.~ nllmh~, a default LNP ~l~t~b~e query process iWl~S the overall call dcli~,.y time of ported nllmh~s since the call has been 15 initially routed to a central office switch that no longer serves the dialed dh nurnber.
Although the a l~t;~ges and dis~l~lt2 ges of ~lu~ . ~ing an LNP ~ UbA u at the orig;--~ g or s~d~d ~ g switch are known, plup~sed impl~ .."~t~l;on.~ of LNP
'hA'~ s~s~ llS do not address the need to intPlligently ~1~ t~ F an ~IJ1;-------- LNP ~l~t~b~e query point ( i.e. either the originating switch or the standard t~minating switch) in the call 20 dcli~ process and to automatically ie ~o~d to the dynamic nature of ported dile~,lol.~ nurnber traffic. Indeed, the current practice of storing trigger NPA-N~ digits in central office switches upon h~r~. of a single d;l~t~ nulll~. out of the trigger N~ e1;...i'~t~s the ability of the ~,lwull~ to rcflect to actuai ported dir~;t~l ~ nu~l traffic.
rh~ef~, there is a need in the art for inte11ig~nt1y ~ t - ~--;~ g the o~ um point for 25 ~lu~ ing an LNP database to ûbtain routing data lequ,l~ for call del;~ and ~ I;c~l1y 8 central office swil~;l~s in _CCûl'~ Ce with the ~ t~ ...;l. ~1;o--This need is addressed and a tec-hnic~1 advance is ach;e.od in the art by the method and system ofthe present invention which aulo...~tic~l1y gathers LNP ~,~t:~b-4~e related query 21 74~59 sPtic ics to ~ an o~)till~Ulll LNP~l~t~h~ce query point in a call delivery process and updates central office swilel~es in accord~ce with the ~ ;on In one plY fe~l~,d ~bodi~ t of the method of the present invention, a local number portability traffic analysis system (LNP-TAS)is established such that it receives LNp~l~t~bqce 5 related query stqtictics from each centTal office switch in its service area. The LNP-TAS uses the st~tictic~l info....~;on to int~llig~ontly det~ the o~tilllUlll LNP dqt~b~ce query point. In op~tiQn each LNP-l ~Ahq~e query p. .Çu~lled by a central office switch is recorded. The record includes v~h~ . or not the dialed dil~ lol ~ is a ported dilcc~ol~/ number, the time ed to pl . ru- - - - the query and the serving office of ported dh~ ~tul ~ nllm~ s The 10 comriled st~tictics are ~ .;l~l by each switch, at pl~dct~ ...;..ed intervals, to the LNP-TAS
over designated data links. The LNP-TAS analy~s the st~tictics using predçfined o~ l ;on criteria (or objectives) to d~ h .. ~ e the plefe.l~d point in the call deli~ process (i.e. ei~er the orig;~ g switch or a particular standard t~ ...;~.z~ g switch) for l~ g LNP ~ h~e queries in accol~ce with the pl~d~ Pd criteria F.Yr .1rs of o~lt;l~ t;on criteria include 15 ...;~ 1;on of call del;~ r delay, ~ i...;7~l;on of .1~1;,h~ query cost for a particular local service provider, Gpt;...;- A routing based on time of day/week or class of service, or m~n~g~nPnt of ll. lwul~ peal~ hour LNP d~b~ queries. If a change in the LM ~l~t~h~e query point is necessary, the LNP-TAS sends an update e~-~ge directly to the a~pl~opl;~te centTal office switch(es) to ~.. ~te the change.
For ~e r'e assume that the LNP-TAS has been initis31i7e~ with the o~t;.. ;~i~l;on objective to ...;~ ..; , call del;~ delay. If a particular ori~;..P~ g switch queries an LNP
database on the basis of a particular N~ but the LNP-TAS analysis reveals that the queries have resulted in very few~-,~oing calls to ported di~ nll~n~s, the ori~ ;ng switch S an update mP~g~ ,t;-.g that the N~ should no longer serve as a trigger for 2S database q~ The standard t~ ...;~.-- ;ng switch Colle~ .ling to the N~ ~ulu... ~1;C~11y p~.rul~s LNP database queries as a default process. Th~cf~l~" the call delivery time for all oul~o~ calls from the ori~s;.. A;n8 switch dh~ d to the N~ is ...;~ d since the pre-delivery LNP datahase query is eliminated, and the call d~ time at the :j~dald te- ",;~l~ting switch is d~la~ only for those few calls which require an LNP d~~b~e query as a default 30 con~lition In accordance with one aspect of the present invention there is provided in a telecommunications network comprising a plurality of central office switches, a method for establishing an optimum d~t~b~ce query point in a call delivery process comprises the steps of: recording database-related query statistics specific to a central 5 office switch in the central office switch memory; receiving the ~l~t~base-related query statistics from each central office switch in the database traffic analysis system; the database traffic analysis system using the d~t~b~ce-related query statistics to determine an optimum database query point; and sending a switch control update message to at least one central office switch such that the optimum database query point is 10 established.
In accordance with another aspect of the present invention there is provided a local telecommunications network comprises: at least one origin~tine switch inclutline memory means for recording LNP d~t~b~e-related query statistics; at least one standard termin~ting switch including memory means for recording LNP d~t~bace-15 related query statistics; a local number portability-traffic analysis system (LNP-TAS) including an LNP database in communication with the origin~tine switch and the standard ter~nin~tine switch; means for receiving LNP database query statistics from the switches in the LNP-TAS in order to determine an optimum LNP d~t~h~.ce querypoint during call delivery in the telecommunications network; and means for sending 20 switch control updates from the LNP-TAS to the origin~tine switch.
s ~1 14~/q~
~- Brief De~cripffon of the n~
FIG. 1 is a simplified block ~liagpm of a se~-nf ~ of the public-~wilched tclf~o..~.n~ ;;ons n~lwo,L. (PSI~) in which the present invention may be practiced;
FIG. 2 is a flow ~ of the steps i~ ;,.~d by an origin~ting central office switch for 5 ~.rulllling LNP A~Ab~e queries in accol~ce with the method of the present invention;
FIG. 3 is a flow dia~a~l of the steps initi~tecl by a standard t~ "~ A~ g central office switch for ~. ru~ g LNP A~t~b~e queries in acco~ lce with the method of the present invention; and FIG. 4 is a flow ~liagr~m of the steps pe r~, ...~d by an LNP traffic analysis system for 10 det~ - ,..i.~;l~g an O~)ti~ LNP A~t ~h~e queFy point in accord~ce with the method of the present invention.
Ih2hil~1 Descril~tion FIG. 1 shows local sc~..~ 100 ofthe public-~witched l~lp~ph~ n~,lwul~ (PSTN) co~ g a plurality of central office ~wil~hes 102, 106 and 110 which provide local 15 tcl~ c~1;nn~ services. Orig;-.n~;ng central office switch 102 serves ~ U..~ line A and co...l.l;.~p~ ~r103and~ ol~ 105whichoperatetogetherto~ A;~globalcontrol fhnrtirnc~ such as switch ~ "il~ictrsltiQn and l.~A ~t~ Similarly, ~dd,~l t~ A~ g central office switch 106 in~h~des plocessor 107 and ~,~Ol~ 109 which also operate to ~cco--.l-l;ch global control fi-n-~.tionc, and serving central office switch 110 incl~dps ~lvcessor 111 and ~c~o,~ 113 which serve the same pu~3e.
For ~ses of example, assume a first local ~,I.ç~ ge carrier (LEC1) ...~;n~;"c ori~;n;.1;.~g switch 102 and ~hn~d t~.n;..~ g switch 106 while serving switch 110 is ~"~ t~--nr~l by a c~ access provider (CAP1). In this P nbo~imPnt skllld~d t~ .n;..,.l;ng switch 106 serves c ~ S~ es E, F and G but C~ lines B, C and D, which were 25 previously saved by switch 106, are now served by serving central office switch l lO. Although c~ t~..er~ lines B, C and D were l.~sÇ.,.l~ from a first central offlce switch (~d~d . ..-;n ~ g switch 106) to a second central office switch (serving switch 110), assume that the lol~l~ . lines Culltiu~l~ to retain di~eclo, ~ numbers which include office codes çhA. ar,l- . ;~l;c of standard tc ...in ~ g suntch 106. In other words, ~;"~IO",PI lines B, C and D are "ported"
30 dh~,tul~ nn.nk~ Th~,~fûl~ colllillg calls ~lireclc;d to c~-~t....- . lines B, C and D require 6 ~1 ;74-799 ~ special routing data for delivery of the call to the actual service switch (in this case, serving switch 110 of CAPl).
Also shown is Local Number Portability Traffic Analysis System (LNP-TAS) 120 including pr~cf ssor 122 _nd data memory 123 for ~1~ t~ . . . i nil~g an ol~tin~ l LNP ~At~AbAce query S point (as described in detail below) and Local Number Portability (LNP) ~-tAbAce 124.
Although LNP ~1 ~t~bA~ 124 is incol~o,dt~d within LNP-TAS 120, it may be ...A;..~ ed as a Sf ~A-~te ~ bAcf in Alt~ ,., e~nho~
Inte.~o~ P-~lion among the central office swilches is accomplished via established trunks, as is known in the art. In this emho~impnt ori~ g central office switch 102 co.. ~.;catf c 10 with serving switch 110 and tf - ~ Ar;i~g switch 106 via trunks 140 and 141, re;.~cliv~ly.
Tl .. ;-.-.1 ;.~g central office switch 106 co,.. I~-ic~ -s with serving switch 110 via trunk 142. All central office ~wi~hes (102, 106 and 110) also 1~ ;Q trunks to tandem ~wilchfls (not showvn) for ~ 8 calls outside local s~l.f~1 100, e.g. an inter-area code call, or if a direct trunk to another central office switch is not available, as is known in the art.
LM-TAS 120 (incl~ ng LM ~ e 124) is in co-------~ ~iC~1;on with each central office switch over d~P~ t~Pd data links. General data links 130 and 131 act as co~luib for ges ~lat ng to LM datubase ~elahd query st-ti~tics and switch control update ll.f~ges ~h.~n LM-TAS 120 and orig;~ g switch 102 and ~d~ tx-lll;~ g switch 106, le ~,ti~,ely. Data link 132 enables coll~ ;c~tion relating to routing data ~l~ LM
database 124 and ori~ g switch 102 while data link 133 serves the same purpose ~l~
LM ~I t~,b~ 124 and ~minati~g switch 106. Although LM ~1 ~t-~h-~ 124 coll.l--~ ;cates with the centr. l office ~wit~l~s via separate data links (i.e. 132 and 133) in the embo~imf~nt shown, it may share gen~l data linlcs 130 and 131 to accolnplish the same flm~tif~n LM-TAS 120 is a data g~ hf ~ ;.~g and d~ t~ n center for establishing the opt;...l~ n 25 point (i.e. ei~her the origina~ng switch or the standard te ..li~ g switch) in the call delivery process for ~ i~ LM database 124. Specifically, LM ~l~at h-a~-related query st-*ctics are r~ce;~od by LM-TAS 120 at plcdet~ d intervals via de~igra~d switch data links and stored in data ~lllo.~ 123. F'~ssor 122 uses the st-ati~tics stored in lll~,~llUl~ 123 to ~f~te- I.~ e the ol)ti~ulll LM f~-.t"h~ query point in acco~ ce with ple~ f ~1 oyt;~ 1;on criteria An optional rAnhAl~ed LM-TAS 120 may also 1.. ~ a conl-e~l;on to trunk control system 160 21~i9~
via data link 161 to control t_e establiehmPnt/removal of trunks b~ - cll central office switches within local seg. . .~ 100 in ~ onse to changes in trigger NPA-N~ digits, as described below.
FIG. 2 is a flow ~iiagr~m of the steps as pc.r~ ,llled by origin~tin~ switch 102 when S deli~l~,ing a call to a ported dhcctul~ number and interacting with LNP-TAS 120 in accordance with the present invention. For purposes of example, assume that a caller at customer line A of oriy;.. ~ g central office switch 102 places an intra-area code call by dialing direcloly number "555-3616" which icl~ntifies a called party who is served by cl~etom~r line B of serving central office switch 110. In this example, the oriei~ g switch is the switch which serves the caller's 10 cu~ c. line. However, for ~ oses of this ~icclle-e;on~ an origin~i~ switch is the first switch in the LNP-TAS service area to receive the dialed dil~ c lol~ number (e.g. the origin~ting switch may be a tandem switch in the LNP-TAS service area which leCe;~S the dialed dil~tol~
nwll~r). The called party has elected a new local service provider and has l.,- .~r~ d her o...- Iine and dire~tol" number ("555-3616" ) to CAPl serving switch 110 from LEC2 15 ~ te-...;~ gcentralofficeswitch106. Theprocessbeginsinstep200whenori~in~ting central office switch 102 l~c~;ves the dialed di~e~ilol~ number "555-3616" from the caller via ~-~.1.J...er line A and prepcnds the ~PA digits "708" COll-. ~IU1i~8 to the area code ~se-oci~ted with the originating switch (and hence, the caller), as is known in the art. If the NPA digits are not ple~ ~ the N~ digits serve as the basis for LNP ~ -q~G triggers~ as described below.
In d~ie-ion step 202, o. ;&;.. -,t;i~g switch 102 (which has been previously pro~. n~.e~l with LNP database trigger digits "708-555") ~,f,lll~s digit analysis to d. ~ "~inr whether the "NPA-NXX' digits of the dialed d~c~ nwnber are digits which ~l~ci~i~te an LNP database query. It is noted tbat database queries can also be triggered by more than six dilccluly nwnber digits (e.g. trigger digits could be NPA-NXX-X, NPA-NXX-XX.. etc.) If the Ou[CGme of 25 ~lee-c;on st~p 202 is a "NO" ~Gc-~-;on, (that is, an LNP ~1 ,t.~ ~ query is not triggered by the NPA-N~ of the dialed dil~:t~l~ nwnber) the process continl)es to step 203 in which the call is delivered without r~h;c~ing routing data and then to step 210 in which a non-ported dL~ectoly nwnber entry is recorded. Delivering the call without retrieving routing data in the origin~ting switch does not imply that routing data is never 1~ ~;e~ed. Indeed, retrieval of routing data may 30 be the le",orsibility ofthe ~ d t~ t;.~g switch, as described below. If, however, as in 8 21 7$19~
the eYe "~ case, the oul~iG,-le of decision step 202 is a "YES" decision, an LNP database quer,v is triggered and the process CG~ J~S to step 204 in which origin~ting switch 102 hP5 a query over data link 132 to LNP ~ b~e 124.
In ~eci~ion step 205, it is ~ t~ . . .i..~d whether routing data is found in LNP tl~t~bAce 124 for the di~ number "708-555-3616". If the outcome of decision step 205 is a "NO"decision, the process returns to step 203 and then co,llinues to step 210 in which a non-ported dil~tul ~ m~ ~. entry is recorded. If the oulcoll.c of dççi~io~ step 205 is a "YES" decision, the process con~;..-~es to step 206 in which ori&;~ g switch 102 ICCeiveS the routing data from LNP ~ kA~e 124 via data link 132. The process cc..~ ,s to step 208 in which ori~in~ting 10 switch 102 çYtçrl~i~ the call from the caller at c ~ilol~.- line A to a called party at ~ lul..~ . line B
of serving central office switch 110 via trunk 140 lltili~ing routing data .~ce;~,d from LM
k-~ 124.
In step 210, originating switch 102 records in switch u.~ ol~ 105 LM ~ b~ relat~ed query s~ a;cs such as v~h~lh~. the o~l~goil~g call is dile~,t~ to a ported or non-ported dhe~
15 nllmb~, the time c~ 3~ for the LM database query, and the NXX of the actual switch (i.e.
the serving switch) to which the oul~---g call is del;~ ,d. SU~ .Jf ~ at ~ te~
intervals (such as hourly ~t ,l~alS), originating switch 102 sends the compilAtion of all LM
~1A~ A~ related query s~-~t;~;cs to LM-TAS 120 via data linlc 130 in step 212. In step 214, ori,di-~ g switch 102 IC~;~3 a switch control update ~f'SS~f~ from LM-TAS 120, as 20 des~ibed below.
FIG. 3 is a flow diagram ofthe steps ~ ru....~ by standard tf ~--;l~ g switch 106 for delivery of an i-~ S...;~g call which call ~ u~le.~ an LM database query. For clarity, the of a caller served by customa line A of ori~;..s~ g switch 102 who places a call to a called par~ served by customer line B of serving central office switch 110 is continlled In thi~ call flow scenario, a default LM database query process is employed. Theprocess begins in step 302 in which standard t~-...;.-PA;-~g switch 106 l~e;~,s an i~ccs~ g call from ori~;;..-~1;.~g switch 102 over trunk 141, wl,~ ,~ the called party is id~ntififYl by di~f .~l~s,~r number "708-555-3616".
In der-i~iQn step 304, standard t~ 8 switch 106 pf ru- ...~ digit analysis of the 30 dialed dil~cto~ lullll;C- to ~ r if the number is dilfJ~ d to a valid ~ u,l, ,. line on itS
9 2~ 7479q service base. If the ouleo,lle of deçi~ion step 304 is a "YES" decision, the process continues to step 305 in which the call is deli~e.cd to the c~YIo~..e~ line coll~;,pol ding to the dialed directory number. If, hu~ ,., the oulcolllc of decision step 304 is a "NO" ~eci~ion, as in the exemplary case, the process co.~ c5 to step 308 in which t~ ;ng switch 106 l~lmr~P,c a query to LNP
5 .Is~t~b~e 124.
In decision step 310 a ~1~t~ ion is made as to whether routing data was found inLNP rl~t~b~e 124. If the o~llcolllc of decision step 310 is a "NO" decision (that is, no routing data is received), the process col.l;..~es to step 311 in which the call is e~ctPn~le~l to an anno....~ circuit and then pl~ceeds to step 316 in which a non-ported dir~e,~l~ number 10 entry is l~col~d. If the oulcollle of dcc;siol1 step 310 is a "YES" dççie;on (that is, routing data was found), the process c0.~ ve5 to step 312 in which ~d~ t~ switch 106 ~cceivc;s the routing data in the switch. In step 314, te ...;l~ g central office switch 106 extends the call to the proper serving switch (serving switch 110) using the routing data .~,~;cvcd from LNP
database 124.
In step 316, switch 100 records in switch n~.llol~ 109 LNP ~ljJt ~ related query;C5 incl~lAing ~,. helL~. or not the i~cGllling call is dir~cled to a ported di~e~tol ~ number, the time ~ ed to p~r~.llll the LNP ~ h~l~e query and the NXX ofthe actual serving switch of the ;~ 4~ g call. Sul,s~u~ , the LNP-TAS ,~t~.~ti~i process continues to step 318 in which te-.-~ g switch 106 sends LNP~t~b~e-related query st~ti~tics to LNP-TAS120 at a plO1~,t~ eA intenal.
FIG. 4 shows a flow ~ b,. .. of the process steps ~ rc.. ed by LNP-TAS120in int~lligently ~,t~ g an ol~1;--l-LNP ~fl~ ~ query point dunng the call delivery process.
It is !'~ A, in this example, that LNP-TAS120 has been previously initi~li7~fl with A~ ~ o~:~";~-~t;~n cr~ a to ~ r call del;~ time.
The process begns in step 400 in which LNP-TAS120 I~C~ S LNP~at~b~-related query statistics from each central office switch via designated switch data links. In the .,A~ case, LNP-TAS 120 receives st~ti~tics from on~-- ,1;,~g switch 102 and ~dald te....;-. ~ 8 switch 106 via switch data links 130 and 131, lé~ el~. The process continl~es to step 402 in which LNP-TAS 120 ~ Ps the o~ LNP~a~ que~ point in 30 accol~ce with the pl~d~ ~.-Pd o~ ;on criteria using the LNP~lAt~A~e-related query lo 2~ 74~99 ~ ~I"t;~t;cs received from the central office swilches. For ~Ai&~le, to clete ...il~e an LNP d~t~b~e query point which ~ s call delivery delay ~h~ n ori~ g switch 102 and standard ;ng switch 106 ~Il~.ei~ the NPA-NXX of ~d~d ~e....;n~ g switch 106 is a LNP
tslh:-~ query trigger for origin~ting switch 102, LNP-TAS 120 co~ s the volurne of ported 5 di~ ol~ number calls with respect to all oulgoing calls from oriYin~ting switch 102.
In step 404, LNP-TAS 120 derives a switch control update ...~ ge for the apl~lo~)l;ate central office switch(es) in accor~ce with the ~ ".;~ ~1;on made in the previous step. In the eY~lnrl~y case, assume that the LNP ~ b~ related query st~ti~tics received from ori~in~ting switch 102 reveal that a relatively small 1l~ll~. of LM ~ h~ queries triggered by the NPA-10 NXX digits ("708-555") of the standard 1 ....i.. 1;"g switch 106 actually resulted in routing calls to ported di~ n---..l~;~. Accor~ gl~ o~ g SWitGh 102 l~C~ . aII update message which deactivates NPA-NXX digits "708-555" as LNP database query trigger digits such that ~l~d~.l t~ . t;n8 switch 106 b~o.nes l~ ~ible for y f~,....;l~g all LM ~i~t~ba~ queries for ported t~n.~ on the switch (see FIG. 3). In gl~ t;~" ernk)~ , LM-TAS 120 may15 use st~,ti~tics relating to the NXX of the saving switch to which the majority of ported dh~ o ..kc- ~ are dil~t~d to formulate new or ~s~litions1 MA-NXX trigger digits to be stored in an ori~ g switch in accol~ce with the volume of ported di.~tol~ nllml~s to a particular NXX. A LM-TAS 120 switch control update message which replaces or supplements the g MA-NXX trigga digits in an ori~ g switch, ~ ,S Coor ~ ;on -20 ~l~.~n LM-TAS and trunk control system 160 such that o~llg~ g calls to the new trigger MA-N~ may be deli~red effif~i~ntly.
The process ends with step 406 in which LM-TAS 120 updates the a~ ;ate central office s..it~Lei by sending the switch control update message daived in the previous step to the ~wil~l~s over the designated switch links. Although the exemplary embodiment describes the 25 present inv~tion as int~ion~ n an LM-TAS and a plurality of central office swilches, the LM-TAS may interact with any other plurality or combindtion of swil,l~s, including tandem swilches.
In this ",nnn " LM ~ m~ related query s~ti~tics as received from each central office switch may be a~ t;r~lly m~ ,cd and evaluated to intellig~ntly ~et~ ...il-r the "o~thll~lll't LM ~1A~bn~e query point in a local teleco.. is~tionc ll~lw~L. so that the ~wilches can be Il ~ 1 7479~
1y updated to reflect the true state of service provider local number portability in the ~twol~. It is to be ~ de~ )od that the above described embodiment is for illustrative purposes only and that IlU~,~US other ~~ g~ may be devised by one skilled in the art without dep~li~g from the scope of the invention.
METHOD FOR DETERMINING AN OPTIMUM POINT FOR DATABASE QUERIES
DURING CALL DELIVERY IN A TELECOMMUNICATIONS NETWORK
5 Technical Field This invention relates to a method and system for A.~te....;~ g an ol)thllulll point during call delivery for ~.Çolllling A~t~b,~e queries le.luiled for routing calls to ported directory in a local telecoll~.ulications ~ wu~
The public-~wilched t~l~ph--l-e nelwc,l~ in~ll)Aes: a large number of central office ~wi~L~s serving local ~ slu~, lines and trunks; a smaller nulll~l of tandem ~wil~hes for providing u~ P~ n~ n central office swilcllej, a co.. ~ c ~,lwvlL cQmrri~ing a large n~b~. of analog and digital coll~lul~ic~tion paths intc~Q~ e~,t;.~g the centTal offlce ~wi~l~s and tandem swi~l~e" and optional ~ s, such as local number portability (LNP) 5 A~ hs~ 5, for storing routing data wd by swi~L~s for call d~ e. ~ .
Calls ~t~ n t~l~h- ne Cu~)lll,.a in the United States are established on the basis of a n~tion~l di,~Lol~ n.,l,l~ plan which ,~u"~s a caller to dial seven or ten digits to identify a called party. A 1 0-digit dialed dh~,~to, ~ number Co~ " ;~,,s a thre~e-digit area code (generally denoted by the letters "NPA") which defines a s~ ;rc geoL; r~hic region and p,~edes a three 20 digit office code (d~ 3d by the letters '~') which id .1;rFs a particular central office switch that serves the called party. The office code is followed by a four digit ~iu~lulll~,. line id~ ;r.~ Jt~ by the letters "X~X'). A seven-digit dialed di~ecto,,~ number is indicative of an intra-area code call and simply co.. .l..; ~,s the three-digit offlce code ('~') followed by a four~igit customer line id~ -~1;fi'-,~ ("X~'). Although a calla may dial only seven digits 25 (NXX-XXX~ when placing a call, the calla's area code (NPA) is often p,~ ed to the dialed seven digits by a digit l~C~i;Ving switch (i.e. the originating switch), as is known in the art.
fo.~" evay o~ltgoing call can be treated as a 10 digit di,~ number even if the caller only actually dials seven digits.
There are catain S;IV~1;QI~C in which the operations of an ~ 8 ~wilching ~,lwo,k can 30 benefit from the int~d~lçtior of additional centTal office awi~hes which share one or more ~1 74799 office codes with the eYiCting IklWOIk. Indeed, during the next several years, it is expected that the Ill~n~ held by local eY~ k~nge carriers (LECs) in providing local telephnn~ service will be s~ y altered and that co...~ ;ve access providers (CAPs) will offer local telephone service to ~ tO~ a. When a awilchillg n~lwo~ n~ d by a CAP is added to a particular geographic area ( i.e. a local access teleco.. l~-lic~tions area (LATA)), it is generally desirable that any ~r~. of c~ u....,. Iines ~e~e."l the eYi~ting local e~ nge carrier and co~ ilive access providers occur wi~oul c~ s to ~ e~ dil~,~,lo. ~ numbers.
Dile~,t~ numbers that include office code digits ck~ t~,~ ;C tiC of a first central office switch but which identify .;~ lu.. .Iines actually served by a second central office switch are knownas"ported"dL~,.,l~" ......... ~ ~ Properdeli~ of callsto~ lu.~ withported ~lL~ r mlrnhers le~uil~s l~h;~ of routing data by a central office switch from a local n.~l.,~, portability (LNP) database. Current ~e~luile,lle~'ta for a pl~,f~ d imple . . nt~1 ;on of the LNP ~ h.q~ system specify that retrieval of routing data may be ~ fv....ed either by the central offlce switch in the local area which first l~ S the dialed digits of the ported dL~
15 number (i.e. the "ori~;n~ ' switch) or the central office switch which would normally sene the dialed NXX (i.e. the ' at;~ni ~ g" switch).
One solution for establishin~ the point in a call delivery process at which the LNP
database is queried lC~Uile,S ori~ swil~ih~s to launch LNP~ bq~e queries each time t~ ~1 (i.e. "trigger") NPA-NXX digits are ~ .~. More particularly, this solution20 l~ ,s o ig;" ~1;"g swilch~s to make LNP database queries if the called NPA-NXX digits are ntifi~ as trigger digits. Under current practice, the NPA-NXX digits are marked and stored in the orig~ g switch ~ GI~ as triggers as soon as a single di~e.,tul~ number is ported from the id. ..1;1~ triggcr NXX. Retrieval of routing data by the orig;. - 1;.~g switch is the most time-~IT;C;.~ .~t ma~ for del;~,~g an o~lg~ g call to a ported d~ul~ nu.llber since the serving 25 switch (i.e. thc central office s vitch that actually serves the ported di~ number) is identifi~ before call delivery is attempted. However, ~lu~ ing an LNP~1A~hq~ for routing data is least el~ 1 for non-ported numbers which need no ~d~iiti~n~ql routing infolll~lion.
Hence, if only a few ~ u.. ~ leph~ne lines in a trigger '~' (i.e. s~dd~ tf - ~ g central office switch) have been ported, I~ g LNp~l~t~h~q~e queries at the origjnqting 21 74~q9 switch may cause n~lPss LNP ~ ,.bq~ queries as the vast majority of queries result in a ~'no routing data found" ~on3e.
Another solution for establishing the point in the call deli~,e.~ process at which an LNP
~Iqt~hq~ is queried is a default query process. In accor~ ce with the default query approach, S LNP ~t~ha~e queries are p~- r.. ~d by the ~ldald t~ .. in~ g switch (that is, the switch which normally serves the dialed N~-X~X that has now been ported). Particularly, a standard t~ g switch which lecf ivcs an ;I-~o...i~g call initially ~t~lll~ to deliver the call norm~lly (i.e. wi~loul querying an LNP ~ t ~bq~). If the call cannot be delive.~ norrnally, an LNP ~t~h~e query is l.-~.n~l-e~ RetIieval of routing data from an LNP ~ h.q~e by the 10 standard tf ~ ~ g switch ...in;-n;~cs the nurnber of LNP datab~ queries since the majority of calls dcli~ d to the t~ ...;.. ~t;l~g switch will be dcli~ d n~ rn~lly. However, for every ported n-lm~, a re-routing from a ~l~d~.l t~-...in~ R switch is l~UilC;I. Hence, if a particular ~ ~ad&.l ~ .;n~ g switch has many ported dir~;tu.~ nllmh~, a default LNP ~l~t~b~e query process iWl~S the overall call dcli~,.y time of ported nllmh~s since the call has been 15 initially routed to a central office switch that no longer serves the dialed dh nurnber.
Although the a l~t;~ges and dis~l~lt2 ges of ~lu~ . ~ing an LNP ~ UbA u at the orig;--~ g or s~d~d ~ g switch are known, plup~sed impl~ .."~t~l;on.~ of LNP
'hA'~ s~s~ llS do not address the need to intPlligently ~1~ t~ F an ~IJ1;-------- LNP ~l~t~b~e query point ( i.e. either the originating switch or the standard t~minating switch) in the call 20 dcli~ process and to automatically ie ~o~d to the dynamic nature of ported dile~,lol.~ nurnber traffic. Indeed, the current practice of storing trigger NPA-N~ digits in central office switches upon h~r~. of a single d;l~t~ nulll~. out of the trigger N~ e1;...i'~t~s the ability of the ~,lwull~ to rcflect to actuai ported dir~;t~l ~ nu~l traffic.
rh~ef~, there is a need in the art for inte11ig~nt1y ~ t - ~--;~ g the o~ um point for 25 ~lu~ ing an LNP database to ûbtain routing data lequ,l~ for call del;~ and ~ I;c~l1y 8 central office swil~;l~s in _CCûl'~ Ce with the ~ t~ ...;l. ~1;o--This need is addressed and a tec-hnic~1 advance is ach;e.od in the art by the method and system ofthe present invention which aulo...~tic~l1y gathers LNP ~,~t:~b-4~e related query 21 74~59 sPtic ics to ~ an o~)till~Ulll LNP~l~t~h~ce query point in a call delivery process and updates central office swilel~es in accord~ce with the ~ ;on In one plY fe~l~,d ~bodi~ t of the method of the present invention, a local number portability traffic analysis system (LNP-TAS)is established such that it receives LNp~l~t~bqce 5 related query stqtictics from each centTal office switch in its service area. The LNP-TAS uses the st~tictic~l info....~;on to int~llig~ontly det~ the o~tilllUlll LNP dqt~b~ce query point. In op~tiQn each LNP-l ~Ahq~e query p. .Çu~lled by a central office switch is recorded. The record includes v~h~ . or not the dialed dil~ lol ~ is a ported dilcc~ol~/ number, the time ed to pl . ru- - - - the query and the serving office of ported dh~ ~tul ~ nllm~ s The 10 comriled st~tictics are ~ .;l~l by each switch, at pl~dct~ ...;..ed intervals, to the LNP-TAS
over designated data links. The LNP-TAS analy~s the st~tictics using predçfined o~ l ;on criteria (or objectives) to d~ h .. ~ e the plefe.l~d point in the call deli~ process (i.e. ei~er the orig;~ g switch or a particular standard t~ ...;~.z~ g switch) for l~ g LNP ~ h~e queries in accol~ce with the pl~d~ Pd criteria F.Yr .1rs of o~lt;l~ t;on criteria include 15 ...;~ 1;on of call del;~ r delay, ~ i...;7~l;on of .1~1;,h~ query cost for a particular local service provider, Gpt;...;- A routing based on time of day/week or class of service, or m~n~g~nPnt of ll. lwul~ peal~ hour LNP d~b~ queries. If a change in the LM ~l~t~h~e query point is necessary, the LNP-TAS sends an update e~-~ge directly to the a~pl~opl;~te centTal office switch(es) to ~.. ~te the change.
For ~e r'e assume that the LNP-TAS has been initis31i7e~ with the o~t;.. ;~i~l;on objective to ...;~ ..; , call del;~ delay. If a particular ori~;..P~ g switch queries an LNP
database on the basis of a particular N~ but the LNP-TAS analysis reveals that the queries have resulted in very few~-,~oing calls to ported di~ nll~n~s, the ori~ ;ng switch S an update mP~g~ ,t;-.g that the N~ should no longer serve as a trigger for 2S database q~ The standard t~ ...;~.-- ;ng switch Colle~ .ling to the N~ ~ulu... ~1;C~11y p~.rul~s LNP database queries as a default process. Th~cf~l~" the call delivery time for all oul~o~ calls from the ori~s;.. A;n8 switch dh~ d to the N~ is ...;~ d since the pre-delivery LNP datahase query is eliminated, and the call d~ time at the :j~dald te- ",;~l~ting switch is d~la~ only for those few calls which require an LNP d~~b~e query as a default 30 con~lition In accordance with one aspect of the present invention there is provided in a telecommunications network comprising a plurality of central office switches, a method for establishing an optimum d~t~b~ce query point in a call delivery process comprises the steps of: recording database-related query statistics specific to a central 5 office switch in the central office switch memory; receiving the ~l~t~base-related query statistics from each central office switch in the database traffic analysis system; the database traffic analysis system using the d~t~b~ce-related query statistics to determine an optimum database query point; and sending a switch control update message to at least one central office switch such that the optimum database query point is 10 established.
In accordance with another aspect of the present invention there is provided a local telecommunications network comprises: at least one origin~tine switch inclutline memory means for recording LNP d~t~b~e-related query statistics; at least one standard termin~ting switch including memory means for recording LNP d~t~bace-15 related query statistics; a local number portability-traffic analysis system (LNP-TAS) including an LNP database in communication with the origin~tine switch and the standard ter~nin~tine switch; means for receiving LNP database query statistics from the switches in the LNP-TAS in order to determine an optimum LNP d~t~h~.ce querypoint during call delivery in the telecommunications network; and means for sending 20 switch control updates from the LNP-TAS to the origin~tine switch.
s ~1 14~/q~
~- Brief De~cripffon of the n~
FIG. 1 is a simplified block ~liagpm of a se~-nf ~ of the public-~wilched tclf~o..~.n~ ;;ons n~lwo,L. (PSI~) in which the present invention may be practiced;
FIG. 2 is a flow ~ of the steps i~ ;,.~d by an origin~ting central office switch for 5 ~.rulllling LNP A~Ab~e queries in accol~ce with the method of the present invention;
FIG. 3 is a flow dia~a~l of the steps initi~tecl by a standard t~ "~ A~ g central office switch for ~. ru~ g LNP A~t~b~e queries in acco~ lce with the method of the present invention; and FIG. 4 is a flow ~liagr~m of the steps pe r~, ...~d by an LNP traffic analysis system for 10 det~ - ,..i.~;l~g an O~)ti~ LNP A~t ~h~e queFy point in accord~ce with the method of the present invention.
Ih2hil~1 Descril~tion FIG. 1 shows local sc~..~ 100 ofthe public-~witched l~lp~ph~ n~,lwul~ (PSTN) co~ g a plurality of central office ~wil~hes 102, 106 and 110 which provide local 15 tcl~ c~1;nn~ services. Orig;-.n~;ng central office switch 102 serves ~ U..~ line A and co...l.l;.~p~ ~r103and~ ol~ 105whichoperatetogetherto~ A;~globalcontrol fhnrtirnc~ such as switch ~ "il~ictrsltiQn and l.~A ~t~ Similarly, ~dd,~l t~ A~ g central office switch 106 in~h~des plocessor 107 and ~,~Ol~ 109 which also operate to ~cco--.l-l;ch global control fi-n-~.tionc, and serving central office switch 110 incl~dps ~lvcessor 111 and ~c~o,~ 113 which serve the same pu~3e.
For ~ses of example, assume a first local ~,I.ç~ ge carrier (LEC1) ...~;n~;"c ori~;n;.1;.~g switch 102 and ~hn~d t~.n;..~ g switch 106 while serving switch 110 is ~"~ t~--nr~l by a c~ access provider (CAP1). In this P nbo~imPnt skllld~d t~ .n;..,.l;ng switch 106 serves c ~ S~ es E, F and G but C~ lines B, C and D, which were 25 previously saved by switch 106, are now served by serving central office switch l lO. Although c~ t~..er~ lines B, C and D were l.~sÇ.,.l~ from a first central offlce switch (~d~d . ..-;n ~ g switch 106) to a second central office switch (serving switch 110), assume that the lol~l~ . lines Culltiu~l~ to retain di~eclo, ~ numbers which include office codes çhA. ar,l- . ;~l;c of standard tc ...in ~ g suntch 106. In other words, ~;"~IO",PI lines B, C and D are "ported"
30 dh~,tul~ nn.nk~ Th~,~fûl~ colllillg calls ~lireclc;d to c~-~t....- . lines B, C and D require 6 ~1 ;74-799 ~ special routing data for delivery of the call to the actual service switch (in this case, serving switch 110 of CAPl).
Also shown is Local Number Portability Traffic Analysis System (LNP-TAS) 120 including pr~cf ssor 122 _nd data memory 123 for ~1~ t~ . . . i nil~g an ol~tin~ l LNP ~At~AbAce query S point (as described in detail below) and Local Number Portability (LNP) ~-tAbAce 124.
Although LNP ~1 ~t~bA~ 124 is incol~o,dt~d within LNP-TAS 120, it may be ...A;..~ ed as a Sf ~A-~te ~ bAcf in Alt~ ,., e~nho~
Inte.~o~ P-~lion among the central office swilches is accomplished via established trunks, as is known in the art. In this emho~impnt ori~ g central office switch 102 co.. ~.;catf c 10 with serving switch 110 and tf - ~ Ar;i~g switch 106 via trunks 140 and 141, re;.~cliv~ly.
Tl .. ;-.-.1 ;.~g central office switch 106 co,.. I~-ic~ -s with serving switch 110 via trunk 142. All central office ~wi~hes (102, 106 and 110) also 1~ ;Q trunks to tandem ~wilchfls (not showvn) for ~ 8 calls outside local s~l.f~1 100, e.g. an inter-area code call, or if a direct trunk to another central office switch is not available, as is known in the art.
LM-TAS 120 (incl~ ng LM ~ e 124) is in co-------~ ~iC~1;on with each central office switch over d~P~ t~Pd data links. General data links 130 and 131 act as co~luib for ges ~lat ng to LM datubase ~elahd query st-ti~tics and switch control update ll.f~ges ~h.~n LM-TAS 120 and orig;~ g switch 102 and ~d~ tx-lll;~ g switch 106, le ~,ti~,ely. Data link 132 enables coll~ ;c~tion relating to routing data ~l~ LM
database 124 and ori~ g switch 102 while data link 133 serves the same purpose ~l~
LM ~I t~,b~ 124 and ~minati~g switch 106. Although LM ~1 ~t-~h-~ 124 coll.l--~ ;cates with the centr. l office ~wit~l~s via separate data links (i.e. 132 and 133) in the embo~imf~nt shown, it may share gen~l data linlcs 130 and 131 to accolnplish the same flm~tif~n LM-TAS 120 is a data g~ hf ~ ;.~g and d~ t~ n center for establishing the opt;...l~ n 25 point (i.e. ei~her the origina~ng switch or the standard te ..li~ g switch) in the call delivery process for ~ i~ LM database 124. Specifically, LM ~l~at h-a~-related query st-*ctics are r~ce;~od by LM-TAS 120 at plcdet~ d intervals via de~igra~d switch data links and stored in data ~lllo.~ 123. F'~ssor 122 uses the st-ati~tics stored in lll~,~llUl~ 123 to ~f~te- I.~ e the ol)ti~ulll LM f~-.t"h~ query point in acco~ ce with ple~ f ~1 oyt;~ 1;on criteria An optional rAnhAl~ed LM-TAS 120 may also 1.. ~ a conl-e~l;on to trunk control system 160 21~i9~
via data link 161 to control t_e establiehmPnt/removal of trunks b~ - cll central office switches within local seg. . .~ 100 in ~ onse to changes in trigger NPA-N~ digits, as described below.
FIG. 2 is a flow ~iiagr~m of the steps as pc.r~ ,llled by origin~tin~ switch 102 when S deli~l~,ing a call to a ported dhcctul~ number and interacting with LNP-TAS 120 in accordance with the present invention. For purposes of example, assume that a caller at customer line A of oriy;.. ~ g central office switch 102 places an intra-area code call by dialing direcloly number "555-3616" which icl~ntifies a called party who is served by cl~etom~r line B of serving central office switch 110. In this example, the oriei~ g switch is the switch which serves the caller's 10 cu~ c. line. However, for ~ oses of this ~icclle-e;on~ an origin~i~ switch is the first switch in the LNP-TAS service area to receive the dialed dil~ c lol~ number (e.g. the origin~ting switch may be a tandem switch in the LNP-TAS service area which leCe;~S the dialed dil~tol~
nwll~r). The called party has elected a new local service provider and has l.,- .~r~ d her o...- Iine and dire~tol" number ("555-3616" ) to CAPl serving switch 110 from LEC2 15 ~ te-...;~ gcentralofficeswitch106. Theprocessbeginsinstep200whenori~in~ting central office switch 102 l~c~;ves the dialed di~e~ilol~ number "555-3616" from the caller via ~-~.1.J...er line A and prepcnds the ~PA digits "708" COll-. ~IU1i~8 to the area code ~se-oci~ted with the originating switch (and hence, the caller), as is known in the art. If the NPA digits are not ple~ ~ the N~ digits serve as the basis for LNP ~ -q~G triggers~ as described below.
In d~ie-ion step 202, o. ;&;.. -,t;i~g switch 102 (which has been previously pro~. n~.e~l with LNP database trigger digits "708-555") ~,f,lll~s digit analysis to d. ~ "~inr whether the "NPA-NXX' digits of the dialed d~c~ nwnber are digits which ~l~ci~i~te an LNP database query. It is noted tbat database queries can also be triggered by more than six dilccluly nwnber digits (e.g. trigger digits could be NPA-NXX-X, NPA-NXX-XX.. etc.) If the Ou[CGme of 25 ~lee-c;on st~p 202 is a "NO" ~Gc-~-;on, (that is, an LNP ~1 ,t.~ ~ query is not triggered by the NPA-N~ of the dialed dil~:t~l~ nwnber) the process continl)es to step 203 in which the call is delivered without r~h;c~ing routing data and then to step 210 in which a non-ported dL~ectoly nwnber entry is recorded. Delivering the call without retrieving routing data in the origin~ting switch does not imply that routing data is never 1~ ~;e~ed. Indeed, retrieval of routing data may 30 be the le",orsibility ofthe ~ d t~ t;.~g switch, as described below. If, however, as in 8 21 7$19~
the eYe "~ case, the oul~iG,-le of decision step 202 is a "YES" decision, an LNP database quer,v is triggered and the process CG~ J~S to step 204 in which origin~ting switch 102 hP5 a query over data link 132 to LNP ~ b~e 124.
In ~eci~ion step 205, it is ~ t~ . . .i..~d whether routing data is found in LNP tl~t~bAce 124 for the di~ number "708-555-3616". If the outcome of decision step 205 is a "NO"decision, the process returns to step 203 and then co,llinues to step 210 in which a non-ported dil~tul ~ m~ ~. entry is recorded. If the oulcoll.c of dççi~io~ step 205 is a "YES" decision, the process con~;..-~es to step 206 in which ori&;~ g switch 102 ICCeiveS the routing data from LNP ~ kA~e 124 via data link 132. The process cc..~ ,s to step 208 in which ori~in~ting 10 switch 102 çYtçrl~i~ the call from the caller at c ~ilol~.- line A to a called party at ~ lul..~ . line B
of serving central office switch 110 via trunk 140 lltili~ing routing data .~ce;~,d from LM
k-~ 124.
In step 210, originating switch 102 records in switch u.~ ol~ 105 LM ~ b~ relat~ed query s~ a;cs such as v~h~lh~. the o~l~goil~g call is dile~,t~ to a ported or non-ported dhe~
15 nllmb~, the time c~ 3~ for the LM database query, and the NXX of the actual switch (i.e.
the serving switch) to which the oul~---g call is del;~ ,d. SU~ .Jf ~ at ~ te~
intervals (such as hourly ~t ,l~alS), originating switch 102 sends the compilAtion of all LM
~1A~ A~ related query s~-~t;~;cs to LM-TAS 120 via data linlc 130 in step 212. In step 214, ori,di-~ g switch 102 IC~;~3 a switch control update ~f'SS~f~ from LM-TAS 120, as 20 des~ibed below.
FIG. 3 is a flow diagram ofthe steps ~ ru....~ by standard tf ~--;l~ g switch 106 for delivery of an i-~ S...;~g call which call ~ u~le.~ an LM database query. For clarity, the of a caller served by customa line A of ori~;..s~ g switch 102 who places a call to a called par~ served by customer line B of serving central office switch 110 is continlled In thi~ call flow scenario, a default LM database query process is employed. Theprocess begins in step 302 in which standard t~-...;.-PA;-~g switch 106 l~e;~,s an i~ccs~ g call from ori~;;..-~1;.~g switch 102 over trunk 141, wl,~ ,~ the called party is id~ntififYl by di~f .~l~s,~r number "708-555-3616".
In der-i~iQn step 304, standard t~ 8 switch 106 pf ru- ...~ digit analysis of the 30 dialed dil~cto~ lullll;C- to ~ r if the number is dilfJ~ d to a valid ~ u,l, ,. line on itS
9 2~ 7479q service base. If the ouleo,lle of deçi~ion step 304 is a "YES" decision, the process continues to step 305 in which the call is deli~e.cd to the c~YIo~..e~ line coll~;,pol ding to the dialed directory number. If, hu~ ,., the oulcolllc of decision step 304 is a "NO" ~eci~ion, as in the exemplary case, the process co.~ c5 to step 308 in which t~ ;ng switch 106 l~lmr~P,c a query to LNP
5 .Is~t~b~e 124.
In decision step 310 a ~1~t~ ion is made as to whether routing data was found inLNP rl~t~b~e 124. If the o~llcolllc of decision step 310 is a "NO" decision (that is, no routing data is received), the process col.l;..~es to step 311 in which the call is e~ctPn~le~l to an anno....~ circuit and then pl~ceeds to step 316 in which a non-ported dir~e,~l~ number 10 entry is l~col~d. If the oulcollle of dcc;siol1 step 310 is a "YES" dççie;on (that is, routing data was found), the process c0.~ ve5 to step 312 in which ~d~ t~ switch 106 ~cceivc;s the routing data in the switch. In step 314, te ...;l~ g central office switch 106 extends the call to the proper serving switch (serving switch 110) using the routing data .~,~;cvcd from LNP
database 124.
In step 316, switch 100 records in switch n~.llol~ 109 LNP ~ljJt ~ related query;C5 incl~lAing ~,. helL~. or not the i~cGllling call is dir~cled to a ported di~e~tol ~ number, the time ~ ed to p~r~.llll the LNP ~ h~l~e query and the NXX ofthe actual serving switch of the ;~ 4~ g call. Sul,s~u~ , the LNP-TAS ,~t~.~ti~i process continues to step 318 in which te-.-~ g switch 106 sends LNP~t~b~e-related query st~ti~tics to LNP-TAS120 at a plO1~,t~ eA intenal.
FIG. 4 shows a flow ~ b,. .. of the process steps ~ rc.. ed by LNP-TAS120in int~lligently ~,t~ g an ol~1;--l-LNP ~fl~ ~ query point dunng the call delivery process.
It is !'~ A, in this example, that LNP-TAS120 has been previously initi~li7~fl with A~ ~ o~:~";~-~t;~n cr~ a to ~ r call del;~ time.
The process begns in step 400 in which LNP-TAS120 I~C~ S LNP~at~b~-related query statistics from each central office switch via designated switch data links. In the .,A~ case, LNP-TAS 120 receives st~ti~tics from on~-- ,1;,~g switch 102 and ~dald te....;-. ~ 8 switch 106 via switch data links 130 and 131, lé~ el~. The process continl~es to step 402 in which LNP-TAS 120 ~ Ps the o~ LNP~a~ que~ point in 30 accol~ce with the pl~d~ ~.-Pd o~ ;on criteria using the LNP~lAt~A~e-related query lo 2~ 74~99 ~ ~I"t;~t;cs received from the central office swilches. For ~Ai&~le, to clete ...il~e an LNP d~t~b~e query point which ~ s call delivery delay ~h~ n ori~ g switch 102 and standard ;ng switch 106 ~Il~.ei~ the NPA-NXX of ~d~d ~e....;n~ g switch 106 is a LNP
tslh:-~ query trigger for origin~ting switch 102, LNP-TAS 120 co~ s the volurne of ported 5 di~ ol~ number calls with respect to all oulgoing calls from oriYin~ting switch 102.
In step 404, LNP-TAS 120 derives a switch control update ...~ ge for the apl~lo~)l;ate central office switch(es) in accor~ce with the ~ ".;~ ~1;on made in the previous step. In the eY~lnrl~y case, assume that the LNP ~ b~ related query st~ti~tics received from ori~in~ting switch 102 reveal that a relatively small 1l~ll~. of LM ~ h~ queries triggered by the NPA-10 NXX digits ("708-555") of the standard 1 ....i.. 1;"g switch 106 actually resulted in routing calls to ported di~ n---..l~;~. Accor~ gl~ o~ g SWitGh 102 l~C~ . aII update message which deactivates NPA-NXX digits "708-555" as LNP database query trigger digits such that ~l~d~.l t~ . t;n8 switch 106 b~o.nes l~ ~ible for y f~,....;l~g all LM ~i~t~ba~ queries for ported t~n.~ on the switch (see FIG. 3). In gl~ t;~" ernk)~ , LM-TAS 120 may15 use st~,ti~tics relating to the NXX of the saving switch to which the majority of ported dh~ o ..kc- ~ are dil~t~d to formulate new or ~s~litions1 MA-NXX trigger digits to be stored in an ori~ g switch in accol~ce with the volume of ported di.~tol~ nllml~s to a particular NXX. A LM-TAS 120 switch control update message which replaces or supplements the g MA-NXX trigga digits in an ori~ g switch, ~ ,S Coor ~ ;on -20 ~l~.~n LM-TAS and trunk control system 160 such that o~llg~ g calls to the new trigger MA-N~ may be deli~red effif~i~ntly.
The process ends with step 406 in which LM-TAS 120 updates the a~ ;ate central office s..it~Lei by sending the switch control update message daived in the previous step to the ~wil~l~s over the designated switch links. Although the exemplary embodiment describes the 25 present inv~tion as int~ion~ n an LM-TAS and a plurality of central office swilches, the LM-TAS may interact with any other plurality or combindtion of swil,l~s, including tandem swilches.
In this ",nnn " LM ~ m~ related query s~ti~tics as received from each central office switch may be a~ t;r~lly m~ ,cd and evaluated to intellig~ntly ~et~ ...il-r the "o~thll~lll't LM ~1A~bn~e query point in a local teleco.. is~tionc ll~lw~L. so that the ~wilches can be Il ~ 1 7479~
1y updated to reflect the true state of service provider local number portability in the ~twol~. It is to be ~ de~ )od that the above described embodiment is for illustrative purposes only and that IlU~,~US other ~~ g~ may be devised by one skilled in the art without dep~li~g from the scope of the invention.
Claims (10)
1. In a telecommunications network comprising a plurality of central office switches, a method for establishing an optimum database query point in a call delivery process comprises the steps of:
recording database-related query statistics specific to a central office switch in the central office switch memory;
receiving the database-related query statistics from each central office switch in the database traffic analysis system;
the database traffic analysis system using the database-related query statistics to determine an optimum database query point; and sending a switch control update message to at least one central office switch such that the optimum database query point is established.
recording database-related query statistics specific to a central office switch in the central office switch memory;
receiving the database-related query statistics from each central office switch in the database traffic analysis system;
the database traffic analysis system using the database-related query statistics to determine an optimum database query point; and sending a switch control update message to at least one central office switch such that the optimum database query point is established.
2. The method of claim 1 wherein recording database-related query statistics in the central office switch memory comprises the step of:
storing local number portability (LNP) database-related query statistics including whether a query resulted in extending a call to a ported directory number.
storing local number portability (LNP) database-related query statistics including whether a query resulted in extending a call to a ported directory number.
3. The method of claim 1 wherein using the database-related query statistics to determine an optimum database query point in accordance with the initialized optimization objective comprises the step of:
determining a database query point resulting in minimum call delivery delay.
determining a database query point resulting in minimum call delivery delay.
4. The method of claim 1 wherein sending a switch control update message to at least one central office switch such that the optimum database query point is established comprises the step of:
the database traffic analysis system sending an update message to a central office switch over a designated link wherein the message requires the central office switch to store supplemental trigger office code digits.
the database traffic analysis system sending an update message to a central office switch over a designated link wherein the message requires the central office switch to store supplemental trigger office code digits.
5. A local telecommunications network comprises:
at least one originating switch including memory means for recording LNP
database-related query statistics;
at least one standard terminating switch including memory means for recording LNP database-related query statistics;
a local number portability-traffic analysis system (LNP-TAS) including an LNP
database in communication with the originating switch and the standard terminating switch;
means for receiving LNP database query statistics from the switches in the LNP-TAS in order to determine an optimum LNP database query point during call delivery in the telecommunications network; and means for sending switch control updates from the LNP-TAS to the originating switch.
at least one originating switch including memory means for recording LNP
database-related query statistics;
at least one standard terminating switch including memory means for recording LNP database-related query statistics;
a local number portability-traffic analysis system (LNP-TAS) including an LNP
database in communication with the originating switch and the standard terminating switch;
means for receiving LNP database query statistics from the switches in the LNP-TAS in order to determine an optimum LNP database query point during call delivery in the telecommunications network; and means for sending switch control updates from the LNP-TAS to the originating switch.
6. The network of claim 5 wherein the means for receiving LNP database query statistics from the switches comprises a data link between the LNP-TAS and each switch.
7. The network of claim 5 further comprising means for controlling a trunk control system to establish trunks between switches.
8. The network of claim 5 and further comprising means for sending switch control updates from the LNP-TAS to the standard terminating switch.
9. An originating switch in a telecommunications network comprises:
means for recording LNP database-related query statistics;
a local number portability traffic analysis system for determining an optimum LNP database query point; and means responsive to the local number portability traffic analysis system for updating the originating switch in accordance with the optimum LNP database query point determination.
means for recording LNP database-related query statistics;
a local number portability traffic analysis system for determining an optimum LNP database query point; and means responsive to the local number portability traffic analysis system for updating the originating switch in accordance with the optimum LNP database query point determination.
10. In a telecommunications network comprising at least one originating switch, at least one standard terminating switch and at least one serving switch, a method for accessing a local number portability database during call delivery comprises the steps of:
recording LNP database-related query statistics in an originating switch memory each time an LNP database query is performed by the switch;
receiving LNP database query statistics in a local number portability traffic analysis system at predetermined intervals;
using the LNP database-related query statistics received from the originating switch to determine an optimum LNP database query point in the call delivery process; and updating the originating switch with a switch control update message in accordance with the optimum LNP database query point determination.
recording LNP database-related query statistics in an originating switch memory each time an LNP database query is performed by the switch;
receiving LNP database query statistics in a local number portability traffic analysis system at predetermined intervals;
using the LNP database-related query statistics received from the originating switch to determine an optimum LNP database query point in the call delivery process; and updating the originating switch with a switch control update message in accordance with the optimum LNP database query point determination.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US08/507,892 US5703939A (en) | 1995-07-27 | 1995-07-27 | Method for determining an optimum point for database queries during call delivery in a telecommunications network |
| US507,892 | 1995-07-27 |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CA2174799A1 CA2174799A1 (en) | 1997-01-28 |
| CA2174799C true CA2174799C (en) | 1999-02-02 |
Family
ID=24020554
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002174799A Expired - Fee Related CA2174799C (en) | 1995-07-27 | 1996-04-23 | Method for determining an optimum point for database queries during call delivery in a telecommunications network |
Country Status (5)
| Country | Link |
|---|---|
| US (1) | US5703939A (en) |
| EP (1) | EP0756428B1 (en) |
| CA (1) | CA2174799C (en) |
| DE (1) | DE69624989T2 (en) |
| MX (1) | MX9602945A (en) |
Families Citing this family (26)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6445785B1 (en) * | 1995-11-21 | 2002-09-03 | Verizon Laboratories Inc. | Methods and apparatus for local number portability in telecommunication systems |
| EP0827319A3 (en) * | 1996-07-30 | 2000-05-17 | Hewlett-Packard Company | Global title translation in a telecommunications signalling network supporting number portability |
| US6134316A (en) * | 1996-10-18 | 2000-10-17 | Telefonaktiebolaget Lm Ericsson | Telecommunications network with relocateability of subscriber number |
| US5943411A (en) * | 1997-05-12 | 1999-08-24 | At&T Corp. | Method for routing an NP call |
| US6366663B1 (en) | 1997-07-21 | 2002-04-02 | Mci Communications Corporation | System for achieving local number portability |
| US6130939A (en) * | 1997-08-08 | 2000-10-10 | Telcordia Technologies, Inc. | Apparatus and method for number portability call processing |
| US6161017A (en) * | 1997-10-07 | 2000-12-12 | Telefonaktiebolaget Lm Ericsson | Method of routing calls to portable numbers in a radio telecommunications network |
| US6081590A (en) * | 1998-02-02 | 2000-06-27 | Lucent Technologies Inc. | Call treatment in portable number networks |
| US6028914A (en) * | 1998-04-09 | 2000-02-22 | Inet Technologies, Inc. | System and method for monitoring performance statistics in a communications network |
| US6614894B1 (en) | 1998-06-05 | 2003-09-02 | Inet Technologies, Inc. | System and method for mass call onset detection in a communications network |
| US6529594B1 (en) | 1998-06-05 | 2003-03-04 | Inet Technologies, Inc. | System and method for generating quality of service statistics for an international communications network |
| US6411604B1 (en) | 1998-06-05 | 2002-06-25 | Inet Technologies, Inc. | System and method for correlating transaction messages in a communications network |
| US6381306B1 (en) | 1998-06-08 | 2002-04-30 | Inet Technologies, Inc. | System and method for monitoring service quality in a communications network |
| US6359976B1 (en) | 1998-06-08 | 2002-03-19 | Inet Technologies, Inc. | System and method for monitoring service quality in a communications network |
| US6249572B1 (en) | 1998-06-08 | 2001-06-19 | Inet Technologies, Inc. | Transaction control application part (TCAP) call detail record generation in a communications network |
| US6487412B1 (en) * | 1999-07-01 | 2002-11-26 | Gte Wireless Service Corporation | Method and system for routing calls to wireless directory numbers in a network |
| US6909900B1 (en) | 1999-07-01 | 2005-06-21 | Gte Wireless Service Corporation | Wireless mobile call location and delivery for non-geographic numbers using a wireline SSP+SCP/wireless HLR interface |
| US6473503B1 (en) | 1999-08-31 | 2002-10-29 | Worldcom, Inc. | System, method and computer program product for achieving local number portability network management support |
| US6438219B1 (en) | 1999-08-31 | 2002-08-20 | Worldcom, Inc. | System, method and computer program product for achieving local number portability costing support |
| US6473502B1 (en) | 1999-08-31 | 2002-10-29 | Worldcom, Inc. | System, method and computer program product for achieving local number portability costing and network management support |
| US7054636B1 (en) * | 2000-03-01 | 2006-05-30 | Gte Wireless Services Corporation | Method and system for communicating data from wireline terminals to mobile terminals |
| US6965574B1 (en) * | 2001-06-20 | 2005-11-15 | Arbor Networks, Inc. | Network traffic data collection and query |
| US6889333B2 (en) * | 2001-11-01 | 2005-05-03 | Microsoft Corporation | System and method for replicating data in a distributed system |
| US6975711B2 (en) | 2004-04-07 | 2005-12-13 | Sbc Knowledge Ventures, L.P. | Method and system for forecasting telephony traffic trends using local number portability databases |
| US7304575B2 (en) * | 2005-06-01 | 2007-12-04 | Intel Corporation | Low cost power amplifier linearization in an RFID radio transmit chain |
| US20090003388A1 (en) * | 2007-06-30 | 2009-01-01 | Lucent Technologies, Inc. | Method and apparatus for synchronizing ported number data |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US4972464A (en) * | 1989-11-01 | 1990-11-20 | U.S. Sprint Communications Company Limited | System for placement of a long distance telephone carrier point-of-presence and call routing |
| US5048081A (en) * | 1989-12-28 | 1991-09-10 | At&T Bell Laboratories | Arrangement for routing packetized messages |
| US5270919A (en) * | 1990-06-04 | 1993-12-14 | At&T Bell Laboratories | Network planning tool |
| US5237604A (en) * | 1991-06-28 | 1993-08-17 | At&T Bell Laboratories | Arrangement for serving a telephone office code from two switching systems |
| US5386467A (en) * | 1992-07-31 | 1995-01-31 | At&T Corp. | Intelligent network communication system |
| CA2165857C (en) * | 1995-12-21 | 2000-07-25 | L. Lloyd Williams | Number portability using isup message option |
-
1995
- 1995-07-27 US US08/507,892 patent/US5703939A/en not_active Expired - Lifetime
-
1996
- 1996-04-23 CA CA002174799A patent/CA2174799C/en not_active Expired - Fee Related
- 1996-07-17 DE DE69624989T patent/DE69624989T2/en not_active Expired - Lifetime
- 1996-07-17 EP EP96305229A patent/EP0756428B1/en not_active Expired - Lifetime
- 1996-07-23 MX MX9602945A patent/MX9602945A/en not_active IP Right Cessation
Also Published As
| Publication number | Publication date |
|---|---|
| EP0756428A2 (en) | 1997-01-29 |
| US5703939A (en) | 1997-12-30 |
| MX9602945A (en) | 1997-01-31 |
| EP0756428B1 (en) | 2002-11-27 |
| DE69624989D1 (en) | 2003-01-09 |
| EP0756428A3 (en) | 2000-02-23 |
| DE69624989T2 (en) | 2003-07-24 |
| CA2174799A1 (en) | 1997-01-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA2174799C (en) | Method for determining an optimum point for database queries during call delivery in a telecommunications network | |
| CA2251507C (en) | System and method for providing caller identification in conjunction with calling card calls | |
| CA2129511C (en) | Intelligent call processing based upon complete identification of calling station | |
| US7421070B2 (en) | Advanced intelligent single telephone number routing | |
| US6697480B2 (en) | Method and network for routing a communication through an alternate carrier | |
| CA2150063C (en) | Completion of intelligent network telephone calls | |
| CA2217037C (en) | A system and method for providing portable telephone number service | |
| US5832072A (en) | Communication network with hidden calling number capability | |
| CA2174796C (en) | Method for automatic maintenance of a local number portability database | |
| US5506894A (en) | System for processing calling party information for international communications services | |
| US5095505A (en) | Efficient flexible special service call processing | |
| US5592541A (en) | Apparatus and method for forwarding incoming calls | |
| US5740239A (en) | Method and apparatus using bit maps to access data for processing telephone calls | |
| CA2232319C (en) | A self-provisioning names database for caller identification services | |
| US6728355B2 (en) | Method and apparatus for forwarding a caller identification for a credit card or calling card call to an automatic number identification system of a telephone network | |
| CA2228242C (en) | Automatic updating of a local database supporting local number portability | |
| US5896447A (en) | Method for accommodating ported directory numbers affected by call block controls implemented in a telecommunications network | |
| Cisco | Chapter 5 - Producing BAF and ASCII Records |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| MKLA | Lapsed |