CA2252757A1 - A communications network having a multicast capability - Google Patents

Abstract

A communications network simultaneously transmits a single message to a number of recipients. This is called a "multicast" transmission. The communications network should have a recipient list database (1302) to receive a list of recipient addresses, a message database (1304) to receive and store the message, and a message delivery system (1306) to send the message to a number of recipients. The communications network may be adapted to collect acknowledgements or responses to a multicast message. If so, the communications network should have a calling record (1308) for storing message delivery information, a response record (1310) for receiving and storing recipient response information, a response processor (1312) for processing the response information, and a response delivery system (1314) for delivering the processed response. The multicast capability may be integrated with other communications network services, such as Personal Location Service, Personal Communications Internetworking, call blocking, etc.

Description

WO 97/44924 PCTtUS97/08229 A COMMUNICATIONS ~ETWORK HAVING A MULTICAST CAPABILITY
5 BACKGROUND OF THE I~VENTION
Field of the lnvention The present inveMion relates to comm-lnir~lions syslems and. more particularly, to 5imul~n~0ucly trancmittin~ a mPsC~e to a number of location . and to collecting and ~ G.~ g acknowledgc-l-e.1~5 and responses to the message.
Diccu~ n of Related Art Delivering information via wireline or wireless tr~ncmicsion is becomin~ incleasiugly common The information may be in the form of a telephone call, fax, digital video.
mnltimP~ . data (such as e-mail). and the like. As seen in FIG. 1. information, such as stock pnces. ~raffic information. wea~her reports, airline srhPdlllPs, and sports scores, may be 15 broadcast from a single source. such as a service provider 30 (not unlike a tcle~,hone sen~ice provider) over a commllnir~tinns network 32 to a number of recipients (users) via wireline and wireless tr~ncmi~sion media. The information lo be tr~ncmirtp~i may be provided by a third partv. with the service provider tr~ncmitting the information in exrh~nge for a fee. The wireline ~r~ncmicsion media may be. for example, a switched col~ tions network, the Interne~. or 20 other wireline network. The wireless media may be connccl~d to the wireline L~n~ ion media and may be, for example. cellular phone networks or PCS (personal co.~ ;r~c services) n~.wo"~s. (A glossary of acronyms is ~tt~chPd as an Appendix.) A user may be any cQmmllnir~rions services cuctom~r having a commlmir~tior1c termin~l 34, such as a wireline tclephone 34A, fax m~ in~ 34B, personal computer 34C, cellular '5 telephone 34D, personal digital assistant (PDA) 34E, or digital video iMerface device 34F, as is illustrate~ in FIG. 1. Note that in Fig. 1, wireless co..ll..ll.lir~rionc are inriir~r~d wi~h 3 dashed line. _ Fig. 2 is a greatly simp!ified illustration of a commnnir~riorc network 32. The desc,ibed comm~nir~tionc system is similar to other types of comm~nir~-ions n~.wGr~s and is described 30 to provide background to the following (iiccussion of the inven~ion; it is not intPntlP-i to limit the invention to use with the desc~ibed co-llllll~nic.,rions system. The Coll~lllllnir~liorl~ n.,.wo~t. 32 inrlud~Ps a sign~linv network 102. which supports a swiL~;hed co.llll.~ ir~tions n~tw~lk. A
switched comm~mir~rions network may be. for example, a Pu~lic Switched Telephone Network (PSTN) or an Integrated Signaling Digital Network (ISDN). The cign~lin~ network 102 is used 35 for exchange of call set-up and other call m~in~en~nre inforrnation. Once a ca~l is set up via the THIS PAGE WAS NOT FURNISHED UPON FILING
THE INTERNATIONAL APPLICATION

W O 97/44924 PCT~US97/08229 THIS PAGE WAS NOT FURNISHED UPON FILING
THE INTERNATIONAL APPLICATION

CA 022~27~7 1998-10-28 The marke~ for information services is large. On the other hand. marke~ l~seal.hinr~ir~t~s that polential customers may place s~rict limita~ions on the amount they are willins ~o pay for ~hese services.
rherefOre. it is an objecl of the presem invemion to provide a cornmllnic~tions network 5 architecnlre which efficiently uses ne~work l~_SUUI-eS tO send a single message to a pluraiity of destina~ions.
It is another object of the present inveMion to provide a col...,.,.,-ir~tions network archir~cmre which helps to solve the illfol,llation "st~lPn~ss" problem when sending a single mrcc~ve to a plurality of ~estin~tions~
It is yet a further object of the present invention to provide a co~ in~ions network arc~ cn-re which may send a single meCc~se to a plurality of de3~;"~ions in an ecQrlomi manner.
It is an even further object of the preseM invention to provide a method for collectins acknowledse.l.~ a and/or responses to a number of sim~llt~nPous tr~ncmicsions of a single message.
SUM~IARY OF THE INVENTION
These and other objects are achieved by the present invention. The present invention simlllt~nrously transmits a single message to a number of l~cl~icnts. This is called a "mllltir~ct"
transmission.
In a first plcf~ d embo~im~nt. existing network cGI~l~onen~s are used to receive a message and simult~n~oucly transmit the m~Cc~ge lo a number of I~Ci~ lLs. Using this commllnir~rions nc.w~lk a~ re. a mllltir~Ct ll"T,~".,c~on may be sent as follows:
1. the message provider (user) calls the mllltir~ct service;
. the message provider-s call is received at a switch and the call is 5ll~ n~
~5 3. the switch queries a network t~ b~ce~ which consults the message provider's (or . ather's) CPR;
1. the CPR illa~u~la the messase provider's network server to hll~".,ede;
5. the nwdlk server queries the message provider and obtains the message and l~,iyient addresses (i.e.. telephone llu~ a, facsim~ numbers. and/or e-mail addresses);
6. the n~lwol~ server stores the messages and at that time or a later time simlllt~n~oucly contacts some or all of the leci~ ; and 7. the m~sS~V,e is transmitted to the contacted I~Ciyi~.ltS.

In a second preferred embo~im~nt Ihe cr~ ir~ri~nc r.e.work uses an existing si~nqlinP network, such as an SS7 network. to forward the m~ccq~e to remole .eiiyie~lL~. Using ~his comm~nirqtions ne~work architPcn~re. a ml~lticqct 11A~C~ SjOn may be sent as follows:
l. the message provider calls the m~ irqcI service;

2. ~he message provider s call is received at a switch and the call is s~c~en~

