# US 12,120,238 B2 · Secure digital information infrastructure > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,120,238 B2 - Document ID: US12120238B2 - Status: Granted - Kind: B2 - Application number: 18/354,902 - Filed: 2023-07-19 - Published: 2024-06-06 - Granted: 2024-10-15 - Earliest claimed: 2019-10-10 - Assignees: Oasis Medical, Inc. - Applicants: Oasis Medical, Inc. - Inventors: Norman Craig Delgado - Web page: https://patentgrep.com/patent/US12120238B2 ## CPC - H04L 9/3226: {using a predetermined code, e.g. password, passphrase or PIN (network architectures or network communication protocols for supporting authentication of entities using passwords in a packet data network H04L63/083)} - H04L 9/0863: {involving passwords or one-time passwords (network architectures or network communication protocols for using one-time keys in a packet data network H04L63/067)} - H04L 9/3213: {using tickets or tokens, e.g. Kerberos (network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807)} - H04L 63/0807: {using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213)} - H04L 63/104: {Grouping of entities} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract An authentication and encryption computer system is disclosed including processing devices, a network interface, and a data store. The authentication and encryption system is configured to maintain in the data store content common to a plurality of entities and content independently specified by each of the plurality of entities. The system is configured to receive a content request from an application executing on a mobile device, the content request comprising a secure access code corresponding to an entity, and the content request encrypted by the mobile device. An interface, comprising the content common to the plurality of entities, is customized to include content independently specified by the entity, wherein the content independently specified by the entity comprises a token value. A user request for an item presented via the interface is received and the token value is transferred to the entity. ## Claims ### Claim 1 An authentication and encryption computer system, the authentication and encryption computer system comprising: one or more processing devices; a network interface; and non-transitory memory that stores instructions that when executed by the one or more processing devices are configured to cause the computer system to perform operations comprising: maintain in memory unique security access codes for respective entities in a first plurality of entities; maintain a data store comprising: the security access codes with an indication as to which of the security access codes is associated with which entity in the first plurality of entities; first common content common to the first plurality of entities; and custom content for entities in the first plurality of entities specified by the respective entities in the first plurality of entities; receive an encrypted first content request from an application executing on a first user device of a first user, the first content request comprising a first securityaccess code, the first securityaccess code corresponding to a first entity of the first plurality of entities; at least partly in response to receiving the first content request: decrypt the received first content request comprising the first security access code; determine that the received first security access code is associated with the first entity; cause a first user interface, comprising at least a portion of the first common content common to the first plurality of entities, to be customized to include custom content for the first entity, wherein the first common content common to the first plurality of entities comprises item data for a first item and wherein the custom content for the first entity comprises a first token value; receive from the first user device a first user request for the first item presented via the first user interface; and enable a first instantiation of the first item to be transferred to the first user. ### Claim 2 (depends on 1) The authentication and encryption computer system as defined in claim 1, wherein the security access codes are restricted to a first number of access code characters and are generated using respective unique seeds. ### Claim 3 (depends on 1) The authentication and encryption computer system as defined in claim 1, the operations further comprising: receive a handshake from the user device, the handshaking message indicting a data compression method supported by the first user device; respond to the first user device with a handshaking message which identifies a cipher suite that will be used in communicating with the first user device; and use the identified cipher suite in encrypting communications with the first device. ### Claim 4 (depends on 1) The authentication and encryption computer system as defined in claim 1, wherein the authentication and encryption computer system is further configured to: receive an encrypted request from a device of a second user for an access security code for a second entity, wherein the encrypted request from the device of the second user is received in association with an identification of the second user and an identification of the second entity; decrypt the encrypted request from the second user device; transmit a verification request message to a destination associated with the second entity, the verification request message including the identification of the second user; at least partly in response to receiving a verification confirmation message from the second entity: retrieve the access security code for the second entity from memory; and enable the retrieved access security code for the second entity to be transmitted via an encrypted channel to the second user device. ### Claim 5 (depends on 1) The authentication and encryption computer system as defined in claim 1, wherein the authentication and encryption computer system is further configured to: at least partly in response to the received first user request for the first item: cause the first token value to be transferred from the first user to the first entity; and cause a second token value, different than the first token value, to be transferred from the first entity to a token destination. ### Claim 6 (depends on 1) The authentication and encryption computer system as defined in claim 1, wherein the authentication and encryption computer system is further configured to: receive a role identification message from a user device; and use the role identification included in the role identification message to determine how to process one or more items of user data. ### Claim 7 (depends on 1) The authentication and encryption computer system as defined in claim 1, wherein the first user interface, comprising the first content common to the first plurality of entities and customized to include the custom content the first entity, is interactive and comprises a plurality of links to respective different item detail documents. ### Claim 8 (depends on 1) The authentication and encryption computer system as defined in claim 1, wherein the authentication and encryption computer system is further configured to: track how many users have received a security access code of a given entity; track transactions by users using the security access code of the given entity; generate an electronic communication comprising an indication as to how many users have received the security access code, and an aggregation summary of the tracked transactions; and enable the given entity to access the electronic communication. ### Claim 9 A computer-implemented method comprising: maintaining in memory unique security access codes for respective entities in a first plurality of entities; maintaining a data store comprising: first common content common to the first plurality of entities; and custom content for respective entities in the first plurality of entities specified by the respective entities in the first plurality of entities ; receiving an encrypted first content request from a first user device of a first user, the first content request comprising a first security access code, the first security access code corresponding to a first entity of the first plurality of entities; decrypting the received first content request comprising the first security access code; causing a first user interface, comprising at least a portion of the first common content common to the first plurality of entities, to be customized to include custom content for the first entity, wherein the first common content common to the first plurality of entities comprises item data for a first item and wherein the custom content for the first entity comprises a first token value; receiving from the first user device a first user request for the first item presented via the first user interface; and enabling a first instantiation of the first item to be transferred to the first user. ### Claim 10 (depends on 9) The computer-implemented method as defined in claim 9, wherein the security access codes are restricted to a first number of access code numbers. ### Claim 11 (depends on 9) The computer-implemented method as defined in claim 9, the method further comprising: receiving a handshake from the user device, the handshaking message indicting a data compression method supported by the first user device; responding to the first user device with a handshaking message which identifies a cipher suite that will be used in communicating with the first user device; and using the identified cipher suite in encrypting communications with the first device. ### Claim 12 (depends on 9) The computer-implemented method as defined in claim 9, the method further comprising: receiving an encrypted request from a device of a second user for an access security code for a second entity, wherein the encrypted request from the device of the second user is received in association with an identification of the second user and an identification of the second entity; decrypting the encrypted request from the second user device; verifying that that second user is associated with a corresponding access security code; at least partly in response to verifying that that second user is associated with a corresponding access security code; and enabling the corresponding access security code for the second entity to be transmitted via an encrypted channel to the second user device. ### Claim 13 (depends on 9) The computer-implemented method as defined in claim 9, the method further comprising: at least partly in response to the received first user request for the first item: causing the first token value to be transferred from the first user to the first entity; and causing a third token value, different than the first token value, to be transferred from the first entity to a token destination. ### Claim 14 (depends on 9) The computer-implemented method as defined in claim 9, the method further comprising: receiving a role identification message from a user device; and using the role identification included in the role identification message to determine how to process one or more items of user data. ### Claim 15 (depends on 9) The computer-implemented method as defined in claim 9, wherein the first user interface, comprising the first content common to the first plurality of entities and customized to include the custom content for the first entity, is interactive and comprises a plurality of links to respective different item detail documents. ### Claim 16 (depends on 9) The computer-implemented method as defined in claim 9, the method further comprising: tracking how many users have received a security access code of a given entity; tracking transactions by users using the security access code of the given entity; generating an electronic communication comprising an indication as to how many users have received the security access code, and an aggregation summary of the tracked transactions; and enabling the given entity to access the electronic communication. ### Claim 17 Non-transitory computer readable data media that stores computer executable instructions that when executed by a computing device, cause the computing device to perform operations comprising: storing in memory unique security access codes for respective entities in a first plurality of entities; storing in memory: first common content common to the first plurality of entities; and custom content for respective entities of the first plurality of entities specified by the respective entities of the first plurality of entities; receiving a first content request from a first user device of a first user, the first content request comprising a first security access code, the first security access code corresponding to a first entity of the first plurality of entities; in response to receiving the first content request: determining that the received first security access code is associated with the first entity; causing a first user interface, comprising at least a portion of the first common content common to the first plurality of entities, to be customized to include custom content for the first entity, wherein the first common content common to the first plurality of entities comprises item data for a first item and wherein the custom content for the first entity comprises a first token value; receiving from the first user device a first user request for the first item presented via the first user interface; and enabling a first instantiation of the first item to be transferred to the first user. ### Claim 18 (depends on 17) The non-transitory computer readable data media as defined in claim 17, wherein the security access codes are restricted to a first number of access code numbers. ### Claim 19 (depends on 17) The non-transitory computer readable data media as defined in claim 17, the operations further comprising: receiving a handshake from the user device, the handshaking message indicting a data compression method supported by the first user device; respond to the first user device with a handshaking message which identifies a cipher suite that will be used in communicating with the first user device; and using the identified cipher suite in encrypting communications with the first device. ### Claim 20 (depends on 17) The non-transitory computer readable data media as defined in claim 17, the operations further comprising: receiving a request from a device of a second user for an access security code for a second entity, wherein the request from the device of the second user is received in association with an identification of the second user and an identification of the second entity; verifying that that second user is associated with a corresponding access security code; and enabling the corresponding access security code for the second entity to be transmitted via an encrypted channel to the second user device. ### Claim 21 (depends on 17) The non-transitory computer readable data media as defined in claim 17, the operations further comprising: at least partly in response to the received first user request for the first item: causing the first token value to be transferred from the first user to the first entity; causing a third token value, different than the first token value, to be transferred from the first entity to a token destination; at least partly in response to the received second user request for the first item; and causing the second token value to be transferred from the second user to the second entity. ### Claim 22 (depends on 17) The non-transitory computer readable data media as defined in claim 17, the operations further comprising: receiving a role identification message from a user device; and using the role identification included in the role identification message to determine how to process one or more items of user data. ### Claim 23 (depends on 17) The non-transitory computer readable data media as defined in claim 17, wherein the first user interface, comprising the first content common to the first plurality of entities and customized to include the custom content for the first entity, is interactive and comprises a plurality of links to respective different item detail documents. ### Claim 24 (depends on 17) The non-transitory computer readable data media as defined in claim 17, the operations further comprising: tracking how many users have received a security access code of a given entity; tracking transactions by users using the security access code of the given entity; generating an electronic communication comprising an indication as to how many users have received the security access code, and an aggregation summary of the tracked transactions; and enabling the given entity to access the electronic communication.