throbber
USOO7907714B2
`
`(12) Umted States Patent
`Baniak et a].
`
`(10) Patent N0.:
`(45) Date of Patent:
`
`US 7,907,714 B2
`*Mar. 15, 2011
`
`(54) PROFILE MANAGEMENT SYSTEM
`INCLUDING USER INTERFACE FOR
`ACCESSING AND MAINTAINING PROFILE
`DATA 0F USER SUBSCRIBED TELEPHONY
`SERVICES
`
`(75) Inventors: Paul G. Baniak, St. Louis, MO (U S);
`Kristin Chambers, Austin, TX (US);
`Katherine L. Krein, St. Louis, MO
`(US); Christopher H. Rolwes, St. Louis,
`MO (US); Terry L. Vieth, St. Louis, MO
`(US); Tracy L. Brokaw, St. Louis, MO
`(US); Mary B. Clark, St. Louis, MO
`(Us)
`
`_
`_
`(73) Ass1gnee: AT&T Labs, Inc., Aust1n, TX (US)
`
`( * ) Notice:
`
`Subject to any disclaimer, the term of this
`patent is extended or adjusted under 35
`U.S.C. 154 b b 1271 da .
`( ) y
`ys
`This Pawnt is SUbleCt to a terminal (115'
`cla1mer.
`
`(21) Appl.No.: 11/459,121
`
`(22) Filed:
`
`Jul. 21, 2006
`
`(65)
`
`Prior Publication Data
`
`Us 2007/0047714 A1
`
`Mar' 1’ 2007
`
`Related U.S. Application Data
`
`(63) Continuation of application No. 10/761,382, ?led on
`Jan. 22, 2004, now Pat. No. 7,103,165, and a
`continuation of application No. 09/050,986, ?led on
`Mar. 31, 1998, now abandoned.
`.
`-
`-
`-
`(60) Provmonal apphcanon NO' 60/042’680’ ?led on Apr'
`3’ 1997'
`(51) Int_ CL
`(200601)
`H0 4 M 3/42
`379/201 02_ 379/207 13
`(52) U 5 Cl
`(58) Field of Classi?cation Search ........... .. 379/201.01,
`379/201.02, 201.12, 207.13
`See application ?le for complete search history.
`
`(56)
`
`References Cited
`
`U .S. PATENT DOCUMENTS
`4,296,463 A 10/1981 Dalboussiere et al.
`.
`(Cont1nued)
`
`EP
`
`FOREIGN PATENT DOCUMENTS
`0 740480
`10/1996
`(Continued)
`
`OTHER PUBLICATIONS
`“MegaHub PACE SMS-Service Management SystemiAdvanced
`Intelligent Network Systems,” Communications Corporation, Issue
`0,4,1u1‘ 17, 1994‘
`
`(Continued)
`
`Primary Examiner * William J Deane
`(74) Attorney, Agent, or Firm * Greenblum & Bernstein,
`PLO
`
`(57)
`
`ABSTRACT
`_
`_
`_
`_
`_
`Subscrlber pro?le data assoc1ated W1th a commumcatlons
`service subscribed to by a subscriber is managed by a pro?le
`management system. The subscriber pro?le data is stored on
`a communications network which executes the communica
`tions service in accordance with the subscriber pro?le data. A
`subscriber request to view the subscriber pro?le data is
`received from a client which hosts a user interface con?gured
`to allow the subscriber to view and update the subscriber
`pro?le data. The subscriber pro?le data is retrieved from the
`communications network based upon receiving the sub
`scriber request to view the subscriber pro?le data from the
`client. The subscriber pro?le data is forwarded to the client. A
`subscriber request to update the subscriber pro?le data is
`received from the client. An update for the subscriber pro?le
`data is forwarded to the communications network based upon
`receiving the subscriber request to update the subscriber pro
`?le data from the Chem
`
`22 Claims, 8 Drawing Sheets
`
`Posilivc 1]) (P03) Sofwnlc
`
`'
`
`IOL
`
`'r,
`
`‘
`
`So?wnn:
`
`10*
`
`,'_ T T T T T n} a:
`1
`:
`K
`PCIQZDWCI <
`QuefyMSScrvel
`:
`\ 120m
`
`|
`'
`
`n—v
`
`Um
`QPPLE
`
`a
`
`“"1
`
`M
`
`r
`
`PlD
`Slihli Server
`
`I26
`
`4
`
`cm“
`
`)-
`
`no
`
`PlD
`Dambasc
`
`131:
`
`ND
`Admin Tool
`
`Suppori Person
`
`AT&T Exhibit 1021
`AT&T v. VoIP, IPR 2017-01384
`Page 1
`
`

