Patent Description:
For example, banks require at least two individuals when opening a branch. These procedures are put in place to ensure that an employee is not kidnapped during an opening. Two employees arrive at a bank, one goes into the bank while the other remains in the parking lot in his/her car. This ensures that if the intruders are lying in wait within the branch that the second employee can notify the authorities and be capable of escaping. The first employee unlocks the door to the branch, immediately locks the door upon entering the branch, and disarms the security alarms of the branch. Meanwhile, the second employee scans the parking lot for suspicious individuals or activity. A security sweep is performed by the employee inside the branch, and the first employee holds a specific sign up through a window of the branch or performs some other type of signaling to the employee in the parking lot so at to notify that employee that is safe to enter the branch. The second employee enters the branch and locks the door behind him. Additional security sweeps are performed, and the bank is prepared for opening with cash drawers, etc. the branch is then opened for business.

As is apparent, the branch security procedures are not limited to just areas within the branch; rather, the procedures extend to areas proximate to the branch on the outside, such as the parking lot and surrounding external areas. These procedures are necessary to protect the branch staff from threats that may be present both inside and outside the branch during the opening of the branch.

Opening and closing of any enterprise poses unique challenges to ensuring the safety of the employees. It is during these times that the enterprise is most vulnerable. Should a security issue arise during this time, it is imperative that authorities be notified as soon as possible.

<CIT> discloses methods and system for employee monitoring and business rule and quorum compliance monitoring. <CIT> discloses systems and computer implemented methods for generating a virtual or augmented reality-based oversight system of business processes at a location remote from where the business process is executed.

In various embodiments, methods and a system for frictionless security processing are presented.

According to a first aspect of the present invention there is provided a method, comprising: detecting a first device of a first individual within a geofenced area of an establishment; sending an estimated time of arrival to the first device indicating when a second device of a second individual will arrive in the geofenced area; determining the second device of the second individual is within the geofenced area of the establishment; pushing an entry instruction to the first device and the second device indicating that the first individual is authorized to enter the establishment, wherein pushing further includes providing a first security role associated with the first individual to the first device and a second security role associated with the second individual to the second device in the entry instruction for performing opening security procedures to open the establishment, wherein the opening security procedures comprise a first portion including tasks that must be performed for the first security role and a second portion including tasks that must be performed for the second security role; monitoring, through video feeds, the first individual within, and relative to an ingress point of, the establishment with respect to the first portion of the opening security procedures taken by the first individual once inside the establishment, wherein monitoring further includes pushing progress updates to the second device reflecting a real-time progress of the first individual in completing the first portion of the opening security procedures; sending a second entry instruction to the second device upon determining that the first portion of the opening security procedures taken by the first individual have been completed successfully, the second entry instruction indicating that the first portion of the opening security procedures has completed and that the second individual is to enter the establishment for completion of the second portion of the opening security procedures; monitoring through the video feeds the second portion of the opening security procedures taken by both the first individual and the second individual once the second individual is inside the establishment; and logging tasks completed with respect to the first portion and the second portion of the opening security procedures in an audit log.

Aptly, the method further comprises monitoring through the video feeds closing security procedures by closing individuals associated with closing the establishment.

Aptly, sending an estimated time of arrival further includes obtaining a current second device location of the second device associated with the second individual; and pushing an estimated arrival time for the second individual to the first device.

Aptly, determining further includes randomly selecting the first individual for entering the establishment first.

Aptly, providing further includes sending a security code to the first device, wherein the security code is to be entered by the first individual into a security panel upon entry into the establishment.

Aptly, pushing the progress updates further includes pushing the progress updates to one or more third devices not located within the geofenced area.

Aptly, monitoring the first individual further includes listening for a keyword spoken by the first individual while the first individual is inside the establishment as detected by one or more microphones located within the establishment.

Aptly, monitoring the first individual further includes monitoring through the video feeds behaviors and actions of the first individual.

Aptly, monitoring the first individual further includes ensuring through the video feeds that only the first individual is present within the establishment.