3, the switch queries a network ~l~tAhac~. which consults the m~scqpe provider's (or other's) CPR;
L the CPR instrucIs the m~Cca~e provider's ne~work server to inL~.~ede:
5. the ne~work server queries the m~ccq~e provider and obtains the message and leciyie.ll addresses (i.e.. teleph~ numbers. f~esimi~ lber~, and/or e-mail addresses);
6. the network server stores the messages and at that time or a later time slmllltAnlooucly contacts some or all of the local ~e~,iyi~nLs 7. the network server or ne.w...k ~q-tAbAqse fo.wdrds the m~sc~e to a remooe network server via thc signq!in~ n.Lw~r~;
8. the remote network server stores the m~csAge and at that time or a la~er timeSjmlllrAqn~ooucly contacts some or all of the remote te.i~)iel,Ls: and 9 the ,llessagc is trq~ncmirted to the local l~,ci~uienL~ by the local network server and to the remote ~eciyients by the remote n~ r~ servers.
In a third ylefe~d emboclim~nt the col.. ,.. ~ ications network uses existing si~rqlinv network co"lyone~lLs to set up a ~runk line to deliver the m~csAqee. Using this comm~ Ar.o~lc ne~work arrhit~c~-re. a mllltirAqct trncmicsiQ~ may be sent as follows:
l. the message provider calls the m~ irAct service;
2. the m~cs~ae provider's call is received at a switch and the call is ~ FQf~
3. the switch queries a nelwork ~qAtAqhqce. which consults the mPcc3ge ~lovide.'s (or . ~her's) CPR; the CPR i~ u~;ts the message provider's ne.wo-k server to i,lte,.,ede;

4. the ne~work server queries the m~ccA~e ~,o~,ider and obtains the ~ e and ,eciyi~ addresses (i.e.. ~elephone numbers, farsimilP numbers. and/or e-mail add~esses);

5. the network server stores the messages and at that time or a later time 5imll1tAqn~ously contacls some or all of the local l.ci~ienLs:

. .

WO 97t44924 PCT/US97/08229

6. the r~.w~rh server dials a special number to contact either a remote n.,.~u-~server or remo~e network ~ se in order to establish a trunlc line beL.._~a~ themessage provider's swiuh and the remote leci~i~nt's switch:

