Client-driven randomized and changing media access control (mac) address (rcm) mechanism
US-2024422202-A1 · Dec 19, 2024 · US
US12413628B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12413628-B2 |
| Application number | US-202117453769-A |
| Country | US |
| Kind code | B2 |
| Filing date | Nov 5, 2021 |
| Priority date | Nov 5, 2021 |
| Publication date | Sep 9, 2025 |
| Grant date | Sep 9, 2025 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
In some implementations, a system may receive, from a terminal, an account identifier, an authentication credential, and a request for data associated with a user, wherein the request may identify requested data items associated with the account identifier. The system may authenticate the request using the account identifier and the authentication credential. The system may determine whether the request satisfies a pre-approval condition after authenticating the request. The system may transmit a first message to a user device associated with the user or transmit a second message to a third party device associated with the terminal based on whether the requested data items satisfy the pre-approval condition. The first message to the user device may request approval to transmit the requested data items to the third party device via the second message, and the second message may enable access to the requested data items.
Opening claim text (preview).
What is claimed is: 1. A system for authentication of data sharing, the system comprising: one or more memories; and one or more processors, communicatively coupled to the one or more memories, configured to: receive, from a terminal, an account identifier, a biometric credential, and a request for data associated with a user based on an interaction between the terminal and a physical medium associated with the account identifier, wherein the biometric credential is communicated from the physical medium to the terminal, and wherein the request is one of: a specific request that identifies one or more requested data items associated with the account identifier, or a general request that does not identify any requested data items; authenticate the request using the biometric credential; identify user contact information associated with the account identifier based on authenticating the request; transmit a message to a user device based on the user contact information, wherein content of the message depends on whether the request is the specific request or the general request; receive, from the user device, an indication to approve transmission of the data to a third party device associated with the terminal, wherein the indication approves transmission of the one or more requested data items if the request is the specific request, or wherein the indication indicates one or more user-specified data items to be transmitted to the third party device if the request is the general request; and transmit the data or information that enables access to the data to the third party device based on receiving the indication, wherein the data includes the one or more requested data items if the request is the specific request, or wherein the data includes the one or more user-specified data items if the request is the general request. 2. The system of claim 1 , wherein the one or more processors are configured to identify all data items associated with the account identifier; and wherein the content of the message indicates all of the data items associated with the account identifier based on the request being the general request. 3. The system of claim 1 , wherein the one or more processors are further configured to: receive, from the terminal, a third party identifier that identifies a third party making the request; and identify a set of data items based on the account identifier and the third party identifier; and wherein the content of the message indicates the set of data items based on the request being the general request. 4. The system of claim 1 , wherein the one or more processors are further configured to: identify a set of data items based on the account identifier and the biometric credential, wherein different users associated with the account identifier are associated with different biometric credentials; and wherein the content of the message indicates the set of data items based on the request being the general request. 5. The system of claim 1 , wherein the one or more processors, to identify the user contact information associated with the account identifier, are configured to: identify the user contact information based on the account identifier and the biometric credential; and wherein different users associated with the account identifier are associated with different user contact information. 6. The system of claim 1 , wherein the content of the message indicates a set of data items identified by the system based on the request being the general request. 7. The system of claim 6 , wherein the one or more user-specified data items are a subset of data items included in the set of data items. 8. The system of claim 1 , wherein the content of the message indicates the one or more requested data items based on the request being the specific request. 9. A method for authentication of data sharing, comprising: receiving, by a system and from a terminal, an account identifier, an authentication credential, and a request for data associated with a user based on an interaction between the terminal and a physical medium that stores the account identifier and the authentication credential, wherein the authentication credential and the account identifier are communicated from the physical medium to the terminal, and wherein the request is one of: a specific request that identifies one or more requested data items associated with the account identifier, or a general request that does not identify any requested data items; authenticating, by the system, the request using the account identifier and the authentication credential; generating, by the system, content for a message based on whether the request is the specific request or the general request; transmitting, by the system and based on authenticating the request, the message to a user device based on user contact information associated with the account identifier; receiving, by the system and from the user device, an indication to approve transmission of the data to a third party device, wherein content of the indication depends on whether the request is the specific request or the general request; and transmitting, by the system, the data, or information that enables access to the data, to the third party device based on receiving the indication, wherein the data includes the one or more requested data items or one or more user-specified data items indicated in the indication to approve transmission of the data. 10. The method of claim 9 , wherein the authentication credential is a biometric credential that is received from the terminal based on the terminal powering the physical medium for fingerprint authentication by the physical medium. 11. The method of claim 9 , further comprising receiving third party contact information from the terminal; and wherein the data or the information that enables access to the data is transmitted to the third party device using the third party contact information. 12. The method of claim 9 , further comprising: receiving a third party identifier from the terminal; and identifying third party contact information based on the third party identifier and a third party profile associated with the third party identifier; and wherein the data or the information that enables access to the data is transmitted to the third party device using the third party contact information. 13. The method of claim 9 , wherein generating the message comprises generating the message to include an input element for input of third party contact information based on a determination that the system has not received or does not store the third party contact information; and further comprising receiving the third party contact information from the user device based on the message; and wherein the data or the information that enables access to the data is transmitted to the third party device using the third party contact information. 14. The method of claim 9 , further comprising: generating a passcode for authenticating access to the data; transmitting the passcode to the user device; receiving, from the third party device, an access request to access the data; prompting input of the passcode based on the access request; and providing access to the data based on authentication of the passcode. 15. The method of claim 9 , wherein the data includes at least one of driver's license information, passport information, government-issued identification, a social security number, a credit score, birth certificate information, vaccination record information, a personal identification numb
Tools and structures for managing or administering access control systems · CPC title
using an additional device, e.g. smartcard, SIM or a different communication terminal (cryptographic mechanisms or cryptographic arrangements for entity authentication involving additional secure or trusted devices H04L9/3234) · CPC title
Biometric identity checks · CPC title
Entity profiles · CPC title
for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.