Page 1 of 42
`
`SECURUS EXHIBIT 1008
`
`

`
`Patent Application Publication
`
`&
`
`30
`
`910.10
`
`SU
`
`00
`
`M
`
`
`
`u.mozmmmczoomozmmmczoo
`
`moT\
`
`Q:
`
`m.
`
`
`
`zocémKE/&_o_E<n_E<n__o_,E<a
`
`S9:\\\
`
`1X
`
`m_.0:
`
`
`#53mmE<Em_z;S<mmom.>E%mZ<§DImmozzamoouW.%\\@:\m:sly:\\»m:Nm+z<&o_E<a
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`zo:/im...ma:...E<n5_E<ammoméizo:/fimzocfimSE289:mozmmmczoo4<E_/momozmmfizoomo.
`
`
`
`
`
`
`
`
`
`:8
`
`0o
`
`aP
`
`g
`
`24£102e
`
`Page 2 of 42
`
`
`

`
`MP
`
`b
`
`0
`
`1A6200
`
`.mmozmmfizoo
`
`m.doz/6mo%.u._59%Emma
`
`
`x._oZ.$H_:.EZOoM.mmmE3813m3m¢:mmo2Em,z:\S<L:mmom_>$%m
`
`.mmommmz/jg
`
`ommozmmfizoom:/_<¢_o_E<a
`nmommmabmmg
`
`t:/_<¢_o_EQI!mmo:zo2‘oimzo:¢omo_:
`m_#N<E_2<o
`ommm:IMmmozzamooommmEamoommm.209#3EEE mo\_xmogbz\W4:\N
`
`SIiwmmEEEmoflozm9>omn_
`
`
`oo.E:_m_<g<©<miEvzfimgo»/_w.fim_m_w_vmo
`Smfism.zo:/$3
`
`nE<¢_o_E/E
`
`gmmoczoz89>
`
`Sm
`
`Um__&E05SE
`
`/mt/_<n__o_E,&<29Qz<Hzmzgaom3::fi_>_n::omMz<2::llmmaozzoo
`
`M.1!ul.Mo:Emm:/_<¢_o_E<gNo_.._Sm
`
`
`
`SOmmmm:_:_OW_;rZO0QZ<%Qm_v_m_m\\\IOON
`
`Page 3 of 42
`
`Page 3 of 42
`
`
`
`

`
`Patent Application Publication
`
`Sep. 18, 2003 Sheet 3 of 19
`
`US 2003/0174826 A1
`
`r ------------- —“fi
`[COURT 310
`
`r*‘”—‘7
`
`L6
`
`CONTROL
`
`STATION
`
`MANAGEMENT
`
`SYSTEM
`
`T
`
`Page 4 of 42
`
`Page 4 of 42
`
`

`
`1A
`
`_
`
`..m_wowooh“
`
`a_
`
`m_ZiaN3»mow
`
`,7wm.1II
`
`«MIMI_w_Id,_h_lmg_S__3__0_mimm_EUH__1_Imflwu
`mIIIIIII.MIIIIIIII0E_m"Eemoomm_W_dz./2:0mmtiéfi_m.,IE3:Ev_S.q.Q___U___._'_9II_m__I‘ImtaomamoiN__M_amt
`oZzoEQzoo
`oz_zoEozoo._m_4<zo_mOBVKII_S_
`
`0534.
`
`___,
`
` u_:3P__IIIS.m_I_EjoEzoo»mafia?/____m_mo/:%_z_1¢\mg_W__VEQEZ_moié_2M_N3
`
`mmmma:_4tN?-IIKLMn_IIIIIm_II
`IIII5aePM.
`
`P
`
`Page 5 of 42
`
`
`
`

`
`Patent Application Publication
`
`Sep. 18, 2003 Sheet 5 of 19
`
`US 2003/0174826 A1
`
`5OO \ @
`
`DETERMINE LOCATION(S) OF AND
`FOR CONFERENCE PARTICIPANTS
`
`IDENTIFY EQUIPMENT AND
`DATA PARTICIPANTS
`
`FOR EACH SCHEDULING PROCESS
`IN HUB OR STATION OF
`THE PLANNED CONFERENCE
`
`
`REQUEST RESERVATION
`OF CAPABILITIES
`
`REQUEST HONORED?
`
`502
`
`5OZI
`
`506
`
`508
`
`N
`
`Y
`
`514
`
`N
`
`Y
`
`516
`
`RECOMMEND
`ALTERNATE
`
`CONFERENCE
`
`FIG. 5
`
`Page 6 of 42
`
`Page 6 of 42
`
`

`
`Patent Application Publication
`
`Sep. 18, 2003 Sheet 6 of 19
`
`US 2003/0174826 A1
`
`\ @
`
`600
`
`602
`
`FOR EACH RESERVED CAPABILITY
`
`Y
`
`604
`
`MEETS REQUIREMENTS?
`
`N
`
`606
`
`FOR EACH ALTERNATIVE
`
`608
`
`AVAILABLE?
`
`N
`
`610
`
`Y
`
`REsERVATIoN(s)
`CAN BE REVISED?
`
`
`
`612
`
`Y
`
`REVISE RESERVATlON(S)
`
`I
`
`D-'
`
`Y
`
`N W
`
`Y
`
`616
`
`N
`
`REVISION OK?
`
`CANCEL RESERVATION(S)
`
` I8
`
`6
`
`Page 7 of 42
`
`Page 7 of 42
`
`

`
`wS
`
`S
`
`w
`
`Um3002
`
`1A
`
`
`
`
`
`amm»mmo:m_>mm.:<2z_
`
`.mti
`
`M..Q»<\.OE
`
`
`
`ME»mzocgmommaE/E_2m_30m
`
`
`
`SIIIll‘.U§mbfizoomi8%.:Emzgafi
`
`mi
`
`
`
`Nonmmozmmmzzoo
`
`Page 8 of 42
`
`
`
`mm»:mz<E
`
`N:1mE<:z_
`
`
`
`3:1!!!IIImQ.mm§<EzEoiFzmzgsomm
`
`91:
`
`mo
`
`
`
`mzfiamo:m_>
`
`on
`
`
`
`
`
`mZ<.EmH<_>_Z_E»mZ<»Ec/_m_:a_:8
`
`PatentApplicationPublication
`
`Page 8 of 42
`
`
`
`
`
`
`
`

`
`Patent Application Publica '“On
`
`
`
`Sep. 18 2003 Sheet 8’
`
`Of 19
`
`US 2003/017482 6 A1
`
`E —
`
`TRANSIT TH\/\E
`ALLOWANCE
`
`F|G. 7C
`
`Page 9 of 42
`
`EQUHDMENT PLANS
`
`704
`
`PART|ClPANT RANK
`
`NEEDED AT LOCAT\ON
`
`Page 9 of 42
`
`

`
`Patent Application Publication
`
`Se
`
`1’
`
`1. 8,2003
`
`Sheet 9 of 19
`
`US 2003/0174826 A1
`
`
` EQUIPMENT
`
`
`
`
`
`
`EQUIPMENT TYPE
`
`CURRENT EQUIPMENT LOCATION
`
`AVAILABILITY
`
`
`
`ON—OFF LINE FLAG
`
`DATE—TIME BACK IN SERVICE
`
`DATE~TIME LAST TESTED
`
`
`
`
`
`
`MAXIMUM PERIOD
`BETWEEN TESTS
`
`FIG. 7D
`
`EQUIPMENT DESCRIPTIONS 716
`
`EQUIPMENT TYPE
`
`EQUIPMENT DESCRIPTION
`
`
`
`
`
`FIG. 7E
`
`
`
`
`
`FIG. 7F
`
`
`
`
`
`
`
`
`
`
`
`
`
`Page 10 of 42
`
`Page 10 of 42
`
`

`
`Patent Application Publication
`
`Sep. 18, 2003 Sheet 10 of 19
`
`US 2003/0174826 A1
`
`I
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`TRANSIT T
`
`ME
`
`
`
`ALLOWANCE
`
`STATUS:
`
`REQUESTED, CONFRMED,
`
`COMPLETED, CANC
`
`
`
`
`
`TRANSIT TIM E
`
`ALLOWANCE
`
`STATUS:
`
`REQUESTED, CONFIRMED,
`
`COMPLETED, CANCELED
`
`FIG. 7G
`
`FIG. 7J
`
`71 4
`
`VISITORS
`
`NAME
`
`AVAILABILITY
`
`
`
`
`
`
`
`
`
`
`
`
`PERMITTED TYPE OF VISIT
`
`START DATE—TIME FOR
`
`RERMITTED VISIT
`
`END DATE—TIME FOR
`
`PERMITTED VISIT
`
`\/IINIMUM PERIOD
`
`BETWEEN VISITS
`
`FIG. 7K
`
`INMATE’S VISITORS
`
`722
`
`INMATE NAME
`
`VISITOR NAME
`
`RELATIONSHIP
`
`DATE—TIME OF LAST
`
`CONFERENCE
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`D ATE—TIME LAST CI-IECI<——IN
`
`
`
`MAXIMUM PERIOD
`
`BETWEEN CHECI<—INS
`
`GUARD NAME
`
`FIG. 7H
`
`ITINERARIES
`
`720
`
`NAME OR EQUIPMENT ID
`
`
`
`TRANSPORT PURPOSE
`
`
`S ART DATE—TIME
`
`LOCATION OR VEHICLE
`
`
`
`‘ END DATE—TIME
`
`
`
`
`
`
`
`FIG. 7I
`
`FIG. 7L
`
`Page 11 of 42
`
`Page 11 of 42
`
`

`
`Patent Application Publication
`
`Sep. 18, 2003 Sheet 11 of 19
`
`US 2003/0174826 A1
`
`CONTACTS
`
`724
`
`NAME
`
`
`ROLE:
`
`WSWOR,|NMAfl§ GUARD
`
`CONTACTINFORMAWON
`
`FIG. 7M
`
`TRANSH'1WMES
`
`TRANSW FROM LOCANON
`
`TRANSW TO LOCAWON
`
`TRANSH‘TWWE ALLOWANCE
`
`FIG. 7N
`
`Page 12 of 42
`
`Page 12 of 42
`
`

`
`Patent Application Publication
`
`Sep. 18, 2003 Sheet 12 of 19
`
`US 2003/0174826 A1
`
`800
`
`/
`
`802
`
`804
`
`806
`
`808
`
`810
`
`MAINTAIN TIME SYNCI-IRONIZATION
`AMONG PARTICIPANT STATIONS
`
`AT TIME OF CONFERENCE,
`
`SEND GREETING PACKET TO ALL
`
`CONFEREE STATION ADDRESSES
`
`RECEIVE GREETING PACKETS FROM
`
`OPERATIVE DARTICIPANT STATIONS,
`
`ADDRESSED TO THIS STATION
`
`RECEIVE, PREPARE AND PRESENT
`I FORMATION FROM CONFERE_
`
`STATION ADDRESSES PER RU_ES
`
`ACCEPT, FORMAT, AND SEND
`INFORMATION FROM PARTICIDANT
`
`ADDRESSES DER RULES
`
`TO OTHER CONFEREE STATION
`
`812
`
`N
`
`CONFERENCE DURATION LAPSE’?
`
`Y
`
`FIG. 8
`
`Page 13 of 42
`
`Page 13 of 42
`
`

`
`.m%
`
`0
`
`M2SU
`
`2
`
`1
`
`B08
`
`
`
`3EdISmdzz/EummEomozamoomm
`
`
`
`
`
`9mbzmmmEm8::3mm__>_:.Hzo_5m_mm_Ez_Eoomdzz<:o
`
`M,3o_.._
`
`
`zo:<>EmE%1|:wNomt/.:._>:._ommm:/m_>mNdzz<:o
`
`
`Patent Application Publication
`
`WWS
`
`Bmzo:<o3
`
`ommzo:<>Emmm
`
`
`
`mommkmmaomm:m.>
`
`Page 14 of 42
`
`Page 14 of 42
`
`
`
`

`
`Patent Application Publication
`
`Sep. 18, 2003 Sheet 14 of 19
`
`US 2003/0174826 A1
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`REQUEST CREATED DATE—TII\/IE
`
`DISPOSITION
`
`RESERVATION ID
`
`FIG. 9B
`
`Page 15 of 42
`
`Page 15 of 42
`
`

`
`Patent Application Publication
`
`Sep. 18, 2003 Sheet 15 of 19
`
`US 2003/0174826 A1
`
`LOCATION LOOKUPS
`
`904
`
`I.JI\/IS LOCATION ID
`
`LOCATION ID
`
`FIG. 9C
`
`BOOTH LOOKURS
`
`906
`
`IJMS BOOTH ID
`
`BOOTH ID
`
`FIG. 9D
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`START DATE-TII\/IE
`
`DURATION
`
`RESERVATION CREATION DATE—TIME
`
`STATUS: REQUESTED CONFIRMED
`
`
`
`
`
`FIG. 9E
`
`
`
`
`
`
`
`
`
`
`Page 16 of 42
`
`Page 16 of 42
`
`

`
`.
`.
`.
`.
`Patent Appllcatlon Publlcatlon
`
`Sep. 18, 2003 Sheet 16 of 19
`
`1 4826 A1
`US 2003/0 7
`
`LOCATIONS
`
`LOCATION ID
`
`DESCRIPTION
`
`FIG. 9F
`
` RECORDING CHANNELS
`
`
`RECORDING PORT
`
`FIG. 9G
`
`BOOTHS
`
`BOOTH ID
`
`912
`
`
`
`
`9I4
`
`LOCATION ID
`
`VIDEO PORT
`
`BOOTH TYPE
`
`AUDIO PORT
`
`VIDEO EQUIPMENT ID
`
`AUDIO EQUIPMENT ID
`
`FIG. 9H
`
`Page 17 of 42
`
`Page 17 of 42
`
`

`
`Patent Application Publication
`
`Sep. 18, 2003 Sheet 17 of 19
`
`US 2003/0174826 A1
`
`
`
`ACHANNEL WMES
`
`CHANNELID
`
`DATE——TI I\/IE SLOT
`
`EH3. 9|
`
`916_
`
`
`
`BOOTH TIMES
`
`918
`
`
`
`
`
`
`BOOTH ID
`
`DATE—TII\/IE SLOT
`
`
`
`EH3. 9J
`
`RESERVATION EVENTS
`
`920
`
`
`
`
`
`RESERVATION ID
`
`STATE
`
`POSTED DATE—TIME
`
`FIG.
`
`SBK
`
`Page 18 of 42
`
`Page 18 of 42
`
`

`
`Patent Application Publication
`
`Sep. 18, 2003 Sheet 18 of 19
`
`US 2003/0174826 A1
`
`Page 19 of 42
`
`Page 19 of 42
`
`

`
`Patent Application Publication
`
`Sep. 18, 2003 Sheet 19 of 19
`
`US 2003/0174826 A1
`
`IOOO
`
`\
`
`
` I002
`
`
`
`I004
`
`I006
`
`
`
`FOR EACH PARTICIPANT IN A CONFERENCE REQUEST
`
`FORM A CANDIDATE TABLE OF TIMES
`BEGINNING WITH START DATE—TIME
`
`
`
`
`
`FORM AN AVAILABILITY TABLE BY
`INTERSECTION OF CANDIDATE TABLE
`
`AN D U NAVAI LABLE TIM ES
`
`
`
`UNTIL ALL PARTICIPANTS CONSIDERED
`
`
`
`FORM OPPORTUNITY TABLE BY
`INTERSECTION OF ALL AVAILABILITY TABLES
`
`
`
`
`
`FIG. 10
`
`Page 20 of 42
`
`OPPORTUNITY EXISTS '?
`
`I014
`
`FOR EACH ROW OF OPPORTUNITY TABLE
`
`
`
`CONFIRMED ?
`
`I016
`
`Y
`
`
`
`IOI8
`
`WHILE OPPORTUNITIES EXIST
`
`I020
`
`
`
`‘DENY REQUEST
`
`GRANT REQUEST
`
`
`
`I022
`
`
`
`Page 20 of 42
`
`

`
`US 2003/0174826 A1
`
`Sep. 18, 2003
`
`VIDEO CONFERENCE SYSTEM AND METHODS
`FOR USE AT MULTI-STATION SITES
`
`FIELD OF THE INVENTION
`
`invention relate to
`[0001] Embodiments of the present
`video conference systems and methods of operation of video
`conference systems.
`
`BACKGROUND OF THE INVENTION
`
`the
`In a conventional video conference system,
`[0002]
`participants may be notified to attend the conference at
`particular locations. Each location typically has one installed
`video conference facility including for example micro-
`phones, 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.
`
`[0003] 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
`
`[0004] A prisoner visitation system according to various
`aspects of the present invention includes a prisoner infor-
`mation 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
`communication. The visitation site includes a first station
`
`used by a first conference coordinator and a first plurality of
`conference 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.
`
`[0005] By arranging conference participation stations in a
`multiplicity at each site, use of an alternate conference
`participation station in the event of failure of a scheduled
`
`automatically
`conference participation station can be
`arranged and coordinators may be given notice to direct
`users to appropriate stations.
`
`[0006] A conference system according to various aspects
`of the present invention includes a network, a plurality of
`participant 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.
`
`[0007] 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.
`
`[0008] By scheduling use of a participant station, maxi-
`mum 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 convenience to the participant may result. Use of
`a notice to direct
`the participant
`to a suitable station
`increases utilization of participant stations and reduces con-
`fusion when a participant station fails before or during a
`conference—direction to an alternative station may be given
`in a timely manner.
`
`[0009] A participant may use a conference system for a
`scheduled 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, username, password, by thumb print, or by opera-
`tion of a control station by a coordinator who ascertains the
`identification and associates the participant with a partici-
`pant station.
`
`[0010] 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 confer-
`ence.
`
`[0011] 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.
`
`[0012] A method for
`BRIEF DESCRIPTION OF THE DRAWING
`
`[0013] Embodiments of the present invention will now be
`further described with reference to the drawing, wherein like
`designations denote like elements, and:
`
`[0014] FIG. 1 is a functional block diagram of a video
`conferencing system according to various aspects of the
`present invention;
`
`[0015] FIG. 2 is a data flow diagram for processes per-
`formed by the system of FIG. 1;
`
`Page 21 of 42
`
`Page 21 of 42
`
`

`
`US 2003/0174826 A1
`
`Sep. 18, 2003
`
`[0016] FIG. 3 is a functional block diagram of an imple-
`mentation of the video conferencing system of FIG. 1;
`
`[0017] FIG. 4 is a functional block diagram of a switch
`used in the video conferencing system of FIG. 3;
`
`[0018] FIG. 5 is a process flow diagram of a method for
`making a reservation according to various aspects of the
`present invention;
`
`[0019] FIG. 6 is a process flow diagram of a method for
`revising reservations according to various aspects of the
`present invention;
`
`[0020] FIGS. 7A through 7N present a class diagram of
`a database used in the system of FIGS. 1 and 2;
`
`[0021] FIG. 8 is a process flow diagram of a method for
`conducting a conference according to various aspects of the
`present invention;
`
`[0022] FIGS. 9A through 9M present a class diagram of
`database used in the system of FIGS. 1 and 2; and
`
`[0023] 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
`
`[0024] A video conference generally allows each human
`participant to hear other participants talk and allows each
`participant 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.
`
`[0025] 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 com-
`binations including gateways and routers. For example,
`network 101 includes conventional hardware at each station
`
`(e. g., network interface cards) and for each link (e. g., cables,
`routers, or wireless equipment). Network 101 includes con-
`ventional software providing data transfer among processes
`and storage devices located anywhere in system 100. Access
`to particular processes and to particular data (eg, files,
`directories, or storage devices) may be restricted (eg, 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 channels of audio and channels of video using any
`conventional network technology.
`
`[0026] Each site of system 100 may include any number of
`stations. Asite 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 (eg, in a
`vehicle,
`in a confinement zone, or in a medical area), a
`portable station may be located anywhere access to network
`101 (eg, access to a hub 108 or any link 101) may be gained
`by wired or wireless techniques.
`
`[0027] Users of system 100 include supervisors 113,
`administrators 114, local coordinators 115, and human par-
`ticipants 116. A single person may use system 100 in
`multiple roles. Typically, a person that uses system 100 as a
`human participant does not perform any other of these roles.
`Supervisors enter and maintain descriptions of participants
`including the location of participants. Administrators sched-
`ule conferences as requested by human participants. Coor-
`dinators are generally located in a convenient vicinity of
`stations used by participants. Coordinators may relocate and
`configure equipment participants and notify human partici-
`pants. A coordinator assists participants (e. g., as an escort or
`receptionist) in getting to particular locations for scheduled
`conferences.
`
`[0028] Different business rules may apply to human par-
`ticipants using video conferencing system 100. A business
`rule includes any implementation for controlling use of
`system 100 (eg, network connectivity, user accounts,
`access control lists, use of particular protocols, registration
`of users, privileges of persons to act as users 113-116 during
`specified periods, privacy of conferences from each other,
`recording 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.
`
`[0029] Avideo 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 (eg, 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 (eg, a multiple station site). The notice or message
`may specify a particular video conferencing station. By
`
`Page 22 of 42
`
`Page 22 of 42
`
`

`
`US 2003/0174826 A1
`
`Sep. 18, 2003
`
`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).
`
`[0030] Stations 102-106 include conventional network
`interfaces, processors (e.g., conventional computer and
`microcomputer 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
`participation in a conference by, among other things, dis-
`playing 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
`complexity 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 interface technology may be used in an alter-
`nate implementation 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.,
`proximity switch), the microphone may have voice recog-
`nition 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.
`
`[0031] 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 partici-
`pating, 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 instruc-
`tions on operation of the station.
`
`[0032] A conference control station supports making res-
`ervations for conferences, revising reservations for confer-
`ences, canceling 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 com-
`
`puter workstations for database management and include
`audio and video capabilities for participating (e.g., as an
`observer) in any conference (e.g., for security or trouble-
`shooting purposes).
`
`[0033] General purpose stations 103 may perform any mix
`of functions described above with reference to conference
`
`control stations 102 and conference participant stations 104.
`
`[0034] Alternative implementations of system 100 include
`systems 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).
`
`[0035] Ahub 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-
`tation, conference participant stations may operate as
`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.
`
`[0036] A conference system architecture according to
`various aspects of the present invention provides scalable
`expansion,
`redundancy, monitored system capabilities,
`responsive
`conference
`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 sys-
`tem architecture is systematically applied as implementa-
`tions of the system are developed and expanded. Systems
`employing this architecture solve the problems and provide
`the benefits discussed above, expand and contract without
`disruption of services, and exhibit extraordinary reliability.
`
`[0037] For example, system architecture 200 of FIG. 2
`includes describe participants process 202, schedule confer-
`ence process 204, conduct conference process 210, select
`and configure 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 confer-
`ence process 222. System architecture 200 is not restricted
`to particular details of any physical implementation. For
`example, any number of processors may perform the pro-
`cesses listed above. These processes may be implemented
`using conventional distributed processing technology (e.g.,
`remote procedure call, client-server, or parallel processing).
`
`Page 23 of 42
`
`Page 23 of 42
`
`

`
`US 2003/0174826 A1
`
`Sep. 18, 2003
`
`Such processors 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. Aproces-
`sor 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 illustrated 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.
`
`station
`participant
`conference
`a
`[0038] Generally,
`designed for use by an individual employs one set of
`equipment 240-246 for exclusive use by one human partici-
`pant. 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 imple-
`mentations may host several threads for a number of per-
`sonal conference participant stations on a single processor,
`for example, made part of a hub 108 serving stations
`105-106.
`
`[0039] 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
`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.
`
`[0040] 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 Directory or by Novell as Network Directory Ser-
`vice). Distributed storage may include physical storage in
`any stations 102-106 and hub 108.
`
`[0041] A describe 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 con-
`ducting conferences. Describe participants process 202 may
`cooperate with storage for participant locations and rules
`206 to perform all conventional functions of a database
`management 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.
`
`[0042] Aschedule 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 duration, or otherwise unsuccessfully) or can-
`celled. Rules referred to by process 204 from store 206 may
`limit participation in conference plans to described partici-
`pants generally or to qualified participants (e.g., having
`particular attributes, prior registration, or approval). Quali-
`fication may be established by any conventional work flow
`or work group software. Process 204 provides a conven-
`tional user interface for use by administrators 114.
`
`[0043] 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 confer-
`ence; 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 na