According to a second aspect of the present invention there is provided a system, comprising: cameras configured to capture videos outside an establishment and inside the establishment; a first mobile device associated with a first individual; a second mobile device associated with a second individual; a server comprising a processor and a non-transitory computer-readable storage medium; the non-transitory computer-readable storage medium comprising executable instructions representing a security procedure enforcer; the security procedure enforcer when executed on the processor from the non-transitory computer-readable storage medium causing the processor to perform processing comprising: detecting that the first mobile device is within a geofenced area of the establishment; sending an estimated time of arrival to the first mobile device indicating when the second mobile device will arrive in the geofenced area; determining the second mobile device is within the geofenced area; sending a first security role to the first mobile device and a second security role to the second mobile device for performing opening security procedures to open the establishment, wherein the opening security procedures comprise a first portion including tasks that must be performed for the first security role and a second portion including tasks that must be performed for the second security role; monitoring through video feeds the first individual relative to an ingress point of the establishment and while the first individual is located within the establishment and performing the first portion of the opening security procedures; sending real-time progression notifications to the second mobile device with respect to performance of the first portion of the opening security procedures by the first individual; sending a notification to the second mobile device indicating that the first portion of the opening security procedures has completed and that the second individual is to enter the establishment for completion of the second portion of the opening security procedures; monitoring through the video feeds the first individual and the second individual during completion of the second portion of the opening security procedures; and logging tasks completed with respect to the first portion and the second portion of the opening security procedures in an audit log.

Aptly, the security procedure enforcer when executed on the processor from the non-transitory computer-readable storage medium further causing the processor to perform additional processing comprising: sending an alert to a security system when a security threat is detected from the video feeds during the first portion or the second portion of the opening security procedures; and monitoring through the video feeds behaviors and actions of the first individual and the second individual during the first portion and the second portion of the opening security procedures.

These and other aspects of the present invention will be apparent from the following specific description, given by way of example, with reference to the accompanying drawings, in which:.

<FIG> is a diagram of a system <NUM> for frictionless security processing according to an example embodiment. It is to be noted that the components are shown schematically in greatly simplified form, with only those components relevant to understanding of the embodiments being illustrated.

Furthermore, the various components (that are identified in the <FIG>) are illustrated and the arrangement of the components is presented for purposes of illustration only. It is to be noted that other arrangements with more or less components are possible without departing from the teachings of frictionless security processing, presented herein and below.

As used herein and below, the terms "user," "personnel," "actor," "person," "individual," and "subject" may be used interchangeably and synonymously. The terms refer to an individual detected within a secure area or a monitored area where one or more secure assets are present.

The phrases "security procedures" and "security policies" may be used synonymously and interchangeably herein and below. These phrases comprise, inter alia, business rules associated with opening or closing an establishment.

An "object" refers to a secure asset or structure located within the establishment. The object may include drawers, computers, keys, cash, checks, tables, security panels, chairs, windows, notary stamps, doors, documents, terminals, countertops, shelving, items being sold within the establishment, etc. that are being monitored within the image frames of one or more videos provided in video feeds.

System <NUM> includes a plurality of cameras <NUM> that capture time-stamped videos of persons and objects outside and on a premise of an establishment and within the establishment. System <NUM> includes mobile devices <NUM> of employees or agents of the establishment. Moreover, system <NUM> also includes server <NUM>. Server <NUM> includes executable instructions that execute on one or more hardware processors <NUM> of server <NUM> from a non-transitory computer-readable storage medium <NUM> as: device manager <NUM>, person tracker <NUM>, object tracker <NUM>, behavior-action tracker <NUM>, and security procedure enforcer <NUM>. Non-transitory computer-readable-storage medium <NUM> also includes security policies/procedures <NUM> (security policies <NUM>).

Security policies <NUM> represent a data structure comprising and embodying business security rules for opening and closing an establishment. Security policies <NUM> include statements of area identifiers, asset/object identifiers, action identifiers, behavior identifiers, security role identifiers for security roles and responsibilities, and conditions that defines rules. Each rule identifying a task required for a portion of a business opening or closing security procedure. Tasks can be required or can be defined as impermissible. The sequence of the tasks may also be defined within the conditions for the rules. Each rule may also include a resource identifier or a processing action that is to be processed when a given rule is violated. The resource associated with the resource identifier may be an automated application, a system, or an electronic contact address of an individual.

