Great research starts with great data.

Learn More
More >
Patent Analysis of

Inbound calls to intelligent controlled-environment facility resident media and/or communications devices

Updated Time 12 June 2019

Patent Registration Data

Publication Number

US10063698

Application Number

US15/469442

Application Date

24 March 2017

Publication Date

28 August 2018

Current Assignee

SECURUS TECHNOLOGIES, INC.

Original Assignee (Applicant)

SECURUS TECHNOLOGIES, INC.

International Classification

H04M1/56,H04M15/06,H04M3/436,H04M3/42

Cooperative Classification

H04M3/436,H04M3/42059,H04M2201/40,H04M2250/52,H04M2203/6045

Inventor

KEISER, LUKE,PASSE, SCOTT,BALANTRAPU, KRISHNA,NOLAND, ALEXANDER,WADE, JAMIE NICOLE

Patent Images

This patent contains figures and images illustrating the invention and its embodiment.

US10063698 Inbound calls intelligent controlled-environment 1 US10063698 Inbound calls intelligent controlled-environment 2 US10063698 Inbound calls intelligent controlled-environment 3
See all images <>

Abstract

Systems and methods for inbound calls to controlled-environment facility resident media and/or communications devices may receive, via the device, data associated with the resident operating the device. Authentication of the resident operating the device may be verified as associated with an address identifier of the device and it may be confirmed that an inbound calling non-resident is associated with the address identifier. A notification of the inbound call may then be sent to the device, and the same or other data associated with the resident operating the device may be received, via the device. Authentication of the resident operating the device as a resident as associated with an address identifier may be re-verified using the same or other data and the call connected as a result of the verification, confirmation and/or re-verification.

Read more

Claims

1. An inbound call system for handling inbound calls to inmate media and/or communications devices, the system comprising:

one or more inmate media and/or communications devices, each having a relatively unique hardcoded address identifier, and each configured to receive data to verify and re-verify authentication of an inmate operating the inmate media and/or communications device; an inbound inmate call server configured to connect non-inmate inbound calls with corresponding inmate media and/or communications devices; andan authenticating server configured to:

verify, using the data, authentication of the inmate operating the inmate media and/or communications device as associated with the hardcoded address identifier of the inmate media and/or communications device; confirm that an inbound calling non-inmate is associated with the hardcoded address identifier of the inmate media and/or communications device the non-inmate is calling; send a notification of a non-inmate call to the inmate media and/or communications device to the inmate operating the inmate media and/or communications device from the calling non-inmate; receive, via the inmate media and/or communications device, after receipt of the notification, the same or other data to re-verify authentication of the inmate operating the inmate media and/or communications device the non-inmate is calling; and re-verify authentication of the inmate operating the inmate media and/or communications device, using the same or other data, as associated with the hardcoded address identifier of the inmate media and/or communications device prior to connection of the non-inmate inbound call with the inmate media and/or communications device by the inbound inmate call server.

2. The system of claim 1, wherein data to verify and/or re-verify authentication of an inmate comprises a personal identification number entered and/or reentered via the inmate media and/or communications device.

3. The system of claim 2, wherein the authenticating server is further configured to verify and/or re-verify the personal identification number is associated with an inmate to whom the inbound call is directed.

4. The system of claim 2, wherein the personal identification number is entered and/or reentered via the inmate media and/or communications device by being spoken and/or respoken by the inmate operating the inmate media and/or communications device and the authenticating server is further configured to enter and/or reenter the personal identification number using speech recognition and verify and/or re-verify authentication of the inmate operating the inmate media and/or communications device using voice recognition.

5. The system of claim 2, wherein the personal identification number is entered and/or reentered via a touchscreen keypad displayed by the inmate media and/or communications device, the inmate media and/or communications device is configured to capture data related to at least one fingerprint during entry and/or reentry for receipt by the authenticating server, and the authenticating server is further configured to verify and/or re-verify authentication of the inmate operating the inmate media and/or communications device using fingerprint recognition and the data related to at least one fingerprint.

6. The system of claim 2, wherein the inmate media and/or communications device further comprises a camera and the inmate media and/or communications device is configured to capture and/or recapture image data of the inmate operating the inmate media and/or communications device during entry and/or reentry of the personal identification number into the inmate media and/or communications device for receipt by the authenticating server, and the authenticating server is further configured to verify and/or re-verify authentication of the inmate operating the inmate media and/or communications device using facial recognition and the image data.

7. The system of claim 1, wherein data to verify and/or re-verify authentication of an inmate comprises biometric data and the inmate media and/or communications device is configured to capture and/or recapture the biometric data.

8. The system of claim 7, wherein the biometric data is the voice of the inmate operating the inmate media and/or communications device and the authenticating server is further configured to verify and/or re-verify authentication of the inmate operating the inmate media and/or communications device using voice recognition.

9. The system of claim 7, wherein the biometric data is at least one fingerprint of the inmate operating the inmate media and/or communications device, the inmate media and/or communications device is configured to capture and/or recapture data related to at least one fingerprint of the inmate operating the inmate media and/or communications device during use of the inmate media and/or communications device for receipt by the authenticating server, and the authenticating server is further configured to verify and/or re-verify authentication of the inmate operating the inmate media and/or communications device using fingerprint recognition and the data related to at least one fingerprint.

10. The system of claim 7, wherein the inmate media and/or communications device further comprises a camera, the biometric data is an image of the inmate using the inmate media and/or communications device, the inmate media and/or communications device is configured to capture and/or recapture image data of the inmate operating the inmate media and/or communications device for receipt by the authenticating server, and the authenticating server is further configured to verify and/or re-verify authentication of the inmate operating the inmate media and/or communications device using facial recognition and the image data.

11. A method for processing inbound calls to inmate media and/or communications devices, the method comprising:

receiving, via an inmate media and/or communications device, data for verifying authentication of an inmate operating the inmate media and/or communications device; verifying authentication of the inmate operating the inmate media and/or communications device using the data as associated with a hardcoded address identifier of the inmate media and/or communications device; confirming that an inbound calling non-resident is associated with the hardcoded address identifier of the inmate media and/or communications device; sending a notification to the inmate media and/or communications device of a call to the inmate operating the inmate media and/or communications device; receiving, via the inmate media and/or communications device, after receipt of the notification, the same or other data for verifying authentication of an inmate operating the inmate media and/or communications device; re-verifying authentication of the inmate operating the inmate media and/or communications device using the data received after receipt of the notification as associated with the hardcoded address identifier of the inmate media and/or communications device; and connecting the non-inmate inbound call with the inmate media and/or communications device as a result of authenticating that the non-inmate is associated with the hardcoded address identifier of the inmate media and/or communications device and verifying and/or re-verifying authentication of the inmate operating the inmate media and/or communications device as associated with the hardcoded address identifier of the inmate media and/or communications device.

12. The method of claim 11 wherein the data for verifying authentication of an inmate operating the inmate media and/or communications device is received by an authenticating server, the authenticating server verifying, using the data, the authentication of the inmate operating the inmate media and/or communications device as associated with the hardcoded address identifier of the inmate media and/or communications device, the authenticating server confirming that the inbound calling non-resident is associated with the hardcoded address identifier of the inmate media and/or communications device, the authenticating server receiving the same or other data for verifying authentication of an inmate operating the inmate media and/or communications device, the authenticating server re-verifying authentication of the inmate operating the inmate media and/or communications device, using the data received after the notification as associated with the hardcoded address identifier of the inmate media and/or communications device.

13. The method of claim 11, wherein data for verifying authentication of an inmate comprises a personal identification number, and the method further comprises accepting entry and/or reentry of the personal identification number via the inmate media and/or communications device.

14. The method of claim 13, further comprising verifying and/or re-verifying that the personal identification number is associated with an inmate to whom the inbound call is directed.

15. The method of claim 13, further comprising:

accepting entry and/or reentry of a spoken personal identification number; entering and/or reentering the personal identification number using speech recognition; and verifying and/or re-verifying authentication of the inmate operating the inmate media and/or communications device using voice recognition.

16. The method of claim 13, further comprising:

accepting entry and/or reentry of the personal identification number via a touchscreen keypad displayed by the inmate media and/or communications device; capturing data related to at least one fingerprint, by the inmate media and/or communications device, during entry and/or reentry; and verifying and/or re-verifying authentication of the inmate operating the inmate media and/or communications device using fingerprint recognition and the data related to at least one fingerprint.

17. The method of claim 13, further comprising:

capturing, by a camera of the inmate media and/or communications device, image data of the inmate operating the inmate media and/or communications device during entry and/or reentry of the personal identification number into the inmate media and/or communications device; and verifying and/or re-verifying authentication of the inmate operating the inmate media and/or communications device using facial recognition and the image data.

18. The method of claim 11, wherein the data for verifying authentication of an inmate comprises biometric data, and the method further comprises capturing and/or recapturing the biometric data by the inmate media and/or communications device.

