1111111111111111 IIIIII IIIII 111111111111111 lllll 111111111111111 lllll 111111111111111 11111111
`US 20160358017Al
`
`c19) United States
`c12) Patent Application Publication
`Guzik
`
`c10) Pub. No.: US 2016/0358017 Al
`Dec. 8, 2016
`(43) Pub. Date:
`
`(54)
`
`IN-VEHICLE USER INTERFACES FOR LAW
`ENFORCEMENT
`
`(71) Applicant: WHP Workflow Solutions, LLC,
`North Charleston, SC (US)
`
`(72)
`
`Inventor: Thomas Guzik, Edina, MN (US)
`
`(21) Appl. No.: 14/732,601
`
`(22) Filed:
`
`Jun. 5, 2015
`
`Publication Classification
`
`(51)
`
`Int. Cl.
`G06K 9/00
`G06F 3/048
`B60R 1100
`G08B 21102
`
`(2006.01)
`(2006.01)
`(2006.01)
`(2006.01)
`
`100~
`
`(52) U.S. Cl.
`CPC ....... G06K 9/00302 (2013.01); G06K 9/00342
`(2013.01); G06K 9/00711 (2013.01); G06K
`9/00832 (2013.01); G08B 21102 (2013.01);
`G06F 3/048 (2013.01); B60R 1100 (2013.01);
`B60R 2300/8006 (2013.01)
`ABSTRACT
`(57)
`User interfaces may be used by a law enforcement officer to
`communicate information to and obtain feedback from a
`person that is held in a secure holding area of a law
`enforcement vehicle. The user interfaces may be presented
`via hardware interfaces in the law enforcement vehicle and
`a computing device. The computing device may receive a
`request to present a user interface to a person in the secure
`holding area. Subsequently, the user interface for the person
`may be generated based on contextual information from one
`or more sources. These sources may include an input pro(cid:173)
`vided to the computing device by a law enforcement officer,
`an input received from a network operations center, or an
`input obtained from an analysis of images or videos from a
`camera in the law enforcement vehicle. The user interface is
`then presented to the person in the secure holding area.
`
`LAW
`
`OFFICER
`
`102(1)
`
`ENFORCEMENT
`VEHICLE
`
`8'-134!
`
`CONTENT
`MANAGEMENT
`\ _______________________ )
`ENGINE 132
`
`O
`PERATOR
`
`I
`:
`1
`
`LAW
`ENFORCEMENT
`VEHICLE
`
`TurnSignl - Exhibit 1027
`Page 1 of 17
`
`

