"dynamic contact exchange system"
The dynamic contact exchange system addresses inefficiencies in contact information exchange by using a DCE server with lifecycle and cryptographic controls for seamless, bidirectional data sharing and real-time updates, enhancing professional networking efficiency.
Patent Information
- Application Number
- PCT/IN2026/050769
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-04
- Filing Date
- 2026-05-04
- Publication Date
- 2026-11-12
AI Technical Summary
Existing methods for exchanging contact information are inefficient, prone to errors, and lack seamless, bidirectional data sharing, leading to outdated records and increased clutter, which impairs professional networking efficiency.
A dynamic contact exchange system with a DCE server that manages identity data and relationship metadata, employing a lifecycle control framework with cryptographic controls to enable relationship-centric access management, allowing for bidirectional exchange, real-time updates, and controlled propagation of access through lineage-based mechanisms.
Facilitates efficient, scalable, and relevant professional networking by ensuring accurate and synchronized contact information exchange with real-time updates and controlled access management, reducing clutter and errors.
Smart Images

Figure IN2026050769_12112026_PF_FP_ABST
Abstract
Description
[0001] “DYNAMIC CONTACT EXCHANGE SYSTEM”
[0002] FIELD OF THE INVENTION:
[0003] The present invention relates to methods and systems for exchanging contact information. More specifically, it relates to a dynamic contact exchange system that facilitates seamless, bidirectional exchange between users through a relationship-entity driven architecture, wherein access to identity data is governed by lifecycle states, enforced through cryptographic controls, and propagated across entities via lineage-based mechanisms with cascade revocation.
[0004] BACKGROUND OF THE INVENTION:
[0005] In typical scenarios involving meetings, conferences, trade exhibitions, and professional events, participants commonly exchange physical business cards containing information such as name, organization, designation, telephone number, email address, business context and other contact particulars. Individuals who frequently attend such events often accumulate large quantities of business cards, making transportation, storage, retrieval, and organization inconvenient and inefficient. Over time, the accumulation of unmanaged or outdated connections leads to increased informational clutter and reduced data relevance, wherein a substantial portion of stored contacts becomes non-actionable, thereby impairing efficient retrieval and distracting users from core professional activities.
[0006] To manage collected business cards, users typically rely upon storage tools such as rolodex systems, folders, drawers, or filing cabinets, each of which haspractical limitations relating to capacity, accessibility, and long-term maintenance. As a result, many collected cards are misplaced, forgotten, or discarded. In addition, organizations are required to bear recurring expenses associated with designing, printing, and distributing business cards for employees, representatives, or members.
[0007] In the modem networking environment, professionals also use messaging platforms, text messages, or social communication applications to exchange contact details. However, such methods are often informal, fragmented, and not structured for long-term professional relationship management. Information shared through such channels may be difficult to retrieve later, may become lost in message histories, and generally lacks a dedicated mechanism for maintaining ongoing professional connectivity. Further, when user changes contact details such as a mobile number, designation, or email address, previously shared contacts are not automatically informed, resulting in outdated records and communication gaps.
[0008] Traditional methods of exchanging contact information, including paper business cards and manual entry into address books or devices, are also timeconsuming and prone to errors. These methods generally do not support mutual or bidirectional exchange in a single interaction, automatic synchronization, controlled sharing preferences, or real-time updating of previously shared information, any modification to shared data usually requires separate manual communication with each prior contact.
[0009] With the widespread adoption of smartphones and wireless communication technologies, certain prior systems have attempted to digitize contact exchangethrough mechanisms such as near-field communication (NFC), Bluetooth, QR codes, and similar technologies. While such approaches may improve convenience, existing solutions typically provide only partial functionality and are often limited to unilateral transfer of data, static information sharing, or isolated transactions without persistent relationship management.
[0010] Accordingly, there exists a need for a dynamic contact exchange system that facilitates relationship-centric identity access control and propagation for enabling seamless, bidirectional exchange of contact information. Also, there exists a need for a system that supports real-time data sharing, automated update propagation, and controlled management of identity data, thereby improving efficiency, scalability, and relevance in professional networking interactions.
[0011] SUMMARY OF THE INVENTION:
[0012] The present disclosure relates to a dynamic contact exchange system for controlled access to identity data. The system includes a DCE server configured to store identity data and manage relationship metadata associated with a plurality of entities, and a plurality of user devices configured to receive identity data and perform access operations based on device-specific credentials.
[0013] The system further includes a relationship graph including a plurality of relationship entities, each representing an association between at least two entities. A lifecycle control framework assigns and transitions lifecycle states of the relationship entities based on interaction events. Access to identity data iscontrolled by a cryptographic control structure based on the lifecycle state of the relationship entity.
[0014] A delegation structure enables generation of downstream relationship entities linked to an upstream relationship entity to propagate access along a lineage path. A revocation mechanism transitions a relationship entity to a revoked state and propagates revocation to downstream relationship entities by modifying cryptographic conditions to prevent access to the identity data.
[0015] Each relationship entity maintains an independent lifecycle state, and access to identity data is determined based on the lifecycle state independent of data-field level access permissions. The lifecycle states include invited, bound, verified, trusted, restricted, and revoked states. The identity data is stored in encrypted form, and the cryptographic control structure includes an identity encryption key, a relationship encryption key, and an access key, wherein the identity encryption key is encrypted using the relationship encryption key and the relationship encryption key is governed through the access key.
[0016] The delegation structure restricts generation of downstream relationship entities based on constraints including lineage depth or number of downstream relationship entities. The revocation mechanism invalidates at least one cryptographic key associated with downstream relationship entities to prevent access to identity data. Access to identity data is enforced at the user devices using device- specific cryptographic credentials.The system further includes a relationship access governance layer configured to evaluate policy parameters associated with each relationship entity to regulate lifecycle state transitions, delegation of downstream relationship entities, access scope to identity data, and revocation conditions.
[0017] The DCE server is configured to store the identity data in encrypted form along with associated cryptographic elements and is restricted from decrypting the identity data due to absence of access to the identity encryption key, thereby maintaining cryptographic isolation of stored data. The system is further configured to support offline exchange of identity data by generating and transferring encrypted exchange payloads between user devices.
[0018] The present invention further discloses a method executed by the dynamic contact exchange system for controlling access to identity data, including steps of receiving an interaction input between entities, creating a relationship entity, assigning and transitioning lifecycle states, controlling access using cryptographic operations based on lifecycle state, and enabling access at a user device based on lifecycle validation.
[0019] The method further includes revocation of upstream relationship entities and preventing access at downstream relationship entities by modifying cryptographic conditions, performing decryption at user devices using device- specific credentials, generating and transferring encrypted exchange payloads between user devices in offline mode followed by synchronization with the DCE server, and generating and linking downstream relationship entities to enable propagation of access along a lineage path.The system of the present invention implements relationship entity-based access control, wherein access to identity data is governed at an association level rather than at a data-field level. The system further employs lifecycle state-driven cryptographic control, such that access permissions dynamically change based on lifecycle transitions of relationship entities. Additionally, the system enables propagation of access through a lineage path via downstream relationship entities, while maintaining controlled constraints on such propagation.
[0020] The system further discloses revocation through modification of cryptographic conditions, enabling prevention of access at downstream entities without requiring direct interaction or deletion of stored data. These features collectively provide a controlled and scalable mechanism for managing access to identity data across multiple entities.
[0021] BRIEF DESCRIPTION OF THE DRAWINGS:
[0022] The objectives and advantages of the present invention will become apparent from the following description read in accordance with the accompanying drawings wherein,
[0023] FIG. 1 shows a schematic of a dynamic contact exchange system with the preferred embodiment of the present invention;
[0024] FIG. 2 shows a schematic illustrating components of a DCE server of the dynamic contact exchange system of FIG. 1;FIG. 3 shows a system architectural schematic of the DCE server of the dynamic contact exchange system of FIG. 1;
[0025] FIG. 4 shows a graph -based representation of dynamic relationship formation and propagation, of the dynamic contact exchange system of FIG. 1;
[0026] FIG. 5 shows a relationship lifecycle including various states of a relationship entity and corresponding state transitions of the dynamic contact exchange system of FIG.
[0027] 1;
[0028] FIG. 6 shows a relationship-centric cryptographic control arrangement explaining layered cryptographic enforcement of access to identity data of the dynamic contact exchange system of FIG.1 ;
[0029] FIG. 7 shows a relationship delegation and lineage model of a dynamic contact exchange system of FIG. 1 showing formation of relationship entities and propagation of access across a plurality of entities in accordance with an embodiment of the present invention; and
[0030] FIG. 8 shows a cascade revocation and access enforcement architecture of the dynamic contact exchange system of FIG. 1, illustrating propagation of revocation across a plurality of relationship entities and enforcement of access restriction through cryptographic invalidation in accordance with an embodiment of the present invention.
[0031] DETAILED DESCRIPTION OF THE DRAWINGS:The invention herein is described using specific exemplary details for better understanding. However, the invention disclosed can be worked on by a person skilled in the art without the use of these specific details.
[0032] References in the specification to "one embodiment" or "an embodiment" means that particular feature, structure, characteristic, or function described in connection with the embodiment is included in at least one embodiment of the invention. The appearances of the phrase “in one embodiment” in various places in the specifications are not necessarily all referring to the same embodiment.
[0033] References in the specification to “preferred embodiment” means that a particular feature, structure, characteristic, or function described in detail thereby omitting known constructions and functions for clear description of the present invention.
[0034] The present invention is illustrated with reference to the accompanying drawings, throughout which reference numbers indicate corresponding parts in the various figures.
[0035] In general aspect, the present invention discloses a dynamic contact exchange system that facilitates seamless and bidirectional identity data including contact data.
[0036] Referring to FIG. 1, a dynamic contact exchange system (hereinafter referred to as “system (100)”) in accordance with the present invention is disclosed. The system (100) includes a DCE (Dynamic Contact Exchange) server (105), a plurality of primary user devices (110), a plurality of secondary user devices (115),a plurality of tertiary user devices (120) and a database (125), a communication network (130). The DCE server (105) communicates with the primary user devices (110), secondary user devices (115) and tertiary user devices (120) via one or more communication networks (130).
[0037] It is to be noted that the DCE server (105) is accessible by multiple users through one or more primary user devices (110-1), (110-2), (110-3)...(110-n) (hereinafter collectively referred to as primary user device (110)), one or more secondary user devices (115-1), (115-2), (115-3)...(115-n) (hereinafter collectively referred to as secondary user device (115)), and one or more tertiary user devices (120-1), (120-2), (120-3)...(120-n) (hereinafter collectively referred to as tertiary user device (120)).
[0038] The DCE server (105) includes a plurality of modules to process requests from the plurality of the primary user devices (110), secondary user devices (115) and tertiary user devices (120) enabling users to exchange their contacts through a unified platform. The DCE server (105) is implemented with a DCE (Dynamic Contact Exchange) engine which ensures that both parties involved in the exchange receive each other’s contact details and update them dynamically.
[0039] The client component of the system (100) is implemented to provide a web interface and a mobile interface. The primary interface is the mobile interface where users access the features of the system (100), including contact exchange, contact updating and saving contact along with meeting hint such as GPS location hint. The secondary interface is the web interface that replicates mobile interfacefunctionality for broader access. The mobile application communicates with the DCE server (105), that hosts backend services supporting scalability, data processing, and security. The system (100) collects, processes, and stores user input, ensuring confidentiality and compliance with relevant access control policies. The system (100) supports real-time contact synchronization, enabling instant messaging and dynamic updating of contact.
[0040] The primary user devices (110) and secondary user devices (115) are the dedicated devices that enable users to communicate with the system (100). The user devices (110, 115, 120) are the digital devices such as handheld devices, tablet, laptop, computer or the like that are configured to communicate with the DCE server (105). The user devices (110), (115), and (120) are configured with a client component of the system (100). However, it is to be noted that the user devices (110), (115), and (120) may be any personal computer (PC), a tablet-style computer, a personal digital assistant (PDA), an internet appliance, a cellular telephone, a smart phone, a laptop, or any other suitable communication device in other embodiments of the present invention.
[0041] The database (125) is configured to store and retrieve the data of the system (100). The database (125) is advantageously stored and automatically updated with the data created within the DCE server (105), and the data received from the user devices (110), (115), and (120). The database (125) stores a database of all registered users and unique visitors who engage with the system (100).
[0042] The communication network (130) is the internet or some other wired and / or wireless data network, including, but not limited to, any suitable wide area networkor local area network. The communication network (130) also supports additional communication technologies such as NFC, Bluetooth, QR codes, barcodes, and other technologies that are compatible with modern smartphones. The DCE server (105) is preferably configured on a high-end computer with a large storage capacity such as high-capacity hard disks, RAM, ROM, etc., one or more fast processors, and one or more high speed network connections.
[0043] Now, in context of the present invention, the primary, secondary and tertiary user devices (110,115, 120) are operated by three types of users, namely primary users, secondary users, and tertiary users respectively. The primary users manage and operate the system (100), for example, administrators, system managers, etc. who oversee and control team- wide interactions and permissions. The secondary users are individual users who utilize and avail the services provided by the system (100) for dynamic contact exchange. For example, the secondary users are the individuals or teams who sign up and manage their contact exchange preferences. The tertiary users are the unregistered users who engage in contact exchange through trigger mechanisms provided by secondary users.
[0044] Further, it is to be noted that in the context of the present invention, the term ‘identity data’ includes contact data, profde data, credentials, and associated metadata, unless stated otherwise.
[0045] Now referring to FIG. 2, a schematic of the DCE server (105) of the system (100) is discussed. The DCE server (105) includes a processing unit (205) having a controller (235) configured to execute one or more stored instructions for facilitating bidirectional contact exchange between users. The controller (235) isimplemented with modules namely an access control unit (240), an orchestrator unit (245), and an exchange unit (250).
[0046] The access control unit (240) is configured with access control policies to maintain security and integrity. The orchestrator unit (245) is configured for serving as the system’s core service providers. The orchestrator unit (245) determines which functional module should handle a given user action. Each functional module represents a distinct service within the system (100).
[0047] The exchange unit (250) is configured for enabling a seamless digital contact exchange experience. The exchange unit (250) enables users to review the contact giver's information before saving it to their contact list digitally. The exchange unit (250) also allows the recipient to reciprocate by sharing their contact details, along with an optional GPS location hint for future reference. The exchanged information is then synchronized with the user's mobile contacts as needed, ensuring a streamlined and efficient process of exchange of contact data.
[0048] The exchange process is initiated through one or more trigger points including NFC Tag, QR codes, Barcodes and other technologies. Each user possesses a uniquely programmed NFC tag embedded. The NFC tag enables the seamless transfer of contact details when the devices are placed in the close proximity. A QR code is generated by the system for each user, representing their contact information. The recipient scans the QR code with their device’s camera, which loads the contact information onto their device. The system may also support additional communication technologies such as barcodes, or other technologies available on modern smartphones.In accordance with the preferred embodiment of the present invention, the system of the present invention is implemented with online and offline functionality. The system of the present invention supports both online and offline modes. In offline mode, contact exchange may still occur using technologies like Bluetooth or QR codes, though certain features may be limited until the system is online. The offline functionality ensures the system remains useful even in environments where network connectivity is unavailable or unstable. In offline mode, exchange is performed through encrypted exchange payloads generated at the client device, ensuring that identity data remains protected until synchronization with the DCE server (105).
[0049] Further, the DCE server (105) includes an input / output (VO) interface (220) for communication with other devices (110), (115) and (120). The VO interface (220) is connected to one or more VO devices (225). The DCE server (105) also includes one or more network interfaces (230) to enable communications between the DCE server (105) and other networked devices. Such network interfaces (230) may include one or more network interface controllers (NICs) or other types of transceiver devices configured to send and receive communications over the communication network (130).
[0050] The DCE server (105) also includes one or more buses or other internal communication hardware or software that allow for the transfer of data between the various modules and components of the DCE server (105). The DCE server (105) includes a memory (210). The memory (210) provides storage of computer-readable instructions, data structures, program modules, andother data for the operation of the system enables a seamless and dynamic contact exchange experience among users.
[0051] The DCE server (105) also includes a data repository (215) to store information for operations of the system (100) and for storing profiles of users and contacts uploaded by the secondary users. The data repository (215) provides dedicated global storage for each user. The data repository (215) stores local data, including a database of all secondary users and tertiary users who engage with the system (100). The data repository (215) ensures that all data related to specific users are organized and easily accessible, eliminating confusion and enhancing data management.
[0052] In accordance with the present invention, the database (125) represents a system- level persistent storage, whereas the data repository (215) represents a logical data management layer within the DCE server (105), configured to organize, index, and retrieve identity data (602), relationship metadata, and policy parameters. The data repository (215) operates over the database (125) and does not constitute an independent physical storage layer.
[0053] Further, each user device (110, 115, 120) includes a client-side storage configured to locally store encrypted identity data, exchange pay loads, and synchronization data, wherein such client-side storage operates in coordination with the DCE server (105) for access enforcement and data synchronization.
[0054] Now referring to FIG. 3, a system architectural schematic of the DCE server of the system (100) is now discussed. The DCE server (105) includes a plurality ofmodules namely a trigger mechanisms module (305), a user actions module (310), an orchestrator module (315), an exchange module (320), a registered user management module (325), a data retrieval (330), and an access control module (335).
[0055] The trigger mechanisms module (305) is configured to initiate the contact exchange process, enabling seamless interaction between users. The user actions module (310) manages the user actions of the primary users, secondary user and tertiary users as per the prescribed access-based policies. The orchestrator module (315) is implemented for assigning and scheduling tasks for handling a specific user action. The exchange module (320) ensures that both parties are mutually connected and keep their contact details updated.
[0056] The registered user management module (325) ensures that each request submitted by users or registered users is subject to validation and authorization prior to processing. When a registered user initiates a contact exchange, a mechanism is employed to ensure that the recipient (user) is only able to view the specific information the registered user has selected to share. This controlled access ensures a secure and seamless exchange process.
[0057] The data retrieval module (330) maintains profiles of all the registered users and stores data shared within the system (100). The access control module (335) implements authorization policies before granting access to any users to services of the system (100). The primary, secondary and tertiary users are prompted for necessary permissions before accessing resources.Referring to FIG. 4, the relationship graph (400) includes a plurality of nodes representing entities including a first entity (402), a second entity (404), a third entity (406), and a fourth entity (408). Each node corresponds to a distinct user or device participating in the dynamic contact exchange system. A plurality of directed edges are established between the nodes, wherein each edge represents a relationship entity governing exchange and access of identity data between the corresponding entities. Each relationship entity (410, 412) represents a relationship edge node within the relationship graph (400), wherein access to identity data is governed based on lifecycle state and associated cryptographic context of the respective relationship entity rather than through object-level or data-field level permissions. In particular, a first relationship entity (410) is established between the first entity (402) and the second entity (404), denoted as R (A, B). A second relationship entity (412) is established between the second entity (404) and the fourth entity (408), denoted as R (B, C). Further, an additional relationship path originating from the third entity (406) to the second entity (404) is also illustrated, representing formation of another relationship entity between said entities.
[0058] In accordance with the present invention, each relationship entity is configured as a stateful and cryptographically governed association, wherein access to identity data is determined based on lifecycle state, cryptographic context, and policy parameters associated with the respective relationship entity.
[0059] The figure also shows a propagation lineage (416) extending from the first entity (402) to the fourth entity (408), representing a chain of delegated relationships through intermediate entities. A propagation lineage (416) defines anordered sequence of relationship entities through which access to identity data is selectively propagated, such propagation being governed by lifecycle state and corresponding cryptographic context associated with each relationship entity.
[0060] In accordance with the present invention, the relationship graph (400) enables tracking of relationship lineage across multiple entities, controlled delegation of access through intermediate nodes, and enforcement of lifecyclebased access control across the propagation chain. In a further embodiment, revocation of any upstream relationship entity results in disruption of downstream propagation within the relationship graph (400), thereby preventing access to identity data by downstream entities.
[0061] Now referring to FIG. 5, the lifecycle state diagram (500) includes a plurality of states including an invited state (501), a bound state (502), a verified state (504), a trusted state (506), a restricted state (510), and a revoked state (512).
[0062] In this one embodiment, a relationship entity is initially established in the invited state (501). Upon occurrence of an identity exchange event (514), the relationship transitions to the bound state (502), indicating establishment of a basic association between entities. From the bound state (502), the relationship may transition to the verified state (504) through a verification process (516), wherein authenticity of participating entities is confirmed. Upon satisfaction of predefined trust conditions, the relationship transitions from the verified state (504) to the trusted state (506) through a trust upgrade process (518).The trusted state (506) enables delegation of access through a delegation operation (520). In certain embodiments, the delegation operation enables propagation of access privileges to downstream entities while maintaining linkage with a parent relationship.
[0063] In certain conditions, the relationship may transition from the bound state (502) to the restricted state (510) based on policy enforcement rules. Further, a policy violation event (524) may cause transition from the restricted state (510) to the revoked state (512). Additionally, the trusted state (506) may directly transition to the revoked state (512) through a revocation event (526) initiated by an upstream entity or system policy. The revocation results in invalidation of associated cryptographic context, thereby preventing further access to identity data.
[0064] Further, the delegation operation associated with the trusted state (506) enables downstream propagation of access relationships while maintaining parentchild relationship lineage for policy enforcement and revocation control.
[0065] Each state transition is associated with corresponding actions including cryptographic key generation, validation, update, or invalidation, thereby ensuring that access to identity data is dynamically governed based on lifecycle state.
[0066] Referring to FIG. 6, the cryptographic control structure (600) includes an encrypted identity payload (602) representing identity data (including contact data, profile data, credentials, metadata) secured using an identity encryption key (604). The identity encryption key (604) is encrypted using a relationship encryption key (606), thereby forming a wrapped identity key (612), wherein the relationshipencryption key (606) is associated with a relationship entity between participating entities.
[0067] The relationship encryption key (606) is further encrypted using an access key (608), thereby forming a wrapped relationship key (614), wherein the access key (608) is configured based on lifecycle state and policy parameters associated with the relationship entity. The access key (608) is encrypted using a device key pair (610) associated with a client device (620), thereby forming a wrapped access key (616), wherein the device key pair (610) includes a public key and a private key, and the private key is retained at the client device (620) for decryption. The client device (620) may comprise any one of the primary user devices (110), secondary user device (115), tertiary user device (120), or any other authorized computing device configured to access the system (100).
[0068] The cryptographic control structure (600) further comprises an access token (618) configured to represent authorization and lifecycle state validation associated with the relationship entity, wherein the access token (618) is generated and managed by a DCE server (105).
[0069] It is noted that in operation, access to the encrypted identity pay load (602) is enabled upon successful validation of the access token (618) and sequential decryption of the wrapped access key (616), the wrapped relationship key (614), and the wrapped identity key (612), thereby retrieving the identity encryption key (604) for decryption of the encrypted identity pay load (602).In accordance with the present invention, the DCE server (105) is configured to store the encrypted identity payload (602) and associated wrapped keys without possessing the capability to decrypt the identity encryption key (604), thereby maintaining cryptographic isolation of identity data. The modification of lifecycle state or invalidation of the access key (608) results in failure to decrypt the relationship encryption key (606), thereby preventing access to the identity encryption key (604) and the encrypted identity payload (602). The DCE server (105) stores encrypted identity data and associated cryptographic elements without possessing visibility into decrypted identity data, thereby enabling enforcement of access control without exposure of underlying identity information.
[0070] Referring to FIG. 7, the relationship delegation and lineage model (700) includes a first entity (702), a second entity (704), a third entity (706), and a fourth entity (708), each representing a user or a corresponding client device participating in the system. In this one embodiment, a first relationship entity (710) is established between the first entity (702) and the second entity (704), denoted as R (A, B), wherein the first relationship entity (710) defines a stateful association including lifecycle state, cryptographic context, and policy parameters governing access to identity data.
[0071] Subsequently, a second relationship entity (712) is established between the second entity (704) and the third entity (706) through a delegation operation, denoted as R (B, C), wherein the second relationship entity (712) is created independently while being logically associated with the first relationship entity (710). Further, a third relationship entity (714) is established between the thirdentity (706) and the fourth entity (708), denoted as R (C, D), thereby extending the delegation chain to additional downstream entities.
[0072] In this one embodiment, each relationship entity (710, 712, 714) is configured as a distinct stateful entity, wherein lifecycle state, cryptographic context, and access conditions are maintained independently for each relationship while preserving logical linkage through delegation. The relationship delegation and lineage model (700) further includes a plurality of delegation links (716) representing parent-child associations between relationship entities, wherein the second relationship entity (712) is derived based on the first relationship entity (710), and the third relationship entity (714) is derived based on the second relationship entity (712). The relationship entities (710, 712, 714) continue to operate as edge-level control units governing access propagation along the lineage path (718).
[0073] A lineage path (718) is defined extending from the first entity (702) to the fourth entity (708), representing a propagation chain through successive relationship entities, wherein the lineage path (718) enables tracking of access propagation across multiple levels of delegation. The access propagation control (720) is applied across the lineage path (718), wherein access to identity data at each downstream entity is determined based on lifecycle state and cryptographic conditions associated with corresponding relationship entities.
[0074] The relationship delegation and lineage model (700) further defines a policy constraint boundary (722) associated with the fourth entity (708), wherein propagation of access and creation of downstream relationship entities are subjectto predefined policy constraints, including restrictions on delegation, access scope, and lifecycle conditions. Each relationship entity operates independently in terms of lifecycle transitions and cryptographic enforcement, while maintaining linkage through the delegation links (716), thereby enabling controlled propagation of access and traceability across the lineage path (718). Revocation or modification of an upstream relationship entity affects downstream relationship entities through the lineage path (718), wherein access propagation control (720) enforces restriction or termination of access at downstream entities based on updated lifecycle state and cryptographic validity.
[0075] FIG. 8 illustrates a cascade revocation and access enforcement architecture (800). Accordingly, the architecture (800) includes a first entity (802), a second entity (804), a third entity (806), and a fourth entity (808) interconnected through a plurality of relationship entities including a first relationship entity (810), a second relationship entity (812), and a third relationship entity (814) forming a lineage path.
[0076] In this one embodiment, prior to revocation, the relationship entities (810, 812, 814) are active, thereby enabling propagation of access across the entities along the lineage path. In this one embodiment, a revocation trigger (816) is initiated at the first relationship entity (810), causing the first relationship entity (810) to transition to a revoked state. Upon revocation of the first relationship entity (810), a cascade propagation path (818) is established, wherein downstream relationship entities (812, 814) are affected based on lineage linkage.The cascade propagation path (818) is represented using dashed arrows indicating propagation of revocation from the first relationship entity (810) to downstream relationship entities (812, 814). The revocation is enforced through cryptographic invalidation (820), wherein cryptographic context associated with downstream relationship entities becomes invalid.
[0077] As a result, downstream entities including the third entity (806) and the fourth entity (808) experience access failure (822), wherein access to identity data is denied due to invalid cryptographic context.
[0078] It is understood, however, that the dashed arrows further indicate that revocation propagation occurs without requiring direct interaction with downstream entities, and access restriction is enforced through invalidation of relationshipdependent cryptographic conditions. The propagation of revocation across the lineage path is governed by relationship dependencies and policy constraints, thereby enabling controlled enforcement of access termination across multiple levels of delegation.
[0079] In this one embodiment, the dynamic contact exchange system operates through creation, evolution, delegation, and termination of relationship entities, wherein access to identity data is governed through lifecycle state and associated cryptographic context. Initially, a first entity (A) initiates an interaction with a second entity (B) through a contact exchange interface. Upon initiation, a relationship entity R (A, B) is instantiated, the relationship entity being associated with an initial lifecycle state corresponding to an invited state. At this stage, identity data is not yet accessible and is maintained in an encrypted form.Upon successful exchange of identity data between the first entity and the second entity, the relationship entity transitions from the invited state to a bound state. In the bound state, a cryptographic context is established, wherein an identity encryption key and a relationship encryption key are generated and associated with the relationship entity. Access to identity data remains controlled and subject to further lifecycle transitions. Subsequently, the relationship entity transitions to a verified state upon completion of a verification operation, wherein authenticity of participating entities is confirmed. Upon satisfaction of predefined conditions, the relationship entity transitions to a trusted state, wherein access permissions are elevated and controlled sharing of identity data is enabled.
[0080] In accordance with the present invention, the trusted state enables delegation, wherein the second entity (B) initiates interaction with a third entity (C) resulting in creation of a new relationship entity R (B, C). The relationship entity R (B, C) is independently instantiated while maintaining linkage with the upstream relationship entity R (A, B) through a lineage association. Similarly, further delegation may result in creation of R (C, D) with a fourth entity (D), thereby forming a propagation chain.
[0081] In accordance with the present invention, each relationship entity maintains an independent lifecycle state, while being associated with a lineage path enabling tracking of propagation across entities. Access to identity data at each downstream entity is governed by lifecycle state and cryptographic context associated with the corresponding relationship entity. The access to identity data is enforced through a layered cryptographic architecture, wherein identity data is encrypted using anidentity encryption key, the identity encryption key being secured through a relationship encryption key, and further governed through an access key associated with lifecycle state. Decryption of identity data is permitted only upon satisfaction of lifecycle conditions and validation of cryptographic dependencies.
[0082] In certain conditions, a relationship entity transitions to a restricted state based on enforcement of policy constraints, wherein access to identity data is limited without complete termination of the relationship entity. A revocation event is initiated at an upstream relationship entity, resulting in transition of the relationship entity to a revoked state. Upon revocation, cryptographic context associated with the relationship entity is invalidated, thereby preventing further access to identity data. Revocation propagates across the lineage path; wherein downstream relationship entities are affected through dependency on upstream cryptographic context. Such propagation is enforced through invalidation of keys associated with downstream relationship entities, resulting in inability to decrypt identity data at downstream entities.
[0083] Cascade revocation is performed without requiring direct interaction with downstream entities, wherein enforcement is achieved through dependency-based cryptographic invalidation associated with the lineage structure. Lifecycle transitions of relationship entities are dynamically governed based on system events, policy constraints, and cryptographic conditions, thereby enabling controlled creation, delegation, restriction, and termination of access to identity data across multiple entities.The system (100) further includes a relationship access governance layer configured to regulate creation, transition, delegation, restriction, and revocation of relationship entities. The relationship access governance layer operates in conjunction with the relationship graph representation (400), the relationship state transition architecture (500), the relationship-centric cryptographic control arrangement (600), the relationship delegation and lineage model (700), and the cascade revocation and access enforcement architecture (800), thereby enabling coordinated governance of access to identity data across a plurality of entities.
[0084] Each relationship entity is associated with a set of policy parameters stored as metadata. The policy parameters define permissible operations applicable to the relationship entity, including delegation permissions, access scope, propagation constraints, lifecycle conditions, and revocation triggers. The policy parameters are evaluated during lifecycle transitions and access operations governed through the cryptographic control arrangement (600).
[0085] The relationship access governance layer governs delegation of relationship entities as illustrated in the relationship delegation and lineage model (700). Delegation from an upstream relationship entity (710) to a downstream relationship entity (712) is permitted only when the upstream relationship entity is in a lifecycle state eligible for delegation, including the trusted state (506), and when associated policy parameters satisfy predefined conditions. Further, constraints are enforced including limitation on lineage depth along the lineage path (718), restriction on the number of downstream entities, and verification status of the target entity. Uponviolation of such constraints, creation of downstream relationship entities is restricted.
[0086] An access scope is defined for each relationship entity, wherein the access scope determines the extent of identity data (602) accessible to a target entity. The access scope is enforced through the relationship-centric cryptographic control arrangement (600), wherein identity data (602) is encrypted and access is enabled through controlled availability of cryptographic keys including the identity encryption key (604), the relationship encryption key (606), and the access key (608). Selective access is achieved by segmenting identity data (602) and providing corresponding cryptographic access in accordance with the policy parameters.
[0087] Lifecycle transitions of relationship entities are validated through the relationship access governance layer, wherein transitions between lifecycle states defined in the relationship state transition architecture (500), including transition from invited state (501) to bound state (502), from verified state (504) to trusted state (506), are permitted upon satisfaction of predefined conditions. Failure to satisfy such conditions results in the relationship entity remaining in its current state or transitioning to the restricted state (510).
[0088] Revocation of relationship entities is initiated based on policy conditions including explicit user action, violation of constraints, expiration of validity, or detection of security -related events. Upon revocation of an upstream relationship entity (810), propagation of revocation is determined along the lineage path (818), wherein downstream relationship entities (812, 814) are affected based on dependency conditions. Revocation is enforced through cryptographic invalidation(820), resulting in denial of access to identity data (602) at downstream entities, thereby causing access failure (822).
[0089] The relationship access governance layer performs dynamic evaluation of policy parameters during operation of the system (100), wherein decisions relating to access, delegation, and lifecycle transitions are determined based on current system conditions, contextual factors, and relationship lineage. This enables adaptive governance of relationship entities and ensures that access to identity data (602) remains synchronized with lifecycle state and associated policy conditions.
[0090] It is understood, however, that the relationship access governance layer operates in coordination with a distributed system architecture, wherein the DCE server (105) evaluates policy parameters, manages relationship metadata, and generates authorization tokens, and client devices enforce access through cryptographic validation and perform decryption of identity data. The DCE server (105) stores encrypted identity data and associated cryptographic elements without possessing capability to decrypt the identity encryption key (604), thereby maintaining cryptographic isolation as defined in the relationship-centric cryptographic control arrangement (600).
[0091] Now referring to FIGS. 1-8, one mode of operation of the dynamic contact exchange system (100) is described. The system (100) includes a client component operatively connected to the DCE server (105) via a communication network (130). Primary users access the system through an administrative interface for managing permissions, policies, and analytics, while secondary users access it via a userinterface for contact exchange. Tertiary users may interact through temporary links or exchange triggers without prior registration.
[0092] In operation, the system (100) receives one or more inputs corresponding to interaction events between entities, including initiation of a contact exchange between a first entity and a second entity. The inputs may include identity data (602), contact information, authentication credentials, contextual attributes, device identifiers, session parameters, policy constraints, lifecycle conditions, and cryptographic inputs including device key pairs (610) associated with user devices (110, 115, 120). A secondary user may first store identity data and contact information within the system (100) for subsequent sharing and may activate one or more exchange mechanisms including NFC, Bluetooth, QR codes, barcodes, or equivalent proximity and machine -readable technologies. Upon activation of an exchange event, the system (100) retrieves selected profile data of the secondary user and presents the same to a recipient entity, which may correspond to another secondary user or a tertiary user.
[0093] Upon receipt of the interaction input, the system (100) creates a relationship entity (410) between participating entities, as represented within the relationship graph (400) of FIG. 4. The relationship entity is initially assigned an invited state (501) within the lifecycle state architecture of FIG. 5. Following successful authentication and exchange validation, the relationship entity transitions successively to a bound state (502), a verified state (504), and a trusted state (506), subject to satisfaction of predefined policy conditions. During such transitions, the relationship access governance layer evaluates policy parameters to determinepermissible transitions, access scope, delegation eligibility, and lifecycle compliance.
[0094] Once the exchange event is initiated, the recipient device receives a web interface, application interface, or equivalent client interaction page. The interface provides selectable options to save received contact details locally, initiate reciprocal sharing of contact information, request additional details, or establish a persistent connection. Upon mutual confirmation, the system (100) completes the bidirectional exchange and generates acknowledgements to participating entities.
[0095] Concurrently, the system (100) processes identity data (602) in accordance with the relationship-centric cryptographic control arrangement (600) of FIG. 6. The identity data (602) is encrypted using an identity encryption key (604), which is protected through a relationship encryption key (606), and further governed through an access key (608). The access key (608) is associated with lifecycle state and policy permissions of the corresponding relationship entity and is encrypted using the device key pair (610) of the relevant user device. The DCE server (105) generates an authorization token (618) for validating access rights and lifecycle eligibility.
[0096] Access to identity data (602) is provided only upon successful validation of lifecycle state, policy permissions, and cryptographic dependencies. Decryption is performed at the authorized user devices (110, 115, 120) through sequential decryption of wrapped keys, thereby ensuring controlled and conditional disclosure of identity data without exposing underlying plaintext data to the DCE server (105). The DCE server (105) stores encrypted identity data (602) without possessingcapability to decrypt the identity encryption key (604), thereby maintaining cryptographic isolation and enhanced security.
[0097] Following successful exchange, the system (100) performs synchronization functions, wherein received contact information may be stored within the device contact repository of the recipient entity. Where reciprocal sharing occurs, returned identity data is stored within a secured private space associated with the initiating secondary user. Such data may thereafter be synchronized automatically or selectively with local address books, enterprise repositories, collaboration platforms, or client-side databases.
[0098] The system (100) further generates engagement analytics and interaction statistics based on completed exchanges. Each recipient interaction may be associated with a unique session or entity identifier, enabling the initiating secondary user to monitor connection history, response activity, follow-up opportunities, and continuing engagement. Where permitted, subsequent profile updates may be selectively propagated to previously connected entities in accordance with lifecycle state and applicable policy conditions.
[0099] The system (100) further supports delegated propagation of access through creation of downstream relationship entities, as illustrated in FIG. 7. When a downstream entity interacts with an intermediate authorized entity, a new relationship entity (712) may be created and logically linked with an upstream relationship entity (710) through a lineage path (718). Each downstream relationship entity maintains an independent lifecycle state while remaining subject to lineage dependencies and governance policies. The relationship accessgovernance layer evaluates delegation permissions, propagation limits, trust status, scope restrictions, branching thresholds, and contextual rules before permitting creation of downstream relationship entities. Accordingly, controlled propagation of identity access is achieved without direct unrestricted transfer of original identity data.
[0100] The system (100) additionally processes revocation events, whether initiated by user action, expiry conditions, security triggers, violation of policy parameters, or other system-defined events. Upon occurrence of a revocation event (816) affecting an upstream relationship entity (810), the affected entity transitions to a revoked state (512), as illustrated in FIG. 8. Revocation propagates through the lineage path (818) to dependent downstream relationship entities (812, 814). Such propagation is enforced through cryptographic invalidation (820), wherein dependent keys, tokens, or access parameters become unusable. As a result, downstream entities experience access failure (822), and decryption of identity data (602) is prevented without requiring deletion of stored encrypted data or direct communication with each downstream entity. Selective, staged, partial, or conditional revocation may also be implemented according to policy conditions.
[0101] Accordingly, the relationship access governance layer dynamically evaluates policy parameters, lifecycle states, trust conditions, contextual factors, and lineage dependencies to regulate creation, exchange, delegation, restriction, synchronization, survivability, and revocation of relationship entities. The DCE server (105) performs policy evaluation, metadata management, analyticsgeneration, and token issuance, while the user devices (110, 115, 120) perform client-side decryption, synchronization, and enforcement of access conditions.
[0102] The dynamic contact exchange system (100) may be implemented in multiple configurations while preserving the core principles of relationship-based lifecycle governance, cryptographic access control, delegated propagation through lineage, and cascade revocation. Interaction between entities may be facilitated through a mobile application executing on user devices (110, 115, 120), a webbased interface, an enterprise application integrated with organizational infrastructure, communication platforms, collaboration environments, customer relationship systems, or identity management ecosystems, wherein relationship entities (410) are created through authenticated sessions over one or more communication networks. Relationship creation may occur through direct user interaction, automated triggers, contextual system events, secure device pairing, APIs, or equivalent exchange mechanisms.
[0103] The identity data (602) associated with entities may include contact information, structured identity attributes, professional credentials, organizational permissions, profile media, or enterprise-specific metadata or privileged information. In one embodiment, the identity data (602) is segmented into multiple data sets, wherein each segment is independently encrypted and selectively accessible according to lifecycle state, access scope, and policy parameters enforced through the cryptographic control arrangement (600). The cryptographic control arrangement (600) may employ symmetric encryption, asymmetric encryption, hybrid key management schemes, tokenized access models, secureenclaves, trusted execution environments, hardware security modules, or protected containers for generation, storage, and processing of cryptographic keys.
[0104] The lifecycle state framework (500) may include additional intermediate states, alternate transition paths, or customized progression models depending upon implementation requirements. Likewise, the sequence and validation criteria of lifecycle transitions may be adapted for enterprise workflows, regulated environments, secure communication systems, or multi-party exchanges. Processing within the system (100) may occur in real time or asynchronously, including scheduled intervals, synchronization sessions, queued workflows, or batch operations. The system (100) may further be implemented using centralized, distributed, or hybrid architectures, including cloud nodes, federated systems, decentralized networks, or blockchain-enabled identity frameworks.
[0105] By way of example, a first entity (A), using one of the user devices (110, 115, 120), initiates interaction with a second entity (B) during a professional meeting. Upon initiation, the system (100) creates a relationship entity R (A, B) within the relationship graph (400). The relationship entity is initially assigned an invited state and subsequently transitions to a bound state and a verified state following successful authentication and exchange of identity data (602). Access to selected identity data (602) of the first entity (A) is then enabled at the device of the second entity (B) in accordance with lifecycle state and cryptographic conditions. Thereafter, the second entity (B) initiates interaction with a third entity (C), resulting in creation of a downstream relationship entity R (B, C) within the lineage structure (700). The downstream relationship entity is independently governedwhile maintaining logical association with the upstream relationship entity R (A, B).
[0106] Prior to such delegation, the system (100) evaluates policy parameters, trust conditions, and propagation permissions. If the first entity (A) initiates a revocation event, the relationship entity R (A, B) transitions to a revoked state, and revocation is propagated through the associated lineage path, resulting in cryptographic invalidation of dependent downstream relationship entities including R (B, C). Consequently, access to identity data (602) at the third entity (C) is denied without requiring direct communication with the third entity or deletion of encrypted stored data.
[0107] A person skilled in the art will appreciate that the system (100) provides substantial technical advantages over conventional identity exchange systems. The system (100) enables lifecycle-driven access control, independent stateful relationship entities, scalable identity propagation through lineage-linked downstream entities, cryptographic compartmentalization of identity data on a per-relationship basis, cascade revocation through cryptographic invalidation, conditional restriction states, separation of storage and access enforcement, efficient synchronization with client-side repositories, and reduced computational and communication overhead, since access control is enforced through lifecycle validation and cryptographic conditions without repeated transmission of identity data or continuous centralized permission checks.
[0108] In accordance with another embodiment of the present invention, the system of the present invention is implemented with feature of integrated communication.Once two users are connected, they may begin communication immediately through an instant messaging (IM) platform integrated into the system. This feature removes the need for users to switch between applications to initiate a conversation.
[0109] In accordance with yet another embodiment of the present invention, the system of the present invention is implemented with enhanced contact sharing features. Users may optionally share their current location as a hint for future reference and profile picture during the exchange. This feature allows recipients to easily identify the sender and provides context for the contact exchange, improving the user experience.
[0110] The system of the present invention advantageously eliminates the need for manual data entry or exchange of physical business cards, thereby providing a quick, seamless, and efficient contact- sharing experience. The system further ensures mutual connectivity between participating users, wherein both parties receive each other’ s details through a bidirectional exchange mechanism.
[0111] The system additionally enables users to update their contact information in real time, wherein such updates are automatically communicated to connected users, thereby ensuring availability of current and accurate information. Further, the system supports offline functionality, enabling contact exchange even in areas having limited or no network connectivity.
[0112] Moreover, the system incorporates enhanced sharing features including optional location sharing and profile picture exchange, thereby making the contact exchange process more personalized, contextual, and effective for users. Theembodiments were chosen and described in order to best explain the principles of the present invention and its practical application, to thereby enable others skilled in the art to best utilize the present invention and various embodiments with various modifications as are suited to the particular use contemplated.
[0113] It is understood that various omission and substitutions of equivalents are contemplated as circumstance may suggest or render expedient, but such are intended to cover the application or implementation without departing from the scope of the present invention.
Claims
CLAIMS:
1. A dynamic contact exchange system (100) for controlled access to identity data, the system (100) comprising:a DCE server (105) configured to store an identity data (602) and to manage relationship metadata associated with a plurality of entities;a plurality of user devices (110, 115, 120) associated with the plurality of entities, each user device configured to receive identity data (602) and perform access operations based on device-specific credentials;a relationship graph (400) including a plurality of relationship entities (410), each relationship entity representing an association between at least two entities;a lifecycle control framework (500) configured to assign a lifecycle state to each relationship entity (410) and to transition the lifecycle state based on one or more interaction events;a cryptographic control structure (600) configured to control access to the identity data (602) based on the lifecycle state of the relationship entity (410);a delegation structure (700) configured to generate one or more downstream relationship entities (712, 714) linked to an upstream relationship entity (710) to enable propagation of access along a lineage path (718); anda revocation mechanism (800) configured to transition a relationship entity (410) to a revoked state and to propagate revocation to one or more downstream relationship entities (712, 714) by modifying one or more cryptographic conditions to prevent access to the identity data (602).
2. The dynamic contact exchange system (100) as claimed in claim 1, wherein each relationship entity (410) maintains an independent lifecycle state.
3. The dynamic contact exchange system (100) as claimed in claim 1, wherein access to the identity data (602) is determined based on lifecycle state of the relationship entity (410) independent of data-field level access permissions.
4. The dynamic contact exchange system (100) as claimed in claim 1, wherein the lifecycle states include invited (501), bound (502), verified (504), trusted (506), restricted (510), and revoked (512) states.
5. The dynamic contact exchange system (100) as claimed in claim 1, wherein the identity data (602) is stored in encrypted form at the DCE server (105).
6. The dynamic contact exchange system (100) as claimed in claim 1, wherein the cryptographic control structure (600) includes an identity encryption key (604), a relationship encryption key (606), and an access key (608).
7. The dynamic contact exchange system (100) as claimed in claim 6, wherein the identity encryption key (604) is encrypted using the relationship encryption key (606) and the relationship encryption key (606) is governed through the access key (608).
8. The dynamic contact exchange system (100) as claimed in claim 1, wherein the delegation structure (700) restricts generation of downstream relationship entities (712, 714) based on one or more constraints including lineage depth or number of downstream relationship entities.
9. The dynamic contact exchange system (100) as claimed in claim 1, wherein the revocation mechanism (800) invalidates at least one cryptographic key associated with downstream relationship entities (712, 714) to prevent access to the identity data (602).
10. The dynamic contact exchange system (100) as claimed in claim 1, wherein access to the identity data (602) is enforced at the user device (110, 115, 120) using device- specific cryptographic credentials.
11. The dynamic contact exchange system (100) as claimed in claim 1, wherein the system further includes a relationship access governance layer configured to evaluate one or more policy parameters associated with each relationship entity (410) to regulate lifecycle state transitions, delegation of downstream relationship entities (712, 714), access scope to identity data (602), and revocation conditions.
12. The dynamic contact exchange system (100) as claimed in claim 1, wherein the DCE server (105) is configured to store the identity data (602) in encrypted formalong with associated cryptographic elements, and is restricted from decrypting the identity data (602) by absence of access to an identity encryption key (604).
13. The dynamic contact exchange system (100) as claimed in claim 1, wherein the system is configured to enable exchange of identity data (602) in an offline mode by generating an encrypted exchange payload at a first user device (110, 115, 120), transferring the encrypted exchange payload to a second user device (110, 115, 120) without network connectivity, and synchronizing the encrypted exchange payload with the DCE server (105) upon restoration of network connectivity.
14. A method executed by a dynamic contact exchange system (100) for controlling access to identity data, the method comprising:a. creating, at a DCE server (105), a relationship entity (410) representing an association between a first entity and a second entity, the relationship entity being a stateful access control unit;b. assigning a lifecycle state to the relationship entity (410);c. transitioning the lifecycle state based on one or more interaction events or policy conditions;d. generating a cryptographic control structure associated with the relationship entity;e. controlling access to an identity data (602) based on the lifecycle state and the cryptographic control structure; andf. enabling access to the identity data (602) at a user device (110, 115, 120) based on validation of the lifecycle state.
15. The method as claimed in claim 14, further including steps of:a. receiving a revocation event associated with an upstream relationship entity (710);b. transitioning the upstream relationship entity (710) to a revoked state; c. identifying one or more downstream relationship entities (712, 714) linked through a lineage path (718); andd. propagating revocation to the downstream relationship entities (712, 714) by invalidating one or more cryptographic keys or access parameters associated therewith, thereby preventing decryption of the identity data (602) at the downstream relationship entities without requiring direct communication with the downstream relationship entities.
16. The method as claimed in claim 14, wherein enabling access includes performing decryption of the encrypted identity data (602) at a user device (110, 115, 120) using a private key associated with a device- specific cryptographic key pair, wherein the decryption is performed through sequential decryption of one or more wrapped cryptographic keys including a relationship encryption key and an identity encryption key associated with a relationship entity (410), and wherein the decryption is permitted only upon validation of a lifecycle state and one or moreaccess parameters associated with the relationship entity (410), such that the identity data (602) is not exposed in decrypted form to the DCE server (105).
17. The method as claimed in claim 14, further including steps of:a. generating an encrypted exchange payload at a first user device (110, 115, 120);b. transferring the encrypted exchange payload to a second user device (110, 115, 120) in an offline mode; andc. synchronizing the encrypted exchange payload with the DCE server (105) upon restoration of network connectivity.
18. The method as claimed in claim 14, further including steps of:a. generating a downstream relationship entity (712, 714) based on an upstream relationship entity (710); andb. linking the downstream relationship entity (712, 714) to the upstream relationship entity (710) through a lineage path (718) to enable propagation of access.