`

`US. PATENT DOCUMENTS
`1/1984
`4,429,188
`Allen
`9/1986
`4,611,094
`Asmuth et al.
`9/1986
`4,611,096
`Asmuth et al.
`11/1988
`4,788,718
`McNabb et al.
`Costello
`8/1989
`4,860,347
`4,878,240
`10/1989
`Lin et al.
`Majmudar et al.
`4,897,866
`1/1990
`4,899,373
`2/1990
`Lee et al.
`5,054,055
`10/1991
`Hanle et al.
`Greenspan et al.
`5,109,408
`4/1992
`5,200,995
`4/1993
`Gaukel et al.
`5,222,125
`6/1993
`Creswell et al.
`5,241,588
`8/1993
`Babson, III et al.
`Kay et al.
`5,247,571
`9/1993
`5,294,229
`3/1994
`Hartzell et al.
`5,333,185
`7/1994
`Burke et al.
`5,337,351
`8/1994
`Manabe et al.
`5,345,380
`9/1994
`Babson, III et al.
`Emery et al.
`5,353,331
`10/1994
`5,396,546
`Remillard
`3/1995
`5,398,220
`Barker
`3/1995
`5,404,396
`4/1995
`Brennan
`5,436,957
`McConnell
`7/1995
`5,438,568
`8/1995
`Weisser, Jr.
`5,444,768
`8/1995
`Lemaire et al.
`5,448,631
`Cain
`9/1995
`5,463,682
`10/1995
`Fisher et al.
`5,467,388
`11/1995
`Redd, Jr. et al.
`5,469,500
`11/1995
`Satter et al.
`5,479,487
`Hammond
`12/1995
`5,533,102
`7/1996
`Robinson et al.
`5,544,320
`Konrad
`8/1996
`5,548,566
`Barker
`8/1996
`5,550,909
`8/1996
`Chanda et al.
`5,572,583
`11/1996
`Wheeler, Jr. et al.
`Seymour
`5,579,384
`11/1996
`5,583,564
`12/1996
`Rao et al.
`5,592,541
`1/1997
`Fleischer, III et al.
`5,615,252
`3/1997
`Sizer, II et al.
`5,625,676
`4/1997
`Greco et al.
`5,629,978
`5/1997
`Blumhardt et al.
`5,642,410
`6/1997
`Walsh et al.
`5,655,013
`Gainsboro
`8/1997
`5,657,451
`Khello
`8/1997
`5,680,446
`10/1997
`Fleischer, III et al.
`5,687,212
`11/1997
`Kinser, Jr. et al.
`Smyk
`5,696,815
`12/1997
`5,740,438
`4/1998
`Ratcliff et al.
`5,742,668
`Pepe et al.
`4/1998
`5,751,707
`5/1998
`Voit et al.
`Bayless et al.
`5,754,636
`5/1998
`5,758,351
`5/1998
`Gibson et al.
`5,764,748
`6/1998
`Rosenthal et al.
`Reilly
`5,787,237
`7/1998
`5,790,173
`8/1998
`Strauss et al.
`5,796,806
`Birckbichler
`8/1998
`Sips et al.
`5,796,950
`8/1998
`5,799,073
`8/1998
`Fleischer, III et al.
`5,802,157
`9/1998
`Clarke et al.
`5,802,159
`9/1998
`Smolentzov et al.
`5,805,587
`9/1998
`Norris et al.
`5,822,419
`10/1998
`Enstone et al.
`5,864,613
`Flood
`1/1999
`5,867,562
`Scherer
`2/1999
`5,870,549
`2/1999
`Bobo, II
`5,881,144
`3/1999
`Havens
`5,892,822
`4/1999
`Gottlieb et al.
`5,915,008
`Dulman
`6/1999
`5,917,817
`6/1999
`Dunn et al.
`5,920,618
`7/1999
`Fleischer, III et al.
`5,933,490
`8/1999
`White et al.
`5,933,778
`8/1999
`Buhrmann et al.
`5,937,050
`8/1999
`Yue et al.
`5,940,488
`8/1999
`DeGrazia et al.
`5,946,381
`8/1999
`Danne et al.
`5,958,016
`Chang et al.
`9/1999
`5,982,774
`11/1999
`Foladare et al.
`5,982,870
`11/1999
`Pershan et al.
`
`US 7,907,714 B2
`Page 2
`
`5,999,611 A 12/1999 Tatchell et al.
`6,028,917 A
`2/2000 Creamer et al.
`6,032,184 A
`2/2000 Cogger et al.
`6,038,296 A
`3/2000 Brunson et al.
`6,058,175 A
`5/2000 Schultz
`6,058,178 A
`5/2000 McKendry et al.
`6,097,802 A
`8/2000 Fleischer, III et al.
`6,104,799 A
`8/2000 Jain et al.
`6,115,040 A
`9/2000 Bladow et al.
`6,118,780 A
`9/2000 Dunn et al.
`6,125,126 A
`9/2000 Hallenstal
`6,134,310 A 10/2000 Swan et al.
`6,160,877 A 12/2000 Tatchell et al.
`6,161,128 A 12/2000 Smyk
`6,167,122 A 12/2000 Titmuss et al.
`6,173,437 B1
`1/2001 Polcyn
`6,192,118 B1
`2/2001 Bayless et al.
`6,195,678 B1
`2/2001 Komuro
`6,195,697 B1
`2/2001 Bowman-Amuah
`6,212,561 B1
`4/2001 Sitaraman et al.
`6,233,330 B1
`5/2001 McClure et al.
`6,240,441 B1
`5/2001 Beckett et al.
`6,246,751 B1
`6/2001 Bergl et al.
`6,246,756 B1
`6/2001 Borland et al.
`6,259,449 B1
`7/2001 Saxena et al.
`6,263,064 B1
`7/2001 O’Neal et al.
`6,317,484 B1
`11/2001 McAllister
`6,320,948 B1
`11/2001 Heilmann et al.
`6,330,598 B1
`12/2001 Beckwith et al.
`6,337,899 B1
`1/2002 Alcendor et al.
`6,445,694 B1
`9/2002 Swartz
`6,463,145 B1
`10/2002 O’Neal et al.
`6,529,596 B1
`3/2003 Asprey et al.
`6,574,661 B1
`6/2003 Delano et al.
`6,631,186 B1
`10/2003 Adams et al.
`6,631,416 B2 10/2003 Bendinelli et al.
`6,640,239 B1
`10/2003 Gidwani
`6,662,221 B1
`12/2003 Gonda et al.
`6,678,827 B1
`1/2004 Rothermel et al.
`6,748,439 B1
`6/2004 Monachello et al.
`2001/0048738 A1 12/2001 Baniak et al.
`2001/0049737 A1 12/2001 Carolan et al.
`2002/0054587 A1
`5/2002 Baker et al.
`2002/0168055 A1 11/2002 Crockett et al.
`2003/0007621 A1
`1/2003 Graves
`2003/0076941 A1
`4/2003 Books et al.
`2003/0079028 A1
`4/2003 Kortum et al.
`2003/0161459 A1
`8/2003 Book et al.
`2003/0200321 A1 10/2003 Chen et al.
`2004/0199624 A1 10/2004 Poisson et al.
`2004/ 0243708 A1 12/2004 Stebbings
`2005/0114794 A1
`5/2005 Grimes et al.
`
`WO
`WO
`WO
`WO
`WO
`
`FOREIGN PATENT DOCUMENTS
`92/09164
`5/1992
`99/16230
`4/1999
`99/20058
`4/1999
`00/65857
`11/2000
`01/35240
`5/2001
`
`OTHER PUBLICATIONS
`
`Berman, Roger K., and Brewster, John H., “Perspectives on the AIN
`Architecture,” IEEE Communications Magazine, Feb. 1992, pp.
`27-32.
`Advanced Intelligent Network (AIN) 0 .1 Switching Systems Generic
`Requirements (Bellcore TR-NWT-001284), Issue 1, Aug. 1992.
`Advanced Intelligent Network (AIN) 0.1 Switch-Service Control
`Point (SCP) Application Protocol Interface Generic Requirements
`(Bellcore TR-NWT-001285), Issue 1, Aug. 1992.
`BT Technology Journal, vol. 13, No. 2. Apr. 1995, Ipswich GB. pp.
`132-142, Marshall et al., “The information services supermarket”.
`Internet web pages by Dazil Internet Services, “Caller EyeDee,”
`downloaded Dec. 2001.
`Internet Web Pages by Z-Tel, “Personal Communications Center”,
`dated Apr. 13, 2000 and May 15, 2000.
`
`AT&T Exhibit 1021
`AT&T v. VoIP, IPR 2017-01384
`Page 2
`
`

`

