Page 1 of 41
`
`SECURUS EXHIBIT 1006
`
`

`
`U
`
`m
`
`a
`
`y
`
`2B
`
`m5Apm2:
`S./22:
`
`1\\:1\
`
`mozmmfzoo_/\/>\/W0/\xx/2:_/_\\//.M_/_\\\//.
` \\//xamo..\\\fl//\/x_M/\/\_s_,I<_zo:/EmzoE:m./,\/x)_E<¢_o_E<n_E<n:o_E/E_/\/\/,Mmazmamzzoo
`
`
`
`
` I\M2:zopémzoE:mzoE:,m
`
`E§5_E/E...mmoami...49:28
`
`mézmmmczou«SZEZBmowSzmmfizooNS
`
`Page 2 of 41
`
`
`
`
`
`mmom_>E%m7,mE<n:o.E/EmmozzamoouW2323:$03mmE<Em.z__>5<
`
`
`
`m_OEW\©:\\m:»\i_\\m:
`
`Page 2 of 41
`
`
`

`
`U.S. Patent
`
`May 16,2006
`
`Sheet 2 of 19
`
`US 7,046,779 B2
`
`ommW3/mmmm:,<#_\, mmozzamooomamEgmoomm
`>:.__mS_<><Evzmim,\\x\w\u«lJl»f.H5./mmflzou
`
`
`.z<m%%zm%mdflmxmzozaomggs\\\\\Em5328
`
`
`\a,
`
`
`obE0232 EN77\\wing.zoE5o,_
`
`mE<n__o_E,&359/2Em_i_38..
`
`
`Q:Emm._.Z<n:O_._.W_<&N.0_.._NE
`
`l%%w77ommEjoEzoo9/2hmdm»\)ooN
`
`:05
`
`
`
`I.\,|E”[r’J:{\V.}!r:f::/_,&_o_EEULJritxx/,mom
`
`mz/fin.\\J/
`
`m43Qm:omgm
`
`uozumglzoo
`
`4moz<oKO5
`
`
`
`5253200mE<1_u_.E/E
`
`mmiommg
`
`L7777%Now
`
`EN.1.mmoZEm_z_§Q<
`
`
`m__mxomSmmm:m
`
`Page 3 of 41
`
`Page 3 of 41
`
`
`
`
`

`
`U.S. Patent
`
`May 16,2006
`
`Sheet 3 of 19
`
`US 7,046,779 B2
`
`jcea;€:g§ """""" “I
`
`
`
`CONTROL
`
`STKHON
`
`
`
`
` MANAGEMENT I302
`
`JNL
`
`SYSTEM
`
`7 -____
`
`II I
`
`I
`_______ ____I
`
`§fi§fifiJé’5E§7Eé_§1giI
`
`.JAm 313
`
`___..__I
`
`I
`
`F331
`
`//330
`
`I I I I I I I I I II I I I I I I I I
`
`.
`
`,32I
`
`/I320
`
`
`
`Page 4 of 41
`
`1. _ _ # _ _ _ _ __
`,¢mL gig
`I
`
`341
`
`//340
`CON7ROL
`
`
`
`I I
`
`I
`
`Page 4 of 41
`
`

`
`U.S. Patent
`
`May 16,2006
`
`Sheet 4 of 19
`
`US 7,046,779 B2
`
`N:
`
`
`Eimfi./___+£f%rIErr\|l".11:$jcEzooL4mo/:wEz_
`
`
`VEQEZ.newmo.“_vaogmzWSTEE;
`I_0Newmamms:_
`
`
`
`
`F::2»+..UJ
`
`mov
`
`
`
`mmw€206nmvfl.I
`
`
`
`OZ_ZO:._QZOQ.
`
`
`
`
`
`Illa’(,uIll
`
`
`
`
`
`mmé1_<ZO_m.vmLnu
`
`.EZZ<Io
`
`I_5D_>_
`
`wmomoomm
`
`0Z_ZOEDZOQ.
`
`_————.——__..__._..—..._._.___.__.—__..._)
`
`Page 5 of 41
`
`Page 5 of 41
`
`
`
`
`
`