It is to be noted that there may be multiple servers <NUM>, such that the different elements <NUM>-<NUM> may execute on a same server <NUM> or multiple different servers <NUM> networked together.

Cameras <NUM> are preconfigured to capture videos <NUM> of areas that are inside and outside the establishment based on the field-of-view of the lenses of cameras <NUM>. Some of cameras <NUM> may capture images <NUM> representing portions of a different area than a different one of the cameras <NUM> captures video <NUM> for. That is, each video <NUM> can include frames that may overlap multiple ones of the defined areas.

In an embodiment, the cameras <NUM> can be situated at different angles and heights within the areas where they are located. Some cameras <NUM> may be at waist level, chest level, or head level to an average sized person and directed in different directions upward or downward slightly for purposes of capturing the eyes of individuals within the room. Additionally, there one or more overhead cameras <NUM> both inside and outside the establishment. Some cameras <NUM> may be specifically calibrated to capture eyes and faces of the individuals.

Initially, cameras <NUM> are situated in locations throughout the establishment and one or more cameras <NUM> may situated on the outside of the establishment to capture the egress and ingress point of the establishment and optionally to capture a parking lot associated with the establishment Each camera lens configured to cover one or more predefined areas both inside and outside the establishment.

Furthermore, metadata is assigned to each camera <NUM> to include a unique camera identifier, a location identifier (representing the physical location that camera <NUM> is situated), and one or more area identifiers (representing the predefined areas that the lens of camera <NUM> captures in the video <NUM>).

Mobile devices <NUM> include mobile applications that minimally reports device locations of the devices <NUM> to device manager <NUM> using that device's location services. Optionally, mobile applications receive messages and notifications from device manager <NUM>. Device manager <NUM> may also send text messages to devices <NUM> and/or in-app messages to the mobile applications.

Device manager <NUM> is initiated based on a schedule associated with opening and closing the establishment. The schedule is a data structure that includes an opening time and a closing time along with employee identifiers associated with opening and closing security procedures on a given calendar date. Furthermore, the employee identifiers are linked to mobile device identifiers associated with mobile devices <NUM> operated by the employees.

Device manager <NUM> begins requesting or listening for mobile device locations being reported by the mobile applications of mobile devices <NUM> at a configurable period of time before a scheduled opening time for the establishment. Device manager <NUM> is preconfigured with geofenced area associated with a parking lot or outside premises of the establishment. At the preconfigured period of time before the scheduled opening time, device manager <NUM> detects with a first one of the mobile device's is reporting a current real-time device location within the geofenced area. If at least one second device <NUM> is not yet also within the geofenced area, device manager <NUM> determines an estimated arrival time of the second device <NUM> based on its currently reported device location, a route calculated to travel to the geofenced area, and current traffic associated with the route. The estimated arrival time is pushed as a notification to the first device <NUM> that was detected within the geofenced area already. The notification may be sent by text or via an in-app message to the first device <NUM>.

Once device manager <NUM> determines the both devices <NUM> are within the geofenced area, device manager <NUM> sends a notification to initiate opening security procedures for the establishment to security-procedure enforcer <NUM> along with mobile device identifiers for the mobile devices <NUM>. It is to be noted that security-procedure enforcer <NUM> may have access to the schedule and device identifiers for the employees, such that the device identifiers do not have to be included with the notification sent by device manager <NUM>.

Security-procedure enforcer <NUM> instructs trackers <NUM>-<NUM> to being monitoring the videos <NUM> (video feeds <NUM>) streamed from cameras <NUM> at the establishment. Security-procedure enforcer <NUM> obtains the opening security policies <NUM> for the establishment. Next, device manager <NUM>, in accordance with the security policy <NUM>, randomly or as identified in the security policy <NUM>, selects a first device <NUM> associated with a first employee. The second device <NUM> is associated with a second employee. The selection determines roles of the first and second employees during the opening of the establishment. The security policy <NUM> associated with the opening security procedure identifies action identifies for actions that must be completed for each role identifier.