`US 7,907,714 B2
`Page 3
`
`Internet Web Pages by TOSC International, “Cool Call”, dated May
`4, 2000.
`Internet Web Pages by Phone.Com, “My Phone Services”, dated May
`4, 2000.
`Lennox et al., “Call processing Language Framework and Require
`ments”, RFC 2824, published May 2000.
`Lennox et al., “CPL: A Language for User Control of Internet Tele
`phony Services”, Internet Engineering Task Force, IPTEL WG, pub
`lished Oct. 25, 2000.
`J. Rosenberg, “Introduction to CPL”, Dynamicsoft, Winter 2001 Von
`Developers Conference, published Feb. 25, 2001.
`
`“Next Generation Phone System”, Internet web pages by CommWeb.
`com, Aug. 2, 2001.
`“Teleglobe International Toll Free Services,” www.teleglobe.com
`(Dec. 2002).
`“Sprint Wholesale Toll-Free Services,” http://www.sprintbiZ.com/
`wholesale/products/tollifreeiservices.pdf (Jan. 2001).
`An article by Kramer, T., “Standalone Call Accounting: The Hard
`ware, the Software, and the Enterprise”, Communications Conver
`gence, Mar. 5, 2001, downloaded from http://www.cconvergence.
`com. shared/article/showArticlejhtml?articled:87 1 1796&pgno:1
`on Jun. 12, 2004.
`
`AT&T Exhibit 1021
`AT&T v. VoIP, IPR 2017-01384
`Page 3
`
`