19. The method of claim 18, wherein the biometric data is the voice of the inmate operating the inmate media and/or communications device, and the method further comprises verifying and/or re-verifying authentication of the inmate operating the inmate media and/or communications device using voice recognition.

20. The method of claim 18, wherein the biometric data is at least one fingerprint of the inmate operating the inmate media and/or communications device, and the method further comprises:

capturing and/or recapturing, by the inmate media and/or communications device, data related to at least one fingerprint of the inmate operating the inmate media and/or communications device during use of the inmate media and/or communications device; and verifying and/or re-verifying authentication of the inmate operating the inmate media and/or communications device using fingerprint recognition and the data related to at least one fingerprint.

21. The method of claim 18, wherein the biometric data is an image of the inmate using the inmate media and/or communications device, and the method further comprises:

capturing and/or recapturing image data of the inmate operating the inmate media and/or communications device, using a camera of the inmate media and/or communications device; and verifying and/or re-verifying authentication of the inmate operating the inmate media and/or communications device using facial recognition and the image data.

22. A non-transitory computer-readable storage medium having program instructions stored thereon that, upon execution by one or more controlled-environment facility communications systems, cause the one or more communications systems to:

receive, via an inmate media and/or communications device, data associated with the inmate operating the inmate media and/or communications device; verify authentication of the inmate operating the inmate media and/or communications device as an inmate associated with a hardcoded address identifier of the inmate media and/or communications device; receive an inbound call from a non-inmate directed to the inmate and/or the inmate media and/or communications device; confirm that the inbound calling non-inmate is associated with a hardcoded address identifier of the inmate media and/or communications device; send a notification to the inmate media and/or communications device of the inbound call; receive, via the inmate media and/or communications device, after receipt of the notification, the same or other data associated with the inmate operating the inmate media and/or communications device; re-verify authentication of the inmate operating the inmate media and/or communications device as an inmate as associated with a hardcoded address identifier of the inmate media and/or communications device using the same or other data associated with the inmate operating the inmate media and/or communications device received after receipt of the notification; and connect the non-inmate inbound call with the inmate media and/or communications device as a result of confirmation that the non-inmate is associated with a hardcoded address identifier of the inmate media and/or communications device and verification and re-verification that the inmate operating the inmate media and/or communications device is associated with the hardcoded address identifier of the inmate media and/or communications device.

Read more

Claim Tree

  • 1
    ystem for handling inbound calls to inmate media and/or communications devices, the system comprising: one or ore inmate
    • edia and/or communications devices, each having a relatively unique hardcoded address identifier, and each configured to receive data to verify and re-verify authentication of an inmate operating the inmate media and/or communications device; an inbound inmate
    • ll server configured to connect non-inmate inbound calls with corresponding inmate media and/or communications devices; andan authenticati
    • server configured to: verify, using the data, authentication of the inmate operating the inmate media and/or communications device as associated with the hardcoded address identifier of the inmate media and/or communications device; confirm that an inb
    • nd calling non-inmate is associated with the hardcoded address identifier of the inmate media and/or communications device the non-inmate is calling; send a notification
    • f a non-inmate call to the inmate media and/or communications device to the inmate operating the inmate media and/or communications device from the calling non-inmate; receive, via the in
    • te media and/or communications device, after receipt of the notification, the same or other data to re-verify authentication of the inmate operating the inmate media and/or communications device the non-inmate is calling; and re-verify authe
    • ication of the inmate operating the inmate media and/or communications device, using the same or other data, as associated with the hardcoded address identifier of the inmate media and/or communications device prior to connection of the non-inmate inbound call with the inmate media and/or communications device by the inbound inmate call server. 2. The system of cla
    • m 1, wherein data to veri y and/o
      • re-verify authentication of an inmate comprises a personal identific
    • m 1, wherein data to veri y and/o
      • re-verify authentication of an inmate comprises biometric ata and t
  • 11
    essing inbound calls to inmate media and/or communications devices, the method comprising: receivin , via an i
    • ate media and/or communications device, data for verifying authentication of an inmate operating the inmate media and/or communications device; verifying authentic
    • ion of the inmate operating the inmate media and/or communications device using the data as associated with a hardcoded address identifier of the inmate media and/or communications device; confirming that an
    • bound calling non-resident is associated with the hardcoded address identifier of the inmate media and/or communications device; sending a notificat
    • n to the inmate media and/or communications device of a call to the inmate operating the inmate media and/or communications device; receiving, via the
    • mate media and/or communications device, after receipt of the notification, the same or other data for verifying authentication of an inmate operating the inmate media and/or communications device; re-verifying authen
    • cation of the inmate operating the inmate media and/or communications device using the data received after receipt of the notification as associated with the hardcoded address identifier of the inmate media and/or communications device; and connecting the
    • n-inmate inbound call with the inmate media and/or communications device as a result of authenticating that the non-inmate is associated with the hardcoded address identifier of the inmate media and/or communications device and verifying and/or re-verifying authentication of the inmate operating the inmate media and/or communications device as associated with the hardcoded address identifier of the inmate media and/or communications device. 12. The method of cl
    • im 11 wherein the data for verifyi
      • g authentication of an inmate operating the inmate media and/or communications device is received by an authenticating server, the authenticating server verifying, using the data, the authentication of the inmate operating the inmate media and/or communications device as associated with the hardcoded address identifier of the inmate media and/or communications device, the authenticating server confirming that the inbound calling non-resident is associated with the hardcoded address identifier of the inmate media and/or communications device, the authenticating server receiving the same or other data for verifying authentication of an inmate operating the inmate media and/or communications device, the authenticating server re-verifying authentication of the inmate operating the inmate media and/or communications device, using the data received after the notification as associated with the hardcoded address identifier of the inmate media and/or communications device. 13. The method of cl
    • im 11, wherein data for ver fying a
      • thentication of an inmate comprises a personal identific
    • im 11, wherein the data for verifyi
      • g authentication of an inmate comprises biometric ata, and
  • 22
    computer-readable storage medium having program instr ctions
    • stored thereon that, upon execution by one or more controlled-environment facility communications systems, cause the one or more communications systems to: receive, via an inmate media and/or communications device, data associated with the inmate operating the inmate media and/or communications device; verify authenticati
    • of the inmate operating the inmate media and/or communications device as an inmate associated with a hardcoded address identifier of the inmate media and/or communications device; receive an inbound
    • ll from a non-inmate directed to the inmate and/or the inmate media and/or communications device; confirm that the in
    • und calling non-inmate is associated with a hardcoded address identifier of the inmate media and/or communications device; send a notification
    • o the inmate media and/or communications device of the inbound call; receive, via the in
    • te media and/or communications device, after receipt of the notification, the same or other data associated with the inmate operating the inmate media and/or communications device; re-verify authentic
    • ion of the inmate operating the inmate media and/or communications device as an inmate as associated with a hardcoded address identifier of the inmate media and/or communications device using the same or other data associated with the inmate operating the inmate media and/or communications device received after receipt of the notification; and connect the non
    • nmate inbound call with the inmate media and/or communications device as a result of confirmation that the non-inmate is associated with a hardcoded address identifier of the inmate media and/or communications device and verification and re-verification that the inmate operating the inmate media and/or communications device is associated with the hardcoded address identifier of the inmate media and/or communications device.
See all independent claims <>

Description

TECHNICAL FIELD

The present disclosure relates generally to controlled-environment facilities, more particularly to communications with residents of controlled-environment facilities, and specifically to inbound phone and video calls to intelligent controlled-environment facility resident media and/or communications devices.

BACKGROUND

According to the International Centre for Prison Studies, the United States has the highest prison population per capita in the world. In 2009, for example, 1 out of every 135 U.S. residents was incarcerated. Generally, inmates convicted of felony offenses serve long sentences in prison (e.g., federal or state prisons), whereas those convicted of misdemeanors receive shorter sentences to be served in jail (e.g., county jail). In either case, while awaiting trial, a suspect or accused may remain incarcerated. During his or her incarceration, an inmate may have opportunities to communicate with the outside world.

By allowing prisoners to have some contact with friends and family while incarcerated, the justice system aims to facilitate their transition back into society upon release. Traditional forms of contact include telephone calls, in-person visitation, conjugal visits, etc. More recently, technological advances have allowed jails and prisons to provide other types of visitation, including individual-to-individual videoconferences and online chat sessions.

Traditional communication services provide residents (inmates) of controlled-environment facilities (such as correctional facilities) the ability to place outbound phone calls to non-residents of the controlled-environment facility. Additionally, non-residents can typically schedule video visitation with residents (inmates) of the controlled-environment facility. Other types of communication available to controlled-environment residents include the ability to exchange email and canned text messages between residents and non-residents of the controlled-environment facility. Basically, all of these forms of communication aim to facilitate communication between a resident of a controlled-environment facility and a non-resident.