`
`U.S. Patent
`
`May 16,2006
`
`Sheet 5 of 19
`
`US 7,046,779 B2
`
`500
`
`\ @
`
`DETERMINE LOCATIONS) OF AND
`FOR CONFERENCE PARTICTPANTS
`
`IDENDEY EQLMRMENT AND
`DATA RARTKHPANTS
`
`IN HUB OR STAHON OF
`
`FOR EACH SCHEDUUNC PROCESS
`
`THE PLANNED CONFERENCE
`
`502
`
`504
`
`506
`
`508
`
`REQUEST RESERVAHON
`OE CAPABHJNES
`
`REQUEST HONORED?
`
`Y
`
`\51o
`
`N
`
`T
`
`7
`
`N 5”
`
`Y
`
`37 4
`
`SUCCESSFUL?
`
`Y
`
`516
`
`
`
`RECOMMEND
`ALTERNATE
`CONFERENCE
`
`
`
`@ ‘W
`
`FIG. 5
`
`Page60f41
`
`Page 6 of 41
`
`

`
`U.S. Patent
`
`May 16,2006
`
`Sheet 6 of 19
`
`US 7,046,779 B2
`
`600 \
`
`602
`
`
`
`i
`
`,
`
`1
`
`FOR EACH RESERVED CAPABELITY
`
`T
`
`Y
`
`MEETS REQUTREMENTS?
`
`N
`
`604
`
`FOR EACH ALTERNATIVE
`
`
`
`606
`
` 614
`
`Y
`
`616
`
`N
`
`REVISTON OK’?
`
`Y
`
`CANCEL RESER\/ATiON(S)
`
`618
`
`620
`
`NY
`
`FIG. 6
`
`J
`
`Page 7 of 41
`
`Page 7 of 41
`
`

`
`U.S. Patent
`
`May 16,2006
`
`Sheet 7 of 19
`
`US 7,046,779 B2
`
`mom
`
`
`
`mzfiamo:m_>onmzfiam._.<_>_Z_¢NmziuEm:a_:om
`
`
`
`
`
`:mz<Emm§<E7:
`
`mi
`
`mmo:m_>
`
`
`
`NBmw_o:m_>m.E<:z_
`
`
`
`<\..o:
`
`fin30328
`
`
`
`Km_-mu.:Emzaaom
`
`mumm.E<$z_:
`
`:.Emzgaom
`
`
`
`EMmzo_E_.5mm5:/@2238
`
`mi
`
`INN
`
`Newmmazmimczoo
`
`Page 8 of 41
`
`Page 8 of 41
`
`
`
`
`
`
`
`

`
`U.S. Patent
`
`May 16,2006
`
`Sheet 8 of 19
`
`US 7,046,779 B2
`
`
`
`STATUS, REQUESTED, CONFIRMED, READY,
`
`
`
`
`
`
`
`IN-PROGRESS, RECONNECTING,
`
`COMPLETED, CANCELED
`
`FIG. 7B
`
`EQUIPMENT PLANS
`
`70-4
`
`TRANSIT TIME
`
`ALLOWANCE
`
`STATUS:
`
`REQUESTED, CONFIRMED,
`
`COMPLETED, CANCELED
`
`FIG. 7C
`
`Page 9 of 41
`
`Page 9 of 41
`
`

`
`U.S. Patent
`
`May 16,2006
`
`Sheet 9 of 19
`
`US 7,046,779 B2
`
`EQUIPMENT
`
`71 O
`
`ON—OFF LINE FLAG
`
`DATE~TIME BACK IN SERVICE
`
`DATE-TIME LAST TESTED
`
`MAXIMUM PERIOD
`
`BETWEEN TESTS
`
`FIG. 7D
`
`
`
`
`EQUIPMENT DESCRIPTIONS 776
`
`EQUIPMENT TYPE
`
`EQUIPMENT DESCRIPTION
`
`
`
`
`FIG. 7E
`
`718
`
`
` EQUIPMENT TESTS
`
`
`
`EQUIPMENT TYPE
`
`TEST PROCEDURES
`
`TEST PARAMETERS, LIMITS
`
`
`
`
`
`FIG. 7F
`
`Page 10 of 41
`
`Page 10 of 41
`
`

`
`U.S. Patent
`
`May 16,2006
`
`Sheet 10 of 19
`
`US 7,046,779 B2
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`TRANSIT T
`
`ME
`
`
`
`ALLOWANCE
`
`
`
`TRANSIT TIM E
`
`ALLOWANCE
`
`
`
`
`STATUS:
`
`REQUESTED, CONFRMED,
`
`COMPLETED, CANC
`
`
`
`
`STATUS:
`REQUESTED, CONFIRMED,
`
`COMPLETED, CANCELED
`
`FIG. 7G
`
`FIG. 7J
`
`
`
`
`
`
`VISITORS
`
`NAME
`
`AVAILABILITY
`
`71 4
`
`
`
`
`
`
`PERMITTED TYPE OF VISIT
`
`START DATE—TIME FOR
`
`RERMITTED VISIT
`
`END DATE—TIME FOR
`
`RERMITTED VISIT
`
`MINIMUM PERIOD
`
`BETWEEN VISITS
`
`FIG. 7K
`
`
`
`
`
`INMATE’S VISITORS
`
`722
`
`INMATE NAME
`
`VISITOR NAME
`
`RELATIONSHIP
`
`DATE—TIME OF LAST
`
`CONFERENCE
`
`
`
`
`
`
`
`
`
`V
`
`DATE—TIME LAST CI-IECI<——IN
`
`MAXIMUM PERIOD
`
`BETWEEN CHECI<—INS
`
`GUARD NAME
`
`FIG. 7H
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`ITINERARIES
`
`720
`
`NAME OR EQUIPMENT ID
`
`LOCATION OR VEHICLE
`
`
`
`TRANSPORT PURPOSE
`
`
`S ART DATE—TIME
`
`‘ END DATE~TIM
`
`FIG. 7I
`
`FIG. 7L
`
`Page 11 of 41
`
`Page 11 of 41
`
`