`

`US. Patent
`
`Mar. 15, 2011
`
`Sheet 1 0f8
`
`US 7,907,714 B2
`
`(
`
`DRS
`2‘3
`
`SCP
`56
`
`1'
`
`'
`
`L1,. as
`
`l'
`
`MP
`

`
`\
`
`10
`
`1
`
`ST?
`59
`
`,"
`as
`1“ //
`
`\\
`88
`\~\
`\\5
`
`ST.“
`51
`
`ST}:
`53
`
`m In
`
`FIG1 1
`(PRzOR ART)
`
`AT&T Exhibit 1021
`AT&T v. VoIP, IPR 2017-01384
`Page 4
`
`

`

`US. Patent
`
`Mar. 15, 2011
`
`Sheet 2 0f 8
`
`US 7,907,714 B2
`
`WE
`
`6%,in 0%
`
`P TQM.
`
`1% A
`min}.me
`
`25.2% 65 9 2:5
`
`A9 \.,
`L,
`
`Ea
`
`EEG Um
`
`X To;
`
`a _
`
`QUE
`
`520m Um
`
`$9
`
`k
`
`DE
`
`62am
`“25m
`
`AT&T Exhibit 1021
`AT&T v. VoIP, IPR 2017-01384
`Page 5
`
`

`

`US. Patent
`
`Mar. 15, 2011
`
`Sheet 3 0f 8
`
`US 7,907,714 B2
`
`m ix ,5 \
`.6, 1W a a2
`
`025% 55 a 2&5
`
`26:0 UL
`
`m .l I. l l I“ TO- 0 +051
`“Krishna
`Stow
`buzO ? Siam. Um
`2% 1 Y Em
`
`_
`
`_ .1
`
`. m
`
`_
`
`q
`
`_ R
`
`1;
`320m
`umO _ Baum
`?z?m
`mEm ? DE
`
`“ _ M
`
`3
`
`¥ IF
`
`\ QE
`
`\ 0;
`3.55.5
`
`v.1
`
`0:
`
`m 05
`
`OE
`
`30% 5 Ev<
`
`52.5
`:0ng
`
`AT&T Exhibit 1021
`AT&T v. VoIP, IPR 2017-01384
`Page 6
`
`

`

`US. Patent
`
`Mar. 15, 2011
`
`Sheet 4 0f 8
`
`US 7,907,714 B2
`
`CNA
`
`ECRS
`14
`
`Y
`
`EASE
`26
`
`SORD
`18
`
`SOAC
`20
`
`F164
`
`BOSS
`4O
`
`...___
`
`GUI 42
`
`CRiS/
`CABS
`26
`
`AIN-IP
`28
`
`I
`
`SPQICE
`
`18C?
`30
`
`STP
`34
`
`+
`
`SMS
`204
`
`/ v
`PC Sewer
`104
`&
`Status
`Server 106
`inn-T.—
`Y
`
`PC Client
`102
`
`MARCH
`22
`
`SSF’
`36
`
`AT&T Exhibit 1021
`AT&T v. VoIP, IPR 2017-01384
`Page 7
`
`

`