Additionally, over the past several years, the above-mentioned sharp increase in the U.S. inmate population has not been followed by a proportional increase in the number of prison or jail staff. To the contrary, budget pressures in local, state, and federal governments have made it difficult for correctional facilities to maintain an adequate number of wardens, officers, and other administration personnel. Hence, many correctional facilities are often unable to perform investigations with respect to their own inmates.

SUMMARY

The present invention is directed to systems and methods, which provide handling of inbound calls to resident (e.g. inmate) media and/or communications devices. Such a system may include an inbound resident call server, an authenticating server, and/or the like. The authenticating server may be a part of the inbound resident call server, or the like, in some implementations.

The inbound resident call server may be adapted to host inbound calling accounts established by non-residents and receive inbound calls from such non-residents. The inbound calls may be routed to the authenticating server by the inbound resident call server. The authenticating server may be adapted to authenticate that a non-resident is associated with an inbound calling account and confirm that the inbound calling account is associated with an address identifier of the resident media and/or communications device the non-resident is calling. The authenticating server may also receive, via the called resident media and/or communications device, a personal identification number associated with the resident the inbound call is directed to and may verify that the personal identification number is associated with the address identifier of the resident media and/or communications device. The inbound resident call server may also confirm that the resident media and/or communications device is active and connect the inbound resident call system with the resident media and/or communications device in response to confirming that the resident media and/or communications device is active, or alternatively, inform the non-resident the resident is not available for the inbound call in response to failure to confirm that the resident media and/or communications device is active. Thereupon, the inbound resident call server may connect the non-resident inbound call with the resident media and/or communications device, as a result of the authenticating server authenticating that the non-resident is associated with the inbound calling account, confirming that the inbound calling account is associated with an address identifier of the resident media and/or communications device and verifying that the personal identification number is associated with the address identifier of the resident media and/or communications device.

In some implementations, the inbound call from the non-resident may be directed to the resident media and/or communications device and the inbound resident call server may, in such cases intercept the inbound call. Additionally, or alternatively, the inbound resident call server, or the like may host a central phone number for calls directed to resident media and/or communications devices, and in such implementations, inbound calls from non-residents may be directed to the central phone number and the inbound resident call server may accept requests from non-residents for calls into residents and/or more specifically into a particular resident's media and/or communications device.

Various other features provided in accordance with assorted implementations of the present systems and methods may include the following. A flat fee or time-based fee may be charged for the inbound call and/or a subscription fee may (periodically) be charged following establishment of the inbound calling account for the non-resident, such as from an inbound calling account of the non-resident. The inbound call may be monitored, such as for impermissible activity, keywords, or the like. The inbound call may also be tracked and/or recorded, and resulting recordings may be stored (and tracked). Also, a determination may be made as to whether the non-resident is on a personal allowed number list and/or a pre-approved contact list associated with the resident and/or the called media and/or communications device.

In accordance with various aspects the present systems and methods multilayer authentication processing of inbound calls to resident media and/or communications devices may include receiving, via such a resident media and/or communications device, data for verifying authentication of a resident operating the device, prior to any incoming call. In such cases, authentication of the resident operating the resident media and/or communications device may also be verified as associated with an address identifier of the device. Again, an inbound calling non-resident may be confirmed as associated with the address identifier of the resident media and/or communications device. Whereupon a notification may be sent to the resident media and/or communications device of a call to the resident operating the device. However, in accordance with multilayer authentication, the same or other data for verifying authentication of a resident operating the resident media and/or communications device is received, via the device, after receipt of the notification. Whereupon, authentication of the resident operating the resident media and/or communications device as associated with the address identifier of the device may be re-verified, using the data received after receipt of the notification. Consistent with such multilayer authentication, the non-resident inbound call may be connected with the device as a result of authenticating that the non-resident is associated with the address identifier of the device and verifying and re-verifying authentication of the resident operating the device as associated with the address identifier of the device.

Similar to other aspects of the present systems and methods, the data for verifying authentication of a resident operating the resident media and/or communications device may be received by an authenticating server. In such case, the authenticating server may verify the authentication of the resident operating the device as associated with the address identifier of the resident media and/or communications device, using the data. The authenticating server may also confirm that the inbound calling non-resident is associated with the address identifier of the resident device. Consistent with multilayer authentication, the authenticating server may also receive the same or other data for verifying authentication of a resident operating the device, after the notification, and the authenticating server may re-verify authentication of the resident operating the device as associated with the address identifier of the device, using this data.

In various embodiments, one or more of the techniques described herein may be performed by one or more computer systems. In other various embodiments, a tangible computer-readable storage medium may have program instructions stored thereon that, upon execution by one or more computer systems, cause the one or more computer systems to execute one or more operations disclosed herein. In yet other various embodiments, one or more systems may each include at least one processor and memory coupled to the processor(s), wherein the memory is configured to store program instructions executable by the processor(s) to cause the system(s) to execute one or more operations disclosed herein.

The foregoing has outlined rather broadly the features and technical advantages of the present invention in order that the detailed description of the invention that follows may be better understood. Additional features and advantages of the invention will be described hereinafter which form the subject of the claims of the invention. It should be appreciated that the conception and specific embodiment disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present invention. It should also be realized that such equivalent constructions do not depart from the invention as set forth in the appended claims. The novel features which are believed to be characteristic of the invention, both as to its organization and method of operation, together with further objects and advantages will be better understood from the following description when considered in connection with the accompanying figures. It is to be expressly understood, however, that each of the figures is provided for the purpose of illustration and description only and is not intended as a definition of the limits of the present invention.

BRIEF DESCRIPTION OF THE DRAWINGS

Having thus described the invention in general terms, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:

FIG. 1 is a diagrammatic illustration of an example communications environment, wherein an example of embodiments of the present systems and methods for inbound calls to intelligent controlled-environment facility resident media and/or communications devices may be practiced, according to some embodiments;

FIG. 2 is a flowchart of an example process for inbound calling to intelligent controlled-environment facility resident media and/or communications devices, in accordance with some embodiments;

FIG. 3 is a flowchart of another implementation of an example process for inbound calling to intelligent controlled-environment facility resident media and/or communications devices, in accordance with some embodiments;

FIG. 4 is a flowchart of yet another example implementation of a process for inbound calling to intelligent controlled-environment facility resident media and/or communications devices, in accordance with some embodiments; and

FIG. 5 is a block diagram of a computer system, device, station, or terminal configured to implement various techniques disclosed herein, according to some embodiments.

While this specification provides several embodiments and illustrative drawings, a person of ordinary skill in the art will recognize that the present specification is not limited only to the embodiments or drawings described. It should be understood that the drawings and detailed description are not intended to limit the specification to the particular form disclosed, but, on the contrary, the intention is to cover all modifications, equivalents and alternatives falling within the spirit and scope of the claims. As used herein, the word “may” is meant to convey a permissive sense (i.e., meaning “having the potential to”), rather than a mandatory sense (i.e., meaning “must”). Similarly, the words “include,”“including,” and “includes” mean “including, but not limited to.”

DETAILED DESCRIPTION

The invention now will be described more fully hereinafter with reference to the accompanying drawings. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. One skilled in the art may be able to use the various embodiments of the invention.

For example, various types of controlled-environment facilities are present in today's society, and persons may be voluntary or involuntary residents of such facilities, whether temporarily or permanently. Examples of controlled-environment facilities may include correctional institutions (e.g., municipal jails, county jails, state prisons, federal prisons, military stockades, juvenile facilities, detention camps, home incarceration environments, etc.), healthcare facilities (e.g., hospitals, nursing homes, mental health facilities, rehabilitation facilities, such as drug and alcohol rehabilitation facilities, etc.), restricted living quarters (e.g., hotels, resorts, camps, dormitories, barracks, etc.), and the like. For convenience of explanation, various examples discussed herein are presented in the context of correctional facilities, or the like. For instance, in some of the embodiments discussed below, a controlled-environment facility may be referred to as a correctional facility, jail or prison, and its residents may be referred to as inmates, arrestees, or detainees. It should be understood, however, that the systems and methods described herein may be similarly applicable to other types of controlled-environment facilities and their respective residents (e.g., a hospital and its patients, a school dormitory and its students, etc.).

The present systems and methods relate generally to controlled-environment facilities, more particularly to communications with residents of controlled-environment facilities, and specifically to inbound phone and video calls to intelligent controlled-environment facility resident media and/or communications devices. Embodiments of the present systems and methods for processing inbound calls to resident media and/or communications devices may employ an inbound resident call server configured to host inbound calling accounts established by non-residents, receive inbound calls from the non-residents, route the inbound calls to an authenticating server, confirm that the resident device is active, and connect the inbound resident call system with the resident device if active or inform the non-resident the resident is not available. The inbound resident call server also connects the non-resident inbound call with the resident device if the non-resident is associated with the inbound calling account, the inbound calling account is associated with an address identifier of the resident device and a personal identification number provided by the called resident is associated with the address identifier of the resident device, all of which may be authenticated by the authenticating server.