Security-procedure enforcer <NUM> sends the roles and/or action identifiers to mobile devices <NUM> (again this can be via text message or an in-app message). The first individual/employee selected by the security-procedure enforcer <NUM> is then monitored from the video feeds <NUM> by person tracker <NUM> using a bounding box or region of interest within pixels of the image frames from the video feeds <NUM> to track locations of the first employee relative to the ingress point of the establishment and while the first employee is located within the establishment and performing a first portion of the opening security procedures. Object tracker <NUM> monitors the structures and assets within the establishment via bounding boxes or regions of interest within pixels of the image frames for the video feeds <NUM>.

Behavior-action tracker <NUM> utilizes the bounding boxes associated with first employee and the objects to perform more detailed pixel analysis on facial features of the first employee and identify behaviors identified by specific behavior identifiers. Moreover, location information within the pixels for the bounding boxes of the first employee and the objects are used by behavior-action tracker to identify actions that corresponding to action identifiers.

Security-procedure enforcer <NUM> utilizes location information of the bounding boxes for the first employee within the establishment against known locations within the establishment with the object identifiers provided by object tracker <NUM>, action identifiers provided by behavior-action tracker <NUM>, and behavior identifiers provided by tracker <NUM> to evaluate the security policies <NUM> and determine that tasks are being performed in the correct order defined in policies <NUM>.

The security-procedure enforcer <NUM> plugs in the identifiers into the policies <NUM> and evaluates the conditions to determine whether tasks are being completed for the first portion of the opening security procedures of the establishment. Once evaluation indicates that the first portion has been successfully completed, security-procedure enforcer <NUM> sends a notification to second device <NUM> indicating that the second employee may now enter the establishment for completion of a second portion of the opening security procedures.

Trackers <NUM>-<NUM> then provides identifiers and location information for both the first employee and the second employee within the establishment, and security-procedure enforcer <NUM> determines from the security policies <NUM> when the second portion of the opening security procedures are completed.

Security-procedure enforcer <NUM> may also time and date stamp entries along with action identifiers, behavior identifiers, and task identifiers associated with rules of the policies <NUM> in a security log.

In an embodiment, security-procedure enforcer <NUM> sends real-time updates to second device <NUM> as rules/tasks are completed by the first employee during performance of the first portion of the opening security procedures.

Security-procedure enforcer <NUM> also checks from identifiers returned by person tracker <NUM> whether at any point someone other than the first employee during the first portion of the opening security procedures or at any point someone other than the first employee and the second employee are present within the establishment during the second portion of the opening security procedures. If someone is detected, security-procedure enforcer <NUM> raises an alarm (silent) to a security system to dispatch authorities to the establishment. An alert may also be raised during the first portion and/or second portion when the first employee or the second employee are identified as taking impermissible actions. The alert may be processed by a security system in accordance with alert rules.

Moreover, the first and second employees are evaluated from the video feeds <NUM> for behaviors associated with nervousness, agitation, and/or aggression by behavior-action tracker <NUM>. Still further, objects carried into or possessed by first employee and second employee are evaluated by object tracker <NUM>, such that if guns or impermissible objects are brought into establishment, security-procedure enforcer <NUM> may raise an alarm.

The system <NUM> may further be processed in a similar manner for closing security procedures in accordance with different security policies <NUM> evaluated by security-procedure enforcer <NUM>.

Each camera <NUM> provides time stamp and image-frame stamped video <NUM> to server <NUM>. This video <NUM> can be streamed over a wired or wireless connection between cameras <NUM> and server <NUM> to a commonly accessible storage area on server <NUM> that is accessible to person tracker <NUM>, object tracker <NUM>, action tracker <NUM>, and audit-notification manager <NUM>.

Each accessible video frame of each video feed <NUM> includes its metadata (minimally including what was discussed above) with its video frame on the server <NUM>.

One now appreciates how system <NUM> can be used as a real-time visual-based frictionless security enforcement mechanism. The employees are not required to make entries in any security log; although in some cases this may still be required to cross check frictionless security system <NUM>. Moreover, non-compliant actions, behaviors, and security threats may cause alarms of different levels of severity as defined in security policies <NUM>. Threats are automatically identified, and a security system is alerted to dispatch authorities when needed.

A variety of scenarios are possible with system <NUM> some of which but not all of which are now discussed.