`
`U.S. Patent
`
`May 16,2006
`
`Sheet 11 of 19
`
`US 7,046,779 B2
`
`
`
`
`
`,
`
`
`
`
`
`
`CONTACTS
`
`724
`
`NAME
`
`ROLE:
`
`WSHOR,|NMAWL GUARD
`
`CONTACTINFORMAWON
`
`
`
`
`
`
`FIG. 7M
`
`TRANSW WMES
`
`726
`
`TRANSW FROM LOCAHON
`
`TRANSW TO LOCAWON
`
`TRANSW Tm%Ifi¢LOWANCE
`
`
`
`
`FIG. 7N
`
`Page 12 of 41
`
`Page 12 of 41
`
`

`
`U.S. Patent
`
`May 16,2006
`
`Sheet 12 of 19
`
`US 7,046,779 B2
`
`@ ’/
`
`800
`
`802
`
`804
`
`MAINTAIN TIME SYNCHRONIZATION
`
`AMONG PARTICIPANT STATIONS
`
`AT TIME OF CONFERENCE,
`SEND GREETING PACKET TO ALL
`
`
`
`CON FEREE STATION ADDRESSES
`
`806 \
`
`RECEIVE GREETING PACKETS FROM
`
`ADDRESSED TO THIS STATION
`
`OPERATI\/E PARTICIPANT STATIONS,
`
`RECEIVE, PREPARE AND PRESENT
`
`
`
`INFORMAT!O\I FROM CONFEREE
`
`STATION ADDRESSES PER RULES
`
`Y
`
`ACCEPT, FORMAT, AND SEND
`
`INFORI\/IATION FROM PARTICIPANT
`
`TO OTHER CONFEREE STATION
`
`ADDRESSES PER RULES
`
`CONFERENCE DURATION LAPSE’?
`
`N
`
`808
`
`8I0
`
`812
`
`FIG. 8
`
`Page 13 of 41
`
`Page 13 of 41
`
`

`
`U.S. Patent
`
`May 16,2006
`
`Sheet 13 of 19
`
`US 7,046,779 B2
`
`zo_.Sm_mmEz_
`
`mjammm
`
`$133::
`
`4mzz<:o
`
`<m
`
`.o:
`
`mmmm:/msm
`
`dzz<:o
`
`zo:<>Emmm
`
`
`
`ommm:zmzm
`
`_,@
`
`mxecom
`
`Smdzz<:o
`
`ozamoumm
`
`E
`
`mzo:/$0-,
`
`mzo:<>EBm
`
`O0C
`
`T)
`
`dilm.
`
`
`
`maaxoogEoom
`
`+\o©
`
`mn5xoo..ZO_250..
`
`
`
`mommfimaomm:m_>
`
`Page 14 of 41
`
`Page 14 of 41
`
`
`
`
`
`
`
`
`
`
`
`

`
`U.S. Patent
`
`May 16,2006
`
`Sheet 14 of 19
`
`US 7,046,779 B2
`
`
`
`VISIT REQUESTS
`
`REOUESTID
`
`VISITOR ID
`
`INIVIATE ID
`
`LO C) l\)
`
`
`
`LOCATION (OF VISITOR)
`
`LOCATION (OF INNIATE)
`
`BOOTH TYPE (EOR VISITOR)
`
`BOOTH TYPE (EOR INIVIATE)
`
`TYPE OF VISIT
`
`REQUESTED DATE-TIME
`
`REQUESTED DURATION
`
`REOUEST CREATED DATE—T|I\/IE
`
`DISPOSITION
`
`RESERVATION ID
`
`FIG. 9B
`
`Page 15 of 41
`
`Page 15 of 41
`
`