Controlled-environment facility calls have traditionally been outgoing only, such as prepaid calls, collect calls or calls made by residents paid for using a trust account maintained to the benefit of the resident. Inbound calls to residents have here-to-fore not been allowed or have been impractical. For example, inbound calls to a correctional facility wall-mounted, table top, roll around, or similar phone in inmate housing areas (i.e. the phones inmates have traditionally used to place outbound calls, such as via an interactive voice response system (IVR)) cannot be properly directed to the intended inmate, since the phone may be answered by any inmate, who may not cooperate, or may not be able to cooperate, to get the intended inmate on the phone. However, controlled-environment facility resident media and/or communications devices, such as tablet computing devices, or the like, specially adapted and/or otherwise approved for use in the controlled-environment facility are capable of receiving inbound communications, such as via a wireless network associated with the controlled-environment facility.

In accordance with embodiments of the present systems and methods, a non-resident can set-up inbound calling account, such as via a website, provide for payment, and place inbound calls to controlled-environment facility resident media and/or communications devices, such as resident tablets. Various embodiments of such systems and methods may accept an inbound call to an inbound controlled-environment facility resident media and/or communications device call server (or via a website). Where the inbound call is directed to a central number for calls directed to controlled-environment facility resident media and/or communications devices, the method may further comprise accepting a request from the non-resident for a call into the resident and/or the controlled-environment facility resident media and/or communications device. Various embodiments of the present systems and methods are directed to allowing inbound calls to residents based on a controlled-environment facility resident media and/or communications device Address Identifier (AID), residents name and, in some embodiments a resident-associated identification number. This AID number may be married to the call request in such embodiments and the resident may accept a forwarded call by entering personal identification number (PIN) and/or verifying authentication, such as through voice recognition, key pad, touchpad, fingerprint, ocular-based recognition or other biometric, non-biometric, or other authentication methods. A PIN can be entered in any number of ways, which may incorporate biometric verification into the entering of the PIN itself. For example, the PIN may be entered using a touchscreen, such that fingerprint recognition can be used to verify the typer's identity. Alternatively (or additionally) the PIN may be spoken to be entered, and while speech recognition may be used to recognize the spoken numbers of the PIN, voice recognition may be used on the spoken PIN to verify the speaker's identity. Further, an image of the user may be captured during such PIN entry and facial recognition may be used to (further) confirm the identity of the user, such as for correlation with the PIN. Security measures applied to inbound calls may include similarly use of voice recognition (during the call) to ensure the tablet is not handed off to another resident (or monitoring to see who the tablet is handed off to). Voice mail, and other call features may also be employed in conjunction with various embodiments of the present systems and methods.

FIG. 1 is a diagrammatic illustration of an example communications environment, wherein example embodiments of the present systems and methods for inbound phone or video calls to intelligent controlled-environment facility resident media and/or communications devices may be practiced, according to some embodiments. As shown, communication processing system 101 may provide telephone services, videoconferencing, online chat, and other communication services to a controlled-environment facility. For example, in some cases, communication system 101 may be co-located with a controlled-environment facility. Alternatively, communication system 101 may be centrally or remotely located with respect to one or more controlled-environment facilities and/or may provide communication services to multiple controlled-environment facilities. More generally, however, it should be noted that communication system 101 may assume a variety of forms, and may be configured to serve a variety of facilities and/or users, whether within or outside of a controlled-environment facility.

In the context of a correctional facility, for instance, inmates may use telephones 102 to access certain communication services. In some facilities, inmates may also use a personal computer wireless device (104), referred to herein as a(n) (intelligent) controlled-environment facility resident media and/or communications device, an inmate media and/or communications device, or the like, to access such services. For example, an inmate may initiate telephone services by lifting the receiver on telephone 102 or launching a communications application program (app) on inmate media and/or communications device 104, at which time the inmate may be prompted to provide PIN, other identifying information, or biometrics. An interactive voice response (IVR) unit (not shown) may generate and play a prompt, send a text or other messages to inmates on devices 102 and/or 104.

Under the control of communication processing system 101, devices 102 and 104 may be capable of connecting to a non-resident's (i.e., a person not committed to a controlled-environment facility) device 105 or telephone 106 across a publicly switched telephone network (PSTN) 107. For example, device 105 may be a mobile phone, whereas telephone 106 may be located at a non-resident's home, inmate visitation center, etc. Switch 108 in communication processing system 101 may be used to connect calls across PSTN 107. Additionally or alternatively, the non-resident may be at telephone 109 or device 112, which is on an Integrated Services Digital Network (ISDN), Voice-over-IP (VoIP), or packet data network 110, such as, for example the Internet. Router 111 of communication system 101 is used to route data packets associated with a call connection to destination telephone 109 or device 112.

Video visitation devices 103 may have video conferencing capabilities to enable inmates to participate in video visitation sessions with non-residents of the correctional facility via video call, secure online chat, etc. For example, a non-resident party may have a personal or laptop computer 113 with camera 114 (or a cell phone, tablet computer, etc.). Additionally or alternatively, device 112 may have an integrated camera and display (e.g., a smart phone, tablet, etc.). A network connection between the parties may be established and supported by an organization or commercial service that provides computer services and software for use in telecommunications and/or VOIP, such as SKYPE®. Additionally or alternatively, the correctional facility and/or the destination may use videoconferencing equipment compatible with ITU H.323, H.320, H.264, and/or V.80, or other suitable standards. Generally speaking, each video visitation device 103 may be disposed in a visitation room, in a pod, cell, etc.

In some embodiments, video visitation devices 103 may be implemented as a computer-based system. For example, each of video visitation devices 103 may include a display, camera, and handset. The display may be any suitable electronic display such as, for example, a Liquid Crystal Display (LCD), a touchscreen display (e.g., resistive, capacitive, etc.), or the like, whereas the camera may be any suitable imaging device such as, for instance, a video camera or webcam equipped with Charge-Coupled Devices (CCDs), Complementary Metal-Oxide-Semiconductor (CMOS) active pixel sensors, etc. A handset may be similar to a traditional telephone handset including an earpiece portion (with a loudspeaker), a handle portion, and a mouthpiece portion (with a microphone).

During a video visitation session, video visitation devices 103 may be configured to capture a video image of an inmate to be transmitted to a non-resident using the camera, and to display a video image of the non-resident to the inmate using the display. Video visitation devices 103 may also be configured to capture an audio signal from the inmate to be transmitted to a non-resident using the mouthpiece portion of the handset, and to provide an audio signal from the non-resident to the inmate using the earpiece portion of the handset. Additionally or alternatively, audio received from the non-resident may be reproduced via a loudspeaker, and audio provided by the inmate may be captured via a microphone. In some cases, video visitation devices 103 may assume the form of any computer, tablet computer, smart phone, etc., or any other consumer device or appliance with videoconferencing capabilities.