`US. Patent
`
`Mar. 15, 2011
`
`Sheet 5 0f 8
`
`US 7,907,714 B2
`
`mEm
`
`meEmz
`(mm/q
`mn=>>
`
`m .GE
`
`GE
`
`The;
`EEG UL
`
`awm
`
`mm
`
`..5132
`
`mm
`
`.HU
`
`DE
`
`62mm 255
`T33
`
`C55 2%
`
`T23 $225
`
`AT&T Exhibit 1021
`AT&T v. VoIP, IPR 2017-01384
`Page 8
`
`

`

`US. Patent
`
`Mar. 15, 2011
`
`Sheet 6 0f8
`
`US 7,907,714 B2
`
`$16.6
`
`v1511-. Ina“ W“ n.
`;
`1» -» 7
`
`.
`
`17mg"
`
`AT&T Exhibit 1021
`AT&T v. VoIP, IPR 2017-01384
`Page 9
`
`

`

`US. Patent
`
`Mar. 15, 2011
`
`Sheet 7 0f8
`
`US 7,907,714 B2
`
`Cm»?
`
`_( (314) E9349 _
`‘ K
`I
`U} 255-5553
`'Slrmklm, K
`(31 1) sin-3450
`.Emkwu, Ste-re
`
`£3141
`
`{Scam John
`
`Elm! Hm:
`“1 1! Has
`1
`
`bruner
`
`:lnfqrmqn?n Sam“;
`
`A
`
`?ee. Juhn (cumnctor)___________ _
`
`AT&T Exhibit 1021
`AT&T v. VoIP, IPR 2017-01384
`Page 10
`
`

`

`US. Patent
`
`Mar. 15, 2011
`
`Sheet 8 0f 8
`
`US 7,907,714 B2
`
`‘ :?dwmw.
`u< mm "SESQ %
`“Ema
`gauutm
`QECDEQ
`
`E€w
`
`02525 mam BE: 8
`“v.8
`.WQMSH 8.2 922 @an
`.Emg? “E :20. if? 95
`mfwm
`
`% mm:
`3258
`gag B“:
`.82:
`0832 $5 $302
`.03:
`302896
`33% 35% E: .32 OE 2% QSWWSQE
`25:3
`3: @QQW
`
`mini
`wag $2 .35. OE 6% 88-2w $5 Ema:
`
`0me .3E EHS¢
`82-5 Q a a $62
`
`AT&T Exhibit 1021
`AT&T v. VoIP, IPR 2017-01384
`Page 11
`
`