`

`100~
`
`I I
`I
`:
`I
`1
`I
`1
`I
`I
`
`- -
`IN-VEHICLE-----------
`INFORMATION D
`EVICE
`104
`
`,
`112 ',
`'
`
`- - - - - - - - - - -
`08
`------
`
`EAKER
`S
`
`____ , ~ ETADATA
`]
`M
`1
`r--
`-,..__
`I ~ -
`I
`1
`
`COLLECTED
`
`2(N)
`
`LAW
`ENFORCEMENT
`VEHICLE
`
`'
`
`,
`
`' ,
`
`HARDWARE
`:
`FA
`I
`1
`INTER
`1
`I
`I
`I
`
`~--------~~- s
`
`o,
`
`--
`
`'
`
`' ,
`
`' 06
`',,
`
`O
`
`~
`
`I
`I
`CAMERA116:
`PERSON
`I
`I
`___________ j
`
`AW
`ENFORCEMENT 114
`L
`
`,(------
`
`OFFICER
`
`102(1)
`
`LAW
`ENFORCEMENT
`VEHICLE
`
`130 9- DAT
`
`128
`
`9VIDEO
`DATA
`
`124
`
`A
`'
`
`'
`
`"
`
`NETWORK OPERATIONS
`CENTER 120
`
`~ - - - - - - - - - - - - - - ,
`&134,
`
`122
`
`SERVERS
`
`OPERATOR
`
`I
`I
`I
`:
`I
`I
`I
`____ ,I
`
`CONTENT
`MANAGEMENT
`ENGINE 132
`
`LAW
`ENFORCEMENT
`VEHICLE
`
`FIG. 1
`
`""O
`~ .....
`
`('D = ..... t "e -....
`.... 0 =
`""O = O" -....
`.... 0 =
`c ('D
`
`(')
`
`~ .....
`
`(')
`
`~ .....
`
`~
`~CIO
`N
`
`0 ....
`
`O'I
`
`('D
`('D
`
`rJJ =(cid:173)
`.....
`....
`0 ....
`
`O'I
`
`c
`rJJ
`N
`0 ....
`O'I
`---0
`~
`Ul
`CIO
`0 ....
`> ....
`
`-....J
`
`TurnSignl - Exhibit 1027
`Page 2 of 17
`
`

`

`COMMUNICATION INTERFACE 2.Q2.
`
`I
`
`SENSOR(S) 2.Q1
`
`/
`
`(
`
`[
`
`)
`)
`/
`I
`(
`)
`/
`PROCESSOR(S) 206
`I ~ - - - - - - - - - - -~
`[
`' - - - - - - - - - - - - - - - - -)
`DEVICE HARDWARE 21.Q
`/
`I
`/
`MEMORY 208
`- - - - - - - - - ,,...-==-------
`I
`I
`I
`OPERATING SYSTEM
`APPLICATIONS
`I
`J
`212
`214
`
`IN-VEHICLE
`INFORMATION DEVICE \
`
`\
`
`\
`\
`\
`\
`\
`\
`\
`\
`
`IN-VEHICLE INFORMATION APPLICATION 21_6_
`INTERFACE SELECTION MODULE 218
`
`(
`
`INFORMATION
`MODULE
`220
`
`VIDEO
`MODULE 224
`
`INTERACTIVE
`INTERFACE
`MODULE 222
`
`DATA MANAGEMENT
`MODULE 226
`
`~================~ ::::===============::::
`
`DATA STORE 228
`- - - - - -~ - - - - - -~
`PRESENTATION
`INTERACTIVE
`DATA 230
`DATA 232
`
`[
`
`Co~NT
`
`]
`
`[ ME~TA
`
`]
`
`FIG. 2
`
`""O
`~ .....
`
`('D = ..... t "e -....
`.... 0 =
`""O = O" -....
`.... 0 =
`c ('D
`
`(')
`
`~ .....
`
`(')
`
`~ .....
`
`~
`~CIO
`N
`
`0 ....
`
`O'I
`
`('D
`
`rJJ =-('D
`.....
`N
`0 ....
`
`O'I
`
`c
`rJJ
`N
`0 ....
`O'I ---0
`0 ....
`> ....
`
`-....J
`
`~
`Ul
`CIO
`
`TurnSignl - Exhibit 1027
`Page 3 of 17
`
`

`

`Patent Application Publication
`
`Dec. 8, 2016 Sheet 3 of 6
`
`US 2016/0358017 Al
`
`In-Vehicle Information System - Interactive Interface Consent
`
`.~306
`
`11
`
`1 302
`
`- ~
`
`
`
`~
`
`~
`
`~ r304
`
`~
`
`By using this interface, you agree that the law enforcement
`officer has verbally informed of your Miranda rights, and you
`further agree that unless prohibited by law, any information
`you provide through the use of interface, or any
`communication with a third party through this interface, can
`constitute admissions that can be used against you in a
`court of law.
`
`AGREE
`
`DECLINE
`
`]
`
`308J
`
`3100
`
`<
`
`(
`
`)
`
`[L
`
`In-Vehicle Information System - Interactive Interface Selection
`
`312-
`
`314-
`
`316-
`
`318-
`
`~
`
`Contact an attorney
`
`~ Contact a family member/relative/friend
`~ Share your point of view regarding the incident
`
`~ Take a survey regarding your experience
`
`( J
`
`(
`
`)
`
`~
`
`I
`
`J -
`
`FIG. 3
`
`TurnSignl - Exhibit 1027
`Page 4 of 17
`
`

`

`400~
`
`402
`
`RECEIVE A REQUEST TO PRESENT AN INTERFACE FOR A
`PERSON ENCOUNTERED BY A LAW ENFORCEMENT OFFICER
`
`MINOR
`
`ADULT
`
`INTERACTIVE
`INTERFACE
`
`408
`
`GENERATE MINOR
`INTERACTIVE
`INTERFACE
`
`INFORMATION
`INTERFACE
`410
`
`INTERACTIVE
`INTERFACE
`
`416
`
`INFORMATION
`INTERFACE
`
`418
`
`GENERATE MINOR
`INFORMATION
`INTERFACE
`
`GENERATE ADULT
`INTERACTIVE
`INTERFACE
`
`GENERATE ADULT
`INFORMATION
`INTERFACE
`
`412
`
`PRESENT THE
`GENERATED
`INTERFACE
`
`FIG. 4
`
`""O
`~ .....
`
`('D = ..... t "e -....
`~ .....
`....
`0 =
`""O = O" -....
`~ .....
`....
`0 =
`c ('D
`
`(')
`
`(')
`
`~
`~CIO
`N
`
`0 ....
`
`O'I
`
`('D
`('D
`
`.i;...
`
`rJJ =(cid:173)
`.....
`0 ....
`
`O'I
`
`c
`rJJ
`N
`0 ....
`O'I ---0
`0 ....
`> ....
`
`-....J
`
`~
`Ul
`CIO
`
`TurnSignl - Exhibit 1027
`Page 5 of 17
`
`

`

`Patent Application Publication
`
`Dec. 8, 2016 Sheet 5 of 6
`
`US 2016/0358017 Al
`
`500~
`
`RECEIVE A REQUEST BY AN ARRESTED PERSON TO ACCESS AN
`INTERACTIVE INTERFACE
`
`PROVIDE WARNING REGARDING LEGAL RIGHTS AND POTENTIAL
`USE OF ADMISSIONS MADE THROUGH THE INTERACTIVE
`INTERFACE AGAINST THE ARRESTED PERSON
`
`No
`
`No
`
`PRESENT THE COMMUNICATION INTERFACE FOR THE
`ARRESTED PERSON
`
`PRESENT THE INTERVIEW INTERFACE FOR THE ARRESTED
`PERSON TO PROVIDE INFORMATION REGARDING AN INCIDENT
`
`PRESENT ANOTHER TYPE OF INTERACTIVE INTERFACE TO THE
`ARRESTED PERSON
`
`DENY USE OF THE INTERACTIVE INTERFACES TO THE
`ARRESTED PERSON
`
`FIG. 5
`
`502
`
`504
`
`No
`
`510
`
`514
`
`516
`
`518
`
`TurnSignl - Exhibit 1027
`Page 6 of 17
`
`

`

`Patent Application Publication
`
`Dec. 8, 2016 Sheet 6 of 6
`
`US 2016/0358017 Al
`
`600 ~
`
`RECEIVE CONTENT TAGGED WITH METADATA FROM THE IN(cid:173)
`VEHICLE INFORMATION DEVICE AT A NETWORK OPERATIONS
`CENTER
`
`DETERMINE WHETHER THE METADATA INDICATES THAT THE
`RECEIVED CONTENT CORRELATES WITH EXISTING CONTENT
`STORED AT THE NETWORK OPERATIONS CENTER
`
`ASSOCIATE THE CONTENT RECEIVED FROM THE IN-VEHICLE
`INFORMATION DEVICE WITH THE EXISTING CONTENT STORED AT
`THE NETWORK OPERATIONS CENTER
`
`STORE THE CONTENT RECEIVED FROM THE IN-VEHICLE
`INFORMATION DEVICE AS NEW CONTENT AT THE NETWORK
`OPERATIONS CENTER
`
`602
`
`604
`
`No
`
`608
`
`610
`
`FIG. 6
`
`TurnSignl - Exhibit 1027
`Page 7 of 17
`
`

`

`US 2016/0358017 Al
`
`Dec. 8, 2016
`
`1
`
`IN-VEHICLE USER INTERFACES FOR LAW
`ENFORCEMENT
`
`BACKGROUND
`
`[0001] Law enforcement vehicles are commonly equipped
`with mobile data terminals that enable law enforcement
`officers to obtain information on persons and vehicles of
`interests, communicate with dispatch centers and other offi(cid:173)
`cers, and create incident reports. However, such systems are
`generally not designed for use by persons that law enforce(cid:173)
`ment officers interact with as the law enforcement officers
`perform their duties. Thus, despite the existence of compu(cid:173)
`tation and multimedia presentation resources in law enforce(cid:173)
`ment vehicles, such resources do not provide direct benefits
`to the citizens that are served by the law enforcement
`officers.
`
`SUMMARY
`
`[0002] Described herein are techniques for providing in(cid:173)
`vehicle user interfaces to a person that is contacted by a law
`enforcement officer. The person may be a member of the
`community, an eyewitness, or a suspect that is arrested by
`the law enforcement officer. The in-vehicle user interfaces
`may be presented by an in-vehicle information device. The
`in-vehicle information device may provide user interfaces
`that include video via a display device and/or audio via an
`audio device to a person that is in a secure holding area ( e.g.,
`backseat, rear passenger compartment, etc.) of a law
`enforcement vehicle. Furthermore, the in-vehicle informa(cid:173)
`tion device may also include a first input device that is
`controllable by the law enforcement officer from an area of
`the vehicle that is intended for use by the law enforcement
`officer. The input device may include a touch display screen,
`a keyboard, a pointing device, and/or so forth. The in(cid:173)
`vehicle information device may further include a second
`input device (e.g., a touch screen) that is accessible to the
`person in the secure holding area.
`[0003] The in-vehicle user interfaces may provide services
`to the person in the secure holding area. The services may be
`provided based on contextual information supplied by the
`law enforcement officer or contextual information provided
`by a dispatch network operations center that dispatched the
`law enforcement officer. In some instances, a law enforce(cid:173)
`ment officer may use an in-vehicle user interface to dissemi(cid:173)
`nate information regarding legal rights to an arrested sus(cid:173)
`pect. In other instances, an in-vehicle user interface may be
`used by the law enforcement officer to solicit information
`regarding an incident from a person. In further instances, an
`in-vehicle user interface provided by the in-vehicle infor(cid:173)
`mation device may present distractions that calm or comfort
`a person that is held in the secure holding area.
`[0004]
`In some instances, the in-vehicle information
`device may generate data regarding the person that is held in
`the secure holding area. For example, the in-vehicle infor(cid:173)
`mation device may include cameras that monitor the body
`movements or facial expressions of the person held in the
`secure holding area. In turn, the body movements or facial
`expressions of the person may be analyzed by an on-board
`analytic engine of the in-vehicle information device or an
`analytic engine at a network operations center to detect
`suspicious behavior by the person.
`[0005] The in-vehicle information device may tag the
`collected data with metadata. The collected data may include
`
`images or camera footage captured by the cameras, infor(cid:173)
`mation supplied by persons using in-vehicle user interfaces,
`and/or information supplied to the in-vehicle information
`device by a law enforcement officer. The metadata may be
`used to index, sort, and organize the collected data with
`respect to incidents, time, case numbers, event identifiers,
`and/or so forth for subsequent analysis and retrieval.
`[0006]
`In at least one embodiment, a request to present a
`user interface to a person in a secure holding area of the law
`enforcement vehicle may be received. Subsequently, the
`user interface for the person may be generated based on the
`request. The user interface is then presented to the person in
`the secure holding area of the law enforcement vehicle.
`[0007] This Summary is provided to introduce a selection
`of concepts in a simplified form that is further described
`below in the Detailed Description. This Summary is not
`intended to identify key features or essential features of the
`claimed subject matter, nor is it intended to be used to limit
`the scope of the claimed subject matter.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0008] The detailed description is described with refer(cid:173)
`ence to the accompanying figures, in which the left-most
`digit(s) of a reference number identifies the figure in which
`the reference number first appears. The use of the same
`reference numbers in different figures indicates similar or
`identical items.
`[0009] FIG. 1 illustrates an example architecture for
`implementing law enforcement in-vehicle user interfaces.
`[0010] FIG. 2 is a block diagram showing various com(cid:173)
`ponents of an in-vehicle information device that implement
`law enforcement in-vehicle user interfaces.
`[0011] FIG. 3 shows illustrative law enforcement in-ve(cid:173)
`hicle user interfaces that are provided by an in-vehicle
`information device.
`[0012] FIG. 4 is a flow diagram of an example process for
`presenting a designated in-vehicle law enforcement user
`interface to a person contacted by a law enforcement officer.
`[0013] FIG. 5 is a flow diagram of an example process for
`presenting an in-vehicle law enforcement interactive inter(cid:173)
`face to a person arrested by a law enforcement officer.
`[0014] FIG. 6 is a flow diagram of an example process for
`storing content that is tagged with metadata at a network
`operations center.
`
`DETAILED DESCRIPTION
`
`[0015] This disclosure is directed to techniques for pro(cid:173)
`viding in-vehicle user interfaces to a person that is contacted
`by a law enforcement officer. The person may be a member
`of the community, an eyewitness, or a suspect that is arrested
`by the law enforcement officer. The in-vehicle user inter(cid:173)
`faces may be presented by an in-vehicle information device.
`The in-vehicle information device may provide video via a
`display device and/or audio via an audio device to a person
`that is in a secure holding area ( e.g., backseat, rear passenger
`compartment, etc.) of a law enforcement vehicle. Further(cid:173)
`more, the in-vehicle information device may also include a
`first input device that is controllable by the law enforcement
`officer from an area of the vehicle used by the law enforce(cid:173)
`ment officer. The input device may include a touch display
`screen, a keyboard, a pointing device, and/or so forth. The
`in-vehicle information device may further include a second
`
`TurnSignl - Exhibit 1027
`Page 8 of 17
`
`

`

`US 2016/0358017 Al
`
`Dec. 8, 2016
`
`2
`
`input device (e.g., a touch screen) that is accessible to the
`person in the secure holding area.
`[0016] The in-vehicle user interfaces may provide services
`to the person in the secure holding area. The services may be
`provided based on contextual information supplied by the
`law enforcement officer or contextual information provided
`by a dispatch network operations center that dispatched the
`law enforcement officer. For example, the law enforcement
`officer may select an in-vehicle user interface based on
`contextual information such as reasons for which the law
`enforcement officer is interacting with the person, behavior
`of the person during the interaction, and/or so forth. In
`another example, contextual information from the dispatch
`center that are used to select an in-vehicle user interface may
`include an age of the person, prior criminal or arrest record
`of the person, propensity for specific behaviors by the
`person, medical conditions of the person, and/or so forth.
`[0017]
`In some instances, a law enforcement officer may
`use an in-vehicle user interface to disseminate information
`regarding legal rights to an arrested suspect, such as a
`suspect that is unable to understand the language spoken by
`the law enforcement officer. In these instances, the dissemi(cid:173)
`nated information may serve to alleviate the anxiety of the
`person. In other instances, an in-vehicle user interface may
`be used by the law enforcement officer to solicit information
`regarding an incident from a person. In further instances, an
`in-vehicle user interface provided by the in-vehicle infor(cid:173)
`mation device may present distractions to calm or comfort a
`person that is held in the secure holding area. For example,
`the person may be a lost child that is waiting to be picked up
`by a parent.
`[0018]
`In additional instances, the in-vehicle information
`device may generate data regarding the person that is held in
`the secure holding area. For example, the in-vehicle infor(cid:173)
`mation device may include cameras that monitor the body
`movements or facial expressions of the person held in the
`secure holding area. In turn, the body movements or facial
`expressions of the person may be analyzed by an on-board
`analytic engine of the in-vehicle information device or an
`analytic engine at a network operations center to detect
`suspicious behavior by the person.
`[0019]
`In various embodiments, the in-vehicle informa(cid:173)
`tion device may tag collected data with metadata. The
`collected data may include camera footage captured by the
`cameras, information supplied by persons using in-vehicle
`user interfaces, and/or information supplied to the in-vehicle
`information device by a law enforcement officer. The meta(cid:173)
`data may be used to index, sort, and/or organize the collected
`data with respect to incidents, time, case numbers, event
`identifiers, etc. for subsequent analysis and retrieval. In
`some instances, the collected data may be indexed, sorted,
`and/or organized at a network operations center. In such
`instances, the collected data and the metadata may be
`encrypted with an encryption key or signed with a digital
`signature to ensure the lack of tampering during the transfer
`of the collected data and the metadata from the in-vehicle
`information device to the network operations center. In this
`way, the lack of tampering may ensure that proper chain of
`custody is maintained for evidentiary purposes.
`[0020] The techniques may enable a law enforcement
`officer to communicate information to and obtain feedback
`from a person that is held in a secure holding area of a law
`enforcement vehicle. The information may be used to alle(cid:173)
`viate the anxiety or fear of a person that is detained or
`
`arrested. The techniques may also enable a law enforcement
`officer to provide distractions that calm or comfort individu(cid:173)
`als being contacted by the law enforcement officer. Accord(cid:173)
`ingly, the in-vehicle user interfaces may be used by law
`enforcement officers to foster trust, increase public safety,
`and improve relations with community members. Example
`implementations are provided below with reference to the
`following figures.
`
`Example Architecture
`
`[0021] FIG. 1 illustrates an example architecture 100 for
`implementing law enforcement in-vehicle user interfaces.
`The architecture 100 may include law enforcement vehicles
`102(1)-102(N). Each of the law enforcement vehicles may
`be equipped with an in-vehicle information device. For
`example, the law enforcement vehicle 102(1) may be
`equipped with an in-vehicle information device 104. The
`in-vehicle information device 104 may be connected to a
`display device 106 and audio speakers 108 that are acces(cid:173)
`sible by a person 110 that is in a secure holding area (e.g.,
`backseat) of the law enforcement vehicle. The vehicle
`information device 104 may be mounted at any location in
`the law enforcement vehicle that is not accessible from the
`secure holding area of the vehicle. In various embodiments,
`the secure holding area may be separated from the remaining
`area of the law enforcement vehicle 102(1) by a protective
`barrier, in which the protective barrier also protect the
`display device 106 and audio speakers 108 from vandalism.
`In some embodiments, the display device 106 may be a
`touch screen device that enables a person in the secure
`holding area to provide inputs to the in-vehicle information
`device 104.
`[0022] The in-vehicle information device 104 may be
`further connected to hardware interface 112 that is used by
`a law enforcement officer 114 that operates the law enforce(cid:173)
`ment vehicle 102(1). For example, the hardware interface
`112 may be mounted proximate to the driver seat of the law
`enforcement vehicle 102(1). The hardware interface 112
`may include a data output device (e.g., visual display, audio
`speakers), and one or more data input devices. The data
`input devices may include, but are not limited to, combina(cid:173)
`tions of one or more of keypads, keyboards, mouse devices,
`touch screens, microphones, speech recognition software,
`and any other suitable devices or other electronic/software
`selection methods.
`[0023] The in-vehicle information device 104 may include
`hardware and software that enables the unit to generate
`in-vehicle user interfaces that are presented by the display
`device 106, the audio speakers 108, and/or the hardware
`interface 112. In various embodiments, the in-vehicle infor(cid:173)
`mation device 104 may be a smartphone, a tablet computer,
`a networked computer, an embedded computer, or any other
`computing device that is capable of receiving input, pro(cid:173)
`cessing the input based on data stored in the device, and
`generating output for presentation.
`[0024] The in-vehicle user interfaces may be used by the
`law enforcement officer 114 to communicate with the person
`in the secure holding area. The law enforcement officer 114
`may use the hardware interface to select the appropriate
`in-vehicle user interfaces. In some instances, the in-vehicle
`user interface may be a multimedia presentation that
`explains the legal rights of an arrested person, e.g., person
`110. The in-vehicle user interface may be selected for
`presentation by the law enforcement officer 114 via the
`
`TurnSignl - Exhibit 1027
`Page 9 of 17
`
`

`

`US 2016/0358017 Al
`
`Dec. 8, 2016
`
`3
`
`hardware interface 112 through an interface menu. In tum,
`the in-vehicle user interfaces may be presented to the person
`via the display device 106 and the audio speaker 108. Other
`information that may be disseminated in this manner may
`include information regarding the destination detention
`facility that the arrested person is being transported to, the
`criminal code that the person is alleged to have violated,
`and/or so forth.
`[0025]
`In other instances, in-vehicle user interfaces that
`are generated by the in-vehicle information device 104 may
`include interactive user interfaces. Such interactive user
`interfaces may be used by the law enforcement officer to
`solicit information regarding an incident from a person of
`interest. For example, a person arrested for drunk driving
`may voluntarily take a mental agility test to prove that they
`are in fact sober. In another example, the person arrested for
`drunk driving may use the in-vehicle user interface to
`answer a series of questionnaires about the current mental
`state of the person.
`[0026] The in-vehicle information device 104 may also
`present in-vehicle user interfaces that provide distractions to
`calm or comfort a person that is held in the secure holding
`area. The distractions may be include games, audio presen(cid:173)
`tations (e.g., music), video presentations (e.g., animations),
`multimedia presentations (e.g., movies), and/or so forth. For
`example, the person may be a lost child that is waiting to be
`picked up by a parent, and a game may help the child pass
`the time. In another example, in-vehicle user interface may
`be used to provide soothing music and visual imagery to a
`distressed person.
`[0027]
`In some instances, the in-vehicle information
`device 104 may include cameras 116 that monitor the body
`movements of the person held in the secure holding area. In
`turn, the body movements of the person may be analyzed by
`an on-board analytic engine of the in-vehicle information
`device 104 to detect suspicious behavior of the person.
`Alternatively, the body movements or facial expressions of
`the person may be analyzed by an analytic engine 118 at a
`network operations center 120 to detect suspicious behavior
`by the person. In some embodiments, the network operations
`center 120 may be part of a law enforcement agency or a
`private contractor that is offering services to the law enforce(cid:173)
`ment agency. The analytic engine 118 may be implemented
`by servers 122 of the network operations center 120. The
`server 122 may include one or more central processing units
`(CPUs) that each has one or more cores. The servers 122
`may be equipped with on board read only memory (ROM),
`e.g., a basic input/output system (BIOS), which manages
`boot up, random access memory (RAM), and one or more
`hard drives. Large arrays of storage, such as Redundant
`Array of Inexpensive Disks (RAID arrays) may be imple(cid:173)
`mented for the servers 122.
`[0028] The in-vehicle information device 104 may trans(cid:173)
`mit video data 124 that captures the body movements or
`facial expressions of the person to the network operations
`center 120 via a network 126. The network 126 may be a
`local area network ("LAN"), a larger network such as a wide
`area network ("WAN"), a carrier network, or a collection of
`networks, such as the Internet. Protocols for network com(cid:173)
`munication, such as TCP/IP, may be used to implement the
`network 126. The carrier network may provide telecommu(cid:173)
`nication and data communication in accordance with one or
`more technical standards.
`
`[0029]
`In other embodiments, the in-vehicle information
`device 104 may tag the collected data 128 with metadata
`130. The collected data 128 may include information sup(cid:173)
`plied by persons via an input device (e.g., a touch display, a
`touch pad, a keyboard, etc.) The collected data may further
`include information supplied to the in-vehicle information
`device 104 by the law enforcement officer 114, as inputted
`via the hardware interface 112. The in-vehicle information
`device 104 may generate the metadata 130 based on dispatch
`information, a vehicle location of the law enforcement
`vehicle 102(1), timestamp information, incident name, case
`number, event identifier, and/or so forth. The in-vehicle
`information device 104 may transmit the collected data 128
`and the metadata 130 to the network operations center 120.
`In tum, the network operations center 120 may store such
`data in the servers 122. In some embodiments, a content
`management engine 132 on the servers 122 may use the
`metadata 130 to sort portions of the collected data 128 and
`aggregate such portions with other data pertaining to similar
`incidents, events, times, cases, and/or so forth. In this way,
`an operator 134 at the network operations center 120 may
`use specific queries to find details and information, so that
`such data may be retrieved from the servers 122.
`
`Example Device Components
`
`[0030] FIG. 2 is a block diagram showing various com(cid:173)
`ponents of an in-vehicle information device 104 that imple(cid:173)
`ment law enforcement in-vehicle user interfaces. The in(cid:173)
`vehicle information device 104 may be equipped with a
`communication interface 202, one or more sensors 204, one
`or more processors 206, and memory 208. The communi(cid:173)
`cation interface 202 may include wireless and/or wired
`communication components that enable the device to trans(cid:173)
`mit or receive voice or data communication via the network
`126, as well as other telecommunication and/or data com(cid:173)
`munication networks. The sensors 204 may include a com(cid:173)
`pass, an accelerometer, and/or a global positioning system
`(GPS) sensor. The compass, the accelerometer, and the GPS
`sensor may detect orientation, movement, and geolocation
`of the in-vehicle information device 104.
`[0031] The memory 208 may be implemented using com(cid:173)
`puter-readable media, such as computer storage media.
`Computer-readable media includes, at least, two types of
`computer-readable media, namely computer storage media
`and communications media. Computer storage media
`includes volatile and non-volatile, removable and non-re(cid:173)
`movable media implemented in any method or technology
`for storage of information such as computer-readable
`instructions, data structures, program modules, or other data.
`Computer storage media includes, but is not limited to,
`RAM, ROM, EEPROM, flash memory or other memory
`technology, CD-ROM, digital versatile disks (DVD), high
`definition video disks or other optical storage, magnetic
`cassettes, magnetic tape, magnetic disk storage or other
`magnetic storage devices, or any other non-transmission
`medium that can be used to store information for access by
`a computing device. In contrast, communication media may
`embody computer-readable instructions, data structures,
`program modules, or other data in a modulated data signal,
`such as a carrier wave, or other transmission mechanism.
`[0032] The device hardware 210 may include other hard(cid:173)
`ware that is typically located on a user device. For example,
`the device hardware 210 may include signal converters,
`antennas, modems, hardware decoders and encoders,
`
`TurnSignl - Exhibit 1027
`Page 10 of 17
`
`

`

`US 2016/0358017 Al
`
`Dec. 8, 2016
`
`4
`
`graphic processors, a subscriber identity module (SIM) card
`slot, and/or the like that enable the in-vehicle information
`device 104 to execute applications and provide telecommu(cid:173)
`nication and data communication functions.
`[0033] The one or more processors 206 and the memory
`208 of the in-vehicle information device 104 may implement
`an operating system 212, applications 214, and an in-vehicle
`information application 216. The operating system 212 may
`include components that enable the in-vehicle information
`device 104 to receive and transmit data via various inter(cid:173)
`faces ( e.g., user controls, communication interface 202,
`and/or memory input/output devices). The operating system
`212 may also process data using the one or more processors
`206 to generate outputs based on inputs that are received via
`hardware interfaces and software user interfaces. For
`example, the operating system 212 may provide an execu(cid:173)
`tion environment for the execution of the applications 214.
`The operating system 212 may include a presentation com(cid:173)
`ponent that presents the output ( e.g., display the data on an
`electronic display, store the data in memory, transmit the
`data to another electronic device, etc.). The operating system
`212 may include other components that perform various
`other functions generally associated with an operating sys(cid:173)
`tem.
`[0034] The applications 214 may include applications that
`provide utility, distractions, and/or productivity functional(cid:173)
`ities to a user of the in-vehicle information device 104. For
`example, the applications 214 may include telephony appli(cid:173)
`cations, electronic mail applications, remote desktop appli(cid:173)
`cations, web browser applications, navigation applications,
`media streaming applications, and/or so forth.
`[0035] The in-vehicle information application 216 may
`include an interface selection module 218, an information
`module 220, an interactive interface module 222, a video
`module 224, and a data management module 226. These
`modules may
`include routines, program
`instructions,
`objects, and/or data structures that perform particular tasks
`or implement particular abstract data types. The memory
`208 may also provide a data store 228.
`[0036] The interface selection module 218 may generate
`an interface selection menu that is presented by the hardware
`interface 112 to the law enforcement officer 114. The inter(cid:173)
`face selection menu may enable the law enforcement officer
`114 to select specific user interfaces for presentation to the
`person 110. The selections may be inputted into the interface
`selection module 218 via the hardware interfaces 112. In
`turn, the interface selection module 218 may activate the
`information module 220 or the interactive interface module
`222 based on the specific user interfaces selected for pre(cid:173)
`sentation. In some embodiments, the law enforcement offi(cid:173)
`cer 114 may make a selection by entering attributes of the
`person that is the audience of the user interface. In such
`embodiments, a user interface may be select by the law
`enforcement officer 114 to suit the demographic attributes of
`the person 110. For example, a user interface may be
`presented in a language other than English if the person 110
`is unable to understand English. The user interface may have
`closed captioning text if the person is hearing impaired. The
`user interface may be further or independently tailored
`according to the age of the person 110. For example, a user
`interface may contain more in-depth explanations or use
`simplified terms if the person 110 is a juvenile rather than
`adult.
`
`[0037