Person tracker <NUM> may be equipped with biometric recognition, such that facial features of the individuals being tracked can be derived from the pixels of the video frames and matched to a registered individual or the enterprise. An enterprise identifier for the individual may then be recorded within the security log with the security log entries. For example, facial recognition may ensure that the first employee and second employee are the expected authorized employees performing the first portion and the second portion of the opening and/or closing security procedures of the establishment.

It is noted that other biometric features may be used as well, such as and my way of example only, a fingerprint provided by a security system indicating that the individual was authenticated for access to the establishment, a retina scan, a digit distance and length measurement, a palm reader, a voice print (captured by a microphone), etc. Additionally, features from the video feeds <NUM> do not have to only include facial features and can include any combination of features or a single set of features associated with the individuals: gait, extremity length, height, and/or facial features.

In an embodiment, security-procedure enforcer <NUM> listens for keywords spoken by first employee or second employee captured from microphones <NUM>. When a keyword associated with distress is spoken, security-procedure enforcer <NUM> raises a silent alarm and may notify second employee during the first portion where second employee is not yet within the establishment.

Enforcer <NUM> may utilize a variety of sensors <NUM> after individuals have left or entered different rooms of the establishment during the first portion and/or second portion of the opening or closing security procedures. Enforce <NUM> may also utilizes sensors <NUM> to check that doors to rooms or drawers are in an appropriate state of unlocked or locked.

In an embodiment, enforcer <NUM> includes a reporting interface for automatically or custom generating reports for opening or closing security procedures, secure assets, policy violations, specific individuals, etc..

The above-noted embodiments and other embodiments are now discussed with reference to <FIG>.

<FIG> is a diagram of a method <NUM> for frictionless security processing, according to an example embodiment. The software module(s) that implements the method <NUM> is referred to as a "frictionless opening and closing manager. " The frictionless opening and closing manager is implemented as executable instructions programmed and residing within memory and/or a non-transitory computer-readable (processor-readable) storage medium and executed by one or more processors of a device. The processor(s) of the device that executes the frictionless opening and closing manager are specifically configured and programmed to process the frictionless opening and closing manager. The frictionless opening and closing manager may have access to one or more network connections during its processing. The network connections can be wired, wireless, or a combination of wired and wireless.

In an embodiment, the device that executes the frictionless opening and closing manager is server <NUM>. In an embodiment, server <NUM> is a cloud-based server, a local-area network (LAN)-based server, or a wide-area network (WAN) server.

In an embodiment, the frictionless opening and closing manager is all or some combination of: device manager <NUM>, person tracker <NUM>, object tracker <NUM>, behavior-action tracker <NUM>, and/or enforcer <NUM>.

At <NUM>, the frictionless opening and closing manager detects a first device of a first individual within a geofenced area of an establishment. The first device reports its location using the first device's location services.

In an embodiment, at <NUM>, the frictionless opening and closing manager obtains a current second device location of a second device associated with a second individual and the frictionless opening and closing manager pushes an estimated arrival time for the second individual to the geofenced area to the first device. The second device reports its location using the second device's location services.

At <NUM>, the frictionless opening and closing manager determines a second device of the second individual is within the geofenced area of the establishment.

In an embodiment, of <NUM>, the frictionless opening and closing manager randomly selects the first individual for entering the establishment first.

At <NUM>, the frictionless opening and closing manager pushes an entry instruction to the first device and the second device indicating that the first individual is authorized to enter the establishment while the second individual is to wait in a vehicle of a parking lot of the establishment.

In an embodiment, at <NUM>, the frictionless opening and closing manager provides a first security role associated with the first individual to the first device and a second security role associated with the second individual in the entry instruction.

In an embodiment of <NUM> and at <NUM>, the frictionless opening and closing manager sends a security code to the first device. The security code is to be entered by the first individual upon entry into the establishment.

At <NUM>, the frictionless opening and closing manager monitors, through video feeds and/or sensor events, the first individual within the establishment with respect to opening security procedures taken by the first individual once inside the establishment. In an embodiment, the sensor events are generated by sensors from within the establishment, such as motion sensors, sensors configured to report the first individual performed a task at a monitor, etc. In an embodiment, the first individual is monitored through both video feeds and sensor events.

In an embodiment of <NUM> and <NUM>, at <NUM>, the frictionless opening and closing manager pushes progress updates to the second device that reflects a real-time progress of the first individual in completing a first portion of the opening security procedures.