`

`US 7,907,714 B2
`
`1
`PROFILE MANAGEMENT SYSTEM
`INCLUDING USER INTERFACE FOR
`ACCESSING AND MAINTAINING PROFILE
`DATA OF USER SUBSCRIBED TELEPHONY
`SERVICES
`
`CROSS-REFERENCE TO RELATED
`APPLICATIONS
`
`The present application is a continuation application of
`pending US. patent application Ser. No. 10/761,382, ?led on
`Jan. 22, 2004, which is a continuation of US. patent applica
`tion Ser. No. 09/050,986, ?led on Mar. 31, 1998, which
`claims the bene?t of US. provisional Patent Application No.
`60/042,680, ?led Apr. 3, 1997, entitled “Pro?le Management
`System Including User Interface forAccessing and Maintain
`ing Pro?le Data of User Subscribed Telephony Services”, in
`the names of Baniak et al., the disclosures of which are
`expressly incorporated herein by reference in their entireties.
`This is also related to the disclosure provided in US. patent
`application Ser. No. 08/831,892, ?led Apr. 3, 1997, entitled
`“Apparatus and Method for Facilitating Service Management
`of Communications Services in a Communications Net
`work”, in the names of Larry JOST et al., the disclosure of
`which is expressly incorporated herein by reference in its
`entirety.
`
`BACKGROUND OF THE INVENTION
`
`1. Field of the Invention
`The present invention generally relates to the ?eld of tele
`communications. More particularly, the present invention
`relates to a user interface, such as a personal computer (PC)
`interface, for accessing and maintaining pro?le data of a
`user’s subscribed telephony service.
`2. Acronyms
`The written description provided herein contains acronyms
`which refer to various telecommunications services, compo
`nents and techniques, as well as features relating to the
`present invention. Although some of these acronyms are
`known, use of these acronyms is not strictly standardized in
`the art. For purposes of the written description herein, acro
`nyms will be de?ned as follows:
`Advanced Intelligent Network (AIN)
`Computer Access Restriction (CAR)
`Common Channel Signaling (CCS)
`Central Of?ce (CO)
`Calling Party Number (CPN)
`Call Processing Record (CPR)
`Data and Reporting System (DRS)
`Integrated Service Control Point (ISCP)
`Interactive Voice Response (IVR)
`Local Area Network (LAN)
`Personal Computer (PC)
`Positive ID (PID)
`Private Branch Exchange (PBX)
`Service Creation Environment (SCE)
`Service Control Point (SCP)
`Service Order Assignment Control (SOAC)
`Service Management System (SMS)
`Service Provisioning And Creation Environment (SPACE)
`Service Switching Point (SSP)
`Signaling Transfer Point (STP)
`Transaction Capabilities Applications Part (TCAP)
`Transmission Control Protocol/ Internet Protocol (TCP/IP)
`User Interface (UI)
`Wide Area Network (WAN)
`Working Telephone Number (WTN)
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`2
`3. Background Information
`In recent years, a number of new telephony service features
`have been implemented and provided by an Advanced Intel
`ligent Network (AIN). The AIN evolved out of a need to
`increase the capabilities of the existing telephone network
`architecture and meet the growing needs of telephony cus
`tomers. The AIN architecture generally comprises two net
`works, a data messaging network and a trunked communica
`tions network. The trunked communications network handles
`voice and data communications between dispersed network
`locations, whereas the data messaging network is provided
`for controlling operations of the trunked communications
`network.
`An illustration of the basic components of anAIN network
`environment is shown in FIG. 1. The AIN network is provided
`to facilitate communication between a plurality of network
`locations or stations 72-86.As shown in FIG. 1, central of?ces
`(COs) 64-71 are provided for sending and receiving data
`messages from a service control point (SCP) 56 via one or
`more signaling transfer points (STPs) 51, 53 and 59. The data
`messages are communicated to and from the COs 64-71 and
`the SCP 56 along a common channel signaling (CCS) net
`work 88. Each CO 64-71 serves as a network service switch
`ing point (SSP) and may be equipped with CCS capabilities,
`which provides for the two-way communication of data mes
`sages between each SSP and the SCP 56 via CCS network 88.
`These data messages may be formatted in accordance with
`Transaction Capabilities Applications Protocol (TCAP).
`Each CO 64-71 serving as a network SSP routes AIN
`service related telephone calls between a calling station (e. g.,
`station 72) and a called station (e.g., station 84) based on
`instructions received from the SCP 56. The SSPs 64-71 may
`be connected by trunked communication lines 90 to transport
`voice and/or data signals. Each of the stations 72-86 is con
`nected to one or more SSPs 64-71 through private or dedi
`cated telephone lines 93. In AIN-type call processing, the
`originating SSP is responsible for: identifying calls associ
`ated with AIN services; detecting when conditions for AIN
`service involvement are met; formulating service requests or
`queries to the SCP 56 for call processing instructions; and
`responding to the instructions or message responses received
`from the SCP 56 to complete or terminate the call.
`In FIG. 1, the SCP 56 is implemented as part of an inte
`grated service control point (ISCP) 10. The ISCP 10 is an
`integrated system which may include a programmable SCP
`56 and a data and reporting system (DRS) 28. The SCP 56
`executes software or programmed-based logic, in accordance
`with a subscriber’s call processing record (CPR), and returns
`call routing instructions to the SSPs. The DRS 28 compiles
`calling information to be used for billing and administrative
`purposes. A service creation environment (SCE) (not shown)
`may also be provided for programming and provisioning the
`CPRs stored in the database of the SCP 56. The CPRs de?ne
`the services for each individual subscriber. The SCE may be
`integrated with the ISCP 10 or provided as a separate appli
`cation or entity. By way of a non-limiting example, the ISCP
`10 may be implemented with a Bellcore integrated service
`control point (ISCP) available from Bell Communications
`Research (Bellcore), Murray Hill, N.J., and the SCE may be
`implemented with SPACE, which is also available from
`Bellcore. SPACE is a service provisioning and creation envi
`ronment. SPACE stores a copy of the data in the ISCP and is
`the network element used for data queries and management
`by the selected users which have access to it. The users do not
`access the ISCP directly because direct access would inter
`fere with call processing by performing data manipulations
`on the same platform. Updates made through SPACE are
`
`AT&T Exhibit 1021
`AT&T v. VoIP, IPR 2017-01384
`Page 12
`
`