Intelligent controlled-environment facility resident media and/or communications devices 104 may be tablet computing devices, smartphones, media players, or the like adapted and/or approved for use by residents of the controlled-environment facility (within the controlled-environment facility). Each intelligent controlled-environment facility resident media and/or communications device 104 may be particularly adapted for use in a controlled-environment. For example, in a correctional institution, jail, or the like, such an intelligent controlled-environment facility resident media and/or communications device, may have a specially adapted operating system and/or may be “stripped-down,” particularly from the standpoint of what apps and/or hardware are provided or allowed on intelligent controlled-environment facility resident media and/or communications device 104, and/or connectivity afforded such a device. For example, such a device may employ an operating system kernel such one based upon an open source platform such as the CyanogenMod-based operating system, which may be built for use in such a device in a controlled-environment facility. As a further example, the intelligent controlled-environment facility resident media and/or communications device may be adapted to only connect to a network provided by the controlled-environment facility, and/or in only certain locations, within the controlled-environment facility, such as may be controlled by availability of Wi-Fi access, or the like, only being available in certain areas. That is, for example, where streaming and/or downloading may be compartmentalized, leveraging the structure of the controlled-environment facility, for example, limiting the availability of a Wi-Fi signal, providing the stream through the placement of wireless access points, antenna directionality of such wireless access points, and/or the like. Further, the intelligent controlled-environment facility resident media and/or communications device may allow access to apps or content only upon application of security measures, by the device. Such security measures may include determining, by the device, DNS spoofing, DNS redirection, use of proxy servers for privacy and security, biometric validation, password validation, and/or the like. Also, in accordance with embodiments of the present systems and methods, the intelligent controlled-environment facility resident media and/or communications device may have a few fixed apps pre-installed on the device, and installation of further apps on the device may be forbidden (i.e. prevented by modifications to the device's operating system, or the like) and/or restricted, such as by requiring permission from a facility administrator, or the like. Apps provided on intelligent controlled-environment facility resident media and/or communications devices might include apps of particular interest to residents of the controlled-environment facility. For example, such inmate media and/or communications devices provided to inmates of correctional facilities, might include apps that may be of particular use to an inmate, in general, such as access to a legal research service, or of more specific interest, such as providing an inmate nearing release, access to employment searching apps or the like. Hence, such inmate media and/or communications devices may be used to help soon-to-be released inmates to transition. For example, the inmate media and/or communications device may be used to communicate with a future employer, or the like. As such, inmate media and/or communications devices may be sponsored, or otherwise subsidized by organizations or companies, assisting with the transition of inmates into society.

In addition to providing certain visitation and communication operations, communication processing system 101 may attempt to ensure that an inmate's calls, video conferences, online chats, etc. are performed only with non-residents whose identities, devices, email addresses, phone numbers, etc. are listed in that inmate's Personal Allowed Number (PAN) or Pre-Approved Contact (PAC) list. Each inmate's PAN or PAC list may be stored, for example, in database 115 maintained by Administration and Management System (AMS) 116. In addition to PAN or PAC list(s), AMS 116 may also store inmate or resident profile data (RPD), as well as visitation rules applicable to each inmate.

As an example, in the context of a correctional facility, database 115 may include information such as balances for inmate trust and calling accounts; trial schedule; conviction data; criminal record; sentencing data, such as time served, time remaining to be served, and release date; cell and cellmate assignments; inmate restrictions and warnings; commissary order history; telephone call history; video and/or audio communication recordings; known or suspected gang or criminal affiliations; known or suspected affiliates, accomplices, or gang members; and any other information that may be relevant or useful to correctional facility staff to house and maintain inmates.

In some implementations, communication system 101 may be configured to perform call and/or video visitation monitoring operations configured to monitor and or record calls and/or video visitations (e.g., as electronic audio or video files). Such monitoring may be carried out to detect impermissible activity, such as attempts to initiate three-way calls, and/or for investigative purposes, such as detection of keywords related to criminal activity or the like. In scenarios where communication system 101 is located within the controlled-environment facility, it may have direct access to AMS 116. In other embodiments, however, communication system 101 may be located remotely with respect to the controlled-environment facility, and access to AMS 116 may be obtained via a computer network such as, for example, network 110.

In many controlled-environment facilities, inmates are restricted from communicating with persons outside of the controlled-environment facility using any device other than the system described in FIG. 1. Reasons for this include protection of persons outside of the controlled-environment facility from offensive, inappropriate, or illegal contact with an inmate. Additionally, these restrictions may help to prevent inmates from directing further illegal activity with conspirators located outside of the controlled-environment facility, witness tampering, victim protection etc. Administrators of the controlled-environment facility may wish to limit the inmate's contact to parties on the inmate's PAN or PAC list.

In the illustrated environment inbound phone or video call processing system 130 may process inbound calls to intelligent controlled-environment facility resident media and/or communications devices 104. Inbound call processing system 130, may include inbound resident call server 132, which may include at least one processor and memory coupled to the processor(s), wherein the memory is configured to store program instructions executable by the processor(s) to cause the system(s) to execute one or more operations. For example, inbound call processing server 132 may be configured to host inbound calling accounts 134 established by non-residents of a controlled-environment facility. Inbound call processing server 132 may also be configured to receive inbound calls from the non-residents, such as calls from non-resident devices 105, 106, 109, 112 or 113, and to route such inbound calls to authenticating server 136, which may, as mentioned above be integrated into inbound call processing server 132 in whole or part, such as a module, functionality, or the like thereof, or separate therefrom. Likewise, inbound call processing server 132, and hence authenticating server 136 may, in some embodiments be integrated into controlled-environment facility communications processing system 101, such as a module, functionality, or the like thereof, thereby integrating inbound calling system 130 into controlled-environment facility communications processing system 101.

The inbound call from the non-resident may be intended by the non-resident to be directed to the controlled-environment facility resident media and/or communications device (104) of the resident the non-resident wishes to call. In such cases, inbound call processing server 132 may intercept the inbound call. Additionally or alternatively, inbound resident call server 132 may host a central phone number, such as a toll-free number, for calls directed to controlled-environment facility resident media and/or communications devices 104. In such embodiments, an inbound call from a non-resident device (105, 106, 109, 112 or 113) may be directed to the central phone number and inbound resident call server 132 may correspondingly be configured to accept requests from non-residents for calls into residents via their controlled-environment facility resident media and/or communications device (104).

Inbound call processing server 132 may also be configured to confirm that the controlled-environment facility resident media and/or communications device (104) being called is active (i.e. available and reachable to receive the inbound call, etc.) or inactive (i.e. the called controlled-environment facility resident media and/or communications device is not active or not available, busy, etc.). If the called controlled-environment facility resident media and/or communications device is active, inbound call processing server 132 may connect with the controlled-environment facility resident media and/or communications device (104), but if the controlled-environment facility resident media and/or communications device is not active inbound call processing server 132 may inform the non-resident that the resident is not available for the inbound call.

Inbound call processing system 130, may as also indicated, include authenticating server 136, which may also make use of at least one processor and memory coupled to the processor(s), wherein the memory is configured to store program instructions executable by the processor(s) to cause the server(s) to execute one or more operations. For example, authenticating server 136 may be configured to authenticate that a non-resident is associated with an inbound calling account (134) and confirm that the inbound calling account is associated with an Address Identifier (AID) number of the controlled-environment facility resident media and/or communications device (104) the non-resident has indicated (i.e. the device the non-resident has called or the device of the resident the non-resident has requested). This unique AID may be tied to a resident name and number and a Media Access Control (MAC) address of the subject controlled-environment facility resident media and/or communications device (104). The MAC address and AID are Hardcoded Addresses (HCAs), which may also include a processor number, or the like for uniquely identifying the subject controlled-environment facility resident media and/or communications device (104). Further, authenticating server 136 may receive, via the controlled-environment facility resident media and/or communications device, a PIN entered by the resident and which should be associated with the resident the inbound call is directed to. The PIN can be entered in any number of ways via device 104. For example, the PIN may be spoken and entered using speech recognition and/or it may be entered using a touch screen keypad, or the like. Further, entry of the PIN may incorporate biometric verification into the entering of the PIN itself. For example, if the PIN is entered using the device's touchscreen, fingerprint recognition can be used to verify the typer's identity. Alternatively or additionally, if the PIN is spoken for entry, voice recognition may be used to verify the speaker's identity, while speech recognition may be used to recognize the spoken numbers of the PIN themselves. Further, a camera of controlled-environment facility resident media and/or communications device 104 may be used during spoken or typed PIN entry to capture an image of the party entering the PIN, and the image may be used for facial recognition of the device user to (further) confirm the identity of the user, which may be used for (further) correlation with the PIN. Regardless, authenticating server 136 may verify that the PIN (and verified user) is associated with the AID number of the controlled-environment facility resident media and/or communications device.

Inbound call processing server 132 may connect the non-resident inbound call with the target controlled-environment facility resident media and/or communications device (104). In one example, proceeding with such a connection may result from, as discussed above, server 136 authenticating that the non-resident is associated with the inbound calling account (134), confirming that the inbound calling account is associated with an AID number of the controlled-environment facility resident media and/or communications device (104) and/or verifying that the PIN is associated with the AID number of the controlled-environment facility resident media and/or communications device (104).

FIG. 2 is a flowchart of example process 200 for inbound phone or video calling to intelligent controlled-environment facility resident (e.g. inmate) media and/or communications devices, in accordance with some embodiments. Therein, a method for processing inbound calls to intelligent controlled-environment facility resident media and/or communications devices is illustrated. At 202 an inbound calling account (134) in accordance with a controlled-environment facility communications system/network arrangement is established for a non-resident (e.g. non-inmate friend, family member, etc.) of the controlled-environment facility (e.g. correctional facility). At 204 an inbound call from the non-resident is received into an inbound resident call system (130). This inbound call from the non-resident may be initially be directed directly to the resident, i.e. to the controlled-environment facility resident media and/or communications device (104), and may be (intercepted and) redirected to initially be received in the inbound resident call system (130) for processing in accordance herewith. However, the inbound call from the non-resident may be directed to a central phone number, such as a toll-free number or the like, for calls directed to controlled-environment facility resident media and/or communications devices (104). In such a case, various method implementations may call for acceptance of a request at 206 from the non-resident for a call into the resident and/or resident's controlled-environment facility resident media and/or communications device (104).

At 208 the inbound call may be routed to an authenticating server (136). This authenticating server may, as noted above, be separate from, or integrated into or with an inbound resident call server (132), which in turn, may a or may not be a part of the controlled-environment facility communications processing system (101). At 210 the non-resident is authenticated, such as by the authenticating server (136), as associated with the inbound calling account (134) being accessed. The authenticating server (136), or the like, may then confirm at 212 that the inbound calling account is associated with an AID number of the controlled-environment facility resident media and/or communications device (104) being called. Various implementations of the present systems and methods may also confirm that the called resident (e.g. the resident associated with the controlled-environment facility resident media and/or communications device to which the inbound call is directed) is allowed to communicate with the calling non-resident at 214, such as by determining if the non-resident is on a PAN and/or PAC list associated with the resident.

The inbound resident call system (130) may confirm that the controlled-environment facility resident media and/or communications device (104) is active, at 216. If the controlled-environment facility resident media and/or communications device (104) is found to be active at 216, the inbound resident call system may connect with the controlled-environment facility resident media and/or communications device at 218. However, in response to a failure at 216 to confirm that the controlled-environment facility resident media and/or communications device (104) is active (i.e. the called controlled-environment facility resident media and/or communications device is not active or not available, busy, etc.) the inbound resident call system (130), or the like, may inform the non-resident, at 220, that the resident is not available for the inbound call. At 222 the authenticating server (136), or the like receives a PIN associated with a resident the inbound call is directed to. This personal identification number may be sent via the controlled-environment facility resident media and/or communications device (104) being called by the non-resident. This PIN may be verified at 224, such as by the authenticating server, as being associated with the AID number of the controlled-environment facility resident media and/or communications device (104) being called (and providing the PIN). As noted this PIN may be entered in any number of ways. Additionally, such entry may, incorporate biometric verification into this entering of the PIN. For example, the PIN may be entered using a touchscreen of the controlled-environment facility resident media and/or communications device (104), such that fingerprint recognition can be used to verify the device user's identity, which may be matched to the PIN. Alternatively or additionally, the PIN may be spoken into a microphone of controlled-environment facility resident media and/or communications device (104) to be entered. In such entry, speech recognition may be used to recognize the spoken numbers of the PIN, while voice recognition may be used on the spoken PIN to verify the speaker's identity, which may be matched to the PIN digits. Moreover, the camera of the controlled-environment facility resident media and/or communications device may be used, such as while the PIN is typed or spoken to capture an image of the speaker/user for use in facial recognition of the device user to (further) confirm the identity of the user for correlation with the PIN.

At 226 the non-resident inbound call may be connected with the controlled-environment facility resident media and/or communications device (104), by the inbound resident call system (130), such as, as a result of authenticating that the non-resident is associated with the inbound calling account (134) at 210, confirming that the inbound calling account is associated with an AID number of the controlled-environment facility resident media and/or communications device at 212, confirming that the calling non-resident is allowed to communicate with the resident at 214 and/or verifying that the personal identification number is associated with the AID number of the controlled-environment facility resident media and/or communications device at 224.

In accordance with various implementations of the present systems and methods a flat fee, subscription fee, time-based fee or the like may be charged for the inbound call and decremented at 228 from the inbound calling account (134) established at 202 and associated with the non-resident. For example, a flat fee, per-minute fee, or the like, may be charged for the inbound call. Additionally or alternatively, (a) subscription fees may be periodically (e.g. monthly) charged for inbound calls by the non-resident to one or more residents, beginning, such as, when the non-resident's inbound calling account is established at 202. Such fees may be decremented from an account associated with the non-resident, which may also be established at such time. Further, the connected call may be monitored and/or recorded, such as for investigative purposes at 230. For example, such monitoring may be carried out for detection of impermissible activity such as attempts to initiate three-way calls, and/or monitored for keywords of the like, such as for investigative purposes. Call recordings may be stored for later review for similar investigative purposes. Additionally or alternatively the connected call may be tracked, such as through creation of a communication detail record (CDR) during and/or after the call at 232.

FIG. 3 is a flowchart of another implementation of an example process (300) for inbound phone or video calling to intelligent controlled-environment facility resident media and/or communications devices, in accordance with some embodiments. Therein, a non-resident (e.g. non-inmate), such as a friend or family member of a controlled-environment facility resident (e.g. inmate), may, at 302 access a website, such as may be hosted by the controlled-environment facility and/or an associated entity such as a communications provider for the controlled-environment facility, or the like. At 304 a determination may be made as to whether the non-resident is registered to make inbound calls. If not, the non-resident may register at 306 to make inbound calls, such as by selecting a facility, a resident and choosing a call plan, establishing and funding an inbound calling account (134), and/or the like. The non-resident may then enter personal and/or identification information at 308. At 310 the non-resident may select the facility and resident that they wish to call and at 312 the non-resident may click a webpage button to initiate the call.

Alternatively, or in situations where the non-resident has already established an inbound calling account (134), the non-resident may call a central number, such as a toll-free number, at 314. The present inbound calling system (130) may answer the call at 316 and at 318 IVR functionality associated with the inbound call processing system (130) may prompt the non-resident for their identification information. At 320 the IVR may prompt the non-resident for information about the resident being called, such as identification information, to initiate the call.

Whether the inbound call is initiated via the website (steps 302 through 312) or through a call placed into the system (steps 314 through 320) the inbound calling system verifies that the rules allow calls to the selected resident at 322, such as in the manner discussed above with respect to PAN and PAC lists. At 324 a determination is made as to whether the resident's communication device is online (i.e. whether the resident is on his or her resident communication media device (104)). If it is determined at 324 that the resident is using his or her resident communication media device (104), the inbound calling system (130) directs the call to the resident's communication media tablet device (104) at 326. Thereupon, a phone application program (app) rings on the resident's tablet (104) at 328. At 330 the resident answers the call, and at 332 the inbound call system (130) verifies the resident's identity by requiring a PIN, and/or verifying authentication, such as through voice recognition, key pad, touchpad, fingerprint or other biometric, non-biometric, or other authentication methods. For example, the PIN may be entered by speaking it into the microphone of the controlled-environment facility resident media and/or communications device (104), by entering it on a keypad displayed on the touch screen of the device, and/or the like. This PIN entry process itself may incorporate biometric verification. For example, when the PIN is entered using the touchscreen, fingerprint recognition can be used to verify the user's identity. Alternatively or additionally, a spoken PIN may not only be subjected to speech recognition to recognize the spoken numbers of the PIN, but also to voice recognition to verify the speaker's identity. Further, the camera of controlled-environment facility resident media and/or communications device (104) may be used during spoken or typed PIN entry as part of facial recognition of the device user to (further) confirm the identity of the user for correlation with the PIN.

A determination is made at 334, such as by the inbound calling system (130), as to whether recording is enabled for the call, such as may be required for security reasons, investigative purposes, and/or the like, particularly with respect to the identity of the resident and/or the non-resident. If it is determined at 334 that the call is to be recorded, the inbound calling system (130) starts recording the call at 336. Additionally or alternative, the call may be monitored, such as at 336 for impermissible activity such as attempts at three-way calling, or the like, and/or for keywords, or the like for investigative purposes. Similarly, the recording may be stored for later review for such investigative purposes. Regardless, at 338 the inbound calling system (130) joins the resident and non-resident for the call to take place. Once the call terminates at 340 a CDR may be generated at 342 for accounting, security, investigative, and/or other purposes, and any recording of the call may be linked thereto.

In accordance with some embodiments of the present systems and methods multilayer authentication of a resident may be employed. FIG. 4 is a flowchart of yet another example implementation. Therein, process 400 for inbound calling to intelligent controlled-environment facility resident media and/or communications devices is illustrated, in accordance with some embodiments. In accordance with embodiments of process 400, a resident media and/or communications device, or the like, receives or captures data at 402, which may be used for verifying authentication of a resident operating the device. Receipt of this data at 402 may include receipt of this data for verifying authentication of a resident operating the resident media and/or communications device by an authenticating server. As noted, this data for verifying authentication of a resident may be, or may at least include, a PIN, a password, or the like. Hence, acceptance of the data at 402 may include entry of the PIN, or the like by the resident, via the resident device. At 404, authentication of identification of the resident operating the resident media and/or communications device may be verified, using the data, in addition to verifying that the resident operating the device is associated with an address identifier of the device. An authenticating server, or the like may verify the authentication of the resident operating the device, and/or the authenticating server may verify that the resident operating the device is associated with the address identifier of the device, at 404, using the data.

At 406 it is confirmed that an inbound calling non-resident is associated with the address identifier of the resident media and/or communications device, which may be carried out by the authentication server, an inbound resident call server, and/or (a) similar system(s) or functionality. Then, at 408 a notification is sent to the resident media and/or communications device of the call to the device.

After receipt of the notification from 408, the same or other data for verifying authentication of the resident operating the resident media and/or communications device is received or captured, at 410, via the resident media and/or communications device, for provision of the aforementioned multilayer authentication of the resident operating the device the call it is directed to. To this end, in certain embodiments, the authenticating server, or the like, may receive this same or other data for verifying authentication of a resident operating the resident device at 410. The data for re-verifying authentication of a resident may also or alternatively include a PIN, or the like, which may be accepted (at 410) by (re)entry of the PIN, or the like, via the resident device. Regardless, at 412, the authentication of the resident operating the resident media and/or communications device is re-verified using the data received after receipt of the notification, which may generally include re-verifying that the resident operating the device is associated with the address identifier of the device. Again, the authenticating server, or similar system or functionality may carry out this re-verification of the authentication of the resident operating the device, including whether the resident is associated with the address identifier of the device, at 412.

As a result of confirming that the non-resident is associated with the address identifier of the resident media and/or communications device at 406, as well as verifying and re-verifying authentication of the resident operating the device (including verifying and re-verifying that the resident operating the device is associated with the address identifier of the device) at 404 and 412, respectively, the non-resident inbound call is connected with the device at 414.

In embodiments employing a PIN, a password, or the like, as at least a part of the data used for verifying and/or re-verifying authentication of the resident, process 400, or the like may include, verifying and/or re-verifying that the PIN, or the like is associated with a resident to whom the inbound call is directed. This verification and/or re-verification, may be carried out, as part of the verification at 404, the confirmation that the inbound calling non-resident is associated with the address identifier of the called resident media and/or communications device at 406, during the re-verification at 412, or the like. This PIN-based verification and/or re-verification may be carried out by the authentication server, the inbound resident call server, and/or a similar system or functionality.

Embodiments employing a PIN, or the like, as at least a part of the data used for verifying and/or re-verifying authentication of the resident, process 400, or the like may further accept entry and/or reentry of a spoken PIN, or the like for receipt at 402 and/or for receipt at 410 for verification of authentication of the device user at 404 and/or re-verification at 412. Under such embodiments, entry and/or reentry of a PIN may be accomplished by performing speech recognition on the spoken PIN. For example, the digits, or the like, spoken may be recognized using speech recognition, such as without necessarily using in voice recognition to recognize the speaker.

Additionally or alternatively, in accordance with certain embodiments, the data for verifying and/or re-verifying authentication of a resident, received at 402 and/or 410 and used at 404 and/or 412, may be, or at least include, biometric data. In accordance with such embodiments, the biometric data may be captured and/or recaptured by the resident media and/or communications device, as a part of receipt of the identification data, at 402 and/or 410. For example, the biometric data may be the voice of the resident operating the resident media and/or communications device, wherein verifying and/or re-verifying authentication of the resident operating the device, at 404 and/or 412 uses voice recognition. Therein, verification and/or re-verification of authentication of the resident operating the device may, additionally or alternatively, be carried out using voice recognition on the spoken digits, or the like, in addition to (or in lieu of) using speech recognition to identify the digits spoken.

Under other biometric-based embodiments, the biometric data may be at least one fingerprint of the resident operating the resident media and/or communications device. Thereunder, capturing and/or recapturing data related to at least one fingerprint of the resident operating the device, by the device, during use of the device, may be a part of receipt of the data at 402 and/or 410, or the like. Under fingerprint-use embodiments verifying and/or re-verifying authentication of the resident operating a resident media and/or communications device, at 404 and/or 412 may use fingerprint recognition and this data related to at least one fingerprint. Hence, some such embodiments, and some PIN-based embodiments or the like, may employ receipt at 402 and/or 410 of entry and/or reentry of the PIN via a touchscreen keypad, or the like, displayed by the resident media and/or communications device. Such embodiments may also capture data related to at least one fingerprint of the entering resident, by the resident media and/or communications device, during this entry and/or reentry of the PIN. Whereupon, authentication of the resident operating the resident media and/or communications device may be verified at 404 and/or re-verified at 412 using fingerprint recognition and the data related to at least one fingerprint, so captured, in addition to (or in lieu of) re-verification and/or re-verification of the PIN entered and/or reentered.

In further such biometric-based embodiments, the data may be an image of the resident using the resident media and/or communications device. In such embodiments, image data of the resident operating the device may be captured and/or recaptured, such as a part of receiving the data associated with the resident operating the device at 402 and/or 410, using a camera of the device. The device may capture image data of the resident operating the device, using the camera of the device, during use, such as, for example, during entry and/or reentry of the PIN, or the like, into the device. In accordance with such embodiments, verification and/or re-verification, at 404 and/or 412, of authentication of the resident operating the resident media and/or communications device may be made using facial recognition and the image data.

With reference back to FIG. 1, embodiments of the present systems and methods multilayer authentication may employ an inbound call system for handling inbound calls to resident media and/or communications devices 102, 103 and/or 104, wherein each device has a relatively unique address identifier. Further, each resident device may be configured to receive data to verify and re-verify authentication of a resident operating the device. Such an inbound call system may further include inbound resident call server or functionality 132 configured to connect non-resident inbound calls with corresponding resident media and/or communications devices and authenticating server or functionality 136. Authenticating server 136 or other authentication functionality is configured, in accordance with such multilayer authentication embodiments to verify, using the received or otherwise collected user data (from 402), to authenticate of the resident operating device 103 or 104, such as in accordance with step 404. Authenticating server 136, other authentication functionality, or the like may also be configured to confirm that an inbound calling non-resident is associated with the address identifier of the device (103, 104, etc.) the non-resident is calling, at 406. Authenticating server 136, other authentication functionality, or the like may also send the notification at 408 to the called device (103, 104, etc.) of an inbound call from the calling non-resident to the resident operating the device.

Further, to implement multilayer authentication, authenticating server 136 or other authentication functionality may be further configured to receive, via the notified resident media and/or communications device (102,103, 104, etc.) the same or other data at 410 to re-verify authentication of the resident operating the resident media and/or communications device the non-resident is calling. Thus, authenticating server 136 or other authentication functionality re-verifies authentication of the resident operating the resident media and/or communications device (102,103, 104, etc.) using this same or other data at 412. For example, the Authenticating server 136 or other authentication functionality may again verify that the resident operating the resident media and/or communications device is associated with the address identifier of the resident media and/or communications device (102,103, 104, etc.). This re-verification may be carried out prior to connection of the non-resident inbound call with the resident media and/or communications device (102,103, 104, etc.) by the inbound resident call server at 414.

As noted the data to verify and/or re-verify authentication of a resident may include a PIN, a password, or the like, entered and/or reentered via resident media and/or communications device 103 or 104. In which case, authenticating server 136 may be further configured to verify (404) and/or re-verify (412) the PIN is associated with the resident to whom the inbound call is directed. Alternatively, or additionally, data to verify and/or re-verify authentication of a resident at 404 and/or 412, respectively may include biometric data. In such embodiments, resident media and/or communications device 102, 103 or 104 may be configured to capture and/or recapture the biometric data. For example, biometrics captured during entry of a PIN or the like may be used as part of the verification and/or re-verification at 404 and 412, respectively.

In such an example, a PIN, a password, or the like may be entered (402) and/or reentered (410) via resident media and/or communications device 102, 103 or 104 by being spoken and/or respoken by the resident operating the resident media and/or communications device. In such embodiments, authenticating server 136 may be further configured to complete entry and/or reentry of the PIN using speech recognition and may verify (404) and/or re-verify (412) authentication of the resident operating the resident media and/or communications device using biometrics in the form of voice recognition. Thus, in accordance with the example above, the biometric data may be the voice of the resident operating resident media and/or communications device 102, 103 or 104, in which case, as noted, authenticating server 136 may be configured to verify and/or re-verify, at 404 and/or 412, authentication of the resident operating the device using voice recognition, with, or without, using speech recognition to recognize (enter) a PIN, or the like. In such embodiments, the voice recognition may be ongoing, to verify and/or re-verify the user during use of the device by carrying out biometric voice recognition of the user during such use, to verify the user is the resident associated with the device.

Other biometric data used in accordance with the present systems and methods may include at least one fingerprint of the resident operating a resident media and/or communications device. Resident media and/or communications device 102, 103 or 104 may be configured to capture and/or recapture data related to at least one fingerprint of the resident operating the resident media and/or communications device during use of the resident media and/or communications device for receipt (402 or 410) by authenticating server 136. This fingerprint capture may be carried out covertly during normal use, such as when the resident uses a touchscreen of the device, or the capture may be carried out overtly, wherein the user is requested, via the device, to provide a fingerprint, via the device. In any case, the authenticating server may be configured to verify and/or re-verify (404 and/or 412) authentication of the resident operating the device using fingerprint recognition on the captured data related to at least one fingerprint. In a further detailed example, a PIN may be entered and/or reentered via a touchscreen keypad displayed by resident media and/or communications device 103 or 104. In such embodiments, resident media and/or communications device 102, 103 or 104 may be is configured to covertly, or overtly, capture data related to at least one fingerprint during this entry (402) and/or reentry (410) for receipt by authenticating server 136. Whereupon, authenticating server 136 may verify (404) and/or re-verify (412) authentication of the resident operating the device using fingerprint recognition and the device-captured data related to at least one fingerprint.

As noted, resident media and/or communications device 102, 103 or 104 may have a camera. Thus, the biometric data used for verification and/or re-verification may be an image of the resident using the device. In such embodiments, the resident media and/or communications device may be configured to covertly, or overtly, capture and/or recapture image data of the resident operating the device for receipt by the authenticating server at 402 and/or 410. Authenticating server 136 may, in accordance with such embodiments, be configured to verify (404) and/or re-verify (412) authentication of the resident operating the resident media and/or communications device using facial recognition on the captured and/or recaptured image data. Hence, in another further detailed example, resident media and/or communications device 102, 103 or 104 that includes a camera may covertly, or overtly, capture and/or recapture image data of the resident operating the resident media and/or communications device during entry and/or reentry of the PIN into the device for receipt by authenticating server 136, at 402 and/or 410. Whereupon, authenticating server 136 may verify (404) and/or re-verify (412) authentication of the resident operating the resident media and/or communications device using facial recognition on the image data thus captured during PIN entry/reentry.

Embodiments of the present systems and methods for inbound calls to intelligent controlled-environment facility resident media and/or communications devices (104), as described herein, may be implemented or executed, at least in part, by one or more computer systems. One such computer system is illustrated in FIG. 5. In various embodiments, computer system 500 may be a server, a mainframe computer system, a workstation, a network computer, a desktop computer, a laptop, a tablet computing device, media player, or the like. For example, in some cases, computer 500 may implement one or more steps of example processes 200 and/or 300 described above with respect to FIGS. 1 through 3, and/or a computer system such as computer system 500 may be used as, or as part of, one or more of controlled environment facility communication processing system 101, intelligent controlled-environment facility resident media and/or communications device 104, inbound call processing system 130, inbound resident call server 132, authenticating server 136, and/or the like. In various embodiments two or more of these computer systems may be configured to communicate with each other in any suitable way, such as, for example, via a network, including via a local area network, and/or using wireless functionality.

As illustrated, example computer system 500 includes one or more processors 510 coupled to a system memory 520 via an input/output (I/O) interface 530. Example computer system 500 further includes a network interface 540 coupled to I/O interface 530, and one or more input/output devices 550, such as video device(s) 560 (e.g., a camera), audio device(s) 570 (e.g., a microphone and/or a speaker), and display(s) 580. Computer system 500 may also include a cursor control device (e.g., a mouse or touchpad), a keyboard, etc. Multiple input/output devices 550 may be present in computer system 500 or may be distributed on various nodes of computer system 500. In some embodiments, similar input/output devices may be separate from computer system 500 and may interact with one or more nodes of computer system 500 through a wired or wireless connection, such as over network interface 540.

In various embodiments, computer system 500 may be a single-processor system including one processor 510, or a multi-processor system including two or more processors 510 (e.g., two, four, eight, or another suitable number). Processors 510 may be any processor capable of executing program instructions. For example, in various embodiments, processors 510 may be general-purpose or embedded processors implementing any of a variety of instruction set architectures (ISAs), such as the x86, POWERPC®, ARM®, SPARC®, or MIPS® ISAs, or any other suitable ISA. In multi-processor systems, each of processors 510 may commonly, but not necessarily, implement the same ISA. Also, in some embodiments, at least one processor 510 may be a graphics processing unit (GPU) or other dedicated graphics-rendering device.

System memory 520 may be configured to store program instructions and/or data accessible by processor 510. In various embodiments, system memory 520 may be implemented using any suitable memory technology, such as static random access memory (SRAM), synchronous dynamic RAM (SDRAM), nonvolatile/Flash-type memory, or any other type of memory. As illustrated, program instructions and data implementing certain operations, such as, for example, those described in connection with FIGS. 1 through 3, above, may be stored within system memory 520 as program instructions 525 and data storage 535, respectively. In other embodiments, program instructions and/or data may be received, sent or stored upon different types of computer-accessible media or on similar media separate from system memory 520 or computer system 500. Generally speaking, a computer-readable medium may include any tangible or non-transitory storage media or memory media such as magnetic or optical media—e.g., disk or CD/DVD-ROM coupled to computer system 500 via I/O interface 530, Flash memory, random access memory (RAM), etc. Program instructions and data stored on a tangible computer-accessible medium in non-transitory form may further be transmitted by transmission media or signals such as electrical, electromagnetic, or digital signals, which may be conveyed via a communication medium such as a network and/or a wireless link, such as may be implemented via network interface 540.

In some embodiments, I/O interface 530 may be configured to coordinate I/O traffic between processor 510, system memory 520, and any peripheral devices in the device, including network interface 540 or other peripheral interfaces, such as input/output devices 550. In some embodiments, I/O interface 530 may perform any suitable protocol, timing or other data transformations to convert data signals from one component (e.g., system memory 520) into a format usable by another component (e.g., processor 510). In some embodiments, I/O interface 530 may include support for devices attached through various types of peripheral buses, such as a variant of the Peripheral Component Interconnect (PCI) bus standard or the Universal Serial Bus (USB) standard, for example. In some embodiments, the function of I/O interface 530 may be split into two or more separate components, such as a north bridge and a south bridge, for example. In addition, in some embodiments, some or all of the functionality of I/O interface 530, such as an interface to system memory 520, may be incorporated into processor 510.

Network interface 540 may be configured to allow data to be exchanged between computer system 500 and other devices attached to a network, such as other computer systems, or between nodes of computer system 500. In various embodiments, network interface 540 may support communication via wired or wireless general data networks, such as any suitable type of Ethernet network, for example; via telecommunications/telephony networks such as analog voice networks or digital fiber communications networks; via storage area networks such as Fiber Channel SANs, or via any other suitable type of network and/or protocol.

As shown in FIG. 5, memory 520 may include program instructions 525, configured to implement certain embodiments described herein, and data storage 535, comprising various data accessible by program instructions 525. In an embodiment, program instructions 525 may include software elements corresponding to one or more of the various embodiments illustrated in the above figures. For example, program instructions 525 may be implemented in various embodiments using any desired programming language, scripting language, or combination of programming languages and/or scripting languages (e.g., C, C++, C#, JAVA®, JAVASCRIPT®, PERL®, etc.). Data storage 535 may include data that may be used in these embodiments. In other embodiments, other or different software elements and data may be included.

A person of ordinary skill in the art will appreciate that computer system 500 is merely illustrative and is not intended to limit the scope of the disclosure described herein. In particular, the computer system and devices may include any combination of hardware or software that can perform the indicated operations. Additionally, the operations performed by the illustrated components may, in some embodiments, be performed by fewer components or distributed across additional components. Similarly, in other embodiments, the operations of some of the illustrated components may not be provided and/or other additional operations may be available. Accordingly, systems and methods described herein may be implemented or executed with other computer system configurations.

Although the present invention and its advantages have been described in detail, it should be understood that various changes, substitutions and alterations can be made herein without departing from the spirit and scope of the invention as defined by the appended claims. Moreover, the scope of the present application is not intended to be limited to the particular embodiments of the process, machine, manufacture, composition of matter, means, methods and steps described in the specification. As one of ordinary skill in the art will readily appreciate from the disclosure of the present invention, processes, machines, manufacture, compositions of matter, means, methods, or steps, presently existing or later to be developed that perform substantially the same function or achieve substantially the same result as the corresponding embodiments described herein may be utilized according to the present invention. Accordingly, the appended claims are intended to include within their scope such processes, machines, manufacture, compositions of matter, means, methods, or steps.

Read more
PatSnap Solutions

Great research starts with great data.

Use the most comprehensive innovation intelligence platform to maximise ROI on research.

Learn More

Citation

Patents Cited in This Cited by
Title Current Assignee Application Date Publication Date
Inmate voice mail system and method PUBLIC COMMUNICATIONS SERVICES, INC 11 May 2005 16 November 2006
System and method for interactive messaging and/or allocating and/or upgrading and/or rewarding tickets, other event admittance means, goods and/or services CALLAHAN CELLULAR L.L.C. 06 February 2006 03 August 2006
Systems and methods for identity verification using continuous biometric monitoring SECURUS TECHNOLOGIES HOLDINGS, INC. 30 June 2006 14 February 2008
Fraud prevention system and method JUSTICE SCOTT C.,HOPPER ERIC L.,OBRIST KEN C. 31 January 2003 18 September 2003
Call transfer detection method using voice identification techniques PIKA TECHNOLOGIES INC. 30 June 2006 22 February 2007
See full citation <>

More Patents & Intellectual Property

PatSnap Solutions

PatSnap solutions are used by R&D teams, legal and IP professionals, those in business intelligence and strategic planning roles and by research staff at academic institutions globally.

PatSnap Solutions
Search & Analyze
The widest range of IP search tools makes getting the right answers and asking the right questions easier than ever. One click analysis extracts meaningful information on competitors and technology trends from IP data.
Business Intelligence
Gain powerful insights into future technology changes, market shifts and competitor strategies.
Workflow
Manage IP-related processes across multiple teams and departments with integrated collaboration and workflow tools.
Contact Sales
Clsoe
US10063698 Inbound calls intelligent controlled-environment 1 US10063698 Inbound calls intelligent controlled-environment 2 US10063698 Inbound calls intelligent controlled-environment 3