`
`U.S. Patent
`
`May 16,2006
`
`Sheet 15 of 19
`
`US 7,046,779 B2
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`LOCATION LOOKUPS
`
`904
`
`IJMS LOCATION ID
`
`LOCATION ID
`
`FIG. 9C
`
`BOOTH LOOKUPS
`
`906
`
`IJI\/IS BOOTH ID
`
`BOOTH ID
`
`FIG. 9D
`
`STATUS: REQUESTED, CONFIRMED
`
`FIG. 9E
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Page 16 of 41
`
`Page 16 of 41
`
`

`
`U.S. Patent
`
`May 16,2006
`
`Sheet 16 of 19
`
`US 7,046,779 B2
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`LOCATIONS
`
`9TO
`
`LOCATION ID
`
`TYPE OF ACCESS
`
`DESCRSPTION
`
`FIG. 9F
`
`RECORDTNG CHANNELS
`
`912
`
`CHANNEL ID
`
`RECORDING PORT
`
`FIG. 90
`
`AUDTO EOUTPMENT ED
`
`FIG. 9H
`
`
`
`
`
`
`
`
`
`
`
`
`Page 17 of 41
`
`Page 17 of 41
`
`

`
`U.S. Patent
`
`May 16,2006
`
`Sheet 17 of 19
`
`US 7,046,779 B2
`
`915,
`
`
`
`
`
`
`%CHANNEL'HMES
`
`CHANNELID
`
`DATE—-TIME SLOT
`
`FH3.
`
`SH
`
`
`
`
`
`BOOTH TIMES
`
`918
`
`
`
`
`
`
`
`BOOTH ID
`
`DATE—THV|E SLOT
`
`FH3.
`
`SBJ
`
`RESERVATION EVENTS
`
`92O
`
`RESERVATION ID
`
`STATE
`
`POSTED DATE-TIME
`
`FTG.
`
`53K
`
`
`
`
`
`
`
`Page 18 of 41
`
`Page 18 of 41
`
`

`
`U.S. Patent
`
`May 16,2006
`
`Sheet 18 of 19
`
`US 7,046,779 B2
`
`
`
`
`
`
`
`
`
`CHANNEL EVENTS
`
`922
`
`CHANNEL ED
`
`STATE
`
`POSTED DATE-TIME
`
`FIG. 9L
`
`BOOTH EVENTS
`
`924
`
`BOOTH TD
`
`STATE
`
`POSTED DATE——TlME
`
`FIG. 9M
`
`
`
`
`
`
`
`
`
`Page 19 of 41
`
`Page 19 of 41
`
`

`
`U.S. Patent
`
`May 16,2006
`
`Sheet 19 of 19
`
`US 7,046,779 B2
`
`
`
`FOR EACH RARTICIPANT IN A CONFERENCE REQUEST
`
` 10
`
`D2
`
`IOO4
`
`IOO6
`
`
`
` FORM A CANDIDATE TABLE OF TIMES
`BEGINNING WIT!-I START DATZ—TIME
`
`
`
`FORM AN AVAILABILITY TABLE B
`INTERSECTION OF CANDIDATE TABLE
`
`
`
`AND UNAVAILABLE TIMES
`
`
`UNTIL ALL PARTICIDANTS CONSIDERED
`
`
`
`IOIO
`
`
`
`FORM OPPORTUNITY TABLE BY
`INTERSECTION OF ALL AVAILABILITY TABLES
`
`OFDORTUNITY EXISTS ?
`
`IOI4
`
`N
`
`
` CONFIRMED ?
`
` DENY REQUEST
`GRANT REQUEST
`
`I022
`
`Page 20 of 41
`
`Page 20 of 41
`
`