In an embodiment of <NUM> and at <NUM>, the frictionless opening and closing manager pushes the progress updates to one or more third devices that are not located within the geofenced area.

In an embodiment, at <NUM>, the frictionless opening and closing manager listens for a keyword spoken by the first individual while the first individual is inside the establishment as detected by one or more microphones located within the establishment.

In an embodiment, at <NUM>, the frictionless opening and closing manager monitors, through the video feed, behaviors and actions of the first individual.

In an embodiment, at <NUM>, the frictionless opening and closing manager ensures, through the video feeds, that only the first individual is presenting within the establishment.

At <NUM>, the frictionless opening and closing manager sends a second entry instruction to the second device upon determining that a first portion of the security procedures taken by the first individual has been completed by the first individual.

In an embodiment, at <NUM>, the frictionless opening and closing manager monitors, through the video feeds and/or sensor events, a second portion of the opening security procedures taken by both the first individual and the second individual once the second individual is inside the establishment.

In an embodiment, at <NUM>, the frictionless opening and closing manager monitors, through the video feeds and/or the sensor events, closing security procedures by closing individuals associated with closing the establishment.

<FIG> is a diagram of another method <NUM> for frictionless security processing, according to an example embodiment. The software module(s) that implements the method <NUM> is referred to as an "frictionless security manager. " The frictionless security manager is implemented as executable instructions programmed and residing within memory and/or a non-transitory computer-readable (processor-readable) storage medium and executed by one or more processors of a device. The processors that execute the frictionless security manager are specifically configured and programmed to process the frictionless security manager. The frictionless security manager may have access to one or more network connections during its processing. The network connections can be wired, wireless, or a combination of wired and wireless.

In an embodiment, the device that executes the frictionless security manager is the server <NUM>. In an embodiment, the server <NUM> is a cloud processing environment, a LAN server, or a WAN server.

In an embodiment, the frictionless security manager is all of or some combination of: device manager <NUM>, person tracker <NUM>, object tracker <NUM>, behavior-action tracker <NUM>, enforcer <NUM>, and/or the method <NUM>.

The frictionless security manager presents another and, in some ways, enhanced processing perspective of the method <NUM> discussed above.

At <NUM>, the frictionless security manager determines real-time locations of a first device and a second device.

At <NUM>, the frictionless security manager initiates opening security procedures associated with opening an establishment when the first device and the second device are determined to be within a geofenced area of the establishment based on the real-time locations.

At <NUM>, the frictionless security manager sends instructions to the first device and the second device indicating roles for the opening security procedures.

In an embodiment, at <NUM>, the frictionless security manager designates a first individual associated with the first device as an opener to enter the establishment first while a second individual associated with the second device remains in a vehicle during a first portion of the opening security procedures.

In an embodiment of <NUM> and at <NUM>, the frictionless security manager pushes one or more security codes to the first device that are to be entered into a security device upon entry of the first individual into the establishment.

In an embodiment of <NUM> and at <NUM>, the frictionless security manager pushes progress updates with respect to the first portion of the opening security procedures to the second device.

In an embodiment of <NUM> and at <NUM>, the frictionless security manager sends a notification to the second device indicating that the first portion of the opening security procedures have ended and that the second individual is authorized to enter the establishment for completion of a second portion of the opening security procedures.

At <NUM>, the frictionless security manager monitors, through video feeds, a progression and completion of the opening security procedures associated with the opening of the establishment.

In an embodiment, at <NUM>, the frictionless security manager monitors, through the video feeds, a second progression and a second completion of closing security procedures associated with a closing of the establishment.

<FIG> is a diagram of a system <NUM> for frictionless security processing, according to an example embodiment. The system <NUM> includes a variety of hardware components and software components. The software components of the system <NUM> are programmed and reside within memory and/or a non-transitory computer-readable medium and execute on one or more processors of the system <NUM>. The system <NUM> communicates over one or more networks, which can be wired, wireless, or a combination of wired and wireless.

In an embodiment, the system <NUM> implements, inter alia, the processing described above with the <FIG>.