7. the call is handed over to the remote n~.wo-k [l~r~h~ce and then to the remote n._twork server:

8. the local and remote network servers (or network server and network ~ hqC~) ex~h~nge mPcc~gl-s over the trunk, and release the trunk; and

9. the message is tr~ncmittt~d to the local reciy~e~ by the local network server and to the remote Ic.ilJ CIlL~ by the remote n~.wolk servers.
In a fourth ylcf~ d embodim~ separate m' ltir~ct service nodes are conlle.,te~ to the co~ n.r~;onC network for h~nrllin~ the m~ c~ct capability. The service nodes may be conn~ed to each other by a data network- Using this co,.. l--;r~lions network arcki~ rc.
a mlllrir~ct trancmicci~ n may be sent as follows:
1. the m~Ss~ve provider calls the mllltir~ct service;
2. the message provider s call is forwarded to a service node;
3, the service node queries the message provider and obtains the m~c~age and l.CipiC lL addresses (i.e., teleFhnn~ numbers, f~cimile nurnbers, and/or e-mail addresses);
4. the service node stores the m~Cca~s and simlll~n~ ously contacts local ~.,iy.C~
5. the service node contacts remote service nodes via the data network; the service nodes e~h~nge information: and 6. the m~ss7Pe is tr~ncmittPd tO the local lLCi~ ~ via the local service node and to the remote recipients via remote service nodes.
This embodiment may be revised to connect the service nodes directly to switches and to each 25 other. This -el;...~n~tf c the local and remote network servers from the mlllti~ct service. This embodiment may also be revised to connect the service nodes to both a switched comm~ sns network and a data network.
Any of these embo~lim~ontc may be adapled to collect ach,uwl~Ag~ .lF,ll~ or ~ yonscs to a mllltin~ct m~Ss~ge~ A ylcr~llcd method of p~rO~ ulg this is to create a calling record when 30 a ml-lti~ct message is seM. The m~sC~ge may be sent with a ~ f,l~d r~yonse. The recipiem's r~;~yonse is received by the network server or service node and stored in the callin~
record.

Wo 97/44924 PCT/US97/08229 The m-lltir~c~ capabilitv may be ;~ r~r d with other CO~ m~ on~ ne~work services.
Mllltirqct may be co~-.binf ~ with Personal Location Services (dcs~libed in U.S. Patem Application Serial No. 081578 879) or Personal Co.. ~ lions Illte~ wo~ing (des."bed in U.S. Patent Application Serial No. 08/309 336). M-~ltic~c~ may also be n-r,~lifif d to handle 5 delivery to ~eciyi..-~ with Do Not Disturb call blocking or time of day call routing.
BRIEF DESCRIPTION OF THE DRAWINGS
The present inveMion is des- "bed with ~~f~.e.~ce to the following figures:
Fig. 1 ill~ r. s a co~ ions n~.wolk data service;
Fig. 2 ill~ ,t~s a co~.".lionql co.. --.-i~a~;o.. c r.~.wG.~;
Fig. 3 illua.,~tcs a co-.. ---~-~a~ionC n.lwu~k ar.l.;t~ e acco.ding to a firs~ f .. l.~l;.. -according to the present inveMion;
Fig. 4 is a call flow diqgram for the ~o------ ~----~a~ions n~.ulk of Fig. 3;
Fig. ~ illustrales a co-..---- --ir~tions network a~ tl~ ~1... c acco,~ g to a second f m~o-iim--nt of the prcseM invention;
Fig. 6 is a call flow diagrarn for the co.. ---- ;~lions n~.wulk of Fig. 5;
Fig. 7 illus~ s a co------ ~.~ lions n lworl~ al~ c~,c according to a third embodiment of the present Invent~on;
Fig. 8 is a call flow diagram for Ihe co... ---- ~,iol.c r,~.wo,~ of Fig. 7;
Fig. 9 ~ lclr ,1~ s a co-mmllnir~tion- network ~l~ki~. cn~c; according to a fourth ~ o~ --t of 20 the present inveMion;
Fig. 10 is a call flow ~iagtq-m for the cO~ iol~c n. .wulk of Fig. 9;
Fig. 11 illustrates a cr.-~--~--...i~ ~lionC n .wul~ al.k;l~ acco,dillg to a fifth embodi neM of the present invention;
Fig. 12 ill..,~ s a c~ nir~lions network al.}s;l~ cl--.e acco~ g to a sixth e.llbo~ of 25 the preseM .~ve.llion; and Fig. 13 is a block ~iqgram of a n~ .wolk co",l,o~ acco,.ling to the present invention.
DETAILED DESCRIPIION OF PREFF~2RF.o EMBODI~NTS
Simultaneous Deliver~ Of One ML ~C To A Pluralitv of Recipients ("~ulticast") The dlawlac~ and yroblc~ls that exist in the related art are solved by Cimlllt~nf'OUCIy 30 delivering a m-oC~age to a number of r~ci~ nts. This is called a m~ ct l~.r.~...iccio!~
Fig. 3 is a first yl~fe~led conlm~ ali~ n~lwo.~ al~ 300 according to the preseM invention. This ar~ (and the ones des~libed below) is desclibed with ieÇe.~ e to telL~hone calls. but the reader understands that it may be equally applicable to other types of CA 022~27~7 1998-10-28 wo 97/44924 PCT/US97/08229 CO~,~,,,,,,,,rqtiOnc media as described in relation to Figs. 1 and 2. This a~ c uses existing co"~ ions r,..woll~ components to provide the faciliti~s ~ Lly offered by c~ y available end-user e4~ --f ~~ such as fax ~ f 5 with "broadcast" capabilities.
In this emboAimPnt existing network components are used to receive a l.~Fcs~.~e and 5 transmit it Sim~ nPousiy to a number of ICei~ ua The al.~ilP~ e 300 inrl~Aes a sending comm~mi~arions terminal 302, a sending SSP 304 connected to the sending co~"""l,~;r_~;onc ~erminal. a network sener 306 such as an IP, a network A-q-tqhqcP 308. such as an SCP. a CPR
310 connected to the network d~rqbace 308, and siPnq-~in~ transfer points 312 (for simplicity.
Fig. 3 and all s~thsequent figures collapse the regional and local si~nqling transfer points into a single co",i~or,ent). ,ecil ient comml~nirqtionc terminqlc 316, and ,~cil,.c.,L SSPs 314 CG~ 'd to the l~ci~ie.1t comml~nirationc terrninals. If the r~ciy.e.,i co~ nlionc re~rninql is a wireless comm~mirqtiQns device. the rccipie.lt SSP is conne.hd to a mobile switching center 318 which COIlnC.La tO a wireless comm~lnir~tirJns n..w..,~. The wireline co"".".";rqtin~c network inrtudes a VLR 322 and one or more base sutions 324. A HLR 320 is co,~rc~ to the15 wireline cQ~ m~irOIiorlc network. In this, and the fol1Owing emboAim~ntc~ a n~.w~ server may be col",e_tcd to other networks 326 such as a dau network, the In-~rn~t etc.In this embodirnent. the conventional co-..,..,lnir~tionS system CPR,IP, and SCP are og~ "ed so that their existing capabili~ies handle the mllltirqct capability. A ~~s-a&, provider may call the mllltirqct service by, for exarnple, dialing a y~det~"~ined number (i.e., 1-800-MULTICAST). The call may be routed to a nearby network server 306, such as an IP.
The lP may contact an a~yloyllatccpR3loto create a rcci~i..ll list. (If a r.ci~ie.l~ list alreadv exists. ~he CPR310 may not be contacted at this time. ) A basic mll~tir~ct service may have one or more d~Airqt~d CPRs which anyone may access by dialing the predesignqrpd number.
Alternatively, advanced mlll~ir~ct service may require a CPR created for each user. The CPR
25 is modified ~o accept and store a mPscqge delivery list. This list is a directory of ~ ,e."
addresses, such as phone ,,u,,,~c.~. farcimil-o number, or e-mail addresses, to which the mPC~a~e is to be delivered. These addresses may be entered into the list using a al~nda~d lf ~ o~r {using DTMF tones or speech recognition), or a co,~ ~r with a m~dpm~ The l~ De provider may specify a list of addresses to be stored in the CPR. The list may be ~cresc~d at 30 a later time for sending future m~ss~ges to the same leci~,h.l~. In that case, the m~crag~
provider need only enter the new message~ and the system uses the stored list of add,~ses to deliver the m~Ccage. The message provider may also retrieve the list of stored addresses. and delete or add numbers to it, using a standard tcle~hone. or a co~ r~ . with a modem.

CA 022~27~7 1998-10-28 The CPR may be proy~ cd to allow a message provider to store a number of different lists. In this case, the addresses (i.e.. phone numbers. ~arsimile .lumbc.~. and e-mail addresses!
may be entered using a standard telephone, using identifiers that may be as simple as a single number ~i.e.. "1 ' to specify list #1. ~ for list #2. elc.) or spelled-out names (i.e., S-A-L-E-S, 5 B-A-~-K-S) eMered from the telephone keypad. Once multiple lists have been created, thc user may be able to specify a list of l..lpients to receive a panicular m~ss~ge. The user may also edit the lists as desired. Preferably, the stored list of addresses may be acceccPd from any phone line within the PSTN by dialing the special number for the m~ltir~sr service (i.e., 1-800-MULTICAST). Thus, for example. a company could set up a centralized list of phone or fax

10 numbers of its sales r~ SC-Ildtives, and allow that list to be used from anywhere in the country (i.e.. other branch offices, store outlets, etc.).
Securit against unauthorized access to the lists is possible. For example, lists may be password or personal identificauon number (PIN) protected in the same way that ~llrol.~r~rd banking accounts are. for example. Another example may be p..lllil1illg access to lists only 15 from a particular phone number. This may be accomplished using "caller ID" technology, where the lis~ may be a~r~cced where Ihe telephone number from which the call is o~ n~
r~tos the authorized phone number (or numbers).
rhe IP 306 may be l"ug.dllulled îo receive a number of ~estin~tionc for a singleincomin_ message. The IP is ylogldllullcd to allow the IP to request the user to enter a list of 20 destinalions. and to receive and record the list. Alternatively (or in addition), the IP 306 rnay receive the list of ~P~tin~rions from the CPR 310. The IP then connects the mrsc~ge to one or more outgoing lines at the same time. The call connections may be made in the usual manner.
rhe messa_e provider may then instruct the system to deliver the information imm~ tPly.
Alternatively, the message provider may specify that the mrcs~ge be sent to all or some of the 25 recipients at a later time (i.e., to take advantage of lower toll charges or to send the message to a differen~ t~ne zone). Note that the IP is not required to handle capabilities not alreadv performed by existing IPs.
The messadge delivery time can be entered using a ~ldnda,d telPph~ or a co.~ . . The IP may be proy-dll~l,cd to store the message and leciyicnts~ addresses until the ~le~i~;n-t~d time 30 before sending the message. Some calls may be made at one time and other calls may be made at others. For example, if a multicast message is to be made to area codes in diff~.e,lL time zones. the mllltir~ct service may be pro~rammed to deliver a message at a particular time in the time zone. A mllltir~ct message provider may request that a message be delivered at 9:00 a.m.

in the time zone in which the message will be received. If the message provider is calling from New ~ersey at 8:00 a.m., the messa_e will be slored and the leciyienl area codes will be checked agairlst a time zonelarea code ~t~hqcP. Calls to New York City (212 area code).
Atlanta (404), and Miami (305) will be made one hour after the message is provided. Calls to Chicago (312) and Kansas City (816) will be made two hours after Ihe m~Cc~ge is provided.
Calls to Los Angeles (213) and Seattle (206) will be made four hours after the message is provided.
The SCP 308 may be prograllllllcd to receive and handle calls requc-sting the mlJltir~cr service. The SCP is not required to handle capabilities not already pe~ro.,l,ed by existing SCPs.
Fig. 4 is a call flow 400 which may be pe.îu~ ed by the a~ ;T~ c of Fig. 3. The call flow may be modified in a marmer well known to those skilled in the art to deliver fax. data.
video, or other type of cn....,.~ f~onS, as well. A rn-llrir~ct Ll,.rl~...;ccion of a single m~Ss~e preferably occurs in the following manner.
1. The m~sc~ge provider contacts the m~ ir~c~ service by, ~or example, dialing a number provided for the m~ ir~5~ service.
2. The message provider's call is received (line 402) at the SSP 304. The SSP 304 suspends the call.
3. The SSP 304 queries the SCP 306 (line 404).
1. The SCP 306 consults ~he a~l~loyli~l~ CPR 310 (e.g., either generic or user- specific), which ins~ructs the IP 306 to intercede (line 406).
5. The IP 306 plays an ~nnr~u~ r such as "Enter ~osrin~tion llu.ll~.a and mrSC~e" (line 4û8).
6. The m~cc~ge provider enters the message, ~eciyie~l~ address list (either a new list or refers to an existing list in the CPR), and other reql~ostt~i information in an a~uylolJliat~ manner (line 410). For example, il~ollllaLion may be y~l~chcd on aphon~ key pad using DTMF signals, typed on a keyboard, or spoken (if the co~ ira~ions network has syeech r.co~,lli~ion capability).
7. The IP 306 stores the m.~cc~ge and places calls to the ;n~ir~.eli re.iyiell~ (line 412).
8. The reciyie~lts receive the message.
If the r.~i~olh server 306 is connected to additional n~.~c.ks 326. such as the Internet.
the ,.ciyient list may include addressei in different formats, such as telephone numbers.
faesimile numbers~ or e-mail addresses. Thus, the same m~sc~e may be delivered to a first leciyic.lI as a farcimil-o transmission over the PSTN and to a second ~~.,t,ie.,i as an e-mail over the Internet. A format conversion may be pe.fulllled for this service. These types of formaI
conversions are well known in the art. Thus, a telephone message may be converted into text by a speech reco~llhion device. The text may then be trancmitt~l as data (i.e., e-mail) or 5 converled into f~rcimii~ forrnat for trqncmiCsi~n An e-mail m.-CC~ge may be converted into a voice messa_e using a speech synth~si7~r. These format conversions may be performed in all of the following embo~im~rltc.
Fig. 5 is a second y.~fellcd co.. ~ ions network arCi~ir~cn~re 500 according to the present invention. The embodiment uses existing sienqlinv. colllyol~ents to transmit the ,.~ ge to remote .e.iyienLs. The arC~lir~ocn~re 500.in~ ri~5 a sending comm~lnir~iorlc terminal S02. a sending SSP 504 connected to the sending comm-~nicqrior~s terminal. a network server 506 such as an IP, a n~.wu-}- dqtqhqce 508 such as an SCP, a CPR 510 inctqlled in the nelwork dqrqhqcP
Sivn~iing transfer points 512. Iocal SSPs 514, and local r~.Ci;;~ienL terrnina's 516. The co...~,imir-q-tions netwo-~ 500 also inrlllde5 an SS7 sigrlqling ne~work 518 for con.t~lion to a remote network server 520. such as an IP, remote SSPs 522, and remote rC~;iy.~.lL
co..,.,.lmirqtions tertninals 524.
Fig. 6 is a call flow 600 which may be used with the arrhi~rct~ of Fig. 5. The call flow may be modified in a manner well known to those skilled in the art to deliver fax. dau.
video, or other type of comml~nir~tinns, as well. A mnlti~ct tr~ncmiccion of a single nt~c~ge 20 preferably occurs in ~he following marmer.
1. The message provider calls the mllltir~ct service by, for exarnple, dialing a number provided for a mlll~ie~ct service.
The message provider s call is received (line 602) at the SSP 504. The SSP 504 5~lcp~n~c the call.
3. The SSP 504 queries the SCP 508 (line 604).
1. ~e SCP 508 consults the ay~ iate CPR 510 (e.g., either generic or user-specific), which instructs the IP 506 to intercede (line 606).
5. The IP 506 plays an annon~ such as "Enter d~stin~i()n ~ lbe,~ and m--ccage" (line 608).
6. The m~cc~ge provider enters the message, l~ciyie.. l address list (or refer to an existing list in the CPR), and other reqlles~ .alion in an ayyn)y-idte manner (line 610).

CA 022~27~7 1998-10-28 7. The IP 506 stores the message and places calls lo the inriirqr~d local recipients (line 612).
8. Either the local IP 506 or SCP 508 forwards the .l.essage to remote IPs 520 via the SS7 network 518 (line 614).
9. The remote IP 520 stores the m~Cc-q-ge and places calls to the in~ qt~d remote recipients ~ line 616) .
10. -The local and remote Icci~ie"L~ receive the m~cs,qPe.
This archirec~ 500 uses the existing SS7 signqling n-,lWU~k 518 to deliver the ...~cc~
to remote recipients via remote IPs in the n .wolk. The remote IPs deliver the ~ocliage to ~t~Stinqtions conl~.hd to a nearby SSP. This a~ kit~ct~i~c 500 may require qa~v~ 1;.. g the SS7 protocol (such as the Trn~ction Capabilities Application Part, or TCAP) with a~lut,.ialc m~ss,q,ges. The qnPm~nrqtiOnS to be made are obvious to a person skilled in the ar~ and are not discussed further. The choice and delivery of the user messaee to the remote SSP may be coordinated by the SCP 508 or by the local IP 506. After collecting the m~sc~qge and list of destinq-rion numbers. Ihe local IP 506 may forward this information to the local SCP 508, which may then contact the local and remole IPs 506, 520, or the local IP 506 may directly contact the (ay~ ate~ remote IPs.
The SS7 network 518 has Iypicall,v been used only for sending cignqlinP inforrnation such as call set up or qCsociq-rpd cignqling. It has not been used for sending user m~csages~ which are 20 typically sent on the voice trunk. It may not be practical or desirable to use the SS7 r,.,.wo.l~
to provide such a capability.
Fig. 7 is a third plefe.l~d commn...~-l;ons neLwo.k a~ ;t~c~ 700 according to the present invention. This embodimeM uses existing r,clwulk co~ one.l~ to set up a trunk line to deliver the message to remote recipients. The archir~cn-re 700 in~lnrlPs a sending commt-ninqrrons terminal 702, a sending SSP 704 conllected to the sending commllni~q-ri~ns terminal, a a~u-k server 706 such as an IP. a r,.,.work ~qrqhqce 708 such as an SCP, a CP~
710 inct~ l in the network rlq~ qce, signaling transfer points 712, local SSPs 714, and local ~ci~Jie.l~ terminals 716. The commm-.~A-iQns nelwork 700 also in~ ldes an SS7 si~nqlinV
network 718, the signaling ne~work connects to a remote ne~work server 720, such as an IP, a remote nc.wolk dqnq-hq-ce 722, such as an SCP, remote SSPs 724, and remo~e l~Ciyi~
c~.. ~ninqtions ~erminals 726 (for clari~y, only one remote SSP 724 is shown). A trunk line 728 is directly or indirec~ly connec~ed be~ween the messqge provider's SSP 7~4 and the remo~e SSP 724.

CA 022527C~7 1998-10-28 Fig. 8 is a call flow 800 which may be used with the al~r.it~ ~..,c of Fig. 7. The call flow may be modified in a manner well known ~o those skilled in the art to deliver fax, data, video, or other type of comml-nir~tiorls~ as well. A m~ ir~ct trancmicsion of a single message f~,dbly occurs in the following manner.
1. The message provider calls the mllltir~ct service by, for example. dialing a number provided for a mllltir~ct service.
. The message provider s call is recei-ed (line 802) at the SSP 704. The SSP 704 5~lcpe~ic the call.
3. The SSP 704 queries trle SCP 708 (line 804).
4. The SCP 708 consults the apylu~liale CP}? 710 (e.g., either generic or user-specific), which ins~ructs the IP 706 to illlt.,_e-dc (line 806).
5. The IP 706 plavs an ~ o~nre~ such as "Enter ~estin~tion 1l.l.ll~,~ and message" (line 808).
6. The message provider enters the mPce~ge~ ,iyie~ll address list (or refers to an existing list in the CPR), and other ~ d infol.llalion in an at,y.uy-iaIe manner (line 810).
7. The IP 706 stores the message and places calls to the inrlir~t~ local Ic~
(line 812). At the same time, the local IP 706 dials a special number to conuct either the remote IP 720 or remote SCP 722 in order to establish a tmnk line b~.-. en the m~sC~ge provider's SSP 704 and the remote SSP 724.
8. The local IP's call is handed over to the remote SCP 722 (line 814) and then to the remote IP 7~0 (line 816).
9. The local and remote IPs 706. 720 e~cl~nge m~osc~gçs over the trunk 728 using voice-band modemc. and release the trunk (line 818).
10. The local and remote ~Ciyie~ 7 receive the message (lines 820, 822).
This &~ e 700 does not use the SS7 ne~woll~ to transmit the m-~Ssage. Rather, the archir~c~ e uses the switched comml~ni~tiorlC nelwulk L~ lg fa~iliti~5 (e.g., trunk line 728) to deliver the ml~Cca~e between remote SSPs. Once the local IP 706 has collected the user m~Sc~ge and desrin~tinn numbers. as before it contacts a remote IP 720 for more efr,cient 30 deliverv. The IP makes a regular "POTS" (plain old tclel)hone service) call to a special number.
The special number is served by an SSP 7'2 near the remote IP. The dialed number triggers the message provider's SSP 704, which s~spen~s the call. and queries the messag~e provider s SCP 708 for instructions. The SCP 708 ins~ructs ~he remote IP 720 to intercede. The local and Wo 97/44924 PCT/US97/08229 remote IPs 706, 7'0 exril~n~e the desired inf~ ,.ation over the voice trunk (i.e.. using voice-band mr~emC). rhe mPCc~e provider's IP ~04 delivers the mPCcaEe to the remote ~ecip,~
via the voice trunk 726.
Fig. 9 is a fourth t,-Cl~ d co....~ ions network a~ c(~c 900 according to the 5 presem invention- This embodiment provides ~irqrPA colllyon~ 5 called service nodes to handle the multir-q-ct capability. rhese service nodes may be connec~ed to commllnirq~ionc network co,uyon.,.-La and may be co~ ctcd to each other by a data r....wu.k. The al~ e 900 inrhldPs a sending comml~nir~tions l~Prrnin~ 902. a sending SSP 904 com~ccted ~o the sending co,...."mir~tions terrninal, a network server 906 such as an IP, a local service node 908 Co~ to the local IP. a network ~qtqhqc~ 910 such as an SCP, a CPR 912 inc~qlled in the r,.lwO-~ ~qtqhqce, si~n~lin~ transfer point 914, local SSPs 916, and local l~iyiC~lL terminals 918.
The service node 908 is preferably a d~tq~ qce cont~ininV m--ltirqst information, such as ~iiall ilnllion lists, tclet,honc numbers, facsimile ~ bc..~.. and e-alail addresses, billing 15 infoll,.hIion. and the like. The service node may be a co".yu~cr (such as an off-the-shelf PC) or other cQrnml~nir~tionC network serving device. The co"....~m;~ ~rions network 900 also inrltld~s a data neLwo,l~ 920. such as a private data n~..wo.L~. a public data nelwork (e.g., the Internet), or a number of leased lines. The data ne.w~ c 920 connects to a remote service node 922, a remote nc.~oll~ server 924, such as an IP, remote SSPs 926. and I~Ci 20 comm~nirq~ions terminals 928.
Fig. 10 is a ca}l flow 1000 which may be used with the architeemre of Fig. 9. The call flow mav be modifiPd in a manner well known to those skilled in the art to deliver fax. data.
video. or other type of commllnirqtions. as well. A mnltir-qct tr~ncmicsion of a single ~.,essa~c preferably occurs in the following manner.
1. The .,~ Ee provider calls the mnltirqc~ service by, for exarnple. dialing a D~nber provided for a m~~ltirqct service. This number may connect the myccq~e provider to the service node 908 (line 1002).
2. The service node plays an q~ Im-~ l.F l~ such as "Enter destinqtion llwll~c~a and messa~e" (line 1004).
3. The mPss~e provider enters Lhe l.. Cs~ee~ l~.Ci~i~.. lL address list, and other reqlJPsted il~lllla~ion in an a~l..ul,liate manner ~line 1006).
4. The service node 908 stores ~he rnPcc~e and 5im-~ltqn~oucly places calls to the intlirqtP~ local leci~iel1t~ via lhe IP 906 (line 1008).

wo 97/44924 PCTIUS97/08229 At the s~ne ~ime. the local senice node 908 contacts a remo~e service node 922 via a data n~.wull~ 920 (line 1010). The service nodes 908, 922 e~ nDe user message and destinqrion h~"l~ ion.
6. The local and remote .cci~ receive ~he message (lines 1012. 1014). If the rnescqve is a voice or fax mPc~qge, it is delivered over ordinary tcle~honc lincs.
- Data m~ccqv~s may be delivered over data nelworks, such as the IMerneI.
This al~ ct~.c is an "open" impl~ At jo~. This is because the primary service logic and funclionality do not reside in the co,~ ;rA~~on~ r,e~w~ el~ . but in service nodcs 908. 922 col.l.F~ to the IPs 906, 924- An advantage of this archioecture 900 is low entry 10 cost, because the service node hardware may be low-cos~ off-the-shelf PCs. This avoids the ~ime and e~pence of r~lu~lA~ inD each of the exisling r,~,wul~ IPs to handle the m~ qct capability.
Fig. 11 is an alternative archil~cntre 1100 to the a"kil~cr~ of Fig. 9. In Fig. 11. the service nodes 1102 ar directly co.",c.,te~ to SSPs 1104. The service nodes 1102 are also col",~e~rd to each other via a data nelwork 1106. The data network 1106 may be, for exasnple.
a PSTN trunk, a public data network (e.g., the Internet), or private leased lines. The service node obtaining the message provider s mllltic~ct message and address list does not commlmi~re with an IP to make calls. Instead, the m~csage is sent bc.~en service nodes. Each service node sends the mPssage to le~ Ms as o,di,~y tclepllone calls using regular telet)honc access 20 lines.
Fig. 12 is a second alternalive ar~ h;~ ,c 1200 to the a~c~ of Fig. 9. As seen in Fig. 12. the service nodes 1202 are directly CQI.. f~ d to SSPs 1204. The service nodes 1202 are also colmc~t d to each other via both a data n~.w~ 1206 and a swiu,hed co.. ~ ir~lions network 1208, such as PSTN. The service node obtaining the message provider's mlliticqC~
25 mPss~q,ge and ,eci~i~,.,L list does not CfJII~IIIIII~ jl ~l~ with an IP to make calls. Instead, the m~C~ageS
are ~,.nc-,.;l~ d-in the same manner as desc,ibed above in relation to Fig. 10. However, the lI,C~ Iist may include telephone numbers, fq,esimiie nusnbers, or e-mail addresses. Thus.
the same m--c~ge may be delivered to a first l~ci~ie.ll as a fax lr~ if!n (perhaps based on a delivery ~,efe,~.lce stored in the service node) over the PSTN and îo a second Ic~i~ier~ as an 30 e-mail over the Intcrnet.
These emboriimpntc describe preferred sl,u.;t~,~s and metho~lc for delivering a m~Csqpe to a number of ~ci~ . These embodimeMs solve the information "stq-ien~ss" problem because the ,cCipie.l~ are receiving the messa e relatively sim--l~n~u~ly. These embo~im~ntc CA 022~27~7 1998-10-28 WO 97/44924 PCTtUS97/08229 also efrlci--,lly use ne~work re~ùur-~s because a single call is made berween the ~ ge provider and the ne.wulk co~ olle-~L~- The n~,Lwo~ o~ o~ nl~ then make the callsSimlllr~n~ollciy~ rather than making them one after the other, which ties up the colllyon~,.t for a longer arnount of time.
Collc~ .g and Returnin~ Res~ ol-~s To a Ml-ltir~ct The embo~lim~nrc above do not address the efficient use of network resources ~o collec and deliver l~sponses to a m-~ltir~ct mPscage.
In some cases it may be helpful for the m~ ir~ct message provider to receive an acknowle~lv.em~n' that the mPscqve was received by the inr~n~d r~ i~ic.ll and. if not, an inriir~tion of those l~ciyier~ who did not receive the message. It may also be useful for the message provider to receive a reply to the message. Por e~ lc, a pollster may desire promptly returned responses to a suNe,v. Another example may be telemarketers who may be required to provide an option for leciyicnts to block delivery of any future tele.llar~ lg messages. Another example may be for eVeM o~iLc,~ tc- receive an RSVP to know whcther or not the leci~ t will attend the event.
This ,~ponse may be provided for any of the co~ ir~irJnc media and any alch;~ c described above. A voice m-llrir~ct mPcc~ge using the al.h;'~r~ c of Fig. 3 is desclibtd for illustration. Referring to Fig. 3, when the IP 306 begins to make the voice calls to deliver the m--ltir~ct m~ss~ve to each lc~iyie~t. the IP creates a calling record containing the phone number.
f;~cimile number. or e-mail address of each l-ci~ie.ll it calls. At some poiM in the message (preferably the end) the IP provides an ~nn~ U~C~ (for example, a voice messa_e "Press I
or sav ves to confirm that you will attend this Ill~ g'l or a text message req~sring that the click a "Yes, I will attend" or "No, I will not attend" button), and waits for the recipient's re~yonse. The response to a voice .~lPssa~e may be collected as DTMF tones from the rcCi~.~.lL'S keypad or by speech recognition using well-known t~chni~ s, and stored in the calling record ~ the lC i~ t. A text l.~onsc may be collected in the o~di~ manner.
The calling records of all the I~,ci~iC.lb may be L~luce~sed at an SCP, IP, or other n.,.wolk pluce~ g entity and letullled to the m~C~a~e provider using relatively sirnple to program software. Fig. 13 illustrates such a C.,lwu~ ucec~;llg element 1300. This element may be a single physical or logical network colllyorl~ or several n~.wulk culll,vol c.l~ u~ atill to~.h.r. The element has a ~ icnl list ~ h~ce 1302, a message ~ hac~ 1304, a message delivery system 1306, a calling record 1308, a response record 1310, a r~lJollse ylucessor 1312.
and a l~ .u.~e delivery syslem 1312.

The leciyien~ list d~t~bace 1302 receives the ,~ciyicnt addresses from the l~Pccage sender (or receives a pledefilled list from the CPR). The mPcc~ge r~ hqce 1304 receives and stores the mPc~q~e from the message provider The mPsc~e delivery system 1306 sends the stored messaee to the reciyient~ in the stored list.
The calling record 1308 m~intAinC h~ll,lation about m-oss~e delivery, such as which recipients have received the message A l-~yol~e record 1310 is corh~;led to the calling record and mainrAinc ll,~yonses received from the 1~,, iy;en~. rhe Ic~,ol~e ylucessor 1312 r~ce;~s the responses from the l~yo~e record 1310- The r~.syonse records may be p-ucesscd in any number of ways, depending on the mPss~e provider's ylef ,ence. For example, the l~.~yOl)~;~CS
may be le.~llle~ individually (i-e-, called number and "yes" or "no" I.~yolLe) or filtered to return only the ones with a certain lc~yonse (i.e.. Lhose Ic.i~ L's who pressed "1"), or a 5!A~.c~.r~l result could be returned (i.e., 98% of lcCiyi~ re~yonded with "yes").
The (~locesseO calling records can be l~uln~d to the message provider by the .~t,onse delivery system 1312 via a number of media, i.e., via fax, phone call. voice mail, e-mail. etc., 15 depending on the user plc~.~nces 5tored in the CPR. The calling records can be COIl~ tO
the ap~lo~liate mPr~ m (i.e., text. fax, or voice) using well-known tec~niq~Ps.
Although this descriplion is for a voice mpcc~ge~ yorL. ~ could also be collPr~P~ for data messages sent to l~ ' comrlJ-~rs~ if the C~ p~t~ . ~ have been loaded with ayyl~ yliate sol~w_l~ for l.,L~il~hlg such le~yonses. For e~llylc~ a sorlw~e provider may be able remotely 20 to supply its ~;u~lOlll.~a with SOfIWA-1C ~Iy~;-.ldes by downlo~iing the upgrade to the computer using a mllltir~ct llAn~.. iccion over tf l~t)h~ lines. If so ploglAl.. Pcl. the COlllyllLC~ may send a le~yonse acknowledging receipt of the upgrade.
In the case of fax or e-mail messages, the l~ciy;~ can be ir~llu.hd to respond via fax.
voice, or e-mail to a service bureau, which collects and !)lucesses the lC~yonscs and returns them 25 to the ml-ltir~ct m~C~age provider.
ApDlications For the M-~ltir~Ct Capabilit~r A key advant~ge of inte~ lg the mllltic~ct facility into exisling co....~ a~ioncn..~olk~ is that it can be combined with other r.e.wol~ farilitiP5 provided either to mPc~a~e providers or l~iyie~
D~ A Multicast Messaee To A Wireless Service St~ ,;b~l The m-litir~ct capability may be integrated with other n..wull~ funclions and s~.vices.
Referring tO Fig. 3, for example, if a l.ci~ie.ll is a wireless col~ ionS user. such as a cellular ~elephone or Personal Comrnunications Services (PCS) subsclibcr, the cullllll~ln~ ons CA 022~27~7 1998-10-28 WO 97l44924 PCT/US97tO8229 network contacts the applu~ iate d~t~h~ces to locate the wireless co~ ns user. The SCP
308 may be used to locate the subscriber and obBin the alJylo~idle routing illÇol,l,alion (UsinU
the HLR 324 and V~R 302 d~t~b~ces as described above). The wireless call is setup in the usual manner. The message is delivered to a SSP 314 co,~,e.~ed to the a~ o~,idle MSC 318.
S The MSC sends the message to a basê station 324 which brs~rir~ctc the message to thê reci~,c"l.
This may be done without setting up a separate PCS call to thal subscriber. but during the m~ ir~c~ process itself. thus reducing the call setup time for delivering the m~csq~e to that subscriber and avoiding duplication of call p,~cec~...-J.
I.-t. ~. dLi..~i Multicast With Pe.~ù.lal T o~ti~r~ S~
The m~ ir~ct capability can be illL~gldt.d with other advanced m~C~aein~ services. For example. the mllltir~ct service can be used in conj,~ ion with Bellcore's iJ~ul~lie~y "Personal Location Service". disclosed in U.S. Patent Application Serial No. 081578 879 filed on Decesnher ~2 1995. The contents of that patent application are inco,~o,dtcd herein by refc.~nce. Personal Location Service (PLS) is a value added personal location service for wi,~less co,.. ~ r~rions system customers. PLS uses existing i,~",.a~ion in a wireless comm~lnir~tion inrlds~ cture to identify the cell or registration area in which a mobile terrninal is curreMly located. In one example of the invention a vehicle fleet is equipped with wireless trrrnin~lc A query plucessor connected to the wireless CQI---~ nrinn network receives a fleet iicp~trhlor query. The query processor co~ n;~ S with existing co .,...---~ t;rJnC n~ c-.o"~
20 components and ri~r~h~ceC such as ~he HLR or VIR~ to dcte..l.inL the location of the ,e~,f ,l~ d vehicle or person. Quenes may be customized to suit a particular c~lctom~r s unique needs such as localing a particular terminal. all terminals in a particular area. all terminals acso~ d with one or more particular a~ributes. or a combination of the above.
IMc~ldtillg ml~ltir~ct capability with PLS allows the same rn~cc~ge sim~ nF~n~ciy to be 5 sent to the selected subset of wireless terminals inct~iled in vehicles by c..~~ g the message once. and th~n ~yeciivulg the subset of terminals to be co~t~rt-~d based on their location and attributes as desc.ibed above.
T~ P Ml~lffr~Ct With P~.su-~al COITI..~ ..t~
The ml~ltir~ct capability can be used in conjunction with Bellcore's ~Iul li.taly Personal 30 Co~ -r~ns 1IIL~ WOII~mg (PCI). PCI is tlicclQsed in U.S. Patent Application Serial Number 08/309.336 filed on September 19~ 1994. The contentc of that patent applica~ion are inco,yoldud herein by ,~fc.ence. PCI provides a networlc subsc,ibcl with the ability ~o remotelv control the receipt and delivery ot wireless and wireline voice and text messages. The CA 022~27~7 1998-10-28 ne.wolk ope.~s as an interface b.,.~._en various wileless and wileli,.e n~,wul~, and also pc,lb~ s media translation, where l1~C~CC- ~. The sub~-_,i~.'s m~s~ge receipt and delivery options are m~int~in-~ri in a ~Iq-~h~CP which the sul,scliber may access by wheless or wilclil~c cU~ ni~tionc to update the options ~ .. rri in the ri~t~h~c~.
S If a l~ipi~.lt of a ml-ltic~ct m~scq~e is a PCS sul,~-,.ii,e., the m~C~age may be routed to the approy-iate phone number or mailbox ~ if-d in the PCI subsclil,e,'s profile. This is preferably done during ~Iu~ of the mllltir~ct message to avoid duplicate call ~ )cr"~g.
This is, if the reci~ic~lt list inriir~t~s that a lccitJ,.nL is a PCI ~ub~clibe" the IP will consult the rCCil~iC.ll'S profile to dcb .~ m~sca~e routing pr, f..~.,.es before placing the call to the I..tf~. t; ~ Multicast With "Do Not Disturb" Call Rlru~kir~
A l~ .ll may have a col.~ .nn~ n.,lwolk service which blocks i~ .;ng phone calls at certain times (say, from 10 pm to 6 am). If ml~itir~ct is not hllc~lat~d with this "Do Not Distnrb" n.,.w~ rk service, a voice call to the r.,~ during those hours will be blocked and 15 the 1~,~.4)i~.1L will not receive the ~ .s1g.. l'he m~-ss~ge provider then has the option of abandoning the call or periodically re-calling the rc.,i~ (in the conventional manner) ulltil thc call goes through.
This may be avoided by h~te~latillg m~ r~ct into the "do not disturb" service. The ation stored in ll.~OIi~ dAtAhACPC (HIR, SCP, CPR) is obtained to ~ tc that the 20 r.,Ci~ .lL has a "Do Not Disturb" block acli~.,t~d, and a~t~lo~J~id~ action is taken so that the messa~e is delivered when the block is de~c~ at~d. l lis may be done in several ways. For ctrarion, the ;~p~ ;ons are ~.c.ibcd with the a,~ c~ c of Fig. 3. It is a~Jp..lem to those skilled in the art that these impl~ ;onc may be used with the other a"hi~ n~ s.
In a first ~nr~ Al;o~1, when the ~ s~g_ provider lc~ue~la a message to be sent to a particular list of rc.,i~;.,.lta' addresses, the SCP 308 checks its ~15lAh~cP to see if any of the r~,Cipi~,n~a' "'~ P5 ha a "Do Not Disturb" block on ~;u~l~ly (or at the time the ~r~3c is to be delivered, if different). If so, for each such address, the SCP crcates a "future delivery record" co~lA;ni~e the number, the time at which the block will be de&~;liYa~Ld, and the i~ eC
to be delivered, and k~lar_~a the record tO the IP 306 to deliver the ~n- "a~., at the times listed.
In a second impl~ . "- - ~t -~ ion when a call is dcli~e~ed to the l~ ic,l~'s SSP 314 (typically .
the ~ ie~-l's SSP queries the ~ L's SCP -- not seen in Fig. 3 for the "Do Not Dis~urb"
~ ~n~llinv inswctions), the l~cipie.lt's SCP consults the ~ .ll's CPR and rl~ c Ihat blocking is in effect. At th;is stage. the lc.ipi~ 's SCP typically illalluL~a the l~ci~;_nl's IP to wO 97/44924 PCT/US97/08229 play a mPcc~e (i.e., "The party you are calling is not available, please call later") or to direct the message to a voice mail system. However. in this case, the SCP d~,t~ es from one of the message provider's SCP/CP~/IP that the call is originqtinSg from a ~i~Pcign~t~~~ "m~ ir~ct capable IP". Having made this dete..~ ion~ the r~ nt'S SCP either pruvides the mPcragP
5 provider's IP 306 with the time at which the block will be deactivated for later delivery, or the iyient~s IP stores the mPC~a~e and delivers it at that time.
T~ d ;--C l,~llltir~ct With "Time of Day" Call ~ lltin~
A ~ccil,ient rnay have a profile stored in a l~.J~ ;.h=~. s~ifyi,lg that at various time iMervals during the day, inro~ calls are to be routed to differeM llulllbe.a (i.e., "From 10 5 pm to 6 am, ;nrCt~lin~ calls to my office fax ...~hi..f should be directed to my home fax m~rhinP"). This may be a call fo~ lillg service or a f~.1ion t~lu~ided by Bellcore's pro~lie~y PCI service desclil,ed in Application Serial Number 08/309,336, desclib~d above.
Without hlL-,gl~tiilg the m~ ir~ct service into the cc~ ;onc l~.JIk services, a ...~55~Ve sent to that r~ i .It would first be sent to the ~ nt's tlsual number, and then -- following~5 lookup of a~luyliate ne.wolk ~ b~CPs -- be redirected to the routing number ~cirled in the ient's user's profile. This slows down the mps-cagp delivery and wastes network resources.
If mllltir~ct capability is i~ fd into the co~ nc nelwulk services, whcn amPss~ge provider ~ u~ that a mPcsagp be mnltir~st to a list of l,",l.;...lc. thc SCP 308 consults its own .1 ~h~cP tables to check if any of the l~.,ipi~ have call routing activated, and 20 if so. sn~ the le~iyi~ s usual number with the r~dil~.,~d number cp~r~ ;fird in the profile.
This saves nc-wol~ l.s~ul~eS and reduces call setup time.
Notice that several related services could be provided by this means also, e.g., to deliver an incGIllh~g tex~ mPc~age via a dirr~len~ medium (fax, pager, or s~ c;,. rl specch) or look up al.~lo~l iate r,e.wo.k ~ ~h~ S (i.e., HLR and VLR r~ ba~ s) in order to more tr~ l ly rou~e 25 the call to a ICC ~ who is using cellular or PCS co~ ;r-l;n~ This is achieved by looking at the ~ItJylo~ n~.wolk ~ h~CPs during the mllltir~ct process.
The above de~,libed embo~imPn~c of the invention are ;..~ .Irifri to be illL~ e only.
Numerous ~lt~tn~tive e.llbo~ may be devised by those skilled in the art without de~lh~g from the spirit and scope of the following claims.

to

Claims (38)

We claim:

1. A method for simultaneously transmitting a single message to a plurality of recipients, comprising the steps of:
a. providing to a communications network the message and addresses of the recipients;
b. the communications network contacting a plurality of the recipients; and c. the communications network simultaneously delivering the message to the plurality of recipients.

2. The method of claim 1, wherein the step of providing further includes the step of calling a preselected telephone number.

3. The method of claim 1, wherein the step of providing addresses further includes the step of providing a list of recipient telephone numbers.

4. The method of claim 1, wherein the step of providing addresses further includes the step of providing a list of recipient e-mail addresses.

5. The method of claim 1, wherein the step of providing addresses includes selecting an existing list stored in the communications network.

6. The method of claim 1, further including the step of storing the message after the message is provided.

7. The method of claim 6, further including, after the step of storing, the step of delaying for a time before performing the step of contacting.

8. The method of claim 1 wherein the step of contacting further comprises the steps of:
a. a local network component forwarding the message to a remote network component via a signaling network; and b. the remote network component contacting remote recipients.

9. The method of claim 1, wherein the step of contacting further comprises the steps of:
a. a local network component contacting a remote network component;
b. the local and remote network components establishing a trunk line between a message sender and a remote recipient;
c. the local network component handing over the message to the remote network component;
d. the remote network component contacting the remoter recipient.

10. The method of claim 1, wherein the message is storing in a local service node and the step of contacting further includes;
a. the local service node contacting a remote service node; and b. the remote service node contacting remote recipients.

11. The method of claim 10, wherein the step of delivering includes the remote service node delivering the message to the remote recipients.

12. The method of claim 1, wherein the message is provided in a first format, the method further comprising the step of after providing the message, converting the message into a second format, and the step of includes the message in the second format.

13. The method of claim 1, wherein the step of contacting further includes:
a. contacting a wireless communications network to obtain a location of a recipient's wireless terminal; and b. setting up a wireless communication; and the step of further includes the message over the wireless communications network.

14. The method of claim 1, further comprising after the step of the message, the steps of:
a. obtaining a response to the delivered message; and b. the response to a message provider.

15. The method of claim 14, wherein the step of obtaining the response further includes:

a. during the step of contacting, the communications network creating a calling record;
b. the step of further including the step of a response request; and c. the communications network receiving a response to the response request.

16. The method of claim 15, further comprising processing a plurality of responses.

17. The method of claim 16, further comprising transmitting the processes responses to a message provider.

18. The method of claim 1, wherein the step of providing addresses includes the step of providing the addresses of recipients located by a personal location service.

19. The method of claim 1, wherein the step of contacting further comprises the step of contacting communication network databases containing information about the recipient's call delivery preferences.

20. The method of claim 19, further comprising the step of the message according to the recipient's call delivery preferences.

21. The method of claim 1, wherein the step of contacting further includes the step of contacting a recipient's personal communications internetworking profile.

22. A communications network having a multicast capability, comprising:
a. a first network component configured to receive a message and recipient list; and b. a second network component connected to the first network component configured to receive the message and to deliver simultaneously the message to a number of recipients on the recipient list.

23. The communications network network of claim 22, wherein the first and second network components are an intelligent peripheral.

24. The communications network of claim 22, wherein the first network component includes a call processing record (CPR).

25. The communications network of claim 24, wherein the CPR is configured to receive and store the message.

26. The communications network of claim 24, wherein the CPR is configured to receive and store a recipient list.

27. The communications network of claim 22, further comprising:
a. a signalling network connected to the second network component and configured to receive the message;
b. remote network components configured to receive message from the signalling network and to deliver the message.

28. The communications network of claim 22, further comprising:
a. a local switch configured to receive the message;
b. a signalling network connected to the local switch and the second network component;
c. a remote network component connected to the signalling network and configured to communicate with the second network component to set up a message delivery trunk line;
d. a remote switch connected to receive the message from the voice delivery trunk line and to deliver the message; and e. the message delivery trunk line connected between the local and remote switches.

29. The communications network of claim 22, wherein the first and second network components are a first service node.

30. The communications network of claim 29 further including:
a. a data network connected to receive the message from the first service node; and b. a second service node connected to receive the message from the data network and to deliver the message to remote recipients.

31. The communications network of claim 30, further including a switched communications network connected between the first and second service nodes.

32. The communications network of claim 29, wherein the service node is a computer.

33. The communications network of claim 22, wherein the second network component is configured to receive a response to the message from recipients.

34. A network component for a communications network having multicast capability, the component comprising:
a. a first database configured to receive and store a recipient address list; and b. a second database configured to receive and store a message and to connect simultaneously the message to a number of communications lines for delivery to a plurality of addresses on the recipient address list.

35. The network component of claim 34, further comprising a calling record containing information regarding delivery of the message.

36. The network component of claim 35, wherein the calling record further includes a response record indicating a response to the message.

37. The network component of claim 36, wherein the component further includes a response processor configured to process response to the message.

38. The network component of claim 37, wherein the response processor is configured to transmit the processed responses to a message provider.