5,861,810
`[11] Patent Number:
`[19]
`United States Patent
`
`Nguyen
`Hg
`iDateofIfinent
`Jan.19,1999
`
`U8005861810A
`
`[54]
`
`[76]
`
`SYSTEM AND METHOD FOR PROVIDING
`CRIME VICTIMS UPDATED INFORMATION
`AND EMERGENCY ALERT NOTICES
`
`.
`-
`-
`Inventor. Eung 111Ng12ye262893§0 W1nter H111 Ct.,
`01115“ e’
`3"
`
`5,153,584 10/1992 Engira ................................ 340/870.18
`5,170,426
`12/1992 D’Alessio et al.
`...................... 340/573
`
`5,266,944
`11/1993 Carroll et al.
`340/825.36
`....... 340/573
`5,307,053
`4/1994 Wills et al.
`
`5,396,227
`3/1995 Carroll et al.
`340/825.36
`
`..... 379/38
`5,402,469
`3/1995 Hopper et a1.
`
`5,461,390 10/1995 Hoshen ........
`342/419
`7/1996 Russek .................................... 340/573
`5,534,851
`
`[21] Appl. No.: 722,359
`
`[22]
`
`Filed:
`
`Sep. 27, 1996
`
`.
`.
`Primary Examiner—Jeffery A. Hofsass
`Assistant Examiner—John Tweel, Jr.
`
`Int. Cl.6 ..................................................... G08B 23/00
`[51]
`[52] US. Cl.
`.................... 340/573; 340/534; 340/825.36;
`379/38; 379/39
`[58] Field of Search ..................................... 340/573 539
`340/540 870.18 825.36 534. 37,9/38,
`’
`’
`’
`3’9 106.1
`’
`
`[56]
`
`References Cited
`
`US. PATENT DOCUMENTS
`5/1974 Kabat et al.
`............................ 340/534
`6/1984 Burnett .......
`.340/825.36
`
`...... 340/573
`12/1990 McCurdy
`2/1992 Shapiro ..................................... 379/39
`
`3,810,096
`4,455,548
`4,980,671
`5,091,930
`
`[57]
`
`ABSTRACT
`.
`.
`.
`.
`A system and method for commun1cat1ng 1nformat1on con-
`cerning the status 0f inmates to callers and automatically
`notify Victims registered With the system at a registered
`electronic address When the status of a specified inmate has
`changed. The notifications to the electronic address of the
`registered Victim Will continue at spaced predetermined
`intervals until either the registered Victim responds With a
`registered personal identification number or a predetermined
`time periOd measured from the initial
`time “Otificafion
`elaPSCS
`
`38 Claims, 13 Drawing Sheets
`
`12
`
`52
`
`IO
`
`REMOTE
`
`HOST
`
`56:
`
`RESET
`
`(0/
`
`(no
`
`54
`
`/O
`
`63
`
`62
`
`59
`
`CONTROL
`CENTER
`
`VICTIM
`ADDRESS
`
`64
`
`@5
`
`IPR of US. Patent No. 8,340,260
`
`GTL 1007
`
`GTL 1007
`IPR of U.S. Patent No. 8,340,260
`
`

`

`US. Patent
`
`Jan. 19,1999
`
`Sheet 1 0f 13
`
`5,861,810
`
`HOST
`COMPUTER
`
`HOST
`
`IO
`
`HOST
`
`REMOTE
`GATEWAY
`
`REMOTE
`GATEWAY
`
`REMOTE
`
`GATEWAY
`
`STATION
`
`F/G./
`
`

`

`US. Patent
`
`Jan. 19, 1999
`
`SheetZ 0f13
`
`5,861,810
`
`IO
`
`HOST
`
`GAIEWMN
`PC
`
`PROCESSOR
`
`l4d
`
`

`

`US. Patent
`
`Jan. 19, 1999
`
`Sheet 3 0f 13
`
`5,861,810
`
`3G
`
`EXECUTIVE
`OPERATING
`SYSTEM
`
`END OF CALL
`END OF CALL
`
`DATABASE OF
`PERSONALITY
`FILES
`
`PERSONALITY
`FILE
`DNIS : 4618
`
`PERSONALITY
`FILE
`DNIS : 4762
`
`PERSONALITY
`FILE
`DNIS : 4762
`
`4618 - FILE 1
`4762 — FILE 2
`
`INSTRUCTION 1
`INSTRUCTION 2
`
`INSTRUCTION 1
`INSTRUCTION 2
`
`INSTRUCTION 1
`INSTRUCTION 2
`
`4376 — FILE 3
`
`END OF CALL
`
`34-
`
`32
`
`F/G. 2
`
`

`

`US. Patent
`
`Jan. 19,1999
`
`Sheet 4 0f 13
`
`5,861,810
`
`I2
`
`52
`
`IO
`
`56
`
`(00
`
`54'
`
`/O
`
`63
`
`62
`
`CONTROL
`CENTER
`
`RESET
`
`(”I
`
`f§K3.41
`
`VICTIM
`
`ADDRESS
`
`@4
`
`@5
`
`59
`
`
`
`REMOTE
`
`CONTROL
`CENTER
`
`44
`
`
`PUBLICITY
`
`
`CALLER
`
`F/G.3
`
`

`

`US. Patent
`
`Jan. 19, 1999
`
`Sheet 5 0f 13
`
`5,861,810
`
`TYPICAL INMATE FILE
`
`4(0
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`TYPICAL VICTIM FILE
`
`48
`
`
`
`
`
`
`
`
`.50
`
`
`
`
`
`
`
`TYPICAL AUDIT FILE
`
`F/G5
`
`

`

`US. Patent
`
`Jan. 19,1999
`
`Sheet 6 0f 13
`
`5,861,810
`
`
`
`STATUS
`CHANGE
`CALL
`
`56
`
`69
`
`
`VERFY
`
`
`DATA
`
`
`SOURCE
`
`
`Y
`
`628
`
`STOP
`
`VICTIM
`
`INMATEOR
`
`
`
`VICTIM
`DATABASE
`CHANGE
`
`UPDATE
`
`72
`
`70
`
`INMATE
`
`74
`
`Y
`
`76
`
`
`
`NOTIFICATION
`NEEDED?
`
`
`
`N
`
`

`

`US. Patent
`
`Jan. 19,1999
`
`Sheet 7 0f 13
`
`5,861,810
`
`INCOMING CALL
`FROM CALLER
`
`CHOICES
`
`PLAY INTRODUCTION
`LANGUAGE
`
`88
`
`INMATE
`INMATE
`
`NAME
`NO.
`
`SEARCH TYPE
`REQUEST
`
`
`
`
` SEARCH BY NO.
`
`SEARCH BY NAME
`(SEE FIG 9A/9B)
`(SEE FIG 8)
`
`
`
`GIVE DATA
`REGISTRATION REQ
`
`(SEE FIG 10)
`
`94
`
`96
`
`PLAY GOODBYE
`
`F/G. 7
`
`

`

`US. Patent
`
`Jan. 19,1999
`
`Sheet 8 0f 13
`
`5,861,810
`
`SEARCH
`
`lNMATE #
`
`
`ENTER
`
`
`
`INMATE #
`
`loo
`
`98
`
`
`CORRECT
`NUMBER
`
`OFDKNTS
`
`YES
`
`
`INMATE
`
`[0&2
`
`NO
`
`SE33”
`
`YES
`
`PLAY INVALID # NO
`
`TRYAGNN
`
`
`
`
`/04
`
`NO
`
`/08
`
`PLNY
`
`NOTFOUND
`
`GOODBYE
`
`PLAY
`
`INMATE NOT
`FOUND
`GOODBYE
`
`RElgRN
`MA'N
`
`F/G. 8
`
`

`

`US. Patent
`
`Jan. 19,1999
`
`Sheet 9 0f 13
`
`5,861,810
`
`SEARCH BY
`VICTIM
`NUMBER
`
`900.
`
`
`
`
`ENTER
`NUMBER
`
`“2
`
`H4
`
`YES
`
`
`IS NUMBER
`CORRECT?
`
`
`
`PLAY
`INVALID NUMBER
`
`
`DO YOU WISH
`TO TRY ANOTHER
`
`H7
`
`NO
`
`GOODBYE
`
`I
`
`’ 8
`
`NO
`
`SEARCH
`INMATE
`
`YES
`
`l22
`
`pLAY
`INMATE NOT
`FOUND
`
`l20
`
`MAIN
`
`RETURN
`TO
`
`F/G. 8A
`
`

`

`US. Patent
`
`Jan. 19,1999
`
`Sheet 10 0f 13
`
`5,861,810
`
`INMATE
`NAME
`SEARCH
`
`
`
`LAST NAME
`REQUEST
`
`ENTER
`
`92
`
`124
`
`)2(o
`
`I28
`
`T
`
`INCORREC
`
`
`
`CONFIRMATION
`
`CORRECT
`
`/32
`
`RE-ENTER
`
`REQUEST
`
`
`NO
`
`’3/
`
`NO
`
`SEARCH
`
`YES
`
`GOODBYE
`
`PLAY
`
`
`
`Ffiggug‘sflE
`
`IBG
`
`FROM
`FIG 93
`
`NOT IN CUSTODY
`
`"GOODBYE"
`
`IE4
`
`[38
`
`TO FIG 93
`
`F/G. 9A
`
`

`

`US. Patent
`
`Jan. 19,1999
`
`Sheet 11 0f 13
`
`5,861,810
`
`FROM 9A
`
`/40
`
`NO
`
`CONFIRMED?
`
`YES
`
`I42
`
`SEE
`
`HG 9A
`
`YES
`
`_
`RE ENTER REQUESTED
`
`NO
`
`144
`
`GOODBYE
`
`YES
`
`148
`
`1%
`
`NO
`
`MORE THAN ONE
`NAME?
`
`
`
`SEARCH
`
`MIDDLE INITIAL
`REQUEST
`
`NO
`
`INMATE
`FOUND
`
`/GO
`
`YES
`
`RETURN
`TO
`MAIN
`
`ENTRY
`
`152
`
`PLAY
`NOT FOUND
`GOODBYE
`
`CONFIRM
`
`CORRECT
`
`
`
`
`I54-
`
`I56:
`
`HG 9,9
`
`/57
`
`YES
`
`NO
`
`INMATE
`FOUND
`
`I58
`
`PLAY
`
`NOT FOUND
`
`GOODBYE
`
`MAIN
`
`RETURN
`
`To
`
`

`

`US. Patent
`
`Jan. 19,1999
`
`Sheet 12 0f 13
`
`5,861,810
`
`GIVE INMATE
`DATA
`
`REGISTER INQUIRY
`
`YES
`
`ENTRY
`
`94
`
`/
`66
`
`Ma?
`
`NO
`
`/(a9
`
`REPEAT STATUS
`
`INFORMATION GOODBYE
`
`68
`
`170
`
`/
`
`/ 174—
`
`PLAY
`
`CAUTION STATEMENT
`
`TELEPHONE NO.
`REQUEST
`
`PIN REQUEST
`ENTER
`
`IS PIN 4 DIGITS
`
`I78
`
` YES
`
`REGISTRATION
`COMPLETE "GOODBYE"
`
`I76
`
`'NVAL'D P'N
`
`F/G. /O
`
`

`

`US. Patent
`
`Jan. 19,1999
`
`Sheet 13 0f 13
`
`5,861,810
`
`__________________ ‘l
`
`CONTACT
`REGISTERED
`TELEPHONE #
`
`NOTIFICATION
`LETrER
`
`I80
`
`
`
`
`182
`
`PLAY NOTIFICATION
`AND PIN REQUEST
`
`ENTRY
`
`/ 4
`8
`
`/86:
`
`YES
`
`N0
`
`IS PIN
`4 DIGITS
`
`
`
`INVALID PIN
`REPEAT PIN
`REQUEST
`
`I90
`
`NO
`
`IS PIN
`CORRECT
`
`YES
`
`[92
`
`/94
`
`RESET
`
`PLAYCIIIEI'E‘IIT'ON
`
`GOODBYE
`
`F/G.//
`
`

`

`1
`SYSTEM AND METHOD FOR PROVIDING
`CRIME VICTIMS UPDATED INFORMATION
`AND EMERGENCY ALERT NOTICES
`
`BACKGROUND OF THE INVENTION
`
`The present invention relates to a system and method for
`the alerting of victims of the change of status of a defendant
`in the criminal justice system.
`The rights of victims in the criminal justice system is
`receiving considerable attention today in the midst of a
`significant violent crime rate and early release of many
`offenders due to the over crowding of prisons. Many states
`have passed legislation enacting the right of victims to be
`alerted to the early release or other changes in status of
`defendants and mandating that
`the state justice system
`timely notify the victims of such change in status. The
`system for notification has been difficult to implement for
`various reasons. Victims are extremely mobile and difficult
`to locate, requiring considerable personal effort and conse-
`quential outlay of expenses in a time of governmental
`budgetary limitations. Moreover, because such systems
`involve numerous status changes and the notification effort
`of busy personnel, they are highly prone to error, miscom-
`munications and complete oversight. Most “home grown”
`systems have proven to be ineffective and the governmental
`agencies often involved make little or no effort
`to call
`victims. The failed approaches result in victims being forced
`to make repeated and, in many instances unsuccessful, calls
`to the appropriated agencies to receive status changes. The
`mental stress and trauma to victims caused by the failed
`systems can be significant coupled with a high potential of
`injurious attacks perpetrated by certain vindicative defen-
`dants.
`
`It is therefore a primary object of the present invention to
`provide for an effective and dependable system for the
`timely notification of victims of a change of judicial status
`of defendants.
`
`20
`
`25
`
`30
`
`35
`
`It is still another object of the present invention to provide
`for a victim notification system that verifies that the recipient
`of a notification is the victim.
`
`40
`
`invention to
`is still a further object of the present
`It
`provide for a victim notification system that is flexible and
`expandable to satisfy a wide variety of options, laws and
`regulations of different localities.
`It is yet another object of the present invention to provide
`for a victim notification system that is economically afford-
`able and technological accessible to all communities, par-
`ticularly to communities of small populations.
`
`SUMMARY OF THE INVENTION
`
`invention comprises a victim notification
`The present
`system and method for notifying a victim of the change of
`status of an inmate associated with the victim. The system
`itself includes a central processor or control station for
`storing in a data base information pertaining to a plurality of
`prison inmates and a plurality of victims. Each of the victims
`in the central processor data base is identified with a
`respective one of the inmates and has selected a personal
`identification number, i.e., a “PIN”. Another component of
`the system is a remote data storage device that receives all
`information pertaining to changes of status of the inmates
`from a computer where the information is originated. The
`remote data storage device communicates any inmate
`change of status to the central control station. Each of the
`victims registered in the system has a communication
`
`45
`
`50
`
`55
`
`60
`
`65
`
`5,861,810
`
`2
`receiving device such as telephone for receiving changes of
`relevant inmate status information from the central control
`station. When the control station receives a change of inmate
`status deemed relevant, it automatically calls and informs
`the victim of the change. The victim then provides the PIN
`to confirm receipt of the notification. If the PIN is not
`correctly entered into the system, the system will continue to
`call back until the PIN is entered or a predetermined time
`period has elapsed.
`The remote devices constantly poll the host computers to
`determine if any change of inmate status has occurred. All
`such information is uploaded to the remote device and
`communicated to the central control station. In this manner
`
`10
`
`the information on inmates is kept current at the central
`control station.
`
`15
`
`To ensure that the remote data storage devices are in
`proper working order, each of the devices calls the central
`control station at predetermined time intervals. Should one
`of the remote devices fail to call
`in by the end of the
`predetermined time interval, an alarm and/or pager is acti-
`vated so that assigned workers can immediately address the
`problem.
`BRIEF DESCRIPTION OF THE DRAWING
`
`FIG. 1 is a schematic of a typical configuration and
`architecture of a system of victim notification in accordance
`with one embodiment of the present invention;
`FIG. 1A is a block diagram of the major components of
`the central victim notification control station and remote
`
`gateway in accordance with one embodiment of the present
`invention;
`FIG. 2 is a block diagram of the executive operating
`system architecture;
`FIG. 3 is a block diagram illustrating the flow of infor-
`mation and signals when initially connecting the system
`with a remote gateway at a new location;
`FIG. 4 is block diagram illustrating the general flow of
`information and signals between the various parts of the
`system for updates on inmate status and monitoring of
`remote equipment;
`FIG. 5 is chart representing typical data base record for
`stored information pertaining to prisoners, victims and sys-
`tem audit records;
`FIG. 6 is a flow chart in block diagram form depicting the
`main operating program used with the present invention;
`FIG. 7 is a flow chart depicting the general routine
`initiated by a caller for information either by inmate number
`or inmate name;
`FIG. 8 is a flow chart depicting an operating program
`initiated by a caller when requesting a search by inmate
`number and the response thereto;
`FIG. 8A is a flow chart of an alternate routine from that
`
`shown in FIG. 8 in which the caller is required to have a
`specific unique number in order to gain information about
`the status of an inmate;
`FIGS. 9A and 9B collectively represent a single flow chart
`depicting an operating program initiated by a caller when
`requesting a search by inmate name and the response
`thereto;
`FIG. 10 is a flow chart representing an operating program
`initiated by a caller when registering as a to-be notified-
`when-status-changes-caller (“victim”) into the notification
`system with respect to a selected inmate; and
`FIG. 11 is a flow chart representing an operating program
`initiated by system to notify a victim when the status of the
`selected inmate has changed.
`
`

`

`5,861,810
`
`3
`DETAILED DESCRIPTION OF THE
`PREFERRED EMBODIMENT
`
`In the following description, reference will be made to
`Callers and Registered Victims in various situations. For a
`clearer understanding, “Caller” shall be defined as any
`person that calls the system for information about the status
`of an inmate. “Registered Victim” shall be any person who
`has provided the system with his or her unique identifying
`communication address such as a telephone number or
`electronic address and selected a personal
`identifying
`number, i.e., a “PIN”.
`Reference is first made to FIGS. 1 and 1A illustrating,
`respectively, a schematic of the victim information and
`notification system (“System”) used to register and notify
`Registered Victims and a schematic of the major compo-
`nents of the remote gateway and central control station. The
`System is comprised of four major components: a plurality
`of host computers 10; a plurality of remote gateways 12
`associated with each host computer 10; a central victim call
`control station 14; and a plurality of notification receiving
`devices such as telephones 18 associated with each Caller or
`Registered Victim. The host computers 10 are physically
`located in the region or locality of the site shown by the
`dashed lines 11 in which the inmates are incarcerated or
`
`placed. Such localities shall define the term “Local Site” as
`used in this description. Computers 10 thus generally store
`inmate and case management
`information pertaining to
`inmates in the respective Local Site. Examples of host
`computers are mainframes such as IBM 3090, Unisys or HP
`mainframes although at some smaller facilities a PC based
`system may be employed. The controlling software compo-
`nent used in a Local Site that tracks inmates through the
`local criminal justice system is ordinarily chosen by the
`agency in charge of managing the information (“Local
`Authorities”). Typically, the Local Authorities will deter-
`mine the precise wording of information to be delivered to
`Callers and Registered Victims pertaining to inmates in the
`Local Site and the nature of the responses required of such
`Callers and Registered Users. As will be discussed below,
`the host computers 10 of the Local Sites are coupled via a
`local area network 36 to associated remote gateways 12
`typically located in the same Local Site. Gateways 12 are
`primarily used to extract and filter the necessary information
`from the host computers 10 to deliver to the central control
`station 14 in a manner to be described. Each remote gateway
`12 comprises hardware components such as a PC, a high
`speed modem and connection hardware as illustrated in FIG.
`1A. The software component of the gateway 12 is respon-
`sive to provide the necessary information and calls needed
`by the central victim call control station 14.
`Control station 14 communicates with remote gateway 12
`through long distance network 16 and houses the central
`processing software functioning to process the data for-
`warded by remote gateways 12 from host computers 10. The
`primary functions of control station 14 are to process
`incoming calls 20 from telephones 18 and provide informa-
`tion in response to such calls via the long distance network
`16 and to initiate warning or notification calls 22 to the
`numbers or electronic addresses of telephones 18 or other
`communication receiving devices of Registered Victims as
`significant changes in inmate status information is received.
`As illustrated in FIG. 1A, each control station 14 typically
`comprises one or more central processors 14a, a high speed
`modem 14b, a voice recognition board 146, and a telecom-
`munication and voice processing board 14d. Examples of
`each are given in the Table 1 set forth below. As will be
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`4
`discussed below, the voice processing board 14d provides
`the System the ability to deliver predetermined spoken
`messages to registered victims while the voice recognition
`board provides the System the ability to process and to react
`to spoken commands and/or store spoken information where
`the Local Authorities have requested this ability as a part of
`the service to the Local Site.
`
`The System of the present invention also contemplates the
`use of a notification work station 24 comprising a PC and
`software permitting operators of the System to directly use
`the control station 14 to generate various reports and letters.
`For example, letters 26 prepared, for example, by operators
`of PCs 27 networked with the central control station 14.
`
`Such letters are backup notices containing information with
`respect to the notification attempts such as when and how
`many notification calls were made and the notification
`message itself. The letters are then posted the Registered
`Victims who were not confirmed as being reached.
`
`As illustrated generally in FIG. 2, the executive operating
`system 28 maintains within control station 14 a comprehen-
`sive database for each Local Site represented by a “DNIS”
`(defined below) as character numeral 30 and “personality”
`files 32 for each site. The term “personality” is used to
`denote that each Local Site has an overall process or
`communication routine customized in accordance with the
`desires of the Local Authorities for communication with
`
`Callers and Registered Victims about victims incarcerated
`within the Local Site. Thus, voice messages, prompts, PIN
`numbers, use of voice recognition and voice inputs, and the
`like vary among the various Local Sites in the System. The
`executive operating system 28 is responsible for the man-
`agement of all calls, database management, collection of
`remote gate way information, the personality and flow of all
`incoming and outgoing telephone calls, and the recording of
`all audit files showing incoming and outgoing call activity.
`When an incoming call is received, the executive operating
`system 28 determines the Local Site to which the incoming
`call pertains. All Local Sites, for example, may be assigned
`a specific 800number for Callers to use when requesting
`status information about an inmate associated with the Local
`
`Site. When a 800 number is dialed, the long distance carriers
`send a special code to the receiving party which identifies
`the specific 800 number being dialed. This service is called
`the Dialed Number Identification Service or “DNIS”. Such
`
`a service provides receiving parties, who have purchased the
`use of a plurality of 800 numbers, the ability to determine
`which of the 800 numbers is being called. When the 800
`number assigned to a particular Local Site is called, the
`operating system 28, using the DNIS, is prompted to locate
`the appropriate personality file 32 for that call. System 28
`then begins executing the located personality file 32, which
`defines all the messages that are played during the particular
`call. The personality file 32 also defines all of 10 the menu
`selections given the Caller and reads/write the various data
`bases used for the call.
`
`REMOTE GATEWAYS 12
`
`TABLE 1
`
`PC
`
`Modem
`
`Pentium PC with 8 MB Ram
`available from Dell Computers
`Corp.
`28.8 KB HS internal modem
`available from US Robotics as
`Model Sportster
`
`

`

`5,861,810
`
`5
`
`TABLE 1-continued
`CENTRAL CONTROL STATION 14
`
`Central Processor 14a
`
`High Speed Modem 14b
`
`Voice Recognition Board 14c
`
`Voice Processing Board 14d
`
`14 Slot Pentium industrial
`grade rack mount central
`processor available from Texas
`Micro
`28.8 KB HS internal modem
`available from US Robotics as
`Model Sportster
`Voice recognition board
`available from Dialogic Corp.
`Mfg. # VR/160
`T1 telecommunications and
`voice processing board
`available from Dialogic Corp.
`as Mfg # D/240SC—T1
`
`The inmate information that goes into the various data-
`bases is initially collected from the host computer 10 by the
`remote gateway 12 which, in part, comprises a PC and a high
`speed modem. The block diagram of FIG. 3 illustrates that,
`as each new Local Site goes into the System of the present
`invention, the PC of the remote gateway 12 associated with
`the new Local Site is connected through a local area network
`36 to the associated host computer 10 and, as stated above,
`is able to communicate with the central control station 14
`
`through a long distance carrier. Once connected, the remote
`gateway 12 then collects a complete set of initial inmate and
`Victim data from host computer 10 and transmits the data to
`the control station 14. It is at this point that Callers (here
`depicted by BLOCK 38) can dial a unique 800 number
`(shown by character numeral 40) assigned to each Local Site
`and search the data bases associated with that Local Site for
`
`information on inmate status. Additionally, the Caller, if not
`already registered, can register as a Registered Victim for
`automatic notification in response to the registration request
`42 communicated to the caller following delivery of the
`inmate status information. Individuals are made aware of the
`
`800 number through public service announcements made in
`the media of the appropriate Local Site, brochures promul-
`gated by the police of the Local Site, and other publicity as
`determined by the Local Authorities. This publicity trans-
`action is depicted by publicity BLOCK 44. It should also be
`understood that registration of Victims as Registered Victims
`is often done during or following the court proceedings of
`the inmates usually at the request of representatives of the
`Local Authorities. In many instances, the Local Authorities
`prefer to limit the availability of the System, both for search
`and registration operations, to those who are specifically
`sought out and registered by the local law enforcement
`personnel as opposed to allowing any person from the
`general public to use the System. In such case, the infor-
`mation pertaining to the Registered Victims is entered into
`the host computer 10 by representatives of the Local
`Authorities and, Via the associated remote gateway 12, is
`delivered and stored in the central control station 14.
`
`Changes to the Registered Victims database can be inputted
`by a keyboard directly into the host computer 10 by autho-
`rized representatives of the Local Authorities and/0r Regis-
`tered Victims or made by the Registered Victim through
`direct electronic communication with the central control
`
`station 14 using the Registered Victim’s telephone.
`It is clearly imperative that the inmate databases at the
`central control station 14 be maintained current with quick
`updates reflecting any changes in inmate status. Reference is
`made to FIGS. 4 and 5 for the ensuing discussion, the latter
`Figure illustrating a typical inmate file 46, Victim file 48, and
`
`6
`audit file 50. To ensure the current state of the inmate files,
`remote gateway 12 makes a transaction file check 52 at
`predetermined intervals, e.g., every 10 minutes, with each
`host computer 10. As each inmate record is modified and
`entered into the host computer 10, the host computer 10
`writes an audit record to a transaction file and uploads the
`transaction file depicted by line 54 to gateway 12. In turn,
`gateway 12 checks the transaction file for changes in inmate
`status. When a change is detected, gateway 12 sends the
`changed status depicted by line 56 to control station 14.
`Control station 14 then searches databases to determine if
`
`there are any Registered Victims (denoted by BLOCK 59)
`that need to be notified of the changed status. In the event
`that such Registered Victims are identified, the notification
`call process (discussed below) will be automatically trig-
`gered and a notification call sequence 58 initiated.
`To ensure that all remote equipment is working properly
`and particularly that no communication lapses are occurring,
`each remote gateway 12 transmits a “handshake” signal 60
`at frequent intervals, e.g., every two minutes,
`to control
`station 14. Preferably, the signal 60 is a telephone call to a
`specific telephone number at control station 14 with the call
`carrying an automatic number identification (ANI) signal
`passed between telephone rings. Such ANI signals enable
`the control station 14 to identify the precise remote gateway
`12 making the call without making a direct connection, i.e.,
`picking up the telephone or using separate communication
`channels. Some telephone carriers still do not have this
`capability, however. In such cases, the remote gateway 12 in
`the Local Site is assigned a 800 number unique for that
`Local Site to call and the control station 14, using the DNIS,
`can then identify the calling remote gateway 12 by the 800
`number thus being called. When the handshake signal is
`timely received,
`the control station 14 “knows” that the
`gateway 12 is operating properly and the timer for that
`remote gateway is reset as shown by reset BLOCK 61. When
`a gateway 12 fails to call in with the handshake signal 60,
`the control station may cause an alert signal 62 to trigger an
`alert window of a computer screen 63 at the site of the
`central control station 14 alerting a Viewer of the possible
`communication malfunction. Additionally, the control sta-
`tion 14 may also send out a pager signal 64 to a pager 65,
`alerting an assigned repair operator of the uncommunicative
`remote gateway who then determines the nature and
`addresses the problem.
`The function block diagram of FIG. 6 describes the
`“updating” of the various files upon receipt of an incoming
`status change call 56 from remote gateway 12. Initially,
`control station 14 handshakes with the calling remote gate-
`way 12 and verifies at VERIFY 66 that the data is coming
`from a legitimate source using a predetermined identifying
`protocol. This, of course, is needed to ensure that system is
`not compromised by entry of incorrect data from extraneous
`sources. Thus, if NO, the program routine stops at BLOCK
`68. If YES, the System determines at BLOCK 70 whether
`this is a change to the Victim or inmate database. If it is a
`change to the Victim database, the Victim database is updated
`at BLOCK 72. If the change is to the inmate database, then
`the inmate database is updated at BLOCK 74 and a deter-
`mination made at NOTIFICATION 76 whether a Registered
`Victim associated with the particular inmate should be
`notified. If YES, then notification calls 78 are begun. If NO,
`the program ends at BLOCK 80.
`The general routine executed when a Caller dials the 800
`number for a Local Site is shown in FIG. 7. The various
`
`subroutines, executed primarily in accordance with menu
`choices selected by the Caller, are illustrated in FIGS. 8 and
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`

`

`5,861,810
`
`7
`9A and 9B. FIG. 10 is the subroutine automatically executed
`following delivery of the requested inmate status informa-
`tion during which the Caller is given the option of register-
`ing as a Registered Victim.
`As stated above, when the Caller calls an 800 number
`assigned to a Local Site at BLOCK 84, the main routine is
`initiated at BLOCK 86 with the control station 14 through its
`voice processor answering the call, identifying the Local
`Site associated with the call via DNIS, and providing initial
`prompts in accordance with the personality file for that
`Local Site. In multilingual localities, the initial prompts may
`start by giving the Caller a choice between two of more
`languages in which further voice communications can pro-
`ceed. For example, the language choices may be English,
`Spanish or Vietnamese, with the voice processor stating each
`choice in the respective language for that choice. The Caller
`would press 1, 2, or 3 as prompted depending on the
`language choice. Once a language has been selected, the
`System will continue to use that language when addressing
`the Caller, in both current and future notification calls. The
`next prompt at BLOCK 88 made in the selected language
`would be a request to press 1 if the Caller wishes to use an
`“inmate number” to initiate the search or press 2 if the Caller
`will use the inmate name for the search. Local Authorities
`typically assign each inmate a number,
`i.e.,
`the “inmate
`number”, for use in the System. Then Caller then makes a
`choice selection depicted by BLOCK 90 for inmate number
`or BLOCK 92 for inmate name. The selection then initiates
`either the subroutines set forth in FIGS. 8 for inmate number
`or FIGS. 9A/9B for inmate name. Once those subroutines
`have been completed with the inmate information being
`vocally given, the Caller is returned to the main routine and
`will be typically asked if he or she wishes to be registered
`as a Registered Victim at BLOCK 94. If the Caller responds
`in the affirmative to the registration inquiry prompt at
`BLOCK 94, then the subroutine of FIG. 10 is initiated and
`executed. Upon completion of the registration menu
`selections,
`the program ends in the main routine with a
`“Goodbye” BLOCK 96 to the caller.
`When the Caller elects to search for inmate status infor-
`
`mation by inmate number as illustrated in the subroutine
`flow chart of FIG. 8,
`the caller is prompted at prompt
`BLOCK 98 by the voice processor to enter the inmate
`number or, in an alternate subroutine, a “victim number” on
`the touch dial phone. Since the inmate number is determined
`by the Local Authorities,
`the Caller obtains the inmate
`number
`through procedures established by the Local
`Authorities. For certain Local Sites,
`the Authorities may
`desire to further limit access to the information imparted by
`the System. Some Local Authorities prefer not to permit use
`of the inmate names to gain access and limit dissemination
`of the inmates number on a need-to-know basis. Some Local
`
`Authorities issue the inmate numbers only to Registered
`Victims. Thus, any Caller wishing to access the System
`using the Local Site DNIS number would have to either
`register as a Registered Victim with the Local Authorities to
`obtain the inmate number or go through some sort of
`prescribed administrative procedure. Moreover, the Local
`Authorities may require that each Registered Victim be
`provided a victim notification card identification number
`(Victim Number) that must be entered before any informa-
`tion on inmates is communicated by the central control
`station. When the Local Site requires the use of a Victim
`Number, entry of a valid Victim Number will automatically
`call up the database for the inmate associated with the
`Victim Number and Registered Victim.
`Once the inmate number is entered in subroutine of FIG.
`
`8 at BLOCK 98, as prompted, control station 14 determines
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`8
`if the number is valid or not at determination BLOCK 100.
`If NO, the Caller is informed that the inmate number is not
`the correct number of digits at BLOCK 102 and invited to
`try another number or hangup. If YES, the Caller is returned
`to Enter Number at BLOCK 98. If No, the caller is returned
`to the main routine at BLOCK 104 for “Goodbye”. If the
`inmate number has the correct number of digits at BLOCK
`100 or YES, a search is made for the inmate database at
`BLOCK 106. If the number corresponds to an inmate in
`custody or YES, the Caller is returned at BLOCK 108 to the
`main routine at BLOCK 94 where the Caller is informed of
`the latest status of the inmate. If NO, i.e., no inmate is found
`at BLOCK 110, then the Caller is informed of this fact and
`the routine ends with “Goodbye”.
`Similarly, in an alternate subroutine set forth in FIG. 8A
`where Victim Numbers are required, once the Victim Num-
`ber is entered at BLOCK 112, control station determines if
`the Victim Number is valid or not at BLOCK 114. If NO, the
`Caller is informed the number is not valid and invited to
`re-enter the correct Victim Number at BLOCK 116. The
`
`cycle will be repeated at predetermined number of intervals,
`e.g., three times, after which the control station will return
`to the main program at the “Goodbye” statement. If YES, the
`control station will search for the corresponding inmate data
`base at BLOCK 118. If the inmate is not found or NO, the
`Caller is told this at BLOCK 120 and the routine ends with
`
`“Goodbye”. If the corresponding inmate database is found
`or YES, the control station returns to the main routine at
`BLOCK 122 and provided the inmate status at BLOCK 94.
`Reference is now made to FIGS. 9A and 9B setting forth
`the subroutine executed whe