The system <NUM> includes a plurality cameras <NUM>, a server <NUM>, a first mobile device <NUM>, and a second mobile device <NUM>. The server <NUM> includes at least one hardware processor <NUM>, a non-transitory computer-readable storage medium <NUM> having executable instructions representing a security procedure enforcer <NUM>.

The security procedure enforcer <NUM> when executed from the non-transitory computer-readable storage medium <NUM> on the processor <NUM> is configured to cause the processor <NUM> to perform processing comprising: <NUM>) detecting that the first mobile device <NUM> is within a geofenced area of the establishment; <NUM>) sending an estimated time of arrival to the first mobile device <NUM> indicating when the second mobile device <NUM> will arrive in the geofenced area; <NUM>) determining the second mobile device <NUM> is within the geofenced area; <NUM>) sending a first security role to the first mobile device <NUM> and a second security role to the second mobile device <NUM> for performing opening security procedures to open the establishment; <NUM>) monitoring through video feeds the first individual upon entry of the establishment during a first portion of the opening security procedures; <NUM>) sending real-time progression notifications to the second mobile device <NUM> with respect to performance of the first portion of the opening security procedures by the first individual; <NUM>) sending a notification to the second mobile device <NUM> indicating that the first portion of the opening security procedures has completed and that the second individual is to enter the establishment for completion of a second portion of the opening security procedures; <NUM>) monitoring through the video feeds the first individual and the second individual during completion of the second portion of the opening security procedures; and <NUM>) logging tasks completed with respect to the first portion and the second portion of the opening security procedures in an audit log.

In an embodiment, the security procedure enforcer <NUM> when executed from the non-transitory computer-readable storage medium <NUM> on the processor <NUM> is configured to further cause the processor <NUM> to perform additional processing comprising: <NUM>) sending an alert to a security system when a security threat is detected from the video feeds during the first portion or the second portion of the opening security procedures; and <NUM>) monitoring through the video feeds behaviors and actions of the first individual and the second individual during the first portion and the second portion of the opening security procedures.

In an embodiment, the security procedure enforcer <NUM> is all of or some combination of: device manager <NUM>, person tracker <NUM>, object tracker <NUM>, behavior-action tracker <NUM>, enforcer <NUM>, the method <NUM>, and/or the method <NUM>.

It should be appreciated that where software is described in a particular form (such as a component or module) this is merely to aid understanding and is not intended to limit how software that implements those functions may be architected or structured. For example, modules are illustrated as separate modules, but may be implemented as homogenous code, as individual components, some, but not all of these modules may be combined, or the functions may be implemented in software structured in any other convenient manner.

Furthermore, although the software modules are illustrated as executing on one piece of hardware, the software may be distributed over multiple processors or in any other convenient manner.

Claim 1:
A method, comprising:
detecting a first device of a first individual within a geofenced area of an establishment (<NUM>);
sending an estimated time of arrival to the first device indicating when a second device of a second individual will arrive in the geofenced area;
determining the second device of the second individual is within the geofenced area of the establishment (<NUM>);
pushing an entry instruction to the first device and the second device indicating that the first individual is authorized to enter the establishment (<NUM>), wherein pushing further includes providing a first security role associated with the first individual to the first device and a second security role associated with the second individual to the second device in the entry instruction (<NUM>) for performing opening security procedures to open the establishment, wherein the opening security procedures comprise a first portion including tasks that must be performed for the first security role and a second portion including tasks that must be performed for the second security role;
monitoring, through video feeds, the first individual within, and relative to an ingress point of, the establishment with respect to the first portion of the opening security procedures taken by the first individual once inside the establishment (<NUM>), wherein monitoring further includes pushing progress updates to the second device reflecting a real-time progress of the first individual in completing the first portion of the opening security procedures (<NUM>);
sending a second entry instruction to the second device upon determining that the first portion of the opening security procedures taken by the first individual have been completed successfully (<NUM>), the second entry instruction indicating that the first portion of the opening security procedures has completed and that the second individual is to enter the establishment for completion of the second portion of the opening security procedures;
monitoring through the video feeds the second portion of the opening security procedures taken by both the first individual and the second individual once the second individual is inside the establishment (<NUM>); and
logging tasks completed with respect to the first portion and the second portion of the opening security procedures in an audit log.