`

`US 7,907,714 B2
`
`3
`input into the ISCP immediately. The service order assign
`ment control (SOAC) system receives all service order activ
`ity from service personnel and forwards the service orders to
`the SMS.
`For additional information regarding AIN and AIN-related
`network environments, see Berman, Roger K., and Brewster,
`John H., “Perspectives on the AIN Architecture,” IEEE Com
`munications Magazine, February 1992, pp. 27-32, the disclo
`sure of which is expressly incorporated herein by reference in
`its entirety.
`A number of services have been provided by AIN or AIN
`type intelligent networks to provide specialized call process
`ing of incoming calls and detailed call information. Services
`such as call routing, call forwarding and call logging have
`been provided by AIN or AIN-type networks. Service activa
`tion of a particular AIN service is normally accomplished by
`service personnel who receive a service order from a cus
`tomer, and then provision or create the CPR that is unique for
`each working telephone number (WTN) in the SCP or ISCP.
`Each customer’s CPR contains subscriber or pro?le data
`which control and/ or de?ne the service features and param
`eters associated with the AIN service subscribed to by the
`customer. Modi?cation to a customer’s CPR may be per
`formed by service personnel based on requests received from
`the customer (e.g., by a formal written submission for service
`modi?cation or via telephone interaction with service person
`nel). For more “simple” AIN services (i.e., AIN services that
`are based on very few or limited service parameters), auto
`mated modi?cation systems and methods have also been pro
`vided to permit a customer or user to modify their service
`pro?le data via a telephone connection and touch tone dialing
`or Dual Tone Multi Frequency (DTMF) response.
`An example of such a simple AIN service is selective call
`acceptance which was deployed in Wichita, Kans. in 1994.
`Selective call acceptance allows residential and small busi
`ness customers to provide a screening list of 50 authorized
`telephone numbers and one access code in order to allow
`people calling from one of the authorized numbers or with the
`access code to connect to the subscriber’s working telephone
`number. If an unauthorized caller calls the subscriber’s work
`ing telephone number, the unauthorized caller can be routed
`to an alternative location if desired, for example, a voice
`mailbox. When the subscriber chooses to modify the autho
`rized numbers and/or access code, the subscriber either con
`tacts service personnel or modi?es their service pro?le data
`via DTMF.
`While such prior systems have been provided, the ability
`for a customer to freely access and maintain their service
`pro?le data has been limited. Prior attempts have relied upon
`the involvement of service personnel or have limited a cus
`tomers ability to access and modify their service pro?le data.
`DTMF-based interfaces have also not provided an ef?cient or
`user-friendly system by which customers may review and
`revise their service pro?le data. Further, for more “complex”
`AIN-based services (i.e., AIN services based on a large num
`ber of service parameters or including more complex sets or
`groups of service parameters) such prior attempts have not
`provided an effective solution for automated service manage
`ment and maintenance. Thus, there is currently a need for an
`interface permitting users to freely access and maintain their
`service pro?le data. A need also exists for a user interface
`permitting a user to review and update their data for services,
`such as AIN-based services, through a computer-based inter
`face without requiring the involvement of or interaction with
`service personnel.
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`4
`SUMMARY OF THE INVENTION
`
`In view of the above, the present invention, through one or
`more of its various aspects and/or embodiments is thus pre
`sented to accomplish one or more objectives and advantages,
`such as those noted below.
`A general object of the present invention is to provide a
`pro?le management system having a user interface that pro
`vides the ability for a customer to freely access and maintain
`their service pro?le data.
`Another object of the invention is to provide a pro?le
`management system for AIN-based services. A further object
`of the invention is to provide such a system that does not rely
`upon the involvement of service personnel to permit a user to
`access and modify their AIN service pro?le data.
`Still another object of the invention is to provide a pro?le
`management system that provides an ef?cient and user
`friendly manner by which customers may review and revise
`their service pro?le data.
`Yet another object of the invention is to provide a pro?le
`management system for more “complex” services (e. g., AIN
`services based on a large number of service parameters or
`including more complex sets or groups of service param
`eters), that permits a user to more effectively access and
`maintain their pro?le data for such a complex service.
`Another object of the invention is to provide a pro?le
`management system that includes a user interface that per
`mits a customer to review and update their pro?le data for
`services, such as AIN-based services, through a computer
`based interface.
`A pro?le management system is provided for accessing
`and maintaining pro?le data associated with a telecommuni
`cations service subscribed to by a user. The pro?le data is
`stored on a telecommunications network which executes the
`telecommunications service subscribed to by the user in
`accordance with the pro?le data. The pro?le management
`system includes a client and a server. The client hosts a user
`interface allowing the user to view and update the pro?le data.
`The server processes user requests from the client to view and
`update the pro?le data by obtaining the pro?le data from the
`telecommunications network and forwarding the pro?le data
`to the client. The server also processes user requests from the
`client to update the pro?le data by forwarding user updates of
`the pro?le data from the client to the telecommunications
`network. As a result of the pro?le management system, the
`user can access and maintain the pro?le data associated with
`the telecommunications service subscribed to by the user
`without involving service personnel.
`In a preferred embodiment, the user interface is a graphical
`user interface, the telecommunications service is positive
`identi?cation, and the pro?le data includes access codes and
`authorized telephone numbers. Moreover when a calling
`party calls the user, the calling party is only successfully
`connected to the user if either the calling party’s telephone
`number is one of the authorized telephone numbers or the
`calling party inputs one of the access codes. If the calling
`party is not successfully connected to the user, the calling
`party hears a prerecorded message and is subsequently dis
`connected. A reporting system may also be provided which
`generates reports detailing calling parties attempting to con
`nect to the user. The report may also indicate each calling
`party successfully connected to the user, and each calling
`party not successfully connected to the user.
`According to another preferred embodiment, the pro?le
`management system also includes an access control system
`which only allows authorizedusers to access and maintain the
`pro?le data. Furthermore, the user may specify a time when
`
`AT&T Exhibit 1021
`AT&T v. VoIP, IPR 2017-01384
`Page 13
`
`

`

