Secure multi-user biometric template authentication
Through the multi-user biometric template authentication system, the biometric templates and PINs are dynamically managed between multiple mobile computing devices, solving the problems of device access parameter restrictions and privacy protection, and achieving secure and privacy protection biometric authentication.
Patent Information
- Application Number
- CN202410405588.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-05-12
- Filing Date
- 2024-04-07
- Publication Date
- 2024-11-22
AI Technical Summary
The prior art has difficulties in implementing biometric authentication on multiple mobile computing devices, especially in the case of enterprise scale and cross-work environments, where traditional methods are complex and difficult to meet the requirements of the privacy protection regulations.
Using the multi-user biometric template authentication (MBTA) system, data can be dynamically authenticated and encrypted between multiple mobile computing devices by generating and managing biometric templates and personal identification numbers (PINs) associated with end users to ensure data Secure transmission and storage.
It realizes secure biometric authentication across multiple mobile computing devices, reduces device access parameter restrictions, meets the requirements of privacy protection regulations, and improves data security and user experience.
Smart Images

Figure CN119004431A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure generally relates to aggregating and digitally transforming biometric data, and more particularly to generating biometric templates associated with one or more end users and distributing the biometric templates across multiple mobile computing devices for secure multi-user biometric template authentication purposes. Background Art
[0002] An enterprise may deploy dozens or hundreds of mobile computing devices to be used by employees associated with the enterprise, and in many contexts, the mobile computing devices may not be directly assigned to corresponding members of the staff. Therefore, various members of the staff may interact with the same mobile computing device. In order to ensure the digital security of data associated with the enterprise, the enterprise may employ biometric authentication on the mobile computing devices to verify the identity of a particular member of the staff before the mobile computing device can be accessed and utilized. Applicants have discovered various problems and inefficiencies associated with the traditional deployment of mobile computing devices to be used by employees associated with a particular enterprise, and describe solutions thereof in detail herein. Summary of the invention
[0003] Details of some embodiments of the subject matter described in this specification are set forth in the following drawings and description. Other features, aspects, and advantages of the subject matter will be apparent from the description, drawings, and claims.
[0004] According to a first aspect of the present disclosure, a computer-implemented method is provided. For example, as described herein, the computer-implemented method may be performed by one or more specially configured computing devices embodied in hardware, software, firmware, and / or any combination thereof. In an example embodiment, a computer-implemented method includes receiving a request to generate a biometric template associated with a first terminal user, wherein the request to generate the biometric template associated with the first terminal user is generated via a first mobile computing device associated with a multi-user biometric template authentication (MBTA) system. The computer-implemented method also includes, in response to receiving the request, collecting biometric data associated with the first terminal user. The computer-implemented method also includes generating the biometric template associated with the first terminal user based on the biometric data. The computer-implemented method also includes generating a personal identification number (PIN), wherein the PIN is associated with the biometric template associated with the first terminal user. The computer-implemented method also includes storing at least one of the biometric template or the PIN associated with the first terminal user in an active biometric template database or an active PIN database, respectively, wherein the active biometric template database and the active PIN database are associated with the MBTA system. The computer-implemented method also includes transmitting MBTA data for storage on a plurality of mobile computing devices different from the first mobile computing device, wherein the MBTA data includes at least one of data associated with the active biometric template database or data associated with the active PIN database.
[0005] The computer-implemented method also includes authenticating the first end user based in part on a first interaction with a second mobile computing device of the plurality of mobile computing devices, wherein the first interaction with the second mobile computing device includes collecting, via the second mobile computing device, the biometric data associated with the first end user, and matching the biometric data to the biometric template associated with the first end user using a biometric data matching algorithm, and wherein the biometric template is included in the active biometric template database stored on the second mobile computing device.
[0006] The computer-implemented method also includes authenticating the first end user based in part on a second interaction with the second mobile computing device, wherein the second interaction with the second mobile computing device includes receiving, via the second mobile computing device, the PIN associated with the biometric template associated with the first end user, and verifying the PIN based in part on data associated with the active PIN database stored on the second mobile computing device.
[0007] The computer-implemented method also includes causing at least one of encryption or decryption of the one or more biometric templates based in part on the symmetric shared secret.
[0008] The computer-implemented method also includes where the symmetric shared secret is generated by a secret management system associated with the MBTA system, and where the secret management system is configured to distribute the symmetric shared secret to each respective mobile computing device of the plurality of mobile computing devices.
[0009] The computer-implemented method also includes where the symmetric shared secret is imported into a biometric trusted application within a trusted execution environment (TEE) included in each respective mobile computing device of the plurality of mobile computing devices, and where the symmetric shared secret is associated with a hash-based message authentication code associated with each respective mobile computing device of the plurality of mobile computing devices.
[0010] The computer-implemented method also includes notifying the plurality of mobile computing devices via an MQTT broker associated with the MBTA system that at least one of the active biometric template database or the active PIN database has been updated. The computer-implemented method also includes causing the plurality of mobile computing devices to obtain current data associated with the at least one of the active biometric template database or the active PIN database.
[0011] The computer-implemented method also includes removing at least one of the one or more biometric templates or the one or more PINs from the active biometric template database or the active PIN database, respectively, wherein removing the one or more biometric templates or the at least one of the one or more PINs includes: notifying the multiple mobile computing devices via the MQTT broker associated with the MBTA system that the one or more biometric templates or the at least one of the one or more PINs have been removed; and causing the multiple mobile computing devices to obtain the current data related to the at least one of the active biometric template database or the active PIN database.
[0012] The computer-implemented method also includes remotely enabling or disabling an MBTA authentication mode on the first mobile computing device or at least one of the plurality of mobile computing devices.
[0013] The computer-implemented method also includes where the MBTA data further includes one or more Extensible Markup Language (XML) configuration documents, and where the first mobile computing device and the plurality of mobile computing devices are configured in part by executing one or more commands associated with the one or more XML configuration documents.
[0014] The computer-implemented method also includes where the one or more XML configuration documents are transmitted to the first mobile computing device and the plurality of mobile computing devices by a mobile device management tool associated with the MBTA system.
[0015] The computer-implemented method also includes wherein the first mobile computing device and the plurality of mobile computing devices are configured to scan, via an optical engine, one or more bar codes associated with one or more corresponding XML configuration documents, wherein scanning the one or more bar codes causes the first mobile computing device and the plurality of mobile computing devices to execute the one or more commands associated with the one or more corresponding XML configuration documents.
[0016] The computer-implemented method also includes authenticating a second end user based in part on a first interaction with a third mobile computing device among the plurality of mobile computing devices, wherein the first interaction with the third mobile computing device includes collecting biometric data associated with the second end user via the third mobile computing device, and matching the biometric data associated with the second end user to a biometric template associated with the second end user using a biometric data matching algorithm, wherein the biometric template associated with the second end user is generated in response to receiving a request by the MBTA system from a fourth mobile computing device to generate the biometric template associated with the second end user, and wherein the biometric template associated with the second end user is included in the active biometric template database stored on the third mobile computing device.
[0017] The computer-implemented method also includes authenticating the second end user based in part on a second interaction with the third mobile computing device, wherein the second interaction with the third mobile computing device includes receiving, via the third mobile computing device, a PIN associated with the biometric template associated with the second end user, and verifying the PIN based in part on data associated with the active PIN database stored on the third mobile computing device.
[0018] According to a second aspect of the present disclosure, a system for providing a secure MBTA is provided. In an example embodiment, the system includes one or more processors, a non-transitory memory, and one or more programs stored in the non-transitory memory. The one or more programs include instructions configured to perform any of the example computer-implemented methods described herein.
[0019] According to a third aspect of the present disclosure, a computer program product for providing a secure MBTA. In an example embodiment, the computer program product includes at least one non-transitory computer-readable storage medium having computer program code instructions stored thereon, which, when executed by at least one processor, configure the computer program product to perform any of the example computer-implemented methods described herein. BRIEF DESCRIPTION OF THE DRAWINGS
[0020] The description of the exemplary embodiments may be read in conjunction with the accompanying drawings. It should be understood that for simplicity and clarity of illustration, the elements shown in the figures are not necessarily drawn to scale. For example, the dimensions of some of the elements are exaggerated relative to other elements. Embodiments incorporating the teachings of the present disclosure are shown and described with respect to the drawings presented herein, in which:
[0021] Figure 1 An exemplary multi-user biometric template authentication (MBTA) system configured for secure MBTA according to one or more embodiments described herein is illustrated;
[0022] Figure 2 illustrates a schematic block diagram of an exemplary mobile computing device to be used in accordance with one or more embodiments described herein;
[0023] Figure 3 illustrates a schematic block diagram of MBTA external auxiliary components associated with an exemplary MBTA system according to one or more embodiments described herein;
[0024] Figure 4 illustrates a data flow diagram for facilitating a safe MBTA according to one or more embodiments described herein;
[0025] Figure 5 illustrates a process flow diagram for updating an active personal identification number (PIN) database associated with an MBTA system according to one or more embodiments described herein;
[0026] Figure 6 illustrates a process flow diagram for adding and / or updating a biometric template (BT) in an active BT database according to one or more embodiments described herein;
[0027] Figure 7 illustrates a process flow diagram for deleting BT from an active BT database according to one or more embodiments described herein;
[0028] Figure 8illustrates a process flow diagram for enabling or disabling a multi-user biometric authentication mode for one or more mobile computing devices according to one or more embodiments described herein;
[0029] Fig. 9 illustrates a process flow diagram for importing a symmetric shared secret into one or more mobile computing devices for biometric template encryption purposes according to one or more embodiments described herein;
[0030] FIG. 10A to FIG. 10B illustrates an exemplary user interface of a BT management application rendered on a mobile computing device associated with an MBTA system according to one or more embodiments described herein;
[0031] FIG. 11A to FIG. 11B illustrates another exemplary user interface of a BT management application rendered on a mobile computing device associated with an MBTA system according to one or more embodiments described herein; and
[0032] Fig.12 A process flow diagram for a method associated with a secure MBTA is illustrated according to one or more embodiments described herein. DETAILED DESCRIPTION
[0033] Now will specifically refer to the embodiments, examples of which are illustrated in the accompanying drawings. In the following specific embodiments, many specific details are set forth to provide a thorough understanding of the various described embodiments. However, it will be appreciated by those of ordinary skill in the art that the various described embodiments can be practiced without these specific details. In other cases, well-known methods, procedures, parts, circuits and networks are not described in detail to avoid obscuring the various aspects of the embodiments. Unless otherwise indicated, the term "or" is used herein in both alternative and combined senses. The terms "illustrative", "example" and "exemplary" are examples for indicating no quality level. Throughout the content, similar reference numerals refer to similar elements.
[0034] The phrases "in one embodiment," "in an embodiment," "according to an embodiment," and the like generally mean that the particular feature, structure, or characteristic following the phrase can be included in at least one embodiment of the present disclosure, and may be included in more than one embodiment of the present disclosure (importantly, such phrases are not necessarily referring to the same embodiment).
[0035] The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any implementation described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other implementations.
[0036] If the specification states that a component or feature "may", "could", "should", "will", "preferably", "likely", "usually", "optionally", "for example", "often", or "might" (or other such words) be included or have a property, the particular component or feature is not required to be included or have that property. Such components or features may optionally be included in some embodiments, or they may be excluded.
[0037] Overview
[0038] As described herein, a particular enterprise may deploy dozens or hundreds of mobile computing devices to be used by employees associated with the particular enterprise, and in many contexts, the mobile computing devices may not be directly assigned to respective members of the staff. Therefore, various members of the staff may interact with the same mobile computing device. In order to ensure the digital security of data associated with the enterprise, the enterprise may employ biometric authentication on mobile computing devices to verify the identity of a particular member of the staff before the mobile computing device can be accessed and utilized. However, there are inherent problems associated with traditional means of biometrically authenticating members of a large number of employees on a large number of mobile computing devices associated with a particular enterprise.
[0039] The initial obstacle presented by conventional biometric authentication systems and protocols is that biometric authentication of a particular end user must occur on a particular mobile computing device associated with that particular end user. Typically, due to strict device access parameters embedded by the vendor and / or manufacturer of the particular mobile computing device, a biometric template (BT) (e.g., a digital representation of a fingerprint associated with a particular end user) must be stored locally on the particular mobile computing device. Furthermore, many modern mobile computing devices only allow a small number of BTs to be stored locally and / or associated with the mobile computing device, which greatly limits the number of end users that can access the mobile computing device.
[0040] These problems are greatly compounded when addressed at an enterprise scale. For example, if an enterprise employs a large workforce including dozens or hundreds of employees who must share a discrete number of mobile computing devices to complete work-related tasks, a system for biometrically authenticating members of the workforce across all mobile computing devices is desirable. Alternatively, the enterprise may have multiple work environments between which members of the workforce must roam and access corresponding mobile computing devices located in the multiple work environments.
[0041] Additionally, businesses increasingly need to meet the privacy requirements of the European General Data Protection Regulation (GDPR) and / or the California Consumer Privacy Act (CCPA), as well as any new privacy regulations that emerge as a result, which are created to give end users control over their personal information (e.g., biometric data associated with the end user). Security schemes are necessary to protect the privacy of personally identifiable information (PII) such as BT. Security schemes such as symmetric and asymmetric encryption, while obvious solutions, complicate the enrollment and verification process. As the use of biometric technology has evolved, ISO standards for template protection schemes (e.g., ISO 24745) and the evaluation of template protection schemes (e.g., ISO30136) have emerged.
[0042] The main criteria for template projection schemes are irreversibility, non-linkability, and confidentiality. The requirement of the irreversibility criterion is that for a fixed predefined purpose (such as identification), the raw biometric data must be transformed into an irreversible representation of the task that accurately fits the predefined purpose. The requirement of the non-linkability criterion is that there must be no relationships between the stored biometric templates across applications or databases. The requirement of the confidentiality criterion is that the biometric templates must be saved and not exposed to unauthorized parties attempting to gain unauthorized access. Meeting this set of criteria is now required to comply with the privacy principles of GDPR, CCPA, and emerging privacy protection regulations.
[0043] Therefore, to address these and / or other issues, various embodiments of the present disclosure relate to computer-implemented methods, systems, and computer program products for biometric data aggregation and secure multi-user biometric template authentication (MBTA) across multiple mobile computing devices associated with a particular enterprise. Various embodiments provide an MBTA system configured to: provide multiple mobile computing devices; generate, update, and / or remove one or more BTs associated with one or more corresponding end users; and dynamically configure the multiple mobile computing devices to securely authenticate the one or more end users based on biometric data associated with one or more end users associated with enterprise employees. Various embodiments also provide means for securely encrypting, decrypting, storing, and / or transmitting one or more portions of MBTA data (e.g., BT data, user authentication data, system configuration data, etc.) through the MBTA system.
[0044] In various contexts, a BT may be understood as a digital representation of one or more portions of biometric data associated with a particular end user. For example, when raw biometric data associated with a particular end user is captured (e.g., via biometric hardware associated with a particular mobile computing device), various minutiae associated with the raw biometric data may be identified, mapped, and / or converted into a computer-readable format. For example, various minutiae associated with a configuration related to a fingerprint or facial features of the end user may be captured, and these minutiae may be mapped. Minutiae points and / or minutiae point mappings may be converted into a computer-readable format referred to as a biometric template (e.g., such as in a data file that includes, for example, a combination of bits representing minutiae points and / or minutiae point mappings). Advantageously, as will be described herein, a BT may be encrypted so as to protect the biometric data associated with the end user.
[0045] Therefore, because the BT associated with the end user represents unique biometric data related to the end user, the BT can be used for various authentication operations related to identifying the end user on the mobile computing device. Non-limiting examples of biometric data associated with the end user include, but are not limited to, fingerprint data, palm data, vein data, retina and / or iris data, voice data, facial feature data (e.g., face shape, eye shape, nose shape, etc.), body feature data (e.g., ear shape), DNA data, handwriting data, and / or any other physical and / or personal data related to a particular end user.
[0046] Embodiments of the present disclosure may be configured to enroll one or more end users into an MBTA system. As will be described herein, the enrollment process includes collecting biometric data associated with a particular end user, generating a BT based on the biometric data, generating a unique PIN for the end user associated with the BT, and / or maintaining a storage system associated with the MBTA system that manages lists of active BTs and PINs associated with one or more end users enrolled in the MBTA system. One or more lists (e.g., an active BT list and / or an active PIN list associated with the BT and / or PIN of one or more enrolled end users, respectively) may be transmitted and stored on one or more mobile computing devices associated with the MBTA system. In addition, whenever a change is made to one or more active BT and / or PIN lists, the MBTA system may automatically publish one or more notifications to one or more mobile computing devices such that each respective one of the one or more mobile computing devices contains a local copy of the most current active BT and / or PIN list. In this regard, embodiments of the present disclosure provide means for verifying and / or authenticating one or more end users on one or more corresponding mobile computing devices associated with an MBTA system (e.g., via one or more biometric data matching algorithms) using biometric data associated with the one or more corresponding end users, BT, and / or a PIN associated with the BT.
[0047] Therefore, by adopting one or more of the techniques disclosed herein, various technical improvements can be achieved. For example, adopting one or more of the techniques disclosed herein can provide a secure MBTA for a large number of mobile computing devices associated with a particular enterprise. In addition, adopting one or more of the techniques disclosed herein can provide a means for alleviating strict device access parameters embedded in multiple mobile computing devices by suppliers and / or manufacturers of multiple mobile computing devices by, for example, overcoming device access parameters that limit the number of BTs that can be associated with a particular device. Additionally, computing resources and business resources associated with an enterprise utilizing the proposed MBTA system are reduced because an end user associated with the enterprise only needs to register once into the MBTA system via a first mobile computing device in order to obtain access to a large number of other mobile computing devices associated with the enterprise. For example, according to various embodiments, an end user can register into the MBTA system on a first device at a first business location associated with the enterprise, and will be able to be automatically authenticated in a biometric manner on a second mobile computing device located at a second business location associated with the enterprise.
[0048] Exemplary systems and devices of the present disclosure
[0049] Figure 1An exemplary multi-user biometric template authentication (MBTA) system 100 configured for a secure MBTA is illustrated, according to one or more described features of one or more embodiments of the present disclosure. According to various embodiments, the MBTA system 100 includes one or more MBTA external auxiliary components 102, a network 104, one or more mobile computing devices 106a-n, and / or an MBTA database 108. The MBTA system 100 is associated with one or more application products, such as a multi-user authentication platform, a biometric data platform, a data security platform, an asset management platform, an asset performance platform, a global operations platform, a site operations platform, an industrial asset platform, an industrial process platform, a digital worker platform, an energy and sustainability platform, a healthy building platform, an energy optimization platform, a predictive maintenance platform, a centralized control platform, and / or another type of asset platform.
[0050] In one embodiment, the MBTA system 100 operates in conjunction with one or more server systems (e.g., server devices such as the MBTA database 108), one or more data sources, and / or one or more assets associated with an enterprise. In one or more embodiments, the MBTA system 100 includes one or more processors and memory. In various embodiments, the MBTA system 100 also involves one or more technologies, such as enterprise technology, industrial technology, conjoined building technology, Internet of Things (IoT) technology, user interface technology, data analysis technology, digital transformation technology, cloud computing technology, cloud database technology, server technology, network technology, private enterprise network technology, wireless communication technology, machine learning technology, artificial intelligence technology, digital processing technology, electronic equipment technology, computer technology, supply chain analysis technology, aircraft technology, network security technology, navigation technology, asset visualization technology, oil and gas technology, petrochemical technology, refining technology, process plant technology, procurement technology, and / or one or more other technologies.
[0051] In addition, the MBTA system 100 provides improvements to one or more technologies, such as enterprise technology, industrial technology, conjoined building technology, IoT technology, user interface technology, data analysis technology, digital transformation technology, cloud computing technology, cloud database technology, server technology, network technology, private enterprise network technology, wireless communication technology, machine learning technology, artificial intelligence technology, digital processing technology, electronic equipment technology, computer technology, supply chain analysis technology, aircraft technology, network security technology, navigation technology, asset visualization technology, oil and gas technology, petrochemical technology, refining technology, process plant technology, procurement technology, and / or one or more other technologies. In a specific implementation, the MBTA system 100 improves the performance of user computing devices. For example, in one or more embodiments, the MBTA system 100 improves the processing efficiency of mobile computing devices, reduces the power consumption of computing devices, improves the quality of data provided by user computing devices, etc. In various embodiments, the MBTA system 100 improves the performance of user computing devices by optimizing biometric data associated with one or more end users, by reducing the number of user interactions with an interactive user interface (e.g., associated with one or more mobile computing devices 106a-n), and / or by reducing the number of computing resources required to render content via the interactive user interface.
[0052] In one or more embodiments, the MBTA system 100 aggregates biometric data associated with one or more end users (e.g., employees associated with a particular enterprise) and can facilitate secure MBTA for the one or more end users across multiple computing devices (e.g., mobile computing devices 106a-n). In various embodiments, to facilitate secure MBTA, the MBTA system 100 can generate, distribute, and integrate a biometric template management application into one or more mobile computing devices 160a-n. The biometric template management application can facilitate one or more programs associated with the MBTA system 100 on the one or more mobile computing devices 106a-n. For example, the biometric template management application may facilitate the execution of one or more procedures associated with the MBTA (such as transmitting a request (e.g., a request to generate a biometric template (BT)) from a particular mobile computing device 106a, receiving and / or processing MBTA data, enrolling an end user into the MBTA system 100 (e.g., collecting biometric data from an end user, assigning a PIN to an end user, etc.), causing an update of an active BT database, an active PIN database, and / or any data store associated with the MBTA system 100 (e.g., a server system, a cloud-based database, etc.), causing configuration of the particular mobile computing device 106a, and / or facilitating any other process associated with the MBTA system 100 because the biometric template management application is associated with the particular mobile computing device 106a.
[0053] In one or more embodiments, one or more components of the MBTA system 100 communicate via a network 104. In various embodiments, the network 104 is any suitable network or combination of networks and supports any suitable protocol suitable for communicating data to and from the components of the MBTA system 100. According to various embodiments, the network 104 includes a public network (e.g., the Internet), a private network (e.g., a network within an organization), or a combination of public and / or private networks. According to various embodiments, the network 104 includes one or more networks that connect devices and / or components in a network layout to allow communication between the devices and / or components. For example, in one or more embodiments, the network 104 is implemented as the Internet, a wireless network, a wired network (e.g., Ethernet), a local area network (LAN), a wide area network (WAN), Bluetooth, near field communication (NFC), or any other type of network that provides communication between one or more components of the network layout. In some embodiments, the network 104 is implemented using a cellular network, a satellite, a licensed radio, or a combination of cellular, satellite, licensed radio, and / or unlicensed radio networks.
[0054] In various embodiments, one or more mobile computing devices 106a-n are integrated within or correspond to a barcode scanner, a smartphone, a tablet computer, a mobile computer, a desktop computer, a laptop computer, a workstation computer, a wearable device, a virtual reality device, an augmented reality device, or another type of computing device associated with the MBTA system 100. The one or more mobile computing devices 106a-n may generate a request and transmit the request to one or more components of the MBTA system 100 (e.g., one or more of the MBTA external auxiliary components 102) via the network 104. In various embodiments, the MBTA system 100 transmits MBTA data to the one or more mobile computing devices 106a-n via the network 104.
[0055] The MBTA system 100 also includes an MBTA database 108. In various embodiments, the MBTA database 108 may embody, be integrated with, or be embodied by one or more server systems associated with the MBTA system 100. For example, the MBTA database may be integrated with a privacy management system, an FTP server, and / or an MQTT broker associated with the MBTA system 100. The MBTA database 108 may be configured to store, update, delete, and / or otherwise manage one or more portions of data associated with the MBTA system 100. For example, in various embodiments, the MBTA database 108 may manage and / or be integrated with one or more active BT lists and / or one or more PIN lists associated with the MBTA system 100. The MBTA database 108 is also configured to manage one or more portions of data associated with one or more requests 216 and / or one or more portions of the MBTA data 112. In various embodiments, the MBTA database 108 may be configured as a cloud-based storage system capable of communicating with various components of the MBTA system 100 via the network 104.
[0056] Figure 2 A schematic block diagram of an exemplary mobile computing device 106a to be used in accordance with one or more embodiments described herein is illustrated. As described herein, in various embodiments, the mobile computing device 106a may be embodied as one or more computing devices, such as a scanner (e.g., a barcode scanner, etc.), a smart phone, a tablet computer, a wearable device, a handheld computing device, an augmented reality device, a virtual reality device, a sensor device, or another type of mobile computing device. In some embodiments, the mobile computing device 106a may be a scanning engine device (e.g., a two-dimensional scanning engine device or a three-dimensional scanning engine device). However, it should be noted that the following description of the mobile computing device 106a may be a scanning engine device (e.g., a two-dimensional scanning engine device or a three-dimensional scanning engine device). Figure 2 exemplified in and about Figure 2The components, devices or elements described may not be mandatory, and thus one or more components, devices or elements may be omitted in certain embodiments. Additionally, some embodiments may include Figure 2 exemplified in and about Figure 2 The mobile computing device 106a may generate a request 216 and transmit the request 216 to one or more components of the MBTA system 100 (e.g., one or more of the MBTA external auxiliary components 102) via the network 104. In various embodiments, the MBTA system 100 transmits MBTA data 214214 to one or more mobile computing devices 106a-n via the network 104.
[0057] In one or more embodiments, the request 216 is a request to enroll a particular end user into the MBTA system 100, wherein enrolling the particular end user includes generating a BT associated with the particular end user, generating a PIN and / or associating the PIN to the BT associated with the particular end user, and / or storing the BT and the PIN in an active BT database and an active PIN database, respectively. In this regard, in some embodiments, the request 216 may be a request to update one or more data stores and / or computing devices (e.g., a server system, a cloud-based storage system, a database, an interactive table, etc.) associated with the MBTA system 100. Thus, the request 216 may be a request to add, delete, augment, and / or otherwise manage biometric data, identification data, and / or user authentication data associated with the particular end user associated with the MBTA system 100. Additionally or alternatively, in some embodiments, the request 216 may be a request to configure and / or reconfigure one or more mobile computing devices 106a-n to facilitate MBTA on the one or more mobile computing devices 106a-n. The request 216 may include identification data associated with one or more end users (e.g., personally identifiable information (PII)), identification data associated with the mobile computing device 106a that generates the request 216 (e.g., device serial number, MAC address, IP address, etc.), and / or any other identification data associated with an enterprise associated with the MBTA system 100.
[0058] In various embodiments, the MBTA data 214 generated by one or more components of the MBTA system 100 includes one or more portions of BT data (e.g., biometric data associated with one or more end users, one or more active BTs, etc.), one or more portions of user authentication data (e.g., active PIN data associated with active BTs related to respective end users, password data, user login data, etc.), and / or one or more portions of system configuration data (e.g., one or more XML configuration documents, symmetric shared secrets, encryption / decryption data, data associated with one or more public / private key pairs, data associated with one or more active BT lists and / or active PIN lists, etc.). In one or more embodiments, the MBTA system 100 may configure the MBTA data 214 based on one or more portions of BT data, user authentication data, and / or system configuration data.
[0059] In various embodiments, the biometric data associated with a particular end user may include, but is not limited to, fingerprint data, palm data, vein data, retina and / or iris data, voice data, facial feature data (e.g., face shape, eye shape, nose shape, etc.), body feature data (e.g., ear shape), DNA data, handwriting data, and / or any other physical and / or personal data associated with a particular end user. In various embodiments, the MBTA system 100 is configured to generate one or more BTs associated with the biometric data associated with a particular end user. Additionally or alternatively, in various embodiments, the MBTA data 214 includes identification data (e.g., PII) associated with one or more end users, identification data (e.g., device serial number, MAC address, IP address, etc.) associated with one or more mobile computing devices 106a-n, and / or any other applicable identification data associated with an enterprise associated with the MBTA system 100.
[0060] In another example, in one or more embodiments, the MBTA data 214 includes one or more notifications associated with the MBTA data 214. In some embodiments, a message queue telemetry transport (MQTT) agent associated with the MBTA system 100 may generate one or more notifications associated with the MBTA data 214. Based on the notifications received by the MBTA system 100 (e.g., via the MQTT agent), one or more mobile computing devices 106a-n may be instructed to perform various actions associated with the methods described herein. As a non-limiting example, based on the notifications generated and / or transmitted by the MQTT agent, one or more mobile computing devices 106a-n may download and / or otherwise obtain one or more of an active BT list and / or an active PIN list associated with the MBTA system 100, wherein the active BT list and / or the active PIN list respectively include data associated with one or more BTs and / or PINs associated with one or more end users currently registered with the MBTA system 100. As another non-limiting example, notifications generated and / or transmitted by the MQTT broker may include and / or be associated with an XML configuration document such that, when the XML configuration document is received by one or more mobile computing devices 106a-n, the one or more mobile computing devices 106a-n are instructed to configure (or reconfigure) one or more hardware and / or software settings, parameters, operating modes, user access levels, applications, etc. associated with the one or more mobile computing devices 106a-n.
[0061] In one or more embodiments, the MBTA data 214 also includes one or more visual elements of a visual display (e.g., as rendered by a user interface component) of one or more mobile computing devices 106a-n for rendering an interactive user interface based on a corresponding user interface configuration. For example, the MBTA system 100 may cause, via a biometric template management application, the rendering of visual data associated with one or more processes and / or methods associated with the MBTA system 100 to be presented via a corresponding electronic interface of the one or more mobile computing devices 106a-n. In various embodiments, the rendering may be caused via one or more computer executable instructions included in the MBTA data 214. In some embodiments, the visual display of the one or more mobile computing devices 106a-n displays one or more graphical elements associated with the MBTA data 214. In some embodiments, the electronic interface component of the one or more mobile computing devices 106a-n renders one or more interactive display elements associated with the MBTA data 214. In some embodiments, the MBTA system 100 may configure the electronic interface to render one or more interactive display elements associated with the biometric template management application.
[0062] The mobile computing device 106a may include or otherwise communicate with a processing circuit 202, which may be configured to perform actions according to one or more embodiments disclosed herein. In this regard, the processing circuit 202 may be configured to perform and / or control the execution of one or more functions of the mobile computing device 106a according to various embodiments, and thus may provide a component for performing functions of the mobile computing device 106a according to various embodiments. According to one or more embodiments, the processing circuit 202 may be configured to perform data processing, application execution, and / or other processing and management services. In some embodiments, the mobile computing device 106a or a portion or component thereof (such as the processing circuit 202) may be embodied as a chip or a chipset, or include a chip or a chipset. In other words, the mobile computing device 106a or the processing circuit 202 may include one or more physical packages (e.g., chips), which include materials, components, and / or wires on a structural assembly (e.g., a footboard). The structural assembly may provide physical strength, dimensional conservation, and / or electrical interaction restrictions for the component circuits included thereon. Thus, in some cases, the mobile computing device 106a or the processing circuit 202 may be configured to implement embodiments of the present disclosure on a single chip or as a single “system on a chip.” Thus, in some cases, a chip or chipset may constitute a means for performing one or more operations for providing the functionality described herein.
[0063] In some embodiments, processing circuit 202 may include processor 206, and in some embodiments, such as Figure 2 In the illustrated embodiment, a memory 204 may also be included. The processing circuit 202 may communicate with the user interface 208 and / or the communication interface 210, or otherwise control the user interface and / or the communication interface. Therefore, the processing circuit 202 may be embodied as a circuit chip (e.g., an integrated circuit chip) configured to perform the operations described herein (e.g., using hardware, software, or a combination of hardware and software).
[0064] The processor 206 can be embodied in several different ways. For example, the processor 206 can be embodied as various processing components, such as one or more of a microprocessor or another processing element, a coprocessor, a controller, or various other computing or processing devices, including integrated circuits, such as ASICs (application-specific integrated circuits), FPGAs (field programmable gate arrays), etc. Although illustrated as a single processor, it should be understood that the processor 206 can include multiple processors. Multiple processors can communicate operably with each other and can be configured together to perform one or more functions of the mobile computing device 106a as described herein. In some embodiments, the processor 206 can be configured to execute instructions stored in the memory 204 or otherwise accessible to the processor 206. Therefore, whether configured by hardware or by a combination of hardware and software, the processor 206 can represent an entity that can perform operations according to the embodiments of the present disclosure while being configured accordingly (e.g., physically embodied in a circuit (in the form of a processing circuit 202)). Therefore, for example, when the processor 206 is embodied as an ASIC, an FPGA, etc., the processor 206 can be hardware that is specially configured for performing the operations described herein. Alternatively, as another example, when the processor 206 is embodied as an executor of software instructions, the instructions may specifically configure the processor 206 to perform one or more operations described herein.
[0065] In some embodiments, the memory 204 may include one or more non-transitory memory devices, such as fixed or removable volatile and / or non-volatile memory. In this regard, the memory 204 may include a non-transitory computer-readable storage medium. It should be understood that although the memory 204 is illustrated as a single memory, the memory 204 may also include multiple memories. The memory 204 may be configured to store information, data, applications, instructions, etc. for enabling the mobile computing device 106a to perform various functions according to one or more embodiments. For example, the memory 204 may be configured to buffer input data for processing by the processor 206. Additionally or alternatively, the memory 204 may be configured to store instructions for execution by the processor 206. As another alternative, the memory 204 may include one or more databases that can store a variety of files, content, or data sets. In the content of the memory 204, applications may be stored for execution by the processor 206 to perform functions associated with each corresponding application. In some cases, memory 204 may be in communication with one or more of processor 206 , user interface 208 , and / or communication interface 210 via a bus to transfer information between components of mobile computing device 106a .
[0066] The user interface 208 may communicate with the processing circuit 202 to receive an indication of a user input at the user interface 208 and / or provide an auditory output, a visual output, a mechanical output, or other output to the user. Thus, the user interface 208 may include, for example, biometric hardware (e.g., a biometric sensor, a biometric reader, a fingerprint scanner, a retinal scanner, etc.), a keyboard, a mouse, a joystick, an electronic display, a touch screen display, a microphone, a speaker, and / or other input / output mechanisms. Thus, in some embodiments, the user interface 208 may provide a user with a means for accessing and interacting with the mobile computing device 106a and / or other devices.
[0067] The communication interface 210 may include one or more interface mechanisms for enabling communication with other devices and / or networks. In some cases, the communication interface 210 may be any component, such as a device or circuit embodied in hardware or a combination of hardware and software, that is configured to receive data from a network and / or any other device or module in communication with the processing circuit 202, and / or transmit data to the network and / or the other device or module. As an example, the communication interface 210 may be configured to enable the mobile computing device 106a to communicate with various components of the MBTA system 100 (e.g., MBTA external auxiliary components 102). For example, in various embodiments, the mobile computing device 106a may receive MBTA data 214 from one or more of the MBTA external auxiliary components 102 via the communication interface 210. Similarly, in various embodiments, the mobile computing device 106a may transmit one or more requests 216 to one or more of the MBTA external auxiliary components 102 associated with the MBTA system 100 via the communication interface 210. Thus, the communication interface 210 may, for example, include an antenna (or multiple antennas) and supporting hardware and / or software for enabling communications with a wireless communication network (e.g., a wireless local area network, a cellular network, a global positioning system network, etc.), and / or a communication modem or other hardware / software for supporting communications via cable, digital subscriber line (DSL), universal serial bus (USB), Ethernet, or other methods.
[0068] In one or more embodiments, the mobile computing device 106a includes an optical engine 212. The optical engine 212 may include an imager, a laser sight, and / or an auxiliary processing device. The imager may be configured to obtain two or more frames (e.g., two or more image frames) associated with an object within the field of view of the imager. In one or more embodiments, the imager and / or the laser sight may be configured as parts of the optical engine 212, which includes a light generating device, a mirror element, an electronic component, a control component, and / or other components configured to obtain an image within the field of view. In various embodiments, the auxiliary processing device of the optical engine 212 may be configured to have less processing power and / or a smaller physical size than the processor 206 of the mobile computing device 106a. For example, the processor 206 of the mobile computing device 106a may be configured for image processing associated with frames captured by the imager. Additionally, auxiliary processing devices of the optical engine 212 may be configured for one or more calculations associated with the imager and / or laser aimer that require less processing power than image processing performed by the processor 206 of the mobile computing device 106a.
[0069] Figure 3 is a schematic block diagram of an MBTA external auxiliary component 102 associated with an exemplary MBTA system 100 according to one or more embodiments described herein. In various embodiments, the MBTA system 100, in conjunction with the MBTA external auxiliary component 102, provides an implementation of biometric data analysis techniques and / or digital transformation techniques to facilitate secure MBTA for one or more mobile computing devices 106a-n associated with a particular enterprise. In one or more embodiments, the MBTA system 100, through the MBTA external auxiliary component 102, provides an implementation of receiving a request to generate a biometric template and PIN associated with one or more end users, and transmitting biometric template data and / or system configuration data (e.g., MBTA data 214) associated with one or more active end users associated with the MBTA system 100 to the one or more mobile computing devices 106a-n.
[0070] MBTA external auxiliary component 102 includes, embodies, and / or is integrated with MBTA database 108, mobile device management tool 302, user interface 304, communication interface 306, processing circuitry 308 including memory 310 and / or processor 312, secret management system 314, FTP server 316, and / or MQTT broker 318. In certain embodiments, one or more aspects of MBTA external auxiliary component 102 (and / or other systems, devices, and / or processes disclosed herein) constitute executable instructions embodied in a computer-readable storage medium (e.g., memory 310). For example, in one embodiment, memory 310 stores computer-executable components and / or executable instructions (e.g., program instructions). Additionally, in various embodiments, the mobile device management tool 302, processing circuitry 308, secret management system 314, FTP server 316, and / or MQTT broker 318 embody executable computer program code and / or interface with one or more computer programs and / or computer hardware configured to employ secure MBTA conventions for one or more mobile computing devices 106a-n. In various embodiments, the processor 312 facilitates the execution of computer executable components and / or executable instructions (e.g., program instructions). In an example embodiment, the processor 312 is configured to execute instructions stored in the memory 310 or otherwise accessible to the processor 312. However, it should be noted that the following description of the instructions and the instructions described herein are not intended to be construed as being inaccurate or undesirable. Figure 3 exemplified in and about Figure 3 The components, devices or elements described may not be mandatory, and thus one or more components, devices or elements may be omitted in certain embodiments. Additionally, some embodiments may include Figure 3 exemplified in and about Figure 3 Additional or different components, devices or elements than those described.
[0071] The MBTA external auxiliary component 102 may include or otherwise communicate with a processing circuit 308 that may be configured to perform actions according to one or more embodiments disclosed herein. In this regard, the processing circuit 308 may be configured to perform and / or control the execution of one or more functions of the MBTA external auxiliary component 102 according to various embodiments, and thus may provide a means for performing functions of the MBTA system 100 according to various embodiments. According to one or more embodiments, the processing circuit 308 may be configured to perform data processing, application execution, and / or other processing and management services. In some embodiments, the MBTA external auxiliary component 102 or a portion or component thereof (such as the processing circuit 308) may be embodied as a chip or a chipset, or include a chip or a chipset. In other words, the MBTA external auxiliary component 102 or the processing circuit 308 may include one or more physical packages (e.g., chips) that include materials, components, and / or wires on a structural assembly (e.g., a footboard). The structural assembly may provide physical strength, size conservation, and / or electrical interaction limitations for the component circuits included thereon. Thus, in some cases, MBTA external auxiliary component 102 or processing circuit 308 may be configured to implement embodiments of the present disclosure on a single chip or as a single “system on a chip.” Thus, in some cases, a chip or chipset may constitute a means for performing one or more operations for providing the functionality described herein.
[0072] In some embodiments, processing circuit 308 may include processor 312, and in some embodiments, such as in Figure 3 In the illustrated embodiment, a memory 310 may also be included. The processing circuit 308 may communicate with the user interface 304 and / or the communication interface 306, or otherwise control the user interface and / or the communication interface. Therefore, the processing circuit 308 may be embodied as a circuit chip (e.g., an integrated circuit chip) configured to perform the operations described herein (e.g., using hardware, software, or a combination of hardware and software).
[0073] The processor 312 may be embodied in several different ways. For example, the processor 312 may be embodied as one or more of various processing components, such as a microprocessor or another processing element, a coprocessor, a controller, or various other computing or processing devices, including integrated circuits, such as ASICs (Application Specific Integrated Circuits), FPGAs (Field Programmable Gate Arrays), etc. Although illustrated as a single processor, it should be understood that the processor 312 may include multiple processors. The multiple processors may be operably in communication with each other and may be configured together to perform one or more functions of the MBTA external auxiliary component 102 as described herein. In some embodiments, the processor 312 may be configured to execute instructions stored in the memory 310 or otherwise accessible to the processor 312. Therefore, whether configured by hardware or by a combination of hardware and software, the processor 312 may represent an entity (e.g., physically embodied in a circuit (in the form of a processing circuit 308)) that is capable of performing operations according to embodiments of the present disclosure while being configured accordingly. Therefore, for example, when the processor 312 is embodied as an ASIC, FPGA, etc., the processor 312 may be hardware that is specifically configured for performing the operations described herein. Alternatively, as another example, when the processor 312 is embodied as an executor of software instructions, the instructions may specifically configure the processor 312 to perform one or more operations described herein.
[0074] In some embodiments, the memory 310 may include one or more non-transitory memory devices, such as fixed or removable volatile and / or non-volatile memory. In this regard, the memory 310 may include a non-transitory computer-readable storage medium. It should be understood that although the memory 310 is illustrated as a single memory, the memory 310 may also include multiple memories. The memory 310 may be configured to store information, data, applications, instructions, etc. for enabling the mobile computing device 106a to perform various functions according to one or more embodiments. For example, the memory 310 may be configured to buffer input data for processing by the processor 312. Additionally or alternatively, the memory 310 may be configured to store instructions for execution by the processor 312. As another alternative, the memory 310 may include one or more databases that can store a variety of files, content, or data sets. In the content of the memory 310, applications may be stored for execution by the processor 312 to perform functions associated with each corresponding application. In some cases, memory 310 may be in communication with one or more of processor 312 , user interface 304 , and / or communication interface 306 via a bus to transfer information between components of mobile computing device 106a .
[0075] The user interface 304 may communicate with the processing circuit 308 to receive indications of user input at the user interface 304 and / or to provide an auditory output, a visual output, a mechanical output, or other output to the user. Thus, the user interface 304 may include, for example, biometric hardware, a keyboard, a mouse, a joystick, an electronic display, a touch screen display, a microphone, a speaker, and / or other input / output mechanisms. Thus, in some embodiments, the user interface 304 may provide a means for a user to access and interact with various MBTA external auxiliary components 102 of the MBTA system 100 and / or other systems and devices.
[0076] In one or more embodiments, the communication interface 306 is configured to receive the request 216 (e.g., such as from one or more mobile computing devices 106a-n). In various embodiments, the communication interface 306 can relay the request 216 to one or more of the mobile device management tool 302, the processing circuit 308, the secret management system 314, the FTP server 316, and / or the MQTT broker 318 for processing and / or compiling the MBTA data 214. Once the MBTA data 214 has been compiled (e.g., by the mobile device management tool 302, the processing circuit 308, the secret management system 314, the FTP server 316, and / or the MQTT broker 318), the communication interface 306 can transmit the MBTA data 214 to the one or more mobile computing devices 106a-n.
[0077] The communication interface 306 may include one or more interface mechanisms for enabling communication with other devices and / or networks. In some cases, the communication interface 306 may be any component, such as a device or circuit embodied in hardware or a combination of hardware and software, that is configured to receive data from a network and / or any other device or module that communicates with the processing circuit 308, and / or transmit data to the network and / or the other device or module. As an example, the communication interface 306 may be configured to enable the mobile computing device 106a to communicate with one or more mobile computing devices 106a-n. For example, in various embodiments, the MBTA external auxiliary component 102 may receive the request 216 from one or more mobile computing devices 106a-n via the communication interface 306. Similarly, in various embodiments, the MBTA external auxiliary component 102 may transmit one or more portions of the MBTA data 214 to one or more mobile computing devices 106a-n via the communication interface 306. Thus, the communication interface 306 may, for example, include an antenna (or multiple antennas) and supporting hardware and / or software for enabling communications with a wireless communication network (e.g., a wireless local area network, a cellular network, a global positioning system network, etc.), and / or a communication modem or other hardware / software for supporting communications via cable, digital subscriber line (DSL), universal serial bus (USB), Ethernet, or other methods.
[0078] The mobile device management tool 302 may configure, reconfigure, update, restore, install applications, and / or otherwise manage one or more mobile computing devices 106a-n. In various embodiments, the mobile device management tool 302 may distribute a biometric template management application to the one or more mobile computing devices 106a-n and cause the biometric template management application to be installed to the one or more mobile computing devices 106a-n. The mobile device management tool 302 may also distribute one or more XML configuration documents to the one or more mobile computing devices 106a-n, wherein the one or more XML configuration documents may be used to configure (or reconfigure) one or more hardware and / or software settings, parameters, operating modes, user access levels, applications, etc. associated with the one or more mobile computing devices 106a-n. Additionally, in various embodiments, the mobile device management tool 302 is configured to generate one or more data packets from the biometric template management application and / or the one or more XML configuration documents and send the one or more data packets to the one or more mobile computing devices 106a-n. In various embodiments, one or more data packets are configured to increase transmission efficiency by reducing network bandwidth requirements and to reduce computing resources by reducing the size of data associated with a biometric template management application and / or one or more XML configuration documents.
[0079] The secret management system 314 is configured to generate, store, and / or distribute symmetric shared secrets across one or more mobile computing devices 106a-n associated with the MBTA system 100. A symmetric shared secret is a cryptographic secret used to encrypt and decrypt BTs. The symmetric secrets are shared across all mobile computing devices 106a-n (e.g., via the secret management system 314) such that one or more BTs are available in a secure manner across the mobile computing devices 106a-n associated with the MBTA system 100. In various embodiments, the secret management system 314 provides an application programming interface (API) configured to securely distribute the symmetric shared secrets across one or more mobile computing devices 106a-n.
[0080] In some contexts, the size of data associated with one or more active BTs associated with the MBTA system 100 may be too large to be stored within the privacy management system. The FTP server 316 is configured to distribute the active BTs and active PINs associated with the MBTA system 100 to one or more mobile computing devices 106a-n. In some embodiments, the FTP server 316 supports one or more network security protocols (e.g., Transport Layer Security (TLS)) to encrypt data associated with the active BT and / or active PIN during transmission.
[0081] In some embodiments, the FTP server 316 provides one or more APIs configured to manage the transfer of various types of data (e.g., biometric data, BT data, user authentication data, system configuration data, etc.) between the MBTA external auxiliary component 102 and one or more mobile computing devices 106a-n. The FTP server 316 may employ an API that serializes data uploads (e.g., uploads to one or more mobile computing devices 106a-n) and returns an error if an operation on the data file being uploaded (e.g., a data file related to biometric data, BT data, user authentication data, system configuration data, etc.) is already in progress. The one or more APIs provided by the FTP server 316 may be used to verify the checksum of the data file upload and generate one or more notifications (e.g., error notifications, update notifications, etc.) in combination with the MQTT broker 318 and / or distribute the one or more notifications to the one or more mobile computing devices 106a-n.
[0082] Additionally or alternatively, the MBTA system 100 may generate and / or employ a public / private key pair to secure one or more data transmissions between one or more mobile computing devices 106a-n and one or more of the components of the MBTA system 100 (e.g., the FTP server 316). A public / private key pair is a set of cryptographic keys created using a Rivest-Shamir-Adleman (RSA) algorithm. In some contexts, the public / private key pair may be used to encrypt a symmetric shared secret prior to transmission by the one or more mobile computing devices 106a-n. In some contexts, a public key in a particular public / private key pair may be associated with the secret management system 314, the FTP server 316, and / or the MQTT broker 318, respectively, and the public key may be stored in the FTP server 316.
[0083] The MQTT broker 318 may be configured to generate and / or transmit one or more types of notifications to one or more mobile computing devices 106a-n when an active BT (e.g., as stored in an active BT list and / or a database such as the MBTA database 108), an active PIN (e.g., as stored in an active PIN list and / or a database such as the MBTA database 108), and / or one or more portions of end-user data (e.g., user authentication data, biometric data, etc.) have changed. The MQTT broker 318 may also be configured to generate and / or transmit one or more types of notifications indicating that a biometric template management application and / or one or more XML configuration documents generated by the mobile device management tool 302 have been transmitted to and / or provided on the one or more mobile computing devices 106a-n.
[0084] In various embodiments, the MBTA database 108 may embody, be integrated with, or be embodied by the secret management system 314, the FTP server 316, and / or the MQTT broker 318 in order to perform one or more methods or processes associated with the MBTA system 100. For example, in some embodiments, the MBTA database 108 may work in conjunction with the FTP server 316 to manage one or more portions of biometric data associated with one or more end users, one or more active BT lists associated with one or more active BTs associated with one or more end users, one or more active PIN lists associated with one or more active PINs associated with one or more end users, one or more XML configuration documents, one or more portions of user authentication data, etc. It should be understood that the storage and processing components of the MBTA system 100 may be configured in various ways to suit certain contexts, and that the exemplary systems, databases, and / or processing components described herein are described for the purpose of describing in detail exemplary embodiments of the present disclosure and not for purposes of limitation.
[0085] Figure 4 A data flow diagram for facilitating a safe MBTA according to one or more embodiments described herein is illustrated. Specifically, Figure 4 An exemplary environment 400 is depicted that is associated with one or more data flows between various components of the MBTA system 100 (e.g., the MBTA external auxiliary component 102), an end user 402, an XML configuration document 404, a barcode 406, and a mobile computing device 106a. As shown, the mobile computing device 106a includes a virtual machine 408, a system server 414, a system kernel 424, a trusted execution environment (TEE) 430, and / or biometric hardware 438. In various embodiments, one or more of the components associated with the virtual machine 408, the system server 414, the system kernel 424, the TEE 430, and / or the biometric hardware 438 may be provided by a user. Figure 2 The depicted components of the mobile computing device 106a (eg, the processing circuitry 202, the user interface 208, the communication interface 210, and / or the optical engine 212) embody and / or are integrated with this component.
[0086] In various contexts, end user 402 may be any user associated with MBTA system 100 associated with a particular enterprise (e.g., a member of staff associated with a particular enterprise, an administrator, etc.). End user 402 may be associated with one or more portions of biometric data, one or more BTs, one or more PINs, and / or one or more portions of user authentication data.
[0087] As described herein, the XML configuration document 404 may be used to configure (or reconfigure) one or more hardware and / or software settings and / or parameters associated with one or more mobile computing devices 106a-n (e.g., settings and / or parameters related to the virtual machine 408, the system server 414, the system kernel 424, the TEE 430, and / or the biometric hardware 438), one or more operating modes (e.g., a multi-user BT authentication mode), one or more user access levels, one or more applications (e.g., the BT management application 410), and the like.
[0088] The barcode 406 may be associated with one or more specific XML configuration documents (e.g., XML configuration document 404) associated with the MBTA system 100. The mobile computing device 106a may scan the barcode 406 via the optical engine 212 to obtain one or more portions of data associated with the XML configuration document 404. For example, in some contexts, the mobile computing device 106a may scan the barcode 406, and in response to scanning the barcode 406, the BT management application 410 may retrieve an active BT list and / or an active PIN list associated with the MBTA system 100, wherein the active BT list and / or the active PIN list includes one or more BTs and / or PINs associated with one or more corresponding end users 402 currently registered with the MBTA system 100. Thus, based on scanning the barcode 406 associated with the XML configuration document 404, the mobile computing device 106a may be instructed to acquire data (e.g., an active BT list and / or an active PIN list) and merge the acquired data by, for example, updating, adding, deleting, synchronizing, and / or otherwise managing one or more portions of the data stored locally on the mobile computing device 106a based in part on the acquired data.
[0089] As another example, based on scanning the barcode 406 associated with the XML configuration document 404, the mobile computing device 106a may be instructed (e.g., by the processing circuit 202) to obtain the XML configuration document 404 from the MBTA external auxiliary component 102 (e.g., from the FTP server 316 or the MBTA database 108) and configure one or more hardware and / or software settings and / or parameters associated with the mobile computing device 106a based on the XML configuration document 404.
[0090] The BT management application 410 is a software application associated with the MBTA system 100 that can be loaded and / or run on a virtual machine 408 associated with one or more mobile computing devices 106a-n. In some embodiments, the mobile device management tool 302 can facilitate the distribution and / or installation of the BT management application 410 in one or more mobile computing devices 106a-n. In various embodiments, the BT management application 410 is configured to execute and / or cause the execution of one or more portions of computer program code configured to perform various methods and / or processes associated with the secure MBTA. FIG. 10A to FIG. 10B and FIG. 11A to FIG. 11B As depicted, in various embodiments, BT management application 410 can be configured as an interactive dashboard application that includes one or more interactive display elements associated with MBTA data 214 or request 216. For example, BT management application 410 can be configured to facilitate the capture, management, transmission, and / or storage of one or more portions of biometric data associated with end user 402, user authentication data associated with end user 402, and / or data related to MBTA system 100.
[0091] As a non-limiting example, the BT management application 410 may be configured to perform one or more operations related to capturing biometric data from a particular end user 402 and subsequently generating a BT based on the captured biometric data. For example, when interacting with the BT management application 410, the particular end user 402 may use the biometric hardware 438 configured as a fingerprint scanner to generate a BT based on the biometric data (e.g., fingerprint data) captured by the biometric hardware 438. In addition, the BT management application 410 may generate a PIN associated with the newly generated BT associated with the particular end user 402. The PIN associated with the newly generated BT may be used by the particular end user 402 to authenticate (e.g., log in, register, etc.) the particular end user 402 on one or more mobile computing devices 106a-n associated with the MBTA system 100. In this regard, the BT management application 410 may facilitate the transmission of the newly generated BT and / or PIN associated with the particular end user 402 for storage in the MBTA external auxiliary component 102 (e.g., in the FTP server 316).
[0092] In addition, the BT management application 410 is configured to perform one or more operations related to authenticating a particular end user 402 to access the corresponding mobile computing device 106a. For example, the BT management application 410 may execute one or more biometric data matching algorithms to match one or more portions of the biometric data associated with the particular end user 402 with a corresponding BT that has been previously generated based in part on the biometric data associated with the particular end user 402. For example, if an active BT database associated with the MBTA system 100 includes a BT associated with the particular end user 402, and the corresponding mobile computing device 106a has been updated to include data associated with the active BT database, the BT management application 410 may employ one or more biometric data matching algorithms to verify the biometric data associated with the end user 402 against data associated with the active BT database. In some contexts, the BT management application 410 may capture biometric data from the end user 402 via the biometric hardware 438 configured as a fingerprint scanner, and compare the biometric data associated with the end user 402 with data associated with the active BT database that has been stored on the mobile computing device 106a. If the BT management application 410 confirms (eg, via a biometric data matching algorithm) that the biometric data associated with the end user 402 matches a corresponding BT associated with the active BT database, the end user 402 may gain access to the mobile computing device 106a.
[0093] As described herein, various embodiments utilize a unique PIN associated with a BT associated with a respective end user 402 in order to authenticate the end user 402 on a particular mobile computing device 106a. For example, when the end user 402 is attempting to access (e.g., log in, register, etc.) the mobile computing device 106a, the BT management application 410 may prompt the end user 402 to enter the PIN associated with the BT associated with the end user 402. For example, in some embodiments, if the MBTA system 100 (e.g., via the BT management application 410) verifies that the end user 402 has entered the authentic PIN, the MBTA system 100 may (e.g., via the BT management application 410) prompt the end user 402 to provide biometric data (e.g., a fingerprint associated with the end user 402). The BT management application 410 may then confirm (e.g., via one or more biometric data matching algorithms) that the biometric data associated with the end user 402 matches the respective BT associated with the active BT database, and the end user 402 may gain access to the mobile computing device 106a. In various alternative embodiments, the MBTA system 100 and / or BT management application 410 may authenticate a particular end user 402 based solely on biometric data associated with the end user 402 and not require the end user 402 to provide a PIN associated with the corresponding BT related to the end user 402.
[0094] like Figure 4 As depicted, the BT management application 410 is configured to integrate with the MBTA system 100 and one or more internal components of the mobile computing device 106a. As described herein, the BT management application 410 is an interactive software application designed to facilitate configuration, reconfiguration, and / or augmentation of one or more internal components of the mobile computing device 106a in order to perform one or more operations related to secure MBTA on the mobile computing device 106a. In various embodiments, the one or more internal components are mobile computing device components that were originally configured by a vendor and / or manufacturer of the mobile computing device 106a. However, the BT management application 410 (and / or the BT management application hardware abstraction layer (HAL) extension 416) is configured to utilize (e.g., operate and / or reconfigure) mobile computing device components that were originally configured by a vendor and / or manufacturer of the mobile computing device 106a.
[0095] In addition to the BT management application 410, the virtual machine 408 of the mobile computing device 106a also includes a biometric data manager 412. The biometric data manager 412 may include one or more portions of executable computer program code that are configured to transmit data (e.g., instructions, indications, etc.) to one or more other internal components of the mobile computing device 106a to perform one or more services associated with BT. For example, the biometric data manager 412 is integrated with the BT service 420 of the system server 414. The system server 414 also includes a BT management application HAL extension 416, a BTHAL 418, and a TEE user space library 422. The BT HAL 418 includes one or more portions of computer program code that are configured to provide a mobile device driver interface that allows one or more software applications to communicate with the hardware associated with the mobile computing device 106a. The BT management application HAL extension 416 includes one or more portions of executable program code associated with the BT management application 410, which are designed to integrate with and / or configure the BT HAL 418 so that the BT management application 410 can interface with, operate, control, and / or otherwise manage one or more pieces of hardware (e.g., biometric hardware 438) associated with the mobile computing device 106a. The TEE user space library 422 includes one or more portions of executable program code (e.g., one or more functions, methods, APIs, etc.) configured to allow the BT management application 410 to interface with the TEE 430 of the mobile computing device 106a.
[0096] The system kernel 424 is associated with the operating system (OS) of a specific mobile computing device 106a. In many contexts, the system kernel 424 has control over the mobile computing device 106a and can facilitate communication between the hardware components and software components of the mobile computing device 106a. In various embodiments, the system kernel 424 includes a TEE kernel driver 426 and a BT driver 428. The TEE kernel driver 426 includes an executable program code configured to integrate with one or more components of the TEE 430, operate the one or more components, control the one or more components, and / or otherwise manage the one or more components. For example, the TEE kernel driver 426 can be integrated with the TEE OS 432 of the TEE 430, operate the TEEOS, control the TEE OS, and / or otherwise communicate with the TEE OS.
[0097] The BT driver 428 is configured to integrate with, operate, and / or facilitate communication between one or more biometric applications associated with the TEE 430 and one or more pieces of hardware associated with the mobile computing device 106a. For example, the BT driver 428 can facilitate communication between a biometric trusted application (TA) 436 of the TA 434 and the biometric hardware 438. In various embodiments, the biometric TA 436 is configured to encrypt and / or save BT associated with a particular end user 402. For example, in various embodiments, the biometric TA 436 can encrypt BT associated with the end user 402 with a symmetric shared secret associated with the MBTA system 100. In addition, the biometric TA 436 can save the encrypted BT associated with the end user 402 as a data file, and generate a file name associated with the data file including the encrypted BT, the file name incorporating a PIN associated with the BT associated with the end user 402.
[0098] In various embodiments, the biometric hardware 438 of the mobile computing device 106a is configured to capture, read, sense, and / or otherwise obtain biometric data associated with a particular end user 402. In various contexts, the biometric data associated with a particular end user 402 may include, but is not limited to, fingerprint data, palm data, vein data, retina and / or iris data, voice data, facial feature data (e.g., face shape, eye shape, nose shape, etc.), body feature data (e.g., ear shape), DNA data, handwriting data, and / or any other physical and / or personal data associated with the particular end user 402. Thus, the biometric hardware 438 of the mobile computing device 106a may include one or more sensors, cameras, fingerprint scanners, palm scanners, eye scanners, one or more hardware components configured to sense the handwriting of the end user 402, one or more microphones, and / or any combination thereof.
[0099] As described in this article, FIG. 10A to FIG. 10B and FIG. 11A to FIG. 11B An exemplary user interface of a BT management application 410 rendered on a mobile computing device 106a associated with an MBTA system 100 is illustrated according to one or more embodiments described herein. Specifically, FIG. 10A to FIG. 10BAn exemplary user interface including one or more interactive display elements 1002-1012 designed to facilitate enrollment of an end user 402 is depicted, the one or more interactive display elements being configured to receive username information, generate a PIN to be associated with a BT associated with the end user 402, and / or integrate with the biometric hardware 438 of the mobile computing device 106a to capture biometric data (e.g., fingerprint data) from the end user 402. For example, the interactive display element 1010 is configured to integrate with the biometric hardware 438 of the mobile computing device 106a to capture fingerprint data for generating a BT associated with the fingerprint of the end user 402.
[0100] Fig.11A An exemplary user interface of the BT management application 410 including interactive display elements 1102 - 1106 configured to facilitate deleting a PIN and / or BT associated with a particular end user 402 is depicted. Fig. 11B An exemplary user interface of BT management application 410 including interactive display elements 1108 - 1114 configured to facilitate recovery of a PIN associated with a particular end user 402 is depicted.
[0101] Exemplary Processes and Methods of the Disclosure
[0102] Figure 5 A process flow diagram of a computer-implemented method 500 configured for adding and / or updating an active personal identification number (PIN) database associated with a multi-user biometric template authentication (MBTA) system 100 associated with a particular enterprise is illustrated in accordance with a detailed description of one or more embodiments described herein. In various embodiments, the active PIN database includes a list of one or more PINs associated with one or more corresponding biometric templates (BTs) associated with one or more corresponding end users 402 currently enrolled in the MBTA system 100, and a representation (e.g., a structured list, a copy of the active BT database, etc.) associated with the active PIN database is stored locally on one or more mobile computing devices 106a-n. Figure 5 As shown, the computer-implemented method 500 utilizes at least the BT management application 410 , the FTP server 316 , the application programming interface (API) 502 , and / or the MQTT broker 318 to add and / or update a particular PIN in an active PIN database associated with the MBTA system 100 .
[0103] The computer-implemented method 500 begins at step 504, where the BT management application 410 is caused to trigger (e.g., initiate) the generation and / or updating of a PIN associated with a particular end-user 402. As described herein, in various embodiments, the BT management application 410 associated with a particular mobile computing device 106a may be used to collect biometric data (e.g., fingerprint data) from the end-user 402, generate a BT based on the biometric data, and generate a secure PIN associated with the BT related to the end-user 402. The PIN may be used in conjunction with the BT to authenticate the end-user 402 on any of the one or more mobile computing devices 106a-n.
[0104] At step 506, the BT management application 410 may cause the mobile computing device 106a to transmit the newly generated PIN to the FTP server 316 for verification and storage. In various embodiments, the BT management application 410 may generate a data file associated with the PIN and assign to the data file a unique file name that includes the PIN, the device serial number associated with the mobile computing device 106a used to generate the PIN, an embedded checksum associated with the data file including the PIN, and a nonce. For example, the file name format associated with the PIN data file may be configured as: <user's BT PIN>_<device serial number>_<checksum>_<random number>. The nonce in the PIN data file is a randomly generated number that is returned to the BT management application 410 of the mobile computing device 106a if a checksum verification error occurs so that the BT management application 410 can determine which transaction failed. In various embodiments, the PIN data file may be compressed into a packaged file format.
[0105] At step 508, MBTA system 100 may employ API 502 to verify a checksum associated with the PIN data file sequence to ensure that the PIN data file has not been corrupted in transit (e.g., to ensure that one or more portions of the data (bits) have not been lost or altered). In various embodiments, a CRC32 (Cyclic Redundancy Check 32) algorithm that utilizes polynomial division is used to hash the byte sequence associated with the PIN data file into a 32-bit value. The CRC32 algorithm may also be used to verify a checksum associated with the PIN data file to ensure data integrity of the PIN data file.
[0106] At step 510, it is determined whether there is an error verifying the checksum of the PIN data file. If there is an error verifying the checksum of the PIN data file, the computer-implemented method 500 proceeds to step 512. If there is no error verifying the checksum of the PIN data file, the computer-implemented method 500 proceeds to step 514.
[0107] At step 512, if it is determined that there is an error verifying the checksum of the PIN data file, the MQTT broker 318 can publish (e.g., transmit) a notification detailing the existence of a checksum verification error to the BT management application 410 associated with the mobile computing device 106a. In some embodiments, the BT management application 410 can automatically retransmit the PIN data file to the FTP server 316 again so that the API 502 can attempt to verify the checksum again.
[0108] At step 514, API 502 may move the PIN data file that has been uploaded to FTP server 316 to the correct folder and / or storage location in the FTP server. Additionally or alternatively, the PIN data file and / or associated PIN may be stored in an active PIN database and / or active PIN list associated with MBTA system 100 (e.g., in FTP server 316 and / or MBTA database 108). In various embodiments, MBTA system 100 may also update the PIN data file to remove the device serial number and / or random number when the PIN data file is moved to the correct folder and / or storage location. For example, the file name may be updated to a format such as: <user's BT PIN>_<checksum>.
[0109] At step 516, it is determined whether the PIN data file has been moved to the correct storage location (e.g., the storage location includes an active PIN list), and the API 502 may initiate the publication of an active PIN database notification. At step 518, the MQTT broker 318 may publish (e.g., transmit) the active PIN database notification to the one or more mobile computing devices 106a-n. In some embodiments, the active PIN database notification may include an active PIN list, so that the one or more mobile computing devices 106a-n may be updated to contain the most current active PIN list associated with the MBTA system 100. Additionally or alternatively, in some embodiments, the active PIN database notification published (e.g., transmitted) by the MQTT broker 318 may cause the one or more mobile computing devices 106a-n (e.g., via one or more APIs associated with the active PIN database notification) to obtain and / or otherwise obtain the active PIN list from the MBTA system 100 (e.g., from the FTP server 316) in order to update the one or more PINs currently stored on the one or more mobile computing devices 106a-n. In this manner, each active end-user 402 currently registered with and / or associated with the MBTA system 100 may authenticate themselves on any of the one or more mobile computing devices 106a-n using a respective PIN.
[0110] Figure 6 A process flow diagram of a computer-implemented method 600 configured for adding and / or updating BTs in an active BT database associated with the MBTA system 100 is illustrated in accordance with the detailed description of one or more embodiments described herein. In various embodiments, the active BT database includes a list of one or more BTs associated with one or more respective end users 402 currently registered with the MBTA system 100, and a representation (e.g., a structured list, a copy of the active BT database, etc.) associated with the active BT database is stored locally on one or more mobile computing devices 106a-n. Figure 6 As shown, the computer-implemented method 600 utilizes at least the BT management application 410 , the FTP server 316 , the API 602 , and / or the MQTT broker 318 to add and / or update BT in an active BT database associated with the MBTA system 100 .
[0111] The computer-implemented method 600 begins at step 604, where the BT management application 410 is caused to trigger (e.g., initiate) the generation of a BT associated with a particular end-user 402. As described herein, in various embodiments, the BT management application 410 associated with a particular mobile computing device 106a may be used to collect biometric data (e.g., fingerprint data) from the end-user 402 and generate a BT based on the biometric data associated with the end-user 402. The BT may be used in conjunction with a PIN to authenticate the end-user 402 on any of the one or more mobile computing devices 106a-n.
[0112] At step 606, the BT management application 410 may cause the mobile computing device 106a to transmit the newly generated BT to the FTP server 316 for verification and storage. In various embodiments, the BT management application 410 may generate a BT data file associated with the BT and assign a unique file name to the BT data file that includes a PIN, a device serial number associated with the mobile computing device 106a used to generate the PIN, an embedded checksum associated with the data file including the PIN, and a random number. For example, the file name format associated with the PIN data file may be configured as: <user's BT PIN>_<device serial number>_<checksum>_<random number>. The random number in the BT data file is a randomly generated number that is returned to the BT management application 410 of the mobile computing device 106a if a checksum verification error occurs, so that the BT management application 410 can determine which transaction failed. In various embodiments, the BT data file may be compressed into a packaged file format.
[0113] At step 608, the MBTA system 100 may employ the API 602 to verify the checksum associated with the BT data file sequence to ensure that the BT data file has not been corrupted in transit (e.g., to ensure that one or more portions of the data (bits) have not been lost or altered). In various embodiments, a CRC32 algorithm utilizing polynomial division is used to hash the byte sequence associated with the BT data file into a 32-bit value. The CRC32 algorithm may also be used to verify the checksum associated with the BT data file to ensure data integrity of the BT data file.
[0114] At step 610, it is determined whether there is an error verifying the checksum of the BT data file. If there is an error verifying the checksum of the BT data file, the computer-implemented method 600 proceeds to step 612. If there is no error verifying the checksum of the BT data file, the computer-implemented method 600 proceeds to step 614.
[0115] At step 612, if it is determined that there is an error verifying the checksum of the BT data file, the MQTT broker 318 can publish (e.g., transmit) a notification detailing the existence of a checksum verification error to the BT management application 410 associated with the mobile computing device 106a. In some embodiments, the BT management application 410 can automatically retransmit the BT data file to the FTP server 316 again so that the API 602 can attempt to verify the checksum again.
[0116] At step 614, the API 602 may move the BT data file that has been uploaded to the FTP server 316 to the correct folder and / or storage location in the FTP server. Additionally or alternatively, the BT data file and / or the associated BT may be stored in an active BT database and / or active BT list associated with the MBTA system 100 (e.g., in the FTP server 316 and / or the MBTA database 108). In various embodiments, the MBTA system 100 may also update the BT data file to remove the device serial number and / or random number when moving the BT data file to the correct folder and / or storage location. For example, the file name may be updated to a format such as: <user's BT PIN>_<checksum>.
[0117] At step 616, it is determined whether the BT data file has been moved to the correct storage location (e.g., the storage location includes an active BT list), and the API 602 may initiate the publication of an active BT database notification. At step 618, the MQTT broker 318 may publish (e.g., transmit) the active BT database notification to the one or more mobile computing devices 106a-n. In some embodiments, the active BT database notification may include an active BT list, so that the one or more mobile computing devices 106a-n may be updated to contain the most current active BT list associated with the MBTA system 100. Additionally or alternatively, in some embodiments, the active BT database notification published (e.g., transmitted) by the MQTT broker 318 may cause the one or more mobile computing devices 106a-n (e.g., via one or more APIs associated with the active BT database notification) to obtain and / or otherwise obtain the active BT list from the MBTA system 100 (e.g., from the FTP server 316) in order to update the one or more BT currently stored on the one or more mobile computing devices 106a-n. In this manner, each active end user 402 currently registered at and / or associated with the MBTA system 100 may authenticate themselves on any of the one or more mobile computing devices 106a-n by providing biometric data associated with the end user 402 for generating a BT to any of the one or more mobile computing devices 106a-n. As a non-limiting example, the end user 402 may provide a fingerprint (e.g., via the biometric hardware 438), and the BT management application 410 may determine whether the fingerprint matches a corresponding BT included in a list of active BTs stored locally on the mobile computing device 106a. If it is determined (e.g., via one or more biometric data matching algorithms) that the provided biometric data (e.g., fingerprint) matches a corresponding BT included in a list of active BTs stored locally on the mobile computing device 106a, the end user 402 will be allowed access to the mobile computing device 106a.
[0118] Figure 7 A process flow diagram of a computer-implemented method 700 configured for deleting BTs from an active BT database is illustrated in accordance with the detailed description of one or more embodiments described herein. As described herein, in various embodiments, the active BT database includes a list of one or more BTs associated with one or more respective end users 402 currently registered in the MBTA system 100, and a representation (e.g., a structured list, a copy of the active BT database, etc.) associated with the active BT database is stored locally on one or more mobile computing devices 106a-n. Figure 7As shown, the computer-implemented method 700 utilizes at least the BT management application 410 , the FTP server 316 , the API 702 , and / or the MQTT broker 318 to delete a particular BT from an active BT database associated with the MBTA system 100 .
[0119] The computer-implemented method 700 begins at step 704, in which the BT management application 410 is caused to trigger (e.g., initiate) deletion of a specific BT associated with the corresponding end user 402. For example, the end user 402 may interact with one or more interactive display elements (e.g., interactive display elements 1102-1106) associated with the BT management application 410 and rendered on the specific mobile computing device 106a to cause the BT management application 410 to initiate deletion of the specific BT. In various embodiments, the BT management application 410 may indicate the specific BT to be deleted based on at least data related to the PIN of the end user 402, the device serial number of the mobile computing device 106a, and / or a randomly generated nonce associated with the BT, and transmit the data to the FTP server 316.
[0120] At step 706, the FTP server 316 may verify the BT to be deleted from the active BT database based on at least data related to the PIN of the end user 402, the device serial number of the mobile computing device 106a, and / or the randomly generated nonce associated with the BT. Once the BT has been verified by the FTP server 316, the computer-implemented method 700 may proceed to step 708, in which the API 702 may cause the BT to be deleted from the active BT database.
[0121] At step 710, the API 702 may initiate the publication of an active BT database notification. At step 712, the MQTT broker 318 may publish (e.g., transmit) the active BT database notification to the one or more mobile computing devices 106a-n. In some embodiments, the active BT database notification may include an active BT list, such that the one or more mobile computing devices 106a-n may be updated to contain the most current active BT list associated with the MBTA system 100. Additionally or alternatively, in some embodiments, the active BT database notification published (e.g., transmitted) by the MQTT broker 318 may cause the one or more mobile computing devices 106a-n (e.g., via one or more APIs associated with the active BT database notification) to retrieve and / or otherwise obtain the active BT list from the MBTA system 100 (e.g., from the FTP server 316) in order to update the one or more BTs currently stored on the one or more mobile computing devices 106a-n.
[0122] Figure 8A process flow diagram of a computer-implemented method 800 configured for enabling or disabling a multi-user BT authentication mode for one or more mobile computing devices 106a-n associated with the MBTA system 100 is illustrated in accordance with a detailed description of one or more embodiments described herein. As described herein, the XML configuration document 404 may be used to configure (or reconfigure) one or more hardware settings and / or parameters and / or software settings and / or parameters (e.g., settings and / or parameters associated with the virtual machine 408, the system server 414, the system kernel 424, the TEE 430, and / or the biometric hardware 438), one or more operating modes (e.g., a multi-user BT authentication mode), one or more user access levels, one or more applications (e.g., the BT management application 410), etc. associated with the one or more mobile computing devices 106a-n. Figure 8 As shown, the computer-implemented method 800 utilizes at least the XML configuration document 404, the BT management application 410, the BT management application hardware abstraction layer (HAL) extension 416, and / or the biometric trusted application (TA) 436 to enable or disable a multi-user BT authentication mode for one or more mobile computing devices 106a-n associated with the MBTA system 100.
[0123] The computer-implemented method 800 begins at step 802, where the BT management application 410 is caused to trigger (e.g., initiate) enabling or disabling of a multi-user BT authentication mode in one or more mobile computing devices 106a-n. In various embodiments, the BT management application 410 may cause triggering of enabling or disabling of a multi-user BT authentication mode for a particular mobile computing device 106a in response to receiving an XML configuration document notification from the MQTT broker 318 that includes data associated with an XML configuration document 404. In this example, the XML configuration document 404 may be associated with one or more portions of executable program code that are configured to enable and / or disable one or more parameter settings and / or access permissions of the mobile computing device 106a associated with the multi-user BT authentication mode of operation.
[0124] In various other embodiments, the BT management application 410 may cause triggering of enabling or disabling of the multi-user BT authentication mode for the particular mobile computing device 106a in response to the particular mobile computing device 106a scanning a barcode (e.g., barcode 406) associated with the XML configuration document 404. The mobile computing device 106a may scan the barcode 406 via the optical engine 212 to obtain one or more portions of data (e.g., executable program code) associated with the XML configuration document 404, and thereby trigger enabling or disabling of the multi-user BT authentication mode.
[0125] At step 804, the BT management application may call an API configured to configure (e.g., enable) a multi-user BT authentication mode for the mobile computing device 106a. In various embodiments, the API is configured to instruct the BT management application HAL extension 416 to adjust hardware parameters and / or software parameters of the mobile computing device 106a. At step 806, the BT management application HAL extension 416 may enable (or disable) the multi-user BT authentication mode by communicating with a biometric TA 436 (e.g., included in a TA 434 of a TEE 430). Because there may be many security risks involved when using biometric data to authenticate an end user 402, certain applications (e.g., biometric TA 436) are deployed by the TEE (e.g., TEE 430) of the mobile computing device 106a to ensure data security and / or integrity. By enabling the multi-user BT authentication mode of the biometric TA 436 of the mobile computing device 106a, any end user 402 registered with the MBTA system 100 (e.g., any end user associated with an active BT and / or PIN) may be authenticated on the mobile computing device 106a. Alternatively, in a context where the multi-user BT authentication mode is disabled for a particular mobile computing device 106a, one or more end users 402 associated with the MBTA system 100 may not be authenticated on the particular mobile computing device 106a by using the biometric data and / or PIN associated with the corresponding BT included in the active BT database and / or active PIN database of the MBTA system 100.
[0126] At step 808, the biometric TA 436 is configured to save the state of the mobile computing device 106a (e.g., save one or more system parameters updated by the multi-user BT authentication mode API). For example, if the multi-user BT authentication mode associated with the mobile computing device 106a is enabled or disabled, the biometric TA 436 is configured to save the current state of the mobile computing device 106a as it relates to the multi-user BT authentication mode.
[0127] At step 810, the BT management application HAL extension 416 determines whether the multi-user BT authentication mode has been successfully enabled (or, in some contexts, disabled). At step 812, the BT management application 410 determines whether one or more operations associated with the multi-user BT authentication mode API have been successfully performed. At step 814, the BT management application 410 saves the current system state (e.g., one or more system parameter settings indicating that the multi-user BT authentication mode has been successfully enabled (or disabled)) and the computer-implemented method 800 is terminated.
[0128] Fig. 9 A process flow diagram of a computer-implemented method 900 configured for importing and providing symmetric shared secrets for BT encryption purposes in one or more mobile computing devices 106a-n is illustrated in accordance with a detailed description of one or more embodiments described herein. As described herein, the secret management system 314 is configured to generate, store, and / or distribute symmetric shared secrets across one or more mobile computing devices 106a-n associated with the MBTA system 100. The symmetric shared secret is a cryptographic secret that can be used by the mobile computing device 106a to encrypt and decrypt BT. Fig. 9 As shown, the computer-implemented method 800 utilizes at least the XML configuration document 404, the secret management system 314, the BT management application 410, the BT management application hardware abstraction layer (HAL) extension 416 and / or the biometric TA 436 to import and provision symmetric shared secrets in one or more mobile computing devices 106a-n associated with the MBTA system 100.
[0129] The computer-implemented method 900 begins at step 902, where the BT management application 410 is caused to trigger (e.g., initiate) importing and / or provisioning of a symmetric shared secret in one or more mobile computing devices 106a-n. In various embodiments, the BT management application 410 may cause triggering of importing and / or provisioning of a symmetric shared secret in a particular mobile computing device 106a in response to receiving an XML configuration document notification from the MQTT broker 318 that includes data related to the XML configuration document 404. In this example, the XML configuration document 404 may be associated with one or more portions of executable program code that are configured to enable and / or disable one or more parameter settings and / or access permissions of the mobile computing device 106a related to provisioning of a symmetric shared secret generated by the secret management system 314.
[0130] In various other embodiments, the BT management application 410 may cause the importation and / or provisioning of a symmetric shared secret in a particular mobile computing device 106a in response to the particular mobile computing device 106a scanning a barcode (e.g., barcode 406) associated with the XML configuration document 404. The mobile computing device 106a may scan the barcode 406 via the optical engine 212 to obtain one or more portions of data (e.g., executable program code) associated with the XML configuration document 404 and thereby trigger the importation and / or provisioning of a symmetric shared secret generated by the secret management system 314.
[0131] At step 904, the BT management application 410 determines whether a symmetric shared secret associated with the MBTA system 100 has been enabled (e.g., previously imported and / or provisioned) on the mobile computing device 106a. If the BT management application 410 determines that a symmetric shared secret associated with the MBTA system 100 has not been enabled, the computer-implemented method 900 proceeds to step 906. At step 906, the BT management application 410 saves the current system state (e.g., one or more system parameter settings) associated with the mobile computing device 106a and proceeds to step 908.
[0132] At step 908, the BT management application 410 causes the mobile computing device 106a to download and / or otherwise obtain a symmetric shared secret from the secret management system 314 associated with the MBTA system 100 (e.g., via the network 104). At step 910, the BT management application 410 determines whether the symmetric shared secret has been successfully downloaded and / or received from the secret management system 314. If it is determined that the symmetric shared secret has not been successfully downloaded and / or received from the secret management system 314 (e.g., the symmetric shared secret is determined to be unavailable), the computer-implemented method 900 proceeds to step 912. At step 912, the BT management application 410 saves the current system state (e.g., one or more system parameter settings) associated with the mobile computing device 106a and the computer-implemented method 900 terminates. However, if it is determined that the symmetric shared secret has been successfully downloaded and / or received from the secret management system 314, the computer-implemented method 900 proceeds to step 914.
[0133] At step 914, the BT management application 410 is configured to call an API configured to provide a symmetric shared secret on the mobile computing device 106a. At step 916, in response to the API being called by the BT management application 410, the BT management application HAL extension 416 is instructed to import the symmetric shared secret. The BT management application HAL extension 416 is also instructed to transmit and / or otherwise communicate the symmetric shared secret to the biometric TA 436 associated with the TEE 430.
[0134] At step 918, the biometric TA 436 is configured to encrypt the symmetric shared secret with a unique authentication token (e.g., a hash-based message authentication code (HMAC) key associated with the mobile computing device 106a). In various embodiments, once the symmetric shared secret is encrypted using the HMAC key associated with the mobile computing device 106a, the encrypted symmetric shared secret may be retained (e.g., saved, stored, etc.) in a data file accessible by the TEE OS 432.
[0135] At step 920, the BT management application HAL extension 416 determines whether the symmetric shared secret was successfully imported and / or saved by the biometric TA 436. At step 922, the BT management application 410 determines whether an API configured to provide the symmetric shared secret on the mobile computing device 106a has been successfully completed. At step 924, the BT management application 410 saves the current system state (e.g., one or more system parameter settings) associated with the mobile computing device 106a and the computer-implemented method 900 is terminated.
[0136] Fig.12 A process flow diagram for providing secure MBTA across one or more mobile computing devices 106a-n according to one or more embodiments described herein is illustrated. Specifically, Fig.12 A method 1200 is illustrated for collecting biometric data from an end user 402 to generate a BT based on the biometric data associated with the end user 402. In one or more embodiments, the method 1200 is associated with the MBTA system 100. Additionally or alternatively, in various embodiments, the method 1200 is associated with one or more mobile computing devices 106a-n in conjunction with the MBTA system 100.
[0137] In various embodiments, method 1200 begins at operation 1202, which is configured to receive a request to generate a biometric template associated with a first end user, wherein the request to generate a biometric template associated with a first end user is generated via a first mobile computing device associated with a multi-user biometric template authentication (MBTA) system. For example, as described herein, end user 402 may use BT management application 410 (e.g., via one or more interactive display elements rendered on an electronic display associated with a particular mobile computing device 106a) to generate a BT and / or an associated PIN. Thus, BT management application 410 may generate request 216 configured to trigger enrollment of end user 402 into MBTA system 100.
[0138] The method 1200 also includes an operation 1204 configured to collect biometric data associated with the first end user in response to receiving the request. For example, the BT management application 410 can combine the biometric hardware 438 to collect biometric data associated with the specific end user 402. As described herein, in various contexts, the biometric data associated with the specific end user 402 can include, but is not limited to, fingerprint data, palm data, vein data, retina and / or iris data, voice data, facial feature data (e.g., face shape, eye shape, nose shape, etc.), body feature data (e.g., ear shape), DNA data, handwriting data, and / or any other physical and / or personal data related to the specific end user 402. Therefore, the biometric hardware 438 of the mobile computing device 106a can include one or more sensors, cameras, fingerprint scanners, palm scanners, eye scanners, one or more hardware components configured to sense the handwriting of the end user 402, one or more microphones, and / or any combination thereof.
[0139] The method 1200 also includes an operation 1206, which is configured to generate a biometric template associated with the first end user based on the biometric data. For example, the BT management application 410 can generate the biometric template based on the biometric data associated with the end user 402 (e.g., fingerprint data, palm data, facial feature data, etc.) (e.g., in conjunction with the processing circuit 202).
[0140] The method 1200 also includes an operation 1208 configured to generate a personal identification number (PIN), wherein the PIN is associated with a biometric template associated with the first end user. As described herein, in various embodiments, a BT management application 410 associated with a particular mobile computing device 106a can be used to collect biometric data (e.g., fingerprint data) from an end user 402, generate a BT based on the biometric data, and generate a secure PIN associated with the BT associated with the end user 402. The PIN can be used in conjunction with the BT to authenticate the end user 402 on any of the one or more mobile computing devices 106a-n.
[0141] The method 1200 also includes an operation 1210 configured to store at least one of a biometric template or a PIN associated with the first end user in an active biometric template database or an active PIN database, respectively, wherein the active biometric template database and the active PIN database are associated with the MBTA system. For example, the BT management application 410 may cause the mobile computing device 106a to transmit the newly generated BT and / or PIN to the FTP server 316 for verification and storage. Additionally or alternatively, the MBTA system 100 may employ one or more APIs to move the BT data file and / or PIN data file that has been uploaded to the FTP server 316 to the correct folder and / or storage location in the FTP server. For example, the BT data file and / or the associated BT, and / or the PIN data file and / or the associated PIN may be stored in an active BT database and / or an active PIN list associated with the MBTA system 100, respectively (e.g., in the FTP server 316 and / or the MBTA database 108).
[0142] The method 1200 also includes an operation 1212 configured to transmit MBTA data for storage on a plurality of mobile computing devices different from the first mobile computing device, wherein the MBTA data includes at least one of data associated with an active biometric template database or data associated with an active PIN database. As described herein, in various embodiments, the active BT database includes a list of one or more BTs associated with one or more respective end users 402 currently registered in the MBTA system 100, and a representation (e.g., a structured list, a copy of the active BT database, etc.) associated with the active BT database is stored locally on the one or more mobile computing devices 106a-n. Additionally, in various embodiments, the active PIN database includes a list of one or more PINs associated with one or more respective biometric templates (BTs) associated with the one or more respective end users 402 currently registered in the MBTA system 100, and a representation (e.g., a structured list, a copy of the active BT database, etc.) associated with the active PIN database is stored locally on the one or more mobile computing devices 106a-n.
[0143] Thus, each active end user 402 currently registered at and / or associated with the MBTA system 100 may authenticate themselves on any of the one or more mobile computing devices 106a-n by providing biometric data associated with the end user 402 for generating a BT to any of the one or more mobile computing devices 106a-n. As a non-limiting example, the end user 402 may provide biometric data such as a fingerprint (e.g., via the biometric hardware 438), and the BT management application 410 may determine whether the fingerprint matches a corresponding BT included in an active BT list stored locally on the mobile computing device 106a. If it is determined (e.g., via one or more biometric data matching algorithms) that the provided biometric data (e.g., fingerprint) matches a corresponding BT included in an active BT list stored locally on the mobile computing device 106a, the end user 402 will be allowed access to the mobile computing device 106a.
[0144] in conclusion
[0145] The general discussion of the present disclosure provides a brief overall description of a suitable computing environment that can realize the present disclosure. In one embodiment, any one of the disclosed system, method and / or graphical user interface can be executed or implemented by a computing system consistent with or similar to the computing system shown and / or explained in the present disclosure. Although not necessary, the various aspects of the present disclosure are described in the context of computer executable instructions, such as by a data processing device, for example, a routine executed by a server computer, a wireless device and / or a personal computer. Those skilled in the art will know that the various aspects of the present disclosure can be put into practice using other communications, data processing or computer system configurations, including Internet home appliances, handheld devices (including personal digital assistants ("PDAs")), wearable computers, various cellular phones or mobile phones (including voice over IP ("VoIP") phones), dumb terminals, media players, gaming devices, virtual reality devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, set-top boxes, network PCs, microcomputers, mainframe computers, etc. In fact, the terms "computer", "server", etc. are usually used interchangeably herein, and refer to any of the above-mentioned devices and systems and any data processors.
[0146] Aspects of the present disclosure may be embodied in a special-purpose computer and / or data processor that is specifically programmed, configured, and / or constructed to perform one or more computer-executable instructions described in detail herein. Although aspects of the present disclosure, such as certain functions, are described as being performed only on a single device, the present disclosure may also be practiced in a distributed environment, where functions or modules are shared between different processing devices linked by a communication network, such as a local area network ("LAN"), a wide area network ("WAN"), and / or the Internet. Similarly, the techniques presented herein as involving multiple devices may be implemented in a single device. In a distributed computing environment, program modules may be located in a local memory storage device and / or a remote memory storage device.
[0147] Aspects of the present disclosure may be stored and / or distributed on non-transitory computer readable media, including magnetic or optical readable computer disks, hardwired or pre-programmed chips (e.g., EEPROM semiconductor chips), nanotechnology memories, biological memories, or other data storage media. Alternatively, computer-implemented instructions, data structures, screen displays, and other data under various aspects of the present disclosure may be distributed over a period of time over the Internet and / or over other networks (including wireless networks) on propagation signals on a propagation medium (e.g., one or more electromagnetic waves, sound waves, etc.), and / or they may be provided on any analog or digital network (packet switching, circuit switching, or other schemes).
[0148] The program aspects of the technology can be considered as a "product" or "article of manufacture" generally in the form of executable code and / or associated data, which is carried or embodied in a type of machine-readable medium. "Storage" type media include any or all tangible memories of computers, processors, etc. or their associated modules, such as various semiconductor memories, tape drives, disk drives, etc., which can provide non-transitory storage for software programming at any time. All or part of the software can sometimes communicate through the Internet or various other telecommunications networks. For example, such communications can enable software to be loaded from one computer or processor to another computer or processor, such as from a management server or host of a mobile communication network to a server's computer platform and / or from a server to a mobile computing device. Therefore, another type of medium that can carry software elements includes light waves, radio waves, and electromagnetic waves, such as those used on physical interfaces between local devices, through wired and optical ground networks, and through various air links. Physical elements that carry such waves, such as wired or wireless links, optical links, etc., can also be considered as media that carry software. As used herein, unless restricted to non-transitory, tangible "storage" media, terms such as computer or machine "readable medium" refer to any medium that participates in providing instructions to a processor for execution.
[0149] In some example embodiments, some of the operations herein may be modified or further amplified as described below. In addition, in some embodiments, additional optional operations may also be included. It should be understood that each of the modifications, optional additions, or amplifications described herein may be included in the operations herein individually or in combination with any other features described herein.
[0150] The foregoing method descriptions and process flow charts are provided only as illustrative examples, and are not intended to require or imply that the steps of the various embodiments must be performed in the order presented. As will be appreciated by those skilled in the art, the order of steps in the above-described embodiments may be performed in any order. Words such as "afterwards," "then," "next," etc. are not intended to limit the order of steps; these words are merely used to guide the reader through the description of the method. In addition, for example, any reference to a claim element in the singular form using the articles "a" or "the" should not be construed as limiting the element to the singular.
[0151] It should be understood that “one or more” includes a function performed by one element, a function performed by more than one element, such as in a distributed manner, several functions performed by one element, several functions performed by several elements, or any combination of the above.
[0152] In addition, it should also be understood that, although in some cases, the terms "first", "second", etc. are used to describe various elements herein, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, without departing from the scope of the various described embodiments, the first contact may be referred to as the second contact, and similarly, the second contact may be referred to as the first contact. Both the first contact and the second contact are contacts, but they are not the same contact.
[0153] The terms used in the description of the various embodiments described herein are only used for the purpose of describing specific embodiments and are not intended to be limiting. As used in the description of the various embodiments described and the appended claims, the singular forms "one" and "the" are also intended to include plural forms, unless the context clearly indicates otherwise. It should also be understood that, as used herein, the term "and / or" refers to and encompasses any and all possible combinations of one or more of the associated listed items. It should also be understood that when the term "comprising" is used in this specification, the presence of the features, wholes, steps, operations, elements and / or parts is specified, but the presence or addition of one or more other features, wholes, steps, operations, elements, parts and / or their groups is not excluded.
[0154] As used herein, the term "if" is optionally interpreted to mean "when" or "upon" or "in response to determining" or "in response to detecting", depending on the context. Similarly, the phrases "if it is determined" or "if [the condition or event] is detected" are optionally interpreted to mean "upon determining" or "in response to determining" or "upon detecting [the condition or event]" or "in response to detecting [the condition or event]", depending on the context.
[0155] The disclosed systems, devices, equipment and methods of the present invention are described in detail by way of example with reference to the accompanying drawings. The examples discussed in the present invention are merely examples, and the purpose of providing is to help explain the devices, devices, systems and methods described herein. Any features or components shown in the accompanying drawings or discussed below should not be considered as mandatory for any specific implementation of any of these devices, devices, systems or methods, unless explicitly stated to be mandatory. For ease of reading and clarity, some components, modules or methods may be described only in conjunction with specific drawings. In the present disclosure, any indication of specific techniques, arrangements, etc. is either related to the specific examples proposed, or is merely a general description of such techniques, arrangements, etc. The indication of specific details or examples is not intended to be or should not be interpreted as mandatory or restrictive, unless explicitly stated to be so. Any situation in which a combination or sub-combination of components is not explicitly described should not be understood as an indication that any combination or sub-combination is impossible. It should be understood that the disclosed and described examples, arrangements, configurations, components, elements, devices, equipment, systems, methods, etc. may be modified, and this may be required for specific patent applications. In addition, for any method described, whether or not the method is described in conjunction with a flowchart, it should be understood that, unless otherwise indicated or required by the context, any explicit or implied ordering of the steps performed during the method execution does not mean that these steps must be performed in the order presented, but may be performed in a different order or in parallel.
[0156] Throughout this disclosure, the components or modules mentioned generally refer to objects that can be logically combined to perform a function or a group of related functions. Similar reference numerals are generally intended to refer to the same or similar components. Components and modules can be implemented in software, hardware, or a combination of software and hardware. The term "software" is used in a broad sense to include not only executable code such as machine executable or machine interpretable instructions, but also data structures, data storage, and computing instructions stored in any suitable electronic format, including firmware and embedded software. The terms "information" and "data" are widely used and include a wide variety of electronic information, including executable code; content such as text, video data, and audio data, etc.; and various codes or marks. The terms "information", "data", and "content" are sometimes used interchangeably when the context allows.
[0157] Hardware for implementing the various illustrative logics, logic blocks, modules, and circuits described in conjunction with the various aspects disclosed herein may include a general purpose processor, a digital signal processor (DSP), a special purpose processor such as an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA), a programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but alternatively, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Alternatively or in addition, some steps or methods may be performed by circuits specific to a given function.
[0158] In one or more example embodiments, the functions described herein may be implemented by a combination of dedicated hardware or hardware programmed by firmware or other software. In a specific implementation that relies on firmware or other software, these functions may be performed due to the execution of one or more instructions stored on one or more non-transient computer-readable media and / or one or more non-transient processor-readable media. These instructions may be embodied by one or more processor-executable software modules residing on one or more non-transient computer-readable or processor-readable storage media. In this regard, non-transient computer-readable or processor-readable storage media may include any storage medium accessible by a computer or processor. As an example and not limitation, such non-transient computer-readable or processor-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), FLASH memory, disk storage, magnetic storage devices, etc. As used herein, disk storage includes compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and blue discs TM , or other storage devices that store data magnetically or optically using lasers. Combinations of the above types of media are also included within the scope of the term non-transitory computer-readable and processor-readable media. Additionally, any combination of instructions stored on one or more non-transitory processor-readable or computer-readable media may be referred to herein as a computer program product.
[0159] Those skilled in the art to which the invention pertains will recognize many modifications and other embodiments of the invention set forth herein, having the benefit of the teachings presented in the foregoing description and associated drawings. Although the figures show only certain components of the apparatus and systems described herein, it should be understood that various other components may be used in conjunction with the supply management system. Therefore, it should be understood that the invention is not limited to the specific embodiments disclosed, and modifications and other embodiments are intended to be included within the scope of the appended claims. In addition, the steps in the method described above may not necessarily occur in the order depicted in the drawings, and in some cases, one or more of the depicted steps may occur substantially simultaneously, or may involve additional steps. Although specific terms are employed herein, they are used only in a general and descriptive sense, and not for purposes of limitation.
[0160] It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
Claims
1. A system comprising: one or more processors; Memory; as well as One or more programs, the one or more programs stored in the memory, the one or more programs comprising instructions configured to: receiving a request to generate a biometric template associated with a first end user, wherein the request to generate the biometric template associated with the first end user is generated via a first mobile computing device associated with a multi-user biometric template authentication (MBTA) system; In response to receiving the request: collecting biometric data associated with the first end user; generating the biometric template associated with the first end user based on the biometric data; generating a personal identification number (PIN), wherein the PIN is associated with the biometric template associated with the first end user; storing at least one of the biometric template or the PIN associated with the first end user in an active biometric template database or an active PIN database, respectively, wherein the active biometric template database and the active PIN database are associated with the MBTA system; and MBTA data is transmitted for storage on a plurality of mobile computing devices different from the first mobile computing device, wherein the MBTA data includes at least one of data associated with the active biometric template database or data associated with the active PIN database.
2. The system of claim 1, wherein the one or more programs further comprise instructions configured to: authenticating the first end user based in part on a first interaction with a second mobile computing device of the plurality of mobile computing devices, wherein the first interaction with the second mobile computing device comprises collecting, via the second mobile computing device, the biometric data associated with the first end user and matching the biometric data with the biometric template associated with the first end user using a biometric data matching algorithm, and Wherein the biometric template is included in the active biometric template database stored on the second mobile computing device.
3. The system of claim 2, wherein the instructions configured to authenticate the first end user via the second mobile computing device further comprise instructions configured to: authenticating the first end user based in part on a second interaction with the second mobile computing device, wherein the second interaction with the second mobile computing device includes receiving, via the second mobile computing device, the PIN associated with the biometric template associated with the first end user, and verifying the PIN based in part on data associated with the active PIN database stored on the second mobile computing device.
4. The system of claim 1 , wherein the one or more programs further comprise instructions configured to cause at least one of encryption or decryption of one or more biometric templates based in part on a symmetric shared secret, wherein the symmetric shared secret is generated by a secret management system associated with the MBTA system, and wherein the secret management system is configured to distribute the symmetric shared secret to each respective one of the plurality of mobile computing devices, wherein the symmetric shared secret is imported into a biometric trusted application included in a trusted execution environment (TEE) of each respective one of the plurality of mobile computing devices, and wherein the symmetric shared secret is associated with a hash-based message authentication code associated with each respective one of the plurality of mobile computing devices.
5. The system of claim 5, wherein the symmetric shared secret is imported into a biometric trusted application included in a trusted execution environment (TEE) of each respective mobile computing device in the plurality of mobile computing devices, and Wherein the symmetric shared secret is associated with a hash-based message authentication code associated with each respective mobile computing device of the plurality of mobile computing devices.
6. The system of claim 1 , wherein the instructions for transmitting the MBTA data for storage on the plurality of mobile computing devices are further configured to: notifying the plurality of mobile computing devices via an MQTT broker associated with the MBTA system that at least one of the active biometric template database or the active PIN database has been updated; and The plurality of mobile computing devices are caused to obtain current data associated with the at least one of the active biometric template database or the active PIN database.
7. The system of claim 6, wherein the instructions are further configured to: removing at least one of the one or more biometric templates or the one or more PINs from the active biometric template database or the active PIN database, respectively, wherein removing the at least one of the one or more biometric templates or the one or more PINs comprises: notifying the plurality of mobile computing devices via the MQTT broker associated with the MBTA system that the at least one of the one or more biometric templates or the one or more PINs has been removed; as well as The plurality of mobile computing devices are caused to obtain the current data associated with the at least one of the active biometric template database or the active PIN database.
8. The system of claim 1, wherein the one or more programs further comprise instructions configured to: Remotely enabling or disabling an MBTA authentication mode on the first mobile computing device or at least one of the plurality of mobile computing devices.
9. The system of claim 1, wherein the MBTA data further comprises one or more Extensible Markup Language (XML) configuration documents, and Wherein the first mobile computing device and the plurality of mobile computing devices are configured in part by executing one or more commands associated with the one or more XML configuration documents.
10. The system of claim 1, wherein the one or more programs further comprise instructions configured to: authenticating a second end user based in part on the first interaction with a third mobile computing device of the plurality of mobile computing devices, wherein the first interaction with the third mobile computing device includes collecting biometric data associated with the second end user via the third mobile computing device and matching the biometric data associated with the second end user with a biometric template associated with the second end user using a biometric data matching algorithm, wherein the biometric template associated with the second end user is generated in response to receiving a request by the MBTA system from a fourth mobile computing device to generate the biometric template associated with the second end user, and Wherein the biometric template associated with the second end user is included in the active biometric template database stored on the third mobile computing device.