`
`US 7,046,779 B2
`
`1
`VIDEO CONFERENCE SYSTEM AND
`METHODS FOR USE AT MULTI-STATION
`SITES
`
`FIELD OF THE INVENTION
`
`Embodiments of the present invention relate to video
`conference systems and methods of operation of video
`conference systems.
`BACKGROUND OF THE INVENTION
`
`In a conventional video conference system, the partici-
`pants may be notified to attend the conference at particular
`locations. Each location typically has one installed video
`conference facility including for example microphones,
`cameras, and network links for communication to several
`other
`similar
`facilities. The communication typically
`includes audio and video signals used to support business
`conversation, business graphics, and eye contact among the
`participants. If a participant arrives at a proper location for
`the scheduled video conference and for any reason the
`conference cannot proceed, no provision is made for making
`a best efforts attempt at accomplishing a business purpose of
`the video conference.
`
`Without systems and methods according to various
`embodiments of the present invention, attempts at using
`video conferencing will continue to result in frustration in
`some cases because the underlying business purposes or
`personal purposes for the conference can be frustrated. The
`difficulty in establishing a value for the loss or damage to
`business relationships due to unreliable conventional video
`conferencing systems does not make unreasonable the asser-
`tion that unsatisfactory video conferencing may have enor-
`mous effects on those who rely on video conferencing for
`business relationships. Also, by reducing factors that con-
`tribute to unreliable video conferencing, future use of video
`conferencing according to the present invention may expand
`to meet new applications.
`SUMMARY OF THE INVENTION
`
`A prisoner visitation system according to various aspects
`of the present invention includes a prisoner information
`system, a conference control station, a visitation site, and a
`prisoner site. The prisoner information system and all other
`stations of the system are coupled to a network for commu-
`nication. The visitation site includes a first station used by a
`first conference coordinator and a first plurality of confer-
`ence participant stations. The prisoner site includes a second
`station used by a second conference coordinator and a
`second plurality of conference participant sites. A confer-
`ence is scheduled by an administrator who operates the
`conference control station. Prisoners and visitors have iden-
`
`tifiers maintained in the prisoner information system by a
`supervisor. The first station provides a first notice of the
`conference to the first coordinator for assuring that a named
`prisoner participates at a station of the first plurality as
`identified in the first notice. The second station provides a
`second notice of the conference to the second coordinator
`
`for assuring that a named visitor participates at a station of
`the second plurality as identified in the second notice.
`By arranging conference participation stations in a mul-
`tiplicity at each site, use of an alternate conference partici-
`pation station in the event of failure of a scheduled confer-
`ence participation station can be automatically arranged and
`coordinators may be given notice to direct users to appro-
`priate stations.
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`2
`
`A conference system according to various aspects of the
`present invention includes a network, a plurality of partici-
`pant stations, and a control station. All stations are coupled
`to the network for communication. The plurality is arranged
`with at least one site having a multiplicity of participant
`stations. The control station provides a notice to a participant
`that directs the participant to a particular participant station
`of the multiplicity for participating in a conference.
`The conference may be a scheduled conference. The
`conference may be a video conference. The participant
`stations of the multiplicity may be functionally equivalent
`having a camera, a microphone, a video display, and an
`audio speaker.
`By scheduling use of a participant station, maximum use
`of the participant station may be obtained. By scheduling
`several conferences by the same participant in back to back
`order using the same participant station, increased conve-
`nience to the participant may result. Use of a notice to direct
`the participant to a suitable station increases utilization of
`participant stations and reduces confusion when a partici-
`pant station fails before or during a conference—direction to
`an alternative station may be given in a timely manner.
`A participant may use a conference system for a sched-
`uled conference according to various aspects of the present
`invention by selecting one of a multiplicity of co-located
`participant stations,
`identifying himself or herself to the
`participant station, and participating in the conference using
`the selected participant station. Identification may be by
`login, usemame, password, by thumb print, or by operation
`of a control station by a coordinator who ascertains the
`identification and associates the participant with a partici-
`pant station.
`A conference system according to various aspects of the
`present invention includes a plurality of hubs. Each hub is
`coupled to a network for communication. Each hub couples
`a multiplicity of participant stations to the network. Each
`hub comprises a processor that refers to a time of day for
`initiating a conference among participant stations, wherein
`multiple hubs take action to initiate each conference.
`By each hub initiating action for one conference, a single
`point of control for initiating a conference is avoided. Higher
`reliability may result from use of conference systems that
`implement this architecture.
`A method for
`
`BRIEF DESCRIPTION OF THE DRAWING
`
`Embodiments of the present invention will now be further
`described with reference to the drawing, wherein like des-
`ignations denote like elements, and:
`FIG. 1 is a functional block diagram of a video confer-
`encing system according to various aspects of the present
`invention;
`FIG. 2 is a data flow diagram for processes performed by
`the system of FIG. 1;
`FIG. 3 is a functional block diagram of an implementation
`of the video conferencing system of FIG. 1;
`FIG. 4 is a functional block diagram of a switch used in
`the video conferencing system of FIG. 3;
`FIG. 5 is a process flow diagram of a method for making
`a reservation according to various aspects of the present
`invention;
`FIG. 6 is a process flow diagram of a method for revising
`reservations according to various aspects of the present
`invention;
`FIGS. 7A through 7N present a class diagram of a
`database used in the system of FIGS. 1 and 2;
`
`Page 21 of 41
`
`Page 21 of 41
`
`

`
`US 7,046,779 B2
`
`3
`FIG. 8 is a process flow diagram of a method for con-
`ducting a conference according to various aspects of the
`present invention;
`FIGS. 9A through 9M present a class diagram of database
`used in the system of FIGS. 1 and 2; and
`FIG. 10 is a process flow diagram of a method for
`scheduling a conference according to various aspects of the
`present invention.
`
`DETAILED DESCRIPTION OF THE
`PREFERRED EMBODIMENTS
`
`A video conference generally allows each human partici-
`pant to hear other participants talk and allows each partici-
`pant to see each other participant, for example, while that
`participant is speaking. The video conference may include
`presentations of audio and video programming (e.g., a
`photograph, a slide show, business graphics, an animation, a
`movie, or sound recordings) for some or all participants.
`Participants generally participate in a conference from
`physically separate locations—each such location in com-
`munication with the others via a conventional network that
`
`supports audio, video, and presentations. According to vari-
`ous aspects of the present invention, a video conference may
`substantially achieve an original purpose for conducting the
`video conference in spite of changes in the availability of
`participants (e.g., human participant or equipment partici-
`pant), particular video conference stations, and particular
`communication links. For example, video conference sys-
`tem 100 of FIGS. 1—2 includes communication network 101;
`conference control stations 102; general purpose stations
`103; conference participant stations 104; hubs 108; and
`conference participant stations 105 and 106 coupled to hub
`108 by links 109.
`A network provides signal communication via links
`between stations or sites. Signals may be analog or digital.
`Network topology may correspond to local area networks,
`wide area networks, wireless networks, and combinations
`including gateways and routers. For example, network 101
`includes conventional hardware at each station (e.g., net-
`work interface cards) and for each link (e.g., cables, routers,
`or wireless equipment). Network 101 includes conventional
`software providing data transfer among processes and stor-
`age devices located anywhere in system 100. Access to
`particular processes and to particular data (e.g., files, direc-
`tories, or storage devices) may be restricted (e.g., using
`access control
`lists, user accounts, or operating system
`partitions). Network 101 may carry audio and video in
`suitable digital packets. Or, network 101 may include (e.g.,
`in addition to or in place of digital communication) portions
`of its analog bandwidth for carrying analog signals that
`convey charmels of audio and channels of video using any
`conventional network technology.
`Each site of system 100 may include any number of
`stations. A site is an arbitrary grouping of stations organized
`within a physical boundary, within a political organization,
`for convenience of installing system components, or for
`achieving system budgets or efficiencies with hubs in par-
`ticular areas. Alternate implementations include any number
`of sites and any number of stations per site. A portable
`station may be temporarily added to network 101 to meet
`demand for system functions. For example, if a participant
`is unexpectedly located away from other stations (e.g., in a
`vehicle,
`in a confinement zone, or in a medical area), a
`portable station may be located anywhere access to network
`101 (e.g., access to a hub 108 or any link 101) may be gained
`by wired or wireless techniques.
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`4
`
`Users of system 100 include supervisors 113, administra-
`tors 114, local coordinators 115, and human participants 116.
`A single person may use system 100 in multiple roles.
`Typically, a person that uses system 100 as a human par-
`ticipant does not perform any other of these roles. Supervi-
`sors enter and maintain descriptions of participants includ-
`ing the location of participants. Administrators schedule
`conferences as requested by human participants. Coordina-
`tors are generally located in a convenient vicinity of stations
`used by participants. Coordinators may relocate and config-
`ure equipment participants and notify human participants. A
`coordinator assists participants (e.g., as an escort or recep-
`tionist) in getting to particular locations for scheduled con-
`ferences.
`
`Different business rules may apply to human participants
`using video conferencing system 100. A business rule
`includes any implementation for controlling use of system
`100 (e.g., network connectivity, user accounts, access con-
`trol lists, use of particular protocols, registration of users,
`privileges of persons to act as users 113—116 during speci-
`fied periods, privacy of conferences from each other, record-
`ing of conferences, and identification of participants). For
`example, system 100 may be used with various business
`rules to support conferences involving prisoners, business-
`men,
`students, educators, officers, constituents, clergy,
`parishioners, group leaders, and group members, to name a
`few representative environments.
`A video conference generally may be scheduled in
`advance of beginning the conference so that communication
`links (e.g., 101 and 109) are established in an orderly fashion
`and so that equipment and human participants will be
`available at designated locations (e.g., particular perma-
`nently installed conference participant stations). When the
`location of at least some of the participants is known, notice
`of the video conference and where to go to participate may
`be conveyed personally in any conventional manner to those
`participants. Other participants may be informed indirectly:
`(a) by giving a message to a coordinator; and/or (b) by using
`communication less direct than face-to-face (e.g., by con-
`veying a message by mail, telephone, voicemail, or email).
`The location that a particular participant may be directed to
`may be a location having numerous video conferencing
`stations (e.g., a multiple station site). The notice or message
`may specify a particular video conferencing station. By
`analogy, equipment (e.g., computer systems, any signal
`source, any signal recorder, or data item) may be scheduled
`and notified to participate in a video conference. If a
`particular human participant or a particular equipment is not
`free to relocate itself (or be available via any conventional
`communication) to a suitable physical location, notice may
`be provided to a coordinator (e.g., guard, escort, reception-
`ist, custodian, or equipment manager).
`Stations 102—106 include conventional network inter-
`
`faces, processors (e.g., conventional computer and micro-
`computer circuits), data storage devices, audio and video
`devices, and suitable signal processing circuitry arranged to
`perform functions and methods of the present invention.
`Conference participant stations 104—106 support participa-
`tion in a conference by, among other things, displaying
`video images, providing sound, picking up sound, and
`picking up visual images. Other functions are reserved to
`other stations for security reasons or to reduce the complex-
`ity and cost of participant stations. A conference participant
`station includes any equipment sufficient for a participant to
`participate in a conference. For example, a video conference
`station for a human participant includes a camera, a video
`monitor, a microphone, and a speaker. Any conventional
`
`Page 22 of 41
`
`Page 22 of 41
`
`

`
`US 7,046,779 B2
`
`5
`interface technology may be used in an alternate implemen-
`tation that accepts user input for computation or control
`purposes, for example, the monitor may further include a
`touch-screen interface,
`the station may have a sensor to
`detect that a person is ready to use the station (e.g., prox-
`imity switch), the microphone may have voice recognition
`capability (e.g., to distinguish “yes” and “no” in various
`languages), the speaker and microphone may be part of a
`conventional telephone handset that operates a hook switch,
`or a keypad or keyboard may be included. The station may
`further include a personal computer for voice recognition,
`dual
`tone multiple frequency signals (DTMF) decoding,
`local processing functions (e.g., menu functions or screen
`displays and controls), or use as a conventional office
`workstation.
`
`Particular advantages are realized in systems according to
`various aspects of the present invention by implementing a
`participant station in a manner suitable for use by abusive
`users (e.g., prisoners). Such a station may include a video
`camera and flat screen LCD monitor installed behind a
`
`protective window; and, a telephone handset for microphone
`and speaker mounted with a hook switch. The hook switch
`provides a signal
`indicating that a participant intends to
`begin participating, continue participating, or discontinue
`participating in a conference. The LCD monitor may provide
`video from a camera or cameras at other participating
`stations as well as screens for instructions on operation of
`the station.
`
`A conference control station supports making reservations
`for conferences, revising reservations for conferences, can-
`celing reservations for conferences, and keeping records of
`conferences. In addition, a conference control station may
`provide a data entry/edit interface for managing descriptions
`of participants including data that may be needed for a
`presentation during a conference. For example, conference
`control stations 102 include conventional computer work-
`stations for database management and include audio and
`video capabilities for participating (e.g., as an observer) in
`any conference (e.g., for security or troubleshooting pur-
`poses).
`General purpose stations 103 may perform any mix of
`functions described above with reference to conference
`
`control stations 102 and conference participant stations 104.
`Alternative implementations of system 100 include sys-
`tems having general purpose stations for all users (hubs 108
`and stations 102 and 104—106 omitted); systems having a
`mix of conference control stations 102 and conference
`
`participant stations (any combination of stations 104—106,
`hubs 108 being omitted where stations 105—106 are not
`included); systems having a mix of stations 102 and 103
`(hubs 108 and stations 102 and 104—106 omitted); and
`systems having a mix of conference control stations 102 and
`conference participant stations (any combination of stations
`104—106, hubs 108 being omitted where stations 105—106
`are not included).
`A hub provides a communication interface between a
`network link and each of a plurality of point-to-point links.
`The communication may provide security (e.g., encryption,
`fire wall functions, time locks). For example, one particular
`hub of hubs 108 provides communication between a con-
`ference participant station 105 and any other station of
`system 100 via network 101. Each station 105—106 is
`coupled to the particular hub of hubs 108 by an individual
`point-to-point link 109. Network 101 is coupled to each hub
`of hubs 108 via a link 101. In a preferred implementation, a
`hub includes a processor that, among other things, controls
`components and participant stations. In such an implemen-
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`6
`stations may operate as
`tation, conference participant
`peripherals (e.g., dumb I/O devices) of such a processor.
`Consequently, processing capabilities of components and
`participant stations may be reduced or eliminated. Further,
`such a processor may perform part or all of the operations
`suitable for supporting use by users 113—116 as discussed
`above, for example, as within a local context of conference
`participant stations 105—106.
`A conference system architecture according to various
`aspects of the present invention provides scalable expansion,
`redundancy, monitored system capabilities, responsive con-
`ference rescheduling, and distributed resources. A system
`architecture is a plan by which system functions are made
`the responsibility of particular processes or components for
`efficient performance of system functions and for efficient
`communication among processes. The system architecture is
`systematically applied as implementations of the system are
`developed and expanded. Systems employing this architec-
`ture solve the problems and provide the benefits discussed
`above, expand and contract without disruption of services,
`and exhibit extraordinary reliability.
`For example, system architecture 200 of FIG. 2 includes
`describe participants process 202, schedule conference pro-
`cess 204, conduct conference process 210, select and con-
`figure equipment process 212, network I/O (i.e.,
`input/
`output) process 214, provide notices process 216, equipment
`and data participants 218, monitor participant availability
`process 220, and reschedule or cancel conference process
`222. System architecture 200 is not restricted to particular
`details of any physical implementation. For example, any
`number of processors may perform the processes listed
`above. These processes may be implemented using conven-
`tional distributed processing technology (e.g., remote pro-
`cedure call, client-server, or parallel processing). Such pro-
`cessors may be located centrally or grouped with instances
`of equipment 218. Processes 210, 212, and 220 may be
`performed in a processor of a hub. Processes 214, 216, and
`222 may be performed in a processor of a hub. Data stores
`206 and 208 may be separate or combined. A processor of
`a control station may perform processes 202, 204, 222, 214,
`and 216. In alternate implementations a first control station
`may perform process 202, a second may perform process
`204, and a third (e.g., a self-service kiosk in a visitors’
`lobby) may perform an identification confirmation portion of
`process 210 and processes 214 and 216. Data flows illus-
`trated in FIG. 2 by arrows may be implemented by common
`access to memory or storage of one processor, or by access,
`bus, or network links between processors.
`Generally, a conference participant station designed for
`use by an individual employs one set of equipment 240—246
`for exclusive use by one human participant. Such a personal
`conference participant station may provide exclusive use of
`(or a thread for) one of each of processes 210—216 and 220.
`All threads for one participant may be performed on a single
`processor to avoid supporting a multiple thread execution
`environment. Alternative implementations may host several
`threads for a number of personal conference participant
`stations on a single processor, for example, made part of a
`hub 108 serving stations 105—106.
`Data used by processes of architecture 200 may be
`organized and stored in any conventional manner. Particular
`synergies are realized in systems according to various
`aspects of the present invention by storing participant loca-
`tions and rules 206 on storage maintained for use primarily
`by supervisors (e.g., access and edit privileges), providing
`limited access (e.g., read only) to administrators, and pro-
`viding barriers to access (e.g., no authorized means of
`
`Page 23 of 41
`
`Page 23 of 41
`
`

`
`US 7,046,779 B2
`
`7
`access) by participants 116, 218 and coordinators 115.
`Additional synergies are realized by storing conference
`plans 208 on storage maintained for use primarily by admin-
`istrators (e.g., access and edit privileges), providing limited
`access (e.g., read only) to coordinators 115, and providing
`barriers to access (e.g., no authorized means of access) by
`participants 116, 218.
`Data storage may be centralized or distributed (e.g.,
`mirrored, shadowed, redundant, or controlled by a directory
`service of the type marketed by Microsoft as Active Direc-
`tory or by Novell as Network Directory Service). Distrib-
`uted storage may include physical storage in any stations
`102-106 and hub 108.
`
`Adescribe participants process 202 maintains information
`about people, equipment, and data that may be designated as
`participants in one or more conferences. Such information
`may include suitable unique identification (e.g., name, serial
`number, path name), role of human participant,
`type of
`equipment for equipment participant, contact and other
`information to locate or make available the participant at a
`particular location, and rules for scheduling and conducting
`conferences. Describe participants process 202 may coop-
`erate with storage for participant locations and rules 206 to
`perform all conventional functions of a database manage-
`ment system. Data from participant locations and rules 206
`may be provided (e.g., to processes 204, 210, and 220) as a
`report, a response to a query, or by reference to a suitable
`index. Process 202 provides a conventional user interface
`for use by supervisors 113.
`A schedule conference process 204 creates, revises, and
`deletes records stored in a database of conference plans 208
`to establish a conference to be held at a date and time in the
`
`future. Conference plans may be maintained as a record of
`conferences completed (successfully through expected dura-
`tion, or otherwise unsuccessfully) or cancelled. Rules
`referred to by process 204 from store 206 may limit par-
`ticipation in conference plans to described participants gen-
`erally or to qualified participants (e.g., having particular
`attributes, prior registration, or approval). Qualification may
`be established by any conventional work flow or work group
`software. Process 204 provides a conventional user interface
`for use by administrators 114.
`For each scheduled conference, conference plans 208 may
`include a unique conference identifier, a list of equipment (if
`any) needed at each site, station, or location; a list of
`participants and stations identifying which station each
`participant is to use (e.g., one or more participants at each
`identified station); a start date and time for the conference;
`an ending date and time for the conference; and status
`information posted by monitor participant availability pro-
`cesses 220. Conference plans 208 may include information
`for establishing links between participant stations via net-
`work 101,
`for example,
`identifiers (e.g., port numbers,
`network addresses, world wide port names) that define links,
`routes, gateways, and pa