`US 7,907,714 B2
`
`5
`the server will forward the user updates from the client to the
`telecommunications network. The pro?le management sys
`tem may also include a DTMF system for accessing and
`maintaining the pro?le data.
`According to another embodiment, a pro?le management
`system is provided for accessing and maintaining pro?le data
`associated with a telecommunications service subscribed to
`by a user. The pro?le management system includes a server,
`a client and a telecommunications network. The client hosts a
`user interface allowing the user to view and update the pro?le
`data. The telecommunications network stores the pro?le data
`and executes the telecommunications service subscribed to
`by the user in accordance with the pro?le data. The server
`processes user requests from the client to view and update the
`pro?le data by obtaining the pro?le data from the telecom
`munications network and forwarding the pro?le data to the
`client. The server also processes user requests from the client
`to update the pro?le data by forwarding user updates of the
`pro?le data from the client to the telecommunications net
`work. As a result of the pro?le management system the user
`can access and maintain the pro?le data associated with the
`telecommunications service subscribed to by the user without
`involving service personnel.
`In a preferred embodiment, the user interface is a graphical
`user interface, the telecommunications service is positive
`identi?cation, and the pro?le data includes access codes and
`authorized telephone numbers. Moreover when a calling
`party calls the user, the calling party is only successfully
`connected to the user if either the calling party’s telephone
`number is one of the authorized telephone numbers or the
`calling party inputs one of the access codes. If the calling
`party is not successfully connected to the user, the calling
`party hears a prerecorded message and is subsequently dis
`connected.
`According to another embodiment, a pro?le management
`system is provided for accessing and maintaining pro?le data
`associated with an AIN service subscribed to by a user. The
`pro?le management system includes a server, client and an
`AIN network. The client hosts a user interface allowing the
`user to view and update the pro?le data. The AIN network
`stores the pro?le data and executes the AIN service sub
`scribed to by the user in accordance with the pro?le data. The
`server processes user requests from the client to view and
`update the pro?le data by obtaining the pro?le data from the
`AIN network and forwarding the pro?le data to the client. The
`server also processes user requests from the client to update
`the pro?le data by forwarding user updates of the pro?le data
`from the client to the AIN network. As a result of the pro?le
`management system the user can access and maintain the
`pro?le data associated with the AIN service subscribed to by
`the user without involving service personnel.
`In a preferred embodiment, the user interface is a graphical
`user interface, the AIN service is positive identi?cation, and
`the pro?le data includes access codes and authorized tele
`phone numbers. Moreover when a calling party calls the user,
`the calling party is only successfully connected to the user if
`either the calling party’s telephone number is one of the
`authorized telephone numbers or the calling party inputs one
`of the access codes. If the calling party is not successfully
`connected to the user, the calling party hears a prerecorded
`message and is subsequently disconnected.
`According to another preferred embodiment, a pro?le
`management system is provided for accessing and maintain
`ing pro?le data associated with a telecommunications service
`subscribed to by a user. The pro?le management system
`includes a client and a server. The client hosts a user interface
`allowing the user to view and update the pro?le data. The
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`6
`server stores the pro?le data and executes the telecommuni
`cations service subscribed to by the user in accordance with
`the pro?le data. The server processes user requests from the
`client to view and update the pro?le data by forwarding the
`pro?le data to the client. The server processes user requests
`from the client to update the pro?le data by replacing the
`stored pro?le data with user updates of the pro?le data
`received from the client. As a result of the pro?le management
`system, the user can access and maintain the pro?le data
`associated with the telecommunications service subscribed to
`by the user without involving service personnel.
`According to another preferred embodiment, a method is
`provided for accessing and maintaining pro?le data associ
`ated with a telecommunications service subscribed to by a
`user. The method includes remotely logging into a server,
`from a client; viewing the pro?le data associated with the
`telecommunications service subscribed to by the user; and if
`desired, updating the pro?le data. As a result of the method,
`the user can access and maintain the pro?le data associated
`with the telecommunications service subscribed to by the
`user without involving service personnel.
`The above-listed and other objects, features and advan
`tages of the present invention will be more fully set forth
`hereinafter.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`The present invention is further described in the detailed
`description which follows, by reference to the noted plurality
`of drawings by way of non-limiting examples of preferred
`embodiments of the present invention, in which like reference
`numerals represent similar parts throughout the several views
`of the drawings, and wherein:
`FIG. 1 illustrates the components of a conventional
`Advanced Intelligent Network (AIN) network environment;
`FIG. 2 illustrates, in block diagram form, an exemplary
`syst

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket